Results for “create_repository_entry”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.JAI_RGM_GST_ACCOUNTING_PKG package body is an Oracle E-Business Suite API that generates accounting entries and inserts corresponding repository records for Goods and Services Tax (GST) processing under the India localization (JAI — Japan/Asia/India) module. Introduced via bug#10043656 for the GST Enhancement in R12.1.3, and carried forward into EBS 12.1.1 and 12.2.2, the package acts as the transactional bridge between GST calculation logic and the Oracle General Ledger interface. It converts tax determination results into accounting lines, persists supporting details in the RGM (Regime) repository tables, and prepares data for the standard GL import process.
The package is classified under the "OTHER" API category in ETRM documentation, meaning it is not a formal public interface but is a supporting utility invoked internally by the GST accounting and regime infrastructure.
Key Procedures and Functions
ETRM documents two entry points in this package body:
- CREATE_REPOSITORY_ENTRY (PROCEDURE) — Inserts a new GST repository entry into the RGM transaction records table. Its parameter list includes the repository ID (OUT), regime ID, tax type, organization type and ID, location ID, source and source transaction type, source table name and document ID, transaction date, account name, charge and balancing account IDs, amount, assessable value, tax rate, reference ID, batch ID, and a "called from" indicator, along with optional defaulted parameters for inventory organization, settlement, and balancing organization/location/tax attributes. This procedure captures the full audit trail of the tax event for downstream accounting and reporting.
- CREATE_GL_ENTRY (FUNCTION) — Builds the GL accounting entry and returns the resulting interface identifier. It is the function targeted when users search for create_gl_entry, and it is responsible for transforming the GST repository record into a GL_INTERFACE-compatible row.
Tables Accessed
The package reads and writes the following documented tables through APPS synonyms:
- JAI_RGM_TRX_RECORDS and JAI_RGM_TRX_RECORDS_S — the primary GST transaction repository tables; CREATE_REPOSITORY_ENTRY inserts into these to persist tax event details.
- JAI_RGM_DEFINITIONS and JAI_RGM_REGISTRATIONS — regime and registration setup, used to validate the taxing regime and determine registered entities and their associated tax configuration.
- GL_INTERFACE — the standard General Ledger interface table; CREATE_GL_ENTRY writes accounting lines here for subsequent GL Journal Import.
- FND_CURRENCIES — used to validate and supply currency attributes (such as precision and description) for the accounting entry.
- HR_ORGANIZATION_INFORMATION — supplies organization classification and attribute data needed to resolve the correct organization context for balancing and accounting.
Usage Notes
This package is invoked from GST processing flows rather than directly by end users. Typical callers include the GST accounting integration routines, tax calculation programs, and India-localization concurrent programs that must post GST charges, assessable values, and balancing entries to the ledger. Because the balancing side of a GST transaction frequently involves a different organization, the optional balancing parameters allow the caller to pass cross-organization context without requiring a separate interface call.
When implementing or troubleshooting GST accounting, note that CREATE_REPOSITORY_ENTRY must execute before CREATE_GL_ENTRY, since the latter depends on the repository record established by the former. The generated GL_INTERFACE rows remain pending until the standard Journal Import concurrent program is run. The package is referenced by one other package within the GST infrastructure, confirming its role as a shared internal utility rather than a standalone interface. Customizations should avoid modifying this package and instead extend behavior through supported hooks, given its ship-quality header version (120.1, 2010/09/07).