topic Re: Material Master Creation Date in Application Development and Automation Discussions

Material Master Creation Date

Former Member — Mon, 01 Oct 2007 13:49:31 GMT

Hi,

I am currently looking into material master data migration, one of the requirement is to have the "original" creation date from the legacy system be retained in the new system.

Does anyone know how can this be done? Are we allowed to direct change the creation date in the material master to reflect the "original" creation date?

Regards,

Norman

Re: Material Master Creation Date

Former Member — Mon, 01 Oct 2007 13:51:07 GMT

HI,

Creation datr will come as SY-DATUM, but if you can provide the creation date than it may take in the Program

Regards

Sudheer

Re: Material Master Creation Date

Former Member — Mon, 01 Oct 2007 14:05:06 GMT

Understand that. However, to do so, I will need to update the MARA table directly via a program. Any idea is this the right thing to do? Will SAP still support?

Regards,

Norman

Re: Material Master Creation Date

Former Member — Mon, 01 Oct 2007 14:49:34 GMT

Yes, You can

Generally when we uploading the data using Migration program, if you have some specific date as CREATION date we will pass that data in the fiel other wise better to hardcode as Sy-datum for that MARA-ERSDA field

which will not change once it is entered in table

change date will be very oftenmly changed for a material.

Regards

Anji

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 03:38:26 GMT

Hi Anji,

I am thinking of either using the BAPI "BAPI_MATERIAL_SAVEDATA" or create a BTC program to migrate material masters. However, both method does not allow me to change ERSDA. The only way I can think of it to have another program that directly update the table MARA-ERSDA.

My worry is that whether SAP will still support if I direct update a standard table. In addition, what are the implication if I update a standard table directly.

Regards,

Norman

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 03:41:10 GMT

Hi,

It is not advisable to do a direct table update...

I would suggest the following..

Append a new field ZERSDA in the table MARA.

Then update the mara table with the bapi extensions which is available in the BAPI BAPI_MATERIAL_SAVEDATA..

Thanks

Naren

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 03:58:30 GMT

This was one of my other options. To use append structure+field to keep the date. Another option was to find any unless field in the material master and keep the creation date there.

Just that there are existing programs that uses ERSDA for reporting purposes. Guess I have to change all of them.

Anyway, thanks for the advice.

Regards,

Norman

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 04:01:05 GMT

Hi,

That is a very good idea..to make use of an existing field which is not being used..

Thanks

Naren

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 04:06:13 GMT

Hi Naren,

the only problem with this is that the existing field is open for changes. Which might not be a good idea. User might accidently change it or delete it without knowing.

What I am thinking of, if I use an existing field, is to change the field to display only. No changes allowed. At least, with this, user is still able to view the original creation date via MM01/02/03.

Regards,

Norman

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 04:09:50 GMT

Hi,

I believe this can be done in the configuration to disable the field for input..

In SPRO...In the field selection group in the material master config..You can make this display only..

Please check this with your MM functional consultant..

Sorry..I don't have the system with me rightnow..Otherwise..I can tell you where exactly to do it in SPRO..

Thanks

Naren

Re: Material Master Creation Date

Former Member — Tue, 02 Oct 2007 15:37:24 GMT

Hi Naren,

yes this can be done via config (SPRO). I do know where the config is.

Just wanted to share what my work around solution is.

Regards,

Norman