eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: IBY.IBY_SYS_PMT_PROFILES_B

Object Details

Object Name:	IBY_SYS_PMT_PROFILES_B
Object Type:	TABLE
Owner:	IBY
FND Design Data:	IBY.IBY_SYS_PMT_PROFILES_B
Subobject Name:
Status:	VALID

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.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_SYS_PMT_PROFILES_B_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	SYSTEM_PROFILE_CODE ZD_EDITION_NAME
IBY_SYS_PMT_PROFILES_B_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	BEPID
IBY_SYS_PMT_PROFILES_B_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	TRANSMIT_PROTOCOL_CODE
IBY_SYS_PMT_PROFILES_B_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAYMENT_FORMAT_CODE
IBY_SYS_PMT_PROFILES_B_N4	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	POSITIVE_PAY_FORMAT_CODE
IBY_SYS_PMT_PROFILES_B_N5	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAY_FILE_LETTER_FORMAT_CODE
IBY_SYS_PMT_PROFILES_B_N6	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	BANK_INSTRUCTION1_CODE
IBY_SYS_PMT_PROFILES_B_N7	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	BANK_INSTRUCTION2_CODE

Columns

Name	Datatype	Length	Mandatory	Comments
SYSTEM_PROFILE_CODE	VARCHAR2	(100)	Yes	The unique Payment Process profile code entered while defining the payment process profile.
BEPID	NUMBER	(15)		Payment system Id attached to the Payment process profile.
SECURITY_PROTOCOL_CODE	VARCHAR2	(100)		Security protocol Identifier
TRANSMIT_PROTOCOL_CODE	VARCHAR2	(100)		Transmission protocol Identifier
PAYMENT_FORMAT_CODE	VARCHAR2	(30)	Yes	The Format attached to the Payment process profile for generating the payment instruction.
POSITIVE_PAY_FORMAT_CODE	VARCHAR2	(30)		The Format attached to the Payment process profile for generating the Positive pay file.
PAY_FILE_LETTER_FORMAT_CODE	VARCHAR2	(30)		The Format attached to the Payment process profile for generating the Payment file accompanying letter.
PRINT_INSTRUCTION_IMMED_FLAG	VARCHAR2	(1)	Yes	Y or N flag indicating whether a printed payment instruction should be printed immediately after the payment instruction is created. The value of this flag defaults to the Print Directly After Formatting parameter of the Create Payment Instruction Program. This is applicable only when the Payment process profiles processing type is 'Printed'.
DEFAULT_PRINTER	VARCHAR2	(255)		Printer to be used by default for printing payments. This is applicable only when the Payment process profiles processing type is 'Printed' and when the option 'Automatically print after formatting' is selected.
DEFAULT_PAYMENT_DOCUMENT_ID	NUMBER	(15)		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)	Yes	Specifies the processing type of the payment process profile. Values from IBY_PROCESSING_TYPES lookup are displayed. The values are 'Electronic', 'Printed' and 'Payment Card'.
MARK_COMPLETE_EVENT	VARCHAR2	(30)	Yes	"Event at which payments in a payment instruction are automatically marked complete for processing type 'Electronic'. Values are from the lookup IBY_MARK_COMPLETE_EVENTS. If the processing type is 'Printed', the field 'Payment completion point' is hidden and it is always updated as PRINTED."
MANUAL_MARK_COMPLETE_FLAG	VARCHAR2	(1)	Yes	Y or N flag indicating whether the user should manually mark the payment as complete after the instruction is formatted. This is applicable only when the Payment process profiles processing type is 'Electronic'.
POSITIVE_PAY_DELIVERY_FLAG	VARCHAR2	(1)	Yes	Y or N flag indicating whether Positive Pay is automatically delivered using the same transmission configuration as the payment instruction.
TRANSMIT_INSTR_IMMED_FLAG	VARCHAR2	(1)	Yes	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)	Yes	Y or N flag indicating whether the concurrent request for generating the payment instruction register is submitted automatically at the payment completion point
CREATED_BY	NUMBER	(15)	Yes	Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table.
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table.
LAST_UPDATE_DATE	DATE		Yes	Standard Who column - date when a user last updated this row
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table.
OBJECT_VERSION_NUMBER	NUMBER	(15)	Yes	Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application.
DECLARATION_OPTION	VARCHAR2	(30)		Specifies the customer's option for the 'Regulatory reporting'. The declaration options are defined in IBY_CENTRAL_BANK_REPORT_OPTION lookup. They include 'No reporting', 'Report directly to Central bank' and Reporting made by bank'
DCL_ONLY_FOREIGN_CURR_PMT_FLAG	VARCHAR2	(1)		Y or N flag to specify whether only foreign currency payments or all payments are declared. Applicable only when Regulatory reporting (DECLARATION_OPTION) option is set to 'Report Directly to Central bank' or 'Reporting Made by Bank'
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)		Indicates the type of exchange rate to be used for converting the thresh hold amount to the payment amount currency. Types are defined in the General Ledger currency exchange rate type lookups table. These include SPOT, CORPORATE, and DAILY.
DECLARATION_CURRENCY_CODE	VARCHAR2	(10)		The currency of the threshold amount in the process of regulatory reporting.
DECLARATION_THRESHOLD_AMOUNT	NUMBER			Threshold amount, above which the payment needs to be reported to the central bank
BANK_INSTRUCTION1_CODE	VARCHAR2	(30)		The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code.
BANK_INSTRUCTION2_CODE	VARCHAR2	(30)		The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code.
BANK_INSTRUCTION_DETAILS	VARCHAR2	(255)		It is a free text field that can be included for additional bank instructions.
PAYMENT_TEXT_MESSAGE1	VARCHAR2	(150)		It is a free text field that can be used payment processing.
PAYMENT_TEXT_MESSAGE2	VARCHAR2	(150)		It is a free text field that can be used payment processing.
INACTIVE_DATE	DATE			The date on which the PPP was made inactive.
ACK_TRANSMIT_PROTOCOL_CODE	VARCHAR2	(100)		Transmission protocol Identifier for acknowledgement file
ACK_SECURITY_PROTOCOL_CODE	VARCHAR2	(100)		Security protocol Identifier for acknowledgement file
SEND_TO_FILE_FLAG	VARCHAR2	(1)	Yes	Y or N flag indicating whether the payment format output should be 'Send to file' or 'Send to Printer'. Value 'Y' indicates that the formatted output is sent to a file and the payments may be printed outside of Oracle Payments. Value 'N' indicates that the printing of the formatted output is managed within Oracle Payments
PI_REGISTER_FORMAT	VARCHAR2	(30)		The Format attached to the Payment process profile for generating the Payment Instruction Register.
ATTRIBUTE_CATEGORY	VARCHAR2	(150)		Descriptive Flexfield structure defining column
ATTRIBUTE1	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE2	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE3	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE4	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE5	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE6	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE7	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE8	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE9	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE10	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE11	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE12	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE13	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE14	VARCHAR2	(150)		Descriptive Flexfield segment
ATTRIBUTE15	VARCHAR2	(150)		Descriptive Flexfield segment
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)		Indicates whether payment instruction formatting needs to be from Payments or from e-Commerce Gateway. The values flow from lookup IBY_FD_PPP_PROCESS_CHANNEL. The possible values are 'Oracle payments' and 'Oracle e-Commerce Gateway'
LOGICAL_GROUPING_MODE	VARCHAR2	(50)		Indicates the grouping mode introduced for the SEPA payments. Values include - None, Single, Mixed or Grouped.
BATCH_BOOKING_FLAG	VARCHAR2	(1)		Indicates the batch booking option introduced for the SEPA payment. The option is Y or N.
DISALLOW_SAVE_PRINT_FLAG	VARCHAR2	(1)		Indicates whether to allow the payment instruction to be saved and reprinted.
ZD_EDITION_NAME	VARCHAR2	(30)	Yes

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT SYSTEM_PROFILE_CODE
,      BEPID
,      SECURITY_PROTOCOL_CODE
,      TRANSMIT_PROTOCOL_CODE
,      PAYMENT_FORMAT_CODE
,      POSITIVE_PAY_FORMAT_CODE
,      PAY_FILE_LETTER_FORMAT_CODE
,      PRINT_INSTRUCTION_IMMED_FLAG
,      DEFAULT_PRINTER
,      DEFAULT_PAYMENT_DOCUMENT_ID
,      PERIODIC_SEQUENCE_NAME_1
,      PERIODIC_SEQUENCE_NAME_2
,      PERIODIC_SEQUENCE_NAME_3
,      PROCESSING_TYPE
,      MARK_COMPLETE_EVENT
,      MANUAL_MARK_COMPLETE_FLAG
,      POSITIVE_PAY_DELIVERY_FLAG
,      TRANSMIT_INSTR_IMMED_FLAG
,      SEEDED_FLAG
,      AUTOMATIC_PI_REG_SUBMIT
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      DECLARATION_OPTION
,      DCL_ONLY_FOREIGN_CURR_PMT_FLAG
,      DECLARATION_REPORT_FORMAT_CODE
,      DECLARATION_CURR_FX_RATE_TYPE
,      DECLARATION_CURRENCY_CODE
,      DECLARATION_THRESHOLD_AMOUNT
,      BANK_INSTRUCTION1_CODE
,      BANK_INSTRUCTION2_CODE
,      BANK_INSTRUCTION_DETAILS
,      PAYMENT_TEXT_MESSAGE1
,      PAYMENT_TEXT_MESSAGE2
,      INACTIVE_DATE
,      ACK_TRANSMIT_PROTOCOL_CODE
,      ACK_SECURITY_PROTOCOL_CODE
,      SEND_TO_FILE_FLAG
,      PI_REGISTER_FORMAT
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      OUTBOUND_PMT_FILE_DIRECTORY
,      OUTBOUND_PMT_FILE_EXTENSION
,      OUTBOUND_PMT_FILE_PREFIX
,      POSITIVE_PAY_FILE_DIRECTORY
,      POSITIVE_PAY_FILE_EXTENSION
,      POSITIVE_PAY_FILE_PREFIX
,      ELECTRONIC_PROCESSING_CHANNEL
,      LOGICAL_GROUPING_MODE
,      BATCH_BOOKING_FLAG
,      DISALLOW_SAVE_PRINT_FLAG
,      ZD_EDITION_NAME
FROM IBY.IBY_SYS_PMT_PROFILES_B;

Dependencies

[top of page]

IBY.IBY_SYS_PMT_PROFILES_B does not reference any database object

IBY.IBY_SYS_PMT_PROFILES_B is referenced by following:

IBY: IBY_SYS_PMT_PROFILES_B#