ORACLE WHITE PAPER

ORACLE WEB APPLICATIONS DESKTOP INTEGRATOR: DEFINE MAPPING

EXECUTIVE SUMMARY
Mappings must be defined to facilitate importing a text file, or Oracle Applications data into a document created by Web Applications Desktop Integrator (Web ADI). A Mapping associates columns being downloaded with fields in the document.

INTRODUCTION
In the Create Document Page Flow, users are given the option of selecting a Content. A Content is selected to import information into the document as it is being created on the desktop. Once the user selects a Content, they will be prompted to select a Mapping. Web ADI requires a Mapping to determine where the imported data is placed in the document. A Mapping associates all the columns that could possibly exist in the import, with all of the columns that could possibly exist in a document. New mappings do not need to be created if data does not exist for a mapped field or if a mapped field is not included in the document. Multiple mappings will only need to be created for a Content if the associations between the columns being downloaded and fields in the document change. Users importing text files will also find themselves creating more than one Mapping for the Text File Content because the structure of data in text files may vary. Mappings can be defined and modified on site through the Define Mapping pages. This document will describe the process of defining a Mapping.

ACCESS THE DEFINE MAPPING PAGE FLOW

Access the Define Mapping page flow by clicking on the Define Mapping link in the Self Service Home Page. Contact your Oracle Applications System Administrator if you do not see this link after logging into Self Service and selecting a responsibility.

10/30/03

ORACLE WHITE PAPER

SELECT AN INTEGRATOR
After selecting the Define Mapping link, you will be prompted to select an Integrator. All Mappings are defined under a particular Content. Each Content is defined under an Integrator. An Integrator indicates the Oracle Applications task you will be performing on the desktop. A Content determines the data that will be imported into the document. Both the Integrator and Content must be identified when users create documents. Choose the Integrator you will use to import information into a document as part of the create document process. The list of Contents you will be able to create Mappings for will be restricted by this selection.

SELECT A CONTENT
The Content indicates the information you will be importing into your documents. One or more Mappings can be defined for a particular Content. The Mapping you create will only be available when the Content selected in this screen is used when documents are created.

MANAGE MAPPINGS
From this screen, you can create, edit, view and delete Mappings for a Content.

10/30/03

ORACLE WHITE PAPER

Define Mapping
New mappings can be created for the selected Content by pressing the Define Mapping button in the main mapping page. Mapping Details A screen will appear prompting you for a name and key for the new Mapping. The Mapping name is what users will see in the Create Document page flow. The key is a unique value used internally to reference the Mapping. Once you save the Mapping, the key cannot be changed. There cannot be any spaces in the Mapping Key; only uppercase English, numeric and underscore characters can be used. Set the Key to Mapping Name_Your Initials. This serves as a standard for Mapping Keys, and also assures what you enter is unique. You must also enter the number of columns that will be mapped. This can be a rough estimate; columns can be added later in the Define Mapping process.

Associate Columns Use the following screen to associate columns being imported from the Content to fields in the document. Click the LOV button for the Source Column to view a list of available columns to import; if you know the Source Column, you can type it directly into the text field. Use the Target Column field directly to the right of a Source Column to create a

10/30/03

ORACLE WHITE PAPER

mapping between the two fields. The Target Column LOV contains a list of columns that can exist in a document. You may add new rows if more columns need to be mapped.

After you are done mapping columns, press the Lookup button if you have ID values in a source column that need to be translated into user values before they are downloaded to the desktop. The lookup button will reveal a check box in the Lookup column for every column that can be translated. Check the columns containing ID values you want to translate. For the General Ledger Journals Integrator, ID values in Source Columns mapped to the following Target Columns can be translated:

Target Column Balance Type Encumbrance Type

SQL Statement Used to Translate Value Select DESCRIPTION from GL_LOOKUPS where LOOKUP_CODE ID value Select ENCUMBRANCE_TYPE from GL_ENCUMBRANCE_TYPES where ENCUMBRANCE_TYPE_ID = ID value

Budget Name

Select BV.BUDGET_NAME from GL_BUDGET_VERSIONS BV, GL_BUDGETS B where BV.BUDGET_VERSION_ID = ID value

Journal Type Reverse Journal

Select MEANING from GL_LOOKUPS where LOOKUP_CODE = ID value Select MEANING from FND_LOOKUPS where LOOKUP_CODE = ID value

When you are finished, press the Apply button to save the Mapping.

Update/View Mapping
It is possible to view or edit an existing Mapping. Press the Update button next to the Mapping you wish to view or edit in the Manage Mappings screen. You will then be able to view/edit the Mapping Name, Number of Columns, and the associations between Source and Target Columns.

10/30/03

ORACLE WHITE PAPER

Duplicate Mapping
Press the Duplicate button in the Manage Mappings screen to copy an existing Mapping. You will be prompted for a name and key for the new Mapping.

Delete Mapping
Press the Delete button in the Manage Mappings screen to delete an existing Mapping. A screen will appear asking if you want to proceed in deleting the Mapping.

CONCLUSION
Mappings are a necessary component if users are to import information into documents. Unless users are importing text files whose structures change frequently, this may not be a function for every day use, but for a system administrator.

Copyright 2003, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

10/30/03