MM Posting Period Keeps Reverting Back

[former_member217601]

Dear Experts,

I have a weird situation that just happen at my customer, where the posting period always going back to last month for a specific company code.

Let say, this morning I check MMRV for this company code A, the current period is 06 2014.

But at noon, when I check MMRV for this company code A, the current period is going back to 05 2014.

So I close and open the period MMPV to 06 2014, but at afternoon, it is back again to 05 2014.

Again and again, like it is on interval background or somekind.

This thing does not happen to other company codes, B or C.

This is new installation for UAT. I have not check other client number, I'll update this later.

Is there somekind of background job for this? How to check this?

Thank you.

[Former Member · Accepted solution]

Hi,

Do check in Table TBTCP in field "PROGNAME"  with program name SAPFM06P.

Does if any Job exists.

You Check the changes in AUT10 also based on T-code MMPV.

[Former Member]

Dear Consultant,

Immediatly write a OSSNote to SAP .

The same behaviour haappen to me also .

What is ur Version.

Give all details to sap then they will check and revert back with SAP Notes.

There is problem in the Current operating system from SAP.

Thsi is for your kind information and necessary confirmation.

Regards

kishore Edagali

Bhutan

[former_member217601]

I was wrong, the posting date is back again..

[former_member183424]

Check, who is the user BAYU ? Ask the user what he did on the date 04.07.2014 ?

[former_member217601]

That is me. If you would compare to my previous reply on Jul 7, the date and time is the same.

[former_member183424]

Strange behavior. If you are sure that there are no custom development, then I suggest please contact SAP regarding this. Raise a OSS ticket to SAP. Let them handle the scenario.

[Oscar_DC]

Hi,

Were you able to fix this? I just discovered I've the exact same issue as you.

The MM period for one of my company codes just keeps magically reverting back, and I'm not sure why ...

Thanks!

[former_member217601]

Hi All,

On my last effort, I do MMPI again and set the period back to 05, and then do MMPV until period 07.

So far, the result has been satisfactory, no unexpected change, and period has been staying on.

So I assume the problem is solved.

Thanks for all the helps, guys!

[former_member183424]

How can system solve it automatically ?

I am quite sure, something development running background in your system.

[former_member217601]

I am sure I've checked everything, but no clue.

The only difference I see is in the table MARV (ccode 2000):

[former_member183424]

I assume how this field can be change ?

Press F1 on this field, it shows "1st Period After 4.6C Upgrade"

In My system it is showing

And it is showing the period from when my organization has implemented SAP for this company code.

But it shows 2014 - 6 for your case.

[Former Member]

If the result are satisfactory and your not facing any issue now, there is no meaning to hold the query.

You can very well close the thread

[former_member217601]

Hi Guys,

Do MM posting period have table or history table?

[former_member217601]

Oh yes, MARV. But do does it have chronological/history table?

[Former Member]

Hi,

The table MARV where all the config posting periods are saved.

Goto T-code AUT10 and select switch std mode. there enter table MARV in field table and execute the report for a given period you will find the changes.

[former_member183424]

Also try to find the changes log in t-code OMSY.

[former_member217601]

Hi All, thanks for your hints.

I have checked the SM37 but no job for RMMMINIT from any user.

This is testing client, and after a few days I monitored with no change, today the posting date is going back again.

I'm still curious, but hopefuly it will not happen in production later.

Is it possible this effected by other module such as FI?

[JL23]

no, no other module.

you can try to check in transaction STAD which user executed MMPI transaction.

Further read OSS note 487381 - RMMMINIT: Protection Against Unintended Execution

which actually explains that a user has to have a parameter MMPI_READ_NOTE set in his user profile to execute it. So it should be possible to find users having this parameter set in their parameters

[former_member217601]

Hi Mallinath Bheemrao Patil, there was no entry for that selection.

Hi Jürgen L, unfortunately the log is not active. Is it suppose to be active?

[Former Member]

You mean there were no Jobs on that program?

Does you see the behavior happening in production or another system?

[JL23]

In my IDES the log is as well not active, but in the production and QA systems it is. And your current problem is actually givning the answer to this question.

If it is a job instead a manual change then go SM37 enter a star * in the job name and the  user field

enter a date range that includes the days where you saw the period changing, enter the ABAP RMMMINIT and execute. this way you should see all jobs that turn the period back (honestly I have never seen a job for this activity)

If you have no technial history option to find the root cause then just send an email to all IT folks or place a system message with SM02 to ask this question. Maybe there is some miscommunication in project and one does not want that the priod closure is done as he is not finished with his tests.

[JL23]

Execute transaction SCU3, enter table MARV, set the radio button to tables and execute.

You should see the change history with old and new values along with the user ID who made the changes