Relating outbound idoc to inbound idoc to create a document

We have a requirement to relate the outbound idoc to inbound idoc , transfer the data and create a document.
Kindly let me know the tcode / configuration steps of how can we relate the idocs.
Thanks,
Nalini S.

Hi Juan,
Check the IDOC: WMATGRP01. Hope it will be helpful for you.
BR,
Lokeswari.

Similar Messages

Outbound Idoc after created Invoice document

Hi All,
May i know how to create outbound idoc after invoice document created.
Because i just found out some solution for inbound idoc.
Regards,
Luke

You need to set up the Output type using the NACE tcode and this output type should be configured to trigger the IDOC. Check the below link.
http://www.erpgenie.com/sapedi/messagecontrol.htm
This output type can be linked with the IDOC type in WE20 tcode.
~Srini
Edited by: VaasPal on Dec 22, 2011 8:13 AM

IDoc to Create Shipment Document in SAP

Hi,
I want to create the shipment document in SAP via EDI message from freight forwarder and subsequently update the shipment document(VT02N) statuses via EDI like planned/loaded/shipment end etc....
I am reasearching on the Idoc type for that...I found SHPMNT03 etc could be used to create/change document but I don't know where the Transportation planning point field exists in the Idoc type. Please help me to how could I create the shipment document...
I am able to create the shipment document using TPSSHT01...but not sure whether it would be good as it's used with TPS and we don't have any external TPS. We just want to create shipment document in SAP based on freight forwarder edi messages 856 I believe
I am new to EDI
Thanks
Chil

We used a program to create the IDoc but I don't see a transportation planning point anywhere in it. I think it should be picked up automatically from the deliveries and I wouldn't fixate on that. Here is the code fragment, but you don't need to fill in all those fields:
e1edt20-shtyp = '0003'.
      e1edt20-signi = i_table-route.
      e1edt20-exti1 = i_table-route.
      e1edt20-exti2 = i_table-driver_num.
      e1edt20-tpbez = i_table-driver_name.
      i_edidd-sdata = e1edt20.
      i_edidd-docnum = w_docnum.
      i_edidd-segnam = 'E2EDT20001'.
      APPEND i_edidd.
      e1adrm4-partner_q = 'OTP'.
      e1adrm4-partner_id = '0001'.
      i_edidd-sdata = e1adrm4.
      i_edidd-docnum = w_docnum.
      i_edidd-segnam = 'E2ADRM4001'.
      APPEND i_edidd.
      e1adre4-extend_q = '305'.
      e1adre4-extend_d = '0001'.
      i_edidd-sdata = e1adre4.
      i_edidd-docnum = w_docnum.
      i_edidd-segnam = 'E2ADRE4001'.
      APPEND i_edidd.
    e1edl20-vbeln = i_table-vbeln.
    i_edidd-sdata = e1edl20.
    i_edidd-docnum = w_docnum.
    i_edidd-segnam = 'E2EDL20'.
    APPEND i_edidd.
From what I remember, this IDoc worked rather strangely and I had to fill in some fields for no obvious reason (e.g. both e1edt20-signi and e1edt20-exti1 when SIGNI is really the one we needed). At some point, I just tried filling in all the possible fields to get past errors. Like I said, it just takes some trial and error.
Unfortunately, I don't have access to that system anymore and have no further information. Also we didn't do any shipment changes. You might want to search in ABAP forum. Good luck.

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Duplicate outbound Idoc created for outbound delivery

Hi Gurus,
We use decentralised whse system for goods movement.
For couple of outbound deliveries there are double idocs created (messge type SHP_OBDLV_SAVE_REPLICA).
I have no idea how the duplication taken plcae. Any body come accross this kind of issue .
Please help to reslove the issue .
Thanks in advance

Hi,
There is nothing in message control tab for outbound parameter(we20) and even there are multiple changes in delivery.
What we do is as soon as the delivery is created . Z trnx is executed which changes the dec whse status A(Relevent ) to B (distribution) simulteneously outbound Idoc is created and delivery details send to whse.
Normally there will be one outbound idoc per delivery , but in this case there are 2 (duplicate)

Outbound idoc has data from previous idoc as well

Hi Experts
I am doing the goods receipt against a scheduling agreement using idocs. If this goods receipt is succesful, I am triggering an outbound idoc informing the WMS of the goods receipt. For example, if idoc number 1 comes in for GR , code has been mentioned in the inbound function module for trigger of an outbound idoc A. Please note that the difference that this isnt the case of an output type.
Now the problem that arises is , the idoc data for outbound idocs is being accumulated and sent. For example, if 1 is the GR idoc, A is the outbound idoc, then 2 is the 2nd GR idoc, then AB is the data coming 2nd outbound idoc (instead of just B), then 3 is the 3rd GR idoc, then ABC is the data coming for 3rd outbound idoc(instead of just C)
I am a little confused about the same as to which area this pertains to and would really appreciate quick help on the same.
Regards
Shubhankar

Hi,
How are you testing this functionality ? Is it using WE19 test transaction or ??
If that is the case then please come out of transaction everytime you process the idoc.
Also, clarify your scenario in more detail.
Processing of your single inbound idoc creates more than one outbound idocs or
for every inbound idoc which is processed you are creating one outbound idoc in user exit.
Also check if the idocdata internal table is refreshed once an outbound idoc is created.
If possible please send your code.
KR Jaideep,

Sender port in an Outbound IDoc

Hi
Can someone please mention where is configuration for IDoc sendor port.
We generally give Receiver port information in outbound parameters in partner profile(WE20). But there is no place where we give the Sender port information.
When an outbound idoc gets created, in the control records you can find the Sender port. Can someone tell from where this port is picked up.
In most of the cases I can find port name SAP<SYSID>. Is this something SAP standard. ?
Thanks,
J.

Hi Brad,
Can you tell me where its hard coded. which program/func module. ?
Thanks,
J.

Outbound idoc missing

Hi All,
Outbound idocs not created for some documents only when we post from VL02, even the document not blocked in tRFC. Message type added in partner profile for outbound processing.
Please suggest me wht is the reason.....
Thanks in advance!!!!!!!

Hi,
Check if you are maintaining some filter criteria in the distribution model like specific company code or sales org.
Thanks
Krithika

ME59 Purchase order outbound idoc header text missing in segment

Hi All,
When Purchase Order created via ME59 for third party vendor Outbound Idoc is created but Header Text of PO not copied into IDOC Segment.This Problem occurs when PO has sales order assignment.
Please Advice..
Thanks,
Vinod.

Hi Ankur,
I am not an expert in this area but I'm looking on an ORDERS05 iDoc where I have the following data for E1EDK14:
E1EDK14 014:
QUALF: 014
ORGID: [Purchasing organization ID]
E1EDK14 009:
QUALF: 009
ORGID: [Purchasing Group ID]
E1EDK14 013:
QUALF: 013
ORGID: [Purchase Order type, e.g. EC]
E1EDK14 011:
QUALF: 011
ORGID: [Company Code]
Hope this helps!
Regards,
Kristoffer

Resend an outbound idoc

Hi experts,
Can you please let me know how to resend an outbound idoc. It is HR master data related outbound idoc. Some idocs have been sent previously from SAP to business connector to a third party application. But the idocs did not reach the application. Is it possible to resend the same idocs from SAP again.
Thanks in advance,

Hi,
For HR data, you can resend using program RHALEINI in the order of organizational objects O,S,P, C
Thanks
Krithika

How to trigger an Outbound IDOC with a default status 68

Hi,
How an Outbound IDOC can be created/triggered with a default status 68??
I have a requirement where the outbound IDOC should always get created with status 68. Once an Outbound IDOC is created, I should not be changing its status manually or using a program.
Basically we don't want any IDOCs created in other status and changing to 68 once an IDOC is created with a different status.
Currently i'm using fm 'IDOC_OUTPUT_DELVRY' to trigger an outbound idoc, and the idocs are triggered with different status 30, 2, 3 etc... By using a program i can change the status of the IDOC. But what we need is "Whenever an outbound idoc is triggered, it should always have status 68".
Please let me know the ways to achieve this functionality.
Thanks!

Hi,
We need to display all the IDOC data on a Smartform layout. But we dont need the IDOC to be used for our requirement. So we want to make sure that IDOC is triggered but will not stay in 02 or other status.
We have a process to monitor the failed idocs (02 status) and we do not want our idoc to have failed status. So we need the idocs to be tirggered directly with status 31 (thanks for letting me know that i cant use status 68 for outbound idocs).
Thanks!

Outbound EDI IDOCs for G/L document posting

Hi All,
I'm trying to generate outbound IDOCs from G/L documents (FB70, FB75 transactions).
Of course INVOIC IDOC type does not work for this.
Does anybody know which is the IDOC type for G/L documents?
Really appreciated any help.
Thanks and regards!
Beatriz Balones
SD and MM Senior Consultant

Hi
it means you can use this document type only if you post the document by B.I (It's special usage).
This characterist is setted in customizing (trx OBA7).
You should choose another document type or change that configuration if you think it's wrong.
In my system the flag "Batch Input Only" for SA is space.
Max
Message was edited by: max bianchi
Message was edited by: max bianchi

User exit , transaction F110, an outbound Idoc

Hi,
During the payment process in transaction F110, an IDOC is generated. I need to identify the user exit within the IDOC build process to do some special processing.
The special process is to substitute the POSTING DATE on the IDOC with the NEXT PAYMENT DATE from the proposal.
Regards,
Jyoti Shankar

Hi Joyti,
I have requirement to trigger outbound IDOC after generating payment document....as your reply i think you already did this requirenment.
Kindly help how to configure outbound IDOC for this............
Plse reply me soon....
Thanks.

IDOC to create from outbound delivery from sales order as INBOUND process

Hi Experts,
We have third party interface for sales processing. Sales order, Outbound delivery and PGI will be done in Third party software and XML files will be send to SAP.
We have to process this XML file into SAP with IDOC.
Sales order processing is done but i am not able to find correct IDOC type for creating outbound delivery.
Can you suggest Basic IDOC type / Message type and process code for the same.
Regards,
Sahadev Abhyankar

Good morning !
In the transaction WE20 to create the customer EDI KU with EM function.
Output parameter: message type DESADV and basic IDOC DESADV01.
I associate the IDoc message type to LAVA, you should link it to the XML file, that is not how.
Please : Could you please explain how you linked the XML file to IDOCS to create sales order ?
Sorry for my poor English
A greeting.

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

Relating outbound idoc to inbound idoc to create a document

Similar Messages

Maybe you are looking for