Results for “cis_tax_code”

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

Overview

The APPS.IGI_CIS_GET_PROFILE package body is a component of the Oracle E-Business Suite (EBS) Construction Industry Scheme (CIS) functionality delivered through the IGI (International Governmental Industry) product family. Its principal business purpose is to retrieve configuration and profile-derived values that govern CIS tax processing for subcontractors in the United Kingdom. In EBS 12.1.1 and 12.2.2, the CIS provisions require the application to determine the correct tax treatment regime applicable to a subcontractor — deductions at the lower rate, higher rate, gross payment status, or verification outcome — and to map that treatment to an appropriate tax code or tax group for downstream supplier invoicing and payment processing.

Rather than hard-coding jurisdictional tax values, the package reads EBS profile option values that administrators maintain through the standard Profile Options setup, then exposes convenience accessors that other CIS components call at runtime. This design allows tax codes and tax groups to be configured per site or organization without code changes.

Key Procedures and Functions

ETRM documents two callable units within this package body:

• CIS_TAX_CODE — Returns the CIS tax code configured for the applicable context. It resolves the profile-based value representing the tax code that should be applied to a subcontractor payment or invoice line under CIS rules. This is the finer-grained value used when a specific tax code (for example, a rate-specific code) is required.
• CIS_TAX_GROUP — Returns the CIS tax group configured for the applicable context. The tax group typically aggregates multiple tax codes or governs the default tax determination set for CIS transactions.

Both units share a common characteristic: their inputs are not supplied as explicit business parameters but are resolved internally by querying profile option tables based on the current session context (such as responsibility, user, or site). Because the metadata does not document parameter lists, no explicit argument signatures are asserted here; the functional contract is the retrieval of profile-derived tax configuration values.

Tables Accessed

The package reads from two FND profile tables:

• FND_PROFILE_OPTIONS — The definition table for all profile options registered in the application. It is accessed to identify and validate the CIS-related profile option names that the package resolves.
• FND_PROFILE_OPTION_VALUES — Stores the actual assigned values at each hierarchy level (Site, Application, Responsibility, User). The package queries this table to obtain the effective value for the current runtime context.

Additionally, the package body references the STANDARD package in the SYS schema, which supplies standard PL/SQL built-in routines. No DML is documented: the package is read-only with respect to persistent data, consistent with its role as a value-retrieval utility.

Usage Notes

This package is not referenced by any database object per the documented dependency trace, so it is not invoked internally by triggers, views, or other database-level constructs. Instead, it is called explicitly from the application layer. Typical invocation points include:

• CIS supplier entry and subcontractor invoice forms, where the tax code and tax group must be defaulted based on profile configuration.
• Payables-related processing that applies CIS deductions.
• Custom extensions or concurrent programs that need to reproduce the standard CIS tax determination logic.

Because profile option values are cached by the FND profile machinery within a session, callers should expect values resolved at the current effective hierarchy level and should re-invoke the package after a profile change if the session cache is refreshed. The package's four documented reverse dependencies indicate that four other packages in the APPS schema consume these accessors, reinforcing that it functions as a shared configuration service rather than an entry-point API. Developers extending CIS behavior should call CIS_TAX_CODE and CIS_TAX_GROUP rather than duplicating profile queries, thereby preserving consistency with standard CIS processing across 12.1.1 and 12.2.2.