This document describes concise information on EnterpriseOne specification. Detailed information can be found in the "Package Management Guide" depending on your Tools Release. See references below. Latest Package Management Guide can be found under:
The details covered in this document is in reference to E1 specification which is the attribute of a certain object. In general, an object is made up of 'C Components' and 'SPEC' and this document will focus on specs.
Depending on encoding, location and usage, specs may be called from any of the following:
| Object | Description |
|---|---|
| Central Object | This object implies it is the central repository of specifications. |
| TAMSpec | This is JDE's specific SPEC format with file extensions of *.xdb & *.ddb |
| SPEC | The short name for specification |
| Metadata | In this example, other than Business/Control data it may also be called metadata |
| Serialized Object | These objects have been generated into JAVA code that the JAS/HTML Server can interpret and use. |
Below is a brief description for each TAMSpec:
| TAMSpec | Central Object |
Replicated Object |
Object Affected | Relationship |
|---|---|---|---|---|
| ASVRDTL | F98753 | F98753<package name> | Interactive Application | Form Information for an application (Ex: is form an entry point, all the forms in an application) One record for each form (and also includes references to the data structures) |
| ASVRHDR | F98752 | F98752<package name> | Int. Application – PO Template | Application level information (Ex: attached PO Data structure, description, system code etc.) One record for each application. If the application has processing options, that information is also stored in the record |
| BOBSPEC | F98720 | F98720<package name> | Business View | Business View Information (Ex: # of tables joined, columns in the business view, data dictionary item, data item attributes, etc.) One record for each business view |
| DDCLMN | F98711 | F98711<package name> | Data Dictionary Items | Columns in a table (Ex: sequence in table, column name, data item name, table name etc.) One record for each column in a table |
| DDDICT | F9200 (F9202) (F9203) (F9207) F9210 |
N/A | Data Dictionary Items | Data Item Attributes (Ex: Size, Display Decimals, Visual Assist, Data Item Class etc.) One record exists for each data dictionary item that has been just-in-time installed |
| DDPKEYD | F98713 | F98713<package name> | Index Information on a table | Detail index information on a table (Ex: table name, which index, sequence, data item etc.) One record for each column in an index |
| DDPKEYH | F98712 | F98712<package name> | Indexes info for a table | Header level index information (Ex: indexes over a table, name of index, unique or not) One record for each table index |
| DDTABL | F98710 | F98710<package name> | Table Information | Table Information (Ex: name, prefix, etc.) One record for each table |
| DDTEXT | (F9200) F9202 F9203 F9207 (F9210) |
N/A | Data Item Text Info | Text related to a data item (Ex: glossary, column headings, row headings etc.) This is data dictionary text |
| DSTMPL | F98743 | F98743<package name> | Data Structure Information | Data Structure Information (Ex: Form interconnect, Business Function data structures, NER DS, each DS field information, etc.) One record for each business function, processing option, form interconnection, report interconnection and data structures, and power form |
| FDASPEC | F98751 | F98751<package name> | Interactive Application Information | Application Level Specification (Ex: BSVW used by the Form, controls on a form, data items, event info, hyper-control info, etc.) One record for every column, grid line, button, hyperitem, control, and so on, in the application |
| FDATEXT | F98750 | F98750<package name> | Interactive Application Information | Application Text Specifications (Ex: Column heading, control text, form name etc.) Contains override text for applications |
| GBRLINK | F98740 | F98740<package name> | Event Rule link in events on an application | Event Rules information in an application (Ex: what the events are in a form/section in an app, event, etc.) One record for each event that has event rules for applications, reports, or tables (Named event rule links are stored in the F9862) |
| GBRSPEC | F98741 | F98741<package name> | Event Detail Information | Event Detail information (Ex: What BSFN is called, # of parameters, form interconnect info in ER, etc.) One record for each line of event rules |
| GLBLTBL | F9871* F98710 F98711 F98712 F98713 |
N/A | Table Information | Table Information (Ex: columns in a table, number of columns, number of indices, column attributes, column name/properties, index information, etc.) One record for each table.The cache information from data dictionary and table specifications contains runtime table and override information. This is built dynamically the first time that the table is used |
| JDEBLC | F98762 | F98762<package name> | Business Function Information | Business Function Information (Ex: Business Function Parent DLL, location (client/server), DS template, etc) One record for each function in BSFN |
| POTEXT | F98306 | N/A | Processing Option text | Processing Option Text Information (B733.* release level and up) |
| RDATEXT | F98760 | F98760<package name> | UBE/Version Text | UBE/Version text information (Ex: including section name, control text, etc) Contains override text for batch reports |
| RDASPEC | F98761 | F98761<package name> | Report/Version Specs | UBE/Version specifications (Ex: BSVW used by the Sections, controls on a section data items, event info, sorting, selection, ER, etc.) One record for each section, column, sort, constant, and so on, in Batch Reports and Versions |
| SMRTTMPL | F98745 | N/A | Smart Field Info | Smart Field information (Ex: smart field data structures, etc.) This is a field information required by the data structure |
| N/A | F98770 | F98770<package name> | The F98770 table contains only one record for each package. This table is empty in Central Objects | |
| CGTYPE* | CGTYPE* | Code Generator Form Types are stored in specification format only | ||
| NEXTID* | F98701 | NEXTID* | F98701 table contains a local record of next IDs that are assigned to each workstation |
Some examples:
This is to determine which table to access(hence the description may be different from above tamspec) as below (this sequence is same with the sequence of package build):
For detail steps, refer to <Document 626511.1> E1: DD: Deploying Data Dictionary Changes. And make it sure that serialized objects includes Data Dictionary Item changed are flushed and generated again and clear all object caches in Java Applicaiton Server (JAS) machine.
To understand better on cache in JAS, refer to Frequently Asked Questions on Caching in EnterpriseOne and <Document 650630.1> E1: FDA: Tables Cached by JDBJ on the Web Client (JDBj Database Caches).
There is no recommendation for purging the global spec tables on a regular basis as they are regenerated automatically. Only in case that some corruption occurs, should they be deleted and regenerated upon login. Please refer to <Document 2164730.1> E1: ENV: How to Manually Delete Global Tables (including Data Dictionary Specs), Runtime Cache, and UBE Overrides on how delete global tables (including Data Dictionary) specs.