Integration process from cache status 99 to new workflow template - issue

[Former Member]

Hi,

we have an integration process in the QA system that showed status 99 (message: locked by a user).

After activating it in SXI_CACHE a screen came up and told that there will be a new workflow template created.

Then it asked for deployment.

Seems we went not too far and missed to press the deployment button.

So now there is a new workflow template besides the old one (checked that in PFTC_DIS).

SXI_CACHE shows now the Int.Process with the new WSxxxxxx number but is missing ESR entries here.

How to handle this now to avoid any more inconsistencies?

A first activation of change list from Directory didn t help. Ok, expected that!

Idea is now (waiting for access to do that in QA) to do another change on the IP in ESR to get another cache update back to ABAP stack.

If this will not work we will import the IP from DEV again.

Or is this not the best way. Is there possibly another way to solve this issue?

And will there be other side effects now as the WSxxxx is then different to that one in DEV.

Any issues with another IP import from DEV with the same WSxxxxxx number as this is not used there currently?

Your help is really appreciated!

Best regards

Dirk

[Shabarish_Nair · Accepted solution]

as long as you have transported the IP from Dev to QA, you can force activate it in SXi_CACHE.

when it asks for deployment, go ahead and deploy it.

It will also be a good idea for you to do a complete cache refresh before you do the activation.

[Former Member · Accepted solution]

Hi Shabarish,

Thank you for the answer. This gave me some hope...

Did the activation an deployment. ESR link is back now.

And status 99...... but with a new error message.

>> For >namespace< >service interface< there is already a definition >abcd<

Is this probably related to the fact that we have two WS templates or any other issue related to this

procedure done here?

regards

Dirk