Ansicht
Dokumentation

FIN_MANAGE_POSTING_PERIOD_OP - Program FIN_MANAGE_POSTING_PERIOD_OP

Addresses (Business Address Services)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Purpose

REPORT FIN_MANAGE_POSTING_PERIOD_OP can be used to import converted existing data from table KAPS used in transaction OKP1. Records in this table are only for closed periods. New table OPENPOSTGPERIOD stores only open periods. Therefore, values need to be reverted. In case no data are in KAPS, they need to be created based on data in TJ01, FINS_BTTYPE and i_fiscalyearperiodforledger(represented by tables behind this cds). Table OPENPOSTGPERIOD is used in new fiori app Manage Posting Periods – Cost Accounting, which is used to define the open posting periods for CO business transactions.

Purpose of this report is to run it only once before users start to use app Manage Posting Period – Cost Accounting.

Afterwards all data need to be handled in app Manage Posting Period – Cost Accounting and import of previous data does not make sense.

Input parameters specify which data are converted:

Controlling Area - Controlling Area used in OKP1

Client - Client in which the data are converted

Fiscal Year From - Fiscal Year used in OKP1

Fiscal Year To - Fiscal Year used in OKP1

Possible case:

expected scenario: Report is run, data are inserted into table OPENPOSTGPERIOD.

unexpected scenario: Table is not empty, it means that data were inserted by app Manage Posting Period – Cost Accounting -> this report is to be used only before first use of the app, afterwards all changes to have to be made in app

unexpected scenario: No suitable data, that could be used to initially fill table OPENPOSTGPERIOD, were found. No data need to be imported.

At the end are listed Bus.Transactions, which were used in table KAPS but do not exist in table FINSC_BTTYPE. These Bus.Transactions are not reflected in app Manage Posting Period – Cost Accounting.

Logic of report:

create all records:

1 Select vorgang from tj01, that has persp = X and wtkat = A in tj01, and exist in finsc_bttype with xperiodcontrol = x; it gives bttype-year-period

2 select company code-ledger-year-period combination from i_fiscalyearperiodforledger

– only ledger based from logic pckg FINS_BTTYPE_BASED_ACCTNG-FINS_BTTYPE_CHECK_CO, method CL_FINS_COMPANY_CHECKS-CHECK_OBJECT_LIST line 43 * determine ledger calls cl_fins_comp_check_tools=>get_rldnr = gets ledger based on co area and version

3 Assign all company code-ledger combination to bttype; based on year-period

4 it created internal table with all open periods

delete existing closed periods (from KAPS):

5 Select from kaps – records with vorgang, that has persp = X and wtkat = A in tj01, and exist in finsc_bttype bttype with xperiodcontrol = x; it gives bttype-year-period (closed periods)

6 select company code-ledger-year-period combination from i_fiscalyearperiodforledger

– only ledger based from logic pckg FINS_BTTYPE_BASED_ACCTNG-FINS_BTTYPE_CHECK_CO, method CL_FINS_COMPANY_CHECKS-CHECK_OBJECT_LIST line 43 * determine ledger calls cl_fins_comp_check_tools=>get_rldnr = gets ledger based on co area and version

7 Assign all company code-ledger combination to bttype; based on year-period

- If year-period from kaps does not exist in i_fiscalyearperiodforledger => no record

8 records from 5-7 created internal table with closed periods, these are removed from internal table from 4. And the rest of data from open period table is inserted into OPENPOSTGPERIOD

General Material Data   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 3996 Date: 20240520 Time: 073912     sap01-206 ( 72 ms )