IDOC- XI - IDOC connection issue

I am trying to do a simple IDOC to XI to IDOC scenario. I am trying to pass the IDOC to XI through an RFC destination of type 'H' (HTTP connection to R/3 System). The sending system is an 6.20 system. I think my problem is in setting up this RFC, I believe I have WE20 and WE21 (using XML HTTP port) setup correct. When I try the IDOC, it errors out before getting into XI. I have SICF active (/sap/bc/ and /xi/ ).
Can anyone tell me what step(s) I may be missing? What pathprefix in SM59 should the RFC be pointing to on XI for XI to receive the IDOC? Is there something that needs to be setup on XI to receive this IDOC?
Thanks for any guidance,
Jake

Hi Jacob,
Use u r own RFC destination (SM59)created in Sender system... of type R/3 pointing towards XISERVER...
and also do settings like Creating Port we21, creating partner profiles we20 and also handle BD64 and generate partner profiles(Out bound parameters) ( Repeat this in Receving system -- for inbound parameters in partner profiles)
and in XISERVER create 2 Business systems one for sender and other for receiver and mention the logical systems defined for both sender and receiver...
and also create and RFC destination which points towards Recevind system..
and also maintain IDX1 and also IDX2 in XISERVER...
This should solve u r problem ...
Thanks and Regards,
Sridhar

Similar Messages

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

Generate DELVRY Idoc when Post goods issue is done in SAP

I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
But I didnt understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
1.Manually doing the post goods issue through the transaction VL02N
2. an Inbound Interface (using Idoc) which will do Post goods Issue in SAP
3.Another Interface using BAPI, which will, do post goods issue in SAP
I have to run my outbound interface when the post goods issue is done by all the above three ways. Can any one help me out in this?

You have to configure the output first .
You can use output type LAVA ( avaialble in Std SAP ) .
( Tcode is NACE , Select Application V2 -> Outputtypes ).
( Create condition records suitable to generate an output)
Next is ALE.
Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
Application - V2
Message Type - LAVA
Process Code - DELV.
Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
Cheers.

RFC, IDOC and secure connection

Hello
Does RFC/IDOC support secure connection like HTTPS?
How the data can be encrypted?

Hi,
As Moorthy Quoted RFC will help you,
This will be help you for encrypying the data.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2cce390-0201-0010-5a9f-cca08c75b6ea
/people/kathirvel.balakrishnan2/blog/2006/06/13/sap-php-together-a-simple-base64-encoding-and-decoding
Encrypting data
Regards
Agasthuri Doss

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

SM58 Error For IDOC to IDOC Scenario

Folks,
I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) IDoc adapter inbound channel: Error Error when reading. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
Thanks
Manish

Hi Renjith,
I'm facing the same problem the flow is basically form BW to BO.
When they load the data at sender side the idocs are stucked with error status 2:
"Could not find code page for receiving system" in transaction BD87.
Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
1)Error in RFC connnection
2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
Also are many queues stucked in SMQ1 Outbound.
Please help. Many Thanks.

Options to create IDOC in IDOC Flatfile

Hi,
we have requirement to process a fixed length file and map that structure to a standard IDOC and that IDOC has to be written out as IDOC flat file.I just want to get different opinions to see whether there are any other options other than using ABAP mapping like mentioned in that standard How to Guide IDOC XML to IDOC Flatfile.
My scenario is Fixed length file ->XI->IDOC Flatfile-->SAP(through File port with RSEINB00 Report)
I know there is module available in PI7.1,but we are still in PI7.0 with SP18 and no plans to up grage yet.
In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC and then use the ABAP mapping to convert IDOC XML to IDOC Flatfile.like two steps.
so I am thinking to avoid BPM,ABAP mapping and to see different options to create an IDOC flat file and the receiving SAP system can read the IDOC flatfile using standard File port.Receiving SAP is is very low version(I think 3.0) which is not supporting IDOC adapter communication from XI.
please suggest different options to get IDOC Flatfile or even directly sending IDOC (with ALE connection) that has been created after the mapping from ffixed length flatfile to standard IDOC.
Thank you in adavance.
Babu

> In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC
Hi Babu,
When PI reads the file from source system, it will read all the data into Single XML file and in message mapping just do 1:N mapping to create multiple IDOCs from single XML. You dont have to use BPM for this requirement.
You wait for better solution from other for 2nd part of your requirement i.e IDOC-XML to IDOC Flat file conversion.
Have a great day.
Cheers,
Jag

IDoc to IDOC, Message Mapping settings

Hi!
I am going to implement IDoc to IDOC scenario.
The IDOC should be send from SAP ECC 6.0 system, client 100 to the same system in client 200 via SAP XI.
I have chosen the message type MATMAS05.
Questions
- What is the minimal message scenario (MATMAS:MATMAS05 to MATMAS.MATMAS05) in message mapping?
- when I change some mapping attributes do I need to activate the other related objects (e.g. Interface Mapping, etc.)?
My problem is that the IDOC will be received in SAP XI, but has the following error:
Error: must node 'E1MARAM' failed in structue MATMAS05
How can i correct this error?
Thank you very much!
regards
Holger

Hi Holger,
> * What is the minimal message scenario (MATMAS:MATMAS05 to MATMAS.MATMAS05) in message >mapping?
No Mapping at all or a direct 1:1 connection of all corresponding fields.
> * when I change some mapping attributes do I need to activate the other related objects (e.g. Interface >Mapping, etc.)?
You only have to activate objects that you changed - so no.
From the error I guess that a node in the target structure is not created although the idoc-definition states it as mandatory.
Do you really need the mapping? Does the incoming IDoc also miss the Node?

IDoc to IDOC, settings

Hi!
I would like to implement IDoc to IDoc scenario.
I have one ECC 6.0 system with 2 clients and SAP XI system.
The problem is that the the message type MATMAS does not exist in XI system.
Furthermore I give the following error when I try to load metadata in tcode IDX2:
Basic type 'MATMAS02' is unknown
Message no. EA224
I already created Ports in tcode IDX1, defined the RFC connections
Can some one give me exactly the steps for business systems and XI to execute?
What I already have done:
1) Sender SAP ECC 6.0 (SID:ERB, client 100))
WE21: Creation of port SAPERP with RFC destination XI_SYSTEM
WE20: Creation of Partner LS according to logical names:
EC6CLNT100 (Outbound parameters: MATMAS and SYNCH)
EC6CLNT200
PIBCLNT100
2) XI System (SID:PIB, client 100)
WE21: Which Ports should I create here?
WE20 : Which partner LS should I create here and with which outbound/inbound parameters?
3) Receiver system SAP ECC 6.0 (SID:ERB, client 200))
WE21 Which Ports should I create here? ()
WE20 Which partner LS should I create here and with which outbound/inbound parameters?
It will be great to get some information.
Thank you very much!
regards
Holger

Hi,
Are some name conventions for the ports?
it should be SAP<System id>_<clent_no> in XI system. Transaction : IDX1
Other questions
What is the succesful condition/steps to see the meta data in IDX2 of SAP XI system?
If you have maintaned ports and RFC destiantion in XI for R3, metadat willl be loaded automatically in first run of your interface.
Do I need to create logical systems of both business systems in SAP XI?
Yes you need to create two business systems for each client.
Regards,
sreenivas.

Error in iDoc to iDoc scenario

Hi,
Am facing an issue in iDoc to iDoc scenario....
There is no problem in outbound. But in SXMB_MONI, in the Sender service column the Receiver Business Service is getting displayed.And the Receiver Service is empty.
I think the problem is in IR configuration. In IR how should i configure Message Interface?
What might be the problem?
Is there any different configuration required for iDoc to iDoc scenario.
Thanks,
RPN

Hi,
you could use an IDoc as Message Interface and if don't have a mapping you don't even need the Integration Repository:
How to send any data (even binary) through XI, without using the Integration Repository
Regards
Patrick

B2B- IDOC 2 IDOC

Hi all,
We are building PI 7.1 from scratch. I have few doubts about it
My client has ECC 6.0 and installing PI 7.1 which able to receive and send IDOC's from it's customers (they also running ECC), so basically it is B2B IDOC 2 IDOC scenario. Can somebody tell me how to setup the Technical systems and Business Systems for this cross company scenario( I never worked on cross company scenario before).
Thanks in Advance,
Rishik.

SOURCE SIDE CONFIGURATION: Client ECC (SAP R/3)
1. Create RFC Destination: To create a RFC destination use transaction SM59.
2. Create Port: To create a port uses the transaction WE21
3. Now Go to Transaction Code SALE and create Logical System.
4.Creation of Partner Profile:
XI SIDE CONFIGURATION: Target SIde ECC (XI SYSTEM)
1. Create a RFC Destination with Target ECC(R/3 System) and select the connection type as 3(Connection to R/3 System).
2. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination
3. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.
TARGET SIDE CONFIGURATION: CGNSAP01 (SAP R/3)
1. Go to SALE and create Logical System.
2. Create Partner Profile:

Conv from IDoc to IDoc xml

Hello All,
When SAP is triggers an IDOC to SAP XI, the conversion from IDOC to IDOC XML takes place in SAP XI(correct me If Im wrong here).
Can some body tell me what is the mechanism behind this conversion from IDoc to IDOC xml....and there is no adapter comes to into picture as the sender is SAP....which component does this conversion in XI
Regards,
Thai

To Convert IDOC to IDOC XML and the other way around,IDOC Meta Data is required by the IDoc adapter(availabe at Integration Server).
IDoc metadata is loaded in IDX2 Using RFC connection maintained in IDX1(port maintenance in the IDoc adapter).
For more details refer http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm

IDoc to IDoc through ALE

hello experts !! could u plz give me some idea or step by step help for creating IDoc to IDoc data transfer through ALE.
My scenarion is like the following:
there will be two client in two R/3 system..(Sending and receiving)....
in sending system i want to insert data in a particular table....
that data will be automatically updated in receiving system..
plz help meeeeeeee
thanks...
points will be rewarded.......

Hi Soumya,
Follow the process as below
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards,
Satish

Need help please......:IDOC TO IDOC

Hi frends,
As Iam a fresher to SAP XI, I would be very thankful if someone can answer this question.
Need to send a Delivery IDOC from a sap system to other to create sales order idoc on the receiver side if the sold to party is already present.
If the sold to party not present, one has to be created using an DEBMAS idoc and then create the Sales order idoc.
I am very much confused how to configure this BPM scenario.
As per the specification i need to create two interface mappings one for Delivery to Salesorder and the other for Delivery to Customer.
But I don't understand how two interface mappings can be created and used in a BPM scenario.
Please help me resolve this issue.
Thanks in Advance.

Hi Kinthali,
Check these blogs/help file realted to IDOC scenario for ur help:
<a href="/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get: IDOC to IDOC tunneling - how fast (and easy) can you get?</a>
Go through Michal's book, this is a one stop for all issues related to IDOC:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi: New book: Mastering IDoc Business Scenarios with SAP XI</a>
Also check these files:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a</a>
Regards,
Subhasha Ranjan

Very simple and working IDoc to IDoc scenario

Hi!
I would like to implement for demo issues a working IDoc to IDoc scenario with SAP XI 7.0.
The IDocs sohuld be send from SAP ECC 6.0 system client 100 to SAP ECC 6.0 system client 200.
Questions:
- which material type should be used (e.g. MATMAS02,..)
- how should the message mapping (e.g. MATMAS02 to MATMAS02) look like
- what are the other settings in IB Repository and IB Configuration
- how should the test from WE19 look like?
Thank you very much!

Hi Holger,
No issues for that , U can use the MATMAS 02 or MATMAS 03.
Setting in R/3 system:
1) Create the RFC Destination(SM59).
2) Create the tRFC port(WE21)
3) Create the Partner profiles( WE20)
4) Create the Distribution Model(BD64)
Setting in XI:
1) Create the RFC Destination
2) Create the IDOC Port into IDOC Adapter(IDX1)
3) Load the Metadata into IDOC into IDOC Adapter(IDX2).
Same settings happened in Receiver IDOC also.
Directory : No need to create the Sender agreement & no need to create the Sender Communication Channel.
Repoistery: Import the Sender IDOC and Receiver IDOC from R/3 system.
In WE19 Testing tool we can test IDOC generated or not.
Regards,
Sateesh
D

IDOC- XI - IDOC connection issue

Similar Messages

Maybe you are looking for