X hits on this document

414 views

0 shares

1 downloads

0 comments

55 / 131

Only Installed Applications: Set this option to YES to reverse-engineer only installed and shared applications. If this option is set to NO, all applications are reverse-engineered.

Min Rows: Leave the default value ‘0’, if you want to reverse-engineer all the tables. If you want to reverse-engineer only tables with a minimum number of rows, specify in this option the minimum number of rows.

Description Mask: Specify the description mask for filtering the reverse-engineered objects based on their description in E-Business Suite.

Flexfields: If this option is set to YES, applications’ flexfields are reverse- engineered.

Interface Tables: If this option is set to YES, applications’ interface tables are reverse-engineered.

4.

Specify the reverse mask in the Mask field in order to select the tables to reverse. The Mask field, in the Reverse tab, filters reverse-engineered objects based on their name.

Note: The Mask field and the Description Mask option are implemented using SQL Like. The patterns that you can choose from are:

%

The percentage symbol allows you to match any string of any length (including zero length).

Empty value allows you to match a single character.

3. Click Apply, and then click Reverse. You can follow the reverse-engineering process in the Execution Log.

Note: The reverse-engineering process may take several minutes. Please wait until the reversed datastores appear under the reversed module in the tree of the execution Log.

At the end of the reverse-engineering, the applications and tables are represented as sub-models and datastores. You can then use Oracle Applications as a source or a target in an interface.

Reverse-Engineering E-Business Suite Table Features

Reverse-engineering E-Business Suite Tables involves the following features:

The E-Business Suite Modules are reversed as sub-models. The sub-model names correspond to the application names.

Each application sub-model is divided into sub-models for Tables, Views, Flexfields and Interface Tables.

The tables/views and columns, as well as the primary and foreign keys are reversed in the data- stores.

A sub-model called Flexfield on <AppName> is created for each application. Data-stores in the Flexfield sub-model correspond to Concatenated_Segment_Views of registered Key flexfields for the application. These objects are a subset of Views. The datastores in the Flexfields sub-folder are named after the flexfields.

Data-stores in Interface-Table sub-model correspond to tables whose names contain the pattern INTERFACE. These objects are subset of tables.

Note: Some of the Open-interfaces (as specified in EBS Integration Repository) may have interface tables whose names may not contain the pattern INTERFACE in their names.

Knowledge Modules Reference Guide

55/131

Document info
Document views414
Page views417
Page last viewedFri Dec 09 19:31:55 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments