Results for “gl_sevt_ttl”

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

Overview

GL_SEVT_TTL is a table owned by the GMF schema (Process Manufacturing Financials) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores GL mapping subevent account titles — specifically, the account titles impacted by a subsystem subevent. The table acts as a configuration bridge between the master definition of subsystem events and the specific GL account titles that a given subevent will post to during the accounting generation process.

Under the heuristic Data Vault classification mined from its foreign key structure, GL_SEVT_TTL is best modelled as a link table. It represents an association between two distinct business entities — a subsystem subevent and an account title type — rather than a standalone hub or a descriptive satellite. This classification reflects its role as a junction that carries a small set of descriptive attributes alongside the two foreign key references.

Key Information Stored

The table comprises 14 documented columns. The most significant are:

• SUB_EVENT_TYPE — the subsystem subevent identity; part of the composite primary key and a foreign key to GL_SEVT_MST.
• SEQUENCE_NO — the ordering component of the composite primary key.
• ACCT_TTL_TYPE — the account title type impacted by the subevent; foreign key to GL_ACCT_TTL.
• TRANS_SIGN — the accounting sign (debit/credit indicator) applied to the mapped amount.
• JV_QTY_IND — indicates whether journal voucher quantity processing applies.
• MAP_ORGN_IND — indicates whether the mapping uses the organisation dimension.
• TRANS_CNT — a transaction count or ordinal counter used during mapping.
• TEXT_CODE — a text reference code associated with the subevent title mapping.
• DELETE_MARK — the soft-delete flag.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle who-column audit attributes.

The surrogate primary key is defined by the GL_SEVT_TTL_PK constraint, comprising (SUB_EVENT_TYPE, SEQUENCE_NO). Because this same unique index is the only business-key candidate documented, the primary key doubles as the natural business key for this junction. No separate numeric surrogate identifier is present; the composite key is the record identity.

Common Use Cases and Queries

This table is typically queried when diagnosing or auditing how a Process Manufacturing subevent resolves to GL accounts — for example, verifying debit/credit sign, organisation mapping, and quantity handling per account title.

• Retrieving all account titles for a given subevent:

  SELECT sequence_no, acct_ttl_type, trans_sign,
         jv_qty_ind, map_orgn_ind
  FROM   gl_sevt_ttl
  WHERE  sub_event_type = :sub_event_type
  AND    delete_mark = 0
  ORDER BY sequence_no;

• Joining to master subevent definitions to produce a reporting view of subevent-to-title mappings.
• Validating that every active subevent has at least one account title row before running accounting generation.
• Feeding GL mapping extracts used in reconciliation and period-close reporting.

Related Objects

• GL_SEVT_MST — joined via GL_SEVT_TTL.SUB_EVENT_TYPE = GL_SEVT_MST.SUB_EVENT_TYPE; the master subevent definition.
• GL_ACCT_TTL — joined via GL_SEVT_TTL.ACCT_TTL_TYPE = GL_ACCT_TTL.ACCT_TTL_TYPE; the account title type master.
• Other GL_SEVT family tables sharing the SUB_EVENT_TYPE key that participate in the same subevent-to-mapping configuration chain.
• GL account mapping and accounting generation objects that consume the resolved titles during journal creation.