MDG: Can I replicate and overwrite Analysis Time frame of a cost center?

[crodv]

Hi all,

I have the following problem: One cost center fails to replicate from MDG to ECC with error "Change interval must be on posting period limit" - I noticed that the editions dates in MDG do not match the Analysis time frame of the same cost center in ECC, there is a lot of discrepancies and overlaps, which makes me think this is the root cause of the problem.

I know I can manually change the analysis time frames in ECC, however in this case there are so many different periods and discrepancies that I think it would be better to just replicate from MDG and overwrite whatever discrepancies are in ECC - is this possible? If not, what would be the best approach to sync MDG and ECC for this cost center?

Thanks.

[former_member360870 · Accepted solution]

Hi Carlos Rodriguez,

thank you for the information.

IDOC replication is supported in general, so you can use it, that should be not a problem. However, from MDG-F perspective we are only responsible for the outbound, but for the inbound the receiver application is responsible in case of IDOC replication

I assume that the error KS028 appears during the inbound of the IDOC. In that case of the data are as intended in the outbound IDOC and the error appears during the inbound of the IDOC, than the reported error should belong to the receiver application, which shall be in this case CO-OM area, so I would recommend to contact your CO colleagues/consultant/community regarding the referenced inbound error to review it.

Despite if that you might also test the replication via SOA to check whether the same error appears during that.

Additional offtopic comment: You mentioned in your reply that you are using DRFOUT to replicate. In general it is not recommended to use DRFOUT to replicate data from MDG-F, but the recommendation is to trigger the replication from the NWBC/FIORI UI.

The background for it is that DRFOUT cannot handle properly the edition logic used in MDG-F. However, since for time-dependent master data always all data slices are replicated, usually there is no problem for such data sending by DRFOUT, but still please consider that the official recommendation is to trigger the replication from the UI.

Best regards,
Attila Toth
SAP Product Support

[former_member360870]

Hi Carlos Rodriguez,

in general regarding the replication of time-dependent master data from MDG-F to ECC/S4 please refer to the SAP Note 2106479.

The reported errors can have different root causes depending on the scenario you are using and the state of source and target data in MDG-F staging/target CSKS table, including that the error could be caused by some missing corrections in your system.

Could you please clarify whether you are using IDOC or SOA replication and the MDG_FND SP/release level of the MDG Hub and the same for SAP_APPL/SAP_FIN/S4CORE?

Best regards,
Attila Toth
SAP Product Support

[crodv]

Hi Attila,

Thanks for your reply - the note helps to understand some things. To answer your questions: we are using IDOC for replication, but when we get errors we usually run DRFOUT and based on the note we should not be using it - am I correct?

These are the versions of our MDG system:

MDG_FND: Release 806 SP 0001

S4CORE: Release 106 SP 0001

Thanks.