Oracle® Imaging and Process Management

GUI/400 Integration Installation Guide

Version 7.7

May 2007


Oracle Imaging and Process Management ERP Integration Suite, GUI/400 Installation Guide, Version 7.7

Copyright © 1998, 2007, Oracle. All rights reserved.

Primary Author: Amy Willard

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the 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 we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

ERP Integration Suite (EIS)

GUI/400 Integration

Table of Contents

GUI/400 Adapter for Application Link 4

Primary Functions 4

Design Goals 4

Prerequisites 4

Installing EIS 5

Install on DSMS 5

Please refer to “Installation and Upgrade” section in EIS.chm for installation instructions. When prompted for Features, please select “ApplicationLink” and “ApplicationLink for J.D.Edwards WorldVision”.Creating GUI/400 Panels 5

Mapping from the IBPM Client 11

GUI400 Data Mapping 11

GUI400 Populate Mapping 12

GUI/400 Adapter for Application Link

Primary Functions

There are two primary functions in the GUI/400 Adapter for Application Link:

·  Retrieve Data from a GUI/400 panel for use in later stages of an Application Link map i.e. Search, Package Update, etc.

·  Deliver Data to a GUI/400 panel (“Populate” functionality);

Design Goals

Four key issues were considered during design of this integration:

·  Seamless Integration

·  Minimal impact to Host System environment

·  Leverage existing IBPM functionality

·  Minimal time necessary for implementation in a GUI/400 environment.

Prerequisites

Before proceeding with the installation of the ERP Integration Suite (EIS), the following prerequisites must be met.

·  The current version of Imaging must be installed and operational to use the Search functionality of the integration. Please see the documentation that comes on the IBPM CD for complete installation instructions.

·  The current version of Process must be installed and operational to use the Update functionality of the integration. Please see the documentation that comes on the IBPM CD for complete installation instructions.

·  GUI/400 ADK V4.1C2 must be installed, with a valid dongle, and operational to implement any portion of this integration.

Installing EIS

The EIS Installation Wizard installs the components necessary to integrate IBPM with GUI/400. The EIS Installation Wizard must be run on the DSMS machine to successfully complete the integration.

Install on DSMS

Please refer to “Installation and Upgrade” section in EIS.chm for installation instructions. When prompted for Features, please select “ApplicationLink” and “ApplicationLink for J.D.Edwards WorldVision”.Creating GUI/400 Panels

  1. If you haven’t already run the GUI400 Configuration Assistant to configure the GUI400 ADK to connect to an AS400 it is necessary to do so.
  2. Start the GUI400 ADK.
  3. Using the Terminal Editor browse to the AS400 window that you want to make a panel match.
  4. For this example the Supplier Ledger Inquiry dialog will be used.

  1. Switch to the Panel Editor by clicking the Switch to Panel Editor toolbar button or from the menu select View | Panel Editor.
  2. From the Panel Editor select from the menu Tools | Smart Build One Panel.
  3. A Panel will appear in the Panel Editor labeled SCR0001.

  1. In the Panel Editor, select Field | Identify from the menu.
  2. Blue boxes will appear around some fields.
  3. Draw a box around the area where the column for Gross Amount is. A Field name and type dialog will appear. Enter GRSSAMTCOL in the Name field and click OK.
  4. The screen should now have a blue box around the column.

  1. Do the same with the following:

Column / FieldName
OP / OPCOL
Ty / TYCOL
Document Number / DOCNUMCOL
Document Itm / DOCITMCOL
Document Date / DOCDATECOL
Net Due Date / DUEDATECOL
Open Amount / OPENAMTCOL
PC / PCCOL
PS / PSCOL

The columns on your screen may be different, but you can make substitutions to match your screen.

  1. Select Field | Identify from the menu. This will make the blue boxes around the fields disappear.
  2. In the Panel Editor, Click on the field that shows the terminal message Opt: 1=Vouch 2=JE 3=Pmts 5=Detail F10=Pmt Ledger F21=Print F24=More and select delete. Click on all of the fields of the line items and delete them as well.

  1. Resize the panel and Right Click to drag all of the buttons on the bottom of the panel to the bottom.

  1. Select Field | List | Listbox from the menu. A List box definition dialog will appear.
  2. Click on the radio Multiple radio button. Enter OPCOL in the Selection Field and 5 in the Selected Value.
  3. Click on the Columns tab. Highlight the +++End+++ Host field in the list. Click the Add button. A List column definition dialog will appear.
  4. Enter OP in the Text textbox. Enter 5 for the Initial Length and 5 for the width.
  5. Click on the Contents tab. Enter OPCOL for the Host field.
  6. Click on the Options Tab. Enter OP for the Field ID.
  7. Click OK. The OP should appear in the Columns list.
  8. Repeat steps 17 through 22 for the following:

Text / Host Field / Field ID
Ty / TYCOL / DOCTYPE
Doc Number / DOCNUMCOL / DOCNUM
Doc Itm / DOCITMCOL / DOCITM
Doc Date / DOCDATECOL / DOCDATE
Net Due Date / DUEDATECOL / DUEDATE
Gross Amount / GRSSAMTCOL / GRSSAMT
Open Amount / OPENAMTCOL / OPENAMT
PC / PCCOL / PC
PS / PSCOL / PS

Make sure that you highlight +++End+++ before hitting the add button or the columns will be out of order.

  1. Click OK on the List box definition dialog.
  2. Drop the grid on the form below the header fields. Resize the grid and the columns appropriately.

  1. Select Tools | OIS objects | New from the menu. A object definition dialog appears.
  2. Enter LOBLINK for the Object.
  3. Enter LOBLink for the Description.
  4. Choose DLL function for the Object Type.
  5. Enter AcrdeOIS for the filename.
  6. Enter RUN for the Procedure/script.
  7. Click OK.
  8. Select Field | Button | PushButton from the menu. A Push Button definition dialog appears.
  9. Enter ~Search for the Text.
  10. Click on the Action tab. Paste the following code into the Script box.

PanelFieldPutData("LOBMAPNAME",0, "SCR0001Search")

PanelFieldPutData("LOBGRPNAME",0, "")

PanelButtonClick("LOBGO")

  1. Click OK. Position the Button on the panel.
  1. Select Field | Output | Output field from the menu. An Output field definition dialog appears.
  2. Click the Options tab and enter LOBMAPNAME for the Field ID.
  3. Click the Visibility tab. Click the Hide radio buttons for both Equal and Not equal.
  4. Click OK. Position this field anywhere on the panel. Repeat this procedure and create a field with LOBGRPNAME as the Field ID.
  5. Select Field | Button | Push Button from the menu. A Push button definition dialog will appear.
  6. Enter ~LOBGO for the Text. Click the Action tab.
  7. Enter LOBLINK as the OIS Object.
  8. Click the Options tab. Enter LOBGO as the Field ID.
  9. Click the Visibility tab. Click the Hide radio button for both Equal and Not equal.
  10. Click OK and position the button on the anywhere on the panel.
  11. Select Tools | Compile and follow the instructions to compile your panel. The .AWR file that gets generated from the compile is the file that needs to be distributed to the RTSPro client installs. The file needs to be placed in the APP directory under the RTSPro install directory.
  12. Test this panel by selecting View | Live Test from the menu. This will allow you to view the panel as if you were running a client. The search button will not work until an Application Link map is set up.

For other functionality such as Populate or Update simply add a button similar to the Search button, but change the map name to match a map that you have configured accordingly. To change the map name that is executed by a button press change this line of code.

PanelFieldPutData("LOBMAPNAME",0, "SCR0001Search")

The SCR0001Search is the map name that is executed. So change this to whatever map is to be executed.

To use map groups, change this line.

PanelFieldPutData("LOBGRPNAME",0, "")

The code to run the ABC map group will look like this

PanelFieldPutData("LOBMAPNAME",0, "")

PanelFieldPutData("LOBGRPNAME",0, "ABC")

PanelButtonClick("LOBGO")

Mapping from the IBPM Client

The Application Link map is a set of instructions that Application Link will follow when executing a transaction. In this case we are going to get data from the GUI/400 panel and execute a named search from within the IBPM client.

For more detailed information on the Map Tool see the InstallLOB.doc Installation document.

GUI400 Data Mapping
  1. Navigate in GUI400 to the panel you generated and that data is to be pulled from.
  2. Open the Map Tool from the IBPM Windows Client by selecting it from the View menu. There are two tabs in the Map Tool that are used, Map Groups and Service Maps.
  3. Select the Service Maps tab. The fields in the dialog are currently inactive or closed.
  4. Click the New button at the bottom of the dialog.
  5. Select the Service Type of GUI400 Data.
  6. The panel name with focus in GUI400 should be in the Service Templates drop-down menu. If you set up the panel described in the example it should be SCR0001. Select this item.
  7. Click the green arrow that points to the right to move to the next stage.
  8. Select the Service Type of IBPM Client Search.
  9. Select the Saved Search, that is to be run when the Search button is clicked, from the Service Template drop-down menu.
  10. In the list of fields in the input pipe, highlight the field that is to be mapped.
  11. Press the green arrow that points up until the field in the input pipe is in the same row as the field in the service input that is to be mapped.
  12. Click the Map button. Three arrows appear showing the association between the two fields.
  13. Use the same procedure to map the other fields to be populated in the search.
  14. Click the Save button.
  15. Type the map name you want. If you are mapping for the example panel the map name is SCR0001Search. Click OK.
GUI400 Populate Mapping
  1. Navigate in GUI400 to the panel you generated and that you want to deliver data to.
  2. Open the EIS Map Tool from the IBPM Windows Client by selecting it from the View menu. There are two tabs in the Map Tool that are used, Map Groups and Service Maps.
  3. Select the Service Maps tab. The fields in the dialog are currently inactive or closed.
  4. Click the New button at the bottom of the dialog.
  5. Select the Service Type of Process Client Data.
  6. Select the appropriate Package Template from the Service Template drop down menu.
  7. Click the green arrow that point to the right to move to the next stage.
  8. Select the Service Type of GUI400 Update.
  9. The panel name currently in focus in GUI400 should be in the Service Templates drop-down menu. If you set up the panel described in the example it should be SCR0001. Select this item.
  10. In the list of fields in the input pipe, highlight the field to be mapped.
  11. Press the green arrows that point up and down until the field in the input pipe is in the same row as the field in the service input that you want to map.
  12. Click the Map button. Three arrows will appear showing the association between the two fields.
  13. Use the same procedure to map the other fields that you want to map.
  14. Click the Save button.
  15. Type the map name you want. Click OK.

OneWorld Installation ERP Integration Suite

04/24/07 2