Reg:IDOC Sender side settings

Dear All,
My scenario is IDOCPIMDM
I have created all the basic ALE settings and they are,
SAP R/3:
1)RFC Destination (SM59)
2)Logical system
2)Port (We21)
3)Partner Profile (WE20) name same as logical system
SAP XI:
1) RFC Destination (SM59)
2) Create Port (IDX1)
3) Load Meta Data for IDOC (IDX2)
In Integration Directory,Adapter-Specific identifiers,its shows the logical system that was created in R/3 server.
Could anyone suggest me on the following queries,
1)Whether I have to create anymore steps other than this.
2)Should I need to create Logical system in PI
3)Should I need to create a distribution model.
4)What are the details ,I should enter in sender/receiver details ,while we use WE19 transaction code for triggering the idoc.
Thanks in Advance,
Lavanya.B

Hi Lavanya,
The steps are the standard steps.
I hope it should work.
In PI, you need to create on LS (Business Service) or Business System.
If you are creating Business Service, it would be mapped via SLD otherwise the Business service needs to be mapped to the indoc(Go to Business Service--> Edit to add Outbound interface as Idoc name)
Regarding Triggering Idoc,
You need to provide the sender and receiver details
Receiver Port
Receiver Partner no
Partner Type
Sender Port
Sender Partner no
Part type
Hope this helps you.
Regards,
Sushama

Similar Messages

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) 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)
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 XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP 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 (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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Business service is not working in sender side but business system is working soap to idoc but why like that

i have scenario SOAP to IDOC
when i'm using business service in sender side it is getting an error as follows
sender message can not convert to ALE Logical system
in this i'm using altova spy as testing tool
my sender interface is asynchronous
but when i'm using business system everything is working fine
In sender side i'm using soap adapter,i checked the logical system everything is fine
mainly the problem is why it is working when i'm using business system rather than business service
my pi version is pi 7.0
thanks in advance
regards
satish

Hi Satish,
You are sending IDOC's to SAP system right. we should create Business system not business service.
so we should create the business system as web AS ABAP in SLD and import the same in ID.
When we create the business system in SLD the logical system name is assigned for the business system. like SAPCLNT100...It plays a key role in IDOC scenarios.
sender message can not convert to ALE Logical system
Reasons for this issue is
1) logical system name is unable to read from SLD for that corresponding business system.
Goto business system click on Adapter specific identifiers from the menu --> read from SLD.
it will automatically fetch the logical system name from the SLD.
2) Sometimes the logical system name will be deleted from the business system in SLD.
Delete the business system and re-create it, and follow the above procedure.it will resolve your issue.
Regards
Bhargava Krishna

PI 7.1 Ehp1 IDOC adapter message packaging - package options on sender side

Hi guys,
I am trying to use the new IDOC adapter PI7.1 Ehp1 functionality for packaging the IDOCs in single PI message, instead of using Collect pattern in BPM. I have configured IDOC sender comm. channel with Sender Agreement as well. So far, so good, but I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side...
What I mean? Do I have to set the Pack. Size (we20) to be the same as the one on PI, and do I have to use "Collect IDocs" as
Output mode (also found in we20) .. I guess "Yes".. Actually what I got also is that I have to schedule RSEOUT00 if I am using the option to Collect IDOCs, right ? Can execution of RSEOUT00 be "plugged" somehow to be executed after bd21(Creation of IDocs from change pointers) execution ..?
If you have any personal experience on this - please share it with me
Thanks & Best Regards,
Lalo

I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side
Do not have to be same.
Think of this way: there are two containers carrying water: A for ECC and B for PI (specified in communication channel), you are defining the size of the containers.
If Size of A > B, then, One full A will need more than one B to handle, means multiple PI messages will be created.
if Size of A < B, One PI message is enough to handle incoming package.
For sure in partner profile of ECC, you will need to enable IDOC packaging and specify the size (container A).
Regards
Liang
Edited by: Liang Ji on Jun 8, 2010 3:30 PM

Why v r not configuring IDoc & HTTP adapters on sender side

Hi Gurus,
Y v r nt configuring the Idoc and HTTP adapter on sender side.
But on d receiver side v r configuring. Why?
IDoc and HTTP Adapters are built on ABAP stack.That's y v r nt configuring on d sender side.It is the same thing also on d receiver side also.But y v r configuring on reciever side.
Could u guide me.

Hi Kumar,
Check this thread for your query
Adapters
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML
but in but XML to IDOC is done by Receiver IDOC adapter
Sachin
Edited by: Sachin Dhingra on Jan 10, 2008 4:03 PM

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC . But in receiver side it is having.
what i know is
1) Idoc adapter is in ABAP Stack.
2)XI having Idoc Metadata.
3)Once Communication Idoc generated , no control on it.
4)SAP using TRFC to identify XI , XI cant.
Pls explain , in comparition with receiverside. Dont post links.

Hi vijayreddy.veluri
these questions are very general.
Please refer to the
[rules of engagement|/thread/117188 [original link is broken];
before creating threads.
Sender agreements are not required as there is no requirement to bind sender information to a sender communication channel.
[IDoc Processing with the IDoc Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm]
Thanks and Regards
Kenny Scott
SDN XI/PI Moderator

Settings if http adapter is sender side?

Hi ALL,
my doubt is if http adapter is sender side how to make settings to before configuring a scenario, because we don't have sender comm. channel, sender agreement.

Hi-
Check this help
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Also check this thread
How to send XML file into XI using sender HTTP adapter

Sender side 10 files and reciever side 10 idocs

hi,
if suppose from sender side there are 10 files ....each files containing name and addresses of customers . and in the recievers side there will be 10 idocs each idocs will have customers name and addresss.........
can u guide me to do the above scenerio..
thanks in advance,
jp.

JP,
<MT_Input>
<Record>
<Emp_Name>J</Emp_Name>
<Emp_ID>10000</Emp_ID>
</Record>
<Record>
<Emp_Name>K</Emp_Name>
<Emp_ID>10000</Emp_ID>
</Record>
<Record>
<Emp_Name>L</Emp_Name>
<Emp_ID>10000</Emp_ID>
</Record>
<Record>
<Emp_Name>M</Emp_Name>
<Emp_ID>10000</Emp_ID>
</Record>
<Record>
<Emp_Name>N</Emp_Name>
<Emp_ID>10000</Emp_ID>
</Record>
Like above we have 10 records in single file.
In case 2 , each Record is in different file.
Best regards,
raj.

Reg:http adapter-sender side

which http client tool is used to send the request if we are using http adapter on sender side?

Hi Chandra,
HTTP: Hyper Text Transfer Protocol is a stateless prtocol to send a request and get a response back on that. For your query is there any specific client used?
Ans: No, you can use any client means the ip address of the system from which you are making request called client and to which you are making request called server. http is nothing but some set of rules to exchange data between two systems.
One more thing to mention is "some jave code is written for http and that is register on W3C" so that different server can connect to each other using it.
See the link below:
http://www.w3.org/Protocols/
Please always Rewards if helpful.
BR,
Alok
Edited by: Alok Sharma on Mar 18, 2008 12:49 PM

Why IDoc Sender Channel Used in Outbound Scenario's

Hi Team,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
Can you give me clear idea on it / suggect any blogs.
Thanks.
Drumi

HI,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
thanks,
Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

Change Idoc Sender system

Which are the necessary steps to be perform in order to change the sender system of an Idoc, for instance:
the current scenario: R3 System1(IDOC) -> XI -> SRM
the to be scenario: R3 System2(the same IDOC) -> XI -> SRM
Thanks in advance

1. All the ALE settings would be changed. So the names of RFC destination, port, Logical system etc would change at sender side.
2. In SLD entries should be maintained for new R3 system
3. There should be an entry on idx1 for ur sender system.
4. At IR it would be better to reimport the IDoc.
5. Mapping would be required if there is a change in structure
6. ID would change completely bcoz the sender system name will change
Regards,
Prateek

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

File content conversion on Sender Side

Hi,
I am doing file content conversion on sender side.when i am executing the scenario,i am getting the following error in sxmb_moni:
Invalid at the top level of the document. Error processing resource 'file:///D:/Documents and Settings/...............
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> DOC_HEADER ...
when i right click on the pyaload and select view source
its displaying the whole flat file with the following line at the beginning:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
i have given all the parameters correctly....
in sxmb_moni.....the error category is Mapping and the error id id EXCEPTION_DURING_EXECUTE
Please help me with this error.
thanks n regards,
anuradha

Hi !!
The best way to debug would be to add TRACE statements in your mappigs. In both Graphical and java Mapping.
Trace out the entire output of java mapping and see if this is the input that the next mapping expects.
For trace , http://help.sap.com/saphelp_nw04/helpdata/en/c8/98e7d5c1620642973565ea3dd319d1/content.htm
refr this links also
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected
unsported character error in message mapping
Re: HTTP to RFC Mapping error:com.sap.aii.utilxi.misc.api.BaseRuntimeException:
Exception com.sap.aii.utilxi.misc.api.BaseRuntimeException
Re: Outbound error
Re: mapping error
error in file to file
have a look at this weblog on how to test your mapping
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Thanks !!!

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

Reg:IDOC Sender side settings

Similar Messages

Maybe you are looking for