Creation of Sales orders through EDI

Hello,
We have a problem when creating sales orders through EDI.
We are getting IDOCs with a delay of 1 second.Before  
creating sales orders through the posting function
module IDOC_INPUT_ORDERS, we need to validate for
reference Purchase order number in the IDOC. If there is
any sales order in the database with the Purchase order
number in the current IDOC that sales order should be 
blocked.
We already put a validation in the User-Exit of the
posting function module. Because of the frequency of
IDOCs we receive, this validation is getting failed.
Can anybody tell me, how to process only 1 IDOC at any
given point of time before the Posting process.
Thanks,
Madhusudan.

Hi Sanjeev,
  Thank you very much for helping me out in this problem.Still I haven't got the solution.
I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
  can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
Regards,
Madhusudan.
Message was edited by: Madhusudan Budati
Message was edited by: Madhusudan Budati

Similar Messages

  • Creation of Sales Order through EDI

    Hi
    Can anybody explain in detail the configuration steps involved in creating the sales order through EDI. If possible with screen shots.
    Points will be rewarded.
    Thanking you
    chan

    Hi Hari & Siva,
    Could you please send the document to my mail id
    [email protected]
    Thanks in advance
    MMVD

  • Creation of sales order through Purchase order

    Hi all
    We have a special scenario in creation of Sales order with the help of purchase order,
    Could you please advice me how we can create sales order with the help of purchase order.
    Thank YOu
    Swaroop

    you can create the sales order from the purchase order.It can be achieved by Idocs.
    Please maintain the condition record for the output medium EDI and also maintain the Partner profile in WE20.

  • Creation of Sales order through inbound idoc

    Hi,
    I'm using two servers 100 and 200.In 100 i'm creating outbound IDOC for PO,In 200 sales order has to be created for that PO.I'm facing some problem in server 200.
    Error i'm facing  : Partner profile not available.
    I done all the basic setting like Logical system,Port and Partner profile creation in both servers.
    Kindly advice.
    By,
    Sathish.

    Hi Satish,
    Are you sure  WEL1 setting is correct?
            The message seems to be telling you that it is looking for a vendor with
    number 00000000 (zero) which doesn't sound too good to me.
    You therefore bill the intercompany customer in sales org 0021 (the
    intercompany receivable is in 0021). The intercompany payable is thus in
    company code 0043, so that looks right.
    Other things to check:
    1. Does your IV billing document get generated in sales organisation
    0043 with customer 300043 as the bill-to?
    2. Check the number of 0's you have in WEL1 Log.addr field. We use
    alphanumeric customer numbers for our "internal" customers so there's
    not an issue with leading zeroes, but it might be a problem for you. it
    seems you've got it right because you've padded with leading zeroes to
    get it to 10 long, but you never know.
    3. have you created your RD04 condition records in VV31 correctly?
    I guess u may find the answer to this link.
    http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/intercompany-billing-edi-partner-profile-not-available-1409203
    Thanks
    Mohinder Singh Chauhan

  • Creation of Sales Order through BAPI_SALESORDER_CREATEFROMDATA2

    Hi friends,
    We are creating Sales order using the  BAPI -BAPI_SALESORDER_CREATEFROMDATA2. Due to some technical problems we are not able to pass the contract start and end data that we desire, the BAPI picks up the default contract start and end date from the contract profile. 
    There was no response in the ABAP forum hence seeking a solution if anyone has achieved the same here.
    Please advise.
    Regards,
    Udaynath.

    Are you creating a sales order with reference to a contract or is it just an isolated sales order? If it's the latest then what's the relevance of the contract dates and how did you configure them exactly?
    If you are referring to an existing contract, then, as I've already said, most likely it won't be possible to specify the different dates when creating the order.
    Also not all functionality is available with BAPI, so you might have to resort to BDC. Additionally, I'd suggest to check the ABAP forum, this BAPI has been discussed there before. A message to SAP might also be a good idea, if you're using standard document types and configuration.

  • Issue with UPC codes in Inbound sales orders via EDI.

    Hi All
    We are on ECC 6.0. We have incoming sales orders through EDI IDOCS. In the incoming IDCO the customer can provide either of the following information in that sequence.
    1.  GTIN number
    2.  Customer material number
    3.  UPC code
    4.  Old Product code.
    We need to derive the correct material number for each customer. Now I can achieve this through standard material determination using material determination type access sequences in the order specified above. However I cannot do the same, as we need to use material determination for genuine promotions. For example I can maintain a material determination record to map UPC 123456789 to Material number ABC in SAP R/3. However we do have situation where in for a particular season or depending upon the ATP situation we may have to derive Material XYZ (SAP material number) in case customer orders material ABC. So in other words if I use material determination to derive my SAP material number for in-coming IDOCS based on UPC codes then I would need to have multi level material determination. I.e. From an IDOC for UPC code 1234566789 I derive material ABC and then for material ABC derive material XYZ.
    I tried setting up these two layers of material determination in the standard system. It is possible only if I use a substitution reason which copies the material entered as a sub-item. We do not want to maintain the sub-item in sales order and relevant documents for a lot of other reasons. Is there a way I can use standard Material determination/substitution to derive this multi level search without haveing to copy the sub-item in sales order? Am I missing some settings here? If not is it possiblt to suppress the sub item from being derived in SAP using some user exit in sales order processing?
    For an IDOC I could have used standard SAP tables to identify SAP material number based on UPC code. However the problem is we have multiple SAP material numbers assigned to one UPC code. So it is not possible to identify a unique material number just based on the UPC code.
    I would like to know if any of you experts have encountered a similar situation and if so what is the ideal way to resolve this issue. Any comments/suggestions/guidance is welcome. You can also reply at my e-mail id [email protected].
    Thanks

    Hi Daniel,
    Can you please which IDoc message type you are using to create sales order using IDoc?
    Also check in IDoc, what is the value of ACTION & EINKZ fields in segment E1EDP01?
    Regards,
    Amit

  • How to create a Sales Order through an EDI configuration.

    Hi
    How to create a Sales Order through an EDI configuration.
    Tell me the step-by-step procedure for this.
    Any power point presentation would be fine.
    Cheers
    Maruthi

    Hi,
    You can go to these links to know little bit about sales order creation through EDI/ALE by means of IDOCS.
    http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Sales Order Idoc Extension.
    http://www.*******************/2007/11/abap-idocs-basic-tools.html
    For any specific information, just do a google search(information like message t ype, IDOC type, Functoin module, etc. You will definitely get the information you are looking for
    Please reward if this helps you

  • Information Messages while creation of the sales order thru EDI 850

    Hello All,
    I am trying to create a Sales Order using EDI 850. When i am doing the same i am getting the information messages and the Sales Order is not created and the IDOC is in 51 status. I am using the ORDERS05 Idoc Type.
    Following are some of the messages i get:  1. Oldest of open items overdue; 2. Document Complete 3. ISO Country code not found.
    some are valid message and i have already fixed them. But when i create the sales order manually it gives me the sales order number even though i get the information messages.
    Please let me know is there any setting that i have to make for EDI process to counter the information messages.
    Thank You,
    Suresh

    whats the final message you got? that will give you what is the issue.
    in you look at IDOC_INPUT_ORDERS, it does some basic validations first, and collect those errors in ERRTAB and set the status to 51. for manual reprocessing of the IDOC, it doesnt care about those pre validations, and goes directly into VA01 processing

  • Creation of  Sales Order throogh Intercompany STO

    Dear SAP Gurus,
    I have a question
    In the intercompany stock trasnport orders.As per the standard process
    i) Creation of STO
    ii) Creation of replenishment delievry.
    iii) Goods Issue from the supplying plant.
    iV) Good receipt at the receiving plant.
    Our requirement is to create a sales order through IDOC in place of delivery at the delivering company code.
    All the subsequent docuements like delivery and shipment will be based on this newly created sales order.
    I want to know primarily that is there anyway of creating a sales order instead of Delievery subsequent to creation of STO.
    IF so how can we disable the SAP standrad process ( Std Intercompany STO process) and enable our requirement.
    A quick response is highly appreciated.
    Regards
    Ganesh

    Hi,
    You can create sales order in the background while creating intercompany purchase order.
    By using BAPI BAPI  BAPI_SALESORDER_CREATEFROMDAT1.
    Ask your technical team to desing.
    Regards
    Ravi Shankar.

  • Adding Sales BOM to Sales Order through SDK

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

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

  • HOW TO CONTROL ON CREATION OF SALES ORDER WITH REFERENCE TO EARLIER SO?

    Dear All,
    I want to contol on creation of Sales order with reference to earlier SO?  While creation of sales order our enduser are creating sales order with reference to earlier month SO which I want to restrict. Recently I made changes in sales order like payment terms is grayed, system will atomatically pick pay terms from customer master.Now I am getting correct data also but enduser is using old SO no while creating new SO and old payment data is reflecting in fbl5n.
    I want to restrict enduser while creating new SO with ref. to old SO. Only for returns they should be able to use Billing refrence. Pl. suggest how to control the with reference to ealier SO.
    Nikhil

    Nikhil Deshpande,
          If you dont want allow create a sales order in referent to other one, just delete the copy control between these sales order type, so when the user tries to create a SO in reference to other one a message is displayed that is not possible.
    Thanks,
    Mariano.

  • Issue with creation of sales order in CRM system

    Hi Experts,
    Here are the details of the process we followed
    1.     We found a Function Module u201CBAPI_BUSPROCESSND_CREATEMULTIu201D which is used to create a sales order in CRM.
    2.     We have set a Break point in the FM u201CCRM_ORDER_MAINTAINu201D and tried to create a sales order using the transaction u201CCRMD_ORDERu201D. For this the parameters we have given are
    a.     sold-to-party
    b.     ship-to-party
    c.     quantity
    d.     product
    And after this we have saved the order and the order is saved and in the debug mode we have the parameters in u201CCRM_ORDER_MAINTAINu201D and we found all these     parameters in the FM.
    3.     After this we have given all the parameters mentioned above in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and still the order is not created, gave an error message saying that CRM_ORDER: Incorrect values in the interface object.
    4.     We checked the CRM_ORDER badiu2019s interface and it is having only header guid to be given. We gave this header guid also in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and then it gave a different error saying that : Document cannot be saved.
    5.     Finally we are not able to know the parameters to be passed to the FM to create an order.
    Any inputs will be highly appreciated.
    Thanks a lot in advance.
    Lakshman.

    Hi Easwar,
    Now i am able to create a sales order by passing the parameters to "BAPI_BUSPROCESSND_CREATEMULTI" and the parameters i am passing are Process_type in the ORDERADM_H, parner_fct (partner function), partner_no , Quantity and prod_ordered (product name) but after creation of sales order using my report program and if i see the sales order uisng transaction crmd_order (using transaction ID) or crmd_orderadm_h(using headerguid) or crm_order_index, only the PROCESS_TYPE is updated but the remaining parameters which i passed like QUANTITY,PRODUCT NAME,PARTNER NUMBER are not present in the sales order. I am providing the code which i have written for creation of the sales order. Can you please look into it and tell me where i might have went wrong??
    *& Report  ZCREATEORDER_TEST
    REPORT  ZCREATEORDER_TEST.
    DATA : LV_HEADER_GUID  TYPE  GUID_32,
    WA_HEADER            TYPE         BAPIBUS20001_HEADER_INS,
    ITAB_HEADER          TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
    ITAB_PARTNER        TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
    lt_product_i TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
    wa_product_i  type BAPIBUS20001_ITEM,
    lt_schedlin_i type standard table of BAPIBUS20001_SCHEDLIN,
    wa_schedlin_i type BAPIBUS20001_SCHEDLIN,
    ITAB_INPUT_FIELDS TYPE TABLE OF bapibus20001_input_fields,
    ls_inputfields TYPE bapibus20001_input_fields,
    WA_PARTNER          TYPE BAPIBUS20001_PARTNER_INS,
    ITAB_RETURN          TYPE STANDARD TABLE OF BAPIRET2,
    WA_OBJECTS_TO_SAVE  LIKE LINE OF ITAB_OBJECTS_TO_SAVE,
               "To store the Objects to be saved.
    WA_CREATED_PROCESS  LIKE LINE OF ITAB_CREATED_PROCESS,
    ITAB_SAVED_OBJECTS   TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
    WA_SAVED_OBJECTS    LIKE LINE OF ITAB_SAVED_OBJECTS,
    GC_X type c.
    gc_x = 'x'.
    CALL FUNCTION 'GUID_CREATE'
      IMPORTING
        ev_guid_32 = lv_header_guid.
    CLEAR : WA_HEADER.
    Passing the respective values from the Header table to internal table.
    WA_HEADER-GUID          =  LV_HEADER_GUID.
    WA_HEADER-PROCESS_TYPE  =  'ZTA'.
    APPEND WA_HEADER TO ITAB_HEADER.
    *Appending the values to the ITAB_HEADER.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_H'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PROCESS_TYPE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    *ls_inputfields-ref_handle = '0000000000'.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-objectname = 'ORDERADM_H'.
      ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_H'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CHANGES MADE
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'LOGICAL_KEY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
       ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'QUANTITY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
       ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CHANGES MADE
    WA_PARTNER-REF_GUID = LV_HEADER_GUID.
    WA_PARTNER-REF_KIND = 'A'.
    giving the partner function and partner no 000000038 for slod to party
    WA_PARTNER-PARTNER_FCT = '00000038'.
    WA_PARTNER-PARTNER_NO = '10017'.
    APPEND WA_PARTNER TO ITAB_PARTNER.
    *"ADDING VALUES for the product
      wa_product_i-header        = lv_header_guid.
      wa_product_i-handle        = '0000000001'.
      wa_product_i-ordered_prod  = '12000014'.
      wa_product_i-mode          = 'A'.
      APPEND wa_product_i TO lt_product_i.
    *"ADDING VALUES for quantity
      wa_schedlin_i-quantity   = 30.
      wa_schedlin_i-handle = 1.
      APPEND wa_schedlin_i TO lt_schedlin_i.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    *ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'REF_GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PARTNER_FCT'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PARTNER_NO'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
      TABLES
        HEADER          = ITAB_HEADER
        ITEM            = lt_product_i
        RETURN          = ITAB_RETURN
        PARTNER         = ITAB_PARTNER
        INPUT_FIELDS    = ITAB_INPUT_FIELDS
        CREATED_PROCESS = itab_created_process
        SCHEDULELINE    = lt_schedlin_i.
    READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
    WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
    Appending the Guid of the contract to be saved to the internal table
    APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
    CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
      EXPORTING
        update_task_local = space
        save_frame_log    = GC_X
      TABLES
        objects_to_save   = itab_objects_to_save
        saved_objects     = itab_saved_objects
        return            = itab_return.
    Calling the Standard BAPI to Commit the transcation.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    I have debugged the above code, all the values are passing are passing to the FM "'BAPI_BUSPROCESSND_CREATEMULTI'" and these passed to the CRM_ORDER_MAINTAIN and then to CRM_ORDER_READ which are called inside the "'BAPI_BUSPROCESSND_CREATEMULTI'". Finally the sales order is created but not able to see all the values that i am passing except PROCESS_TYPE.
    Thanks a lot in Advance,
    Lakshman.

  • Creation of Sales Order and Service Contract from Inbound IDOC

    Hi Experts,
    My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
    I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
    Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
    I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
    Thanks in Advance.
    Regards,
    Priyabrata

    Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
    Regards,
    Priyabrata

  • Import of Sales Order through DTW

    Dear All
    I am having problems in importing Sales Orders through DTW. I have used the template 'oOrders' and enter the required data in the 'Document' and 'Document-Lines' files.
    When, I run the DTW and uploaded the Sales Orders, it was imported successfully. But when I search in SBO, no Sales Order was created.
    I have also, unchecked the box 'Test Run', but still it doesnot posted any Sales Order.
    Kindly, help me in this regards
    Thanks and Best Regards
    Nabeel

    Dear Gordon
    Thanks for your prompt response.
    In the 'Documents' template, I filled the following columns:
    RecordKey   CardCode            DocDate       DocDueDate  
    1                  AAJ-KAC-6         20081203      20081203
    In the 'Documents-Lines' template, I filled following columns:
    RecordKey    ItemCode                 DocDate       DocDueDate     Price   Quantity   Tax Code
    1                  701-0020-0000         20081203      20081203         10        10            X0
    I, also tried to post the Sales Order manually by entering the above data and SO was posted. But it is not posting through DTW.
    Thanks and Best Regards
    Nabeel

  • Dates fields issue in the sales orders through IDOC

    Hi all,
    I'm trying to create a sales order through Inbound IDOC using IDOC_INPUT_ORDERS.
    I have 2 custom fields in the sales order which are date fields.
    I'm populating them from the IDOC segments(using E1EDKT1-tdid, E1EDKT2-tdline) in the user-exit just before the call trasacation statement. These dates are not coming for a few orders... but are getting populated normally for few of them.
    But the tricky part is that... if I process the same IDOC for the second time.. the order created is having the dates.
    My issue is that.. i need all the orders to be populated with the dates which IDOC have.
    Could anyone please help me with this issue.
    All the answers/replies are highly appreciated!!
    Thanks for you help!

    hi,
    the following may be of help
    There are 2 major exceptions to the batch input internal table. All text data from the segments E1EDKT1/2 and E1EDPT1/2 are not part of the batch input session. Text elements from these segments are posted directly to the data base AFTER the sales order has been created (please note: in order that item texts are posted correctly to the sales order the field POSEX from segment E1EDP01 MUST be transmitted). Also, configurable material information from the IDOC is exported to a global memory and therefore will not be part of the batch input session. Configurable material data is performed in Form CHECK_CONFIGURATION and the data is exported to global memory in the following code:
    Exportiert IDOC Daten ins globale Memory     
    export IDOC data to global memory            
      call function 'CUXC_IDOC_TO_MEMORY'          
           tables                                  
                cfg_instref = xe1curef             
                cfg_ref     = xe1cucfg             
                inst        = xe1cuins             
                part_of     = xe1cuprt             
                value       = xe1cuval             
           exceptions                              
                error       = 1                    
                others      = 2.                   
    One extra piece of useful infomartion if you wish to debug the process is to set your breakpoints at the following points
    for Function module IDOC_INPUT_ORDERS
    include LVEDAF0F..
      CALL TRANSACTION 'VA01' USING bdcdata
                                MODE  input_method
                                UPDATE 'S'
                                MESSAGES INTO xbdcmsgcoll.
    Now input_method is A foreground process and N for background processing but try changing it to P (pass through mode)
    If you have breakpoints in va01, e.g. MV45AF0B_BELEG_SICHERN,(the part where the sales document is saved)
    they will be hit, e.g
    perform userexit_save_document_prepare.
    perform userexit_save_document.
    Lastly, don't forget using program SDJEDI , see note 380603 for more information on this
    Hope this is useful
    Paul Quinn

Maybe you are looking for