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).

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.

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...