Sale order bom explosion in delivery doc

hi all
there is an urgent requirement for my clint
issue is my clint want the BOM should not expolde in sales order, should expolde at the time of delivery only.
is there any possibility please suggest
thanks
sridhar

Hi,
Thanks for your reply.
As per your answer, ur saying we can change the item category but item category is grey at the sales order level and its not modifable.
Can please help how to make editable.
Rgds
Gautam

Similar Messages

  • Quote and Sales Order BOM Explosion

    We are attempting to utilize a ETO process without PS.  We create a sales quotation and begin to build a quote BOM (using type 1 production) and a Routing for the entered quotation.  Eventually we decide to create a sales order with reference to the quote.  We copy the quote, we copy the quote BOM (type 1 production) to create a sales order BOM (type 1 Production) and copy the quote routing to create a sales order routing.  We however make a few additions/changes to the Sales order BOM.  When we run MRP for the sales order the system pulls the quote BOM not the sales order BOM. 
    If we slightly adjusted this proccess and create a costing BOM (type 6) at the quote rather than the production BOM (type 1) and again create a sales order with reference to the quote copying the costing BOM to create a sales order type 1 production BOM MRP says no BOM is found.  We believe that MRP should pull the sales order BOM rather than the quote BOM if both are type 1 but most certainly believe that if the quote only has a costing BOM and the sales order has a production BOM MRP should recognize it and utilize it.  This does not happen.  Any thoughts?

    Thanks Piyush.
    I have already gone through that. All my questions I have alredy put here .. Could you please care to have a look at it..
    Integrating SD with PI and any Services available out of the box to use..
    VJ

  • Sales Order - BOM Explosion

    Hi ,
    We have a scenario of variant configuration, wherein there is a bom explosion. Whenever there is a change in the BOM, the change is also getting reflected in the order.
    How can I prevent this?
    Thank you very much
    Jaffer

    I think that it is the configurator that manage this, so you cannot prevent the re-determination because if you change the configuration, then the also BOM changes.
    Roberto

  • BOM changes reflecting in sales order BOM of delievery completed materials.

    Hello gurus
    i am explaining my requrement. My scenario is like this.
    1.creating sales order
    2.reating sales order BOM
    Next production peole will create production order and will do confirmation of order and Goods reciept.
    3. after this sales people will do delivery of the materail.
    For example yesterday i have delivered one material X.
    Today if i change the super BOM of the material X, these changes are reflecting in the sales order BOM of yesterday delivery done material X also. My client want to restrict thise changes. Pl help me how to resolve this ?
    regards
    srao

    Hi Brahmankar
      we checked for User exits we didnt find. Can u help me out on this regard.
    Can we lock the sales order BOM ? means if we do any changes to super BOM assly level also, these should not reflect to sales order BOM . pl guide me
    regards
    srao

  • Reg: sales order BOM

    hi friends,
    can anyone explain me what is SALES ORDER BOM.
    Where it is applicable.

    Dear
    Sales Order BOM are used in Make to Order .If you want to assemble the products and depending upon the assemblies you want to price.   For eg. if the customer asks for a certain combinationa of Material A, B and C respectively, then you create a Material Master record Material D with item category group as LUMF.  While the Materials A, B and C are created with standared item category groups NORM only. 
    Then create a sales BOM using Tcode CS01 and enter the following details: 
    Material : Material D 
    Plant : Plant in which you created the material. 
    BOM Usage : 5 (Sales and Distribution) 
    then give the Materials A, B, and C and give their respective quantities. 
    Before you have to create pricing condition records for Materials A, B, and C. 
    Then configure the item categories ( T - code : VOV4). 
    When processing the sales order, just give the Material D and the system will pick up the corresponding assemblies for that material and populate in the order. 
    The item category for the header item will be TAP and the item cateory for the items will be TAN.
    In this cas the Material D is called as the higher level Item , and all the assemblies are called as the sub items.  Here the subitems are relevant for pricing and delivery where as the header item is not relevant for neither pricing nor delivery. It just acts as a text item.
    However , you can create Sales Order BOM by using Tcode : CS61 .Specify Sales Order, Item , Material, BOM Usage 5 in CS61 and create the same. Activate SO/WBS BOM active under BOM explosion in OMIW or OPPQ
    Regards
    JH

  • Plant change in Sales Order not possible due to Sales Order BOM

    Hi all,
    we are trying to change the Delivery Plant in a Sales Order after the creation of a Sales Order BOM, but it gives a V1773 message first, then a blocking error V1810. The same happens with a Production Order.
    How can we change the Delivery Plant after the creation of one of these objects?
    Our scenario:
    - Make To Order
    - Sales Order BOM created with transaction CS61
    - Sales Order Routing created with transaction CA01
    We need to create the Sales Order BOM on the Production Plant (which doesn't change), but we need to be able to change the Delivery Plant in any time.
    Should you have further questions, feel free to ask.
    Thanks in advance,
    Giuseppe

    Hello Caselli,
    For V1773, please check the solution provided by note 588884, which is a modification. With this note it turns possible to delete all multi-level sales order BOM using transaction CSKB, which may be useful.
    The behavior mentioned by you is the standard behavior of the system. The scenario works as designed, a plant change is only possible as long as there is no other document assigned to the sales order.
    Longtext of V1 810 says:
    The plant can no longer be changed in the following situations:
        2. There is a production order for the order item but it is not a static assembly order.
    Your scenario seems to be point 2 as mentioned above. You can check the requirement type (VBAP-BEDAE) and requirement class in OVZH and assembly type (MNTGA) in OVZG.
    If you change the plant for the items with existing production orders, it will cause the incorrect values in the COPA. An order item is assigned to plant A and the corresponding production order exits. This
    means that the costs are assigned to plant A (this is the place where the costs accrue). Order and production order will be balanced at plant A.
    If you now, after the process has already started, should allow to change the order to plant B the following examples of problems will come up:
    - The costs accrued in plant A (see production order)
    - The SD order is now assigned to plant B, this means billing will be with plant B
    This leads to the fact the costs are on plant A, plant B has a benefit. Plant A cannot settle the costs and plant B has unexpected earnings. Inconsistencies in all involved process steps, SD, CO, COPA are the results.
    If you want to change the plant in the sales order you'll have to perform these steps:
    = Delete the production order.
    = Change the plant of the sales order item from A to C.
      This should be possible unless there are other documents which are already assigned to this sales    order item. Save.
    = Create a new production order and assign it to the sales order item again.
    I hope I am able to help you with this information.
    Best Regards,
    Bhavin Joshi

  • Sales order BOM is not reflecting in sales order

    Hi Guys,
    I have created a sales order in which all the items of the sales BOM (ex:A-a1,a2,a3).have been exploded.My strategy is make to order and i am dealing with valuated stock.
    Now i have created sales order BOM for that particular sales order thro cs61.I have made some changes in the item level (ex:A-a1,a4,a5) in the order BOM i want these changes to be reflected in my sales order is there any way to do so...
    RAMASWAMY

    Dear,
    You have to configure BOM explosion in VOV7 - item category settings - BOM area and you can specify whether it is a single level or multi level explosion etc., Depending on the configuration made here, the BOM explosion takes place in the order.
    Regards,
    R.Brahmankar

  • Sales Order BOM-Cost of Sales issue

    Dear Gurus
    Standard Sales Order BOM supports either Pricing Inventory control, Delivery at Header level (Item category group ERLA) or All these at Component level ( Item category group LUMF).
    I have a scenario where in Header is Intangible and Relevent for Pricing only. However Down the level parts are relevent for Delivery and Inventory control.
    I am exploding the Sales Order BOM with Item category group ERLA. However When I do Billing only for Header I do not get Cost of Sales as there is no Cost in Header. I cannot bring Down the level components in Billing as these are not Billing relevent.
    Just To Clarify it more these are Cost is not posted in COPA as Protability analysis documents are only generated with Billing.
    Regards,
    Neeraj Srivastava
    Looking for your valuable inputs How the Cost of Sales can be achieved.
    Regards,
    Neeraj Srivastava
    Edited by: NEERAJ SRIVASTAVA on Jun 5, 2008 5:15 PM

    Hi,
    just try to use BELOW Function moduleS
    CABM_READ_BOM
    CABM_READ_BOM_HEAD            
    CABM_READ_BOM_ITEM            
    These are function Modules ( BOM link to Sales order)
                        OR
    See the function Group CKDI to view more function modules that have relation between BOM and Sales order
    Thanks
    Ramesh

  • Reg WBS Element in Sales Order Line Item For Sales Order BOM

    Hi ,
    Greetings!!!!
    I have a requirement, in a Sales Order I am Exploding BOM. After that Projects will be Created.
    Once Project will be created i need to Assign WBS element for All Items in Sales Order.
    My requirement is When I assign WBS element for Header Material (Parent Item) system will auto assign WBS for Child Items.
    for this what Configuration I have to do.
    Please do need full.
    Thanks,
    Regards,
    Prasad.

    Hi Dayananda
    Check in transaction VTFL for given item category what copying routine are set. Check those copy routine and see if there is any data is being copied from table VBAP
    Similar to above also check transaction VTFA for copying routine (if any)
    As a standard SAP even we create an invoice with reference to the delivery document, still there are some data which is being copied from a sales order i.e. all pricing relevant information is copied from your sales order and not from delivery.

  • Copying sales order header data into delivery line item

    Hi
    In copy control from sales order to delivery I want to copy value in sales order header to all the items in delivery, can I achieve this in the header level data transfer routine (Source sales document type to target delivery doc type i.e TVCPL-GRUAK)  or I have to do the changes in item level data transfer routine (TVCPL-GRUAP)
    The requirement is to copy a value from VBAK into LIPS during delivery creation
    Thanks
    Javed

    Dear Javed,
    Your requirement sounds interesting.
    If possible can you explain the scenario where we have to transfer the header data form order to item data in delivery?
    Also if you have found the solution, can you please update the same.
    Thanks & Regards,
    Hegal K Charles

  • Price and item proposal for Sales order bom

    Good day everyone,
    I've created a sales order bom for a material, when I create a new sales order for this material, SAP give me all the materials listed in the bom, may I ask is there anyway to do the setting as below:
    1: Gross price (PB00) for material that come from BOM explosion having different price as the material that enter manually (without BOM).
    2: Could BOM explosion happen in item proposal? With this, I could send out the item proposal to my customer before the actual sales order.
    Thank you very much for you help.
    Best regards,
    Lee
    Edited by: CK Lee on Mar 31, 2011 2:46 PM

    Good day everyone,
    I've created a sales order bom for a material, when I create a new sales order for this material, SAP give me all the materials listed in the bom, may I ask is there anyway to do the setting as below:
    1: Gross price (PB00) for material that come from BOM explosion having different price as the material that enter manually (without BOM).
    2: Could BOM explosion happen in item proposal? With this, I could send out the item proposal to my customer before the actual sales order.
    Thank you very much for you help.
    Best regards,
    Lee
    Edited by: CK Lee on Mar 31, 2011 2:46 PM

  • Sales Order BOM IDoc Steps

    Hi all,
    I am new to IDoc and got a requirement where I want to mass update the Sales Order BOM in SAP. I have to use the IDOC type BOMORD01, message type BOMORD with the inbound function module IDOC_INPUT_BOMORD in order to mass create Sales Order BOM. I have been provided input file with following fields:
    Order Number     
    Item Number     
    Material      
    BOM Usage     
    Item Category     
    Components     
    Quantity
    Indicator (Create/Delete)
    Could you please tell me the steps-by-step approach with TCODES?
    Thanks in advance.
    Regards,
    Balaji Viswanath.

    Hi
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Regards
    Anji

  • How to compare sale order bom and production order bom.

    i would like to provide report with respect to comparation of sale order bom and production order bom, but i am not familiar with SD and PP, can anyone give me some clue? i only know sale order bom is created via 'CS61', afterwards run mrp to get production order, the process appears complicated, i needn't know the process detail, just want to know how to get sale order bom and relative production order bom. please guide me.

    Hi,
    Check Tcode:CS14 to SD/PP BOM's
    Chidambaram

  • Sale order bom

    dear sir,
       can you tell be how to create sale order bom(master bom) from the beginning. please give detailed process right from creating sale order. my requirement is to have a single bom which can be changer according to customers requirement
    tahnking you
    arun kumar .r.v

    Hi,
    We need to maintain Material master records for the BOM Item and for the components also.
    The <b>item category group</b> of the BOM items should be <b>‘ERLA or LUMF’</b> and the item category is ‘NORM’.
    To Creating BOM item: Tcode - CS01 
    Specify the data for the following fields.
    Material: Specify the material for which components are to be maintained.
    Plant: Specify the plant of BOM item.
    BOM usage: Specify the application in which BOM is maintained (5 for SD).
    Alternative BOM: Specifies the sequence of a BOM within a group of BOMs.
    (L = stock item                  N = Non-stock item)
    In the overview screen specify the components which makes the main item and the corresponding quantities and save it.
    Note: During sales document processing if we enter the BOM item the system automatically determines corresponding components.
    I   *For the BOM to be exploded in the sales document the following customizing  setting is required.
    A) If the item category group is ERLA the item category of the BOM is TAQ, in the definition of which we have to specify the value A (Explode single level BOM) in the structure scope.
    B) If the item category group is LUMF the item category of the BOM item is TAP in the definition of which we have to specify the value A in the field structure scope.
    II   If the item category group is LUMF the system shows price for the components but not for the BOM item. For this the following customizing setting is required.
    A)     The item category of the BOM item is TAP which is not relevant for pricing, so the BOM item is not Priced.
    B)     The item category of the components is TAN which is relevant for pricin! g, so the components are priced
    III        If the item category group is ERLA the system shows price for the BOM item but not for components. For this following customizing setting is required.
    A)   The item category of BOM item is TAQ, which is relevant for pricing, so the BOM is priced.
    B)    The item category of components is TAE which is not relevant for pricing, so the components are not priced.
    While creating sales document to get the list of alternative BOMs in the definition item category of BOM item we have to check the field “Manual Alternative”
    Rewards if this helps you,
    cheers,
    RC

  • Sale order bom can be used in to process order or not

    To change the BOM for particular order items the sale order BOM can be created , to copy the sale order BOM into production order CO08 can be used , whether the process order can be created with ref to sale order any option is available is SAP

    Hi,
    There is no such transaction for process order with respect to Sale order.If planned order is created with respect to sale order after MRP,that can be converted to process order thorugh COR8 transaction.
    try to explore COR8 transaction

Maybe you are looking for