FI / FICOarchitect

FICO FI Integration Part 4: Integration Strategy Across Modules and Deployment Models

Key takeaway

Architect financial integration: account determination governance across modules, harmonized master data groupings, integration with non-SAP systems (interfaces, journal entry APIs), hybrid landscapes (public/private cloud, Central Finance), monitoring and reconciliation strategy.

Explanation

📌 KEY POINTS
✅ Govern account determination centrally with a matrix and change process across MM, SD, AA, HR and bank.
✅ Harmonize the master data groupings that drive it (valuation classes, account assignment groups, asset classes).
✅ Non-SAP systems should post via released APIs with validation and monitoring.
✅ Hybrid landscapes (several ERPs, cloud) may use Central Finance or group reporting for a unified view.
⚠️ Point-to-point interfaces posting journals without monitoring create silent gaps in the books.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered MM-FI. Now strategy.

━━━━━━━━━━━━━━━━━━━━
▶ 1. GOVERNANCE

Matrix, owners, change control, tests.

━━━━━━━━━━━━━━━━━━━━
▶ 2. HARMONIZATION

Global groupings; local exceptions documented.

━━━━━━━━━━━━━━━━━━━━
▶ 3. NON-SAP INTEGRATION

Journal entry APIs; error handling.

━━━━━━━━━━━━━━━━━━━━
▶ 4. LANDSCAPE

Central Finance, group reporting, cloud.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MONITORING

Interface monitors; reconciliation to source.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Inventory integration points.
Define governance and matrix.
Set monitoring per interface.

✅ CHECKPOINT: every posting source has an owner and reconciliation.

Code example

ABAP Code

===== INTEGRATION INVENTORY =====MM (OBYC) | SD (VKOA) | AA (AO90) | HR (symbolic accounts) | Bank (EBS) | Non-SAP (journal entry API) | Other ERPs (Central Finance) ===== CONTROLS =====Change request → finance approval → transport → regression test (P2P, O2C, depreciation, payroll)Interface monitoring: failed messages, source-target reconciliation

Real project scenario

A multinational group integrated a non-SAP billing system by posting summarized journals via file upload. Failed files were unnoticed for weeks. Moving to an API with error monitoring and daily reconciliation closed the gap.

Common mistakes

Unmonitored interfaces.
Local groupings.
No change control.
Manual uploads.
No reconciliation.

Best practices

Govern centrally.
Harmonize groupings.
Use APIs with monitoring.
Reconcile sources.
Regression tests.

Interview angle

Questions: "How do you govern account determination globally?", "How should non-SAP systems post to FI?", "When use Central Finance?"
Strong answer: governance, harmonization, APIs, landscape options, monitoring.

Practice this lesson

Quick check

1. Local plants want to create their own valuation classes freely. What is the safest architectural approach?

2. According to architectural best practices, what is a key constraint an architect must consider when designing an FI integration solution specifically for an SAP S/4HANA Public Cloud environment?

3. A non-SAP billing system posts journals via manual file uploads, and failures go unnoticed. What is the better design?

Interview questions

1. A multinational with several ERPs and non-SAP systems wants reliable financial integration. What strategy do you propose?

Answer it in your own words first, then compare.

2. What are the most important design decisions, trade-offs, and best practices in FI Integration?