3rd Part Dropship Scenario with Sales BOM

Question

Hi
We have a 3rd Party Dropshipment scenario with Sales BOM with susequent Debit
Characteristics of Sales BOM
Sales BOM is created
Header Material is Valuated but non-inventorised (Accounting and costing view should exist)
Component Material is Valuated and inventorised
In Sales order, Pricing is done at the header material not at the components level
During Billing we get the COGS for the header material (cost coming from VPRS)
No VPRS exist at component level instead we have copy of VPRS just to capture the value in COPA for our reporting
Process
1. Sales Order created with Sales BOM exploded in sales order.
2. At the Item level Purchase requisition is created.
3. PR for the components is converted to PO
4. Vendor Delivers the components to Customer.
5. Statistical GR done in our system.
6. Invoicing is done in MIRO
7. We directly do the Billing. Billing is created at header level. Revenue and COGS is reported at Header level only.
We are stuck when we are doing the Subsequent Debit (can be for any unplanned cost). For Susequent Debit we are not able to report differential COPA at header level.
Normally whenever you do subsequent debit in case of 3rd party dropship for normal material, COPA document automatically attached to Billing. This is happening because of the behaviour of VPRS condition type. In our case VPRS only exists at header level and not at component level but replenishment is for components. Subsequent debit is also happening at component level. We need it to be reported at header level.
We need some solution to this.
Please advise
Regards
Neeraj
Edited by: NEERAJ BHARDWAJ on Dec 2, 2011 5:12 AM

Answer 1

Hi Raj,
Please clarified your requirement here, you mention that you wanted to valuated COGS at actual cost of PO? That sound more like actual costing here and what is the reason for this requirement?
Is this MTO with variant configuration?
If this is MTO with VC, Yes - we do cost Sales Order and here is the brief steps:-
Price Control S
a) Sales Order Creation - Normally when you save this will be costed and marked automatically. Note that condition type EK02 will represent the cost here
b) Run MRP based on Sales Order requirement which resulting planned orders, PR, etc
c) Convert PR-PO, Planned Order -> Production Order
d) Confirmations, GR on PO which valuated according to the SCE Costing in step a)
e) PGI will be based on the GR value on step d) which is also your SCE Costing
f) Any variance between PO and SCE need to be settle.
Thanks,
Ong Yang Lim