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: VEA.VEA_PACKAGES

Object Details

Object Name:	VEA_PACKAGES
Object Type:	TABLE
Owner:	VEA
FND Design Data:	VEA.VEA_PACKAGES
Subobject Name:
Status:	VALID

The VEA_PACKAGES table contains information about following types of packages registered with the trading partner architecture repository
- Base layer packages
- Trading partner selector packages
- Trading partner layer packages
- Callout packages
- Packages generated by the trading partner architecture
Each row contains information about files containing the package code, application each package belongs to and whether package is client side or server side.
The import utility parses package files and registers information about requisite packages in the repository. Layer workbench displays this information and generate utility uses this information to find out packages to be generated and corresponding file names.

Storage Details

Tablespace:	APPS_TS_SEED
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
VEA_PACKAGES_U1	NORMAL	UNIQUE	APPS_TS_SEED	LAYER_PROVIDER_CODE PACKAGE_ID
VEA_PACKAGES_U2	NORMAL	UNIQUE	APPS_TS_SEED	APPLICATION_SHORT_NAME CLIENT_SERVER_FLAG NAME

Columns

Name	Datatype	Length	Mandatory	Comments
PACKAGE_ID	NUMBER		Yes	Package Identifier
LAYER_PROVIDER_CODE	VARCHAR2	(30)	Yes	Layer developer identifier
CLIENT_SERVER_FLAG	VARCHAR2	(1)	Yes	Indicates whether package is client(C) or server(S) side package
GENERATE_FLAG	VARCHAR2	(1)		Not currently used
TPA_FLAG	VARCHAR2	(1)	Yes	Indicates whether package will be generated by the trading partner architecture, Y or N Flag
NAME	VARCHAR2	(30)	Yes	Package name
CREATED_BY	NUMBER	(15)	Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who column
REQUEST_ID	NUMBER	(15)		Standard Who column
PROGRAM_APPLICATION_ID	NUMBER	(15)		Standard Who column
PROGRAM_ID	NUMBER	(15)		Standard Who column
PROGRAM_UPDATE_DATE	DATE			Standard Who column
SPECIFICATION_FILENAME	VARCHAR2	(50)		Specification or library file name
BODY_FILENAME	VARCHAR2	(50)		Body file name
LABEL	VARCHAR2	(100)		Package label
VERSION_NUMBER	VARCHAR2	(100)		Current version number for packages generated by the architecture
DESCRIPTION	VARCHAR2	(1000)		Package description
APPLICATION_SHORT_NAME	VARCHAR2	(3)		Short name of the application , package belongs to
TP_LAYER_ID	NUMBER			Identifier for the trading partner layer, package belongs to

Query Text

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


SELECT PACKAGE_ID
,      LAYER_PROVIDER_CODE
,      CLIENT_SERVER_FLAG
,      GENERATE_FLAG
,      TPA_FLAG
,      NAME
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      SPECIFICATION_FILENAME
,      BODY_FILENAME
,      LABEL
,      VERSION_NUMBER
,      DESCRIPTION
,      APPLICATION_SHORT_NAME
,      TP_LAYER_ID
FROM VEA.VEA_PACKAGES;

Dependencies

[top of page]

VEA.VEA_PACKAGES does not reference any database object

VEA.VEA_PACKAGES is referenced by following:

APPS: VEA_PACKAGES