Professional Documents
Culture Documents
MM-PUR Training
Trainer : Sanjeev Shrivastava
Confirmations - Sanjeev Shrivastava
Business Process
Example:
A purchase order (PO) is sent to vendor.
Vendor initially sends an OA referencing the PO.
He may then follow this up e.g. with a shipping
notification referencing the PO.
There is no direct link between an order
acknowledgment X and a shipping notification Y
(the information provided by the latter is firmer,
more precise, more up-to-date).
The GR can be posted with reference to the purchase order (PO) or with reference to the
shipping notification. When a confirmation category is entered, the MRP element BS-EIN is
replaced by BS-AVI in the stock/requirements list (transaction: MD04). When the GR is
entered, the MRP element BS-AVI disappears.
Expediting confirmations:
Up to Release 4.5A, the system used the current date to calculate whether the
reminder period had been exceeded. As of Release 4.5A, you can enter a
reference date with which the calculation is to be carried out.
Internal conf. categories give you the option of using Idocs. Only the
aforementioned 3 Idocs are supported by SAP. The customer cannot define
any further internal conf. categories.
The internal definition is especially important with regard to the use of Idocs
because the structure of the later depends on this definition.
1.Confirmation sequence
You define the sequence in which the confirmation categories are expected.
Note:
You can work with a maximum of 8 confirmation categories, the numbers 1 to 8 are reserved for it.
The schedule line in the PO is internally assigned the number 0 and the GR the number 9.
The “GR-reference” indicator should always be selected for the last confirmation category expected in the sequence (i.e. prior to the GR). This is required
by the offsetting logic, so that the last confirmation category is also offset by the GR.
“GR assignment” ensures that goods receipts are assigned to the relevant confirmation in the case of a PO item with several confirmations.
The “GR assignment” indicator is only effective if the “GR relevance” indicator is also selected.
Note: You can find the values in the right column in the requirements list (MD04).
So if the quantities in MD04 are wrong in most of the cases it is a MM-PUR-Problem (not PP).
Offsetting logic:
In a similar way to example 2, first the remaining 35 of the SL are offset (earlier date
and lower sequence no.), then the 25 of the first OA.
Only then do the remaining 5 of the SN offset (reduce) the quantity of the second
OA (with the delivery date 03.18.01).
Tip:
The total of the MRP-relevant quantities must agree with the SL quantity in each
step as long as no GR has yet taken place.
Symptom: Confirmations AND schedule lines are shown in MD04, i.e. reducing as not taken place correctly.
=> Check that the sequence number of the confirmation is <> 0 in Customizing.
(Prior to Rel. < 4.0 there were no checks in Customizing, so that the value 0 was accepted as the sequence
number by the system.
As of Rel. 4.0, the entry of 0 is no longer accepted).
Symptom: Second confirmation overwrites the first -> check ekes-etens is not ‘0000’.
Over-/underdelivery tolerances relate to the GR quantity and PO quantity, NOT to the confirmation quantity.
Non-MRP-relevant confirmations are for information only and do/are not reduced.
Correction reports
Note 215072: Correction of quantities reduced (MRP) for GR assignment
Note 202875: Correction report: Redistribution using batch input
Release dependant functionalities
As of 4.0: Change affecting Customiying tables>
Previously there was one GR/assgt. Indicator for each confirmation category
With Rel. 4.0, you can define an indicator per BSTAE and confirmation category for a more fine-tuned control.
As of 4.5: GR can be posted using VL transaction
As of 4.6: Batch splitting in VL32 / VL33
The END