SAP S/4HANA EWM Best Practice Content

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1> VBAK-<Custom Field 2> VBAK-<Custom Field 3> ENDCHAIN. Thank you.

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...

Embedded EWM in SAP S/4HANA (available as basic and advanced EWM)	Basic EWM: Basic Warehouse Inbound Processing from Supplier (‏1FS‏) Basic Warehouse Inbound Processing from Supplier with Quality Management (‏1V9‏) Basic Warehouse Outbound Processing to Customer (‏1G2‏) Batch Management in Outbound Processing (‏1V7‏) Initial Stock Upload for Warehouse (‏1FU‏) Physical Inventory in Warehouse (‏1FW‏) Production Integration - Component Consumption and Receipt in Warehouse (‏1VB‏) Replenishment in Warehouse (‏1FY‏) Scrapping in Warehouse (‏1G0‏) Warehouse Inbound Processing from Supplier with Batch Management (‏1V5‏) Advanced EWM: Advanced Warehouse Outbound Processing to Customer (‏1VD‏) For additional information see SAP note 2483936 (These links point to the 2022 release of SAP S/4HANA and country DE)
Decentralized EWM based on SAP S/4HANA and integrated with SAP S/4HANA	Decentralized EWM - Ad Hoc Goods Issue (‏4RQ‏) Decentralized EWM - Inbound Processing (‏4RO‏) Decentralized EWM - Outbound Processing (‏4RP‏) Decentralized EWM - Physical Inventory (‏4RR‏) Decentralized EWM - Replenishment (‏4RS‏) Decentralized EWM - Technical Integration ERP (‏4UA‏) For additional information see SAP note 2930991 (These links point to the 2022 release of SAP S/4HANA and country DE)

SAP Logistics

Search This Blog