Search Results pay_cn_exc

Overview

PAY_CN_EXC is a payroll localization package owned by APPS and classified under the OTHER API category in Oracle E-Business Suite. It is part of the Oracle Payroll (PAY) schema and is associated with the China (CN) localization, as indicated by the "_CN_" segment in its name. The package provides date derivation logic used by the payroll engine to resolve statutory date boundaries — such as the start of a contribution period — that are required when processing Chinese payroll. These boundaries support elements and payroll rules that must align to monthly, twelve-month, and yearly cycles rather than to the standard payroll period.

The header comment records a revision level of 120.0, last updated in May 2005, and is marked "noship," meaning the package is delivered as a database object supporting localization functionality rather than as a directly callable public interface. The package body is not part of the documented metadata, so only the specification-level behavior can be stated with certainty.

Key Procedures and Functions

The specification exposes five documented procedures, built from four distinct procedure names (DATE_EC appears twice as overloads):

• DATE_EC — The only procedure in the package carrying the generic payroll "EC" payload signature: owner and user payroll action identifiers, owner and user assignment action identifiers, owner and user effective dates, a dimension name, and an output expiry-information value. Its purpose is to compute an expiry or validity boundary for a named payroll dimension. Two overloads exist; they differ solely in the datatype of the output expiry-information parameter, one returning a NUMBER and the other a DATE. Callers must therefore select the overload that matches the expected expiry representation.
• START_CODE_P12MTH — Derives a start date representing the beginning of a rolling twelve-month window relative to the supplied effective date, for a given payroll, business group, and assignment action.
• START_CODE_PMTH — Derives a start date representing the beginning of the applicable monthly period relative to the supplied effective date, scoped by payroll, business group, and assignment action.
• START_CODE_PYEAR — Derives a start date representing the beginning of the applicable yearly period relative to the supplied effective date, again scoped by payroll, business group, and assignment action.

All three START_CODE procedures share the same input signature shape: an effective date supplied by the caller, followed by payroll, business group, and assignment action context, with a NOT NULL output start date. The consistent signature indicates that the three procedures implement the same period-anchoring algorithm at monthly, twelve-month, and yearly granularity, with the period code embedded in the procedure name.

Tables Accessed

ETRM documents three tables accessed through APPS synonyms:

• PER_TIME_PERIODS — Supplies the calendar and period definitions from which the monthly, twelve-month, and yearly start dates are resolved. This is the principal source for the START_CODE_* procedures.
• PAY_PAYROLL_ACTIONS — Provides payroll action context, consistent with the payroll action identifiers and effective dates accepted by DATE_EC.
• HR_ORGANIZATION_INFORMATION — Resolves business group level configuration or organization-level attributes used to scope the date derivation, consistent with the business group parameter passed to each procedure.

Because the package body is undocumented, the precise read/write pattern against these tables cannot be confirmed; they should be treated as reference data sources for date and organizational resolution.

Usage Notes

PAY_CN_EXC is referenced by zero other packages in the ETRM metadata, which indicates it is a leaf-level dependency invoked through configuration rather than a library consumed by other PL/SQL modules. Typical invocation points are Chinese payroll element fast formulas, payroll initialization or period-start rules, and concurrent programs that must establish statutory period boundaries before processing. Direct calls from Oracle Forms are unlikely, since the procedures require internal payroll and assignment action identifiers rather than form-level keys. Any custom code invoking the package must supply those identifiers and must handle the two DATE_EC overloads explicitly; ambiguous or untyped calls will fail to resolve at compile time.

Due to the limited documented surface, implementers should validate behavior against a test payroll before relying on the derived start dates for statutory reporting. The "noship" designation and stale revision level also suggest the package has not been revised for recent releases, so customers on 12.1.1 and 12.2.2 should confirm that the delivered version matches their localization patch level.