22 Work with Extensibility Tool

This chapter contains these topics:

• Section 22.1, "Reviewing the Extensibility Flow,"

• Section 22.2, "Working with Event Definition,"

• Section 22.3, "Working with Program Exports,"

• Section 22.4, "Working with Mappings,"

• Section 22.5, "Working with Extension Logic,"

• Section 22.6, "Working with Extension Management,"

You use the Extensibility Tool to extend the functionality of a base program through an external soft coding database to minimize custom modifications to the base code line. The Extensibility Tool facilitates the process to upgrade to future releases.

Navigation

From Master Directory (G), type G98X to access Extensibility

22.1 Reviewing the Extensibility Flow

The following describes the Extensibility flow.

Figure 22-1 Extensibility flow

Description of "Figure 22-1 Extensibility flow"

Figure 22-2 Extensibility flow

Description of "Figure 22-2 Extensibility flow"

To add Extensibility to a program using the Extensibility tool to perform a customizable call of one program from another program

1. Identify the placement in the calling program where the event (/COPY member) needs to be added. Set up the new custom Event Master record via P98X00 for that program placement, if the Event does not already exist.

2. Identify the logic (extension) to be added to the program (Programs to Call and so on).

3. To call the programs, identify the parameters necessary to be added. Also determine which parameters are variables versus literals.

4. Identify and include the variable parameters in the Program Exports program (P98X02).

5. Change the source in the calling program to add the /COPY Event(s) (program placements) as necessary and make the program extensible (by adding the /COPY's for D98XBASE and C98XBASE) if not already, via SVR.

6. Compile the program from SVR. If the program compiles successfully, the Events added and the variables to be exposed for Extensibility will be available and shown in the Program Exported Items program (P98X12).

7. Create an SVR record for the program to be called, if one does not already exist.

8. Establish the PLIST (*ENTRY) parameters in SVR. The parameters need to exist in the F98016 SVR-Entry Parameter Definitions file for the called program. Either run the P98016B Parameter Build DREAM Writer or enter the parameters manually thru program the SVR-Entry Parameter Definitions program (P98016). If the parameters are created using DREAM Writer P98016B, review for accuracy and make any necessary changes through the entry program (P98016).

9. Once the parameters have been established, the Mapping Values from the calling program to the program to call can be created. These are referred to as Mapping Versions maintained through the Defined Mapping Values (P98X11) program.

10. Create the logic from the calling program to the called program via the Program Extension Master (P98X03), attaching the Mapping Version created in the previous step.

11. Using the Program Event Extension (P98X01) program, tie together the Calling Program, Event and Extension Name (Program to Call) and any associated Named Condition. The new selection option or function key and the Video Text Description, for the F24 window, can also be defined when necessary.

12. Once the Program Event Extension is enabled, it can be tested.

13. The Extensibility Workbench program (P98XWB) is then used to manage the Program Event Extensions and all of its various components described in previous steps.

For quick instructions to set up Extensibility, see Appendix E, "Quick Instructions to Set up Extensibility."

22.2 Working with Event Definition

22.2.1 Event Master Maintenance (P98X00)

You use the Event Master Maintenance program (P98X00) to define an Event ID which will to be used throughout the Extensibility system. The Event ID is then associated to a /COPY member as a placement within an RPG/ILE program. An Event ID is unique and a unique Event Copy Member name must be used when defining each event.

The Event ID is a combination of two defined fields, the Event Group Code and the Event Number.

The Event Group Code separates each group of defined events. The Event Group Code with the Event Number allows upgrading and adding new events, at different release levels, without overlapping events. Since Oracle JD Edwards, Customers, and Business Partners will define their own Event Group Codes, it will be easy for each group to keep track of current and future event definitions.

The Event Number is used to uniquely define an event. The Event Number is meaningless by itself and totally dependent on the Event Group Code, this combination becomes the Event ID.

WARNING:

The JDEP and JDES Event Group Codes must not be altered in any way. These /COPY modules are integrated into the base software in several programs and any changes could cause undesirable results.