Where is HZ_CUST_ACCOUNTS used in reporting?

It appears in 43 OTBI subject areas.

Oracle Fusion · Data dictionary

HZ_CUST_ACCOUNTS

Trading CommunityUsed in 43 subject areas14 reporting columns

Trading Community (HZ), customer accounts (the sales-side relationship layered on HZ_PARTIES).

Primary key: CUST_ACCOUNT_ID

Joins (inferred from key columns): PARTY_ID → HZ_PARTIES

Column	Key	In reports	Description (inferred)
ACCOUNT_ESTABLISHED_DATE		●	Account established date.
ACCOUNT_NAME		●	Name of the account.
ACCOUNT_NUMBER		●	Account number.
ACCOUNT_TERMINATION_DATE		●	Account termination date.
AUTOPAY_FLAG		●	Indicator (Y/N) for the autopay.
COTERMINATE_DAY_MONTH		●	Coterminate day month.
CUSTOMER_CLASS_CODE		●	Code identifying the customer class.
CUSTOMER_TYPE		●	Type of customer.
CUST_ACCOUNT_ID	PK	●	Identifier for the customer account.
HOLD_BILL_FLAG		●	Indicator (Y/N) for the hold bill.
ORIG_SYSTEM_REFERENCE		●	Orig system reference.
PARTY_ID		●	Identifier for the party.
STATUS		●	Status.
TAX_CODE		●	Code identifying the tax.

Change a column here and these are the reports that move with it, the blast radius for any change to HZ_CUST_ACCOUNTS.

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for HZ_CUST_ACCOUNTS?

We ship parameterized SQL, BICC config, and dbt models you own.

Problems that run through this table