Inspection lot with origin 17 is created despite QM is deactivated for movement type in OMJJ

Root cause

Creation of inspection lot with origin 17 is controlled by EWM and during inspection planning EWM coding is triggered. Therefore, setting to prevent inspection lot creation in movement type customizing at ERP side (transaction OMJJ) is not considered.

Solution Approach

In order to restrict inspection lot creation in EWM environment, following possibilities can be considered:

A) Use EWM inspection rule to restrict the lot creation for certain document type, item type or other properties. In decentralized EWM landscape, inspection rules are used by default. In embedded EWM landscape, the setting to use inspection rules can be reached at following customizing: transaction SPRO ---> SCM Extended Warehouse Management ---> Extended Warehouse Management ---> Cross-Process Settings ---> Quality Management ---> Basic and Integration ---> Define and Activate Warehouse-Dependent IOTs.

Inspection rules can be maintained in transaction /SCWM/QRSETUP.

B) Check if BAdI /SCWM/EX_QM_INSP_RELEVANCE (method: INSPECTION_RELEVANCE_SET) can be used to prevent inspection lot creation according to the business requirement. This BAdI is available for both decentralized and embedded landscape.

Comments

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

SAP Logistics

Search This Blog