6 Using Object Usage Tracking (Release 9.2.1.2)

This chapter contains the following topics:

6.1 Understanding Object Usage Tracking

You perform an object usage tracking analysis to determine the frequency that objects are being used within a path code. This information will enable you to determine the objects that need to be validated prior to upgrading or applying an update to your system.

See the JD Edwards EnterpriseOne Tools Security Administration Guide to secure applications to system administrators only.

You can track the usage of the following objects:

  • Applications (APPL)

  • Batch Applications (UBE)

  • Business Functions (BSFN)

Note:

Object Usage Tracking is available for JD Edwards EnterpriseOne Application Release 9.0 and later releases.

6.2 Working with Object Usage Tracking Configuration (P980042T)

Object Usage Tracking is disabled by default. You enable Object Usage Tracking with the Working with Object Usage Tracking Configuration (P980042T) application. You must first enable Object Usage Tracking for the system prior to enabling at the path code level.

To activate Object Usage Tracking:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development(GH902)/Object Usage Tracking.

  2. Click Object Usage Tracking Configuration.

    The Revise Object Usage Tracking Enablement form displays the following fields and columns:

    System Level Tracking Enabled

    Checked - object tracking is enabled at the system level.

    Un-checked - Object tracking is disabled at the system level.

    Tracking

    Green circle - Object tracking is enable for the path code.

    Red Square - object tracking is disabled for the path code.

    Path Code

    The available path codes.

    Description

    The path code descriptions.

  3. Click the System Level Tracking Enabled check box.

  4. Click the path code row in the Tracking column to enable object usage tracking for that path code.

  5. Close the application.

    Note:

    You can use Server Manger to restart the HTML Server and Enterprise Server for the changes in Object Usage Tracking Configuration to take effect immediately. Otherwise, the configuration changes will not take effect until the Object Usage Tracking Configuration is automatically updated on the server every 60 minutes.

6.2.1 Disable / Enable Object Usage Tracking by Object Type (Release 9.2.2)

You can enable and disable object types through Revise Usage Tracking by Object Type (W980042TC). The Usage Tracking Configuration Lists (F98900) table maintains the object types that are disabled and enabled. By default the F98900 table is empty to prevent disruption of current Object Usage Tracking configuration. Applications and batch application are enabled for tracking and business functions are disabled until a record is added and set to disable or enable.

To enable or disable an object type for Object Usage Tracking:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. 2Click Object Usage Tracking Configuration.

  3. Select the path code you want to exclude an object type in.

  4. On the Row menu, click Object Type Tracking.

  5. On the Revise Object Type Enablement form click the Tracking column for the object type to want to enable / disable.

    • Green Circle = Enabled

    • Red Square = Disabled

  6. Click Close.

6.2.2 Object Exclusion list (Release 9.2.2)

You can add and remove object names in the Object Exclusion List (W980042T). When you add object names to the grid, Object Usage Tracking does not track them. If a business function is in the list and calls another business function, the called business function is tracked unless also added to the Object Exclusion List. The Usage Tracking Configuration Lists (F98900) table maintains the names of objects in the Object Exclusion List.

To exclude an object from Object Usage Tracking:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. Click Object Usage Tracking Configuration.

  3. Select the path code you want to exclude an object in.

  4. On the Row menu, click Exclusion List.

  5. Enter the object to be excluded in the grid.

  6. Click OK.

6.2.3 Copy Path Code

You can copy the object type and exclusion list for a path code to another path code.

To copy the tracking configuration of a path code:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. Click Object Usage Tracking Configuration.

  3. Select the path code you want to copy.

  4. Click the Copy button on the tool bar.

  5. In Object Path Search & Select, select the path code you want to copy to.

  6. Click the Select button on the tool bar.

6.3 Working with Object Usage Tracking Detail (P98911)

The Object Usage Tracking Detail (P98911) application displays all object usage recorded by the system that has not been purged from the Object Usage Tracking Detail (F98911) table. Object usage is any time a tracked object is accessed by a user or the system. Sub-system calls to an object will create only one record. The grid displays the object name, the user, path code, environment, date, time, and future use columns .You can delete individual or multiple records from the grid, or use Purge Object Usage Tracking Detail (R98911P) to delete records.

To launch Working with Object Usage Tracking Detail:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. Click Object Usage Tracking Detail.

Note:

It is recommended you increase the table size for Object Usage Tracking Detail (F98911).The table size necessary will depend on how often you run R98911P.

6.4 Working with Object Usage Tracking Summary (P98902)

The Object Usage Tracking Summary (P98902) application displays data from the Object Usage Tracking Summary (F98902) table, which is populated by running the Summarize Object Usage UBE (R98902). Object usage data in this table can be summarized by Object Name, Object Name/Form/Version, and/or Product Code. In addition, object usage counts for each type can be totaled by day, month, or year.

To launch Object Usage Tracking Summary:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. Click Object Usage Tracking Summary.

6.5 Working with Summarize Object Usage UBEs (R98902)

The Summarize Object Usage UBEs (R98902) populates the F98902 table with data up to the last complete day. The following four batch versions summarize data in F98902:

  • XJDE0001 - Summarize Object Usage by Object Name UBE

  • XJDE0002 - Summarize Object Usage by Object Form Version UBE

  • XJDE0003 - Summarize Object Usage by Product Code UBE

  • XJDE0004 - Summarize Object Usage by Business Function UBE

Each time you run a summarization version, it will summarize the records in the F98911 or F98912 tables based on the Object Tracking Type:

  • 01 - Object Name (F98911 and F98912)

  • 02 - Object Name/Form/Version (F98911)

  • 03 - Product code (F98911 and F98912)

  • 04 - object Name/Business Object (F98912)

Each summary will summarize by Tracking Unit:

  • 01 - Hours per Day (24)

  • 02 - Days per Month (28-31)

  • 03 - Months per Year (12)

Each time you run a summarization version, it will add to the existing records for Days per Month and Months per Year, so that it is cumulative from the first time it was executed and it will create new records for:

  • Hours per Day for new days

  • Days per Month for new months

  • Months per year for new years

The first time you run a summarization version, it will summarize to the current date minus 1 for the Object Tracking Type version selected.

At the end of the summarization, the UBE adds a LASTSUMMARY record to the F98902 table with Object Tracking Type of 01, 02, 03, 04 with the current date minus 1. This record will contain a value in the OSOTUT field of how many F98911 records were read.

The next time you run the UBE, it will use the LASTSUMMARY date and will only use records from that date to the current date minus 1. Each Object type will have a LASTSUMMARY record.

To launch Summarize Object Usage UBEs:

  1. Navigate to: EnterpriseOne Menus/ EnterpriseOne Life Cycle Tools/Application Development (GH902)/Object Usage Tracking.

  2. Click Summarize Object Usage by (select a version).

6.6 Purging Object Usage Tracking Detail for Applications and Batch Applications (R98911P)

You purge records from the Object Usage Tracking Detail (F98911) table by running the Purge Object Usage Tracking Detail UBE (R98911P). Complete the following processing options prior to running

Select Tab

Path Code

The path code you want to purge from.

Object Tracking Purge From Date

The date you want the purge to start.

Object Tracking Purge To Date

The date you want the purge to end.

Process Tab

Proof or Final Mode

Blank = Proof Mode

1 = Final Mode

Report View

Blank = View the summary.

1 = View the detail purge records.

Note:

It is recommended you run the Purge Object Usage Tracking Detail UBE in proof mode first to verify the summarization UBEs have been run. Use the Proof mode to generate a report that displays the Path Code, From and To Dates, Purge Total, and Last Summary Dates for each Tracking Type.

6.7 Purging Business Function Tracking Detail (R98912)

You purge records from the Business Object Usage Tracking Detail (F98912) table by running the Purge Business Function Tracking Detail UBE (R98912P).

Complete the following processing options prior to running:

Select Tab

Path Code

The path code you want to purge from.

From Date

The date you want the purge to start.

To Date

The date you want the purge to end.

Process Tab

Proof or Final Mode

Blank = Proof Mode

1 = Final Mode

6.8 Working with Object Usage Tracking Composed EnterpriseOne Page

The Object Usage Tracking Composed EnterpriseOne Page (CMP_1701270001JDE) presents four charts for you to use to analyze Object Usage Tracking data.

Note:

The Object Usage Tracking Composed Page is available for JD Edwards EnterpriseOne Applications Release 9.2 and later releases.

See the JD Edwards EnterpriseOne Tools Security Administration Guide to secure UDOs to system administrators only.

Surrounding text describes obus.png.

Usage Count by (Tracking Type) Chart

Use this chart to view object usage for the specified path code. The chart is based the Object Usage Tracking Summary table (F98902).

Additionally, you can use the drop-down menu on the top of the chart to change the data that the system displays. You can select one of the these options:

  • Object

  • Object/Form/Version

  • Product Code

You can use the menu to further filter the data in the chart that the system displays.

The queries associated with the object Usage Tracking Summary table are all filtering on Tracking Unit 01. Any query you create for use with this composite page must be filtering on one of the three tracking units. Tracking Unit 01 provides the most detail.

Daily Peak Time Usage for (Date) Chart

Use this chart to view daily object usage by path code. The chart is based over the Object Usage Tracking Summary table (F98902). You can use the input date field in the chart's title to change the date of the data displayed in the chart.

You can also use the menu to further change the data displayed in the chart.

  • The Path Code field determines which path code totals display on the chart. If you select multiple path codes, a separate line for each path code displays on the chart. If you do not select a path code, totals from all path codes in the F98902 are displayed in separate lines on the chart by default.

  • The Tracking Type field determines the type of summary totals displayed on the chart. For example, object usage totals may only be summarized in the F98902 by product code, so you will need to select the Product Code option from this field to view the data in the chart.

Note:

If the Universal Time setting in User Preferences is populated, the usage totals displayed on the chart will be adjusted to the account for your time zone offset. This will correctly display the hourly totals according to your day. Otherwise, all hourly totals on the chart are displayed according to Coordinated Universal Time (UTC) regardless of your time zone.

Object Usage by Product Code

Use this chart to view object usage totals by Product Code for a specified number of days. The chart is based over the Object Usage Tracking Detail table (F98911) and can show object usage totals for the past seven days.

You can use the menu to further change what data displays in the chart.

  • The Path Code field determines which path code totals display on the chart. If you select multiple path codes, product code totals for all selected path codes are combined into a single bar for each date. If you do not select a path code, usage totals for all path codes in the F98911 display on the chart by default.

  • The Number of Days field determines the number of dates appearing on the chart. You can select between one to seven days in the past.

  • The Display Count field determines the number of individual product code totals displaying on the chart. If the chart data contains totals for more product codes than the number specified, the totals beyond this number are accumulated and displayed under an "Other" category.

Object Usage by Path Code

Use this chart to view object usage totals by path code for a specified number of days. The chart is based over the Object Usage Tracking Detail table (F98911) and can show object usage totals for the past seven days.

You can use the menu to further change the data displaying in the chart.

  • The Path Code field determines which path code totals display on the chart. If you select multiple path codes, a separate totals bar for each selected path code displays on each date. If do not select a path code, usage totals for all path codes in the F98911 display on the chart by default.

  • The Number of Days field determines the number of dates appearing on the chart. You can select between one to seven days in the past.

These charts are based on the Object Usage Tracking Detail and Summary tables. By default, the charts are set up to render using predefined queries found in the chart's menu drawer. You can modify the queries to better meet your requirements. Additionally, you can add filters in the menu of each chart to further restrict the chart's data. The filters provide selection capabilities based on the columns included in the primary table used by each chart. For example, with the Daily Peak Time Usage chart, you can display hourly totals for a single object by creating a filter to only retrieve data where the F98902 Summary ID (OTSUM) column equals the name of the object.

The shared queries are:

  • All Supported Types (QRY98902_1702010003JDE)

    Tracking Unit = 1

  • Applications (QRY98902_1701300005JDE)

    Tracking Unit = 01

    OMWOT = APPL

  • Applications and Reports (QRY98902_1701300008JDE)

    Tracking Unit = 01

    OMWOT = APPL or UBE

  • Reports (QRY98902_1701300006JDE)

    Tracking Unit = 01

    OMWOT = UBE

Note:

To limit irrelevant objects from appearing in the charts, you can add an exclude into the query, for example; SY not in (' ','H92','H95','H96U','H96B') and SYR not in (' ','00','UX'). This will limit some tools system codes that you may not want in your reporting.