10/27/2017 Document 639024.

E1: RDA: How to Create a Handle and Use it in a Table I/O to an Alternate Data
Source (Doc ID 639024.1)

In this Document

Goal
Solution
References

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version 8.98 and later

Information in this document applies to any platform.

GOAL

I am purging tables and want to write the results to a custom archive table that resides in a different data source. This is not
working properly, the insert statement is failing. How can I access a table in an alternate data source when using Table I/O
Event Rules from within Report Design Aid?

SOLUTION

The following are the steps to create a Handle and use the Handle in Table I/O Event Rules:

1. Create a Data Dictionary [DD] item to be used as a Table Handle for the archive table.
The naming convention for the alias is HFxxxxx, where xxxxx is the name of the archive table.
Use a Class of 'Handle' and Data Type of '7.'
On the Edit Rule tab, define the archive table to which this handle is associated.
2. Create an ER variable for the Table Handle
In order to actually use this handle within the Table I/O event rules, you must first create an Event Rules [ER]
variable based on the DD item created above.
This ER variable should be defined with a Scope of either Report or Section.
Once the ER variable is created, it will now be available when selecting the Handle tab in Table I/O.
3. Create an ER Variable for the Archive Environment:
This will be a literal for the archive environment.
Use something like LL or ENV.
4. Go to Event Rules of the Driver Section
5. In the Initialize Section event, make an assignment such that ERVariable for Archive Environment = Archive
Environment Name [literal], or use a Processing Option value and pass it into the Table I/O.
The Environment Names are listed in P0094
6. Go to Table I/O by clicking on the icon
7. Open a handle for the archive table - check the "Open" radio button in the Advanced group and then Next.
8. In the next screen, select the 'Handles' tab, select the handle variable and click Next.
9. Pass the appropriate Environment variable on the following screen, e.g. 'Login Environment.'
If passing a different environment from the Login Environment, ensure that the pathcode of that environment is
installed on the machine where the table is being opened, otherwise the error "JDB9900915 - Failed to find
global table specs" is generated in the log.
10. In the Do Section event, perform the Table I/O operations, e.g. Insert, Delete, Update
11. Use the same handle as above rather than the actual table in these statements.
12. In the End Section event, be sure to CLOSE the handle again by adding a 'Close Handle' statement.

NOTE: This option assumes an advanced knowledge of the EnterpriseOne toolset, including but not limited to Report
Design Aid, Event Rules, Table I/O, etc.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=k9xlgjhal_4&id=639024.1 1/2
10/27/2017 Document 639024.1

Although event rule logic examples are provided; field assistance needs to be requested if the customer requires more
detailed development help with their implementation. These are billable activities that are not supported by Oracle
Software Support.

REFERENCES

NOTE:647066.1 - E1: FDA: Using Event Rules for Table I/O

NOTE:1393085.1 - E1: FDA: Frequently Asked Questions on Table I/O Event Rules
NOTE:658410.1 - E1: FDA: Retrieving Data from a Different Environment using Table I/O within an Interactive Application
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=k9xlgjhal_4&id=639024.1 2/2