Material Archiving by SARA

[Former Member]

Hi all.

I have done the first steps for archiving material in SARA(customizing and write). Jobs in job log are finished successfully.

I used MM_MATNR object and everything seems OK. But in write step, in Archive selection, there is no file to choose like below:

What is wrong with it?

Can anyone help me?

Regards.

Mona

[JL23 · Accepted solution]

There must be something special with your system, can it be that you are doing Self Service procurement where you have master data synchronization with the SRM add-on

[Former Member · Accepted solution]

Dear Jurgen,

Yes, you may be right. We have done some configurations in SRM. Now, where can I cancel the synchronization with the SRM ?

Regards.

Mona

[JL23 · Accepted solution]

I dont think that you want to stop synchronization for all just because of archiving one material.

Unfortunately I dont have a system like that, but I guess there is a table somewhere which has the link between the material master and the product master, probably the one which is bespoken in this discussion:

You should contact your colleague who maintains such catalogs, he probably knows as well how to remove a allocation. Maybe it is as easy like clicking a trash can icon

[Former Member · Accepted solution]

There is not only one material to archive, there are a lot !

[Former Member]

Dear all,

Our ABAPer has debugged the error and  compared it with another similar system with the same technical characteristics.

The below checks are not done in the system working correctly, while in our system they are checked:

Also, this is an screenshot from the related program, where there is probably a problem:

Can anyone help me?

Regards.

Mona

[JL23]

Check the spool of each archiving job and the job log. from there you should usually find the reason why nothing was archived

[Former Member]

Yes. Spool shows that there is a problem, but which problem?

[JL23]

You had already posted this question and got an answer to it see

did you implement the note, that I mentioned?

This note is supposed to give a clearer information.

[Former Member]

Dear friend. I have still problem and it is not solved yet.

Yes i did it step by step.

[JL23]

After implementing OSS note 1329723 you should usually find a second message with details  next to this message.

Do you use EHS module in your company? if yes, then you should remove the assignment from the material to the substance.

If you do not use EHS, then you should check if you are using a BADI that does own checks for archiving of a material.

If that is not the case, then  you have only the option to have an ABAPer debugging the program to know in which situation this error is triggered.

Then you have to contact SAP to get this included into the error like I did it, as OSS note 1329723 was created after my call.

[Former Member]

dear friend.

For OSS note 1329723 I face this message:

"Can Not be Implemented"

[JL23]

what is your release? the note is valid from 500 to 604

do you use EHS?

[Former Member]

I think it is 702.

[JL23]

702 is not an application release, this is a basis release.

In system > status...

you have to click the detail icon for component version, and there you have to scroll to find SAP_APPL

[Former Member]

So it is 700.

[JL23]

I am sorry I do not know such a release. Maybe something new, maybe again with the same old errors, you have to call SAP Support.

[Former Member]

Maybe I did not find your answer correctly. Please check image below:

[Former Member]

Hey I made a mistake. It is 605.

[JL23]

in that case I expect that the note is already there. You can check this.

Go to SE37 and enter C106M1_SPECIFICATION_MATNR_USE and display the code.

if you find the note number 1329723 somewhere in there in the coding, then it is already applied.

In  any case you can only determine the root cause by debugging, and you can only get more information into the log when SAP does a change to the coding, hence you have to contact them

[Former Member]

Yes it is repeated there several times.

[JL23]

then you should have a second message in the archiving log that explains this message in more detail, in case it is an EHS related issue.

if you dont use EHS, then it might have another reason which can only be found by debugging

[Former Member]

What is EHS?

[JL23]

Environment, Health and Safety module SAP Environment, Health, and Safety Management (SAP EHS Management) – SAP Help Portal Page

[Former Member]

If you are getting an Error message "Other dependent data exists" while archiving materiala then you have to implement note 688297, if you are in higher relaease then there is a possibility that this message can also be raised by any implementation of the BAdI BADI_MM_MATNR, so please check all your active implementations. For your own implementations you should use the note 619015 to get specific check error messages instead message "Error message other dependent data exisits..

[Former Member]

No we are not using EHS.

[Former Member]

Dear Manjunath,

These notes and Function modules are related to other older release. But our release is 605 and it is included in the mentioned function module by itself.

[Former Member]

If that is the case then you need to debug the FM or may raise an oss to SAP.

[Former Member]

Dear Jurgen,

Here is debugging of SE38 after executing MMREO050 :

[JL23]

Not sure what you want tell me with that screen shot. I can just see that it came successful back from an enhancement.

[Former Member]

Dear Manjunath,

Our ABAPer checked the problem, the problem is raised from BAdI BADI_MM_MATNR. Now, which sap note we should implement?

[JL23]

I dont have this BAdI in my system. Your ABAPer has to debug again and need to look at the coding in the BAdI to know what is checked that causes finally the message 125