IBP transporting changes

[aparna_ranganathan]

Hello All , 

Couple of basic questions about transporting changes from IBP dev to prod environment 

1. Should we create an OSS note to create a transport route everytime a planning area related change has to be moved from dev to prod or is it a one time activity ? 

2. For non- planning area related changes in IBP , how do we transport changes ? The same export software collection and import in target ? 

Please advice 

Thanks

Aparna 

[vincentverheyen · Accepted solution]

Hi @aparnau .

1. There is no need to create an OSS note / SAP Case every time you want to export a change from an IBP Dev/Test system into your IBP Production system. Setting up the transport route is a one time activity. There is no need to reach out to SAP subsequently.

2. Whether or not they are Planning Area related changes, you can move them together in 1 Software Collection, or split them into different/multiple Software Collections according to your preference. This is done in the IBP web-UI app 'Export Software Collection'. You can simply 'Add Items' of any 'Type' to a Software Collection; and in case you only want to export this item, or a few items only, then simply select the item(s) subsequently and 'Add to Hotfix'. Subsequently, one can export only the Hotfix. Then open the target (in your case IBP Production) tenant/system, and via the web-UI app 'Import Collection' you can complete the Import. As I am sure you are aware, in case these are Planning Area-related changes, what is left to do is to activate the Planning Area in the Production tenant (outside business hours / during a window agreed upon with your customer), to effectuate the changes.

I hope this helped.

Kind regards,
Vincent Verheyen