0% found this document useful (0 votes)
571 views2 pages

RMMMINIT - Protection Against Unintended Execution PDF

1) Initializing a posting period in SAP can lead to loss of information for book inventory balances for previous periods if done for a previous period. 2) Running report Z_DEL_HIST_ENTRIES is necessary to delete history entries after initializing to avoid inconsistencies. 3) Initializing a period should only be done after understanding the consequences, such as imprecise prior period values and potential loss of historical records.

Uploaded by

lovely lovely
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
571 views2 pages

RMMMINIT - Protection Against Unintended Execution PDF

1) Initializing a posting period in SAP can lead to loss of information for book inventory balances for previous periods if done for a previous period. 2) Running report Z_DEL_HIST_ENTRIES is necessary to delete history entries after initializing to avoid inconsistencies. 3) Initializing a period should only be done after understanding the consequences, such as imprecise prior period values and potential loss of historical records.

Uploaded by

lovely lovely
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SAP Note

    487381 - RMMMINIT: Protection Against Unintended Execution  


Version   27     Validity: 11.03.2014 - active   Language   English

Header Data
Released On 12.03.2014 [Link]
Release Status Released for Customer
Component LO-MD-MM Material Master
Priority Correction with high priority
Category Advance development

Symptom
When executing period closing with initialization, you receive a message stating that the program
cannot be launched.

Before you start period closing with initialization, you must be clear about the consequences of
using this function. This SAP Note describes the potential data inconsistencies that can arise if
the initialization is carried out in a productive system. The resulting inconsistencies are not the
result of a system error. Instead, they are the result of carrying out period closing with
initialization.

These inconsistencies can, therefore, be corrected only by chargeable remote consulting


because period closing must, as a rule, no longer be started with initialization in
releases higher than Release 4.5.

Other Terms
MMPI, PIINKON, MMINKON, RMMMINIT, MMINKONH, history records, MARDH, MBEWH, MM016, MM 016

Reason and Prerequisites


In releases lower than Release 4.6C, SAP Note 369637 is a prerequisite.

Solution
In order to run period closing, you must define the parameter ID MMPI_READ_NOTE in the user
parameters using the current date in the form YYYYYMMDD (Y=Year, M = Month, D = Day).

If you need this additional security function beforehand, implement the attached correction
instructions and create the SET/GET parameter MMPI_READ_NOTE. The SET/GET parameter belongs to
development class MG and should have the following short text:
'Initializing periods: See SAP Note 487381'.
You should also change message MM(016):
'Follow the instructions in SAP Note 487381 before initializing'

The SAP System uses the period concept for stocks. Postings are updated precisely for each period in
the system. The book inventory balances for the current and previous periods are relevant for
posting. As of Release 4.5, the history concept for book inventory balances was implemented.
Note that initializing a posting period has the following effects on the period stocks:

l Initializing a posting period for a previous/any other posting period can lead to loss of
information for book inventory balances for previous periods! In this case, the book value of
the current posting period is used as the basis for the prior period value!

           If you want to continue working with this new posting period, you should also run the
attached report Z_DEL_HIST_ENTRIES to delete the history entries that are larger than or equal to
the new posting period.

l If you need to set the posting period back one period temporarily (and for a small number of
postings) in order to correct an error, (e.g. postings still have to be posted to a particular
period), you should initialize the posting period back to the old value to ensure that the prior
period values do not get lost (posting should be prohibited while  corrections are being made!).

           The prior period values / history records (as of Release 4. 5) for the materials posted
in this case are, however, imprecise!
           Report Z_DEL_HIST_ENTRIES should NOT be performed in this case

l If, however, the posting period is set back to a previous posting period and postings are made
during this time, all information about the book inventory for the previous periods will be
lost!

           As of Release 4.5a, you should implement the correction report Z_DEL_HIST_ENTRIES in
order to delete history records newer than the current posting period. If this is not done,
inconsistencies can arise when the history records are updated.
l Important!  If there are open physical inventory documents that have status "Paid" or for which
the "Freeze book inventory" indicator is set, you should discard them in case they relate to a
prior period or were created during what used to be the prior period. The inventory difference
to be posted is calculated using the current book value for the previous period and the book
quantity set in the inventory document (ISEG-BUCHM) and is not the same as the currently valid
book inventory for the previous period!

Validity
Software Component From Rel. To Rel. And Subsequent
SAP_APPL 45A 45B  

46A 46B  

46C 46C  

470 470  

500 500  

600 600  

602 602  

603 603  

604 604  

605 605  

606 606  

616 616  

617 617  

Correction Instructions
Correction Instructions

Software Component Valid from Valid to Number


SAP_APPL 45A 45B 363792
SAP_APPL 45A 46C 359320
SAP_APPL 46A 470 363793
SAP_APPL 500 604 739355
SAP_APPL 605 617 1042181

Support Packages & Patches


Support Packages

Software Component Release Support Package


SAP_APPL 45B SAPKH45B51
46B SAPKH46B38
46C SAPKH46C30

References
This document refers to:
SAP Notes
1645304   MMPI : Not All Tables Relevant for Stock are Initialized
1082841   MMPV: Prevent shifting to a future period by mistake
369637   Period closing program with initialization after Release 4.5
192571   Period closing - Number of records closed

This document is referenced by:


SAP Notes (4)
192571   Period closing - Number of records closed
369637   Period closing program with initialization after Release 4.5
1645304   MMPI : Not All Tables Relevant for Stock are Initialized
1082841   MMPV: Prevent shifting to a future period by mistake

You might also like