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: EC.ECE_TP_DETAILS

Object Details

Object Name:	ECE_TP_DETAILS
Object Type:	TABLE
Owner:	EC
FND Design Data:	EC.ECE_TP_DETAILS
Subobject Name:
Status:	VALID

ECE_TP_DETAILS contains information for the trading partner processing
rules. You need one row for each EDI transaction or transaction type
enabled for a trading partner. Each row contains the document,
document type, translator code, EDI flag, and test flag.

TP_DETAIL_ID is the unique system-generated primary key that is
invisible to the user. TP_HEADER_ID is the foreign key associated
with ECE_TP_HEADERS.

Each ECE_TP_DETAILS row is associated with one row in ECE_TP_HEADERS.
There is a one-to-many relationship between ECE_TP_HEADERS and
ECE_TP_DETAILS.

TRANSLATOR_CODE is the trading partner identifier as defined in the
EDI translator. This value links Oracle e-Commerce Gateway and the EDI
translator. The TRANSLATOR_CODE is written to the control record
(0010) in the transaction data file. For outbound transactions, the
EDI Translator will use the code to identify the trading partner to
receive the transaction. For inbound transactions, e-Commerce Gateway
will use the TRANSLATOR_CODE and Oracle Applications location code
(ECE_TP_LOCATION_CODE) to determine the unique trading partner address
site.

EDI_FLAG identifies the communication method as EDI or other. The
default value of the EDI_FLAG field is "enabled". If EDI_FLAG is
"disabled", the outbound transaction will not be extracted by
e-Commerce Gateway. Currently, some application open interface
APIs may not be reviewing the EDI_FLAG. The result is that all
transactions in the inbound data file may be loaded into the Oracle
applications open interface table.

TEST_FLAG identifies the transaction as a test or production
transaction. The default value of the TEST_FLAG is "production".
For outbound transactions, a TEST_FLAG value of "test" informs the EDI
translator and trading partner to treat the document as test,
regardless if it comes from an environment of test or production
status.

For inbound transactions, the TEST_FLAG in the control record (0010)
is passed to the application open interface tables overriding the
TEST_FLAG setting defined for the trading partner. This results in
"test" transactions being imported into the application open interface
for processing. The processing options are as follows:
{{"bul:1"}} Validate data but do not import data into the application
database as business data.
{{"bul:1"}} Validate and import data into the application database as
true business data but provide an indicator so that the user can delete
the test transaction.
{{"bul:1"}} Validate and import data into the application database as
business data with no indicator for the user. Users run a report the
identify the newly imported data.

{{"bodytext"}}Refer to the manual for each application open interface
to determine how each will treat the TEST_FLAG.

Define trading partners using the Trading Partners form. Define trading
partner processing rules in the Details tabbed region of that form.

ORG_ID is reserved for a future use.

Storage Details

Tablespace:	APPS_TS_SEED
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
ECE_TP_DETAILS_U1	NORMAL	UNIQUE	APPS_TS_SEED	TP_DETAIL_ID
ECE_TP_DETAILS_U2	NORMAL	UNIQUE	APPS_TS_SEED	TP_HEADER_ID DOCUMENT_ID DOCUMENT_TYPE
ECE_TP_DETAILS_N1	NORMAL	NONUNIQUE	APPS_TS_SEED	DOCUMENT_ID DOCUMENT_TYPE TRANSLATOR_CODE

Columns

Name	Datatype	Length	Mandatory	Comments
ORG_ID	VARCHAR2	(15)		Organization ID
TP_DETAIL_ID	NUMBER		Yes	Trading Partner Detail ID
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
CREATED_BY	NUMBER		Yes	Standard Who column
TP_HEADER_ID	NUMBER		Yes	Trading Partner Header ID
DOCUMENT_ID	VARCHAR2	(6)	Yes	Document ID
DOCUMENT_TYPE	VARCHAR2	(30)	Yes	Type of Document
TRANSLATOR_CODE	VARCHAR2	(30)		Translator Code
TEST_FLAG	VARCHAR2	(1)	Yes	EDI Test Flag
EDI_FLAG	VARCHAR2	(1)	Yes	EDI Flag
PRINT_FLAG	VARCHAR2	(1)	Yes	Print Flag
LAST_UPDATE_LOGIN	NUMBER			Standard Who column
ATTRIBUTE_CATEGORY	VARCHAR2	(150)		Descriptive Flexfield
ATTRIBUTE1	VARCHAR2	(150)		Descriptive Flexfield Segment 1
ATTRIBUTE2	VARCHAR2	(150)		Descriptive Flexfield Segment 2
ATTRIBUTE3	VARCHAR2	(150)		Descriptive Flexfield Segment 3
ATTRIBUTE4	VARCHAR2	(150)		Descriptive Flexfield Segment 4
ATTRIBUTE5	VARCHAR2	(150)		Descriptive Flexfield Segment 5
REQUEST_ID	NUMBER			Standard Who column
PROGRAM_APPLICATION_ID	NUMBER			Standard Who column
PROGRAM_ID	NUMBER			Standard Who column
PROGRAM_UPDATE_DATE	DATE			Standard Who column
DOCUMENT_STANDARD	VARCHAR2	(30)		EDI Document Standard
MAP_ID	NUMBER	(15)		Map ID

Query Text

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


SELECT ORG_ID
,      TP_DETAIL_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      TP_HEADER_ID
,      DOCUMENT_ID
,      DOCUMENT_TYPE
,      TRANSLATOR_CODE
,      TEST_FLAG
,      EDI_FLAG
,      PRINT_FLAG
,      LAST_UPDATE_LOGIN
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      DOCUMENT_STANDARD
,      MAP_ID
FROM EC.ECE_TP_DETAILS;

Dependencies

[top of page]

EC.ECE_TP_DETAILS does not reference any database object

EC.ECE_TP_DETAILS is referenced by following:

EC: ECE_TP_DETAILS#