M Records in P-Tables

[Former Member]

We are currently in technical go-live process

and are getting errors when trying to transport a infoobject to our production system.

The transport contains a version of an infoobject which removes a set of attributes from the active version in production.

The transport crashes with the message that MD has to be activated before conversion. The problem is that we already did a attribute change-run (to avoid this excact problem) before running the transport, however there are still records in the P-table with objvers=M.

No matter what we have tried we can't get this MD activated (includes running attribute change-run, tests from RSRV etc). We just tried to reload all MD

to see if an update of the P-table and a new attribute change-run would solve the problem but the M-records are still available.

Does anyone have an idear on how to get the M-records

of the P-tables either activated in a normal way or alternativly removed or changed to vers A.

Regards

/Frank

[Former Member]

What is Mversion, We also get a message do we activate M-versiion while fixing jobs what is it. Please help

[Former Member]

Hi

When ever You load masterdata to versions will exists - an A version and a M version (see in the field objvers of the infoobjects P-table). The A version of the masterdata are the active version - that is the masterdata you will be able to see when running your queries etc. The M version is the updated masterdata (the new stuff that you just loaded). The new masterdata in written with objvers value M in the md tables and are NOT visible in any of your queries etc, until you have activated the masterdata. Once You run an attribute change run (if You have aggregates in your infoproviders where the md object is used) or a normal masterdata activation from the context menu the M version is translated to the A version and thereby overwriting the old masterdata with the new You just loaded.

Problem is that some times the activation dosn't work for several reasons and You then have to follow the instruction given in this thread.

Regards

/Mads

[Former Member]

I had the issue twice.

Firt time : The master data was time dependant, with overlapping period and the load (infopackage settings) was done package by package instead of globally on all records. As the overlapping records were in 2 different packages, M version have been created and the activation failed (with no log) so M records where always in the P table. I've realized that you are mentionning a P table so not time dependant, but maybe you have the same kind of issue (conflict between 2 packages). In the Infopackage I would choose "load only PSA then subsequently data target". This way if master data are not consistent, no M version will be created and you'll see the inconsistency in the log. However I had to delete first all master data (from rsa1 - infoobject - delete master data). Then load with option specified above. The activation worked fine.

Second issue was solved by SAP with little explaination. Just know that they have used Function module RSDDS_CHANGE_CHA_MAINTAINI_CHABASNM <name of the infoobject>

I_RNSID -1

comment from SAP on same issue : "whenever there is any modification in the Master data of an infoobject, an entry is created in the table RSDDCHNGPROT (Table with InfoObject whose master table has been changed) with CNSID=0. Any other entry for which CNSID>0 is absolete.

During the Master data activation / Changerun occurs, it reads the table RSDDCHNGPROT where CHSID=0 and tries to list the infoobjects for which changerun has to be carried out. Upon successful activation of the Master data, the entry in the table is deleted."

good luck