UTP - Test Plans IDOCs - Inbound -Outbound

Hi All,
can some one please provide the samples of standard UTP - Test plans for INBOUND & OUTBOUND IDOC interfaces, if you have such.
Regards,
Sridhar

Hi,
I am also in need of UTP for outbound IDoc.
Please forward me to my id : [email protected]
Your help would be appreciated.
Thanks,
Sangeetha

Similar Messages

ALE/Idoc (inbound & outbound)

Hi,
Can any one help me by providing simple sample code for creation of ALE/Idoc (inbound & outbound). Where I need do understand flow cycling of outbound from one client to other inbound client. Waiting for replay. My email-ID is [email protected]
Regards,
Lokesh.K

Hi,
have you seen these documentation sections?
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2174b051ce11d189570000e829fbbd/frameset.htm">Implementing Inbound Processing</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2177bc51ce11d189570000e829fbbd/frameset.htm">Implementing Outbound Processing</a>
Hope they'll help.

Unit test plan for inbound and outbound interfaces

I am trying to create a UNIT TEST PLAN for an interface. In this interface a flat file in IDOC format is picked up from the application server and processed using EDI_DATA_INCOMING for the relevant posting ( example : Sales order creation from a PO IDOC). IF the file is not in IDOC format then it is reformatted to the IDOC format manually.
In second scenario(outbound), after sales order creation or billing document creation, IDOC is created which is read and a custom flat file is created and sent to a middleware.
PLease suggest a unit test plan for these kind of scenarios or send a sample UTP if possible.
REgards
Nishant
PS: points will be awarded to helpful answers.

Unfortunately this isn't possible, the esa has only one routing table. You'll have to add specific routes for your internal networks.
I usually avoid two-armed setups because of this and it gets even worse if you want to use virtual gateways (traffic gets sent via the internal interface with an IP from the external interface)

Urgent: Automate IDOC Inbound/ Outbound

Hi all,
I need to automate the whole IDOC process, inbound and outbound.
For inbound, I need to run or schedule a program that will read all files in a given directory as separate idocs. Note that the filename is not constant, whatever file is in the given directory should be consumed. I don't know if I can use we16 for this still. If I could do this, I just need to schedule RWPOS_PARA_ENQUEUE and I' finished.
For outbound, what do I do for the system to automatically generate IDOCs? I thought if I activate change pointers, IDOCs will automatically be generated if a change is detected. I am using SAP Retail, one of the idocs is similar to matmas but I cant use BD10 for this. The other two idocs are still problems for me.
In short, what do I do to automate eveything?
Thanks so much,
Kenny

Hi Kenny Martinez ,
For Inbound Automation
First attach your idoc to a process code.
In the process code you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Good Luck and Reward me for the same.
Thanks
Ashok.N

IDOC(Inbound/Outbound) - SAP(ABAP)

Hi Everybody,
i m new to iDOC programing .I know to create logical sytem,rfc destination,port, partner profile ,idoctype,messagetype integration idoctype into msgtyp but i don't know hw to develop program for both creation of outbound idoc and inbound idoc.Could u guide me with small example of each one .
i m waiting for ur reply...........
Thx and Regds in Adv.
Prabhas

Hi Prabhas,
Check the following sample FMs:
IDOC_INPUT_ORDERS
IDOC_OUTPUT_ORDERS
Check the Tcode WE41 & WE42 to find the FM attached to the Process code.
For BAPI programming Tcode - BAPI
BAPI programming guide:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
BAPI user guide:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
For creating a RFC - SE37
RFC is a remote-enabled Function Module.
Create a function module with attributes Remote-enabled.
RFC programming in ABAP:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
hope this helps!
best regards,
Thangesh

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

Need IDOC inbound and outbound programs

hi,
i am new to xi.
i want IDOCs , inbound and outbound / function module programs for PURCHASE ORDER
and GOODS RECEIPT.
ex: BD10 for material master (matmas01).
thanks and regards
v ijender

for purchase order.
ORDERS / ORDERS04
ORDCHG / ORDERS04
ORDRSP / ORDERS04
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
and also check the below link
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
regards
kummari

Send inbound IDOC as outbound(copy)

Hi,
We need to send the same inbound IDOC as outbound IDOC to the customer(they want to get a copy of it) How can we do this? We are getting inbound sales order IDOC's and the customer wants the copy of the same IDOC, not order acknowledgement. Is it possible?
Any inputs are greatly appreciated.
Sarita

I can think of following:
You create your own Process code, Function Module to update your data using Inbound IDOC and at the end generate outbound IDOC using same data and then distribute using MASTER_IDOC_DISTRIBUTE.

IDOC Inbound and Outbound

Please let me know How to handle IDOC inbound and Outbound preferably with example. I am new to it.

hi,
your question is very broad,
start reading continue from there...
<a href="http://help.sap.com/saphelp_46c/helpdata/en/19/3cf334c20ccc52e10000009b38f83b/frameset.htm">Doc Interface: EDI Application Scenarios (BC-SRV-EDI)</a>
<a href="http://help.sap.com/saphelp_46c/helpdata/en/dc/6b8a4943d711d1893e0000e8323c4f/frameset.htm">IDoc Interface / Electronic Data Interchange (BC-SRV-EDI)</a>
An example:
inter company invoiceing:
the SD invoice has an output type (INVOICE01) that sends an Idoc that creates the mm invoice (invoice verification)
for more data see the links above
good luck

Converting Inbound idoc to Outbound idoc

Hii,,
How to convert inbound idoc to outbound idoc.
I have IDOC -> SOAP -> IDOC Scenario.
In case of error at SOAP side , it return idoc with 51 status.
Now i need to convert the Inbound idocs to Outbound Idocs and send it back to the Sender system...
How to do accomplish this??
Regards,
Siya

Hii,
By using we19 and by exchanging sender & receiver we can convert outbound idoc to inbound idoc.
Just want to confirm is it proper way??
Regards,
Siya

How to write utp(unit test plan)

how to write utp(unit test plan)

Hi,
Steps to be followed for UTP.
UTP : Unit Test Plan. Testing the program by the developer who developed the program is termed as Unit Test Plan.
Two aspects are to be considered in UTP.
1. Black Box Testing
2. White Box Testing.
1. Black Box Testing : The program is executed to view the output.
2. White Box Testing : The code is checked for performance tuning and syntax errors.
Follow below mentioned steps.
Black Box Testing
1. Cover all the test scenarios in the test plan. Test plan is usually prepared at the time of Techincal Spec preparation, by the testing team. Make sure that all the scenarios mentioned in the test plan are coverd in UTP.
2. Execute your code for positive and negative test. Postive tests - to execute the code and check if the program works as per expected. Negative Test - Execute code to know if the code is working in scenarios in which it is not supposed to work. The code should work only in the mentioned scenarios and not in all cases.
White Box Testing.
1. Check the Select statments in your code. Check if any redundant fields are being fetched by the select statements.
2. Check If there is any redundant code in the program.
3. Check whether the code adheres to the Coding standards of your client or your company.
4. Check if all the variables are cleared appropriately.
5. Optimize the code by following the performance tuning procedures.
Using tools provided by SAP
1. Check your program using EXTENDED PROGRAM CHECK.
2. Use SQL Trace to estimate the performace and the response of the each statement in the code. If changes are required, mention the same in UTP.
3. Use Runtime Analyser and Code Inspector to test your code.
4. Paste the screen shots of all the tests in the UTP document. This gives a clear picture of the tests conducted on the program.
All the above steps are to be mentioned in UTP.
Regards,
Vara

What is IDOC Inbound process and Outbound Process?

What is IDOC Inbound process and Outbound Process?
can any one explain about the inbound and outbound process step by step?
Tks in advance,
Phanikumar

Hi,
Inbound means transfer legacy data to SAP system and
outbound means transfer SAP system data to legacy system.
Regards,
Prashant

Mapping Inbound-Outbound IDocs

Hy everybody,
Is there a table in the receiving system where inbound IDocs numbers are linked to outbound IDocs numbers from the sending system ?
Regards,
Christian Baldari

Hi,
there is no link from inbound idoc to outbound idoc.
We will only come to know by looking document flow.
Sales order - Docuemnt flow
Delivery - Docuemtn flow.
You will come to know all the things by looking docuemnt flow.
ramesh

IDOC inbound processing ( Function module Rquired )

Hi,
I am working on IDOC inbound, I am looking for a standard FM for Production order confirmation which i need to assign in WE57 along with the standard Message type(Production order confirmation).
Could you please let me know where i can get the standard inbound function modules for the standard idoc types,
for eg: IDOC_INPUT_ORDERS for sales order.
Thanks.
Krishnakumar

Hi,
Go to WE42 for inbound processing codes and WE41 for outbound.
OR
We have WE19 which is a test tool for IDOC processing.
Provide the IDOC number then press F8, then in the next screen , you will have inbound function module.
Click that button. Then enter the text in search criteria.
Then you can get related function module.
Reward points if helpful.
Thanks and Regards

Activate IDoc Inbound Processing in LSMW

Hi Gurus,
Why do we need to activate the IDoc Inbound Processing in LSMW if we are going to use BAPI or IDoc in LSMW?
Thanks and Regards,

Hello Paulo
Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
Regards
Uwe

UTP - Test Plans IDOCs - Inbound -Outbound

Similar Messages

Maybe you are looking for