Search Results billing_date

Overview

OTFV_COST_TRANSFER is an APPS-owned business view template in the Oracle E-Business Suite Learning Management module (OTA). It is classified in ETRM as a VIEW with VALID status, and its description explicitly identifies it as a "business view template from which the flexfield view is generated." This designation is significant: rather than a standalone reporting view, OTFV_COST_TRANSFER serves as the structural blueprint for a generated flexfield view in Oracle Training Administration (OTA). The flexfield mechanism attaches a key flexfield structure — here, the Accounting Flexfield indicated by the '_KF:SQLGL:GL#:GCC' literal mapped to the GL_CODE_COMBINATIONS alias GCC — to cost transfer reporting data so that cost center segments can be resolved and reported.

The view consolidates cost transfer activity across enrollments, finance headers and lines, delegate bookings, events, activity versions, and person records. It is used to expose training-related financial transfer information to reporting and downstream general ledger integration, particularly where a paying cost center must be associated with an internal or external enrollment.

Underlying Base Objects

The documented base objects include GL_CODE_COMBINATIONS, HR_ALL_ORGANIZATION_UNITS_TL, HR_BIS (package), OTA_ACTIVITY_VERSIONS and its _TL table, OTA_BOOKING_STATUS_TYPES and _TL, OTA_CATEGORY_USAGES and _TL, OTA_DELEGATE_BOOKINGS, OTA_EVENTS and _TL, OTA_FINANCE_HEADERS, OTA_FINANCE_LINES, OTA_GENERAL (package), OTA_OFFERINGS, and PER_ALL_PEOPLE_F. The central join is OTA_FINANCE_HEADERS.FINANCE_HEADER_ID = OTA_FINANCE_LINES.FINANCE_HEADER_ID, restricted by TFH.TYPE = 'CT' (cost transfer). The paying cost center is resolved through TFH.TRANSFER_FROM_CC_ID = GCC.CODE_COMBINATION_ID(+), making GL_CODE_COMBINATIONS an outer-joined lookup for the flexfield segments. Translation tables are joined with USERENV('LANG') to return the session-language organization names used as the business group and event center.

Key Columns

• PAYING_COST_CENTER — sourced from TFH.PAYING_COST_CENTER, the primary attribute referenced in the user search and the cost center charged for the transfer.
• BUSINESS_GROUP_NAME — from HR_ALL_ORGANIZATION_UNITS_TL, the operating business group.
• EVENT_TITLE, EVENT_TYPE, EVENT_START_DATE, TRAINING_DURATION_DAYS — event scheduling attributes from OTA_EVENTS.
• CATEGORY_NAME, ACTIVITY_NAME — activity classification and version description, with category decoded via HR_BIS.BIS_DECODE_LOOKUP('ACTIVITY_CATEGORY', ...).
• STUDENT_NAME, EMPLOYEE_NUMBER, PERSON_ID — delegate identity from PER_ALL_PEOPLE_F and OTA_DELEGATE_BOOKINGS.
• BOOKING_STATUS, BOOKING_DATE, BOOKING_ID — delegate booking lifecycle data.
• ENROLLMENT_AMOUNT, CURRENCY, BILLING_DATE, TRANSFER_DATE — financial amounts and dates from OTA_FINANCE_LINES.
• TRANSFER_STATUS — decoded through BIS_DECODE_LOOKUP('GL_TRANSFER_STATUS', ...).
• FINANCE_HEADER_ID, FINANCE_LINE_ID, OFFERING_ID, RCO_ID — surrogate keys supporting drill-down joins.

Common Use Cases and Queries

The most frequent requirement is reporting training cost transfers by paying cost center, either for reconciliation or for feeding GL. A representative query lists transfers for a paying cost center:

• SELECT paying_cost_center, student_name, event_title, enrollment_amount, currency, transfer_status FROM otfv_cost_transfer WHERE paying_cost_center = :cc ORDER BY transfer_date;
• Aggregation by cost center for management reporting: SELECT paying_cost_center, SUM(enrollment_amount) FROM otfv_cost_transfer GROUP BY paying_cost_center;

Because the view carries PERSON_ID, BOOKING_ID, and finance keys, it also supports drill-down from a summarized cost transfer report back to the underlying booking and finance line. Reporting tools and OTA integration logic reference this view for its paying cost center and transfer status attributes, while generated flexfield views inheriting its template expose the Accounting Flexfield segments needed for GL posting. Note that a typographical alias, FINANCDE_HEADER_ID, appears in the view text and should be accounted for in code that references that column.