From fast two years I have been working on WM module on lean and extended warehouse management so what I would like to know is when look at inbound and outbound delivery who suppose to work on shipping,picking,packing,tranporation,stoarge unitit,handling unit manegemnt,yard management on this scenarious whether SD consultant should work or WM consultant should work.
Becuase when I tested in SAP easy access in both modules above said transactions functionalitys are there. so that's why I would like to confirm.
Starting with SAP EWM 9.0 it is possible to visualize route information on the SAP geo-map component Visual Business. How the displayed map content can be configured is described in the following knowledge snippet provided by SAP Transportation Management:
Everyone may not like keying in user name into the Barcode scanners or PDAs commonly used in warehouses. I had an opportunity to observe the end user community in a Hospital store going through this learning curve. The warehouse picker community involves temporary workers who may be introduced to handle mobile devices for the first time or may have gone through totally different device UI in another warehouse.
The idea of creating and scanning the barcode in lieu of keying in is certainly not new, however, I thought of putting the tip into this site to help whomsoever it may be worth a penny!
Scan to Log into the PDA Scanner:
Is the Scanner keyboard too sensitive? You can’t see the soft keys properly? Do you have a complex User Name or Password and struggle to enter into the Scanner? Bar Code helps you to simply scan a piece of paper and get into the scanner!
Step-1 Convert your User Name into Bar Code and print on a Sheet of Paper (It doesn’t have to be a Label).
Step-2 Simply scan the Bar Code next time when you need to enter the User Name into the Bar Code.
This is a blog item to illustrate a possible methodology to automate the 'goods issue' functionality within EWM for outbound deliveries using a batch job.
I posted a query in the EWM community hoping a nicer, better tip would come up. But while waiting for tips, I figured out the following method which is off course just one of many possible options depending on the business processes involved in your Warehouse.
Background:
My client runs a medium sized Warehouse using SAP EWM 7.0 SP6. Business processes are not so complex and custom code is fairly limited to RF functionality other than few reports. He doesn't use the Shipping and Receiving function in EWM, nor he performs loading or transportation activities within EWM. These considerations count towards the solution proposal shown below:
Having stabilized the operations after Go Live, the client was interested in spreading the Goods Issue load during the day Vs current manual job of having to go to the transaction /scwm/prdo, select confirmed ODOs and press the 'goods issue' button. One issue with this operation is slowing down of RF devices the moment a big bunch of deliveries were goods issued.
Method proposed considering the functionality being used in this Warehouse:
It is evident that the goods issue is processed by a PPF action in EWM. So, I worked backwards in steps to figure out how to automate the steps.
I did not find any job to mimic the action of clicking on the goods issue button in /scwm/prdo, hence I focussed on getting it done by PPF itself.
SAP provides the report RSPPFPROCESS (transaction: SPPFP) to manually select and process PPF actions. Based on this, I decided to first to change the setting on "Send message to ERP" PPF action to non-automatic.
My next goal is to 'mimic the goods issue action' itself within EWM. In order to do so, I found that after the Warehouse Task confirmation, I need to achieve the task of Goods Issue without the user intervention. Warehouse pickers use RF devices to complete picking and confirm the warehouse tasks. However, the goods issue action was not automatic. I noticed the PPF action for the goods issue function:
I set the processing time on this PPF action to 'Processing when saving document'.
Handling the statuses:
To my surprise, though I had made the goods issue PPF action automatic, deliveries were not getting goods issued. This led me to check what is preventing the goods issue. I noted that when I complete the "LOADING" activity, the delivery was now ready to be goods issued. The standard SAP steps leading up to the goods issue were: Pick-Pack(optional)-Load(optional)-Goods issue.
I did not want to retain the loading the get the loading PPF action completed automatically, nor I had the flexibility or the incentive to spend more time researching the options. Since the customer was not using the loading functionality and not earmarked to use it in the distant future, I thought I could perhaps switch off the loading indicator leading up to the goods issue.
I recognize that this kind of decisions are subjective and perhaps best to decide with the customer input and SAP centre of excellence input (if there is one).
I set the "Loading" status as 'inactive' for the outbound delivery document:
In order to do so, I created my own Z*status profile and preserved the standard SAP status profile. I attached the Z*profile to my ODO.
Effect: Now as soon as the Warehouse task of a Warehouse order is confirmed, system completes the goods issue and creates a message to send out to ERP. For performance control, I kept the goods issue action non-automatic and used batch job to send the message in a defined frequency to ERP. Stock status will not be synchronized with ERP until the goods issue message is sent out to ERP. This was not a major concern in our business process.
Options:
We have two options. (1) Keep the goods issue PPF action processing manual and create a batch job for this step or 2) Keep the goods issue processing automatic upon WT confirmation as described above.
If you go with the option-1, you may set up 2 batch jobs as shown below:
Batch Job-1 Z_PPF_POSTGOODSISSUE_STEP1
Batch Job-2 Z_PPF_POSTGOODSISSUE_STEP2
Both jobs use the same report program ‘RSPPFPROCESS’ (transaction: SPPFP).
Batch Job-1 processes the ‘create goods issue in EWM’ PPF action
Batch Job-2 processes the ‘send goods issueto ERP’ PPF action
Side effect:
I also noted a side effect which was positive for the customer's business process. Earlier, when the warehouse clerk manually goods issued many deliveries together, all those deliveries got combined into one EWM material document based on system's own grouping decisions. Though efficient, the problem with this is when you want to reverse the goods issue, you will end up reversing goods issue for all those related deliveries together.
With the batch job processing, we noticed that goods issue was done with separate material document per delivery.
Further:
We are currently assessing the full impact and performance issues if any. Personally, I intend to look at the business process at a higher perspective and try to find bottlenecks with this approach with future enhancements. I will keep an eye at EWM community as well looking for tips and better approaches. Meanwhile I hope this documentation helps other like me who have just stepped into the EWM area and looking for knowledge tips.
Note: Due to the 1mb size limit, I could not attach 2 more test results. Interesting to not that SCN does not allow PDF or WORD attachments.
I meet with a lot of clients who ask this question. They believe in the best of the breed systems and a proven history of operating warehouses successfully.
In the past I used to give detailed answers about how great EWM features are, how it can support the business, etc. Now I smile and begin my round of questions with "Why wouldn't you like EWM?"
Don't you want to reduce operational costs?
Don't you want to improve customer delivery performance?
Don't you want to improve inventory visibility?
Don't you want to improve fill rates and provide real time delivery status to your customer?
How about empowering your people with data on how they are performing?
How about taking your decisions by leveraging data on how your network is performing?
The list is long but typically 2-3 questions are enough for my clients to understand what SAP EWM can do for their business.
The logic is "simplicity with complexity". With cost containment pressures and fluctuating demand, supply chain executives are looking for systems that will be simple to install, simple for people to follow, while still supporting complex processes.
Simplicity - unlike other BOB systems, SAP EWM does not require bolt-ons for labor management, slotting, yard / dock management, kitting, cross-docking, MHE management and many other processes. Having these capabilities in a single platform reduces IT cost and provides one system for Business to learn and operate.
Simplicity extended - EWM is scalable from small warehouses to large warehouses. An entire supply chain can now operate on a common backbone thereby improving information sharing.
Complexity simplified - "but large warehouses have complex processes that are an over kill for small warehouses. How do we manage that?" Answer is not in the software but in the design of how you operationalize the system with different templates. Further, think of EWM as a supply chain system and not just a warehouse management system. In my previous blog entry, Developing an Integrated Supply Chain, I had highlighted the benefits of an integrated supply chain. EWM integrates your warehouse with front office functions, hence helping you to improve customer experience.
The Myth –“EWM is expensive to implement.” This statement was true not too long ago. 2011 was a remarkable year as cloud technology evolved and industry took a turn. Think of EWM as Software as a Service that reduces your total cost of ownership. And, even with limited skill set there are new ways of accelerating implementation to reduce your CapEx.
Well, I can keep going but you have a business to run. Send me an email if you find yourself in the situation I have described above.
Augmented Reality (AR) technology enhances our perceptions and improves the user experience in a revolutionary way. Our challenge is to transfer this technology to the manufacturing world. What if you could see animated instructions upon the reality and interact with them instead of using clipboards or going to a kiosk to enter data?
A team of SAP colleagues of different areas built an augmented reality pilot that is based on google glasses together with our customer Bechtle. Bechtle is a German IT distributor, SAP Consulting implemented EWM at Bechtle. This pilot is based on EWM but does not use our RF framework. In various design thinking workshops together with Bechtle, a vision has been established which has been captured in a videoand also a mock up has been built. This can be seen as basis for further projects to enable operators in the warehouse to work more effectively.
SAP and Vuzix (the partner for the glasses) are piloting an AR hands-free solution built for industrial applications while leveraging existing SAP investments. Enterprise information is visible right before the worker’s eyes while allowing the worker to stay focused on their work and environment. With data coming in real-time from machine-to-machine sensors and SAP systems, workers can respond quickly with unmatched situation awareness such as knowing what and where to pick inventory, receiving alerts and instruction to handle maintenance and getting safety messages to avoid accidents from a blind spot. These are just a few use cases where warehouse management, assembly, field installation, testing, machine tooling and repair operations represent a dazzling opportunity for the implementation of AR tools.
This was also presented at SAPPHIRE and shows how SAP Extended Warehouse Management is driving innovations as a best in class warehousing solutions in the market.
Knowledge source: EWM RF Cookbook is a great source of information, however illustrates only the generic processes and does not dwell into specific situations and requirements.
EWM RF Configuration: Switching off a Screen cannot be accomplished using EWM RF configuration node activities alone. The steps/transactions sometime are decided by the corresponding RF Function Modules/programs (~akin to hard-coding). We may treat this as the limitation of EWM wizard currently.
Case: Switch off the following screen that comes up during the activity 'Putaway by WO' (3-1-1). Customer reason: HU is not being used for putaway.
Upon investigation, we noticed that the transaction code is expected by the system irrespective of configuration for screen flow. This was further confirmed by useful reply from SAP for our customer message.
The Function Module /SCWM/RF_PT_WO_NAVIGATION was responsible for calling the step. It was deemed that a minor enhancement is the only cost-effective choice to achieve the end result.
Relevant SAP Notes: Since the customer's system was at EWM 7.0 SP6, it needed the SAP Notes to resolve issues with ITS Mobile templates, Presentation profiles and RF Logical Transactions. Following notes were choses and implemented:
1736194 Resolves error in ITS templates when changes are made to standard screens
1754368 Resolves SAP program error when a an existing Presentation Profile is copied into new one
1521250 Re-use of standard RF Logical transactions
Solution Steps:
An enhancement was created in the FM /SCWM/RF_PT_WO_NAVIGATION as shown below. It simply set the function code to GTPLMT to make system skip the step PTMASC.
SAP co-innovates with customer Bechtle using a Design Thinking approach to create a show case for a mobile application in the area of augmented reality (AR).
In a joint effort, with partners Buena la Vista and Vuzix, SAP proved its ability to be a frontrunner in new technologies: AR glasses (like Vuzix M100 or Google Glass) offer hands-free communication to help speed up business processes.
Our team of highly motivated colleagues from different areas of expertise across SAP concentrated on a logistics use case. The warehouse picking process (see video) uses device features like bar code scanning, voice control, reading information aloud, and displaying relevant information in the field of view. With this exciting new technology the warehouse worker can be guided to the right storage area to pick a product, highlight the relevant bin and scan the bar codes of bins, handling units and products.
Although the technology is not yet mature and still perhaps expensive for broad adoption, we already see a high interest. Especially for warehouse workers, for example for picking processes, we see a new era ahead with this technology that will increase the speed and accuracy of goods selection.
We’re presently working on prototypes to explore the potential and use cases with customers. AR supporting warehouse processes is on the roadmap to deliver standard products for Extended Warehouse Management in the future.
AR is versatile. Besides consumer applications, we can envision AR supporting different other applications for business users such as service technicians, engineers and manufacturers.
Stay tuned! At TechEd we are planning to demo a prototype running on various glasses with a connection to an SAP EWM backend system.
we made available the SAP Business Content for EWM in BI and I want to run all available extracts. Master data and some other transactional data could be extracted. But I get no data back for Delivery Inbound (0WM_DLVI_IN) and Delivery Outbound (0WM_DLVI_OUT) and Delivery for Planning (0WM_PL_DLVI). Tables in EWM are filled. With t-code RSA3 in EWM I got data extracted. But when I start the extractor from our BI system I got no data returned.
I could not find any useful documentation of the extract logic. I wonder if someone had a similar situation or can help me with documentation of the extract logic.
Sometimes when you tried to unload goods from TU (/n/scwm/tu), you might have got error "Warehouse Process Type XXXX does not allow for immediate confirmation" or "Simple unload is not possible". That means we need to do complex unloading where we need to create Warehouse Tasks for unloading and confirm them.
This blog explains you the steps to be done for complex unloading and possible errors you may come across.
Overview of steps:
Pack goods in TU --> /scwm/prdi
Create WT for Unloading --> /scwm/tu
Confirm the Task --> /scwm/to_conf or /scwm/mon
Assumptions:
Inbound delivery(ies) are distributed to EWM.
Shipment distributed to EWM or TU was created manually in EWM.
TU linked to inbound deliveries in EWM.
TU was checked in & docked at door.
1. Pack the Goods in TU
If HUs are not there already, we need to pack the goods. For this, go to transaction /n/scwm/prdi.
NOTE: If you do any change to Inbound delivery after assigning it to TU, then you may get error "Delivery assigned to TU is inconsistent". In such cases, please click on check button on TU screen, save the TU and try creating WT for unloading.
Now, WT will be created for unloading. This can be verified in the unloading screen (transaction /n/scwm/unload) or by checking the log in TU screen. Log shows HU WT Creation for HU XXXXXXXXXXXXXX with all entries in green.
You can find the task in Warehouse Monitor (transaction /n/scwm/mon) or in TO Confirmation screen (transaction /n/scwm/to_conf). In Warehouse monitor go to Inbound\Documents\Inbound Delivery, enter inbound delivery# and execute. Click on Warehouse Task button by selecting inbound delivery.
To confirm the WT, select WT, go to more functions and use Confirm WT in Foreground/background functions. Alternatively, you can do this from TO Confirmation screen.
In My EWM project we are experiencing issues with the Spanish language display on the RF devices.
Vowels with accent (á, é, í, ó, ú) are not showed correctly in VMC (vehicle mounted computers) and the HH (hand helds), but they are in desktops. Is there something that we can do to correct this? In this example: C3 = ó, C- = í, C: = ú
On RF device in spanish language Vowels with accent (á, é, í, ó, ú) printing as C3 = ó, C- = í, C: = ú but if we login in SAP desktop the Vowels with accent (á, é, í, ó, ú) are coming properly.
Did any one has any idea why these Vowels with accent (á, é, í, ó, ú) in spanish are not coming properly on RF device. Any suggestions will be appreciated.
In this post, I'll explain you the real time GUI display issues with RF screens and how to fix them when you implement RF with EWM using ITS Mobile. This will not cover implementation of RF with EWM. I assume you have prior knowledge about RF device and its functionality, integrating it with SAP EWM. To understand more you can refer RF Cookbook, SAP EWM 120 and Wiki.
General practice to design RF screens in EWM is to
Copy standard Menus, Screens
Modify screens with screen painter and activate
Generate HTML templates and publish
Check with RFUI or by running the related internet service
Here comes the trouble, sometimes what you see in RFUI does not match with browser display (on desktop or in RF device) or you are not able to modify screens with screen painter. In such cases, we can go for updating the HTML templates manually.
This post mainly concentrates on
briefing HTML template
updating HTML templates manually
testing webpages locally on desktop or in RF device
I assume you don't have any knowledge on HTML pages.
What is a HTML template and how to understand it?
In simple terms, HTML template is a combination of logical code and HTML tags. Based on inputs, code inside the template will decide how to display the page by allowing or blocking few sections of HTML tags. If you know basic commands of C you can guess what is the logic running through the page. You can refer W3C website for quick understanding of HTML.
Basic rule to remember is all HTML code starts with character " ` " and end with " ` ". So, the content inside `` is HTML code and the other logical code or comments.
How to identify where and what to be updated in HTML template?
When you are simulating webpages in local desk browser you might have found some issues with screen like height or width of a field or label is not proper, unwanted fields appearing on the screen, missing margin space or extra space, arrangement of screen elements are not in order etc. Most of the modern browsers have Developer Tools feature (in the Tools menu as shown below) with which you can easily identify where to update in HTML template.
Aftering enabling tools, you'll get two panes at the bottom. Left one is to view the source code and right one is to view the properties of selected object/tag. Also there are many tabs in each pane. So, just select the relevant tab to view the code.
Now click on mouse button available in left pane (right under the HTML tab), and select the object on the screen. It will highlight the selected object on the screen and also open ups the relevant code section in the bottom left pane and its properties in the bottom right pane.
Just note down the comments or object name in the HTML code and go to the same in the template. I prefer using Notepad ++ to update template.
After selecting the object like as shown above, try to change the properties in the right pane as desired. As soon as you update the properties in the right pane, same will be reflected in the webpage. So, if you are okay with the modified properties make a note of them and do similar updates in template.
Or, if you want to delete some labels/text boxes from your screen I advise you to comment that section instead of deleting the code from template. So, that you can recall original template whenever you want. Comments start with "<!--" and ends with "-->".
Sample:
<!--not disabled-->
Note that comments should be outside of HTML code that means "`" and "`".
How to publish your changes?
After making updates, copy template code and paste in actual template (SE80). Save changes and publish the template. Refresh your webpage, you should be able to see your changes. If you are kicked out from that page after refresh, go back to code in template and check for syntax errors like opening and closing of HTML tags etc.
Below is an example of screen on RF device before and after.
The field 'Created On' is familiar to SAP users. However, this field is not seen on some regularly used selection screens of Extended Warehouse Management.
We were handicapped by lack of this field while searching for deliveries that were yet to be goods issues on /SCWM/MON transaction. Alternately, we used /SCWM/PRDO to both 'search' and 'goods issue' actions. While /SCWM/PRDO has the 'created on' field, it is not tuned for faster search like /SCWM/MON transaction according to SAP.
We recently took up the case with SAP who actively listened to our need and understood the benefit to business users. We were happy to get the SAP Note 1991270. This note introduces the 'created on' field in the Outbound Delivery Order Node.
I would like to share with all my experience while configuring inbound process using POSC. My scenario is like this.
1. Unload stock from door and put at staging area.
2. Move stock from staging area to final bin.
For this, I have configured POSC with two steps
1. INB1 - to unload stock with automatic creation of put-away task
2. INB3 - to put-away stock
After unloading the stock from door, system shows that there no packed/unpacked stock for unloading. Because, I have already completed the first step and using POSC system automatically created put-away task. After confirming the put-away task surprisingly, I could see the status of document as PutAway - Not Started and Warehouse Activity - Partially Completed.
When I go back to /scwm/prdi, follow on functions --> warehouse task, I could see same HU ready for unloading. When I see this, I was surprised and clueless. After going through my POSC and Warehouse process type, I feel that everything looks okay but still no clue about this weird behavior. Finally I found that storage type role (where final bin belongs to) was set to "D" - staging area group.
After changing this to standard storage type, I was able to set the document status as complete.
Thanks
Sasidhar Gupta
We can play with EWM too not only C/Java programs.
For most of the warehouses, the generic requirement is to reflect the stock in newly configured warehouse in the system. So that it matches with the reality. In EWM, we have two ways for this.
1. Create Initial stock in MIGO of ECC (movement type 561). This creates inbound delivery and distributes to ECC. Once the delivery is in EWM, the normal inbound delivery processing steps are followed.
2. Prepare CSV file with all the products/HUs and their quantities. Upload this CSV file into EWM.
In this, I'll explain the process of uploading the initial stock using CSV file.
After upload, you'll get a log saying HU is created for material and material document posted. By default "Do Not Post Data in ERP" check box will be unchecked. Because of this, after successful upload, material document posted with 561 movement type.
See below material document posted in ECC after stock upload in EWM.(MB51)
URL given above explains you two variants of stock upload.
1. Without HU
2. With HU (internal or external number range)
Also, good thing about this transaction is (/scwm/isu), after upload you can view the file content in CSV(XLS) format there itself and edit and save the data for upload. Otherwise you can also access the files stored on application server.
Few notes from observations:
1. Packaging specification is not required to defined, to upload stock via CSV file.
2. While uploading more than one HU or Product or both, fields HU, Higherlevel HU(if there are multiple layers in one HU), Highest HU, Line ID must be filled appropriately.
HU - This is unique ID for each HU (a sequence number can be given). For HU, this unique ID should be given and for products inside this should be given. On the same lines, respective HU IDs should be filled for Higherlevel HU and Highest HU.
Line ID is a sequence across rows in CSV.
3. After linking product to HU as above, Storage bin mentioned for Highest level HU will only be considered. If you give different bin for product which even does not exist in the wh, no error will be thrown.
eg:
Item Category,Product,Owner,Partner Role,Batch,Stock Type,Type,Sales Order/Project,Sales Order Item,Usage,Party Entitled to Dispose,Partner Role,Country of Origin,Quantity,Base Unit of Measure,Handling Unit Type,Storage Bin,GR Date,GR Time,Shelf Life Exp. Date,Packaging Material,ExternalNumberAssgmt,Handling Unit,Higher-Level HU,Highest-Level HU,Line ID,Reference to Line,Total Weight,Loading Weight,Weight Unit,Tare Weight,Weight Unit,Total Volume,Loading Volume,Volume Unit,Tare Volume,Volume Unit,Total Capacity,Net Capacity,Tare Capacity Key Fig.,Length,Width,Height,Unit of Dimension,Maximum Weight,Excess Wgt Tolerance,Tare Weight Variable,Maximum Volume,Excess Volume Tol.,Closed,Maximum Capacity,Max. Packing Length,Max. Packing Width,Max. Packing Height,Unit of Measure,Serial Number,Valuation Quantity,Valuation Unit,Valuation Measured,Certificate Number
I had already finished the installation ERP 6.0 EHP 7 Server and I want to install Add-on EWM 9.1 package on ERP system. To install, I follow up SAP Note 1892669 - Installing or upgrading to SAP EWM 9.1. When I try to use T-Code : SAINT to install these packages (SCM_BASIS rel. 713 and SCMEWM 9.10), I get this information "The installation of SCMEWM rel. 910 must be configued with a Stack XML". Could you please advise how to fix this problem? Remark : Please see the capture screen in the attached file.
Exception code is not working properly while picking.
Here the scenario we are performing is Fixed bin replenishment. During RF picking a stock shortage is encountered and an exception code is needed to be entered.
After entering the exception code it using internal code od BIDU or BIDF and an giving an error and WT is remail open. The detailed steps i mentioned below.
We have configured separate full pallet storage and partial pallet storage types in our warehouse. When fixed bin replenishment is run, warehouse tasks/warehouse orders are created. The system will create them for the available quantity in a bin. Storage types are configured to have available quantity at storage bin level (HU - neutral). The entire HU is required to be picked and splitting is not allowed. If there is insufficient stock in an HU that is picked the picker is not allowed to enter an exception code to bypass this warehouse task. This is what we need fixed.
Steps to recreate the issue:
Transaction: /SCWM/RFUI
Whse No. = XXXX
Resource = XXXXX
DefPresDvc = XXXXX
Press enter
Select 01 System-Guided
Enter Queue = XXXXXXXX
Press F4 Next (do NOT create a pick hu).
The pick screen will appear.
Warehouse orders exist for this queue, 200000xxxx and 200000xxxx. These are for fixed bin replenishment in case picking.
(Look at the Monitor for HU’s to scan, instructions below)
Enter the SrceHU and press Enter, use an HU with an unrestricted batch.
Enter AQty (Ensure that you do NOT take the full quantity in the HU because you need to get an error message), then press Enter.
You will receive an error message: ‘E: Enter exception code for reporting di’.
[We configured 2 exception codes: ZFUL which uses BIDF and ZRMV which uses BIDU. Both react the same]
Enter Exception Code: ZFUL
Press Enter
You will receive an error message: ‘E: Full bin denial and quantity not perm’.
** The transaction at this point should close the current warehouse task and continue on with the next warehouse order in the current queue. **
Exception Code ZFUL was configured to cancel the Warehouse Task.
One note: If I use exception code NEXT, the picker receives a screen with this message ‘Do you want to send the rest of work back to the pool (split WO)?’. If the user selects Yes, the current task is closed, a new one is opened but the picker is taken completely out of the transaction. This is almost what we want, except the user should remain in the same queue and the next WO should be ready to execute.
If the user selects No, The current task remains open but the picker is taken completely out of the transaction. It should close the task, no new task should be created and user should remain in the same queue and the next WO should be ready to execute.
We need the solution working like NEXT ( EXP Code Intl Process code) Here the problem with NEXT is it is going to appropriate stock discrepancy buring picking for fixed bin replenishment But it is coming out from Queue from RF ( Here we need it should be proceed or continue to next WOfor replenishment).
Is there any Exception code which may fix the issue?. Any Ideas will be appreciated.
Very pleased to say the online selection tool to help assist in deciding between SAP EWM and SAP WM has been updated to include the latest functionality available in EWM 9.1.
This WMS selection tool can quickly help customers on their way to starting to make an informed decision on their SAP WMS platform selection.
The evaluation criteria are a combination of years of experience and the partnership of SAP with Rocket Consulting, an Extended Warehouse Management 'SAP-validated Expertise' accredited partner specialising in SAP Supply Chain Execution solutions.
At the end of the survey the customer receives an immediate indication of the suitability of SAP Warehouse Management vs SAP Extended Warehouse Management based on their requirements. They can also choose to receive a detailed personalised report, ideal for WMS platform selection or inclusion in business case documents.
It is a great starting point to kick start the platform selection.
