Nº nota SAP 1976487

Número 1976487
Versión 0019
Respons. -
Status
nuevo
tratamiento
Estado
No implementable
estructura
Idioma E
Txt.breve Information about adjusting customer-specific programs to th
Componente FI-GL General Ledger Accounting

Txt.expl.

Symptom
You have installed SAP Simple Finance, on-premise edition or plan to do so. You
require further information about how you can adjust your customer-specific programs
or modifications to the new simplified data model in SAP Simple Finance.

Other Terms
Migration, 1402, 1503

Reason and Prerequisites

You have developed customer-specific accounting developments (in particular in the
application components AC, FI, CO, FIN) that were developed for SAP ERP 6.0.

SAP Simple Finance offers a simplified data model. In addition to the usual
SPAU/SPDD activities, this might require special adjustments to customer-specific
developments or modifications.

Task: Check whether the customer uses the affected tables or views in their own source
code.

Procedure: See chapter 1.5

Rating:

At least one of the tables or views is used in the customer-specific source code ->
YELLOW
None of the tables or views is used in the customer-specific source code -> GREEN

Solution
1. Adjustment of customer-specific development objects

1.1. Write access to totals tables and index tables in FI and CO

In SAP Simple Finance, the following tables have been replaced with views of the same
name:

COSP
COSS
BSIS
BSAS
FAGLBSIS
FAGLBSAS
BSIK
BSAK
BSID
BSAD
FAGLFLEXT
LFC1
LFC3
KNC1
KNC3
GLT0

These views of the same name select data from the line item tables and convert this into
the format of the replaced tables so that all read accesses still work.

However, no write accesses may take place - the views are read-only. Remove all write
accesses to these objects from your source code (operations INSERT, UPDATE,
DELETE, and MODIFY).

1.2 Read accesses to totals tables and index tables in FI and CO

See the following SAP Notes:

Notes about using views BSID, BSAD, BSIK, BSAK, BSIS, and BSAS in
2219527
customer-defined programs in SAP S/4HANA Finance
Notes about using views GLT0, FAGLFLEXT, FMGLFLEXT,
2221298 PSGLFLEXT, and JVGLFLEXT in custom programs in SAP S/4HANA
Finance
Compatibility views COSP, COSS, COEP, and COVP. How can their use be
2185026
optimized?

SELECTs from views of the same name with the addition ORDER BY PRIMARY
KEY result in a syntax error in Release S/4H Finance 1503. These must be replaced by
an explicit field list, for example, ORDER BY BUKRS HKONT AUGDT AUGBL
ZUONR GJAHR BELNR BUZEI. In later releases, you can implement SAP Note
2489438 so that ORDER BY PRIMARY KEYs no longer result in a syntax error.

1.3 Views for totals tables and index tables

If, in the ABAP Dictionary, you have defined database views for one of the tables that
has been eliminated in SAP Simple Finance, you must remove these views. The ABAP
Dictionary does not support database views based on other views.

Example:

You have created a database view called Z_BKPF_BSIS with the base tables BKPF and
BSIS. In SAP Simple Finance, BSIS is a view. As a result, Z_BKPF_BSIS would be
based on the BSIS view. This is not supported.

Proceed as follows to find affected views in your namespace.

1. Use the where-used list in transaction SE11. One after the other, enter the
affected objects (COSP, COSS, BSIS, and so on) into the table field.
2. Call the where-used list (Ctrl+Shift+F3) and set the "Views" indicator only.
3. Execute the where-used list.

You must remove these database views from the ABAP Dictionary and replace the
selection from the views by an Open SQL SELECT or a read module call.

1.4 Aging

If you actively use SAP data aging for the FI document, you have to make further
adjustments. See SAP Note 2076652.

1.5 Finding the affected parts of the code

You can use the Code Inspector to find all affected parts of the code. Proceed as
follows:

1. Call transaction SCI and define a new variant. In the definition of the variant, set
the indicator for searching for DB operations in "Search Functs.". Enter the list
of affected objects (COSP, COSS, BSIS etc.).
2. Create an object set that contains all of your programs, classes, function groups,
and so on.
3. Create a new inspection and execute it. The result is a list of all database
accesses to the totals tables and index tables removed in Simple Finance.

Remember that generic database accesses that cannot be found using standard methods
are possible too.

Example: UPDATE (lv_tabname) FROM lt_index.

1.6 SAP Simple Finance, on-premise edition 1503

Additional compatibility views were implemented in SAP Simple Finance, on-premise
edition 1503. The technology is different than in the previous release. The views do not
have the same name as the original table. Instead, in the database interface (DBI), all
SELECTs are redirected to compatibility views that receive data in the same structure
from the new data model (mainly from the new table ACDOCA). The process of
redirecting SELECTs is also called REDIRECT.

Table -> View

ANEA -> FAAV_ANEA

ANEK -> FAAV_ANEK
ANEP -> FAAV_ANEP
ANLC -> FAAV_ANLC
ANLP -> FAAV_ANLP
BSIM -> V_BSIM
CKMI1 -> V_CKMI1
COEP -> V_COEP
FAGLFLEXA -> FGLV_FAGLFLEXA
MLCD -> V_MLCD
MLCR -> V_MLCR
MLHD -> V_MLHD
MLIT -> V_MLIT
MLPP -> V_MLPP
T012K -> V_T012K_BAM
T012T -> V_T012T_BAM
FMGLFLEXA -> FGLV_FMGLFLEXA
FMGLFLEXT -> FGLV_FMGLFLEXT
PSGLFLEXA -> FGLV_PSGLFLEXA
PSGLFLEXT -> FGLV_PSGLFLEXT
JVGLFLEXA -> FGLV_JVGLFLEXA
JVGLFLEXT -> FGLV_JVGLFLEXT
ZZ<CUST>A -> ZFGLV_GLSI_C<number>
ZZ<CUST>T -> ZFGLV_GLTT_C<number>

The ZZ* tables are General Ledger Accounting (new) line item tables and totals tables
in the customer namespace. They can be identified with a SELECT on the table T800A
with the restriction TTYPE IN ( 'TT', 'SI' ) AND GLFLEX = 'X' AND INACTIVE = ''.

The views select data from the table ACDOCA and other tables and convert it into the
format of the original tables so that all read accesses continue to work.

The write accesses (INSERT, UPDATE, DELETE, and MODIFY operations) must be
converted as described in the following sections.

1.6.1 General ledger

Write accesses to the line item tables FAGLFLEXA, FMGLFLEXA, PSGLFLEXA,

JVGLFLEXA, and ZZ<CUST>A must be converted to the table ACDOCA. Most of the
fields in the table ACDOCA match the fields in the General Ledger Accounting (new)
line item tables. However, there are a few exceptions:
  ACTIV is BTTYPE in ACDOCA.
 RVERS is obsolete.
 DOCNR is obsolete.
 COST_ELEM is obsolete. There is only one field for the account: RACCT.
 LOGSYS is AWSYS in ACDOCA.
 Optional fields (for example, ZZHOART) have a different name in the table
ACDOCA. The mapping is implemented in the method
GET_ACTIVE_OPT_FIELDS of the class CL_FINS_FI_UTILITY.

We advise against converting write accesses directly to the table ACDOCA. Instead, use
the new ABAP class CL_FINS_ACDOC_CHANGE for all write accesses to
ACDOCA.

Write accesses to the totals tables FAGLFLEXT, FMGLFLEXT, PSGLFLEXT,

JVGLFLEXT, and ZZ<CUST>T must be removed without being replaced.

Assignments using the group names PERIOD_DATA, TSL, HSL, KSL, OSL, MSL,
and FIX must be reprogrammed.
Example: The following code results in SY-SUBRC 4 in SAP Simple Finance.
FIELD-SYMBOLS <ls> TYPE faglflext.
ASSIGN COMPONENT 'HSL' OF STRUCTURE <ls> TO FIELD-
SYMBOL(<ls_hsl>).

In SAP Simple Finance, compatibility views for the tables FAGLFLEXA/T,

FMGLFLEXA/T, PSGLFLEXA/T, JVGLFLEXA/T, and ZZ<CUST>A/T return data
for all general ledgers. Make sure that all read accesses restrict the field RLDNR.
Example:
Before the upgrade to SAP Simple Finance, you had two ledgers, 0L and 1N, persisted
in separate tables (0L in FAGLFLEXA/T and 1N in ZZFLEXA/T). Following an
upgrade, a SELECT from FAGLFLEXA/T returns data for 0L and 1N. The same is true
for ZZFLEXA/T.

For certain posting documents, there is no entry view in transactions FB03 and FB03L.
For these documents, there are only entries in BKPF/ACDOCA but not in
BSEG/BSEG_ADD (see SAP Note

2297729).

1. Intracompany CO processes

2. Foreign currency valuation (FAGL_FCV)

3. GL allocations

4. SAP Fiori app for foreign currency valuation

1.6.2 COEP

Use the new ABAP class CL_FCO_COEP_UPDATE for all write accesses to COEP
outside the software component SAP_FIN. This ensures that actual postings in COEP
are no longer updated. Important: This class does not transfer the alternative posting to
the table ACDOCA.

You must therefore remove write accesses to the line item tables COEP if you
previously changed document line items of the value type 04 ("Actual postings"):
Actual postings of the value type 04 are no longer supported in the table COEP. (In
other words, the compatibility views COEP and COVP no longer read actual postings
from COEP. Instead, they are calculated from ACDOCA.) Write accesses for value
types other than "04" are still possible.

We strongly advise against converting write accesses directly to the table ACDOCA
because most of the field names in COEP differ from those in ACDOCA and, to some
extent, cannot be mapped on a 1:1 basis. In addition, the new posting logic in ACDOCA
differs significantly from the posting logic in COEP. Therefore, a customer-specific
program cannot simply be converted to the table ACDOCA.

1.6.3 Asset Accounting

You must remove write accesses to the tables ANEA, ANEP, ANEK, ANLC, ANLP
without replacing them.

1.6.4 Material ledger

You must remove write accesses to the ML document tables (MLHD, MLIT, MLPP,
MLCR, MLCD) if you previously changed documents of the transaction type "UP"
("Update"). Write accesses for other transaction types are still possible.

The compatibility views from ACDOCA are used to calculate update documents. We
strongly advise against converting write accesses directly to the table ACDOCA
because most of the field names in the ML document tables differ from those in
ACDOCA and, to some extent, cannot be mapped on a 1:1 basis. Therefore, a customer-
specific program cannot simply be converted to the table ACDOCA.

Write accesses to the table CKMI1 must be removed. Data is calculated from ACDOCA
using a compatibility view. We strongly advise against switching write accesses directly
to the table ACDOCA since most of the field names of the index table differ from those
of ACDOCA and sometimes cannot be mapped on a 1:1 basis. Therefore, a customer-
specific program cannot simply be converted to the table ACDOCA.

1.6.5 T012K/T012T

Write accesses to the tables T012T and T012K must be converted to the tables
FCLM_BAM_AMD, FCLM_BAM_AMD_CUR, FCLM_BAM_AMT_T, and
FCLM_BAM_ACLINK2.
We recommend that you perform write accesses via the BOR object FCLM_CR only.
Otherwise, the approval processes configured in bank account management are not
taken into account.
The manner in which the IBAN of the house bank account is stored has been changed. It
is no longer in the table TIBAN, but in the IBAN field of the table FCLM_BAM_AMD.
As a result, accesses using the function modules

READ_IBAN_EXT
READ_IBAN_FROM_DB
READ_IBAN
READ_IBAN_INT
SEARCH_FOR_IBAN

no longer work. To read the IBAN of a house bank account, you must replace these
modules as follows (old name with the attached _HBA):

READ_IBAN_EXT_HBA
READ_IBAN_FROM_DB_HBA
READ_IBAN_HBA
READ_IBAN_INT_HBA
SEARCH_FOR_IBAN_HBA

1.6.6 Views on redirected tables

If, in the ABAP Dictionary, you have defined database views for one of the tables listed
in Section 1.6, you must remove these views. Otherwise, you will access data in
decommissioned tables.

You must remove these database views from the ABAP Dictionary and replace the
selection from the views by an Open SQL SELECT or a read module call.
Alternatively, you can create new CDS views.

The attached file lists all views that have been replaced in the standard system with
equivalent ABAP source code or a new CDS view. REDIRECT technology is used to
redirect the SELECTs to the new CDS views. The REDIRECT procedure cannot be
used for customer-defined views.

Example: The compatibility view V_COVP was created for the view COVP. In the case
of SELECT FROM COVP, the SELECTs are redirected to V_COVP.

1.7 S/4HANA readiness checks

Hits from the S/4HANA readiness check "S/4HANA: Search for ABAP Dictionary
enhancements" that reference this SAP Note can be ignored and can be suppressed by
implementing correction note 2522926.

Releases válidos

 700
 720
 730
Desconoc.

 Desconoc.
o 700
o 720
o 100
o 101