Sie sind auf Seite 1von 2

Traditional ECC 6 database tables:

 BKPF –  SAP Accounting Header Table Data


 BSEG – SAP Cluster table used to store Accounting Document Segment data(Line item
Data)

Index Tables:

 BSIS – Accounting: Secondary Index for G/L Accounts data


 BSAS – Accounting: Secondary Index for G/L Accounts (Cleared Items)
 BSID – Accounting: Secondary Index for Customers data.
 BSIK – Accounting: Secondary Index for Vendors data
 BSAK – Accounting: Secondary Index for Vendors (Cleared Items)
 BSIM – Secondary Index, Documents for Material data
 FAGLBSIS – Accounting: Secondary Index for G/L Accounts data
 FAGLBSAS – Accounting: Secondary Index for G/L Accounts (Cleared Items)

Aggregated Tables:

 GLT0 – G/L account master record transaction figures


 FAGLFLEXT – New General Ledger: Total Tables
 KNC1 – Customer master (transaction figures)
 LFC1 – Vendor master (transaction figures)
 KNC3 – Customer master (special G/L transaction figures) data
 LFC3 – Vendor master (special G/L transaction figures) data
 COSS – CO Object: Cost Totals for Internal Postings data
 COSP – CO Object: Cost Totals for External Postings data

Material Ledger Tables:

 MLIT, MLPP, MLPPF, MLCR, MLCD, CKM11, BSIM

Asset Accounting Tables:

 ANEK, ANEP, ANEA, ANLP, ANLC

SAP S/4 HANA(Simple Finance):

SAP Released SAP S/4 in 2015 named as ‘Smart Finance’ and later it changed the name to
‘Simple Finance(S-FIN)’ and thereafter it was renamed as ‘S/4 HANA Finance’. S/4 HANA
Finance provides a database table “ACDOCA”(Universal Journal) is which contains all the
documents types from FI, CO, MM, SD, PP applications. All the postings to these applications
are written in single ACDOCA table (so it’s a replacement table for existing traditional tables like
BKPF,BSEG etc). This way system avoids data redundancy to a great extent.

What if we still need to access traditional tables? The traditional tables from system are replaced
by HANA CDS(Core Data Services) views, which will be referencing and fetching data from
ACDOCA(Universal Journal table). In this way SAP has ensured that the traditional tables are
converted to database views so the existing programs using those as tables will not be impacted
even after migration to S/4 HANA S-FIN. There still might be a minimal need to align and re-
adjust some ABAP syntaxes which can be easily analysed by doing syntax checks.
It will be user’s choice to either use ACDOCA or use CDS views to build reports/programs going
forward after the migration. In my next blog I will try to explain practical use cases for ACDOCA
table vs CDS views, so stay tuned!

Das könnte Ihnen auch gefallen