Using SAP XI just for mapping; no real receiver

[Former Member]

Hi everybody,

I wrote a compex java-mapping. We now want to use this mapping for R/3 just to convert some data.

R/3 sends a request via RFC communication channel and receives the response of the mapping?.

How do I have do do this in integration directory? There is NO real receiver.

Thanks regards

Mario

[Former Member]

Hi,

we found the problem. Somebody maintained a sender agreement inclusiv a IDOC-Sender CC!

What is wrong!

Thank You all

Regards

Mario

[Former Member]

Hi all,

thanks for your posts.

To make it clear:

I want NO BPM.

The RFC-Call from R/3 to XI has to synchronous.

Regards Mario

[former_member181985]

>want NO BPM.

>The RFC-Call from R/3 to XI has to synchronous.

I am just thinking of the following,...

create a BAPI with in SAP PI which has both I/o structure same as OUTPUT RFC response structure of sender R/3 system. Remote enable that BAPI. import this RFC in PI.

Now scenario would be

Sender R/3 (RFC, sync) ---> SAP PI --> RFC in PI (sync)

Request message mapping -->

Sender R/3 RFC request(Input)---> ur LOGIC -->PI RFC Request(Input)

Response message mapping -->

PI RFC response (output)---> one to one mapping -->Sender R/3 RFC Response(output)

Regards,

Praveen Gujjeti

[Former Member]

Hi Praveen,

good idea!? I'm not sure if I understood in detail. Do you thinks of creating two RFC-BAPI?

Regards

Mario

[former_member181985]

Only one BAPI in PI (which should be sysnchronous in behavior). You already have a BAPI on sender R/3 system.

Synchronous communication and hecne one interface mapping which will have two message mappings(request and response)

[Former Member]

Hi Praveen,

OK, I will try this. Points guaranteed!

Unfortunalety I have an error in RWB when sending the RFC-Data to XI:

Verarbeitungsfehler verursacht durch: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Error during Sender Agreement Determination caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Error during Sender Agreement Determination

--> I scanned SDN. There are unfortunately no useful answers.

Regards

Mario

[former_member181985]

can you tell your configuration details?

I guess receiver determination is missing....

Also can you provide us the SXMB_MONI error details for this message (if any...)

Regards,

Praveen Gujjeti.

[Former Member]

Hi Praveen,

the only think I did not maintain is the interface determination. When I test the configuration in ID, everythings is fine:

senderagreement is found

receiver determination is found.

As the error occurs on RWB the is no message in SXMB_MONI.

FYI: RWB --> Detail --> audit protokoll:

SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: IDoc; AdditionalText:  ; ApplicationFaultMessage:  ; ErrorStack: Sender agreement found belongs to adapter IDoc; however, current adapter is 'XI'

regards Mario

Edited by: Mario Müller on Jun 1, 2010 1:18 AM

[former_member181985]

Ideally the message should be in MONI. Have you activated all the objects in ID.

what is ur Receiving business system?

[stefan_grube]

when you are working with PI 7.1:

Make shure that your sender RFC channel does not have a * as party. Party must be empty.

[Former Member]

@Stefan,

thx for reply.

We are on PI 7.0

Regards

Mario

[Former Member]

@Praveen

- The is nothing in MONI.

- All object are activated

- the receiver-service is the same as the sender-service

Regards

mario

[Former Member]

@all.

Some more information.

In RWB --> Detail --> Message-Part: There is no PAYLOAD!

I am not sure if this is

a) causing the error

b) caused by the error.

regards

Mario

[stefan_grube]

> ErrorStack: Sender agreement found belongs to adapter IDoc; however, current adapter is 'XI'

could you check whether you have a generic sender agreement with * in interface and naespace.

This could be the reason.

Create a specific agreement with interface corresponding to your RFC name and namespace.

[Former Member]

@Stefan.

Sender agreement:

Party = emtpy

Sender = <SENDING_R/3>

Interface = Imported RFC from IR

NS = corresponding namespace from Imported RFC from IR

Regards

Mario

[former_member181985]

>the receiver-service is the same as the sender-service

You mean for synchronous behavior, r u doing like this..

SenderR/3BusinessSystem > SAP PI>SenderR/3BusinessSystem (as receiver)

Can you explain us your current set up in IR & ID .........( I am not sure which solution you are following)

Edited by: Praveen Gujjeti on Jun 1, 2010 11:16 AM

[Former Member]

Hi all,

I give up.

Is there another way I could call the interface-mapping from a R/3?

I never worked with proxies.

Could a proxy be the solution? Could you pls. give some instructions?

Thanks

Regards Mario

[stefan_grube]

Look here:

https://websmp107.sap-ag.de/operationsNWpi71

[former_member181985]

Hi Mario,

>R/3 sends a request via RFC communication channel and receives the response of the mapping?.

Using BPM this should be possilbe( though performance comes into picture).

RFC sender (R/3 system, Synchronous Fashion) --> SAP XI/PI

In BPM

Receive Step (Open S/A bridge mode) --> Transformation (which points to mapping) --> Send Step (Close S/A bridge Mode)

Then mapping will have RFC request message as sender (on source side) and RFC response message type as receiver (on target side). Do your logic according to the business requirement.

In ID,

1) Sender Agreement with associated RFC sender channel.

2) Receiver Determination (sender R/3 Business system --> to IP Business system )

3) Interface determination (BPMs abstract interface for RFC request message, No Interface mapping)

4) No receiver agreement.

Note: You can also acheive this, without a transformation step (to improver performance) in BPM....

Let me know if you need further info...:)

Regards,

Praveen Gujjeti.

Edited by: Praveen Gujjeti on May 31, 2010 8:44 PM

Edited by: Praveen Gujjeti on May 31, 2010 8:46 PM

[former_member200962]

R/3 sends a request via RFC communication channel and receives the response of the mapping?.

SAP R3 <> XI/ PI <> SAP R3 .....just the mapping happens in XI/ PI.....do we really need a BPM for this?

Thanks,

Abhishek.

[former_member181985]

>SAP R3 <> XI/ PI <> SAP R3 .....just the mapping happens in XI/ PI.....do we really need a BPM for this?

I know this is not required, but the subject of Mario indicates he exactly needs this requirement. And looking at his points, I feel he knows PI pretty well. I am just providing the possibility.

@Mario, would you like share us why this special requirement..

Regards,

Praveen Gujjeti.

Edited by: Praveen Gujjeti on May 31, 2010 9:18 PM

[former_member200962]

If at all you need to pass this data through XI....the same R3 system will act as your Sender and receiver....if using PROXY, then add your Message/ Service Interfaces accordingly (source, target).

Regards,

Abhishek.

[Former Member]

R/3 is sender and receiver.

Nothing special...

[Former Member]

@Andre,

does this really work with a sync. RFC?

Regards

Mario