Dear experts,
I have a scenario where an SAP system (ECC) sends a fully custom IDoc through PI (7.3) to another SAP system (SID: SRD, this too an ECC5). IDoc adapter used on sender and receiver are in IS (not AAE)
IDocs are being sent out from SAP (Source) successfully, and PI receives the message. Source and Target IDoc types are different and mapping is done in message mapping.
The messages in MONI has overall and outb status 'Successful'. But Ack status column has green question mark (still awaiting ack)
IDX5 records also looks good. I do not see any trace of error in PI
SM58 in PI and receiver SAP do not show any error.
But the problem is, I am not getting the IDocs in the receiver SAP system 😔
The receiver SAP has all configurations for Inbound IDocs (message type, function module, direction, function assigning, process code, pratner profile, etc)
From WE19, when I test the IDoc type with
sender system as PI logicla system
sender port as SAP<SID> of PI
Receiver system as logical system (of current client) of SRD
Receiver port as SAPSRD
and with some valid data in segments, the partner profile is identified successfully and IDoc gets posted successfully.
So I think the config for back end SAP is good.
In the IDoc mapping, I have mapped all components of EDI_DC40 segment from source IDoc (which may not be right as both are different idoc type) but in receiver IDoc adapter I have 'Apply control record values from Payload' Selected.
And in receiver agreement I haveheader mapping selected for Sender communication component and assigned communication component is PI business system.
As I don't see any error in PI and in receiver SAP system, I am not able to find why the IDocs are not reaching receiver SAP.
Can some one please guide me to find where the IDoc is stuck or errored?
In MONI, in IDocOutbound section, I can see the control records are getting mapped correctly.
But in same screen under payload ->MainDocument, I still see EDI_DC40 segment with original source IDoc control records aprt of payload.
Can that be an issue ? If so, how should avoid this in message mapping? All these are mandatory fields.
Any thoughts will be highly appreciated.
Thanks in anticipation.
Regards,
Mark