IBY_INBOUND_FILE
Stores files received from external payment systems such as payment acknowledgments or bank statements.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
IBY_INBOUND_FILE_PK |
INBOUND_FILE_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments | Status |
|---|---|---|---|---|---|---|
| INBOUND_FILE_ID | NUMBER | 18 | Yes | System-generated primary key. | Active | |
| INBOUND_FILE | BLOB | Inbound file contents as a BLOB. In encrypted form if encryption is turned on. | Active | |||
| PROCESSING_STATUS | VARCHAR2 | 30 | Yes | Processing status for the inbound file. Values taken from lookup: IBY_INB_FILE_PROC_STATUS | Active | |
| FORMAT_TYPE_CODE | VARCHAR2 | 30 | Format type of the inbound file. | Active | ||
| FORMAT_CODE | VARCHAR2 | 30 | Format of the inbound file. | Active | ||
| BEPID | NUMBER | 18 | Payment system that the inbound file is pulled from. | Active | ||
| TRANSMIT_CONFIG_ID | NUMBER | 18 | Transmission configuration used for retrieving or receiving the file from the payment system. | Active | ||
| TRADING_PARTNER_FILE_REF | VARCHAR2 | 50 | String identifier assigned by the payment system to uniquely identify an inbound file for a time period. For payment acknowledgment this maps to MessageIdentification field in ISO PaymentStatusReportV02. | Active | ||
| TRADING_PARTNER_FILE_DATE | DATE | Date/Time stamped on the inbound file by the trading partner. | Active | |||
| FILE_PATH | VARCHAR2 | 200 | File path on remote system for FTP protocol family or file path on local file system for local file. This is not the user-entered parameter, but the actual evaluated value used by the communication component to retrieve the file. | Active | ||
| FILE_NAME | VARCHAR2 | 255 | Electronic bank statement file name. | Active | ||
| FILE_LENGTH | NUMBER | 18 | Length of the file. | Active | ||
| ENCRYPTED_FLAG | VARCHAR2 | 1 | Indicates if payload is encrypted. | Active | ||
| COMPRESSED_FLAG | VARCHAR2 | 1 | Indicates if payload is compressed | Active | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | Active | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | Active | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | Active | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | Active | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | Active | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | Active | |
| ERROR_MESSAGE | VARCHAR2 | 4000 | Error message. | |||
| REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | |||
| CES_FLOW_CODE | VARCHAR2 | 64 | Code of the flow identified by Oracle Connected Partners. | |||
| CES_SUBFLOW_CODE | VARCHAR2 | 64 | Code of the sub flow identified by Oracle Connected Partners. | |||
| CES_VENDOR_CODE | VARCHAR2 | 64 | Code of the partner stored within Oracle Connected Partners. | |||
| UCM_DOC_ID | VARCHAR2 | 255 | Identifier of the document uploaded within Oracle Universal Content Management. | |||
| DOCIO_DOCUMENT_ID | NUMBER | 18 | Identifier of the corresponding Doc IO document, when the inbound file is stored or tracked through Doc IO. This enables linkage between product processing records and Doc IO ingestion/transmission details. | Active | ||
| OBJECT_STORE_REFERENCE_ID | NUMBER | 18 | Reference identifier for the file object stored in object storage or Doc IO-backed storage. Used to locate or retrieve the physical file content or related stored object. | Active | ||
| FILE_TYPE | VARCHAR2 | 30 | File extension or physical file type of the inbound file, such as PDF, CSV, TXT, or XML. | Active | ||
| DOCUMENT_STATUS_CODE | VARCHAR2 | 30 | Status of the inbound file transfer or ingestion activity, indicating whether the file was received, transferred, failed, or completed before product-level processing. | Active | ||
| PROCESSING_SUMMARY | VARCHAR2 | 4000 | Summary of file processing outcome, including success, warning, or failure details captured during import or downstream processing. This can include high-level error context when transactional parent records are not created. | Active |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| IBY_INBOUND_FILE | iby_formats_b | FORMAT_CODE |
| IBY_INBOUND_FILE | fun_docio_incoming_documents | DOCIO_DOCUMENT_ID |
| iby_transaction_acks | iby_inbound_file | INBOUND_FILE_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_INBOUND_FILE_N1 | Non Unique | Default | FILE_NAME |
| IBY_INBOUND_FILE_N2 | Non Unique | Default | TRADING_PARTNER_FILE_REF |
| IBY_INBOUND_FILE_U1 | Unique | Default | INBOUND_FILE_ID |