Skip to main content

[SAP EWM] Posting from EWM due to closed posting period

 Solution Approach :

If you want to correct the faulty queue entries with message M7 053 without debugging, you must activate user parameter DLV_POSTING_DATE.

You have the following options for this:

Call transaction SU01 and add the user parameter DLV_POSTING_DATE to the master data of the EWM qRFC user. To activate this value, set it to "X" or set an eight-digit posting date (YYYYMMTT). This user is used when executing in SMQ2 with F8.

The users in question can maintain the parameter themselves using transaction SU3 and the menu option "System" -> "User Profile" - > "Own Data". However, to be able to use this, the qRFC user must be a dialog user. Furthermore, the ParameterID is valid only for debugging the EWM queue (F8).

The set user parameter leads to the actual posting with the date according to the ParameterID only after the second posting in transaction SMQ2. If the system issues error message M7 053 at least once, an entry is created in table /SPE/COMM_DATA. This is then deleted with the actual adjustment posting. If you have have entered an invalid date for the user, the system, for example, issues error message FGV 004. The ParameterID must be entered in the form "YYYYMMTT" or for the current date "X" (for example, for January 2, 2013: 20130102).

Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Revenue Account Determination - SAP SD

Revenue account determination is one critical integration point between Sales & Distribution and Financial Module. Here on posting a billing document to account, based on this revenue account determination, system determines relevant G/L accounts for revenue posting. As like any other basic function configuration like pricing, its configuration also based on condition technique. The condition technique is used in account determination in order to allocate the correct GL account and account key assigned in the pricing procedure against condition types carries the condition values from SD to FI. IMG -> SD -> Basic Function -> Account Assignment -> Revenue account determination -> Check master data relevant for account assignment. Through check master data relevant for account assignment, one has the opportunity to create account assignment grouping criteria. This grouping criteria provides the system with an extra variable in determ

Determinations in SAP SD

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport