IBP Landscape

[rcordeiro_com]

Dear IBP community, what is the best way to work in IBP development system, regarding PA (Planning area) avoiding wrong configurations in production ? Similar in ECC when we have 3 clients, one for Configuration, other sand box and ABAP one.

The app Export Software Collection will be use.

Using 3 PAs one PA1 for functional and test configuration, one PA2 to integration and the PA3 to consolidate the correct configuration tested from PA1 and PA2.

1 - The PA3 only be disponible when we need to configure and transport already tested configuration in PA 1 or PA2. Access control will restrict the access to PA3 preserving its integrity . When we need to transport IBP objects PA dependent we must transport the whole PA3.

2 - The IBP objects that is not PA dependent will be transport alone, to prodction without transport the whole PA3.

3 - The PA1 and PA2 will be refresh with a PA3 copy and data load when necessary .

Is this the right way to work in DEV IBP system ?

Have anyone other suggestion to work with PAs with security avoiding error in the PA3, configuration Planning Area wich will be transport to IBP production ?

[former_member194529 · Accepted solution]

Hi Rodrigo,

There is no "right way" of performing such developments.

In general, it is more common that IBP customers use the DEV/QA systems for development on a PA X and then transport the PA X to PROD when it is ready for use.

However, if you prefer to make developments on a PA and then copy everything to a new PA when is ready, it is also a possibility, although not the most used approach.

You need to keep in mind that some business catalogs in the WEB UI does not give you the possibility of restricting WRITE access on a PA basis.

For instance, you can't allow an administrator to have WRITE access to delete the PA1 in the Planning Areas app but not be able to delete the PA2 on the same app.

Best,

Ivan