ZR_3022_JOB

Key Responsibilities: Solution design & configuration— Define chart of depreciation, depreciation areas, assetclasses, 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 multipleaccounting principles (local GAAP, IFRS, US GAAP) across parallel ledgers, understanding that each ledger has a fixed, non-changeable depreciationarea assignment (e.g., ledger 0L = area 01, 2L = area 32, 3L = area34)[1].Depreciation key configuration— Analyze and, where standard configuration doesn't cover therequirement, manage the SAP Expert Configuration Service process for new depreciationkeys, including preparing the required depreciation key template andcoordinating quality-system testing before go-live[1].Master data & migration— Lead legacy asset data migration using the SAP S/4HANAMigration Cockpit, including staging table setup for fixed asset masterdata, postings, and usage objects, and troubleshoot common migrationerrors (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-endclosing/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, includingenabling forecasted/future depreciation values[1].Segment/profit center reporting— Ensure fixed assets derive profit center and segmentcorrectly (from cost center/internal order assignment) for consistentsegment-level reporting, including running the "Fill Master Data for Segment Reporting" job for legacy assets[5][2].Integration— Managecross-module dependencies with Controlling (cost center/internal orderassignment), Materials Management (asset acquisition via PO), and Investment Management (Assets under Construction / WBS-basedcapitalization)[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 masschanges[1].Troubleshooting & incident resolution— Act as the escalation point for account determinationerrors, closing errors, and other configuration-lock issues (e.g., inability to change a G/L account once postings exist)[1].Governance— Ensurechanges to productive configuration go through proper sandbox/developmenttesting and transport before deployment; never modify productive settingsdirectly. Required Skills &Experience5+ yearshands-on SAP FI-AA configuration and support experience, ideally across atleast one full S/4HANA implementation or conversion. Strongunderstanding of parallel ledgers/parallel valuation concepts, chart ofdepreciation, and depreciation area design. Experience withSAP S/4HANA Migration Cockpit for legacy asset data. Familiaritywith relevant Fiori apps: Manage Fixed Assets, Manage Legacy Assets, PostAsset Acquisition/Retirement/Revaluation, Schedule Asset Accounting Jobs[1].Workingknowledge of CDS (Core Data Services) views relevant to Asset Accountingfor custom reporting (e.g., I_FixedAsset, I_DepreciationAreaForLedger, I_AssetClass )[1].Understandingof relevant OData/SOAP APIs and communication scenario SAP_COM_0563 for FixedAsset integrations[1].Cross-modulefluency in FI (G/L, AP) and CO (cost centers, internal orders) as theyrelate to asset postings. Exposure tocountry-specific / localization requirements is a plus (e.g., statutoryasset reporting forms)[6].

Nice to Have: Experience withSAP Activate methodology and Best Practice scope items (e.g., J62 – AssetAccounting, BFH – Assets Under Construction)[1].Exposure to SAPS/4HANA Cloud Public Edition self-service configuration (SSCUI) activitiesfor Asset Accounting. Anatural next thing to learn once this clicks: look into howdocument splittingandparallel ledgersinteract with Asset Accounting, since that's usually where FI/CO SMEs get pulled into the trickiest designconversations. Also worth exploring the difference betweenclassic Asset Accounting and new Asset Accounting (FI-AA new)ifyou'll be touching any older or converted systems, since terminology and someconfig paths differ.

Risks &Monitoring: Depreciation area/ledger misassignment during design— since the ledger-to-depreciation-area mapping is fixed andcannot be changed once assets exist (e.g., 0L01, 2L32, 3L34), verifythe mapping in SSCUIAssign Accounting Principle to Ledger and Company Codes(103556) before any asset master data or postingsoccur[1].Account determination lock-in— once postings exist against a G/L account tied to an assetaccount determination, it cannot be changed (error FAA_CFG_CHECK307 ); check forexisting postings via the asset's account determination assignment beforeattempting changes, and create a new account determination instead ifneeded[1].Legacy data transfer date conflicts— migration failures ( FAA_CMP061, FAA_CMP080 ) typically stem from the Asset Accounting legacy transfer date notaligning with the G/L migration date or fiscal year status; validate datesin Make Company Code Settings – Asset Accounting-Specificandconfirm Balance Carry Forward has run before closing fiscal years[1].