Issue

Succinctly describe the issue or problem statement that this Decision addresses. Why is a decision required? What business or technical problem does it address?

This design decision document addresses the need for Syensqo to have a comprehensive profitability analysis through multi-dimensional account-based Profit and Loss (P&L) reporting to:

• Support decision-making
• Ensure compliance
• Provide real-time insights into business performance.
• Utilize universal ledger as the data pool.

The current Profit & Loss (P&L) reporting system lacks uniformity due to different reporting characteristics in the two primary data entry systems, WP1 and PF1, as well as the old system architecture that relies on secondary data and aggregate tables. As a result, Syensqo depends on numerous satellite reporting systems and custom solutions to provide uniform, multi-dimensional profitability analysis. A decision is needed to choose between account-based margin analysis and costing-based profitability analysis to address these deficiencies. It is important to note that the purpose of this design decision document is not to determine the P&L structure or the dimensions/characteristics, as these will be addressed in the detailed design phase. This decision aims to fulfill the business need for detailed, uniform, real-time profitability insights that align with the trial balance and ensure accuracy.

Recommendation

Implement Margin Analysis utilizing Account-Based Profitability Analysis instead of Costing-Based Analysis.

• This approach will enhance integration with financial accounting by consuming data directly from the transactional table.
• Provide real-time data access, and leverage the capabilities of Universal Ledger. e.g Ledger approach capabilities like P&L by ledger and currency type. 
• Additionally, it will improve online analytical processes by reducing the need for satellite system reports and possibly systems. (e.g Finance - several dashboards, BW,BI, Qlicksense, Qlickview etc)

Background & Context

Explain the context in which the decision is being made.

With evolving business complexities and the need for granular profitability insights, traditional reporting mechanisms fall short. Account based Margin Analysis offers a robust solution for detailed profitability analysis by integrating with the Universal ledger, thus eliminating reconciliation issues and enabling multidimensional reporting directly at the source. 

Technical Overview of the S4 Account-Based Margin Analysis

Margin Analysis leverages the Universal Journal (table ACDOCA) to integrate financial and managerial accounting data into a single source of truth. The Universal Journal consolidates data from various submodules such as General Ledger (FI-GL), Asset Accounting (FI-AA), Material Ledger, and Controlling (CO). This integration ensures that all financial transactions, including those relevant for profitability analysis, are stored in a single table (ACDOCA), the so-called Universal ledger which includes detailed line items for each transaction. In the Syensqo world this will means that it will be possible to have the P&L already prepared in the data entry system by activity and reconciled with the trial balance.  

Account-based CO-PA utilizes the same dimensions and characteristics available in the Universal ledger. These include company code, profit center, segment, cost center as well as and more crucially the sales flow related dimension, like customer, product, sales channels etc. The complete set of characteristics will be defined during the detailed design. 

As transactions occur, data is instantly updated in the Universal ledger, providing real-time insights without the need for batch processing or data reconciliation with the trial balance. 

Enhanced Reporting Capabilities:

• Multidimensional Reporting: Users can analyze profitability across multiple accounting, controlling and sales dimensions such as, Ledger, product, customer, region, business unit etc.
• SAP Fiori Applications: Account-based CO-PA leverages SAP Fiori applications that allow for real-time data slicing and dicing.
• SAP BW/4HANA reports: The previous SAP BW reports become now available in the Fiori user interface. With the concept of the logical data warehouse approach, SAP BW/4HANA eliminates the data replication, storage, and the need to move data from an organization’s applications
• Traditional SAP GUI Reports: For users familiar with the classic SAP interface, traditional reports are available that can utilize the same real-time data from the Universal Ledger.

A new concept that Account based - Margin analysis introduced is the use of Semantic tags in reports. Syensqo will have the flexibility to define the financial reporting items, such as revenue, COGS, labor, sales deductions, recognized margin, and so on, as semantic tags. The report creator then uses these semantic tags in the various margin analysis or financial reports instead of defining them each time a query is built. A basic example on the use of semantic tags are the tags assigned to general ledger accounts under the operational chart of accounts and defined for financial statement versions (FSV).

Here is a straightforward example of how account-based reporting functions in practice. Please note that the P&L structure provided is solely for illustrative purposes and should not be interpreted as representative of Syensqo's P&L.:

Performance Optimization

Elimination of Redundancies, by maintaining a single source of truth, data redundancies are eliminated, significantly improving data accuracy and reporting speed. Moreover, custom fields can be added to the Universal Journal to capture additional profitability characteristics specific to Syensqo's business needs or units of measure.

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

• Syensqo will implement S/4
• The data volume will be substantial, necessitating efficient data processing capabilities
• Standard SAP Fiori apps, customer CDS views and standard SAP GUI transactions, like KE30 will be available for reporting.

Constraints

Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.

• There may be a need for customization to fully leverage all reporting capabilities. Like custom CDS views.

Impacts

Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

New uniform dimensions/characteristics as well as new P&L structure will be defined during detailed design

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

• All profitability transactional data must be integrated into the Universal Ledger
• New dimensions/characteristics will be defined during detailed design to cover various dimensions such as product lines, geographies, and customer segments.

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Implement Account-based profitability analysis

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option B: Implement costing based profitability analysis

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Option A: Account based	Option B: Costing based	Option C	Option D
Integration	Seamless with Universal Ledger Con	Separate data persistence, requires reconciliation Pro	Pro Con	Pro Con
Reporting Capabilities	Supports multidimensional reporting Margin analysis is fully integrated with the Universal Journal and derives the appropriate characteristics on every journal posted to the Universal Ledger that can feed into SAP Analytics Cloud. Con	Con	Pro Pro	Con Con
Future compatibility	SAP encourages its customers to move to margin analysis, where all the innovation and investment are focused.	Con	Con	Pro
Performance

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history