Revert custom changes in single integration flow of standard integration package?

[floriangu]

Hello,

we have copied a standard integration package to our own design workspace. Some changes to mappings have been done to the integration flows. This means that the status of these flows was changed to "modified", hence these integration flows do not receive updates anymore.

The changes of one of the integration flows has become obsolete. Is there any way to revert back all custom changes so that this single integration flow gets back into its initial status "unmodified" and therefore receives official updates again?

Afaik it is not possible just to copy single integration flow from a standard package into the already existing package in the design workspace again.

What would be the recommended approach here as we of course do not want to loose changes already applied to other flows?

Thank you!

[apu_das2]

As the package is already copied in your workspace so it will not be copied again unless you overwrite. But you can always copy the same package in your workspace just putting some suffix so that workspace will treat this as a new package i.e. old_package_v2.

From this newly copied package, you can work with the particular iFlow you want to redeploy with latest official changes.

It is a better approach than downloading the same in local and deploying through Eclipse.

Thanks,

Apu

[floriangu]

Hello,

thank you for your reply and information.

In this context I am also wondering about a best-practice approach on how to handle any updates of standard content when an integration flow is modified (even if it is just small configuration change). In case of modification the integration flow will not receive any further updates. I see a risk here, if there are bugfixes applied to the standard content.

Any recommendation here?

Thank you.

[apu_das2]

Hi Florian,

As per current process, no update will be pushed once you will edit any standard content. It doesn't matter how small the change is.

SAP allows only configuration on the standard content to receive update.

Thanks,

Apu