Bseg and BSIs, bSAS, Bsid, Bsad, Bsik, Bsak
Relationship of six tables
1. Data relations:
Bsas+bsis+bsak+bsik+bsad+bsid = bseg
2, six table description:
Cleared |
Opened |
|
bSAS |
BSIs |
==>all GL Documents |
Bsak |
Bsik |
==>all AP Documents |
Bsad |
Bsid |
==>all AR Documents |
bSAS: General Ledger details (cleared) Ledger
BSIs: General Ledger details (not cleared) ledger
Bsad: Accounts receivable (cleared) customer
Bsid: Accounts receivable (not cleared) customer
Bsak: Payables (cleared) Suppliers
Bsik: Payable details (outstanding) Supplier
3. Table Relationship:
BSEG is mainly associated with these six tables through the "voucher number" "Fiscal year" "line number"
Bukrs (company code)
BELNR (Document No)
Gjahr (Fiscal year)
Buzei (line Item)
BKPF is the financial voucher header, BSEG is the financial voucher line item. The data is inserted into BKPF and bseg when the financial voucher is billed, and if necessary, the data is inserted into an open table in the above six tables.
When clearing the account, the data is deleted from one of the six tables, and the corresponding cleared table is inserted. In general, the certificate generated by a business is not clear, then: if the business line is customer-related, it is recorded to Bsid, if the business row is vendor-related, is logged to Bsik, regardless of customer-related or vendor-related, is related to General ledger, so there will be recorded to BSIs But if the business is cleared, the corresponding records will be transferred from bsi* to bsa*
Under normal circumstances: Accounts receivable, pre-payment, other receivables, receivable bills and other subjects are related to the customer, but also the outstanding management of the general ledger account; Accounts payable, prepaid, other payables, bills of exchange and other subjects are related to the supplier, but also to the outstanding management of the general ledger accounts;
Other general ledger accounts generally do not enable open management, so records are generally placed in bsis.
4, BSEG Features:
Bseg itself is a Cluster table (cluster table), BSEG is the integration of the above six tables, when you want to read "bseg" table is equal to read the six tables, so you can imagine how slow it will read. The cluster table or pool table is used by the SAP system itself, so the cluster table itself does not exist in the repository entity, although it can be used in ABAP, but there are some limitations:
- You cannot use the SELECT DISTINCT or GROUP by syntax
- Cannot use native SQL
- You cannot use specify field names after the ORDER BY clause
- You cannot create a secondary index
- Be sure to use key FIELD when querying
PS: Data extraction in the cluster is very inefficient, can be based on different subjects, in the other six tables to take object data!!!!!
---------------------------------------------------------------------------------
Original: http://skewen.iteye.com/blog/1478241
a detail part of an accounting voucher can contain multiple line items, which are stored in the following six financial data tables, as well as the status of the row items, as they are stored in the BSEG table.
in general, it's just beginning to be an open voucher,
if the line item is related to the customer, it is recorded to Bsid;
if the line item is vendor-related, it is logged to Bsik;
Both customer-related and vendor-related, are related to General Ledger, so they are also recorded in BSIs.
then when the business was cleared,
if the line item is customer-related, the corresponding record is transferred from Bsid to Bsad;
if the line item is customer-related, the corresponding record is transferred from Bsik to Bsak;
Both customer-related and vendor-related are related to General ledger, so the corresponding records are transferred from BSIs to bSAS.
under normal circumstances:
Accounts receivable, Accounts receivable , other receivables, bills of exchange and other subjects are related to the customer, but also to the outstanding management of the General ledger account;
The accounts of prepaid accounts, accounts payable, other payables, bills of exchange, etc. are related to the supplier and are related to the general ledger account of outstanding management;
Other general ledger accounts generally do not enable open management, so records are generally placed in bsis.
There is an item voucher table in addition to the above 6 accounting voucher tables, because item-related line items also appear in the voucher, but the item-related line items do not need to be cleared, so only one item voucher table corresponds.
Bsim:
Second level index, commodity voucher
secondary Index,
Documents for Material
Here's a concept to note:
when the bseg is deposited into a cluster table, it is binary
The Save form edits all line item information in the detail part of a voucher into a long text, and then into the Vardata project in the RFBLG of the table cluster.
When depositing 7 corresponding transparent tables, the corresponding transparent table is deposited according to the nature of the above line items, and each record in the table only records one line item information.
With the above knowledge, we are not difficult to understand,
When you use T-CODE:FB03 to view the details of a voucher, you are actually reading information about the cluster tables such as BSEG.
When you use t-code:fbl1n, fbl3n, fbl5n to view the vendor, General Ledger, and customer's outstanding and cleared information separately, you actually read the information in the Accounting voucher table Bsik, Bsak, and so on.
Bseg and BSIs, bSAS, Bsid, Bsad, Bsik, Bsak Six Tables relations (EXT)