RE: [sap-log-sd] BOM header price

Posted by CIpinza (SAP Senior Consultant)
on Sep 21 at 12:13 PM
Hi,
For SAP this is a typical scenario "Managing Displays in the Consumer Products Industry".
Unfortunately, no easy standard solution exits for this issue.

Definition:
? "Displays" is a consumer products industry term referring to finished products that are assembled from other finished product(s). Typically, pallets of standard product are broken down into individual packages and then re-assembled, sometimes with promotional materials, into new units (trays, cases, pallets). These new, finished products have their own UPC code, but may contain packages from one or more other finished product UPC codes.


? "Displays" may be assembled at manufacturer owned facilities, third-party distribution centers, or co-pack manufacturers.


? Examples of "Displays" include display trays, display shippers, modular pallets, merchandising units, rainbow pallets, banded packs, and pre-priced products.
Business Requirement:
The main business requirements are:


1. Cost-effectively track the sales volume and profitability of a "Display" product and its components.


2. Automatically calculate the 'list' price of a "Display" product based on the list prices of its components.


Conceptual Design:
? Automatically transfer the finished product items from the production bill of material of a "Display" product into the sales order as statistical sub-items for pricing and reporting purposes.


? Note: While the 'SAP Best Practices CP Value Chain' recommends using sales BOM's, with the rapidly growing number of "Display" products that many consumer products manufacturers have to manage, the maintenance of sales BOM's is considered unmanageable.


? Automatically calculate the 'list' price of a "Display" product based on the sum of its individual component prices.


? Note: The pricing elements of the component products that are used to calculate the price of the "Display" product can be flexibly defined. The decimal precision of the calculation can also be controlled to any level of accuracy and can vary by pricing element.


? Define and apply all discount, surcharge, and cost conditions at the "Display" product level only. Automatically suppress these elements for the component sub-items.


? Automatically allocate all revenue, discount, surcharge, and cost conditions of a "Display" product to its finished product components according to the following rules


? Revenue and non-distribution related discounts and surcharges applied to a "Display" product are to be allocated to its finished product components based on the "gross" price of each component.


? Note: The gross price of the components can be flexibly defined.


? Distribution related discounts and surcharges applied to the "Display" product are to be allocated to the components based on the quantity of each component.


? Cost of the "Display" product is to be allocated to the components based on the cost price of each component.


Standard Solution:
The custom solution uses the following standard solution as a starting point. Keep in mind that the standard solution is very basic, and the custom solution involves extensive configuration and user-exit development. This standard solution is intended to capture the component quantities for statistical volume reporting only. This does not include the pricing or profitability dimensions.


? Maintain a sales bill of material for each "Display" product (transaction CS01, usage=5). The sales BOM would be similar to the production BOM, but would only contain the finished product materials and quantities and not packaging, labor, etc.


? Assign item category group 'ERLA' to each "Display" product


? When a "Display" product is entered on an order, the item category group 'ERLA' will trigger the determination of item category 'TAQ'. This item category will trigger a lookup of the sales bill of material and an 'explosion' of the BOM components as sub-items with item category 'TAE'.


? The sub-items with item category 'TAE' are not relevant for shipping, inventory management, pricing, or billing.


Custom Solution:

? No standard solution exists, and custom solution was developed based on the requirements of a specific consumer products manufacturer. Extensive pricing routines and copy control is required.

Regards,
Claudio Ipinza

---------------Original Message---------------
From: Typewriter
Sent: Wednesday, September 21, 2011 3:51 AM
Subject: BOM header price

In my opinion this is an interesting yet "tricky" business requirement!

You are doing pricing at Main item level. Then for your sub-item(s), in item category (VOV7), field Pricing = blank.
This means that in the sales order, in the sub-item level, Tab Conditions, all cond types have value 0 (zero).
Your business requirement is that you want one condition type in that sub-item line, Tab Condition with some value (statistical in nature).

I think for this you would have to change the value in field "Pricing" in VOV7 for that item category.

I could suggest some tests, but I would suggest NOT to go forward with this business requirement.
In BOM if you have pricing either at -
- Main item level
- or at sub-item level
not at both levels.

It might have consequences in posting of accounts, as both main and sub-item are relevant for pricing.

Lets hope that some other members have solutions / ideas, for this requirement.

Please give your feedback, comments.

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
CIpinza
SAP Logistics Sales and Distribution Helper

Posted helpful replies on 5 threads in a group to earn a Bronze Achievement

_.____.__