IDOC_ADAPTER.RECEIVER_BSI_INCORRECT

Hi,
I'm trying to send an IDOC to a SAP system (IQ1_100) from XI. I've defined a technical system (IQ1) and a business system (IQ1_100) in SLD. The corresponding logical system is also named IQ1_100. In Integration Builder configuration, the receiver of the IDOC is IQ1_100 - IDOC Adapter with port SAPIQ1, RFC-destination IQ1_100. (so maintained in SM59) In XML-monitor all messages send to this receiver fail in step 'call Adapter' with the following error:
Code: IDOC_ADAPTER.RECEIVER_BSI_INCORRECT
Unable to convert partner to IDoc receiver partner.
What did I miss???
Thank you for any help, regards, Kathrin!

Hello Kathrin,
Please make sure that the ALE name for your receiving (and sending) systems in SLD is in UPPER case only. Then you can try this:
1. In Integration Directory (Configuration).
   Follow menu path: Environment -> Clear SLD data cache.
2. In the transaction SXI_CACHE.
   - F6 (complete cache refresh)
   - Follow menu path: Goto -> Business System. Choose the busine
     system and press the button #Compare Data#.
Hope this will help.
Kind regards Johan

Similar Messages

XI 2.0 - IDOC Adapter configuration

Hi,
I currently have an integration scenario whereby an external system sends IDOC-XML to our integration server which then forwards this via an IDOC adapter to an R/3 620 system.
When I send the XML to one client I keep getting the following message :-
<SAP:Context />
<SAP:Code p1="Requested parameter does not exist" p2="RQ1CLNT302" p3="" p4="">IDOC_ADAPTER.RECEIVER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc receiver partner</SAP:Text>
After my initial investigation I believed that the above error was due to the client within the SLD had been set-up without a logical system name and the receiving business system had been set-up without an ALE name. In order to resolve this I deleted and re-created the client and the business system within the SLD. Having done all this the error still occurs.
Does anyone know what causes this problem?
The systems involved have been set-up in the SLD as follows :-
a) Sending system PKMS_SAPTEST Alename: PKMS_TEST
b) Receiving system RQ1CLNT302 Alename RQ1CLNT302
I have checked the ports in IDX1 and the partner profile in the receiving system but still cannot work out what is causing this problem.
I know I am missing something really obvious as these messages work when I send them to other clients but I am at a loss to explain the difference
Regards
Ian

Hi All,
I have now resolved this problem and thought I should spend some time sharing this with you.
I decided to look at the code that was issuing the error which was calling a function module called SAI_LOGICAL_SYSTEM_GET to return the logical system for my business system. When I ran the function module in test mode it returned a blank logical system. The logical system is stores in table sailcrbsc. I re-ran the function module with the bypass buffer field set to 'X' - now when the function module is called it returns the correct logical system.
Anyone out there have any more info on this? How should I have re-built this table?
Regards
Ian

Error:IDOC_ADAPTER" ATTRIBUTE_INV_SND_PARTY : File to IDOC scenario .

Dear XI experts ,
Issue : Error to a new implementated SAP ERP SYSTEM . File to IDOC Scenario
Business Scenario : Exchange Rates from Thomas REuters (XML) - > XI-> SAP 1 , SAP 2 ERP Systems ( 2 diff SAP ERP systems)
SAP 2 is a new system set up for a new plant of our Organization.
The Excahnge rate is gettiong updated by IDOC: EXCHANGERATE.EXCHANGE_RATE01 in two SAP Systems
Each one is configured with diffrent IDOC receiver .
The Error is : for the SAP 2 system . The MEssage gets branched and one message is successfully sent to SAP1 , and turns an error : in SXMB_MONI for SAP2 system
I had been thropugh few blogs have performed the below steps:
-IDOC metadata : IDX2 have configured in XI
-checked the port of EGP , Partner Profile in SAP 2 ERP system
-Checked IDX1 , IDX2 of SAPEGP in XI .
-Refreshed business system .
-Tried to send the xml data from the start point through File Zilla(FTP)
Could somehow help as this is Production issue ans this is affecting the business.
Error from SXMB_MONI:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Reuters</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Reuters to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Reuters : is the Sender Party of Exchange Rates. I have seen in blogs to craete agency / schema , but since thsi scenario is 2 seperate SAP ERP systems , my question is do i need to create agency , schema for sender party .
Appreciate your Input
Thank you,
Vara
Edited by: Varalakshmi SB on Oct 26, 2011 12:14 PM
Edited by: Varalakshmi SB on Oct 26, 2011 12:16 PM

agency and scheme are used when your doing B2B scenarios.

XI Error ATTRIBUTE_IDOC_RUNTIME.IDOC_ADAPTER: Queue in SMQ2

Hi XIer's,
I have an issue while i am doing an IDOC-to-IDOC Scenario
The queues have been stucked in the SMQ2 and when i checked the queue it is showing sys-fail and with this Error : "XI Error ATTRIBUTE_IDOC_RUNTIME.IDOC_ADAPTER: Queue ".
when i tried to process the queue by executing LUW it is not processing.
Therefore i request you let me know the reason for this error why it occurred and please let us know how to resolve it.
Appreciate your quick reply and points will be awarded accordingly.
Thanks & Regards,
Ram

Hi XIer's,
I have an issue while i am doing an IDOC-to-IDOC Scenario
The queues have been stucked in the SMQ2 and when i checked the queue it is showing sys-fail and with this Error : "XI Error ATTRIBUTE_IDOC_RUNTIME.IDOC_ADAPTER: Queue ".
when i tried to process the queue by executing LUW it is not processing.
Therefore i request you let me know the reason for this error why it occurred and please let us know how to resolve it.
Appreciate your quick reply and points will be awarded accordingly.
Thanks & Regards,
Ram

IDOC_ADAPTER ATTRIBUTE_WRONG_INTF

Hi Experts,
I have a scenario where, i want to create as many number of IDOCs as the number of rows in the source XML.
For this i have done the following.
1)I have exported the XSD schema of the IDOC.
2)I have changed the occurances to Unbounded.
3)I have reimported the xsd as external definition.
4) Developed the Message mapping and the Interface mapping as per the requirement.
When I execute the scenario, I get the following 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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>Orders_Multiple_Oubound_Async_MI</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface Orders_Multiple_Oubound_Async_MI</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can someone help me in this regard?
Thanks and Regards,
Ravi Kanth Talagana

HI,
Just you need to delete the IDOC metadata from IDX2 and then have to process the scenario.
You have changed the occurance in External defination but the IDOC Metadata pertain to the old one...
Try it out as well as Refer similar discussions
IDOC Adapter error / ATTRIBUTE_WRONG_INTF
What does this error mean in idoc_apapter
Problem sending multiple IDOC
Thanks
Swarup

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

IDOC_ADAPTER: ATTRIBUTE_IDOC_RUNTIME

Hello All,
I have had an problem dropped on me. The consultant left prior to the BPM going live and I have not worked with BPM before.
The error I an receiving is:
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPPF1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>*Error: Transaction IDX1: Port SAPPF1, client , RFC destination contain errors*</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have compared the setup in "test" with this in "PRD" and everything looks the same... what could be missing?
Thanks,
Rich

Hello All,
Thank you for all of the help. I finally went to SAP Support. Turns out that there are some "not well documented" facts (this quoting SAP) about having an SAP system with multiple clients that will send or receive IDOCs to/from PI. This is especially true if (as in my case) the 2 production clients are 020 and 050... but I want to use client 050. It seems that PI when accessing the list of ports internally in IDX2 looks at only the first entry on the list. (a sorted list)... so client 020 shows up first.... hence the error.
SAP has recommended that I go back and have only 1 port to a system with multiple clients and that port should point to client 000. I have asked for some clarification, but I am hoping to get this resolved next week. I will post again at that time.

IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP Only asynchronous processing supported

Hello Expert,
Error while send IDOC
" IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP Only asynchronous processing
supported for IDOC Adapter" is returned.
Please suggest
Thulasi

Hi,
Make sure that you have mentioned the Recever message interface as Async mode
Here it is saying that IDOC suports only Async that means some where else u have mentioned as Sync interface
Regards
Seshagiri

IDOC_ADAPTER - ATTRIBUTE_INV_SND_SERV

I´ve read all the thread regarding this problem, but I still can't solve it.
My interface is synchronic from an Idoc. it goes through a BPM and then reaches a WebService
The messagge arrives perfectly but the ACK has the following error:
IDOC_ADAPTER - ATTRIBUTE_INV_SND_SERV
Unable to convert sender service R3_FPA_SALDOSBANC_BPM to an ALE logical system

Hi,
i think there is a problem with the Logical systems or ALE settings that you have performed.
Kindly follow or verify the 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)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     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 7)
     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.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

IDOC_ADAPTER.SENDER_BSI_INCORRECT

Hi,
I get the following error message. Can anyone help on this? I have imported the metadata using transaction IDX2. Also the cache displays the logical system for the receiver system. My sender system is a third party and not an SAP System. Do I still need to specify the logical system for that?
Regards
Amit
SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in SLD client: AbapSLDRequestHandler.ext" p2="BS_Enfield_WS" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
</SAP:ErrorHeader>

problem resolved by Creating an entry in 'sailcrbsc' table for the sender system. Even though the sender system is not a SAP system I had to create an entry in the above table. Refresh the cache from SXI_CACHE. And resend the message.

ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"

Dear SAP experts,
Good day!
Can i seek your advise regarding the error i am getting in sxmb_moni?
It seems that XI cannot deliver the IDoc to SAP system (in our case, Q40011).
We are in GDA (Acceptance).
The error log is,
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPQ40, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPQ40, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The user SAPXI0RFC have already been unlocked in Q40011.
But, when i've checked the monitoring now, it is still error.
Kindly advise regarding my issue.
Thank you very much!
Fred

Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

IDOC_ADAPTER ATTRIBUTE_IDOC_METADATA

Hi Experts,
We have a scenario cXML to IDoc using BPM, which is working ok in Development environment.
But when it is transported to SIT environment got failed. please see the details below
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>You have no authorization for extensions (activity 03)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: You have no authorization for extensions (activity 03)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Please suggest on how to resolve the issue.
Thanks in advance.
MK

hi mk
logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
      Field name RFC_TYPE value FUGR
      Field name RFC_NAME value EDIMEXT, SDTX
      Field name ACTVT    value 16
Authorization object S_IDOCDEFT
      Field name ACTVT value 03
      Field name EDI_CIM value ' '
      Field name EDI_DOC value TXTRAW01
      Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
      Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
      Field name ACTVT      value 03
      Field name DICBERCLS value
Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.
Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function
reward points if helpfull
rgrds
kummari
Edited by: kummari on Jul 8, 2008 7:40 AM

IDOC - Idoc_adapter.sender_bsi_incorrect (path //s)

Hi people, I get this error when I run the idoc_adapter :
<SAP:Code p1="The accessing object does not support the path //s" p2="DEV" p3="" p4="">
I have configured the ale name, for example, for BS dev I put SAPDEV for client 100, but this error is showed.
Do you know if there is one log, one way to debug and discover something? Something strange is the "path //s", it looks like an address.
Thank you for any help !
Regards,
Renato.

Hi people, I discovered !!!
I am going to tell the way that I did to discover the problem :
In the monitor (sxmb_moni) the process trace is showed, there are entries like CL_IDX_IDOC_SERVICE-ENTER_PLSRV that means one abap class method, so, I debug this method and I find the function SAI_LOGICAL_SYSTEM_GET which get the logical system names, and debuging this function I could see one comparation statement "hosts_in ne me->host" whose in my case was "SRLCPD13" <> "srlcpd13", bingo !
I used transaction SLDAPICUST to change the host name to low case, and voilá !
Bye,
Renato.

SYSTEM ERROR, IDOC_ADAPTER, Unable to convert ALE to logical system

Hi,
I just wanted to check when i am using SXMB_IFR for monitoring then in message monitoring ---> if i check for Integration server as a whole i Find error as SYSTEM ERROR but if i check only for Adapter engine I get all the idocs successful.
So what we have to monitor the whole integration server or adapter engine only

saras,
When you see successful in the Adapter Engine, what it impliesis that the Adapter Engine has picked up the message ( file in your case ) and then passed it to the Integration Engine for processing ( this is where the actual pipeliining steps take place). As far the adapter Engine is concerned the message has been passed to the integration engine and so its job is done.
The error you see in Integration Server is becuase it includes the status of the messge in both the adapter Engine and the Integration Engine. You messages has errored out in the Integration Engine and so the problem!
Just rememebr this terminology --> Integration Server is the runtime of XI which in turn contains the Adapter Engine and the Integration Engine.!!
Regards,
Bhavesh

Error Posting IDOC: need help in understanding the following error

Hi ALL
Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
where SAP_050 is the RFC destination created to post IDOCs
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated.............Thank you!

Hi Patrick,
Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
Also Refer this Note 747322
Regards,
Prakash

IDOC_ADAPTER.RECEIVER_BSI_INCORRECT

Similar Messages

Maybe you are looking for