Sales document creation error.

Hi Guru's,
I am using a function module to create a sales order. But i'm getting an error which says: For object RV_BELEG , number range interval  does not exist.
How to rectify this?
Below is the code :
CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'
         EXPORTING
              SYNCHRON                   = SPACE
              STATUS_BUFFER_REFRESH      = SPACE
              REQUISITION_BUFFER_REFRESH = SPACE
              REFERENCED_PM_ORDER        = CAUFVD_IMP-AUFNR
         IMPORTING
              EVBAK                      = VBAK_LOC.
Please help.
Thanks,
Das

Number range objects are maintained in transaction SNUM, but before you rush off to that transaction you should check what happens in the standard Sales Order create - i.e. do you get the same message in VA01?  It could be you have wrong values in your SD_SALES_DOCUMENT_SAVE setup.
Jonathan

Similar Messages

  • Reg: Sales document creation

    Hi Abapers,
    As i am new to SD Module, would like to get some ideas from your end. My requirement is to create a sales order using Programming. After creation of sales order it should post to finance. Could anyone help me how this can be done.

    REPORT  ZSALESORDER.
    * Parameters
    * Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    * Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    * Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    * Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    * Start-of-selection.
    START-OF-SELECTION.
    * Header data
    * Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    * Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    * Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    * Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    * Partner data
    * Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    * Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    * ITEM DATA
      itemx-updateflag = 'I'.
    * Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    * Material
      item-material = p_matnr.
      itemx-material = 'X'.
    * Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    * Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    * item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
    *   ITEM DATA
      itemx-updateflag = 'I'.
    * Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    * Material
      item-material = p_matnr.
      itemx-material = 'X'.
    * Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    * Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
    *   Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
    *   Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    *   Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
    *   Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    * Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    * Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    * Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.
    Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:58 AM

  • While saving the sales document .this error is coming.

    Is there any body to help it out .......
    While saving the document this error is coming
    **Financial document: No financial document assigned**

    Dear dinesh
    It seems the field "Financial doc.no" is made as mandatory in VA01.  Also if I am right, you are trying to create an export sale order which is against L/C.
    To create L/C, go to VX11N, give the required datas and save.  While saving, system will generate a reference.  Make a note of this reference and now go to VA01, give the required datas and select header Billing tab where you can find a field "Financial doc.no.".  Assign the above reference here and now save.
    thanks
    G. Lakshmipathi

  • Sales document creation using bapi

    Hi Experts ,
    When i try create sales order using bapi " BAPI_SALESDOCU_CREATEFROMDATA'" , it says error like this , Please enter sold to party and ship to party, even though we are sending partner number it shows same error , if we pass values directly in se37 we get the correct result , but when we are calling it in program it says error.
    Error on this field : partner Number
    Thanks & Regards
    Siva Krishna

    Hi shiva,
               Please go through the documentation,
    Sales document type is checked with sales and distribtion document type.
    You must at least enter order header data (using the structure ORDER_HEADER_IN) and partner data (using the table ORDER_PARTNERS).
    Furthermore, you must enter the business object for which the sales document is to be created:
                   - BUS2030 for inquiries
                   - BUS2031 for quotations
                   - BUS2032 for sales orders
    I think ur program,
    does not pass business object , kindly check

  • Sales Document creation

    I am creating the sales document using the FM SD_SALESDOCUMENT_CREATE But if we pass net value 120 it creates as 1200. it is same for tax values also if tax is 10 it takes as 100. How can we solve this problem?

    I am creating the sales document using the FM SD_SALESDOCUMENT_CREATE But if we pass net value 120 it creates as 1200. it is same for tax values also if tax is 10 it takes as 100. How can we solve this problem?
    Hi,
    The condition values ( kbetr -  % ) are stored in the database tables in a different format ( Multiplied by 10 ).
    So, before sending the value to bapi divide it by 10.
    wa_condition-cond_value = wa_condition-cond_value / 10.
    The same issue happens when reading the details from KONV.
    Regards,
    Satish.

  • Sales Document Creation in CRM System

    Dear all,
    We are implementing CRM 5.0 and ECC 6.0 (IS-Retail) for our client. As per the Business Process Customer creation take's place in CRM, which uploads Customer Records into ECC system.
    Material Master (Article), Pricing Procedure and Condition Types are being maintained in ECC system only.
    Now the new requirement is to create Quotations in CRM system, in turn it has to upload into ECC system. We have to enable or maintain all article data, Pricing Data and Discounts in CRM system also.
    I don't know how could we exchange the Article Master Records (Material), Pricing Procedures and condition types between ECC system.
    I have expertise in CRM Marketing. by getting basic understanding of CRM and ECC data flow landscape, Middleware Settings and Object downloads, I have confidence to map the requirement into SAP successfully.
    I request you to educate me on this scenario, your help and suggestions will be highly appreciated.
    Thank you
    Raghu ram.

    Hi,
    i'm not quite sure about ECC retail, but for sure, as per CRM 5.0 and ECC 6, depending on your scenario, you may not need whole complete set of pricing, nor the condition tables to be maintained in CRM.
    you can use minimum pricing which is basic condition type PR00. once the quotation is saved in CRM, during the replication process, the pricing will be determined in the ERP and passed back to CRM. so when you look into CRM quotation document, you will be able to find all the condition types maintained in CRM.
    however, this scenario is not suitable if you require customer to review the pricing before saving the quotation, let say internet sales / e-commerce. then in that case you'll probably need to have complete set of pricing in CRM.
    hope this helps.

  • Sales order Creation error -- COPA error

    Hi,
    We are trying to create Sales order and getting error as below;
    Inconsistency between a document field and the prof. segment number
    Message no. KE396
    Diagnosis
    A line item was assigned to a profitability segment (number 046xxxxxx) which has the value 0000005xxx for characteristic Customer. The original document (FI document, sales order, internal order, etc.), however, contains Txxxx in this field. It is therefore inconsistent with the profitability segment found.
    Can anybody please help me to resolve this?
    Thanks,
    Niki Shah.

    H iShiva,
    Thanks for quick reply. We are on ECC 6.0 so, this note is not applicable to us.
    Let me know if you have anything else.
    Regards,
    Niki Shah.

  • Document Creation error - "We're sorry. We can't open document name because we found a problem with its contents"

    Morning Friends,
    I have created a SharePoint 2010 "Site Workflow" that is designed to take information from a form and create a Word doc with the gathered information and store this Word doc in a document library.
    I am using Sharepoint 2013 with Office 2013 
    I understand there are a lot of steps (19) outlined below and I can provide more information as needed but the bottom line is this, workflow successfully takes info from an initiation form, uses the info to create a Word doc. Places this Word doc in a library.
    When attempting to open / edit doc, receive error
    "We're sorry. We can't open <document name> because we found a problem with its contents"
    Details - No error detail available.
    Any info or advice would be greatly appreciated. 
    Very high level view of what I have done:
    1 - Created content type called "Letters"
    2 - Added site columns " First Name" and "Last Name"
    3 -  Created and saved to my desktop a very basic Word document (Letter.docx) that says "Hello, my name is XXXX XXXX"
    4 - In the advanced settings of the "Letters" content type I uploaded this "Letter.docx" file as the new document template.
    5 - Created a new document library called "Letters"
    6 - In Library Settings - Advanced Settings, clicked "Yes" to enable the management of content types.
    7 - Then I clicked "Add from existing content types" and added the "Letters" content type
    8 - Back in the advanced settings of the "Letters" content type I selected "Edit Template" and replaced the first XXXX with the Quick Part "First Name" and the second XXXX with the Quick part "Last Name"
    9 - Created a new 2010 Site workflow called "Create a Letter"
    10 - To the workflow I added the action "Create List Item"
    11 - Configured the action to create Content Type ID "Letters" in the document library "Letter" 
    12 - For the "Path and Name" I gave it a basic name of "Letter to"
    13 - The next step was to create the Initiation Form Parameters and added to form entries "First Name" and "Last Name"
    14 - I then linked the initiation form fields to the data source "Workflow Variables and Parameters" to their respective Field from Source parameters
    15 - Went back to the "Path and Name" and modified the basic name of "Letter to" to include the first and last name parameters.
    16 - Saved - published and ran the work flow.
    17 - As expected, Initiation Form prompts for First and Last Name. ("John Doe") Then click "start
    18 - Go to document library "Letters" and see a new Word document created titles "Letter to John Doe" 
    19 - Go to open / edit the Word document and receive the following error
    thoughts? Any info or advice would be greatly appreciated. 

    See this MS support article for SP2010 workflows and generating Word docs:
    https://support.microsoft.com/kb/2889634/en-us?wa=wsignin1.0
    "This behavior is by design. The Create
    List Item action in the SharePoint
    2010 Workflow platform can't convert Word content type file templates to the correct .docx format."
    I've had success in using SP 2013, Word 2013 (saving a .docx as the template instead of .dotx for the document library content type), and an SP 2010 workflow using SP Designer 2013.

  • Sales order creation error

    Hello Everyone,
    I am getting this error while creating a sales order : Please analyse and let me know the solution:
    Material 302309 is not defined for sales org.5000,  distr.chan.06,  language 
    EN                                                                               
    Message no. V1 382                                                                               
    Diagnosis                                                                               
    Material 302309 is not defined for the following combination of          
         requirements:                                                                               
    o   Sales organization 5000                                                                               
    o   Distribution channel 06                                                                               
    o   Language EN                                                                               
    System Response                                                                               
    The system allows no further processing.                                                                               
    System Response                                                                               
    The system allows no further processing.                                                                               
    Procedure                                                                               
    You can check whether                                                                               
    o   the material number that you entered is correct                                                                               
    o   the material has been created for the sales organization and       
             distribution channel                                               
            <i><b>                                                                    
         o   a short text with the appropriate language exists in the material  
             master record (a short text must be available in the language of   
             either the customer or the sales organization)                     </b></i>
            I guess the error lies here in this particular point...there is some text maintained in customer master record which i am not able 2 remove ...
                                                                                    The material must meet all three of the above requirements before you  
         can process it further.                                             
    Thanks in advance

    Hi Sachin,
    Have you checked whether the material 302309 is created in the Sales org 5000 and dist. channel 06
    If it is maintained in the same sales org, then goto Material Master of 302309, using T.code MM02.
    Now goto Administrative Data and give there Language as EN and your material no. and save it.
    Now create the order once agin, there wont be any prob.
    Hope this is clear.
    REWARD IF HELPFUL.
    Regards,
    Praveen

  • Output determination does not happen during Sales Document creation

    Hello All,
    I am facing an issue where the automatic output determination does not happen when the Sales Order is created. Let me explain a bit on the background.
    Output type ZDL2 has been defined as a special function (TNAPR-NACHA = 8) attached to a custom program and Form routine to create Outbound delivery after successful posting of the sales order.
    Condition records are maintained to trigger this output for the Key Combination of Sales Org/Distrib Channel/Division/Route. Access sequence has also been correctly maintained for the above fields.
    When the Sales order is saved, the output is supposed to be triggered but out of several sales orders created, it triggered for just one document. We have no clues on what could be the issue.
    One question here is, can we have the access sequence maintained for the fields from both header and item level (ie KOMKBV1 and KOMPBV1). Please be reminded that, in our case, the field ROUTE comes from the field catalog KOMPBV1.
    Another point which we noticed is that, the Function Module COMMUNICATION_AREA_KOMPBV1 which is supposed to fill the Item data Communication structure for output determination was never called.
    Has anyone came across such situations. Comments or suggestions are really appreciated.
    Kind Regards
    Sabu Kuriakose

    Sabu Kuriakose,
    Since you are using ROUTE as one parameter for the condition table, and it is at the item level.
    the output is triggered at the header level.
    So a sales order can contain multiple items with different routes. so at header level how will u identify the route ?
    the fields might be available for creatign the condition table but the problem is the fields should get the value during order processing.
    in the analsysis screen you will know that the field is getting the value of the ROUTE  or not ?
    also for creating a delivery you need a shipping point. same as above you can hae multiple items with different shipping points. how will u consider that scenario.
    If you can explain that, then that will be helpful to answer your problem.

  • PDF Document Creation Error

    Hi All,
    In one of my webdynpor applications i need to render one PDF document but while i am trying to do the same I am getting this error .
    com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../asianpaints.com/hs_rework_wd/ReworkApplication/~wd_key_80eZ1tsPlvcfxodN/ErrorPDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=b8b061b0906411de8a690050569630a5&sap-wd-appwndid=b8b061b1906411deb5a40050569630a5&sap-wd-norefresh=X
        at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:624)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:972)
        at com.sap.tc.webdynpro.clientserver.phases.RespondPhase.execute(RespondPhase.java:60)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
    in the back end or default trace, the message displayed is
    com.adobe.ProcessingException: Failed to connect to a <Render> XML Form Module.
    Please ensure that the XML Form Module service is running.
    I suppose, there is some service with the name "XML Form Module service " and its not running .
    Can any one help me with the ways to run this service ?? or any other suggestion about why the error would be coming
    thanks in advance

    Smriti,
    Did you upload a valid credential into the Visual admin? Also check that your ADSSAP SP level is the same as your J2EE Engine SP level.
    You can restart the XML Form Module service as follows (if I am not wring) :-.
    1.     Logon to Visual Admin
    2.     On the Cluster tab, choose server -> Services -> XML Form Module
    3.     Right click and stop the service.
    4.     Once stopped, right click and start the service
    Chintan

  • Sales Document Mapping Error

    Tcode SMW01 in SAP CRM
    Bdoc Error
    Bdoc State: E08
    Bdoc Description: Mapping error
    Bdoc Type: BUS_TRANS_MSG
    Bdoc Detail Error Description: Business transaction type ZZZZ does not exist
    The ZZZZ is a quotation transaction type maintained in ECC. But we donu2019t want this replicated in CRM, reason why ZZZZ is not maintained in CRM. The queues in SMQ2 is building-up with these error (R3AD_SALESD* with SYSFAIL status), is there a way to block, filter etc. this transaction type to exclude it from replication? Or other better way to address the problem?
    Thanks in advance!

    Hi Noel
    try setting a filter on object SALESDOCUMENT in Transaction R3AC1.
    Table=VBAK
    Field = AUART( its a guess, can't check it in a system)
    OP = NE> Not Euqal
    Low = ZZZZ
    save it. your filters wil also be updated to R/3
    Hope it helps
    best regards,
    Remko

  • Sales Document Creation with SD_SALESDOCUMENT_CREATE

    Hi All,
    I am trying to create a Sales Order using FM SD_SALESDOCUMENT_CREATE. I have the following questions:
    1). Do I need to specify the Line Item Numbers? If I don't need to then how does SAP know which line items in SALES_ITEMS_INX and SALES_SCHEDULES_IN tables are referring to the items in SALES_ITEMS_IN?
    2). How do I add the pricing conditions? I see the table SALES_CONDITIONS_IN but what fields do I need to fill in?
    Do I need to fill in the Step number, Condition Count, Condition Type, and Condition Value fields?
    Any suggestions will be greatly appreciated.
    Regards.

    Hi Aurag,
    Why dont you use the BAPI "BAPI_SALESORDER_CREATEFROMDAT2" - the line item numbers can be assigned by you or system will assign them as per configuration setup. Look at the documentation for this BAPI and you will understand what needs to be populated.
    Cheers

  • 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

  • Handling Business Area for sales documents

    Hi Experts,
                   My requirement is that , I have to change the default Business area  , determined by the system , at the time of sales document creation . For Eg: I have two business areas 0001 and 0002.
    When i create a sales document , by default system determined business area 0001. But  if certain conditions are met , i have to change the business area to 0002. and finally when we post the document to the Accounting after billing , the document must hit the business area 0002.I could able to change the business area in the sales documents through the user-exits available for Delivery document and Billing document .But when i post the document into accounting , the entries are going into wrong business area . How to handle this situation.
    Thanx in advance.
    Durga.

    You mean there is a different business area in sales and account document after creation? Are you sure?
    Or your user exits might not be updating properly? else system might be re-defining business area in accounting thru configuration.
    Regds
    Manohar

Maybe you are looking for