Skip to Content
avatar image
Former Member

BPM: Correlation check

Hi All,

I am developing one BPM:

Receive1 -> Send1 -> Receive2

I am using correlation between Send1 (Cremas Idoc) and Receive2 (ALEAUDIT response), for the testing purpose i have hardcoded one value inside the Cremas-> DOCNUM (EDI_DC40) for instance "001" and after that i am triggering my Scenario, the message is flowing to SAP system and the hardcoded value gets replicated in the table IDXRCVPOR (unders SNDLAD field) in PI system

So table entry in PI table IDXRCVPOR:


XXX                 001

And while getting the Reponse ALEAUDIT Idoc message (from SAP to my BPM), i am doing the RFCLOOKUP in PI to change the idoc number field : (/ALEAUD01/IDOC/E1ADHDR/E1STATE/DOCNUM) ) which will be "XXX" with the SNDLAD field value "01" (under the table IDXRCVPOR) so that my corelation gets completed.

But this is not happening, my scenario is failing stating that the correlation does not exist, but i can see the response ALEAUDIT contains the "01" value (so my RFC lookup is sucessful) inside the DOCNUM field and the same filed i have used for my correlation?

so my doubt is when this correlation comes into picture?? Am i following the correct preocedure? Please help


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 26, 2012 at 01:25 PM

    Have you activated the correlation by assigning it to block and send step? Have you used the correlation in receive step? Have you defined the correlation correctly in correlation editor?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi All,

      I have found something new, i am sending the CREMAS Idoc to receiver SAP system and i have mapped the field DOCNUM (under EDI_DC40) with a unique value (say "XXX" evey time i run the scenario unique value gets generated in this field).

      And after posting the idoc in SAP system, i am generating an ALEAUDIT idoc from receiver SAP system.

      So when i am viewing the Ack idoc in SAP system after generating the ack using RBDSATE, i can see PI's Idoc number under the field E1STATE-DOCNUM but when the very same ack idoc comes to PI, the E1STATE-DOCNUM filed is getting changed and reflecting the unique number ("XXX") which i have generated in the first flow under the original CREMAS idoc in field DOCNUM (EDI_DC40).

      So wanted to know where exactly this conversion is happening?

      Note: Currently i am not using any mapping for the ack idoc, means the ack idoc comes into PI and failed at ID level.