Search Results trans_request_if_hold_ind




Overview

IGS.IGS_AS_DOCPROC_STUP is the institutional setup table for general Document Request Processing in Oracle E-Business Suite. It is part of the Student Systems (IGS) schema, which underpins Oracle Student System and the transcript/enrollment certification features exposed through Self-Service and Administrative flows. Each row represents one setup record, keyed by TPSET_ID, that governs the options controlling how document requests are raised, validated, charged, and delivered. In ETRM 12.1.1 the table is documented with 19 columns and resides in the APPS_TS_TX_DATA tablespace; the unique index IGS_AS_DOCPROC_STUP_U1 lives in APPS_TS_TX_IDX. The object is registered in FND Design Data as IGS.IGS_AS_DOCPROC_STUP.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table is not a high-volume transactional hub; it holds relatively stable configuration attributes that modify the behavior of downstream document request entities. Treating it as a satellite of the governing setup context (TPSET_ID) aligns well with how the application reads these flags at runtime.

Key Information Stored

The primary key is IGS_AS_DOCPROC_STUP_PK on TPSET_ID, a sequence-generated NUMBER(15). The unique index IGS_AS_DOCPROC_STUP_U1 on TPSET_ID is the business-key candidate for this setup record.

Common Use Cases and Queries

Typical scenarios include verifying whether transcript requests are enabled for a given setup, auditing which institutions enforce holds, and reporting on fee-charging configuration. A common query pattern checks the transcript indicator alongside related hold flags:

  • SELECT tpset_id, provide_transcript_ind, trans_request_if_hold_ind, hold_deliv_ind FROM igs.igs_as_docproc_stup WHERE provide_transcript_ind = 'Y';
  • Joining to FND_USER on administrator_id = user_name to identify notification recipients.
  • Reporting EDI capability: SELECT tpset_id, edi_capable_ind, always_send_docs_via_edi FROM igs.igs_as_docproc_stup;
  • Validating duplicate-processing policy via provide_duplicate_doc_ind.

Because setup rows are read at request time, queries against this table are frequently embedded in concurrent programs and OAF-based setup pages rather than ad-hoc reporting.

Related Objects

  • FND_USER — referenced through ADMINISTRATOR_ID; join on user_name or user_id depending on implementation.
  • IGS_AS_DOCPROC_STUP_PK / IGS_AS_DOCPROC_STUP_U1 — primary and unique indexes on TPSET_ID.
  • IGS_AS_DOC_REQUEST — the transactional document request entity whose validation and delivery logic consults these setup flags.
  • IGS_AS_DOC_REQUEST_ITEM — line-level document items affected by duplicate and fee indicators.
  • IGS_AS_STUDENT_HOLD — hold records evaluated against TRANS_REQUEST_IF_HOLD_IND and HOLD_DELIV_IND.
  • IGS_AS_TRANS_DETAIL / transcript views — transcript content and delivery processes governed by PROVIDE_TRANSCRIPT_IND and ALL_ACAD_HIST_IN_ONE_DOC_IND.
  • EDI partner configuration — used with EDI_CAPABLE_IND and ALWAYS_SEND_DOCS_VIA_EDI.