IDOC Error

[Former Member]

Hi,

I am executing File 2 IDOC Scenario.

Its giving error after executing,

Error Category 	IDOC_ADAPTER  
Error Code 	ATTRIBUTE_INV_RCV_SERV 

I tried to see Service -> Adapter Specific Identifiers. But there is no entry for "Logical System Name", its empty.

I followed this procedure.

1. Create SWC

2. Create ThirdParty Technical System & Business System for File (Sender)

3. Created Web AS ABAP Technical & Business System for IDOC Receiver.

<u>in XI System..</u>

Created RFC Destnation (With same name as Logical System) of conn type 3.

Parameters:

Name:T90CLNT090

Conn Type: 3

Target Host: FIC

System Number: 00

Save As: IP Address

under Logon/ Security tab gave login details.

Tested Connection, Its fine!!

Create Port (IDX1)

Name: SAPFIC

Client: 800

RFC Destination:T90CLNT090

in I.R

4. Created Data Type, Message Type, Message Interface for File

5. Imported CREMAS IDOC and created Mapping, and did Interface Mapping.

in I.D

6. Assigned Buss System and created commu channels for File sender and IDOC receiver.

7.created Sender Agreement, Receiver Determination, Interface determination and receiver agreement.

How to solve this issue..

Thanks

Seshu

[MichalKrawczyk · Accepted solution]

hi,

>>>> tried to see Service -> Adapter Specific Identifiers. But there is no entry for "Logical System Name", its empty.

have a look at this weblog:

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

you need to have logical system for your r3 business system (which you put in header mapping - sender service of the receiver agreement)

Regards,

michal

[Former Member · Accepted solution]

Hi Michal,

Thanks for reply.

Regd Logical System, i did like this.

T-Code: SALE

Copied 'Logical System' name which is assigned for Client 800.

and While creating SLD,

Technical System: ( for Receiver IDOC)

1.Web As ABAP

2.Web AS ABAP Name (SID): FIC ( i don't know where to find SID , somebody asked me to give my R/3 System name.

Note:Other guy told me like this to find SID, T-Code:SM51

There will be name Seperated by 2 Underscores, the part next to 2nd underscore is SID. So, in my R/3 System, its like FIC_FIC_00, but when i tried to give 00 as SID, its not accepting, so i gave FIC)

Installtion Number: (i gave)

Database hostname: FIC

3. In next page Instance Number:00

4. In next page Host Name: FIC and clicked Add

5. Client: 800

Logical System: T90CLNT090 ( which is from T-Code Sale)

Business System:

1. New_BS_IDOC

2. Selected the Technical System created above.

Still cannot find in "Adapter Specific Identifiers"

<i>>>>you need to have logical system for your r3 business system (which you put in header mapping - sender service of the receiver agreement)</i>

do i need to provide, receiver Buss System for Sender Service of Receiver Agreement?

and i looked at weblog given, i am unable to find anything under T-Code IDX2, its empty..

Any Sugg?

[MichalKrawczyk · Accepted solution]

Hi,

>>>Still cannot find in "Adapter Specific Identifiers"

did you try the button at this screen

(compare with SLD) ?

there mmust exist an entry in SLD for the logical system

to use it

Regards,

michal

[Former Member · Accepted solution]

Hi Michal,

Yah, i pressed Compare with SLD also.

I did like, intially when i define Tech and Buss Systems (IDOC Receiver), i forgot to give Logical System name.

Later after executing the scenario, i checked blog u given and modified ( deleted the tech and buss systems and created with same name, becoz same name already assigned in I.R)

Is that ok? if i did like that?

Which one i have to choose for

Business System Role: Integration Server or Application System

Thanks

Seshu

[Former Member · Accepted solution]

I am just trying to understand what you have done so far.

1.You need to have Recevier Agreement with the appropriate Receiver IDOC Adapter assigned to it.

2.Also you have to load the IDOC Meta data in transaction IDX2. I did not see a mention of this in your discussion so far.

[Former Member · Accepted solution]

Hi,

Thanks for reply..

1.You need to have Recevier Agreement with the appropriate Receiver IDOC Adapter assigned to it.

I assigned

2.Also you have to load the IDOC Meta data in transaction IDX2. I did not see a mention of this in your discussion so far.

i did't.. how to do this?

Thanks

Seshu

[Former Member · Accepted solution]

1.IDX2:

Go to this transaction.

Select the menu Metada and then select Create. In the screen that comes specify the IDOC Type, Extension and Source Port. In your case the Source Port is the port of SAP R3.

After you do this the IDOC Meta data will be retrieved from SAP R3 if the port is configured appropirately.

2.About the Logical System:

Go to SLD and Technial Systems. Look for the SAP R3 Technical System. Then select the client say 100. In the screen that you see you should see a Logical system name. If if is not defined define the logical sytem name.

After you do this go to ID and then go to the Business System and then go to Adapter Specific Identifiers. You should see the Logical System.

Also remeber to use the same name for the Logical system names in SAP R3 as well as XI.

[Former Member · Accepted solution]

Hi,

When using IDX2:

its asking

IDOC Type:

Extension:

How to find IDOC Type and Extension for CREMAS.CREMAS03?

Thanks

Seshu

[Former Member · Accepted solution]

Hi,

I tried to look at

sxmb_moni

the error details as follows

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Call Adapter 
  --> 
- <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_RCV_SERV</SAP:Code> 
  <SAP:P1 /> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

I have some confusion under Logical System name:

I took existing logical system name(T90CLNT090: from 800 client in r/3) while creating Technical System

and created business system for that..

In my XI system, logical system from client 100 is LS100CL.

these logical systems need to match?

Sugg me

Seshu

[Former Member · Accepted solution]

Yes they should match. Take the Logical System Name for SAP R3 from SAP R3 and use the same name for the Logical System Name in SLD. To change the Logical System name in SLD you go to Technical System Landscape and select the WebAs ABAP Technical Systems and then select the SAP R3 technical system. Click on the client under consideration and then type in the correct Logical System name.

Remember that each client is a Logical System or Business System. Each client has a different Logical System name.

[Former Member · Accepted solution]

Hi,

Let me clarify..

Logical System Name of R/3 = Logical System Name of XI

or

Logical System Name of R/3 = Logical System name for Technical System created under SLD?

i followed the second one.. it matches..

Thanks

Seshu

[Former Member · Accepted solution]

no.

Logical System Name of R3 in R3 = Logical System Name of R3 in XI

Logical System Name of XI in R3 = Logical System Name of XI in XI

[Former Member · Accepted solution]

In IDX2 the IDOC Type in your case is CREMAS03.

You do not need an extension.

Try to make this work. This proves that your port set up for R3 is good.

[Former Member]

Hi Seshu,

Look at this too...

http://help.sap.com/saphelp_erp2005/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/96/d8fa40badbf56fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0e/d8fa40badbf56fe10000000a1550b0/frameset.htm

cheers,

Prashanth

[Former Member]

Hi Seshu,

In the SLD for your technical sytem, make sure that in the specific client settings you have added the logical system name correctly.

Then, in the adapter specific identifiers of your business sytem, bring in this value into the logical system name, by clicking on the "Compare with System Landscape Directory" button(you have to be in change mode).

Thanks,

Renjith