Search Results igs_as_docproc_stup_pk

Overview

IGS_AS_DOCPROC_STUP is a setup table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to hold configuration parameters that govern Transcript Document Processing. Each row in the table represents a processing document setup, distinguishing the table as a configuration repository rather than a transactional or event-recording structure. In practical terms, it defines how academic documents such as transcripts, enrollment certificates, and duplicate documents are produced, delivered, and charged.

The table resides in the IGS schema and is marked VALID in the ETRM metadata for 12.1.1 and 12.2.2. Its primary key is IGS_AS_DOCPROC_STUP_PK, defined on the single column TPSET_ID. A unique index, IGS_AS_DOCPROC_STUP_U1, also exists on TPSET_ID, confirming it as the sole business-key candidate and implying a one-to-one relationship between the surrogate identifier and the configured setup record.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. The table stores descriptive attributes qualifying a single parent construct (identified by TPSET_ID) rather than modeling independent hubs or many-to-many links. It is best understood as a Type 1 configuration satellite whose attribute set changes through controlled functional setup rather than high-frequency transactional updates.

Key Information Stored

The table contains 19 documented columns. TPSET_ID is the surrogate primary key and the only unique business-key candidate; it uniquely identifies each document processing setup record. The remaining attributes are primarily indicator flags that toggle behavior for the document processing pipeline.

• LIFETIME_TRANS_FEE_IND — indicates whether a transcript fee applies for the lifetime of the student record.
• PROVIDE_TRANSCRIPT_IND — controls whether transcripts are generated under this setup.
• TRANS_REQUEST_IF_HOLD_IND — governs whether a transcript request is accepted when a hold is present.
• ALL_ACAD_HIST_IN_ONE_DOC_IND — determines whether all academic history is consolidated into a single document.
• HOLD_DELIV_IND — controls whether document delivery is held or suppressed.
• ALLOW_ENROLL_CERT_IND — permits production of enrollment certificates.
• BILL_ME_LATER_IND — enables deferred billing for the associated document requests.
• EDI_CAPABLE_IND and ALWAYS_SEND_DOCS_VIA_EDI — define electronic data interchange capability and whether EDI delivery is mandatory.
• PROVIDE_DUPLICATE_DOC_IND — allows issuance of duplicate documents.
• CHARGE_DOCUMENT_FEE_IND and CHARGE_DELIVERY_FEE_IND — control fee assessment for document production and delivery respectively.
• ADMINISTRATOR_ID — foreign key to FND_USER identifying the administrator responsible for the setup.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

The most common reporting need is to confirm which behaviors are enabled for a given setup, particularly when investigating fee assessment, hold handling, or EDI delivery anomalies. A simple configuration lookup pattern is:

• SELECT TPSET_ID, PROVIDE_TRANSCRIPT_IND, EDI_CAPABLE_IND, ALWAYS_SEND_DOCS_VIA_EDI, CHARGE_DOCUMENT_FEE_IND, CHARGE_DELIVERY_FEE_IND FROM IGS.IGS_AS_DOCPROC_STUP WHERE TPSET_ID = :p_tpset_id;
• Joining to FND_USER resolves the administrator name: SELECT s.TPSET_ID, u.USER_NAME, s.PROVIDE_TRANSCRIPT_IND FROM IGS.IGS_AS_DOCPROC_STUP s, FND_USER u WHERE s.ADMINISTRATOR_ID = u.USER_ID;

Typical scenarios include auditing which setups permit duplicate documents, determining whether deferred billing (BILL_ME_LATER_IND) is enabled before processing fees, and verifying EDI routing rules. Migration or comparison scripts frequently extract all indicator columns to compare configuration across environments.

Related Objects

The documented foreign-key relationship links this table to the following object, which should be used when attributing a setup to a responsible user:

• FND_USER — joined via IGS_AS_DOCPROC_STUP.ADMINISTRATOR_ID = FND_USER.USER_ID.

Beyond the documented FK, the setup row is referenced conceptually by the transcript document processing and delivery programs within the IGS Student System, which read these indicator values at run time. The primary key and unique index IGS_AS_DOCPROC_STUP_PK and IGS_AS_DOCPROC_STUP_U1 on TPSET_ID are the defined access paths. Administrators are advised to treat the table as controlled reference data and change it only through functional setup, since indicator changes take effect immediately for subsequent processing runs.