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: HR.PAY_PAYMENT_TYPES

Object Details

Object Name:	PAY_PAYMENT_TYPES
Object Type:	TABLE
Owner:	HR
FND Design Data:	PAY.PAY_PAYMENT_TYPES
Subobject Name:
Status:	VALID

PAY_PAYMENT_TYPES holds details of the payment types that can be
processed by the system. Used to define specific payment methods in
PAY_ORG_PAYMENT_METHODS_F.

Storage Details

Tablespace:	APPS_TS_SEED
PCT Free:	10
PCT Used:

Primary Key: PAY_PAYMENT_TYPES_PK

PAYMENT_TYPE_ID

Unique Key: PAY_PAYMENT_TYPES_UK2

PAYMENT_TYPE_NAME
TERRITORY_CODE

Indexes

Index	Type	Uniqueness	Tablespace	Column
PAY_PAYMENT_TYPES_PK	NORMAL	UNIQUE	APPS_TS_SEED	PAYMENT_TYPE_ID
PAY_PAYMENT_TYPES_UK2	NORMAL	UNIQUE	APPS_TS_SEED	PAYMENT_TYPE_NAME TERRITORY_CODE

Foreign Keys

Table		Foreign Table	Foreign Key Column
PAY_ORG_PAYMENT_METHODS_F		PAY_PAYMENT_TYPES	PAY_ORG_PAYMENT_METHODS_F PAYMENT_TYPE_ID
PAY_PAYROLL_ACTIONS		PAY_PAYMENT_TYPES	PAY_PAYROLL_ACTIONS PAYMENT_TYPE_ID

Columns

Name	Datatype	Length	Mandatory	Comments
PAYMENT_TYPE_ID	NUMBER	(9)	Yes	System generated unique key.
TERRITORY_CODE	VARCHAR2	(2)		Foreign key to FND_TERRITORIES.
CURRENCY_CODE	VARCHAR2	(15)		Foreign key to FND_CURRENCIES.
CATEGORY	VARCHAR2	(2)	Yes	The different methods of payment check(cheque)/cash/magnetic tape, etc.
PAYMENT_TYPE_NAME	VARCHAR2	(80)		Name of the payment type.
ALLOW_AS_DEFAULT	VARCHAR2	(30)		Indicates if this payment method is the default payment method.
DESCRIPTION	VARCHAR2	(80)		Description of payment type.
PRE_VALIDATION_REQUIRED	VARCHAR2	(30)		Optional since only applies to magnetic category payment types.
PROCEDURE_NAME	VARCHAR2	(61)		PLSQL procedure for magnetic tape format.
VALIDATION_DAYS	NUMBER	(15)		Number of days required before method is considered valid.
VALIDATION_VALUE	VARCHAR2	(15)		Payment value to be included in a validation record. Null/normal.
LAST_UPDATE_DATE	DATE			Standard Who column - date when a user last updated this row.
LAST_UPDATED_BY	NUMBER	(15)		Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID).
CREATED_BY	NUMBER	(15)		Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
CREATION_DATE	DATE			Standard who column - date when this row was created.
RECONCILIATION_FUNCTION	VARCHAR2	(61)		PLSQL procedure for reconciling magnetic tape process.

Query Text

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


SELECT PAYMENT_TYPE_ID
,      TERRITORY_CODE
,      CURRENCY_CODE
,      CATEGORY
,      PAYMENT_TYPE_NAME
,      ALLOW_AS_DEFAULT
,      DESCRIPTION
,      PRE_VALIDATION_REQUIRED
,      PROCEDURE_NAME
,      VALIDATION_DAYS
,      VALIDATION_VALUE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
,      RECONCILIATION_FUNCTION
FROM HR.PAY_PAYMENT_TYPES;

Dependencies

[top of page]

HR.PAY_PAYMENT_TYPES does not reference any database object

HR.PAY_PAYMENT_TYPES is referenced by following:

APPS: PAY_PAYMENT_TYPES; PAY_PAYMENT_TYPES_BRUI; PAY_PAYMENT_TYPES_WHO
PUBLIC: PAY_PAYMENT_TYPES