Results for “std_occurrence_code”

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

Overview

JL_BR_AR_BANK_OCCURRENCES is a Latin America Localization (JL) table that stores bank occurrence codes used during the processing of Brazilian accounts receivable remittance and bank return files. In Oracle EBS 12.1.1 and 12.2.2, the table functions as the configuration repository that maps the occurrence codes transmitted by individual banks to the standardized occurrence codes recognized by Oracle Receivables. Each row identifies a specific occurrence code for a given bank, tied to a party record representing that financial institution.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. Because the table holds descriptive attributes that change infrequently and are keyed to a parent entity (the bank), it is best modeled as a satellite attached to a bank hub rather than as an independent hub or a link.

Key Information Stored

The table contains 29 documented columns. The most significant columns are:

• BANK_PARTY_ID — The identifier of the bank party, joining to HZ_PARTIES. This is the primary reference to the financial institution whose codes are being defined.
• BANK_OCCURRENCE_CODE — The bank-specific occurrence code received from the institution's return file. This is a principal business attribute and part of the unique business key.
• BANK_NUMBER — The bank number as transmitted, another component of the unique business key and important for distinguishing codes across bank identifiers.
• BANK_OCCURRENCE_TYPE — The classification of the occurrence (e.g., return type), used to interpret and route the mapped code.
• DESCRIPTION — The descriptive meaning of the occurrence code.
• STD_OCCURRENCE_CODE — The standardized (internal) occurrence code to which the bank code is mapped for downstream processing.
• REMITTANCE_MEDIA — The media or format associated with the remittance, distinguishing processing channels.
• DAYS_TO_SEND — The number of days associated with sending the remittance, used in scheduling or cutoff logic.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns tracking creation and modification audit information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF/descriptive flexfield columns reserved for user-defined extension attributes.

The surrogate primary key is JL_BR_AR_BANK_OCCURRENCES_PK, defined on (BANK_PARTY_ID, BANK_OCCURRENCE_CODE, BANK_OCCURRENCE_TYPE). The documented unique index JL_BR_AR_BANK_OCCURRENCES_U1 on (BANK_OCCURRENCE_CODE, BANK_NUMBER, BANK_OCCURRENCE_TYPE) is a business-key candidate that enforces uniqueness of the bank code combination.

Common Use Cases and Queries

Typical scenarios include reconciling inbound bank return files, validating that a received occurrence code is registered before processing, and reporting on configuration coverage. A representative query joins to HZ_PARTIES to resolve the bank name along with its codes:

• SELECT b.BANK_OCCURRENCE_CODE, b.BANK_NUMBER, b.BANK_OCCURRENCE_TYPE, b.DESCRIPTION, b.STD_OCCURRENCE_CODE, b.REMITTANCE_MEDIA, p.PARTY_NAME FROM JL_BR_AR_BANK_OCCURRENCES b, HZ_PARTIES p WHERE b.BANK_PARTY_ID = p.PARTY_ID AND b.BANK_OCCURRENCE_TYPE = :p_type;
• Look up the standardized code for a received bank code: SELECT STD_OCCURRENCE_CODE FROM JL_BR_AR_BANK_OCCURRENCES WHERE BANK_OCCURRENCE_CODE = :code AND BANK_NUMBER = :number AND BANK_OCCURRENCE_TYPE = :type;
• Detect unregistered bank codes by comparing the return interface against this table on BANK_OCCURRENCE_CODE, BANK_NUMBER, and BANK_OCCURRENCE_TYPE.

Reporting use cases include auditing configuration completeness per bank, listing remittance media mappings, and analyzing DAYS_TO_SEND parameters used during collection processing.

Related Objects

The following objects are most significant to this table, based on the documented FK relationships:

• HZ_PARTIES — Referenced by JL_BR_AR_BANK_OCCURRENCES.BANK_PARTY_ID. Supplies the bank party identity.
• JL_BR_AR_OCCURRENCE_DOCS_ALL — References this table via BANK_OCCURRENCE_CODE, BANK_NUMBER, and BANK_OCCURRENCE_TYPE. This is the primary dependent table that consumes occurrence definitions during document processing.
• JL_BR_AR_BANK_OCCURRENCES_PK — The primary key constraint on (BANK_PARTY_ID, BANK_OCCURRENCE_CODE, BANK_OCCURRENCE_TYPE).
• JL_BR_AR_BANK_OCCURRENCES_U1 — The unique index on (BANK_OCCURRENCE_CODE, BANK_NUMBER, BANK_OCCURRENCE_TYPE), acting as the business-key constraint.
• JL_BR_AR_OCCURRENCE_DOCS_ALL child columns — BANK_OCCURRENCE_CODE, BANK_NUMBER, and BANK_OCCURRENCE_TYPE form the join path linking occurrence documents to their definitions.

Because the metadata documents only one inbound reference from JL_BR_AR_OCCURRENCE_DOCS_ALL, dependency analysis should center on that table and HZ_PARTIES; the standard WHO and DFF attribute columns complete the physical schema.