Ansicht
Dokumentation

NSDM_MIG_CREATE_PERFY - MM-IM Migration: Create PERFY entries to S/4HANA Table MATDOC_EXTRACT

CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Purpose

The PERFY (=Posting Period of Fiscal Year) records hold values for the fiscal year variant and the posting period.

For each company (field “bukrs”/ company code), table MARV (=Material Control Record) contains the information since when this company has been used in the system. The relevant fields are
* GJA 46C = Fiscal Year of 1st Period After 4.6C Upgrade and
* MON 46C = 1st Period After 4.6C Upgrade

The content of table MARV is the basis for the PERFY entries in table MATDOC_EXTRACT which are being created by this report. For every month since this month/year combination, a PERFY entry will be created.

Example

For company code 0001, table MARV has the following entries for GJA_46C = 2014 and MON_46C = 12.
As a result of this report, new entries will be written to table MATDOC_EXTRACT with record type PERFY:

RECORD_TYPE,,BUKRS,,PERIV,,GJPER,,

PERFY,,0001,,K4,,012.2014,,

PERFY,,0001,,K4,,001.2015,,

…,,,,,,,,

PERFY,,0001,,,,,,

,,,,,,

&Determination logic for PERFY records&

In regular cases, values for GJA_46C and MON_46C are maintained in table marv and are used as basis for the PERFY determination, see example above.

However, in some exceptional cases the values for GJA_46C and MON_46C may be initial in the source system (companies may have been created but not been used at all or data in the system may be inconsistent). In this case the system will use the following logic to determine a start date for the PERFY entries:

First, we attempt to derive the entries from the corresponding history tables (MARCH, MARDH, ..) associated with this company

Second, we look for the oldest PERFY-related MATDOC_EXTRACT entry already written (independent from the company).

As a final fallback, we use January 2000 as default value (independent from the company)

&Report Parameters and Settings&

Default parameters are “Create new PERFY records” and “Test (no database update)”.

&Run Options&

From the first three options

·,,Create new PERFY records

·,,Clear old & create new PERFY

·,,Clear old PERY only

exactly one has to be selected

The delta migration has to be triggered explicitly by setting the flag “delta-migration”. This second run is required to check if

·,,the current period has changed since the first run of this report or if

·,,any additional BUKRS have been created

In these cases additional PERFY entries will be written.

In test mode, the creation of new PERFY entries is simulated but not persisted; existing entries will not be deleted and no new entries will be created. This parameter can be used both during regular/initial migration as well as delta migration.

&Restrict processing of company codes&

Default is that the user does not make any entries, in this case all company codes will be processed.
Should the administrator decide to analyze entries for specific companies, only the corresponding PERFY entries will be deleted and (re-)created, according to the settings in the section “run options”.
Multiple company code values can be either listed explicitly or by supplying a value range.
This parameter can be used both during regular/initial migration as well as delta migration

&Logging options&

Logs can be written to the database and/or when being called by the the Software Update Manager (SUM)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3946 Date: 20240531 Time: 215143     sap01-206 ( 58 ms )