cancel
Showing results for 
Search instead for 
Did you mean: 

Multi country roll out issue...

prasad_ulagappan2
Contributor
0 Kudos

Hi All,

This is regarding multi country roll out project. We are already in live for a country (Say A) and about to go live to other countries by this year end (Say B and C). Suppose if we have some interfaces which are comman for A and B country (with few enhancement for country B), how shall we go with this? for example if interface int 1 is already in country A Production, in the mean time we will be working on the same interface for country B in Dev. Suppose if we get a CR for the same interface, hw do we need to maintain the version for the interface "int 1*?

Regards

Prasad U

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member206760
Active Contributor
0 Kudos

Prasad,

1. your rseuable datatypes and message types should go into a sperate resuable software component

2. now suppose country A has already used a data type ...transfer it to the reusable SWC now again if country B wants the same kindo of data type..it will use it and may be add some 2-3 fields extra that it requires. now this can be done by defining a dependency between SWC for Country B and resuable SWC

3. same way u can reuse message type by maintaining it in the same reusable SWC

4. Message interfaes cannot be reused . u will have to create then country specific say materialmaster_outAs_NewZealand...this is because if you try to reusue then it will give an error in configuration that object still exists

5.messsage maping and interface mapping should also be created country specific like MM_materialmaster_NZ so that you can make country specific changes there..

do not make country specific changes in the same mapping else it will create a problem like u are mentioning that if the same interface is in prod and u are changing its mapping in dev

6. obviously the configuration scenario you will create country specific like CS_Materialmaster_NZ

This will help

Former Member
0 Kudos

Hi tarang,

The solution given by is ok..but here scenario is little different !!!

suppose Interface 1 is already live in country A and this is a Global interface ( means it should work for all country)

But when this interface ran for country B,say.. they realized some enhancement is required to get it work in B.....

So now enhancement is done....the interface tested successfuy in D , for further testing it went to Q.

Now suppose a defect has come in production for country A for the same interface.

And also in the meantime they realized for Country C some more enhancement is required for the same interface.

So want to know how these 3 scenario can be handled in PI,

which one will be taken care first... the production defect or the enhancement for the same which is in Q for testing. for country B and new change for country C

if defect is taken care first... the mapping need to be reverted back to the version of production, so whatever enhancement done for country B will be lost.

And we can't take all together...since we are not sure... how the new enhancement will work in production....

Its little complex to understand... but need help from experts.....

former_member206760
Active Contributor
0 Kudos

what i can think of is ,

1. suppose u know that the global interface is in production and the mapping needs changes corresponding to say country B..then wat you can do is copy the mapping and name it as say TEMP_MAPPING_COUNTRYB

do the changes in this mapping and transport it to Q...test here also with this test mapping...

2. now suppose some change is required for the country which is always in production then you can make changes to the original mapping and transport it to prod...while parallely testing with temp mapping will also be going on(obviously one interface determination can have only one interface mapping so when u transport with interface mapping for country A..country B testing has to be on hold)

3. finally when u feel that the temp mapping is working ok ...implement the same changes to the original mapping and transport..

or else

create a seperate Message interface and Mapping for the country seperately ..wherein all the sender MI/receiver MI and Interface mapping all will be country specific...howver they might be pointing to the same table/file on source/target as all other countries ....

Edited by: Tarang Shah on Apr 3, 2009 3:03 PM