Problem sending IDOC to XI

I am trying to send a INVOIC Idoc to XI. Messages are struck in SM58.
SAP config :
SM59 - Target host: XI server IP address and XI U.id/P.W given and tested connection
WE21 - port type Trfc created
WE20 - Customer (KU) created, outbound parm - INVOIC created with port created in WE21.
I triggred a Idoc and status is data passed to port OK.
But messages are struck in SM58.
What I'm doing wrong here.
Thanks in Advance.

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 n

Similar Messages

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

Problem sending IDoc

Hi all,
I'm trying to sent an IDoc from XI to R/3 via the IDoc Adapter
should I create a partner profile (we30) on the XI system like I have done on the R/3 system?
I get the following Error:
"Unable to convert the sender service to an ALE logical system"
IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV
Thanx - Thomas

Hi Thomas,
The Partner Profile should be with respect to the Logical System Name.
Internally, during runtime, IDOC adapter fills up the IDOC control record with the corresponding Logical system names for the sender partner (SNDPRN) and Receiver Partner (RCVPRN) . If your Business Systems have the correct logical system name assigned to them and you can see the same in Business System--> Adapter Specific Identifiers.
These links will definitely help you to get the Concept right.
Check Michel Krawczyks
Mastering IDoc Business Scenarios with SAP XI
And
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Cheers...
Vasu
** REward POints if found useful **

Handling acknowledgement for sender idoc from multiple receivers

Hi,
Problem: Sender IDOC mapped to multiple FILE receivers. So sender system is SAP, receivers are BS_SYS1, BS_SYS2 and BS_SYS3. The partner profile for IDOC is set as BS_SYS. Due to this, I can enter BS_SYS in the Adapter-Specific Identifiers of one of the services say BS_SYS1. But all three will send acknowledgements and the ack messages for BS_SYS2 and BS_SYS3 error out in MONI due to
'Unable to convert sender service BS_SYS2 to an ALE logical system' and 'Unable to convert sender service BS_SYS3 to an ALE logical system'. How do I solve this since I am not able to set BS_SYS in all three services/adapter-specific identifiers box at the same time.
Anyone have this issue before? I am guessing one option is to create logical systems BS_SYS2 and BS_SYS3 in SAP and have the aleaud messages routed to these logical systems. But when there are say scores of receivers, it is a clumsy solution.
Thanks
JB

007,
nice to have here
You have alternatives:
1. Just use one business system with different inbound interfaces / receiver agreements / communication channels and conditions at interface determination
2. Create a Business Process which is doing the split. This could lead to some minus performance but you would be able to handle the acknowledgements in a senseful way (you get 3 ackn for one send msg)
Regards,
Udo

Problems with sending IDocs into R/3 using BPM

Hi Vishnu,
as I have read the forum, you have experience with sending IDocs into R/3 from XI using the BPM.
Did you have problem, that this sending takes very long time?
My BPM splits the xml, sends IDoc into R/3 immediately, but the processing of the 2nd IDoc takes 6-10 minutes!
Do you have any idea, what could be wrong?
Thanx 4 answer, Peter

Vishnu, I was discussing this problem in another thread, but no helpful answer was sent, and I have read, that you have experience, so - just for explanation
Well,
yes, this situation is really strange.. New facts are:
when I send into XI XML, which is splitted in the BPM only into 1 IDoc, it is processed immediately. When I send there XML for 2 IDocs, the first is processed immediately, the 2nd starts immediately, but end of process is after 6-10 minutes, it depends... Then I tried to send there XML for 10 IDocs - and now attention please! 5 of them have been processed almost immediately, 5 of them after 8 minutes... The last test was with 16 items - 6 processed immediately, 10 after 10 minutes... And all these 10 minutes was my 4 processor XI box unavailable, with over 60% load... But finally the IDocs arrive!!
Any explanation???
This is really unbelievable situation!
Port name is SAPDEV, rfc destination DEVCLNT100
Actually, when I was creating the scenarion using the wizard and trying to add my communication channel(IDoc type) to receiver agreement, I got error - communication channel is not configured correctly, use another one. But somewhere I read, that I should create the receiver agreement manually. So I did.
To my BPM:
-receive MSG
-switch (but I'm testing only one branch now) - and the MSG message is always passed here, it's ok
-then I have transformation to MultiMSG (message with multiple DATA for multiple IDOCS)
-then comes the split mapping Multi2SingleMSG
-then ForEach Block with sending the Single MSG
this is the end of the BPM, and outside the BPM comes the mapping Single2IdocMSG and sending the IDoc into R/3
before I had the Single2Idoc mapping in the BPM, but thought, that this could be the bottleneck, so moved the mapping after the BPM... It didn't help...
So, what do you say?
Peter

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problems at sending IDOC from XI to R/3

Hello everybody, I have a problem sending an IDOC (WPUUMS) from XI to R/3. Everytime the ERP system presents overflow problems at the locked table, the IDOC, send by the XI, is not created. The type of the sending message is asynchronous. I tried to use the ALE configuration but it doesn´t seem to work.
I hope anyone can help me to figure out this issue.
Thank you.

Julio
Please try this...
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
http://help.sap.com/saphelp_nw70/helpdata/en/44/a1b46c4c686341e10000000a114a6b/content.htm
Check the Queue [SMQ2] & if the message got struck in queues clear the queues
Then goto SMQR - De-register & register the queues.
I hope it helps you ...
Thanks,
Vasanth.

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Problems with sending IDOC in tRFC.

Hi All,
I am sending IDOC to websphere from SAP.
Problem is very weird. All the IDOCs have status 03, but some of them never reach webshpere.
I checked SM58 and there are some tRFC entries for the same.
Following is the error there:
Check SAP Connector log. Error in BO Handler.
I think problem is after the data has been sent to ALE layer.
Can anyone suggest what can be the issue? And how can this be resolved.
Regards
Anuj

Hi Anuj,
As it seems like from the error message there is some problem with the way BO handler is responding to request BOs .
The base class to initialize the connector has been set properly though.
Check the log in SM21 on this and it might give you the detailed information.
Also check if you are passing the large objects, which might require some additional config.
Hope these pointers help in solving the issue.
Cheerio,
Disha

Problem when sending IDOC from ECC to MII 12.0

Hi all,
   I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
   But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
   - 53 IDOCS were successfully outbounded (list in WE02).
   - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
   - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
   I'm wonder why some IDOCs were successful while some others were error. If the bean IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
   I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
   If some have the same problem and know how to resolve it, could you please help me?
Thank a lot in advance,
Vinh Vo

Hi Vinh,
Please read the following document:
[IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.
In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it.
I suggest that you follow the document completely and do nothing else to set up a new listener.
If you are not using ECC 6.0, you may find the paths are different, but the transactions codes are generally the same. However, you may want to check with some of the older installation instructions regarding specific modifications. Look in the Wiki for MII under Connectivity.
Good luck,
Mike

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
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
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP 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 (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 R/3 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
Regards,
AshwinM

Problem in idoc transfer from ent to r 4.6c server

hi,
   SAPR4.7->XI->R4.6c
   I've got a problem in transfering an IDOC from R4.7(ENT) to r4.6c server.My problem is, I have created an IDOC in R4.7 with 03 status,but in XI server (sxmb_moni) i get a message which reads 'NO_RECEIVER_DETERMINED'.I've configured all receiver sender details in configuration .I'm not able to trace out the problem.
   how many communication channels are needed?
   Can anyone help me with a 'detailed' walkthrough.

Hi,
'NO_RECEIVER_DETERMINED' occurs when no Receiver is configured.Check your configuraation once again.
As u have stated the return code is 03, the IDoc has successfully reached XI Server.
You don't need any communitaion channel for sending Idocs from SAP system to XI Server.
But You need a communication channel for XI Server-> SAPR/3 (4.6) communication.
Refer to "Introduction to IDoc-XI-File scenario and complete walk through for starters" by Prateek Shah
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Cheers,
Siva Maranani.

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Sending IDoc Batches to SAP: Issue with Header Mapping for SNDPRN

We are sending batched IDocs from XI to SAP. We need the individual IDocs to reflect different SNDPRN values. Our mapping creates the different IDoc EDI_DC40 record correctly with different SNDPRN values. However, XI wipes out the SNDPRN values in the payload. When we define Header mapping to get the Sender Party as the XPath to the SNDPRN in the payload, then the header mapping errors out because the XPath returns multiple values.
I wanted to know if anyone has successfully implemented sending IDoc batches to SAP from XI with different SNDPRN values.
Your feedback is appreciated.
Jay Malla
Licensed To Code
Genentech SAP XI Team

Hello,
I have the same problem. I want XI send an IDOC with the SNDPOR, SNDPRT and the SNDPRN that are in the EDIDC40.
I find this in sap.help : 
Mapping
The IDoc adapter does not make any special demands on mapping. The IDoc adapter must simply be provided with an IDoc XML structure at the Integration Server outbound channel. This either already exists or must be generated by using a mapping.
If the IDoc XML structure contains a control record, it is deleted and created again by the IDoc adapter. If you want to include additional values in the control record, you must select the Apply Control Record Values from Payload checkbox in the parameters in the communication channel and provide a corresponding mapping for the values.
You can include the values from the following fields in your IDoc control record:
MESCOD, MESFCT
TEST
EXPRESS
STD, STDVRS, STDMES
SNDSAD, SNDLAD
RCVSAD, RCVLAD
REFINT, REFGRP, REFMES
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
Perhaps we must use party configuration but I don't know how do this !
Regards,
Chris

Problem sending IDOC to XI

Similar Messages

Maybe you are looking for