Results for “phone_no”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_IE_P45_ADDRESS_DETAILS is an Oracle E-Business Suite view owned by the APPS schema and delivered within the Payroll (PAY) product module. Its documented purpose is to supply address information to the Irish P45 form, the statutory end-of-employment tax certificate issued under Irish Revenue requirements. The view is therefore a reporting-only construct: it does not store data, but projects a denormalised, form-ready address record from the underlying payroll action and action information tables.
The view is functionally bound to the P45 archive process. Its driving query filters PAY_PAYROLL_ACTIONS for REPORT_TYPE = 'P45', REPORT_QUALIFIER = 'IE', REPORT_CATEGORY = 'ARCHIVE' and ACTION_STATUS = 'C'. Only completed Irish P45 archive actions are visible, which means the view returns data exclusively for employees whose P45 has already been processed and stored. The object is reported as VALID in EBS 12.1.1 and 12.2.2, and its definition is unchanged between those releases.
Underlying Base Objects
The view is defined over three base objects plus one PL/SQL package, joined with a USE_NL hint that forces nested-loop execution between PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS:
PAY_PAYROLL_ACTIONS(PPA) — supplies the P45 archive action header; drives the report type, qualifier, category and completion status filters.PAY_ASSIGNMENT_ACTIONS(PAA) — links each payroll action to its constituent assignment actions viaPAYROLL_ACTION_ID.PAY_ACTION_INFORMATION(PAI_ADD) — holds the actual address attribute values, restricted toACTION_CONTEXT_TYPE = 'AAP'andACTION_INFORMATION_CATEGORY = 'ADDRESS DETAILS'. The join key isPAA.ASSIGNMENT_ACTION_ID = PAI_ADD.ACTION_CONTEXT_ID.PAY_IE_P45_ARCHIVE(package) — supplies theGET_LOOKUP_MEANINGfunction, called twice to translate stored lookup codes into displayable county and postal code values.
Address segments are held positionally in ACTION_INFORMATION5 through ACTION_INFORMATION7, with county in ACTION_INFORMATION9 and postal code in ACTION_INFORMATION12. Each is truncated to 30 characters via SUBSTR.
Key Columns
ASSIGNMENT_ACTION_ID— surrogate key linking the returned address row to a specific assignment action; the primary correlation column for downstream joins.ADDRESS1,ADDRESS2,ADDRESS3— the three free-form address lines, each capped at 30 characters.COUNTY— the decoded Irish county name, resolved throughGET_LOOKUP_MEANING('IE_COUNTY', ...).POST_CODE— the decoded Irish postal code, resolved throughGET_LOOKUP_MEANING('IE_POSTAL_CODE', ...).PHONE_NO— exposed as a literalNULL. The view does not populate a telephone number from any source column; the column exists purely to satisfy the P45 layout contract. Any query filtering or sorting onPHONE_NOwill return no rows or an arbitrary ordering.
Common Use Cases and Queries
The view is used to reproduce or audit P45 address blocks for terminated Irish employees, and to validate that address information was archived correctly at the point of P45 generation.
SELECT assignment_action_id
, address1
, address2
, address3
, county
, post_code
FROM apps.pay_ie_p45_address_details
WHERE assignment_action_id = :p_assignment_action_id;
Because PHONE_NO is a constant NULL, it should never be used as a filter predicate. A typical diagnostic query joins the view back to assignment actions to reconcile archived address data:
SELECT paa.assignment_id
, a.address1
, a.county
, a.post_code
FROM apps.pay_ie_p45_address_details a
, apps.pay_assignment_actions paa
WHERE paa.assignment_action_id = a.assignment_action_id
AND paa.assignment_id = :p_assignment_id;
Since all filters are embedded in the view definition, no additional REPORT_TYPE or status predicates are required by callers.
-
Used by P45 form to populate Address details
APPS.PAY_IE_P45_ADDRESS_DETAILS·↳ PAY_ACTION_INFORMATION·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_IE_P45_ARCHIVE·Explore PAY module →
-
Used by P45 form to populate Address details
APPS.PAY_IE_P45_ADDRESS_DETAILS·↳ PAY_ACTION_INFORMATION·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_IE_P45_ARCHIVE·Explore PAY module →
-
Vendor master.
-
Customer master.
-
View: OP_CUST_MSTI2_VW1 12.1.1
Customer Master table view.
APPS.OP_CUST_MSTI2_VW1·↳ FND_PROFILE·↳ OP_CUST_MST·Explore GML module →
-
View: PO_VEND_MSTI2_VW1 12.1.1
View on vendor master table.
-
View: PO_VEND_MSTI2_VW1 12.2.2
View on vendor master table.
-
View: OP_CUST_MSTI2_VW1 12.2.2
Customer Master table view.
APPS.OP_CUST_MSTI2_VW1·↳ FND_PROFILE·↳ OP_CUST_MST·Explore GML module →
-
View: OPM_CUSTOMERS 12.2.2
Used for OPM customer synchronization
APPS.OPM_CUSTOMERS·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ GMF_AR_CUSTOMER·Explore GMF module →
-
View: OPM_CUSTOMERS 12.1.1
Used for OPM customer synchronization
APPS.OPM_CUSTOMERS·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ GMF_AR_CUSTOMER·Explore GMF module →
-
Table: FV_FACTS_SUBMISSION 12.2.2
Stores FACTS submission information
-
View: OP_CUST_MST_V 12.1.1
View of op_cust_mst for OPM OF customers
APPS.OP_CUST_MST_V·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ HZ_CUST_ACCOUNTS·Explore GML module →
-
Table: OP_CUST_MST_INT 12.2.2
Customer Interface table for data transferred from Oracle Receivables into the OPM customer master.
-
Table: FV_FACTS_SUBMISSION 12.1.1
Stores FACTS submission information
-
Table: PO_VEND_MST_INT 12.2.2
This table is not used in 11i.
-
Customer master.
-
View: OP_CUST_MST_V 12.2.2
View of op_cust_mst for OPM OF customers
APPS.OP_CUST_MST_V·↳ FND_PROFILE·↳ GL_PLCY_MST·↳ HZ_CUST_ACCOUNTS·Explore GML module →
-
Table: OP_CUST_MST_INT 12.1.1
Customer Interface table for data transferred from Oracle Receivables into the OPM customer master.
-
Vendor master.
-
Table: PO_VEND_MST_INT 12.1.1
This table is not used in 11i.
-
VIEW: GML.PO_VEND_MST# 12.2.2
-
VIEW: GML.PO_VEND_MST_INT# 12.2.2
-
VIEW: GML.OP_CUST_MST_INT# 12.2.2
-
VIEW: GML.OP_CUST_MST_OPM# 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.2.2
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.1.1
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.1.1
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.2.2
-
VIEW: GML.PO_VEND_MST# 12.2.2
-
VIEW: GML.OP_CUST_MST_OPM# 12.2.2
-
VIEW: GML.PO_VEND_MST_INT# 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.1.1
-
VIEW: GML.OP_CUST_MST_INT# 12.2.2
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.2.2
-
VIEW: APPS.OP_CUST_MSTI2_VW1 12.2.2
-
VIEW: APPS.PO_VEND_MSTI2_VW1 12.1.1
-
VIEW: APPS.OPM_CUSTOMERS 12.2.2
-
TABLE: GML.PO_VEND_MST_INT 12.1.1
-
VIEW: APPS.OPM_CUSTOMERS 12.1.1
-
TABLE: GML.PO_VEND_MST_INT 12.2.2
-
TABLE: GML.PO_VEND_MST 12.1.1
-
TABLE: GML.PO_VEND_MST 12.2.2