Doubt on IDoc Config

Hi xperts,
May i request for clarifications on points to consider for configuring inbound and outbound idoc?
I have read couple of blogs for reference yet posting to get more clarification
what all configs required in R3 to post idoc to xi and vice versa? and in this case what basic points to be considered...something like logical sys name to be same as business syste etc? pls share .

Hi,
Need to follow like this
SAP R/3
1. Create a partner profile using tcode we20 (need to maintain an entry in tables based on partner type)
2. Create a RFC destination of Type 3 pointing to XI
3. Create a port and assign RFC destination
4. Create an entry of outbound message type and assign port..
PI
1. Create a RFC destination of type of 3 pointing to R/3
2. Create a port using idx1...and assign above RFC destination name
in order to receive the data from R/3 business system/service created for R/3 should contain logical system name as partner profile name...created in R/3
Hope this clears all your queries...
Regards
Rajesh

Similar Messages

Doubt on IDOC TO IDOC communication

Hi Experts,
I have a doubt on IDOC to IDOC communication:
Plz clarify it
1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
2.what is the advantage of passing like this through XI compared to ABAP?
                       Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

Hi,
See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
You can go with ALE also here.
Situations to go to XI.
1) when you have the Different field mappings
2) When you are having the multiple receivers
3) when you are dealing with Bundling & Transformations
Reward Ponts If Helpful
Regards
Giri

Doubt on IDOC communication

Hi Experts,
                  I have a doubt on IDOC to IDOC communication:
Plz clarify it
                    1. what is the need of passing same IDOC from one system to other system    through XI while communicating between two systems,it can be done by using ABAP also ?
                     2.what is the advantage of passing like this through XI compared to ABAP?
               Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

The need for an XI to transfer IDOC from one system to another sytem : the answer for this comes from the basic of using XI as a middle ware.
1. When you connect IDOC directly to another system without using XI....you are going for P2P connections then this leds to problem in monitoring if the data breaks, you have to login to both systems to check......
2. we have a central monitoring tool for check this iterface..
3. You can build a message orchestration using the BPM if required for this IDOC...
4. You can have full control in the IDOC processing...i mean do you want to send ot not and so on.
Beofre XI or typical connection between 2 SAP Systems were using IDOC directly but they are P2P connectinons,,,no control, no monitoring....NO orcheatreation...etc.....

Receiver IDOC Config

Hi there
Is there some documentation that could help me find a technical issue I have with my idoc config? Im looking for a step by step showing where I must check for all the config. like in sm59 and idx1, but explaining what everything is used for. I seem to get idoc status 51 if I try and reprocess some old idocs that have worked before so I guess there is something wrong with the technical side.
Thanx,
Jan

Hello again,
I have 2 systems, XID150 - sender and ECD999 receiver.
In SM59 in ECD999 I have a ABAP Connection, XIDCLNT150 pointing to XI which is type 3. I tested it and it works.
In We21 in ECD999 I have a Transactional RFC SAPXID with the RFC Destination XIDCLNT150.
In We20 in ECD999 I have a profile under Type KU, B006 and in the Inbound parameters I have the idoc WALREQ01 which im using.
In We19 I create the idoc and Start inbound processing and it gives me: Partner profile found with status green.
If I go to We02 and look at the Idoc which was successful in we19 it shows status 51 as I mentioned before.
On the XI side:
In sm59, I have ECDCLNT999 pointing to my receiver system. Connection tested and works.
In idx1 I have SAPECD as a port name and it points to client 999 on RFC ECDCLNT999. with Partner Nr B006 and Type KU.
and in idx2 I have the IDOC loaded there. So everything seems to be working fine except for we02.

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Doubt in IDOC

Hi everyone,
Am beginner of ale idoc can anyone clear my doubts.
1)In an idoc How to get a value for a particular field in a segment which system is not generating.But a field exist for it.
For Eg.
I want a field(TLCCAT) in the idoc(TPSLOC).But it is not generating any value for it.
But in idoc(TPSDLS) it is giving value for it.
Like this i need some more fields to be filled.
how to get those fields filled.
2)Can we send TPSSHT as outbound, as if i know we cant send it as outbound.If am wrong can u correct me and tell me the way to send it as outbound.
3)How to use idoc(SYSTAT) for sending status and error messages as outbound.
Thanks in advance,
Sakthi

Dhanush,
I believe records means u refer here to each IDOC messages.
For Question 1:
- See No IDOC's will be created in Integration Server. IDOC's will be created only when it got posted in R/3 System.
- I can say based on your scenario design 100 IDOC's structure messages are created but not IDOC's in Integration Server.
- You can handle the scenario in two ways upto my knoweldge.
Split the 100 records and send each record to R/3 system.(You need BPM for this)
Export the IDOC change the occurrence of IDOC to 0..unbounded and in the mapping logic map records to IDOC. Hence if there are 100 records 100 IDOC Message structure will be created. Finally when u post the IDOC in target system 100 IDOC's are created.
For Question 2:
- From R/3 side 100 IDOC's will be created in order to get 100 records.
- Here also you can design scenario in 2 ways..
Use BPM and collect 100 IDOC's and map to target structure so that 100 Records are created.
Collect 100 IDOC's in file system by creating File port[I think u might knew the blog] and finally do file to file scenario.
Hope it helps!!!
-raj.

Doubt in Idoc user exit..............

Hi All,
 i have written the user exit for Sales Order subscreen tab called additional data2 , this tab is provided by sap for developer can write their own user exit coding.
 my doubt is whenever PO comes as an Inbound IDOC i need to pass the value from segment to my user exit fields.
 where can i find the inbound idoc user exit for SO .
 Thanks in advance,
Regards,
Saravanan.

Look at enhancement VEDA0001. It has got quite a few user exits you can use. You will also need to enhance the IDOC for the additional fields you have added on your screen.
Cheers,
Sanjeev

Doubt in IDOC's - Process Codes

Hi,
Currently i am working on an object related to IDOC generation. This is my first object in IDOC's. I am doing it from the scratch including creation of segments, IDOC type, message type, process codes...
In this process, I am developing a function module that should be assigned to the process code. My doubt here is, is there any standard interface to the function module that we have to assign to the process code?
I am also giving the flow which i will be using in developing the Function module. Please go through it and kindly let me know if I am doing it in the right way or not?
1. Extract data from data base based on the entry in NAST
2. Filling IDOC DATA & Control records
3. Calling the FM MASTER_IDOC_DISTRIBUTE to generate the IDOC
Please suggest me whether i am doing it in the correct way or not?
Thanks in Advance,
Best Regards,
Phani

Hi,
For outbound u need to attach ur FM to the process code in WE41 tcode..I think u r using message control method for ur requirement.please look at the configurations for outbound using message control method.we use we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
Regards,
Nagaraj

Doubt on Idoc adapter parameters

Hi ,
      I need one more clarification on Idoc adapter parameters :
1.while configuring for IDOC adapter in communication channel , we have an option
called "APPLY CONTROL RECORD VALUES FROM PAYLOAD" doubt arises here
what actually this mean,and if this check box is ticked what values will be taken from payload and where will be they applied?
                       Plz clarify answers will be definetely rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi vinod reddy ,
If u want to add values to the control record , u have to select the APPLY CONTROL RECORD VALUES FROM PAYLOAD checkbox in the communication channel. When a new communication channel of type IDoc is created, the flag is set by default. If the flag is not set, the
settings comply with XI 2.0
This following websites clearly clarifies u'r doubt with detailed description with fields :
Fields of the IDoc Control Record
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Configuring the Receiver IDoc Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
How to.......Sample IDoc XI Scenarios
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
cheers!
gyanaraj
****Pls reward points if u find this helpful

Doubt about idoc meta data

hi this is seshagiri. i have one doubt while in sending idoc to xi server in the idoc to file scenario, can we do with out configuring metadata in idx2.
if can we do means wat is the procedure.
please clarify me
thans & regards
giri

Hi Sesha giri,
    If you are dealing with Idoc to File Scenario...you need to create
1) RFC Destination in R/3 pointing to XI.
2) Ports in R/3.
3) PartnerProfiles
   we need to send idoc from R/3...so we have to do ALE configuration.
   Please see the below link for more details.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Hope I am clear.
Please let me know if you have any queries...!
Thanks and Regards,
Chandu

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Doubt in Idoc To File Scenario

Hi Experts,
I didn't created any scenario in XI, i have created an idoc in R/3 and i have send it to XI system using tcode we19, i could able to see the idoc in XI system in tcode IDX5, when i double click on the xml message in IDX5, i am getting the follwoing error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors. Please correct me if iam wrong. Kindly suggest me what might be the problem for getting this sort of error.
U'r help will be greatly appreciated.
Thanks & Regards,
Venkat.

Hi Venkat,
>> Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors.
If you check in the inbound message payload u can see the xml message with out errors. But the error is due to non availability of receiver determination path to send the xml message to the desired target system from XI.
So create all the design objects in IR and configuration objects in ID and then try to trigger idoc from r/3 and check the mapping flow and check whether the desired file is created in the target folder.
For more info refer the below blogs:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken]
Regards,
Prasanthi.

Doubt in idoc 2 file scenario

Hi,
I want to create idoc 2 file scenario with out any Transformation.
In that case how/what to create Data type for receiver.
I want to receive the same idoc in the receiver folder/Directory (like XML file) with out any transformation.
Thanks
Ruban

Hi,
For this scenario you need to create the Data type structures as similar to IDOC type and just have to transfer to file without FCC.
It will transfer the IDOC data as it is in XML format
refer
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
(Just avoid using FCC conversions on receiver file adapter in above scenarios)
Thanks
Swarup
Edited by: Swarup Sawant on Mar 24, 2008 6:15 PM

IDOC Config Problem... Transaction BDFG giving error mesage..

Hi ,
Transaction BDFG, If i click on the change button i get an error as Message (Idoc Message Name) has not been generated,Furthur Processing is not problem. Reason being in Table EDBG the Generated field for Idoc Message is blank.
How can i get in generated.. Do help..

Hi ,
Could you please check the below links.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/00/a814b5d05b11d6b2ca00508b6b8b11/content.htm
Regards,
Ratheesh BS

Doubt on IDoc and BAPI

Hi Experts,
I doing Idoc to file scenario, my question is when we go ahead to use IDOC or BAPI. please give me some basic understanding of when and how you use IDoc?
When to use BAPI?
Please provide some links of document
Regards,
Venkatesh

Hi,
when u want asynchronous communication u have to use IDOCS
when u want to use synchrnous communciation and want to communicate external langauges u have to use BAPIS
For File to IDOC,
in R/3
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using we21
4.create partner profile using we20
in xi
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using IDX!
for IDOC to FIle
R/3 side
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using we21
4.create partner profile using we20
5.distribute busynessmodel using bd64
for xi side
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using IDX!
4.create partner profile using we20
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Edited by: krishnachitanya siddavattam on Mar 7, 2008 5:37 AM

Doubt on IDoc Config

Similar Messages

Maybe you are looking for