Results for “bill_to_address”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSI_IP_ACCOUNTS is a table in the CSI (Install Base) product schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. Its documented description is "Instance to Accounts (Party Accounts) Association." The table therefore serves as the association bridge between an installed base instance — represented through its instance party record — and the Oracle Receivables party accounts (customer accounts) that are financially or commercially linked to that instance. In the install base model, instances are the atomic objects tracked by CSI (items, systems, components), and CSI_I_PARTIES records the parties associated with those instances. CSI_IP_ACCOUNTS refines that association by tying an instance party to a specific HZ_CUST_ACCOUNTS record, optionally qualified by relationship type and by bill-to or ship-to address usages.

In Data Vault modeling terms, the heuristic classification for this table is satellite-leaning. Although it introduces associations, the presence of effective dating columns (ACTIVE_START_DATE, ACTIVE_END_DATE), descriptive context attributes (CONTEXT and ATTRIBUTE1 through ATTRIBUTE15), and a MIGRATED_FLAG suggests the table behaves more like a descriptive satellite surrounding the instance-party and customer-account hubs than a pure link. This is offered as a modeling suggestion rather than a documented fact.

Key Information Stored

The documented physical schema contains 36 columns. The most significant are:

• IP_ACCOUNT_ID — the surrogate primary key of the table, defined by CSI_IP_ACCOUNTS_PK and also by the unique index CS_IP_ACCOUNTS_U01.
• INSTANCE_PARTY_ID — foreign key to CSI_I_PARTIES, identifying the instance party involved in the association.
• PARTY_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the customer account linked to the instance party.
• RELATIONSHIP_TYPE_CODE — foreign key to CSI_IPA_RELATION_TYPES, qualifying the nature of the account association.
• BILL_TO_ADDRESS — foreign key to HZ_CUST_SITE_USES_ALL, indicating the bill-to site usage for the association.
• SHIP_TO_ADDRESS — foreign key to HZ_CUST_SITE_USES_ALL, indicating the ship-to site usage.
• ACTIVE_START_DATE and ACTIVE_END_DATE — the effective dating range for the association.
• OBJECT_VERSION_NUMBER — the standard optimistic locking column used by Oracle Application Framework and concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling multi-org / data security access.
• MIGRATED_FLAG — indicates whether the row was produced through a migration process.
• CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield and DFF columns reserved for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program tracking columns.
• MIGRATED_FLAG — flag indicating migration origin.

Common Use Cases and Queries

A frequent reporting requirement is to list all customer accounts associated with a given instance, joining through the instance party and customer account records. A representative query pattern is:

• Select ipa.IP_ACCOUNT_ID, ip.INSTANCE_PARTY_ID, ca.ACCOUNT_NUMBER, ca.ACCOUNT_NAME, ipa.RELATIONSHIP_TYPE_CODE, ipa.ACTIVE_START_DATE, ipa.ACTIVE_END_DATE FROM CSI_IP_ACCOUNTS ipa JOIN CSI_I_PARTIES ip ON ipa.INSTANCE_PARTY_ID = ip.INSTANCE_PARTY_ID JOIN HZ_CUST_ACCOUNTS ca ON ipa.PARTY_ACCOUNT_ID = ca.CUST_ACCOUNT_ID WHERE ipa.ACTIVE_END_DATE IS NULL OR ipa.ACTIVE_END_DATE > SYSDATE.

Additional scenarios include auditing which bill-to and ship-to site usages are attached to an instance account association by joining BILL_TO_ADDRESS and SHIP_TO_ADDRESS to HZ_CUST_SITE_USES_ALL; reporting on relationship types using CSI_IPA_RELATION_TYPES; enforcing multi-org data security by filtering on SECURITY_GROUP_ID; and identifying records loaded by migration through MIGRATED_FLAG. Because the table carries DFF columns and the WHO audit trail, it is also commonly queried for change tracking and extracts into downstream data warehouses.

Related Objects

• CSI_I_PARTIES — joined on CSI_IP_ACCOUNTS.INSTANCE_PARTY_ID = CSI_I_PARTIES.INSTANCE_PARTY_ID; provides the instance party context.
• HZ_CUST_ACCOUNTS — joined on CSI_IP_ACCOUNTS.PARTY_ACCOUNT_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID; supplies the party account.
• CSI_IPA_RELATION_TYPES — joined on CSI_IP_ACCOUNTS.RELATIONSHIP_TYPE_CODE; defines valid relationship types.
• HZ_CUST_SITE_USES_ALL — joined via BILL_TO_ADDRESS and SHIP_TO_ADDRESS; defines the site usages.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; enforces data security.
• CSI_IP_ACCOUNTS_H — the history table, joined on IP_ACCOUNT_ID; captures prior versions of the association.
• CSI_T_PARTY_ACCOUNTS — an interface/translation table referencing CSI_IP_ACCOUNTS.IP_ACCOUNT_ID; used for inbound processing of party account associations.

These relationships make CSI_IP_ACCOUNTS a central junction between the install base instance model and the Receivables customer account model within the CSI product.