POR_REQ_IMPORT_HDRS_SESSION_GT
POR_REQ_IMPORT_HDRS_SESSION_GT stores information of requisition during requisition import. Because of grouping, an interface header can be split into multiple req headers. Hence, two requisition headers from the same interface header can have different values for process_flag. This table is used to store the process flag in the req header level after grouping so that we can report the process flag value for each requisition header in the output VO in the web service case. It also helps in some of our sqls later on to eliminate the need for joining to a subquery.
Details
-
Schema: FUSION
-
Object owner: POR
-
Object type: TABLE
-
Tablespace: Default
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| INTERFACE_HEADER_ID | NUMBER | 18 | Yes | Indentifier of interface header | |
| REQUISITION_HEADER_ID | NUMBER | 18 | Yes | Identifier of requisition header | |
| PROCESS_FLAG | VARCHAR2 | 30 | Process flag, could be 'IN PROCESS', 'SUCCESS', 'ERROR', 'FAILED' or 'PARTIAL' | ||
| REQUISITION_NUMBER | VARCHAR2 | 64 | Requisition number | ||
| DOCUMENT_STATUS | VARCHAR2 | 25 | Document status | ||
| INTERFACE_HEADER_KEY | VARCHAR2 | 50 | Cloud interface alternate header key code for integrating applications to be able to identify the requisition header data loaded in the interface table. | ||
| LOAD_REQUEST_ID | NUMBER | 18 | SQL Loader request identifier |
Indexes
| Index | Uniqueness | Columns |
|---|---|---|
| POR_HRDS_SESSION_GT_N1 | Non Unique | INTERFACE_HEADER_ID |
| POR_HRDS_SESSION_GT_N2 | Non Unique | PROCESS_FLAG |
| POR_HRDS_SESSION_GT_U1 | Unique | REQUISITION_HEADER_ID |