Sr. SAP S /4 \- SAP FICO with Fixed Assest SME functional Consultant \- 100% Remote

Role Summary Serve as the primary authority for Fixed Asset Accounting (FI-AA) design, configuration, and support within an SAP S/4HANA landscape (Public Cloud, Private Cloud, or On-Premise). Own end-to-end asset accounting processes — from chart of depreciation setup through year-end closing — while ensuring integration with General Ledger, Controlling, and Materials Management stays clean. Experience working on Finance projects which is also working with Project Systems.

Key Responsibilities

• Solution design & configuration — Define chart of depreciation, depreciation areas, asset classes, account determination, and valuation views (e.g., Book, Tax, IFRS, US GAAP) aligned to the client's ledger strategy (leading ledger 0L, non-leading ledgers such as 2L/3L) ^[1].
  


• Parallel accounting / parallel valuation — Design depreciation area structures to support multiple accounting principles (local GAAP, IFRS, US GAAP) across parallel ledgers, understanding that each ledger has a fixed, non-changeable depreciation area assignment (e.g., ledger 0L = area 01, 2L = area 32, 3L = area 34) ^[1].
  


• Depreciation key configuration — Analyze and, where standard configuration doesn't cover the requirement, manage the SAP Expert Configuration Service process for new depreciation keys, including preparing the required depreciation key template and coordinating quality-system testing before go-live ^[1].
  


• Master data & migration — Lead legacy asset data migration using the SAP S/4HANA Migration Cockpit, including staging table setup for fixed asset master data, postings, and usage objects, and troubleshoot common migration errors (e.g., legacy transfer date conflicts) ^[1].
  


• Period-end / year-end closing — Own the fixed asset side of period and year-end close, including running depreciation jobs, fiscal year change, and year-end closing/reset by depreciation area, typically via apps like Schedule Fixed Asset Accounting Jobs ^[2] and Make Company Code Settings – Asset Accounting-Specific ^[1].
  


• Reporting — Configure and support standard reporting: Asset Balances, Asset Transactions, Depreciation Lists, and Asset History Sheet, including enabling forecasted/future depreciation values ^[1].
  


• Segment/profit center reporting — Ensure fixed assets derive profit center and segment correctly (from cost center/internal order assignment) for consistent segment-level reporting, including running the "Fill Master Data for Segment Reporting" job for legacy assets ^[5][2].
  


• Integration — Manage cross-module dependencies with Controlling (cost center/internal order assignment), Materials Management (asset acquisition via PO), and Investment Management (Assets under Construction / WBS-based capitalization) ^[1].
  


• APIs & mass processing — Guide teams on OData APIs (e.g., API_FIXEDASSET_G4BA, API_FIXEDASSETACQUISITION_G4BA) for mass asset processing in Cloud environments, since the Migration Cockpit is migration-only and not meant for regular mass changes ^[1].
  


• Troubleshooting & incident resolution — Act as the escalation point for account determination errors, closing errors, and other configuration-lock issues (e.g., inability to change a G/L account once postings exist) ^[1].
  


• Governance — Ensure changes to productive configuration go through proper sandbox/development testing and transport before deployment; never modify productive settings directly.
  

Required Skills & Experience

• 5+ years hands-on SAP FI-AA configuration and support experience, ideally across at least one full S/4HANA implementation or conversion.
  


• Strong understanding of parallel ledgers/parallel valuation concepts, chart of depreciation, and depreciation area design.
  


• Experience with SAP S/4HANA Migration Cockpit for legacy asset data.
  


• Familiarity with relevant Fiori apps: Manage Fixed Assets, Manage Legacy Assets, Post Asset Acquisition/Retirement/Revaluation, Schedule Asset Accounting Jobs ^[1].
  


• Working knowledge of CDS (Core Data Services) views relevant to Asset Accounting for custom reporting (e.g., I_FixedAsset, I_DepreciationAreaForLedger, I_AssetClass) ^[1].
  


• Understanding of relevant OData/SOAP APIs and communication scenario SAP_COM_0563 for Fixed Asset integrations ^[1].
  


• Cross-module fluency in FI (G/L, AP) and CO (cost centers, internal orders) as they relate to asset postings.
  


• Exposure to country-specific / localization requirements is a plus (e.g., statutory asset reporting forms) ^[6].
  

Nice to Have

• Experience with SAP Activate methodology and Best Practice scope items (e.g., J62 – Asset Accounting, BFH – Assets Under Construction) ^[1].
  


• Exposure to SAP S/4HANA Cloud Public Edition self-service configuration (SSCUI) activities for Asset Accounting.
  

A natural next thing to learn once this clicks: look into how document splitting and parallel ledgers interact with Asset Accounting, since that's usually where FI/CO SMEs get pulled into the trickiest design conversations. Also worth exploring the difference between classic Asset Accounting and new Asset Accounting (FI-AA new) if you'll be touching any older or converted systems, since terminology and some config paths differ.

Risks & Monitoring

1. Depreciation area/ledger misassignment during design — since the ledger-to-depreciation-area mapping is fixed and cannot be changed once assets exist (e.g., 0L↔01, 2L↔32, 3L↔34), verify the mapping in SSCUI Assign Accounting Principle to Ledger and Company Codes (103556) before any asset master data or postings occur ^[1].
   


2. Account determination lock-in — once postings exist against a G/L account tied to an asset account determination, it cannot be changed (error FAA_CFG_CHECK307); check for existing postings via the asset's account determination assignment before attempting changes, and create a new account determination instead if needed ^[1].
   


3. Legacy data transfer date conflicts — migration failures (FAA_CMP061, FAA_CMP080) typically stem from the Asset Accounting legacy transfer date not aligning with the G/L migration date or fiscal year status; validate dates in Make Company Code Settings – Asset Accounting-Specific and confirm Balance Carry Forward has run before closing fiscal years ^[1].