IBY_SYS_PMT_PROFILES_B_
IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified in a user-defined account payment process profile stored in IBY_ACCT_PMT_PROFILES. A combination of the two tables is defined in the view IBY_PAYMENT_PROFILES. The payment process profile as a whole controls the behavior of the payment process. To create a payment process profile, the user specifies how the payment instruction should be formatted, how it should be transmitted, how its acknowledgment and clearing files should be handled by the system, and other relevant information. This table corresponds to the Payment Process Profile pages.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_SYS_PMT_PROFILES_B_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, SYSTEM_PROFILE_CODE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | 100 | Yes | User-entered primary key. | |
| LOGICAL_GROUPING_MODE | VARCHAR2 | 30 | Specifies the grouping mode for ISO20022 format. | ||
| BEPID | NUMBER | 18 | Payment system Identifier | ||
| SECURITY_PROTOCOL_CODE | VARCHAR2 | 100 | Security protocol Identifier | ||
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | 100 | Transmission protocol Identifier | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | 30 | Payment format code | ||
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | 30 | Positive pay format code | ||
| PAY_FILE_LETTER_FORMAT_CODE | VARCHAR2 | 30 | Payment file accompanying letter format code | ||
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether a printed payment instruction should be printed immediately after the payment instruction is created. The default value of this flag is N. The value of this flag defaults to the Print Directly After Formatting parameter of the Create Payment Instruction program. | ||
| DEFAULT_PRINTER | VARCHAR2 | 255 | Printer to be used by default for printing payments. | ||
| DEFAULT_PAYMENT_DOCUMENT_ID | NUMBER | 18 | Payment document to be used by default for printing payments. | ||
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | 80 | Name of the sequence. The name is referenced in the payment format templates. | ||
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | 80 | Name of the sequence. The name is referenced in the payment format templates. | ||
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | 80 | Name of the sequence. The name is referenced in the payment format templates. | ||
| PROCESSING_TYPE | VARCHAR2 | 30 | Specifies what type of processing should be done. Values from the IBY_PROCESSING_TYPES lookup include ELECTRONIC and PRINTED. | ||
| MARK_COMPLETE_EVENT | VARCHAR2 | 30 | Event at which payments in a payment instruction are automatically marked complete. Values are from the lookup IBY_MARK_COMPLETE_EVENTS. Value for payments with a processing type of Printed is always PRINTED. | ||
| MANUAL_MARK_COMPLETE_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether an administrator can manually mark the payments in a payment instruction complete after the instruction is formatted, but before it is automatically marked complete | ||
| POSITIVE_PAY_DELIVERY_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether Positive Pay is delivered using the same transmission configuration as the payment instruction. | ||
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether an electronic payment instruction should be transmitted immediately after the payment instruction is created. The default value of this flag is N. The value of this flag defaults to the Print Directly After Formatting parameter of the Create Payment Instruction program. | ||
| SEEDED_FLAG | VARCHAR2 | 1 | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | ||
| AUTOMATIC_PI_REG_SUBMIT | VARCHAR2 | 1 | Y or N flag indicating whether the payment instruction register is submitted automatically at the payment completion point | ||
| AUTOMATIC_PPR_REPORT_SUBMIT | VARCHAR2 | 1 | Submit payment process request status report automatically | ||
| CREATED_BY | VARCHAR2 | 64 | Who column: indicates the user who created the row. | ||
| CREATION_DATE | TIMESTAMP | Who column: indicates the date and time of the creation of the row. | |||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | 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. | ||
| DECLARATION_OPTION | VARCHAR2 | 30 | Specifies the customer's chosen declaration option. The declaration options are defined in IBY_CENTRAL_BANK_REPORT_OPTION lookup. They include NO_DECLARATIONS, DECLARE_THROUGH_BANK, and DECLARE_DIRECT_TO_CENTRAL_BANK | ||
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | 1 | Used in upgrade. | ||
| DECLARATION_REPORT_FORMAT_CODE | VARCHAR2 | 30 | Format of the Regulatory Report. Only needed if the DECLARATION_OPTION is set to DECLARE_DIRECT_TO_CENTRAL_BANK | ||
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | 255 | Exchange rate type, such as corporate, spot, and daily, used for regulatory reporting. Types are defined in the General Ledger currency exchange rate type table. | ||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | 10 | Declaration or reporting currency code | ||
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | Threshold amount, above which the payment needs to be reported to the central bank | |||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | 30 | Code of first bank instruction | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | 30 | Code of second bank instruction | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | 255 | Additional bank instruction details | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | 150 | Text message for use in payment processing | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | 150 | Text message for use in payment processing | ||
| INACTIVE_DATE | DATE | Inactive date | |||
| ACK_TRANSMIT_PROTOCOL_CODE | VARCHAR2 | 100 | Transmission protocol identifier for acknowledgment file | ||
| ACK_SECURITY_PROTOCOL_CODE | VARCHAR2 | 100 | Security protocol identifier for acknowledgment file | ||
| SEND_TO_FILE_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether the payment format output should be sent to a file or a system printer. A Y value indicates that the formatted output is sent to a file so that payments may be printed outside of Oracle Payments. An N value indicates that the printing of the formatted output is managed within Oracle Payments. | ||
| PPR_REPORT_FORMAT | VARCHAR2 | 30 | Format to be used for payment process request status report | ||
| PI_REGISTER_FORMAT | VARCHAR2 | 30 | Payment Instruction Register format | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | 150 | Descriptive Flexfield: structure definition of the user descriptive flexfield. | ||
| ATTRIBUTE1 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE2 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE3 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE4 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE5 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE6 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE7 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE8 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE9 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE10 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE11 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE12 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE13 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE14 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE15 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| OUTBOUND_PMT_FILE_DIRECTORY | VARCHAR2 | 255 | File directory where output of outbound payment file is stored | ||
| OUTBOUND_PMT_FILE_EXTENSION | VARCHAR2 | 255 | File extension of outbound payment files | ||
| OUTBOUND_PMT_FILE_PREFIX | VARCHAR2 | 255 | File name prefix of outbound payment files | ||
| POSITIVE_PAY_FILE_DIRECTORY | VARCHAR2 | 255 | File directory where output of positive pay file is stored | ||
| POSITIVE_PAY_FILE_EXTENSION | VARCHAR2 | 255 | File extension of positive pay files | ||
| POSITIVE_PAY_FILE_PREFIX | VARCHAR2 | 255 | File name prefix of positive pay files | ||
| ELECTRONIC_PROCESSING_CHANNEL | VARCHAR2 | 50 | Investigate | ||
| START_DATE | DATE | Date from which the payment process profile is available for use. | |||
| END_DATE | DATE | Date until which the payment process profile is available for use. | |||
| BATCH_BOOKING_FLAG | VARCHAR2 | 1 | Denotes if customer requests for batch booking entry to their bank. | ||
| SERVICE_LEVEL_CODE | VARCHAR2 | 30 | The service level with which a payment transaction should be processed. | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | 30 | Additional information to qualify a service level. | ||
| AUTO_RECORD_PRINTED_PMTS_FLAG | VARCHAR2 | 1 | Indicates whether the check print status is automatically recorded after payment. | ||
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| AUDIT_ACTION_TYPE_ | VARCHAR2 | 10 | Action Type - have values like INSERT, UPDATE and DELETE. | ||
| AUDIT_CHANGE_BIT_MAP_ | VARCHAR2 | 1000 | Used to store a bit map of 1s and 0s for each column in the table. | ||
| AUDIT_IMPERSONATOR_ | VARCHAR2 | 64 | Original Impersonator User. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_SYS_PMT_PROFILES_BN1_ | Non Unique | Default | SYSTEM_PROFILE_CODE, LAST_UPDATE_DATE |
| IBY_SYS_PMT_PROFILES_B_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, SYSTEM_PROFILE_CODE |