on 10-06-2015 10:11 AM
All,
I face a very strange issue in my message mapping.
On my 3 SAP PO systems, the Message Mapping is identical.
Both source and target structures are checked and OK.
When I use 1 and the same message on all 3 systems, my production deviates in the message mapping result.
I tested the message mapping separately and when I display the queue, the value is present.
But still, that value is not being displayed in the final XML coming out the message mapping.
Any clues or leads?
Thanks a lot
Dimitri
Hi Dimiti,
Have you changed the message mapping?, have you tried to refresh the CPA cache?, any issue on the cache monitoring?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On production all is OK. In the meantime we deleted the mapping on acceptance and wanted to import from production. Unfortunately, that fails.
When I import into acceptance, I get a message popup saying all is imported, but the objects are not visible.
I need to correct that first and make sure the mapping is back on acceptance.
After that, I will have a look again because the root cause needs to be found asap.
UPDATE
I performed a CPA cache refresh on our development system
FULL: HTTP 500 - internal server error
DELTA:
kind regards,
Dimitri
Just another thing as I already explained...
I take my Message Mapping and go to the test tab. Upload a message.
Check the queue of the target field
As you can see, the value (11223344) is there.
When I run the test and check the result, the field PatientId is not in the target structure.
To me, that is very strange.
I see the behavior above on the dev and acc system. The production system is OK.
Hi Dimitri,
If you are under PI dual installation, this note 1670123 - CPA Cache not updated with directory data - HTTP 500: Internal Server Error can be helpful in the cache refresh error.
Regards.
Hi,
I played around and I saw something. When I leave out the CopyValue function, it works!
But on production, this function is used in the mapping and it works fine. That is very strange.
UPDATE
I bounced into OSS note 2185824. That is an interesting one.
On production, the MESSAGING component deviates from the dev and acc system.
Now, I want to figure out what causes this. Probably an OSS note being applied on dev and acc.
I will check with the basis team and revert back as soon as I have new.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.