cancel
Showing results for 
Search instead for 
Did you mean: 

Idoc Meta Data Issue in PI

Former Member
0 Kudos

Hello Experts,

We are using PI 7.3 dual stack version and have an issue with idoc to idoc scenario. In this scenario, we have several clients for this ECC system, one original while the other for testing purpose.

Testing scenario for your reference -

Client X - Original client of ECC

Client Y - Testing client of ECC

Idoc HRMD_A07 was recently extended and triggered from both the mentioned clients

During testing, data looks perfect in PI when received from Client X but the few fields are missing in the xml when the idoc is received from Client Y. The idocs in both the systems are created correctly and there are no issue with the same.

Our initial instinct was to do the metadata refresh but it seem to have worked for Client X but not from Client Y.

Upon further checking, we found that the meta data refresh is always done from Client X and we could not find a way to replicate this action for Client Y.

Any suggestions to fix this issue ?

Accepted Solutions (0)

Answers (2)

Answers (2)

PriyankaAnagani
Active Contributor
0 Kudos

Hi Mradul,

If you are using a dual stack system, maintain the idx1 ports for both Client X and Client Y and in idx2 load the metadata using the respective port.

If you are using a single stack, in the Metadata monitor, load the metadata using the respective Idoc sender communication channel for each client.

Regards,

Priyanka

Former Member
0 Kudos

Hi Priyanka,

While loading meta data, only source port is asked and not the client. So by default the loading happens from Client X. Is there a way that this can be changed ?

Regards,

Mradul

PriyankaAnagani
Active Contributor
0 Kudos

While loading the metadata it will ask you only the port.

But, you can have 2 separate ports created in idx1 i.e. PORTX for client X and PORTY for client Y. Then, in idx2 you can load the metadata two times using PORTX & PORTY.

Regards,

Priyanka

Former Member
0 Kudos

We have two ports but when i am selecting the client specific port, an error pops up - No RFC Destination is maintained for SAPABC_Y, ABC being the ECC system. Just to add, we do have a RFC destination for this client.

PriyankaAnagani
Active Contributor
0 Kudos

Open the port "SAPABC_Y" in idx1  and see what is the name of the RFC destination.

In SM59 of your PI system, make sure you've the RFC destination maintained with the same name pointing to client Y.

---Priyanka

former_member186851
Active Contributor
0 Kudos