Inbound Idoc Testing File Template

Hello friends,
Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
Only these are the 4 segments I am going to use.
E1BPACHE09
E1BPACGL09
E1BPACAR09
E1BPACCR09
Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
I am able to test post one document at a time thru WE19.
Thanks for ur help.
Sam.

Hi Sam,
Try this, to my knowledge this is only to test if idoc is posted properly or not (to check the configuration), we can only post one Idoc at a time i think...but try this...
am not sure  but try this...
Go to WE19-> acc_docume*>control on the data segment and copy it->insert(next to copy in menu bar) the segment at the same level> fill the data and post it ...to see..just try this...
Thanks
Ajay

Similar Messages

  • Inbound idoc testing via partner profile

    i want to test inbound idoc testing via partner profile.
    the problem is i its generating idoc no and giving a message like
    "idoc no 12453152.. is saved but cannot or shd not be processed".
    what does that mean ..
    how shd i veiw properties of partner p[rofiles

    i am getting thid message from we 19 ..
    in that i am creating a sales order...
    i am clicking on startinboung button on application tools bar.
    this is an information pop up window ..
    if i press f1 on that ..
    help says that ...may be you  cannot process the idoc immediatly...
    check for partner profiles

  • Inbound Idoc Testing

    Hi All ,
    Can anyone pls let me know how to test Inbound Idocs.
    I am writing a ZFM to process orders01 idocs coming from the external system. After writing the code, how can i test the same for the IDOC that has to come . I mean to say : Idoc will not be available at the port in real time now (only once the system is up ,the Idoc really come). SO , what is the way to test the program developed for Inbound processing of Idoc of a certain type ?
    Thanks,

    Hello,
    Use WE19, copy any existing Idoc, and then use your FM to test it.
    If there isn't any then make an file on the server, which actually will be generated by Outbound processing.
    Regards,
    Naimesh

  • Inbound IDOCs - which file

    Is there a way to identify the name of an inbound IDOC file after it's been imported into SAP?
    I know the file processed correctly because the IDOC went to status 53.
    But, the file that created the IDOC isn't shown in the control record when it's displayed with transaction WE05.

    Hi guys,
    Thanks for replying, but that's not exactly what I was asking about.
    When a file is imported into SAP with program RSEINB00, the original file is automatically deleted by the program.
    What I wanted to know was if the path/name of the file was saved somewhere.
    Outbound IDOCs have the information details of the Status "03" segment. Unfortunately, inbound IDOCs don't seem to have anything similar.

  • Inbound idoc from file

    i run a job to upload text file to inbound processing of IDoc
    the job run in two steps with two program
    RSEINB00 : to upload the file
    RBDAPP01 :to activate the list of the idocs
    but the job failed in the second step and it  return
    " During inbound processing of IDoc , an error occurred. The event for object type 'IDOC' could not be triggered "
    any one know why ???

    Hi Kenny
    I have also faced a similar issue in the past: To automate the process of file reading and triggering the inbound process whenever partner system (legacy system) copies a text file (containing data to be posted) to the SAP application server.
    To automate file reading for inbound process, you have to use SAP events. You can define these events using transaction SM62.
    This event will be used to execute the IDOC create program in a job based on this event.
    Every time the partner system copies the extract file to the SAP application server, this event will be  triggered which then runs the job for processing the data file.
    For more information on using SAP events, click the following link and look into topics under heading ‘Using events to trigger job starts’:
    http://help.sap.com/saphelp_erp2005/helpdata/en/fa/096e44543b11d1898e0000e8322d00/frameset.htm
    the topic, ‘Triggering events from external programs’ is quite interesting.
    Cheers
    Ashish Jain
    [email protected]

  • Testing Inbound IDoc via WE19...

    Hi,
    I am trying to learn IDOCs via WE19.
    I just took a sample IDOC from WE02 and tried to test in WE19.
    I am trying to understand what do we mean by following:
    1) Process Inbound IDOC via file ?
    2) Process Inbound IDOC via function module ?
    Regards,
    Rajesh,

    Rajesh,
    Go thru this link
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

  • Inbound IDOC File Testing

    Hello friends,
    Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
    Only these are the 4 segments I am going to use.
    E1BPACHE09
    E1BPACGL09
    E1BPACAR09
    E1BPACCR09
    Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
    I am able to test post one document at a time thru WE19.
    Thanks for ur help.
    Sam.

    Did you find the answer for you question?
    I am trying to do the same to run a LSMW that load data through FB50 but I don't find how to fill the structures.
    Thanks.

  • How to Test, Inbound idoc ,with out the Sender System, using a Text File

    Hi Guru's .
    we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
    on the same client.
    we wanted to test this idoc with text file from our local machine.
    Can anyone give us detail steps.like how to create  File layout
    with Segment name,and values for the fields.how to pass this file to the system.
    Thanks in advance.

    Hi Aparna.
    My requirement is to test the idoc with Inbound File.
    Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
    when i am trying to do this syst complaing about
    Partner Profile not available, and some times
    port not available. and some  times with
    'No further processing defined'.
    but i maintained part profiles and port perfectly.
    Can you help me in testing with test 'File' port.

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • Testing of an inbound idoc.

    hi experts,
    i have to create an inbound interface for processing message order/ordchg.I have a .txt data file .how do i test my inbound interface so that the data in the text file is passed onto the inbound idoc?
    Valuable help will be rewarded.
    Regards,
    Shrita.

    Hi shrita sharma
    1)Generating Idoc as a flat File on the outbound.
    2)Uploading File as IDoc in the Inbound System
    1) Send an outbound IDOC data(ORDERS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    Good Luck and Reward me for the same ..!!
    Thanks
    Ashok

  • How to create Inbound Idoc from XML file-Need help urgently

    Hi,
    can any one tell how to create inbound Idoc from XML file.
    we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml'  we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
    Please let me know the process to trigger inbound Idoc with out using  XI and any other components.
    Thanks in advance
    Dora Reddy

    Hi .. Did either of you get a result on this?
    My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
    I see lots of mention of using a Function Module.
    Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
    Or is there something tht can be done with Standard SAP?
    Thanks
    Lee

  • Inbound IDOC Format (Flat File)

    Hi,
    I'm using SAP CRM Middleware for communication between CRM and Legacy System.
    I have configured Outbound IDOCs and I see something like this:
    EDI_DC40  2200000000000000023700 3012  CRMXIF_PARTNER_SAVE_M01                                     CRMXIF_PARTNER_SAVE_M
    E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX
    E201CRMXIF_PARTNER_HEADER000  220000000000000002300000200000102CRMXIF_PARTNER_HEADER         BusinessPartner                 U
    E201CRMXIF_PARTNER_KEYS000    220000000000000002300000300000203CRMXIF_PARTNER_KEYS           0000000014488DDB8AD891249EE10080010A6CA883
    The questions are:
    I need to know how do the following information must be filled in an Inbound IDOC:
    The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...
    So I need how do fields like IDOC number must be filled in an Inbound IDOC
    Thanx in advance..
    BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.

    Hi,
    Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).
    This information you will need.
    The records are builded using the following structure:
    1st record contains control record information and follows the structure of table EDIDC.
    Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).
    All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).
    Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.
    To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.
    Hope this helps you out.
    Regards,
    Rob.

  • Testing Inbound Idocs

    Hi All!
    I am trying to fix an inbound Idoc program that is erroring in our testing environment with a REALLY big IDoc.  I need to move this IDoc to our development environment in order to be able to accurately fix the program.
    Is there any way to move an inbound IDoc from one environment to another without manually re-creating it or having to create an outbound IDoc process of some sort?
    Help is MUCH appreciated - thanks!
    Abby

    Try out this
    On the source system
    Go to WE19 - > IDoc -> Test Inbound IDoc ->Inbound File
    Here enter application server path like
    /appl/interfaces/MDDC/MLGA01
    Also Uncheck the check box Start IDoc inbound processing of file imm.
    On the target system
    Go to WE16
    Give the same application server file name in Directory + File name
    In Port give EDIPORT  and run it.  
    This will create an IDoc
    Regards
    Kesava
    Message was edited by:
            Kesava Chandra Rao

  • How to read file from prsntn server in Inbound idoc FM.

    Hi Experts,
    I am new to idoc.
    I have requirment that i need to read a file from presentation and application server and put in inbound idoc FM.Idoc will be processed in batch.
    How can i put selection screen in FM and read the file?or how can i proceed  with the solution?
    Please help..
    Umesh

    Hi Umesh,
    My understanding on your requirement is to read a file from pres. server and pass the data to an IDoc function module. Am I correct?
    If this is the case then you can create a report which picks up the file from pres. server and then read data from the file and pass it to the parameters of the required function module.
    Hope this helps.
    Regards,
    -Sandeep

  • Creation of Inbound IDOC from a flat file.

    Hi all,
    I hav to create Purchse Order using inbound IDOC in which I hav to take data from a .xls or any flat file.
    Can any one help me with this. i.e wat r the steps involed to do so.
    Regards.
    Rahul

    Hello,
    Why do u want to create a Idoc for creating PO from flat file - you can simply use BAPI. Ok if you want to create PO only using Idoc.
    I think message type is ACC_PURCHASE_ORDER0.
    I just made one sample program to you how to create a PO with Idoc method. Here i am doing for Material Master Creation. Let me know if want any clarification.
    ********Poorna********
    TABLES : MARA, MAKT, EDP13.
    DATA : I_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
          I_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    PARAMETERS : P_MATNR LIKE MARA-MATNR.
    START-OF-SELECTION.
      REFRESH I_EDIDC.
      SELECT * FROM EDP13 WHERE MESTYP = 'ZMATMASTER'.
        MOVE-CORRESPONDING EDP13 TO I_EDIDC.
        I_EDIDC-IDOCTP = EDP13-IDOCTYP.
        APPEND I_EDIDC.
      ENDSELECT.
      READ TABLE I_EDIDC INDEX 1.
      I_EDIDD-SEGNAM = 'ZMATMASTER'.
      SELECT SINGLE * FROM MARA WHERE MATNR = P_MATNR.
      SELECT SINGLE * FROM MAKT WHERE MATNR = P_MATNR
                                  AND SPRAS = SY-LANGU.
      I_EDIDD-SDATA+0(18) = MARA-MATNR.
      I_EDIDD-SDATA+18(40) = MAKT-MAKTX.
      I_EDIDD-SDATA+58(4)  = MARA-MTART.
      I_EDIDD-SDATA+62(1)  = MARA-MBRSH.
      I_EDIDD-SDATA+63(3)  = MARA-MEINS.
      APPEND I_EDIDD.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          master_idoc_control                  = I_EDIDC
       OBJ_TYPE                            = ''
       CHNUM                                = ''
        tables
          communication_idoc_control          = I_EDIDC
          master_idoc_data                    = I_EDIDD
    EXCEPTIONS
       ERROR_IN_IDOC_CONTROL                = 1
       ERROR_WRITING_IDOC_STATUS            = 2
       ERROR_IN_IDOC_DATA                  = 3
       SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
       OTHERS                              = 5
      COMMIT WORK.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

Maybe you are looking for