How to generate Outbound Test IDOC ?

I have the sample IDOC receiver application running and registered with the SAP test system, but now I am trying to find out how to create an IDOC and send it from the SAP system to my test application.
(We are using the test system provided by SAP and I do not have any SAP knowledge)
Can anyone help ?

Hi Andrew,
you can use transaction WE19 for sending IDocs to other systems, for more information see http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/frameset.htm. We alos published a paper a on http://download.microsoft.com/download/5/7/f/57f1490e-8a8d-497b-bbae-ec2a44b3799f/CollaborationBrief.pdf which discusses how to setup the SAP system for IDoc processing, the topic of the paper is different but the steps in SAP should be the same.
- Juergen

Similar Messages

How to generate Outbound idoc for Material Reservation

Hi Experts,
I want to send outbound IDoc when a material reservation is created with tcode MB21.
I have been working on this issue and finding the solution in SCN for a week...
I found some messages similar to this but I could not find out the correct way how to do that.
At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
Implement ALE_RESERVATION_CREATE
I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
Best Regards,
Kenji

Hi;
Have been able to find the solution to create the IDoc MRESCR after entering a reservation?
I am in the same situation and I do not see the IDoc output in the BD87.
It would be nice if you share the solution.
Thanks in advance

How to generate PAYEXT (PEXR2002) IDOC with many invoices for same vendor

Hello,
We are implementing the IDOC payment processing through transaction F110. The first test we ran using multiple items for the same vendor created an IDOC with multiple E1IDPU1 segments for each invoice. We then configured a second bank and ran the test again. This time the multiple invoices for the same vendor generated a seperate IDOC.
Does anyone know where I should start looking to figure out what I did wrong? We are hoping to generate 1 IDOC for all invoices for the same vendor.
Thanks,
Brian

Hello,
May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
Please advise. Thank you very much!

How to build outbound ACC_GL_POSTING IDOC

We have a requirement where we need to build ACC_GL_POSTING IDOC's outbound from SAP. These will be sent to a middleware system where it will be translated and then posted in a separate SAP system using the same IDOC.
Is there an easy way to build the structure in ABAP without causing it to post in the source SAP system??

Let me clarify:
We need to send GL posting information from one SAP system to another. Call the source SAP system, SAP system A.
One method proposed was wrapping up a file and putting all the info in there, parsing it in the middleware, and then posting teh ACC_GL_POSTING IDOC into the target system, SAP system B.
We'd rather use IDOC's on each side of the interface. We know for sure we can use ACC_GL_POSTING in SAP system B to make the postings. We'd like to know how to populate the same IDOC in SAP system A(source) so we can use standard ALE and avoid flat files.

How to send outbound ASN IDoc with all the delivery info on legacy system??

Hi EDI-Gurus,
I have a small question.
We accept inbound sales orders into SAP and send outbound Order Acknowledgments out of SAP. We don't really maintain shipping and billing info on SAP. They are being maintained on legacy. But we have to send Outbound ASN, Invoice out of SAP for them.
Can you please let me know how exactly we can do that in detail.
thanks,
Matt

Can we do this way, correct me if i am wrong.
We'll send ASN when we issue Goods right??. If we get all the Goods issues details relevant to an order from legacy using LSMW using IDoc method, can we send it out of SAP.
I am just wondering if it is possible or not.
Or get the Shipping and Billing details from legacy (using which method i don't know), and using a custom function module can we send the outbound 856 and 810 out of SAP.
Can you throw some light on this?
Thanks,
Matt

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

How to generate an OUTBOUND INVOICE IDOC from the ABAP Program?

How to generate an OUTBOUND INVOICE IDOC from the ABAP Program? Any Function Module that can be used for this?

Hi
This is more of configuration
(1) Create a Output type with Medium 6 ( Check with your functional consultant)
(2) Maintain Partner Profiles using WE20 transaction
       Idoc type - INVOIC02
       Message type - INVOIC
       Process Code - SD09
Regards
Madhan D

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

How to configure, push and test Idoc from XI to R/3

Assuming mapping between imported Idoc and some file structure is fine ,I have to configure XI and R/3 for pushing Idocs from Xi to r/3. I have to make sure they talk.
-I have done this long time ago for pushing Idocs from R/3 to XI but I wonder if it is same procedure or it is different ?
-Can someone tell me - how to configure both for this purpose partner profiles , logical systems etc ?
-And also after configurations , how I can check if Idocs is received from Xi and the entire process is successful?
-does it make difference the type of Idocs during the configurations?
-Are the test for success same for all type Idocs?
Thanks all !
Jon

Here are the steps:
===========================
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
Additional References
Ale Configuration for pushing Idocs form SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

How to create outbound idoc?

Hi Experts,
I want to know , how to create the oubound idocs.What is the procedure ? I sit gets generated on the application server.
Regards,
Rahul.

Hi,
Check this link...
https://wiki.sdn.sap.com/wiki/display/ABAP/Outbound%20Idoc%20Through%20ALE
Regards,
Raj.

How to suppress certain fields in ALE Outbound INFREC IDOCs?

Dear All
Is it possible to suppress certain fields in Outbound ALE IDOCs (for example INFREC IDOCs) ?
I am in need to send Info Records from one ECC system to another. The problem is, in the sending ECC system the INFREC IDOCs are created with the field E1EINAM-INFNR which carries the Info Record number. But the target ECC system might have a different Info Record already existing (for a different article) with the same Info Record Number. If the INFREC IDOCs are created without the INFNR field (i.e. if the field is blank) and then sent to the target system via ALE, it is successfully processed in the target system and a new Info Record is created with a different Info Record number. This is what is required. How can it be made possible?
Thanks
Vignesh Sankaranarayanan

Use the transactions BD62, BD79 and BD55 to setup and assign conversion rules for your IDOC fields and set a constant '/' for the infnr field.
Test if that is enough or you might need to take extra care for the name field of info record texts. I am not in a system currently, so I can't check whether long text name is based on info record number or only a mix of info record keyfields (without info record number itself).
You should also have a look into my blog Stumbling blocks in purchasing info record migration by LSMW IDOC method
You will probably hit the one or other issue that I described too.

How to generate an Idoc form an existing Sales Order?

Hi experts.
Our client needs to generate an ORDERS05 output Idoc for Sales Orders that has already been created.
Is there a way to generate a new Idoc for those Sales Orders?
MASTER_IDOC_DISTRIBUTE won’t do the job cause I don’t how to complete all the segments, I need the standard procedure to be execute.
I thought to use a Bapi to modify the Sales Order, but that might execute routines that we not want to.
Any ideas?
Thanks.

Hi,
You can generate an IDOC from invoice cancellation.Define a new "Z" output type for this cancellation billing document type and select the medium as 5(EDI).Check with your ABAPer for this.
Regards,
Krishna.

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and         places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
                 HTTP connection to ABAP Runtime failed.
                 Error: 403 Forbidden
                 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
                 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
<b>Sender</b>
Service   : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
<b>Receiver:</b>
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

How to generate test data for all the tables in oracle

I am planning to use plsql to generate the test data in all the tables in schema, schema name is given as input parameters, min records in master table, min records in child table. data should be consistent in the columns which are used for constraints i.e. using same column value..
planning to implement something like
execute sp_schema_data_gen (schemaname, minrecinmstrtbl, minrecsforchildtable);
schemaname = owner,
minrecinmstrtbl= minimum records to insert into each parent table,
minrecsforchildtable = minimum records to enter into each child table of a each master table;
all_tables where owner= schemaname;
all_tab_columns and all_constrains - where owner =schemaname;
using dbms_random pkg.
is anyone have better idea to do this.. is this functionality already there in oracle db?

Ah, damorgan, data, test data, metadata and table-driven processes. Love the stuff!
There are two approaches you can take with this. I'll mention both and then ask which
one you think you would find most useful for your requirements.
One approach I would call the generic bottom-up approach which is the one I think you
are referring to.
This system is a generic test data generator. It isn't designed to generate data for any
particular existing table or application but is the general case solution.
Building on damorgan's advice define the basic hierarchy: table collection, tables, data; so start at the data level.
1. Identify/document the data types that you need to support. Start small (NUMBER, VARCHAR2, DATE) and add as you go along
2. For each data type identify the functionality and attributes that you need. For instance for VARCHAR2
a. min length - the minimum length to generate
b. max length - the maximum length
c. prefix - a prefix for the generated data; e.g. for an address field you might want a 'add1' prefix
d. suffix - a suffix for the generated data; see prefix
e. whether to generate NULLs
3. For NUMBER you will probably want at least precision and scale but might want minimum and maximum values or even min/max precision,
min/max scale.
4. store the attribute combinations in Oracle tables
5. build functionality for each data type that can create the range and type of data that you need. These functions should take parameters that can be used to control the attributes and the amount of data generated.
6. At the table level you will need business rules that control how the different columns of the table relate to each other. For example, for ADDRESS information your business rule might be that ADDRESS1, CITY, STATE, ZIP are required and ADDRESS2 is optional.
7. Add table-level processes, driven by the saved metadata, that can generate data at the record level by leveraging the data type functionality you have built previously.
8. Then add the metadata, business rules and functionality to control the TABLE-TO-TABLE relationships; that is, the data model. You need the same DETPNO values in the SCOTT.EMP table that exist in the SCOTT.DEPT table.
The second approach I have used more often. I would it call the top-down approach and I use
it when test data is needed for an existing system. The main use case here is to avoid
having to copy production data to QA, TEST or DEV environments.
QA people want to test with data that they are familiar with: names, companies, code values.
I've found they aren't often fond of random character strings for names of things.
The second approach I use for mature systems where there is already plenty of data to choose from.
It involves selecting subsets of data from each of the existing tables and saving that data in a
set of test tables. This data can then be used for regression testing and for automated unit testing of
existing functionality and functionality that is being developed.
QA can use data they are already familiar with and can test the application (GUI?) interface on that
data to see if they get the expected changes.
For each table to be tested (e.g. DEPT) I create two test system tables. A BEFORE table and an EXPECTED table.
1. DEPT_TEST_BEFORE
     This table has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look BEFORE the
     test for that test case is performed.
     CREATE TABLE DEPT_TEST_BEFORE
     TESTCASE NUMBER,
     DEPTNO NUMBER(2),
     DNAME VARCHAR2(14 BYTE),
     LOC VARCHAR2(13 BYTE)
2. DEPT_TEST_EXPECTED
     This table also has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look AFTER the
     test for that test case is performed.
Each of these tables are a mirror image of the actual application table with one new column
added that contains a value representing the TESTCASE_NUMBER.
To create test case #3 identify or create the DEPT records you want to use for test case #3.
Insert these records into DEPT_TEST_BEFORE:
     INSERT INTO DEPT_TEST_BEFORE
     SELECT 3, D.* FROM DEPT D where DEPNO = 20
Insert records for test case #3 into DEPT_TEST_EXPECTED that show the rows as they should
look after test #3 is run. For example, if test #3 creates one new record add all the
records fro the BEFORE data set and add a new one for the new record.
When you want to run TESTCASE_ONE the process is basically (ignore for this illustration that
there is a foreign key betwee DEPT and EMP):
1. delete the records from SCOTT.DEPT that correspond to test case #3 DEPT records.
          DELETE FROM DEPT
          WHERE DEPTNO IN (SELECT DEPTNO FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3);
2. insert the test data set records for SCOTT.DEPT for test case #3.
          INSERT INTO DEPT
          SELECT DEPTNO, DNAME, LOC FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3;
3 perform the test.
4. compare the actual results with the expected results.
     This is done by a function that compares the records in DEPT with the records
     in DEPT_TEST_EXPECTED for test #3.
     I usually store these results in yet another table or just report them out.
5. Report out the differences.
This second approach uses data the users (QA) are already familiar with, is scaleable and
is easy to add new data that meets business requirements.
It is also easy to automatically generate the necessary tables and test setup/breakdown
using a table-driven metadata approach. Adding a new test table is as easy as calling
a stored procedure; the procedure can generate the DDL or create the actual tables needed
for the BEFORE and AFTER snapshots.
The main disadvantage is that existing data will almost never cover the corner cases.
But you can add data for these. By corner cases I mean data that defines the limits
for a data type: a VARCHAR2(30) name field should have at least one test record that
has a name that is 30 characters long.
Which of these approaches makes the most sense for you?

How to generate idoc PODRCH02 using out put type

Hi All,
I need to generate outbound idoc PORDCH02 and message type PORDCH using out put types (messages).But i unable to generated this idoc using message type. System is giving error as *No recipient found for message type PORDCH in the ALE model*
To do this , i have done the following steps.
1. In BD64 i have configure the business object BUS2012, using add bapi. ( In cust.distn model it doesn't allowing the message type. so i have given BAPI )
2. In partner profile (WE20), for sending logical sytems
i have configure the message type in outbound parametes.
3. In NACE for out put type NEU i have given medium as Distribution (ALE), Partner function as LS
Could you please help me out , what are the necessary steps i need to take care and what are the steps i missed out.
Thanks and regards
Praveen

In distribution model, you have to configure both the sending system and receiving system. The Tcode of Distribution model is BD64.

How to generate Outbound Test IDOC ?

Similar Messages

Maybe you are looking for