IFlow vs ICo transport over PO system landscape

[turmoll]

Hello,

I'm on SAP PO 7.4 SP11. We are using CTS+ for transport over SAP PO landscape.

To be up to date,  I have build IFlow  instead of ICos.  Actually, IFlow generated ICo.  Whatever.

I transported IB objects from SAP PO DEV to SAP PO QA using IB using Configuration Scenario  (CS) as container (kinda old school ).  In CS I enclosed both IFlow and "underlying" ICo and other objects:

I release both for CTS transport.

While activating I can see the warning:

And the linkage between IFlow and ICo is gone on SAP PO QA:

Is that expected behaviour?

Can we only configure and manage IFlows on SAP PO DEV and after transporting we need to maintain ICos  (not IFlows) e.g. maintenance of  MM/OM parameters  in IFlow on SAP PO DEV and in ICo in SAP PO QA ?

Regards,

Jakub

[nidhi_srivastava22]

Agreed with Brian.

I also implemented the same way as suggested by Brian and it worked perfectly fine.

Just you need to keep in mind that you select all the objects of the IFlow in the next step

Once imported to Quality, you just need to login through NWDS(URL for Quality) and you can see the Iflow. Deploy the same and you can then see your ICO in swing tool(ID).

Thanks,

Nidhi