Requirement: Synchronous posting from EWM2S4 are generally required because of following reasons.

• Avoid hanging queue from EWM2S4
  
• Avoid stock inconsistencies between EWM & S4
  
• Real time storage location extension during posting from /SCWM/ADGI( GM code=04, NWLO from EWM to non-EWM storage location).

Logic of Synchronous Posting from EWM2S4: Activation at warehouse level( SPRO–>Extended Warehouse Management–>Interfaces–>Goods Movements–>Activate Synchronous Goods Movement Posting)

/SCWM/CL_ERP_GOODSMVT_SYNC_S4 is the maintain service class for synchronous posting from EWM2S4.

Two important methods play a pivotal role for synchronous posting

/SCWM/IF_ERP_GOODSMVT_SYNC~SIMULATE_POSTING–> This method checks the corresponding S4 Data like sufficient stock availability or even master data extension like ‘material is extended to storage location or nor in real time to avoid hanging queues and display of error at ‘UI Level’ at 10 EWM relevant transaction.

IS_GM_CODE_ALLOWED: This is the main method displaying the EWM relevant transaction meant for Synchronous posting from EWM to S4. There are total relevant processes, the blog will highlight the /SCWM/ADGI synchronous capability only from EWM to S4.

Below example is moving a Material from EWM managed to IM managed storage location using /SCWM/ADGI, GM Code=4)

System does the real time storage location extension check instead of posting and creating a hanging queue( If No Auto Sloc creation is enable in 411 Mvt type in S4).

The class /SCWM/CL_ERP_GOODSMVT_SYNC_S4 with method /SCWM/IF_ERP_GOODSMVT_SYNC~SIMULATE_POSTING performs all relevant synchronous posting simulation before posting goods movement. In below example, a real time stock availability check is performed during a Material movement from EWM to IM managed storage location.

Similarly all relevant synchronous posting can be conducted from EWM2S4 with below transaction as well which are mentioned

• Difference analyzer(/SCWM/DIFF_ANALYZER)
  
• Difference analyzer(/DIFF_ANA_CAT_CHG)- Stock category change during posting.
  
• Initial Stock upload( /SCWM/ISU)
  
• Posting change ( /SCWM/POST )
  
• /Unplanned Goods Issue( /SCWM/RGI_SCRAP)- /SCWM/ADGI
  
• Stock type change report( R_STOCK_TYPE_CHANGE )
  
• monitor posting change via ‘BBD/SLED Overview’—>MON_DDATES_PC’,
  
• monitor posting change via ‘Physical Stock–> ‘MON_PHYSTO_PC’,
  
• Consumption against PMR- ‘MFG_GI’,
  
• Goods Movement Kanban Staging task Wbse to PSA- TO_KANBAN’,

All relevant information replicated is based on my personal experience and insight. Relevant tests have been performed in S/4 HANA 2023 FPS02 system.

The post Which Synchronous Posting is enabled from EWM to S4 & relevant Service Class for posting appeared first on ERP Q&A.

The purpose of this blog post is to show the configuration steps needed to perform printer determination based on warehouse door during inbound receiving.

Scenario: Lets take an example of a warehouse which has two inbound doors DOR1 and DOR2. Both have a unique printer attached to them. DOR1 is linked to printer YEP1_17 and DOR2 is linked to printer LP01.

Configuration:

1) Define Print Profiles for Delivery Processing:

SPRO IMG > EWM > Goods Receipt Process > Inbound Delivery > Print > Define Print Profiles for Delivery Processing

2) Define Print Profile Determination for Goods Receipt Process

SPRO IMG > EWM > Goods Receipt Process > Inbound Delivery > Print > Define Print Profile Determination for Goods Receipt Process

3) Activate PPF /SCWM/PDI_01_UNLOAD_LIST_PRINT (Transaction SPPFCADM)

4) Setup condition record to trigger printing upon inbound delivery creation in EWM (Transaction /SCWM/DLVPPFC)

5) Ensure that the printer in transaction SPPFCADM -> Condition Configuration (Transportable Conditions) is cleared. This is mandatory to inform the system to determine printer based on configuration

Testing:

1) Inbound Delivery received at door DOR1. PPF action is triggered upon inbound delivery creation and spool generated for printer YEP1_17

2) Inbound Delivery received at door DOR2. PPF action is triggered upon inbound delivery creation and spool generated for printer LP01

Note: – The above scenario has been executed on S4 Hana embedded EWM 2022 sandbox.

The post Printer Determination based on warehouse door during EWM Inbound Receiving appeared first on ERP Q&A.