Skip to main content

Pre-requisites for product allocation in SAP SD

Product allocation must be switched on in the requirement class (transaction OVZG) and in the schedule line (transaction VOV6).

Transfer of requirement must be switched on in the requirement class and in the schedule line.

Availability check must be switched on in the requirement class and in the schedule line.

Product allocation determination procedure has been maintained in the Basic data 1 tab in Material Master.


Check your update settings:


  • Check the update setting of the info structure in transaction MC25.
  • For standard info structure S140, you can use the standard formulas 141 – 144.
  • Formula 140 is the standard formula, independent from the info structure, and must always be entered for characteristic Product allocation object.
  • If you use your self-defined info structure, you can use formulas 141 - 144 as a copy reference and you must adjust them to your info structure.
  • The key figure incoming orders quantity (AEMENGE) must be updated. Update must occur on schedule line level (quantity and date are transferred from schedule line, MCVBEP). The formulas of the characteristics are processed on schedule line level. The update date is the delivery date (EDATU).

Check whether statistics groups for Material, Customer, Sales Document Type and Sales Document Item Category are correctly maintained.

Check whether Assign Update Group at Item Level and Assign Update Group at Header Level are correctly maintained.
(Transaction SPRO, Logistics – General, Logistics Information System (LIS), Logistics Data Warehouse, Updating, Updating Control, Settings: Sales)

 Check whether the updating of the info structure is set to synchronous (transaction OMO1). For product allocation synchronous updating is necessary.

You can check the update for each document in transaction MCVR.
Here is displayed which info structures are updated using which update groups.


Check the validity of the product allocation object and the factory calendar:

Check the validity of the relevant product allocation object in transaction OV4Z (V_T190-KTGBI).  Make sure that the date maintained here is inside the validity of your factory calendar.


Check the validity of the factory calendar of the shipping point and the factory calendar of the route. Make sure that the validity of both calendars is maintained at least 2-3 years into the future.

Comments

  1. Thanks for sharing this post about Pre-requisites for product allocation in SAP SD as i got to learn new things from your Blog as its gives best info about procedure for Product allocation determination .Visit now SAP SD Online Training in Hyderabad.

    ReplyDelete

Post a Comment

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