|
原帖由 Phoenix_Reborn 于 2011-7-15 09:21 发表 ![]()
Cann't access the SAP note.
Note 49995 - MMIM: Valuation of return deliveries and GR revrsls
Symptom
1. The return delivery or reversal of a goods receipt for a purchase order, scheduling agreement, or production order is valuated differently than the original goods receipt.
2. In the case of a return delivery or reversal of a goods receipt for a subcontract order, the component is reversed on the basis of a different value than in the case of the original goods receipt.
3. In the case of a return delivery or reversal of a goods receipt for a purchase order or scheduling agreement, delivery costs are valuated differently than in the case of the original goods receipt.
4. The reversal of a goods receipt returns (movement type 162) for a purchase order or scheduling agreement is valuated differently than the original returns (movement type 161).
5. During the return delivery or reversal of a goods receipt for a purchase order, scheduling agreement the negativ delivery costs (as rebate accruals) are valuated differently than during the original goods receipt.
Other terms
Return delivery, GR/IR clearing account, valuation, MB01, MB31, MBRL, MBST, BWA102, BWA106, BWA122, BWA161, BWA162, BWA543, BWA544, BWA545, BWA546, material document, exchange rate, reversal, conversion, provision of material, freight, subcontracting, subcontract order, subcontractor scheduling agreement, volume-based rebate, returns item, WRX, MMVAL
Reason and Prerequisites
This situation can occur in the following cases:
Note: In the following examples, the amount which the system posts to the GR/IR clearing account is given in each case. The examples apply to both, to assigned purchase order items and to purchase order items that are not assigned or production order items or scheduling agreement items.
1. Case A:
There are two goods receipts with different values. This situation occurs when the order price between the two goods receipts was changed. The system valuates the return delivery or the reversal with the average value of goods received.
Example: 100 pieces of a material are ordered at 10 DEM per piece.
1. Goods receipt: 10 pieces at 100 DEM
Price change in the purchase order: Order price now 12 DEM per piece.
2. Goods receipt: 10 pieces at 120 DEM, so that a total of 20 pieces was posted with DEM 220.
Return delivery (or reversal) of 10 pieces is now valuated with the proportional value of goods received of 10 pieces * 220 / 20 pieces = 110 DEM.
2. Case B:
There are two goods receipts with different values in local currency for a purchase order in foreign currency. This situation occurs with an unchanged order price if different exchange rates between external and local currency were used for the two goods receipts. The system valuates the return delivery or the reversal with the average value of goods received in local currency.
Example: 100 pieces of a material are ordered at 7 USD per piece.
1. Goods receipt: 10 pieces at 70 USD or 100 DEM, with an exchange rate of 70 USD = 100 DEM.
2. Goods receipt: 10 pieces at 70 USD or 120 DEM, with an exchange rate of 70 USD = 120 DEM now. Now, 20 pieces with DEM 220 were posted as a receipt in total.
Return delivery (or reversal) of 10 pieces is now valuated with the proportional value of goods received of 10 pieces * 220 / 20 pieces = 110 DEM.
3. Case C:
An invoice with a different amount is posted after a goods receipt. A later return delivery (or reversal) is carried out with the invoiced amount. If the invoice is net-posted, this is the invoiced amount minus cash discount.
Example: 100 pieces of a material are ordered at 10 DEM per piece.
Goods receipt: 10 pieces at 100 DEM
Invoice: 10 pieces at 110 DEM.
Return delivery (or GR reversal): 10 pieces at 110 DEM.
4. Case D:
An order price unit (OPUn) (different to the order unit (OUn)) was defined in the purchase order. The relationship between quantity in OUn and quantity in OPUn is different in the (sum of all) goods receipts to that in the (sum of all) invoices.
Example: 100 pieces of a material are ordered at 1 DEM per kg.
1 piece (OUn) correspond to 10 kg (OPUn)
Invoice: 100 pieces with 1000 kg at 1000 DEM
Goods receipt: 90 pieces with 950 kg at 950 DEM
Goods receipt: 10 pieces with 100 kg at 100 DEM
Return delivery: 10 pieces with 105 kg at 105 DEM
The difference of 5 DEM in the valuation of the return delivery (or reversal) is a result of the system determining the returned quantity in OPUn - as long as the user has not entered anything different - with the portion of the returned quantity in OUn (10 pieces from 100 pieces, since in OPUn 105 kg from 1050 kg), and valuating with the proportional value delivered to date.
5. Case E:
There are two goods receipts for one subcontract order with a component being posted with different values. This situation occurs if the material price of a component has changed between two goods receipts. The system evaluates the return delivery or the reversal with the average value of the adjustment postings.
Example: material price is 10 DEM per piece.
1. Goods receipt: Adjustment posting of 10 pieces of 100 DEM
The material price changes to 12 DEM per piece.
2. Goods receipt: Adjustment posting of 10 pieces of 120 DEM so that a total of 20 pieces with DEM 220 have been posted.
The cancellation of the adjustment posting of 10 pieces is now valuated with the proportional value of 10 pieces * 220 DEM / 20 pieces = 110 DEM.
This valuation logic in its general sense is used for delivery costs too.
This valuation logic in its general sense is used for returns items too.
This valuation logic in its general sense is also used for negative delivery costs.
For users of the subsequent settlement function:
When you change fields for subsequent settlement or change the document conditions (pricing), please note the following:
A new pricing or other changes to the document conditions (also implicit changes by changing price-relevant fields, see Note 486757) are allowed only, if goods receipt quantity and invoice quantity are zero, i.e. if there are either no follow-up documents or if the follow-up documents were cancelled completely. This is called an open purchasing document item.
Otherwise - apart from the posting of undesired accrued incomes - the sales date become inconsistent too, i.e. the reconstruction and the detailed statement provide different data from the ones determined in previous updates (see statistics statement).
The background is that due to the data model all essential data are stored in the purchasing document. A change may cause data to be lost for all existing follow-up documents so that the sales data can no longer be determined correctly. This means that all updates would be carried out with the sales data existing after the change instead of the values that were originally valid.
Example: GR1 was updated with 100 p - 1 000 USD. then, the document conditions are corrected, GR 2 - 100 p - 1 200 USD is posted. Both the detailed statement and the reconstruction/subsequent update determine a total of 200 p - 2 400 USD. The information regarding GR1 are lost. As a matter of course, the statistics statement function will display 200 p - 2 200 USD. Only after the reconstruction, the result would be 200 p - 2 400 USD. This does not correspond to the posted values, however.
[ 本帖最后由 LostHorizon 于 2011-7-15 10:32 编辑 ] |
|