Call Master_idoc_distribute for collective outbound idocs

Hi All,
I want to process outbound idocs (4 idocs collectively) using master_idoc_distribute FM. I am calling master_idoc_distribute inside a FM and assigned it to process code outbound. It is working for one idoc but not for 4 idocs.
How can i call the master_idoc_distribute for sending out 4 idocs one at a time.
Thanks

Ok. I guess the requirement was wrongly typed. Ok here is the requirement.
I basically want to take a collective idoc in R/3 and cal master_idoc_distribute to create and send idocs. This is my collective idoc structure.
EDIDC
--+ E1STZUM
--+ E1STZUM
where 'E1STZUM' repeats for each idocs. In the above structure, there are two idocs in one idoc which is a collective idoc. So i want to write a logic to take the first segment E1STZUM and call master_idoc_distribute and then call the second segment E1STZUM and call master_idoc_distribute FM again and so on depends on how many segments. How can i write a logic to loop at idoc_data and call FM master_idoc_distribute. I am not a core ABAP programer. So pls do send me sample code with comments if possible.
Thanks a lot.

Similar Messages

How configure a Logical System (XI) as receiver for an Outbound Idoc?

Hi all,
How can I configure a Logical System (XI) as receiver for an Outbound Idoc?
Points will be given,
Regards,
Daniela

hi,
it all depends on what kind of document you need to send to XI
if you want to send some logistic documents (like orders, deliveries etc)
have a look at my book - where you will find step by step guides
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
then you will undestand where to change to get it send via LS
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Configure background job for collective outbound delivery processing

Hello Gurus,
I want to Create a background job to be executed during off-peak hours for collective outbound delivery processing. will you please give me step-by-step configuration ?
thanks very much!

To set up a batch job for delivery creation use SM36 T-code.
Input batch job name say - ZSD_CREATE_DELY_SALES_ORG
Select class = C or B.
Set up by / created by = BATCHADMIN or your id
Program Name = WS_DELIVERY_UPDATE
Varient = (as per your requirement - say for a particular sales area and plant)
Click on "Check" icon and "Save".
Go to the main page, select icon "Schedule a Batch job".
Give detils like daily, weekly or periodic or Immediate.
Enter date and time accordingly. Save it.
Same thing applies for Invoice creation batch job.
Use program name:RSBDCSUB
All other steps remain the same.
Hope this will help you out !
Regards,
Rajesh Banka

Standard program for creating outbound IDoc holding wbs+cost plan

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

FM for ORDERS05 Outbound Idoc.

Hi,
I have to post an idoc of basic type ORDERS05 from a custom program.
I have populated the fields for control header and the data section of the idoc.I tried using the FM IDOC_OUTPUT_ORDERS to post the idoc,but when I went and checked in WE05,there were no idoc created.I don't understand why the idoc's are not been created.Could you help me in knowing how to use the FM IDOC_OUTPUT_ORDERS or if there are any other FM's to post an outbound idoc.
Please reply asap.
Thanks,
Sandeep.

Hi,
There is a exit in the FM IDOC_OUTPUT_ORDERS line no 50... double click on the '001' it will take u to the Function Module EXIT_SAPLEINM_001... there click on the Zprogram ...
The FM has EKKO table fields has a Impirting parameter .
u write a code in that Z include program
u have to call the FM MASTER_IDOC_DISTRIBUTE in the program
which creates the IDOC
Thanks,
Manjunath MS

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear: g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'. "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'. "Direction
* Receiver
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-rcvpor = 'SAPDE2'. "Port
 g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'. "Partner type
g_idoc_control_record-rcvpfc = ''. "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'. "tRFC Port
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'. "Partner type
g_idoc_control_record-sndpfc = ''. "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam = 'E1BPACHE09'.
g_edidd-segnum = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
 exporting
 pi_idoc_control_rec_40 = g_idoc_control_record
* PI_DO_COMMIT = 'X'
* IMPORTING
* PE_IDOC_NUMBER =
* PE_ERROR_PRIOR_TO_APPLICATION =
 tables
 pt_idoc_data_records_40 = g_edidd
 exceptions
 idoc_not_saved = 1
 others = 2.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
 in background task as separate unit
 tables
 idoc_control_rec_40 = g_idoc_control_record
 idoc_data_rec_40 = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
 can anybody tell me the steps how to configure an Outbound IDOC.
 It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
 if not anything else will also do.
 Kindly give me steps in detailed. Since i have never done this. Including
 distribution modle (BD64). in which case it generates the Automatic Partner
 profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
 a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
 b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
 c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

Configuring shipping point as Trigger point for posting outbound idoc

Hello All,
I have a requirement that on saving an Outbound Delivery(VL02N), an Outbound Idoc should be posted...but the condtion for posting the idoc should be its shipping point. I am not sure how to configure shipping point as the trigger point for the idoc.
Please suggest.
Thanks for your co-operation.
Regards
Anand

Hi Anand,
1. Go to transaction: NACE & select application V2 and click on output types.
2. change display <->Change mode.
3. select LAVA and press F6 (to copy Standard output type LAVA to ZLAV).
4. Give ur Z name for the new custom output type.
5. change access sequence from 0005 to 0012(shipping point).
6. Press ENTER and click copy all.
7. Now goto trasaction VV21, give the created output type name. ENTER
8. Maintain entries, shipping point, customer#, Medium as '6' ...etc
Now try VL01N with the given shipping point and check the output ZLAV has been triggered or not?
Let's see, if we miss any configs still!
Keep this as reference:
http://www.erpgenie.com/sapedi/messagecontrol.htm
Reddy

BADI for PO OUTBOUND IDOC

Hello Experts,
Please help me out finding a suitable BADI for T code: ME21N
OUTBOUND IDOC.
Scenario:
I have to populate a "Z" segment while creating an IDOC in ME21N. for this I require a BADI.
I have tried using FM: idoc_output_orders
Form Routine fuellen_idoc_inttab.
but ME21N doesn't execute it at all !!!
I have set my Output Type to EDI with the Valid Settings
when ever i create a PO it creates an IDOC but it doesn't execute FM idoc_output_orders
Thanks in Advance!!!
R

Hi,
Below steps for your reference.
1.M/59 Define Condition Tables
2.M/50 Define Access Sequences
3.NACT Define Message Types
4.Set up fine-tuned control for each message type
5. NACZ Define Message determination shemas
6.NACR Define Condition Records
Regards.
David.

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

ALE settings for MIRO outbound IDOC

PLz tell Output Type, Process Code etc...for MIRO outbound.
for inbound i am using INVOIC01..
Thanks and regards

Hi madan,
u can use the transaction NACE to find out the output type of MIRO.
If u know the function module u can able to find the process code easily.
Since function module names are based on message types.
Regards...
Arun.

Triggering E-mail for failed outbound idoc (Without using workflow)

Hi Experts,
In my secnario Idoc to file, where any failures of Idoc( Inbound/Outbound ) at SAP R/3 side will generate and send Emails to the required group. How to do this without using Work flow. If anybody knws please help me out its very urget.
Regards,
venkatesh

Hi,
Create a Distribution list using SO23 and add Users whom to recieve messages.
Modify your Inbound function module to handle if idoc failed to post by calling the function module: SO_NEW_DOCUMENT_SEND_API1
Reward points if it is helpful.
Ashok

Unable to perform call transfer or call park for an outbound call via SIP Trunk (SKYPE)

We have configured the SIP Trunk & SIP profile and successfull make outbound call through SIP Trunk (SKYPE). However, we are not able to perform call transfer or call park when the call is connected.
The scenario is:
A call to an phone number via SIP trunk, when call established, A perform call-transfer to B. After the call-transfer, the call Drop and Phone B show error code "Temp Fail"
When i select "enable MTP" in SIP trunk, we are able to call transfer and call park. But it limit the number of call session to 1.

You are probably running into some sort of Codec issue. IE, your phone is G.711 and the trunk is G.729. You will need to transcode the call at somepoint.

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

Call Master_idoc_distribute for collective outbound idocs

Similar Messages

Maybe you are looking for