Agami Insights

Oracle Fusion BICC data warehouse amounts: the four journal line debit and credit columns beside the one column whose name ends in Amount, and the conversion rule that catches each.

Oracle Fusion Balances to the Cent. Your Warehouse Can't Prove It.

Oracle's ledger balances to the cent because the amounts are decimal. The connector lands them as floating point, and the semantic model is the only place that records they used to be exact.

IFS Cloud code part dimensions in the warehouse: nine ledger dimensions named CODE B through CODE J, beside the named dimensions on the same general ledger fact.

The Only Place IFS Says What Code Part B Means Is a Power BI File

IFS ships nine ledger dimensions named B through J, and never writes down which one is the cost centre. The semantic model is where that finally gets said.

SAP MATNR leading zeros: the readable form is declared on the type, replication copies only the column, and the padded value lands beside a trimmed copy that joins to nothing.

Two Columns, One SAP Material Number, and the Join Uses the Padded One

Your SAP warehouse stores material 4711 as 000000000000004711 and ships a trimmed copy beside it. Only one of the two joins to anything. The semantic model declares which.

Workday RaaS data warehouse grain: one data source fixes one row per primary business object inside Workday, and the warehouse gets those rows under a table name somebody typed.

Only Your Semantic Model Knows Whether a Workday Student Row Is a Student

A Workday Student table is one custom report's output, at a grain Workday fixed inside the tenant. The table name was typed by hand. The semantic model is where that grain gets declared.

Infor M3 custom fields data warehouse: the item master lands complete with no customer-defined field, while the values sit in CUGEX1 behind a literal table name in a column called FILE

In Infor M3, Your Custom Fields Are Rows in a Table Called CUGEX1

Infor M3 keeps every customer-defined field in CUGEX1, found by matching the extended table's name in a column called FILE. The semantic model declares that join and its mandatory filter.

Oracle EBS org_id in your warehouse: a session variable sets the operating unit and a view filters on it, while a replication has no session and lands every unit in one table

Oracle EBS Secured Every Operating Unit in a Session Variable. Your Warehouse Copied the Table.

Oracle partitions EBS by operating unit through a view reading a session variable. A warehouse has no session, so every unit lands in one table. The semantic model makes org_id a required dimension.

Kantata data warehouse hours by client: workspace_association has two columns and both are the primary key, so a project in three groups has its hours counted three times

The Kantata Link Table That Counts the Same Hour Once Per Group

Kantata has no client table. A client is a group with a box ticked, a project can sit in several, and the obvious join counts its hours under each. The semantic model declares the path that totals.

Autodesk Construction Cloud issue status values land beside four other vocabularies: RFI codes, submittal numbers, hyphenated step states and an asset UUID, one foreign key among them

Eighteen Autodesk Construction Cloud Tables Carry a Status Column. One Is a Foreign Key.

An open issue is the string open. An open submittal item is the string 2. An open asset is a UUID. Five modules, five status vocabularies, and the semantic model is where all five get declared.

Ivanti Neurons for ITSM data warehouse: Server, Workstation, Printer and Contract are separate business objects in Ivanti, but all 35 kinds land as rows in one ci table, keyed by citype

How to Count Servers in Ivanti When Your Warehouse Has No Server Table

Ivanti shows a server, a printer, and a vendor contract as separate business objects. The warehouse lands all 35 kinds in one ci table where Server is a value. The semantic model makes it the filter.

ukg combined pay codes in your warehouse: a Grand Overtime row sits in employee_time_card_actual_total beside the Overtime and Double Time rows it sums, flagged combined

UKG's Combined Pay Codes Land in Your Warehouse Beside the Hours They Sum

A combined pay code is the total of several pay codes, and it lands as a row beside the rows it sums. Add up the hours column and those hours count twice. The semantic model draws the line once.

certinia data warehouse: a week crossing a month is one row in pse_timecard_header_c and two in pse_timecard_c, and the header's total hours column is a formula Fivetran drops

In Your Certinia Warehouse, the Table Named Timecard Is Not the Timecard

A Certinia timecard is a week, and its total is a formula that never lands. The table the API calls Timecard is the child. The semantic model records which one is the week.

clio data warehouse: the activities table holds seconds on a time entry and a unit count on an expense in one quantity column, and the column documented as hours is optional

Clio Stores Billable Time in Seconds. The Column Named Hours Is Optional.

In a replicated Clio activities table, quantity is seconds on a time entry and a unit count on an expense. The semantic model holds the unit and the row filter that every Clio screen applies for you.