Sales BOM creation

Hi ,
My requirement is that create Sales BOM.
What are FM or BAPI present for creating BOM ?
Thanks And Regards,
Amit

Hi check the below listed BAPIs and FM.
I guess last onne will do the needful.
BAPI_MATERIAL_BOM_GROUP_CREATE
BAPI_MAT_BOM_EXISTENCE_CHECK
BAPI_BOM_UPLOAD_SAVE
CAD_CREATE_BOM_WITH_SUB_ITEMS
Thanks,
Utsah Garg

Similar Messages

Error: Sales BOM / delivery document creation via DI API

Running into an error from SAP when trying to post a Delivery Note document object via the DI API.
-5002 -You cannot add a document with a bill of materials that does not include all components
I have a Sales BOM on a Sales Order. All components have been included within the Delivery Note object. When calling the document Add() function, SAP is pushing back with the error above.
Does the fact that the components of the Sales BOM are also BOMs themselves make a difference in whether the DI API fails or succeeds in posting the Delivery Note?

Does the fact that the components of the Sales BOM are also BOMs themselves make a difference ?
I believe the answer is YES.
Thanks,
Gordon

Dump during sales order creation for a config material (uding order BOM)

Dear all,
I am getting the following error during sales order creation for a configurable material
When I click on 'Engineering' tab in the characteristics value assignment for the parent material i.e. sales order material I get dump with following message,
'Field symbol has not yet been assigned'
Thanks,
Yogesh

Yogesh,
what was the problem ?
Thanks,
Pavan Verma
Edited by: Pavan Verma on May 11, 2010 9:31 AM

3rd Part Dropship Scenario with Sales BOM

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

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

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Wrong Availability check for Header Item in Sales BOM after BOP

Hi Guys
I am stuck with a very weird problem. Request your advice:
I have a Sales BOM with one item Lets header is 'A' and Item 'B'. On creation of Sales Order ATP check is performed and both the line items (with A and B) the committed qty and committed date.
Now when BOP runs, it deletes the allocation of A and changes it to '0'
Details:
'A' is a non stockable product
Req:
1. I am not sure whether I should include A in BOP selection, however even running it only with B it deletes the allocation of A and the committed qty changes to '0'
Can you please suggest the solution or standard way of running BOP for Sales BOM
Thanks in advance
-Rahul

Thanks for writing in Prasun
Yes I created a new Filter type however when you add a STO category and then you change the fields to include item category you will get the same error. I am also in V 5.0 of SCM
Normally we use SAP_NetChange filter type. So is it possible to restrict using item category for this filter some how!
On the otherhand I also wonder these should not ATP relevant as the header item is non stockable item! And I guess there should some catch to exclude if not item category as you mentioned!
So the order categories included are:
Customer Inquiry
Customer quotation
Sales Order
SD Scheduling Agreement
SD Scheduling agreement w/external
Contract
Delivery w/io charge
Independent requriement
Release from customer in plant
STO
Deplyometn release
TLB release for purc ord
Fields
Product
location
distribution centrer
MRP area
product Hierarchy
Location hierarchy
supplier location
These are std filter type and I cant be modified.. however we restrict our filter to location only!
Kindly advice!
Thanks in advance
-RK

Drop Ship processing for Sales BOM

Hi,
We have a requirement to have a Sales BOM drop shipped from a Vendor. Only the header material is relevant for pricing and purchase order. However, we have a business requirement to explode the sales BOM in the sales document and billing document to address statistical pricing requirements at the component level.
Since only the header material is required in the PO, it has a billing relevance of 'F'. However, we have set the components to be relevant for order related billing. Standard SAP opens up the components for billing even though a vendor invoice for the header has not been received.
Can copy control be used to control the components from being billed unless the header is billed AND the quantity of component materials modified based on the header material being invoiced ? Is it possible to only explode the sales BOM in the billing document using a billing document exit ?
Would appreciate suggestions from the forum.
Regards

Hi
The billing document creation can be controlled through the copying requirement in Copy Control of Billing documents.
Transaction VOFM | Billing documents: Create a new requirement which prevents billing unless the parent item has the vendor invoice receipt.
This requirement has to be then assigned to the respective billing and sales document type in copy control.
Regards,
Vinu

SD - Sales BOM unusual business scenario

Hi Experts,
I would like to know is that possible that in SAP to create the the BOM highlevel (mother) material number with no quantity needed (this particular material number always zero qty)? which means that the BOM highlevel material number used as a dummy material code for reporting purposes.
1) created a sales BOM with material A and child materials are A1 and A2
2) MM master MM01 already maintained item category to ERLA
3) VA01 sales order creation BOM able to explode
4) highlevel(mother A) line item with material number shown BUT without qty in order qty column.
5) 2 sub items (child - A1 and A2) exploded A1 - order is qty 1 and A2 - order qty is 1
6) SO document SAVED. SO number #123 created.
7) VL01N with reference to the SO number #123.
8) PGI done ,able to issue A1 and A2 respectively reduce the inventory with qty 1 each.
Vice versa for return sales order
1) user return the material A entered in SO. (regardless of return partial A1 only or A2 only / fully return A1 and A2 ) SO must able to be created #987.
2) VL01N with reference to the RSO #987. Based on partial or full return, the inventory increase is based on sub item(child level - A1 / A2), the high item is ZERO.
3) If child level sub item A1 return qty 1 then system increase the A1 qty balance.
Thank you.
Regards,
Yong Kok Wah

Hi Yong
As you discribed scenario for BOM and returns.
It is possible
Create sales order BOM & explode in sales order
Carry delivery & invoice creation.
Now take this materials return.
If any quiry revert back.
Kapil

Correlated schedule lines in sales BOM

Hi all,
I'm having an issue with correlated schedule lines using a sales BOM in a sales order.
I've created a sales BOM in which the parent item has item category group LUMF (resulting in item category TAP) and child items with item category grp NORM (item category TAN). Pricing, inventory, cost etc is at item level. So far so good. No problem with the functionality.
I've got BOM configuration set up for item category TAP with "A" (Delivery group with correlated schedule lines) for creating the delivery group.
However, when a create a sales order the schedule lines are getting created with different quantities depending upon the availability of individual quantities instead of creating co related schedule lines.
Ordered
BOM parent Qty: 100
Bom Item A : 100
BOM Item B: 200
__Desired outcome__
Confirmed
BOM parent Qty: 20
Bom Item A : 20
BOM Item B: 40
Current Outcome
Confirmed
BOM parent Qty: 20
Bom Item A : 20
BOM Item B: 120
I believe I've configured it right. Am I missing something?
Any inputs / expert opinion would be greatly appreciated.
Thanks,
Srini

Hi,
Please check the below configuration settings for Successful BOM.
BOM item consist of combination of the materials by having a structure like header and sub u2013 items.
Different combination of the materials combined together to make one single object. The complete combination of
materials only called as a BOM item.
Ex: u201CComputeru201D as it contains monitor as a header item and keyboard, hard disk, mouse as sub-items. The BOM
items can independently sold to the customers separately.
Ex: If the mouse is going to participate as sub-item in the BOM.
But the customer requires same mouse as a u201Cstand byu201D (spare). So the business can offer.
In BOM the pricing, delivery can be carried out at header level item (above structure) or sub-item level (below
structure).
If BOM with above structure then system carries out delivery, billing process only for header item (item category
group ERLA). Then system treats sub-items as text items (no pricing and no delivery for text items).
Above structure: Item category TAQ for header item.
Item category TAE for sub u2013 items.
If BOM with below structure then system carries out delivery and billing process only for sub u2013 items (item
category group LUMF). Then system treats header item as text item.
Below structure:Item category group for header item TAP
Item category group for sub u2013 item TAN
Delivery group: The delivery group facilitates to confirm the quantities of all items in the BOM with best schedule
lines.
Ex: As the BOM contains number of items system can confirm the quantities for some items on required delivery
date, and it may not confirm the quantity for some items on required delivery date. In this context we can put all the
items in a single delivery in a delivery group by specifying delivery group as one in delivery group field at header
level of sales document under shipping tab in delivery group field.
NOTE: Item category group should only be changed for header item.
BOM can be exploded in application areas like production planning, material management and sales and
distribution. While configuring BOM we have to specify the application area where it has to explode. BOM can be
exploded single level or multilevel. Usually multilevel BOMu2019s are exploded in production planning.
Ex: Material is the u201CBikeu201D, as it has so many sub-items, again those sub-items will have some sub-items.
Configuration settings: [ABOVE structure]
 Create a material with item category group ERLA
 Create another 2 materials as sub-items with item category group NORM
 Go to MB1C and maintain the stock for 3 materials
 Go to VK11 and maintain condition records for 3 materials
Configure BOM item: Transaction code: CS01
167
Path:
 Logistics
 Production
 Master data
 Bills of Material
 Bill of Material
 Material BOM
 CS01 u2013 Create
 Specify the BOM header item [ERLA item] and plant
 Specify usage as [5]  Sales and Distribution
 Maintain the sub u2013 items
 Save and Exit
NOTE: Item category u201CLu201D  Stock item.
It is categorization item in the BOM according to set criteria.
Use: This categorization allows us to process data that is relevant to individual items in a BOM. It controls field
selection default values for BOM triggering of specific system activities.
 Go to VA01 and raise the sales order by specifying header item and check whether BOM has exploded or
not.
Item Item category Schedule line
Header item TAQ CP = Deterministic MRP
Sub u2013 item TAE CT = No inventory management,
No goods issue.
VOV7 of TAQ  Extent delivery
 Go to VOV7
 Select TAQ from position button
 Click on details icon and maintain the values like below
Billing relevance [A] = Delivery related billing document.
Price [X] = Standard
Structure scope [A] = Explode single level of Bill of Materials
[The value of this field causes to explode BOM in the document]
Application [SD01] = Sales and Distribution
It indicates the applications are where it has to explode
 Check manual alternatives.
168
169
VOV7 of TAE  Explanation
170
 Statistical value [X] = No cumulation values cannot be used statistically.
VOV6 of CT  No inventory management/No goods issue
 Check item relevant for delivery
It is used for only information purpose
Item category determination table:
OR + ERLA + NIL + NIL = TAQ
OR + NORM + NIL + TAQ = TAE
Configuration settings: [BELOW structure]
 Create material with item category group in the header item should be LUMF
 Go to VA01 and raise the sales order by specifying header item
 Check the BOM explosion
NOTE: For Below structure also we have to follow all the steps like above structure, except the creation of
LUMF material instead of ERLA material.
VOV7 of TAP:
Billing relevance is [A]
Pricing [NIL]
Structure scope [A]
Application [SD01]
171
172
VOV6 of CT:
 Check item relevant for delivery
 Go to VL01N and do the delivery
 Go to VF01 and raise the invoice
Item Item category Schedule line
Header item TAP CT
Sub u2013 item TAN CP
Multilevel BOM: [ABOVE structure]
Item category Schedule line
Header item: TAQ CP
TAE CT
TAE CT
TAE CT
Multilevel BOM: [BELOW structure]
Item category Schedule line
TAP CT
TAN CP
TAN CP
TAN CP
Important notes:
 For Above structure in the material master record should have the item category group ERLA in the Sales:
Sales organization 2 screen.
 This process ensures that pricing, inventory control and delivery processing is carried out at the u201Cheader level
itemu201D only.
 That means the associated sub-items function only as text items, and thus is not relevant for delivery.
 For Below structure item category group is LUMF.
 In this process the sub-items are responsible for pricing, inventory control and delivery processing.
 To ensure all the components in a u201Csingle deliveryu201D use the functionality of the u201Cdelivery groupu201D.
The delivery group: The sub-items of a BOM may be available at different times due to the lead times in
procurement (MM) and production (PP). You can use the delivery group to indicate that all the sub-items must be
delivered as a group (single delivery).
Regards,
Siva

Explode Sales BOM in Replenishment Delivery

Hi All,
We have a requirement of exploding Sales BOM in replenishment Delivery. We tried a lot exploring the same and ended up with a Snote mentioning no solution.
Do we have a enhancement sought of solution where we can insert line item in the delivery after data transfer functionality of SAP (Copy control).
Can anyone suggest us a BADI as well as function modules where we identify the material as Sales BOM and insert the items manually in the Delivery based on validity date.
Regards

Thanks for the reply. Snote i too have seen. Also I have already seen that link and it didn't give much clarity.
it is sure we can achieve this functionality only by enhancement.
Till now we have seen that only routine 302 is triggering during the VL10B and no other exits or BADI'ns are helping us.
If you have any such enhancements where we could insert the line items during the creation of replenishment delivery.Then it will be very helpful.
basically I need any such user exits or BADI'ns for the same.
regards

Adding Sales BOM to Sales Order through SDK

Hello Experts,
We're encountering an issue with adding Sales BOM items to the Sales Order through the SDK. When we add the parent, the object automatically adds the children as lines after all other lines. This causes issues with our batch delivery creation. When the Sales Order is created inside SBO Client, it always adds the child items right under the parent. We have a work around where we change the LineNum through SQL, but that seems like a sketchy method - what's the proper way of adding Sales BOM items to a Sales Order?
Here is the code we're using to add the Sales Order lines
olOrders.Lines.ItemCode = sItemCode
olOrders.Lines.ItemDescription = aRecSet.Fields.Item("name").Value
olOrders.Lines.UnitPrice = aRecSet.Fields.Item("cartprice").Value
olOrders.Lines.Quantity = aRecSet.Fields.Item("qty").Value
Thanks for the help!

Hi Rob,
I certainly wouldn't recommend you use a direct SQL command to update the LineNum on the sales order rows. This will invalidate your support agreement with SAP.
One way you can deal with this would be to add your Sales BOM header item to a draft document (of type sales order) and add this first. You can then retrieve it in the DI API and add the other Items before adding the document as a proper sales order (and removing the draft). You can do this using the Draft and Documents objects either by coding each property or by exporting the Draft to XML and using XLST to convert it to a Sales Order and reimporting it. It does require a fair bit of coding but it will achieve what you need.
Kind Regards,
Owen

Sales order creation, standard event trigger is taking long time .

We have a requirement where we are sending data to CRM system using RFC function module. This data is sent while sales order creation or change. We have used standard event BUS2032.CREATED to trigger CRM FM in sales order creation mode. In sales order change mode, we are using custom event. In production system, our custom change event is getting triggered fine and data is sent to CRM system with small time lag of around 1 minute. But, while sales order creation, standard event trigger is taking long time ( sometimes about 20 minutes) in production system.
We tried triggering same custom event at the time of sales order creation using FM u2018SWE_EVENT_CREATE_IN_UPD_TASKu2019 as well but, still we are not able to improve performance of the event trigger at sales order creation.
Regards,
Sushee Joshi

HI,
we have written SWE_EVENT_CREATE in update task
I think instead of calling in update task simply call to function module CALL FUNCTION "SWE_EVENT_CREATE" might trigger the event immediately.. Did you try to check in this way..
OR
And I also suggest you to check the entry in SWE2 txn with respect to your workflow tempalte, may be you have enable the option ENABLE EVENT QUEUE, this could be one of the reasons.. If it is enabled please disable it (uncheck)
Please check..
Regards
Pavan

How to transfer sales bom from SAP R/3 to APO?

Hi Experts,
I just want to ask how to transfer sales bom from R/3 to APO? if i change my bom usage to 5 and use this BOM in my Production version be enough to send it to APO?
Also, this is my first time using sales bom, could you please help me understand how sales bom work in APO planning?
Thanks so much.
Mylene

Hi Senthil,
Thanks again for your reply. I was trying to CIF sales BOM in APO but only the header material are being created in APO. The component are not added in PDS. This is how I create it in SAP R/3:
1. transaction cs01 --> enter header material, plant and BOM USAGE =5
2. inside cs01, i entered components, quantity for each components and ITEM category = L (stock item)
i also eneterd base quantity for header material
3. create production version for header material with routing and this BOM
4. create and activate material CIF model for header and components
5. create and activate PDS CIF model for header and components.
After doing all these steps, PDS is created in APO but I only have the header material (no components)
I tried changing BOM to other bom usage and components were populated in PDS.
Am i missing nay steps? Thanks.
Regards,
Mylene

Schedule Lines for Sales BoM Material

Hi All,
When i trying to maintain the multiples schedule lines for the Sales BoM Material(Both Header and Item), system is not allowing to maintain it.Please guide me how to achieve this?

Hi,
"Schedule Line allowed" is enabled at Item category. The Requirement is If we have multiple schedule lines for BoM Line Item, we are not able to maintain. Suppose the Order Quantity is 50 Units and we need schedule line of 10 Quantity each month. We are not able to maintain. System takes the complete 50 quantity and do the availability check and proposes the availablity Date. We are not able to maintain different schedules manually.

Sales BOM Header line item confirmed without components in Delivery

Hi Experts,
The issue is about the delivery is created with the single component for the Sales BOM where as it contains two.
We have analyzed the issue and checked that the missing component would have not been available in the stock during the time when the delivery is created and hence is not included(Header material and single component is included in the Delivery).
The user's concern is; when there is no stock for any one of the component, then it shouldn't have confirmed the header material. Kindly suggest.

Hi Azam,
It seems to me that you want to use Delivery Group for Sales BOM where If Mat A = Mat B + Mat C and Mat B Availability date is 20/07/2014 (DD/MM/YYYY) and Mat C availability is 25/07/2014 then Main line item should be confirmed with 25/07/2014.
If any one sub Item is not available, then Any of the item from the Grouping should not be dispatched.
If this is the requirement then, In Item Category (VOV7) for main Item update Create Delivery Group field with X and your requirement will be fulfilled.
Do let us know the result after testing.
Regards,
MJ.

Sales BOM creation

Similar Messages

Maybe you are looking for