Results for “ce_ba_signatories_v”

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

Overview

CE_BA_SIGNATORIES_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite, belonging to the Cash Management (CE) product family. It exists primarily to simplify Oracle Forms coding for the Bank Account Signatory form, presenting a denormalized, user-friendly projection of signatory records without requiring form-level joins against multiple HR and Cash Management tables. In EBS 12.1.1 and 12.2.2 the view is documented as VALID and is classified as a reporting and integration convenience object rather than a transactional entity; no DML should be performed directly against it.

Because the view returns the human-readable person name, person type, organization, job, location, and e-mail alongside the signatory limits and status, it is a natural source for enquiry screens, extracts, and integrations that need to present signatory information in business terms rather than surrogate identifiers. The column PERSON_ORG_NAME in particular is the attribute most frequently searched by users, since it resolves the signatory's organization through HR lookup logic instead of exposing a raw ORGANIZATION_ID.

Underlying Base Objects

The view is defined over the following documented base objects:

• CE_BA_SIGNATORIES (synonym) — the driving table holding signatory rows, limits, status, approval attributes, and descriptive flexfield columns.
• PER_PEOPLE_F (view) — the effective-dated person record supplying FULL_NAME, INTERNAL_LOCATION, and EMAIL_ADDRESS.
• PER_ALL_ASSIGNMENTS_F (synonym) — the effective-dated assignment supplying organization and job information, joined with outer-join (+) syntax.
• HR_GENERAL (package) — invoked as HR_GENERAL.DECODE_ORGANIZATION and HR_GENERAL.DECODE_JOB to translate organization and job identifiers into display names, producing PERSON_ORG_NAME and PERSON_JOB.
• HR_PERSON_TYPE_USAGE_INFO (package) — function GET_USER_PERSON_TYPE supplies PERSON_TYPE.
• HR_PERSON_NAME and HR_SECURITY (packages) — documented dependencies supporting person name resolution and security filtering.

The join criteria require BASIG.DELETED_FLAG = 'N', an effective-dated match on PER_PEOPLE_F for SYSDATE, and an outer join to assignments restricted to non-applicant (ASSIGNMENT_TYPE <> 'B') primary assignments. Because the HR joins are effective-dated against SYSDATE, the view returns only currently effective person and assignment data.

Key Columns

• SIGNATORY_ID, BANK_ACCOUNT_ID, PERSON_ID — primary and foreign key identifiers linking the signatory to the bank account and the HR person.
• PERSON_NAME — full name from PER_PEOPLE_F.FULL_NAME.
• PERSON_ORG_NAME — organization name resolved via HR_GENERAL.DECODE_ORGANIZATION; NULL when no assignment organization exists.
• PERSON_JOB — job name resolved via HR_GENERAL.DECODE_JOB.
• PERSON_TYPE, PERSON_LOCATION, PERSON_EMAIL — person type via HR_PERSON_TYPE_USAGE_INFO, plus internal location and e-mail.
• SINGLE_LIMIT_AMOUNT, JOINT_LIMIT_AMOUNT, OTHER_LIMITS, SIGNER_GROUP — signatory authority limits and grouping.
• START_DATE, END_DATE, STATUS, APPROVAL_TYPE_FLAG, REQUESTER_ID — signatory validity window and approval metadata.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include listing all active signatories for a bank account, validating authority limits before payment approval, and extracting signatory data for treasury or audit reporting. A basic query returning the most requested attributes:

• SELECT signatory_id, bank_account_id, person_name, person_org_name, person_job, single_limit_amount, joint_limit_amount, status FROM ce_ba_signatories_v WHERE bank_account_id = :p_account_id AND status = 'ACTIVE';
• SELECT person_name, person_org_name, person_email, start_date, end_date FROM ce_ba_signatories_v WHERE person_org_name LIKE :p_org AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• SELECT person_id, person_name, person_type, signer_group, joint_limit_amount FROM ce_ba_signatories_v ORDER BY person_org_name, person_name;

Because the underlying HR joins are effective-dated against SYSDATE, historical reporting on superseded assignments or person records is not supported by this view; queries requiring point-in-time history should address the base tables directly.