🏠 Home FPR Tower Architecture 📝 ADA Editor ↗
IAO Architecture

DC-100 — Revenue Recognition

Architecture Document (TOGAF BDAT)

Finance Plan To Report (FPR) Tower
Capability DC-100 · DC Manage Accounting and Control Data

IAO Program · R1 – R5
Generated: May 2026
Sajiv Francis

IAO Architecture Pipeline — Intel Confidential

Page 1↑ Back to TOCDC-100 — Revenue Recognition

Table of Contents

Page 2↑ Back to TOCDC-100 — Revenue Recognition

1. Executive Summary

This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for DC-100 Revenue Recognition within the IAO program. It includes 6 BPMN process diagram(s) in Section 3.

Dimension Value
Tower Finance Plan To Report (FPR)
Process Group DC Manage Accounting and Control Data
Capability DC-100 - Revenue Recognition
Release R1 – R5
Total Systems 0
System Status 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM
RICEFW Objects 1 Reports, 1 Interfaces, 12 Enhancements

System nodes in architecture diagrams are IAPM-linked where matches exist (0/0 matched) — click any linked node to open its IAPM page. Diagrams require securityLevel: 'loose' for click events.

Page 3↑ Back to TOCDC-100 — Revenue Recognition

2. Business Context & Objectives

2.1 Classification

Level Value
L0 Tower Finance Plan To Report
L1 Process DC Manage Accounting and Control Data
L2 Capability DC-100 - Revenue Recognition

2.2 Business Drivers

# Driver Description Strategic Alignment Priority
1 S/4 HANA Finance Consolidation Migrate legacy costing and reporting platforms to unified S/4 HANA finance backbone IDM 2.0 Core Finance Transformation High
2 Real-Time Financial Visibility Enable real-time cost reporting and variance analysis replacing batch-driven legacy processes CFO Digital Finance Initiative High
3 Regulatory Compliance Readiness Ensure SOX compliance and audit trail continuity through the ERP transition period Intel Corporate Compliance Medium
4 DC-100 Process Migration Migrate DC-100 business processes and 0 integrated systems from legacy to S/4 HANA target architecture IDM 2.0 Finance High
Page 4↑ Back to TOCDC-100 — Revenue Recognition

2.3 Success Criteria

Metric Target Measure Baseline Owner
Month-End Close Cycle Time < 3 business days Calendar days from period close trigger to final posting 5 business days (legacy) Finance Controller
Cost Variance Accuracy < 0.5% deviation Variance between standard and actual cost post-migration 1.2% (ICOST baseline) Cost Accounting Lead
System Availability (Finance) 99.9% uptime S/4 HANA finance module availability during business hours 99.5% (legacy) IT Operations
DC-100 Migration Completeness 100% flow chains validated All 0 flow chains verified in target state 0% (pre-migration) Tower Architect

2.4 Companion Documents

Document Description
Business Architecture Included in this document (Section 3) — process flows from BPMN diagrams
This Document Full BDAT Architecture — Business + Data + Application + Technology
Page 5↑ Back to TOCDC-100 — Revenue Recognition

3. Business Architecture (TOGAF “B”)

3.1 Business Process Overview

This capability includes 6 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for DC-100 Revenue Recognition.

# Step ID Process Name Lanes Tasks Gateways
1 DC-100-010_Create_Revenue_Accounting_Contracts DC-100-010_Create_Revenue_Accounting_Contracts RAR IT Support Analyst, Revenue Accountant 4 2
2 DC-100-030_RAR_Closing_and_Reconciliation DC-100-030_RAR_Closing_and_Reconciliation Revenue Accountant 15 12
3 DC-100-040_RAR_Reports DC-100-040_RAR_Reports Revenue Accountant 8 1
4 DC-100-050_Define_Transaction_Price DC-100-050_Define_Transaction_Price Revenue Accountant 0 0
5 DC-100-060_Determine_Performance_Obligations DC-100-060_Determine_Performance_Obligations RAR IT Support Analyst, Revenue Accountant 4 2
6 DC-100-070_Allocate_Transaction_Price DC-100-070_Allocate_Transaction_Price Revenue Accountant 0 0
Page 6↑ Back to TOCDC-100 — Revenue Recognition

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 DC-100-010_Create_Revenue_Accounting_Contracts — DC-100-010_Create_Revenue_Accounting_Contracts

Swim Lanes: RAR IT Support Analyst · Revenue Accountant | Tasks: 4 | Gateways: 2

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["RAR IT Support Analyst"] n1["fa:fa-user Resolve the Error for RAR Contract and Reprocess"] n4[["fa:fa-cog Perform Real Time Processing of Revenue Accounting Items"]] n8{{"fa:fa-code-branch If RAI is in Postponed Status then it needs to be Reprocessed?"}} end subgraph lane_1["Revenue Accountant"] n2["fa:fa-user View and Manage RAR Contract"] n3["fa:fa-user Display Sales Order for RAR Contract"] n5(["fa:fa-play Request to Create Sales Order Received"]) n6(["fa:fa-stop RAR Contract Created in SAP"]) n7["Revenue Accounting Items - Order Items Created"] n9{{"fa:fa-code-branch exclusiveGateway"}} end n5 --> n3 n3 --> n7 n2 --> n6 n9 --> n2 n1 --> n9 n8 -->|"Yes"| n1 n4 --> n8 n7 --> n4 n8 -->|"No"| n9 class n1 userTask class n2 userTask class n3 userTask class n4 serviceTask class n5 startEvt class n6 endEvt class n7 startEvt class n8 gateway class n9 gateway
👁 View Diagram
Page 7↑ Back to TOCDC-100 — Revenue Recognition

BUSINESS ARCHITECTURE — 3.2.2 DC-100-030_RAR_Closing_and_Reconciliation — DC-100-030_RAR_Closing_and_Reconciliation

Swim Lanes: Revenue Accountant | Tasks: 15 | Gateways: 12

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Revenue Accountant"] n1["fa:fa-user Change Status to 'In Closing' for RAR Period"] n2["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"] n3["fa:fa-user Go to Shift Contract to Next Period"] n4["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"] n5["fa:fa-user Go to Shift Contract to Next Period"] n6["fa:fa-user Go to Monitor for Parallel Processing Run and Make Required Corrections"] n7["fa:fa-user Go to Shift Contract to Next Period"] n8["fa:fa-user Rerun Batch Job A"] n9["fa:fa-user Rerun Batch Job B"] n10["fa:fa-user Rerun Batch Job C"] n11["fa:fa-user Update fulfilment of Manual Fulfilment based Performance Obligation"] n12[["fa:fa-cog Run Batch Job A : Transfer Revenue"]] n13[["fa:fa-cog Run Batch Job B : Calculate Contract Asset and Liability"]] n14[["fa:fa-cog Run Batch Job C: Revenue Posting Run"]] n15[["fa:fa-cog Run Batch Job C for Close Revenue Period"]] n16(["fa:fa-play RAR Closing and Reconciliation Initiated"]) n17(["fa:fa-stop Contract Shifted"]) n18(["fa:fa-stop Contract Shifted"]) n19(["fa:fa-stop Contract Shifted"]) n20(["fa:fa-stop RAR Closing and Reconciliation Completed"]) n21["Revenue Posting Completed in FI-GL"] n22{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}} n23{{"fa:fa-code-branch Error Resolved?"}} n24{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}} n25{{"fa:fa-code-branch exclusiveGateway"}} n26{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}} n27{{"fa:fa-code-branch Error Resolved?"}} n28{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}} n29{{"fa:fa-code-branch exclusiveGateway"}} n30{{"fa:fa-code-branch IF Any Error Occurred that needs to be Resolved ?"}} n31{{"fa:fa-code-branch Error Resolved?"}} n32{{"fa:fa-code-branch Does Revenue Accounting Require Contract Shift to Next Period?"}} n33{{"fa:fa-code-branch exclusiveGateway"}} end n16 --> n11 n1 --> n12 n12 --> n22 n22 -->|"Yes"| n2 n2 --> n23 n23 -->|"No"| n24 n24 -->|"Yes"| n3 n3 --> n17 n25 --> n13 n24 -->|"No"| n25 n23 -->|"Yes"| n8 n26 -->|"Yes"| n4 n4 --> n27 n28 -->|"Yes"| n5 n5 --> n18 n29 --> n14 n27 -->|"Yes"| n9 n13 --> n26 n27 -->|"No"| n28 n30 -->|"Yes"| n6 n6 --> n31 n31 -->|"No"| n32 n32 -->|"Yes"| n7 n7 --> n19 n14 --> n30 n33 --> n15 n21 --> n20 n32 -->|"No"| n33 n28 -->|"No"| n29 n15 --> n21 n31 -->|"Yes"| n10 n8 --> n25 n22 -->|"No"| n25 n26 -->|"No"| n29 n9 --> n29 n30 -->|"No"| n33 n10 --> n33 n11 --> n1 class n1 userTask class n2 userTask class n3 userTask class n4 userTask class n5 userTask class n6 userTask class n7 userTask class n8 userTask class n9 userTask class n10 userTask class n11 userTask class n12 serviceTask class n13 serviceTask class n14 serviceTask class n15 serviceTask class n16 startEvt class n17 endEvt class n18 endEvt class n19 endEvt class n20 endEvt class n21 startEvt class n22 gateway class n23 gateway class n24 gateway class n25 gateway class n26 gateway class n27 gateway class n28 gateway class n29 gateway class n30 gateway class n31 gateway class n32 gateway class n33 gateway
👁 View Diagram
Page 8↑ Back to TOCDC-100 — Revenue Recognition

BUSINESS ARCHITECTURE — 3.2.3 DC-100-040_RAR_Reports — DC-100-040_RAR_Reports

Swim Lanes: Revenue Accountant | Tasks: 8 | Gateways: 1

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Revenue Accountant"] n1["fa:fa-user Execute Contract Balance Reports"] n2["fa:fa-user Execute Disaggregation of Recognizable Revenue Reports"] n3["fa:fa-user Execute Disaggregation of Revenue Report"] n4["fa:fa-user Execute Remaining Performance Obligation - with Time Bands Report"] n5["fa:fa-user Execute Remaining Performance Obligation Report"] n6["fa:fa-user Execute Revenue Catch-up Report"] n7["fa:fa-user Execute Contract Balance Reclassification Report"] n8["fa:fa-user Execute Contract Balance Movements Report"] n9(["fa:fa-play RAR Reporting Started"]) n10(["fa:fa-stop Contract Balance Report Validated"]) n11(["fa:fa-stop Disaggregation of Recognizable Revenue Report Validated"]) n12(["fa:fa-stop Disaggregation of Revenue Report Validated"]) n13(["fa:fa-stop Remaining Performance Obligation - with Time Bands Report Validated"]) n14(["fa:fa-stop Remaining Performance Obligation Report Validated"]) n15(["fa:fa-stop Revenue Catch-up Report Validated"]) n16(["fa:fa-stop Contract Balance Reclassification Report Validated"]) n17(["fa:fa-stop Contract Balance Movements Report Validated"]) n18{{"fa:fa-arrows-alt inclusiveGateway"}} end n1 --> n10 n2 --> n11 n9 --> n18 n3 --> n12 n18 --> n3 n18 --> n2 n18 --> n1 n4 --> n13 n5 --> n14 n18 --> n5 n6 --> n15 n18 --> n6 n7 --> n16 n8 --> n17 n18 --> n7 n18 --> n8 n18 --> n4 class n1 userTask class n2 userTask class n3 userTask class n4 userTask class n5 userTask class n6 userTask class n7 userTask class n8 userTask class n9 startEvt class n10 endEvt class n11 endEvt class n12 endEvt class n13 endEvt class n14 endEvt class n15 endEvt class n16 endEvt class n17 endEvt class n18 gateway
👁 View Diagram
Page 9↑ Back to TOCDC-100 — Revenue Recognition

BUSINESS ARCHITECTURE — 3.2.4 DC-100-050_Define_Transaction_Price — DC-100-050_Define_Transaction_Price

Swim Lanes: Revenue Accountant | Tasks: 0 | Gateways: 0

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Revenue Accountant"] n1(["fa:fa-play Sales Order Created"]) n2(["fa:fa-stop Transaction Price Defined"]) n3[["fa:fa-folder-open Determine Performance Obligations​"]] end n1 --> n3 n3 --> n2 class n1 startEvt class n2 endEvt class n3 subProc
👁 View Diagram
Page 10↑ Back to TOCDC-100 — Revenue Recognition

BUSINESS ARCHITECTURE — 3.2.5 DC-100-060_Determine_Performance_Obligations — DC-100-060_Determine_Performance_Obligations

Swim Lanes: RAR IT Support Analyst · Revenue Accountant | Tasks: 4 | Gateways: 2

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["RAR IT Support Analyst"] n1["fa:fa-user Resolve the Error for POB and Reprocess"] n4[["fa:fa-cog Perform Real Time Processing of Revenue Accounting Items for POB"]] n8{{"fa:fa-code-branch If RAI is in Postponed Status then it needs to be Reprocessed?"}} end subgraph lane_1["Revenue Accountant"] n2["fa:fa-user View and Manage Performance Obligation"] n3["fa:fa-user Display Sales Order for POB"] n5(["fa:fa-play Request to Create Sales Order Received"]) n6(["fa:fa-stop Performance Obligations​ Created"]) n7["Revenue Accounting Items - Order Items Created"] n9{{"fa:fa-code-branch exclusiveGateway"}} end n5 --> n3 n3 --> n7 n7 --> n4 n2 --> n6 n4 --> n8 n9 --> n2 n8 -->|"No"| n9 n8 -->|"Yes"| n1 n1 --> n9 class n1 userTask class n2 userTask class n3 userTask class n4 serviceTask class n5 startEvt class n6 endEvt class n7 startEvt class n8 gateway class n9 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.6 DC-100-070_Allocate_Transaction_Price — DC-100-070_Allocate_Transaction_Price

Swim Lanes: Revenue Accountant | Tasks: 0 | Gateways: 0

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Revenue Accountant"] n1(["fa:fa-play Transaction Price Allocation Started"]) n2(["fa:fa-stop Transaction Price Allocation Completed"]) n3[["fa:fa-folder-open Determine Performance Obligations​"]] end n3 --> n2 n1 --> n3 class n1 startEvt class n2 endEvt class n3 subProc
👁 View Diagram
Page 11↑ Back to TOCDC-100 — Revenue Recognition

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
RAR IT Support Analyst DC-100-010_Create_Revenue_Accounting_Contracts, DC-100-060_Determine_Performance_Obligations,
Revenue Accountant DC-100-010_Create_Revenue_Accounting_Contracts, DC-100-030_RAR_Closing_and_Reconciliation, DC-100-040_RAR_Reports, DC-100-050_Define_Transaction_Price, DC-100-060_Determine_Performance_Obligations, DC-100-070_Allocate_Transaction_Price
Page 12↑ Back to TOCDC-100 — Revenue Recognition

3.4 Process Readiness

Process readiness for DC-100 — Revenue Recognition with automated risk flags from Config Tracker, User Story Tracker, RICEFW Object Tracker, ECA Object Tracker.

L2 Description L3 In-Scope Config User Stories RICEFW ECA Status
DC-100 Revenue Recognition 5/6 86% (6/7) 28F/10G/39 14/14 — 🟢

📄 Full Process Readiness Detail → — per-capability breakdown with config items, RICEFW objects, transport analysis, and QA verification. For the comprehensive L1/L0 readiness rollup across all capabilities, see the L0 Tower Summary.

Data Sources: Config Tracker, User Story Tracker, S4 R3 Object Tracker, ECA R3 Object Tracker (Smartsheet exports). RICEFW and ECA objects are matched via Sub-Tower Name → L2 mapping. Generated .

Page 13↑ Back to TOCDC-100 — Revenue Recognition

4. Data Architecture (TOGAF “D”)

4.1 Data Flows — Source to Target

Data flows with DB platform details will be populated when tower architects complete the extended flow template columns (42-47) via the Input Portal.

4.2 Data Flow Diagrams

DATA ARCHITECTURE — Database-to-database data flows. Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.

4.3 Data Lineage

Data lineage (source schema/object → target schema/object mappings) will be populated when tower architects provide validated schema details via the Input Portal.

4.4 RICEFW Data Objects

Data-centric RICEFW objects (Reports and Conversions) from the Object Tracker:

Object ID Type Description Status Source → Target Complexity
FPRR1240 Report Custom report for Revenue Recognition by Stage for Product/Services Sale​ act… 10. Object Complete 03.Medium

4.5 Data Governance & Quality

Standard governance framework per Intel IDM 2.0 data management policies. Capability-specific governance details will be populated from the Input Portal when tower architects complete the Data Governance tab.

Concern Approach
Data Ownership Per-entity owners aligned to Finance Plan To Report tower organizational structure
Data Classification Per Intel corporate data classification policies
Data Retention Per Intel corporate retention policies
Data Quality Validated at source; reconciliation at target
Page 14↑ Back to TOCDC-100 — Revenue Recognition

5. Application Architecture (TOGAF “A”)

5.4 Component Overview

System Inventory

System IAPM ID Status

5.5 Development Object Inventory

Summary: 13 SAP, 1 ECA, 1 Interfaces | RICEFW: 1 Reports, 1 Interfaces, 12 Enhancements

5.5.1 SAP Development Objects

SAP platform objects (Reports, Interfaces, Conversions, Enhancements, Forms, Workflows) developed on S/4, MDG, or S/4 BOT:

Object ID Type Description Status Dev System Complexity
FPRR1240 Report Custom report for Revenue Recognition by Stage for Product/Services Sale​ act… 10. Object Complete 01.S4 03.Medium
FPRE1660 Enhancement Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 10. Object Complete 01.S4 02.High
FPRE1659 Enhancement Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 10. Object Complete 01.S4 02.High
FPRE1239 Enhancement Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 10. Object Complete 01.S4 02.High
FPRE0760_IP Enhancement SAP RAR and TM Integration to trigger POD Event 10. Object Complete 01.S4 03.Medium
FPRE0760_IF Enhancement SAP RAR and TM Integration to trigger POD Event 10. Object Complete 01.S4 04.Low
FPRE0697 Enhancement RAR Balance sheet posting with MM & Sold To ID 10. Object Complete 01.S4 03.Medium
FPRE0500_IP Enhancement Rule for Transaction Price Allocation in BRIM vs SD 10. Object Complete 01.S4 03.Medium
FPRE0500_IF Enhancement Rule for Transaction Price Allocation in BRIM vs SD 10. Object Complete 01.S4 03.Medium
FPRE0477 Enhancement Rebate for Direct Customer to Rebate of Intransit deferrals for Direct & Dist… 10. Object Complete 01.S4 03.Medium
FPRE0476 Enhancement Accounting for Stock Rotation 10. Object Complete 01.S4 03.Medium
FPRE0475 Enhancement Accounting for reserves for unissued returns credit note & Rebate Return Accr… 10. Object Complete 01.S4 03.Medium
FPRE0474 Enhancement Accounting for technical return reserve 10. Object Complete 01.S4 03.Medium

5.5.2 ECA Development Objects

Enterprise Cloud Analytics (ECA) platform objects (Databricks/Snowflake) — views, tables, and ETL jobs with Source or Target System = ECA:

Object ID Type Description Status Source → Target Complexity
FPRI1241 Interface Disti Rebate percentage of gross for Unissued Returns and Intransit Deferral 10. Object Complete ECA → S/4 03.Medium

5.5.3 Interface Objects

Holistic view of all interface objects by L2 capability — includes ECA → S/4, S/4 → ECA, boundary system, and inter-platform interfaces with middleware and integration approach:

Object ID Description Source → Target Middleware Approach Status
FPRI1241 Disti Rebate percentage of gross for Unissued Returns and Intransit Deferral ECA → S/4 BODS 10. Object Complete

5.5.5 Scheduling & Batch Objects

This section provides a holistic view of all batch processing and job scheduling — both internal SAP background jobs (SM37) and external orchestration (AutoSys, CWA).

5.5.5b External Scheduling Objects

External scheduling data is not yet available. Pending either AutoSys API access or a JIL export to the External Job Scheduling Tracker.

Scheduling and batch job data will be auto-populated once SAP background job extraction (TBTCO/TBTCP via ADT) is run against the development systems and AutoSys metadata is available. Run python scripts/fetch_sap_background_jobs.py to extract SAP internal jobs.

Page 15↑ Back to TOCDC-100 — Revenue Recognition

5.6 Integration Patterns

Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.

6. Technology Architecture (TOGAF “T”)

6.1 Platform & Infrastructure

TECHNOLOGY / PLATFORM ARCHITECTURE — Platforms (green) host applications (blue). Thick arrows show platform-to-platform integration flows.

Platform Inventory

Platform inventory will be populated when tower architects provide validated technology platform details via the extended flow template.

6.2 SAP Development Object Status

Metric DEV QAS PRD
Transport Requests — — —
Custom Code Objects — — —
CDS Views — — —
Fiori Apps — — —
BAdIs / Enhancements — — —

6.3 NFRs & Design Principles

Category Requirement Target / SLA Priority
Performance Month-end batch costing/closing completes within SLA window < 4 hours end-to-end batch window High
Availability S/4 HANA finance modules available during business hours 99.9% (Mon-Fri 06:00-22:00 PST) High
Scalability Support 2x transaction volume growth over 3-year horizon Handle 500K+ journal entries/day Medium
Recoverability RPO/RTO for financial systems meets audit requirements RPO < 1 hour, RTO < 4 hours High
Data Volume Support growing data volumes from legacy migration + BAU 50M+ records in material ledger Medium
Latency Near-real-time posting for financial transactions < 5 seconds for online postings Medium
Concurrency Support concurrent month-end users across time zones 200+ concurrent finance users Medium

6.4 Security & Governance

Concern Approach Standard / Policy Owner
Authentication Single Sign-On (SSO) via Intel corporate Azure AD identity Intel IT Security Policy - Identity Management IT Security
Authorization Role-based access control (RBAC) with SAP authorization objects Intel SAP Security Standards - Role Design SAP Security Team
Data Classification All financial/operational data classified per Intel Data Classification Standard Intel Data Classification Policy Data Governance
Data Encryption (at rest) AES-256 encryption for SAP HANA database and file storage Intel Encryption Standard Infrastructure Security
Data Encryption (in transit) TLS 1.3 for all system-to-system and user-to-system communication Intel Network Security Policy Network Engineering
Network Segmentation SAP systems in dedicated network zones with firewall controls Intel Network Architecture Standard Network Security
API Security OAuth 2.0 / certificate-based authentication for all API integrations Intel API Security Guidelines Integration Architecture
Audit Logging Comprehensive audit trail for all data changes and user actions (SAP Security Audit Log) SOX Compliance / Intel Audit Policy Internal Audit
Certificate Management Automated certificate lifecycle management for system-to-system trust Intel PKI Standard Certificate Authority Team
Compliance SOX controls, export control (EAR/ITAR) screening, data privacy (GDPR) Intel Corporate Compliance Framework Compliance Office

6.5 ECA Development Object Status

Metric Count
ECA Objects (this capability) 1
ECA Interfaces 1
Total ECA + SAP Interface Dependencies 1
Page 16↑ Back to TOCDC-100 — Revenue Recognition

7. Project Context

7.1 Project Roadmap & Go-Live Plan

ID Description FS TDD Build FUT Status
FPRR1240 Custom report for Revenue Recognition by Stage for Product/Services Sale​ act… 2025-03-21 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2026-03-04 00:00:00 (100%) 4. Completed
FPRI1241 Disti Rebate percentage of gross for Unissued Returns and Intransit Deferral 2025-03-21 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-07-16 00:00:00 (100%)
FPRE1660 Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 2025-12-03 00:00:00 (100%) 2026-01-07 00:00:00 (100%) 2026-01-07 00:00:00 (100%) 2026-03-04 00:00:00 (100%) 1. On Track
FPRE1659 Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 2025-12-03 00:00:00 (100%) 2026-01-07 00:00:00 (100%) 2026-01-07 00:00:00 (100%) 2026-02-04 00:00:00 (100%) 1. On Track
FPRE1239 Enhancement for Revenue Recognition by Stage postings for Product/Services Sa… 2025-03-21 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2026-02-04 00:00:00 (100%) 4. Completed
FPRE0760_IP SAP RAR and TM Integration to trigger POD Event 2025-01-24 00:00:00 (100%) 2025-04-24 00:00:00 (100%) 2025-04-24 00:00:00 (100%) 2025-06-11 00:00:00 (100%)
FPRE0760_IF SAP RAR and TM Integration to trigger POD Event 2025-01-24 00:00:00 (100%) 2025-04-24 00:00:00 (100%) 2025-04-24 00:00:00 (100%) 2025-06-11 00:00:00 (100%)
FPRE0697 RAR Balance sheet posting with MM & Sold To ID 2024-11-15 00:00:00 (100%) 2025-03-28 00:00:00 (100%) 2025-03-28 00:00:00 (100%) 2025-05-16 00:00:00 (100%)
FPRE0500_IP Rule for Transaction Price Allocation in BRIM vs SD 2024-09-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2025-03-21 00:00:00 (100%) 1. On Track
FPRE0500_IF Rule for Transaction Price Allocation in BRIM vs SD 2024-09-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2025-03-21 00:00:00 (100%) 1. On Track
FPRE0477 Rebate for Direct Customer to Rebate of Intransit deferrals for Direct & Dist… 2024-09-20 00:00:00 (100%) 2025-06-20 00:00:00 (100%) 2025-06-20 00:00:00 (100%) 2025-07-16 00:00:00 (100%)
FPRE0476 Accounting for Stock Rotation 2024-08-23 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2025-02-21 00:00:00 (100%)
FPRE0475 Accounting for reserves for unissued returns credit note & Rebate Return Accr… 2024-09-20 00:00:00 (100%) 2025-01-17 00:00:00 (100%) 2025-01-17 00:00:00 (100%) 2025-03-21 00:00:00 (100%)
FPRE0474 Accounting for technical return reserve 2024-08-23 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2024-12-20 00:00:00 (100%) 2025-02-21 00:00:00 (100%)
Page 17↑ Back to TOCDC-100 — Revenue Recognition

7.2 RAID Log

RAID items will be auto-populated from the Smartsheet RAID log when matched to this capability.

7.3 Recommendations & Next Steps

# Category Recommendation Priority Owner Target Date Status
1 Architecture Complete extended flow attributes (Data Entity, Integration Pattern, Tech Platform) in Flows tab for full BDAT coverage High Tower Architect 2026-Q2 Open
2 Data Define data ownership and classification for all 0 flow chains to satisfy Data Architecture (TOGAF D) requirements Medium Data Architect 2026-Q3 Open
3 Testing Develop integration test scenarios covering all 0 flow chains for FUT/SIT readiness High Test Lead 2026-Q3 Open
4 Business Architecture Review and validate Business Architecture process steps against latest Signavio/BIC process models Medium Business Analyst 2026-Q2 Open
5 Security Complete security review for API integrations and data flows per Intel Security Architecture standards Medium Security Architect 2026-Q3 Open

DC-100 — Architecture Document (TOGAF BDAT) · Finance Plan To Report · Generated: May 2026

Page 18↑ Back to TOCDC-100 — Revenue Recognition
IAO Architecture Document | Intel IDM 2.0 | Generated by IAO Architecture Pipeline
↑ Back to TOC DC-100 — Revenue Recognition IAO Architecture Pipeline — Intel Confidential