Pre-built netcracker data mapping rules: Subscribers → Fusion Customer Hub, Bills → Fusion AR Transactions, Payments → Fusion AR Receipts / AP Invoices, Network Inventory → Fusion Assets. TM Forum SID-aware, multi-currency, multi-instance, signed off by finance and revenue assurance.
Tier-1 telco data is shaped by 30 years of telecom-specific data modelling — TM Forum SID, eTOM, the ITU recommendations, GSMA TADIG/TAP3. Oracle Fusion's AR/GL/Customer Hub doesn't speak that language natively, and the mapping is where conformance happens.
A subscriber in Netcracker isn't a Fusion party — it's a TM Forum Individual or Organization with a complex hierarchy of accounts, products, services, resources and orders, all linked to consent flags, marketing preferences, regulatory tags (legal-intercept marker, slum-area subsidy flag in some jurisdictions) and partner-of-record assignments. A bill in Netcracker isn't a Fusion AR Transaction — it's a bill-cycle artefact composed of recurring charges, usage-rated CDRs, one-time fees, taxes, regulatory surcharges, partner pass-throughs and promotional adjustments, each with its own rating-engine provenance.
Translating those structures into Fusion AR/GL/Customer Hub correctly — not just structurally but semantically, with reconciliation chains intact and regulator-required attributes preserved — is the heart of the netcracker data mapping workstream.
Syntra ETL ships netcracker data mapping rules refined across multiple tier-1 and tier-2 carrier conversions. The rules cover subscribers, accounts, products, bills, payments, partner settlement, taxes, regulatory surcharges, network inventory (where capitalised to Fusion Assets), multi-currency conversion and multi-instance consolidation. Each rule is reviewed by finance, revenue assurance, BSS engineering and compliance, and signed off before build.
These six are the recurring sticking points across tier-1 conversions — and the ones Syntra ETL ships pre-built recommendations for.
TM Forum SID product hierarchies are deep and recursive. Collapsing to Fusion COA segments without losing analytical detail is the recurring tension. Syntra ETL routes material dimensions to COA, non-material to DFFs.
Same enterprise customer in three acquired Netcracker tenants. Dedup rule based on fuzzy match (tax-id + legal name + primary contact) with manual-override workflow for ambiguous matches.
Original transaction currency and original amount preserved as AR DFFs. Fusion functional-currency conversion at posting time per the agreed Ledger rate-type policy.
E911, USF and state-level taxes for US carriers; VAT regimes elsewhere; jurisdiction-specific levies. Routed to dedicated AR Memo Lines and GL clearing accounts agreed with compliance.
Wholesale, roaming, MVNO and content partner pass-throughs separated from subscriber revenue and routed to AP Invoices via partner master created from Netcracker Revenue Management.
Where Active Inventory feeds Fusion Assets, capitalisation lifecycle comes from the existing FAM (not Netcracker). Netcracker provides the asset_inventory_id linkage for OSS-to-finance traceability.
Mapping is a workstream, not a single document. Below is the repeatable sequence Syntra ETL runs across every tier-1 netcracker data mapping engagement.
Per-instance inventory of Netcracker Customer, Account, Product Specification, Product Offering, Bill Cycle, Invoice, Payment, Partner Settlement, Network Inventory and Service Activation. TM Forum SID conformance noted per entity.
Per-target inventory of Fusion Customer Hub, AR Transactions, AR Receipts, AP Invoices, GL Journals, COA segments and (where applicable) Assets. Decision signed off by finance lead before mapping draft.
Field-level mapping per source-target pair with default and conditional logic, dependent reference data, validation rules and reconciliation grain. Drafted by Syntra ETL using pre-built mapping rules and reviewed line-by-line with the customer team.
Finance, revenue assurance, BSS engineering and compliance lead sign-off per mapping. Open items resolved via working session before sign-off is final.
Mapping rules implemented in Syntra ETL pipelines, validated against representative source extracts, reconciled at count + sum + hash level. Any deviation surfaced and re-signed-off before load.
A structured workbook delivered at the end of the mapping cycle. Single source of truth through to hypercare close-out.
Per-instance inventory of every Netcracker source entity with TM Forum SID conformance, REST Open API endpoint, NCT export path and Oracle DB schema reference.
Per-module inventory of every Fusion target entity with the load mechanism (FBDI, REST, FSM), the owning BU/ledger and the post-load reconciliation expectation.
Source → target field mapping with default and conditional logic, default value, dependent reference data, validation rule and reconciliation grain.
Per-mapping sign-off authority (finance, revenue assurance, BSS engineering, compliance) with sign-off date, open items log and resolution audit trail.
Per-mapping reconciliation pack template — count, sum and hash reconciliation, variance threshold, exception handling and escalation rule.
Any change to a signed-off mapping triggers re-sign-off by the original authorities. Hypercare changes governed through the same process.
Netcracker data mapping is the field-level crosswalk that translates Netcracker's TM Forum-aligned BSS data model into Oracle Fusion's AR, GL, Customer Hub, AP and Asset data model. The mapping covers: Netcracker Subscribers → Fusion Customer Hub parties; Netcracker Accounts → Fusion Customer Hub accounts; Netcracker Bills → Fusion AR Transactions; Netcracker Payments → Fusion AR Receipts (or Fusion AP/GL for partner settlement); Netcracker Network Inventory → Fusion Assets where the carrier owns capitalised network estate. Each crosswalk is governed by reviewed mapping rules, sign-off from finance and revenue assurance, and a reconciliation pack proving the loaded Fusion data ties back to source. Syntra ETL ships pre-built netcracker data mapping rules refined across multiple tier-1 conversions.
Netcracker Customer Experience Management holds the subscriber master with TM Forum Party, Individual, Organization, Account, Contact and Address entities. The netcracker data mapping into Oracle Fusion Customer Hub does the following: each Netcracker Account becomes a Fusion Customer Account; each Netcracker Party becomes a Fusion Party (Person or Organization); contacts and addresses load to Fusion Party Sites and Contact Points; consent flags and subscriber preference centre data preserve via Fusion DFFs or extension attributes; multi-instance dedup uses fuzzy match on tax-id + legal name + primary contact, with a manual-override workflow for ambiguous matches. Subscriber tier (postpaid, prepaid, IoT/M2M, wholesale, MVNO host) becomes a Customer classification driving downstream AR transaction-type rules.
Netcracker Charging & Billing produces bill cycles, invoice headers and invoice lines (rated revenue per product, recurring charges, one-time fees, taxes, regulatory surcharges, partner pass-throughs). The netcracker data mapping into Oracle Fusion AR Transactions does the following: each Netcracker invoice header becomes a Fusion AR Transaction (Invoice, Credit Memo or Debit Memo as appropriate); each invoice line becomes a Fusion AR Transaction Line; tax lines map to Fusion Tax with jurisdiction-aware tax codes; regulatory surcharges (E911, USF, state-level taxes for US carriers; VAT regimes elsewhere) route to dedicated AR Memo Lines; partner pass-throughs route to clearing accounts that reconcile against Netcracker Revenue Management partner-settlement records. The mapping carries Netcracker bill_cycle_id, invoice_id and invoice_line_id as Fusion DFFs for end-to-end traceability.
Netcracker tracks subscriber payments (Fusion AR Receipts target), partner-settlement disbursements (Fusion AP Invoices and Payments target) and inter-partner clearing (Fusion GL Journal target). The netcracker data mapping into Oracle Fusion does the following: subscriber receipts (credit card, ACH, wallet, retail cash-collection point) become Fusion AR Receipts with the original payment_method preserved as a DFF; partner-settlement obligations to roaming partners (GSMA TADIG/TAP3), MVNO hosts, interconnect partners and content partners become Fusion AP Invoices with the partner master created from Netcracker Revenue Management; inter-partner clearing entries become Fusion GL Journals with partner-clearing accounts in the COA. Original Netcracker payment_id and settlement_id preserve through every hop, supporting revenue assurance and dispute resolution.
Not every carrier capitalises network estate to Fusion Assets — some run a separate FAM (Fixed Asset Management) system, some keep network estate operational in OSS only. Where Fusion Assets is the target, the netcracker data mapping handles it as follows: Netcracker Active Inventory sites, equipment, network elements and racks map to Fusion Asset records; capitalised cost and accumulated depreciation come from the existing FAM source of record (not Netcracker), which lacks the capitalisation lifecycle; Netcracker preserves the asset_inventory_id as a Fusion Asset DFF for OSS-to-finance traceability (which cell tower, which transmission element, which submarine cable segment). Where Fusion Assets is not the target, Active Inventory is archived alongside BSS for operational forensics without loading to Fusion.
TM Forum SID models products as Product Specification (the technical definition), Product Offering (the commercial wrapper), and Product Offering Price (the tariff). A wireless plan typically contains a dozen Product Offerings, each linked to multiple Product Specifications, each rated by complex Product Offering Price logic. The netcracker data mapping doesn't replicate that hierarchy in Fusion COA — Fusion COA isn't built for it. Instead, the mapping identifies the material reporting dimensions (typically Product Family + Service Type + Region + Customer Segment) and routes them to dedicated COA segments. Non-material attributes (specific Product Offering variants, tariff plan codes, promotional overlays) become AR Transaction DFFs for analytical retrieval and Fusion BI Publisher reports — without polluting GL.
Tier-1 telcos with multi-jurisdictional operations book revenue in many currencies — USD, EUR, GBP, INR, JPY, BRL and a long tail of emerging-market currencies. The netcracker data mapping carries the original transaction currency through every layer: invoice currency on AR Transactions, payment currency on AR Receipts, partner-settlement currency on AP Invoices, with Fusion Ledger functional-currency conversion applied at posting time using the rate type signed off by finance (corporate rate, daily rate or period-end rate depending on the entity and the Fusion Ledger configuration). FX gain/loss journals route to the GL accounts agreed during the COA design phase. Original currency and original amount preserve as AR Transaction DFFs for revenue assurance.
Mapping documentation is a deliverable in its own right — Syntra ETL issues the netcracker data mapping as a structured workbook covering: source-object inventory per Netcracker instance, target-object inventory per Fusion module, field-level mapping per source-target pair, default and conditional logic, dependent reference data, validation rules, reconciliation grain (count, sum, hash) and sign-off authority per mapping. Each mapping is signed off by finance, revenue assurance, BSS engineering and compliance leads before build proceeds. The workbook lives in the project governance tool of record and remains the source of truth for hypercare and any future change.
Book a 30-minute scoping call. We'll walk through your Netcracker instance estate, Fusion target footprint and TM Forum SID customisation profile — and scope the field-level mapping workbook your finance, revenue assurance and compliance teams will sign off on.