ATTRIBUTE_INV_SND_SERV

[Former Member]

Hi, there.

I have big problem and i don't know what I can do.

we have xi3.0 and most recent version and patch

(was, kernel, j2ee, xi is most recent version).

we'd like to connect regacy(file) -> xi -> was620(IDOC).

when we connect xi-> was620, we use IDOC Adapter.

but I have error.

=====================================================

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>

========================================================

here are the steps I did:

WAS620 Client is 100.

XI Client is 800.

1. Setup an RFC R/3 Destination on my client 100 (WAS620) to client 800 (my XI): BEO_800 (in WAS)

2. Setup an RFC R/3 Destination on my client 800 to client 100: BEO_100 (in XI)

3. Setup the IDOC processing port "SAPBEO" on client 100 with RFC Destination BEO_800. (in WAS)

4. Execute IDX1, I input the SAPBEO port created in step 3, input the client number 100 and the RFC destination BEO_100 created in step 2 and save. (in XI)

5.Execute IDX2 input port SAPBEO and idoc type(CREMAS03) (in XI)

And I input SAPBEO in the port field on the Configuration Builder.

I don't know why error occured.

and is there any missing configation??

or is there IDOC Adapter Document to help me?

Regards

Miru.

Message was edited by: taewoo kim

[p_vanos]

Hi,

The third party needs to send a confirmation message back to XI which needs to be coupled in XI to the sending message which then creates the ALEAUD idoc. THis only works automatically for IDOC to IDOC scenario's as far as I know.

It is I think difficult to make some logic to find the correct original message when creating your own confirmation interface from third party back to SAP! If you can manage I would like to know please!

Cheers,

Paul

[cdumont69]

Hi,

I am not sure but It seems to be possible :

http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/frameset.htm

/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

In my flow, XI create the ALEAUD Idoc but it is not sent to SAP (or I can't find it in SAP with WE05 ?).

How can I change the log level, the status of the Idoc ALEAUD (there is always status 03 even if there is an error) ?

Thanks

Regards

[p_vanos]

Hi,

When you do not want a confirmation to take place, please maintain entries in table IDXNOALE. When you perform a search on this table you will find a message I posted recently.

Cheers,

Paul

[cdumont69]

The IDXNOALE table must be use to switch off ALEAUD.

I don't want this, I want to get an acknowledgment and this doesn't work. So, I search why XI don't want to send an Ack to SAP R/3 !?

I use Business System (SAP and 3rd Party) that are created in SLD.

In the directory, I configure the flow SAP (idoc) -> 3rd Party (CSV) with Mapping.

And when XI want to send an Ack, It create an error. If I put the XI LS to my 3rd Party in SLD the error disapear but the ALEAUD idoc is not sent.

I don't understand why I must put XI LS in my 3rd Party ?

It is normal ?

Thanks,

Regards.

[p_vanos]

Hi,

Pfew, the only thing I can come up with now is that you can maybe check the SM59 settings! And if that is ok, restart the whole system!

Paul

[cdumont69]

I check the SM59 settings, I have the 2 systems with good name and test connection are OK.

So, I reboot XI, but nothing better append !!??

What can I do ?

Perhaps I forget something ?

Must I customize something in SAP to insert Acknowledgement except SAP and XI RFC destination ?

Must I customize something in XI except by transaction IDX1, IDX2, SM59 ?

Thanks

[cdumont69]

Hello,

I have a new question.

My process is SAPR3 (Idoc) -> XI -> 3rdParty (CSV).

I create the 3rd party in my SLD and I use it in the process flow.

I have this error "ATTRIBUTE_INV_SND_SERV" when acknowledgment must be sent. So, in this case the sender is my 3rd system that doesn't have LS configuration.

Must I add the XI LS in the Directory configuration (Service -> Adapter specific identifiers) ?

Thanks,

Regards

[p_vanos]

Hi,

Did you maintain the adapter specific settings in the directory of the business system (SAP)?

Make sure you have entered the LOGICAL SYSTEM name of the SAP system when creating the SAP system in the SLD.

Cheers,

Paul

[cdumont69]

The Logical system name of SAP is in the Business Landscape definition with the Client and it's the same as the R/3 LS.

When I check it in the Directory (Service / Adapter-specific Identifiers), there is no problem.

The configuration of the Idoc adapter is complete (only mandatory) with IDX1 customizing.

[p_vanos]

HI,

Then my answer is still valid. Please execute IDX1 and IDX2 in client 800. Use the correct port in your IDOC receiver channel. Also check the adapter specific settings in the directory, goto your Service (SAP system client 100) and goto Service--> Adapter specific identifiers. You should see Logical system, and R/3 system ID and the correct client. If not, press Compare with system landscape directory. If this does not help, check the definition in the SLD of your client 100, did you define the correct logical system for the client in the technical system/business system?

Hope this helps

if not send me an email: paul.van.os@capgemini.com

Cheers,

Paul

[cdumont69]

Hello,

I have the same problem.

I want to send an Idoc with SAP R/3 to create a CSV flatfile.

Because I have the same message : "ATTRIBUTE_INV_SND_SERV ...", and because all seem to be correct, I do all I find in this forum

1. Delete Scenario in the Directory.

2. Delete Technical and Business system in SLD.

3. Delete (IDX1) the port and (IDX2) the Metadata.

4. Purge all the cache.

5. Recreate with IDX1 and IDX2 the port and the metadata (the RFC destination is already create).

6. Recreate in the SLD the Technical Landscape (with the same name than the older).

7. Recreate in the SLD the Business Landscape (with an new name).

8. Recreate my scenario.

And the error is the same !!??

I don't know why.

Does anybody have an idea ?

Thanks,

Regards

[p_vanos]

Hi,

Do I understand that your XI client is 800? If so, you need to execute IDX1 and IDX2 in client 800 and not in client 100. So you have to define your WAS 620 system in the XI system. Why do you enter SAPXII in the port definition? I think it should be SAPBEO!

Hope this helps.

Cheers,

Paul

[Former Member]

Hi Paul.

Thank for your reply mail.

Client of WAS620 System is 100.

Client of XI system is 800.

I think that all this thig is wrong typo.

I correct my sentence.

Please give me your help.

Thank.

Regards,

Miru.

Message was edited by: taewoo kim