Multiple ECC to one PI architecture

[#1]

Hi SDN Experts,

We are in a test phase of a project and facing some architectural issue.

My Client XX has 2 ECC tracks and already one project (P1) with few interfaces gone live.

Existing project (P1) landscape is:

PR1 (Dev) -> PR2 (PPD) ->PR3 (Prod)

For the new project (R1), client has asked to use the new ECC track:

ECC1 (Dev) -> ECC2(Test)-> PR3 (Prod)

PI landscape:

PIB (Dev) -> PIC (PPD) -> PID (Prod)

For project P1, Live interfaces in PI (w.r.t. ECC) use the following BSu2019s:

BS_ECC_PR1_DEV -> BS_ECC_PR2_PPD -> BS_ECC_PR3_PRD

Project R1 interfaces in PI (w.r.t. ECC) uses the following BSu2019s:

BS_ECC1_DEV -> BS_ECC2_PPD -> BS_ECC_PR3_PRD

Points to note:

1)The rule here is once a project goes live, the ABAP development moves to P1 track and so after goe live for any change request or defect of R1 we need to connect PIB system to PR system( P1 project business system).

2)We are in test phase of project R1. Currently all interfaces are configured with EERP system and not a single interface of project R1 has ID configured with PR system.

This is little tricky to understood, i am not sure if i have explained it correctly.

I hope some of you might have already experienced such kind of issue, so i request you to spend some of your valuable time and let me know what is the best way to solve this considering the following:-

1) For all project the final ECC production system is same and a single business system (BS_ECC_PR3_PRD) needs to be used.

2) Project P1 is already live with 10 interfaces.

3) Project R1 is in end of test phase and we have more than 100 interface (with IDoc, proxy etc)

4) Minimum effort and without touching existing live interfaces.

Thanks !

Cheers

Biplab Das

Edited by: biplab das on Aug 9, 2011 9:29 PM

[Former Member]

We decided to duplicate the configuration objects.

Thanks for your input.