Skip to main content

Posts

Showing posts with the label sap ewm

[SAP EWM] Fixed Bins determination

 At technical level, fixed bin will be determined based on the below logic : system will first check for the fixed bin field at the storage type level , if this is checked (  /scwm/t331 - fixbin = 'X' then system will call FM ' /SCWM/BINMAT_READ_MULTI' which will read the data maintained through the bins maintained in the /SCMW/BINMAT transaction at the front end level to fetch the bin data.

[SAP EWM] Source Bin Not found issue

At times, we will struggle with stock being not picked from the source bin, in this situation to investigate from technical level for issue related to the source bin determination, try to keep breakpoint on the FM ' /SCWM/REM_BIN_DET_INT' which will give you some hint related to the root cause of the issue

[SAP EWM] /SCWM/ISU does not consider maximum bin capacity during initial stock upload

As per standard SAP functionality capacity check for /SCWM/ISU is deactivated. This transaction should be used for initial data transfer from old system to EWM (example). That means the stocks must be physical stocks already stored within the warehouse at storage bins. The same would happen if physical inventory will be performed and the user count more then allowed capacity. The system will post the differences without capacity check.  At /SCWM/ISU, and also in physical inventory counting (PI), not all checks against storage type, bin type customizing are performed, compared to 'normal' putaway. The reason for this: Both in initial stock upload, and PI counting, it must be possible to enter stock on a bin the way it physically exists there. Even if it is against the put away rules. 

[SAP EWM ] EWM stocks in /SCWM/ERP_STOCKCHECK is different from /SCWM/MON stocks

  E WM stock is composed by the physical stocks plus the Difference Analyzer stocks. /SCWM/ERP_STOCKCHECK shows the total physical stock quantity of a given warehouse. The Physical Inventory difference was not yet posted on /SCWM/DIFF_ANALYZER, so the stocks still exist in the warehouse as a "difference" yet to be posted. While /SCWM/MON displays only available and physical stocks, not differences. The correct procedure is to run the /SCWM/DIFF_ANALYZER to clear this stock pending, so it will not be shown on /SCWM/ERP_STOCKCHECK as well. If  /SCWM/ERP_STOCKCHECK  has a different EWM quantity than the total physical stock, the difference can be found on the  Difference Analyzer , since the EWM stock is equal to the physical stock plus the Difference Analyzer stock.

[SAP EWM] After zeroing out EWM delivery, non-EWM relevant items are not zeroed out

  Issue After zero out EWM delivery, non-EWM relevant items in the ERP delivery are not zeroed out.\ Solution Approach Do not mix EWM relevant items and non-EWM relevant items into one single delivery. But you can add your own logic in method EXIT_SAPLV50I_004 of SMOD_V50B0001 to change the quantity of non-EWM relevant items to zero when the delivery is zeroed out in EWM.

[SAP SD] Error VL062 in queue for goods issue from EWM

 Issue  Delivery created from a sales order is distributed to the EWM system.  "Partial delivery at item level" is set to 'C' - Only complete delivery allowed Quantity is changed or Goods issue is complete in the EWM system.  Queue fails in the ERP system with error VL062 - "Full delivery is required" Solution Approach Maintain the following entries within your system using transaction OVM1 - if they already exist, adjust them accordingly: Application: 'L' - Shipping processing Call type 'D' - Confirm from external system Call type 'B' - Background processing, multiprocessing with Work phase 'B' Application Area = VL, Message no = 062, Type = I * Call type 'B' with Work phase 'A' is for background delivery creation.

[SAP EWM] Capacity check BADI

 At times, we might need to overrule the existing capacity check of the bins and create a custom rule to determine capacity of the bin, in this situation we have leverage the below BADI to accomplish the requirement /SCWM/IF_EX_CORE_PTS_CAPACHECK~CUSTOM_CAPA_CHECK  Note : This BADI will be called for all types of transfers to the Bin due to that ensure to be careful while implementing this.

SAP EWM - Valuation data maintenance from S4

We use the transaction  /SCWM/VALUATION_SET    'Determine and Set Prices from ERP' to replicate the valuation data for products into the EWM system. For the non-valuated ERP products, not any data is created in the data base table /SCWM/T_VALUATE - Valuation Data for Physical Inventory. It is not possible in EWM to distinguish between just missing valuation data for a product( not replicated ), and non-valuated products.

[SAP EWM ] Change Business System Key after Client Copy

Transaction /SCWM/CONV_BSKEY  can be used to change the business system key in all EWM tables. In addition, customer-specific tables that contain fields with domain SLD_BSKEY can be updated, if they are specified in the parameters of the transaction. The transaction does not update the tables /SCMB/TOWNBS and /SCMB/TBUSSYS. These tables must be manually maintained before executing the transaction. The transaction provides a test run, which checks the number of records per table to be updated. Both the test run results as well as the productive execution will write an application log.

[SAP EWM] EWM Initial Stock Upload with External Amount in Local Currency

Issue : In /SCWM/ISU, there is no option to fill stock items with AMOUNT_LC, External Amount in Local Currency. Analysis : This functionality is not available in the EWM standard until S/4HANA 2021 release. Before that, the EWM standard design did not foresee any price management. Every stock posting from EWM had to be done based on the existing price data on ERP side. Solution Approach : Before upgrading to a higher release, implement BAdI /SCWM/EX_ERP_GOODSMVT_EXT to update the price-related fields AMOUNT_LC and AMOUNT_SV in table CT_GOODSMVT_ITEM for every item to be posted. Note : This BADI will be called for any type of material document posting so this BADI can be used in general for multiple purposes.

[SAP EWM] Notes for implementation (composite SAP Note)

  Stock Data Transfer with /SCWM/ISU: 974852  Stock data transfer using transaction /SCWM/ISU Uploading packaging specifications using /SCWM/IPU: 1726759 uploading packaging specifications using /SCWM/IPU Delivery: 1064376 Customer-specific determinations/validations of the delivery 1071644 BOPF: Manually implementing notes/importing Support Packages 1227714 FAQ: BC Sets and delivery Customizing in EWM 1276862 Generation of outbound delivery with quantity of zero Batches: 990638  Requirement for processes with batches in SCM-EWM 1272566 BAPI_OBJCL_CHANGE: Object for class type is not defined II (valid up to EWM 700) 1305698 Overview of communication/integration of batches ERP bet. EWM 1344366 FAQ: Batch Creation On ERP Side by Using Tx.: VL31N Handling Units (HUs): 1081145 Deleting empty unused handling units Inventory: 1166998 Settings for printing physical inventory documents Quality Management: 1278425 Connecting ERP QM to EWM Radio Frequency (RF): 1091765 En...

[SAP EWM] How to reset/approve the delivery tolerance check

To reset the tolerance check (or approve this under/over tolerance violation), you can follow the steps bellow: Open /SCWM/PRDI transaction (for inbound deliveries) or /SCWM/PRDO transaction (for outbound deliveries); Open your delivery in the respective warehouse number; Select the delivery item blocked with the tolerance check error; Press the button "BBD/Tolerance" and then you have 2 options: Choose "Reset Tolerance Violation" to reset the current block and let the system available re-check the over/under tolerance. Choose "Approve Tolerance Violation" to approve the over/under tolerance and make the delivery item processable.

[SAP EWM] Error message "Delivery assignment to TU &1/&2 is inconsistent" (/SCWM/SHP_RCV177)

 Issue Transportation Unit is blocked with a red flag and you are not able to use it due to error message  "Delivery assignment to TU &1/&2 is inconsistent" (/SCWM/SHP_RCV177 ) Solution Approach To unblock your TU and synchronize the information again, Go to /SCWM/TU transaction, Select your TU, Push the Check button. Save the TU.

[SAP EWM] Configuration changes to be made while setting up new process in EWM

Whenever there is a new process setup by the SD team based on the business cases. It's a good practice to setup new document in EWM level as well.  Below are the config changes to be performed while creation of new document type :  Define Document Types for Outbound Delivery Process (copy from standard OUTB)  Map Document Types from ERP System to EWM  Control Message Processing Dependent on Recipient  Map Date Types from ERP System to EWM  Map Item Types from ERP System to EWM  Define Warehouse Process Type  Determine Storage Type Search Sequence for Stock Removal  Specify Storage Type Search Sequence Note : Always ensure that no process is controlled at the product master level i.e., item level. Some consultants use WPT indicator at product master data level as a parameter to control the business process. This is not good practice as this will have an impact when business try to use the same material for other processes as well.

[SAP EWM] tracking product master changes

 At times, business look for the personnel who did changes for a specific field in the product master. In this situation, SAP has given standard transaction code  '/SCWM/PROD_CD_READ' to view the change documents. Apart from the above transaction, the same can be access through warehouse monitor as well

[SAP EWM ] Process to perform goods movement for delivery through technical level

 There are various ways to perform goods movement for a ODO in EWM : FM -  SCWM/PPF_POST_GM can be accomplish the requirement and this requires import parameters as ' DOCID' and 'DOCCAT' but the challenge for this FM is capturing the return messages. This FM will not return any message. To avoid the above situation, we have alternate way to handle this. Class /SCWM/CL_GOODS_MOVEMENT can be leveraged to accomplish the requirement as well by passing the same parameters as above in method /SCWM/IF_GM_DLV~POST_DLV. In general, this class will be called from the above mentioned FM

[SAP EWM] Warehouse execution status in LE not updated after goods issue is completed in EWM

  In customizing, you can enable that an update is send to LE when warehouse activities are completed in EWM. Customizing path: SPRO -> SCWM Extended Warehouse Management -> Cross-Process Settings -> Delivery – Warehouse Request -> Process Management and Control -> Define Process Profile for Document Header Select the process profile and flag the checkbox “Ready for Shipping (Send Update to LE)”. When the EWM delivery is set to “Ready for Shipping”, the warehouse execution status is also updated in the LE delivery.

[SAP EWM] Error /SCWM/GM034 comes during GI reversal

 Issue : Product has been posted goods issue (GI) from HU AAAA on storage bin BBBB. The GI reversal is stuck by error: /SCWM/GM034: You can only post to bin BBBB using a handling unit Root Cause : During GI cancellation the system tries to post the stock back into the same HU (which has been deleted in the meantime). If this HU no longer exists, it will try to post as unpacked stock to the same bin. However, this can be prevented by error /SCWM/GM034 in case of HUs are obligatory in that storage type and the GI happened by a product warehouse task (WT). Consider also it is not possible to cancel the goods movement and post the stock to a different HU. Solution Approach : In case the GI posting was done by a HU WT, then system re-creates automatically the HU posted for GI. In case the GI posting was done by a product WT there are two options: Option A) Change the storage type settings regarding HU requirement to value ' ' (HU allowed but not a requireme...

[SAP EWM] Analyzing and correcting inconsistencies in the available stocks or the warehouse order status

Below is the approach to be followed to fix the issue : Call transaction /SCWM/CHM_LOG. Choose "Ad-Hoc". On the following screen, choose "Stock and Bin" and enter the selection criteria by choosing the yellow arrow on the right (entry of warehouse number, storage type, and storage bin as required). From the checks available below this node, select "Available Quantity" and then select the line. As a result, the system should display the bulb icon on the left. At the level of the available stocks, you can optionally restrict your selection (arrow) to a transportation unit (TU), resource, or product. Make the selection using F8. The system now checks for inconsistencies. If there are any inconsistencies, they can be corrected by positioning the cursor on a line and right-clicking it, provided that the relevant function supports this. However, the selection criteria should be entered as specifically as possible. A selection that checks an entire storage type w...