Costins for Sales order & Production Order

I require an urgent clarification on the following:
We are in Producing to Sales Order scenario.  We are using separate costing variants for Sales Order and Production Order
Sales order is costed first. 
the valuation variant in the costing variant for Sales order treats material valuation in the following order:
1. Plan price for the period
2. Price indicator from the material master
2. Future standard price
Then the Production order is released.
In the Production order, the valuation variant says the material valuation as :
1. Preliminary cost estimate from sales order
2. Price indicator from the material master.
My doubt is since the production order costing variant says the first option for material valuation is 'preliminary cost estimate from sales order', which value of the raw materials will be picked in the Production Order cost analysis ?  Is it from the Sales order costimate as prer preliminary cost estimate or is it as per the price indicator from the material master ?

I require an urgent clarification on the following:
We are in Producing to Sales Order scenario.  We are using separate costing variants for Sales Order and Production Order
Sales order is costed first. 
the valuation variant in the costing variant for Sales order treats material valuation in the following order:
1. Plan price for the period
2. Price indicator from the material master
2. Future standard price
Then the Production order is released.
In the Production order, the valuation variant says the material valuation as :
1. Preliminary cost estimate from sales order
2. Price indicator from the material master.
My doubt is since the production order costing variant says the first option for material valuation is 'preliminary cost estimate from sales order', which value of the raw materials will be picked in the Production Order cost analysis ?  Is it from the Sales order costimate as prer preliminary cost estimate or is it as per the price indicator from the material master ?

Similar Messages

  • MRP-Delivery Schedule for Sales order is not updating in Production order

    Dear Experts,
    I have created Sales order and maintained delivery scheduling, Then Run MRP through MD50,
    We received Planned order then through this we have converted to Prodcution order.
    When we observe the delivery schedule for sales order under assignment Tab in Produciton order which is showing zero instead showing line item of Delivery schedule.
    I am able to see Sales order and Line item but i am not abel to get any delivery schedule line item.
    Please suggest where settings are missing.
    Thanks in advance
    Regards
    Don

    Dear Experts,
    Please provide me solution.
    after Running MD50 transaction against Sales order.
    If I maintained different Scheduling Line Item for First Line item of Sales order.
    The Respective Scheduling Lines should update against Each Production order which has converted from Planned order.
    Thanks in advance.
    Regards
    DON

  • Planned material price in case of production order for sales order (MTO)

    Hi,
    In case of production orders created for sales order, the planned price for a component (BOM) material gets picked as per following:-
    1. If there is no entry in EBEW for the component (that is, there is no previous GR for the component) for that sales order, then plan price is picked up on the basis of planned costing variant.
    2. In case there is an entry for the component in EBEW (there has been a previous GR for the component with reference to the sale order) then the plan price for the component is taken from the EBEW table (first GR price) and system ignores the costing variant.
    The above is as per my observation. Please validate if this is correct or not.
    The requirement is that even if there has been a previous GR for the component (there is an existing entry in EBEW) the system should take the plan price on the basis of costing variant and not from the EBEW table.
    How can this be achieved? Is there a user exit that can force the system to read the costing variant before looking into the EBEW table?
    BR
    Abhi

    Hi Ajay,
    Yes i had considered it but I'm not sure If it will help.
    Because the main problem here is that system is ignoring the costing variant itself and instead picking the price from EBEW table. So changing the costing variant (validation variant) may not help.
    Moreover i don't want to valuate with my own strategy. I want the plan price to be equal to standard price of material from material master. Basically MBEW instead of EBEW.
    Any clues?
    BR
    Abhi

  • Product valuation for Sales order with itemizations

    Hi experts,
       I'm trying to find a data source which extracts Product valuation for sales order, and which is important, with itemizations. This is for the KMAT material. I tried 0CO_ACT_* and 0CO_PC_PCP_* but found no proper one.
       The closest one is 0CO_PC_PCP_03 but which only extracts normal material instead of KMAT.
       Points will awarded.
    B'R
    Aaron

    I found it.
    0CO_PC_01
    Cost Object Controlling: Plan/Actual Data

  • Product cost collector for sales order related production

    Hi Friends,
    This is Azam and here i am new to this discussion forum.
    we are in situation that use diffrent variant for configurable material in sales order related production,
    I would like to have some information about use product cost collector for this kind of sales order related production,
    also I want to know difference between prelimanary cost estimate or cost estimate for sales order?
    Please co-operate me.
    I would be highly appriciated if you can respond at the earliest.
    Thanks
    Azam

    Hi,
    Here, for each sales order item, you will have sales order cost estimate. This enables the system to compute the variances once the actual costs are booked against the production.
    In the case of preliminery cost, we get the preliminery cost for production order as a plan cost and is not being used for the computation of variance but only for comparision purpose which is very marginally used.
    Trust this helps much and do encourage our efforts!
    Cheers!

  • BAPI for Sales Order & Production Order

    Hi Experts,
    1)i need to Identify standard  BAPI's for Sales Order & Production Order.ie for one BAPI need both sales order and production order.
    2)i need to Identify standard BAPI to return delivery number and shipment number for a particular Sale Order. If any one give me answer thanks for advance. it's really helpful for my project.
    thanks and regards,
    bala.

    Hi Bala
    Kindly do not open duplicate threads for the same topic. Help to close one thread and continue with the other to avoid confusion.
    Kind Regards
    Eswar

  • RBA GATP check is not getting invoked for Sales Order

    Hi Everyone,
    RBA GATP check is not getting invoked for Sales order.
    I maintained the configuration settings for 'Rules-Based Availability Check', APO general settings (check mode, check instruction), carried out integrated rule maintenance, Rule determination for the combination of order type & product, associated the check mode to product master. Also maintained all the settings in ECC towards Req class, Req type, checking control etc.
    However, sales order is not invoking RBA Check though it is showing up the 'Rule' icon in the screen. Also, in the APO Availability check in Sales order when I click onto 'check instruction', I get the checking mode that pertains to RBA for business event 'A' (Sales order). Though I have not maintained any stock for the main material for which I have the sales order, yet system is confirming any quantity that I put in.
    I would expect that system would propose the same material in an alternate location where we have stock through RBA.
    Request you to share ideas on this.
    Regards,
    Avijit Dutta

    Hi Avijit,
    You should used No Checking Horizon in Checking instructions and also Check your rule control settings.
    What you have defined in 1st and 2nd steps. Check whether product substitution is carried out or Location Substitution.
    Thanks,
    Bala.

  • Error reading material cost estimate for sales order (KE292)

    Dear All,
    I have an issue with billing. we are posting july month transactions, the material cost is maintained through MR21. When releasing billing document for accounting we are getting error message like"Error reading the material cost estimate for sales order "11"
    Message no. KE292
    Diagnosis
    In Profitability Analysis (CO-PA), the system tried to valuate item 000010 of sales order 11 by reading the corresponding product cost estimate.
    However, no product cost estimate could be found for this sales order item.
    The system accessed product costing for product AMLFP011011XX00P using costing key YB3 as defined in the
    CO-PA Customizing settings.
    System Response
    The system cannot process the document any further.
    Procedure
    Check your Customizing settings."
    We cross checked with other client as a current date and we ran cost estimate through CK40N with same material. and we posted entries. Here it is working fine. but in above process it is not working. Can you pls guide me where i missed.
    Regards,
    Nagaraju,

    Hi,
    When the Costing Key is assigned to the material types in the COPA customizing, then system expects Cost estimation when billing is released to Accounts.
    If you dont run cost estimation but update the material master through MR21, system will not accept as in the Costing key configuration you must have selected the Current Standard price field for the valuation.
    Hence, try to run cost estimation and then do releasing.
    Thanks & Regards
    Ravi Kumar

  • 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

  • Using MD50 to run MRP for Sale Order

    Dear all,
    I have some problem when using MD50 with Mill Product Industry.
    When SAP system not activate Mill Product yet. I used transaction code MD50 to run MRP for Sale Order, the system have generated planned order for multilevel. But when SAP system have activated Mill Product, I used transaction code MD50 to run MRP for Sale Order, the system only generate planned order for single level. I think that we have to configure something based on Mill Product Industry. So can you help me for this
    Thanks, Regards

    Hi,
    Check with following links which may help you resolve your issue :
    http://www.sap.com/sme/whysap/industries/millproducts/index.epx
    http://help.sap.com/saphelp_di471/helpdata/en/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
    http://help.sap.com/content/documentation/industry/docu_is_mill.htm
    Regards,
    Tejas

  • Deleting list for sale order

    Hi Guru’s
    How can get the deleting list for sale order?   
    Useful answer duly rewarded back.
    Regards,
    Devendra

    Hi Devendra,
    General Sales order will be deleted form the database after archiving.
    Step for Archiving:
    Sales Order is archived and deleted by the Archiving object know as SD_VBAK.
    If you just want to delete the sales order with out thinking of saving to archive server then please follow the path:
    1.GOTO SARA ---> Click Customizing -> click Archiving Object specific customizing (Technical settings)> In delete jobs mention start automatic --> Leave other settings as per the standard save and close it.
    2. Click write --> Mention Variant name -->Click on Maintain --> Select all the sales orders that you want to archive and delete --> Mention sales organinsation under which you have created --> Select Production Mode --> Click on Attributes --> Mention meaning of that attribute it could be any text --> Enter and save.
    3. Click on Spool parameters --> mention the output type --> Enter now you can see green signal light
    4. Click on Start date --> Click on Immediate --> Save.
    5. Execute or click F8 and see the job.
    6. After some time you can see the data is archived and deleted form the database.
    Hope this will help you in deleting the sales order form the database.
    Please Note: It is bit complicated you should take help of SAP Archiving consultant.
    -Thanks,
    Ajay
    Message was edited by:
            Ajay Kumar
    Message was edited by:
            Ajay Kumar

  • How settlement rule will be created for Sales order with cost object

    Dear Experts,
    We are using product cost by sales order with valuated stock. In addition we are not using COPA
    We also consume some materials at sales order level and at the end of month we want to do the result analysis and settlement for the same amount. In this case can any on explain how system will behave regarding settlement of sales order cost and what entries will get pass in the system.
    In our case we have done below activities...
    we have created sales order,
    All production order activities completed till final GRN including month end activities
    Material consumption against sales order
    Result analysis executed
    At the time of sales order settlement, system throwing error (Sender doesn't have valid receiver, please create settlement rule for sender object)
    Then i checked in sales order there sales order settlement rule not defined.
    I guess this settlement rule need be generated by system automatically. If not, please let me know the process of it.

    HI kishore
          the reason is that sale order always carry the revenue  and production order and production period carry the cost .
       cost you can settle to the Material and even management want  to be settle the cost to material only in production order OR period
    but in sales order  when u sell the product it carry the revenue not the cost and management want see and analysis based on profitability segment are profit center level .
    Prerequisites
    If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
    If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
    You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
    The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
    The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
    The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
    The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
    Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.

  • BOM Cost Estimate for sales order items

    Hi experts,
        Which data source could extract data created by CK51N (Order BOM Cost Estimate )? We need to get BOM Cost estimate (including input material and activity) for sales order items.
        The closest one is 0CO_PC_01, but it extracts itemizations for production order.
        It's urgent.Helpful answers would be awarded.Thanks.
    Regards,
    Aaron

    Hi Henry,
       They even do not have Sales Order segment. How could I get cost estimate data based on sales order?
    Regards,
    Aaron

  • How can we identify what are all user exits are there for sales orders,deli

    Dear All,
    How can we identify what are all user exits are there for sales orders,deliverys and invoices
    thanks
    nitchel v

    Hi Nitchel
    There are many ways to find out the user exits..
    For example for VA01.
    Goto Transaction ie VA01:
    goto System-- Status
    doubleclick on the program name ie SAPMV45A
    SE38 -> Enter the program name and in the program( SAPMV45A) goto -- attributes
    get the package name from here ie VA
    note the package(VA) and get back to main screen
    goto SMOD tcode  and click on find button in the package spec giv the package name ie VA and execute it
    you will find list of exits available
    check out the exit that suits ur requirement
    goto cmod and create a new project and implement in that user exit.
    You will get the following exits in SMOD..
    SDTRM001  Reschedule schedule lines without a new ATP check
    V45A0001  Determine alternative materials for product selection
    V45A0002  Predefine sold-to party in sales document
    V45A0003  Collector for customer function modulpool MV45A
    V45A0004  Copy packing proposal
    V45E0001  Update the purchase order from the sales order
    V45E0002  Data transfer in procurement elements (PRreq., assembly
    V45L0001  SD component supplier processing (customer enhancements
    V45P0001  SD customer function for cross-company code sales
    V45S0001  Update sales document from configuration
    V45S0003  MRP-relevance for incomplete configuration
    V45S0004  Effectivity type in sales order
    V45W0001  SD Service Management: Forward Contract Data to Item
    V46H0001  SD Customer functions for resource-related billing
    V60F0001  SD Billing plan (customer enhancement) diff. to billing
    For Delivery you will get .. here the package name will be VL.
    V02V0001  Sales area determination for stock transport order
    V02V0002  User exit for storage location determination
    V02V0003  User exit for gate + matl staging area determination (h
    V02V0004  User Exit for Staging Area Determination (Item)
    V50PSTAT  Delivery: Item Status Calculation
    V50Q0001  Delivery Monitor: User Exits for Filling Display Fields
    V50R0001  Collective processing for delivery creation
    V50R0002  Collective processing for delivery creation
    V50R0004  Calculation of Stock for POs for Shipping Due Date List
    V50S0001  User Exits for Delivery Processing
    V53C0001  Rough workload calculation in time per item
    V53C0002  W&S: RWE enhancement - shipping material type/time slot
    V53W0001  User exits for creating picking waves
    VMDE0001  Shipping Interface: Error Handling - Inbound IDoc
    VMDE0002  Shipping Interface: Message PICKSD (Picking, Outbound)
    VMDE0003  Shipping Interface: Message SDPICK (Picking, Inbound)
    VMDE0004  Shipping Interface: Message SDPACK (Packing, Inbound)
    For Billing VF01..Package is VF..
    SDVFX007  User exit: Billing plan during transfer to Accounting
    SDVFX008  User exit: Processing of transfer structures SD-FI
    SDVFX009  Billing doc. processing KIDONO (payment reference numbe
    SDVFX010  User exit item table for the customer lines
    SDVFX011  Userexit for the komkcv- and kompcv-structures
    V05I0001  User exits for billing index
    V05N0001  User Exits for Printing Billing Docs. using POR Procedu
    V60A0001  Customer functions in the billing document
    V60P0001  Data provision for additional fields for display in lis
    V61A0001  Customer enhancement: Pricing
    Or another way is ..
    - Get the program name for that T-Code
    - Go to that program
    - In that program, search for word 'EXIT' or 'CUSTOMER-FUNCTION' by using where-used list which will give u the list of user exits for that program
    And also you can check in the tables in SE16 for user exits..
    MODSAP - Stores SAP Enhancements
    MODSAPT - Stores SAP Enhancements - Short Texts
    MODACT - Stores Modifications
    And there are other ways as well , pls check the forum for this ,
    Regards,
    Vvieks
    Note : If you have any specific requirement then pls let us know , we will guide you

  • Invoiced blocked for sales order (configurable material external procurement )

    Hello Expert
    Configurable material external procurement
    Invoiced blocked because ,"Error reading the material cost estimate for sales order "75501"
    Message no. KE292
    Diagnosis
    In Profitability Analysis (CO-PA), the system tried to valuate item
    000010 of sales order 75501 by reading the corresponding product cost
    estimate.
    However, no product cost estimate could be found for this sales order
    item.
    The system accessed product costing for product 10820 using costing
    key 002 as defined in the
    CO-PA Customizing
    settings.
    System Response
    The system cannot process the document any further.
    Procedure
    Check your Customizing settings.
    Note:We can't run cost estimate and releasing it because it's a configurable material  but external procurement. We place a purchse order based on configurable sales orser
    Thanks
    Parves

    Hello Declan,
    Thanks for your reply. Could you please give me the steps for Maintain the
    sales order cost estimate?
    Requirement: Customer service receive order with variant configuration product,
    then MRP Crete PeReq, convert  PO and
    send to supplier .Supplier configure the product and direct delivery to
    customer. Supplier sends an invoice to us. Then we send invoice to our customer
    Thanks
    Parves

Maybe you are looking for