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. Anonymous14 February 2019 at 23:45

    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

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

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...
1 comment
Read more