Results for “je_ch_sad_sequences”

24 results




Overview
Explore in AI Chat

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

Overview

The JE_CH_SAD_SEQUENCES table is a Swiss localization data object within the Oracle E-Business Suite (EBS) European Localizations (JE) product family. It is owned by the AP schema and resides in the Applications database tier. In Oracle EBS 12.1.1 and 12.2.2, this table stores the numbering sequences required for Swiss SAD (Single Administrative Document) payment processing. The SAD is the customs declaration document used across the European Union and Switzerland for cross-border goods movement, and the localization logic relies on this table to generate and track the sequential identifiers assigned to payments tied to those declarations.

The documented physical schema for release 12.2.2 lists AP as the owner, with four columns and two unique indexes. The table carries no foreign key relationships to other objects, and the metadata classifies it as standalone. Applying the heuristic Data Vault classification supplied in the metadata, the table is best modeled as a hub candidate, since it anchors a business key (SAD_ID) and holds no dependent descriptive attributes from upstream entities. This is a modeling suggestion rather than a documented constraint, and it reflects the absence of FK dependencies rather than an explicit design decision by Oracle.

Key Information Stored

The documented column set is compact, comprising four attributes, two of which form the business-key candidates captured by the unique indexes.

  • SAD_ID — The surrogate primary key, enforced by the JE_CH_SAD_SEQUENCES_PK constraint and also indexed by JE_CH_SAD_SEQUENCES_U1. It uniquely identifies each sequence record and serves as the internal join anchor for localization logic.
  • SA_NR — A sequence or reference number associated with the SAD. Together with MONTH it forms the composite business key indexed by JE_CH_SAD_SEQUENCES_U2.
  • MONTH — The period identifier for which the sequence applies, forming the second half of the JE_CH_SAD_SEQUENCES_U2 composite unique key alongside SA_NR.
  • DUE_DATE — The due date associated with the sequence record, supporting payment scheduling and aging logic within Swiss SAD processing.

The distinction between the surrogate key (SAD_ID) and the composite business key (MONTH, SA_NR) is material for integration work: external systems should reference SAD_ID for internal joins, while the MONTH/SA_NR pair represents the natural identifier that must remain unique within the Swiss localization scope.

Common Use Cases and Queries

Typical usage centers on sequence assignment, reconciliation, and period-based reporting for Swiss customs payments. A common query retrieves the active sequence for a given period:

  • SELECT SAD_ID, SA_NR, MONTH, DUE_DATE FROM AP.JE_CH_SAD_SEQUENCES WHERE MONTH = :p_month ORDER BY SA_NR;
  • SELECT SA_NR, DUE_DATE FROM AP.JE_CH_SAD_SEQUENCES WHERE MONTH = :p_month AND SA_NR = :p_sa_nr; — validates the composite business key.
  • SELECT COUNT(*) FROM AP.JE_CH_SAD_SEQUENCES WHERE DUE_DATE BETWEEN :p_from AND :p_to; — supports payment aging and due-date reporting.

Reporting scenarios include period-end reconciliation of SAD payment volumes, verification of sequence gaps, and audit extracts that trace a SAD_ID back to its payment documents. Because the table is standalone, sequence checks are typically performed in isolation and then correlated to payment tables through application logic rather than database-enforced joins.

Related Objects

The documented metadata indicates no foreign key relationships, and the Data Vault classification confirms the table is standalone. The primary and unique constraints (JE_CH_SAD_SEQUENCES_PK on SAD_ID; JE_CH_SAD_SEQUENCES_U1 on SAD_ID; JE_CH_SAD_SEQUENCES_U2 on MONTH, SA_NR) are the only documented structural dependencies within the AP schema. Consequently, no upstream tables, views, or APIs are documented as referencing JE_CH_SAD_SEQUENCES directly.

In practice, integration is maintained at the application layer, where Swiss localization processes read this table alongside other AP payment and custom declaration objects. Because no FK columns are exposed, joins must be constructed using SAD_ID or the MONTH/SA_NR business key as supplied by the calling localization logic. Where details are not documented in the ETRM metadata, they should be confirmed against the specific 12.1.1 or 12.2.2 installation before extension or reporting work is committed.