Domain catalogue Finance on ServiceNow

Cost centre and profit centre on ServiceNow

Responsibility units as governed master data: cost centres, profit centres, their managers, their hierarchies and their validity, consistent across finance, HR and planning.

SOURCES, READ IN PLACEServiceNowITSM · assetsASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN COST CENTRE AND PROFIT CENTRECost centre and profit centreone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on ServiceNow, the assembly steps, and who reads the result. Writes go through the Table API and Import Sets.
2
objects read in place from ServiceNow
catalogue
4
attribute groups assembled
catalogue
2 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The ServiceNow objects behind the golden record

Tables are read through the Table API and, for volume, exports; the rows stay in ServiceNow.

ObjectRead fromFields the domain usesFreshness
Cost centrecmn_cost_centersys_id · code · name · manager · valid_from · valid_tolive; polled or event-driven
Departmentcmn_departmentname · dept_head · cost_centerlive; polled or event-driven
The keys

How cost centre and profit centre records match, in this system's fields

code within a controlling areaname and manager (fuzzy)

The first object above carries the strong keys; the standardised attributes come from the same rows. A reorganisation is a new hierarchy version with a validity date; the units keep their ids and their history.

What is written back

Through the interfaces ServiceNow supports

Writes go through the Table API or Import Sets with a coalesce field; each call returns the sys_id or the error, logged beside the change.

InterfaceUsed forResult
Table API PUT on cmn_cost_center by coalesce on codegolden values approved for write-back: unit; responsibility; hierarchiesthe id or error ServiceNow returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

ServiceNow roles and ACLs are mapped to Lima policies once.

Register the objects2 objects from the connector catalogue; each shows its rows at once.
Nearby

This domain on other systems, and other domains on ServiceNow

Cost centre and profit centre on

Other domains on ServiceNow

Terms on this page

Controlling areaSAP's boundary within which cost centres are unique.
Standard hierarchyThe one tree every cost centre must belong to.
Read in placeThe rows stay in ServiceNow; Lima sends the filter and the columns and ServiceNow returns the matching rows.
Questions

Does this domain copy data out of ServiceNow?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the ServiceNow team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in ServiceNow.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.