Skip to Content

PI 7.0 EhP2 - multiple ID objects under same name

Hello experts,

I'm facing a strange behavior of a PI 7.0 EhP2 server (XD2) and would like your opinion on how to solve it.

We have 2 different systems in this same box (GRC NFe - client 100, and the PI itself - client 001).

XD2 box is a copy of another server (PID) with same structure (GRC 100 and PI 001).

Basis team needed to change the XD2 GRC NFe business system name after the client copy, from PID_100 to XD2_100.

Now, working on new environment XD2, when I imported XD2_100 from SLD to ID, it appears duplicated and the existing objects were also multiplicated.

Also, the other existing objects (parties and their business services) were affected:

When I try to remove a repeated object, it takes all the other copies of the same object away at same time and when importing/creating it again, all others come again.

As we had to set some routing rules in receiver determinations, the muliple objects make the rule be attended more than once, and therefore we fall into No Receiver Could Be Determined error.

Does anyone have any sugestion on how to solve this or where to check?

Tks a lot guys!

Rafael Vieira.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 29, 2013 at 07:28 AM

    Hello Rafael,

    If I remember correctly, SAP recommends strongly to not install any other systems on the PI server except PI itself. So it would probably be a good idea to install the GRC on a different server.

    Have you checked your CPACache (or XICache) after creating the new objects? Do they contain multiple entries, too? How is your SLD? Do the old system IDs still exist there? What happens when you create new objects? Do they all appear simultaneously under all systems?

    This is to find out which object is causing the problem, the SLD entry, PI display or PI objects.

    Regards,

    Jörg

    Add a comment
    10|10000 characters needed characters exceeded

    • It was needed to revise all XI DB tables due to problem with primary key generation during system copy.

      Thread http://scn.sap.com/thread/1907095 helped, however it describes the XI tables to be revised superficially and the problem here required a deep analysis in order to identify every table with primary key issue.

      We have fixed:

      XI_DIRDATACHANNEL

      XI_DIRDATASERVICE

      XI_DIRKEYBINDING

      XI_DIRKEYCHANNEL

      XI_DIRKEYMAPKIDET

      XI_DIRKEYNAME

      XI_DIRKEYPARTY

      XI_DIRKEYSERVICE

      XI_DIRKEY_DIR_VIEW

      XI_DIRKEY_RD_RELAT

      XI_DIRTEXTHEAD

      XI_DIRTEXTSHORT

      XI_DIRDATAADMIN

      XI_DIRCACHEERRORS

      XI_RUNMAPPINGS

      XI_RUNPOOLSTAMP

      XI_REPCACHEEVENT

      XI_REPKEYNAME

      XI_REPKEYSWC

      XI_REPSWC_FIXEDDEF

      XI_REPTEXTSHORT

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.