SAP SD Sales Order approval process

Hi Gurus,
Could anyone explain how to map the following scenario in SAP SD sales Order Management?
Ques-1:
Sales order will be reviewed by supervisor.  If the supervisor approves, then the sales order will be available for the Sales manager for review. If the supervisor disapproves, then the sales order will be stopped from getting processed.
Ques-2:
Sales order will be reviewed by sales manager.  If the sales manager approves, then the sales order will be available for the Sales director for review, if the order is above a pre-set value limit. If the sales manager disapproves, then the sales order will be stopped from getting processed.
Ques-3:
Pending sales orders will be automatically promoted to the next level.
Have a Nice Day.
Regards,
Ravikumar.S

Hi  Ravikumar
For all your questions ,
Configure credit management and in FD32 maintain credit limit for the customer. and in OVA8 , maintain Error indicator . So if the error exits then the sales order will be sent to the supervisor to get the approval.and then do delivery. After approving by the supervisor then it the sales order will be forwarded to 
Sales manager. to finalize again
So while doing configuration in credit mgmt , dont maintain credit limit for the supervisor and maintain credit limit to Sales manager. But make sure that the 1st level is supervisor and the 2nd level is sales manger. So that once the Error comes in the sales order then it will be forrwarded to Supervisor and then supervisor will forward to Sales manager
Regards
Srinath

Similar Messages

  • Sales order approval workflow

    Hi,
    I am new to workflow. I have to implement sales order approval process in sap.
    Below are my queries:
    1) Can anyone tell me that is there any standard method for "approval" available in BOR.
    2) Organization level should be derived from the custom table in sap depending on the input coming to workflow.
    So how i can implement this process?
    3) Is there any possibility to approve the sales order through e-mail. If yes then how to do that.
    Can anyone suggest any example for this.
    Thanks in Advance.
    Sumit

    Hi Sumit,
    There are standard Objects available in BOR for sales order  you can extend that object type and use a
    new method for Approval process check object BUS2032.
    You can forward your workitem through email maintain settings in SCOT and SOST.
    Thanks & Regards
    Hari Sankar M

  • SAP SD Sales Order is not processing

    Dear sir,
    When I am creating sales order and processing it for delivery, it is not processed and it gives message that delivery can not be processed due to credit limit has to be checked. It is despite of that when I have not configured credit management for the company.
    Kindly send me answer pls.

    dear sunil..
    check whether in the customer master credit control area is assigned.
    check whether ur company code is linked to any credit control area in enterprise strucutre... as when u copy a company code when creating it... this might have occured.
    i don't think so u have activated automatic credit control area.
    check ur basic configurations.
    regards
    suresh sangoju

  • Sales order reles process

    hello guru's
    i need sales order relese process.
    how can i map in sap.
    if know any one please help me?
    regards
    dharma

    Hi Dharma,
    There is nothing like release strategy for sales order. There is a release strategy for purchase order. A bit of search on sdn forum in MM section will help you a lot on this area.
    For your reference, The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 0
    1
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • 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

  • Sales Order Approval flow

    I wish to know if there is any standard procedure for the below in SD.
    "Sales Order Approval. There is a need from business to align on confirmation control.
    User requests to change the sales order flow to include SO confirmation step."
    rgds,
    Pri

    hi
    <u><b>U will follow this steps:</b></u>
    1.First create the status profile.
    2.In this status profile,u have create the Approval and Non-Approval and Double click to the Processing Process.
    3.Then assign to the Sales document header or Item Level.
    <b>IMG - Sales and Distribution - Sales - Sales Documents -Define And Assign Status Profile</b>

  • Fiori Approve Reqs - Custom Sales Order Approval Issue

    Hi All,
    Urgent Help required .
    We are developing Sales Order Approval apps using Approve Requests as baseline.   We have requirement to  display the sales Order details in Apps Like the PO apps.  Please help me find out how to add business data to Approve request apps . I have checked below Doc .
    .http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0ab2463-4e16-3110-b08e-d93918e513a1?QuickLink=index&overridelayout=true&58789512365087
    Step 8 Extensibility section .
    8.2 we have implemented . all the steps mentioned in Doc were implemented in the backend system as we have to retrieve data from ECC/ERP
    Created Model Provider Class.
    Created the data provider Class.
    Created Service and maintained the customization table /IWPGW/C_TGW_CTX with Service.
    But i am not able to see the fields i have added to Entity when testing in the metadata fields in TASKPROCESSING. However, it does show there is Contextserviceurl with the context service what we have created
    Please let me know the Next step or if i am missing some steps .
    Please suggest me best approach to develop the Approval apps if not delivered by SAP ???
    Thank you very much for your help.
    Thanks,
    Deepanker
    Tags edited by: Michael Appleby

    You need to REDEFINE   method ENTITYSET_TASK and couple of other methods like GET_ENTITY etc. I am showing one for reference:
    Please look at std SAP method for GET_ENTITY in the std class. Here is a sample example:
    first get a handle to the Instance ID
    CASE iv_entity_name.
        WHEN 'InvoiceItem'.
    * get work item's instance ID   
          READ TABLE it_key_tab INTO ls_key WITH KEY name = 'InstanceID'.
          READ TABLE it_key_tab INTO ls_key_item WITH KEY name = 'InvoiceLineItem'.
          lv_wiid = ls_key-value.
    *     retrieve Invoice details
                      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                      EXPORTING
                        input  = lv_wiid
                      IMPORTING
                        output = num.
                     CALL FUNCTION 'SAP_WAPI_READ_CONTAINER' destination lv_destination
                       EXPORTING
                         WORKITEM_ID              = num
                         BUFFERED_ACCESS          = 'X'
                       IMPORTING
                         RETURN_CODE                = lv_returncode
                       TABLES
                         SIMPLE_CONTAINER         = lt_simple_container
                         SUBCONTAINER_BOR_OBJECTS = lt_subcontainer_bor_objects
                         SUBCONTAINER_ALL_OBJECTS = lt_subcontainer_all_objects.
                   if lv_returncode = 0.
                   "TEST
                          READ TABLE lt_subcontainer_bor_objects with table key element = lc_element
                          into wa_subcontainer_bor_objects.
                                      " call rfc for data
                                         CALL FUNCTION 'ZRFC' destination lv_destination
                                          EXPORTING
                                                AUSBK = wa_subcontainer_bor_objects-value+20(4)
                                                BELNR = wa_subcontainer_bor_objects-value+24(10)
                                                GJAHR = wa_subcontainer_bor_objects-value+34(4)
                                          IMPORTING
                                                BLDAT = wa_BLDAT
                                                XBLNR = wa_XBLNR
                                                VENDOR = wa_vendor
                                                WRBTR = wa_wrbtr
                                          TABLES
                                                  LT_ITEM        =  lt_inv_item.
                    ENDIF.
    *     map details
          READ TABLE lt_inv_item INTO  wa_inv_item WITH KEY BZKEY = ls_key_item-value.
                    ls_item-instance_id = lv_wiid.
                    ls_item-invline_item =  wa_inv_item-BZKEY.
                    ls_item-COST_CENTER =   wa_inv_item-KOSTL.
                    ls_item-COMPANY_CODE =    wa_inv_item-AUSBK.
                    ls_item-FISCAL_YEAR =  wa_inv_item-GJAHR.
                    ls_item-GLACC_TEXT =   wa_inv_item-TXT20.
                    ls_item-FISCAL_YEAR =  wa_inv_item-GJAHR.
                    ls_item-GL_ACC_NO =  wa_inv_item-SAKNR.
                    ls_item-INV_DOC_NO =  wa_inv_item-BELNR.
                    ls_item-INVOICE_AMT =  wa_inv_item-WRBTR.
          CALL METHOD copy_data_to_ref
            EXPORTING
              is_data = ls_item
            CHANGING
              cr_data = er_entity.
    You might have to handle exceptions in this code and this is just an example.
    thanks
    Ashish

  • Sale order costing process : Help required

    Hello All,
    Belatted Happy New Year 2011 to all.
    I have a question related to Sale Order Costing. It goes like this,
    My client is into Pipe coating business who receives the pipe from the customers, coats it as per there requirements and despatches it thereon. There is no concept of FG here as its only the service he is doing on it and also when he receives the pipe there is no raw material cost on it. Raw materials for him would be chemicals etc which he uses to coat the pipe.
    And also this demands variant configuration from SD and PP angel.
    As this scenario is customer specific, it demands Sale Order based costing(Sale order cost estimate).
    My doubt is, how the sale order costing process goes with.
    In general scenarios, Make to stock, we use production order based costing where standard cost estimate is calculated for planned cost and actuals are incurred on PO settling the variance to COPA
    Similarly how the costing goes with if Sale order cost estimate is used. What i think is, here instead of Standard cost estimate for plan, we will go with Sale order cost estimate at sale order level, and incur actual cost at production order and settle the cost of Production order to Sale order. Correct me if i am wrong, and request you ppl there to explain me the process of costing in the scenario said above.
    apart from that, my client wants the flexibility to change the cost estimate at quotation level.
    Please suggest me with solution explaining the process of costing here.
    Thanks in advance,
    Ravi Kumar

    Hi Ravi
    Your understanding of the scenario is very much right...
    In your case, you need to have sales order as cost object...
    Process
    Your stock would be non valuated stock, because the FG is not your stock.. You are just doing a service
    Based on the characteristics chosen in the Sales orders, system would determine the Sales order BOM
    Based on sales order BOM, Sales order cost estimate would be calculated....
    You would receive the Customer pipe in your stock against the sales order... It would be a non valuated GR... You can track the Qty only
    Sales order would trigger a production order... The prod order can have its planned cost, which is only for information sake
    The Customer Pipe, Chemicals would be issued to prod order to coat the pipe... And also Labor/machine hrs may be confirmed
    There after your production order would be settled on Sales order
    Then you would do PGI (Post Goods Isue).. This will not trigger any accounting doc
    Then you do billing... The sales revenue would be posted on the sales order
    Then you settle the sales order to COPA.. This will close the cycle
    Configuration
    The IMG Settings required would be as below
    1. You would use account assignment category (AAC) E
    2. Create a Requirement class with
    a. AAC = E.... (Means sales order is CO Object)
    b. Valuation Indicator = BLANK (Means Non Valuated Stock)
    c. Costing ID/Costing Method = As per your choice to calculate the Sales order cost estimate
    3. Assign this req class to Requirement Type
    4. Give this req type to your PP/SD team.. They would assign it to Strategy group / Item Category to determine it in the sales order
    Regards
    Ajay M

  • Function Module to fetch Customer Number from Sales Order or Process Order

    Hi Gurus,
    I am looking for a Function module which gives me customer number from Sales order or Process order.
    Please let me know of any FM's available.
    Regards,
    Madan

    Hi,
    Thanks for your response.
    I am actually looking for function modules which take "Sales Order" or "Process Order" as input (import parameter) and return Customer Number as output (export parameter).
    Please suggest some function modules you know any.
    Many Thanks,
    Madan

  • Sales order stock process

    Hi All,
    We are planning to implement sales order stock process. There is some confusion regarding the picking process of sales order stock. Can anyone help me in this matter, how to do picking for sales order stock item? Is this in the normal way or not?
    Thanks,
      Vijesh

    Hi,
    yes the stock is maintained for sales order and even blocked in MB1B using 412 -E ..in MMBE now the stock is showing as sales order stock .
    this part is clear,
    now the issue is regarding picking... how can we to picking process..can we do picking using sales order stock..it is because , in LS24 the stock is showing as E which is not in any bin locations.
    In the normal process we are doing the picking from bin locations..
    thanks to advise the picking process in sales order stock.
    Best Regards,
    Vijesh

  • Move order approval process

    Please!
    Can any one tell me the full setup for move order approval with navigation?

    Hi,
    There is no separate setup for move order approval process.
    But you should ensure the following:
    1. Inventory org parameters - Mover order time out period should be greather than zero.
    (Otherwise move order will get approved automatically)
    2. Create an item and assign a planner to it.
    (Ensure planner is an employee and having assigned user id)
    3. Create a move order requistion
    4. Approve
    (Move order will go for approval. Assigned planner to the respective item will get notification)
    Tks
    Jagan.

  • To change/overwrite material price in sales order - while processing

    The scenario is - when the user creates a sales order in system 1, there has to be an RFC called to another SAP system to get the price of the materials in that system. Then it has to overwrite that price in this S.O in system 1.
    Which user exit in S.O processing can be used for this ? (Lets say to get price we use some BAPI to the other system). But how the price can be overwritten on this S.O in system 1 ? Any help ?

    HI,
    you do a RFC while entering your order to get the price.
    If you store the price in vk12 in System 1 and do new-pricing, in our system, that woult take too long. The pricing conditions need several secondes ( i wait up to 10 seconds ) from vk12 up to the time, you can use it in va01. ( due to the synchronisation between several application-servers ).
    I would try to do it in MV45afZB in the form new-pricing. Insert a manual condition in xkonv ( check in ther is an xkonv-updkz ) and select new-pricing = 'C'.  ( at this time i have no access on you system - i don't know, if xkonv is avalible - if not my next choice would be mv45afzz / userexit vbap ).
    perhps that will do. good luck.
    hans

  • MTO-Need to block (Not to Change)plant in sales order after process order

    Hi All,
    We are creating MTO sales order and requirement has been forwarded to MRP. Planning person is creating process order and will start their work. Sometime sales person change the plant in the existing sales order. Say for ex: changing the plant from 1000 to 1001. But requirement is already been transferred to 1000 plant. After changing the plant in sales order again the same requirement transferring to 1001 plant for planning. So based on this, 1001 plant also started producing the material. Here the problem is both the plants are producing for the same requirement. Now I need to control the this problem. Is there any way to control in std sap? if possible which way we can control? Please share your ideas.
    Thanks in advance,
    Babu

    hi
    use user exit
        MV45AFZZ
    FORM USEREXIT_FIELD_MODIFICATION    
    here you write the logic
    when production order  exit that line item plant is not changeable ,

  • Sales order approval based on Price

    Hi Champs,
    Have a scenario which needs to be mapped in SD.
    Flexibility to decide if the billing needs to be processed for the respective sales order even if the actual price is lower than the sales budgeted price is required.
    System will first compare the actual sales price with the budgeted price and if found lower a release for the sales order will be trigerred and attached to the sales order.
    The function of this release in sales order will be to block the sales order at the time of billing creation. Please note that in this option, system will not stop the user from creating the sales order.
    Until the authority does not release this order, the billing cannot be processed.
    Can you please guide me if you have come across any such requirement.

    Create one budgeted price conditon in the pricing procedure as statistical. The actual price should be compared with the budgeted price condition & if it is greater then automatically set a billing block. The billing block (VBAK-FAKSK) can be set automatically through the Module Pool MV45AFZZ & you make sure to put the logic that once the billing block is removed manually (Approved) then set VBAK-FAKSK eq initial.

  • BADI for Sales Order Item Process

    I am using BADI BADI_SD_SALES_ITEM to process and fill customer-material number for certain items of a sales order which are not automatically filled.
    I am inside the IF_EX_BADI_SD_SALES_ITEM~ITEM_PROCESS where I have access to all the item data in FVBAP. I need the ship-to party from the Sales order header. How do I access header data inside the Item_process method ?
    PS : BADI_SD_SALES_ITEM badi is meant for internal use by SAP. I changed it to be used externally.

    >
    Shareen Hegde wrote:
    > PS : BADI_SD_SALES_ITEM badi is meant for internal use by SAP. I changed it to be used externally.
    That will be interesting when hot packs go in.

Maybe you are looking for