Skip to Content
Done with Integration Process in Repository and imported into the Directory. Many times Integration Process (BPM) is not reflected in the Integration Directory. In these cases many are landed up with importing the Integration Process again in the Directory and also ending up with doing configuration for associated objects.  The concept behind this is after activating of the Integration Process an equivalent workflow definition is generated in the Integration Server. This workflow is however has not been activated. This problem can be avoided by use of Transaction Code SXI_CACHE. This blog explains how to activate the Integration Process, when it is not reflected in the Directory. Step 1: Go to Transaction Code: SXI_CACHE in XI Server. You can see following screen. imageStep 2: Following screen is displayed with list of all the Integration Process, which are all designed in the Repository/Directory.  image You can see the list of Integration Process configured. Here Service column shows the BPM imported in the Directory.  If you observe, there is one column called Return Code. It shows status of the Integration Process. Return code for the creation of the runtime version: •     0: The runtime version was created without errors. •     Not equal to 0: Errors occurred.  If it is not equal to Zero, then you need to activate the same. Otherwise it will not be reflected in the Directory.   Step 3: The following screen shows the IP which is having the Return Code as 99. If the return code 99 is displayed in the runtime cache for the IP, then you need to check conditions given in the IP are valid, Correlations are used/activated properly and then we need to activate the IP by clicking the Activate Button (Ctrl+F5) image Following screen appears after clicking the Activate Button. image Pressing the Activate Button once again, will lead into following screen. imageimage If the status bar in the screen shows with checked flag as above, then it is understood that runtime version for the IP is created.
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Hi,

    This issue was fixed in Sp13. In fact SAP has notes specifically addressing this issue even before SP13.

    Naveen

    (0) 

Leave a Reply