CREMAS / ADRMAS Outbound Idoc Example

Hi All,
I need to send Vendor Data to SAP PI (This will be a daily Job, not every time vendor's data is change so no change pointers involved). I created a program to select vendors based on some criteria and then called transaction BD14. Everything ok so far but the Analyst told me they want to use CREMDM instead of CREMAS because CREMDM contains address segment that might be a requirement in the future (this is understandable...).
I searched SDN and found out that BD14 does not support CREMDM. I also read that I can extend CREMAS with Address segment. Now I have a couple of questions:
- If I extend the IDOC, I won't be able to use BD14 anymore right? I mean, I'll need to complete the segments myself and then use MASTER_IDOC_DISTRIBUTE?
- I also read there are no BD* transactions for CREMDM but there is transaction MDMV. Can I use this transaction to select Logical System as I can do it in BD14?
- I also read about Idoc Serialization. I have Serialization Group (ADRMAS / CREMAS). Can I use it for my purposes?
Any help would be appreciated.
Thanks & Regards,
Ernesto.

Hello,
I just created partner profile for dev. system clients. i.e., client 010 to 020 using BD64 for CREMDM message type.
When I run MDMV t-code it automatically picked up my receiver system at per distribution model setting.
You can also try submit report RMDMIDVE (t-code MDMV) through your custom report.
Regards,
Sameer

Similar Messages

Vendor Master record change using CREMAS & ADRMAS

Hi ,
I have one problem with CREMAS & ADRMAS idocs, i am using one custom program(it is using IDOC) to change/ create the vendor master record ,While i try to change some filed of one particular vendor using the idoc,it delete all other fileds related to the vendor like phone no, street mail id ..etc
Can any one help me to slove this problem.
Advance thanx .
With warm regards.
Elango..

Hi,
   When you are updating vendor information pass the
   existing information that is already present for
   vendorlike street from lFA1 table and fill other
   fields that need to be updated.
   IDOC may be replacing the existing fileds values
   will space as they are not populated in IDOC.
Regards
Amole

Custom error in outbound idoc FIDCC1

Hi all,
I am generating outbounds idocs for FI documents and i need to put some of them in error. I need the FI Document created and the idoc in error so that i can reprocess it later. To do that i am using the User Exit EXIT_SAPLF050_007
Enhancement - F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(MESSAGE_TYPE) LIKE EDMSG-MSGTYP
*" TABLES
*" IDOC_DATA STRUCTURE EDIDD
*" CHANGING
*" VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
*" VALUE(DISTRIBUTION) LIKE BOOLE STRUCTURE BOOLE
*" OPTIONAL
IDOC_CONTROL-status = '26'.
The problem is that in the UserExit i set the Idoc Status to some value diferent than 3 (Data passed to port OK) but finally the idoc is created with the status 3.
Does anybody know how to change the idoc status in the creation from 3 to for example 26 or 27? ( an error idoc status ).
thanks!!

Hi,
In the partner profile, set the option as Collect IDOC's option.
Create a background job in which the first step of that should be your custom program and the second step is RSEOUT00 program.
In your custom program, validate the idoc if you feel your idoc is correct then leave it like that and if you feel there is some problem in the idoc then flag that error idoc for deletion that means that error idoc will not be sent to your partner.
For flagging an outbound idoc to deletion is nothing setting the idoc status to 31. This you can do with the program RC1_IDOC_SET_STATUS.
Thanks,
Mahesh.

XI generates own IDOC numbers in outbound IDOC

Hello, The scenario we have is R/3 --> XI --> 3'rd party (via IDOC rcvr adapter) AND then SYSTAT back from the 3'rd party to R/3 via XI.
Example: R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number).
Accordingly, the 3'rd party responds back with a status IDOC, SYSTAT, containing IDOC 200 in the E1STATS ==>DOCNUM field.
This is now a problem since if XI submits the SYSTAT as received from the 3'rd party, it has 200 in the DOCNUM field and this fails in R/3 since there is no original IDOC with number 200.
This can be solved if XI is able to pass the original number 100 through to the 3'rd party system (since then when the 3'rd party responds it will send a SYSTAT with IDOCNUM as 100 back, which will setup correctly in R/3).
I have gone through the other pertinent posts and none of them have this specific problem / offer a solution. I'm hoping I have missed something as this seems to be a pretty basic requirement.
Thank you for the time.
Some additional details...
- 3'rd party is non SAP.
- In the IDOC rcvr adapter we have flags 'Apply Control Record Values from Payload', 'Take Sender from Payload' and 'Take Receiver from Payload' fields checked.
- We have not checked any flags in the Rcvr Agreement.
- We are not using BPM and do not have a way to correlate the inbound 200 with the original 100 that went out.

Bhishma,
Just clarrification for you...when you said..
"R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
Let us know the result.
Nilesh

Validation on outbound idoc

Hello team
I have the below requirement now. please check and suggest me
1. i am sending outbound MATMAS05 idoc from SAP system. but i want to do few validations on the data of idoc (for example i will check the value of plant data with some other value of the table). if my checking is success then only i need to create outbound idoc and send it to downstream systems.
So now i want to know where i need to write the code which performs the validations against the data before creating/posting of idoc.
Please suggest me.
Regards
Raj

Vinod
Dont mine of asking little more clarification. you mean to say go MM01 and find out the package (ie MGA) and then goto SMOD and findout the exits right.
But when check in this way, i didnt find the enhancment MGV00001 you have provided.
please tell me the procedure to check in a detail way. i want to know how can we check for the related enhancments for any idoc type. please tell me to check for MATMAS05 as an example, i will use the same techinque for any idoc type.
Regards
Raj

Outbound Idocs in 03 status

How do these get processed to be sent to the external system...in this case XI. They are setup as "Transfer idoc Immediately" but I am not sure what to execute to get them to process....message type WP_PLU....Thank-You

Test: Outbound Processing from IDoc
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 make sure that this is the case 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, via the application or the test tool), the IDoc is only generated in the R/3 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
Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
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.
Thanks,

IDoc to XI u0096 Outbound IDoc

hi Experts,
Please let me know how to post IDOC to XI in R/3 Sender System?
Please help
Sourabh

Hi,
WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.
What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.
Suppoce u have to post the production order details then u have to go to CO02 TC code there u have to give the production order details and release the IDOC .
Before release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.
Chech the ALE settings.
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

Urgent --- How to resend an outbound IDoc which is in status 03

Hi Experts,
I've a rquirement to resend an outbound IDoc which is in status 03. I don't want to use BD87 or WE19 to reprocess.
Please provide me some FM or some technique by which I may use in a Z-program to accomplish the above requirement.
Even if IDoc no is changed....that won't cause any problem....i just need to resend the IDoc.
Thnx in advance
Rudresh
Mumbai

Test: Outbound Processing from IDoc
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 make sure that this is the case 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, via the application or the test tool), the IDoc is only generated in the R/3 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
Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
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.

Trigger outbound idoc for F110 program

Hi Experts,
I am new to idocs, please anybody can help
regarding to create outbound idocs when i run F110 program.
when i run F110 with parametrs company code and payment method, automatically it will create idoc and send it to partner system.
i think i have to use pexr2002 and message type payext.
please help me on my request, it is very urgent work.
Regards,
Venkata

Follow the steps:
1) Do relevant Settings for payment program ( FBZP).
2) Example: For the house bank you have to set the EDI partner profile no. and the EDI partner profile and EDI compatible payments methods.you have to attach the payment methods to the house bank EDI profile. And check generate
EDI immediately in we20.
3) Create the partner profile for bank with message type " PAYEXT", partner
type " B". AND THE IDOC BASIC TYPE AS " pexr2002".
4) when you run the payment, the IDOC will be generated.
REfer to:
http://help.sap.com/bp_bblibrary/500/Documentation/W25_BB_ConfigGuide_EN_US.doc
http://www.sap.com/usa/solutions/business-suite/erp/financials/pdf/BWP_%20SAP_In-House_Cash.pdf
Reddy

Nace config for DESADV type Outbound IDOC of type 856 at Delivery level

Hi All,
My requirment is to trigger Outbound IDOC of type 856 at delivery level & not at shippment level & one line per ASN.
How can I configure this in NACE?
Thanks in Advance.

Hi Raj,
For example, you can use the ASN0 output condition as a SAP standard. please go to NACE t-code and select the V2 for shipping and
go into the ASN0 output type configuration. in the that sceen;
1)give access sequence regarding of your requirment, for general data.
2)in the default values tab, Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH.
3 go in to the processing routines for the output type and Programcan be configured as RSNASTED, Form Routine as ALE_PROCESSING. But these are SAP Standard and they are changing your requirements with the ABAP tricks.
After the output type configuration, go in to the output condition from nace t-code same. And create condition for ASN0 output type. when creating your conditions regarding of your acces sequence, you should Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH like output type configuration,too.
I hope these will very useful to meet your requirements. But additionally, you should also contact with a ABAPER for the program and routines.
Regards,

Creating Outbound IDOC

Hi All,
I have a program which generates an outbound idoc. My basic type is PRICAT. My problem is i cannot make the child segments. The segments created are all parent segments.
How will i make the child segments? what fields do i have to fill up to it child segment?
Any response will be gladly appreciated!
Thanks in advance!
jim

Hi Jim,
for correct child segments you have to provide some fields of structure EDIDD.
Important for the hierarchy relationship are the
following fields:
PSGNUM -> Number of parent segment
HLEVEL -> Hierarchy level
Example:
Definition of MATMAS01
Parent segment E1MARAM
--> Child Segment E1MAKTM(Child of E1MARAM)
--> Child segment E1MARCM(Child of E1MARAM)
> Child Segment E1MARDM(Child of E1MARCM)
....... and so on
==> In EDIDD structure:
DOCNUM | SEGNUM | SEGNAM | PSGNUM | HLEVEL
000001 | 000001 | E1MARAM | 000000 | 02
000001 | 000002 | E1MAKTM | 000001 | 03
000001 | 000003 | E1MARCM | 000001 | 03
000001 | 000004 | E1MARDM | 000003 | 04
....... and so on
When you are creating the segments,you are responsible
for the correct sequence of segments.
With best regards
Ivan

Outbound Idoc issue

Hi,
We have migrated from 4.6B to ECC 5.0. While posting an outbound idoc to a middleware, its failing in the middleware. This is because few segements of the basic type has been modified by SAP ( fields have been added ).
This was running properly in 4.6B. So basically this error is due to the additional fields which cannot be recognised by the middleware.
Now, if i need to send the version similar to that of 4.6B, without those additional fields, how do i go about it?
Thanks,
Raj.

Hi Rajgopal,
use the latest version idoc type(basic type)for example for orders we have orders01,orders02,orders03,orders04,orders05,it's better to use the latest version.
else
u have to extend the stanard idoc with those additonal fields and write the code in user exit to populate them.
Regards,
nagaraj

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,

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

Sales Order Outbound IDOC - Restricting Items being created with a Segment

Hi,
I have a requirement to restrict segments being created for Items (Child) in Sales Order Outbound IDOC based on conditions in the Items (Parent & Child). Can you please suggest me a suitable solution?
Basic Type: ORDERS05, Message Type: ORDRSP. What is the IDOC Function Module to be used to create Outbound IDOC for Sales Order?
Appreciate Your Help.
Thanks,
Kannan
Edited by: Kannan SA on Jan 3, 2008 3:03 PM

Hi,
if the segments are mandatory then you can't trigger the idoc without those segments.
Otherwise, you can read the segment and clear all the data in it, the segment will not be attached to the outbound idoc.
Where to do it? Search the CALL CUSTOMER-FUNCTION '002' for the outbound idoc for example IDOC_OUTPUT_INVOICE for Invocing.
Regards,
Baburaj

CREMAS / ADRMAS Outbound Idoc Example

Similar Messages

Maybe you are looking for