Skip to main content

MMPV_DATE_CHECK: Error occurred (SAP Note 1082841) how to solve

SAP Note 1082841 - MMPV/Close Periods : Prevent shifting to a future period by mistake

You must backup the database before executing following program or function in the Production system!

Symptom

When running MMPV/ Close Periods, prevent shifting to a future period by mistake (for example, a common mistake is running MMPV twice at the beginning of a month).

Other Terms

MMPV, MMPI, MARV, period roller, period shift, material ledger, MMPV_READ_NOTE, MMPV_DATE_CHECK, T001, PERIV

Reason and Prerequisites

In the event that MMPV is mistakenly executed twice at the beginning of a period, the active period could be shifted to a future period. As a consequence, system would accept goods movements with a posting date pointing to this wrong future period.

To revert wrong period shift and correct such posting errors is difficult, especially when Material Ledger is active.

Solution

This note provides a feature to prevent using MMPV to shift into a future period.  The future period is defined according to the fiscal year variant setting of the company code (T001-PERIV).  This feature is activated automatically after implementing this note (or if the note is included in a support package upgrade or a new release), and it works both with and without Material Ledger active.  By default, MMPV is allowed only if the new period is within 10 days away from the current date in the system.  Otherwise, an error will be displayed and no change will be made.

The default behavior can be changed in the following ways:

  • To disable this feature, it is suggested to enter a user parameter "MMPV_READ_NOTE" and set it to the current date in YYYYMMDD format (Y = year, M = month, D = day), with transaction SU3 > Parameters:
Get/Set parameter IDParameter Value
MMPV_READ_NOTE<current date, e.g. 20191231>

This will disable the feature on the specified date (e.g. "20191231" for December 31, 2019) and no date check will be done during MMPV.

  • To change the default number of days from 10 to a different value, it is suggested to add the following entry in table CKMLMVADMIN, with transaction SM30 > V_CKMLMVADMIN:
KKEYKDATA
MMPV_NUMBER_DAYS_ALLOWED <number of days, e.g. 15>

This will allow MMPV to be performed within the specified days before the new period (e.g. "15" for 15 days before the new period).

Note: Only integers are valid for the KDATA field, with "0" meaning MMPV is allowed only on or after the first day of a new period.  If the value is greater than the actual number of days in a period then it means MMPV is allowed for the entire month.  Any invalid entry in the KDATA field will be ignored and the default value will be used.


If apply this note with SNOTE, it is suggested to carry out the following manual steps, and then implement the attached note.

1. Use transaction SE80 to create a SET/GET parameter:

Package/Dev. Class : MG
Parameter ID : MMPV_READ_NOTE
Text : Follow instructions in Note 1082841.

2. Use transaction SE37 to create function module MMPV_DATE_CHECK with the following attributes:

Function group : MLCCS_MATERIAL_MASTER
Short text : Date check for period roller
Import parameters:

Parameter NameTypeAssociated Type
I_NEW_LFGJATYPEBDATJ
I_NEW_LFMONTYPEMONAT
I_BUKRSLIKET001-BUKRS
I_FY_VARIANTTYPEPERIV

Exceptions:

MMPV_BLOCKED
ERROR_OCCURRED

3. Use transaction SE38 to add the following Text Elements to program RMMMPERI (select the radio button 'Text elements' and click on the 'Change' button):

Sym  : 099
Text : Transaction MMPV cannot be executed.  Please refer to SAP note 1082841.

Save and activate the changes.

4. Add the following entries to table T139A:

Use Transaction se16n and enter table name T139A, verify the 'Maintain Entries' checkbox is ticked.  Select AUSNA = 99 and execute (F8); create the following entry:

AUSNA : 99
ABBRU : X
SORT  : 99
KTEXT : MMPV_DATE_CHECK: Error occurred (Note 1082841).

5. Similarly, add the corresponding translation text to table T139B (if a translation is missing in T139B, then the program will use the entry in T139A as default):

SPRAS : <language code>
AUSNA : 99
KTEXT : MMPV_DATE_CHECK: Error occurred (Note 1082841).

6. Implement the attached program corrections.

Comments

Popular posts from this blog

SAP How to mass close open sales orders (Partially or Not Executed)

Sometimes we need to mass close open sales orders (Partially or Not Executed). Using VA02 to close them one by one is inefficient. Method 1: You can use the TCODE MASS . Method 2: You can also use the  TCODE VKM4  to close all open orders. Firstlly use VA06 to choose what SO you wana to mass close, then copy the SO number to VKM4, and execute. Select all item and click Reject.

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) Please read SAP Note 1121176

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) It means SAP require to open Adobe LiveCycle Designer locally. But your PC do not install any version of Adobe LiveCycle Designer. Form SAP Note 1121176 is obsoleted, and LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. SAP Note 1658830 Adobe LiveCycle Designer 9.8 - Installation Symptom You want to install Adobe LiveCycle Designer (LCD) 9.8 on your local computer or upgrade your existing installation. Other Terms Adobe Document Services, ADS, Adobe LiveCycle Designer, SAP Interactive Forms by Adobe, PDF form Reason and Prerequisites You can use Adobe LiveCycle Designer 9.8 with the following versions of Adobe Document Services (ADS): SAP NetWeaver 7.31 and higher For lower releases of SAP NetWeaver, see SAP Note 1317925. This describes the ret...

SAP BASIS tips how to deal with SAP HANA log full situation DiskFullEvent on Log Volume

You observe that the log volume has reached its capacity, causing the database to reject any new incoming requests.And the SAP ERP system or S/4 HANA system is hanging. To determine whether the operating system path is full, you can use commands such as df -h or bdf to check the disk space usage.👀 Reason: Due to an architectural limitation, SAP HANA cannot perform a log backup when the log area is completely full, leading to potential system unresponsiveness or failure to start. Affected Releases: SAP HANA 1:  All revisions. SAP HANA 2:  Revisions from SPS00 to SPS05. Prerequisites: The log volume is full, causing the database to become unresponsive or fail to start. Solution: Upgrade to one of the following SAP HANA revisions: SAP HANA 2:  Revisions >= 060.00 (SPS06) or higher. Workaround: If upgrading is not immediately possible, follow these steps to resolve the issue: Log in as  <SID>adm  User: Ensure you are logged in as the  <SID>adm ...

Newest version of Adobe LiveCycle Designer 11.0 download

As SAP Note 1121176  descripts, Adobe LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. The newest version of Adobe LiveCycle Designer is 11.0.  SAP release a patch at 17.07.2024. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Adobe LiveCycle Designer 11.0 Click here to download. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Click here to download.