General Ledger Accounting. ACDOCA. ACDOCA is a standard General Ledger Accounting Transparent Table in SAP FI application, which stores Universal Journal Entry Line Items data. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Loaded 0%. This is a preview of a SAP Knowledge Base Article. Click to access the full version on SAP for Me (Login required). FAGLL03 report terminates with a dump TSV_TNEW_PAGE_ALLOC_FAILED. The report runs for a single day, for a single company code and for a single GL account. Memory settings are taken care of as per the KBA 2180736.

Here is my brief synopsis of each of the Browsers within S/4 HANA. FAGLL03H – This transaction allows selection and display of most fields in ACDOCA, as well as many fields from BKPF and BSEG, and also from account master data tables SKA1 and SKB1. It also includes a number of fields from master data tables KNA1 and LFA1 for customers and

Jun 15, 2013 at 11:07 AM. Hi Kumar, Field "SAKNR" indentifies the GL Acct in chart of Account and the field "HKONT" identifies GL account number to which the transaction figures are updated. You can also say.. BSEG-HKONT is the GL account used in posting whereas BSEG-SAKNR is the sub-ledger account from master data.
Quickly Retrieving FI document Data from BSEG. 18 7 36,438. In other BLOGs, I showed some general techniques that you can use to improve the performance of your ABAP code. In this one, I will show some specific techniques that you can use to retrieve accounting document data. BSEG is a cluster table and in the forums it is often said that you Accounting Document Segment. BSEG (Accounting Document Segment) is a standard table in SAP R\3 ERP systems. Below you can find the technical details of the fields that make up this table. Key fields are marked in blue. Additionally we provide an overview of foreign key relationships, if any, that link BSEG to other SAP tables. You should check your belnr has left padding '0' you can check it with double click on the record in SE16n tcode. Actually, you can directly link these table. Last option, If these are still not working for you, then you can link: However, it will kill the performance, I believe. RSEG-EBELN = BSEG-EBELN RSEG-EBELP = BSEG-EBELP RSEG-MATNR = BSEG
Required fields are selected from the table ACDOCA with all entries in the C_T_DATA on Key Fields of the table. As discussed above “For All Entries” statement is nothing but an inner-join between the two tables. Hence you can see inner join between table ACDOCA and SOURCE_DATA (Copied from C_T_DATA) in the code.
OSS 2856765 - telling that table BSEG is not filled anymore here - is also very interesting in this context. ACDOCA-BSTAT = 'U' is an interesting one (i.e. "not in BSEG anymore") mentioned in note OSS2297729 - and can be seen in "document status" in the depreciation postings inside this blog. Again, thanks a lot. Inspiring. Thomas
The information from BSEG is available in Universal Journal table ACDOCA, but from a process standpoint, BSEG is still being used. Also note that the field names are not identical in these two tables, e.g. Trading Partner is having a field name of VBUND in table BSEG and RASSC in table ACDOCA; Cost Center is having a field name of KOSTL in

Search for additional results. Visit SAP Support Portal's SAP Notes and KBA Search. The "Net Due Date" of Reversal document in FBL1N / FBL5N is incorrect, which is not matched with table ACDOCA / BSEG.

The DataSource uses the delta method to transfer each new status of the changed line item. For this reason, it is not possible to update the InfoCube directly. The InfoCube can only be deleted via the DataStore object (update with MOVE). The delta method works with a lower safety interval of an hour (standard setting).
Dear SAP Gurus, Please explain me about the basic line of difference between FBL1N and FBL1H. Are these transaction codes same or is there any difference?
2713775 FI_DOCUMENT_CHANGE is not updating ACDOCA. You use FI_DOCUMENT_CHANGE to update some field value in accounting document, such as SGTXT value. But you find this FM updates BSEG table but does not update the value in ACDOCA.
In ACDOCA as you can see in screenshot below, the value got posted only in the ledgers in which the currency type ‘Z5’ was defined, in our case it is in the ledger I3 (IFRS) and L3 (Local GAAP) In FB03 as you can see below, the amount in transaction currency, local currency, group currency are zero and only the FD currency BOB is populated
You can use Data Mapping to transform and load data from the ACDOCA table into the ACDOCU table. Both tables are within the same SAP S/4HANA system. Examples: Retrieve additional ACDOCA data for statistical information (e.g., aging information of AR/AP). If ACDOCA data or details on Movement Type or Sub-item are missing, you can also use the
Search for additional results. Visit SAP Support Portal's SAP Notes and KBA Search. You find that some documents cannot be displayed with T-code FBL3N or FBL3H in S/4 Hana system. But these documents can be displayed with T-code FB03 only with General Ledger View.
Only the ACDOCA table (Universal Journal) will undergo migration. There will be no entries in BSEG andd FAGLFLEXA, as only balances are migrated, and no documents are generated. No need for Balance Carry Forward execution. Available Migration Objectsin SAP S/4HANA Cloud. Viewing migrated historical documents – Not Available

I have already known that BSEG store accounting document items and COEP store CO documents items. I have record in table BSEG with accounting document 1111111111 and cost element 2222222222. There is 100 records. Then I select to COBK (CO Document Header) where REFBN (Ref Doc Number) = 1111111111 and I found CO document number = 3333333333.

.