You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 108 Next »

Introduction

This Data Flow Specification (DFS) defines the end-to-end data flow required to meet the following requirements:

Sub areaData flowPurposeNotesJira
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 

Incld Headcount, PlanTax
Net Working CapitalBSEG

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.

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 Assetsfixed assets (need all depreciation areas)missing, assume the std cds


Lease FXNo requirements as yet, no BCT

Statistical Key FiguresSKFSKF will be calculated in SAC and retracted to both S/4 systems. Option to plan for a value if not available

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






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 LedgersBut 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

SystemCodeExtractor NamePurposeDeltaTypeFrequencyJira RefExtended fieldsTexts

S/4 x

ACDOCA

I_GLACCOUNTLINEITEMRAWDATA

View does not implement the logic for extension ledgers (just basis ledgers)

Includes Balances Brought Forward (000)

YTDcontinuous
there will be
S/4 xBSEGI_OPERATIONALACCTGDOCITEM








I_CASHLIQUIDITYFORECASTFLOW








I_CASHLIQUIDITYACTUALFLOW
















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.

TypeCodeTech NameLogicPotential ChangesPartitioning
TL1TL_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

TL1TL_BSEG

1TL_S4HR_I_OperationalAcctgDocItem

Adds flag for cleared, based on date



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

TypeCodeTech NameLogicPotential Changes
TL2TL_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

VR2VR_GLAccItm2VR_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

VF2VF_GLAccItmV12VF_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


TL2TL_BSEG

2TL_HARM_I_OperationalAcctgDocItem

Persist after union for performance  

 

VR

2VR_HARM_I_OperationalAcctgDocItem

Adds flag for cleared, based on date

 


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

TypeCodeTech NameLogicPotential Changes

2VR_ActPlnItm
Union with the plan data
VF3VF_AcPlSemTagActlPlnJournalEntryItemSemTag

Remove redundant measures

Join ActPlan N:N SemTagGLAccount (filter for validity dates and excld FunctArea)

Can we reduce initial projection?

Need to add headcount somewhere, maybe here?

VF3VF_PFSemTagProfitLossSemanticTag

Create parameters for FinStatemtVersion and Category

Reduce dimensions (need to align to our needs)

Add associations




SemTag Leading Ledger

see BCT help doc


VR3VR_LeadLed2VR_HARM_GLAccountLineItemLeadingLedger

join on Leading Ledger


VR3VR_JEBalTSJournalEntryBalanceTimeSeries

This model provides monthly balances from GLAccountLineItemLeadingLedgerConvert SQL to graphical?

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.


VR3VR_JESTTim3VR_JEBalSTTimJournalEntryBalanceSemTagTimeSeries

This model provides monthly balances from GLAccountLineItemLeadingLedger. Convert SQL to graphical

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.


VR3VR_JESTTimJournalEntrySemTagTimeSeries

This model provides monthly balances from GLAccountLineItemLeadingLedger. Convert SQL to graphical

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 (SAP_FI_IL_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 (SAP_FI_RL_NetWorkingCapitalTimeSeries). 


VF3VF_InventInventoryTimeSeries

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. 

  • ‘BALANCE’ selects data from Journal Entry Balance Time Series,
  • 'SEMTAGBAL' from Journal Entry Balance Semantic Tag Time Series and
  • 'SEMTAG' from Journal Entry Semantic Tag Time Series.



JournalEntryOperationalViewTimeSeries

This model provides monthly balances based on journal entry line items in leading ledger joint with operational accounting document items (sourced from I_OperationalAcctgDocItem) to get details whether these items are sales-related or not (IsSalesRelated indicator). Journal Entry Operational View Time Series focuses only on normal documents (AccountingDocumentCategory = ‘’) and journal entries related to a customer (FinancialAccountType = ‘D’= or supplier (FinancialAccountType = ‘K’).




NetWorkingCapitalBalanceTimeSeriesTable



NetWorkingCapitalTimeSeries




 





 




JournalEntryItemOperationalView

ACDOCA (GLAccountLineItemLeadingLedger) + BSEG (OperationalAcctgDocItem)

This will add the 3 XREF fields














Headcount



Reporting Layer

TypeCodeTech NameLogicFunctional Spec
MA4MA_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



4MA_InventInventoryTimeSeries

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



4MA_NWCNetWorkingCapitalTimeSeries

This model is the data source of the overview page of the Working Capital Dashboard. It combines data from different areas such as Cash, Accounts Receivables, Accounts Payables, and Inventory. “Net Working Capital Balance Time Series Union” (SAP_FI_HL_NetWorkingCapitalBalanceTimeSeriesUnion) combines these areas and defines the first KPIs as a basis for the KPIs defined in “Net Working Capital Time Series Consumption” (SAP_FI_RL_NetWorkingCapitalTimeSeries).

The Net Working Capital Balance Time Series dataflow (SAP_FI_DF_NetworkingCapitalBalance) 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. To prevent this, an interim result is stored and updated hourly via the Net Working Capital Persist Task Chain task chain (SAP_FI_TC_NetWorkingCapitalPersist).

“Net Working Capital Rolling Time Series” (SAP_FI_HL_NwcRolling12MonTimeSeries) takes the interim result and creates an additional accumulated sum of rolling 12-month period. Dataflow “Net Working Capital Rolling Time Series” (SAP_FI_DF_NetWorkingCapitalRolling) aggregates this rolling 12-month period data to an interim result and stores its result in “Net Working Capital Balance Time Series Table”. The goal is to be able to calculate moving averages for specific KPI’s available in the Overview-Page and analytical Model “Net Working Capital Time Series Consumption”.



4MA_ARAPARAPOpenItem

This analytical model is the data source for the Open Payables/Receivables charts on the Accounts Payables/Receivables pages of the Working Capital Dashboard. 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.

AP/AR Line-Item Base View (SAP_FI_HL_APARLineItemBase) returns cleared vendor and customer items from "SAP_FI_HL_JournalEntryItemOperationalView" that are sales-related, for example, invoice and credit memo, and excludes the statistical items and items from recurring documents. It will only return those items that are posted in the leading ledger, which is controlled by an inner join to "SAP_FI_Ledger". This model includes those items that have been posted counting from the value of the input parameter “Key Date” (P_KEYDATE) and still not cleared at the point of Key Date.

AP/AR Open Item with Reference Join (SAP_FI_HL_APAROpenItemWRJ) selects open items with an invoice reference from the AP/AR Line Item Base View (SAP_FI_HL_APARLineItemBase). 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.

AP/AR Open Item no Reference Join (SAP_FI_HL_APAROpenItemNORJ) selects open items with no invoice reference from the AP/AR Line Item Base View (SAP_FI_HL_APARLineItemBase). In this case, the net due date of the base item is retrieved for further calculation.

AP/AR Line Item Union View (SAP_FI_HL_APARLineItemUnion) links AP/AR Open Item with the Reference Join (SAP_FI_HL_APAROpenItemWRJ) view and the AP/AR Open Item no Reference Join (SAP_FI_HL_APAROpenItemNORJ) view, which retrieves dimensions and amounts fields for both direct payment and partial payment cases of open items for further calculation.

AP/AR Open Item (SAP_FI_HL_APAROpenItem) is based on the AP/AR Line Item Union View (SAP_FI_HL_APARLineItemUnion), which calculates the days between the key date and net due date of open items and expose the minus as “NetDueArrearsDays”. As this view is used both for AP and AR page, the “ItemCategory” field is added according to “FinancialAccountType” to distinguish AP and AR items for the Working Capital Dashboard.



4MA_DSODSODrctLineItem

This analytical model is the data source for the Days Sales Outstanding (DSO) charts on the Accounts Receivable page of the Working Capital Dashboard. 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.



4MA_DPODPODrctLineItem

This analytical model is the data source for the DPO charts in the Accounts Payable page of the Working Capital Dashboard. 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.



4MA_CashBalCashBalanceTimeSeries

sourced fromtable fqm_flow which i assume we dont use (FinServices)  



4MA_CashFrcstCashForecastBalncFlw

Consumption View for Forecast Cash Balance & Flow



4MA_CashWeekCashActualFlowByWeek

 



4MA_CashDiscAPCashDiscount

This model is the data source for the discount charts on the Accounts Payable page of the Working Capital Dashboard. 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.



4MA_OnTimeOnTimePaymentRate

This model is the data source of On-time Payment Rate on the top-right corner of the Account Payable page of the Working Capital Dashboard. 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.

On Time Payment Rate Base (SAP_FI_HL_OnTimePaymentRateBase) returns cleared vendor items from SAP_FI_HL_JournalEntryItemOperationalView, which are sales-related, for example, and exclude the statistical items and items from recurring documents. It will only return those items that are posted in the leading ledger, which is controlled via an inner join to SAP_FI_Ledger. This model includes those items that have been cleared in the last 24 months counting from the value of the input parameter “Key Date” (P_KEYDATE). The view counts the number of invoice line items as InvoiceNumber and marks the invoice items by the date comparison of ClearingDate and NetDueDate. Invoice items whose ClearingDate before NetDueDate would be counted as OntimeInvoiceNumber while for items whose ClearingDate after NetDueDate would be counted as OverDueInvoiceNumber.





 




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 DescriptionSAP Table-Field Name / processComments / Calculation / Formula / Restriction dimensions and valuesAggregation of dataExample 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

FieldRequired/OptionalScopeDefaultComment
Periods (Weeks / Months / Quarters)OptionalInterval (Date or Fiscal Period)Default = last xxxxxApplied 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 DescriptionSAP Table-Field Name / processComments / Calculation / Formula / Restriction dimensions and valuesAggregation of dataExample 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_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 DescriptionSAP Table-Field Name / processComments / Calculation / Formula / Restriction dimensions and valuesAggregation of dataExample SAP field data
Notification CountProcess: constant 1 per recordBase measure for notification-level counting.SUM1



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 

DimensionDesignVariableParameter
Consol COA
Mandtory
Consol Group
Mandtory
Version
Mandtory
FYPeriod
Mandtory
PrfctHier

Mandtory
SegmentHier

Mandtory
UnitHier

Mandtory
Key date

Mandtory
Ref Date

Mandtory
Seg for Elim0

Segment1

Proft Centre elim2

Profit Centre3

Consol Unit4

FinStatItem5

Doc Type6

SubItem7

Elim Member8

Supplier9

Cost Centre10

Cont Area11

Missing: Asset

Calculated Measures (Post Aggregation Calculations / exception aggregation etc)

Consider using a structure for Current and Prior, movement(variance)

Report Field DescriptionSAP Table-Field Name / processComments / Calculation / Formula / Restriction dimensions and valuesAggregation of dataExample SAP field data

Transaction Amount



SUM

Company Amount



SUM

Group Amount



SUM

Quantity



SUM


Outbound Layer

  • No labels