SAP Logistics

 At times, there will be a situation where you want to control the accounting document type, not based on the billing type ( which in general is a standard behaviour) instead should determine it in a custom manner like based on company code etc. In this situation to accomplish the requirement, below below-mentioned exit needs to be implemented. EXIT_SAPLV60B_001

 Standard Storage Type A physical area in the warehouse where products are stored. SAP has pre-configured a number of standard storage types. Identification Point An area within a warehouse where goods are labelled, identified, and/or checked during the putaway process. Pick Point A physical area within the warehouse where goods are checked, labeled, inspected, and/or packed during the goods removal process. Identification and Pick Point An area within a warehouse where both identification (Identification Point) and picking (Pick Point) takes place. Staging Area Group A material staging area, or many material staging areas, in the warehouse. Work Center A physical area within the warehouse where processes such as deconsolidation, inspection, packing or value added service processing take place. Doors A door or many doors is a certain physical location within a warehouse, for example, the doors to the west of the warehouse. Yard A yard adjacent to the warehouse. Automati...

 SAP note “1606493 – SAP EWM deployment options best practices”.  The major differences between embedded EWM in SAP S/4HANA 2020 and a de-central EWM are described in SAP note “2938306 - SAP S/4HANA 2020: Release information and restrictions for EWM in SAP S/4HANA”  2938308 - Release information and restrictions of Decentralized EWM on S/4HANA 2020” Stock Room Management reuses major parts of LE-WM and can be used beyond 2025. For details about this solution see the SAP Note 2270211 - S4TWL - Warehouse Management (WM). 2808143 - Overview: Batch management for decentralized EWM SAP S/4HANA” for details about the limitations and supported processes.

At times, business wish to have custom criteria to perform availability check. In this situation, we can make use of the customer exit  'EXIT_SAPLATPC_001 ' to manipulate the values before passing on the data to perform availability check of a specific material.

 At times, there will be situations where we are required to trigger a specific set of data during the creation/saving of shipment documents. In this situation, we are required to leverage the BADI 'BADI_LE_SHIPMENT' to accomplish the requirement 

if the business requires to implement some conditions during auto purchase order creation through ME59N transaction then we can use the below exit so that we can manipulate the values in the purchase order during creation. EXIT_SAPLME59_001

Sometimes, there will be a business requirement to pass on a few details from the sales order to the purchase requisition. In this situation, we have to leverage the below BADI/Method to accomplish this requirement. BADI_SD_SALES_ME_REQ~MOVE_FIELD_TO_ME_REQ

Business some times requires to populate data like profit center in the accounting document based on certain criteria rather than through the regular way of  fetching from material master. In this situation, we have to leverage the below mentioned customer exit to populate the values in the accounting document. EXIT_SAPLV60B_004 Thank you

At times, there will be requirement where business requires leading zero's to be displayed for the GTIN's. In this situation, rather than going for the conversion exit there is a specific config changes to be done to accomplish the requirement. The below highlighted field in the screenshot is required to be maintained with the maximum character length so that if the GTIN is characters are less than the max. length then the rest of missing characters will be displayed with the leading zeros. Thank you.

At times, delivery is not distributed to the EWM from S/4 but however, but the status of the delivery is distributed status.  In this situation, we are required to follow the below process to fix the issue. Solution Approach Execute FM /SPE/DELV_RESET_DIST_STATUS with delivery # and status D. This will allow editing delivery in S/4. Now go to VL02N and click on save so that delivery gets distributed to EWM Thank you.

In EWM, we will come up with a scenario where the queue doesn't exist and the flow is not completed. Due to this, there will be a discrepancy in stocks.  In this situation, follow the below process to fix the issue. Perform physical inventory in EWM and set the parameter /SCWM/IF_DEBUG_QRFC  as "X" for a specific user, this will make the Queue stop in SMQ2  Thank you.

 Below are the commonly used transactions in SAP EWM Monitor  /N/SCWM/MON Outbound Delivery ODO    /N/SCWM/PRDO Maintain Wave     /N/SCWM/WAVE Inbound Delivery   /N/SCWM/PRDI Internal Move product/ Create WarehouseTask    /N/SCWM/ADPROD Move HU/ Create HU WarehouseTask     /N/SCWM/ADHU Make Posting Change for Product   /N/SCWM/POST Confirm Warehouse Task    /N/SCWM/TO_CONF Log on RF Environment    /N/SCWM/RFUI Pack station    /N/SCWM/PACK Process Transportation Unit     /N/SCWM/TU Physical Inventory Create Phy Inv Doc       /N/SCWM/PI_CREATE Enter count Results          /N/SCWM/PI_COUNT Difference Analyzer         /N/SCWM/DIFF_ANALYZER Master Data Maintain Resource      /N/SCWM/RSRC WorkStation Master Data       /N/SCWM/TWORKST APO Product      ...

 At times, we might require validations to be maintained during warehouse creation like keeping an error message during the creation of a warehouse task if an open warehouse task exists for the same HU As standard SAP behaviour will not restrict warehouse task creation of the same HU that contains an open warehouse task already.  In this situation, we are required to implement BADI '/SCWM/EX_CORE_CR_INT_CR' to accomplish this requirement Thank you

 As per standard SAP behaviour, if we move the HU to another HU with the transaction /SCWM/ADHU, the destination HU will become a nested HU. if we want to move the stock without HU, we can use transaction /SCWM/ADPROD Field ' Control F. HU Pick' in the warehouse process type controls this behaviour. Thank you

At times, business requires to manipulate the delivery of foreign trade data such as country of origin or dispatch country etc..based on certain custom parameters. In this situation, we have to make use of the exit 'EXIT_SAPLV50E_003' to accomplish this requirement.

The system validates against the copy control table TVCPF and throws the mentioned error message. As a subsequent action, check if the billing document type is new then maintain the required copy control setup to fix the issue. Thank you

There will be situation where we require to amend the existing delivery Idoc with that of custom segments. In this situation, while generating the IDoc we are required to populate the custom segments values. Exit 'EXIT_SAPLV56K_002' can be used to handle this requirement. Thank you

 Pass the delivery number in the table  SER01 and fetch OBKNR Pass OBKNR into table OBJK to fetch serial numbers for the specific delivery We can use the same process as mentioned above for all SER* tables to fetch the respective data. Thank you

 Below is the logic to fetch equipment number from functional location Step 1 : Pass the functional location into table ILOA and fetch ILOAN Step 2 : Pass ILOAN into table EQUZ to fetch equipment number Thank you.

 At times, we will have a requirement to add custom fields in the customer master data. These new fields need to be sent to the other system through Standard  Idoc with DEBMAS message type. In this situation, we have to append new custom segment to the customer Idoc type and then populate the custom segment field values through the exit  EXIT_SAPLVV01_001 .  

 Below are the commonly used exits at shipment document level EXIT_SAPLV56U_003 is used for handling number ranges i.e, sometimes there will be a requirement to have the same shipment number as that of the DWM in that case, you can leverage this exit EXIT_SAPLV56U_004 is used to write custom functionality or validations based on the shipment status