Inbound IDoc Usetr-Exit

Hi All,
I am trying to find an userexit for the Inbound Idoc.
<b>Basic type : COPAGN01.</b>
If anyone has used any user exit for the COPAGN01 kindly let me know.
Best Regards,
Manish

Hi,
Go to SPRO and find enhancements idoc, it will show u both exit available for idoc.
Or goto se84-> enhancements find the idoc keyword search. It will give u the desired result.
Hope this will work for u.

Similar Messages

  • Inbound IDOC user exits

    Re: IDOC User Exits
    Posted: Aug 1, 2006 10:43 AM        Reply      E-mail this post 
    Hi
    I have a basic doubt. We can modify or add new segments and change existing values to segments only for outbound idoc.
    I have a requirement where a particular field in a segment would be empty for an inbound idoc. Is it possible to change inbound idoc values after the idoc is created and before it gets posted.
    Please let me know,
    Regards,
    B.Anandh

    Updating IDoc data in segments.
    STEP 1 - Open document to edit
    CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
           EXPORTING
                document_number               = t_docnum
           IMPORTING
                idoc_control                  = itab_edidc
           TABLES
                idoc_data                     = itab_edidd
           EXCEPTIONS
                document_foreign_lock         = 1
                document_not_exist            = 2
                document_not_open             = 3
                status_is_unable_for_changing = 4
                OTHERS                        = 5.
    STEP 2 - Loop at itab_edidd and change data
    LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
      e1edka1 = itab_edidd-sdata.
      IF e1edka1-parvw = 'LF'.
        e1edka1-partn = t_eikto.
        itab_edidd-sdata = e1edka1.
        MODIFY itab_edidd.
        EXIT.
      ENDIF.
    ENDLOOP.
    STEP 3 - Change data segments
    CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
               TABLES
                    idoc_changed_data_range = itab_edidd
               EXCEPTIONS
                    idoc_not_open           = 1
                    data_record_not_exist   = 2
                    OTHERS                  = 3.

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

  • Inbound IDoc user exit

    I am attempting to write my first user exit for an Inbound IDoc. Outbound seems easy by comparison. I am going to add a date to VBAK-MAHDT from and extended ORDERS03 segment. My extended segment is pretty much like E1EDK03.
      I'm working with enhancement VEDA0001. For include ZXVEDU03 of component EXIT_SAPLVEDA_001 I have this so far:
    DATA:
      w_z1edk03 LIKE z1edk03,
      w_vbak LIKE vbak.
    CASE segment-segnam.
      WHEN 'Z1EDK03'.
        IF segment-sdata(3) = 'Z01'.
          w_z1edk03 = segment-sdata.
          MOVE dxvbak TO w_vbak.
          w_vbak-mahdt = w_z1edk03-datum.
          MOVE w_vbak TO dxvbak.
        ENDIF.
      WHEN OTHERS.
    ENDCASE.
      Am I on the right track? Isn't there something else that I need for include ZXVEDU04 of EXIT_SAPLVEDA_002?

    I went ahead and added:
    IF contrl-mestyp = 'ORDERS' AND
      contrl-idoctp = 'Z_EK_ORDERS03'.
    for that check Mahendra.
      I am trying to figure out how to update dxbdcdata correctly to add my data to the screen in EXIT_SAPLVEDA_002 include ZXVEDU04. With the debugger I see updates in dxbdcdata for screens '4002' and '4003' but not for '4001' where I believe my data should be added. Do I just append the records for '4001' myself and does it matter what order it is in?

  • Inbound IDOC User Exit ZXVEDU04 change IDoc Data

    Hi all,
    We have to develop an user exit for changing the Plant, Shipping Point and Storage location
    We have identified the exit ZXVEDU04 . Is there some other exit for this ??
    But which internal table we are supposed to change this to change the data .
    If possible send me a sample code
    Thanks in Advance .
    Vivek K ..

    Hi all,
    I have done this for a single line item IDoc .
    How do i go for IDocs with more than one line item ???
    I have hardcoded VBAP-WERKS(1) etc for Plant, Strg Loc and shp pt .
    How to identify how many line items are there in the IDocs ??
    Thanks in Advance .
    Vivek K ..

  • Inbound IDOC User Exit ZXVEDU04

    Hi all,
    We have to develop an user exit for changing the Plant, Shipping Point, Storage location, Shipp to party and Pricing date .
    Now the requirement is changed , only Pricing date has to be changed . Please give me some answer .
    We have identified the exit ZXVEDU04 .
    But which internal table we are supposed to change this to change the data .
    If possible send me a sample code
    Thanks in Advance .
    Vivek K ..
    Message was edited by: Vivek Krishnan Kandasamy

    Internal table dxdbdata will the Screen flow.
    you can read the the table   
    read table dxbdcdata with key fnam = 'VBAP-WERKS'.
        if sy-subrc = 0.
    *--- filed dxbdcdata-fval will have the plant,here you can assign a new plant.
          dxbdcdata-fval = new plant
          modify dxbdcdata index sy-tabix.
        endif.
        read table dxbdcdata with key fnam = 'VBAP-VSTEL'.
        if sy-subrc = 0.
    *--- filed dxbdcdata-fval will have the shipping point ,here you can assign a new shipping point.
          dxbdcdata-fval = new shipping point
          modify dxbdcdata index sy-tabix.
        endif.

  • Doubt in Idoc user exit..............

    Hi All,
               i have written the user exit for Sales Order subscreen tab called <b>additional data2</b> , this tab is provided by sap for developer can write their own user exit coding.
               my doubt is whenever PO comes as an <b>Inbound IDOC i need to pass the value from</b> <b>segment to my user exit fields</b>.
               <b>where can i find the inbound idoc user exit for SO .</b>
                Thanks in advance,
    Regards,
    Saravanan.

    Look at enhancement VEDA0001. It has got quite a few user exits you can use. You will also need to enhance the IDOC for the additional fields you have added on your screen.
    Cheers,
    Sanjeev

  • Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

    Hello all,
    I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
    Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
    The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc. 
    So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
    In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
    During the development and testing phase in the Sandbox system this works.
    However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
    I was wondering if there are any ideas why this could have happened?
    Oh ... I  also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
    Well I hope to hear from you.
    Regards
    Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

    Hi,
    Check in t.code CMOD whether project is active or not (Activate the Project)
    BR,
    Vijay

  • Inbound idoc values when updated from user exit not saved

    I'm trying to process some user exits of an inbound idoc from WE19.
    The values get correctly populated to IDOC_DATA internal tables of IDOC_INPUT_ORDRSP function module in debug kode
    but when the new idoc is generated from WE19 , those segment values (populated by exit) are not shown/saved.
    The user exit is EXIT_SAPLEINM_007.
    Is it not possible to populate segment values of inbound idocs from using user exits. If yes , then during testing using WE19 , every time a new idoc is created it should display those values into the concerned segments. Please help.

    Hello,
    yes is possible it ...
    I think the problem is:
    or
    you have something wrong when to append the new line on internal table
    or
    the exit used is not correct: read the documentation on EXIT_SAPLEINM_0**

  • User Exit / Badi after (inbound idoc) database commit

    Hello Folks,
    I want to know the User Exit/Badi that can be used after inbound idoc gets posted, as i want to use perform on commit statement.
    Thanks & Regards,
    Nishanth Kumar

    Hi Sengupta,
    Usually there are no user-exits after COMMIT.
    What you need to do is register a call which will be executed after COMMIT, from one of the available user-exits.
    To do this, SAP provides 2 methods:
    1. PERFORM xxx ON COMMIT
    2. Function Module with attribute "Update Module"
    Check ABAP keyword help for more information for PERFORM xxx ON COMMIT.
    <a href="http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm">http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm</a>
    Hope this helps.
    Regards,
    Sumant.
    PS: Reward points if this is helpful.

  • User exit for inbound idoc

    could anyone please tell the user exit for inbound idoc : ACC_POSTING_GL01

    I thnk the inbound idoc name is ACC_GL_POSTING01. User Exit for this is EXIT_SAPLACC4_001.
    *****Reward points if useful
    Regards,
    Kiran Bobbala

  • PORDCR - Inbound IDOC via User-Exit

    Hi All,
    I would like to create a Purchase Order via an inbound Idoc with a message type PORDCR.
    I would like to make use of the enhancement MM06E001 and the function module EXIT_SAPLEINM_002 to populate data segments.
    Please advise if this is the correct user-exit to process an inbound idoc.
    Any input appreciated.
    Meghna

    Hi Meghanarrao,
    IDOC_INPUT_ORDRSP-->PERFORM fill_data_ordrsp-->and find the below user exits for each segment...
    List of user exits available for --
    EXIT_SAPLEINM_001   
    EXIT_SAPLEINM_002   
    EXIT_SAPLEINM_003   
    EXIT_SAPLEINM_004   
    EXIT_SAPLEINM_005   
    EXIT_SAPLEINM_006   
    EXIT_SAPLEINM_007   
    EXIT_SAPLEINM_008   
    EXIT_SAPLEINM_009   
    EXIT_SAPLEINM_011   
    EXIT_SAPLEINM_012   
    EXIT_SAPLEINM_013   
    EXIT_SAPLEINM_014   
    EXIT_SAPLEINM_015   
    EXIT_SAPLEINM_016   
    EXIT_SAPLEINM_017   
    EXIT_SAPLEINM_018   
    EXIT_SAPLEINM_019   
    EXIT_SAPLEINM_020   
    IDOC----- Dir -Enhancemnt --Description
    ORDCHG -O -MM06E001   -- Purch. Ord. Change
    ORDCHG- I -VEDB0001     --Sales Ord. Change
    ORDERS- O -MM06E001   --Purchase Orders
    ORDERS -I- VEDA0001     --Sales Orders
    ORDRSP -O- SDEDI001    --Order Confirmation
    ORDRSP -I- MM06E001    --Order Response for Purchase Order   "This is the Right one for Purchase order create
    IDOC           Msg        ANSI EDIFACT I O
    ORDERS01 ORDCHG 860 ORDCHG X X
    ORDERS01 ORDERS 850 ORDERS X X
    ORDERS01 ORDRSP 855 ORDRSP X X
    IDOC_INPUT_ORDRSP--Function module-BUS2012-Inbound-Purchase order / order confirmation
    regards,
    Prabhudas

  • Creation of Service Contract from Inbound IDOC

    Hi Experts,
    I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a  Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
    So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
    Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
    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

  • Sale Order from Inbound IDOC

    I am testing creating Sale Order from inbound IDOC with WE19.
    Partn. number = AAA001
    Partn. type = KU
    Partn.func = PY
    Message Type = ORDERS
    Process Code = ORDE
    I get message 51 "Error: Application document not posted" in IDOC status:
    VKORG, VTWEG, SPART cannot be determined for customer AAA001 , vendor                                                                               
    Message no. VG 204                                                                               
    Diagnosis                                                                               
    No sales organization, distribution channel or division were sent to the
        IDOC. This data is necessary if a sales order is to be added           
        automatically. If this data is unavailable, you cannot create a sales  
        order document.                                                                               
    Procedure                                                                               
    If data on the sales organization, distribution channel and division   
        have not been entered in the IDOC, it must be determined using a user  
        exit defined in the program.

    I will receive IDOC from external non-SAP system.
    How can i populate E1EDK14 segment with appropriate values:
    E1EDK14 -QUALF = 006
    E1EDK14 -ORGID = Division (VBAK-SPART)
    E1EDK14 -QUALF = 007
    E1EDK14 -ORGID = Distribution Chanel (VBAK-VTWEG)
    E1EDK14 -QUALF = 008
    E1EDK14 -ORGID = Sales Organisation (VBAK-VKORG)
    If external system does not know this values?
    Edited by: S S on Feb 28, 2009 12:46 PM

  • Create shipment from inbound IDOC SHPMNT05 ?

    Hello All,
    I would like to create an individual shipment when i receive from a partner an inbound IDOC.
    I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
    How can I start the creation of the shipment with this inbound IDOC ?
    Is it possible ? or is it necessary  to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)? 
    Thanks a lot,
    My

    Hello Reddy
    thanks for your answer.
    is there particular customizing to be done ?
    i exactly use function BORES_IDOC_INPUT_SHPMNT
    The inbound idoc is generated but i have the following status message 51 "Application document not posted"
    What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
    Thanks a lot
    MY

Maybe you are looking for