Oracle eBusiness Suite Technical Reference

Release 11i - Copyright (c) 2001 - 2005 Oracle

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend

This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.

eTRM - VEA Tables and Views

TABLE - VEA.VEA_EXCEPTIONS

TABLE - VEA.VEA_LAYERS

TABLE - VEA.VEA_LAYER_HEADERS

TABLE - VEA.VEA_LAYER_LICENSES

TABLE - VEA.VEA_LAYER_PROVIDERS

TABLE - VEA.VEA_PACKAGES

TABLE - VEA.VEA_PARAMETERS

TABLE - VEA.VEA_PARAMETER_MAPPINGS

TABLE - VEA.VEA_PROGRAM_UNITS

TABLE - VEA.VEA_RELEASE_DETAILS

TABLE - VEA.VEA_TP_LAYERS

TABLE - VEA.VEA_VERSIONS

VIEW - APPS.VEA_LAYERS_V

VIEW - APPS.VEA_RELEASE_EXCEPTION_V

Table: VEA_EXCEPTIONS

Primary Key: PK_VEA_EXCEPTIONS

1. EXCEPTION_ID

Primary Key: VEA_EXCEPTIONS_PK

1. EXCEPTION_ID

Comments

This table stores the exception messages that are generated while using the Trading Partner Tool kit.

Indexes

Columns

[top of page]

VEA.VEA_EXCEPTIONS does not reference any database object

VEA.VEA_EXCEPTIONS is referenced by following:

VEA

VIEW - VEA_EXCEPTIONS#

[top of page]

Table: VEA_LAYERS

Primary Key: PK_VEA_LAYERS

1. LAYER_PROVIDER_CODE
2. LAYER_ID

Primary Key: VEA_LAYERS_PK

1. LAYER_PROVIDER_CODE
2. LAYER_ID

Foreign Keys from this table:

Comments

The VEA_LAYERS table contains information about branches with each base layer program unit.
Each row contains information about
- Which trading partner layer program unit is linked to base layer program unit
- Branching conditions under which trading partner layer program unit is to be called in place of base layer program unit
- Whether branch is active or inactive
Layer developers create branches using layer workbench and generate utility generate code to conditionally execute active branches , that is , trading partner layer program units using this information.

Indexes

Columns

[top of page]

VEA.VEA_LAYERS does not reference any database object

VEA.VEA_LAYERS is referenced by following:

VEA

VIEW - VEA_LAYERS#

[top of page]

Table: VEA_LAYER_HEADERS

Primary Key: PK_VEA_LAYER_HEADERS

1. LAYER_PROVIDER_CODE
2. LAYER_HEADER_ID

Primary Key: VEA_LAYER_HEADERS_PK

1. LAYER_PROVIDER_CODE
2. LAYER_HEADER_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

The VEA_LAYER_HEADERS table contains information about
- how base layer program units are linked with callout program units
- Which trading partner selector program unit is to be executed to derive the branch criteria
Layer developers or customers specify this information using layer workbench and it is used by generate utility to generate code for calling callout program units and trading partner selector program units.

Indexes

Columns

[top of page]

VEA.VEA_LAYER_HEADERS does not reference any database object

VEA.VEA_LAYER_HEADERS is referenced by following:

VEA

VIEW - VEA_LAYER_HEADERS#

[top of page]

Table: VEA_LAYER_LICENSES

Foreign Keys from this table:

Comments

The VEA_LAYER_LICENSES table contains information about customers licensed to use trading partner layers.
Layer developers can licenses trading partner layers to customers using the layer workbench and layer manage utility uses the license information to install layers only for licensed customers.

Indexes

Columns

[top of page]

VEA.VEA_LAYER_LICENSES does not reference any database object

VEA.VEA_LAYER_LICENSES is referenced by following:

VEA

VIEW - VEA_LAYER_LICENSES#

[top of page]

Table: VEA_LAYER_PROVIDERS

Primary Key: VEA_LAYER_PROVIDERS_PK

1. LAYER_PROVIDER_ID

Comments

This table contains information like Identifier, Code and Number for the Layer Developers.
Layer Developer Code could be created by running the LPInitiate Utility

Columns

[top of page]

VEA.VEA_LAYER_PROVIDERS does not reference any database object

VEA.VEA_LAYER_PROVIDERS is referenced by following:

VEA

VIEW - VEA_LAYER_PROVIDERS#

[top of page]

Table: VEA_PACKAGES

Primary Key: PK_VEA_PACKAGES

1. LAYER_PROVIDER_CODE
2. PACKAGE_ID

Primary Key: UK1_VEA_PACKAGES

1. APPLICATION_SHORT_NAME
2. CLIENT_SERVER_FLAG
3. NAME

Primary Key: VEA_PACKAGES_PK

1. LAYER_PROVIDER_CODE
2. PACKAGE_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

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.

Indexes

Columns

[top of page]

VEA.VEA_PACKAGES does not reference any database object

VEA.VEA_PACKAGES is referenced by following:

VEA

VIEW - VEA_PACKAGES#

[top of page]

Table: VEA_PARAMETERS

Primary Key: PK_VEA_PARAMETERS

1. LAYER_PROVIDER_CODE
2. PARAMETER_ID

Primary Key: UK1_VEA_PARAMETERS

1. LAYER_PROVIDER_CODE
2. PROGRAM_UNIT_ID
3. NAME

Primary Key: UK2_VEA_PARAMETERS

1. LAYER_PROVIDER_CODE
2. PROGRAM_UNIT_ID
3. PARAMETER_SEQ

Primary Key: VEA_PARAMETERS_PK

1. LAYER_PROVIDER_CODE
2. PARAMETER_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

The VEA_PARAMETERS table contains information about signatures of program units registered with the trading partner architecture repository
- Base layer program units
- Trading partner selector program units
- Trading partner layer program units
- Callout program units

Each row contains information about whether the parameter type, its datatype, sequence and default value.
The import utility parses package files and registers signature information about requisite program units in the repository. Layer workbench displays this information and generate utility uses this information to generate the code to call the registered program units as specified by layer developers.

Indexes

Columns

[top of page]

VEA.VEA_PARAMETERS does not reference any database object

VEA.VEA_PARAMETERS is referenced by following:

VEA

VIEW - VEA_PARAMETERS#

[top of page]

Table: VEA_PARAMETER_MAPPINGS

Primary Key: PK_VEA_PARAMETER_MAPPINGS

1. LAYER_PROVIDER_CODE
2. PARAMETER_MAPPING_ID

Primary Key: UK1_VEA_PARAMETER_MAPPINGS

1. LAYER_PROVIDER_CODE
2. LAYER_HEADER_ID
3. TPS_PARAMETER_ID
4. TPS_PARAMETER_LP_CODE

Primary Key: VEA_PARAMETER_MAPPINGS_PK

1. LAYER_PROVIDER_CODE
2. PARAMETER_MAPPING_ID

Foreign Keys from this table:

Comments

the VEA_PARAMETER_MAPPINGS table contains information about mapping between
- Parameters of base layer program unit
- Parameters of trading partner selector program unit.
It specifies IN/IN OUT parameters of base layer program units which will be passed to IN/IN OUT parameters of trading partner selector program units when called from the code generated by the architecture.
Layer developers specify the mapping using layer workbench while selecting a trading partner selector for a base layer program unit and generate utility derive exact calling syntax for trading partner selector program units using this information.

Indexes

Columns

[top of page]

VEA.VEA_PARAMETER_MAPPINGS does not reference any database object

VEA.VEA_PARAMETER_MAPPINGS is referenced by following:

VEA

VIEW - VEA_PARAMETER_MAPPINGS#

[top of page]

Table: VEA_PROGRAM_UNITS

Primary Key: PK_VEA_PROGRAM_UNITS

1. LAYER_PROVIDER_CODE
2. PROGRAM_UNIT_ID

Primary Key: VEA_PROGRAM_UNITS_PK

1. LAYER_PROVIDER_CODE
2. PROGRAM_UNIT_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

The VEA_PROGRAM_UNITS table contains information about following types of program units registered with the trading partner architecture repository
- Base layer program units
- Trading partner selector program units
- Trading partner layer program units
- Callout program units
- Program units generated by the trading partner architecture
Each row contains information about whether the program unit is customizable, whether it is trading partner selector and type of program unit whether it is procedure or function. It also stores mapping between base layer program unit and corresponding program unit to be generated by the architecture.
The import utility parses package files and registers information about requisite program units in the repository. Layer workbench displays this information and generate utility uses this information to find out program units to be generated and base layer program units it is linked to.

Indexes

Columns

[top of page]

VEA.VEA_PROGRAM_UNITS does not reference any database object

VEA.VEA_PROGRAM_UNITS is referenced by following:

VEA

VIEW - VEA_PROGRAM_UNITS#

[top of page]

Table: VEA_RELEASE_DETAILS

Primary Key: PK_VEA_RELEASE_DETAILS

1. FILE_NAME
2. LAYER_PROVIDER_CODE
3. RELEASE_ID
4. APPLICATION_SHORT_NAME

Primary Key: VEA_RELEASE_DETAILS_PK

1. LAYER_PROVIDER_CODE
2. RELEASE_ID
3. APPLICATION_SHORT_NAME
4. FILE_NAME

Comments

This table contains the files that a Trading Partner Layer is dependent upon.
Base product name, file name and path of the file are stored in this table.

Indexes

Columns

[top of page]

VEA.VEA_RELEASE_DETAILS does not reference any database object

VEA.VEA_RELEASE_DETAILS is referenced by following:

VEA

VIEW - VEA_RELEASE_DETAILS#

[top of page]

Table: VEA_TP_LAYERS

Primary Key: PK_VEA_TP_LAYERS

1. LAYER_PROVIDER_CODE
2. TP_LAYER_ID

Primary Key: UK1_VEA_TP_LAYERS

1. LAYER_PROVIDER_CODE
2. NAME

Primary Key: VEA_TP_LAYERS_PK

1. LAYER_PROVIDER_CODE
2. TP_LAYER_ID

Foreign Keys to this table:

Comments

The VEA_TP_LAYERS table contains information about trading partner layers. Each row contains information about trading partner layer name, description and whether it is active or inactive.
Layer developers create trading partner layers using layer workbench. Trading partner layers can be made active or inactive using runtime option of the trading partner architecture. Generate utility look at this information to generate code to execute only active layers

Indexes

Columns

[top of page]

VEA.VEA_TP_LAYERS does not reference any database object

VEA.VEA_TP_LAYERS is referenced by following:

VEA

VIEW - VEA_TP_LAYERS#

[top of page]

Table: VEA_VERSIONS

Primary Key: VEA_VERSIONS_PK

1. VERSION_ID

Comments

This table contains the version of the files that a Trading Partner Layer is dependent upon.

Columns

[top of page]

VEA.VEA_VERSIONS does not reference any database object

VEA.VEA_VERSIONS is referenced by following:

VEA

VIEW - VEA_VERSIONS#

[top of page]

View: VEA_LAYERS_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

Internal

Columns

[top of page]

APPS

SYNONYM - VEA_LAYERS

SYNONYM - VEA_LAYER_HEADERS

SYNONYM - VEA_PACKAGES

SYNONYM - VEA_PROGRAM_UNITS

SYNONYM - VEA_TP_LAYERS

APPS.VEA_LAYERS_V is not referenced by any database object

[top of page]

View: VEA_RELEASE_EXCEPTION_V

Comments

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns

[top of page]

APPS

SYNONYM - VEA_EXCEPTIONS

SYNONYM - VEA_RELEASE_DETAILS

APPS.VEA_RELEASE_EXCEPTION_V is not referenced by any database object

[top of page]