Skip to Content
Jan 21, 2020 at 09:44 AM

MDG-F - Best Practice for Accounts and Editions



we are using yearly Editions (01.01. - 31.12.) with ad-hoc replication after final approval of the Change Request. At the moment, we have two open editions 2019 (01.01.2019-31.12.2019) and 2020 (01.01.2020-31.12.9999).

This seems to be cause problems with Accounts because of the relation between the two entities (ACCOUNT and ACCCCDET). For example, I change an existing Account A-Segment which is valid 01.01.2019 till 31.12.9999 and choose the new edition 2020. This will create a new timeslice for 2020 and restrict the other timeslice to 31.12.2019. The Account A-Segment has two timeslices now. Then, I search for an Account B-Segment which is also valid 01.01.2019 till 31.12.9999 and change it. MDG-F will automatically use the old edition 2019 and no edition popup appears. After the approval of the Account B-Segment Change Request, no replication will take place - probably because the B-Segment with timeslice 2019 belongs to A-Segment with timeslice 2019, which is not valid anymore.

If I set the edition 2019 to Mark for Release, I cannot even edit the B-Segment because MDG-F says no editions available. I would expect to get the Change Request Type and Edition popup when I click edit on a B-Segment, as I get it with A-Segments.

So what is the best practice to use Editions with time-independent objects like Accounts?