Introduction:
Any Financial document posted in FI will have its data stored in BKPF (header level data) and BSEG (line item level data). Hence BSEG table is the repository for fetching any transaction level data.
In a migration project,even the financial postings done are to be moved to the new system either for reporting or any legal compliance adherence. In such scenarios generally a full database table dumps to files is done. Then loading of those tables into applications like Applaud, SQL app and others, and do all the table joins and translations from there to SAP (re-implementation) or non-SAP system.
In the above context let us differentiate “Transparent and Cluster Tables” for our understanding. Transparent tables are physical tables stored in the database. Cluster tables are not physical tables stored in the database. Cluster tables indeed require Abap dictionary definitions and the SAP logic layer to be able to read.
Example: One can read BSEG from SE16 as a table but if when connect to the DB directly and run a SQL statement against BSEG it won’t work, because BSEG is a Cluster table.
But with S4, this feature can be overcome by directly fetching the details from the BSEG table, because it has been converted to a transparent table in S4.
Taking an in-detail example .
ECC version of SAP
Step 2) Based on the document number we can fetch the header data from BKPF – feasible,
since BKPF is a Transparent table.
Step 3) Now if you need any specific fields of the document posted (say PO number, Assignment, etc), you need the data from the BSEG table – not feasible,
since BSEG is a Cluster table.
S4 version of SAP
Step 2) Based on the document number we can fetch the header data from BKPF – feasible,
since BKPF is a Transparent table in S4.
Step 3) Now if you need any specific fields of the document posted (say PO number, Assignment, etc), you need the data from the BSEG table –feasible,
since BSEG is a Transparent table in S4
Conclusion:
S4 enables easy migration of Financial data either for reporting or migration or any such other scenarios.
Cheers
Okumaya devam et...
Any Financial document posted in FI will have its data stored in BKPF (header level data) and BSEG (line item level data). Hence BSEG table is the repository for fetching any transaction level data.
In a migration project,even the financial postings done are to be moved to the new system either for reporting or any legal compliance adherence. In such scenarios generally a full database table dumps to files is done. Then loading of those tables into applications like Applaud, SQL app and others, and do all the table joins and translations from there to SAP (re-implementation) or non-SAP system.
In the above context let us differentiate “Transparent and Cluster Tables” for our understanding. Transparent tables are physical tables stored in the database. Cluster tables are not physical tables stored in the database. Cluster tables indeed require Abap dictionary definitions and the SAP logic layer to be able to read.
Example: One can read BSEG from SE16 as a table but if when connect to the DB directly and run a SQL statement against BSEG it won’t work, because BSEG is a Cluster table.
But with S4, this feature can be overcome by directly fetching the details from the BSEG table, because it has been converted to a transparent table in S4.
Taking an in-detail example .
ECC version of SAP
- Let’s say we need to fetch the open item records for all the vendors from ECC along with the header data.The Option isStep 1) First let’s fetch the line items from BSIK table – feasible,
since BSIK is a Transparent table.
Step 2) Based on the document number we can fetch the header data from BKPF – feasible,
since BKPF is a Transparent table.
Step 3) Now if you need any specific fields of the document posted (say PO number, Assignment, etc), you need the data from the BSEG table – not feasible,
since BSEG is a Cluster table.
S4 version of SAP
- Considering the same example of fetching the open item records for all the vendors from ECC along with the header data.Step 1) First let’s fetch the line items from BSIK table – feasible,
since BSIK is a SQL view. in S4
Step 2) Based on the document number we can fetch the header data from BKPF – feasible,
since BKPF is a Transparent table in S4.
Step 3) Now if you need any specific fields of the document posted (say PO number, Assignment, etc), you need the data from the BSEG table –feasible,
since BSEG is a Transparent table in S4
Conclusion:
S4 enables easy migration of Financial data either for reporting or migration or any such other scenarios.
Cheers
Okumaya devam et...