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

Similar Messages

Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

Hi Team,
I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
which creates a BDOC and is passed to R/3 system through an Inbound IDOC which triggers the Outbound IDOC to PI system. So far good.
The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
Thanks,
Imran

Hi,
Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
Hope this helps,
Karuna.

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

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
 Enter segment name and click on Create.
 The name of the segment type must start with Z1 , and have a maximum of eight characters.
 Enter description and enter the relevant field names and data elements.
 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
 Save the segment and enter Person Responsible and Processing Person .
 Go to Edit and Set Release.
 Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
 Enter segment name (starting with Z), click on Basic Type and then Create.
 Create as new, enter Person Responsible and Processing Person and enter description.
 On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
 Complete relevant fields in the Maintain Attributes screen:
 From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
 The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
 The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
 Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
 When IDOC created return to initial screen. Go to Edit and Set Release.
 Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
 Display/Change and click on New Entries
 Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
 Display/Change and then click on New Entries.
 Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
 WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
 BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
 Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
 The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
 c_SEGMENT_type1.
 The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
 The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
 NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
 The ALE Layer handles the sending of the IDOC to the receiving system.
 Error Handling (see Step 7b).
 Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
 Declare a structure of type MCMAILOBJ for sending instructions.
 Enter values for the internal table based on structure MCMAILOBJ
 For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
 Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
 MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
 Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
 Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
 Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
 Enter your message type and execute.
 Status should be green, double click on one of the Idocs you have created to view its contents.
 If a problem has occurred click on Status which will give you a description of the error.
 Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
 Click on each individual segment and view the content to check that the correct data has been read.
 If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
rewards if useful
regards,
nazeer

There is large time differnce in Outbound IDoc's for Interest Run posting

Hi Experts,
When i posting Interest Run (T.code : FINT) i am executing for a range of Customers(For 4500 Customers)
using Background Job it took nearly 3 days to execute the job in Production and i found that there is
no Partner Profile in WE20,IDoc's went in Error.Until this its fine.
The major problem is there are group of 100 idoc's created in no time span and it took 4 hrs time gap to create
another idoc 100 more idoc's.
In between these 2 bunch of idoc's another 700 idoc's created for different message types.
Can you please let me know why there is that much time gap for the same message type for Interest Run.
Thanks in Advance.
Regards,
Sudhakar Reddy Allam.

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

Vendor Outbound IDoc and Unblock Indicator...

Hi All,
I am using an outbound IDoc to pass on the information of vendor master to a legacy system via PI. Basic type I am using for the same is CREMAS05.
Now, when I am unblocking a vendor via XK05 and when I am changing the data of vendor, I am not able to make a difference between these 2 scenarios.
If vendor data is changed, I need to send the legacy system an action flag as 'C'; if vendor is unblocked, I need to send the legacy system an action flag as 'U'.
So, could somebody please let me know how can I differentiate based on IDoc data if vendor is changed or is unblocked.
Any suggestions are really appreciated.
Thanks in advance.
Regards,
Richa

Thanks for answer.
but, Serialization process will have two message type each one for Vednor mater and Addres and seriallise the Idoc i.e. two Outbound Idoc will be created.
But I want ONLY I Idoc to be created which should have Vendor Master data and also address Data.
~Pramod

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,

Regarding the Outbound IDOC process

Hi Experts,
Please answers the following questions which i have some doubts in Outbound Process.
1) Which program is resposible to fill the segments of IDOC(Std IDoc) in case of Outbound IDOC Process with message control , Is it FM in Process code or any other FM based on message type( Std Msg)?.
2) Where we need to code or search the exit in Case of extension of basic IDOC type with and without message control?
3)Which prog is responsible to fill the IDOC in case of outbound process without message control but using std basic IDOC.
Regards,
Kali Pramod

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

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

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc TYPE edidc-docnum.
DATA i_edidd TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
 CLEAR i_msgs[].
 CALL FUNCTION 'WFMC_PROTOCOL_GET'
 EXPORTING
 cps_nast = wa_nast
 tables
 messages = i_msgs
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
 IF wa_msgs-msgv1 IS INITIAL.
 CONTINUE.
 ENDIF.
 v_idoc = wa_msgs-msgv1.
 CLEAR i_edidd[].
 CLEAR wa_idoc_ctrl.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 document_number = v_idoc
 IMPORTING
 IDOC_CONTROL = wa_idoc_ctrl
* NUMBER_OF_DATA_RECORDS =
* NUMBER_OF_STATUS_RECORDS =
 TABLES
* INT_EDIDS =
 INT_EDIDD = i_edidd
 EXCEPTIONS
* DOCUMENT_NOT_EXIST = 1
* DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
 CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
 EXPORTING
 object = wa_nast
 control_record_in = wa_idoc_ctrl
* IMPORTING
* OBJECT_TYPE =
* CONTROL_RECORD_OUT =
 tables
 int_edidd = i_edidd
* EXCEPTIONS
* ERROR_MESSAGE_RECEIVED = 1
* DATA_NOT_RELEVANT_FOR_SENDING = 2
* OTHERS = 3
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 COMMIT WORK.
 ENDLOOP.
ENDLOOP.

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

Outbound IDOC WPDTAX not getting generated

Hi
I am not able to generate outbound IDOC WPDTAX through WPMA transaction.
We are using TAXUSJ as the tax procedure.
Tax Condition type UTXJ and JR1 has been maintained in the system.
On looking at the code against WPMA ,
POS_TAX_GET is called to calculate taxes.
It does not have a fetch against all the condtion tables for tax.
The above condition has been maintained in table A053.While the above program fetches data against only A003.
Can somebody help?
Regards,
Amit.

Hi Amit,
For TAXUSJ, the conditions maintained are time dependent conditions.
However , IDoc type WPDTAX01 does not support time dependent conditions.
Only time independent conditions will be transferred with the help of Idoc type WPDTAX01.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/3f/81e33bfa5d11d38d1f080009d10d9a/frameset.htm
Regards,
Lisa

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

IDoc to XI u0096 Outbound IDoc

Similar Messages

Maybe you are looking for