Introduction
This Data Flow Specification (DFS) defines the end-to-end data flow required to meet the following requirements:
| Sub area | Data flow | Purpose | Notes | Jira |
|---|---|---|---|---|
| Financial Ledger Reporting | ACDOCA | Replicating business content for GLAccountLineItemRawData to create Semantic tags model that is used for financial reporting It mirrors the CDS views used in S/4 but creates the semantic tag model in a more logical fashion that in S/4 (removes the hard coding in the CDS views) This model provides all journal entry details. Organisational entities such as Company Code, Profit Centre, Cost Centre, Business Area, Functional Area, Financial dimensions like Ledger, G/L Account, Segment, Financial Document Type, Posting Key, Debit/Credit Code, are available in this data model. The model provides a source ledger as well as all the ledgers that apply to the relevant company codes. This model maps the journal entries to the semantic tags defined based on G/L Accounts. The semantic tags based on functional areas are not considered in this model. Differs in some way to the Functional Area Semantic Tag model Potentially need to create another AM to view different I_JournalEntryItem - this separates AMOUNT by Dr/Cr - suggested for data flows (and suggesting using BALANCE from acdoca) | Incld Headcount, Plan | Tax |
| Net Working Capital | BSEG | The Operation Accounting Document item view provides details of an operational accounting document item (sourced from BSEG) like clearing document details, payment data, and tax data. The long-term vision is that table BSEG will be used only for open item management Used as the foundation of accounts receivable and accounts payable analysis, such as total payables and receivables, overdue receivables and payables, and future receivables. Generates a balance and movements model (else look at stock, treasury and Group Reporting for inspiration) There is a model that should cover the requirement for the 3 XREF fields not in ACDOCA | Leading ledger only | |
| Fixed Assets | fixed assets (need all depreciation areas) | missing, assume the std cds Actual values from tables ANEP, ANEA, ANLP, ANLC are saved in table ACDOCA in new Asset Accounting. The values from table ANEK are saved in tables BKPF and ACDOCA in new Asset Accounting. Postings are still made to the table BSEG. | ||
| Lease FX | No requirements as yet, no BCT | |||
| Statistical Key Figures | SKF | SKF will be calculated in SAC and retracted to both S/4 systems based on company code. SKF can be amended in S/4 and need to be extracted back into DSP | ||
| Group Reporting | Std model cash flow loads of schedules - does it make sense to add a planning model for data capture? eg goodwill breakdown I dont think it does the YTD model anymore They run quarterly. projecting the 3rd Q forwards to predict the end picture | Planning is not included in this model - need to add | ||
| Balances | There is a CDS called C_GLAccountBalance_F0707A This is implemented via a class Predessor was probably C_CN_GLAccountBalanceSumQuery but this also uses a class |
Vision:
The vision is to be able to run a sales report showing Net Sales from GR with a drill down to S/4
Concern is that any drill down will go to ACDOCU at best?
In a perfect world, we would create a KPI once and share it, to ensure consistency.
If a KPI is only calculated in the Analytical Model, it will not be shared. Reasons for defining at this level are:
- Performance on aggregated data is better
- Some KPI's must be calculated pre aggregation eg price x quantity
Can remove the measures for alternate currency /quantity as we will not use these as per KDD047 Universal parallel Ledgers. But then how does this fit in with currency roles?
Reporting is done in tons so store rather than calc. Where if we dont persist again
Probably the same for value at bud rate. It has been decided that this will not be persisted but rather calculated.
Commentary will be added per model. This is not ideal as there is no leverage.
Source System Extractors
| System | Code | Extractor Name | Purpose | Delta | Frequency | Jira Ref | Extended fields |
|---|---|---|---|---|---|---|---|
S/4 x | ACDOCA | I_GLACCOUNTLINEITEMRAWDATA | View does not implement the logic for extension ledgers (just basis ledgers) Includes Balances Brought Forward (000) | Y | continuous | there will be | |
| S/4 x | BSEG | I_OPERATIONALACCTGDOCITEM | |||||
| I_CASHLIQUIDITYFORECASTFLOW | |||||||
| S/4 x | FQMFLOW | I_CASHLIQUIDITYACTUALFLOW | Cash liquidity actual flow for working capital inventory. Does not offer dimensions for PC, debtor, vendor, segment | Y | |||
Inbound Layer
No inbound field adjustments are applied. Standard technical fields (load date/time, source system) are retained as delivered.
Persist data as found in the source system CDS view. This should be including any extensions.
Any data sourced from both S/4 environments, will be created using delta capture and re-persisted in Harmonisation layer. Assumption is that this data can be in cold storage if available.
In the Business Content, some calculated fields are populated with Null values to make the model compatible with SAP S/4HANA release 2020. These fields will now be added in the 1TL object and mapped, removing the NULL calculation.
| Type | Code | Tech Name | Logic | Potential Changes | Partitioning |
|---|---|---|---|---|---|
| TL | 1TL_ACDOCA | 1TL_S4HR_I_GLAccountLineItemRawData | Retain all 402 fields even though SAP Business Content has 60 fields less. As the BCT is based on SAP 2023, I assume that these are new fields | extensions | Source Ledger = 0L, CO, LG, LT, TX (will always be specified) Fiscal Year = I guess can be specified |
| TL | 1TL_BSEG | 1TL_S4HR_I_OperationalAcctgDocItem | Adds flag for cleared, based on date | ||
| TL | 1TL_CashA | 1TL_S4HR_I_CashLiquidityActualFlow | Lover levels of the CDS have more dimensions, why are they excluded? cust, vend, PC, WBS, material | add dimensions? | |
CDS View I_SemTagGLACcount from SAP S/4HANA provides the mapping between the G/L accounts and semantic tags. It is the key component of this model.
This CDS view does not have any key fields. The replication of data without key fields from CDS Views is not supported by the Replication Flow at moment. Instead the local table SAP_FI_IL_I_SemTagGLAccount is used in this model to support both SAP S/4HANA Cloud and SAP S/4HANA source systems. The inbound layer view SAP_FI_IL_SemTagGLAccount is based on this table.
Customer should perform the following activities after importing the content package:
Create a remote table from CDS View I_SemTagGLAccount of the connected SAP S/4HANA system and replicate the data.
Create a dataflow to populate the local table SAP_FI_IL_I_SemTagGLAccount from the remote table. (For SAP S/4HANA Cloud sources a conversion from Date to String Datatype is needed in the dataflow.)
or
Replace the local table SAP_FI_IL_I_SemTagGLAccount with the remote table in the inbound layer view SAP_FI_IL_ SemTagGLAccount.
The Inbound layer view G/L Account with Semantic Target (IL) (SAP_FI_IL_ SemTagGLAccount) is based on the local table SAP_FI_IL_I_SemTagGLAccount and has some simple data type conversions like date conversion.
Harmonisation Layer
Both transaction data or master data that is not tier 1 will require a union between environments and re-persisted. This is to improve performance.
As soon as a local table is joined with another dataset, the reference is lost and the "I" from the extractor can be dropped
| Type | Code | Tech Name | Logic | Potential Changes |
|---|---|---|---|---|
| TL | 2TL_ACDOCA | 2TL_HARM_I_GLAccountLineItemRawData | Persist after union for performance remove additional amount/quantity fields Perform any calculations likes tonnes conversion and potentially conversion to budget group currency | Set as Delta Capture Requires delete and recreate and you lose all the conversions |
| VR | 2VR_GLAccItm | 2VR_HARM_GLAccountLineItem | Changing name to replicate the corresponding CDS in S/4 Dates: cast to DATE | Could I combine with the next level? Would love to add XREF from BSEG. see union |
| VF | 2VF_GLAccItmV1 | 2VF_HARM_GLAccountLineItem V1 | I_LedgerSourceLedger joined to I_LedgerCompanyCodeCrcyRoles to provide all the ledgers available to a company code This has the effect of exploding the rows to ensure that all ledgers are created for every source ledger Calculations: derive when statistical assignments for WBS, Sales Doc, Order, Cost Centre | pic shows as relational, sap is fact |
| TL | 2TL_BSEG | 2TL_HARM_I_OperationalAcctgDocItem | Persist after union for performance | Set as Delta Capture |
| VR | 2VR_OpsItm | 2VR_HARM_I_OperationalAcctgDocItem | Adds flag for cleared, based on date |
|
| TL | 2TL_Cash | 2TL_HARM_I_CashLiquidityActualFlow |
| |
| VR | 2VR_Cash | 2VR_HARM_I_CashFlowActualItem | Read from CashLiquidityActualFlow (adding fields that dont get populated) Amend to include the previous layer (casting date) | Convert SQL to graphical? |
|
Propagation Layer
Only at this layer will we add additional datasets like plan and headcount
I am worried that the BSEG leg does not use PLAN
Ensure we perform group by when aggregating......
| Type | Code | Tech Name | Root | Logic | Potential Changes |
|---|---|---|---|---|---|
| Headcount | |||||
| 2VR_ActPlnItm | ACDOCA/ PLAN | 2VF_HARM_GLAccountLineItem V1 union with the plan data | |||
| VF | 3VF_AcPlSemTag | ActlPlnJournalEntryItemSemTag | ACDOCA/ PLAN | Join ActPlan N:N SemTagGLAccount (filter for validity dates and excld FunctArea) Remove redundant measures | Can we reduce initial projection? Need to add headcount somewhere, maybe here? |
| VF | 3VF_PFSemTag | ProfitLossSemanticTag | ACDOCA/ PLAN | Create parameters for FinStatemtVersion and Category Reduce dimensions (need to align to our needs) Add associations | |
| SemTag Leading Ledger | ACDOCA/ PLAN | ||||
| VR | 3VR_LeadLed | GLAccountLineItemLeadingLedger | ACDOCA | Restrict to Leading Ledger | |
| VR | 3VR_JEBalTS | JournalEntryBalanceTimeSeries | ACDOCA | Every month includes all postings belonging to this month and all postings from the past, and aggregates the data as cumulative balances Therefore, it excludes all postings with Fiscal Period ‘000’, which can be viewed as balance carry-forward items, which otherwise would lead to double counted values. | Convert SQL to graphical? |
| VR | 3VR_JESTTim3VR_JEBalSTTim | JournalEntryBalanceSemTagTimeSeries | ACDOCA | The semantic tags based on functional areas are not considered in this model. Every month includes all postings belonging to this month and all postings from the past, and aggregates the data as cumulative balances Therefore, it excludes all postings with Fiscal Period ‘000’, which can be viewed as balance carry-forward items, which otherwise would lead to double counted values. | Convert SQL to graphical? |
| VR | 3VR_JESTTim | JournalEntrySemTagTimeSeries | ACDOCA | The semantic tag assignments only consider G/L Accounts. Each month shows the changes or postings that occurred in this month. The values of the Financial Data Model Configuration (FinancialDataModelConfiguration) table are not fixed and can be changed by the user. If you define a G/L Account Hierarchy before joining with G/L Account with Semantic Tag (IL), you restrict the data from Journal Entry item Operational View to a single G/L Account Hierarchy by default. This is a requirement for Net Working Capital Time Series Consumption (NetWorkingCapitalTimeSeries). | Convert SQL to graphical? |
| VF | 3VF_Invent | InventoryTimeSeries | ACDOCA | Combines data from “Journal Entry Balance Time Series”, “Journal Entry Balance Semantic Tag Time Series” and “Journal Entry Semantic Tag Time Series”. Some semantic tag KPIs must include data from the past months, whereas others need to consider only the movements of the relevant months. Every branch introduces a calculated field UnionBranch which is included in some KPIs to check which type of data should be considered.
| |
| Cash Balances |
|
| |||
| VR | 3VR_CashTS | CashBalanceTimeSeries | CashA | Read from CashFlowActualItem, returns cash balance with bank account on End of MonthDate
| SQL to Graphic View? |
| TL | 3TL_CashBalT | TotalCashBalanceTimeSeriesTable | CashA | Dataflow aggregates an interim result from CashBalanceTimeSeries and persists the results for performance. This table is updated on an hourly basis. | |
| VF | 3VF_CashBalC | TotalCashBalanceTimeSeriesCube | CashA | Projection of TotalCashBalanceTimeSeriesTable adding associations | |
| Net Working Capital |
|
| |||
| VR | 3VR_GLAccOps | JournalEntryItemOperationalView | ACDOCA/ BSEG | ACDOCA (GLAccountLineItemLeadingLedger) + BSEG (OperationalAcctgDocItem). 1:N This will add the 3 XREF fields | |
| VR | 3VR_OpsItemTS | JournalEntryOperationalViewTimeSeries | ACDOCA/ BSEG | Reads using SQL, JournalEntryItemOperationalView with inner join on TimeSeriesMonthlyValues to restrict to monthly balances Restricted to Debtors and Creditors and excludes Statistical Items Flag for items that are sales-related or not (IsSalesRelated indicator). Performs the currency role selection | SQL to Graphic View? |
| 3VR_NWCTSUn | NetWorkingCapitalBalanceTimeSeriesUnion | ACDOCA/ BSEG | Union of:
| SQL to Graphic View? | |
| 3TL_NWCTable | NetWorkingCapitalBalanceTimeSeriesTable | ACDOCA/ BSEG | A dataflow retrieves the data from “Net Working Capital Balance Time Series Union” and aggregates an interim result that is stored in the Net Working Capital Balance Time Series table. When you combine data from multiple areas, this may result in complex KPIs on top and may lead to serious performance issues, as live data from the inbound layer is processed to calculate the KPIs.
| Replace DF with Transformation Flow | |
| VF | 3VF_NWCCube | NetWorkingCapitalBalanceTimeSeriesCube | ACDOCA/ BSEG | Just a projection (removing Amount in Group Currency?) on NetWorkingCapitalBalanceTimeSeriesTable | Add Grp Curr? |
| Payables / Receivables |
|
| |||
| VR | 3VR_OpsItemPr | OperationalAcctDocItemProj | BSEG | Convert SQl to Graphical view (just restricting the fields read from OperationalAcctgDocItem) | SQL to Graphic View? |
| VR | 3VR_APItmBase | APARLineItemBase | ACDOCA/ BSEG | Read JournalEntryItemOperationalView Returns cleared vendor and customer items that are sales-related, for example, invoice and credit memo, and excludes the statistical items and items from recurring documents.
| SQL to Graphic View? |
| VR | 3VR_APARWR | APAROpenItemWRJ | ACDOCA/ BSEG | Reading from APARLineItemBase and restricting by joining on OperationalAcctDocItemProj to sales related, doc type <> V/P , Inv ref not Null Selects open items with an invoice reference (payments) When calculating arrears days for partial payment cases for base invoice items, the net due date of the reference item would be used instead of the net due date of the base item. | SQL to Graphic View? |
| VR | 3VR_APARNorj | APAROpenItemNORJ | ACDOCA/ BSEG | Reading from APARLineItemBase and restricting to doc type V/P, Inv ref is Null Selects open items with no invoice reference (partial payments). The net due date of the base item is retrieved for further calculation. | SQL to Graphic View? |
| VR | 3VR_APARUnion | APARLineItemUnion | ACDOCA/ BSEG | Links AP/AR Open Item with the Reference Join (APAROpenItemWRJ) view and the AP/AR Open Item no Reference Join (APAROpenItemNORJ) view, which retrieves dimensions and amounts fields for both direct payment and partial payment cases of open items for further calculation. | SQL to Graphic View? |
| VR | 3VR_APAROpen | APAROpenItem | Reading from APARLineItemUnion
| SQL to Graphic View? Please dont use OIDs Anymore. Product and CostCenter are exceptions right now. | |
| VF | 3VF_APAROpenC | APAROpenItemC | ACDOCA/ BSEG | Adding Associations | |
| Days Sales Outstanding |
|
| |||
| VF | 3VF_DSOBase | DaysSalesOutStdgDrctBase | ACDOCA/ BSEG | Reading from JournalEntryItemOperationalView
| SQL to Graphic View? prior year? |
| VR | 3VF_DSOAgg | DaysSalesOutStdgDrctLineItem | ACDOCA/ BSEG | Nested select from DaysSalesOutStdgDrctBase (for calculations before group by?)
Why is it called line item when aggregated? | SQL to Graphic View? |
| VR | 3VF_DSOTS | DaysSalesOutStdgDrctLineItemTmeSers | ACDOCA/ BSEG | Nested select from CalendarMonth with left outer join on DaysSalesOutStdgDrctLineItem To perform if before aggregation? | SQL to Graphic View? perform string on lower level? |
| VF | 3VF_DSOCube | DSODrctLineItem | ACDOCA/ BSEG | Add associations | |
| Days Payable Outstanding |
|
| |||
| VF | 3VF_DPOBase | DaysPyblOutStdgDrctBase | ACDOCA/ BSEG | Reading from JournalEntryItemOperationalView
| SQL to Graphic View? prior year? |
| VR | 3VF_DPOAgg | DaysPyblOutStdgDirect | ACDOCA/ BSEG | Nested select from DaysPyblOutStdgDrctBase (for calculations before group by?)
Why is it called line item when aggregated? | SQL to Graphic View? |
| VR | 3VF_DPOTS | DaysPyblOutStdgDrctLineItemTmeSers | ACDOCA/ BSEG | Nested select from CalendarMonth with left outer join on DaysPyblOutStdgDrctLineItem To perform if before aggregation? | SQL to Graphic View? perform string on lower level? |
| VF | 3VF_DPOCube | DPODrctLineItem | ACDOCA/ BSEG | Add associations | |
| On Time Payments |
|
| |||
| VR | 3VR_OTPBase | OnTimePaymentRateBase | ACDOCA/ BSEG | Reading from JournalEntryItemOperationalView, returns cleared vendor items
| SQL to Graphic View? Time range as 2 years |
| VR | 3VR_OTPAgg | OnTimePaymentRateSum | ACDOCA/ BSEG | Nested select from OnTimePaymentRateBase (for calculations before group by?)
| SQL to Graphic View? |
| VF | 3VF_OTPCube | OnTimePaymentRate | ACDOCA/ BSEG | Add associations | |
| Cash Discounts |
|
| |||
| VR | 3VR_DiscBase | APCshDiscRealizedBase | ACDOCA/ BSEG | Reading from OperationalAcctgDocItem
| SQL to Graphic View? |
| VR | 3VR_DiscCnv | APCshDiscRealizedConvert | ACDOCA/ BSEG | Reading from APCshDiscRealizedBase, returns cleared vendor items
| SQL to Graphic View? |
| VR | 3VR_DiscAgg | APCshDiscRealized | ACDOCA/ BSEG | Nested select from APCshDiscRealizedConvert (for calculations before group by?)
| SQL to Graphic View? |
| VF | 3VF_DiscCube | APCshDiscRealizedC | ACDOCA/ BSEG | Add associations | |
Reporting Layer
| Type | Code | Tech Name | Logic | Functional Spec |
|---|---|---|---|---|
| MA | 4MA_PL_SemTag | 4MA_R2RGLR_SemanticTags | ProfitLossSemanticTagKPIs Currency handling: select single based on role Quantity Conversion: Measures: 19 restricted by Semantic tags and simple calculations Variables: FinStatemtVersion, Category, Date | |
| MA | 4MA_Invent | InventoryTimeSeries | Provides a balance and movements for the entire TB (not sure why called inventory) - includes semantic tags Dimensions: a limited set - will have to review if adequate Currency handling: select single based on role Quantity Conversion: Measures: 19 restricted by Semantic tags and simple calculations Variables: FinStatemtVersion, Category, Date | |
| MA | 4MA_NWC | NetWorkingCapitalTimeSeries | Read from NetWorkingCapitalBalanceTimeSeriesCube. The goal is to be able to calculate moving averages for specific KPI’s It combines data from different areas such as Cash, Accounts Receivables, Accounts Payables, and Inventory. When you combine data from multiple areas, this may result in complex KPIs on top and may lead to serious performance issues, as live data from the inbound layer is processed to calculate the KPIs. To prevent this, an interim result is stored and updated hourly via the Net Working Capital Persist Task Chain task chain | |
| MA | 4MA_ARAP | ARAPOpenItem | It provides overdue payables/receivables, future payables/receivables, and total payables/receivables in the point of Key Date. This analytical model distinguishes open items to overdue and future items by the comparison of posting date and net due date of open invoice items. | |
| MA | 4MA_DSO | DSODrctLineItem | It provides per calendar month the measures DSO, Best Possible DSO and the DSO 12 months before. Days Sales Outstanding (DSO) is to measure the time elapsed between the completion of a sale and the collection of the revenue, that is, the time taken to process accounts receivable items. This analytical model calculates DSO according to the direct calculation method. The direct calculation method is based on original documents. The period of time between posting an invoice (posting date) and receiving the payment for the invoice (clearing date) is calculated for the relevant document line item to provide accurate results. | |
| MA | 4MA_DPO | DPODrctLineItem | This model provides measures DPO and corresponding DPO 12 months before according to the direct calculation method. Direct Days Payables Outstanding (DPO) is calculated based on the period of time between posting an invoice (posting date) and actual paying for the invoice (clearing date) along with the invoice amount. | |
| MA | 4MA_CashBal | CashBalanceTimeSeries | Provides cash balance with bank account on End of MonthDate. The cash balance amount is represented by two currencies, that is, Company Code Currency and Global Currency. Cash Balance also contains the transaction currency amount and bank information, as it can be drilled down by Transaction Currency and bank dimension. | more dmensions? |
| MA | 4MA_CashFrcst | CashForecastBalncFlw | Consumption View for Forecast Cash Balance & Flow | |
| MA | 4MA_CashWeek | CashActualFlowByWeek |
| |
| MA | 4MA_DiscAP | APCashDiscount | This model provides measures realized discount, lost discount, discounted spend, and discount realization rate, which is calculated based on the discount-related fields on invoice line items along with the invoice amount. | |
| MA | 4MA_OnTime | OnTimePaymentRate | This model provides measures on-time payment rate from year to Key Date and its comparison rate of the whole last calendar year based on the date comparison between actual paying for the invoice (clearing date) and proposed payment date for the invoice (net due date) along with the invoice number count. | |
| ||||
| Balance with movements | can i do the same for other areas besides WCap above? | |||
| Assets | ||||
| Restructering | ||||
| HSE |
4MA_R2RGLR_SemanticTags
Supports:
- ERP-682 Tax
- ERP-1321 Corporate insurance
Includes technical details for:
- Post-aggregation calculations
- Restricted measures
- Time-based analysis and drill-through
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
|---|---|---|---|---|
Inverted amount | Amount In Global Currency * -1 | Calculated | ||
Amortization of Intangible Asset | Inverted amount when Semantic Tag = 'AMORINASST' | Restricted | ||
COGS | Inverted amount when Semantic Tag = 'RECO_COS' | Restricted | ||
Depreciation of Tangible Assets | Inverted amount when Semantic Tag = 'DPRTASSET' | Restricted | ||
Gross Revenue | Inverted amount when Semantic Tag = 'GROSS_REV' | Restricted | ||
Income Tax | Inverted amount when Semantic Tag = 'INCOMETAX' | Restricted | ||
Net Income | Inverted amount when Semantic Tag = 'PL_RESULT' | Restricted | ||
Net Revenue | Inverted amount when Semantic Tag = 'RECO_REV' | Restricted | ||
Employee Expense | Amount in Global Currency when Semantic Tag = 'EMPLEXP' | Restricted | ||
Operating Expense | Inverted amount when Semantic Tag = 'OPEREXP' | Restricted | ||
Recognized Revenue | Inverted amount when Semantic Tag = 'RECO_REV' | Restricted | ||
Gross Profit | Recognized Revenue + COGS | Calculated | ||
Gross Margin | (Gross Profit / Recognized Revenue) * 100 | Calculated | ||
Total Operating Expense | COGS + Operating Expense | Calculated | ||
Operating Profit | Recognized Revenue + Total Operating Expense | Calculated |
Restricted Measures
tbd
Currency Conversions
tbd
Variables
| Field | Required/Optional | Scope | Default | Comment |
| Periods (Weeks / Months / Quarters) | Optional | Interval (Date or Fiscal Period) | Default = last xxxxx | Applied using CreationDate or CreationDateTime |
Data access controls
4MA_R2RGLR_Account Balance & Movements
Supports:
- ERP-1564 Balances
- cash flow
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
|---|---|---|---|---|
Amount in Currency Role Currency (AmountInCurrencyRoleCurrency) | Source measure for every measure described here. This measure distinguishes between Amount in Global Currency and Amount in Company Code Currency. | |||
Capital Employed (CapitalEmployed) | TotalAssets-CurrentLiabilities | |||
Cash Asset Ratio (CashAssetRatio) | Liquidity/CurrentLiabilities based on semantic tag 'CSH_CSHEQV' and 'CURLIABEQU'. | |||
Cash Asset Ratio Last (CashAssetRatioLast) | CashAssetRatio with exception aggregation LAST | |||
Cost Of Sales (CostOfSalesAmount) | Shows SemanticTag = 'RECO_COS' assigned movements within a month. UnionBranch = ‘SEMTAG’. | |||
Current Liabilities – LAST (CurrentLiabilities) | Displays SemanticTag = 'CURLIABEQU' assigned balances cumulated on month level with exception aggregation LAST. UnionBranch = ‘SEMTAGBAL’. | |||
EBIT (EBIT) | NetIncomeAmount-(IncomeTax+Interest) | |||
Income Tax (IncomeTax) | Displays SemanticTag = 'INCOMETAX' assigned movements within a month. UnionBranch = ‘SEMTAG’. | |||
Interest (Interest) | Displays SemanticTag = 'INTEREST' assigned movements within a month. UnionBranch = ‘SEMTAG’. | |||
Liquidity – LAST (Liquidity) | Displays SemanticTag = 'CSH_CSHEQV' assigned balances cumulated on month level with exception aggregation LAST. UnionBranch = ‘SEMTAGBAL’. | |||
Marketable Securities – LAST (MarketableSecuritiesAmount) | Displays SemanticTag = 'MARK_SEC' assigned balances cumulated on month level with exception aggregation LAST. UnionBranch = ‘SEMTAGBAL’. | |||
Net Income (NetIncomeAmount) | Displays SemanticTag = 'PL_RESULT' assigned movements within a month. UnionBranch = ‘SEMTAG’. | |||
Number Of Days In Month (NumberOfDaysInMonth) | Displays the number of days of every month based on Time Series Date that provides the end date of a month. | |||
Numbers Of Days In Month Max (NumbersOfDaysInMonthMax) | MAximum Number of Days In Month to provide the number of days of the selected time range. | |||
Quick Ratio (QuickRatio) | TotalLiquidityLast/CurrentLiabilities | |||
ROCE (ROCE) | Refers to a financial ratio that assesses the profitability and capital efficiency of a company by dividing EBIT by Capital Employed. Capital Employed = Total Assets - Current Liabilities, which are based on Semantic Tag 'ASSET' and 'CURLIABEQU'. Formula: EBIT/CapitalEmployed | |||
ROCE Last (ROCELast) | LAST of ROCE | |||
Total Assets – LAST (TotalAssets) | Shows SemanticTag = 'ASSET' assigned balances cumulated on a monthly basis with exception aggregation LAST. UnionBranch = ‘SEMTAGBAL’. | |||
Total Inventory (TotalInventory) | Displays data assigned with TransactionTypeDetermination = 'BSX' cumulated on a monthly basis. UnionBranch = ‘BALANCE’. | |||
Total Inventory Average (TotalInventoryAverage) | Average of Total Inventory based on Time Series Date that provides the end date of a month. | |||
Total Liquidity (TotalLiquidity) | Displays your Total Liquidity based on 'Cash and Cash Equivalence' (Semantic Tag 'CSH_CSHEQV'), 'Marketable Securities' (Semantic Tag 'MARK_SEC'), and 'Accounts Receivables'. Accounts Receivables includes all open invoices up to the current month (Financial Account Type = 'D' and isOpen = 'X'). Formula: SemanticTag = 'CSH_CSHEQV' or ( SemanticTag = 'ACCREC2') or SemanticTag = 'MARK_SEC'. | |||
Total Liquidity Last (TotalLiquidityLast) | Displays Total Liquidity balances cumulated on a monthly basis with exception aggregation LAST. |
4MA_R2RGLR_APAROpenItems
Supports:
- ERP-
Includes technical details for:
- Time-based analysis of Open Items
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
|---|---|---|---|---|
| Amount | Currency derived using currency roles | SUM | 1 |
4MA_R2RGLR_APCashDiscount
Supports:
- ERP-
Includes technical details for:
- realized discount, lost discount, discounted spend, and discount realization rate, which is calculated based on the discount-related fields on invoice line items along with the invoice amount.
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
|---|---|---|---|---|
| Discount realisation rate | SUM | 1 | ||
| On time payment rate | OntimeInvoiceNumber / InvoiceNumber | |||
| Overdue payment rate | OverDueInvoiceNumber / InvoiceNumber |
4MA_R2RGLR_Depreciation
Supports:
- ERP-293 - Depreciation Areas
Includes technical details for:
- Post-aggregation calculations in SAC (e.g., hours conversions, ratios, availability formulas)
- Restricted measures by breakdown / downtime flags and status
- Time-based analysis (malfunction start/end, creation dates) and drill-through to Maintenance Notification
Dimensions & Measures are defined in the Functional Specification under “Dimensions & Measures: Requirements View”; the analytical model exposes those fields at notification grain without pre-aggregation.
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
| Notification Count | Process: constant 1 per record | Base measure for notification-level counting. | SUM | 1 |
4MA_R2RGR_GrpJrnlMtrxElm
Supports:
- ERP-
Includes technical details for:
- Post-aggregation calculations in SAC (e.g., hours conversions, ratios, availability formulas)
- Restricted measures by breakdown / downtime flags and status
- Time-based analysis (malfunction start/end, creation dates) and drill-through to Maintenance Notification
Dimensions & Measures are defined in the Functional Specification under “Dimensions & Measures: Requirements View”; the analytical model exposes those fields at notification grain without pre-aggregation.
Dimensions (significant only)
Assume that Semantic Tags cannot be used
Attribute for discontinued ops?
| Dimension | Design | Variable | Parameter |
|---|---|---|---|
| Consol COA | Mandtory | ||
| Consol Group | Mandtory | ||
| Version | Mandtory | ||
| FYPeriod | Mandtory | ||
| PrfctHier | Mandtory | ||
| SegmentHier | Mandtory | ||
| UnitHier | Mandtory | ||
| Key date | Mandtory | ||
| Ref Date | Mandtory | ||
| Seg for Elim | 0 | ||
| Segment | 1 | ||
| Proft Centre elim | 2 | ||
| Profit Centre | 3 | ||
| Consol Unit | 4 | ||
| FinStatItem | 5 | ||
| Doc Type | 6 | ||
| SubItem | 7 | ||
| Elim Member | 8 | ||
| Supplier | 9 | ||
| Cost Centre | 10 | ||
| Cont Area | 11 |
Missing: Asset
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
Consider using a structure for Current and Prior, movement(variance)
| Report Field Description | SAP Table-Field Name / process | Comments / Calculation / Formula / Restriction dimensions and values | Aggregation of data | Example SAP field data |
Transaction Amount | SUM | |||
Company Amount | SUM | |||
Group Amount | SUM | |||
Quantity | SUM |


