AAE not calling Message Mapping (using Integrated Configuration)

[Former Member]

Hi Guys...

AAE not calling Message Mapping (using Integrated Configuration) in my scenario Client Proxy to JDBC.

The mapping transformations are not happening. In JDBC Communication channel, the receiver payload still containing source values. means, message mapping not executing. I gave correct OM in ICo also.

Thanks in asdv...

[Former Member · Accepted solution]

Hi

AAE have few limitations, Please make sure the below points

1. we cannot configure additional communication scenarios

2. we can only use Integrated Configuration to set up communication scenarios where the message is only to be transferred within an Adapter Engine from a sender to a receiver adapter.

http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/69f88453070ea1e10000000a155369/content.htm

Thanks

Ramg

[Former Member · Accepted solution]

Thanks Ram,

I have simple doubt about mapping program calling. I have confgured the ICo and AAE settings as per standards in ECC and PI.

I configured SOAP sender with modules generateSysAck and ignoreDuplicate.

My scenario is: Client proxy to JDBC using AAE.

PI receiving proxy from ECC, not performing mapping and sending the source structure to receiver adapter.

I can see the source message content in target CC message content.

I don't know what I missed in the configuration...

Thanks,

RY

[VijayKonam]

You might have to use the SOAP sender adapter with XI protocol to get this working(if you are PI 7.1.1).

VJ

[Former Member]

Thanks VJ,

"Sender SOAP wth XI protocol" is the basic configuration. I did these steps earlier.

Experts,

Please suggest me...

Thanks,

RY

[Former Member]

Hi All,

we are having the same problem. The mapping step is not executed in the AAE when sending the proxy data to AAE.

The audit log in the receiver channel shows clearly the call to ithe operation mapping but the mapping is not getting executed.

any help or suggestions would be appreciated

Thanks,

Srini

[Former Member]

Hi All,

Now we observed that the Mapping is executing, and target JDBC table is updating as expected.

New observation is... The JDBC communication channel message content is showing source payload only instead of target payload. This should show the transformed values (target schema). I can't see this in CC Monitoring>MDT>Message Content-->Payload.

Even in RWB--> Message Monitoring --> Its same thing.

My doubt is, whether we missed any post installation steps or should apply patch...

Thanks for Ur time guys,

RY

[Former Member]

Hi,

I'm facing the same issue and I have tried to refresh cache, reactivate objects, etc, but no success, I haven't found a note that seem to fix my issue with my current landscape. I'm about to open a ticket for SAP to look at it....

Did you get a resolution to this problem? How did you fix it?

Any advise is greatly appreciated.

Thanks in advanced.

Gerardo.