cancel
Showing results for 
Search instead for 
Did you mean: 

MDG-F Replication Timing

Former Member
0 Kudos

I am confused by the parameters (options) used in Edition and Change Request.

During Edition creation, there are three options we can pick and use to control as to when we want replication to occur.

option 1 - Manaully started after release of Edition

option 2 - On final approval of change request.

option 3 - Selected in each change request

However, during Change Request creation, it has only two option 1 and 2. Option 3 is not included there.

Then my question is - What option MDG-F will really go if I choose option 2 in Edition and choose option 1 in Change Request?

Would there be any document that shows the difference across these 3 options and configuration steps of each option?

Thanks, 

LUO

Accepted Solutions (1)

Accepted Solutions (1)

michael_theis
Active Contributor
0 Kudos

Hi Luo,

it is correct that there are three options while definining the edition. The part you miss is that the option you select for your edition surely has some impacts on the change request. This is best explained with some examples:

Edition A defines option 1 - manually start after release of edition.  Each CR that you create for this edition will use exactly this option. In other words, the related selection field of the replication will be read-only. You cannot distribute the data immediately after the release of the CR.

Edition B defines option 2 - on finall approval of CR. Each CR that you create for this edition exactly use this option. In other words, the related selection field of the replication will be read-only. You will always distribute the data immediately after the release of the CR.

Edition C defines option 3 - selected in each CR. Each CR that you create in this edition will have an enabled replication timing field. You can decide on the level of the CR, if you want to replicate the data of the CR immediately or after the release of the edition.

Best regards

Michael

Former Member
0 Kudos

Hi Michael,

Thanks for the informtion. That is useful and helpful. Just one more question for you. If so, then I came to realize that the choice given for either going with Option 1 or Option 2 in "Change Request Replication Timing" drop down is kind of loose if the change request is grouped into an Edition with option 1 or 2 already chosen in its "Edition replication timing".

End users who create CR must know about option 1 or 2 selected in Edition in which their CR should go because the replication timing option must stay exactly same in these two steps (Edition and CR).

Then Option 1 and 2 in Change Request apply to an Edition created with Option 3 in Edition replication timing only.

Correct?

Thanks,
Luo.

michael_theis
Active Contributor
0 Kudos

Hi Luo,

yes, that's correct.

The selection of 1 or 2 in the change request is only enabled if the edition uses Option 3. If the edition defines 1 or 2, the change request cannot change this setting.

Best regards

Michael

Former Member
0 Kudos

Hi Michael,

Thanks for confirming.

Then what is used to determine as to whether data distribution is immediate (ah-hoc for urgent request) or non-immediate (planned for future)? I thought "valid from" date in Edition is used to do this. In other words, if a change request is tied with an Edition A with Valid From date =January 1, 2015 (think of today=07/10/2014)  won't come into ECC until January 1 2015 regardless of option 1, 2, 3 we chose. I think i am still missing something. Please advise.

Thanks,

LUO

michael_theis
Active Contributor
0 Kudos

Hi Luo,

please see my replies above. Replication timing is bound first to the selected option within the edition and second (if the edition allows the same) to the selection within a CR.

Some outbound implementations contain a check whether the replication is valid or not - e.g. if your example refers to an account, replication is not valid due to the fact that the account master in SAP ECC is time independent. If it is a cost center, replication is valid, since cost centers support time dependent data in the backend.

Best regards

Michael

Former Member
0 Kudos

Hi Michael,

Thanks for the info. What ( as far as the reflection of desired master data change/create records in ECC is concerned) if the edition used in above (edition is valid from January 1 2015, contains GL/CC/PC change requests) has Option 1 - manually start after release of edition?

What if the edition do Option 2?

Thanks,

LUO

Former Member
0 Kudos

it is assumed that I have attempted to replicate. what will actually happen?

Former Member
0 Kudos

I have another question to Michael. Given what you've said above, I would think that given option 1 and 2 is good enough to satisfy the needs for data replication.  it can be dependent on release of edition (option 1) or be independent of edition (option 2).

Option 1 - manually start after release of edition

Option 2 - On final approval of change request.

then I became clueless about usage of Option 3 - Selected in each change request.  In which business situation should I use Option 3 as if this is chosen, uses still come down to pick option 1 or 2, why don't they make this call during edition create step?

Please help.

Thanks,

LUO

michael_theis
Active Contributor
0 Kudos

See http://scn.sap.com/thread/3588476 for a detailed example.

michael_theis
Active Contributor
0 Kudos

Hi Luo,

some customers I know use option 3 for the following business use case: In general data shall be replicated once the edition is released (option 1). Nevertheless it might be required that some adhoc changed need immediate replication (option 2).

Best regards

Michael

Former Member
0 Kudos

Hi Michael,

in the given case, why don't they make this decision as Edition is created using its option 1 or option 2? Instead they do option 3 during Edition create and then do option 1 or 2 during Change Request create? In my opinion, the same purpose can be served well during Edtion create by uisng option 1 or option 2. I don't quite understand the purpose of using Option 3.

Please. advise again.

LUO

michael_theis
Active Contributor
0 Kudos

Hello Luo,

please read my previous replies and explanations carefully! As said, some customers want to use both the edition based and CR based replication. That's why there is option 3.

Best regards

Michael


Former Member
0 Kudos

I see your point now that some customers don't like to be tied with the chosen option 1 or option 2 some one made during Edition create process and rather they want to make their own choise during CR create. That''s why this option 3 come into design. Correct?

Answers (0)