Embedded Analytics on

Universal Journal (ACDOCA)

1. Universal Journal (ACDOCA)
2. ACDOCA in SAP S/4HANA: Key Technical Aspects
3. ACDOCA in SAP S/4HANA: Key Functional Aspects
4. VDM for ACDOCA – Standard Interface Views
5. VDM for ACDOCA – Standard Consumption Views
6. Use Case I - P/L Actual Query
Universal Journal (ACDOCA)
 Universal Journal (ACDOCA)

Imagine a single table that brings all your financial data together, reducing duplication, improving performance, and simplifying everything—

Welcome to ACDOCA, the powerhouse of SAP S/4HANA.

This Universal Journal integrates data from multiple applications such as asset accounting, general ledger, material ledger, profitability analysis,
and more. Let’s dive into the magic behind ACDOCA’s efficiency
 ACDOCA in SAP S/4HANA: Key Technical Aspects

Simplified Data Model Optimized for HANA DB

Forget about the old total and index tables used in previous SAP Get ready for a performance boost! ACDOCA takes full
versions. S/4HANA sweeps them aside by allowing real-time advantage of HANA’s cutting-edge architecture:
aggregations and calculations directly from ACDOCA. The • Data Layout: ACDOCA leverages HANA's in-memory
result? No more duplicate data and a centralized home for FI structure, partitioning, and parallel processing for
and CO data, earning it the title "Universal Journal.“ lightning-fast performance.
• Compression: HANA’s compression technology gives you
a 5x–10x reduction in data size, meaning less data has to
travel to the CPU.
• Columnar Storage: Data is stored in columns, making
queries speedier and reducing memory usage.
• Horizontal Partitioning: The data is split into smaller, more
manageable sections, enabling faster searches through
parallel processing.
 ACDOCA in SAP S/4HANA: Key Technical Aspects

Smart Indexing Compatibility Views

With data compression, small tables don't always need Worried about older code breaking? Don’t be! Total and index
indexes, but as your tables grow, inverted (single-column) and tables were replaced by compatibility views (DDL SQL views)
composite (multi-column) indexes ensure fast access to large during the installation of SAP Simple Finance. Your old SELECT
datasets. In S/4HANA, these indexes are HANA-specific and statements will work as before. However, write operations
make your database more efficient. (INSERT, UPDATE, DELETE) are restricted, so take note! For
more details, check out SAP Note #1976487.

Amount Field Length Extension

S/4HANA is built to handle the heavy financial lifting. Currency
amount fields have been extended to 23 digits, meeting the
demands of financial institutions with high transaction
volumes. This extension applies to fields of type CURR, DEC,
CHAR, and NUMC. Just be careful of potential overflow errors
BSEG: From Cluster to Transparent Table in your ABAP coding!
Goodbye, BSEG cluster table! In S/4HANA, BSEG was converted
ACDOCA Extensibility
to a transparent table, eliminating the need for pooled and
cluster tables. While this speeds up performance, there's one Want to add custom fields? No problem! ACDOCA supports
small catch: you’ll now need to handle sorting explicitly in your extensibility. If you’re interested in expanding your ACDOCA
custom programs. The database interface no longer manages it table, be sure to refer to SAP Note #2453614 for all the details.
for you automatically, so keep that in mind.
 ACDOCA in SAP S/4HANA: Key Functional Aspects
Real-Time Reconciliation Across Modules Controlling Integration: CO Meets FI
One of the biggest transformations is the integration of multiple
Ever felt the hassle of maintaining FI and CO as separate
modules into a single table, ACDOCA. No more period-end
systems? With ACDOCA, primary and secondary cost
reconciliation headaches across Financial Accounting (FI) and
elements are handled seamlessly under one roof.
Controlling (CO) – everything happens automatically in real-
time. Here’s how it works:

Here’s a Fun Fact: • Primary Postings: Transactions related to FI (like cost

Old reconciliation programs like RAABST01, RAABST02, and center assignments) are fully integrated into ACDOCA.
FAA_GL_RECON are now obsolete. With ACDOCA, the General
• Secondary Postings: CO processes like allocations and
Ledger (GL) and Asset Accounting (AA) are always reconciled
in real-time, simplifying processes for your finance teams! settlements are recorded in ACDOCA as well, keeping
sender-receiver relationships intact. No more guesswork
ACDOCA vs BSEG: What’s the Difference? when tracking profit center data or functional areas.
While BSEG still handles transactions like AR, AP, and GL, This unified approach ensures FI and CO are always
ACDOCA is where most of the magic happens. It's responsible reconciled, with no need for manual intervention.
for the detailed line items across different SAP modules.
No More 999-Line Item Limit!
Key Change:
BSEG is slowly transitioning to manage only open items, leaving One of the most frustrating issues in the past was the 999-line
all line-item details for other processes in the hands of item limit in BSEG. But now, with ACDOCA, you can say
ACDOCA. It eliminates the need for index tables like BSIS, BSAS, goodbye to that restriction! The Universal Journal doesn’t have
and BSID – making everything faster with the in-memory SAP
a line-item limit, so you can post large entries without needing
HANA database.
to worry about splitting documents.
 ACDOCA in SAP S/4HANA: Key Functional Aspects
Profit Center Accounting (PCA): Simplified in Meet Margin Analysis in S/4HANA
S/4HANA You may have heard about Profitability Analysis (CO-PA) being part
With S/4HANA, classical PCA is no longer required, and of S/4HANA. Well, SAP is recommending switching to Margin Analysis
the new PCA runs in parallel with the General Ledger in for a better, more efficient reporting experience. It integrates
ACDOCA. seamlessly with ACDOCA and provides real-time insights for multi-
dimensional financial reporting. Here’s What Changed:
Good News!
If you’re still using classical PCA, the transition to the • Margin Analysis gives you real-time access to revenue, cost of
Universal Journal is smooth and doesn’t require any major goods sold, and other market segment details without the need for
reconfigurations. You simply deactivate classical PCA and reconciliation between General Ledger and CO-PA.
switch to the new functionality that S/4HANA provides. • Everything is aligned under ACDOCA, so you get consistent,
accurate data every time you run a report.
Material Ledger: Now Fully Integrated!
A big change in SAP S/4HANA is that the Material Ledger Currency Handling: Easier Than Ever
(ML) is now mandatory. It’s fully integrated into ACDOCA,
With ACDOCA, currency handling has become much more flexible. In
which optimizes performance and simplifies access to
S/4HANA, you can configure up to 8 parallel currencies per company
material data.
code, which is a big jump from the 3 currencies available in ECC.
Did You Know?
This flexibility is especially useful for global businesses that deal with
Old ML tables like CKMLHD, CKMLPR, and others are now
transactions in multiple currencies, allowing for streamlined,
obsolete. Their content is now stored in ACDOCA, making
consistent financial reporting across the board.
reporting and data retrieval faster and simpler.
 VDM – Standard Interface Views

DDL Source Data Description Analytic Cube Name Source Table

Actual data of GL Line Items
I_GLAccountLineItemCube 2CIFIGLLITMCUBE ACDOCA
(with fewer fields)
Detailed journal entry items
I_JournalEntryItemCube 2CIFIDOCJRNLCUBE ACDOCA
(no balance carried forward)
I_GLAcctBalanceCube Financial Balance Amounts 2CIFIGLBALCUBE ACDOCA
I_FixedAssetValueCube Asset balance 2CIFASSETVALUECUBE ACDOCA
I_ActualPlanJrnlEntryItemC Plan and actual data for
2CIFIACTPLNJEIC ACDOCA/ACDOCP
ube journal entries
I_WorkCenterProdCostCub Production cost by work
2CIFIWCPRODCSTCUB ACDOCA/ACDOCP
e center
 VDM – Standard Consumption Views

DDL Source Analytic Cube Name DDL Source Analytic Query Name Fiori ID Transaction

I_JournalEntryItemCube
C_ServiceOrderQry2401
(Accounting Journal Entry 2CIFIDOCJRNLCUBE 2CCFISERVORDQ2401
(Service Orders - Actuals)
Item Cube)

C_SalesOrderQ2301 (Sales
2CCFISALESORDQ2301 KKBC_KUN
Orders - Actuals)

C_ProjectQ2201 (Projects -
2CCFIPROJECTQ2201
Actuals)

C_ProfitCenterQ2701 (Profit
2CCFIPROFCTRQ2701 KE80
Centers - Actuals)

C_ProfitAndLossQ2901 (P&L
2CCFIPROFLOSSQ2901 S_ALR_87012284
- Actuals)

C_MarketSegmentQ2501
2CCFIMARKSEGMQ2501 KE30
(Market Segments - Actuals)

C_FunctionalAreasQ2801
2CCFIFAQ2801
(Functional Areas - Actuals)

C_CostCenterQ2001 (Cost
2CCFICOSTCTRQ2001 S_ALR_87013611
Centers - Actuals)

I_GLAcctBalanceCube (G/L C_Trialbalanceq0001 (Trial

2CCFITRIALBALQ0001 2CCFITRIALBALQ0001 F0996A FAGLB03
Account Balance Cube) Balance)
 VDM – Standard Consumption Views

DDL Source Analytic Cube Name DDL Source Analytic Query Name Fiori ID Transaction

I_ActualPlanJrnlEntryItem C_ProjectPlanActQ2203
Cube (Actual Plan Cube for 2CIFIACTPLNJEIC (Projects - 2CCFIPROPLACTQ2203
Journal Entry Item) Baseline/EAC/Ongoing)
C_ProjectPlanActQ2201
2CCFIPRPLANACT2201 S_ALR_87013532
(Project - Plan/Actual)
C_ProfitCenterPlanActQ270
1 (Profit Center - 2CCFIPCPLANACT2701 KE30
Plan/Actual)
C_ProfitAndLossPlanActQ29
2CCFIPLPLANACT S_ALR_87012284
03 (P&L - Plan/Actual)
C_MarketSegmentPlanActQ
2501 (Market Segment - 2CCFIMSPLANACT2501 KE30
Plan/Actual)
C_InternalOrderPlanActQ21
01 (Internal Order - 2CCFIIOPLANACT2101 S_ALR_87012993
Plan/Actual)
C_FunctionalAreaPlanActQ2
801 (Functional Area - 2CCFIFAPLANACT2801 F1584A
Plan/Actual)
C_CostCenterPlanActQ2001
2CCFICCPLANACT2001 S_ALR_87013611
(Cost Center - Plan/Actual)
I_APJrnlEntrItmAgingGrid
(Aging grid of journal entry 2CIAPJEITMAGGRID C_APJrnlEntrItmAgingGrid 2CCAPJEITMAGGRID
view of Accounts Payables)
I_FixedAssetValueCube C_FixedAssetBalance (Asset
2CIFASSETVALUECUBE 2CCFASSETBAL F1617A AR01
(Asset Balances Cube) Balances)
 VDM – Standard Consumption Views

DDL Source Analytic Cube Name DDL Source Analytic Query Name Fiori ID Transaction

I_WorkCenterProdCostCub C_WorkCenterProdCostQuer
e (Production Cost By Work 2CIFIWCPRODCSTCUB y (Production Cost By Work 2CCFIWCPRODCSTQRY
Center) Center)

I_WorkCenterProdCostCub C_WorkCenterProdCostQuer
e (Production Cost By Work 2CIFIWCPRODCSTCUB y (Production Cost By Work 2CCFIWCPRODCSTQRY
Center) Center)

I_WorkCenterProdCostCub C_WorkCenterProdCostQuer
e (Production Cost By Work 2CIFIWCPRODCSTCUB y (Production Cost By Work 2CCFIWCPRODCSTQRY
Center) Center)

I_GLAccountLineItemCube
C_GLLineItemsQ0001
(Accounting Journal Entry 2CIFIGLLITMCUBE 2CCFIGLLITMQ0001 F0956A
(Journal Entry Analyzer)
Item Cube)

I_GLAccountLineItemSemT
C_Profitability_Q0001
ag (GL Account Line Item 2CIFIGLACCTLITST 2CCFIPROFQ0001
(Project Profitability)
with Semantic Tag)

C_Profitability_Q0002
2CCFIPROFQ0002
(Product Profitability)

C_CashFlowIndirectIFRS
 Use Case I: P/L actual Query

Objective: To create a finance report that provides insights into Profit and Loss
(P&L) by utilizing set hierarchies and filtering options for enhanced analysis.

1. Query Creation:
•Source: The data for the report is sourced from the I_JournalEntryItemCube.
•Tool: Custom Analytical Queries are utilized to develop the queries required
for the report.
2. Query Structure:
•Rows: The G/L Account dimension employs the activated hierarchy YCOA,
allowing for organized representation of accounts.
•Columns: The report will include the following:
• Year Month: Time period representation.
• Measure: Displays the amount in the company code currency.
3. Free Characteristics:
•The following attributes can be added for detailed analysis:
• Material Group
• Sales Document
• Chart of Account
• Company Code
• Ledger
• Posting Date
4. Hierarchy Utilization:
•The set hierarchy defined in S/4HANA can be incorporated into the Analytic
Query.
 Use Case I: P/L actual Query

4. Hierarchy Utilization:
• The set hierarchy defined in S/4HANA can be incorporated into
the Analytic Query.
• Users can choose to display this hierarchy by default or select it
manually after running the query.
• To ensure the set hierarchy data is available, it needs to be
replicated to hierarchy tables for CDS Views (HRRP*) using
transactions HRY_REPRELEV and HRRP_REP.
• Additionally, custom hierarchies can be established through
Manage Global Accounting Hierarchies.
 Use Case I: P/L actual Query
5. Filter Implementation:
• For filtering data based on Posting Date, the YEARTODATE
date function is applied, enhancing the query's flexibility.
• In the value help section for default user input values
regarding the Posting Date, users can select from date
functions predefined within the system.
6. Results Presentation:
• Upon executing the query, users will be prompted with
suggested values for Date From and Date To, facilitating
easy selection and ensuring accurate time frame analysis in Filter Implementation
the report.

Final Prompt

Month to Date Variable