Oracle Utilities Work and Asset Management and Operational Device Management

Administrative User Guide

Release 2.2.0

E69061-02

August 2017

Documentation build: 1.17.2018 8:38:40 [WAM2_1516196320000]

Copyright © 2012, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Framework Administrative User Guide

The topics in this section describe how to administer the Oracle Utilities Application Framework.

Next in This Section

- Defining General Options

- Defining Security & User Options

- User Interface Tools

- Database Tools

- Configuration Tools

- To Do Lists

- Background Processes

- Defining Algorithms

- Defining Script Options

- Mobile Application

- Attachments

- Application Viewer

- Reporting and Monitoring Tools

- External Messages

- Integrations

- Configuration Migration Assistant (CMA)

- Configuring Facts

- Cloud Service Foundation

Defining General Options

This section describes control tables that are used throughout your product.

Next in This Section

- Defining Installation Options

- Support For Different Languages

- Defining Countries

- Defining Currency Codes

- Defining Time Zones

- Defining Geographic Types

- Defining Work Calendar

- Defining Display Profiles

- Defining Phone Types

- Setting Up Characteristic Types & Values

- Setting Up Foreign Key Reference Information

- Defining Feature Configurations

- Defining Master Configurations

Defining Installation Options

The topics in this section describe the various installation options that control various aspects of the system.

Next in This Section

- Installation Options - Main

- Installation Options - Messages

- Installation Options - Algorithms

- Installation Options - Accessible Modules

- Installation Options - Installed Products

Installation Options - Main

Select Admin > General > Installation Options - Framework to define system wide installation options.

Description of Page

The Environment ID is a unique universal identifier of this instance of the system. When the system is installed, the environment id is populated with a six digit random number. While it is highly unlikely that multiple installs of the system at a given implementation would have the same environment ID, it is the obligation of the implementers to ensure that the environment ID is unique across all installed product environments.

System Owner will be Customer Modification.

The Admin Menu Order controls how the various control tables are grouped on Admin.

- If you choose Functional, each control table appears under a menu item that corresponds with its functional area. Note, the menu that is used when this option is chosen is the one identified with a menu type of Admin.

- If you choose Alphabetical, each control table appears under a menu item that corresponds with its first letter, using a Roman alphabet. For example, the Language control table will appear under the L menu item entry.

Note: The Alphabetical option only supports the Roman alphabet. For languages that do not use the Roman alphabet, the recommendation is to configure the system for the Functional setting.

CAUTION:

In order to improve response times, installation options are cached the first time they are used after a web server is started. If you change the Admin Menu Order and you don't want to wait for the cache to rebuild, you must clear the cached information so it will be immediately rebuilt using current information. Refer to Caching Overview for information on how to clear the system login cache (this is the cache in which installation options are stored).

The Language should be set to the primary language used by the installation. Note that if multiple languages are supported, each user may define their preferred language.

The Currency Code is the default currency code for transactions in the product.

If your product supports effective dated characteristics on any of its objects, define the date to be used as the Characteristic Default Date on objects without an implicit start date. The date you enter in this field will default when new characteristics are added to these objects (and the default date can be overridden by the user).

Active Owner displays the owner of newly added system data (system data is data like algorithm types, zones, To Do types, etc.). This will be Customer Modification unless you are working within a development region.

Country and Time Zone represent the default country and time zone that should be used throughout the application.

CAUTION:

In most implementations, the time zone defined here matches the database time zone. However, if there is some reason that the database time zone does not match the installation time zone, an implementation may configure a setting in the properties file to automatically convert data from the database time zone to the time zone defined here when displaying dates. Note that when this property setting is defined, changes to the installation time zone will require the server and the thread pool workers to be restarted in order for the changes to take effect.

Turn on Seasonal Time Shift if your company requires seasonal time shift information to be defined. Note that this is currently only applicable to Oracle Customer Care and Billing > Interval Billing functionality.

Installation Options - Messages

Select Admin > General > Installation Options - Framework and the Messages tab to review or enter messages that will appear throughout the application when a given event occurs.

The Message collection contains messages that are used in various parts of the system. For each message, define the Installation Message Type and Installation Message Text. The following table describes the Message Types provided by the framework product and how they are used in the system. Your specific product may have introduced addition message types.

Message Type

How The Message Is Used

Company Title for Reports

This message appears as a title line on the sample reports provided with the system. Generally it is your company name. It is only used if you have installed reporting functionality and are using the sample reports (or have designed your reports to use this message).

Installation Options - Algorithms

Select Admin > General > Installation Options - Framework and the Algorithms tab to review or enter the algorithms that should be evoked when a given event occurs.

The grid contains Algorithms that control important functions in the system. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

CAUTION:

These algorithms are typically significant processes. The absence of an algorithm might prevent the system from operating correctly.

The following table describes each System Event.

System Event

Optional / Required

Description

Validate Email Attachment

Optional

Algorithms of this type are used to validate the attachments for size and total count while sending attachments using the Email service. Refer to Sending Email for more information

Click here to see the algorithm types available for this system event.

Address Geocoding

Optional

Algorithms of this type use Oracle Locator to retrieve latitude and longitude coordinates using address information.

Click here to see the algorithm types available for this system event.

Global Context

Optional

Algorithms of this type are called whenever the value of one of the global context fields is changed. Algorithms of this type are responsible for populating other global context values based on the new value of the field that was changed.

Refer to Global Context Overview for more information.

Click here to see the algorithm types available for this system event.

Guaranteed Delivery

Optional

Algorithms of this type may be called by processes that receive incoming messages that should ‘guarantee delivery’. Refer to Guaranteed Delivery for more information. The business service F1-GuaranteedDelivery may be used to invoke this plug-in spot.

Click here to see the algorithm types available for this system event.

Ldap Import

Optional

Algorithms of this type are called for operations on users, groups, and group memberships after they have been processed.

Click here to see the algorithm types available for this system event.

Ldap Import Preprocess

Optional

Algorithms of this type are called to preprocess data retrieved from LDAP.

Click here to see the algorithm types available for this system event.

Next To Do Assignment

Optional

This type of algorithm is used to find the next To Do entry a user should work on. It is called from the Current To Do dashboard zone when the user ask for the next assignment.

Click here to see the algorithm types available for this system event.

Reporting Tool

Optional

If your installation has integrated with a third party reporting tool, you may wish to allow your users to submit reports on-line using report submission or to review report history online. This algorithm is used by the two on-line reporting pages to properly invoke the reporting tool from within the system.

Click here to see the algorithm types available for this system event.

SMS Receive

Optional

This type of algorithm is used to provide SMS receive service. Only one algorithm of this type should be plugged in.

Click here to see the algorithm types available for this system event.

SMS Send

Optional

This type of algorithm is used to provide SMS send service. If your installation uses the base algorithm that uses BPEL, you will need to create a feature configuration with the SMS Send Configuration feature type to define your Oracle BPEL server and service call details. If your installation has integrated with a third-party SMS service, you may want to override this algorithm type with your own implementation. Only one algorithm of this type should be plugged in.

Click here to see the algorithm types available for this system event.

To Do Information

Optional

We use the term To Do information to describe the basic information that appears throughout the system to describe a To Do entry.

Plug an algorithm into this spot to override the system default "To Do information".

Click here to see the algorithm types available for this system event.

To Do Pre-creation

Optional

These types of algorithms are called when a To Do entry is being added.

Click here to see the algorithm types available for this system event.

Installation Options - Accessible Modules

Select Admin > General > Installation Options - Framework and the Accessible Modules tab to view the list of accessible modules.

Description of Page

This page displays the full list of the application's function modules. A Turned Off indication appears adjacent to a module that is not accessible based on your system's module configuration setup.

Fastpath: Refer to Module Configuration for more information on function modules and how to turn off modules that are not applicable to your organization.

Installation Options - Installed Products

Select Admin > General > Installation Options - Framework and the Installed Products tab to view a read only summary of the products that are installed in the application version that you are logged into.

Description of Page

The Product Name indicates the name of the "products" that are installed. The collection should include Framework, an entry for your specific product and an entry for Customer Release.

Release ID shows the current release of the application that is installed. This field is used by the system to ensure that the software that executes on your application server is consistent with the release level of the database. If your implementation of the product has developed implementation-specific transactions, you can populate the Release Id for the Customer Release entry to define the latest release of implementation-specific logic that has been applied to this environment. In order for this to work, your implementation team should populate this field as part of their upgrade scripts.

The Release ID Suffix, Build Number and Patch Number further describe the details of your specific product release.

The Display column indicates the product whose name and release information should be displayed in the title bar. Only one product sets this value to Yes.

Owner indicates if this entry is owned by the base package or by your implementation (Customer Modification).

Product Type indicates if the product is a Parallel Application. A parallel application is one that is independent of, and does not conflict with, other parallel applications. Multiple parallel applications can be installed in the same database and application server.

Note: About Information. The information on this tab is used to populate the information displayed in the About information for your product.

Support For Different Languages

Next in This Section

- User Language

- Customer Language

- Defining Languages

User Language

The system provides support for multiple languages in a single environment. System users can use the system in their preferred language, as long as a translation into that language has been provided. A user sees the system in the language defined on their user record. If enabled, users can use the Switch Language zone to switch to another supported language real time.

Note: Normally, setting up the system for another language is an implementation issue, not an administrative setup issue. However, there are several online administrative features that are used to set up a new language, and these are described here.

The following steps are required to support a new language:

1. Define a language code and indicate that it is enabled. For details on this procedure, see Defining Languages.

2. Copy descriptions of all language-enabled tables from an existing translation (e.g., English). The copied values act merely as placeholders while the strings are translated into the new language. It is necessary to do this as a first step in order to create records using the new language code created in the previous step. Language-based descriptions can be copied using a supplied batch process, F1–LANG. The batch copies all English labels in the system.

3. Apply the language pack. If the product supplies a language pack with translations for the system metadata descriptions, follow the instructions provided with the language pack to add the translated text.

4. Translate additional content. Translatable descriptions and labels for implementation data may be updated / entered in the application. First the user record must be updated to reference the new language. This may be done in one of the following ways:

1. Switch to the new language using the Switch Language zone.

2. If that zone is not available, navigate to the user page, assign the new language code to your User ID, sign out, and sign back in again.

Any online functions that you access will use your new language code. You can change the language code for all users who plan to use/modify the new language.

Note: The language pack updates all language entries for base owned system data. If your implementation updates base owned labels and descriptions prior to applying the language pack, they will be overwritten. Note that most user facing labels and messages support defining an Override Label or Override Description. This information is not updated by the base product and should be utilized if your implementation desires a specific label or description.

Customer Language

Your specific product may also support capturing the language of a customer. Such that correspondence sent from the product may be produced in a language set on a customer record. Refer to your specific product’s documentation for more information about additional language support.

Defining Languages

Your product may support multiple languages. For example, the field labels, input text, and even outputs and reports can be configured to appear in a localized language. A language code for every potential language exists in the system to supply this information in various languages.

Select Admin > General > Language to define a language.

Description of Page

Enter a unique Language Code. If you are applying a language pack provided by the product, use the language code designed by the language pack.

Enter the Description for the language. Typically this should be the name of the language in that language.

Turn on Language Enable if the system should add a row for this language whenever a row is added in another language. For example, if you add a new currency code, the system will create language specific record for each language that has been enabled. You would only enable multiple languages if you have users who work in multiple languages. Languages that are configured as enabled, appear in the Switch Language dashboard zone. In addition, the login page for the application displays all the languages that are enabled, allowing the user to toggle the login instructions in that language.

Note: The list of enabled languages is captured on the server at startup time. If a new language is enabled, contact your server administrator to refresh the server in order to see the new language displayed in the login page.

The following two fields control how the contents of grids and search results are sorted by the Java virtual machine (JVM) on your web server:

- The Locale is a string containing three portions:

- ISO language code (lower case, required)

- ISO country code (upper case, optional)

- Variant (optional).

- Underscores separate the various portions, and the variant can include further underscores to designate multiple variants. The specific JVM in use by your particular hardware/OS configuration constrains the available Locales. Validating the Locale against the JVM is outside the scope of this transaction. This means you are responsible for choosing valid Locales.

The following are examples of valid locales:

Locale

Comments

en_US

American English

en_AU

Australian English

pt_BR

Brazilian Portuguese

fr_FR_EURO

European French

ja_JP

Japanese

In addition, the Java collation API can take a Collator Strength parameter. This parameter controls whether, for example, upper and lower-case characters are considered equivalent, or how accented characters are sorted. Valid values for collator strength are PRIMARY, SECONDARY, TERTIARY, and IDENTICAL. If you leave this field blank, Java will use its default value for the language. We'd like to stress that the impact of each value depends on the language.

Please see https://docs.oracle.com/javase/7/docs/api/java/text/Collator.html for more information about the collator strength for your language.

Display Order indicates if this language is written Left to Right or Right to Left.

Owner indicates if this language is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a language. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_LANGUAGE.

Note that all administrative control tables and system metadata that contain language-specific columns (e.g., a description) reference a language code.

In addition, other tables may reference the language as a specific column. For example, on the User record you indicate the preferred language of the user.

Defining Countries

The topics in this section describe how to maintain countries.

Next in This Section

- Country - Main

- Country - States

Country - Main

To add or review Country definitions choose Admin > General > Country.

The Main page is used to customize the fields and field descriptions that will be displayed everywhere addresses are used in the system. This ensures that the all addresses conform to the customary address format and conventions of the particular country you have defined.

Description of Page

Enter a unique Country and Description for the country.

The address fields that appear in the Main page are localization options that are used to customize address formats so that they conform to address requirements around the world. By turning on an address field, you make that field available everywhere addresses for this country are used in the system. You can enter your own descriptions for the labels that suffix each switch; these labels will appear wherever addresses are maintained in the system.

Note: For any country where the State switch is checked, the valid states for the country must be entered on the Country - State tab. When entering address constituents on a record that captures this detail, the value for State is verified against the data in the State table. For any country where there is a component of the address that represents a "state" but your implementation does not want to populate the valid states for that country, choose a different field such as County for this constituent (and define an appropriate label). When entering address constituents on a record that captures this detail, no validation is done for the County column.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_COUNTRY.

Country - States

To maintain the states located in a country, choose Admin > Country > Search and navigate to the State page.

Description of Page

For any country where you have enabled the State switch, use the State collection to define the valid states in the Country.

- Enter the standard postal abbreviation for the State or province.

- Enter a Description for this state or province.

Defining Currency Codes

The currency page allows you to define display options related to currency codes that are used by your system. Use Admin > General > Currency to define the currency codes in which financial information is denominated.

Description of Page

Enter a unique Currency and Description for the currency.

Use Currency Symbol to define the character that prefixes currency amounts in the system (e.g., $ for U.S. dollars).

Enter the number of Decimals that will appear in the notation for the currency.

Note: Please contact your specific product to verify whether it supports a currency with more than 2 decimals.

The Currency Position indicates whether the currency symbol should be displayed as a Prefix or a Suffix to the currency amount.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_CURRENCY_CD.

Defining Time Zones

The following topics describe how to design and set up time zones.

Next in This Section

- Designing Time Zones

- Setting Up Time Zones

- Setting Up Seasonal Time Shift

Designing Time Zones

Note: Oracle Utilities Customer Care and Billing - Interval Billing applications customers should consult the topic Time Issues (search the Help index for "time issues") for specific information relating to that product's interval billing time related functionality.

It is recommended that all time sensitive data is stored in the standard time (also called 'physical time') of the base time zone as defined on the installation options. This will prevent any confusion when analyzing data and will ensure that your algorithms do not have to perform any shifting of data that may be stored in different time zones.

The Time Zone entity is used to define all the time zones where your customers may operate. Each time zone should define an appropriate Time Zone Name. This is a reference to an external source that defines time zones, their relationship to Greenwich Mean Time, whether the time zone follows any shifting for summer / winter time (daylight savings time) and when this shift occurs.

When designing your time zones, the first thing to determine is the base time zone. You may choose the time zone where the company's main office resides. Once this is done you can link the time zone code to the installation option as the base time zone. Refer to Installation Options - Main for more information.

Note: An attribute in the system properties file may be configured to indicate that the DB session time zone should be synchronized with the value defined on the Installation Options. Refer to the Server Administration Guide for more information.

If your company does business beyond your main office's time zone, define the other time zones where you may have customers or other systems with which you exchange data. At this point, your specific product may include configuration tables to capture default time zones, for example based on a postal code or geographic location.

Note: Date and time in business object schemas. When defining date / time fields in a BO schema, schema attributes can be used to define whether or not data should be stored in standard time for the base time zone or if it should be stored in the standard time of another time zone (related to the data). In addition, schema attributes can be used to indicate if the display of the time should be shifted to represent the "local time". This is used to adjust for seasonal time differences. For example, if the data is stored in the appropriate time zone, but currently daylight savings time is being observed, the data will be shifted and shown in the "local" time. In addition, if the data is stored in the base time zone but the data is related to a different time zone, the data will be shown in the time zone appropriate for the data (including the appropriate seasonal adjustment). Refer to Schema Nodes and Attributes- Standard Time Considerations for more information.

Setting Up Time Zones

Refer to Designing Time Zones for background information about defining time zones.

Open Admin > General > Time Zone > Search to define the time zones and their relation to the base time.

Description of Page

Enter a unique Time Zone and Description for the time zone.

Select the Time Zone Name from the list of Olson time zone values. This value is a reference to an external definition that allows the system to know how the time zone relates to Greenwich Mean Time and information about whether the time zone shifts for summer / winter time and when.

Indicate the Shift in Minutes that this time zone differs from the base time zone defined on the Installation Options. This is only applicable for the Oracle Utility Customer Care and Billing - Interval Billing application.

Indicate the Seasonal Time Shift applicable for this time zone. This is only applicable for the Oracle Utility Customer Care and Billing - Interval Billing application.

Default Time Zone Label and Shifted Time Zone Label are used for data that is sensitive to time zones and time shifting. It indicates whether the data displayed or data to be input is related to the "standard" time or the "shifted" time. For example, on a day when clocks are turned back one hour, a time entry of 1:30 a.m. needs to be labeled as either 1:30 a.m. standard time or 1:30 a.m. daylight savings time.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_TIME_ZONE.

Setting Up Seasonal Time Shift

Note: The information in this topic applies only to Oracle Utilities Customer Care and Billing - Interval Billing applications.

Open Admin > General > Seasonal Time Shift > Search to define the seasonal time shift schedule.

Description of Page

Enter a unique Seasonal Time Shift code and Description for the seasonal time shift.

The Collection defines the Effective Date/Time (in standard time) that a time zone may shift in and out of standard time. If time is changed from standard time on the effective date/time, enter the Shift in Minutes that the time changes from standard time (usually 60). If the time is changed back to standard time on the effective date/time, enter a Shift in Minutes of 0.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_SEAS_TM_SHIFT.

Defining Geographic Types

If your company uses geographic coordinates for dispatching or geographic information system integration, you need to setup a geographic (coordinate) type for each type of geographic coordinate you capture on your premises and/or service points (geographic coordinates can be defined on both premises and service points).

To define geographic types, open Admin > Geographic > Geographic Type.

Note: Product specific. There is no framework functionality that uses this information. Refer to your specific product documentation to verify how this table is used in your specific product. In addition, use the data dictionary link below to determine if this object is a foreign key on any tables specific to your product.

Description of Page

Enter an easily recognizable Geographic Type code and Description.

Define the algorithm used to validate the Validation Format Algorithm. If an algorithm is specified, the system will validate that the geographic location entered on the premise and/or service point for the geographic type is in the format as defined in the algorithm. If you require validation, you must set up this algorithm in the system.

Click here to see the algorithm types available for this plug-in spot.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_GEO_TYPE.

Defining Work Calendar

Workday calendars are used to ensure system-calculated dates fall on a workday. Select Admin > General > Work Calendar > Search to define a workday calendar.

Description of Page

The information on this transaction is used to define the days of the week on which your organization works.

Enter a unique Work Calendar and Description.

Turn on (check) the days of the week that are considered normal business days for your organization.

Use the collection to define the Holiday Date, Holiday Start Date, Holiday End Date, and Holiday Name for each company holiday. Holiday Start Date and Holiday End Date define the date and time that the holiday begins and ends. For example, your organization might begin a holiday at 5:00 p.m. on the day before the actual holiday.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_CAL_WORK.

Defining Display Profiles

When you set up your users, you reference a display profile. A user's display profile controls how dates, times, and numbers displayed. Choose Admin > General > Display Profile > Search to maintain display profiles.

Description of Page

Enter a unique Display Profile ID and Description to identify the profile.

Enter a Date Format. This affects how users view dates and how entered dates are parsed. The following table highlights standard supported date mnemonics and what is displayed at runtime.

Mnemonic

Comments

dd

Day of the month.

d

Day of the month, suppressing the leading 0.

MM

Month number.

M

Month number, suppressing the leading 0.

yyyy

The 4-digit year.

yy

The 2-digit year.

y

Allows entry in either 2 or 4-digit form and is displayed in 2-digit form.

Other characters are displayed as entered. Typically, these other characters should be separators, such as "-", ".", or "/". Separators are optional; a blank space cannot be use.

Examples:

Configuration Format

Sample Output

MM-dd-yyyy

04-09-2001

d/M/yyyy

9/4/2001

yy.MM.dd

01.04.09

MM-dd-y

04-09-01 - In this case you could also enter the date as 04-09-2001

Note: For centuries, the default pivot for 2-digit years is 80. Entry of a 2-digit year greater than or equal to 80 results in the year being interpreted as 19xx. Entry of a 2-digit year less than 80 results in the year being interpreted as 20xx.

In addition, the following date localization functionality is supported. Note that in every case, the date is stored in the database using the Gregorian format. The settings below result in a conversion of the date for the user interface.

- Hijri Dates

Entering iiii for the year is interpreted as a year entered and displayed in Hijri format. For example, the Gregorian date 2014–05–30 may be entered / displayed as 1435/07/30 for a user whose display profile date format is iiii/MM/dd. Note that this functionality relies on date mapping to be defined in the Hijri to Gregorian Date Mapping master configuration. entry. Refer to Additional Hijri Date Configuration for more information.

- Taiwanese Dates

Entering tttt for the year is interpreted as a year entered and displayed in Taiwanese format where year 1911 is considered year 0000. For example, if the Gregorian date is 01-01-2005, it is displayed as 01-01-0094 for a user whose display profile date format is dd-mm-tttt.

- Japanese Dates

There are two options available for configuring Japanese Era date support. The setting Gyy for the year is interpreted as a year entered and displayed using an English character for the era followed by the era number. The letter ‘T’ is used for dates that fall within the Taisho era. The letter ‘S’ is used for dates that fall within the Showa era and the letter ‘H’ is used for dates that fall within the Heisei era. For example, for a user whose display profile date format is Gyy/mm/dd the Gregorian date 2008/01/01 is shown as H20/01/01; the Gregorian date 1986/03/15 is shown as S61/03/15. The setting GGGGyy is interpreted as a year entered and displayed using Japanese characters for the era followed by the era number.

Japanese date limitations are as follows:

- The years 1912 through the current date are supported.

- Any functionality that displays Month and Year does not support Japanese Era dates. These dates are shown in Gregorian format.

- Graphs that display dates do not support the GGGGyy format.

Enter a Time Format. The following table highlights standard supported date mnemonics.

Mnemonic

Comments

hh

The hour 1-12.

h

The hour 1-12, suppressing the leading 0.

HH

The hour 0-23.

H

The hour 0-23, suppressing the leading 0.

KK

The hour 0-11.

K

The hour 0-11, suppressing the leading 0.

kk

The hour 1-24.

k

The hour 1-24, suppressing the leading 0.

mm

Minutes.

m

Minutes, suppressing the leading 0.

ss

Seconds.

s

Seconds, suppressing the leading 0.

a

Indicates to include am or pm. This is only needed for 12 hour formats, not 24 hour formats. (hh, h, KK, K). If an am or pm is not entered, it defaults to am.

Examples:

Configuration Format

Sample Output

hh:mma

09:34PM (can be entered as 09:34p)

hh:mm:ss

21:34:00

h:m:s

9:34:0

There are several options for displaying Numbers.

Decimal Symbol defines the separator between the integer and decimal parts of a number. Valid values are "." (a period) or "," (a comma).

Group Symbol defines the means to separate groups of bigger numbers. Valid values are as follows:

- A comma (","). Large numbers group by threes separated by a comma, for example 1,000,000.

- A period ("."). Large numbers group by threes separated by a period, for example 1.000.000.

- None. Large numbers do not have any separator, for example 1000000.

- South Asian. This option uses a comma for its separator but will group large numbers as follows: the first comma is used for the thousands separation and numbers over 9,999 are grouped with 2 units, for example 10,00,000.

- Space. Large numbers group by threes separated by a space, for example 1 000 000.

Negative Format defines how negative values are displayed. Valid values are -9.9, (9.9), or 9.9-.

Currency values can have a different Negative Format from other numbers. Valid values are -S9.9, (S9.9), or S9.9-, where the "S" represents the currency symbol.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_DISP_PROF.

Next in This Section

- Additional Hijri Date Configuration

Additional Hijri Date Configuration

For implementations that wish to support displaying dates according to the Hijri calendar, besides appropriate configuration in the Display Profile, the mapping between the Hijri dates and the Gregorian dates must be entered. This mapping is defined in the Hijri to Gregorian Date Mapping master configuration record.

The mapping record contains a collection of entries for each year in the Islamic calendar.

For each year, clicking the Expand Zone icon shows the mapping collection with the first date of each month of the Hijri calendar. The corresponding date in the Gregorian calendar should be entered for each row.

Defining Phone Types

Phone types define the format for entering and displaying phone numbers.

To add or review phone types, choose Admin > General > Phone Type.

Description of Page

Enter a unique Phone Type and Description for each type of phone number you support.

Select an appropriate Phone Number Format Algorithm for each Phone Type. This algorithm controls the format for entry and display of phone numbers. Click here to see the algorithm types available for this plug-in spot.

Use Phone Type Flag to define if this type of phone number is a Fax number. Defining which phone type is used for facsimile transmittal is only pertinent if your product supports routing of information via fax. For example, in Oracle Utilities Customer Care and Billing, the system may be configured to fax a bill to a customer.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_PHONE_TYPE.

Setting Up Characteristic Types & Values

Many objects in the system support a collection of Characteristics, which are used to capture additional fields for the object that are not already supported by the object’s provided attributes. Each characteristic is associated with a characteristic type, which defines attributes of the field you wish to capture.

All characteristics are captured as a list. However, the user interface for characteristics differ based on the type of page that is used to maintain the object.

- For portal based pages the business object drives the display and maintenance of an object. For these types of pages, it is recommended that characteristics are defined as part of the business object schema allowing the user interface to display the characteristic as if it is another field. However, the display / maintenance of the characteristic is determined by the business object’s user interface design.

- There are some fixed pages in the system that do not support customization of the user interface. For these objects, the characteristics are displayed / maintained as a generic list.

The topics in this section describe how to setup a characteristic type.

Next in This Section

- There Are Four Types Of Characteristics

- Searching By Characteristic Values

- Characteristic Type - Main

- Characteristic Type - Characteristic Entities

There Are Four Types Of Characteristics

Every characteristic referenced on an object references a characteristic type. The characteristic type controls the validity of the information entered by a user when they enter the characteristic's values. For example, if you have a characteristic type on user called "skills", the information you setup on this characteristic type controls the valid values that may be specified by a user when defining another user's skills.

When you setup a characteristic type, you must classify it as one of the following categories:

- Predefined value. When you setup a characteristic of this type, you define the individual valid values that may be entered by a user. A good example of such a characteristic type would be one on User to define one or more predefined skills for that user. The valid values for this characteristic type would be defined in a discreet list.

- Ad hoc value. Characteristics of this type do not have their valid values defined in a discreet list because the possible values are infinite. Good examples of such a characteristic type would be ones used to define a user's birth date or their mother's maiden name. Optionally, you can plug-in an algorithm on such a characteristic type to validate the value entered by the user. For example, you can plug-in an algorithm on a characteristic type to ensure the value entered is a date.

- Foreign key value. Characteristics of this type have their valid values defined in another table. For example perhaps you want to link a user to a table where User is not already a foreign key. Valid values for this type of characteristic would be defined on the user table. Please be aware of the following in respect of characteristics of this type:

- Before you can create a characteristic of this type, information about the table that contains the valid values must be defined on the foreign key reference table.

- The referenced table does not have to be a table within the system.

- Not all entities that support characteristics support foreign key characteristics. Refer to the data dictionary to identify the entities that include the foreign key characteristic columns.

- As described in Search Options, there are two different searching metaphors supported on FK reference. If the object that a characteristic is being linked to is defined on a fixed page, it will display a search icon if the characteristic type's FK reference defines a navigation key based search. If the object is maintained on a portal based page, it will display a search icon if the characteristic type's FK reference defines a search zone.

- File Location. Characteristics of this type contain a URL. The URL can point to a file or any web site. Characteristics of this type might be useful to hold references to documentation / images associated with a given entity. For example, the image of a letter sent to you by one of your customers could be referenced as a file location characteristic on a customer contact entry. When such a characteristic is defined on an entity, a button can be used to open the URL in a separate browser window.

File location characteristic values must be entered in a "non-relative" format. For example, if you want to define a characteristic value of www.msn.com, enter the characteristic value as http://www.msn.com. If you omit the http:// prefix, the system will suffix the characteristic value to the current URL in your browser and attempt to navigate to this location when the launch button is pressed. This may or may not be the desired result.

Note:

Due to browser security restrictions, opening URLs using the file protocol ("file://") from pages retrieved using http does not work. If the file protocol is used, the browser either does not return properly or an error is thrown (e.g., "Access Denied", which usually results from cross site scripting features added for security reasons). This issue has no known workaround. To comply with browser security standards, the recommendation is to move the target files to an FTP or HTTP server location to avoid protocols that are subject to browser security restrictions.

Also note that the functionality described in the topics for Referencing URIs do not apply to this value given that the browser is responsible for connecting to the URI and does not go via server logic.

For references to a file, the recommendation is to use the Attachment functionality to link a file to an object rather than a characteristic type of File Location. Refer to Attachment Overview for more information. The documentation related to file location remains for upgrade purposes.

Searching By Characteristic Values

For certain entities in the system that have characteristics, you may search for a record linked to a given characteristic value. The search may be done in one of the following ways:

- Some base searches provide an option to search for an object by entering Characteristic Type and Characteristic Value.

- Your implementation may define a customized search for an entity by a characteristic value for a specific characteristic type using a query data explorer.

- Your implementation may require a business service to find a record via a given characteristic value. For example, maybe an upload of user information attempts to find the user via an Employee ID, defined as a characteristic.

Not all entities that support characteristics support searching by characteristics. Refer to the data dictionary to identify the characteristic collections that include the search characteristic column.

CAUTION:

For ad-hoc characteristics, only the first 50 bytes are searchable. For foreign key characteristics, the search value is populated by concatenating the values of each foreign key column to a maximum of 50 bytes.

For the base searches that provide a generic option to search by characteristic type and value, you can restrict the characteristic types that can be used to search for an entity. For example, imagine you use a characteristic to define a "jurisdiction" associated with a To Do for reporting purposes. If your company operates within a very small number of jurisdictions, you wouldn't want to allow searching for a To Do by jurisdiction, as a large number of To Do entries would be returned.

A flag on the characteristic type allows an administrator to indicate if searching by this characteristic type is allowed or not allowed.

Characteristic Type - Main

To define a characteristic type, open Admin > General > Characteristic Type.

Description of Page

Enter an easily recognizable Characteristic Type and Description for the characteristic type. Owner indicates if this characteristic type is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new characteristic type, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Use Type of Char Value to classify this characteristic type using one of the following options (refer to There Are Four Types Of Characteristics for more information):

- Predefined value. Characteristics of this type have their valid values defined in the Characteristic Value scroll, below. For each valid value, enter an easily recognizable Characteristic Value and Description.

- Ad hoc value. Characteristics of this type capture free form text. If you use this option, you can optionally define the Validation Rule used to validate the user-entered characteristic value. Click here to see the algorithm types available for this plug-in spot.

- File location value. Characteristics of this type contain a URI. The URI can point to a file or any web site. Refer to There Are Four Types Of Characteristics for limitations associated with this type of characteristic value.

- Foreign key reference. Characteristics of this type have their valid values defined in another table. If you choose this option, you must use FK Reference to define the table that controls the valid values of this characteristic type. Refer to Setting Up Foreign Key References for more information.

Use the Allow Search by Char Val to indicate if searching for an entity by this characteristic type is Allowed or Not Allowed. Refer to Searching by Characteristic Values for more information.

The Custom switch is only applicable to Predefined value types. It indicates whether or not an implementation is allowed to add values for a characteristic type whose owner is not Customer Modification

- If this switch is turned on, an implementation may add characteristic values to the grid for system owned characteristic types.

- If this switch is turned off, an implementation may not add characteristic values to the grid for system owned characteristic types.

Note: Regardless of the value of the Custom switch, an implementation may not update or remove system owned characteristic values.

The Characteristic Value grid defines the valid values for a Predefined value type of characteristic.

The Characteristic Value is the unique identifier of the value.

Description is the text that is visible in the dropdowns and display when viewing this characteristic value.

Owner indicates if this characteristic value is owned by the system or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add characteristic values to a characteristic type. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_CHAR_TYPE in the data dictionary schema viewer.

Characteristic Type - Characteristic Entities

To define the entities (objects) on which a given characteristic type can be defined, open Admin > General > Characteristic Type and navigate to the Characteristic Entities tab.

Description of Page

Use the Characteristic Entity collection to define the entities on which the characteristic type can be used. Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

Note: The values for this field are customizable using the Lookup table. This field name is CHAR_ENTITY_FLG.

Note: For some entities in the system, the valid characteristics for a record are defined on a related "type" entity. For example, the To Do type defines valid characteristics for manually created To Do entries of that type. When configuring your system, in addition to defining the appropriate entity for a characteristic type, you may also need to link the characteristic type to an appropriate entity "type". This technique is typically not followed for business object driven maintenance objects, where the business objects can be configured with the appropriate “flattened” characteristic types in the schema.

Setting Up Foreign Key Reference Information

A Foreign Key Reference defines the necessary information needed to reference an entity in certain table.

You need to set up this control table if you need to validate a foreign key value against a corresponding table. For example, if a schema element is associated with an FK Reference the system validates the element's value against the corresponding table. Refer to Configuration Tools to learn more about schema-based objects. Another example is characteristics whose valid values are defined in another table (i.e., you use "foreign key reference" characteristic types). Refer to There Are Four Types Of Characteristics for a description of characteristics of this type.

A FK Reference is used not just for validation purposes. It also used to display the standard information description of the reference entity as well as provide navigation information to its maintenance transaction. Info descriptions appear throughout the UI, for example, whenever an account is displayed on a page, a description of the account appears. The product provides base product FK references for many of its entities as they are used for validation and display of elements in both fixed page user interfaces as well as portal based user interfaces.

An implementation may also see the need to define a foreign key reference. The following points describe what you should know before you can setup a foreign key reference for a table.

- The physical name of the table. Typically this is the primary table of a maintenance object.

- The program used by default to construct the referenced entity's info description. Refer to Information Description Is Dynamically Derived for more information on how this is used.

- The transaction used to maintain the referenced entity. This is where the user navigates to when using the "go to" button or hyperlink associated with the entity. Refer to Navigation Information Is Dynamically Derived for more information on how this is used.

- The name of the search page used to look for a valid entity. Refer to Search Options for more information.

Next in This Section

- Information Description Is Dynamically Derived

- Navigation Information Is Dynamically Derived

- Search Options

- Foreign Key Reference - Main

Information Description Is Dynamically Derived

Typically a FK Reference is defined for a maintenance object's primary table. In this case the system dynamically derives the standard information associated with a specific referenced entity as follows:

- Attempt to determine the business object associated with the referenced entity. Refer to the Determine BO maintenance object algorithm system event for more information. If a business object has been determined, the system lets the business object's Information plug-in, if any, format the description.

- If a business object has not been determined or the business object has no such plug-in, the system lets the maintenance object's information plug-in, if any, format the description.

- If the maintenance object has no such plug-in, the system uses the info program specified on the FK Reference to format the information.

Note: Technical note. The class that returns the information displayed adjacent to the referenced entity is generated specifically for use as an info routine. Please speak to your support group if you need to generate such a class.

Note: Generic routine. The system provides a generic information routine that returns the description of control table objects from its associated language table. By "control table" we mean a table with an associated language table that contains a DESCR field. Refer to Defining Table Options for more information on tables and fields. The java class is com.splwg.base.domain.common.foreignKeyReference.DescriptionRetriever.

Navigation Information Is Dynamically Derived

Typically a FK Reference is defined for a maintenance object's primary table. In this case the system dynamically derives the actual transaction to navigate to for a given referenced entity as follows:

- Attempt to determine the business object associated with the referenced entity. Refer to the Determine BO maintenance object algorithm system event for more information. If a business object has been determined, use the maintenance portal defined as its Portal Navigation Option business object option.

- If a business object has not been determined or the business object defines no such option, the system uses the transaction specified on the FK Reference.

Search Options

The product provides two main metaphors for implementing a user interface. For input fields that are foreign keys, search options are dependent on the metaphor used by the page in question.

- A portal based user interface is a more flexible user interface where an implementation has more options for customizing the look and feel. The base product uses UI maps or automatic UI rendering to display input fields. Elements that are foreign keys may display a search icon if the FK reference defines a Search Zone.
Note: Defining search zones directly. It's possible for elements on a UI map to define a specific search zone directly in the HTML, rather than using the search zone defined on an FK reference. Refer to the UI map tips for more information on implementing searches using zones.

- A fixed maintenance page user interface is a page supplied by the base product where only minor enhancements, if any, can be introduced by implementations. The foreign key reference may be used in one of two ways.

- The based product may use an FK reference to define a base element on one of these pages. If a search is available for such elements, the FK reference's Search Navigation Key is used to implement the search.

- Entities that support characteristics typically include a generic characteristic collection UI metaphor on these types of pages. In this metaphor, a foreign key characteristic displays a search icon if the FK Reference has configured a Search Navigation Key.

Note: Not every FK reference provided with the product is configured with both search options. Specifically, objects that are maintained in a portal based page typically do not provide a navigation key based search. It means that if linking this type of object as a characteristic to an object that is maintained on a fixed page, a search will not be available.

Foreign Key Reference - Main

To setup a foreign key reference, open Admin > Database > FK Reference.

CAUTION:

Important! If you introduce a new foreign key reference, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Description of Page

Enter an easily recognizable FK (foreign key) Reference code and Description for the record.

Enter the name of the Table whose primary key is referenced. After selecting a Table, the columns in the table's primary key are displayed adjacent to Table PK Sequence.

Use Navigation Option to define the page to which the user will be transferred when they press the go to button or hyperlink associated with the referenced entity. Refer to Navigation Information Is Dynamically Derived for more information on how this is used.

The Info Program Type indicates whether the default program that returns the standard information description is Java or Java (Converted), meaning it was converted into Java.

Note: Java (Converted) program types are not applicable to all products.

Use Info Program Name to enter the Java class / program name.

Refer to Information Description Is Dynamically Derived for more information on the info program is used.

Note: View the source. If the program is shipped with the base package, you can use the adjacent button to display the source code of this program in the Java docs viewer.

Use Context Menu Name to specify the context menu that appears to the left of the value.

Note: Context Menu Name is not applicable to user interface elements displaying a generic collection using a foreign key characteristic type. It is only applicable for pages utilizing the foreign key compound element type for fixed page user interface and for data displayed in a portal based user interface where the foreign key reference is defined as an attribute for an element. Report parameters that reference foreign key characteristics are an example of a user interface where a context menu is not displayed even if the foreign key reference defines one.

Use Search Zone to define the search zone that opens when a user searches for valid values when the foreign key reference is configured as an input field on a portal based page. Refer to Search Options for more information.

Use Search Navigation Key to define the search page that will be opened when a user searches for valid values on a user interface that is a fixed page. Refer to Search Options for more information.

Use Search Type to define the default set of search criteria used by the Search Navigation Key's search page.

Use Search Tooltip to define a label that describes the Search Navigation Key's search page.

Note: Search Type and Search Tooltip. These attributes are only applicable to user interface elements utilizing the foreign key compound element type on fixed page user interfaces. Report parameters that reference foreign key characteristics are an example of a user interface where this information is not used even if the foreign key reference defines them.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_FK_REF.

Defining Feature Configurations

Some system features are configured by populating options on a "feature configuration". Because various options throughout the system may be controlled by settings in feature configuration, this section does not document all the disparate possible options. The topics below simply describe how to use this transaction in a generic way.

For information about specific features:

- Refer to the detailed description of each option type.

- Use the index in the online help and search for ‘feature configuration’ to find any specific topics describing feature options in the administration guide.

You can create options to control features that you develop for your implementation. To do this:

- Review the lookup values for the lookup field EXT_SYS_TYP_FLG. If your new option can be logically categorized within an existing feature type, note the lookup value. If your new option warrants a new feature type, add a lookup value to this lookup field.

- Define the feature's option types. If you have identified an existing feature type to add the options to, find the lookup with the name xxxx_OPT_TYP_FLG where xxxx is the lookup value of EXT_SYS_TYP_FLG noted above. If you decided to create a new feature type (by adding a new lookup value to the EXT_SYS_TYP_FLG lookup, you must create a new lookup with the name xxxx_OPT_TYP_FLG where xxxx is the new value you defined above.

- Flush all caches.

Next in This Section

- Feature Configuration - Main

- Feature Configuration - Messages

Feature Configuration - Main

To define your feature configuration, open Admin > General > Feature Configuration.

Description of Page

Enter an easily recognizable Feature Name code.

Indicate the Feature Type for this configuration. For example, if you were setting up the options for the external messages, you'd select External Messages.

Note: You can add new Feature Types. Refer to the description of the page above for how you can add Feature Types to control features developed for your implementation.

Note: Multiple Feature Configurations for a Feature Type. Some Feature Types allow multiple feature configurations. The administration documentation for each feature will tell you when this is possible.

The Options grid allows you to configure the feature. To do this, select the Option Type and define its Value. Set the Sequence to 1 unless the option may have more than value. Detailed Description may display additional information on the option type.

Note: Each option is documented elsewhere. The administration documentation for each feature describes its options and whether an option supports multiple values. Use the index to look for ‘feature configuration’ to find the various types of feature options.

Note: You can add new options to base-package features. Your implementation may want to add additional options to one of the base-package's feature types. For example, your implementation may have plug-in driven logic that would benefit from a new option. To do this, display the lookup field that holds the desired feature's options. The lookup field's name is xxxx_OPT_TYP_FLG where xxxx is the identifier of the feature on the EXT_SYS_TYP_FLG lookup value. For example, to add new batch scheduler options, display the lookup field BS_OPT_TYP_FLG.

Feature Configuration - Messages

If the feature exists to interface with an external system, you can use this page to define the mapping between error and warning codes in the external system and our system.

Open this page using Admin > General > Feature Configuration and navigate to the Messages tab.

Description of Page

For each message that may be received from an external system, define the Feature Message Category and Feature Message Code to identify the message.

A corresponding message must be defined in the system message tables. For each message identify the Message Category and Message Number. For each new message, the Message Category defaults to 90000 (because an implementation's messages should be added into this category or greater so as to avoid collisions during upgrades).

Defining Master Configurations

A master configuration is an object that enables an implementation to define configuration for features in the system. It is an alternative to using feature configuration for defining options. A master configuration is defined using a business object. Only one master configuration may exist for a given business object.

The product provides one or more master configuration that may be used for configuration. Some examples, of base master configuration business objects are as follows

- Hijri to Gregorian Date Mapping. This allows an implementation that uses Hijri dates to define the mapping between those dates and Gregorian dates.

- ILM Configuration. For implementations that use Information Lifecycle Management, the ILM configuration record defines some parameters used by the process.

- Migration Assistant Configuration. For implementations that use the configuration migration assistant (CMA), the configuration record defines some parameters used by the process.

For a list of all the master configuration records provided by the product, navigate to the master configuration page in the application. To find help topics related to functionality controlled by the master configuration records, use the keyword ‘master configuration’ in the index.

To set up a master configuration, open Admin > General > Master Configuration.

The topics in this section describe the base-package zones that appear on the Master Configuration portal.

Master Configuration

The Master Configuration List zone lists every category of master configuration.

The following functions are available:

- If a master configuration record exists for a given master configuration business object, the broadcast icon may be used to view details information about the adjacent master configuration. In addition, an edit icon is visible to allow a user to update the record.

- If a master configuration record does not exist for a given master configuration business object, the add icon is visible to allow a user to define the record.

Master Configuration Details

The Master Configuration Details zone contains display-only information about a master configuration.

This zone appears when a master configuration has been broadcast from the Master Configuration zone.

Please see the zone's help text for information about this zone's fields.

Defining Security & User Options

The contents of this section describe how to maintain a user's access rights.

Next in This Section

- The Big Picture of Application Security

- The Big Picture of Row Security

- Defining Application Services

- Defining Security Types

- Defining User Groups

- Defining Access Groups

- Defining Data Access Roles

- Defining Users

The Big Picture of Application Security

The contents of this section provide background information about application security.

Next in This Section

- Application Security

- Action Level Security

- Field Level Security

- Encryption and Masking

- The Base Package Controls One User, One User Group, And Many Application Services

- Importing Security Configuration from an External Source

Application Security

The system restricts access to transactions or explicit services using an application service. The following points highlight what may be secured.

- The following points highlight security related to viewing and modifying individual records in the system:

- All maintenance objects define an application service that includes the basic actions available, typically Add, Change, Delete, and Inquire. The base product supplies an application service for every maintenance object. Note that the application service for the maintenance object is defined on its related service program.

- For maintenance objects whose user interface page is not portal-based, the application service also controls whether the menu entry appears. If a user doesn't have access to the maintenance object's application service, the menu item that corresponds with the application service will not be visible.

- For portal based user interfaces, each main (stand-alone) portal defines an explicit application service with the access mode Inquire, allowing the user interface to be secured independently of the underlying object security. If a user doesn't have access to the portal's application service, the menu item that corresponds with the application service will not be visible. The base product supplies an application service for every portal that is accessible from the menu. Note that the application service for the portal is defined on its related service program, which is derived via its navigation option and navigation key.

- Menu items may define an application service / access mode. Typically the security supplied for portals and maintenance objects provides enough granularity to suppress menu items that a user does not have access to. Linking an explicit application service / access mode will further suppress the menu item under one of the following scenarios:

- Suppress a menu item if the underlying application security for the transaction does not provide enough fine grained control. For example, imagine your implementation creates a special BPA script to add a To Do Entry and would like users to use the special BPA rather than the base supplied Add dialogue for To Do Entry. The underlying security settings for To Do Entry should grant Add access to these users given that the special BPA will still add a record. To suppress the base Add dialogue, link a special application service and access mode for the base supplied menu item for To Do Entry Add. Then define a menu entry for the new special BPA for adding.

- Suppress the add option if a user does not have add security for the object. By default the product does not suppress the add function if a user does not have add access to the object. Rather, the user is prevented from adding the record at the back-end. If your implementation would like to suppress the menu option, link the object's application service and the Add access mode to the Add menu item.

Note: The base product does not typically provide menu items with application services configured. Implementations may add this configuration if one of the above scenarios exist.

- Zones define an application service.

- For zones linked to a portal, if a user doesn't have access to the zone's application service, the zone will not be visible on the portal. In most cases the zone is delivered with the same application service as its portal. In special cases, such as the zones on the Dashboard, the product supplies separate application services for each zone allowing implementations to determine at a more granular level which users should have access to which zones.

- For query zones that are configured on a multi-query zone, if a user doesn't have access to the zone's application service, the zone will not be visible in the dropdown on the multi-query zone. In most cases all zones in a multi-query zone define the same application service as the multi-query zone. The product may supply a special application service for one or more zones in a multi-query zone if the functionality is special to certain markets or jurisdictions and not applicable to all implementations.

- For zones that are used by business services to perform SQL queries, the product supplies a default application service. Security for these zones is not checked by the product as they are used for internal purposes.

- Business objects define an application service. If the business object defines a lifecycle, the application service must include access modes that correspond to each state. In addition, the standard maintenance object access modes of Add, Change, Delete and Inquire are included. The base product business objects are supplied with appropriate application services. In addition, implementations may override the configured application service if desired.

- Batch controls define an application service which provides the ability to secure submission of individual batch processes. The application service must include an access mode of Execute. The base product batch controls are supplied with appropriate application services. These services will typically have an ID that matches the batch control ID.

- Report Definition records define an application service. The application service must include an access mode of Submit / View Report.

- The following objects are securable but are typically executed via internal processes. The security is provided to ensure that any access to the objects from an external source is secured.

- BPA scripts may define an application service with the access mode Execute. The base BPA scripts are typically not configured with any application service. An implementation may define one. Note that as mentioned above, a menu item may also be configured with an application service and access mode. This allows for a BPA that is invoked via a menu entry to be secured in more than one way.

- Business Services and Service Scripts define an application service with the access mode Execute. This is needed for services that may be executed from an external system, for example via an inbound web service. Base business services and service scripts that are linked to an inbound web service are configured with special application service. All other business services and service scripts are delivered with a default application service, which may be overridden by an implementation.

- Service Programs define an application service. As mentioned above, for Portals and Maintenance Objects, their application service is taken from the related service program. In base, specific application services are released for each of these types of service programs. All other service programs are typically delivered with a default application service, which may be overridden by an implementation. Note that for service programs linked to a Business Service, the application service on the business service takes precedence when invoking the business service.

Users are granted access to application services via user groups. For example, you may create a user group called Senior Management and give it access to senior manager-oriented pages and portals.

- When you grant a user group access to an application service with multiple access modes, you must also define the access modes that are allowed. Often the access modes correspond to an action on a user interface. For example, you may indicate a given user group has inquire-only access to an application service, whereas another user group has add, change, cancel and complete access to the same service. Refer to action level security for more information.

- If the application service has field level security enabled, you must also define the user group's security level for each secured field on the transaction.

- And finally, you link individual users to the user groups to which they belong. When you link a user to a user group, this user inherits all of the user group's access rights.

Action Level Security

When you grant a user group access to an application service, you must indicate the actions to which they have access.

- For application services that only query the database, there is a single action to which you must provide access - this is called Inquire.

- For application services that can modify the database, you must define the actions that the user may perform. At a minimum, most maintenance transactions support Add, Change, and Inquire actions. Additional actions are available depending on the application service's functions.

CAUTION:

Important! If an application service supports actions that modify the database other than Add, Change, and Delete; you must provide the user with Change access in addition to the other access rights. Consider a transaction that supports special actions in addition to Add, Change, and Inquire (e.g., Freeze, Complete, Cancel). If you want to give a user access to any of these special actions, you must also give the user access to the Inquire and Change actions.

Field Level Security

Sometimes transaction and action security is not sufficient. There are situations where you may need to restrict access based on the values of data. For example, in Oracle Utilities Customer Care and Billing you might want to prevent certain users from completing a bill for more than $10,000. This is referred to as "field level security".

Field level security can be complex and idiosyncratic. Implementing field level security always requires some programming by your implementation group. This programming involves the introduction of the specific field-level logic into the respective application service(s).

Note: Field level security logic is added to user exits. Refer to the Public API chapter of the Software Development Kit Developer Guide for more information on how to introduce field-level security logic into an application service's user exits.

Even though the validation of a user's field-level security rights requires programming, the definition of a user's access rights is performed using the same transactions used to define transaction / action level security. This is achieved as follows:

- Create a security type for each type of field-level security.

- Define the various access levels for each security type. For example, assume you have some users who can complete bills for less than $300, and other users who can complete bills for less than $1,000, and still other users who can complete bills for any value. In this scenario, you'd need 3 access levels on this security type:

- Level 1 (lowest): May authorize bills <= $300

- Level 2 (medium): May authorize bills <= $1,000

- Level 3 (highest): May authorize all bills

- Link this security type to each application service where this type of field level security is implemented. This linkage is performed on the security type transaction.

- Defining each user group's access level for each security type (this is done for each application service on which the security type is applicable).

Note:

Highest value grants highest security. The system expects the highest authorization level value to represent highest security level. Moreover, authorization level is an alphanumeric field so care should be taken to ensure that it's set up correctly.

Encryption and Masking

"Encryption" refers to encrypting data stored in the database using an encryption key. There are two different types of encryption described in the sections below. System encryption refers to columns in the system identified by the product to use encryption. Application encryptions refers to the ability for an implementation to configure fields and element that should be encrypted in the database.

"Masking" refers to overwriting all or part of an un-encrypted field value with a masking character. For example, perhaps only the last 4 digits of a credit card number are visible with the other digits changed to an asterisk. The system provides support for masking fields on the user interface that may be stored as plain text in the database. In addition, there are cases where encrypted fields are shown to the user interface using masked values rather than the encrypted value.

The following sections provide more information about each feature.

Next in This Section

- System Encryption

- User Interface Masking

- Application Encryption

System Encryption

The system automatically encrypts certain fields captured in various option tables or context tables. This is mainly used for passwords. For example, passwords captured in Message Sender context or password

In addition, batch control supports configuring a security option for parameters that capture sensitive information, such as a password. Refer to Defining Batch Controls for more information.

It is also possible to enable system encryption using the characteristic type F1-PWD. However, the maintenance object must include specific code to enable system encryption for characteristics of this type. In Oracle Utilities Application Framework, the only maintenance object that supports this is extendable lookup. Refer to Extendable Lookup Advanced Topics for more information.

User Interface Masking

The functionality described in this section is used to take data that is stored in plain text in the database and mask the value before it is presented to a user (or an external system). This feature includes the ability to allow some users to view the data unmasked using security configuration. The system allows different masking rules to be applied to different fields. For example, a credit card number can be masked differently than a social security number.

The following topics describe how to mask field values.

Identify the Data to be Masked

Identify the data that is stored as plain text, but should be masked for display to users. For example, imagine that you have identified that Credit Card Numbers and a person’s federal ID number (for example, in the United States, the Social Security Number or SSN). Each field identified may be displayed and maintained in different user interfaces throughout the system, but the masking rules for a given field are probably uniform regardless of where the data is displayed.

Primary keys cannot be masked. A field defined as a unique identifier of a row cannot be configured for masking. Masking a field that is part of the primary key causes a problem when attempting to update the record. This restriction also applies to elements that are part of a "list" in an XML column on a maintenance object. One or more elements in the list must be defined as a primary identifier of the list. Be sure that primary key elements in the list are not ones that require masking.

List members that contain different "types". Consider a page with a list that contains a person's identification numbers. You can set up the system so that a person's social security number has different masking rules than their drivers license number. If your implementation has this type of requirement, the list of masked fields should contain an entry for each masking rule.

For each field, if there are some users that may see the data unmasked on one or more of the user interfaces, then security configuration is required. If the value of a field should be masked for all users across all pages in the application, then the security configuration is not needed.

Security Configuration

Define a security type for each field with two authorization levels:

- 1 - Can only see the element masked

- 2 - Can only see the element unmasked

Link all of the security types to an application service of your choosing. We recommend linking every masking-oriented security type to a single application service (e.g., CM_MASK) as it makes granting access easier.

For each security type, identify which users can see its data unmasked and which users can only see its data masked. If the masked and unmasked users fit into existing user groups, no additional user groups are necessary. Otherwise, create new user groups for the masked and unmasked users.

After the user groups for each security type are defined, link each user group to the application service defined above. When a user group is linked to the application service, you will define the authorization level for each security type linked to the application service. If a user group's users should see the security type's field values unmasked, set the authorization level to 2; otherwise set it to 1.

Note: Flush the cache. Remember that any time you change access rights you should flush the security cache (by entering flushAll.jsp on the URL of the application) if you want the change to take effect immediately.

Configure a Masking Algorithm

A data masking algorithm must be created for each combination of masking rules and security type. These algorithms determine if a user has the rights to view a given field unmasked, and, if not, how the field should be masked.

The base package provides the algorithm type F1-MASK whose parameters are designed to handle most masking needs. If certain users may see the data unmasked, parameters capture the application service, security type and authorization level defined above used to evaluate this. In addition, parameters allow you to configure how much of the data to mask, what masking character to use. Refer to the algorithm type description for more information.

Click here for a list of all the algorithms supplied for this plug-in spot.

Determine How the Fields are Displayed

The masking configuration differs based on how a field is retrieved for access to the user interface. So for the masking of one “logical” field (like a person’s SSN), there may be multiple configuration entries required to cover all the access methods. Review each user interface where a given field is displayed and create the following categories:

- The field is an element that is retrieved by invoking a business object, a business service, or a service script

- The field is displayed on a fixed maintenance page (and is therefore retrieved by invoking a page service)

- The field is displayed on a fixed search page (and is therefore retrieved by invoking a search service)

- The field is stored as an ad hoc characteristic

Create a Feature Configuration for Each Masked Element

Create a feature configuration with a Feature Type of Data Masking. An option entry with option type of Field Masking is needed for every combination of field to mask and the method used to display the data. The value will contain mnemonics that reference the appropriate data masking algorithm along with configuration that differs depending on how the field is retrieved for display as described below.

Schema Based Object Field Masking

For data that is accessed via a schema-based object call and displayed in a UI map, the field to be masked must reference a meta-data field name in its schema definition: field="fld_name", alg="algorithm name"

If the element references an mdField in the schema, that is the field used to identify the masking rule. If there is no mdField reference but only a mapField reference, that is the field used to identify the masking rule. For example, if you want to mask a credit card number, let's assume that field is defined in the schema is the following:

<creditCard mdField="CCNBR" mapField="EXT_ACCT_ID"/>

In this case, the option value should be field="CCNBR", alg="algorithm name". An option value of field="EXT_ACCT_ID", alg="algorithm name" would not result in masking.

A "where" clause may also be specified. This is useful for data that resides in a list where only data of a certain type needs to be masked: field="fld_name", alg="algorithm name", where="fld_name='value'"

For example, person can have a collection of IDs and only IDs of type 'SSN' (social security number) should be masked. If the person data including its collection of person IDs is displayed on a UI map via a business object call, let's assume the collection is defined in the following way:

<personIDs type="list" mapChild=CI_PER_ID">

<isPrimaryId mapField="PRIM_SW"/>

<idType mapField="ID_TYPE_CD"/>

<personIdNumber mapField="PER_ID_NBR"/>

</personIds>

The option value may look like this: field="PER_ID_NBR", alg="algorithm name", where="ID_TYPE_CD='SSN'"

Please note the following important points for schema based masking:

- Limitation of 'where' field Although the main use of a 'where' clause for schema oriented elements is to mask certain elements in a list based on a 'type', it is also possible to mask a single field in the schema based on the value of another field. For example, imagine that a customer submits a registration form that defines an ID type and ID value. Although this data is not in a list, the implementation may still want to only mask the ID value if the ID type is "SSN". The framework is only able to mask an element in the schema based on a 'where' clause if the element in the 'where' clause is a "sibling" in the schema.

- If the element to be masked is in a list, the element in the 'where' clause must be in the same list.

- If an element to be masked maps to a real column in a table, the element in the 'where' clause must also map to a real column in the table.

- If an element to be masked maps to and XML column in the table as a single element, the element in the 'where' clause must map to the same XML column as a single element.

- Multiple feature option entries for the same field. It's possible that different schemas in the system have a similar type of data that may be masked based on different conditions. For example, imagine that an implementation has different schemas that captured or referenced person identifiers in different ways:

- One schema captures a single person ID without any corresponding "type" record and it should always be masked using Algorithm CM_SSN_MASK:

<personSSN mapXML=BO_DATA_AREA mdField=PER_ID_NBR/>

- One schema captures a person ID and a corresponding ID Type and it should be masked with Algorithm CM_SSN_MASK if the type is "SSN" and masked with algorithm CM_FEIN_MASK if the type is "FEIN".

<personIdType mapXML=BO_DATA_AREA mdField=ID_TYPE_CD/>

<personId mapXML=BO_DATA_AREA mdField=PER_ID_NBR/>

- One schema captures a person ID and a corresponding ID Type and it has the same masking rules as the previous schema, but a different field name is used for the ID Type code. (This scenario could happen if for example a different label is desired for ID Type on the user interface for this schema.)

<personIdType mapXML=BO_DATA_AREA mdField=CM_ID_TYPE/>

<personId mapXML=BO_DATA_AREA mdField=PER_ID_NBR/>

For this scenario, the feature options may look like this:

1. field="PER_ID_NBR", alg="CM_SSN_MASK"

2. field="PER_ID_NBR", alg="CM_SSN_MASK", where="ID_TYPE_CD='SSN'"

3. field="PER_ID_NBR", alg="CM_FEIN_MASK", where="ID_TYPE_CD='FEIN'"

4. field="PER_ID_NBR", alg="CM_SSN_MASK", where="CM_ID_TYPE='SSN'"

5. field="PER_ID_NBR", alg="CM_FEIN_MASK", where="CM_ID_TYPE='FEIN'"

For each schema, the system will first find whether the element applies to any masking option. It will find 5 masking options for the field PER_ID_NBR. Then it will determine if any sibling elements match the 'where' clause.

- If more than one sibling element matches a 'where' clause, a runtime error is issued. For example if a schema has an element that references "mdField=ID_TYPE_CD" and an element that references "mdField=CM_ID_TYPE", this is an error. Additionally, if multiple elements reference mdField=ID_TYPE_CD", this is an error.

- If one and only one sibling element matches a 'where' clause, the value of the element is compared to the values defined in the 'where' clause. If it finds a match on the value, the appropriate masking algorithm is applied. If no match is found (for example, the Person ID Type is "LICENSE") the element is displayed as is.

- If no sibling element matches a 'where' clause and a feature option exists with no 'where' clause (option 1 above), then the masking algorithm of the option with no 'where' clause is applied.

- Changing the value in the 'where' clause. If your implementation has some users that are allowed to change records where some data is masked based on a condition, it is recommended to design the user interface to reset the masked value when the value in the 'where' clause changes. For example, if a user is prevented from viewing a person's social security number, but the user is allowed to make updates to the person's record, changing the value of the Person ID Type should reset the Person ID Number. This would ensure that the user does not 'unmask' the social security number by simply changing the ID Type.

Records Maintained Using Page Maintenance

For data that is accessed via a page maintenance service call, indicate the table name and the field name where the data resides: table="table_name", field="fld_name", alg="algorithm name"

For example if the Person record and its collection of identifiers are displayed and maintained using page maintenance, the option value should be table="CI_PER_ID", field="PER_ID_NBR", alg="algorithm name"

A "where" clause may also be specified: table="table_name", field="fld_name", where="fld_name='value'", alg="algorithm name"

This is useful for data that resides in a child table where only data of a certain type needs to be masked. For the person ID example, table="CI_PER_ID", field="PER_ID_NBR", alg="algorithm name", where="ID_TYPE_CD='SSN'"

Characteristic Data

For data that is stored as a characteristic, simply indicate the characteristic type: CHAR_TYPE_CD='char type', alg="algorithm name"

This needs to be defined only once regardless of which characteristic entity the char type may reside on. Note that only ad-hoc characteristics are supported.

Masking Fields in Explorer Zones or Info Strings

In explorer zones data is often retrieved using SQL directly from the database. No masking is applied automatically in this case. If there is data in the explorer zone results that should be masked, the masking must be applied by calling a business service.

Similarly, an MO Info algorithm may not use BO interaction to get data. It may access data using SQL for efficiency purposes. No masking in applied when retrieving data via SQL. To apply masking to a string prior to including it in an info string, the masking must be applied by calling a business service.

The system supplies two business services to be called to determine if masking rules apply for a specific field.

- F1-TableFieldMask. Mask a Table field. This business service receives a table name, field name and one or more field values. If masking applies it returns the masked value.

- F1-SchemaFieldMask. Mask a Schema field. This business service receives a schema name and type, XPath and field value. If masking applies it returns the masked value.

Search Service Results

For data that is displayed on a ‘fixed’ search page, it is retrieved via a search service call. Indicate the search name and the appropriate field to mask along with the masking algorithm. For example: search="SearchServiceName", field="PER_ID_NBR", where="ID_TYPE_CD='SSN'", alg="algorithm name"

To find the name of the search service, launch the search in question, right click in the filter area and choose View Source. Search for ServiceName. The service name is listed there. To find the field name to mask, go back to the search window and right click on the results area and choose View Source. Look for the Widget Info section and find the field name in the SEARCH RESULTS (do not include the $). Note, the "where" statement can only apply to fields that are also part of the search results.

Additional Masking Information

The following points provide additional information to assist in your masking configuration:

- If the demonstration database includes a Data Masking feature configuration, review the settings because it will probably contain masking rules that will match your own.

- On data input pages, a user might be able to enter or change masked data, such as a bank account number, but not be able to subsequently see what they added or changed.

- External systems can request information by performing a service call via a web service. Please keep in mind that some web service requests require data to be masked and some do not. For example, a request from an external system to synchronize person information needs the person's social security number unmasked; whereas a request from a web self service application to retrieve the same person information for display purposes needs the person's social security number masked. To implement this type of requirement, different users must be associated with each of the requests and these users must belong to separate user groups with different access rights.

- If a maintenance object (MO) contains a field that holds an XML document and a service call invokes the MO's service program directly, the system will mask individual XML elements in the field if a Determine BO algorithm has been plugged into the maintenance object and the element(s) in the respective BO schema have been secured as described above.

Application Encryption

The functionality described in this section allows implementations to configure fields to encrypt when storing it in the database. This functionality is mutually exclusive from the User Interface Masking functionality described in the previous section. This feature supports encrypting specific elements stored within a CLOB or XML column.

The following points highlight the features of the encryption functionality:

- The encryption key is defined using a keystore, which must be set up in order to use this functionality. For details about setting up the keystore in the system, see the Installation Guide.

- When a field is configured to be encrypted, the encrypted data is stored in a special encryption field that is not the source field (the one exposed to the user on the user interface). The source field captures the data as masked. Because a special field is required to support encryption, the product must provide support for that field to be encrypted.

- For encrypted data that must allow searching, the system supports capturing a hash value in a special field. The product must provide support for this functionality. Besides providing a special field to capture the hash value, base search functionality for that data must also cater for this configuration.

- The system supports encrypting data that is captured as an element within an XML field. If the XML field is provided in a schema owned by the product, then the product must provide specific support for the capture of the encrypted data.

The following sections provide additional information about the support for encryption provided by the framework. Refer to the security chapter of the administration guide for your particular product for more information.

Encrypting and Masking the Data

When a product enables encrypting for a given type of data, a special encryption field should be created to capture the encrypted value. Because encrypting is optional, the source field (the one exposed to the user) should not be this special encrypted field. If encryption is configured, the system will internally populate the encrypted field. The source field will be populated with asterisks by default. That way the masked data is what is shown to the user on page rather than the encrypted value.

The following points highlight how the system behaves when encryption is configured and when it is not. Assume as an example, the field is a credit card number. The user views and populates a field with the field name CC_NBR. The table also has a second field ENCR_CC_NBR. A user populates the credit card number:

- If encryption is not configured, CC_NBR will be updated with the entered credit card number and ENCR_CC_NBR will be empty. Note that in this case, an implementation may choose to configure user interface masking.

- If encryption is configured, CC_NBR will be updated with ‘*******************’ and ENCR_CC_NBR will contain the encrypted value. The asterisks for the standard field will fill the full field size up to 50 characters.

If for some reason the standard masking using all asterisks is not desired, the system supports supplying an explicit masking algorithm using the same Data Masking plug-in spot used for User Interface Masking.

Warning: Unlike user interface masking, the masking of encrypted fields is not driven by security. The data stored in the source field for all encrypted data should be masked. Be sure not to configure security authorization logic in algorithms used for this type of masking.

Feature Option Configuration

Create a feature configuration with a Feature Type of Encryption. For each source field you are encrypting, enter an option with option type of Field Encryption. The value will contain mnemonics that reference the appropriate encryption key alias defined in the keystore along with configuration related to the field and its table location. Unlike the user interface data masking, the configuration for data encryption is related to how the data is stored rather than how it is displayed. In addition, each entry may define an explicit masking algorithm to override the default and if supported, may also define a hash field and hash alias.

For data that is stored in a specific column on a table, an explicit field to capture the encrypted value must exist. Indicate the table name, source field name and encrypted field name along with the alias: table='table_name', field='fld_name', encryptedField='encr_fld_name', alias='alias key'

A "where" clause may also be specified when data resides in a child table and only data of a certain type needs to be encrypted.

Example, table='CI_PER_ID', field='PER_ID_NBR', encryptedField='ENCR_PER_ID_NBR', alias='key alias', where='ID_TYPE_CD='SSN''

For data that is stored in an XML column in a record, the source field to be encrypted must reference a meta-data field name in its schema definition along with the element that captures the encrypted data and the alias: field='field_name', encryptedField='encr_field_name', alias='key alias'

The syntax for adding a reference to a masking algorithm is maskAlg='algorithm name' .

The syntax for adding configuration for capturing a hash value for searching purposes is hashAlias='hashAliasKey' hashField='HASH_FLD_NAME'.

The following is an example of configuration that uses all the possible options (specific masking algorithm, where clause and hash field support):

table='CI_PER_ID', field='PER_ID_NBR', alias='aliasKey', encryptedField='ENCR_PER_ID_NBR', hashAlias='hashAliasKey' hashField='HASH_PER_ID_NBR', where='ID_TYPE_CD=SSN', maskAlg='CM-PERIDMASK'

Searching by an Encrypted Value

If the product supports a hashed value for an encrypted field for searching purposes, the following points highlight explorer zone configuration for this purpose

- The user filter value should reference the source field and should include an additional encrypt= mnemonic. For example

type=STRING

label=PER_ID_NBR

encrypt=[CI_PER_ID,PER_ID_NBR,ID_TYPE_CD,F1]

Refer to User Filters for more information.

- The SQL should include the hashed value in the WHERE clause. Note that because encryption is optional, a product zone that includes searching by a field eligible for encryption will include finding a match for the filter in the source field (as plain text) or in the hashed field. For example:

WHERE

[(F2) (ID.PER_ID_NBR =:F2 OR ID.HASH_PER_ID_NBR = :F2)]

Customizing Encryption Algorithm

Although the encryption algorithm to use with a given key can be gleaned from the key in the keystore, there is sometimes extra information associated with an algorithm that might need to be used to encrypt or decrypt data.

The system provides a feature configuration option for the Encryption feature type using the option type Algorithm Info that can be used to adjust the behavior of the encryption.

- You can modify the default mode and padding of the encryption algorithm.

- If a key will be used to digitally sign anything, the signing algorithm can also be specified for the key.

For details about the syntax, refer to the feature option type’s detailed description.

The Base Package Controls One User, One User Group, And Many Application Services

When the system is initially installed, the following information is delivered:

- Application services for all secured transactions, maintenance objects, business objects, business services, scripts and zones in the base package.

- A user identified by the user id SYSUSER.

- A user group identified by the user group code ALL_SERVICES. This user group is associated with all supported application services delivered with the base product. This user group is given access to all access modes for all application services (i.e., all actions on all transactions).

- The user SYSUSER is linked to the ALL_SERVICES user group. This means that this user has access to all transactions and all actions.

You cannot change or remove the information delivered for ALL_SERVICES. This information is owned by the base package. It is provided so that an "initial user" has access to the entire system and can setup user groups and users as per your organization's business requirements. It is not recommended to provide your own users with access to the ALL_SERVICES user group. Rather, create user groups that are appropriate for the organization's business requirements and define user access to these user groups. If you introduce new transactions, configure them for the appropriate custom user groups.

In addition, SYSUSER is provided to allow for an initial user to define appropriate users in your implementation. Once proper administrative users have been defined, it is recommended that SYSUSER is updated to set the User Enable setting to Disabled.

When you receive an upgrade:

- New application services are delivered for the new transactions, business objects, zones introduced in the release. The release notes highlights the additions / changes.

- Existing application services are updated with changes in their access modes (e.g., if a new action is added to a transaction, its application service is updated accordingly).

- The ALL_SERVICES user group is updated so it can access the new / changed application services.

- Implementations should review the release notes and determine which user groups created for your implementation should be updated with the additions, if applicable.

Importing Security Configuration from an External Source

The product provides support for importing security information from an external source:

- If your organization uses Lightweight Directory Access Protocol (LDAP), you can import your existing LDAP users and groups into the system. Once imported, all user and group functions are available. You can import a user group, or a single user. You can resynchronize your LDAP users and groups at any time.

Fastpath: For more information refer to LDAP Integration.

- The system provides an integration with Oracle Identity Manager. When a user is created in the identity manager product, its information can automatically be interfaced to the product. Once the user is successfully created in the system, all functions are available.

Fastpath: For more information refer to Oracle Identity Manager Integration.

The Big Picture of Row Security

Some products allow you to limit a user's access to specific rows. For example, in Oracle Utilities Customer Care and Billing, row level security prevents users without appropriate rights from accessing specific accounts.

A combination of framework configuration and configuration in your edge product is required for row level security. The following points describe the configuration:

- For each record that should be secured, associate it with an Access Group. Note that if your edge product supports row level security, that product is providing a link between the secure-able record and Access Group. Your access groups may be granular and only referenced by one secured record or they may be more broad and be referenced by multiple secured records that require the same type of security restriction.

- To define which users have access to the secured records, you define a Data Access Role. For each data access role, define which Access Groups the role has security clearance for. An access group may be linked to one or more data access roles. In addition, define the Users that have access rights to these secured records. When you grant a data access role rights to an access group, you are giving all users in the data access role rights to all secured records all the referenced access groups. A user may belong to many data access roles.

If your edge product supports row level security, it will include logic in the appropriate areas of the system to limit the secured rows that a user may view or maintain based on this configuration. For example, in Oracle Utilities Customer Care and Billing, throughout the system users are only able to view and maintain information about an account and any of its detail if the user is in a Data Access Role for the account’s Access Group (or the account is not linked to an Access Group).

Fastpath: Refer to your product’s documentation for more information on row level security, if applicable.

Defining Application Services

An application service exists for every transaction in the system. Please refer to Application Security for a description of how application services are used when you grant user groups access rights transactions.

CAUTION:

Important! If you introduce a new application service, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Next in This Section

- Application Service - Main

- Application Service - Application Security

Application Service - Main

Select Admin > Security > Application Service to define an application service.

Description of Page

Enter a unique Application Service code and Description for the application service.

Indicate the application service's various Access Modes (i.e., actions). Refer to Action Level Security for more information about the significance of these fields.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference SC_APP_SERVICE.

Application Service - Application Security

Use the Application Security portal to set up security for an application service.

Open this page using Admin > Security > Application Service, and then navigate to the Application Security tab.

This section describes the available zones on this page.

Application Service Details zone. This zone contains display-only information about the selected application service, including the Access Modes for the application service and its security type.

Secured Objects zone. This zone displays the object (or objects) that are secured by this application service. Refer to Application Security for details about the types of objects that may be secured.

User Groups Linked zone. This zone lists the user groups that currently have a link to the application service. Note that expired links are also included. The following actions are available:

- Click the Description link to navigate to the User Group - Users page for the adjacent user group. This allows you to add or remove users linked to the user group.

- Click Deny Access to remove the selected Application Service’s link to this user group.

User Groups not Linked zone. This zone lists the user groups that do not have a link to the application service. The following actions are available:

- Click the Description link to navigate to the User Group - Users page for the adjacent user group.

- Click Grant Access to navigate to the User Group - Application Services page for the user group. The page is automatically positioned at the selected application service allowing you to set the access modes and the expiration date.

Defining Security Types

Security types are used to define the types of field level security.

Note: Programming is required. You cannot have field level security without introducing logic to user exits. Refer to Field Level Security for more information on how security types are used to define field level security.

Next in This Section

- Security Type - Main

Security Type - Main

Select Admin > Security > Security Type to define your security types.

Description of Page

Enter a unique Security Type and Description.

Use the Authorization Level grid to define the different authorization levels recognized for this security type. Enter an Authorization Level Number and its Description.

Note: Programming is required. Note that the values that you enter are not interpreted by the system itself, but by the user exit code used to implement the special security. Check with the developer of the user exit logic for the correct values. Refer to Field Level Security for more information on how security types are used to define field level security.

Use the Application Services grid to define the application service(s) to which this security type is applicable. If this application service is already associated with user groups, you must update each user group to define their respective security level. This is performed using User Group - Application Service.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_SC_TYPE.

Defining User Groups

A user group is a group of users who have the same degree of security access. Think of a user group as a "role"; associated with a role are:

- The users who play this role

- The application services to which the role's users have access (along with the actions they can execute for each service and their field level security authorization levels).

Next in This Section

- User Group - Main

- User Group - Application Services

- User Group - Users

User Group - Main

Select Admin > Security > User Group to view the application services to which a user has access.

CAUTION:

Application services may not be changed or removed from the ALL_SERVICES user group. Refer to The Base Package Controls One User, One User Group, And Many Application Services for an explanation.

Description of Page

Enter a unique User Group code and Description for the user group.

Owner indicates if this user group is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a user group. This information is display-only.

The Application Services grid displays the various application services to which users in this group have access. Please note the following in respect of this grid:

- Use the Application Service search to restrict the application services displayed in the grid. For example, if you only want to see application services that start with the word "field", you can enter this word and press enter.

- To add additional application services to this user group, navigate to the User Group - Application Services page and click the add icon.

- To remove or change this user group's access to an application service, click the go to button adjacent to the respective application service. This will cause you to be transferred to the User Group - Application Services tab where you should click the - icon to remove the application service from the user group.

- Note, Owner indicates if this user group / application service relationship is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add an application service to the user group. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference SC_USER_GROUP.

User Group - Application Services

Select Admin > Security > User Group and navigate to the Application Services tab to maintain a user group's access rights to an application service.

Note: Important! When you grant a user group access rights to an application service, you are actually granting all users in the user group access rights to the application service.

Description of Page

The Application Service scroll contains the application services to which the User Group has access.

Note: You can also use Main page to select the application service for which you wish to change the access privileges. To do this, simply click the go to button adjacent to the respective application service.

To add additional application services to this user group, click the + icon and specify the following:

- Enter the Application Service ID to which the group has access.

- Define the Expiration Date when the group's access to the application service expires.

Define the Access Modes that users in this group have to the Application Service. When a new application service is added, the system will default all potential Access Modes associate with the Application Service. You need only remove those modes that are not relevant for the User Group. Refer to Action Level Security for more information about access modes.

CAUTION:

Important! If an application service supports actions that modify the database other than Add, Change, and Delete; you must provide the user with Change access in addition to the other access rights. Consider a transaction that supports actions in addition to Add, Change, and Inquire (e.g., Freeze, Complete, Cancel). If you want to give a user access to any of these additional actions, you must also give the user access to the Inquire and Change actions.

If you require additional security options, often referred to as "field level" security, then you use Security Type Code and assign an Authorization Level to each. When a new application service is added, the system will display a message indicating how many security types are associated with this application service. Use the search to define each Security Type Code and indicate the appropriate Authorization Level for this user group. Refer to Field Level Security for more information about security types.

User Group - Users

Select Admin > Security > User Group and navigate to the Users tab to maintain the users in a user group.

Description of Page

The scroll area contains the users who are part of this user group.

Note: Keep in mind that when you add a User to a User Group, you are granting this user access to all of the application services defined on the Application Services tab.

The following fields are included for each user:

- Enter the User ID of the user.

- Use Expiration Date to define when the user's membership in the group expires.

- Owner will be Customer Modification.

Note: You can also add a user to a user group using User - Main.

Defining Access Groups

Fastpath: Refer to The Big Picture of Row Security for a description of how access groups are use to restrict access to specific objects.

Access groups control which groups of users (referred to as Data Access Roles) have rights to accounts (or other objects) associated with the access group. Select Admin > Security > Access Group to define your access groups.

Description of Page

Enter a unique Access Group code and Description for the data access group.

Use the Data Access Role collection to define the data access roles whose users have access to the access group's accounts (or other objects). Keep in mind that when you add a Data Access Role to an Access Group, you are granting all users who belong to this role access to all of the accounts (or other objects) linked to the access groups.

Note: You can also use Data Access Role - Access Group to maintain a data access role's access groups.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_ACC_GRP.

Defining Data Access Roles

Fastpath: Refer to The Big Picture of Row Security for a description of how access groups are use to restrict access to specific objects.

The data access role transaction is used to define two things:

- The users who belong to the data access role.

- The access groups whose accounts (or other objects) may be accessed by these users.

Next in This Section

- Data Access Role - Main

- Data Access Role - Access Group

Data Access Role - Main

Select Admin > Security > Data Access Role to define the users who belong to a data access role.

Description of Page

Enter a unique Data Access Role code and Description for the data access role.

The scroll area contains the Users who belong to this role. A user's data access roles play a part in determining the accounts (or other objects) whose data they can access.

To add additional users to this data access role, press the add button, , and specify the following:

- Enter the User ID. Keep in mind that when you add a User to a Data Access Role, you are granting this user access to all of the accounts (or other objects) linked to the data access role's access groups.

- Use Expiration Date to define when the user's membership in this data access role expires.

Note: Also maintained on the user page. You can also use User - Access Security to maintain a user's membership in data access roles.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_DAR.

Data Access Role - Access Group

Select Admin > Security > Data Access Role and navigate to the Access Groups tab to define the access groups whose accounts (or other objects) may be accessed by the users in this data access role.

Description of Page

Use the Access Group collection to define the access groups whose objects can be accessed by this role's users. Keep in mind that when you add an Access Group to a Data Access Role, you are granting all users who belong to this role access to all of the accounts (or other objects) linked to the access groups.

Note: You can also use Access Group - Main to maintain an access group's data access roles.

Defining Users

The user maintenance transaction is used to define a user's user groups, data access roles, portal preferences, default values, and To Do roles. To access the user maintenance transaction, select Admin > Security > User.

The user maintenance transaction is the same transaction invoked when the user launches Preferences.

User Interface Tools

This section describes tools that impact many aspects of the user interface.

Next in This Section

- Defining Menu Options

- The Big Picture of System Messages

- The Big Picture of Portals and Zones

- Custom Look and Feel Options

- Setting Up Portals and Zones

- Defining Display Icons

- Defining Navigation Keys

- Defining Navigation Options

Defining Menu Options

The contents of this section describe how you can add and change menus.

CAUTION:

Updating menus requires technical knowledge of the system. This is an implementation and delivery issue and should not be attempted if you do not have previous experience with menus.

Note: Security and menus. Refer to Application Security for a discussion of how application security can prevent menu items (or an entire menu) from appearing.

Note: Module configuration and menus. Your module configuration can prevent menu items (or an entire menu) from appearing.

Next in This Section

- Menu - Main

- Menu - Menu Items

Menu - Main

This transaction is used to define / change any menu in the system. Navigate to this page using Admin > System > Menu.

Description of Page

Enter a meaningful, unique Menu Name.

Owner indicates if this menu line is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a menu line. This information is display-only.

The Flush Menu button is used to flush the cached menu items so you can see any modified or newly created menus. Refer to Caching Overview for more information.

Menu Type defines how the menu is used. You have the following options:

- Admin is one of the menus that appears in the Application Toolbar. It is a special type of menu because admin menu items can be grouped alphabetically or by functional group. Refer to the description of Admin Menu Order on Installation Options - Framework for more information about admin menu options.

- Context refers to a context menu.

- Main is another menu that appears in the Application Toolbar that is simply titled Menu .

- Page Action Menu defines buttons that appear in the Page Title Area.

- Submenu defines a menu group that appears when an Application Toolbar menu is selected. for the Admin menu, this is only visible when it's organized functionally.

- Enter User Menu refers to the menu items that appear on the user menu; for example, User Preferences.

Description provides a description of the menu. Note that this is not the text used when displaying a menu option.

Sequence is only enabled for the Main and Admin menu types.

The grid contains a summary of the menu's lines. Besides the standard add and delete icons available in a grid, the following information is displayed:

- Menu Line ID is the unique identifier of the line on the menu. This information is display-only. Before the menu line id is a Go To icon that allows a user to drill into the Menu Items for the displayed menu line.

- Sequence is the relative position of the line on the menu. Note, if two lines have the same Sequence, the system organizes the lines alphabetically (based on the Long Label, which is defined on the next tab).
Note: An implementation may override the sequence of a base product owned menu line. Also note that the sequence is defined on the menu line language table, allowing for different orders to be used for different languages (or to let the menu be sorted alphabetically in one language and in a specified order in a different one).

- Navigation Option / Submenu contains information about the line's items. If the line's item invokes a submenu, the submenu's unique identifier is displayed. If the line's item(s) invoke a transaction, the description of the first item's navigation option is displayed.

- Long Label is the verbiage that appears on the menu line.

- Item Count is the number of menu items on the line.

- Owner indicates if this menu line is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a menu line. This information is display-only.

Note: Adding menu lines to base owned menus. An implementation may choose to add custom menu lines along with its menu item (or items) to a base owned menu.

Refer to the description of Menu Items for how to add items to a menu line.

Menu - Menu Items

Once a menu has lines (these are maintained on the main page), you use this page to maintain a menu line's items.

Each menu line can contain one or two menu items. The line's items control what happens when a user selects an option on the menu.

There are two types of menu lines that define a single menu item: one type causes a submenu to appear; the other type causes a transaction or script to be invoked when it's selected.

- The following is an example of a menu line with a single item that opens a submenu:

- The following is an example of a menu line with a single menu item that launches a transaction or script:

A menu line that defines two menu items is used to provide an Add option and a Search option for the same type of object. In this case each menu item defines a transaction or script to be launched. The menu is rendered with the Add and Search options displayed. The following is an example of a menu line with two menu items.

Navigate to this tab by clicking the Go To button adjacent to a menu line from the Main tab.

Description of Page

Menu Name is the name of the menu on which the line appears. Menu Line ID is the unique identifier of the line on the menu. Owner indicates if this menu is owned by the base product or by your implementation (Customer Modification). This information is display-only.

The Menu Line Items scroll contains the line's menu items. The following points describe how to maintain a line's items:

- Menu Item ID is the system assigned unique identifier of the item.

- Owner indicates if this item is owned by the base product or by your implementation (Customer Modification).

- If the menu item should invoke a submenu:

- Use Sub-menu Name to identify the menu that should appear when the line is selected

- Use Long Label to define the verbiage that should appear on the menu line

- Populate the Override Label to override the long label of a base product owned sub-menu.

- If the item should invoke a transaction or BPA script:

- Use Sequence to define the order the item should appear in the menu line (we recommend this be set to 1 or 2 as a menu line can have a maximum of 2 menu items). The “search” menu item should be defined as sequence 1 and the “add” menu item as sequence 2 given that the label of the “search” menu item is used for the menu line’s label.

- Use Navigation Option to define the transaction or script to open. Refer to Defining Navigation Options for more information.

- For a menu line that includes two items — one for Add and one for Search, if one of the items includes configuration for Image GIF Location and Name , the system assumes that this represents the Add. This functionality is a carryover from earlier releases where the Add function rendered in the menu with a “+” image, which also identified the item that represents the Add. If neither item includes Image configuration (because it is no longer needed for rendering the menu), the system relies on the order of the items as mentioned above. The first item is the “search” and the second item is the “add”.

- Image Height, Image Width and Balloon Description are not applicable at this time.

- Use the Long Label to define the text to appear on the menu entry. Note that when a menu line defines two menu items, the long label on the search entry is used to build the menu entry text. The label long on the menu line that defines the Add option is information only.

- The Override Label is provided in case you want to override the base-package's label.

- Use Application Service and Access Mode to easily suppress a menu item for one or more users. Refer to Application Security for more information.

The Big Picture of System Messages

All error, warning and informational messages that are displayed in the system are maintained on the message table. Every message is identified by a combination of two fields:

- Message category number. Think of a message category as a library of messages related to a given functional area. For example, there is a message category for billing messages and another one for payment messages.

- Message number. A unique number identifies each message within a category.

Every message has two components: a brief text message and a long description. On the Main tab, you can only maintain the brief message. If you need to update a message's long description, you must display the message on the Details tab.

Note: You cannot change the product’s text. If the message is "owned" by the product, you cannot change the product’s message or detailed description. If you want your users to see a different message or detailed description other than that supplied by the product, display the message on the Details tab and enter your desired verbiage in the "customer specific" fields (and flush the cache).

Next in This Section

- Defining System Messages

Defining System Messages

The contents of this section describe how to maintain messages that appear throughout the system. An implementation may introduce messages used in custom processes or may choose to override the text for messages delivered by the product.

Next in This Section

- Message - Main

- Message - Details

Message - Main

Select Admin > System > Message to maintain a message category and its messages.

Description of Page

To add a new message category, enter a Message Category number and Description.

CAUTION:

Message category 80000 or greater must be used to define new messages introduced for a specific implementation of the system. Changes to other Message Text will be overwritten when you next upgrade. If you want to make a change to a Message, drill down on the message and specify Customer Specific Message Text. Note that even for message categories 80000 and higher, message numbers lower than 1000 are reserved for common base product messages.

Note: Owner indicates if this message category is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a category. This information is display-only.

To update a message, you must first display its Message Category. You can optionally start the message grid at a Starting Message Number.

To override the message text or detailed description of messages owned by the base product, click on the message's go to button. When clicked, the system takes you to the Details tab on which you can enter your implementation's override text.

The following points describe how to maintain messages owned by your implementation:

- Click the - button to delete a message.

- Click the + button to add a new message. After clicking this button, enter the following fields:

- Use Message Number to define the unique identifier of the message within the category.

- Use Message Text to define a basic message. You can use the %n notation within the message text to cause field values to be substituted into a message. For example, the message text The %1 non-cash deposit for %2 expires on %3 will have the values of 3 fields merged into it before it is displayed to the user (%1 is the type of non-cash deposit, %2 is the name of the customer, and %3 is the expiration date of the non-cash deposit).
Note: The system merges whatever values are supplied to it. Therefore, if a programmer supplies a premise address as the second merge parameter in the above message, this address is merged into the message (rather than the customer's name).

- Owner indicates if this message number is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a message. This information is display-only.

- Click the go to button to enter a detailed description of the message. Clicking this button transfers you to the Details tab.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_MSG. In addition, messages are used throughout the system for error messages and other system messages.

Message - Details

Select Admin > System > Message and navigate to the Details tab to define detailed information about a message.

Note: Drilling in from the Main tab. Rather than scrolling through the messages, you can display a message by clicking the respective go to button in the grid on the main tab.

Description of Page

The Message Collection scroll contains an entry for every message in the grid on the Main tab. It's helpful to categorize messages into two categories when describing the fields on this page:

- Product messages

- Implementation-specific messages (i.e., a message added to Message Category 80000 or greater)

For product messages, you can use this page as follows:

- If you want to override a message, specify Customer Specific Message Text.

- You are limited to the same substitution values used in the original Message Text. For example, if the original Message Text is The %1 non-cash deposit for %2 expires on %3 and %1 is the type of non-cash deposit, %2 is the name of the customer, and %3 is the expiration date of the non-cash deposit; your Customer Specific Message Text is limited to the same three substitution variables. However, you don't have to use any substitution variable in your message and you can use the substitution variables in whatever order you please (e.g., %3 can be referenced before %1, and %2 can be left out altogether).

- If you want to override the detailed description of an error message, specify Customer Specific Description. Note that the system does not present detailed descriptions when warnings are shown to users. Therefore, it doesn't make sense to enter this information for a warning message.

For implementation-specific messages, you can use this page as follows:

- Message Text is the same Message Text displayed on the main tab.

CAUTION:

If both Message Text and Customer Specific Message Text are specified, the system will only display the Customer Specific Message Text in the dialog presented to the user.

- Use Detailed Description to define additional information about an error message. Note that the system does not present detailed descriptions when warnings are shown to users. Therefore, it doesn't make sense to enter this information for a warning message.

CAUTION:

If both Detailed Description and Customer Specific Description are specified, the system will only display the Customer Specific Description in the dialog presented to the user.

The Big Picture of Portals and Zones

A portal is a page that is comprised of one or more information zones. The base product pages are built using either a fixed page metaphor or using portals and zones. The contents of this section describe general information about portals and zones.

Next in This Section

- There Are Three Types of Portals

- Common Characteristics of All Portals

- Common Characteristics of Stand-Alone Portals

There Are Three Types of Portals

There are three broad classes of portals:

- Standalone Portal. Standalone portals are separate pages where the main tab of the page is built using a portal. These pages are opened using any of the standard methods (e.g., by selecting a menu item, by selecting a favorite link, etc.). Additional tabs for a stand-alone portal may be included using tab page portals.

- Tab Page Portals. These types of portals cannot be attached to a menu. They simply define the zones for a tab on either a standalone portal or on a “fixed” page. Please contact customer support if you need to add portals to existing transactions.

- Dashboard Portal. The dashboard portal is a portal that appears in the Dashboard Area on the user’s desktop. Its zones contain tools and information that exist on the user's desktop regardless of the transaction.

There is only one dashboard portal. This portal and several zones are delivered as part of the base-package. Your implementation can add additional zones to this portal. Please contact customer support if you need to add zones to the dashboard portal.

Common Characteristics of All Portals

The topics that follow describe characteristics common to all types of portals.

Next in This Section

- Portals Are Made Up of Zones

- Configuring Zones for a Portal

- Granting Access to Zones

Portals Are Made Up of Zones

A portal is a page that contains one or more zones, and each zone contains data of some sort.

All zones reference a Zone Type. The zone type controls the behavior of the zone and the parameters available to configure the zone.

Configuring Zones for a Portal

The portal includes configuration of how the zones should appear on the portal by default. This includes the following options, all of which may be overridden by an implementation.

- The order in which the zone should appear. An implementation may configure an override sequence to change the order zones on a base delivered portal.

- Whether the zone is visible on the portal. Zones delivered in the base product should be configured to be visible. But an implementation may override this if desired.

- Whether the zone should display initially collapsed or not. A zone’s data is only retrieved when it is expanded. As such, a zone may be configured to be initially collapsed when the data is not needed very often. A user can expand the zone when the information is required. Implementations may change the collapsed setting of a base product portal / zone.
Fastpath: Refer to Zones May Appear Initially Collapsed When a Page Opens for more information.

Fastpath: Refer to Defining Portals for more information about this configuration.

In addition, the portal includes configuration to indicate whether or not the portal should appear on a user’s portal preferences. This is typically enabled for a portal that provides disparate information where not all zones are applicable to all users or where users may wish to adjust the order of the zones. An example of a portal enabled for portal preferences is the Dashboard portal. The user can override zone oriented configuration for the portal:

- Which zones appear on that portal

- The order in which the zones appear

- Whether the zones should be initially collapsed when the portal opens.

- The refresh seconds. This is applicable to zones displaying data that changes often.

An implementation can optionally configure the system to define portal preferences on one or more "template" users. When a template user is linked to a "real" user, the real user's preferences are inherited from the "template" user and the "real" user cannot change their preferences. Some implementations opt to work this way to enforce a standard look and feel for users in the same business area.

Fastpath: Refer to User — Portal Preferences for more information about how users configure their zones.

Granting Access to Zones

An application service is associated with each zone. A user must be granted access rights to the respective application service in order to see a zone on a portal.

Fastpath: Refer to The Big Picture Of Application Security for information about granting users access rights to an application service.

Please note the following with respect to zone application security:

- For most base product portals, all the zones for all the portals reference the same application service that is used to grant access to the main (stand-alone) portal for the page. In other words, if the user has access to the page, then he has access to all the zones on all portals for the page. There may be exceptions to this rule for certain portals.

- For a base product multi-query zones, typically the individual query zones and the multi-query zone reference the same application service that is used to grant access to the main (stand-alone) portal for the page. However, there may be individual query zones provided with a unique application service. This may occur when the query option is unusual and not applicable to all users or even to all implementations. If a user does not have security access to an individual query zone, that option will not be available in the dropdown.

- For base product portals that are configured to show on portal preferences, it is common that the portal contains different types of zones that may be applicable to different types of users. Typically these types of portals will deliver a unique application service for each zone so that an implementation may configure which user groups are allowed to view each zone. For these types of portals, please note the following:

- A user's Portal Preferences page contains a row for a zone regardless of whether the user has access rights to the zone. Because of this, the system displays an indication of the user's access rights to each zone.

- If a user's access rights to a zone are revoked, the zone will be suppressed when the user navigates to the respective portal.

- Revoking a user's access rights does not change the user's portal preferences (i.e., a user can indicate they want to see a zone even if they don't have access to the zone - such a zone just won't appear when the respective portal appears).

Note: If you don't need to use zone security. When defining a zone, an application service is required. For zones that don’t require special security, the product provides a “default” application service (F1-DFLTS) that may be used. The expectation is that all user groups are granted access to this application service.

Common Characteristics of Stand-Alone Portals

The topics that follow describe addition characteristics specific to stand-alone portals.

Next in This Section

- Putting Portals on Menus

- Granting Access to A Portal

Putting Portals on Menus

A stand-alone portal should appear as a menu item on one of your menus. The following points provide how to do this:

- Every stand-alone portal has an associated navigation option. You can see a portal's navigation option on the Portal - Main page.

- To add a portal to a menu, you must add a menu item to the desired menu. This menu item must reference the portal's navigation option. There are two ways to add a menu item:

- If the portal's navigation option doesn't currently exist on a menu, you can press the Add To Menu button on the Portal - Main page. When you press this button, you will be prompted for the menu. The system will then create a menu item on this menu that references the portal's navigation option.

- You can always use the Menu page to add, change and delete menu items.

Note: No limit. A portal's navigation option can appear on any number of menu items (i.e., you can create several menu items that reference the same portal.

Note: Favorite links. Your users can set up their preferences to include the portal's navigation option on their Favorite Links. This way, they can easily navigate to the portal without going through menus.

Granting Access to A Portal

An application service is associated with each stand-alone portal. A user must be granted access rights to the respective application service in order to see a portal. Tab portals do not have separate security access. If a user has access to the main stand-alone portal, then the user will have security access to all its tabs. However, as mentioned in Granting Access to Zones, in some scenarios, the individual zones on the portal may have different security access rights depending on the functionality.

Fastpath: Refer to The Big Picture Of Application Security for information about granting users access rights to an application service.

Note: Automatically created. When you add a new stand-alone portal, the system automatically creates an application service behind the scenes. You'll need to know the name of this application service as this is what you use to grant access to the portal. The name of each stand-alone portal's application service is shown on the portal transaction.

Please note the following in respect of how application security impacts a user's portals:

- A user's Portal Preferences page only shows the portals configured to show on user preferences and where they have security access.

- The system's menus only show portals to which a user has security access.

- Users can set up favorite links to all portals, but they must have security rights to the portal's application service in order to invoke the favorite link.

Custom Look and Feel Options

The default look and feel of the application can be customized via feature configuration and cascading style sheets. The base product is provided with a Custom Look And Feel Feature Configuration type. You may want to set up a feature configuration of this type to define style sheet and UI Map help options.

Next in This Section

- User Interface

- UI Map Help

User Interface

The base product allows for the conditional inclusion of custom style sheets into the system style set. Custom styles may override any style provided by the base product. The style sheet may also include new styles for use in customer zone definitions. Use the Style Sheet option on the Custom Look And Feel Feature Configuration to define your custom style sheet.

Note: Some styles cannot change if they are part of the HTML code.

CAUTION:

Implementers must ensure that the customized user interface is stable and scalable. Changing font, alignment padding, border size, and other user interface parameters may cause presentation problems, like scrollbars appearing or disappearing, cursors not working as expected, and unanticipated look and feel alterations of some layouts.

UI Map Help

A tool tip can be used to display additional help information to the user. This applies to section elements as well as individual elements on a map zone or UI Map. Refer to the tips context sensitive zone associated with the UI Map page for more information. The Custom Look And Feel Feature Configuration provides options to control the following:

- Whether UI Map Help functionality is turned on or off. By default it is turned on.

- Override the default help image with a custom image

- The location of the help image, either before or after the element.

Fastpath: Refer to the feature configuration for a detailed description of each option.

Setting Up Portals and Zones

The topics in this section describe how to set up portals and zones. Please refer to The Big Picture of Portals and Zones for background information.

Next in This Section

- Defining Zone Types

- Defining Zones

- Defining Context-Sensitive Zones

- Defining Portals

Defining Zone Types

A Zone Types represents a particular type of zone with a specific behavior. For example, a data explorer zone type is used to select data using a specific SQL statement and display the data based on parameter configuration. The zone type defines the Java Class that controls the behavior of the zone and defines the parameters that the Java Class supports. The base product supports many zone types used to build the portal / zone user interface. Implementations may introduce their own zone types.

Note: It is not very common for an implementation to introduce their own zone types.

Select Admin > System > Zone Type to maintain zone types.

Description of Page

Specify an easily recognizable Zone Type code and Description. Use the Detailed Description to describe in detail what the zone type does.

CAUTION:

When adding new zone types, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Owner indicates if this zone type is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a zone type. This information is display-only.

Java Class Name is the Java class responsible for building the zone using the parameters defined below.

Two types of parameters are specified when defining a zone type:

- Parameter values that have a Usage of Zone are defined on the zones and control the functionality of each zone governed by the zone type. A Usage value of Zone - Override Allowed indicates that an implementation may override the parameter value for a base zone.

- Parameter values that have a Usage of Zone Type are defined directly on the zone type and control how the zone type operates (e.g., the name of the XSL template, the name of the application service). A Usage value of Zone Type - Override Allowed indicates that an implementation may override the parameter value for a base zone type.

The following points describe the fields that are defined for each parameter:

- Sequence defines the relative position of the parameter.

- Parameter Name is the name of the parameter.

- Description is a short description that allows you to easily identify the purpose of the parameter.

- Comments contain information that you must know about the parameter or its implementation. For parameters with a usage of Zone or Zone — Override Allowed, this information is visible to the user when viewing or defining this parameter for a zone of this type.

- Usage indicates whether the parameter value is defined in a Zone of this type or in the Zone Type. Zone - Override Allowed and Zone Type - Override Allowed indicate that override values for the parameters defined in a base zone or base zone type can be entered.

- Required is checked to indicate that a zone must define a value for the parameter. It is not checked if a value for the parameter is optional. This field is protected if the Usage is Zone Type or Zone Type - Override Allowed.

- Parameter Value is used to define the value of zone type parameters. This field is protected if the Usage is Zone or Zone - Override Allowed.

- Owner indicates if this parameter is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a parameter. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_ZONE_HDL.

Zone Type Parameter Comments

For the product owned zone type parameters, the parameter’s detailed description provides the detail needed for properly configuring the parameter. For the Action parameters (IMPLEMENTOR_ACTION_n), the parameter description is abbreviated. Additional detail about configuring this parameter may be found in the Zone Action Parameter detailed information. The same details apply.

Defining Zones

The contents of this section describe how to maintain zones.

Next in This Section

- Zone - Main

- Zone - Portal

- Zone Configuration Topics

Zone - Main

Implementations may use the zone page to define custom zones. In addition, an implementation may override descriptions or some parameter values for base product zones.

Select Admin > System > Zone to create or maintain a zone.

Description of Page

Specify an easily recognizable Zone identifier and Description. Note that if this zone appears on a portal, this description acts as the zone title.

Override Description is provided if your implementation wishes to override the description of the value provided by the product.

CAUTION:

Important! When introducing a new zone, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Owner indicates if this zone is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a zone. This information is display-only.

Zone Type identifies the zone type that defines how the zone functions.

Application Service is the application service that is used to provide security for the zone. Refer to Granting Access To Zones for more information.

The Width defines if the zone occupies the Full width of the portal or only Half.

Note: Zones on the dashboard portal are always the width of the dashboard.

If the zone type supports help text, you can use Zone Help Text to describe the zone to the end-users. Note that for multi-query zones, if the multi-query zone has help text, that is displayed for any zone selected. If the multi-query zone does not have help text, but the selected zone has help text, the selected zone’s help text is displayed. Please refer to the section on zone help text for more information on how you can use HTML and cascading style sheets to format the help text.

Use Override Zone Help Text to override the product provided help text for this zone.

Note: Viewing Your Text. You can press the Test button to see how the help text will look when it's displayed in the zone.

The grid contains the zone's parameter values. The Zone Type controls the list of parameters. The grid contains the following fields:

- Description describes the parameter. This is display-only. Note that if there is a detailed description on the zone type parameter, an icon appears next to the parameter's description. Click the icon to see details related to the parameter, including tips on how to populate the parameter value.

Note: Additional Details for Some Parameters. There are several parameter types that have a lot of detail related to the possible configuration that cannot easily fit into the detailed description. Refer to Zone Parameter Details for additional information about these parameters.

- Parameter Value is the value for the parameter.

- Use Override Parameter Value to override the existing value for this parameter. This field is enabled when the related zone type parameter value is Zone - Override Allowed, and the zone is owned by the base product.

- Owner indicates if this parameter is owned by the base product or by your implementation (Customer Modification). This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_ZONE.

Zone - Portal

Select Admin > System > Zone and navigate to the Portal tab to define the portals on which a zone appears.

Description of Page

The scroll area contains the portals on which the zone appears.

To add a zone to a portal, press the + button and specify the Portal.

Note: Owner indicates if this portal / zone relationship is owned by the base product or by your implementation (Customer Modification). This information is display-only.

Note: You can also add a zone to a portal using Portal - Main. Additional configuration about how the zone appears on the portal is available only on the Portal.

Zone Configuration Topics

The topics in this section provide additional information related to setting up your zones.

Next in This Section

- Zone Help Text

- Zone Parameter Details

- Pagination Configuration

- Use Data Explorer for Derived Data

- Configuring Timeline Zones

Zone Help Text

Most zone types support a button that allows a user to see zone-specific help text, which is defined on the zone page.

You can use HTML tags in the zone help text. The following is an example of help text that contains a variety of HTML tags:

This zone summarizes <font color=blue><b>revenue</b></font> in 4 periods:<br>

The above would cause the word revenue to be bold and blue:

- <b> and </b> are the HTML tags used to indicate that the surrounded text should be bold

- <font color=blue> and </font> are the HTML tags used to indicate that the surrounded text should be blue.

The following are other useful HTML tags:

- <br> causes a line break in a text string. If you use <br><br> a blank line will appear.

- <I> causes the surrounded text to be italicized

Please refer to an HTML reference manual or website for more examples.

You can also use "spans" to customize the look of the contents of a text string. For example, your text string could be <span style="font-family:Courier; font-size:large; font-weight:bold;">revenue</span>. This would make the word "revenue" appear as large, bold, Courier text. Please refer to a Cascading Style Sheets (CSS) reference manual or website for more examples.

The following is an example of help text using a variety of HTML tags:

<font FACE="arial" size=2>

This zone summarizes <font color=blue><b>revenue</b></font> in 4 periods:<br>

- The <b>1st period</b> is under your control. You simply select the desired <b>Period</b>, above <i>(you may need to click the down arrow to expose the filter section)</i><br>

- The <b>2nd period</b> is the period before the 1st period<br>

- The <b>3rd period</b> is the same as the 1st period, but in the previous year<br>

- The <b>4th period</b> is the period before the 3rd period<br>

<br>

The traffic light's color is determined as follows:<br>

- The ratio of the 1st and 3rd period is calculated<br>

- If this value is between 80 and 100, <font color=orange><b>yellow</b></font> is shown<br>

- If this value is < 80, <font color=red><b>red</b></font> is shown<br>

- If this value is > 100, <font color=green><b>green</b></font> is shown<br>

- If the value of the 3rd period is 0, no color is shown<br>

</font>

Note: It is possible to associate tool tip help with individual HTML and UI map elements. For more information, see UI Map Help.

Zone Parameter Details

For most zone parameters, the embedded help for the parameter provides the detailed information needed for configuring the parameter values. For some parameters with very detailed descriptions, the embedded help is abbreviated and more detail is provided here.

Next in This Section

- Zone Visibility Service Script

- SQL Statement

- Column Parameters

- Zone Action

- User Filters

- Hidden Filters

- Multi-Select Action

Zone Visibility Service Script

All zones support a visibility script that is used to determine if the zone should be displayed to the user or not based on conditions. The script may receive input parameters and is expected to return a Boolean value indicating if the zone should be displayed or not. The embedded help for the Zone Visibility Service Script parameter provides details related to the syntax.

The following table highlights some service scripts provided by the product that may be used if applicable to your zone's requirements. This is not an exhaustive list of visibility scripts. There may be others that are specific to a given zone.

Script Code

Description

Comments

F1-ShldShwZn

Zone Visibility - Display Zone in Portal

This script simply returns a value of 'true' and is used when the zone should always appear.

F1-CondShwZn

Zone Visibility - Display Zone in Portal Conditionally

This is used when the condition for showing the zone is based on the population of a context value. This is commonly used when one zone in the portal should only appear after a broadcast of a record from another zone in the portal.

For an example of a zone the uses this visibility script, refer to F1-BSFTYPE .

F1-RwCtShwZn

Zone Visibility - Based on Row Count

This is used when the condition for showing the zone is based on the existence of one or more rows that can be determined using SQL. This script accepts a zone code, user filters 1 through 25 and hidden filters 1 through 10. The script returns an indication of 'true' if at least one row count is returned by the zone.

To use this visibility script, a specific data explorer zone must be developed for the specific use case.

For an example of a zone the uses this visibility script, refer to F1-MIGRREQEL .

SQL Statement

Data explorer zones are used to select data to display using one or more SQL statements. The SQL parameters are applicable to the following zone types

- Info Data Explorer - Single SQL (F1–DE-SINGLE). The parameter has the description SQL Statement.

- Info Data Explorer - Multiple SQLs (F1–DE). The parameters follow the description pattern of SQL Statement x.

- Query Data Explorer - Multiple SQLs (F1–DE-QUERY). The parameters follow the description pattern of SQL Statement x.

Note: If your implementation has been configured to restrict the functions that may be used when defining an SQL then an error is issued at runtime if there are functions found that are not in the whitelist. The whitelist may be viewed using the View SQL function whitelist link in the Tips zone on the zone maintenance page.

The following table provides a list of SQL substituted keywords that may be used in the SQL Statement parameters in explorer zones. At execution time, the system determines the database and substitutes the keyword with the database specific syntax:

Keyword

Description

Examples

@toCharacter()

Converts the input to Character data type.

select @toCharacter(batch_cd) as batchCode from ci_batch_ctrl

@toDate()

Converts the input to Date data type.

select @toDate(last_update_dttm) as lastUpdateDate from ci_batch_ctrl

@toNumber()

Converts the input to Number data type.

select @toNumber(next_batch_nbr) from ci_batch_ctrl

@currentDate

Fetches the current date.

CAUTION:

The Oracle functions SYSDATE and CURRENT_DATE should not be used because they do not properly cater for adjusting dates from the database time zone to the installation time zone, if needed.

select batch_cd, @currentDate as today from ci_batch_ctrl

@currentTimestamp

Fetches the current date / time.

CAUTION:

The Oracle functions SYSTIMESTAMP and CURRENT_TIMESTAMP should not be used because they do not properly cater for adjusting the date / time from the database time zone to the installation time zone, if needed.

select batch_cd from ci_batch_ctrl where last_update_dttm > @currentTimestamp

@concat

Combines the result list of two or more columns.

select batch_cd @concat next_batch_nbr concatNbr from ci_batch_ctrl

@substr(string, start)

String is the input String that you are trying to get a substring of.

Start is the position of the character for the output results.

select batch_cd batchCode from ci_batch_ctrl

Result: TESTCD

select @substr(batch_cd,3) batchCode from ci_batch_ctrl

Result: STCD

@substr(string, start, end)

String is the input String that you are trying to get a substring of.

Start is the position of the character for the output results.

End is the number of characters required in the output from starting position.

Select batch_cd batchCode from ci_batch_ctrl

Result: TESTCD

select @substr(batch_cd,3,2) batchCode from ci_batch_ctrl

Result: ST

@trim

Trims the white spaces of the output on both sides.

select @trim(batch_cd) as batchCode from ci_batch_ctrl

The following syntax is related to ‘fuzzy’ searching. It is only applicable if Oracle DB Text is enabled and a context text index has been created. Refer to Advanced Search Options for more information.

@fuzzy(string, score, numresult, ‘weight’)

String is the input value for the search.

Score is the degree of ‘fuzziness’. Valid values are between 1 - 80. The higher the number the more precise the search. Default is 60.

Numresults is the number of variations to consider for the string. Valid values are between 1 and 5000. Default is 100.

Indicate ‘weight’ to signal that the results are returned in order of weight. Leave this setting off to indicate that the results are returned in order of score.

Set score to 70, number results to 6, and specify weight.

select user_id, last_name from sc_user where contains(last_name, @fuzzy(:F1,70, 6, 'weight')) > 0

@fuzzy(string)

This returns a string result from the fuzzy expansion operation where the default value of 60 is assumed for the score and the default value of 100 is assumed for the numresult.

To use default values:

select user_id, last_name from sc_user where contains(last_name, @fuzzy(:F1))> 0

@fuzzy(string, score)

This returns a string result from the fuzzy expansion operation with the score specified and the default value of 100 for the numresult.

Set score to 70.

select user_id, last_name from sc_user where contains(last_name, @fuzzy(:F1,70)) > 0

@fuzzy(string, score, numresult)

This returns a string resulted from the fuzzy expansion operation with the similarity score and the numresults specified.

Set score to 70, number results to 6.

select user_id, last_name from sc_user where contains(last_name, @fuzzy(:F1,70, 6)) > 0

Column Parameters

Data explorer zones are used to select data to display using one or more SQL statements. For each SQL statement, the zone may configure up to 20 Columns that contain the formatting definition for displaying the output data.

These parameters are applicable to the zone types

- Info Data Explorer - Single SQL (F1-DE-SINGLE). The parameters follow the description pattern of Column x.

- Info Data Explorer - Multiple SQLs (F1-DE). The parameters follow the description pattern of Column x for SQL y.

- Query Data Explorer - Multiple SQLs (F1-DE-QUERY). The parameters follow the description pattern of Column x for SQL y.

The following sections describe the various types of mnemonics.

Contents

Source Mnemonics

Formatting Mnemonics

Click Mnemonics

Source Mnemonics

This table describe the mnemonics that control how the data in a column is derived.

Mnemonic

Description

Valid Values

Comments

source=

Defines how the column's value is derived.

SQLCOL

Indicates that the source of the column's value comes from a column in the SQL statement. This type of column must also reference the sqlcol= mnemonic.

BO

Indicates that the source of the column's value comes from a business object. This type of column must also reference the bo=, input= and output= mnemonics to define how to interact with the business object.

BS

Indicates that the source of the column's value comes from a business service. This type of column must also reference the bs=, input= and output= mnemonics to define how to interact with the business service.

SS

Indicates that the source of the column's value comes from a service script. This type of column must also reference the ss=, input= and output= mnemonics to define how to interact with the service script.

FORMULA

Indicates that the source of this column's value is calculated using a formula. This type of column must also reference the formula= mnemonic.

SETFUNC

Indicates that the source of this column's value is calculated using a superset of values from the rows in the SQL statement. This type of column must also reference the setfunc= mnemonic.

ICON

Indicates that the source of this column's value is a display icon reference (meaning that an icon will be displayed in the column). This type of column must also reference the icon= mnemonic to define the icon reference.

Note: When using this source mnemonic, the formatting mnemonic type= is not applicable.

FKREF

Indicates that the source of this column's value is an FK reference (meaning that the FK reference's context menu and information string will be displayed in the column). This type of column must also reference the fkref= and input= mnemonics to define how the FK reference is called.

Note: When using this source mnemonic, the formatting mnemonic type= is not applicable.

SPECIFIED

Indicates that the source of this column's value is specified by concatenating literals and other column values. This type of column must also reference the spec= mnemonic.

MSG

Indicates that the source of this column is a message from the message table (along with any substitution variables). This type of column must also reference the msg= mnemonic.

sqlcol=

Defines the column in the SQL statement when source=SQLCOL.

COLUMN_NAME

Enter the name of a column that is retrieved in the SELECT statement. Note that if the select statement uses an alias for a column, then the alias should be referenced here.

x

Where x is an integer value that references a column by its relative position in the SELECT statement. For example, sqlcol=3 would display the 3rd column in the SELECT statement).

bo=

Defines the business object to invoke when source=BO.

This mnemonic must be used in conjunction with the input= and output= mnemonics to define how information is sent to / received from the business object.

'Business Object Code'

bs=

Defines the business service to invoke when source=BS.

This mnemonic must be used in conjunction with the input= and output= mnemonics to define how information is sent to/received from the business service.

'Business Service Code'

ss=

Defines the service script to invoke when source=SS.

This mnemonic must be used in conjunction with the input= and output= mnemonics to define how information is sent to / received from the service script.

'Service Script Code'

fkref=

Defines the FK reference used to retrieve the column’s information when source=FKREF.

This mnemonic must be used in conjunction with the input= mnemonic to define how information is sent to the FK reference to build the information.

Cx

This means FK reference code is defined in an earlier column. For example, define C1 if column 1 defines the FK reference value.

COLUMN_NAME

This means the FK reference was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'FK Reference Code'

This means the FK Reference is defined directly. For example 'F1-ROLE'.

formula=

Defines the formula to use when source=FORMULA.

Examples:

- formula=C1*.90/C2

- formula=(C1/C2)*100

The formula can contain numeric constants, operators and column references.

For column references, use the format Cx where x represents the column number.

Refer to Expression Parser for information about the functions supported.

setfunc=

Defines the function to apply to the rows of a given column when source=SETFUNC.

function(Cx)

Where Cx represents a column whose rows should have the function applied and the function is one of the following:

- MAX. This derives the maximum value of all rows in the column.

- MIN. This derives the minimum value of all rows in the column.

- TOT. This derives the sum (total value) of all rows in the column.

- ACC. This derives the cumulative total of all rows up to an including the current row.

input=

This is used to define one or more input fields and values passed to business objects, business services, service scripts, and FK references.

The syntax is as follows: [ELEMENT_NAME=ELEMENT_REF ELEMENT_NAME=ELEMENT_REF ...]

In other words, the list of input values is surrounded by square brackets separated by a space. Each passed value first defines the ELEMENT_NAME, which is the name of the element / field in the target. ELEMENT_REF is the value passed in. The next column indicates the possible values for ELEMENT_REF.

Cx

Where Cx represents the value of a previous column. If the value to pass is in the first column, reference C1.

COLUMN_NAME

This means the value to pass in was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'literal value'

This means a literal value within the single quotes should be passed in.

userTimeZone

This means the current user's time zone should be passed in. This is typically used with the business service F1-ShiftDateTime to convert data in the storage time zone to the user's time zone for display.

installationTimeZone

This means the installation time zone should be passed in. This is typically used with the business service F1-ShiftDateTime to convert data in the storage time zone to the installation time zone for display.

Examples:

- input=[USER_ID=C1]

- input=[USER_ID=USER_ID]

- input=[input/targetTimeZone=userTimeZone]

output=

This is used to define the name of the element retrieved from the business object, business service or service script used to populate this column.

elementName

Example: output=personInfo

pagingkey=

This mnemonic is only applicable when the Enable Paging parameter has been configured. It indicates that this column is one of the keys used by the SQL statement to orchestrate paging through results. This mnemonic can only be specified when the source=SQLCOL.

Fastpath: Refer to Pagination Configuration for more information.

Y

N

This is the default, meaning that you don't need to indicate pagingkey=N at all to indicate that the column is not one of the paging keys.

Note: If multiple columns are configured with the same source BO, BS or SS and the same input data, the system caches the output from the first call and reuses the results for subsequent columns.

Formatting Mnemonics

This table describe the mnemonics that control how a column is formatted.

Mnemonic

Description

Valid Values

Comments

type=

Defines how the column's value is formatted.

Note: Icon and Foreign Key columns. The source= source mnemonic may be used to indicate a column should be derived from an icon reference or a foreign key (FK) reference. If you use either of these sources, the type= mnemonic is not relevant as either an icon or a context menu / info string will appear in the column.

STRING

Columns of this type capture a string. This is the default value.

DATE

Columns of this type capture a date.

TIME

Columns of this type capture a time (in database format) and will be displayed using the user's display profile.

DATE/TIME

Columns of this type capture a date and time (in database format) and will be displayed using the user's display profile.

MONEY

Columns of this type capture a monetary field. This type of column may also reference the cur= mnemonic. If the cur mnemonic is not specified, the currency code on the installation record is used.

NUMBER

Columns of this type capture a numeric field. This type of column may also reference the dec= mnemonic.

label=

Defines the column's override label. The label appears in the column's heading and in the zone's drag and drop area.

If this mnemonic is not defined, the system uses the column's default label. The source of a column's default label differs depending on the column's source. Note that some sources don't have a default value and omitting this mnemonic will result in a blank label.

FIELD_NAME

Enter a valid field name whose label should be used for the column label. This should always be the option used if multiple languages are needed.

'text'

Defines the text directly.

cur=

Defines the currency code applied when type=MONEY if the installation record's currency should not be used.

Cx

This means currency code value is defined in an earlier column. For example, define C1 if column 1 defines the currency code.

COLUMN_NAME

This means the currency code was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'Currency Code'

This means the currency code is defined directly. For example 'USD'.

dec=

Defines the number of decimal places when type=NUMBER.

It is optional. If provided it should be an integer. If not provided, the number of decimals will default to the number of decimal places defined on the currency code specified on the installation record.

nR

Where n is the number of decimal places to show. Suffixing the number of decimal places with R means that the system should round up / down. Simply specifying n (without an R) means that decimal places should be truncated. For example, entering dec=4 will display 4 decimal places and truncate the remainder.

Note: Formatting only. This mnemonic is only used for formatting, it does not impact the precision used for subsequent calculations. For example, if a column retrieved from the database contains 6 significant digits and dec=0, the column will be shown with no decimal places (truncated), however any references to the column in subsequent calculations will use 6 decimal places. For example, if the column is referenced in a formula or set function, all 6 decimal places will be used.

char=

This mnemonic applies special character(s) to the column's value.

'x[]x'

Where x references the literal value to display and [ ] defines the relative position of the characters (before or after the value).

You need only include the [ ] if you want to position characters in front of the value. For example, char='%' will place a percent sign after the value. If you want to position the word 'minutes' before a value, enter char='minutes [ ]'. If you want to output a value like BUDGET $123.12 (YTD), enter char='BUDGET [ ] (YTD)'.

suppress=

This is used to indicate a column should not be displayed.

A column would be suppressed if it's only defined for use by subsequent columns, for example, if there is a formula that derives a column using two other columns. In this scenario, the columns referenced in the formula can be suppressed.

true

false

This is the default, meaning that you don't need to indicate suppress=false at all to indicate that the field should be shown.

suppressSearch=

This is used to indicate a column should not be displayed when the zone is invoked in search mode only.

true

false

This is the default, meaning that you don't need to indicate suppressSearch=false at all to indicate that the field should be shown.

suppressExport=

This is used to indicate a column should not be downloaded to Excel.

true

false

This is the default, meaning that you don't need to indicate suppressExport=false at all to indicate that the field should be included in a download.

width=

This is used to override the width of a column (number of pixels). The default value is the maximum width of any cell in the column.

n

Where n is a number between 0 and 999.

Note:

If there is no available breaking point in the data, the column will be longer than the specified number of pixels.

The length of the column's label (which appears in the column's heading) may also make the width wider than specified.

color=

This is used to override the column's text color.

A valid HTML "named" color

For example color=red or color=yellow.

A valid RGB color model combination

For example color=#FF0000 or color=#CCCCCC. Note that the # is required.

bgcolor=

This is used to override the column's background color.

A valid HTML "named" color

Similar to the color= mnemonic.

A valid RGB color model combination

Similar to the color= mnemonic.

order=

Defines the column's default sort order.

ASC

Indicates that the order is ascending. This is the default meaning that it is not necessary to indicate order=ASC.

DESC

Indicates that the order is descending.

Click Mnemonics

This table describe the mnemonics that define whether a column value may be clicked and if so, what should happen.

Mnemonic

Description

Valid Values

Comments

navopt=

Defines the navigation option that references the target transaction or script when the user clicks a column.

Note, this mnemonic should be used in conjunction with the context= mnemonic to define what information is sent to the navigation option's target transaction.

This mnemonic is ignored if source=FKREF because the FK reference code defines the hyperlink's destination.

Cx

This means navigation option code is defined in an earlier column. For example, define C1 if column 1 defines the navigation option.

COLUMN_NAME

This means the navigation option was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

Example: navopt=MAIN_PORTAL

'Navigation Option Code'

This means the navigation option code is defined directly. For example navopt='userMaint'.

context=

This is used to define one or more context fields and values passed to the target navigation option to go along with the navopt= mnemonic.

The syntax is as follows: [FIELD_NAME=FIELD_REF FIELD_NAME=FIELD_REF ...]

In other words, the list of input values is surrounded by square brackets separated by a space. Each passed value first defines the FIELD_NAME, which is the name of the context field in the navigation option. FIELD_REF is the value passed in. The next column indicates the possible values for FIELD_REF.

Cx

Where Cx represents the value of a previous column. For example, if the value to pass is in the first column, reference C1.

COLUMN_NAME

This means the value to pass in was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'literal value'

This means a literal value within the single quotes should be passed in.

bpa=

Indicates that a BPA script should be executed with the user clicks the column and indicates the BPA to execute.

Note, this mnemonic should be used in conjunction with the tempstorage= mnemonic to define the temporary storage values that will be initiated when the script is executed.

This mnemonic is ignored if source=FKREF because the FK reference code defines the hyperlink's destination.

Cx

Indicates that the BPA script is defined in a previous column.

COLUMN_NAME

This means the BPA script to execute was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'BPA Script Code'

This means that the BPA script to execute is defined directly.

tempstorage=

This is used to define how temporary storage variables are initiated when the bpa= mnemonic is used.

The syntax is as follows: [FIELD_NAME=FIELD_REF FIELD_NAME=FIELD_REF ...]

In other words, the list of input values is surrounded by square brackets separated by a space. Each passed value first defines the FIELD_NAME, which is the name of the field in temporary storage. FIELD_REF is the value passed in. The next column indicates the possible values for FIELD_REF.

Cx

Where Cx represents the value of a previous column. For example, if the value to pass is in the first column, reference C1.

COLUMN_NAME

This means the value to pass in was retrieved by the SELECT statement. The value should match the name defined in the SELECT clause.

'literal value'

This means a literal value within the single quotes should be passed in.

list=

This is used to enable work list capability for this column.

You may optionally populate the listdesc= mnemonic to override the text that will be placed in the worklist zone.

true

Setting list=true will cause the work list icon to appear in the column's header. If a user clicks the column, it will populate all the rows in the output into the work list zone.

Note: In the case of the zone type Info Data Explorer - Multiple SQLs (F1–DE), the output may be showing a union of the results of multiple SQL statements. In this case, if some of the SQL statements configure a given column with list=true, but not all, only the data in the cells for the statements that configure this mnemonic are put into the work list when the user clicks the icon.

listdesc=

This is an optional mnemonic when using the list= mnemonic. It can be used to override the text that is placed in the work list zone.

Cx

Where Cx represents the value of a previous column. For example, if the text to use is in the first column, reference C1.

listbroadcast=

Indicates that the broadcast information for the column is also to be made available in the work list zone. This means that the work list can be used to broadcast information to a portal in the same manner as a data explorer.

true

Use this setting to turn on the feature.

Zone Action

Most zone types provided by the product allow for one or more Zone Actions to be defined to appear in the zone header. An action can appear as a hyperlink, icon or button. The action can also be provided as an HTML string.

Note: Zone types also include parameters for actions defined at the zone type level using IMPLEMENTOR_ACTION_n (Action n) parameters. These are rarely used by the product zone types. The actions defined here override any actions defined on the zone type (if present). The details below apply to the zone type level actions as well.

A zone action is defined using the following mnemonics:

Mnemonic

Description

Valid Values

Comments

type=

This mnemonic defines the appearance of the action in the zone header.

LINK

Indicates that the action is shown as a textual hyperlink.

ICON

Indicates that the action is shown as a graphical icon.

BUTTON

Indicates that the action is shown as an HTML button.

ASIS

Indicates that the parameter will provide the HTML to be used for the action.

action=

This mnemonic defines the action to take when the link/icon/button is clicked. This is ignored when the type=ASIS.

NAVIGATION

Indicates that the action is navigation to a page.

SCRIPT

Indicates that the action is to run a BPA script.

navopt=

Defines the navigation option to use when the action=NAVIGATION.

'NAV_OPT_CD'

Enter a reference to a valid navigation option in single quotes.

bpa=

Defines the script to run when the action=SCRIPT.

'SCRIPT_CD'

Enter a reference to a valid BPA script in single quotes.

icon=

Indicates the icon to use when type=ICON.

DISP_ICON_CD

Enter a reference to a valid display icon.

'path'

Enter an explicit path to the icon, for example 'images/gotoZone.gif'.

asis=

This is required when the type=ASIS. This provides the ability to precisely define the HTML you wish to have included in the header. All valid HTML is permitted including the use of "ora" css classes and JavaScript functions.

['HTML']

label=

By default, the label or tooltip will come from the navigation option or BPA script description. Use this mnemonic to override that label.

FIELD_NAME

Enter a valid field name whose label should be used. This should always be the option used if multiple languages are needed.

'text'

Enter the text directly in single quotes.

context=[target1=source1 target2=source2]

This is used to pass context data when navigating to a page or executing a BPA script. The mnemonic supports passing multiple values.

In each case the target context field or BPA script variable is defined first followed by an equal sign, followed by source data defined using one of the valid values defined in the next column.

One or more values may be defined. Each context value is defined separated by spaces. The whole set of context values should be surrounded by square brackets.

FIELD_NAME

Indicates that the value should be taken from the field with this name from portal context, global context or the page data model. The mnemonic sourceLoc is used for defining the source.

xpath

Indicates that the value should be taken from a schema field, represented by the Xpath, displayed in this zone. This is valid when the zone is displaying a UI Map.

'constant'

Indicates that the value defined in single quotes should be passed.

sourceLoc=

This mnemonic defines the source of the FIELD_NAME's value in the context mnemonic.

If this mnemonic is left blank, the default behavior is as follows:

- The portal context is checked.

- If no portal context value is found, the global context is checked.

- If neither value is available, the field is ignored.

G

Indicates that the field's value is retrieved from the global context.

P

Indicates that the field's value is retrieved from the portal context.

D

Indicates that the field's value is retrieved from the page data model.

class=

Use this mnemonic to override the look and feel of the link / icon / button using a different CSS style.

'className1' 'className2'

Enter one or more classes in single quotes. Multiple class names may be provided.

style=

Use this mnemonic to override the look and feel of the action element using the indicated css style.

Standard style= format.

All allowed css style definitions may be used.

Examples:

- type=BUTTON action=SCRIPT bpa='F1-SET-USER' context=[USER_ID=USER_ID] label=UPDATE_LBL

- type=LINK action=NAVIGATION navopt='gotoUser' context=[USER_ID=path(schema/userdId)]

- type=ASIS asis=['<A class="oraLink" href="www.google.com">Search</a>']

Note: If the zone type has actions defined and there is a desire to simply remove the zone type actions, the Zone Action can be set with the following configuration: type=ASIS asis=[]

User Filters

Data explorer zones include the ability to define User filters to allow a user to enter data to restrict the zone’s rows and / or columns. The filters may be defined individually using User Filter parameters 1–25. Alternatively, a UI map may be defined for capturing filters. In this case, the map's input fields must be associated with the zone's filters by specifying the xpath= mnemonic on the respective User Filter parameters.

These parameters are applicable to the zone types

- Info Data Explorer - Multiple SQLs (F1–DE)

- Query Data Explorer - Multiple SQLs (F1–DE-QUERY)

- Info Data Explorer - Single SQL (F1–DE-SINGLE)

A user filter is defined using the following mnemonics:

Mnemonic

Description

Valid Values

Comments

name=

This mnemonic is used if the zone's filter should be pre-populated with a value from global context, portal context or broadcast from another zone.

MD Field Name

datasource=

This mnemonic defines the source of the filter's pre-populated value defined in the name mnemonic.

If this mnemonic is left blank, the default behavior is as follows:

- If the field has been broadcast from another zone, the broadcast value is used.

- If no value is broadcast, the portal context is checked to determine if this field exists (if so, its value is taken).

- If still no value, the global context is checked.

- If still no value, no default value is shown.

G

Indicates that the zone should look for the filter value in global context.

P

Indicates that the zone should look for the filter value in portal context.

D

Indicates that the zone should look for the filter value in the page data model.

type=

Defines the visual metaphor used to capture the filter values.

DATE

Filters of this type capture a date.

DATE/TIME

Filters of this type capture a date and time.

STRING

Filters of this type capture a string

MONEY

Filters of this type capture a monetary field. This type of filter must also reference the cur mnemonic.

NUMBER

Filters of this type capture a numeric field. This type of filter may also reference the decimals mnemonic.

LOOKUP

Filters of this type capture a lookup value. This type of filter must also reference the lookup mnemonic.

TABLE

Filters of this type capture an administrative table's value (code and description). This type of filter must also reference the table mnemonic.

CHARTYPE

Filters of this type capture predefined characteristic values for a characteristic type (code and description). This type of filter must also reference the chartype mnemonic.

ASIS

Filters of this type capture a list of values to be referenced within an 'IN' clause within the SQL statement.

label=

Defines the filter's label that appears in the zone's description bar and in the input area.

MD Field Name

Enter a valid field name whose label should be used for the filter label. This should always be the option used if multiple languages are needed.

'text'

Defines the text directly.

cur=

Defines the currency code applied when type=MONEY.

Currency Code

Enter a reference to a valid currency code.

dec=

Defines the number of decimal places when type=NUMBER.

Valid number

It is optional. If provided it should be an integer. If not provided, the number of decimals will default to the number of decimal places defined on the currency code specified on the installation record.

lookup=

Defines the lookup flag whose values appear when type=LOOKUP.

Lookup Field Name

Enter a reference to a valid lookup field name.

table=

Defines the admin table whose values appear when type=TABLE.

Table Name

Enter a reference to a valid control table name.

chartype=

Defines the characteristic type code whose values appear when type=CHARTYPE.

Char Type code

Enter a reference to a valid characteristic type code.

xpath=

This mnemonic is used in conjunction with a Filter Area UI Map. For each filter, you must specify the XPath to the corresponding UI map schema element.

XPath

The type= mnemonic must also be appropriate for the map's input field, otherwise the query's SQL could fail.

likeable=

This mnemonic defines if a likeable search is performed on the entered value when type=STRING.

S

The query will add % to the suffix of the filter value.

P

The query will add % to the prefix of the filter value.

PS

The query will add % to the prefix and suffix of the filter value.

divide=

The mnemonic controls if a divider line appears above and/or below the filter.

Note, you can specify this parameter twice if you want divider lines placed above and below a filter, e.g., divide=above divide=below.

above

This results in a divider line placed above the filter.

below

This results in a divider line placed below the filter.

searchField=

This mnemonic controls the initial population of the filter when the zone is launched as a search from a UI map.

MD Field Name

Enter the field name that exactly matches the searchField name specified in the oraSearchField HTML element in the UI map.

encrypt=

This mnemonic defines if the user filter is encrypted and needs to be searched by hashed value.

[TBL_NAME,FLD_NAME,WHERE_FLD,WHERE_VALUE]

Note: The field name referenced here should be the source value of the field. However, the SQL should use the hashed value in its filter.

A valid table name and field name are required.

The WHERE_FLD and WHERE_VALUE are optional, but if entered, both are required. Use this to only encrypt the field if another field has a certain value. The following is an example.

encrypt=[CI_PERSON,PER_ID_NBR,ID_TYPE_NBR,'SSN']. The WHERE_VALUE may also reference another filter. The following is an example.

encrypt=[CI_PERSON,PER_ID_NBR,ID_TYPE_NBR,F1].

Examples:

- label=F1_NBR_DAYS type=NUMBER

- label=F1_SHOW_ALL_REQ_FLG type=LOOKUP lookup=F1_SHOW_ALL_REQ_FLG

- Filter value where a Filter UI Map is defined and Description is one of the filters. type=STRING xpath=description likeable=S

- type=STRING label=DESCR likeable=S divide=below

- label=REQ_TYPE_CD type=TABLE table=F1_REQ_TYPE

Hidden Filters

Data explorer zones include the ability to define Hidden filters to restrict the rows and / or columns that appear in the zone. The following are the potential sources of a hidden filter's value:

- The global area contains the fields whose values are maintained in global context.

- The portal area contains the fields describing the object currently displayed in a portal.

- Other zones on a portal can broadcast information to the portal area, which can then in turn be used by the zone as a hidden filter.

These parameters are applicable to the zone types

- Info Data Explorer - Multiple SQLs (F1–DE)

- Query Data Explorer - Multiple SQLs (F1–DE-QUERY)

- Info Data Explorer - Single SQL (F1–DE-SINGLE)

A hidden filter is defined using the following mnemonics:

Mnemonic

Description

Valid Values

Comments

name=

This mnemonic defines the name of the field that needs to be broadcast from other zones or populated in the portal context

FIELD_NAME

datasource=

This mnemonic defines the source of the hidden filter's value.

If this mnemonic is left blank, the default behavior is as follows:

- If the field has been broadcast from another zone, the broadcast value is used.

- If no value is broadcast, the portal context is checked to determine if this field exists (if so, its value is taken).

- If still no value, the global context is checked.

- If still no value, the zone appears as per the poprule mnemonic.

G

Indicates that the zone should look for the filter value in global context.

P

Indicates that the zone should look for the filter value in portal context.

D

Indicates that the zone should look for the filter value in the page data model.

poprule=

This mnemonic controls what happens if the hidden filter is not present.

R

Indicates that a value for the filter is required. The zone will be set to the "empty state" and the "please broadcast" message will appear in the zone. This is the default value.

O

Indicates that the value is optional. If no value is required, the zone is still built without that value.

type=

Defines the visual metaphor used to capture the filter values.

DATE

Filters of this type capture a date.

DATE/TIME

Filters of this type capture a date and time.

STRING

Filters of this type capture a string

MONEY

Filters of this type capture a monetary field. This type of filter must also reference the cur mnemonic.

NUMBER

Filters of this type capture a numeric field. This type of filter may also reference the decimals mnemonic.

LOOKUP

Filters of this type capture a lookup value. This type of filter must also reference the lookup mnemonic.

TABLE

Filters of this type capture an administrative table's value (code and description). This type of filter must also reference the table mnemonic.

CHARTYPE

Filters of this type capture predefined characteristic values for a characteristic type (code and description). This type of filter must also reference the chartype mnemonic.

ASIS

Filters of this type capture a list of values to be referenced within an 'IN' clause within the SQL statement.

label=

Defines the filter's label that appears in the zone's description bar.

FIELD_NAME

Enter a valid field name whose label should be used. This should always be the option used if multiple languages are needed.

'text'

Defines the text directly.

cur=

Defines the currency code applied when type=MONEY.

CURRENCY_CD

Enter a reference to a valid currency code.

dec=

Defines the number of decimal places when type=NUMBER.

N

It is optional. If provided it should be an integer. If not provided, the number of decimals will default to the number of decimal places defined on the currency code specified on the installation record.

lookup=

Defines the lookup flag whose values appear when type=LOOKUP.

LOOKUP_FIELD_NAME

Enter a reference to a valid lookup field name.

table=

Defines the admin table whose values appear when type=TABLE.

TABLE_NAME

Enter a reference to a valid admin table name.

chartype=

Defines the characteristic type code whose values appear when type=CHARTYPE.

CHAR_TYPE_CD

Enter a reference to a valid characteristic type code.

searchField=

This mnemonic controls the initial population of the filter when the zone is launched as a search from a UI map.

FIELD_NAME

Enter the field name that exactly matches the searchField name specified in the oraSearchField html element in the UI map.

Multi-Select Action

This parameter defines an action to be included in the action area for multi-selection processing. Note that a multi-selection action can only be used if the Multi Select parameter has been set to YES, which causes a checkbox to appear on each row displayed. The action defined here will trigger against all rows selected by the user via the checkbox.

These parameters are applicable to the zone types

- Info Data Explorer - Multiple SQLs (F1–DE)

- Query Data Explorer - Multiple SQLs (F1–DE-QUERY)

- Info Data Explorer - Single SQL (F1–DE-SINGLE)

A multi select action has the following mnemonics:

Mnemonic

Description

Valid Values

Comments

script=

This mnemonic defines the script to be invoked when the action is clicked. This is required.

SCR_CD

Enter a reference to a valid BPA script or Service Script.

type=

This mnemonic defines how the action should be rendered.

BUTTON

The action is rendered as a button. This is the default.

LINK

The action is rendered as hypertext.

ICON

The action is rendered as a graphic icon. For this option, the icon mnemonic is required.

icon=

This mnemonic defines the icon to display when type=ICON.

DISPLAY_ICON_CD

Enter a reference to a valid display icon code.

refresh=

This mnemonic indicates how and if a refresh should occur after the script completes.

NO

Indicates that no refresh is performed. This is the default.

ZONE

Indicates that a refresh of the zone is performed.

PORTAL

Indicates that a refresh of the entire portal is performed.

label=

By default, the button label, link text or icon tooltip will come from the script description. Use this mnemonic to override that label.

FIELD_NAME

Enter a valid field name whose label should be used. This should always be the option used if multiple languages are needed.

'text'

Enter the text directly in single quotes.

list=

When executing the script, the framework builds an XML list containing information from each row selected. This list must be defined in the script's schema and referenced in this mnemonic.

listElementName

Enter a valid list element name from the script schema.

context=[elementName1=rowData1 elementName2=rowData2]

This mnemonic is used to populate the list with the appropriate information from each selected row. The mnemonic supports passing multiple values.

In each case the element in the schema list is defined first followed by an equal sign, followed by information about the data used to populate the element defined using one of the valid values defined in the next column.

One or more values may be defined. Each context value is defined separated by spaces. The whole set of context values should be surrounded by square brackets.

Example of a schema:

<schema>

<accountInfo type="list">

<accountId/>

<name/>

<amount/>

<process/>

</accountInfo>

</schema>

Example of list and context mnemonics.

list=accountInfo

context=[accountId=ACCT_ID name=C2 amount=P3 process='O']

Cx

Indicates that the element should be populated with a value in the referenced column parameter.

Px

Indicates that the element should be populated with a value in the referenced post processing parameter.

COLUMN_NAME

Indicates that the element should be populated with a value from a column in the SQL statement.

'constant'

Indicates that the value defined in single quotes should be passed.

class=

Use this mnemonic to override the look and feel of the action using a different CSS style.

'className1' 'className2'

Enter one or more classes in single quotes to be appended to the standard class(es). Multiple class names may be provided.

style=

Use this mnemonic to override the look and feel of the action element using the indicated css style.

Standard style= format.

All allowed css style definitions may be used.

Pagination Configuration

The various data explorer zones in the product support the ability to configure pagination so that a user can 'page through' a large set of results using "previous" and "next" buttons or links.

There are several zone parameters that are impacted when attempting to configure this functionality. The following steps highlight the configuration.

- The Enable Pagination parameter must be configured to define the basic setup for pagination for the zone. This parameter defines whether the "previous" and "next" actions are defined as buttons, links or icons and indicates the location of the actions. It also allows an indication as to whether the additional rows are simply appended, rather than shown in a new "page". Refer to the parameter's embedded help for information about the specific syntax.

- It is recommended that the zone is configured with record count and page information by properly configuring the Record Count Display parameter. Refer to the parameter's embedded help for information about the specific syntax.

- Configure the Number of Rows to Retrieve for SQL. parameter to define the number of records displayed per page. If this parameter is not specified the value in the Number of Rows to Display parameter is used.

- Configure the key that will be used for paging so that the system can keep track of the 'page break'. The data must be sorted by the paging key; as a result, the decision for identifying the paging key must take into account the design for the zone and the data being displayed. In addition, the paging key must be unique to ensure that the page breaks occur correctly. See below for configuration examples.

- The SQL Statement must includes additional clauses PAGENEXT and PAGEPREV based on the paging key. In addition, as mentioned above, the paging key must be used in the ORDER BY clause.

- The SQL Column parameters must define the paging key mnemonic to be used in conjunction with the SQL statement paging clauses.

- It is recommended to configure the SQL Display Column parameter to show the data in the same order as the ORDER BY clause.

The following zone types support this capability:

- Info Data Explorer - Single SQL (F1–DE-SINGLE).

- Info Data Explorer - Multiple SQLs (F1–DE). Note that zones of this type support a union of the results of all the SQL statements. As a result, pagination may only be enabled for zones of this type if a single SQL is used. The system is not able to keep track of the pagination across disparate SQL statements.

- Query Data Explorer - Multiple SQLs (F1–DE-QUERY).

- Multi Query Data Explorer (F1–DE-MULQRY). Zones of this type do not include configuration for SQL statements or column display. However, they do include configuration for the Enable Pagination. This parameter must be configured in order for pagination on the individual zones to work.

Note: Zones used for a Business Service. Note that pagination is ignored when invoking a data explorer zone via a business service. In this scenario, the zone will return the first "chunk" of rows as defined by the Number of Rows parameters.

Examples

Simple Paging Key

In this example, the Extendable Lookup Value is defined as Column 1 (C1) and is marked as the paging key. This field is unique for the table and works well as a simple paging key.

SELECT A.F1_EXT_LOOKUP_VALUE,A.BUS_OBJ_CD

FROM

F1_EXT_LOOKUP_VAL A,

F1_EXT_LOOKUP_VAL_L B

WHERE

A.BUS_OBJ_CD = :H1

AND A.BUS_OBJ_CD = B.BUS_OBJ_CD

AND A.F1_EXT_LOOKUP_VALUE = B.F1_EXT_LOOKUP_VALUE

AND B.LANGUAGE_CD = :LANGUAGE

[(F1) AND UPPER(A.F1_EXT_LOOKUP_VALUE) like UPPER(:F1)]

[(F2) AND ((UPPER(B.DESCR_OVRD) like UPPER(:F2))

OR (B.DESCR_OVRD = ' ' AND UPPER(B.DESCR) like UPPER(:F2)))]

[(PAGENEXT) AND A.F1_EXT_LOOKUP_VALUE > :C1]

[(PAGEPREV) AND A.F1_EXT_LOOKUP_VALUE < :C1]

ORDER BY A.F1_EXT_LOOKUP_VALUE

Complex Paging Key

Most queries however do not sort by a unique value. In this case, the paging key needs to be set based on the sorting of the query and should include a unique field, such as the primary key, as the last paging key. In this example, the query is showing results sorted by To Do Type, Role and User. All fields, including the To Do Entry ID (the primary key) are marked as paging keys.

SELECT TD_TYPE_CD, ROLE_ID, ASSIGNED_TO, ASSIGNED_DTTM, TD_PRIORITY_FLG, TD_ENTRY_ID

FROM  CI_TD_ENTRY

WHERE

ENTRY_STATUS_FLG IN ('O', 'W')

[(F1) and TD_TYPE_CD = :F1]

[(F2) AND ASSIGNED_TO = :F2]

[(F3) AND ROLE_ID = :F3]

[(PAGENEXT) and ((TD_TYPE_CD>:C1) or (TD_TYPE_CD=:C1 and ROLE_ID>:C2) or (TD_TYPE_CD=:C1 and ROLE_ID=:C2

and ASSIGNED_TO>:C3) or (TD_TYPE_CD=:C1 and ROLE_ID=:C2 and ASSIGNED_TO=:C3 AND TD_ENTRY_ID>:C4))]

[(PAGEPREV) and ((TD_TYPE_CD<:C1) or (TD_TYPE_CD=:C1 and ROLE_ID<:C2) or (TD_TYPE_CD=:C1 and ROLE_ID=:C2

and ASSIGNED_TO<:C3) or (TD_TYPE_CD=:C1 and ROLE_ID=:C2 and ASSIGNED_TO=:C3 AND TD_ENTRY_ID<:C4))]

ORDER BY TD_TYPE_CD, ROLE_ID, ASSIGNED_TO, TD_ENTRY_ID

Use Data Explorer for Derived Data

There are times when a design warrants displaying data in a data explorer zone that is not accessible via SQL. For example, perhaps the data is from another system and it requires a web service call. The JMS Message Browser is another example.

The product provides functionality in the data explorer that allows you to call a script after the user filters are populated but before the SQL is executed. The script can retrieve the data as appropriate, store the data in table format so that the SQL can retrieve the data from the table.

The following points provide more detail:

- Create a service script that retrieves the data as needed. This script should store the retrieved data in a temporary table.

- The product provides a table that may be used. It is called F1_GENERIC_GTT (Generic Global Temporary Table). There is a business service — Create Global Temporary Table Records (F1-InsertGTTRecords) that the service script may call to insert the records.

- Note that if the data is accessed via a web service call, it may be appropriate to execute the web service in a separate session using the business service F1-ExecuteScriptInNewSession to trap errors that may be issued by the web service call and provide a better error.

- In the data explorer zone use this service script in the zone’s pre-processing script parameter. If any user or hidden filters should be passed into the script, the parameter supports mnemonics for this purpose. Refer to the parameter’s embedded help for the supported syntax.

- The SQL for the data explorer should access the temporary table that was populated by the service script.

Configuring Timeline Zones

This topic highlights information related to configuring a timeline zone. The zone type is F1-TIMELINE. A timeline zone contains one or more "lines" where each line shows when significant events have occurred. The output of each line is driven by an algorithm configured on a timeline zone. Each algorithm is responsible for retrieving a single type of data. For example, on algorithm may retrieve bills for an account in a given time period whereas another algorithm may retrieve payments for that account for the same time period.

The algorithms to configure for a timeline zone use the Zone — Timeline plug-in spot. Please note the following details about the behavior for algorithms for this plug-in spot.

- The timeline algorithm receives all the global context values currently populated. In addition, it receives a start and end date from the zone, based on the time period chosen by the user, along with the maximum number of events that can be reasonably display for the chosen time period. The algorithm should use this information to retrieve data for a given type of transaction related to one or more of the input context values for the provided time period.

- For each event found, the algorithm returns information about the event along with many options that assist the user in getting more detail about each event or acting on an event.

- Event date

- Primary key of the record (key / value pairs)

- FK Reference. With this information, the timeline zone will display the appropriate info string to display in the zone’s info area when clicking on the event. In addition, the FK reference identifies the appropriate navigation option to use when a user clicks the info string hypertext to view the record on its maintenance page.

- Background Color and Text Color to use for the event. (Optional). The algorithm may be configured to provide one color for all events or it may be configured to return different colors for different events based on other factors such as status or priority.

- Icon use for the event. (Optional). The algorithm may be configured to provide an icon to display adjacent to the event.

- BPA script to launch when a user clicks on an event. (Optional). The algorithm may return one or more BPA scripts that a user may launch to act on an event. For example, for an event that has a status of Error, perhaps a BPA is provided to walk a user through resolving the error.

When a script is initiated from a timeline, the system puts the prime key of the event into a field in the page data model. The name of the field is the column name(s) of the event's prime key. For example, when a script associated with a payment event is kicked off, the system populates a field called PAY_ID with the prime-key of the selected payment.

Note that your specific edge application may supply algorithm types for a timeline zone as part of the base product. Click here to see the algorithm types available for this plug-in spot. Although algorithm types may be provided, typically the product does not deliver algorithms because the parameters for the algorithms are driven by a particular implementation’s business rules and preferences. As a result, the product will also not deliver pre-configured timeline zones. Please refer to your edge application’s documentation for more information about what timeline algorithm types are delivered, if any and recommendations for configuration.

Defining Context-Sensitive Zones

A context-sensitive zone allows you to associate a zone with a specific user-interface transaction. A context-sensitive zone appears at the top of the Dashboard when a user accesses a page for which the zone is specified as the context. For example, when viewing a business object, additional zones are visible that are specific to the business object page.

CAUTION:

Make sure that the zone is appropriate for the transaction on which you are specifying it. For example, if your zone requires a business object ID as one of its keys, it should not be displayed on the To Do entry transaction.

Select Admin > Context Sensitive Zone to maintain context-sensitive zones.

Description of Page

The Navigation Key is a unique identifier of a tab page within the system. Owner indicates if this navigation key is owned by the base product or by your implementation (Customer Modification).

CAUTION:

Important! When introducing a new context sensitive zone, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

The grid contains the list of context-sensitive zones and the sequence in which they appear in the dashboard for the selected navigation key. The grid contains the following fields:

- Zone is the name of the zone to display in the Dashboard.

- Sequence is the sequence in which the zone is displayed (if multiple context-sensitive zones are defined).

- Owner indicates if this context sensitive zone is owned by the base product or by your implementation (Customer Modification).

Where Used

A context-sensitive zone displays at the top of the Dashboard whenever a user accesses the transaction for with the zone is specified.

Defining Portals

This transaction is used to define / change portals. An implementation may define their own portals. In addition, an implementation may override some of the settings for base product provided portals.

Next in This Section

- Portal - Main

- Portal - Options

Portal - Main

Navigate to this page using Admin > System > Portal.

Description of Page

Enter a meaningful and unique Portal code and Description. Please be aware that for stand-alone portals, the Description is the portal's title (i.e., the end-users will see this title whenever they open the portal).

CAUTION:

Important! When introducing a new portal, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Owner indicates if this portal is owned by the base product or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a portal. This information is display-only.

Type flag indicates whether the portal is a Standalone Portal, a Tab Page Portal or the Dashboard. Refer to There Are Three Types of Portals for more information.

The following fields are only enabled for Standalone Portals:

- Navigation Option defines the navigation option that is used to navigate to this portal from menus, scripts and your favorite links. The navigation option is automatically created when a Standalone Portal is added.

- You'll find an Add To Menu button adjacent. This field is only enabled if the navigation option is not referenced on a menu. When you click this button, a pop-up appears where you define a menu. If you subsequently press OK, a menu item is added to the selected menu. This menu item references the portal's navigation option. You can reposition the menu item on the menu by navigating to the Menu page.
Refer to Putting Portals on Menus for more information.

- Application Services defines the service used to secure this portal. The application service is automatically created when a Standalone Portal is added. Please note that only users with access to this application service will be able to view this portal and its zones. Refer to Granting Access to A Portal for more information.

- Show on Portal Preferences indicates if a user is allowed to have individual control of the zones on this portal. The portal will not appear in the accordion on the user's Portal Preferences page if this value is set to No. Note that an implementation may change this value for a product delivered portal.

The grid contains a list of zones that are available in the portal. Click + to add a new zone to the portal. Click - to remove a zone from the portal. The grid displays the following fields:

- Zone is the name of the zone as defined on the Zone page.

- Description is a description of the zone as defined on the Zone page.

- Display controls whether or not the zone is visible in the portal. For portals that are configured to Show on Portal Preferences, users may override this value for their view of the portal.

- Initially Collapsed controls whether or not the zone is initially collapsed in the portal. For portals that are configured to Show on Portal Preferences, users may override this value for their view of the portal.
Note: Recommendation. It is recommended that zones that have information that is always needed when users first display a portal be set up to be initially collapsed. That way the data in the zone is only built when the user expands the zone. This improves response times.

- Default Sequence is the default sequence number for the zone within the portal. It does not need to be unique within the portal. Note that a sequence of zero will appear last, not first, in the portal. For portals that are configured to Show on Portal Preferences, users may override this value for their view of the portal.

- Override Sequence can be used by an implementation team to override the Default Sequence value that is set in the base product.

- Refresh Seconds defines in seconds how often the zone is automatically refreshed. The minimum valid value is 15. The maximum valid value is 3600 (1 hour). A value of 0 indicates no automatic refresh. Implementers can change this value as needed.

- Owner indicates if this portal / zone relationship is owned by the base product or by your implementation (Customer Modification). This information is display-only.

Note: Removing zones from a portal. You cannot remove a base product zone from a base product portal. An implementation may override the Display setting to prevent a zone from displaying on the portal. In addition, you cannot remove a zone if a user has enabled it on their Portal Preferences. To remove a zone from the portal list, first make sure that no user has it enabled in their portal preferences.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_PORTAL.

Portal - Options

Use this page to maintain a portal's options. Open this page using Admin > System > Portal and then navigate to the Options page.

Description of Page

The options grid allows you to configure the options that provide additional information related to the portal.

Select the Option Type dropdown to define its Value. Detailed Description may display additional information on the option type.

Set the Sequence to a unique value within a given option type.

Owner indicates if this is owned by the base product or by your implementation (Customer Modification).

Note: You can add new option types. Your implementation may want to add additional portal option types. To do that, add your new values to the customizable lookup field PORTAL_OPT_FLG.

Defining Display Icons

Icons are used to assist users in identifying different types of objects or instructions. A limited number of control tables allow administrative users to select an icon when they are configuring the system. Select Admin > System > Display Icon Reference to maintain the population of icons available for selection.

Description of Page

Each icon requires the following information:

- Display Icon is a code that uniquely identifies the icon.

- Icon Type defines how big the icon is (in pixels). The permissible values are: 30 x 21, 21 x 21, and 20 x 14. Note that only icons that are 20 x 14 can be used on base product instructions.

- Description contains a brief description of the icon.

- URL describes where the icon is located. Your icons can be located on the product's web server or on an external web server.

- To add a new icon to the product web server, place it under the /cm/images directory under the DefaultWebApp. Then, in the URL field, specify the relative address of the icon. For example, if the icon's file name is myIcon.gif, the URL would be /cm/images/myIcon.gif.

- If the icon resides on an external web server, the URL must be fully qualified (for example, http://myWebServer/images/myIcon.gif).

- Owner indicates if this icon is owned by the base product or by your implementation (Customer Modification). This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_DISP_ICON.

Defining Navigation Keys

Each location to which a user can navigate (e.g., transactions, tab pages, tab menus, online help links, etc.) is identified by a navigation key. A navigation key is a logical identifier for a URL.

Next in This Section

- Navigation Key Types

- Navigation Key vs. Navigation Option

- The Flexibility of Navigation Keys

- Linking to External Locations

- Overriding Navigation Keys

- Maintaining Navigation Keys

Navigation Key Types

There are three types of navigation keys:

- System navigation keys define locations where the target for the navigation is a transaction or portal within the system. The navigation keys define the program component that identifies the page to navigate to.

- External navigation keys define a URL that identifies the target location. External URLs can be specified as relative to the product web server or fully qualified. External navigation keys always launch in a new instance of a browser window. Examples of external navigation keys include application viewer links and URLs to external systems.

- Help navigation keys define a online help topic that identifies the specific page within the online help to launch. Help navigation keys may be related to a program component when the help is related to a specific page in system.

Navigation Key vs. Navigation Option

The system has two entities that work in conjunction with each other to specify how navigation works:

- Navigation Key defines a unique location to which a user can navigate. For example, each page in the system has a unique navigation key. Navigation keys can also define locations that are "outside" of the system. For example, you can create a navigation key that references an external URL. Think of a navigation key as defining "where to go".

- Navigation Option defines how a page is opened when a user wants to navigate someplace. For example, you might have a navigation key that identifies a specific page. This navigation key can then be referenced on two navigation options; the first navigation option may allow users to navigate to the page with no context included, while the second navigates to the page with context data provided to automatically display information related to that context.

- Please note that a wide variety of options can be defined on a navigation option. In addition to defining if data is passed to the page, it could also define search options. In addition, there are some navigation options that do not reference a navigation key but rather refer to a BPA script that should be launched.

The Flexibility of Navigation Keys

Navigation keys provide a great deal of functionality to your users. Use navigation keys to:

- Allow users to navigate to new pages or search programs

- Allow users to transfer to an external system or web page. After setting up this data, your users may be able to access this external URL from a menu, a context menu, their favorite links, etc. Refer to Linking to External Locations for more information.

Refer to the Tool Suite Guide for more information on developing program components.

Note: Replacing Base-Package Pages or Searches. If your new page or search has been designed to replace a module in the base-package, the navigation key must indicate that it is overriding an existing navigation key.

Linking to External Locations

If you want to include links to external systems or locations from within the system, you need to:

- Define a navigation key that specifies the URL of the location. For example, define an external navigation key that as a URL of http://www.oracle.com/.

- Define a navigation option that specifies from where in the system a user can go to your external location. For example, define a navigation option with a usage of Favorites or with a usage of Menu. Your navigation option points to the navigation key you defined above.

- Add your navigation option to the appropriate location within the system. For example, have users add the navigation option to their Favorite Links or add the navigation option as an item on a menu.

Overriding Navigation Keys

Your implementation may choose to design a program component (e.g., a maintenance transaction or search page) to replace a component provided by the system. When doing this, the new navigation key must indicate that it is overriding the system navigation key. As a result, any menu entry or navigation options that reference this overridden navigation key automatically navigates to the custom component.

For example, if you have a custom On-line Batch Submission page and would like users to use this page rather than the one provided by the system, setting up an override navigation key ensures that if a user chooses to navigate to the On-line Batch Submission from Menu or a context menu, the user is brought to the custom On-line Batch Submission page.

To create an override navigation key, you need to:

- Define a navigation key using an appropriate naming convention.

- If the Navigation Key Type of the navigation key being overridden is External, specify a Navigation Key Type of Override (Other) and define the appropriate URL Component.

- If the Navigation Key Type of navigation key being overridden is System, specify a Navigation Key Type of Override (System) and populate the Program Component ID with your custom program component ID.

- Specify the navigation key that you are overriding in the Overridden Navigation Key field.

Refer to the Tool Suite Guide for more information about developing your own program components.

Maintaining Navigation Keys

Select Admin > System > Navigation Key to maintain navigation keys.

CAUTION:

Important! When introducing a new navigation key, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Description of Page

The Navigation Key is a unique name of the navigation key for internal use.

Owner indicates if this navigation key is owned by the base product or by your implementation (Customer Modification). This information is display-only.

Navigation Key Type includes the following possible values:

- External indicates that the location is specified in the URL Component field.

- Help indicates that the navigation key is used to launch online help where the specific help topic is defined in the URL Component field.

- Override (Other) indicates that the navigation key overrides another navigation key of type External or Help. For this option, the name of the navigation key being overridden is populated in the Overridden Navigation Key field.

- Override (System) indicates that the navigation key overrides a system navigation key. For this option, the name of the navigation key being overridden is populated in the Overridden Navigation Key field.

- System indicates that the navigation key refers to a transaction in the system identified by its program component.

Fastpath: Refer to Navigation Key Types for more information about navigation key types.

Fastpath: Refer to Overriding Navigation Keys for more information about settings required to override a system navigation key.

Program Component ID is the name of the program component identified by the key (for system navigation keys). The program component ID can also be used to specify the transaction with which an online help link is associated.

Overridden Navigation Key is the name of the navigation key that the current navigation key is overriding (if Override (Other) or Override (System) is selected for the Navigation Key Type). Refer to Overriding Navigation Keys for more information.

URL Component is the specific URL or portion of the URL for the navigation key (external and help navigation keys only). The URL can be relative to the product web server or fully qualified.

Open Window Options allows you to specify options (e.g., width and height) for opening a browser window for an external navigation key. (External navigation keys always launch in a new browser window.) You can use any valid features available in the Window.open( ) JavaScript method. The string should be formatted the same way that it would be for the features argument (e.g., height=600,width=800,resizeable=yes,scrollbars=yes,toolbar=no). Refer to a JavaScript reference book for a complete list of available features.

Application Service is the application service that is used to secure access to transactions associated with External navigation keys. If a user has access to the specified application service, the user can navigate to the URL defined on the navigation key. Refer to The Big Picture of Application Security for more information.

The grid displays menu items that reference the navigation key (actually, it shows menu items that reference navigations options that, in turn, reference the navigation key).

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_MD_NAV.

Defining Navigation Options

Every time a user navigates to a transaction, the system retrieves a navigation option to determine which transaction should open. For example:

- A navigation option is associated with every menu item. When a user selects a menu item, the system retrieves the related navigation option to determine which transaction to open.

- A navigation option is associated with every favorite link. When a user selects a favorite link, the system retrieves the related navigation option to determine which transaction to open.

- A navigation option is associated with every node in the various trees. When a user clicks a node in a tree, the system retrieves the related navigation option to determine which transaction to open.

- Etc.

Many navigation options are shipped with the base product and cannot be modified as these options support core functionality. As part of your implementation, you may add additional navigation options to support your specific business processes.

Navigation options may also be used to launch a BPA script.

The topics in this section describe how to maintain navigation options.

CAUTION:

In order to improve response times, navigation options are cached the first time they are used after a web server is started. If you change a navigation option and you don't want to wait for the cache to rebuild, you must clear the cached information so it will be immediately rebuilt using current information. A special button has been provided on the Main tab of the navigation option transaction that performs this function. Please refer to Caching Overview for information on the various caches.

Next in This Section

- Navigation Option - Main

- Navigation Option - Tree

Navigation Option - Main

Select Admin > System > Navigation Option to maintain a navigation option.

Description of Page

Enter a unique Navigation Option code and Description.

CAUTION:

When introducing a new navigation option, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

The Flush System Login Info button is used to flush the cached navigation options so you can use any modified navigation options. Refer to Caching Overview for more information.

Owner indicates if this navigation option is owned by the base product or by your implementation (Customer Modification). This field is display-only. The system sets the owner to Customer Modification when you add a navigation option.

Note: You may not change navigation options that are owned by the base product.

Use Navigation Option Type to define if the navigation option navigates to a Transaction, launches a BPA Script or opens an Attachment.

Note: The Attachment option type is only applicable to navigation options that are used to launch a file attached to a record in the Attachment maintenance object.

For navigation option types of script, indicate the Script to launch. You can use the Context Fields at the bottom of the page if you want to transfer the contents of specific fields to temporary storage variables available to the script. The script engine creates temporary storage variables with names that match the Context Field names.

For navigation option types of transaction, define the Target Transaction (navigation key) and optionally a specific Tab Page (also a navigation key) if a specific tab on the transaction (other than the Main tab) should be opened when navigating to that transaction.

Note: Finding transaction navigation keys. When populating the Target Transaction and Tab Page you are populating an appropriate navigation key. Because the system has a large number of transactions, we recommend using the "%" metaphor when you search for the transaction identifier. For example, if you want to find the currency maintenance transaction, enter "%currency" in the search criteria.

The additional information depends on whether the target transaction is a fixed page or a portal-based page:

- For portal-based pages:

- Navigation Mode is not applicable and should just be set to Add Mode.

- If navigating to a query portal, by default the query portal will open with the default search option defined. If the navigation should open a different search option, define the Multi-Query Zone for that query portal and indicate the Sub-Query Zone to open by default. Note that for this configuration, it is common to define Context Fields to pre-populate search criteria in the target query zone. When using this configuration, be sure that the target query zone’s user filters are defined to populate data from context.

- For fixed pages:

- Navigation Mode indicates if the Target Transaction should be opened in Add Mode or Change Mode.

- Add Mode should be used if the option is used to navigate to a transaction ready to add a new object. You can use the Context Fields at the bottom of the page if you want to transfer the contents of specific fields to the transaction when it opens.

- Change Mode is only applicable for fixed pages and should be used if the option is used to navigate to a transaction ready to update an object. You have two ways to define the object to be changed:

- Define the name of the fields that make up the unique identifier of the object in the Context Fields (and make sure to turn on Key Field for each such field).

- Define the Search Transaction (navigation key) if you want to open a search window to retrieve an object before the target transaction opens. Select the appropriate Search Type to define which search method should be used. The options in the drop down correspond with the sections in the search (where Main is the first section, Alternate is the 2nd section, Alternate 2 is the 3rd section, etc.). You should execute the search window in order to determine what each section does.

When you select a Search Type, define appropriate Context Fields so that the system will try to pre-populate the search transaction with these field values when the search first opens. Keep in mind that if a search is populated with field values the search is automatically triggered and, if only one object is found that matches the search criteria, it is selected and the search window closes.

- Search Group is only visible if the Development Tools module is not turned off. It is used to define the correlation between fields on the search page and the tab page. You can view a tab page's Search Groups by viewing the HTML source and scanning for allFieldPairs.

The Go To Tooltip is used to specify the label associated with the tool tip that appears when hovering over a Go To object. Refer to the Usage grid below.

The Usage grid defines the objects on which this navigation option is used:

- Choose Favorites if the navigation option can be used as a favorite link.

- Choose Menus if the navigation option can be used as a user's home page or as a menu or context menu item.

- Choose Script if the navigation option can be used in a script.

- Choose Foreign Key if the navigation option can be used as a foreign key reference.

- Choose Go To if the navigation option can be used as a "go to" destination ("go to" destinations are used on Go To buttons, tree nodes, and hyperlinks).

- If your product supports marketing campaigns, you can choose Campaign if the navigation option can be used as a "post completion" transaction on a campaign. For more information refer to that product's documentation for campaigns.

The Context Fields grid contains the names of the fields whose contents will be passed to the Target Transaction or Script or used to launch an Attachment. The system retrieves the values of these fields from the "current" page and transfers them to the target transaction or to the script's temporary storage. Turn on Key Field for each context field that makes up the unique identifier when navigating to a transaction in Change Mode.

Note: For an Attachment, the grid should contain the Attachment ID.

Note: Navigating from a Menu. The standard followed for many base main menu navigation options for fixed transactions is that navigation options launched from the Menu dropdown are configured with no context.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_NAV_OPT.

Navigation Option - Tree

This page contains a tree that shows how a navigation option is used. Select Admin > System > Navigation Option and navigate to the Tree tab to view this page.

Description of Page

The tree shows every menu item, favorite link, and tree node that references the navigation option. This information is provided to make you aware of the ramifications of changing a navigation option.

Database Tools

This section describes a variety of database tools that are supplied with the your product.

Next in This Section

- Defining Table Options

- Defining Field Options

- Defining Maintenance Object Options

- Defining Valid Values

- The Big Picture Of Audit Trails

- Bundling

- Revision Control

- Information Lifecycle Management

Defining Table Options

The topics in this section describe the transaction that allows you to define metadata for the application's tables.

Next in This Section

- Table - Main

- Table - Table Field

- Table - Constraints

- Table - Referred by Constraints

Table - Main

Navigate using Admin > Database > Table.

Description of Page

Table Name is the identifier of this table.

Description contains a brief description of the table.

System Table defines if the table includes rows that are owned by the base product.

Enable Referential Integrity defines if the system performs referential integrity validation when rows in this table are deleted.

Data Group ID is used for internal purposes.

Enable Data Dictionary defines if the table is to be included in the Data Dictionary application viewer.

Table Type defines if the table is an External Table, a View or a physical Table.

Date / Time Data Type defines if the system shows times on this table in Local Legal Time or in Local Standard Time Local Legal Time is the time as adjusted for daylight savings / summer time.

Table Classification Type specifies the category of data the table will hold. This is for information purposes only and is not used by any system processing. Valid values are Admin System Table, Admin Non System Table, Master Table, Transaction Table, and Unclassified.

Table Volume Type specifies the expected amount of data the table will hold. This is for information purposes only and is not used by any system processing. Valid values are High Volume, Low Volume, Medium Volume, and Unclassified. The volume of data in a particular table in the system may differ greatly from one implementation to another based on unique business requirements. The values populated for base product tables are set to volumes that are typical but may not be true for a given implementation. The value may be updated to reflect the situation for a given implementation.

Audit Table is the name of the table on which this table's audit logs are stored if using the legacy table / field audit technique. Refer to The Audit Trail File for more information.

Use Audit Program Type to define if the audit program is written in Java or Java (Converted), meaning it was converted into Java.

Note: Java (Converted) program types are not applicable to all products.

Audit Program is the name of the program that is executed to store an audit log. Refer to Turn On Auditing For a Table for more information.

Note: View the source. If the program is shipped with the base package, you can use the adjacent button to display the source code of this program in the Java docs viewer.

Upgrade controls what happens to the rows in this table when the system is upgraded to a new release:

- Keep means that the rows on this table are not touched during an upgrade

- Merge means that the rows on this table are merged with rows owned by the base product

- Refresh means that the rows on this table are deleted and refreshed with rows owned by the base product.

Data Conversion Role controls if / how the table is used by the conversion tool:

- Convert (Retain PK) means that the table's rows are populated from the conversion schema and the prime key in the conversion schema is used when the rows are converted. A new key is not assigned by the system.

- Convert (New PK) means that the table's rows are populated from the conversion schema and the prime key is reassigned by the system during conversion.

- Not Converted means that the table's rows are not managed by the conversion tool.

- View of Production means that the conversion tool uses a view of the table in production when accessing the rows in the table. This is commonly used for administrative tables.

A Language Table is specified when fields containing descriptions are kept in a child table. The child table keeps a separate record for each language for which a description is translated.

A Characteristic Entity is populated if this table is used to capture characteristics and indicates the associated characteristic entity lookup value for this table. When defining characteristic types, you indicate the characteristic entities where that characteristic type is applicable / valid.

A Key Table is specified when the prime-key is assigned by the system. This table holds the identity of the prime keys allocated to both live and archived rows.

Type of Key specifies how prime key values are generated when records are added to the table:

- Other means a foreign-system allocates the table's prime-key.

- Sequential means a sequence number is incremented whenever a record is added to the table. The next number in the sequence determines the key value.

- System-generated means a program generates a random key for the record when it is added. If the record's table is the child of another table, it may inherit a portion of the random number from its parent's key.

- User-defined means the user specifies the key when a record is added.

Inherited Key Prefix Length defines the number of most significant digits used from a parent record's primary key value to be used as the prefix for a child record's key value. This is only specified when the Type of Key is System-generated and the high-order values of the table's key is inherited from the parent table.

Note: In general, randomly generated system keys are used to attempt to evenly distribute records across a full range of possible IDs. Batch programs that use multiple threads will typically divide the threads using ID ranges and evenly distributed keys will help spread out the work. The reason for inherited keys for child records further extends the performance benefit. When considering partitioning, the recommendation for DBAs is to range partition data based on the primary key so that different batch threads operate on different partitions which reduces contention for hot blocks. Ideally the number of batch threads will be an exact multiple of the number of partitions. Batch programs that insert child data (for example batch Billing creation) also benefit from this design especially when the child tables are partitioned in the same way. The parent is often the driver of the batch process. If this is multi-threaded, then each thread is processing a set of parent records in a given ID range and all child records are being inserted into the same ID range.

Java Table Name. This field is used to identify the entity/Java class name of the class that represents the table in the Java code. It should contain a short "camelCased" name to be used as the name of the entity within the system. It must also be a valid Java name, and must be unique across the system. This name is used as follows:

- As the short class name on all classes in the Java hierarchy for the class: the Impl class, the Gen, and the interface.

- In HQL queries, it is used to identify the hibernate entity being selected.

Caching Regime determines if the table’s values should be cached when they are accessed by a batch process. The default value is Not Cached. You should select Cached for Batch if you know the values in the table will not change during the course of a batch job. For example, currency codes will not change during a batch process. Caching a table's values will reduce unnecessary SQL calls and improve performance.

Key Validation determines if and when keys are checked for uniqueness. The default value is Always Check Uniqueness. Select Check Uniqueness Online Only when the database constructs the keys in the table, such as in log tables. Select Never Perform Uniqueness Checking when you know that the database constructs the keys in the table and that users cannot add rows directly to the table, such as in log parameter tables. This will reduce unnecessary SQL calls and improve performance.

Help URL is the link to the user documentation that describes this table.

Help Text contains additional information about the table.

Extract for Translation is only visible in a development environment. It indicates whether or not the table includes strings that are eligible for product translation.

Translation Context is only visible in a development environment. It is used to provide information to a translator about the nature and purpose of rows in the table.

Note: Changes to base owned tables. Only the following attributes of tables that are owned by the product are modifiable: Audit Table, Audit Program Type, Audit Program, Caching Regime, Key Validation and Table Volume Type.

The grid contains an entry for every field on the table. Drilling down on the field takes you to the Table Field tab where you may modify certain attributes. The following fields may also be modified from the grid: Description, Override Label, Audit Delete, Audit Insert and Audit Update. Refer to the Table Field tab for descriptions of these fields.

Table - Table Field

Navigate using Admin > Database > Table and click the Table Field tab.

Description of Page

Field Name is the name of the field. It is followed by its Java Field Name.

Field Help Text displays the help text listed for this field on the Field page, if populated.

Nullable, Required and Validate are for internal use.

Turn on Audit Delete if an audit record should be stored for this field when a row is deleted. Refer to How To Enable Auditing for more information.

Turn on Audit Insert if an audit record should be stored for this field when a row is added. Refer to How To Enable Auditing for more information.

Turn on Audit Update if an audit record should be stored for this field when it is changed. Refer to How To Enable Auditing for more information.

The Allow Customization is only applicable if the table is an Admin System Table. It indicates fields that an implementation is allowed to change for a base owned record. Changes to the field value of one of these types of fields by an implementation are maintained when upgrading to a new version of the product.

Standard Time Type is only enabled if the Table indicates that the Date/Time Data Type is Local Standard Time. Each field that represent date/time should define if it uses Logical Standard Time, Physical Standard Time or uses a Referenced Time Zone.

Sequence is a unique sequence of this field with respect to other fields on the table.

The Label column is used to define a special label for this field when it relates to this table if it should be different from the field’s label. Note that this only impacts the label on a fixed page user interface. Labels on portal based user interfaces do not use this information.

The Override Label is provided if an implementation wants to override the base-product label.

Note: If you want the Override Label to be shown in the data dictionary, you must regenerate the data dictionary.

Help Text contains any additional information about the field with respect to its use on this table.

Extract for Translation is only visible in a development environment. For tables marked to extract for translation, each translatable field on the table should indicate Yes.

Translation Context is only visible in a development environment. It is used to provide information to a translator about the nature and purpose of the data in this field on this table.

Note: Changes to base owned table / fields. Only the following attributes of table / fields that are owned by the product are modifiable: Audit Delete, Audit Insert, Audit Update, Override Label.

Table - Constraints

Select Admin > Database > Table and navigate to the Constraints tab to view the constraints defined on the table.

Description of Page

The fields on this page are protected as only the product development group may change them.

This page represents a collection of constraints defined for the table. A constraint is a field (or set of fields) that represents the unique identifier of a given record stored in the table or a field (or set of fields) that represents a given record's relationship to another record in the system.

Constraint ID is a unique identifier of the constraint.

Owner indicates if this is owned by the base package or by your implementation (Customer Modification)

Constraint Type Flag defines how the constraint is used in the system:

- Primary Key represents the field or set of fields that represent the unique identifier of a record stored in a table.

- Logical Key represents an alternate unique identifier of a record based on a different set of fields than the Primary key.

- Foreign Key represents a field or set of fields that specifies identifying and non-identifying relationships to other tables in the application. A foreign key constraint references the primary key constraint of another table.

- Conditional Foreign Key represents rare relationships between tables where a single field (or set of fields) may reference multiple primary key constraints of other tables within the application as a foreign key.

When Enable Referential Integrity is checked, the system validates the integrity of the constraint when a row in the table is modified.

Referring Constraint Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

Referring Constraint ID is the Primary Key constraint of another table whose records are referenced by records stored in this table.

Referring Constraint Table displays the table on which the Referring Constraint ID is defined. You can use the adjacent go-to button to open the table.

Additional Conditional SQL Text is only specified when the constraint is a Conditional Foreign Key. The SQL represents the condition under which the foreign key represents a relationship to the referring constraint table.

Note: Additional Conditional SQL Syntax. When specifying additional conditional SQL text, all table names are prefixed with a pound (#) sign.

The Constraint Field grid at the bottom of the page is for maintaining the field or set of fields that make up this constraint.

Field is the name of the table's field that is a component of the constraint.

Sequence The rank of the field as a component of the constraint.

The Referring Constraint Field grid at the bottom of the page displays the field or set of fields that make up the Primary key constraint of the referring constraint.

Field is the name of the table's field that is a component of the referring constraint.

Sequence is the rank of the field as a component of the referring constraint.

Table - Referred by Constraints

Select Admin > Database > Table and navigate to the Referred By Constraints tab to view the constraints defined on other tables that reference the Primary Key constraint of this table.

Description of Page

This page is used to display the collection of constraints defined on other tables that reference the table.

Referred By Constraint Id is the unique identifier of the constraint defined on another table.

Referred By Constraint Owner indicates if this constraint is owned by the base package or by your implementation (Customer Modification).

Prime Key Constraint Id is the Primary Key constraint of the current table.

Prime Key Owner indicates if this prime key is owned by the base package or by your implementation (Customer Modification).

Referred By Constraint Table is the table on which Referred By Constraint ID is defined.

When Enable Referential Integrity is checked, the system validates the integrity of the constraint when a row in the table is modified.

The grid at the bottom of the page displays the Field and Sequence for the fields that make up the constraint defined on the other table.

Defining Field Options

The topics in this section describe the transaction that can be used to view information about a field and to change the name of a field on the various pages in the system.

Next in This Section

- Field - Main

- Field - Tables Using Field

Field - Main

Open this page using Admin > Database > Field.

Description of Page

Field Name uniquely identifies this field.

CAUTION:

As described in System Data Naming Convention for most system data tables, the base product follows a specific naming convention. However, this is not true for the Field table. If you introduce new fields, you must prefix the field with CM. If you do not do this, there is a possibility that a future release of the application could introduce a new field with the name you allocated.

Owner indicates if this field is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a field.

Base Field indicates that the field inherits some of its definitions from another field.

Data Type indicates if the type of data the field will hold. Valid values are Character, Character Large Object, Date, DateTime, Number, Time, Varchar2 and XML Type. This field is protected if the field refers to a Base Field.

Ext Data Type or Extended Data Type is used to further define the type of data for certain data types. Valid values are Currency Source, Day of Month, Duration, Money, Month of Year, Flag, Switch and URI. This field is protected if the field refers to a Base Field.

Precision defines the length of the field. In the case of variable length fields, it is the maximum length possible. For number fields that include decimal values, the precision includes the decimal values. This field is protected if the field refers to a Base Field.

Scale is only applicable for number fields. It indicates the number of decimal places supported by the field. This field is protected if the field refers to a Base Field.

Sign is only applicable for numbers. It indicates if the data may contain positive or negative numbers.

Value List is only visible for products that had at one point included COBOL. It defines the copybook that includes the list of valid values for the field.

Description contains the label of the field. This is the label of the field that appears on the various pages on which the field is displayed. Note, the field's label can be overridden for a specific table by specifying an Override Label on the table / field information. However, this override is not used in portal based user interfaces. It is only applicable if the field is displayed on fixed page user interfaces.

Java Field Name is the reference to this field used in Java code.

Override Label is used if an implementation would like to override the label that appear on user interfaces in the system.

CAUTION:

For fixed pages, if the field's label is overridden for a specific table, that override takes precedence. In this is the case the override on the table / field page should be used.

Work Field indicates that the field does not represent a database table column.

Help Text is used to provide field level embedded help to this field. If the field is displayed on a user interface that supports display of embedded help, this text may be displayed.

Use Override Help Text to override the existing embedded help text for this field.

Extract for Translation is only visible in a development environment. It indicates whether or not the field and its description should be included in an extract of translatable strings when doing a product translation. This flag may be set to "No" for work fields whose label is not visible to a user on any user interface.

Translation Context is only visible in a development environment. It is used to provide information to a translator about the use of the field’s label so that an appropriate translation can be provided.

Field - Tables Using Field

Select Admin > Database > Field and navigate to the Tables Using Field tab to view the tables that contain a field.

Description of Page

The grid on this page contains the Tables that reference the Field. You can use the adjacent go to button to open the Table Maintenance transaction.

Defining Maintenance Object Options

A maintenance object defines the configuration of a given “entity” in the system. It includes the definition of the tables that together capture the physical data for the entity. In addition, the maintenance object includes options that define important information related to the maintenance object that may be accessed for logic throughout the system. Several algorithm plug-in spots are also defined on the maintenance object, allowing for business rules that govern all records for this maintenance object.

Many maintenance objects in the system support the use of business objects to further define configuration and business rules for a given record. Refer to The Big Picture of Business Objects for more information.

Next in This Section

- Maintenance Object - Main

- Maintenance Object - Options

- Maintenance Object - Algorithms

- Maintenance Object - Maintenance Object Tree

Maintenance Object - Main

Select Admin > Database > Maintenance Object to view information about a maintenance object.

Description of Page

Most maintenance objects are provided with the base package. An implementation can introduce custom maintenance objects when needed. Most fields may not be changed if owned by the base package.

Enter a unique Maintenance Object name and Description. Owner indicates if this business object is owned by the base package or by your implementation (Customer Modification).

Important: If you introduce a new maintenance object, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Service Name is the name of the internal service associated with the maintenance object.

Click the View XML hyperlink to view the XML document associated with the maintenance object service in the Service XML Viewer.

Click the View MO hyperlink to view the definition of the maintenance object in the Maintenance Object Viewer.

The grid displays the following for each table defined under the maintenance object:

- Table is the name of a given table maintained as part of the maintenance object.

- Table Role defines the table's place in the maintenance object hierarchy. Only one Primary table may be specified within a maintenance object, but the maintenance object may contain many Child tables.

- Parent Constraint ID specifies the constraint used to link the table to its parent table within the maintenance object table hierarchy.

- Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

Maintenance Object - Options

Use this page to maintain a maintenance object's options. Open this page using Admin > Database > Maintenance Object and then navigate to the Options tab.

Description of Page

The options grid allows you to configure the maintenance object to support extensible options.

Select the Option Type drop-down to define its Value. Detailed Description may display additional information on the option type.

Set the Sequence to 1 unless the option can have more than one value.

Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

Note: You can add new option types. Your implementation may want to add additional maintenance option types. For example, your implementation may have plug-in driven logic that would benefit from a new type of option. To do that, add your new values to the customizable lookup field MAINT_OBJ_OPT_FLG.

Maintenance Object - Algorithms

Use this page to maintain a maintenance object's algorithms. Open this page using Admin > Database > Maintenance Object and then navigate to the Algorithms tab.

Description of Page

The Algorithms grid contains algorithms that control important functions for instances of this maintenance object. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

- If the algorithm is implemented as a script, a link to the Script is provided. Refer to Plug-in Scripts for more information.

- Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

The following table describes each System Event.

System Event

Optional / Required

Description

Audit

Optional

Algorithms of this type are called to notify of any changes to the maintenance object's set of tables. These algorithms are invoked just before the commit at the end of a logical transaction. The system keeps track of what records are added or changed in the course of a transaction and all MO audit algorithms are executed in order of when each record was first added or updated.

Click here to see the algorithm types available for this system event.

Determine BO

Optional

Algorithm of this type is used to determine the Business Object associated with an instance of the maintenance object. It is necessary to plug in such an algorithm on a Maintenance Object to enable the business object rules functionality.

The system invokes a single algorithm of this type. If more than one algorithm is plugged-in the system invokes the one with the greatest sequence number.

Click here to see the algorithm types available for this system event.

ILM Eligibility

Optional

Algorithms of this type are used for maintenance objects that are enabled for Information Lifecycle Management. They are used to review records that have reached the maximum retention days and evaluate if they are ready to be archived.

The system invokes a single algorithm of this type. If more than one algorithm is plugged-in the system invokes the one with the greatest sequence number.

Click here to see the algorithm types available for this system event.

Information

Optional

We use the term "Maintenance Object Information" to describe the basic information that appears throughout the system to describe an instance of the maintenance object. The data that appears in this information description is constructed using this algorithm.

The system invokes a single algorithm of this type. If more than one algorithm is plugged-in the system invokes the one with the greatest sequence number.

Click here to see the algorithm types available for this system event.

Revision Control

Optional

An algorithm of this type is used to enforce revision control rules when an object is added, changed or deleted. The maintenance object service calls the plug-in once before the object is processed and once more after applying all business object rules. This allows revision rules to take place in proper revision timings.

Click here to see the algorithm types available for this system event.

Transition

Optional

The system calls algorithms of this type upon each successful state transition of a business object as well as when it is first created. These are typically used to record the transition on the maintenance object's log.

Note that most base maintenance objects are already shipped with an automatic logging of state transitions. In this case you may use these algorithms to override the base logging functionality with your own. Refer to State Transitions are Audited for more information.

Click here to see the algorithm types available for this system event.

Transition Error

Optional

The system calls this type of algorithm when a state transition fails and the business object should be saved in its latest successful state. The algorithm is responsible for logging the transition error somewhere, typically on the maintenance object's log.

Notice that in this case, the caller does NOT get an error back but rather the call ends successfully and the exception is recorded somewhere, as per the plug-in logic.

The system invokes a single algorithm of this type. If more than one algorithm is plugged-in the system invokes the one with the greatest sequence number.

Click here to see the algorithm types available for this system event.

Note: You can inactivate algorithms on Maintenance Objects. Your implementation may want to inactivate one or more algorithms plugged into the base maintenance object. To do that, go to the options grid on Maintenance Object - Options and add a new option, setting the option type to Inactive Algorithm and setting the option value to the algorithm code.

Maintenance Object - Maintenance Object Tree

You can navigate to the Maintenance Object Tree to see an overview of the tables and table relationships associated with the maintenance objects.

Description of Page

This page is dedicated to a tree that shows the maintenance object's tables as well as business objects, if you have defined any. You can use this tree to both view high-level information about these objects and to transfer to the respective page in which an object is maintained.

Defining Valid Values

The product provides several options for defining valid values for a column on a table:

- Lookup

- Extendable Lookup

- Control Table

The following provides more information about the functionality of each of the options available for defining valid values for a column.

Lookup

The simplest mechanism for defining valid values for a column on a table is via the Lookup table. This is sometimes referred to as a “simple” lookup to distinguish it from an extendable lookup (described below). Using the lookup table, you can define valid values and their descriptions. When choosing a valid value that is defined by a lookup, a dropdown UI metaphor is used.

The following highlights functionality related to lookups:

- Lookups are associated with a Field. The field is defined as a character data type with an extended data type of Flag. The field’s label serves as the description for the prompt to select the valid value.

- The lookup code is limited to four characters and must be all uppercase. If there is any functionality where a valid value in the application must match valid values in an external system, the lookup table may not be the appropriate choice.

- The lookup table does not support additional attributes to be defined for each value. This option is only appropriate when a simple code and description pair is needed.

- The product may also use Lookups to define valid values for functionality unrelated to a column on a table. For example, an algorithm plug-in spot may define an input parameter that supports one or more valid values. The plug-in spot may define the valid values using a lookup, allowing for a simple way to validate the value supplied when invoking the algorithm and to document the valid values.

Fastpath: For more information, refer to Defining Lookup Options.

Extendable Lookup

The extendable lookup provides a way of defining valid values for a column with additional capabilities that are not supported using the Lookup table. When choosing a valid value that is defined by an extendable lookup, a dropdown UI metaphor is used.

The following highlights functionality related to extendable lookups:

- Each Extendable Lookups is defined using a business object.

- A field should be defined for the extendable lookup code. The field defines the label for the lookup code and defines the size of the lookup code. The size is determined based on the business use case. In addition, there are standard fields included in all extendable lookups, including a description, detailed description and an override description (so that implementations can override the description of base delivered values).

- The extendable lookup may define additional information for each value if warranted by the business requirement. See Additional Attributes for technical information about additional attributes.

Fastpath: For more information, refer to Defining Extendable Lookups.

Control Table

There may be scenarios where a list of valid values warrants a standalone maintenance object, which is considered an administrative or control table object. When choosing a valid value that is defined by a control, either a dropdown UI metaphor or a search metaphor is used, depending on how it has been designed.

The following points highlight some reasons why this option may be chosen:

- The records require a lifecycle such that BO status is warranted.

- The additional attributes are sophisticated enough that they warrant their own column definition rather than relying on using CLOB or flattened characteristic. For example, if a list of information needs to be captured with several attributes in the list and the information in the list needs to be searchable.

In this situation, if a product has provided a control table for this type of functionality, it will be documented fully in the appropriate functional area. If an implementation determines that a custom control table is warranted, all the standard functionality for a maintenance object is required: database tables, maintenance object metadata, appropriate Java maintenance classes, portals, zones, etc. Refer to the Software Development Kit for more information. No further information is provided in this section for this option.

Next in This Section

- Defining Lookup Options

- Defining Extendable Lookups

Defining Lookup Options

Lookup fields may be used to define valid values for a column in a table or for other types of values like parameters to an algorithm.

Fastpath: Refer to Defining Valid Values for some background information.

The base product provides many different lookup fields and their values as part of the product. The following points highlight some functionality related to base-package lookups.

- Fields that are owned by the product will typically provide base lookup values. Implementations are not permitted to remove base delivered lookup values. Implementations may be able to add custom values to base owned lookups. This is controlled with the Custom switch on lookup.

- When the custom switch is unchecked, it means that there is functionality controlled by the base values and an implementation may not extend or customize this functionality. An example of this type of lookup is the Data Type field on the Field table. The system supports a distinct list of data types and an implementation may not add additional values.

- When the custom switch is checked, it means that there is base functionality supplied for the base values but that an implementation can extend the functionality by supplying their own values. An example of this type of lookup is the Access Mode on Application Service. The product provides many values for the access mode lookup, representing various actions a user may perform. Implementations may add their own values to this lookup. Documentation should indicate when functionality may be extended and should highlight the lookup value that can be extended.

CAUTION:

Important! If you introduce new lookup values, you must prefix the lookup value code with X or Y. If you do not do this, there is a possibility that a future release of the application could introduce a new lookup value with the name you allocated.

- There may be some scenarios where the product supplies a base field and base lookup field with no base lookup values supplied. This occurs when the product doesn’t have any base functionality driven by the lookup values. Typically this type of lookup is for information or categorization purposes. The configuration guide for the functional area associated with the lookup should include a configuration step regarding defining values for this type of lookup.

- The description of base delivered values may be overridden by an implementation.

An implementation may also identify the need for defining a new lookup field with its values.

Next in This Section

- Lookup - Main

Lookup - Main

Select Admin > Database > Lookup to maintain lookup values.

Description of Page

Field Name is the name of the field whose lookup values are maintained in the grid. If you need to add a new lookup field, you must first add the lookup field here, then navigate to the Field page to create a field with a data type of Character and an extended data type of Flag.

Owner indicates if this lookup field is owned by the base package or by your implementation (Customer Modification). This information is display-only.

Custom switch is used to indicate whether you are allowed to add valid values for a lookup field whose owner is not Customer Modification.

- If this switch is turned on, you may add new values to the grid for system owned lookup fields.

- If this switch is turned off, you may not add, remove or change any of the values for system owned lookup fields, with the exception of the override description.

This field is always protected for system owned lookup fields because you may not change a field from customizable to non-customizable (or vice versa).

Java Field Name indicates the name of the field as it is referenced in Java code.

The grid contains the lookup values for a specific field. The following fields are visible:

Field Value is the unique identifier of the lookup value. If you add a new value, it must begin with an X or Y (in order to allow future upgrades to differentiate between your implementation-specific values and base-package values).

Description is the name of the lookup value that appears on the various transactions in the system

Java Value Name indicates the unique identifier of the lookup value as it is referenced in Java code.

Status indicates if the value is Active or Inactive. The system does not allow Inactive values to be used (the reason we allow Inactive values is to support historical data that references a value that is no longer valid).

Detailed Description is the detailed description for a lookup value, which is provided in certain cases.

Override Description is provided if your implementation wishes to override the description of the value provided by the product.

Note: If you wish the override descriptions of your lookup values to appear in the application viewer, you must regenerate the data dictionary application viewer background process.

Owner indicates if this lookup value is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add lookup values to a field. This information is display-only.

Defining Extendable Lookups

Extendable lookups are a way of defining valid values that are more sophisticated than simple lookups.

Fastpath: Refer to Defining Valid Values for some background information.

The base product provides extendable lookups as part of the product. The following points highlight some functionality related to base-package extendable lookups.

- The base product may supply base extendable lookup values. Implementations are not permitted to remove base delivered extendable lookup values. It is also possible that implementations may be able to add custom values to base owned lookups. If an implementation is not permitted to add lookup values to the base extendable lookup, the extendable lookup’s business object will include validation to prevent this. There is no equivalent of the Custom switch that is on the lookup field.

- There may be some scenarios where the product supplies a base extendable lookup with no base lookup values supplied. This occurs when the product doesn’t have any base functionality driven by the extendable lookup values. The configuration guide for the functional area associated with the extendable lookup should include a configuration step regarding defining values for this type of extendable lookup.

- The description of base delivered values may be overridden by an implementation.

Open this page using Admin > General > Extendable Lookup.

You are brought to the Extendable Lookup Query where you need to search for the extendable lookup object (i.e., its business object).

Once you have found the appropriate extendable lookup, select the value and you are brought to a standard All-in-One portal that lists the existing lookup values for the extendable lookup. The standard actions for an All-in-One portal are available here.

Next in This Section

- Extendable Lookup Advanced Topics

Extendable Lookup Advanced Topics

This section provides some addition technical information about extendable lookup attributes

Defining Additional Attributes

The product provides a few different ways to define additional values for an extendable lookup. Some of the methods are only relevant for base delivered lookup values as they may impact whether or not an implementation can update the values.

The following table highlights the options available and some summary information about what the option provides.

Option

Brief Description

Extendable Lookup Value Searchable by this Attribute?

Base Delivered Value Modifiable?

Element mapped to BO_DATA_AREA

The element is mapped to a CLOB field that allows for base delivered values to be modified.

No

Yes

Element mapped to BASE_BO_DATA_AREA

The element is mapped to a CLOB field that does not allow for base delivered values to be modified.

No

No

Flattened characteristic

The element is defined using the flattened characteristic mechanism.

Yes

No

The following points highlight information from the table above:

- The decision of defining an additional attribute using a CLOB mapping or a flattened characteristic will depend on whether the functionality expects that the lookup value is known when the attribute is needed (in which case a CLOB mapping is appropriate) or if the functionality expects to determine the lookup value based on the attribute (in which case, a flattened characteristic is appropriate).

- When the base product defines an extendable lookup with additional attributes and intends to provide base extendable lookup values, it needs to determine whether or not implementations may update the additional attribute or not.

- If no and the value is mapped to a CLOB, it will map the value to the BASE_BO_DATA_AREA column. This means that implementations will receive an owner mismatch error when attempting to change the value. In addition, upgrading to a new release will replace the value with the base value.

- If yes and the value is mapped to a CLOB, it will map the value to the BO_DATA_AREA column. This means that implementations will be able to change the value for a base owned record. In addition, upgrading to a new release will not make any changes to the value.

- For values mapped to a characteristic, the product does not support an implementation changing the value of a base delivered record. If the product would like to support an implementation overriding this type of value, the business object will need to be designed with a corresponding "override" element (also a flattened characteristic), similar to how the product supplies an Override Description field to support an implementation overriding the base product delivered description for a base value. This element will not be delivered with any value and will allow an implementation to populate that value.

Note: Note that in this situation, the product functionality that uses this value must cater for the override value.

- All of this detail is only relevant for base provided extendable lookup values. If an implementation adds custom values for a base supplied extendable lookup, all the additional attributes may be populated as appropriate.

- If an implementation defines a custom extendable lookup business object and wants to define an additional attribute using a CLOB, it doesn't matter which CLOB column is used. Both BO_DATA_AREA and BASE_BO_DATA_AREA provide the same functionality for custom business objects.

Capturing a Password

If an extendable lookup includes configuration of a password for some functionality, the system supports automatic encryption of the password value if the schema maps the password to a characteristic using the characteristic type F1-PWD. Refer to the business object F1-FileStorage for an example of such a configuration.

The Big Picture Of Audit Trails

The topics in this section describe one way of auditing changes in the system. Note that this technique has limitations and may not be the best option for all situations.

- This functionality is configured at the table and field level. Many base maintenance objects use an XML or CLOB field to capture one or more elements using XML format, configured using a BO schema. This auditing technique is not able to capture changes to individual elements. It can only capture overall changes to the single field. The BO Audit plug-in is a better option for auditing changes to individual elements with the CLOB / XML field.

- The base table provided for supporting audits limits the field size of the before and after values to 254 bytes.

- Auditing is captured for each field. In some cases it is prefered to capture a before and after image for several fields at once. For example, if an address is changed, it’s nore user friendly to capture the before and after for the full address rather than the individual address components. The BO Audit plug-in allows for capturing a single audit record for multiple elements rather than granular changes for each element.

The subsequent topics highlight how to enable auditing for fields, and describe the auditing queries that you can use to view audit records.

Next in This Section

- Captured Information

- How Auditing Works

- The Audit Trail File

- How To Enable Auditing

- Audit Queries

Captured Information

When auditing is enabled for a field, the following information is recorded when the field is changed, added and/or deleted (depending on the actions that you are auditing for that field):

- User ID

- Date and time

- Table name

- Row's prime key value

- Field name

- Before image (blank when a row is added)

- After image (blank when a row is deleted)

- Row action (add, change, delete)

How Auditing Works

You enable auditing on a table in the table's meta-data by specifying the name of the table in which to insert the audit information (the audit table) and the name of the program responsible for inserting the data (the audit trail insert program). Then you define the fields you want to audit by turning on each field's audit switch in the table's field meta-data. You can audit fields for delete, insert and update actions.

Once auditing is enabled for fields in a table, the respective row maintenance program for the table assembles the list of changed fields and calls the audit trail insert program. If any of the changed fields are marked for audit, the audit program inserts audit rows into the audit table.

Note: Customizing Audit Information. You may want to maintain audit information other than what is described in Captured Information or you may want to maintain it in a different format. For example, you may want to maintain audit information for an entire row instead of a field. If so, your implementation team can use the base audit program and base audit tables as examples when creating your own audit trail insert program and audit table structures.

The Audit Trail File

Audit log records are inserted in the audit tables you define. The base product contains a single such table (called CI_AUDIT ). However, the base audit insert program is designed to allow you to use multiple audit tables.

If you want to segregate audit information into multiple tables, you must create these tables. Use the following guidelines when creating new audit tables (that use the base delivered audit insert program):

- The new audit tables must look identical to the base table (CI_AUDIT).

- The new tables must be prefixed with CM (e.g., CM_AUDIT_A, CM_AUDIT_B, etc.). An appropriate java table name must be defined and an *_impl.java program for that java table name must be defined.

- The name of the new table must be referenced on the various tables whose changes should be logged in the new table.

Note: It's important to note if you use your own tables (as opposed to using the base package table called CI_AUDIT), the SQL used to insert and access audit trail records in the base delivered audit program is dynamic. Otherwise, if the base package's table is used, the SQL is static.

How To Enable Auditing

Enabling audits is a two-step process:

- First, you must turn on auditing for a table by specifying an audit table and an audit trail insert program.

- Second, you must specify the fields and actions to be audited for the table.

The following topics describe this process.

Next in This Section

- Turn On Auditing For a Table

- Specify The Fields and Actions To Be Audited

Turn On Auditing For a Table

In order to tell the system which fields to audit, you must know the name of the table on which the field is located. You must specify the audit table and the audit trail insert program for a table in the table's meta-data.

Note: Most of the system's table names are fairly intuitive. For example, the user table is called SC_USER, the navigation option table is called CI_NAV_OPT, etc. If you cannot find the table using the search facility on the Table Maintenance page, try using the Data Dictionary. If you still cannot find the name of the table, please contact customer support.

To enable auditing for a table:

- Navigate to the Table maintenance page and find the table associated with the field(s) for which you want to capture audit information.

- Specify the name of the Audit Table.

Note: Specifying the Audit Table. You can use the audit table that comes supplied with the base package ( CI_AUDIT) to audit multiple tables and fields. All the audit logs are combined in a single table ( CI_AUDIT). However, you can also have a separate audit table for each audited table. Refer to The Audit Trail File for more information.

- Specify the name of the Audit Program . The product provides two programs. com.splwg.base.domain.common.audit.DefaultTableAuditor is a standard table audit program. In addition com.splwg.base.domain.common.audit.ModifiedTableAuditoris supplied as an alternative. This program does not audit inserts or deletes of empty string data.

CAUTION:

By default, none of a table's fields are marked for audit. Even though you have enabled auditing for a table, you must still specify the fields and actions on those fields to be audited (see below).

Specify The Fields and Actions To Be Audited

The system only audits actions (insert, update and delete) made to fields that you want audited.

To specify the fields and actions to be audited:

- Navigate to the Table - Table Field maintenance page for a table on which you have enabled auditing.

- For each field you want to audit, specify the actions you want to audit by turning on the Audit Delete, Audit Insert and Audit Update switches as appropriate.

Note: You can also turn on the audit switches using the Field grid at the bottom of the Table maintenance page.

CAUTION:

Audit Program Caching! The audit program from the table meta-data is read into a program cache on the application server whenever the date changes or when the server starts. If you implement new auditing on a table, your audit trail does not become effective until this program cache is reloaded. In other words, new audits on tables where the audit program was not previously specified do not become effective until the next day (or the next restart of the application server). However, if you change the fields to be audited for a table where the audit program is already in the cache, your changes are effective immediately.

Audit Queries

There are two queries that can be used to access the audit information.

Next in This Section

- Audit Query by User

- Audit Query by Table / Field / Key

Audit Query by User

This transaction is used to view changes made by a user that are stored on a given Audit Trail File.

CAUTION:

The system only audits changes that you've told it to audit. Refer to The Big Picture Of Audit Trails for more information.

Navigate to this page by selecting Admin > Database > Audit Query By User.

Description of Page

To use this transaction:

- Enter the User ID of the user whose changes you wish to view.

- Enter the name of the table on which the audit trail information is stored in Audit Table. Refer to The Audit Trail File for more information about this field.

Note: Default Note. If only one audit table is used to store audit trail information, that table is defaulted.

- Specify a date and time range in Created between to restrict the records that result from the query.

Note: Default Note. The current date is defaulted.

- Click the search button to display all changes recorded on a specific audit table associated with a given user.

Information on this query is initially displayed in reverse chronological order.

The following information is displayed in the grid:

- Row Creation Date is the date and time that the change was made.

- Audited Table Name contains the name of the table whose contents were changed.

- Primary Key is the prime key of the row in the Audited Table whose contents where changed.

- Audited Field Name is the name of the field that was changed.

- Audit Action indicates whether the row action was Add, Change or Delete.

- Field Value Before Update contains the content of the field before the change. This column is blank if information was Added.

- Field Value After Update contains the content of the field after the change. This column is blank if information was Deleted.

Audit Query by Table / Field / Key

This transaction is used to view audited changes made to a given table.

CAUTION:

The system only audits changes that you've told it to audit. Refer to The Big Picture Of Audit Trails for more information.

This transaction can be used in several different ways:

- You can view all audited changes to a table. To do this, enter the Audited Table Name and leave the other input fields blank.

- You can view all audited changes to a given row in a table (e.g., all changes made to a given user). To do this, enter the Audited Table Name and row's prime key (the row's prime key is entered in the field(s) beneath Audited Field Name).

- You can view all audited changes to a given field in a table (e.g., all changes made to all customers' rates). To do this, enter the Audited Table Name and the Audited Field Name.

- You can view all audited changes to a given field on a specific row. To do this, enter the Audited Table Name, the Audited Field Name, and row's prime key (the row's prime key is entered in the field(s) beneath Audited Field Name).

Navigate to this page by selecting Admin > Database > Audit Query By Table/Field/Key.

Description of Page

To use this transaction:

- Enter the name of the table whose changes you wish to view in Audited Table Name.

- If you wish to restrict the audit trail to changes made to a specific field, enter the Audited Field Name.

- If you wish to restrict the audit trail to changes made to a given row, enter the row's prime key (the row's prime key is entered in the field(s) beneath Audited Field Name). These fields are dynamic based on the Audited Table Name.

- Specify a date and time range in Created between to restrict the records that result from the query.

Note: The current date is defaulted.

- Click the search button to display all changes made to this data.

Information on this query is initially displayed in reverse chronological order by field.

The following information is displayed in the grid:

- Create Date/Time is the date / time that the change was made.

- User Name is the name of the person who changed the information.

- Primary Key is the prime key of the row in the Audited Table whose contents where changed.

- Audited Field Name is the name of the field that was changed.

- Audit Action indicates whether the row action was Add, Change or Delete.

- Value Before Update contains the content of the field before the change. This column is blank if information was Added.

- Value After Update contains the content of the field after the change. This column is blank if information was Deleted.

Bundling

The topics in this section describe the bundling features in the application.

Next in This Section

- About Bundling

- Configuring Maintenance Objects for Bundling

- Working with Bundles

About Bundling

Bundling is the process of grouping entities for export or import from one environment to another.

For example, you might export a set of business objects and service scripts from a development environment and import them into a QA environment for testing. The group of entities is referred to as a bundle. You create export bundles in the source environment; you create import bundles in the target environment.

Working with bundles involves the following tasks:

- Configuring entities for bundling if they are not preconfigured

- Creating an export bundle, which contains a list of entities to be exported from the source environment

- Creating an import bundle to import those entities to the target environment

- Applying the import bundle, which adds or updates the bundled entities to the target environment

Next in This Section

- Sequencing of Objects in a Bundle

- Recursive Key References

- Owner Flags on Bundled Entities

Sequencing of Objects in a Bundle

Bundle entities are added or updated to the target environment in the sequence defined in the bundle

Typically, the sequence of entities does not matter. However, sequence is important in the following situations:

- Entities that are referenced as foreign keys should be at the top of the sequence, before the entities that reference them. Specify zones last, as they typically contain numerous foreign key references.

- When importing a business object, specify the business object first, then its plug-in scripts, then the algorithms that reference the scripts, and then the algorithm types that reference the algorithms.

- When importing a portal and its zones, specify the portal first and then its zones.

- When importing a multi-query zone, specify the referenced zones first and then the multi-query zone.

- Always specify algorithms types before algorithms.

You can specify the sequence when you define the export bundle or when you import the bundle to the target environment.

Recursive Key References

Recursive foreign keys result when one object has a foreign key reference to another object that in turn has a foreign key reference to the first object.

For example, a zone has foreign keys to its portals, which have foreign keys to their zones. If the objects you want to bundle have recursive relationships, you must create a 'bundling add' business object that has only the minimal number of elements needed to add the entity. A bundling add business object for a zone contains only the zone code and description, with no references to its portals. In the same way, a bundling add business object for a portal defines only its code and description.

When you apply the bundle, the system initially adds the maintenance object based on the elements defined in the bundling add business object. Before committing the bundle, the system updates the maintenance object with the complete set of elements based on its physical business object.

Owner Flags on Bundled Entities

The owner flag of the entities in an import bundle must match the owner flag of the target environment.

If you need to import objects that your source environment does not own, you must replace the owner flag in the import bundle with the owner flag of the target environment.

Configuring Maintenance Objects for Bundling

All base package meta-data objects are pre-configured to support bundling. All other objects must be manually configured.

If a base package maintenance object is pre-configured for bundling, the Eligible For Bundling option will be set to "Y" on the Options tab for the maintenance object.

To configure other objects for bundling, review the configuration tasks below and complete all those that apply:

Configuration Task

Scope of Task

Make maintenance objects eligible for bundling

All objects to be included in the bundle

Add a foreign key reference

All objects to be included in the bundle

Create a physical business object

All objects to be included in the bundle

Create a bundling add business object

Objects with recursive foreign key references

Add the Current Bundle zone

All objects, if you want the Current Bundle zone to appear on the maintenance object's dashboard. This is not required by the bundling process.

Create a custom Entity Search zone and add it to the Bundle Export portal

All objects, if you want them to be searchable in the Bundle Export portal. This is not required by the bundling process.

Next in This Section

- Making Maintenance Objects Eligible for Bundling

- Adding a Foreign Key Reference

- Creating a Physical Business Object

- Creating a Bundling Add Business Object

- Adding the Current Bundle Zone

- Adding a Customized Entity Search Query Zone to the Bundle Export Portal

Making Maintenance Objects Eligible for Bundling

The "Eligible For Bundling" maintenance object option must be set to "Y" for all bundled objects.

To make maintenance objects eligible for bundling:

1. Go to the Maintenance Object page and search for the maintenance object.

2. On the Options tab, add a new option with the type Eligible For Bundling.

3. Set the value to "Y" and click Save.

Adding a Foreign Key Reference

Each maintenance object in a bundle must have a foreign key reference. Bundling zones use the foreign key reference to display the standard information string for the maintenance object.

To add a foreign key reference to the maintenance object:

1. Navigate to FK Reference and set up a foreign key reference for the primary table of the maintenance object.

2. Navigate to Maintenance Object and search for the maintenance object.

3. On the Option tab, add a new option with the type Foreign Key Reference. The value is the name of the foreign key reference you just created.

Creating a Physical Business Object

Each maintenance object in a bundle must have a physical business object. The physical business object's schema represents the complete physical structure of the maintenance object, and includes elements for all fields in the maintenance object's tables. The bundling process uses this schema to generate the XML for the import bundle.

To create a physical business object for the maintenance object:

1. Navigate to Business Object and specify the maintenance object.

2. Click Generate in the BO Schema dashboard zone to generate a schema that looks like the physical structure of the maintenance object.

3. Save the physical business object.

4. Navigate to Maintenance Object and search for the maintenance object.

5. On the Option tab, add a new option with the type Physical Business Object. The value is the name of the physical business you just created.

Creating a Bundling Add Business Object

If the objects to be bundled have recursive foreign key references, you must create a bundling add business object to avoid problems with referential integrity.

To create a bundling add business object:

1. Navigate to Business Object and specify the maintenance object.

2. Click Generate in the BO Schema dashboard zone to generate a schema that looks like the physical structure of the maintenance object.

3. Remove all elements that are not essential. Typically, only a code and description are required.

4. Save the physical business object.

5. Navigate to Maintenance Object and search for the maintenance object you want to bundle.

6. On the Option tab, add a new option with the type Bundling Add BO. The value is the name of the bundling add business object you just created.

Adding the Current Bundle Zone

If you want the Current Bundle zone to appear on the maintenance object's dashboard, you must add the Current Bundle zone as a context-sensitive zone for the maintenance object.

To add the Current Bundle zone to the maintenance object:

1. Navigate to Context Sensitive Zone and search for the navigation key for the maintenance object.

2. Add the Current Bundle zone F1-BNDLCTXT, to that navigation key.

Adding a Customized Entity Search Query Zone to the Bundle Export Portal

If you want the maintenance object to be searchable in the Bundle Export portal, you must first create an entity-specific query zone to search for the maintenance object. Then you must create a customized entity search zone that references this new query zone. Finally, you must add the customized entity search zone to the Bundle Export portal.

To make the maintenance object searchable:

1. Create an entity-specific query zone to search for the maintenance object:

1. Navigate to Zone and search for one of the base query zones, such as the Algorithm Search zone F1-BNALGS.

2. Click the Duplicate button in the page actions toolbar.

3. Enter a name for the new zone.

4. Click Save.

5. Locate the User Filter parameter in the parameter list. Add SQL to search for the maintenance object(s) you want to appear in the zone.

6. Save the query zone.

2. Create a customized entity search zone:

This step only needs to be done once. If you already have a customized search zone in the Bundle Export portal go to step 3

1. Navigate to Zone and search for the F1-BNDLENTQ Entity Search zone.

2. Duplicate this zone (as described above).

3. Remove any references to base query zones.

3. Add the new entity-specific query zone to the customized entity search zone:

1. Locate the customized entity search zone for your Bundle Export portal. This is the zone created in Step 2.

2. Locate the Query Zone parameter in the parameter list. Add the name of the query zone you created in Step 1.

3. Save the entity search zone.

4. Add the customized entity search zone to the Bundle Export portal:

This step needs to be done only once.

1. Navigate to Portal and search for the Bundle Export portal, F1BNDLEM.

2. In the zone list, add the entity search zone you created in Step 2. (Add the new zone after the base entity search zone).

3. Save the portal.

Working with Bundles

Use the Bundle Export portal to create an export bundle. The export bundle contains a list of entities to be exported from the source environment. When you are ready to import the objects, use the Bundle Import portal to import the objects to the target environment.

Next in This Section

- Creating Export Bundles

- Creating and Applying Import Bundles

- Editing Export Bundles

- Editing Import Bundles

Creating Export Bundles

An export bundle contains a list of entities that can be imported into another environment.

To create an export bundle:

1. Log on to the source environment from which objects will be exported.

2. Select Admin > Implementation Tools > Bundle Export > Add.

3. Complete the fields in the Main section to define the bundle's basic properties.

Note: You can use the Entities section to add bundle entities now, or save the bundle and then add entities as described in step 5.

4. Click Save to exit the Edit dialog. The export bundle status is set to Pending.

5. While an export bundle is in Pending state, use any of the following methods to add entities to the bundle:

1. Use the Entity Search zone on the Bundle Export portal to search for entities and add them to the bundle. If an entity is already in the bundle, you can remove it.

2. To import entities from a .CSV file, click Edit on the Bundle Export portal, and then click CSV File to Upload. Specify the file name and location of the .CSV file containing the list of entities. Click Submit to upload the file, and then click Save to save the changes.

3. Use the Current Bundle zone in the dashboard of the entity you want to add. (All entities that are configured to support bundling display a Current Bundle zone). This zone displays a list of all pending export bundles to which you can add the entity.

4. When you check an entity into revision control, specify the export bundle on the Revision Info dialog.

6. When you have added all entities, click Bundle in the Bundle Actions zone on the Bundle Export portal. The export bundle state is set to Bundled and the Bundle Details zone displays the XML representation of every entity in the bundle.

Note: The owner flags of the entities in the bundle must match the owner flag of the bundle itself. If the owner flags do not match, the system displays a warning message. Click OK to continue or Cancel to abort the bundle. If you click OK, you will need to resolve the owner flag discrepancy before you import the bundle to the target environment.

7. Copy the XML from the Bundle Detail zone to the clipboard (or to a text file). You can now create an import bundle and apply it to the target environment.

Note: If you need to make additional changes to the bundle, you must change the bundle state by selecting the Back to Pending button in the Bundle Actions zone.

Creating and Applying Import Bundles

Import bundles define a group of entities to be added or updated in the target environment.

Before you create an import bundle, you must have already created an export bundle, added entities, and set the bundle's state to Bundled.

To create an import bundle and apply it to the target environment:

1. If you have not already copied the XML from the export bundle, do so now:

1. Select Admin > Implementation Tools > Bundle Export and search for the bundle.

2. Copy the XML from the Bundle Detail zone to the clipboard (or to a text file).

2. Log on to the target environment.

3. Select Admin > Implementation Tools > Bundle Import > Add.

4. In the Bundle Actions zone, click Edit XML.

5. Paste the contents of the clipboard (or text file if you created one) into the Bundle Detail zone.

6. Make any necessary changes to the XML and click Save. The status of the import bundle is set to Pending.

Note: Use caution when editing the XML to avoid validation errors.

7. To remove entities from the import bundle or change their sequence, click Edit. Enter your changes and click Save to exit the Edit dialog.

8. When you are ready to apply the bundle, click Apply. The import bundle state is set to Applied and the entities are added or updated in the target environment.

Editing Export Bundles

You can add or remove entities from an export bundle when it is in Pending state. You can also change the sequence of entities.

To edit to an export bundle that has already been bundled, you must change the bundle state by selecting the Back to Pending button on the Bundle Export portal.

To edit a pending export bundle:

1. Open the bundle in edit mode.

2. Click Edit on the Export Bundle portal.

3. Make any necessary changes on the edit dialog and then click Save.

Editing Import Bundles

You can remove entities from an import when it is in Pending state. You can also change the sequence of entities and edit the generated XML.

To edit a pending import bundle:

1. Open the bundle in edit mode.

2. To edit the XML snapshot, click Edit XML. Edit the XML code as needed, then click Save.

Note: Use caution when editing the XML to avoid validation errors.

3. To remove entities or change their sequence, click Edit. Make any necessary changes and click Save.

Revision Control

The topics in this section describe the revision control features in the application.

Next in This Section

- About Revision Control

- Working with the Revision Control Zones

- Working with the Revision Control Portal

About Revision Control

Revision control is a tool provided for the development phase of a project to allow a user to check out an object that is being worked on. In addition, it captures the version of the maintenance object when users check in an update, maintaining a history of the changes to the object.

If revision control is enabled for an object you must check out the object to change it. While the object is checked out no one else can work on it. You can revert all changes made since checking out an object, reinstate an older version of an object, recover a deleted object, and force a check in of an object if someone else has it checked out.

Note: Revision control does not keep your work separate from the environment. Because the metadata for maintenance objects is in the central database, any changes you make to an object while it is checked out will be visible to others and may impact their work.

Many of the maintenance objects used as configuration tools are already configured for revision control, but it is turned off by default. For example, business objects, algorithms, data areas, UI maps, and scripts are pre-configured for revision control.

Next in This Section

- Turning On Revision Control

- Configuring Maintenance Objects for Revision Control

Turning On Revision Control

Revision control is turned off by default for maintenance objects that are configured for revision control.

To turn on revision control:

1. Add the base package Checked Out zone to the Dashboard portal.

1. Navigate to Portal.

2. Search for the portal CI_DASHBOARD.

3. In the zone list for the Dashboard portal, add the zone F1-USRCHKOUT.

2. Set up application security.

For users to have access to revision control, they must belong to a user group that has access to the application service F1-OBJREVBOAS.

3. Add the revision control algorithm to the maintenance object that you want to have revision control.

This step must be repeated for each maintenance object that you want to have revision control.

1. Go to the Maintenance Object page and search for the maintenance object that you want to have revision control.

2. On the Algorithms tab of the maintenance object, add the revision control algorithm F1-REVCTL.

Configuring Maintenance Objects for Revision Control

Most configuration tool maintenance objects are pre-configured for revision control. You can configure other maintenance objects for revision control, as well.

To configure other objects for revision control:

1. Create a physical business object for the maintenance object.

A physical business object is one that has a schema with elements for all of the fields for the tables in the maintenance object. Follow these steps to create a physical business object:

1. Navigate to Business Object and specify the maintenance object.

2. Use the BO Schema dashboard zone to generate a schema that looks like the physical structure of the maintenance object.

3. Save the physical business object.

4. Go to the Maintenance Object page and search for the maintenance object for which you want to enable revision control.

5. On the Options tab of the maintenance object add a new option with the type Physical Business Object. The value is the name of the physical business object that you just created.

2. Add a foreign key reference to the maintenance object.

The revision control zones will display the standard information string for the object based on the foreign key reference. Follow these steps to create a foreign key reference:

1. Navigate to FK Reference and set up a foreign key reference for the primary table of the maintenance object.

2. Go to the Maintenance Object page and search for the maintenance object.

3. On the Options tab of the maintenance object, add a new option with the type Foreign Key Reference. The value is the name of the foreign key reference that you just created.

3. Add the Revision Control zone to the maintenance object.

1. Navigate to Context Sensitive Zone and search for the navigation key for the maintenance object.

2. Add the Revision Control zone, F1-OBJREVCTL, to that navigation key.

4. Add the revision control algorithm to the maintenance object.

1. Go to the Maintenance Object page and search for the maintenance object that you want to have revision control.

2. On the Algorithms tab of the maintenance object, add the revision control algorithm F1-REVCTL.

Working with the Revision Control Zones

You use two zones in the dashboard to work with revision controlled objects when revision control is turned on.

The Revision Control zone gives you several options for managing the revision of the currently displayed object. This zone also shows when the object was last revised and by whom. This information is linked to the Revision Control Search portal which lists all of the versions of the object.

Using the Revision Control zone you can:

- Check out an object in order to change it.

- Check in an object so others will be able to work on it.

- Revert the object back to where it was at the last checkout.

- Force a check in of an object that is checked out by someone else. You need special access rights to force a check in.

- Delete an object.

The Checked Out zone lists all of the objects that you currently have checked out. Clicking on an object listed in this zone will take you to the page for that object. The zone is collapsed if you have no objects checked out.

See Revision Control Search for more information about Check In, Force Check In, and Check Out one or more records simultaneously.

Next in This Section

- Checking Out an Object

- Checking In an Object

- Reverting Changes

- Forcing a Check In or Restore

- Deleting an Object

- Restoring an Object

Checking Out an Object

You must check out a revision controlled object in order to change it.

An object must have revision control turned on before you can check it out.

Note: When you first create or update an object a dialog box informs you that the object is under revision control. You can select OK to check out the object and save your changes, or Cancel to stop the update.

1. Go to the object that you want to work on.

2. Select Check Out in the Revision Control dashboard zone.

Checking In an Object

You must check in a revision controlled object in order to create a new version of it. Checking in an object also allows others to check it out.

1. Select a link in the Checked Out dashboard zone to go to the object that you want to check in.

2. Select Check In in the Revision Control dashboard zone.

3. Provide details about the version:

- In the External References field state the bug number, enhancement number, or a reason for the revision.

- In the Detailed Description field provide additional details regarding the revision.

- In the Keep Checked Out box specify if you want to keep the object checked out. If you keep the object checked out then your revision is a new version that you can restore later.

- In the Add To Bundle box specify if the object belongs to a bundle.

4. Select OK to check in the object.

Reverting Changes

Reverting changes will undo any changes you made since you checked out an object.

To revert changes:

1. Go to the object that you want to revert.

2. Select Revert in the Revision Control dashboard zone.

3. In the confirmation dialog box select OK to confirm the action or Cancel to return to the object page.

Once reverted, the object can be checked out by another user.

Forcing a Check In or Restore

You can force a check in if an object is checked out by another user and that person is not available to check it in.

You must have proper access rights to force a check in or restore.

To force a check in or restore:

1. Go to the object that is checked out by another user.

2. Select Force Check In or Force Restore in the Revision Control zone.

The Force Check In option is the same as a regular check in. The Force Restore option checks in the object and restores it to the previously checked in version.

Deleting an Object

If revision control is turned on for an object, you must use the Revision Control zone to delete it.

The object must be checked in before it can be deleted.

To delete a revision controlled object:

1. Go to the object that you want to delete.

2. Select Delete in the Revision Control zone.

3. Provide details regarding the deletion.

4. Select OK to delete the object.

The system creates a revision record before the object is deleted so that the deleted object can be restored.

Restoring an Object

You can restore an older version of either a current object or a deleted object.

An object must be checked in before an older version can be restored.

To restore an object:

1. Go to the Revision History portal for the object.

If the object was deleted you must search for it by going to Admin > Implementation Tools > Revision Control.

2. Select the desired entity by clicking the hyperlink in the Details column.

3. Locate the row in the version history that has the version that you want to restore and click Restore.

4. In the confirmation dialog box select OK to confirm the action or Cancel to return to the object page.

Working with the Revision Control Portal

The Revision Control portal lists information about each version of a revision controlled object.

You can navigate to the Revision Control portal from either a link in the Revision Control dashboard zone or by going to Revision Control portal through Admin.

If you want to find the Revision History entry for an earlier version or deleted object, you must search for the object using the Revision Control Search portal. Once you select the desired entry, you can restore a previous version of the object clicking Restore in the row for the version that you want to restore. You can also see the details of each version by clicking the broadcast icon for that version.

See Working with Revision Control Zones for more information about tasks that can be performed through Revision Control.

Next in This Section

- Revision Control Search

Revision Control Search

The Revision Control Search portal allows users to search for entities that have a revision history. The Search By dropdown provides additional functionality so that users can search for revisions that are associated to theirs or other’s user ID. Users can also Check In, Force Check In, or Check Out one or more entities through this portal.

Zone Options

- Revision History Search allows the user to query for revised entities based on a combination of criteria.

- In the User ID field, enter the user ID that is associated with a revision.

- In the External Reference field, enter an ID from an external system and is associated with a revision.

- In the Maintenance Object dropdown menu, select the Maintenance Object that is associated with a revision. The options in this list are populated by the Maintenance Objects that are active to track revision.

- In the Key 1, Key 2, Key 3, Key 4, Key 5 fields, enter the primary identifier(s) for the revised entity. Typically, the entity only requires a single key, but some entities require more than one (for example, Oracle Utilities Customer Care and Billing SA Type require CIS Division and SA Type).

- In the Status dropdown menu, select the entity status for your search.

- Check In allows the user to search for entities currently checked out to the logged in user ID and a combination of criteria. Once the search results are returned, the user has the option to select one or more entities and check them in.

- In the Maintenance Object dropdown menu, select the Maintenance Object that is associated with a revision. The options in this list are populated by the Maintenance Objects that are active to track revision.

- In the Key field, enter the primary identifier(s) for the revised entity.

- Force Check In allows the user to search for entities that are currently checked out by other user IDs (excluding the logged in user ID) based on a combination of criteria. Once the search results are returned, the user has the option to select one or more entities and check them in.

- In the Checked Out By User field, enter the user ID that has the entity in a Checked Out status.

- In the Maintenance Object dropdown menu, select the Maintenance Object that is associated with a revision. The options in this list are populated by the Maintenance Objects that are active to track revision.

- In the Key field, enter the primary identifier(s) for the revised entity.

- Check Out allows the user to search for entities currently checked in user ID and a combination of criteria. Once the search results are returned, the user has the option to select one or more entities and check them out.

- In the Maintenance Object dropdown menu, select the Maintenance Object that is associated with a revision. The options in this list are populated by the Maintenance Objects that are active to track revision.

- In the Key field, enter the primary identifier(s) for the revised entity.

Please see Working with Revision Control Zones for more information about working with individual entities.

Information Lifecycle Management

Information Lifecycle Management (ILM) is designed to address data management issues, with a combination of processes and policies so that the appropriate solution can be applied to each phase of the data’s lifecycle.

Data lifecycle typically refers to the fact that the most recent data is active in the system. As time progresses, the same data becomes old and unused. Older data becomes overhead to the application not only in terms of storage, but also in terms of performance. This older data’s impact can be reduced by using advanced compression techniques, and can be put into slower and cheaper storage media. Depending on how often it’s accessed, it can be removed from the system to make an overall savings of cost and performance. The target tables for ILM are transactional tables that have the potential to grow and become voluminous over time.

Next in This Section

- The Approach to Implementing Information Lifecycle Management

- Enabling ILM for Supported Maintenance Objects

- Ongoing ILM Tasks

- Archived Foreign Keys

The Approach to Implementing Information Lifecycle Management

This section describes the product approach to implementing ILM for its maintenance objects (MOs).

Note: The term archiving is used to cover any of the possible steps an implementation may take in their data management strategy, including compression, moving to cheaper storage, and removing the data altogether.

Age is the starting point of the ILM product implementation for some of its high volume data. In general "old" records are considered eligible to be archived. In the product solution, maintenance objects (MOs) that are enabled for ILM have an ILM Date on the primary table and the date is typically set to the record's creation date. (An MO may have special business rules for setting this date, in which case, a different date may be used to set the initial ILM Date). For implementations that want to use ILM to manage the records in the MO, the ILM date is used for defining partitions for the primary table.

There are cases where a record's age is not the only factor in determining whether or not it is eligible to be archived. There may be some MOs where an old record is still 'in progress' or 'active' and should not be archived. There may be other MOs where certain records should never be archived. To evaluate archive eligibility using information other than the ILM Date, the ILM enabled MOs include an ILM Archive switch that is used to explicitly mark records that have been evaluated and should be archived. This allows DBAs to monitor partitions based on age and the value of this switch to evaluate data that may be ready to be archived.

Evaluating records to determine their archive eligibility should still occur on “old” records. The expectation is that a large percentage of the old records will be eligible for archiving. The small number that may be ineligible could be updated with a more recent ILM date. This may cause the records to move into a different partition and can delay any further evaluation of those records until more time has passed.

For each MO enabled for ILM, the product provides a batch process to review “old” records and an ILM eligibility algorithm that contains business logic to evaluate the record and mark it eligible for archiving or not. The following sections provide more information about the batch process and algorithm functionality.

Next in This Section

- Batch Processes

- Eligibility Algorithm

Batch Processes

There are two main types of batch processes that manage data for ILM in the application: ILM Crawler Initiator and individual ILM Crawlers (one for each MO that is configured for ILM).

- ILM Crawler Initiator: (F1-ILMIN) - The ILM Crawler Initiator is a driver batch process that starts the individual ILM Crawler batch control as defined by the MO’s options.

Restartable: In case of server failure, the ILM Crawler Initiator process can be restarted, which will also restart the ILM Crawler processes.

- ILM Crawler: Each maintenance object that is configured for ILM defines an ILM Crawler. These are child batch processes that can be started either by the ILM Crawler Initiator or by a standalone batch submission.

The ILM Crawler batch process selects records whose retention period has elapsed and invokes the MO's ILM eligibility algorithm to determine if the record is ready to be archived or not. The ILM eligibility algorithm is responsible for setting the record's ILM archive switch to 'Y' and updating the ILM date, if necessary.

The retention period defines the period that records are considered active. It spans the system date and cutoff date (calculated as system date - retention days).

The retention days of an MO is derived as follows:

- If the ILM Retention Days MO option is defined, that is used.

- Otherwise, the Default Retention Days from the ILM Master Configuration record is used.

An error is issued if no retention period is found.

The crawler calculates the cutoff date and selects all records whose ILM archive switch is 'N' and whose ILM date is prior to the cutoff date. Each record returned is subject to ILM eligibility.

If the Override Cutoff Date parameter is supplied, it will be used instead of the calculated cutoff date. An error is issued if the override cutoff date is later than the calculated cutoff date. This parameter is useful if an object has many years of historic data eligible for archiving. Setting this parameter allows for widening the retention period and therefore limiting the process to a shorter period for initial processing

Note: ILM Crawler batch processes are designed not to interfere with current online or batch processing. Because of this, these batch processes can run throughout the day.

Note: Before passing the cut-off date to the algorithm, the ILM crawler ensures that the number of days calculated (System Date – override cut-off date) is more than the retention period specified in the MO option or the Master Configuration. If the number of days calculated is less than the retention period specified on the MO option or the Master Configuration, then it throws an error.

Eligibility Algorithm

Algorithms are triggered by the ILM batch crawler for the maintenance object. The key responsibility of the ILM algorithm is to determine whether a record can be marked as ready to be archived or not. If a record is determined to be ready for archive, the algorithm should set the ILM Archive switch to Y. If not, the algorithm leaves the switch set to N and may decide to update the ILM Date to something more recent (like the System Date) to ensure that the record does not get evaluated again until the future.

This algorithm is plugged into the Maintenance Object — Algorithm collection.

Oracle Utilities Application Framework provides the algorithm ILM Eligibility Based on Status (F1-ILMELIG) to support the ILM batch crawler. Refer to the algorithm type description for details about how this algorithm works. If a maintenance object has special business rules that are evaluated to determine the eligibility for ILM, a custom algorithm can be created and applied by the implementation team.

Enabling ILM for Supported Maintenance Objects

In order to enable ILM for one or more maintenance objects, several steps are needed in both the configuration and in the database. This section describes some configuration enabled by default and some steps that must be taken in order to fully implement ILM.

There is some configuration enabled by default, but it won’t be used unless ILM is fully configured. Each maintenance object that the product has configured for ILM has the following provided out of the box:

- Special Table Columns: Maintenance objects that support ILM include two specific columns: ILM Archive Switch (ILM_ARCH_SW) and ILM Date (ILM_DT).

- Crawler Batch Process: A "crawler" batch process is provided for each maintenance object that supports ILM and it is plugged into the MO as an option. Refer to Batch Processes for more information.

- ILM Eligibility Algorithm: Each maintenance object that is configured for ILM defines an eligibility algorithm that executes the logic to set the ILM Archive switch appropriately. This is plugged in to the MO algorithm collection.

If an implementation decides to implement ILM, there are steps that need to be followed, which are highlighted below.

Create the Master Configuration Record

The first step when enabling ILM is to create the ILM Configuration master configuration record.

The master configuration for ILM Configuration defines global parameters for all ILM eligible maintenance objects. For example, the Default Retention Period. In addition, your product may implement additional configuration. Refer to the embedded help for specific details about the information supported for your product's ILM configuration.

In addition, the user interface for this master configuration record displays summary information about all the maintenance objects that are configured to use ILM.

Confirm the Maintenance Objects to Enable

In viewing the list of maintenance objects that support ILM in the ILM master configuration page, your implementation may choose to enable ILM for only a subset of the supported maintenance objects. For example, some of the maintenance objects may not be relevant for your implementation. Or perhaps, the functionality provided by the maintenance object is used, but your implementation does not expect a high volume of data.

For each maintenance object that your implementation has confirmed for ILM, the following steps should be taken:

- Determine if the maintenance object should have a different default retention days than the system wide value defined on the master configuration. If so, use the MO option ILM Retention Period in Days to enter an override option for this maintenance object.

- Review the functionality of the ILM Eligibility algorithm provided by the product for this maintenance object. Each algorithm may support additional configuration based on business needs. If your organization has special business rules that aren't satisfied by the algorithm provided by the product, a custom algorithm may be provided to override the base algorithm.

For each maintenance object that your implementation does not want to enable for ILM, inactivate the eligibility algorithm. This will ensure that the ILM Crawler Initiator background process does not submit the crawler batch job for the maintenance object in question.

- Go to the Maintenance Object - Algorithm tab for each maintenance object and take note of the ILM Eligibility algorithm code.

- Go to the Maintenance Object - Option tab for the same maintenance object and add an option with an option type of Inactivate Algorithm and the value set to the ILM eligibility algorithm noted in the previous step.

Database Administrator Tasks

In order to implement ILM for each of the maintenance objects determined above, your database administrator must perform several steps in the database for the tables related to each MO. The following points are a summary of those steps. More detail can be found in the Information Lifecycle Management section of your product's Database Administration Guide.

- Initializing ILM Date: Your existing tables that are enabled for ILM may not have the ILM Date and ILM Archive switch initialized on all existing records. When choosing to enable ILM, a first step is to initialize this data based on recommendations provided in the DBA guide.

- Referential Integrity: The recommended partitioning strategy for child tables in a maintenance object is referential partitioning. In order to implement this, database referential integrity features must be enabled.

- Partitioning: This provides a way in which the data can segregate into multiple table partitions and will help in better management of the lifecycle of the data.

Schedule the ILM Crawler Initiator

The final step of enabling the system for ILM is to schedule the ILM crawler initiator F1-ILMIN regularly based on your implementation’s need. It is recommended to only schedule this batch process once all the required database activities are complete.

Ongoing ILM Tasks

For an environment where ILM is enabled, besides the periodic execution of the ILM crawler batch processes to review and mark records, your database administrator has ongoing tasks.

The DBA reviews and maintains partitions and identifies partitions that may warrant some type of archiving step. The Information Lifecycle Management section of your product's Database Administration Guide provides more information for your DBA.

Archived Foreign Keys

If your DBA chooses to archive a partition, there may be records in the system that refer to one of the archived records as a foreign key.

When a user attempts to view a record using a hyperlink or drill down mechanism, if the implementation of the navigation uses FK Reference functionality, the system will first check if the record exists. If not, it will display a message to the user indicating that the record has been archived.

Configuration Tools

This section describes tools to facilitate detailed business configuration. The configuration tools allow you to extend both the front-end user interface as well as create and define specialized back-end services.

Next in This Section

- Business Objects

- Business Services

- User Interface (UI) Maps

- Maintaining Managed Content

- Data Areas

- Advanced Schema Topics

- Business Event Log

- Miscellaneous Topics

Business Objects

A maintenance object defines the physical tables that are used to capture all the possible details for an entity in the system. A business object is tool provided to further define business rules for a maintenance object.

This section provides an overview of business objects and describes how to maintain them.

Next in This Section

- The Big Picture of Business Objects

- Defining Business Objects

- Advanced BO Tips and Techniques

- Defining Status Reasons

The Big Picture of Business Objects

The topics in this section describe background topics relevant to business objects.

Next in This Section

- What Is A Business Object?

- Business Object Inheritance

- Each Business Object Can Have A Different Lifecycle

- BO Algorithm Execution Summary

- Granting Access To Business Objects

What Is A Business Object?

A business object (BO) is a powerful tool used throughout the system. For many maintenance objects, a BO is a key attribute of the record used to define the data it captures, its user interface behavior and its business rules. Some business objects support the definition of a lifecycle, capturing different states that a record may go through, allowing for different business rules to be executed along the way. This type of business object is considered the “identifying” or “governing” business object. We will see later that other types of BOs exist that are different from the “identifying” business object.

The use of business objects allows for extensibility and customization of product delivered maintenance objects. There are many options to adjust the behavior of base delivered business objects. In addition, implementations may introduce their own business objects if the base product delivered objects do not meet their business needs.

Note: Not all maintenance objects in the product support business objects as a “identifying” or “governing” tool. This is the standard going forward for new maintenance objects. However, there are some maintenance objects created before this became a standard.

Next in This Section

- A Business Object Has a Schema

- A Business Object May Define Business Rules

- A Business Object Defines its User Interface

- Invoking A Business Object

- Determine the Identifying BO

- Base Business Objects

A Business Object Has a Schema

A business object has elements. The elements are a logical view of fields and columns in one of the maintenance object’s tables. The structure of a business object is defined using an XML schema. The main purpose of the schema is to identify all the elements from the maintenance object that are included in the business object and map them to the corresponding maintenance object fields. Every element in the BO schema must be stored somewhere in the maintenance object. The BO may not define elements that are derived.

When defining elements for the primary table or the language table (for an administrative object) there is no need to define the name of the physical table in the schema. The system infers this information. The following is a snippet of a schema:

<schema>

<migrationPlan mapField="MIGR_PLAN_CD" suppress="true" isPrimeKey="true"/>

<bo mapField="BUS_OBJ_CD" fkRef="F1-BUSOB"/>

<customizationOwner mapField="OWNER_FLG" suppress="input"/>

<version mapField="VERSION" suppress="true"/>

<description mapField="DESCR"/>

<longDescription mapField="DESCRLONG"/>

…

Many maintenance objects have child table collections (e.g., a collection of names for a person, or a collection of persons on an account). Depending on the requirements, the business object may define the full collection such that the user will maintain the information in a grid. However, the schema also supports “flattening” records in a child table so that they can be treated as if they were singular elements. The following are examples of each:

Example of a child table. This is a snippet of the Instructions collection on the migration plan business object. You can see that the list attribute defines the child table and all elements within it map to the appropriate column in that table.

<migrationPlanInstruction type="list" mapChild="F1_MIGR_PLAN_INSTR">

<migrationPlan mapField="MIGR_PLAN_CD" suppress="true"/>

<sequence mapField="PLAN_INSTR_SEQ" suppress="true"/>

<instructionSequence mapField="INSTR_SEQ"/>

<instructionType mapField="INSTR_TYPE_FLG"/>

<parentInstructionSequence mapField="PARENT_INSTR_SEQ"/>

<businessObject mapField="BUS_OBJ_CD" fkRef="F1-BOMO"/>

...

Example of a simple “flattened” field. The business object for Status Reason includes an element called Usage, which maps to a pre-defined characteristic of type F1–SRUSG. The “row” defines which child table is being flattened and the attributes of the row in that child that uniquely identify it.

<usage mdField="STATUS_RSN_USAGE" mapField="CHAR_VAL">

<row mapChild="F1_BUS_OBJ_STATUS_RSN_CHAR">

<CHAR_TYPE_CD is="F1-SRUSG"/>

<SEQ_NUM is="1"/>

</row>

</usage>

Example of a “flattened row”. This business object for Account includes a single row for the Person collection where only the “financially responsible, main” customer is defined. The “accountPerson” attribute defines one field from that row (the Person Id) and includes the ‘flattening’ criteria in the “row” information. In addition, a second field from that same row (“accountRelType”) is defined. Instead of having to repeat the flattening criteria, the “rowRef” attribute identifies the element that includes the flattening.

<accountPerson mapField="PER_ID">

<row mapChild="CI_ACCT_PER">

<MAIN_CUST_SW is="true"/>

<FIN_RESP_SW default="true"/>

</row>

</accountPerson>

<accountRelType mapField="ACCT_REL_TYPE_CD" rowRef="accountPerson" dataType="string"/>

Example of a “flattened list”. The business object for Tax Bill Type includes an list of valid algorithms for “bill completion”. The Sequence and the Algorithm are presented in a list. The list element identifies the child table and the ‘rowFilter’ identifies the information about the list that is common.

<taxBillCompletion type="list" mapChild="C1_TAX_BILL_TYPE_ALG">

<rowFilter suppress="true" private="true">

<TAX_BILL_TYPE_SEVT_FLG is="C1BC"/>

</rowFilter>

<sequence mapField="SEQ_NUM"/>

<algorithm mapField="ALG_CD" fkRef="F1-ALG"/>

</taxBillCompletion>

In addition, many maintenance objects support an XML structure field within the entity. These fields may be of data type CLOB or XML. One or more business object elements may be mapped to the MO's XML structure field. These elements may be defined in different logical places in the business object schema based on what makes sense for the business rules. When updating the MO, the system builds a type of XML document that includes all the elements mapped to the XML structure and stores it in one column. The following is an example of elements mapped to an XML column:

<filePath mdField="F1_FILE_PATH" mapXML="MST_CONFIG_DATA" required="true"/>

<characterEncoding mdField="F1_CHAR_ENCODING" mapXML="MST_CONFIG_DATA"/>

Note: If the MO’s XML structure field is of the data type XML, the database will allow searching for records based on that data, assuming appropriate indexes are defined. If the MO’s XML structure field is of the data type CLOB, indexing or joining to elements in this column via an SQL statement is not typically supported. Note that most MOs are currently using the CLOB data type for the XML structure column, if provided.

Some business objects may have child tables that allow data to be stored in an XML structure field. The schema language supports defining elements from those fields in your schema as well.

Besides including information about the physical “mapping” of the element to its appropriate table / field location in the maintenance object, the schema supports additional syntax to provide the ability to define basic validation and data manipulation rules, including:

- Identifying the primary key of the record or the primary key of the a row in a list.

- Identifying which elements are required when adding or changing a record.

- Default values when no data is supplied on an Add.

- For elements that are lookup values, the lookup may be specified to validate that the value of the element is a valid lookup value.

- For elements that are foreign keys to another table, the FK Reference may be specified to validate the data.

The system will check the validity of the data based on the schema definition obviating the need for any special algorithm to check this validation.

In addition, the schema language may include some attributes that are used to auto-render the view of the record on the user interface, such as the suppress attribute. Refer to BO Defines its User Interface for more information.

Note: Refer to Schema Syntax for the complete list of the XML nodes and attributes available to you when you construct a schema.

A business object’s schema may include a subset of the fields and tables defined in the maintenance object. There are two reasons for this:

- The fields or tables may not be applicable to the type of record the business object is governing. For example, a field that is specific to gas may not be included on a Device business object that is specific to electric meters.

- The information is not maintained through the business object, but rather maintained separately. For example, many BO based maintenance objects include a Log table. The records in the log table are typically not included the BO because they are viewed and maintained separately from the business object.

A Business Object May Define Business Rules

A business object may define business rules that govern the behavior of entities of this type.

- Simple element-level validation is supported by schema attributes. Note that element-level validation is executed before any maintenance object processing. For more sophisticated rules you create Validation algorithms and associate them with your business object. BO validation algorithms are only executed after "core validation" held in the MO is passed.

- A Pre-Processing algorithm may be used to "massage" a business object's elements prior to any maintenance object processing. For example, although simple element-level defaulting is supported by schema attributes. you may use this type of algorithm to default element values that are more sophisticated.

- A Post-Processing algorithm may be used to perform additional steps such as creating a To Do Entry or add a log record as part of the business object logical transaction. These plug-ins are executed after all the validation rules are executed.

- An Audit algorithm may be used to audit changes made to entities of this type.
Any time a business entity is added, changed or deleted, the system detects and summarizes the list of changes that took place in that transaction and hands it over to Audit plug-ins associated with the business object. These plug-ins are executed after all the post-processing rules are executed. It is the responsibility of such algorithms to log the changes if and where appropriate, for example as a log entry or an entry in an audit trail table or an entry in the business event log

By default all elements of the business object are subject to auditing. You can however mark certain elements to be excluded from the auditing process using the noAudit schema attribute. Marking an element as not auditable will prevent it from ever appearing as a changed element in the business object's audit plug-in spot. In addition, if the only elements that changed in a BO are ones marked to not audit, the audit algorithm is not even called. Refer to Schema Syntax for more information on this attribute.

Refer to Business Object - Algorithms for more information on the various types of algorithms.

The system applies business object rules (schema based and algorithms) whenever a business object instance is added, changed or deleted. This is only possible when the call is made via the maintenance object service. For example, when made via business object interaction ("invoke BO"), the MO's maintenance page or inbound web services that reference the BO. In addition the system must be able to determine the identifying business object associated with the actual object being processed. If the business object cannot be determined for a maintenance object instance business object rules are not applied.

Note:

Pre-Processing is special. The pre-processing algorithm plug-in spot is unique in that it only applies during a BO interaction. It is executed prior to any maintenance object processing. It means that when performing add, change or delete via the maintenance object service, the pre-processing plug-in is not executed.

CAUTION:

Direct entity updates bypass business rules! As mentioned above, it is the maintenance object service layer that applies business object rules. Processes that directly update entities not via the maintenance object service bypass any business object rules you may have configured.

Fastpath: Refer to BO Algorithm Execution Order for a summary of when these algorithms are executed with respect to lifecycle algorithms.

The plug-in spots described above are available for all business objects and they are executed by the system when processing adds or updates to the business object. It is possible for a specific maintenance object to define a special plug-in spot for business objects of that MO. When this happens, the maintenance object identifies the special algorithm entity lookup value as an MO option: Valid BO System Event, causing the BO Algorithm collection to include that system event in its list.

A Business Object Defines its User Interface

One of the responsibilities of an identifying business object is to define its user interface rules for viewing and maintenance of its record. The standard implementation for maintaining a business object is that a maintenance portal is used to display a record. This portal includes a "map" zone that displays the information about the business object. To add or make changes to a record, the user clicks a button that launches a maintenance BPA script which displays a maintenance "map".

The display and maintenance "maps" are driven by the business object. The BO may define a full UI map where all the information is displayed based on the map's HTML. Note that for a child BO, the maps may be inherited by a parent BO (or any BO "up the chain").

The standard going forward is to use schema definition and UI Hints to define user interface behavior so that a full UI map is not needed but rather the HTML is derived. The schema language includes some basic display attributes such as label and suppress. UI hints provide many additional tags and elements that allow dynamic generation of formatted UI Maps. For more complex behavior in the user interface, for example where javascript is needed, UI map fragments may be defined within the schema via UI hints. In this way only complex UI behavior warrants small snippets of javascript and HTML. However the rendering of standard fields can be dynamically rendered. UI map fragments also allow for derived fields to be included in the user interface.

A business object schema may include data areas for segments of its schema definition to allow for reusable components. In this case the data area would also include schema attributes and UI hints for the elements that it is including.

Note: Refer to UI Hint Syntax for detailed information about the supported syntax.

As mentioned in Business Object Inheritance, schemas are not inherited on a child business object. As such, when using UI hints for automatic UI rendering, the child BO must define the full schema with all the definitions. A good business object hierarchy will be designed for reuse meaning that the child BO will include the parent BO schema or alternatively, the BO schemas will include reusable data areas.

Invoking A Business Object

We have talked about defining a business object. This section describes how business objects are used throughout the system to view, add and update records.

- Various parameters for zones that are used to display data in the system include support for retrieving data by referencing a business object. The zone code will "invoke" the BO, meaning that the record will be retrieved using the referenced BO.

- The system's scripting language includes a step type to "invoke BO". This allows for BPA scripts, service scripts and plug-in scripts to retrieve information and add or update records using BO interaction.

- Inbound web services may reference a business object in its operations collection. This allows external systems to add or update records in our product via web service interaction.

Often when configuring a zone or writing a script, the BO to use in the "invoke BO" statement should be the identifying BO of the record. As such, often the script will include steps prior to the "invoke BO" step to "determine the identifying BO of the record" and once the identifying BO is found, the script step will invoke that BO. Note that zones and inbound web services reference a BO directly. In each case, if the BO to use should be dynamic, then the zone / inbound web service should reference a service script that can perform the steps to identify the BO and then invoke that BO.

It should be noted however that the BO used in an "invoke BO" statement (or referenced in an inbound web service) does not have to match the identifying BO for the record. Here are some examples of where this may be true:

- A script may only require a subset of elements for a record and not the entire record. In this case, it is better for performance purposes to define a special BO (sometimes called a "lite" BO or a "mini" BO) that only defines the needed elements. When the system retrieves the data, it will only access the tables that are included in the BO's schema definition. In addition, if there are no elements that map to an XML structure field, the system will skip any parsing of that column. Similarly, if a script is updating a subset of elements on a record, it may be beneficial to use a "mini" BO to do the updates.

Note: Please note the following with respect to using a mini BO. This BO is only used for its schema. This type of BO would not define algorithms or a lifecycle. Because the BO is special, it often should not be able to be used as any record’s identifying BO. To control that, these BOs are often configured to not allow new instances. Refer to Determine the Identifying BO for more information.

- The maintenance object to be added or updated in a script may not support business objects as "identifying BOs". For example, Batch Control maintenance object does not have an identifying BO. However, scripts may still wish to retrieve data (or make updates) to these types of records. An easy way to achieve that goal is to define a business object and use "invoke BO" to access the data.

Note: Not all maintenance objects support being maintained through a business object interaction. This is true in a small number of older objects where the underlying maintenance service includes additional functionality besides simply updating the database tables. These maintenance objects are identified via the MO option BO Maintenance, set to N.

- Some functionality may be trying to add or update records for a maintenance object in a 'physical' manner and do not want or need to use the object's identifying BO. Or the MO may not have an identifying BO. For example, revision control takes a snapshot of a record for audit purpose and to be able to restore a previous version. In this case, the system wants to capture a full "physical" view of the record. To do this, a special "physical" BO may be created that includes all (or most of) the columns and the child tables.

Note: Like the mini BO, the physical BO would not define algorithms or a lifecycle and should not be able to be used as any record’s identifying BO. To control that, these BOs are often configured to not allow new instances. Refer to Determine the Identifying BO for more information.

Note: To reiterate, the BO referenced in the "invoke BO" statement or referenced in an inbound web service does not have to match the identifying BO and does not have to be configured to "allow new instances".

Determine the Identifying BO

As mentioned in other topics, the identifying BO is the business object that governs the business rules for a record. This is the business object that the record will be validated against when any additions or changes are made to the record as long as updates are made via the maintenance service. This includes using "invoke BO" for add or update, using inbound web service interaction and for access to the maintenance page service (via an old style fixed page or via a business service).

How does the system determine the identifying BO? An algorithm plugged into the maintenance object (the Determine BO plug-in spot) is responsible for this. If the maintenance object is not configured with an algorithm for this plug-in spot, or no BO is found by the algorithm, no BO business rules are applied.

Most maintenance objects in the system capture the record's identifying BO directly on the record. However, it is possible to define the identifying BO somewhere else. For example, there may be some maintenance objects that are master or transaction objects with an associated "type" object where the identifying BO is defined on its "type" object. Note that the standard Determine BO algorithm plugged into most maintenance objects (F1-STD-DTMBO - Determine Standard Business Object) checks for these two conditions.

There may also be cases where a single identifying BO is used for all BOs for a given MO. This may be an option used for some older maintenance object created prior to the business object functionality when implementations wish to introduce custom business rules that are common for all records of that MO. The product provides a base algorithm type (F1–MOBO - Determine Specific Business Object) that captures the BO as a parameter.

Base Business Objects

For each maintenance object (MO) that supports an “identifying” business object, the type of business object provided by the product depends on the functionality and expected use by implementations. The following are some common patterns.

- There are MOs where the product provides base BOs that implementations may use if applicable for their business rules. In addition, it is expected that implementation will define custom BOs to support their business needs. Good examples of this type of MO are any of the various “rule” MOs. For example, calculation rule in Oracle Utilities Customer Care and Billing or the usage rule in Oracle Utilities Meter Data Management or the form rule in Oracle Public Sector Revenue Management. The product provides business objects for common rules but each implementation could have special rules that they need to implement and will need to create custom business objects.

- There are MOs where the product provides base BOs that supply common behavior for an object. Implementations may find that supplied the business objects match their business requirements and use the BOs as is. It is expected, however that for many implementations, their business rules will require additional elements to be captured or have special rules to apply. In this case the base business objects may be extended. This scenario may apply to ‘master’ data objects in various products such as the Device or Meter or Tax Role.

- There are MOs where the product may deliver a base BO that is not expected to satisfy most implementations because different jurisdictions or different implementations will typically have their own rules. In this case the base delivered BO can be used as a template or starting point for custom defined BOs. Some examples of this are Rebate Claim in Oracle Utilities Customer Care and Billing or the Appeal object in Oracle Public Sector Revenue Management.

- There are MOs where the expectation is that every implementation will have different requirements for the type of data to capture and the product will not supply base BOs that can be used as the “identifying” BO. However, it may supply a “parent” BO that defines the lifecycle and many of the business rules that it expects all records to follow. In these scenarios, the implementations will create “child” BOs that will serve as the “identifying” BOs and refer to the base “parent” BO for many of its rules through inheritance. Some examples of the are Tax Form in Oracle Public Sector Revenue Management or Activity in Oracle Utilities Mobile Workforce Management.

- There are some scenarios where the base product provides business objects and the expectation is that implementations will use the business objects as delivered with little or no customization. This is a case where the system used business objects to implement product functionality, not because there is an expectation that the implementers will extend the functionality, but because the business object model is the favored development tool even for the product. The objects delivered for Configuration Migration Assistant are an example.

Note: Not all maintenance objects in the product support business objects as a “identifying” or “governing” tool. This is the standard going forward for new maintenance objects. However, there are some maintenance objects created before this became a standard.

For all maintenance objects, the base product may provide additional BOs that are not meant to be “identifying” BOs, but instead are provided to support functionality to interact with the MO using the BO as a tool as described in Invoking a BO.

- One or more “mini” or “lite” BOs may be supplied for a maintenance object. This may be found when the product has functionality to retrieve a subset of elements for the maintenance object via scripting or via a user interface.

- A “physical” BO may be supplied. This a BO that typically includes all tables and all fields of the maintenance object in there “physical” form. In other words, there is no “flattening” of child tables and any XML structure fields are defined as a single field. Physical BOs are used in system processing where the full record needs to be captured as is. Some functionality that uses a physical BO includes bundling, revision control and the pre-compare algorithm for CMA to adjust data prior to comparing.

Business Object Inheritance

A business object may inherit business rules from another business object by referencing the latter as its parent. A child business object can also have children, and so on. A parent's rules automatically apply to all of its children (no compilation - it's immediate). A child business object can always introduce rules of its own but never remove or bypass an inherited rule.

The following is an illustration of multiple levels of business object inheritance.

Notice how the "Business Customer" business object extends its parent rules to also enforce a credit history check on all types of customers associated with its child business objects.

Most types of business object system events allows for multiple algorithms to be executed. For example, you can have multiple Validation algorithms defined for a business object. For these, the system executes all algorithms at all levels in the inheritance chain starting from the highest-level parent business object moving on to lower levels.

Other types of system events allows for a single algorithm to be executed. For example, you can only have one Information algorithm to format the standard description of a business object instance. For these, the system executes the one at the level nearest to the business object currently being processed.

Note: The parent and its children must reference the same maintenance object.

Note: Data structures are not inherited. While you can declare schemas on parent business objects, their children will not inherit them. A good practice is to design child business object schemas to include their parent business object's schema.

Note: User interface maps are inherited. When determining if the business object has a UI map to use for UI rendering, the system looks for display and maintenance maps linked to the BO as options. If the identifying BO does not have maps defined, the system follows “up the chain” of inheritance until it finds a map to use. This allows for a child BO to be used to extend business rules of a parent BO but inherit its user interface behavior. Refer to Business Object Defines its User Interface for more information.

Note: Use Inheritance Wisely. While it is intellectually attractive to abstract behavior into parent BOs to avoid redundant logic and simplify maintenance, before doing this weigh the reuse benefits against the cost in transparency, as it is not easy to maintain a complex hierarchy of business objects.

Each Business Object Can Have A Different Lifecycle

Many maintenance objects have a status column that holds the business entity's current state within its lifecycle. Rules that govern lifecycle state transition (e.g., what is its initial state, when can it transition to another state, etc.) and the behavior associated with each state are referred to as lifecycle rules. Older Maintenance Objects, such as To Do Entry, have predefined lifecycles whose rules are governed by the base-package and cannot be changed. The lifecycle of newer Maintenance Objects exists in business object meta-data and as such considered softly defined. This allows you to have completely different lifecycle rules for business objects belonging to the same maintenance object.

Here are examples of two business objects with different lifecycles that belong to the same maintenance object.

Note: A Maintenance Object supports soft lifecycle rules if it is defined with a Status Field Maintenance Object option.

The topics that follow describe important lifecycle oriented concepts.

Next in This Section

- Valid States versus State Transition Rules

- One Initial State and Multiple Final States

- State-Specific Business Rules

- Inheriting Lifecycle

- Auto-Transition

- Keeping An Entity In Its Last Successful State

- Monitoring Batch Processes

- Transitory States

- State Transitions Are Audited

- Required Elements Before Entering A State

- Capturing a Reason for Entering a State

Valid States versus State Transition Rules

The boxes in the above diagram show the potential valid states a business entity of the above business object can be in. The lines between the boxes indicate the state transition rules. These rules govern the states it can move to while in a given state. For example, the above diagram indicates a high bill complaint that's in the Lodged state can be either Canceled or moved into the Preliminary Investigation state.

When you set up a business object, you define both its valid states and the state transition rules.

One Initial State and Multiple Final States

When you set up lifecycle states, you must pick one as the initial state. The initial state is the state assigned to new entities associated with the business object. For example, the above high-bill complaint business object defines an initial state of Lodged, whereas the literature request one defines an initial state of Literature Sent.

You must also define which statuses are considered to be "final". Typically when an entity reaches a "final" state, its lifecycle is considered complete and no further processing is necessary.

Note: Allowing An Entity To Be "Reopened". You can set up your state transition rules to allow a business entity to be "reopened" (i.e., to be moved from a final state to a non-final state). Neither of the above examples allows this, but it is possible if you configure your business object accordingly.

State-Specific Business Rules

For each state in a business object's lifecycle, you can define the following types of business rules.

Fastpath: Refer to BO Algorithm Execution Order for a summary of when these lifecycle algorithms are executed with respect to BO level algorithms.

Next in This Section

- Logic To Take Place When Entering A State

- Logic To Take Place When Exiting A State

- Monitor Rules

Logic To Take Place When Entering A State

You can define algorithms that execute before a business entity enters a given state. For example, you could develop an algorithm that requires a cancellation reason before an entity is allowed to enter the Canceled state.

You can also incorporate state auto-transitioning logic within this type of algorithms. Refer to auto-transition for more information.

Also note that when a record is processed by the monitor batch program, by default the BO Post Processing, BO Audit and MO Audit algorithms are not executed. However, it is possible for an enter algorithm to indicate that the other algorithms should be executed by the batch process by setting the “force post processing” indicator to true.

Logic To Take Place When Exiting A State

You can define algorithms that execute when a business entity exists a given state. For example, you could develop an algorithm that clears out error messages when a given entity exits the Error state.

Also note that when a record is processed by the monitor batch program, by default the BO Post Processing, BO Audit and MO Audit algorithms are not executed. However, it is possible for an exit algorithm to indicate that the other algorithms should be executed by the batch process by setting the “force post processing” indicator to true.

Monitor Rules

You can define algorithms to monitor a business entity while it is in a given state. This type of logic is typically used to check if the conditions necessary to transition the entity to another state exist (and, if so, transition it). For example, transition an entity to the Canceled state if it's been in the Error state too long. Another common use is to perform ancillary work while an entity is in a given state. For example, update statistics held on the object while it's in the Active state.

Monitor algorithms are invoked when a business entity first enters a state and periodically after that in batch. You have the option to defer the monitoring of a specific state until a specific monitoring batch job runs. You do so by associating the state with a specific monitoring process. In this case the system will only execute the monitoring rules of this state when that specific batch process runs. This is useful when processing one type of record typically creates another type of record. You may want the processing of the second set of records to be deferred to a later time.

A monitor algorithm can carry out any business logic. In addition it can optionally tell the system to do either of the following:

- Stop monitoring and transition to another state. The system will not call any further monitoring algorithm plugged in on the state and attempt to transition the entity to the requested new state.

- Stop monitoring. Same as above except that no transition takes place. You may want to use this option to prevent transitions while some condition is true.

If none of the above is requested the system keeps executing subsequent monitoring algorithms.

Also note that when a record is processed by the monitor batch program, by default the BO Post Processing, BO Audit and MO Audit algorithms are not executed. However, it is possible for a monitor algorithm to indicate that the other algorithms should be executed by the batch process by setting the “force post processing” indicator to true.

Fastpath: Refer to Business Object - Lifecycle for more information on how to set up state-specific algorithms.

Inheriting Lifecycle

If a business object references a parent business object, it always inherits its lifecycle from the highest-level business object in the hierarchy. In other words, only the highest-level parent business object can define the lifecycle and the valid state transitions for each state. Child business objects, in all levels, may still extend the business rules for a given state by introducing their own state-specific algorithms.

The system executes all state-specific algorithms at all levels in the inheritance chain starting from the highest-level parent business object moving on to lower levels.

Auto-Transition

In a single transition from one state to another, the system first executes the Exit algorithms of the current state, transitions the entity to the new state, executes the Enter algorithms of the new state followed by its Monitor algorithms. At this point if a Monitor algorithm determines that the entity should be further automatically transitioned to another state the remaining monitoring algorithm defined for the current state are not executed and the system initiates yet another transition cycle.

Notice that an Enter algorithm can also tell the system to automatically transition the entity to another state. In this case the remaining Enter algorithm as well as all Monitor algorithms defined for the current state are not executed.

The following illustration provides an example of an auto-transition chain of events.

In this example a business entity is in a Pending state. While in that state a Monitor algorithm determines to auto-transition it to the Denied state. At this point the following takes place:

- No further Monitor algorithms of the Pending state are executed

- Pending state Exit algorithms are executed

- The system transitions the entity to the Denied state

- Denied state Enter algorithms are executed. No further auto-transition is requested.

- Denied state Monitor algorithms are executed. No further auto-transition is requested.

Keeping An Entity In Its Last Successful State

By default, any error encountered while transitioning a business entity from one state to another rolls back all changes leaving the entity in its original state.

When applicable, the Maintenance Object can be configured to always keep an entity in its last successful state rather than rolling all the way back to the original state. This practice is often referred to as "taking save-points". In case of an error, the entity is rolled back to the last successfully entered state and the error is logged on the maintenance object's log. Notice that with this approach no error is returned to the calling process, the error is just logged.

The logic to properly log the error is in a Transition Error Maintenance Object plug-in. The system considers a maintenance object to practice "save-points" when such an algorithm is plugged into it.

Even if the maintenance object practices "save-points", in case of an error the system will not keep an entity in the last successfully entered state if that state is either marked as transitory or one of its Enter algorithms has determined that the entity should proceed to a next state. The system will roll back to the first previous state that does not match these conditions.

Monitoring Batch Processes

A monitor batch process may be used to transition a business object into its next state by executing the monitor algorithms associated with the current state of the entity. The use cases for performing the monitor logic in batch are as follows:

- The record may be waiting for something else to occur before transitioning. The monitor algorithm may be coded to determine if the condition is satisfied and initiate the transition then. For example perhaps when entering a state, a field activity is generated and the record should exit the state when the field activity is complete. The monitor algorithm can check the status of the field activity.

- Perhaps a record is added or updated manually and the next step in the BO lifecycle includes a large amount of processing such that the logic should occur in batch. In this case the BO status is configured with an explicit reference to a batch control (called a “deferred” batch control), which indicates to the system that the monitor algorithms should not be performed automatically (but should be deferred to batch). Later when the batch process runs, it selects all the records to process to progress the records.

Note: When a status includes a deferred batch control, it may also be configured to allow a user to manually transition the record to the next state rather than waiting for batch. When a user manually transitions a record that includes monitor algorithms, those algorithms are not executed.

- Perhaps a record is added or updated in batch, but a subsequent step in the overall lifecycle should be processed later. This may be accomplished by ensuring that the batch control linked to the state to process later does not match the batch control that added or updated the record.

- Monitor processes may also be used to periodically perform some logic related to the record without actually transitioning the record.

Note that only the parent business object may refer to a deferred monitor batch process. However, any business object in the “inheritance” chain may be configured with monitor algorithms, which will all be executed.

The base package provides a periodic monitoring batch process for each maintenance object that supports a configurable BO lifecycle. The process periodically executes the monitoring algorithms associated with the current state of an entity, excluding states explicitly referencing a deferred monitoring batch process that is for a different batch control.

A deferred monitoring process works in the same way except that it considers entities whose current state references this particular batch control as their monitor process in addition to records that don’t refer to any batch controls as their monitor process. Deferred monitoring is only needed when a given state should not execute its monitor algorithms immediately upon entering the state, but rather when the batch process is specifically executed.

Note: MO option configuration. The maintenance object includes options to indicate the batch controls delivered for periodic and deferred monitor batch controls.

Your business rules will dictate the execution frequency of each monitoring process and the order in which they should be scheduled. Refer to Monitor Background Processes in the background process chapter for more information about the parameters supported for this type of batch process.

Note: Updates to the business object. When the monitor algorithms indicate that the business object should transition, the monitor batch processes are responsible for ensuring the business object is transitioned appropriately and that the appropriate exit, enter and monitor algorithms are executed. Please note that the business object is not updated using a call to the maintenance object service and therefore by default the business rules plugged in to the business object are not executed. However, it is possible for an Enter algorithm, Exit algorithm or Monitor algorithm to indicate that the other algorithms should be executed by the batch process. If the “force post processing” indicator is set to true, then the batch process invokes the BO Post Processing, BO Audit and MO Audit algorithms.

Transitory States

You can define a state as Transitory if you do not wish the business entity to ever exist in that particular state.

The following illustrates a lifecycle with a transitory Validate state.

In this example, the business entity is saved still not validated in the Pending state. At some point, the user is ready to submit the entity for validation and transitions it into a transitory state Validate whose Enter rules contain the validation logic. The responsibility of the transitory state's Enter algorithms is to decide if the entity is valid or in error and then transitions it into the appropriate final state. In this scenario, you may not ever want the business entity to exist in the Validate state.

Let's also assume that the maintenance object in this example is practicing "save-points" and requires the entity to be kept in its last successful state. If an error were to occur during the transition from Validate to the next state, the system would roll back the entity back to Pending, and not Validate even though the entity has successfully entered the Validate state. Refer to the Auto Transition section for more information.

State Transitions Are Audited

Most Maintenance Objects that support soft lifecycle definition also have a log to hold significant events throughout a business entity's lifecycle. For example, log entries are created to record:

- When the business entity is created (and who created it)

- When its status changes (and who changed it)

- If a transition error occurred (and the error message)

- References to other objects created throughout the entity's lifecycle. For example, if a To Do entry is created as part of processing the entity, the To Do Entry is referenced in the log.

- Manual entries added by a user (think of these as "diary" entries)

When a business entity is first created and when it transitions into a new state the system calls Transition algorithm(s) plugged in on the Maintenance Object to record these events. If the maintenance object supports a log these events can be captures as log entries.

Note: Most base package maintenance objects supporting a log may already provide state transition logging as part of their core logic. In this case you only need to provide a Transition plug-in if you wish to override base logging logic with your own.

Required Elements Before Entering A State

You can define additional elements that are required before a business entity can enter a given state. For example, let's assume that a Cancel Reason must be defined before an object can enter the Canceled state. You do this by indicating that element as a Required Element state-specific option on the appropriate state on the business object.

Capturing a Reason for Entering a State

Some business objects support configuring certain states to allow or require a status reason when an object enters the state. The product provides a centralized status reason table that may be used to define the valid BO status reasons for various business objects and various states. The status reasons are defined using the Status Reason portal.

The following sections provide additional information about the BO status reason functionality.

Maintenance Object Must Support Status Reason

In order for a business object to use the centralized status reason table to define reasons, the maintenance object must first support the status reason. MOs that support status reason have the following characteristics:

- The primary table includes a column for Status Reason. This represents the status reason for the record’s current status, if applicable.

- The log table includes a column for Status Reason. The standard logic for capturing a log record when entering a state also captures the status reason, if applicable. This allows a user to review the history of the changes in status and the status reason captured for a previous state transition, if applicable.

- The maintenance object option collection includes an option that defines the Status Reason field. This setting is a trigger for business objects of this MO to be able to configure states to allow or require status reason.

Business Object State Indicates if Reasons are Applicable

Once the MO is configured to support status reason, configuration on the business object is required to indicate the states where a reason is applicable. States may be configured to require status reasons, allow status reasons as optional or not allow status reasons. With this configuration, the framework will automatically get the list of valid reasons for a state that allows or requires them and then prompt the user for a status reason when a manual state transition occurs for that state. It also automatically triggers an error if the state requires a status reason and no reason is provided.

Note: The status reason configuration on the business object state is customizable. That means that for a product owned business object, an implementation may opt to change the delivered configuration.

Status reasons are defined for the parent (or “lifecycle”) business object. All business objects in the hierarchy of the parent business object have the same valid reasons for their states.

The status reason code must be unique for the centralized status reason table. Business object and status are required fields, so it is not possible to share a common reason code (like “Not applicable”) across multiple business objects or states. If multiple BOs / states want to support a reason “Not applicable” then each must define a unique record for it. This point should be considered when planning for your status reasons.

Selectable vs. Not Selectable

When defining a status reason, you may indicate whether it’s Selectable or Not Selectable. When a manual transition is performed and a user is prompted for a status reason, only the Selectable reasons are presented. The Not Selectable reasons may be defined to support transitions that occur via algorithm processing.

Note: The Selectable setting is customizable. That means that if a product provides a base owned status reason for a business object state, an implementation may opt to change whether it is selectable or not. Careful consideration should be made before changing a base delivered status reason from Not Selectable to Selectable as this may affect base provided algorithm functionality that could be relying on the setting of Not Selectable.

Status Reason Business Object

The status reason maintenance object, as with many maintenance objects in the product, references a business object used to define attributes and behavior related to defining status reasons. The framework provides a business object for status reason (F1–BOStatusReason). For the business objects that have states that require a status reason (let’s call these “transactional BOs”), if there is some special logic required for defining the status reasons, it is possible to define a different status reason BO. In this situation, the override status reason BO to use for capturing status reasons should be defined as a BO option on the transactional BO using the Status Reason Business Object option type. If a transactional BO does not define any status reason BO option, then the F1–BOStatusReason is used when adding a status reason.

Defining a Usage

The base product status reason BO provides the ability to define a “usage” value. This is useful for algorithms that perform state transitions where a status reason is needed and where the algorithm is usable by more than one business object. In this case, the status reason to use cannot be provided as a parameter because each business object must define its own set of status reasons for each state. The Usage value can be used instead. Each business object can configure the status reason to use in the algorithm and set the appropriate usage value. The algorithm can reference the usage value and retrieve the correct status reason to use based on the record’s transactional BO.

The status reason business object provided with the framework product (F1–BOStatusReason) supports capturing a usage. The valid usage values are defined in the Status Reason Usage characteristic type.

Alternatives for Defining Reasons

There may be business objects in the system that capture reasons that are defined somewhere besides the BO status reason table. For example, some objects may have an explicit administrative table for status reasons. Some objects may use a Lookup or an Extendable Lookup to capture reasons. Refer to the business object description for information about how valid reasons are defined, if applicable.

If a business object supports a reason that is not related to a state transition (such as a creation reason), the BO status reason would not be used. One of the alternate methods for defining a reason, described above, would be used.

BO Algorithm Execution Summary

This table highlights the processing steps that occur when adding or changing a record that is governed by a business object.

Invoke BO

Event

Comments

BO Pre-processing algorithms executed

These algorithms are only executed when Invoke BO is used. The business object in the Invoke BO is the one whose rules are executed.

MO Processing

Event

Comments

Determine if status has changed.

The system keeps a note of the new status value but initially proceeds with the old value.

MO Processing.

Standard MO processing, including MO validation is executed.

Determine BO algorithm executed.

The MO level algorithm is executed to determine the identifying BO.

BO Validation algorithms executed.

State transition rules are performed if the status has changed.

BO Status Exit algorithms for the “old” status executed.

Status updated to the new value.

BO Status Enter algorithms for the “new” status executed.

If no error — MO Transition algorithms are executed.

Fastpath: Refer to State Transitions are Audited for more information.

If error and there are “save points” the MO Transition Error algorithms are executed.

Fastpath: Refer to Keeping An Entity In Its Last Successful State for more information.

Otherwise, the error is reported.

BO Status Monitor algorithms are executed.

If the record transitions again, the prior step (State transition rule step) is repeated for the new transition.

BO Post-processing algorithms are executed.

BO Audit algorithms are executed.

These algorithms are only executed if the system detects a change in elements that are not marked with “no audit”.

Note: To emphasize, the steps in the MO Processing table are only executed when the maintenance object service is invoked. Any add or update initiated by an “invoke BO” statement will invoke the MO service. This is also true for web service that invoke the business object. The Monitor Batch Process does not invoke the maintenance service. By default the monitor batch process only executes the monitor algorithms and the state transition rules (if the monitor algorithms indicate that a status change should occur). However, it is possible for an Enter algorithm, Exit algorithm or Monitor algorithm to indicate that the other algorithms should be executed by the batch process. If the “force post processing” indicator is set to true, then the batch process invokes the BO Post Processing, BO Audit and MO Audit algorithms.

Note: For records that do not have a status, the state transition rules and the monitor rules are not applicable.

Granting Access To Business Objects

Every business object must reference an application service. When you link a business object to an application service, you are granting all users in the group access to its instances. You can prevent users from transitioning a business object into specific states by correlating each business object status with each application service action (and then don't give the user group rights to the related action).

Fastpath: Refer to The Big Picture Of Application Security for information about granting users access rights to an application service.

The system checks if a user has access rights each time the application is invoked to add, change, delete, read, or transition a business object. However, if a business object invokes another business object, we assume that access was controlled by the initial business object invocation and we do not check access for other business objects that it invokes. In other words, access rights are only checked for the initial business object invoked in a service call.

In order to apply business object security the system must be able to determine the business object associated with the actual object being processed. To do that the Maintenance Object itself has to have a Determine BO algorithm plugged in. If this algorithm is not plugged in or it cannot determine the BO on the MO, the system will not invoke any BO rules. If the business object cannot be determined for a maintenance object instance, business object security is not checked. In this case the system checks the user's access rights using standard maintenance object security.

Note: Parent business objects are ignored. If a child business object exists, a user need only have access to the child business object's application service (not to every application service in the business object hierarchy).

Defining Business Objects

The topics in this section describe how to maintain business objects.

Note that several context sensitive dashboard zones appear on this page and are visible on all tabs.

- Schema Tips. This zone provides several links to launch help topics related to valid schema syntax and UI Hint syntax in one click.

- View UI Rendering. This zone provides buttons to view the automatic rendering of the Display map or Input map based on the attributes defined in the schema, including UI hints.

- Generate Schema. This zone includes a button that can be used to generate a “physical” schema based on the maintenance object definition. The element names are taken from the Java field name for each column. Once generated, adjust the schema as desired.

- Create a BO Algorithm. This zone includes a button to create a script based algorithm related to this business object. You are then prompted for information regarding the plug-in spot (BO or BO Status) and the system event, the name, description, etc. Once all the information is provided, the system creates an algorithm type, algorithm, links the algorithm to the business object, creates the script and brings you to the script step to start defining the logic for the plug-in script.

- BOs Linked to the MO. This zone displays other business objects for the same maintenance object as the BO currently displayed. You may drill into any of the other BOs by clicking its description.

Next in This Section

- Business Object - Main

- Business Object - Schema

- Business Object - Algorithms

- Business Object - Lifecycle

- Business Object - Summary

Business Object - Main

Use this page to define basic information about a business object. Open this page using Admin > System > Business Object

Description of Page

Enter a unique Business Object name and Description. Use the Detailed Description to describe the purpose of this business object in detail. Owner indicates if this business object is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new business object, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Enter the Maintenance Object that is used to maintain objects of this type.

Enter a Parent Business Object from which to inherit business rules.

Lifecycle Business Object is only displayed for child business objects, i.e. those that reference a parent business object. It displays the highest-level business object in the inheritance hierarchy. Refer to Inheriting Lifecycle for more information.

Application Service is the application service that is used to provide security for the business object. Refer to Granting Access To Business Objects for more information. The application service on the child business object must have the same valid actions as the application service on the parent business object.

Use Instance Control to allow or prevent new entities from referencing the business object. Typically only the identifying BOs are marked to allow new instances.

Click the View Schema hyperlink to view the business object's expanded schema definition. Doing this opens the schema viewer window.

Click the View XSD hyperlink to view the business object's expanded schema definition in XSD format.

Click the View MO hyperlink to view the maintenance object in the Maintenance Object Viewer. You may find it useful to leave the application viewer window open while defining your business object schema.

The options grid allows you to configure the business object to support extensible options. Select the Option Type drop-down to define its Value. Detailed Description may display additional information on the option type. Set the Sequence to 1 unless the option can have more than one value. Owner indicates if this option is owned by the base package or by your implementation (Customer Modification).

Note: You can add new options types. Your implementation may want to add additional option types. For example, your implementation may have plug-in driven logic that would benefit from a new option. To do that, add your new values to the customizable lookup field BUS_OBJ_OPT_FLG. If you add a new option type for a business option, you must update its maintenance object to declare this new option type. Otherwise, it won't appear on the option type dropdown. You do that by referencing the new option type as a Valid BO Option Type maintenance object option.

Where Used

Follow this link to open the data dictionary to view the tables that reference F1_BUS_OBJ.

Business Object - Schema

Use this page to maintain a business object's schema. Open this page using Admin > System > Business Object and then navigate to the Schema tab.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays main attributes of the business object.

Click the View Schema hyperlink to view the business object's expanded schema definition. Doing this opens the schema viewer window.

Click the View XSD hyperlink to view the business object's expanded schema definition in XSD format.

The Schema Designer zone allows you to edit the business object's schema. The purpose of the schema is to describe the business object's properties and map them to corresponding maintenance object fields.

Fastpath: Refer to Schema Syntax and UI Hint syntax for a complete list of the XML nodes and attributes available to you when you construct a schema. Also note that the Schema Tips zone in the dashboard provides links to launch these help topics directly.

Note: Generating a Schema A context sensitive "Generate Schema" zone is associated with this page. The zone provides a button that allows the user to generate a basic schema that includes all the fields for all the tables for the BO’s maintenance object.

Note: View UI Rendering. A context sensitive "View UI Rendering" zone is associated with this page. The zone is useful for business objects that define the user interface detail using schema attributes and UI Hints. The buttons allow you to view the automatically rendered display and input maps.

The Schema Usage Tree zone summarizes all cross-references to this schema. These may be other schemas, scripts, and web services. For each type of referencing entity, the tree displays a summary node showing a total count of referencing items. The summary node appears if at least one referencing item exists. Expand the node to list the referencing items and use their description to navigate to their corresponding pages.

Business Object - Algorithms

Use this page to maintain a business object's algorithms. Open this page using Admin > System > Business Object and then navigate to the Algorithms tab.

Description of Page

The Algorithms grid contains algorithms that control important functions for entities defined by this business object. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

- If the algorithm is implemented as a script, a link to the Script is provided. Refer to Plug-In Scripts for more information.

- Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

The following table describes each System Event. Refer to A Business Object May Define Business Rules for more information about these system events.

System Event

Optional / Required

Description

Audit

Optional

Algorithms of this type may be used to audit certain changes made to business object instances.

The system hands over to the algorithms a summary of all the elements that were changed throughout a specific call to update an object. Excluded from this processing are elements explicitly marked on the schema as requiring no audit. For each element its original value before the change as well as its new value are provided.

It is the responsibility of the algorithms to record corresponding audit information.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object inheritance for more information.

Click here to see the algorithm types available for this system event.

Information

Optional

We use the term "Business Object Information" to describe the basic information that appears throughout the system to describe an entity defined by the business object. The data that appears in this information description is constructed using this algorithm.

The system invokes a single algorithm of this type. If more than one algorithm is plugged-in the system invokes the one with the greatest sequence number found on the business object closest to the current business object in the inheritance hierarchy. Refer to Business Object inheritance for more information.

Click here to see the algorithm types available for this system event.

Post-Processing

Optional

Algorithms of this type may be used to perform additional business logic after a business object instance has been processed.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object inheritance for more information.

Click here to see the algorithm types available for this system event.

Pre-Processing

Optional

Algorithms of this type further populates a request to maintain a business object instance right before it is processed.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object inheritance for more information.

Click here to see the algorithm types available for this system event.

Validation

Optional

Algorithms of this type may be used to validate a business object instance when added, updated or deleted.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object inheritance for more information.

Click here to see the algorithm types available for this system event.

Fastpath: Refer to BO Algorithm Execution Summary for more information about how these algorithms fit within the business object processing.

Note: Generate Algorithm. A context sensitive "Generate a BO Algorithm" zone is associated with this page. Refer to Defining Business Objects for more information about this zone.

Note: You can add new system events. Your implementation may want to add additional business object oriented system events. For example, your implementation may have plug-in driven logic that would benefit from a new system event. To do that, add your new values to the customizable lookup field BO_SEVT_FLG. If you add a new business object system event, you must update the maintenance object to declare this new system event. Otherwise, it won't appear on the system event dropdown. You do that by referencing the new system event as a Valid BO System Event maintenance object option.

Note: You can inactivate algorithms on base Business Objects. Your implementation may want to use a business object provided by the base product, but may want to inactivate one or more algorithms provided by the base business object. To do that, on the business object where this algorithm is referenced, go to the options grid on Business Object - Main and add a new option, setting the option type to Inactive Algorithm and setting the option value to the algorithm code.

Business Object - Lifecycle

Use this page to maintain a business object's lifecycle oriented business rules and options. Open this page using Admin > System > Business Object and then navigate to the Lifecycle tab.

Description of Page

The Status accordion contains an entry for every status in the object's lifecycle. The entry appears differently for a child business object as it can only extend its inherited lifecycle by introducing algorithms and options of its own.

Use Status to define the unique identifier of the status. This is not the status's description, it is simply the unique identifier used by the system. Only the highest-level business object can define lifecycle statuses. For a child business object the inherited status description is displayed allowing navigation to the corresponding entry on the business object defining the lifecycle.

Use Description to define the label of the status. This field is hidden for a child business object.

Use Access Mode to define the action associated with this status. Refer to Access Rights for the details of how to use this field to restrict which users can transition a business entity into this state. This field is hidden for a child business object.

Enter a Monitor Process to defer the monitoring of entities in this state until the specific batch process runs. Refer to Monitor Rules for more information. This field is hidden for a child business object.

The Status Reason dropdown indicates if users should be prompted to provide a specific reason when the business object enters this state. This field appears only if the Status Reason Field is configured as an option on the business object's maintenance object. Valid values are blank, Optional, and Required. The default value is blank (users are not prompted to provide a status reason). See Configuring Status Reasons for more information about status reasons.

Use Status Condition to define if this status is an Initial, Interim or Final state. Refer to One Initial State and Multiple Final States for more information about how this field is used. This field is hidden for a child business object.

Use Transitory State to indicate whether a business entity should ever exist in this state. Only Initial or Interim states can have a transitory state value of No. Refer to transitory states for more information. This field is hidden for a child business object.

Use Alert Flag to indicate that being in this state warrants an application alert. This may be used by custom logic to provide an alert to a user that entities exist in this state. This field is hidden for a child business object.

Use Display Sequence to define the relative order of this status for display purposes. For example when displayed on the status accordion and on the summary tab page. This field is hidden for a child business object.

Algorithms

The Algorithms grid contains algorithms that control important functions for a given status. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

- If the algorithm is implemented as a script, a link to the Script is provided. Refer to Plug-In Scripts for more information.

- Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

The following table describes each System Event.

System Event

Optional / Required

Description

Enter

Optional

Algorithms of this type apply business rules when a business object instance enters a given state.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object Inheritance for more information.

Click here to see the algorithm types available for this system event.

Exit

Optional

Algorithms of this type apply business rules when a business object instance exits a given state.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object Inheritance for more information.

Click here to see the algorithm types available for this system event.

Monitor

Optional

Algorithms of this type monitor a business object instance while in a given state. Typically these are used to auto-transition it to another state.

The system invokes all algorithms of this type defined on the business object's inheritance hierarchy. Refer to Business Object Inheritance for more information.

Click here to see the algorithm types available for this system event.

Fastpath: Refer to BO Algorithm Execution Summary for more information about how these algorithms fit within other business object algorithms.

Note: Generate Algorithm. A context sensitive "Generate a BO Algorithm" zone is associated with this page. Refer to Defining Business Objects for more information about this zone.

Note: You can inactivate status level algorithms on base Business Objects. Your implementation may want to use a business object provided by the base product, but may want to inactivate one or more of the status oriented algorithms provided by the base business object. To do that, on the business object and status where this algorithm is referenced, go to the options grid and add a new option, setting the option type to Inactive Algorithm and setting the option value to the algorithm code.

Next Statuses

Use the Next Statuses grid to define the valid statuses a business entity can transition into while it's in this state. This section is hidden for a child business object. Refer to Valid States versus State Transition Rules for more information. Please note the following about this grid:

- Status shows the statuses for the top-level business object, the Status Code, the Lifecycle BO description, and the Status description for each status.

- Use Action Label to indicate the verbiage to display on the button used to transition to this status.

- Sequence controls the relative order of one status compared to others for display purposes. This information may be used to control the order in which buttons are presented on a user interface.

- Default controls which next state (if any) is the default one. This information may be used by an Enter or Monitor algorithm to determine an auto-transition to the default state. It may also be used to also mark the associated button as the default one on a user interface.

- Transition Condition may be configured to identify a common transition path from the current state. By associating a given "next status" with a transition condition value, you can design your auto-transition rules to utilize those flag values without specifying a status particular to a given business object. Thus, similar logic may be used across a range of business objects to transition a business entity into, for example, the next Ok state for its current state. You'll need to add your values to the customizable lookup field BO_TR_COND_FLG.

- Transition Role controls whether only the System or both System and User have the ability to transition a business entity into a given "next status".

- When you initially set up a business object lifecycle, none of the statuses will reside on the database and therefore you can't use the search to define a "next status". We recommend working as follows to facilitate the definition of this information:

- Leave the Next Statuses grid blank when you initially define a business object's statuses

- After all statuses have been saved on the database, update each status to define its Next Statuses (this way, you can use the search to select the status).

Options

The options grid allows you to configure the business object status to support extensible options. Select the Option Type drop-down to define its Value. Detailed Description may display additional information on the option type. Set the Sequence to 1 unless the option can have more than one value. Owner indicates if this option is owned by the base package or by your implementation (Customer Modification).

Note: You can add new options types. Your implementation may want to add additional option types. For example, your implementation may have plug-in driven logic that would benefit from a new option. To do that, add your new values to the customizable lookup field BO_OPT_FLG. If you add a new option type for a status, you must update the business object's maintenance object to declare this new option type. Otherwise, it won't appear on the option type dropdown. You do that by referencing the new option type as a Valid BO Status Option Type maintenance object option.

Business Object - Summary

This page summarizes business object information in a high level. Open this page using Admin > System > Business Object > Search and then navigate to the Summary tab.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays main attributes of the business object.

Click the View Schema hyperlink to view the business object's expanded schema definition. Doing this opens the schema viewer window.

Click the View XSD hyperlink to view the business object's expanded schema definition in XSD format.

The Business Object Hierarchy zone displays in a tree view format the hierarchy of child business object associated with the current business object. It also shows the current business object's immediate parent business object.

For business objects with a lifecycle, the Lifecycle Display zone shows a graphical depiction of the lifecycle. Refer to the embedded help of that zone for more information.

The Options zone summarizes business object and state specific options throughout the inheritance chain.

The Rules zone summarizes business object and state specific rules throughout the inheritance chain.

Advanced BO Tips and Techniques

The topics in this section describe some advanced tips and techniques for configuring business objects.

Next in This Section

- Managing To Do Entries

- Submitting a Batch Job

Managing To Do Entries

The product provides several base algorithm types that may be used to manage To Do entries through status changes for a given record via BO lifecycle plug-ins.

Create To Do Entry

The product supplies a BO status Enter algorithm type Generic To Do Creation (F1-TDCREATE) that creates a To Do entry based on parameter configuration. Refer to the algorithm type description for more information about how it determines the To Do type or To Do role and how to populate the appropriate message text onto the To Do. This algorithm may be used in conjunction with the Retry Logic (below).

If your implementation has a business rule that requires a To Do entry to be created when entering a given BO status and the logic provided by the algorithm type meets the needs of the business rule, this algorithm type may be used. Create an algorithm for the algorithm type, populate the algorithm parameters according to the business rules and plug the new algorithm into the appropriate business object status as an Enter algorithm.

Retry Logic

The algorithm type Retry for To Dos (F1-TODORETRY) is supplied for a special use case. It is a BO status monitor plug-in and may be used for a state that is a type of ‘error’ or ‘waiting’ state. It relies on the To Do entry creation logic to set a Retry Frequency. The algorithm transitions to the originating state to retry the logic. The idea is that the condition that caused the record to enter the ‘error’ or ‘waiting’ state may be resolved after some period of time has passed, allowing the record to progress in its lifecycle. Refer to the algorithm type description for more information about its logic.

To use this functionality, create an algorithm for this algorithm type, populate the algorithm parameters according to the business rules and plug the new algorithm into the appropriate business object status as a Monitor algorithm. The state should also have an algorithm for the Generic To Do Creation algorithm type plugged in as an Enter algorithm (or something equivalent) that sets the appropriate Retry Frequency.

To Do Completion

It is common that one or more To Do entries associate with a given record should be completed when exiting a state (if it is not already completed). The system supplies the algorithm type Generic To Do Completion (F1-TODOCOMPL) that may be used for this purpose. Note that the algorithm type functionality is not tied to any To Do creation logic. It may be used for any use case where To Do entries should be completed on exiting a state. Refer to the algorithm type description for more information about its functionality and how to prevent certain To Do entries from being automatically completed.

To use this functionality, create an algorithm for this algorithm type, populate the algorithm parameters according to the business rules and plug the new algorithm into the appropriate business object status as an Exit algorithm.

Submitting a Batch Job

The product provides a base algorithm type that submits a batch job when entering a BO state. This functionality allows for “event driven” batch submission where the event is the lifecycle transition for a certain record.

The algorithm type is Create Batch Job Submission Entry for Batch Control (F1-SCHEDJOB). The batch control code is a parameter for the algorithm. Refer to the algorithm type description for more information about its logic.

To use this functionality, create an algorithm for this algorithm type, populate the algorithm parameter with the batch control that should be submitted and plug the new algorithm into the appropriate business object status as an Enter algorithm.

Defining Status Reasons

Status Reasons are used to provide more information about why a business object transitioned to a given state. The status reason table provides a centralized place where status reasons can be defined across many different business objects and states.

Note: Refer to Defining Reasons for Entering a State for overview information.

If a business object has one or more states that are configured to capture a status reason, you may configure the valid reasons by navigating to the status reason portal using Admin > System > Status Reason.

The topics in this section describe the base-package zones that appear on the Status Reason portal.

Business Objects with Status Reason List

This zone displays the business objects that have one or more status values that allow status reasons to be defined.

Click the broadcast icon to open other zones that contain more information about the business object’s status reasons.

Status Reasons

The Status Reasons zone contains a list of the existing status reasons for the broadcasted business object.

Business Services

A business service is used to expose a back-end service so that it may be invoked by a script or a zone or a map to retrieve information or perform functions, depending on the related service.

As with the business object, the business service's interface to the internal service is defined using its schema. The schema maps the business service's elements to the corresponding elements in the internal service program's XML document. Just as a business object can simplify the schema of its maintenance object by only defining elements that it needs and “flattening” entries in a child collection to be defined as a singular element, a business service schema may simplify its service XML in a similar way.

Fastpath: Refer to Schema Syntax for a complete list of the XML nodes and attributes available to you when you construct a schema.

Inbound web services and scripts support interaction with business services. You can also invoke a business service from a Java class.

Next in This Section

- Service Program

- Defining Business Services

Service Program

This transaction defines services available in the system. These include user interface services as well as stand-alone services that perform a specific function. A service may be referenced by a business service. Use this transaction to view existing service and introduce a new stand-alone service to be made available to a Business Service.

Select Admin > System > Service Program to maintain service programs.

Description of Page

Service Name is the unique identifier of the service.

CAUTION:

Important! When adding new service programs, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Owner indicates if this service is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a service. This information is display-only.

Description describes the service.

Application Service is the application service that is used to provide security for the service. If the service is related to a maintenance object, the access modes for the application service should be the standard Add, Change, Delete and Inquire. For other services, the application service should have the Execute access mode.

Service Type indicates whether the service is a Java Based Service or a Java (Converted) Service.

This Program Component grid shows the list of program user interface components associated with the service. For a stand-alone service, this list is typically not applicable.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_MD_SVC.

Defining Business Services

The topics in this section describe how to maintain business services.

Note that several context sensitive dashboard zones appear on this page and are visible on all tabs.

- Schema Tips. This zone provides several links to launch help topics related to valid schema syntax.

- Generate Schema. This zone includes a button that can be used to generate the schema based on the XML of its related Service. Once generated, adjust the schema as desired.

Next in This Section

- Business Service - Main

- Business Service - Schema

- Useful Services and Business Services

Business Service - Main

Use this page to define basic information about a Business Service. Open this page using Admin > System > Business Service

Description of Page

Enter a unique Business Service name and Description. Use the Detailed Description to describe the purpose of this business service in detail. Owner indicates if the business service is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new business service, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Enter the internal Service Name being called when this business service is invoked.

Enter the Application Service that is used to provide security for the business service. The application service must have an Access Mode of Execute.

Click the View Schema to view the business service's expanded schema definition. Doing this opens the schema viewer window.

Click the View XSD hyperlink to view the business object's expanded schema definition in XSD format.

Click the View XML hyperlink to view the XML document used to pass data to and from the service in the Service XML Viewer. You may find it useful to leave the application viewer window open while defining your business service schema.

Note: XML document may not be viewable. If you create a new service program and do not regenerate the application viewer, you will not be able to view its XML document.

Where Used

Follow this link to open the data dictionary to view the tables that reference F1_BUS_SVC.

Business Service - Schema

Use this page to maintain a Business Service's schema and to see where the Business Service is used in the system. Open this page using Admin > System > Business Service and then navigate to the Schema tab.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays main attributes of the business service.

The Schema Designer zone allows you to edit the business service's schema. The purpose of the schema is to map the business service's elements to the corresponding fields of the back-end service program it rides on.

Note: Generating a Schema A context sensitive "Generate Schema" zone is associated with this page. The zone provides a button that allows the user to generate a basic schema that includes all the elements that are found in the XML of the BS’s service.

Fastpath: Refer to Schema Syntax for a complete list of the XML nodes and attributes available to you when you construct a schema. Also note that the Schema Tips zone in the dashboard provides a link to launch this help topic directly.

The Schema Usage Tree zone summarizes all cross-references to this schema. These may be other schemas, scripts, and web services. For each type of referencing entity, the tree displays a summary node showing a total count of referencing items. The summary node appears if at least one referencing item exists. Expand the node to list the referencing items and use their description to navigate to their corresponding pages.

Useful Services and Business Services

The following section highlights some business services and services provided by the product that may be useful for implementations to use.

Data Explorer Service

The system provides a mechanism for performing an SQL select statement for use in scripting, Java plug-ins, or via a web service call. This is done by creating a zone using one of the data explorer zone types where the SQL is defined. Then, create a business service using the Data Explorer service (FWLZDEXP).

Note: There are numerous business services delivered with the base product that reference this service that may be used as a template.

The following points highlight how to create your own business service for this service. Note that typically a separate business service exists for each zone.

- Enter a Business Service code and a Description. It is recommended to define the business service code to match the zone code so that it’s easier to manage which business service invokes which zone.

- Select the Service Name FWLZDEXP.

- On the Schema tab, under the <schema> node, enter mapping for the fields that are required for the Data Explorer service:

- The Zone should be mapped into service field ZONE_CD . Define the zone code as the default value.

- For every user filter defined on the zone, create a schema mapping into the service field Fx_VALUE , where "x" is the filter number (from the zone parameters).

- For every hidden filter defined on the zone, create a mapping into the service field Hx_VALUE , where "x" is the filter number (from the zone parameters).

- The search results are returned as a list by the data explorer service. Each column value is in the service field COL_VALUE with an appropriate sequence number ( SEQNO ). The results can be flattened based on sequence number allowing for a logical element name to be defined.

- Another useful field is ROW_CNT , which provides the number of rows retrieved by your search.

The following is an example of the schema for a BS that receives a business object code and returns a list of status values and their descriptions that allow status reasons to be defined.

<schema>

<zone mapField="ZONE_CD" default="F1-BOSTSLST"/>

<bo mapField="H1_VALUE" />>

<rowCount mapField="ROW_CNT"/>>

<results type="list" mapList="DE">>

<status dataType="string" mapField="COL_VALUE">

<row mapList="DE_VAL">>

<SEQNO is="1" />>

</row>>

</status>>

<description dataType="string" mapField="COL_VALUE">

<row mapList="DE_VAL">>

<SEQNO is="2" />>

</row>>

</description>>

</results>>

</schema>

Maintenance Object Log Service

Many maintenance objects support a log table that follows a pattern of column names and behavior. The system provides a service called Generic MO Log Service (F1MOLOGP) that may be used to perform common functions related to log entries:

- Read log entries. If you pass a certain MO, primary key and log sequence number, the service will return the details of that log entry. The product provides a generic business service that may be used for this purpose — Generic MO - Retrieve Log Details (F1–ReadMOLog). Alternatively, it is possible to create a business service for a given MO where the MO code is assigned to the MO element using the default syntax. This allows business functionality specific to that maintenance object to use the specific BS.

- Add log. The service may be used to add a log entry. If a user log is added, then the comments from the user are populated in the detailed description. System generated log entries typically supply a message category / message number along with other information such as the status, a specific log type and optionally a related object reference (via a characteristic). The product provides a generic business service that may be used for this purpose — Add Generic MO Log (F1–AddMOLog). Alternatively, it is possible to create a business service for a given MO where the MO code is assigned to the MO element using the default syntax. This allows business functionality specific to that maintenance object to use the specific BS.

Base Business Services

The following table highlights some business services provided by the product that may be useful for custom logic for an implementation.

CAUTION:

This is not intended to be a complete reference of Business Services. Refer to the business service page to find all the supported business services.

Business Object Related Services

Business Service Name

Description

F1-AutoTransitionBO

Performs monitoring algorithms associated with the current state of a given business object instance (which may result in subsequent state transitioning).

F1-CompareBusinessObjectData

Compares two versions of a given business object instance.

F1-DetermineBo

Determines the business object of a given instance of a maintenance object by executing the MO's Determine BO logic.

F1-GetRequiredFieldsForBOState

Returns the required fields for a given business object status.

F1-RetrieveBOOption

Returns BO option values for a given BO and option type.

F1-RetrieveBOStatusOption

Returns BO option values for a given BO, status and option type.

F1-RetrieveBOStatusOption

Retrieves a list of BOs for a given MO that are accessible for the current user.

F1-RetrieveBoStatusDescription

Return the description of a given BO status.

F1-RetrieveBusinessObjectLabel

Return the label appropriate for a given path (e.g. element) within a BO schema.

F1-RetrieveNextStates

Return a list of next possible states based on the input of a MO and its prime key, or a BO and one of its statuses.

Email Related Services

Business Service Name

Description

F1-EmailService

Sends an email message in real time.

F1-RetrieveEmailAddress

Retrieves the email addresses of users belonging to a To Do Role.

F1-RetrieveEnvironmentURL

Retrieves the current environment URL information for the installation.

Tools for Maps and Scripting

Business Service Name

Description

F1–DateMath

Performs various date and time math calculations. Refer to the BS description for more details.

F1-DateTimeFormattingService

Formats a given date / time based on the user’s display profile settings.

F1-ExecuteScriptInNewSession

Executes a Service Script in a new processing session/transaction.

F1-GetFieldLabel

Retrieves the label for a given field.

F1-GetForeignKeyReference

Returns foreign key reference information for a given FK Reference and primary key, including info description, navigation option, and context menu.

F1-GetFKReferenceDetails

Returns foreign key reference information for a given MO and primary key, including FK reference code, info description, navigation option, search zone and context menu.

F1-GetLookupDescription

Returns lookup description for a lookup field value given the lookup field name.

F1-GetExtLookUpVal

Returns the list of values for a given extendable lookup BO.

F1-GetMonthInYearAbbreviation

Returns a 3-character month abbreviation for an input date in system format.

F1-NumberAmountFormatter

Formats a given amount or number based on the user’s display profile settings. It also may receive input to adjust the scale and optionally apply currency settings.

F1-OutmsgDispatcher

Dispatches a real-time message giving the user the option of whether to persist the message on the database, and whether to trap errors that may take place during the call. Refer to Real Time Messages for more information.

F1-OutmsgMediator

Alternative to F1-OutmsgDispatcher and may be a better option if the sender does not require an outbound message record to be instantiated. Refer to Real Time Messages for more information.

F1-RethrowError

Issues an application error using the input message category / number / parameters.

F1-RetrieveMODescription

Retrieves the description for a maintenance object.

F1-ReturnMessage

Returns the expanded message given a message category, number, parameters, and parameter types.

F1-SavePointDispatcher

Allows for a service script to be executed where exceptions are trapped and the transaction is rolled back to a save point set before the service script execution.

User Related Services

Business Service Name

Comments

F1-CheckApplicationSecurity

Checks a user’s security for a given application service / access mode

F1-CheckUserAuthorization

Determine whether a given user is authorized for access based on the input application service, security code, and authorization level.

F1-DetermineIfUserCanApproveTD

Determine if the current user can approve a given To Do.

User Interface (UI) Maps

The User Interface (UI) map holds HTML to be rendered within portal zones and Business Process Assistant (BPA) scripts. UI maps allow your implementation to create input forms and output maps that closely match your customer's business practices. In other words, the UI Map is designed to facilitate the capture and display of your business objects and business services.

The UI map is a repository for a single HTML document paired with an XML schema where the schema defines the data that the HTML document displays and/or modifies. The UI Map HTML gives you the ability to craft the display by any method that an html document can support, including JavaScript and full CSS functionality.

Configuration tool support for UI Maps hinges around the ability to inject and extract an XML document from the HTML. For more information on the specialized support for HTML and JavaScript functionality refer to UI Map Attributes and Functions.

Figure 1. HTML to Display Customer Business Object

Figure 2. Customer HTML Rendered (Output Data for Zone)

UI maps are typically crafted as output tables when used in conjunction with portal zones - please refer to Map Zones for more information. When referenced within BPA scripts, UI maps are typically crafted as forms for the capture and update of data.

Figure 3. HTML Input Form Rendered (for BPA Script)

Portal zones can reference a UI map for the zone header. They may also utilize a UI map to define their filter area. This type of UI map is not a complete HTML document, but is instead configured as a UI Map "fragment".

Note: UI Map Tips. A context sensitive "UI Map Tips" zone is visible on the UI map maintenance page. This zone provides several links to launch help topics related to valid schema syntax and UI Hint syntax in one click.

Note: Editing HTML. You can use a variety of HTML editors to compose your HTML, which you can then cut, and paste into your UI map. In addition, the zone provides a complete list of the XML schema nodes and attributes available to you when you construct the map's data schema.

Next in This Section

- Defining UI Maps

- Ensuring Unique Element IDs for UI Maps

Defining UI Maps

The topics in this section describe how to maintain UI Maps.

Next in This Section

- UI Map - Main

- UI Map - Schema

- UI Map Attributes and Functions

- UI Map Standards

UI Map - Main

Use this page to define basic information about a user interface (UI) Map. Open this page using Admin > System > UI Map

Description of Page

Enter a unique Map name. Owner indicates if the UI map is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new UI map, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Use UI Map Type to indicate whether the map is a Complete XHTML Document, Complete HTML Document, XHTML Fragment or an HTML Fragment. The default value is Complete XHTML Document.

Enter a Description. Use the Detailed Description to describe how this map is used in detail.

Click on the View Schema to view the UI map's expanded schema definition. Doing this opens the schema viewer window.

Use the Test UI Map hyperlink to render your HTML in a test window.

Note: The Test UI Map hyperlink also exercises the proprietary functionality that binds an XML element with an HTML element so you can get immediate feedback on your HTML syntax.

Where Used

Follow this link to open the data dictionary to view the tables that reference F1_MAP.

UI Map - Schema

Use this page to maintain a UI Map's HTML and schema and to see where the UI Map is used in the system. Open this page using Admin > System > UI Map and then navigate to the Schema tab.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays main attributes of the UI Map.

The HTML Editor zone allows you to edit the HTML document of the map.

Note: Refer to UI Map Attributes and Functions and UI Map Standards for more information about HTML definition syntax. These topics describe good ways to produce simple HTML, however, they are not an HTML reference. Note that you can use a variety of HTML editors to compose your HTML, which you can then cut and paste into your UI map.

Note: Providing Help. A tool tip can be used to display additional help information to the user. This applies to section elements as well as individual elements on a map. Refer to UI Map Attributes and Functions for more information on how to enable and provide UI map help.

The Schema Designer zone allows you to edit the data schema part of the map. The purpose of the schema is to describe the data elements being displayed by the map.

Fastpath: Refer to Schema Syntax for a complete list of the XML nodes and attributes available to you when you construct a schema. Also note that the UI Map Tips zone in the dashboard provides a link to launch this help topic directly.

The Schema Usage Tree zone summarizes all cross-references to this schema. These may be other schemas, scripts, and web services. For each type of referencing entity, the tree displays a summary node showing a total count of referencing items. The summary node appears if at least one referencing item exists. Expand the node to list the referencing items and use their description to navigate to their corresponding pages.

UI Map Attributes and Functions

Note: This topic uses the term "field" to refer to both the generic concept of displaying and capturing data in a 'field' as well as referring to the meta-data object supplied in the product to define Fields. When referring to the latter, the term "MD Field" (meta-data Field) is used and a hyperlink to the Field documentation is provided.

Contents

Bind XML to HTML

Build a Dropdown List

Format Input and Output Fields

Display Labels

Enable UI Map Help

Search Using a Pop-Up Explorer Zone

Display Errors

Fire JavaScript for Browser Events

Hide Elements

Invoke Schema Based Services

Refresh a Rendered Map or Portal Page

Embed Framework Navigation

Launch BPA Script

Exit UI Map with Bound Values

Include a Map Fragment

Show Schema Default on Add

Configure a Chart

Upload and Download a CSV File

Construct Portal Zone Map Fragments

Required JavaScript Libraries

Bind XML to HTML

Only two different attributes are required to bind a UI Map's XML to its HTML. Both of these attributes require an XML document embedded within the HTML, where the XML is bounded by <xml> nodes.

Warning: You must embed a pair of <xml></xml> tags within your HTML document for binding to occur.

Linking a Field

Syntax

Values

Description

oraField=" "

Field element XPath

This attribute is used to link an HTML element directly with an XML element, where the XML element is defined within the UI Map's XML schema. The attribute can be used with any rendering HTML element, such as: <span>, <div>, and <input>.

- HTML for input element:

<html>

<body>

<table>

<tr>

<td>Address:</td>

<td><input type="text" oraField="address"/></td>

</tr>

<tr>

<td>City:</td>

<td><input type="text" oraField="city"/></td>

</tr>

<tr>

<td>State:</td>

<td><input type="text" oraField="state"/></td>

</tr>

<tr>

<td>Zip:</td>

<td><input type="text" oraField="zip"/></td>

</tr>

</table>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

</root>

</xml>

</html>

Rendered HTML

- HTML for span and div elements:

<html>

<body>

<div oraField="address"></div>

<span oraField="city"></span>

<span>,</span>

<span oraField="state"></span>

<span oraField="zip"></span>

<span oraField="country"></span>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

</root>

</xml>

</html>

HTML rendered:

Linking a List

This attribute is used to link an HTML table with an XML list, where the XML list is defined within the UI Map's XML schema. The purpose of the element is to trigger the framework to replicate the table's HTML for each occurrence of the list.

Syntax

Values

Description

oraList=" "

List element XPath

This attribute is used to link an HTML table with an XML list, where the XML list is defined within the UI Map's XML schema. The purpose of the element is to trigger the framework to replicate the table's HTML for each occurrence of the list.

Note: The oraField attributes embedded within the list must contain XPath navigation relative to the list. See below for an example.

<html>

<head><title>Bind xml list element</title></head>

<body>

<table oraList="payment">

<thead>

<tr>

<th><span>Pay Date</span></th>

<th><span>Amount</span></th>

</tr>

<tr/>

</thead>

<tr>

<td>

<span oraField="date" oraType="date"></span>

</td>

<td align="right">

<span oraField="amount" oraType="money"></span>

</td>

</tr>

</table>

</body>

<xml>

<root>

<payment>

<date>2008-01-01</date>

<amount>44.28</amount>

</payment>

<payment>

<date>2008-02-01</date>

<amount>32.87</amount>

</payment>

<payment>

<date>2008-03-01</date>

<amount>21.76</amount>

</payment>

</root>

</xml>

</html>

HTML rendered:

Build a Dropdown List

The following attributes are provided to build an HTML ‘select’ element, also called a dropdown, based on various sources.

Source

Syntax

Values

Examples

Lookup

oraSelect="lookup: ;"

Lookup field

...

<td>House Type:</td>

<td>

<select oraField="houseType"

oraSelect="lookup:HOUSE_TYPE;">

</select>

</td>

Extendable Lookup

oraSelect="lookupBO: ;"

BO code

...

<td>UI Device Display Type:</td>

<td>

<select oraField="uiDeviceType"

oraSelect="lookupBO:

F1-DeviceDisplayTypes;"></select>

</td>

Characteristic Type (pre-defined)

oraSelect="charType: ;"

Characteristic Type code

...

<td>Usage:</td>

<td>

<select oraField="statusReasonUsage"

oraSelect="charType:F1-SRUSG;"></select>

</td>

...

Control Table

oraSelect="table: ;"

Note: This attribute only works with tables that follow the standard control table structure where there is a related language table that includes that includes the column DESCR as its description column. Use the Application Viewer data dictionary to identify tables that qualify for this functionality.

Warning: The oraSelect function will only work if less than 500 values are displayed.

Table name

...

<td>Currency: </td>

<td>

<select oraField="currency"

oraSelect="table:CI_CURRENCY_CD;">

</select>

</td>

...

Page Service

oraSelect="service: ;"

Page Service name

...

<td>Country:</td>

<td>

<select oraField="country"

oraSelect="service:CIPTCNTW;">

</select>

</td>

...

Embedded List

Used to build a select dropdown based on a list within the map’s XML.
oraSelect="valuePath: ;descPath: "

After the valuePath, indicate the XPath of the element that holds the values. After the descPath, indicate the XPath of the element that holds the descriptions.

<html>

<body>

<table summary="" border="0"

cellpadding="1" cellspacing="1">

<tr>

<td>Select: </td>

<td><select oraSelect=

"valuePath:list/value;

descPath:list/desc"

oraField="target"></select></td>

</tr>

</table>

</body>

<xml>

<root>

<target>10</target>

<list>

<value>10</value>

<desc>Ten</desc>

</list>

<list>

<value>20</value>

<desc>Twenty</desc>

</list>

<list>

<value>40</value>

<desc>Forty</desc>

</list>

</root>

</xml>

</html>

Service Script

oraSelect="ss: ;"

Service Script code

See below for additional syntax needed when using this function.

Business Service

oraSelect="bs: ;"

Business Service code

See below for additional syntax needed when using this function.

When specifying a service script or a business service, extra mapping information is needed to pass data to and from the service.

Syntax

Values

Description

oraSelectIn=" ;"

serviceXPath:element;

Used to pass the value of another element into the service (mapping to the service's XPath).

serviceXPath:'Literal';

Used to pass a constant or literal to the service (mapping to the service's XPath).

oraSelectOut="valuePath: ; descPath: "

See examples below

Used to indicate which element in the service's output holds the values and which one holds the descriptions.

Example using a business service:

...

<td>External System: </td>

<td>

<select oraField="externalSystem" oraSelect="bs:F1-RetrieveExternalSystems"

oraSelectIn="outboundMsgType:boGroup/parameters/outboundMsgType;" oraSelectOut="valuePath:results/externalSystem;

descPath:results/description"></select>

</td>

...

This method for building dropdowns is often used when there is a dependency between elements and the list of valid values in a dropdown (for the child element) is based on another element in the map (the parent element). When the parent element is changed, it may be required to refresh the child element. This behavior can be implemented using the function called within an onChange event in the map. The syntax is oraHandleDependentElements('dependent element');. Multiple target elements (dependents) can be named.

The following example is related to the above business service example where the list of external systems is specific for a given outbound message type, which is passed in as input. The snippet below shows the configuration for the outbound message type element to trigger a refresh of the external system’s dropdown list.

...

<div>

<label oraLabel="boGroup/parameters/outboundMsgType"></label>

<span>

<select oraSelect="table:F1_OUTMSG_TYPE"  oraField="boGroup/parameters/outboundMsgType"

onChange="oraHandleDependentElements('boGroup/parameters/externalSystem');"></select>

</span>

</div>

...

Format Input and Output Fields

The following attributes are designed to apply data type formatting for input and output fields.

Automatic Formatting

Syntax

oraSchemaDataTypes="false"

This attribute is used to trigger automatic formatting in the rendered HTML document. The automated formatting will occur according to the data type attributes defined in the UI map's schema. For details on specific data type formatting, please refer to the oraType attribute descriptions below.

Warning: The attribute oraSchemaDataTypes="true" will be automatically injected into the UI map's HTML! If you do not wish to apply the schema's data types to the rendered HTML then you must specify this attribute in the body node with a value of false. The attribute <body oraSchemaDataTypes="false"> is required to avoid automatic formatting!

- UI Map schema:

<schema>

<schemaDate dataType="date"/>

<schemaDateTime dataType="dateTime"/>

<schemaFKRef fkRef="CI_USER"/>

<schemaLookup dataType="lookup" lookup="ACCESS_MODE"/>

<schemaMoney dataType="money"/>

<schemaNumber dataType="number"/>

<schemaTime dataType="time"/>

</schema>

- UI Map HTML:

<html>

<body oraSchemaDataTypes="true">

<table border="1" cellpadding="1" cellspacing="1">

<tr><th>dataType</th><th>result type</th><th>input result</th><th> display-only result</th></tr>

<tr>

<td rowspan="2">date (from schema)</td>

<td>raw</td>

<td><input oraField="schemaDate" oraType="string" /></td>

<td><span oraField="schemaDate" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaDate"></td>

<td><span oraField="schemaDate"></span></td>

</tr>

<tr>

<td rowspan="2">dateTime (from schema)</td>

<td>raw</td>

<td><input oraField="schemaDateTime" oraType="string"></td>

<td><span oraField="schemaDateTime" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaDateTime"></td>

<td><span oraField="schemaDateTime"></span></td>

</tr>

<tr>

<td rowspan="2">fkRef (from schema)**</td>

<td>raw</td>

<td><input oraField="schemaFkRef" oraType="string"></td>

<td><span oraField="schemaFkRef" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaFkRef"></td>

<td><span oraField="schemaFkRef"></span></td>

</tr>

<tr>

<td rowspan="2">lookup (from schema)</td>

<td>raw</td>

<td><input oraField="schemaLookup" oraType="string"></td>

<td><span oraField="schemaLookup" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaLookup"></td>

<td><span oraField="schemaLookup"></span></td>

</tr>

<tr>

<td rowspan="2">money (from schema)</td>

<td>raw</td>

<td><input oraField="schemaMoney" oraType="string"></td>

<td><span oraField="schemaMoney" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaMoney"></td>

<td><span oraField="schemaMoney"></span></td>

</tr>

<tr>

<td rowspan="2">number (from schema)</td>

<td>raw</td>

<td><input oraField="schemaNumber" oraType="string"/></td>

<td><span oraField="schemaNumber" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaNumber"></td>

<td><span oraField="schemaNumber"></span></td>

</tr>

<tr>

<td rowspan="2">time (from schema)</td>

<td>raw</td>

<td><input oraField="schemaTime" oraType="string"></span></td>

<td><span oraField="schemaTime" oraType="string"></span></td>

</tr>

<tr>

<td>rendered</td>

<td><input oraField="schemaTime"></td>

<td><span oraField="schemaTime"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<schemaDate>2007-11-02</schemaDate>

<schemaDateTime>2007-11-02-23.45.00</schemaDateTime>

<schemaFkRef>USD</schemaFkRef>

<schemaLookup>A</schemaLookup>

<schemaMoney>1000000</schemaMoney>

<schemaNumber>5661976.11548</schemaNumber>

<schemaTime>23.45.00</schemaTime>

</root>

</xml>

</html>

HTML rendered.

Date Formatting

This function is used to display a date according to the user's display profile. For input fields, the setting formats the data when the user tabs out of the field.

Syntax

oraType="date"

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Date: </td>

<td><span oraField="date" oraType="date"></span></td>

</tr>

<tr>

<td>Date: </td>

<td><input oraField="date" oraType="date"/></td>

</tr>

</table>

</body>

<xml>

<root>

<date>2008-12-28</date>

</root>

</xml>

</html>

HTML rendered.

Time Formatting

This function is used to display a time according to the user's display profile. For input fields, the setting formats the data when the user tabs out of the field.

Syntax

oraType="time"

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Time: </td>

<td><span oraField="time" oraType="time"></span></td>

</tr>

<tr>

<td>Time: </td>

<td><input oraField="time" oraType="time"/></td>

</tr>

</table>

</body>

<xml>

<root>

<time>00.28.54.389</time>

</root>

</xml>

</html>

HTML rendered.

Date and Time Formatting

This function is used to display a timestamp according to the user's display profile. If this function is used for an input element, it is broken into two pieces, one for date and one for time. Optionally, the time portion of the date time element can be suppressed using the attribute value 'time:suppress'.

Syntax

oraType="dateTime; time:suppress"

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Date time: </td>

<td><span oraField="dateTime" oraType="dateTime"></span></td>

</tr>

<tr>

<td>Date only: </td>

<td><span oraField="dateTime" oraType="dateTime; time:suppress"></span></td>

</tr>

<tr>

<td>Date time: </td>

<td><input oraField="dateTime" oraType="dateTime"/></td>

</tr>

<tr>

<td>Date only: </td>

<td><input oraField="dateTime" oraType="dateTime; time:suppress"/></td>

</tr>

</table>

</body>

<xml>

<root>

<dateTime>2009-11-01-00.28.54</dateTime>

</root>

</xml>

</html>

HTML rendered.

Date / Time Formatting with Standard Time

This true function is used to render a date / time element according to the daylight savings time schedule of the 'base' time zone. The 'base' time zone is specified on the Installation table and represents the database time zone. For input elements with this setting, all time entered is assumed to correspond with the daylight savings time schedule of the base time zone. If a time is entered that cannot be unambiguously translated to standard time, then the user will be required to provide a time zone label to indicate whether daylight savings time, or standard time, has been entered.

Syntax

oraType="dateTime; stdTime:true;"

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Date time: </td>

<td><span oraField="dateTime" oraType="dateTime; stdTime:true;"></span></td>

</tr>

<tr>

<td>Date time: </td>

<td><input oraField="dateTime" oraType="dateTime; stdTime:true;"/></td>

</tr>

</table>

</body>

<xml>

<root>

<dateTime>2009-11-01-00.28.54</dateTime>

</root>

</xml>

</html>

HTML rendered.

Note: The time zone label is displayed because 1:28 is ambiguous otherwise. Legally, November 1, 2009 1:28 AM occurs twice because daylight savings time (DST) is removed at 2:00 AM. With the stdTime function time zone labels are only displayed when required to clarify time overlaps.

HTML rendered for the following day.

Date and Time Formatting with Time Zone Reference

Syntax

Valid Values

Description

oraType="dateTime; stdTimeRef: ;"

Reference an XPath after the colon.

This function is used to render a date / time element according to the daylight savings time schedule of a time zone whose XPath is referenced. Note that the time processed is assumed to have been stored in the standard time of the referenced time zone - so only daylight savings time shifting will execute - not time zone shifting.

oraType="dateTime; displayRef: ;"

Reference an XPath after the colon.

This function is similar to the stdTimeRef function, except that this function will execute time zone shifting in addition to daylight savings time shifting. To use displayRef correctly, only associate it with time zone elements that have been stored in the base time zone.

For input elements, all time entered is assumed to correspond with the daylight savings time schedule of the referenced time zone. If a time is entered that cannot be unambiguously translated to standard time, then the user will be required to provide a time zone label to indicate whether daylight savings time, or standard time, has been entered.

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Date time: </td>

<td><span oraField="dateTime" oraType="dateTime; stdTimeRef:timeZone;"></span></td>

</tr>

<tr>

<td>Date time: </td>

<td><input oraField="dateTime" oraType="dateTime; stdTimeRef:timeZone;"/></td>

</tr>

</table>

</body>

<xml>

<root>

<timeZone>US-EAST</timeZone>

<dateTime>2009-11-01-00.28.54</dateTime>

</root>

</xml>

</html>

HTML rendered.

Note: The time zone label is always displayed for a referenced time zone.

HTML rendered for the following day.

Duration Formatting

Syntax

oraType="duration"

This function is used to display time duration. For an input element, the value entered by the user is translated from minutes to hour and minutes as appropriate. For example, an entered value of '90', is converted to '00:01:30' when tabbing out of the input field.

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Duration: </td>

<td><span oraField="duration" oraType="duration"></span></td>

</tr>

<tr>

<td>Duration: </td>

<td><input oraField="duration" oraType="duration"/></td>

</tr>

</table>

</body>

<xml>

<root>

<duration>90</duration>

</root>

</xml>

</html>

HTML rendered.

Day in Month Formatting

Syntax

oraType="dayInMonth"

This function is used to display a concatenated day and month.

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Day In Month: </td>

<td><span oraField="dayMonth" oraType="dayInMonth"></span></td>

</tr>

<tr>

<td>Day In Month: </td>

<td><input oraField="dayMonth" oraType="dayInMonth"/></td>

</tr>

</table>

</body>

<xml>

<root>

<dayMonth>0228</dayMonth>

</root>

</xml>

</html>

HTML rendered.

Month In Year Formatting

Syntax

oraType="monthInYear"

This function is used to display a concatenated month and year.

<html>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Month In Year: </td>

<td><span oraField="month" oraType="monthInYear"></span></td>

</tr>

<tr>

<td>Month In Year: </td>

<td><input oraField="month" oraType="monthInYear"/></td>

</tr>

</table>

</body>

<xml>

<root>

<month>200811</month>

</root>

</xml>

</html>

HTML rendered.

Monetary Formatting

This function is used to display a number as a monetary amount. See the table for configuration options with respect to the currency. For input elements, an error is issued if a non-numeric value is entered.

Syntax

Description

oraType="money: "

Directly specify a currency code after the colon.

oraType="money;currencyRef: "

Reference an XPath (after the colon) for an element that references a currency code.

oraType="money"

If no currency or currency reference is specified, the installation currency is used.

Note: You must specify a pair of stylesheet references, cisEnabled and cisDisabled, in the map's header for right alignment. The stylesheet controls how the field will be rendered. If you want to alter the rendering you must override the oraMoney style.

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Amount, currency specified:</td>

<td><span oraType="money:EUR" oraField="totalAmt"></span></td>

</tr>

<tr>

<td>Amount, default currency:</td>

<td><span oraType="money" oraField="totalAmt"></span></td>

</tr>

<tr>

<td>Amount, default input:</td>

<td><input oraType="money" oraField="totalAmt"/></td>

</tr>

<tr>

<td>Amount, currency reference:</td>

<td><input oraType="money;currencyRef:cur" oraField="totalAmt"/></td>

</tr>

</table>

</body>

<xml>

<root>

<totalAmt>50500.09</totalAmt>

<cur>EUR</cur>

</root>

</xml>

</html>

HTML rendered

Number Formatting

This function is used to display a number or validate an input value. For input elements, the system will return an error if a non-numeric value is entered.

Syntax

oraType="number"

Note: You must specify a pair of stylesheet references, cisEnabled and cisDisabled, in the map's header for right alignment. The stylesheet controls how the field will be rendered. If you want to alter the rendering you must override the oraNumber style.

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Count:</td>

<td><span oraType="number" oraField="count"></span></td>

</tr>

<tr>

<td>Count, input:</td>

<td><input oraType="number" oraField="count"/></td>

</tr>

</table>

</body>

<xml>

<root>

<count>989</count>

</root>

</xml>

</html>

HTML rendered.

FK Reference Formatting

By default, when an element with an fkRef oraType is displayed, an info string, context menu, navigation, and search are enabled (if the FK reference has been configured accordingly). Syntax is provided to allow you to selectively turn off any of these features.

Note that you can enable the foreign key hyperlink separately as well, refer to Embed Framework Navigation for more information. The various attributes used to control foreign key reference functionality are as follows. Note that in every case, the default value is true. A value of false should be used to disable the feature.

Syntax

oraType="fkRef:true|false; info:true|false; context:true|false; navigation:true|false; search:true|false"

- fkRef. A value of 'true' enables all of the following foreign key reference processing. Use a value of 'false' to disable automatic FK Reference processing.

- info. A value of 'true' renders an information string on the UI map, if applicable.

- context. A value of 'true' renders a context menu to appear before the foreign key reference element, if applicable.

- navigation. A value of 'true' causes the information string to be rendered as a hyperlink, if applicable. Clicking the hyperlink navigates to the appropriate page.

- search. A value of 'true' displays a search icon that launches the search zone if applicable.

Note: Foreign key navigation and context menu functionality is only available for UI maps presented in a portal zone. UI Maps presented during BPA script processing cannot support navigation options. Search functionality is only available for input HTML elements.

- UI Map schema:

<schema>

<userId fkRef="CI_USER"/>

</schema>

- UI Map HTML:

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>User</td>

<td><span oraField="userId" oraType="fkRef:true; info:true; context:true; navigation:true;"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<userId>CZAAND</userId>

</root>

</xml>

</html>

- HTML rendered.

Lookup Formatting

This function is used to display the description of a lookup value.

Syntax

Valid Values

oraType="lookup: "

Lookup field name after the colon.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Status:</td>

<td><span oraField="status" oraType="lookup:BATCH_JOB_STAT_FLG"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<status>PD</status>

</root>

</xml>

</html>

HTML rendered.

Extendable Lookup Formatting

This function is used to display the description of an extendable lookup value.

Syntax

Valid Values

oraType="lookupBO: "

Business Object code name after the colon.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Status:</td>

<td><span oraField="status" oraType="lookupBO:F1-DeviceDisplayTypes"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<status>PD</status>

</root>

</xml>

</html>

HTML rendered.

Characteristic Type Formatting

This function is used to display the description of a predefined characteristic value.

Syntax

Valid Values

oraType="charType: "

Characteristic Type code after the colon.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Skill:</td>

<td><span oraType="charType:CM-SKILL" oraField="skill"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<skill>10</skill>

</root>

</xml>

</html>

HTML rendered.

Control Table Formatting

This function is used to display the description of a control table that has an associated language table.

Syntax

Valid Values

oraType="table: "

Table code after the colon.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Currency:</td>

<td><span oraType="table:CI_CURRENCY_CD" oraField="curr"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<curr>USD</curr>

</root>

</xml>

</html>

HTML rendered.

Add / Remove Grid Formatting

Syntax

Description

oraType="addGridRow"

The addGridRow function is used to build “insert row" dialog into the UI map.

- An 'add' image is displayed.

- Clicking the image inserts a new row in the grid.

- If the list is empty, by default, an empty grid row is automatically be added. This means that the user will always see at least one grid row when this attribute is used.

oraType="deleteGridRow"

The deleteGridRow function is used to build “delete row" dialog into the UI map.

- A 'delete' image is displayed.

- Clicking the image removes the adjacent row from the grid.

Note: Because add and delete dialogs are relevant only inside a table, these attributes must be specified within a <td> element.

Warning: These attributes are designed to work with the business object action of 'replace' rather than 'update'. Therefore, if the map contains a grid, the business object action of 'replace' must be used to update the business object. Refer to BO Replace Action for more information.

Example:

<html>

<head>

<title>Demonstrate Grid Add and Grid Delete OraTypes</title>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table oraList="listEntry">

<thead>

<tr>

<th/>

<th/>

<th><span>Date</span></th>

<th><span>Amount</span></th>

</tr>

<tr/>

</thead>

<tr>

<td oraType="addGridRow"></td>

<td oraType="deleteGridRow"></td>

<td>

<input oraField="date" oraType="date"></input>

</td>

<td align="right">

<input oraField="amount" oraType="money"></input>

</td>

</tr>

</table>

</body>

<xml>

<root>

<listEntry>

<date>2008-01-01</date>

<amount>44.28</amount>

</listEntry>

<listEntry>

<date>2008-02-01</date>

<amount>32.87</amount>

</listEntry>

<listEntry>

<date>2008-03-01</date>

<amount>21.76</amount>

</listEntry>

</root>

</xml>

</html>

HTML rendered.

Unformatted Elements

This function is used to display the contents of an element that contains 'raw' data as defined for the schema element being rendered.

Syntax

oraType="raw"

- UI Map schema:

<schema>

<rawStuff type="raw"/>

</schema>

- UI Map HTML:

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Raw Stuff:</td>

<td><span oraType="raw" oraField="rawStuff"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<rawStuff>

<ele1>text in element 1</ele1>

<group1>

<ele2>text inside element 2, group 1</ele2>

<ele3>text inside element 3, group 1</ele3>

</group1>

</rawStuff>

</root>

</xml>

</html>

HTML rendered.

String Formatting

This function is used to display the contents of an element, as XML pretty-print, when the element contains escaped XML.

Syntax

oraType="xmlString"

Note: It is not required, but the pretty print of the rendered XML is enhanced if you specify a pair of stylesheet references, cisEnabled and cisDisabled, in the map's header.

Example:

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>XML Stuff:</td>

<td><span oraType="xmlString" oraField="xmlStuff"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<xmlStuff>

<ele1>text in element 1</ele1>

<group1>

<ele2>text inside element 2, group 1</ele2>

<ele3>text inside element 3, group 1</ele3>

</group1>

</xmlStuff>

</root>

</xml>

</html>

HTML rendered.

HTML rendered without oraType=”xmlString”

HTML Formatting

This function is used to display the contents of an element as HTML as opposed to plain text. An element defined as oraType="fkref" is automatically rendered as HTML.

Syntax

oraType="html"

Warning:

To avoid execution of malicious HTML not all HTML tags are supported. The list of supported tags is defined in the "F1-HTMLWhiteList" managed content definition.

If unsupported HTML is detected the entire element is escaped and rendered as plain text. It is therefore recommended to properly escape any source string that contributes to the final HTML element if it is not expected to contain valid HTML. This way only the offending string is escaped and not the entire element.

If the HTML element is composed in scripting refer to the 'escape' function described in the Edit Data Syntax for more information. Use the WebStringUtilities.asHTML java API for escaping text composed in Java.

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table summary="" border="0" cellpadding="1" cellspacing="1">

<tr>

<td>Info :</td>

<td><span oraType="html" oraField="info"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<info><b>text in bold</b></info>

</root>

</xml>

</html>

HTML rendered.

HTML rendered without oraType="html"

Display Labels

Derive Label from an Element

This attribute is used to obtain a language sensitive label for a <span>, <td>, or <input> HTML element.

Syntax

Valid Values

oraLabel=" "

XPath of an element in the UI map schema. The element must reference either the mapField=, mdField=, or label= attribute.

Note: You can also define a field directly in your HTML for label definition, refer to Deriving Label from a Field for more information.

Note: If the schema contains multiple attributes, the oraLabel attribute will pick the label to render according to the following hierarchy: The label attribute overrides the mdField attribute, which in turn will override the mapField attribute.

- UI Map schema:

<schema>

<user mapField="USER_ID"/>

<info type="group" mapXML="CLOB">

<city label="Metro Area"/>

<age mdField="AGE_LBL"/>

</info>

</schema>

- HTML:

<html>

<head><title oraMdLabel="BUS_LBL"></title></head>

<body>

<table>

<tr>

<td oraLabel="user"></td>

<td><input oraField="user"/></td>

</tr>

<tr>

<td oraLabel="info/city"></td>

<td><input oraField="info/city"/></td>

</tr>

<tr>

<td oraLabel="info/age"></td>

<td><input oraField="info/age"/></td>

</tr>

<tr>

<td/>

<td><input type="button" oraMdLabel="ACCEPT_LBL"/></td>

</tr>

</table>

</body>

<xml>

<root>

<user>RWINSTON</user>

<info>

<city>Alameda</city>

<age>32</age>

</info>

</root>

</xml>

</html>

HTML rendered:

Deriving Label from a Field

This attribute is used to obtain a language sensitive label for a <span>, <td>, <input>, or <title> HTML element. The label text is derived from the field referenced.

Syntax

Valid Values

oraMdLabel=" "

MD Field code.

Note: You can also define labels derived from the map's schema definition, refer to Derive Label from an Element for more information.

- HTML:

<html>

<head><title oraMdLabel="NOTES_LBL"></title></head>

<body>

<table>

<tr>

<td oraLabel="user"></td>

<td><input oraField="user"/></td>

</tr>

<tr>

<td oraLabel="info/city"></td>

<td><input oraField="info/city"/></td>

</tr>

<tr>

<td oraLabel="info/age"></td>

<td><input oraField="info/age"/></td>

</tr>

<tr>

<td/>

<td><input type="button" oraMdLabel="ACCEPT_LBL"/></td>

</tr>

</table>

</body>

<xml>

<root>

<user>RWINSTON</user>

<info>

<city>Alameda</city>

<age>32</age>

</info>

</root>

</xml>

</html>

HTML rendered:

Enable UI Map Help

The Display Labels section describes ways to derive the label for an element using an underlying MD Field. In addition, if the same MD field contains help text, the system will automatically generate a tool tip adjacent to the element label. Clicking the tool tip allows the user to view the help text.

It is possible to change the rendering of the tool tip. Refer to Custom Look And Feel Options for more information

Search Using a Pop-Up Explorer Zone

Search Option

This attribute is used to enable search zone functionality for input HTML elements.

Syntax

Valid Values

oraSearch=" "

Zone code.

Note: The oraSearch attribute is similar to the oraType attribute, because it will be 'automatically' included into HTML via the oraSchemaDataTypes attribute. This means that coding the oraSearch attribute into UI Map HTML is only required if a search zone has not been specified in the schema, or in the schema element's FK reference.

- Example of defining the search in the HTML. UI Map’s Schema:

<schema>

<uiMap/>

</schema>

UI Map’s HTML

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>UI Map with Search </td>

<td><input oraField="uiMap" oraSearch="F1-UISRCH"></td>

</tr>

</table>

</body>

<xml>

<root>

<uiMap/>

</root>

</xml>

</html>

- Example of defining the search in the schema. UI Map’s Schema:

<schema>

<uiMap search="F1-UISRCH"/>

</schema>

UI Map’s HTML

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>UI Map with Search </td>

<td><input oraField="uiMap"></td>

</tr>

</table>

</body>

<xml>

<root>

<uiMap/>

</root>

</xml>

</html>

- Example where the FK reference defines the search zone. UI Map’s Schema:

<schema>

<uiMap fkRef="F1-UISRC"/>

</schema>

UI Map’s HTML

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>UI Map with Search </td>

<td><input oraField="uiMap"></td>

</tr>

</table>

</body>

<xml>

<root>

<uiMap/>

</root>

</xml>

</html>

In all cases, the HTML rendered is the same.

Initializing Search Fields

This optional attribute is used to initialize search zone filters. Multiple filters may be initialized. This attribute can only be used in conjunction with the oraSearch attribute.

Syntax

Valid Values

Field Value Options

Comments

oraSearchField=" "

One or more pairs of field name and field value separated by colon. Each pair is separated by a semi-colon.

oraSearchField="fieldName:fieldValue: ..."

The field name is used to identify the zone filter to initialize when the search is launched. The field name must match the value of the searchField mnemonic specified on a search zone user filter or hidden filter parameter.

No value

If you do not specify a field value, then the value of the input element containing the oraSearchField attribute will be used.

XPath

Indicate the XPath to the schema element that contains the value to use.

'literal'

Indicate a literal value to supply.

Note: If you do not specify an oraSearchField attribute and the schema element has a search enabled fkRef specified, the framework automatically builds an oraSearchField where the field name is equal to the FK reference's key (MD) fields.

Warning: The pop-up explorer zone can be invoked one of two ways: By clicking on the search button, or by hitting the enter key from the field to the left of the button. If you click on the button then no search field information will be passed to the zone. Search field information is only used to initialize zone filter values when enter is pressed.

Two filter values are initialized as shown in the following example:

<schema>

<bo/>

<uiMap/>

</schema>

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>UI Map with Search </td>

<td><input oraField="uiMap" oraSearch="F1-UISRCH" oraSearchField="MAP_CD; BUS_OBJ_CD:bo;"></td>

</tr>

</table>

</body>

<xml>

<root>

<bo/>

<uiMap/>

</root>

</xml>

</html>

Mapping Returned Search Fields

This optional attribute is used to direct values returned by the search zone. Multiple fields may be specified. This attribute can only be used in conjunction with the oraSearch attribute.

Syntax

Valid Values

Field Value Options

Comments

oraSearchOut=" "

One or more pairs of field name and field value separated by colon. Each pair is separated by a semi-colon.

oraSearchOut="field name:xpath target; ..."

The field name is used to identify the search result returned from the query zone. The field name must match the ELEMENT_NAME mnemonic defined within the explorer zone's search results parameter.

No value

If you do not specify a field value, then the input element containing the oraSearchField attribute receives the returned value.

XPath

Indicate the XPath to the schema element that should receive the returned value.

Note: If you do not specify an oraSearchOut attribute, the framework will build a default where the field name will be set equal to the oraSearchField's field name.

Two values are returned in the following example:

<schema>

<bo/>

<mo/>

</schema>

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>BO Search </td>

<td><input oraField="bo" oraSearch="Z1-BOSRCH" oraSearchOut="BUS_OBJ_CD; MO_CD:mo;"></td>

</tr>

</table>

</body>

<xml>

<root>

<bo/>

<mo/>

</root>

</xml>

</html>

Display Errors

Display Error Variables

One of the following error variables may be displayed.

Syntax

oraErrorVar="ERRMSG-TEXT"

oraErrorVar="ERRMSG-LONG"

oraErrorVar="ERRMSG-CATEGORY"

oraErrorVar="ERRMSG-NUMBER"

...

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td>

<a href="" onclick="oraShowErrorAlert(); return false;">

<span  class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span>

</a>

</td>

</tr>

</table>

...

HTML rendered

Highlight a Field in Error

Note: For more information on throwing an error, refer to the Terminate Statement in the Edit Data Syntax.

Syntax

Comments

oraError="automate:true|false; prefix: "

Specifying automate:true automatically enables highlighting of the element in error when issuing an error. Note that true is the default and doesn’t need to be specified. Specify automate:false to turn off field highlighting.

The system uses a match on the element name referenced in the error to the element names in the UI map. If the elements in the schema are within an XPath that may not match what is referenced by the error, use prefix:XPath to specify that.

Note: A pair of stylesheet references, cisEnabled and cisDisabled, must be specified for reference of the oraError style. The stylesheet controls how the field in error will be rendered. If you want to alter the rendering you must override the oraError style.

The following HTML example shows that the elements in the map are defined within a group called boGroup. The element name returned by the error will not include this group so in order for the field highlighting to work properly the prefix: attribute must indicate the group name.

<html>

<head>

<title>User Zone Input</title>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body oraError="automate:true; prefix:boGroup">

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td>

<a href="" onclick="oraShowErrorAlert(); return false;">

<span  class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span>

</a>

</td>

</tr>

</table>

<table width="100%" border="0" cellpadding="4">

<tr style="padding-top:30px;">

<td align="right" class="label">User Id</td>

<td>

<span oraField="boGroup/userId" class="normal"/>

</td>

</tr>

<tr>

<td align="right" class="label">First Name</td>

<td>

<input oraField="boGroup/firstName" class="normal"/>

</td>

</tr>

<tr>

<td align="right" class="label">Last Name</td>

<td>

<input oraField="boGroup/lastName" class="normal"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<boGroup>

<userId>BOND007</userId>

<firstName>James</firstName>

<lastName></lastName>

</boGroup>

</root>

</xml>

</html>

HTML rendered, where the error element thrown is equal to 'lastName':

Overriding the Error Element Name

In the rare occasion where the element name returned by the error doesn't match the element name in the map, you can add an explicit attribute to indicate the error element name.

Syntax

Valid Values

Comments

oraErrorElement=

"element name"

The element name referenced here must exactly match the name of the error element assigned when the error was thrown. More than one HTML field can be referenced by the same error element name.

Note: A pair of stylesheet references, cisEnabled and cisDisabled, must be specified for reference of the oraError style. The stylesheet controls how the field in error will be rendered. If you want to alter the rendering you must override the oraError style.

This illustrates a scenario where the element name associated with the error differs from the element name on the map.

<html>

<head>

<title>User Zone Input</title>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td>

<a href="" onclick="oraShowErrorAlert(); return false;">

<span  class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span>

</a>

</td>

</tr>

</table>

<table width="100%" border="0" cellpadding="4">

<tr style="padding-top:30px;">

<td align="right" class="label">User Id</td>

<td>

<span oraField="userId" class="normal"/>

</td>

</tr>

<tr>

<td align="right" class="label">First Name</td>

<td>

<input oraField="firstName" class="normal" oraErrorElement="firstName"/>

</td>

</tr>

<tr>

<td align="right" class="label">Last Name</td>

<td>

<input oraField="familyName" class="normal"  oraErrorElement="lastName"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<userId>BOND007</userId>

<firstName>James</firstName>

<familyName></familyName>

</root>

</xml>

</html>

HTML rendered.

Display Error Pop-Up

When the error text is displayed, this function may be used to pop-up the standard error dialog (which displays more information) when a user clicks the error message.

Syntax

oraShowErrorAlert(); return false;

<html>

<head>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td>

<a href="" onclick="oraShowErrorAlert(); return false;">

<span  class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span>

</a>

</td>

</tr>

</table>

<table>

<tr>

<td >Address:</td>

<td><input type="text" oraField="address"/></td>

</tr>

<tr>

<td>City:</td>

<td><input type="text" oraField="city"/></td>

</tr>

<tr>

<td>State:</td>

<td><input type="text" oraField="state"/></td>

</tr>

<tr>

<td>Zip:</td>

<td><input type="text" oraField="zip"/></td>

</tr>

<tr>

<td/>

<td style="padding-top=15px;">

<oraInclude map="F1-SaveCancelButtons"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

</root>

</xml>

</html>

HTML rendered.

Standard error pop-up dialog launched via click on error message:

Fire JavaScript for Browser Events

Working with the JavaScript Framework

There are many JavaScript events that can be used within the HTML/Javascript environment. These include events such as onLoad, onBlur, onChange, etc. The UI Map Framework also makes use of some of these events. It is important that any UI Map you develop works with the framework in order to obtain consistent results (events may not always be executed in the same order at all times!).

Warning:

The following describes the recommended approach for safely handling loading and processing field updates in your UI Maps.

If JavaScript is required within an XHTML UI Map or fragment, it will be necessary to bound it within a ![CDATA[ ]] tag to ensure a valid XML document. Note that the tags themselves may need to be commented out to promote compatibility with older browsers. For example:

<script type="text/javascript">

/* <![CDATA[ */

//

// javascript

//

/* ]]> */

</script>

Element Change Event

Syntax

Valid Values

oraChange=" "

A JavaScript function.

At the time of UI Map load, if there is an event handler already attached to an HTML element, the framework removes it and attaches a combined event handler. The combined handler calls any framework handler first and then calls the other (custom) handlers.

Warning: Note that the function must not be used to execute logic that will modify the associated field data value again - or an endless loop will occur.

In the following example the oraInvokeBS function is executed when the button is clicked.

<html>

<head>

<title>oraInvokeBS test</title>

</head>

<body>

<table>

<tr>

<td>User Id:</td>

<td>

<input oraField= "xmlGroup/userId"/>

<input type="button" value="Search" oraChange="oraInvokeBS('UserSearch','xmlGroup');"/>

</td>

</tr>

<tr>

<td/>

<td>Search Results</td>

</tr>

<tr>

<td/>

<td>

<table oraList="xmlGroup/searchList">

<tr>

<td><span oraField="userId"></span>

</td>

</tr>

</table>

</td>

</tr>

</table>

</body>

<xml>

<root>

<xmlGroup>

<userId/>

<searchList>

<userId></userId>

</searchList>

</xmlGroup>

</root>

</xml>

</html>

Page Load Event

Syntax

Valid Values

oraLoad=" "

A JavaScript function.

Warning: When executing oraLoad within a fragment UI map, and you need to execute a JavaScript function during page load (where the function invokes a business object, business service, or service script) you can use the special syntax "oraLoad[$SEQUENCEID]". For other special syntax used for map fragments, refer to the Construct a Portal Zone Header section.

- In the following example, the oraDisplayNone function is executed during page load:

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td oraLoad="oraDisplayNone(item,'userId','')">User Id: </td>

<td><span oraField="userId"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<userId>SPLAXT</userId>

</root>

</xml>

</html>

- HTML rendered

After Page Load Event

Syntax

Valid Values

oraAfterLoad=" "

A JavaScript function.

In the following example the oraGetValueFromScript function is executed after page load.

<div>

<label for="boGroup_parameters_externalSystem" oraLabel="boGroup/parameters/externalSystem">

</label>

<span>

<select oraSelect="bs:F1-RetrieveExternalSystems" class="oraInput"

id="boGroup_parameters_externalSystem" oraField="boGroup/parameters/externalSystem"

oraSelectOut="valuePath:results/externalSystem; descPath:results/description"

oraSelectIn="outboundMsgType:boGroup/parameters/outboundMsgType"

oraAfterLoad

="oraGetValueFromScript(document.getElementById('boGroup_parameters_externalSystem');">

</select>

</span>

</div>

Hide Elements

Hide Using a Function

The system provides a function that is used to hide an HTML element based on the value on another element or based on the results of a JavaScript function. Note that the first parameter is the string item, which lets the function identify the HTML item being manipulated.

Syntax

Valid Values

Comments

oraDisplayNone(item );

(item, 'XPath', 'value', 'operator')

Used to hide an element based on the value of another element (referenced using its XPath). Enter a value of ' ' to interrogate a blank value. By default the operator is '='. This may be set instead to another operator such as '!=', '>', or '<'.

(item, function name,true | false)

Used to indicate a JavaScript function, which must return a Boolean.

- Example where the User Id label is hidden when no User Id value exists.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td oraLoad="oraDisplayNone(item,'userId','')">User Id: </td>

<td><span oraField="userId"></span></td>

</tr>

</table>

</body>

<xml>

<root>

<userId></userId>

</root>

</xml>

</html>

- Example where the Save button is hidden when the user does not have security access to the action of change ('C') for the application service 'F1-DFLTS'.

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td oraLoad="oraDisplayNone(item, oraHasSecurity('F1-DFLTS', 'C'), false );">

<input name="Save" type="button" onclick="oraInvokeBO('CM-IndividualTaxpayer', null, 'replace')"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<userId></userId>

</root>

</xml>

</html>

Check User's Security Access

The system provides two functions to check a user's security access to a given application service and access mode. These are commonly used for hiding elements.

Syntax

Parameters

oraHasSecurity( )

'Application Service code'

'Access Mode'

oraHasSecurityPath('x','y')

'Application Service XPath'

'Access Mode XPath'

See the previous section for an example of the oraHasSecurity function. The following shows an example where the status button is hidden when the user does not have security access to the access mode 'ACT' of the application service 'FORMTST'.

<html>

<body>

<table>

<tr>

<td oraLoad="oraDisplayNone(item, oraHasSecurityPath('appService', 'accessMode'), false );">

<input oraField="statusLabel" type="button" onclick="oraRunScript('UpdateState','status');"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<status>ACTIVATE</status>

<statusLabel>Activate</statusLabel>

<appService>FORMTST</appService>

<accessMode>ACT</accessMode>

</root>

</xml>

</html>

Invoke Schema Based Services

The system provides functions for invoking a business object, business service or service script.

Invoke BO Function

This function is used to perform a BO interaction directly from the UI map's HTML. It returns a 'true' or a 'false' depending on whether the invocation encounters an error.

Syntax

Parameters

Comments

oraInvokeBO( )

'BO Name'

'XPath' or null

Identifies a group element via XPath. If you specify the word null, then the entire embedded XML object will be passed.

'action'

Indicate the action to use. Valid values are add, delete, read, update, and replace.

- Example with the statement invoked in a JavaScript function.

function invokeBO {

if (!oraInvokeBO('F1-User','xmlGroup','read')) {

oraShowErrorAlert();

return;

}

}

- Example with the statement invoked within onClick.

<html>

<head>

<title>oraInvokeBO test</title>

</head>

<body>

<table>

<tr>

<td>User Id:</td>

<td>

<input oraField= "xmlGroup/userId"/>

<input type="button" value="Find" onClick="oraInvokeBO('F1-User','xmlGroup','read');"/>

</td>

</tr>

<tr>

<td/>

<td>Result</td>

</tr>

<tr>

<td/>

<td>

<span oraField="xmlGroup/firstName"></span>

<span oraField="xmlGroup/lastName"></span>

</td>

</tr>

</table>

</body>

<xml>

<root>

<xmlGroup>

<userId>SPLNXU</userId>

<firstName></firstName>

<lastName></lastName>

</xmlGroup>

</root>

</xml>

</html>

HTML rendered.

Invoke BS Function

This function is used to perform a business service interaction directly from the UI map's HTML. It returns a 'true' or a 'false' depending on whether the invocation encounters an error.

Syntax

Parameters

Comments

oraInvokeBS( )

'BS Name'

'XPath' or null

Identifies a group element via XPath. If you specify the word null, then the entire embedded XML object will be passed.

- Example with the statement coded within a JavaScript function.

function invokeBS {

if (!oraInvokeBS('F1-UserSearch','xmlGroup')) {

oraShowErrorAlert();

return;

}

}

- Example with the statement invoked via onClick.

<html>

<head>

<title>oraInvokeBS test</title>

</head>

<body>

<table>

<tr>

<td>User Id:</td>

<td>

<input oraField= "xmlGroup/userId"/>

<input type="button" value="Search" onClick="oraInvokeBS('F1-UserSearch','xmlGroup');"/>

</td>

</tr>

<tr>

<td/>

<td>Search Results</td>

</tr>

<tr>

<td/>

<td>

<table oraList="xmlGroup/searchList">

<tr><td><span oraField="userId"></span></td></tr>

</table>

</td>

</tr>

</table>

</body>

<xml>

<root>

<xmlGroup>

<userId/>

<searchList>

<userId></userId>

</searchList>

</xmlGroup>

</root>

</xml>

</html>

HTML rendered.

Invoke SS Function

This function is used to perform a service script interaction directly from the UI map's HTML. It returns a 'true' or a 'false' depending on whether the invocation encounters an error.

Syntax

Parameters

Comments

oraInvokeSS( )

'Service Script Name'

'XPath' or null

Identifies a group element via XPath. If you specify the word null, then the document belonging to the parent node will be passed. If the parent node is not enough, then the entire document can always be passed using the following syntax:
oraInvokeSS('service script',

null, null, [$SEQUENCEID])

- Example with the statement invoked within a JavaScript function:

function invokeSS {

if (!oraInvokeSS('F1-GetUsers','xmlGroup')) {

oraShowErrorAlert();

return;

}

}

- Example with the statement invoked within onClick.

<html>

<head>

<title>oraInvokeSS test</title>

</head>

<body>

<table>

<tr>

<td>User Id:</td>

<td>

<input oraField= "xmlGroup/userId"/>

<input type="button" value="Search" onClick="oraInvokeSS('F1-GetUsers','xmlGroup');"/>

</td>

</tr>

<tr>

<td/>

<td>Search Results</td>

</tr>

<tr>

<td/>

<td>

<table oraList="xmlGroup/searchList">

<tr><td><span oraField="userId"></span></td></tr>

</table>

</td>

</tr>

</table>

</body>

<xml>

<root>

<xmlGroup>

<userId/>

<searchList>

<userId></userId>

</searchList>

</xmlGroup>

</root>

</xml>

</html>

HTML rendered.

Refresh a Rendered Map or Portal Page

Refresh Map

This function is used to 'Refresh' only the map zone issuing the command.

Syntax

oraRefreshMap;

...

<tr>

<td/>

<td><input type="button" onclick="oraRefreshMap();" value="Refresh"/></td>

</tr>

...

Refresh Page

This function is used to refresh all zones in the portal.

Syntax

oraRefreshPage;

...

<tr>

<td/>

<td><input type="button" onclick="oraRefreshPage();" value="Refresh"/></td>

</tr>

...

Embed Framework Navigation

Navigate using Navigation Option

This function is used to navigate to another page using the information defined on a navigation option.

Syntax

Parameters

oraNavigate( );

'Navigation Option code'

'Key XPath'

Warning: This function is only intended for a UI map defined within a portal zone. It should not be used within a UI map launched by a BPA script.

The following example exhibits two possible uses of this function: as a URL and as a button. Note that the UI Map schema must contain a fkRef attribute. Refer to FK Reference Formatting for more information.

<schema>

<userId fkRef="CI_USER"/>

</schema>

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>User Link: </td>

<td><a href="" onclick="oraNavigate('userMaint','userId'); return false;">

<span oraField="userId" oraType="fkRef:CI_USER"></span></a>

</td>

</tr>

<tr>

<td>User Button: </td>

<td><input type="submit" onclick="oraNavigate('userMaint','userId')"

value="Go to User"/></td>

</tr>

</table>

</body>

<xml>

<root>

<userId>SPLAXT</userId>

</root>

</xml>

</html>

HTML rendered.

Launch BPA Script

Launch BPA Script

Syntax

Parameters

Comments

oraRunScript( );

'BPA script code'.

'XPath Element'

One or more element values may be passed into the BPA where it may be referenced as temporary variables.

Warning: This function is only applicable to UI maps displayed in portal zones. UI maps launched within a running BPA script cannot directly launch another BPA script from the UI map's HTML. Instead, return a value from the UI map and execute a Perform Script or Transfer Control step type.

Note: It is incumbent on the script author to pull information out of temporary storage in the initial steps of the script.

In the following example, a temporary variable named 'personId' is created with value '1234567890' and the BPA script named 'Edit Address' is launched.

<html>

<body>

<table>

<tr>

<td>

<div oraField="address"></div>

<span oraField="city"></span>

<span>,</span>

<span oraField="state"></span>

<span oraField="zip"></span>

<span oraField="country"></span>

<a href="" onClick="oraRunScript('Edit Address','personId');">edit</a>

</td>

</tr>

</table>

</body>

<xml>

<root>

<personId>1234567890</personId>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

</root>

</xml>

</html>

HTML rendered.

Launch BPA Script With Values

This function is used to launch a BPA, providing name/value pairs to push into temporary storage. Multiple values can be passed. The BPA script can then reference the temporary variables by name.

Syntax

Parameters

Comments

oraRunScriptWithValues( );

'BPA script code'.

'XPath Element Name':value

One or more pairs of element names and values.

Note: You would use this JavaScript function, instead of oraRunScript, if you need to push values to the BPA script that are not located in the UI Map's XML structure.

In the example below, a JavaScript function named 'editUser()' is responsible for launching the BPA script named 'UserEdit'. The temporary variable named 'userId' will be created with value 'CMURRAY'.

<html>

<head>

<script type="text/javascript">

function editUser() {

var values = {'userId': 'CMURRAY'};

oraRunScriptWithValues('UserEdit', values);

return;

}

</script>

</head>

<body>

...

</body>

</html>

Exit UI Map with Bound Values

This function is used to exit a UI Map. When you quit the map you can specify a value to return to the script and, in addition, whether to return updated XML.

Syntax

Parameters

Comments

oraSubmitMap( );

'Return Value'

Boolean value

Indicates if the updated XML should be returned. Default is true.

In the following example, the Save button will return updated information, the Cancel button will not.

<html>

<body>

<table>

<tr>

<td/>

<td style="padding-bottom:15px;">

<a href="" onclick="oraShowErrorAlert(); return false;">

<span oraErrorVar="ERRMSG-TEXT"></span></a>

</td>

</tr>

<tr>

<td >Address:</td>

<td><input type="text" oraField="address"/></td>

</tr>

<tr>

<td>City:</td>

<td><input type="text" oraField="city"/></td>

</tr>

<tr>

<td>State:</td>

<td><input type="text" oraField="state"/></td>

</tr>

<tr>

<td>Zip:</td>

<td><input type="text" oraField="zip"/></td>

</tr>

<tr>

<td/>

<td style="padding-top=15px;">

<input type="button" value="Save" onClick="oraSubmitMap('SAVE');"/>

<input type="button" value="Cancel" onClick="oraSubmitMap('CANCEL',false);"/>

</td>

</tr>

</table>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

</root>

</xml>

</html>

Save and Cancel buttons rendered:

Include a Map Fragment

This function is used to embed a map fragment within another UI map. Note that it is possible to use the include node within a map or a map fragment.

Syntax

Parameters

Comments

<oraInclude map=' ' prefixPath=' '/>

map='UI Map Code'

prefixPath='Xpath'

Optionally specify an xpath prefix to be appended onto every included oraField, oraLabel, oraList, oraSelect valuePath and descPath, oraDownloadData, and oraUploadData attribute value defined within the included UI map fragment's HTML.
Note: This functionality only applies to XPath attribute values when those values do not appear beneath an oraList attribute. Any XPath value within a table containing an oraList attribute will not be affected by a prefixPath.

- An example of a map fragment with two buttons, named 'F1-SaveCancelButtons'.

<input onClick ="oraSubmitMap('SAVE');" oraMdLabel="SAVE_BTN_LBL" class="oraButton"

type="button"/>

<input onClick ="oraSubmitMap('CANCEL',false);" oraMdLabel="CANCEL_LBL" class="oraButton"

type="button"/>

- An example of a map that includes the map fragment named 'F1-SaveCancelButtons'.

...

<tr>

<td colspan="2" align="center">

<oraInclude map="F1-SaveCancelButtons"/>

</td>

</tr>

...

Show Schema Default on Add

Default values within in the UI map's schema will be displayed on a UI map's input fields if an embedded <action> node has a value of 'ADD' or blank.

Syntax

<action>ADD</action>

<action> </action>

The schema default for the <description> element will be displayed:

<schema>

<action/>

<boGroup type="group">

<key/>

<description default="enter description here"/>

</boGroup>

</schema>

<html>

<body>

<table summary="" border="1" cellpadding="1" cellspacing="1">

<tr>

<td>Description   </td>

<td><input oraField="boGroup/description"></td>

</tr>

</table>

</body>

<xml>

<root>

<action>ADD</action>

<boGroup>

<key/>

<description/>

</boGroup>

</root>

</xml>

</html>

HTML rendered.

Configure a Chart

The following HTML attributes are used to configure a graphical representation of an XML list. The designer can control the type, size, position, and contents of the chart using the following attributes.

oraChart="type:pie, stacked, cluster, line, area, combo ;"

This attribute defines the type of graph to display and its general configuration. The set of configuration parameters available for this attribute are as follows:

Parameter

Values

Description

type:

pie

stacked

cluster

line

area

combo

Defines the type of chart to display.

Required

showLegend

true

false

Defines if the chart should have a legend displayed.

Optional (default is true)

legendPosition

left

right

bottom

top

Defines where the legend should appear.

Optional (default is right)

Setting position to left or right will automatically render it vertically.

Setting position to top or bottom will automatically render it horizontally.

legendBorder

true

false

Defines if the legend should display with a border around it.

Optional (default is false )

depth

true

false

A value of true indicates a 3 dimensional depth for the chart.

Optional (default false, which is a 2 dimensional chart)

animate

true

false

A value of true indicates that the graph should animate when displayed.

Optional (default is true). When using large data sets, consider disabling animation.

dataCursor

on

off

A value of on enables hovering anywhere in the graph.

Optional (default is off). It is not applicable to pie charts.

orientation

horizontal

Defines the chart orientation. This only applies to bar, line, area, combo charts.

E.g., oraChart="type:cluster; orientation:horizontal", defines horizontal cluster chart.

Optional (default is vertical).

The oraChartSeries attribute defines the source information for the graph. There are 5 of these attributes:

- oraChartSeries1

- oraChartSeries2

- oraChartSeries3

- oraChartSeries4

- oraChartSeries5

Stacked charts support an unlimited number of series by continuing to add attributes oraChartSeries6 and above, but beware of performance implications and memory limits when using an excessively high number of series.

All attributes are identical in format and accept the same parameters, as described below.

Note: All the charts require oraChartSeries1. Stacked, Cluster and Line charts may optionally include the additional series attributes (for multiple bars/lines).

If you define multiple series, then data must be provided for all series defined. The data amounts can be 0 (zero) but they have to be present in order for the chart to display correctly.

The set of configuration parameters available for the oraChartSeriesN attribute are:

Parameter

Values

Description

list:

XPath value

Defines the XPath to the list in the XML that contains the data to chart.

Required

amount:

XPath value

Defines the XPath to the element in the XML list that contains the amount to chart.

Required

xaxis:

XPath value

Defines the XPath to the element in the XML list that contains the x-axis data.

Required for Stacked, Cluster, Line, Area and Combo charts.

xaxisFormat:

date

dateTime

time

localDate

string

Defines the x-axis data format.

If it is date, dateTime or time then the value is presented in the format as defined on the user’s display profile.

In case of localDate or string the data is displayed as is with no special formatting.

Optional (Default is date).

label:

Text value

Defines the label for the amount being charted.

Either this setting or labelPath: must be defined.

labelPath:

XPath value

Defines the XPath to the element that provides the label for the amount being charted.

Either this setting or label: must be defined.

currency:

A valid Currency code

Defines the currency code for the amount being charted.

Optional.

currencyPath:

XPath value

Defines the XPath to the element that provides the currency code for the amount being charted.

Optional.

hoverText:

Text value

Defines the hover text for the chart element.

Optional (A default hover text is always available.) Ignored if hoverTextPath: is defined.

The following substitution variables are available.

- $label This will be replaced with the label text as determined by the label: or labelPath: setting.

- $amount This will be replaced with the amount text as specified by the amount: setting.

- $axis This will be replaced with the x-axis text.

- $% This will be replaced by the percentage "slice" of the pie or bar.

- $newline This will be force a line break.

If the hover text defined contains any of the above values, they will be replaced by the equivalent text prior to being displayed.

Example:

"hoverText:$label$newline$amount"

hoverTextPath:

XPath value

Defines the XPath to the element that provides the hover text for the chart element.

The hover text in the XML can utilize all the substitution functionality described above in the hoverText: description.

Optional.

type:

bar

line

area

This attribute is used for the combo chart type only. It defines how each series on the combo chart should be presented.

The following example defines a combo chart where one series is rendered as bars and another one as area.

oraChart="type:combo;"

oraChartSeries1="list:set; xaxis:date;

label:Charge; amount:amount;type:bar"

oraChartSeries2="list:set; xaxis:date;

label:Balance; amount:balance;type:area"

navOpt:

A valid Navigation Option code.

Defines a navigation option to be activated when the chart element is clicked.

Optional.

navOptPath:

XPath value

Defines the XPath to a navigation option to be activated when the chart element is clicked.

Optional

Note that both navOpt: and navOptPath: may be configured. The XPath navigation option is processed first. If a value is found it is used, otherwise the value in the navOpt: setting is used. This means that the HTML can define a "default" navigation option and a navigation option present in the XML document will override it.

key:

XPath value

Defines the XPath to an XML element in the series list that contains the key field data to be used in a navigation option.

This is required if either navOpt: or navOptPath: is defined.

Note: Only one key field can be configured for a navigation option.

script:

A BPA script name

Defines a BPA script to be activated when the chart element is clicked.

Optional

When a script is executed, all the elements from that list item will be made available to the script as temporary variables.

scriptPath:

XPath value

Defines the XPath to a BPA script to be activated when the chart element is clicked.

Optional

Note that both script: and scriptPath: can be configured. The XPath script option is processed first. If a value is found it is used, otherwise the value in the script: setting is used. This means that the HTML can define a default script and a script present in the XML document will override it.

color:

HTML Color code / RGB value

Defines the color for the series. The format is valid HTML color code, e.g. green, red or black. All valid color names are defined in this link: http://www.w3schools.com/htmL/html_colornames.asp.

Alternatively an RGB format may be used. (FF0000 is red, 00FF00 is green and 0000FF is blue)

Optional (default colors applied)

colorPath:

XPath value

Defines the XPath to a color for the series. The valid format as described in the color: setting apply.

Optional (default colors applied)

pieColors:

HTML color code / RGB values

Defines the colors for the pie series. Any number of HTML color codes or RGB color values can be specified, separated by spaces. Examples:

pieColors: red green black

pieColors: FF0000 00FF00

Optional (default colors applied if the series exceeds the values specified)

oraChartBroadcast="FIELD_NAME:XPath;"

A chart configured in a map zone can be set to broadcast portal context. An unlimited number of fields can be broadcast, configured as name/value pairs, as follows:

1. FIELD_NAME: the name of the portal context field to be broadcast.

2. XPath: the XML schema element from the same list item that corresponds to the user selected chart segment and contains the data value to be broadcast.

Graph Examples

- Sample of a pie chart configuration:

<html>

<head>

<title>Pie Chart</title>

</head>

<body>

<div style="width:100%; height:290px;"

oraChart="type:pie;"

oraChartSeries1="list:set; labelPath:date; amount:amount; "

oraChartBroadcast="BILL_ID:billId;">

</div>

</body>

<xml>

<root>

<set>

<date>05-02-2003</date>

<amount>163.24</amount>

<billId>592211649441</billId>

</set>

<set>

<date>06-02-2003</date>

<amount>97.29</amount>

<billId>592211649442</billId>

</set>

<set>

<date>07-02-2003</date>

<amount>54.38</amount>

<billId>592211649443</billId>

</set>

</root>

</xml>

</html>

- A pie chart rendered for a single series:

- Sample of a line, cluster, or stacked graph configuration - each with two series:

<html>

<head>

<title>Stacked Chart</title>

</head>

<body>

<div style="width:100%; height=300px;"

oraChart="type:line;"

oraChartSeries1="list:set; xaxis:date; label:Charge; amount:amount; "

oraChartSeries2="list:set; xaxis:date; label:Balance; amount:balance; "

oraChartBroadcast="BILL_ID:billId;">

</div>

<div style="width:100%; height=300px;"

oraChart="type:cluster;"

oraChartSeries1="list:set; xaxis:date; label:Charge; amount:amount; "

oraChartSeries2="list:set; xaxis:date; label:Balance; amount:balance; "

oraChartBroadcast="BILL_ID:billId;">

</div>

<div style="width:100%; height=300px;"

oraChart="type:stacked;"

oraChartSeries1="list:set; xaxis:date; label:Charge; amount:amount; "

oraChartSeries2="list:set; xaxis:date; label:Balance; amount:balance; "

oraChartBroadcast="BILL_ID:billId;">

</div>

</body>

<xml>

<root>

<set>

<date>05-02-2003</date>

<amount>163.24</amount>

<balance>163.24</balance>

<billId>592211649441</billId>

</set>

<set>

<date>06-02-2003</date>

<amount>97.29</amount>

<balance>260.53</balance>

<billId>592211649442</billId>

</set>

<set>

<date>07-02-2003</date>

<amount>54.38</amount>

<balance>314.91</balance>

<billId>592211649443</billId>

</set>

</root>

</xml>

</html>

- Three types of chart rendered for two series each: line, cluster, and stacked.

Upload and Download a CSV File

The following HTML attributes can be used to manage both an upload and a download between a list defined within the map's schema and a CSV (comma separated value) file.

The syntax is oraUploadData="type:embed;path:list xpath;useLabels:true;showCount:true"

Upload configuration requires you to name a CSV file to be uploaded, and an XML list as target. By convention, each CSV row will create a separate list instance. Each comma-separated field in the file will be uploaded as a separate element in the list. To embed an upload dialog within a map, the oraUploadData attribute must be associated with a container element such as a div, td, or span.

The optional useLabels:true value indicates that while parsing the upload CSV file, the headers are expected to be labels

Note: If you do not specify the useLabels:true value and the XML target element name is "camelCase" then the corresponding spreadsheet header should be title case with a space between words, e.g.;"Camel Case". Letters and special characters are not considered a different word, for example Address1 must be uploaded into the target XML element address1.

Specifying the optional showCount:true value will display the number of records uploaded.

CAUTION:

If you are using a grid in conjunction with the oraUploadData function, then you must maintain the grid's list with a 'replace' business object action. Refer to BO Replace Action for more information.

Sample of oraUploadData="embed" within a div element.

<html>

<head>

<title>File Upload</title>

</head>

<body>

<div oraUploadData="type:embed;path:myList"> </div>

</body>

<xml>

<root>

<myList>

<id>838383930</id>

<name>Janice Smith</name>

</myList>

<myList>

<id>737773730</id>

<name>Bill McCollum</name>

</myList>

</root>

</xml>

</html>

This file upload dialog will be embedded into the body of the page where the oraUploadData is defined.

oraUploadData="type:popup;path:list xpath;useLabels:true;showOk:true;showCount:true"

Upload configuration requires you to name a CSV file to be uploaded, and an XML list as target. By convention, each CSV row will create a separate list instance. Each comma-separated field in the file will be uploaded as a separate element in the list. To upload a CSV file using a pop-up dialog, the oraUploadData attribute must be associated with an input element such as a button, text link, or image.

The optional useLabels:true value is used to indicate that while parsing the upload CSV file, the headers are expected to be labels

Note: If you do not specify the useLabels:true value and the XML target element name is "camelCase" then the corresponding spreadsheet header should be title case with a space between words, e.g., "Camel Case". Letters and special characters are not considered a different word, for example Address1 must be uploaded into the target XML element address1.

Specifying the optional showOk:true value will display an "Ok" button once the upload finishes. The popup will stay open until the button is pressed. Additionally, specifying the showCount:true value will display number of records uploaded.

CAUTION:

If you are using a grid in conjunction with the oraUploadData function, then you must maintain the grid's list with a 'replace' business object action. Refer to BO Replace Action for more information.

Sample of oraUploadData="popup" associated with a button:

<html>

<head>

<title>File Upload</title>

</head>

<body>

<input type="button" name="submitButton" oraUploadData="type:popup;path:myList;" value='Get Data'>

<table oraList="myList">

<tr/>

<tr>

<td><span oraField="id"/></td>

<td><span oraField="name"/></td>

</tr>

</table>

</body>

<xml>

<root>

<myList>

<id>838383930</id>

<name>Janice Smith</name>

</myList>

<myList>

<id>737773730</id>

<name>Bill McCollum</name>

</myList>

</root>

</xml>

</html>

HTML Rendered:

Pressing the "Get Data" button will launch a standard file upload dialogue (provided by Framework) as shown below.

oraDownloadData="list xpath"

Download configuration requires you to name an XML list to be downloaded. By convention, each list instance will represent a separate row in the created file. By default every element of the list will be comma separated in the file.

Note: The number formatting is based on the user profile setting. For localities where the decimal symbol is a comma, an implementation may configure a property setting (spl.csv.delimiter.useFromDisplayProfile=true) to cause the system to use a semicolon as the delimiter that separates the elements rather than a comma.

Sample of oraDownloadData.

<html>

<head>

<title>File Download</title></head>

<body>

<input type="button" name="downloadButton" oraDownloadData="myList" value="Download"/>

</body>

<xml>

<root>

<myList>

<id>881-990987</id>

<name>John Mayweather</name>

</myList>

<myList>

<id>229-765467</id>

<name>Anna Mayweather</name>

</myList>

<myList>

<id>943-890432</id>

<name>Andrew Brewster</name>

</myList>

</root>

</xml>

</html>

HTML Rendered:

Pressing the "Download" button will launch a standard file download dialogue (provided by Framework) as shown below.

A successful download will result in a CSV file:

To download data from a sub list use the attribute oraDownloadDataInList instead of oraDownloadData. The attribute oraDownloadDataInList will have the sub list name. The XPath of the sub list is used to pick data of the specific row from the parent list. Thus only the specific sub list is downloaded.

oraDownloadDataUseLabels="true"

The oraDownloadDataUseLabels attribute can be used in conjunction with the oraDownloadData attribute described above. Specify oraDownloadDataUseLabels if you want the generated CSV file to use the element labels for columns headers rather than element names.

Construct Portal Zone Map Fragments

Portal zones can reference a UI map for the zone header and filter area. This UI map is not a complete HTML document, but is instead configured as a UI Map fragment. When constructing a zone map fragment you can reference the following substitution variables. Note that these variables will be dynamically populated at run time with information particular to the map's zone within the portal:

Variable

Replacement Logic

[$ZONEDESCRIPTION]

Zone's description text.

[$SEQUENCEID]

Zone's sequence ID.

[$ZONENAME]

Zone's name.

[$HELPTEXT]

Zone's help text.

[$ZONEPARAMNAME]

Zone parameter's value (or blank if it has not been specified).

Warning:

- Refer to one of the following maps as examples: F1-UIMapHeader and F1-ExplorerHeader.

- These maps make use of the oraInclude tag to incorporate HTML fragments for the header menu and framework actions. Refer to the zone type parameters for the UI Map fragments you should include in your HTML.

- If you wish to have the "help text" icon appear next to your zone description, you should have id="title_[$SEQUENCEID]" on the <td> that contains your description.

- If it is necessary to encapsulate JavaScript within a UI Map fragment, it will be necessary to bound the JavaScript within a ![CDATA[ ]] tag to ensure a valid XML document. Note that the tags themselves may need to be commented out to promote compatibility with older browsers. For example:

<script type="text/javascript">

/*<![CDATA[ */

//

//javascript

//

/*]]> */

</script>

Note: If you wish to preserve the values of a filter input field, within a filter map fragment, for the framework 'Go Back' and 'Go Forward' functionality, you must associate the input field (text box, select, etc.) with a unique HTML id. Input field values associated with a unique id will be captured in the framework's 'memento'. The 'memento' is used to rebuild the input map when the portal zone is navigated to using the 'Go Back' or 'Go Forward' functionality.

Note: Many specialized functions exist to manipulate zone behavior, for example:

- oraGetZoneSequence(zoneName). Uses the zone's code to retrieve its sequence number.

- oraIsZoneCollapsed(sequenceId). Uses the zone's sequence to determine if collapsed.

- oraHandleCollapse(seq). Collapse a zone.

- oraHandleExpand(seq,refresh). Expand and/or refresh a zone.

All of these, and many more functions, are located within the JavaScript library userMapSupport.js described below.

Note: When executing oraLoad within a fragment UI map, and you need to execute a JavaScript function during page load (where the function invokes a business object, business service, or service script) you can use the special syntax "oraLoad[$SEQUENCEID]". Refer to the Load Page Event section for more information.

Example of oraLoad[$SEQUENCEID] used within a function:

<script type="text/javascript">

function oraLoad[$SEQUENCEID]() {

checkRebateClaimStatus();

}

function checkRebateClaimStatus() {

var work = id(''analyticsFilterText[$SEQUENCEID]'',

document).cells[0].innerText.split('' '');

var rebateClaimId = work[work.length - 3];

id(''rebateClaimId'', document).value = rebateClaimId;

oraInvokeSS(''C1-CheckRCSt'',''checkRebateClaimStatus'', false);

var statusIndicator = id(''statusInd'', document).value;

if (statusIndicator == ''C1PE'' || statusIndicator == ''C1ID'') {

id(''addRebateClaimLine'', document).style.display = '''';

} else {

id(''addRebateClaimLine'', document).style.display = ''none'';

}

}

</script>

F1-ExplorerHeader rendered:

Invoking a Business Object

The oraInvokeBO function may be used within a portal zone header or zone filter map. It is similar to the command described in Invoke BO Function which allows for a business object to be invoked within the UI map’s HTML. Refer to that section for a description of the first three parameters.

Syntax

Parameters

Comments

oraInvokeBO( )

'BO Name'

'XPath' or null

'action'

null

This must be specified as the fourth argument.

[$SEQUENCEID]

This must be specified as the fifth argument.

true | false

Specify true if the fragment is used within a portal zone header. Specify false if the fragment is used with a zone filter map.

Example in a portal zone header:

oraInvokeBO('CM-User','xmlGroup','read', null, [$SEQUENCEID], true)

Invoking a Business Service

The oraInvokeBS function may be used within a portal zone header or zone filter map. It is similar to the command described in Invoke BS Function which allows for a business service to be invoked within the UI map’s HTML. Refer to that section for a description of the first two parameters.

Syntax

Parameters

Comments

oraInvokeBS( )

'BO Name'

'XPath' or null

null

This must be specified as the fourth argument.

[$SEQUENCEID]

This must be specified as the fifth argument.

true | false

Specify true if the fragment is used within a portal zone header. Specify false if the fragment is used with a zone filter map.

Example in a portal zone header:

oraInvokeBS('CM-UserSearch','xmlGroup', null, [$SEQUENCEID], true)

Invoking a Service Script

The oraInvokeSS function may be used within a portal zone header or zone filter map. It is similar to the command described in Invoke SS Function which allows for a service script to be invoked within the UI map’s HTML. Refer to that section for a description of the first two parameters.

Syntax

Parameters

Comments

oraInvokeSS( )

'Service Script Name'

'XPath' or null

null

This must be specified as the fourth argument.

[$SEQUENCEID]

This must be specified as the fifth argument.

true | false

Specify true if the fragment is used within a portal zone header. Specify false if the fragment is used with a zone filter map.

Example in a portal zone header:

oraInvokeSS('UserSearch','xmlGroup', null, [$SEQUENCEID], true)

Detecting Unsaved Changes

Use this function to return a Boolean set to true if there are unsaved changes. The system will interrogate the function when the user attempts to navigate and issue a warning accordingly. This function is only needed if a UI map is using custom javascript to manage elements such that the system is not able to detect whether changes have been made. Also note that it's the responsibility of the UI map javascript to manage the values in the Boolean used for this function.

function hasUnsavedChanges(){

return isDirtyFlag;

}

Hiding Portal Tabs

The product provides the ability to use JavaScript to hide a tab on the current portal based on some condition using the oraAuthorizeTab JavaScript API. This API accepts a function as a parameter and turns off the tab index indicated.

For example, the UI Map may have a function to turn off one or more tab indexes.:

function overrideTabIndex(index){

if (index == 2) return false;

if (index == 3) return false;

}

The JavaScript is referenced “on load”:

<body class="oraZoneMap"

onLoad="oraAuthorizeTabs(overrideTabIndex);">

Required JavaScript Libraries

All of the functionality described in this document depends on a pair of JavaScript libraries. If you are writing and executing your maps entirely within the UI map rendering framework - you do not need to manually insert the following libraries - the framework will insert them for you when the UI Map is rendered.

Warning: When executing HTML outside of the framework you must include the following references explicitly within your HTML. In addition, the tool you use to render the HTML must have access to a physical copy of privateUserMapSupport.js for bind support.

src="privateUserMapSupport.js"

Your HTML document must reference this library to execute binding in a stand-alone environment.

Warning: Referencing functions within this JavaScript library is dangerous - because these functions are owned by framework and they may be changed during version upgrade or via the normal patch process.

<script type="text/javascript" src="privateUserMapSupport.js"></script>

src="userMapSupport.js"

To take advantage of optional toolset features, you must reference this library.

Note: You can reference the functions within this JavaScript library to write custom functions within the UI map..

<script type="text/javascript" src="userMapSupport.js"></script>

onload="oraInitializeUserMap();"

To execute binding in a stand-alone environment, you must embed the following onload function into the <body> node.

<body onload="oraInitializeUserMap();">

UI Map Standards

Contents

Basic UI Map Templates

Basic HTML and Styles

Grids (Tables of Data)

Action Buttons

Available Styles

Using OJET

Basic UI Map Templates

All UI Maps share the same basic structure regardless of placement (page area, zone, pop-up) or usage (display only, input).

Sample XML

All information in this document is based upon the following XML structure.

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

<contactInformation>

<type>Home Phone</type>

<number>510-555-2287</number>

</contactInformation>

<contactInformation>

<type>Cell Phone</type>

<number>510-555-4285</number>

</contactInformation>

</root>

</xml>

Display Only UI Map

<html>

<head>

<title oraMdLabel="ADDRESS_LBL"></title>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body class="oraZoneMap">

<table cellspacing="4" width="100%">

<colgroup>

<col class="oraLabel oraTableLabel" />

<col class="oraNormal oraTableData" />

</colgroup>

<tr>

<td oraLabel="address"></td>

<td oraField="address"></td>

</tr>

<tr>

<td oraLabel="city"></td>

<td oraField="city"></td>

</tr>

<tr>

<td oraLabel="state"></td>

<td oraField="state"></td>

</tr>

<tr>

<td class="oraSectionEnd" oraLabel="zip"></td>

<td class="oraSectionEnd" oraField="zip"></td>

</tr>

<tr>

<td colspan="2" class="oraSectionHeader" oraMdLabel="CONTACT_LBL"></td>

</tr>

<tr>

<td colspan="2" class="oraSectionStart oraEmbeddedTable">

<table oraList="contactInformation" cellspacing="2">

<thead >

<tr>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type></span>

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/number"></span>

</th>

</tr>

</thead >

<tbody>

<tr>

<td class="oraNormalAlt oraDisplayCell">

<span oraField="type"></span>

</td>

<td class="oraNormal oraDisplayCell">

<span oraField="number"></span>

</td>

</tr>

</tbody>

</table>

</td>

</tr>

</table>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

<contactInformation>

<type>Home Phone</type>

<number>510-555-2287</number>

</contactInformation>

<contactInformation>

<type>Cell Phone</type>

<number>510-555-4285</number>

</contactInformation>

</root>

</xml>

</html>

Input UI Map

<html>

<head>

<title oraMdLabel="ADDRESS_LBL"></title>

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

</head>

<body>

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td><a href="" onclick="oraShowErrorAlert(); return false;">

<span  class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span></a>

</td>

</tr>

</table>

<table cellspacing="4" width="100%">

<colgroup>

<col class="oraLabel oraTableLabel" />

<col class="oraNormal oraTableData" />

</colgroup>

<tr>

<td oraLabel="address"></td>

<td><input type="text" oraField="address"/></td>

</tr>

<tr>

<td oraLabel="city"></td>

<td><input type="text" oraField="city"/></td>

</tr>

<tr>

<td oraLabel="state"></td>

<td><input type="text" oraField="state"/></td>

</tr>

<tr>

<td oraLabel="zip"></td>

<td><input type="text" oraField="zip"/></td>

</tr>

<tr>

<td colspan="2" class="oraSectionHeader" oraMdLabel="CONTACT_LBL"></td>

</tr>

<tr>

<td colspan="2" class="oraSectionStart oraEmbeddedTable">

<table oraList="contactInformation" cellspacing="2">

<thead >

<tr>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type></span>

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/number"></span>

</th>

</tr>

</thead >

<tbody>

<tr>

<td oraType="addGridRow"></td>

<td oraType="deleteGridRow"></td>

<td>

<input type="text" oraField="type"/>

</td>

<td>

<input type="text" oraField="number"/>

</td>

</tr>

</tbody>

</table>

</td>

</tr>

<tr>

<td colspan="2" class="oraSectionStart oraEmbeddedTable">

<table cellspacing="2">

<tr>

<td>

<input class="oraButton" oraMdLabel="C1_SAVE_LBL" type="button"

onClick="oraSubmitMap('OK');"/>

</td>

<td>

<input class="oraButton" oraMdLabel="CANCEL_LBL" type="button"

onClick="oraSubmitMap('CANCEL',false);"/>

</td>

</tr>

</table>

</td>

</tr>

</table>

</body>

<xml>

<root>

<address>123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

<contactInformation>

<type>Home Phone</type>

<number>510-555-2287</number>

</contactInformation>

<contactInformation>

<type>Cell Phone</type>

<number>510-555-4285</number>

</contactInformation>

</root>

</xml>

</html>

Basic HTML and Styles

The basic templates introduced the standard HTML and styles used for UI Maps. These standards are described individually in the following sections.

Stylesheets

The styles to apply the standard look to the maps are all contained in stylesheets. These stylesheets should be included in all UI Maps.

...

<link rel="stylesheet" type="text/css" href="cisDisabled.css"/>

<link rel="stylesheet" type="text/css" href="cisEnabled.css"/>

...

Title

Each UI Map should have a <title> tag.

...

<title oraMdLabel="ADDRESS_LBL"></title>

...

This will give the UI Map a descriptive title.

- If the UI Map is presented in a "pop-up", the title will be in the window title bar.

- If the UI Map is presented in the page area, the title will be added as a <span> tag to the UI Map and will appear at the top of the UI Map.

- If the UI Map is presented as a zone map, it will be ignored. The <title> tag should still be included in the HTML as standard.

Zone Maps

When the map is presented in a zone as part of a portal, the UI Map should have a border so that the information is "contained" within the zone.

...

<body class="oraZoneMap">

...

Page Area Maps vs Pop-Up Maps

The presentation of the UI Maps can vary from design to design. The following standards have been applied to decide when to use a Page Area UI Map and when to use a Pop-Up Map:

- If there are multiple UI Maps in the sequence, always use the Page Area.

- If the UI Map has many input fields, always use a Page Area.

- If the UI Map is a "confirmation" type dialog or only has one or two input fields, use a Pop-Up.

Note: The difference between "just a few input fields" and "many input fields" can be discretionary. The final decision should rest with the dialog designer.

Error Messages

Input maps have a ability to present error messages to the User.

...

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td><a href="" onclick="oraShowErrorAlert(); return false;">

<span class="oraErrorText" oraErrorVar="ERRMSG-TEXT"></span></a></td>

</tr>

</table>

...

This HTML structure provides the provides the necessary elements and functions to display errors to the User. It should be directly after the <body> tag. When there is no error, nothing will be visible on the UI Map. It will be made visible if an error occurs and the UI Map is re-presented to the User. Clicking on the link (when visible) will result in a pop-up alert appearing with the long error message text.

Standard Layout and Styles

The information is presented on the UI Map by using a <table> to organize the information in rows and columns.

...

<table cellspacing="4" width="100%">

<colgroup>

<col class="oraLabel oraTableLabel" />

<col class="oraNormal oraTableData" />

</colgroup>

...

The <colgroup> and <col> tags allow for the application of classes to the columns (the label is in the first column and the data is in the second column.). Using these tags mean that the class attribute (to apply styles) does not need to be defined on every <td>.

Grids (Tables of Data)

A UI Map could contain information that is best presented as a grid. These are referred to as "Embedded Tables". The embedded table can be used to display information or input information.

Example Embedded Table HTML

The embedded table will be included within a row (<tr>) of the basic layout:

...

<tr>

<td colspan="2" class="oraEmbeddedTable">

<table oraList="contactInformation" cellspacing="2">

<thead >

<tr>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type></span>

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/number"></span>

</th>

</tr>

</thead >

<tbody>

<tr>

<td class="oraNormalAlt oraDisplayCell">

<span oraField="type"></span>

</td>

<td class="oraNormal oraDisplayCell">

<span oraField="number"></span>

</td>

</tr>

</tbody>

</table>

</td>

</tr>

...

<xml>

<root>

<address> 123 Main St</address>

<city>Alameda</city>

<state>CA</state>

<zip>94770</zip>

<contactInformation>

<type>Home Phone</type>

<number>510-555-2287</number>

</contactInformation>

<contactInformation>

<type>Cell Phone</type>

<number>510-555-4285</number>

</contactInformation>

</root>

</xml>

Embedding the Table

The embedded table is included within the overall table structure. The colspan attribute ensures that the embedded table can span the standard two columns of the overall layout table.

...

<tr>

<td colspan="2" class="oraEmbeddedTable">

...

...

...

</td>

</tr>

...

Embedded Table Structure

The embedded table is very similar to the basic layout table.

...

<table oraList="contactInformation" cellspacing="2">

<thead>

...

...

</thead>

<tbody>

...

...

</tbody>

</table>

...

- The <table> tag has a slightly smaller cellspacing and it defines the "list" element contained in the XML that will be used to provide the data.

- The <thead> element is used to give the embedded table headings for the columns.

- The <tbody> element is the element that will be repeated for each referenced "list" element in the XML. In the previous example, there are two "contactInformation" list elements, so the displayed embedded table will have two rows.

Column Headings

Embedded tables should have headings for the displayed columns. The <thead> tag defines these.

...

<thead>

<tr>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type></span>

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/number"></span>

</th>

</tr>

</thead>

...

The "nowrap" attribute prevent the column heading from taking multiples lines. If multiples lines are required, the "nowrap" may be removed.

Input Fields

Embedded tables may be used for input as well as display only. The framework provides a convenient control to assist in the creation of editable embedded tables.

...

<tr>

<td colspan="2" class="oraEmbeddedTable">

<table oraList="contactInformation" cellspacing="2">

<thead >

<tr>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type></span>

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/number"></span>

</th>

</tr>

</thead >

<tbody>

<tr>

<td oraType="addGridRow"></td>

<td oraType="deleteGridRow"></td>

<td>

<input type="text" oraField="type"/>

</td>

<td>

<input type="text" oraField="number"/>

</td>

</tr>

</tbody>

</table>

</td>

</tr>

...

There are two new columns added to the input embedded table.

- oraType="addGridRow" will add a "+" button to the row. This will allow the User to add an additional row to the existing grid.

- oraType="deleteGridRow" will add a "-" button to the row. This will allow the User to delete an existing row from the grid.

Note: The <thead> tag also requires these two new columns to be added.

These controls are, as standard, placed at the beginning of the row in the order shown. Either of the controls may be omitted if required (if, for example, Users are not permitted to delete information).

The presence of either of these controls will activate the "empty list" process. This means that if the XML has no data for the "list" specified, the input grid will display with an empty row ready for the input of new information.

Action Buttons

Example Action Button HTML

Action buttons are used to perform some specified function from the UI Map. The actions are as varied as the information being displayed/updated. Below are two common examples:

- Save. Normally used on an Input UI Map to allow a User to save any changes they have made.

- Cancel. Normally used on an Input UI Map to allow a User to cancel changes in progress.

...

<tr>

<td colspan="2" class=" oraEmbeddedTable">

<table cellspacing="2">

<tr>

<td>

<input class="oraButton" oraMdLabel="C1_SAVE_LBL" type="button"

onClick="oraSubmitMap('OK');"/>

</td>

<td>

<input class="oraButton" oraMdLabel="CANCEL_LBL" type="button"

onClick="oraSubmitMap('CANCEL',false);"/>

</td>

</tr>

</table>

</td>

</tr>

...

Button Standards

The following points highlight some standards related to buttons.

- Buttons are included as an embedded table.

- Buttons should be grouped together. They should not be placed in different areas of the UI Map.

- The location of the buttons depends mainly on the type of UI Map.

- Display Only UI Maps should have a Record Actions section in the upper right section of the UI map.

- Input UI Maps should have the buttons at the foot of the UI Map (after all input fields).

Available Styles

Styles are all contained in the referenced CSS stylesheets. They are applied by the HTML "class" attribute. The actual style settings used are not documented here as they may be adjusted. This section only specifies when a particular style should be used.

Note: The "class" attribute may reference more than one style (class="oraLabel oraSectionEnd")

Style

Comments

Example

oraButton

Applied to <input> elements where the type is button.

...

<input class="oraButton"

oraMdLabel="CANCEL_LBL"

type="button"

onClick="oraSubmitMap('CANCEL',false);"/>

...

oraDisplayCell

Applied to the <td> tag of an embedded table. It defines how the table cell looks (not the data contained inside the cell).

...

<td class="oraDisplayCell">

<span oraField="type"></span>

</td>

...

oraEmbeddedTable

Applied to the <td> tag that will contain the embedded table.

...

<tr>

<td colspan="2" class=" oraEmbeddedTable">

<table cellspacing="2">

...

...

...

</table>

</td>

</tr>

...

oraError

This style is applied to elements that are identified as "error elements". Refer to Display Errors for more information.
Note: This style is not normally applied directly in the UI Map HTML

oraErrorText

This style is applied to the elements concerned with error messages.

...

<table width="100%" cellpadding="12">

<tr class="oraErrorText">

<td><a href=""

onclick="oraShowErrorAlert();

return false;">

<span class="oraErrorText"

oraErrorVar="ERRMSG-TEXT"></span>

</a>

</td>

</tr>

</table>

...

oraGridColumnHeader

This style is applied to the <td> tags that define column headers within embedded table.

...

<thead >

<tr>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeaderButton"></th>

<th class="oraGridColumnHeader"

nowrap="nowrap">

<span oraLabel="contactInformation/type>

</span></th>

<th class="oraGridColumnHeader"

nowrap="nowrap">

<span oraLabel="contactInformation/number">

</span></th>

</tr>

</thead >

...

oraGridColumnHeaderButton

This style is applied to the <td> tags that define the column headers for the "+" and "-" buttons used on editable embedded tables.

...

<thead >

<tr>

<th class="oraGridColumnHeaderButton">

</th>

<th class="oraGridColumnHeaderButton">

</th>

<th class="oraGridColumnHeader" nowrap="nowrap">

<span oraLabel="contactInformation/type>

</span></th>

<th class="oraGridColumnHeader"

nowrap="nowrap">

<span oraLabel="contactInformation/number">

</span></th>

</tr>

</thead >

...

oraInput

This style is applied to input fields:

- <input type="text">

- <input type="checkbox">

- <select>

- <textarea>

Note: This can normally be omitted as input styles are applied automatically when oraSchemaDataTypes="true".

...

<input type="text" class="oraInput"

oraField="address"/>

...

oraInputMoney

This style is applied to input fields:

- <input type="text">

- <select> (rare)

- <textarea> (not recommended)

Note: This can normally be omitted as input styles are applied automatically when oraSchemaDataTypes="true".

...

<input type="text" class="oraInputMoney"

oraField="amount"/>

...

oraInputNumber

This style is applied to input fields:

- <input type="text">

- <select> (rare)

- <textarea> (not recommended)

Note: This can normally be omitted as input styles are applied automatically when oraSchemaDataTypes="true".

...

<input type="text" class="oraInputNumber"

oraField="count"/>

...

oraLabel

This style is applied to standard label fields that are right aligned.
Note: This can normally be omitted as it is applied by the <col> tag.

...

<td class="oraLabel"

oraLabel="address"></td>

...

oraLabelAlt

This style is applied to standard label fields only if it is desired to have the label aligned to the left.

...

<td class="oraLabelAlt"

oraLabel="address"></td>

...

oraLabelCenter

This style is applied to standard label fields only if it is desired to have the label aligned in the center of the cell.

...

<td class="oraLabelCenter"

oraLabel="address"></td>

...

oraLink

This style is applied to foreign key references (links). This is automatically added by the UI Map framework but can also be used manually if desired.

...

<td class="oraLabel">

<a href="www.google.com"

class="oraLink">Google</a></td>

...

oraNormal

This style is applied to standard data fields (display only) that are left aligned.
Note: This can normally be omitted as it is applied by the <col> tag.

...

<td class="oraNormal"

oraField="address"></td>

...

oraNormalAlt

This style is applied to standard data fields (display only) only if it is desired to have the data aligned to the right.

...

<td class=" oraNormalAlt"

oraField="address"></td>

...

oraNormalCenter

This style is applied to standard data fields (display only) only if it is desired to have the data aligned in the center of the cell.

...

<td class=" oraNormalCenter"

oraField="address"></td>

...

oraPageTitle

This style is applied to the element that contains the page title.
Note: This style is not normally applied directly in the UI Map HTML. The <span> is created by the UI Map framework when the UI Map is displayed in the page area.

...

<span class=" oraPageTitle"

oraMdField="PAGE_TITLE_LBL"></span>

...

oraSectionEnd

This style is applied to the <td> tags at the end of a "section" (group of elements). It provides some space to separate the section from the following information.
Note: The style must be applied to both <td> tags or the label may be misaligned with the data/input.

...

<tr>

<td class="oraSectionEnd"

oraLabel="zip">

</td>

<td class="oraSectionEnd"

oraField="zip">

</td>

</tr>

...

oraSectionHeader

This style is applied to the <td> tag used to give a heading for a section within the information being displayed. It does not provide spacing before or after itself. The oraSectionStart and oraSectionEnd classes are used for this.
Note: The section header should span both the label column and the data column.

...

<tr>

<td class="oraSectionHeader"

colspan="2"

oraMdField="DATA_SECTION_LBL"></td>

</tr>

...

oraSectionStart

This style is applied to the <td> tags at the start of a "section" (group of elements). It provides some space to separate the section from the previous information (often a section header).
Note: The style must be applied to both <td> tags or the label may be misaligned with the data/input.

...

<tr>

<td class="oraSectionStart"

oraLabel="zip"></td>

<td class="oraSectionStart"

oraField="zip"></td>

</tr>

...

oraTableData

This style is applied to the <col> tag for the data column of the main table (second column). It is used to provide a percentage width for the horizontal space to be used for the information.

...

<colgroup>

<col class="oraLabel

oraTableLabel"/>

<col class="oraNormal

oraTableData"/>

</colgroup>

...

oraTableLabel

This style is applied to the <col> tag for the label column of the main table (first column). It is used to provide a percentage width for the horizontal space to be used for the labels.

...

<colgroup>

<col class="oraLabel

oraTableLabel" />

<col class="oraNormal oraTableData"/>

</colgroup>

...

oraTinyText

This style is typically applied directly beneath an <input> tag to provide information or a hint to the user concerning information relevant to the input. For example, name or address format.

...

<tr>

<td oraLabel="address"></td>

<td>

<input type="text" oraField="address"/>

<div class="oraTinyText"

oraField="addressFormatHint"></div>

</td>

</tr>

...

oraZoneMap

This style is used applied when the UI Map is to be displayed as a zone on a portal.

...

<body class="oraZoneMap">

...

Using OJET

There are some UI maps delivered by the product that use UI widgets provided by Oracle JavaScript Extension Toolkit (OJET). Releases for OJET do not always align with releases of the framework. In addition, there are times when OJET adjusts APIs that the product uses. The framework will attempt to ensure that each release of the product has the latest and greatest version of the OJET libraries. Implementations are discouraged from attempting to use features in OJET that are not used by the product because the product is not necessarily testing those features and is not ensuring that upgrades to the APIs for those features are backward compatible.

Note that the product isolates the references to OJET into a UI map fragment that is included in the maps that use OJET widgets. This is so that changes to future versions of OJET are minimized to a single place. The map is called F1–OJETLIBS. If your implementation wants to use OJET, the recommendation is to use this UI map fragment.

Ensuring Unique Element IDs for UI Maps

The following describes how to modify JavaScript code to ensure the proper rendering of unique element IDs for UI Maps.

The modification is required only for code that renders HTML using a getElementById() (or similar) function to generate list IDs and avoid account verification or related errors.

The following sample snippet contains the necessary modifications:

...

function getElementsFromList(namePrefix) {

var ret = [];

var elements = document.getElementsByTagName("INPUT");

for(var i=0;i<elements.length;i++) {

var elemID = elements[i].id;

if((id) && (id.startsWith(namePrefix + '_')) {

ret.push(elements[i]);

}

}

...

return ret;

Since IDs aren't necessarily unique in generated UI Map IDs, the code shown above ensures uniqueness at runtime by appending an underscore and row number (e.g., myField_1, myField_2) for proper handling by Framework in the rendered HTML, while still allowing you to reference the unmodified IDs contained in the generated UI Map.

A switch in the spl.properties file also permits you to disable the generation of unique IDs for elements in a grid (as described below), though, for standards compliance reasons, it is highly recommended that this switch be left at is default value.

Property Name: spl.runtime.compatibility.uiMapDisableGenerateUniqueHtmlIDs

File Name: spl.properties (under web project in FW)

Default Value: false

Accepted Values: true or false

Description: This property controls the generation of unique IDs for all input elements inside

a list. When this value is set to true it disables the generation of unique IDs, thus

replicating the old behavior. When this property is set to false or this property is missing

it enables the generation of unique IDs, thus enabling the list to be standards-compliant.

Maintaining Managed Content

The Managed Content maintenance object is used to store content such as XSL files used to create vector charts, JavaScript include files, and CSS files. These files may then be maintained in the same manner as the HTML in UI Maps.

The topics in this section describe the Managed Content portal.

Next in This Section

- Managed Content - Main

- Managed Content - Schema

Managed Content - Main

This page is used to define basic information about the content. Open this page using Admin > System > Managed Content.

Description of Page

Enter a unique name for the content in the Managed Content field.

Owner indicates if the content is owned by the base package or by your implementation.

Use Managed Content Type to indicate the type of content, for example, XSLT or JavaScript.

Enter a Description.

Use the Detailed Description to describe in detail how this map is used.

Managed Content - Schema

This page is used to create and maintain the managed content. Open this page using Admin > System > Managed Content and then navigate to the Schema tab.

Description of Page

The General Information zone displays the main attributes of the content. The Editor zone allows you to edit the content.

Data Areas

The data area has no business purpose other than to provide a common schema location for re-used schema structures. It exists solely to help eliminate redundant element declaration. For example, if you have multiple schemas that share a common structure, you can set up a stand-alone data area schema for the common elements and then include it in each of the other schemas.

Be aware that a stand-alone data area can hold elements that are mapped to true fields. For example, you might have 50 different types of field activities and all might share a common set of elements to identify where and when the activity should take place. It would be wise to declare the elements that are common for all in a stand-alone data area and then include it in the 50 field activity business objects.

It's strongly recommended that you take advantage of stand-alone data areas to avoid redundant data definition!

CAUTION:

Dynamic inclusion! When the system renders a schema, all schemas included within it are expanded real-time. This means that any change you make to a data area will take effect immediately within all schemas it is referenced within.

Note:

Schema Tips. The data area page includes a speical Schema Tips zone that provides a link to launch help topics related to the Advanced Schema Topics help in one click.

Data areas may be included in a business object that does not define a full UI map for display or input. Rather, it is using auto-rendering by defining UI attributes in its schema and via UI hints.

Note: View UI Rendering. A context sensitive "View UI Rendering" zone appears on this page. It may be used for a data area that is part of a business object that is using auto-rendering for the display and input maps. The buttons allow you to view the rendered UI for the segment of the schema that is defined by the data area.

Next in This Section

- Defining Data Areas

Defining Data Areas

The topics in this section describe how to maintain Data Areas.

Next in This Section

- Data Area - Main

- Data Area - Schema

Data Area - Main

Use this page to define basic information about a data area. Open this page using Admin > System > Data Area.

Description of Page

Enter a unique Data Area name and Description. Use the Detailed Description to describe what this data area defines in detail. Owner indicates if the data area is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new data area, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Click the View Schema to view the data area's expanded schema definition. Doing this opens the schema viewer window.

Click the View XSD hyperlink to view the business object's expanded schema definition in XSD format.

To extend another data area, reference that data area in the Extended Data Area field. By extending a data area you can add additional elements to a base product data area.

Here's an example of an extended data area:

- The product releases with data area A, which contains elements a, b, and c.

- Your implementation creates data area CM-A, which contains element z, and references data area A as the extended data area.

- At run time, everywhere data area A is included it will contain elements a, b, c, and z.

Where Used

Follow this link to open the data dictionary to view the tables that reference F1_DATA_AREA.

Data Area - Schema

Use this page to maintain a Data Area's schema and to see where the data area is used in the system. Open this page using Admin > System > Data Area and then navigate to the Schema tab.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays the main attributes of the data area.

The Schema Designer zone allows you to edit the data area's schema. The purpose of the schema is to describe the structure and elements of the data area.

Fastpath: Refer to Schema Syntax and UI Hint syntax for a complete list of the XML nodes and attributes available to you when you construct a schema. Also note that the Schema Tips zone in the dashboard provides links to launch these help topics directly.

Note: View UI Rendering. A context sensitive "View UI Rendering" zone is associated with this page. The zone is useful for data areas that are to be included in business objects that define the user interface detail using schema attributes and UI Hints. The buttons allow you to view the automatically rendered display and input maps.

The Schema Usage Tree zone summarizes all cross-references to this schema. These may be other schemas, scripts, and web services. For each type of referencing entity, the tree displays a summary node showing a total count of referencing items. The summary node appears if at least one referencing item exists. Expand the node to list the referencing items and use their description to navigate to their corresponding pages.

Advanced Schema Topics

The topics in this section describe some advanced information related to schemas used for business objects, business services, service scripts and UI maps.

Next in This Section

- Schema Nodes and Attributes

- UI Hint Syntax

- Schema Designer

- Schema Viewer

Schema Nodes and Attributes

For business object definition, the purpose of the schema is to create a link between the schema and a maintenance object. For business service definition you are specifying the link between the schema and a service (either a general service, search service, or a maintenance object service). For service script definition, you are defining the API for passing information to and from the script. The following documentation is a complete list of the XML nodes and attributes available to you when you construct a schema.

Contents

The Four Element Types

The Data Type of a Field Element

Referencing Other Elements

Standard Time Considerations

The Mapping Attributes

Descriptive Attributes

Schema Constants

Defaulting and System Variables

The Flattening Nodes and Attributes

Search Zone

Extend Security for Service Script

Overriding Action for a Business Service

Specifying searchBy for a Search Service

Including Other Schemas

Compatibility Attributes

The Four Element Types

A schema element can be one of four different structure types. Note that there are two classes of element types: the structural nodes group and list, and the data containing nodes of field and raw.

Mnemonic

Valid Values

Description

Examples

type=

"field"

The field type is the default type for any element not explicitly labeled as something other than a field. Therefore, you virtually never have to explicitly label an element as a field. Note that a field element, unlike group or list, will contain information in its nodes - rather than other nodes.

"group"

The group element is typically a structural element of the schema only, in which case it has no mapping.

Note that when grouping several elements that are all used to map an XML structure of a CLOB / XML field of a business object driven record, the mapping may be at the group level.

Example where a group is used to create a structure

<schema>

<input type="group"

<userId/>

</input>

<output type="group">

<firstName/>

<lastName/>

</output>

</schema>

Example where the group includes the mapping:

<parameters type="group"

mapXML="BO_DATA_AREA" mdField=

"F1_TODOSUMEMAIL_PARM_LBL"/>

<numberOfDays

mdField="F1_NBR_DAYS"

required="true"/>

<frequency

mdField="F1_FREQUENCY"/>

"list"

The list node is structural node like the group node. The only difference is that the list structure has the ability to repeat multiple times in an XML document.

Example of a schema with a list:

<schema>

<statesList type="list">

<state isPrimeKey="true"/>

<description/>

</statesList>

</schema>

Example of a schema with a list:

<xml>

<statesList>

<state>AK</state>

<description>Alaska</description>

</statesList>

<statesList>

<state>AL</state>

<description>Alabama</description>

</statesList>

...

</xml>

"raw"

The raw data type is used to capture a chunk of raw text that doesn't have any inherent structure associated with it.

<sendDetail type="raw" />

Example of an XML instance for the above schema:

<sendDetail>

<messageInfo>

<senderAddress>123 W. Main St,    Ontario, CA

</senderAddress>

<corpZone>3A</corpZone>

</messageInfo>

</sendDetail>

The Data Type of a Field Element

Of the four different element types, only a field can have a data type.

Mnemonic

Valid Values

Description

Examples

dataType=

"string"

By default, a field element is a string. Therefore, there is no requirement to specify the string data type.

<schema>

<custName dataType="string"/>

</schema>

"number"

Defines an element that is a number.

Note: UI hints include a setting to Suppress Automatic Number Formatting.

Note: Use currencyRef attribute for auto-display of currency symbol that is associated with the referenced currency code. The currency decimal positions are ignored by this formatting allowing you to display a currency symbol for a unit rate with many decimals.

Examples

<schema>

<count dataType="number"/>

</schema>

<schema>

<taxRate dataType="number"

currencyRef="currency"/>

</schema>

"money"
Optional additional attributes

currencyRef=
"element name"

Defines an element that represents a monetary amount.

The currency reference is optional and if left blank the installation currency will be used. Automatic formatting and validation to be applied based on the currency. For example, the currency symbol will be shown when auto-rendering. In addition, the number of decimal places must not exceed the valid number defined for the currency.

Note: Refer to Referencing Other Elements for supported syntax for referring to other elements.

<schema>

<currency default="USD"

suppress="true"/>

<balance dataType="money"

currencyRef="currency"/>

</schema>

"lookup"
Required additional attribute

lookup=
"field name"

Defines an element that has valid values defined using a lookup. The lookup field is required.

<schema>

<status dataType="lookup"

lookup="STATUS_FLG"/>

</schema>

"lookupBO"
Required additional attribute

lookupBO=
"bo name"

Defines an element that has valid values defined using an extendable lookup. The extendable lookup's business object is required.

<schema>

<category dataType="lookupBO"

lookupBO="CM-BusinessCategory"/>

</schema>

"boolean"

Defines an element that has values of "Y" and "N".

<schema>

<allowsEdit dataType="boolean"/>

</schema>

"date"

Defines an element that represents a date.

<schema>

<startDate dataType="date"/>

</schema>

"dateTime"

Defines an element that represents a date and time.

Note: Refer to Standard Time Considerations for additional configuration available for date / time fields that represent standard time.

<schema>

<startDateTime

dataType="dateTime"/>

</schema>

"time"

Defines an element that represents a time.

<schema>

<startTime dataType="time"/>

</schema>

"uri"

Defines an element captures a URI. Elements defined with this type enable the support for URI Whitelist and Substitution as described in Referencing URIs .

<schema>

<exportDirectory dataType="uri"/>

</schema>

Referencing Other Elements

There are several attributes that allow for a reference to another element in the same schema. The supported syntax of the XPath reference is the same in every case. This section provides examples using the default reference attribute (defaultRef).

Reference a sibling element:

<schema>

<id mapField="ACCT_ID" required="true"/>

<altId defaultRef="id" required="true"/>

</schema>

Reference an element in a higher group:

<schema>

<id mapField="ACCT_ID" required="true"/>

<msgInfo type="group" mapXML="XML_FIELD">

<altId defaultRef="../id" required="true"/>

</msgInfo>

</schema>

Reference an element in a lower group:

<schema>

<id mapField="ACCT_ID" defaultRef="msgInfo/altId" required="true"/>

<msgInfo type="group" mapXML="XML_FIELD">

<altId required="true"/>

</msgInfo>

</schema>

Reference an element in another group:

<schema>

<acctInfo type="group">

<id mapField="ACCT_ID" required="true"/>

</acctInfo>

<msgInfo type="group" mapXML="XML_FIELD">

<altId defaultRef="../acctInfo/altId" required="true"/>

</msgInfo>

</schema>

Standard Time Considerations

Most date / time fields represent "legal" time such that if a time zone changes their clocks for winter and summer time, the date / time field captures the current observed time. However, some date / time fields should always be captured in standard time to avoid confusion / ambiguity. A good example is a date and time related to detailed interval data.

When defining an element with dataType="dateTime", you may optionally configure stdTime="true" indicating that data captured in the element always represents standard time in the 'base' time zone. The 'base' time zone is specified on the Installation options.

Note: If an element is mapped to a table / field with a Standard Time Type of Physical, then stdTime="true" is implied. Refer to Table / Field for more information.

Example:

<schema>

<startTime dataType="Time" stdTime="true"/>

</schema>

If the time zone that represents the date / time field is not the installation time zone, use the optional setting stdTimeRef="XPath to time zone element" on a date / time element to indicate that the element represents standard time and indicates the time zone to use. Refer to Referencing Other Elements for supported syntax for referring to other elements. .

Example:

<schema>

<alternateTimeZone fkRef="F1-TZONE" suppress="true"/>

<startDateTime dataType="dateTime" stdTimeRef="alternateTimeZone"/>

</schema>

Note: If an element is mapped to a table / field with a Standard Time Type of Referenced, then stdTime="XPath" is implied. Refer to Table / Field for more information.

Note: When schema elements are captured in standard time the UI map supports HTML notation to automatically display the data applying a daylight savings time / summer time correction. Refer to the HTML attribute oraType="dateTime; stdTime:true" for more information.

There may be cases where the date / time is captured as standard time in one time zone, but should be displayed using a different time zone. In this case, the attribute displayRef="XPath" may be used in addition to the appropriate attribute that identifies the time zone that the data is capture in. Refer to Referencing Other Elements for supported syntax.

<schema>

<displayTimeZone fkRef="F1-TZONE" suppress="true"/>

<startDateTime dataType="dateTime" stdTime="true" displayRef="displayTimeZone"/>

</schema>

The Mapping Attributes

When constructing your schema, you can choose from one of the following mapping attributes.

Mnemonic

Valid Values

Description

Examples

mapField=

"field name"

In the case of a business object, the mapField attribute is used to identify the database column the element is related to. For business service schemas, the mapField= attribute is used to link a schema element with a service element.

<schema>

<factId

mapField="FACT_ID"/>

</schema>

mapChild=

"table name"

The mapChild attribute is used only for business object mapping. It is used in two ways:

- First, to create a list in the business object that corresponds to a child table of an MO.

- Second, you can use mapChild to identify the child table a flattened field lives in. For more information on flattening, refer to flattening section below.

Example of a list within a child table in a BO:
<persons type="list"

mapChild="CI_ACCT_PER"

<personId mapField="PER_ID"/>

</persons>

mapList=

"list name"

The mapList attribute is used only for business service mapping. It is used in two ways:

- First, to create a list in the business service that corresponds to a list in the service.

- Second, you can use mapList to identify the list that a flattened field lives in. For more information on flattening, refer to flattening section below.

Example of a list within a business service:
<selectList type="list"

mapList="DE"

<value mapField="COL_VALUE">

<row mapList="DE_VAL">

<SEQNO is="2"/>

</row>

</value>

</selectList>

mapXML=

"field name"

The mapXML attribute is typically used to map XML structures into a large character / XML field of the service. Note that when you use mapXML to map either a list or group structure (type="list" or type="group") you don't have to map all the child elements within the structure. It is also possible to map list elements to a large character field associated with the list child.

<enrollmentRequest type="group"

mapXML="CASE_CLOB">

<messageID/>

<sender/>

</enrollmentRequest>

<enrollmentKey

mapXML="CASE_CLOB"/>

<enrollmentInfo type="list"

mapChild="CI_CASE_CHILD">

<sequence

mapField="CHILD_SEQ"/>

<name

mapXML="CASE_CHILD_CLOB"/>

<value

mapXML="CASE_CHILD_CLOB"/>

</enrollmentInfo>

isPrimeKey=

"true"

You must specify a primary key for a list defined within a mapped XML element (type="list" mapXML="CLOB"). The primary key is used by the framework to determine whether a list element add, update or delete is required during a business object update.

Note: You do not need to specify the prime key for a business object list mapped to maintenance object list. When a physical list is mapped, the prime key is derived from existing physical meta-data.

<questionnaire

type="list" mapXML="CASE_CLOB">

<question

isPrimeKey="true"/>

<answer/>

</questionnaire>

orderBy=

"XPath asc|desc, XPath asc|desc"

By default, a list defined within a mapped XML element (type="list" mapXML="CLOB") is sorted by the first element of the list. A different sort order may be specified using the orderBy attribute. The attribute value is a comma separated list of field XPaths (relative to the list element) with an optional sort order (ascending is the default).

Note: This is only available for lists mapped as XML within business objects.

<questionnaire type="list"

orderBy="page/section,

page/sequence"

mapXML="CASE_CLOB">

<question isPrimeKey="true"/>

<answer/>

<page type="group">

<section/>

<sequence/>

</page>

</questionnaire>

Descriptive Attributes

The following attributes can be used to describe a schema element and provide additional configuration related to the element. Typically, these attributes are useful for field elements only.

Mnemonic

Valid Values

Description

Examples

<!-- comment -->

Use this to add a comment to a schema by using special open and close characters: <!-- and -->.

<schema>

<!-- This schema is used to

capture business information

only, please refer to the

'HUMAN' BO for person

information -->

</schema>

description=

"text"

The description of an element may be used to provide an internal description of the element to help a reader of the schema to understand the business reason for the element.

<schema>

<active type="boolean"

description="active account"

label="Active"/>

</schema>

label=

"text"

The label of an element is meant to be a short bit of verbiage that would typically precede the element in a user interface.

<schema>

<active type="boolean"

description="active account"

label="Active"/>

</schema>

required=

"true"

Used to require the existence of an element during object interaction.

Note: For included schemas, the required="true" attribute is not processed on business object and business service schemas when they are included within a service script schema. This is to support the ability of the service script to populate required elements before an embedded business object or business service is invoked from the service script.

<schema>

<logDate mapField="LOG_DT"

default="%CurrentDate"

required="true"

private="true"

</schema>

mdField=

"field code"

The meta-data field attribute is used to associate an element with a field's metadata. The field defines data type, as well as its label and help text. If you link an element with a meta-data field, you don't need to specify any of these attributes.

Note: For a business object schema, the mapField attribute is used to derive the data type and label. An mdField attribute may be provided to override these attributes, if needed. If the element is mapped to an XML column, the mdField is needed to provide the appropriate data type and label.

<schema>

<active

mdField="CM_ACTIVE_SW"/>

</schema>

fkRef=

"FK Reference Code"

If the element is a foreign key, defining its FK Reference will enable framework validation of the element during schema interaction and automatically provide descriptions and navigation capability.

<schema>

<person fkRef="PER"

mapField="CHAR_VAL_FK1">

<row mapChild="CI_SA_CHAR">

<CHAR_TYPE_CD is="PER"/>

</row>

</person>

</schema>

private=

"true"

Marking an element as private will prevent it from being exposed in schema interaction.

Note: A private element requires a default.

<schema>

<type mdField="SA_TYPE_CD"

default="E1" private="true"/>

</schema>

suppress=

"true"

This setting prevents an element from appearing in automatically generated user interfaces.

Note: This attribute can be specified on a group, in which case all elements of the group will be suppressed.

<schema>

<ls mdField="LIFE_SUPPORT_FLG"

default="N" suppress="true"/<

</schema>

"blank"

This setting means that automatic UI rendering will hide the element if its value is blank. The element will still be modifiable on the input map whether blank or not.

<schema>

<email mdField="EMAIL"

suppress="blank"/>

</schema>

"input"

This setting means that automatic UI rendering will suppress the element for input, although it may still be displayed if it is not blank.

Note: Elements marked as suppress="input" will behave as with suppress="blank". If the value is blank, no value will be displayed on either the display or input map. If the element's value is present, then the element will be displayed on both the display and input map.

<schema>

<email mdField="EMAIL"

suppress="input"/>

</schema>

noAudit=

"true"

This setting prevents an element from appearing as a changed element in the business object's audit plug-in spot. If specified on a group or list node it applies to the whole node. You cannot specify it on the schema root node, only on schema elements.

Note: This attribute is only applicable to business object schemas.

<schema>

...

<version mapField="VERSION_NBR"

noAudit="true"/>

...

<workFields type="group"

noAudit="true"

<lastProcessedId/>

<lastProcessedTime/>

</workFields>

</schema>

Schema Constants

There are some product owned schemas where the design warrants a value to be defaulted in the schema, but where the value is implementation specific and therefore cannot be defined by the product. For these situations, the product may use a technique called a schema constant. The design of the schema will include a declared constant. At implementation time, a configuration task will include defining the appropriate value for the constant.

For example, imagine the product delivers an algorithm that will create an outbound message when a certain condition occurs. The outbound message type to use must be configured by the implementation. To use a schema constant to define the outbound message type, the base product will configure the following:

- An option type lookup value for the lookup F1CN_OPT_TYP_FLG is defined. For example, M202 - Activity Completion Outbound Message Type with a Java Value Name of outmsgCompletion

- The base schema that is used to create the "complete activity" outbound message references the schema constant using the Java Value Name of the option type's lookup value

...

<outboundMessageType mapField="OUTMSG_TYPE_CD" default="%Constant(outmsgCompletion)"/>

...

At implementation time, the administrative users must configure the appropriate outbound message type for "activity completion". Then, navigate to Feature Configuration, choose the Schema Constants feature type, choose the option type Activity Completion Outbound Message Type and enter the newly created outbound message type in the option value.

Schema constants may also be used in the flattening syntax to define the row elements required for flattening.

Defaulting and System Variables

The default node can be used to default values into field elements as well as the row elements required for flattening . You can default a field to a constant or to one of several system variables.

Note:

When a field is displayed on the user interface in Add mode, the default value defined in the schema is shown. In addition, the server logic uses the default value if no value is supplied and the element is marked as required or suppressed.

Mnemonic

Valid Values

Description

Examples

default=

"value"

Use this attribute to default an element to a specified value. The values that are valid depend on the dataType setting.

<schema>

<perType mapField="PER_OR_BUS_FLG"

default="P" required="true"/>

</schema>

<schema>

<frequency dataType="number"

default="1" required="true"/>

</schema>

"%CurrentDate"

Used to default the element to the current date. This is only applicable to date elements.

<schema>

<logDate mapField="LOG_DT"

default="%CurrentDate" required="true"/>

</schema>

"%CurrentDateTime"

Used to default the element to the current date / time. This is only applicable to date / time elements.

<schema>

<logDateTime mapField="LOG_DTTM"

default="%CurrentDateTime"

required="true"/>

</schema>

"%StandardDateTime"

Used to default the standard date and time. The standard date and time is identical to the current date and time, unless daylight savings time / summer time is in effect for the base time zone. This may be used with the stdTime attribute.
Note: Refer to Standard Time Considerations for more information.

<schema>

<startDateTime mapField="START_DTTM"

default="%StandardDateTime"

required="true"/>

</schema>

"%ProcessDate"

You can default the process date. The process date differs from the current date because the process date will remain constant throughout the duration of the process being executed. The current date will reflect the actual date of processing. This is similar to the batch business date that is a standard batch parameter.

<schema>

<billDate mapField="BILL_DT"

default="%ProcessDate"

required="true"/>

</schema>

"%ProcessDateTime"

This is similar to "%ProcessDate" but for date / time fields.

<schema>

<calcDateTime mapField="CALC_DTTM"

default="%ProcessDateTime"

required="true"/>

</schema>

"%CurrentUser"

Used to default the element to the current user.

<schema>

<logUser mapField="LOG_USER"

default="%CurrentUser"

required="true"/>

</schema>

"%CurrentUserTimeZone"

Used to default the element to the current user's time zone. If the current user's time zone is not found, the installation time zone is used.

<schema>

<timeZone

default="%CurrentUserTimeZone"

required="true"/>

</schema>

"%CurrentUserLanguage"

Used to default the element to the current user's language.

<schema>

<custLanguage mapField="CUST_LANG"

default="%CurrentUserLanguage"

required="true"/>

</schema>

"%InstallationCurrency"

Used to default the currency from the installation record.

<schema>

<currency mapField="CURRENCY_CODE"

default="%InstallationCurrency"

required="true"/>

</schema>

"%InstallationCountry"

You can default the country from installation record.

<schema>

<country mapField="COUNTRY"

default="%InstallationCountry"

required="true"/>

</schema>

"%InstallationLanguage"

You can default the language from the installation record.

<schema>

<language mapField="LANGUAGE"

default="%InstallationLanguage"

required="true"/>

</schema>

"%Constant( )"

You can default an element value using a schema constant.

The following is an example of a schema constant used as a default value, where the Java Value Name of the Lookup Value is 'customerLanguage'.
<language mapField="CUSTOMER_LANG"

default="%Constant(customerLanguage)"

required="true"/>

"%Context( )"

You can default a value contained in a context variable.
Warning: Context variables must be initialized within a server script before the schema context default can be applied. Refer to Context Variables for more information.

An example of a context variable used as a default value:
<source mapField="PER_ID"

default="%Context(source)"

required="true"/>

Note: When defining a context variable in scripting, it should be prefixed with $$. When referring to the variable in the %Context( ) syntax, the prefix is not included.

defaultRef=

"XPath"

Use this attribute to default the value of one element to the value of another one.

Refer to Referencing Other Elements for supported syntax for referring to other elements.

The Flattening Nodes and Attributes

The term "flattening" is used to describe the act of defining one or more single elements for a schema that are actually part of a list within the maintenance object. Flattening is possible if there are other attributes of the list that can be defined to uniquely describe the element or elements. A common use case for flattening is a characteristic. Rather than defining the characteristics of an object using a collection where the user must choose the characteristic type and then define the value, the characteristics are defined as actual elements with the appropriate label already displayed. This technique enables the designer of the schema and the user interface to display each separate characteristic in the logical place in the user interface rather than all lumped together.

Note: A flattened element represents a unique row in the database. This row is inserted when the flattened values are created. The row is updated when any of the flattened values are changed. The row is deleted when all the flattened values are removed. The behavior of effective dated elements is slightly different - please see Flattening an Effective Dated List.

Note: The flattening feature can also be used to define a list, see Flattened List.

Identifying the List or Child Table

When flattening a child table, the row node is required to identify the list / child table that the element comes from. Within the row node, at least one element must be defined with an is= definition that ensures that the element is a unique row in the database. It may also define elements or fields in the row that are suppressed and are populated using default value configuration.

- For a business object, the row node defines the child table the flattened field belongs to.

The syntax is <row mapChild="table name">. This example is for the list of persons for an account in the customer care and billing product. One person may be marked as the "main" person. This illustrates how to define an explicit element for the main person ID to simplify references to that field. It is part of the CI_ACCT_PER child table. What makes it unique is that the MAIN_CUST_SW is true (and only one row may have that value)

<custId mapField="PER_ID" mdField="CM-MainCust">

<row mapChild="CI_ACCT_PER">

<MAIN_CUST_SW is="true" />

<ACCT_REL_TYPE_CD default="MAIN" />

</row>

</custId>

Note: The above example illustrates that the row node may also define elements within the list that are suppressed and assigned a default value. This syntax is never used to identify a particular row. Note that a default value can either be a literal string, or a system variable.

- For a business service, the row node identifies the list name the flattened field belongs to.

The syntax is <row mapList="list name">. This example shows two entries from a list being flattened to a field value and description.

<selectList type="list" mapList="DE">

<value mapField="COL_VALUE">

<row mapList="DE_VAL">

<SEQNO is="2"/>

</row>

</value>

<description mapField="COL_VALUE">

<row mapList="DE_VAL">

<SEQNO is="3"/>

</row>

</description>

</selectList>

Uniquely Identifying the Flattened Field or List

The is= syntax within a row or rowFilter element is used to uniquely identify the row.

Mnemonic

Valid Values

Description

Examples

is=

"value"

Use this attribute to reference a value directly.

<tdTypeCd

mapField="CHAR_VAL_FK1">

<row

mapChild="F1_EXT_LOOKUP_VAL_CHAR">

<CHAR_TYPE_CD

is="CM-TD-TYPE"/>

</row>

</tdTypeCd>

"%Constant( )"

You can configure a flattened element using a schema constant. During a service interaction the value of the schema constant will be used to identify the flattened element in its child row.

An example of a schema constant used in flattening syntax where the Java Value Name of the Lookup field value is 'cmRate'.

<unitRate mapField="CHAR_VAL"

dataType="number">

<row mapChild=

"F1_EXT_LOOKUP_VAL_CHAR">

<CHAR_TYPE is

="%Constant(cmRate)"/>

</row>

</unitRate>

"%n"

The %n substitution value is used to reference a relative list instance. A relative list instance is typically used to configure a flattened element for a child table keyed by sequence number. The value of n should be a positive integer value. During a business object read interaction the relative list instance (position) specified by the integer will be returned.

An example with a relative list instance - where the first instance of the row is returned.
<schema>

<mainPhone mapField="PHONE">

<row mapChild="CI_PER_PHONE">

<PHONE_TYPE_CD

is="%Constant(mainPhoneType)"/>

<SEQ_NUMis="%1"/>

</row>

</mainPhone>

</schema>

Fastpath: Additional values for is= are used when Flattening an Effective Dated List. Refer to that section for more information.

Flattening a Pre-defined Characteristic Type

If the flattened field is in a characteristic collection and the characteristic type is a predefined characteristic, automatic UI rendering will generate a dropdown for the list of valid values. For example, the schema below will generate a dropdown for the Usage element showing the valid values of the Status Reason Usage (F1-SRUSG) characteristic type.

<usage mdField="STATUS_RSN_USAGE" mapField="CHAR_VAL">

<row mapChild="F1_BUS_OBJ_STATUS_RSN_CHAR">

<CHAR_TYPE_CD is="F1-SRUSG"/>

<SEQ_NUM is="1"/>

</row>

</usage>

Defining Multiple Elements from the List

When attempting to include multiple columns from the same list, the system provide shorthand notation for copying the flattening rules defined on another element so that the flattening rules do not need to be repeated. To do this, the row node includes the rowRef attribute and it indicates the other element name that defines the mapping information. The following example illustrates flattening the fields Customer ID and Receives Copy of Bill from the same list of Persons for an Account (where the MAIN_CUST_SW is true ).

<custId mapField="PER_ID">

<row mapChild="CI_ACCT_PER">

<MAIN_CUST_SW is="true" />

<ACCT_REL_TYPE_CD default="MAIN" />

</row>

</custId>

<copyBill mapField="RECEIVE_COPY_SW" rowRef="custId"/>

Note that the above notation also illustrates that the rowRef may be defined directly in the element's attribute definition.

Note: Refer to Referencing Other Elements for supported syntax for referring to other elements.

Flattening Two Layers Deep

If your maintenance object or service has nested lists two layers deep, the system supports flattening and element within a flattened element. This technique also uses the rowRef attribute. The flattening of the second level refers to the flattened element of the first level. The following example illustrates flattening a characteristic into an element called legalContact for the "main" customer. Notice that the legalContact element has two row nodes: one to refer to the flattening information for its parent record and one to define its child table

<custId mapField="PER_ID">

<row mapChild="CI_ACCT_PER">

<MAIN_CUST_SW is="true" />

<ACCT_REL_TYPE_CD default="MAIN" />

</row>

</custId>

<legalContact mapField="CHAR_VAL_FK1">

<row rowRef="custId">

<row mapChild="CI_ACCT_PER_CHAR" >

<CHAR_TYPE_CD is="LEGAL" />

</row>

</row>

</legalContact>

Note that the above notation also illustrates that the rowRef may be defined as an attribute of a row node rather than directly in the element's attribute definition.

Defining a Flattened List

There are times that a list or child table supports multiple values of the same "type" and these should be presented as a list. To continue with the example above, the list of persons for an account may identify one person as the "main" person. This person has been flattened to a single element (with the account relationship type defaulted and suppressed). To maintain the other persons related to an account, you can define a list where each row captures the Person Id and the Account Relationship Type.

Rather than a row node, the flattened list is configured with a rowFilter element. The following schema illustrates the described example. The list node defines the child table. The rowFilter includes the criteria that identify the rows within the table to include. The elements of the list are defined within the list node outside the rowFilter element.

<custId mapField="PER_ID">

<row mapChild="CI_ACCT_PER">

<MAIN_CUST_SW is="true" />

<ACCT_REL_TYPE_CD default="MAIN" />

</row>

</custId>

<miscPersons type="list" mapChild="CI_ACCT_PER">

<rowFilter>

<MAIN_CUST_SW is="false" />

</rowFilter>

<relType mapField="ACCT_REL_TYPE_CD"/>

<personId mapField="PER_ID"/>

</custId>

Note that the system will validate that if a schema contains flattened single elements and flattened lists from the same child table, the criteria that defines what makes them unique must be analogous.

Flattening an Effective Dated List

There are some lists in the application that are effective dated (and still others that have effective date and time). For example, there are some effective dated characteristic collections. In these collection, the design is to capture a single value for a characteristic type that may change over time. It is not meant to support multiple characteristic values in effect at the same time. The following highlights some information regarding effective dated characteristic functionality:

- The most recent dated row is returned when invoking a BO for read.

- No new row added when all of the values are unchanged on a change to the BO.

- The flattened row value is updated when any of the flattened values are changed and the most recent date is equal to the current date (or the referenced effective date);

- A new row value is inserted when any of the flattened values are changed and the most recent date is different than the current date (or the referenced effective date);

Note: Refer to Referencing Other Elements for supported syntax for referring to other elements.

When flattening an effective dated list, the date column must include information regarding the date to use. The following table highlights the possible values.

Mnemonic

Valid Values

Description

Examples

is=

"%effectiveDate"

Use this configuration to indicate that current date should be used for processing. Any value added or updated using this schema will be for the current date.
With this option, if the maintenance object allows for the characteristic value to be blank, then setting the flattened value to blank during the BO update will result in updating the existing record with an empty value, or adding a new row with an empty value in case the current date effective dated record is not found.

<schema>

<price mapField="CHAR_VAL"

dataType="number">

<row

mapChild="CI_SA_CHAR">

<CHAR_TYPE is="PRICE"/>

<EFFDT

is="%effectiveDate"/>

</row>

</price>

</schema>

"%effectiveDate( )"

Use this configuration to indicate that the date to use the value of another element.
Note: Refer to Referencing Other Elements for supported syntax for referring to other elements.

<schema>

<price mapField="CHAR_VAL"

dataType="number" required="true">

<row mapChild="CI_SA_CHAR">

<CHAR_TYPE is="PRICE"/>

<EFFDT

is="%effectiveDate(priceEdate)" />

</row>

</price>

<priceEdate mapField="EFFDT"

rowRef="price"/>

</schema>

"%effectiveDateTime"

Use this configuration to indicate that current date /time should be used for processing. Any value added or updated using this schema will be for the current date / time.

<schema>

<price mapField="CHAR_VAL"

dataType="number">

<row mapChild="RATE_CHAR">

<CHAR_TYPE is="PRICE"/>

<EFFDT

is="%effectiveDateTime" />

</row>

</price>

</schema>

"%effectiveDateTime( )"

Use this configuration to indicate that the date / time to use the value of another element.
Note: Refer to Referencing Other Elements for supported syntax for referring to other elements.

<schema>

<price mapField="CHAR_VAL"

dataType="number">

<row mapChild="RATE_CHAR">

<CHAR_TYPE is="PRICE"/>

<EFFDTTM

is="%effectiveDateTime(priceEdatetime)"/>

</row>

</price>

<priceEdatetime mapField="EFFDTTM"

rowRef="price"/>

</schema>

Search Zone

A UI Map schema element can be configured to enable an automatic search dialog when the schema is included within a maintenance UI map.

Note: Please note that an fkRef can be configured with a search zone. If a schema element has an fkRef but no explicit search attributes (as described here) then the fkRef search information will be used in the UI map. In other words, if the schema element already has an fkRef, then these explicit search attributes in the schema are only used to override the fkRef search information.

Note: Refer to the UI Map Attributes and Functions for more information on search zone configuration.

search="search zone"

The search attribute can be used within a UI map schema and is used to automatically generate the oraSearch UI map attribute. The search zone is an explorer zone configured as a search.

<person fkRef="PER" search="C1_PSRCH"/>

searchField="search field:element|'literal';"

The searchField attribute can only be used in conjunction with the search attribute. The searchField attribute is used to build the oraSearchField UI map attribute. The searchField value is used to populate a search zone filter with an initial value when the search zone is launched. The initial value can be a literal also. The searchField value is used to match to the filter mnemonic also named searchField.

Search field: element|'literal'. The search field represents the search zone filter to populate on launch. The element is the map's schema element used to populate the filter. The element is optional, if left blank, it will default to the element that this attribute is specified on. The searchField also takes 'literal' as input value

Note: Multiple filters can be populated within the search zone at launch, but multiple search field pairs must be constructed within the attribute value. The value specified here will be used to directly build the HTML attribute oraSearchField within the UI map where this schema is specified.

Note: Note that the element reference is relative. Refer to Referencing Other Elements for supported syntax for referring to other elements.

<person fkRef="PER" search="C1_PSRCH" searchField="PERSON; PER_TYPE:personType;"/>

searchOut="search field:element;"

The searchOut attribute can only be used in conjunction with the search attribute. The searchOut attribute is used to build the oraSearchOut UI map attribute. The searchOut value is used to capture a selected value from the search zone and move it to a UI map element. The searchOut value specified should match the ELEMENT_NAME mnemonic within the search result zone parameter.

Search field: element. The search field represents the search zone result brought back to the UI map. The element is the map's schema element to be populated. The element is optional, if left blank, it will default to the element that this attribute is specified on.

Note: Multiple elements can be populated as a result of search zone selection, but multiple search field pairs must be constructed within the attribute value. The value specified here will be used to directly build the HTML attribute oraSearchOut within the UI map where this schema is specified.

Note: Note that the element reference is relative. Refer to Referencing Other Elements for supported syntax for referring to other elements.

<person fkRef="PER" search="C1_PSRCH" searchField="PER_ID"

searchOut="PER_ID;PRIMARY_PHONE:personPhone;"/>

Extend Security for Service Script

Application service security will be enforced when either a business object or a service script is invoked from a BPA script or a UI map, but not from a service script. If you want security to be enforced when the business object or a service script is invoked from a service script, you must add the following attribute to the service script's schema.

appSecurity="true"

The appSecurity attribute is only available for service script schemas. If specified, any business object or service script directly invoked by the service script will have their application service evaluated for access.

<schema appSecurity="true">

...

</schema>

Overriding Action for a Business Service

If you want to invoke a business service with an action other than 'read', you need to specify the action attribute on the primary node business service schema.

pageAction="add, change, delete"

The action attribute is used to override the default action of read on a business service schema. Valid values are:

- add

- update (only allowed for maintenance object service)

- change (not allowed for maintenance object service)

- delete

- read (this is the default action if no pageAction specified)

Example:

<schema pageAction="change">

<parm type="group">

<ele1/>

<ele2/>

</parm>

</schema>

Specifying searchBy for a Search Service

If you want to invoke a search service then you must explicitly specify the searchBy attribute appropriate for the elements mapped in the schema.

searchBy="MAIN"

The value values of the searchBy attribute can be found by viewing the XML schema linked to the business service, use the View XML URL. Typical values are:

- MAIN

- ALT

- ALT2

- ALT3

- etc.

<schema searchBy="MAIN">

<AccountID mapField="ACCT_ID"/>

<Results type="list">

<AccountID mapField="ACCT_ID"/>

</Results>

</schema>

Including Other Schemas

There are no limitations on your ability to include a schema into another schema - all types can be included in all other types. Nested includes are also allowed - and at present there is no limitation on the depth of the nesting.

Including a schema requires two parts:

1. The include node

2. The name attribute

The following table highlights the supported include statements.

Mnemonic

Description

Examples

<includeBO name=" "/>

Including a business object schema into another schema is allowed.

Note that the mapping rules of a business object or business service schema may or may not make sense in the context of the parent schema. Include other schemas at your own risk. However, a very useful aspect of XML processing is that the framework ignores non-pertinent attributes. In other words, it will not hurt to have mapping attributes included into a script schema.

<schema>

<cust type="group">

<includeBO name="C1-Person"/>

</cust>

<spouse type="group">

<includeBO name="C1-Person"/>

</spouse>

</schema>

<includeBS name=" "/>

Used to include a business service schema.

<schema>

<includeBS name="F1-ReadMOLog"/>

</schema>

<includeDA name=" "/>

Used to include a data area schema.

<schema>

<includeDA

name="F1CommonSchemaFieldData"/>

</schema>

<includeMP name=" "/>

Used to include a UI map schema.

<schema>

<includeMP

name="F1-DisplayRecordActions"/>

</schema>

<includeSS name=" "/>

Used to include a service script schema.

<schema>

<includeSS name="F1-ActShowZn"/>

</schema>

Compatibility Attributes

These attributes were added as part of upgrades from pervious versions of the Framework.

fwRel="2"

This attribute has been added to schemas created in Framework 2 as part of a Framework 4 upgrade. New schemas will not need this attribute. It is not advisable to modify this attribute without understanding the following behavior differences as improper changes could result in errors:

Note: Schemas created in Framework 2 with the fwRel="2" attribute will store any XML mapped fields under groups as top-level XML elements in the mapXML field. This means that if two or more fields, in different group structures, were to have the same field name, their storage would conflict with one another resulting in errors. The new behavior, without the fwRel="2" attribute, will preserve the group structure and avoid the conflicts.

<schema fwRel="2"

...

</schema>

UI Hint Syntax

Contents

Working Examples

Technical Notes

Format an Input Map Title

Create a Section

Include a Map Fragment

Build Dropdown

Conditionally Hide Elements

Conditionally Protect Elements

Trigger Dependent Behavior

Control Rendering Target

Generate a Text Area

Modify FK Reference Defaults

Suppress Automatic Number Formatting

Auto Capitalize the Input Data

Working Examples

For working examples of uiHint functionality, refer to the following business objects:

BOs with User Assigned Keys

The following examples illustrate the patterns used to enable uiHints on an object with a user specified key.

- F1-OutcomeStyleLookup. This extendable lookup BO does not require state transition, but does allow duplicate and delete actions.

- F1-TodoSumEmailTyp. This request type illustrates the hints required to support state transition on a display map.

- F1-WebSvc. This web service BO is a good example for management of complex JavaScript requirements. Both display and input maps have functionality that requires specialized javascript.

BO with System Generated Key

The following example illustrates the pattern used to enable uiHints on an object with a system generated key.

- F1-GenericAttachment. This attachment BO has a system assigned key, which entails the following special handling:

- F1-AttachmentMain. This is the main section data area contains the elements common to all attachments, including the key, bo, and version. Because this data area is used to define the main section of the generated maps, the main section of the map can be extended by an implementation via data area extension functionality.

- F1-AttachmentActions. This record actions map contains the standard actions, Edit and Delete, plus custom actions used only by attachments, View and Upload.

- F1-AttachmentIDFrag. This record information map contains the primary key of the attachment.

Display Map Service Script

Display map service scripts can be fully supported via dynamic HTML generation. However, to help eliminate the need for a display service script, self-contained uiHint functionality has been developed to write the business object status and determine valid state transitions. So the two most common reasons to craft a display service script have been eliminated.

A typical reason to use a display pre-script is if you have an embedded map fragment that contains a business service schema. The display service script can be used to invoke the business service. Both the map fragment and the display service script must declare the business service schema to support this scenario.

Warning: The zone used to display the object's map must have a derivation script, like F1-GncDsMpDZ or F1-GenDss, that will invoke a display service script for the business object if it has been defined as a BO option - but not require an explicit display map BO option. In addition, the display service script's schema must be enabled for uiHint functionality - as the script's schema will be dynamically rendered by the zone - and not the BO schema.

- F1-ExcelSpreadsheet. This attachment BO has a display service script used to manipulate the attachment business object before displaying it:

- F1-AttchDtlU. This display map service script's schema has been defined with the uiHint namespace, and will have a display map generated for it.

Maintenance Pre-Processing Service Script

Maintenance pre-processing service scripts can be used with uiHints.

- F1-ExcelSpreadsheet. This attachment BO has a maintenance pre-processing service script used to manipulate the attachment business object before rendering the maintenance map:

- F1-AttchPre. This pre-processing service script's schema mimics a maintenance map schema with embedded boGroup and action elements. It will be invoked before the maintenance map is rendered.

Maintenance Post-Processing Service Script

Maintenance post-processing service scripts can be used with uiHints.

- F1-ExcelSpreadsheet. This attachment BO has a maintenance post-processing service script used to manipulate the attachment business object after rendering the maintenance map:

- F1-AttchPost. This post-processing service script's schema mimics a maintenance map schema with embedded boGroup and action elements. It will be invoked after the maintenance map is rendered.

Technical Notes

The following prerequisites are required to support dynamic HTML generation:

Schema Requirements

To support automated UI generation, the business object schema must contain the following:

- <schema xmlns:uiHint="http://oracle.com/ouafUIHints">. The schema node must name the uiHint namespace.

- isPrimeKey="true". Every element of the business object schema that is part of the primary key must be identified.

Maintenance Script Requirements

The maintenance script for the MO must be enabled for dynamic generation.

CAUTION:

The business object maintenance BPA script must be declared as an MO Option for uiHint maintenance functionality to work!

If the script performs F1-BOProc then it is likely no special functionality is needed. However, if the maintenance script contains its own call to F1-GetValOpt then the following statement is required prior to that call:

move 'false' to "F1-GetBOOpts/input/maintenanceMapRequired";

performScript 'F1-GetValOpt';

After the call to F1-GetValOpt the following logic must be included to dynamically declare the map schema if the business object does not have a maintenance map of its own:

// Perform Main Processing

if ("F1-GetBOOpts/output/maintenanceMap = $BLANK")

declareBOWithBOGroup "$bo" as 'map_schema';

else

declareMap "F1-GetBOOpts/output/maintenanceMap" as 'map_schema';

end-if;

Format an Input Map Title

Note: Throughout this topic the term "field" to refer to both the generic concept of displaying and capturing data in a 'field' as well as referring to the meta-data object supplied in the product to define Fields. When referring to the latter, the term "MD Field" (meta-data Field) is used.

A uiHint element can be used to build a title for a maintenance map. The title will only print on the maintenance map, not on the display map. It will be printed as the first line in the map, centered, with a heading style.

Syntax

Description

Examples

<uiHint:title mdField=" "/>

Displays the label of a referenced MD field as the title.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<uiHint:title

mdField="STATUS_RSN_LBL"/>

...

</schema>

<uiHint:title text=" "/>

Displays the indicated text as the title. (Do not use this mechanism when multiple languages are supported.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<uiHint:title

text="Status Reason"/>

...

</schema>

Create a Section

The uiHint namespace supports the definition of a UI map section. Note that sections are currently created in generated UI Maps when the schema has a group or list node with a label or mdField. The functionality described here enables the creation of a section without requiring a labeled group or list node within the schema. Every section must be bounded by startSection and endSection element pair.

Syntax

Supporting Attributes

Description

<uiHint:startSection .../>

sectionColumn="left | right | fullWidth | float"

The default is that the section will be the full width in display maps. To override that setting, specify if you want a half-width section to appear in either the left (left) or right (right) column or to float (float). Sections that are marked as 'float' will display half-width and be aligned according to whether prior sections are displayed or conditionally hidden. For example, if a left-aligned section is followed by a floating section, the floating section will appear in the right column if the left section is populated but will display in the left column if the left section is hidden / collapsed.

editColumn="left | right | fullWidth | float"

By default a section appears as full width in maintenance maps. To override that setting, specify if you want a half-width section to appear in either the left (left) or right (right) column or to float (float). The behavior is the analogous to the sectionColumn behavior.

sectionOpen="false"

By default a section is open on initial display. Specify this attribute to initially display the section as closed (collapsed).

mdField=" "

Specify the name of a MD field whose label should be used as the section heading.

label=" "

Specify the explicit text to use as the section heading.

visibleOn="displayMap | inputMap"

By default a section appears on both the display and the input maps. Use this attribute to limit the display of the section to either the display map (displayMap) or input map (inputMap).

The syntax for the end section attribute is <uiHint:endSection/>

Examples:

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<uiHint:startSection label="Main" sectionColumn="left"/>

...

<uiHint:endSection/>

</schema>

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<uiHint:startSection mdField="F1-ADD-INFO" sectionColumn="fullWidth" editColumn="float" sectionOpen="false" visibleOn="displayMap"/>

...

<uiHint:endSection/>

</schema>

Note: The sectionColumn, editColumn and sectionOpen attributes are available for group and list nodes as well.

Include a Map Fragment

You can specify a UI map fragment to inject HTML into a generated map using the includeMap element name. This allows for you to support more sophisticated behavior on your user interface. For any element that is included for rendering in the map fragment, be sure to suppress the element in its schema definition, otherwise HTML will automatically be generated for the element.

Syntax

Supporting Attributes

Description

<uiHint:includeMap .../>

map=" "

Specify the name of the map.

visibleOn="displayMap | inputMap"

By default the details from the map fragment appear on both the display and the input maps. Use this attribute to limit the display of the section.

Example:

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<uiHint:includeMap map="StandardActionButtons" visibleOn="displayMap"/>

...

</schema>

Note: Important note on the map fragment schema: If a map fragment contains a schema, then the fragment schema structure will be injected into the dynamically generated schema when the business object is rendered for input. Technically, the fragment schema will be inserted after the boGroup structure within the map's schema. This method may be used to support the implementation of maintenance pre and post script processing for a business object and oraInvokeBS function calls within embedded JavaScript.

If JavaScript is required within an XHTML UI Map fragment, it is necessary to bound it within a ![CDATA[ ]] tag to ensure a valid XML document. Note that the tags themselves may need to be commented out to promote compatibility with older browsers. For example:

<script type="text/javascript">

/* <![CDATA[ */

//

//javascript

//

/* ]]> */

</script>

Flush the cache: For performance reasons, the Framework automatically caches business object schemas, data areas, and UI maps. When you update a business object, the cache is automatically flushed. However, if the business object includes either a data area or embedded UI map fragment, the cache must be manually flushed in order for your changes to be recognized. Refer to Server Cache for more information.

Build A Dropdown

Syntax is provided to build a dropdown list in an edit map. The dropdown may be built using data returned from a service script, a business service or a table.

Syntax

Description

uiHint:select="ss: "

Specify the name of the service script after the colon.

uiHint:select="bs: "

Specify the name of the business service after the colon.

uiHint:select="table: "

Specify the name of the table after the colon.

When specifying a service script or a business service, extra mapping information is needed to pass data to and from the service.

Syntax

Values

Description

uiHint:selectIn=" "

serviceXPath:element

Used to pass the value of another element into the service (mapping to the service's XPath).

serviceXPath:'Literal'

Used to pass a constant or literal to the service (mapping to the service's XPath).

uiHint:selectOut="valuePath: ; descPath: "

See examples below.

Used to indicate which element in the service's output holds the values and which one holds the descriptions.

Examples:

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<boStatus mapField="BO_STATUS_CD" uiHint:select="bs:F1-BOStateReasonList"

uiHint:selectIn="boStatusBO:boStatusBO" uiHint:selectOut="valuePath:results/status;

descPath:results/description"/>

...

<algorithm mdField="ALG_CD" uiHint:select="bs:F1-RetrieveSysEvtAlgorithms"

uiHint:selectIn="algorithmEntity:'F1AA';" uiHint:selectOut="valuePath:results/algorithm;

descPath:results/description"/>

...

<outboundMsgType mdField="OUTMSG_TYPE_CD" required="true" fkRef="F1-OMTYP" uiHint:select="table:F1_OUTMSG_TYPE"/>

</schema>

Conditionally Hide Elements

The displayNone attribute is used to suppress elements on the map based on conditions.

Syntax

Values

Description

uiHint:displayNone=

"'XPath','value','!=' | '='"

Used to conditionally hide this element based on the value of another element (referenced using its XPath). Enter a value of ' ' to interrogate a blank value. By default the operator is '='. This may be overridden using '!='.

"function name, true | false"

Used to indicate a JavaScript function, which must return a Boolean.

Warning:

Embedded spaces are not supported within the comma separated string values of this attribute.

This setting may be used on group nodes, list nodes, and elements - except for elements within a list. Elements within a list cannot be hidden conditionally.

The following example illustrates that two elements (currency reference and lookup) that will be hidden or displayed based on the value of the data type element. Note that this example also illustrates Trigger Dependent Behavior because the data type element's value may change and if it does, the condition for hiding the subsequent elements should be re-evaluated.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<dataType mdField="F1_SE_DATA_TYPE" dataType="lookup" lookup="F1_SE_DATA_TYPE"

uiHint:dependents="currencyRef;lookup; "/>

<currencyRef mdField="F1_SE_CURR_REF_LBL" uiHint:displayNone="'dataType','F1MO','!='"/>

<lookup mdField="F1_SE_LOOKUP_LBL" fkRef="F1-LKUPF" uiHint:displayNone="'dataType','F1LP','!='"/>

...

</schema>

The following example illustrates referring to a function where the function receives parameters:

<uiHint:startSection mdField="F1_SE_DEFAULT_SECT"

uiHint:displayNone="isApplicableForSchemaType(item,'F1MP'),true"/>

Conditionally Protect Elements

The protect attribute is used to protect elements on the map based on other factors.

Syntax

Values

Description

uiHint:protect=

"'XPath','value','!=' | '='"

Used to conditionally protect this element based on the value of another element (referenced using its XPath). Enter a value of ' ' to interrogate a blank value. By default the operator is '='. This may be overridden using '!='.

"function name, true | false"

Used to indicate a JavaScript function, which must return a Boolean.

"'action','A' | 'C','!=' | '='"

Use the 'action' setting to protect the element based on the current action. For example, certain elements may only be specified when adding a record. Any subsequent changes to the record should protect the element from being changed. When using this option, the valid values for the 'value' are A (add) and C (change).

Warning:

Embedded spaces are not supported within the comma separated string values of this attribute.

The protect UI Hint may be used on group nodes, list nodes, and elements - except for elements within a list. Elements within a list cannot be protected conditionally.

The following UI Hint will protect the statistics category when the action is 'C'.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<statisticsCategory dataType="lookup" mapField="STAT_CATEGORY_FLG"

lookup="STAT_CATEGORY_FLG" uiHint:protect="'action','C','='"/>

...

</schema>

Trigger Dependent Behavior

The dependents attribute is used to trigger behavior on a child element when a parent element is changed.

Syntax

Values

uiHint:dependents=" "

A list of one or more dependent elements separated by semicolons.

The following example illustrates that the dropdown list of one element is driven by the value of another element. In this example, when the Country changes, the list of States to choose from should change to only show the states for the indicated country.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<country label="Country" uiHint:select="table:CI_COUNTRY" uiHint:dependents="state"/>

<state label="State" uiHint:select="ss:CM-RetrieveCountryStates"

uiHint:selectIn="input/country:country;"  uiHint:selectOut="valuePath:output/state/stateCode;

descPath:output/state/stateDesc"/>

...

</schema>

Note:

Dependent targets may only name elements, not group or list nodes.

Do not modify the "id" attribute value of dependent and parent element. Data population in dependent is done based on the "id" attribute value.

Control Rendering Target

By default all elements that are not suppressed are visible on both the display map and the input map. Use the visibleOn attribute to limit the inclusion of an element to either the display or input map.

Syntax

Values

uiHint:visibleOn=

"displayMap"

"inputMap"

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<uiHint:includeMap map="StandardActionButtons" visibleOn="displayMap"

...

</schema>

Generate a Text Area

By default, a standard text box is rendered in an input map for any string element. If the field is larger and you wish to have a bigger text area (with a scroll bar), use the textArea attribute.

Syntax

uiHint:textArea="true"

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<message label="Message" uiHint:textArea="true"/>

...

</schema>

Modify FK Reference Defaults

By default, when an element with fkRef is displayed, an info string, context menu, navigation, and search are enabled (if the FK reference has been configured accordingly). Syntax is provided to allow you to selectively turn off any of these features.

Syntax

uiHint:fkRef="info:false;context:false;navigation:false;search:false;"

Only the feature that you wish to turn off needs to be specified. The following example illustrates turning off the navigation capability, meaning the text will not be rendered as hypertext.

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<attachmentID fkRef="F1-ATTCH" primeKey="true" suppress="input" uiHint:fkRef="navigation:false;"/>

...

</schema>

Fastpath: Refer to FK Reference Formatting in the UI Map Attributes section for more information on each FK reference setting.

Suppress Automatic Number Formatting

By default numeric fields (dataType="number") are formatted as numeric fields. An attribute is provided to instead apply alphanumeric formatting.

Note: If dataType is not specified explicitly, it is be derived from mdField or mapField.

Syntax

uiHint:alphaFormat="true|false"

By default, its value is false (and therefore can be left out altogether).

Examples:

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

...

<numberCount mdField="" dataType="number" uiHint:alphaFormat="true"/>

...

</schema>

Auto Capitalize the Input Data

The uiHint provides syntax to automatically capitalize input data.

Syntax

uiHint:capitalize="true|false"

By default, its value is false (and therefore can be left out altogether).

<schema xmlns:uiHint="http://oracle.com/ouafUIHints">

<toDoTypeCd mdField="TD_TYPE_CD" uiHint:capitalize='true' isPrimeKey="true"/>

</schema>

Note: This attribute is ignored if uiHint:textArea="true" is configured.

The attribute is only available in the schema designer when the isPrimeKey is set to true. The attribute may be added to any string element when using the source viewer.

Schema Designer

The Schema Designer is a user-friendly interface for performing the following common schema editing tasks:

- Displaying existing schemas.

- Creating schema elements.

- Moving elements within a schema.

- Adding attribute values.

The designer provides two view modes:

- Text mode shows the schema elements and their attributes written in the proper syntax and allows for direct text entry.

- Tree mode is a view showing the elements in a tree format with many of the key attributes of each element in tabular form. While in this mode, the Node Display controls allow the user to choose between displaying the elements by their internal identifiers or their associated screen labels while viewing or editing the schema.

Note: Schemas that are not owned by the current installation owner are protected in both view modes.

The following sections provide more information about functionality available in the Tree mode.

- If the schema definition refers to another schema using an 'include' statement, a triangle is visible to the left of the tree area. One can expand that schema by clicking the triangle.

- Detailed information about an element's definition can be displayed and if applicable, updated from theTree view by clicking the edit icon for that element, which appears on the right. Note that the element attributes are only editable if the element is defined in this schema. When viewing the attributes of an element that is part of an 'include' of another schema, the attributes are display only.

- Context-sensitive embedded help is provided for fields and controls in the edit pane by clicking the Help icon

- There is a menu dropdown icon visible to the left of the tree for any element that is defined in the current schema being viewed. It is not visible for elements included from another schema. New elements may be added in the Tree mode. Clicking that dropdown displays options to Add, Delete or Move an element. Note that not all options are visible, based on what is allowed for the element adjacent to the menu. For example, on the main "schema" node, only the Add option is visible as deleting or moving the "schema" node is not applicable.

When adding a new element, you are prompted first for the element position, which is either a sibling node to the current element or a child node of that element. For either option, the new element is added below the one adjacent to where the menu is clicked. You are then prompted for the element type.

The following lists the possible element types. Most are self explanatory and represent standard schema options.

- Characteristic List. This is a special type of Flattened List element that is used to map list elements that include a sequence and a characteristic value for a given characteristic type. This element is only applicable for maintenance objects that have one or more characteristic child tables where the primary key is the maintenance object’s key, characteristic type and sequence. Effective dated characteristic collections are not supported. The user defines the list name, the characteristic value element name and the characteristic type. The system will configure the remaining flattening information accordingly.

- Characteristic. This is a special type of Flattened Field element that is used to map a single element to the characteristic for a given characteristic type. This element is only applicable for maintenance objects that have one or more characteristic child tables where the primary key is the maintenance object’s key, characteristic type and sequence. Effective dated characteristic collections are not supported. The user defines the element name and the characteristic type. The system will configure the remaining flattening information accordingly.

- Comment. This adds a comment to the schema.

- Embedded HTML. This is specific to a schema enabled for UI Hints. It is used to include a UI map fragment.

- Field

- Flattened Field

- Flattened List

- Group

- Include BO Schema

- Include BS Schema

- Include DA Schema

- Include Map Schema

- Include SS Schema

- Input Map Title. This is specific to a schema enabled for UI Hints. It is used to define a title element for the map.

- List

- Nested Flattened Field. This is a flattened field from a child table.

- Raw Element. This element is used to capture text as is. It is typically used to capture an XML structure without any details of the definition of the individual nodes.

- Section. This is specific to a schema enabled for UI Hints. It is used to define a section within the map.

- Simple Field. This is a special type of Field element that is used to define an element that is mapped to a column that supports data defined in an XML structure. (This is either a column with the character large object data type (CLOB) or the XML data type).

The Schema Designer is available by choosing the Schema tab on the Business Object, Data Area, UI Map, Business Service, and Script pages.

Schema Viewer

The schema viewer shows a tree-view presentation of a schema in its expanded form.

The schema illustrates the structure to be used when communicating with the schema's associated object. The following takes place when a schema is expanded:

- If the schema definition includes references to other schemas, these references are replaced with the corresponding schema definitions.

- Also, if the schema definition contains private elements, they are omitted from this view.

Clicking on any node on the tree populates the text box on the top with the node's absolute XPath expression. You will find this feature very useful when writing scripts interacting with schema-based objects. Scripting often involves referencing elements in a schema-based XML document using their absolute XPath expression. You can use this feature on the schema viewer to obtain the XPath expression for an element and copy it over to your script.

Business Event Log

Business Event Log may be viewed as a tool designed to capture any type of business event worth noting. You configure business objects to represent the various types of events your application calls for. The following type of details may be captured for each event:

- The business object representing the type of event.

- The date and time the event took place and who initiated it.

- The business entity for which this event is logged.

- Standard application message to describe the event.

- Additional context information that is available at the time of the event and varies for each type of event. The Business Event Log maintenance object supports a standard characteristics collection as well as an XML storage (CLOB) field. The event's business object determines where each piece of information resides. Refer to Business Objects for more information.

One common type of event may be the audit of changes made to sensitive data, for example, tracking an address change. Whenever an entity associated with a business object is added, changed, or deleted the system summarizes the list of changes that took place in that transaction and hands them over to Audit business object algorithms to process. You may design such an algorithm to audit the changes as business event logs. Refer to a business object may define business rules for more information.

You can also allow users to initiate business event logs to capture important notes about a business entity by exposing a BPA Script to invoke the event's corresponding business object.

Bottom line is that any process can create a business event log by invoking the business object representing the appropriate type of event.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_BUS_EVT_LOG.

Miscellaneous Topics

The following sections describe miscellaneous system wide topics.

Next in This Section

- Module Configuration

- Global Context Overview

- System Data Naming Convention

- Referencing URIs

- Caching Overview

- Expression Parser

- Debug Mode

- System Override Date

- Advanced Search Options

Module Configuration

The system provides the ability to simplify the user interface based on functionality areas practiced by your organization.

Menu items and other user interface elements are associated with function modules. By default, all function modules are accessible. If a function module is not applicable to your business you may turn it off. Refer to Turn Off A Function Module for more information on how to turn off a module.

If a function module is made non-accessible, i.e. turned off, its related elements are suppressed from the user interface. In addition the system may validate that related functionality is not accessed. This also means that turning off the wrong module may cause any of the following to occur:

- Menu items may not appear. Refer to Menu Item Suppression to better understand how menu item suppression works.

- Entire menus may not appear. Refer to Menu Suppression to better understand how menu suppression works.

- Tabs on pages may not appear.

- Fields may not appear.

- The system may return an error message when you attempt to use a function (indicating the function is turned off).

To correct the above situation, simply remove the module from the turned off list thus making it accessible again.

Your module configuration setup is displayed on the installations record.

Next in This Section

- Menu Item Suppression

- Menu Suppression

- Turn Off A Function Module

Menu Item Suppression

The following points describe how your module configuration can suppress menu items.

- Menu items that are owned by the base product (as opposed to those your implementation adds) are associated with one or more function modules. If your module configuration has turned off all of the menu item's modules, the menu item is suppressed. If at least one of the modules is accessible, i.e. turned on, the menu item is not suppressed.

- If a menu line doesn't contain any accessible items, the menu line is suppressed.

- If all lines on a menu are suppressed, the menu itself ( Menu or Admin menu) is suppressed in the application toolbar.

Menu Suppression

In addition to the above Menu Item Suppression logic, the following points describe how your module configuration can suppress an entire menu.

- Menus that are owned by the base product (as opposed to those your implementation adds) are associated with one or more function modules.

- If your module configuration has turned off all of the menu's modules, the entire menu is suppressed. If at least one of the modules is accessible, i.e. turned on, the menu is not suppressed.

Turn Off A Function Module

The base package is provided with a Module Configuration Feature Configuration that allows your organization to turn off base package function modules.

To turn off any of the base package function modules add a Turned Off option to this feature configuration referencing that module. Refer to the MODULE_FLG lookup field for the complete list of the application's function modules.

Any module not referenced on this feature configuration is considered turned on, i.e. accessible. To turn on a module, simply remove its corresponding Turned Off option from this feature configuration.

You may view your module configuration setup on the installation options page.

Note: Only one. The system expects only one Module Configuration feature configuration to be defined.

Global Context Overview

The framework web application provides each product the ability to nominate certain fields to act as a "global context" within the web application. For example, in Oracle Utilities Customer Care and Billing, the global context fields include Account ID, Person ID and Premise ID. The values of these fields may be populated as a result of searching or displaying objects that use these fields in their keys. If you navigate to the Bill page and display a bill, the global context is refreshed with the Account ID associated with that bill. The global context for Person ID and Premise ID are refreshed with data associated with that account.

The fields designated as global context for the product are defined using the lookup F1_UI_CTXT_FLDS_FLG.

Changing the values of the global context typically cause data displayed in zones on the dashboard to be refreshed to show information relevant to the current values of these global context fields.

When the value of one of the global context fields changes, an algorithm plugged into the installation record is responsible for populating the remaining global context values accordingly. Refer to your specific product for more information about the base algorithm that is provided for that product.

System Data Naming Convention

There are several maintenance objects in the system that include owner flag in one or more of its tables. We refer to the data in these tables as "system data". Some examples of system data tables include Algorithm Type, Batch Control, Business Object and Script. Implementations may introduce records to the same tables. The owner flag for records created by an implementation is set to CM (for customer modification), however the owner flag is not part of the primary key for any of the system data tables. As a result, the base product provides the following guidelines for defining the primary key in system data tables to avoid any naming conflict.

Next in This Section

- Base Product System Data

- Implementation System Data

Base Product System Data

For any table that includes the owner flag, the base product will follow a naming convention for any new data that is owned by the base product. The primary key for records introduced by the product is prefixed with xn- where xn is the value of the owner flag. For example, if a new background process is introduced to the framework product, the batch code name is prefixed with F1-.

Note: There are some cases where the hyphen is not included. For example, portal codes omit the hyphen.

For most system data, the remainder of the primary key is all in capital case. An exception is schema oriented records. For business objects, business services, scripts, data areas and UI maps, the product follows the general rule of using CapitalCase after the product owner prefix. For example, F1-AddToDoEntry is the name of a base product business service.

Note: Data Explorer Business Services. For business services used to invoke a data explorer zone, it is recommended to name the Business Service the same name as the related zone rather than defining a different CapitalCase name for the business service.

Please note that this standard is followed for all new records introduced by the base product. However, there are base product entries in many of these system data tables that were introduced before the naming convention was adopted. That data does not follow the naming convention described above.

Note: Schema naming conventions. A context sensitive "Schema Tips" zone is associated with any page where a schema may be defined. The zone provides recommended naming conventions for elements within a schema along with a complete list of the XML nodes and attributes available to you when you construct a schema.

Implementation System Data

When new system data is introduced for your implementation you must consider the naming convention for the primary key. The product recommends prefixing records with CM, which is the value of the owner flag in your environment. This is consistent with the base product naming convention. This convention allows your implementation to use the CM packaging tool in the Software Development Kit as delivered. The extract file provided with the tool selects system data records with an owner flag of CM and with a CM prefix.

Note: If you choose not to follow the CM naming convention for your records and you want to use the CM packaging tool, your implementation must customize the extract file to define the appropriate selection criteria for the records to be included in the package. Refer to the Software Development Kit documentation for more information.

Also note that owner flag may be introduced to an existing table in a new release. When this happens, the CM packaging tool is also updated to include these new system data tables. Your implementation will have existing records in those tables that probably do not follow any naming convention. After an upgrade to such a release, if you want to include this data in the CM packaging tool, you must customize the extract file for the tables in question.

Referencing URIs

There are some configuration objects that require a reference to a URI, including file path URIs. The following sections highlight some functionality supported by the product with respect to defining / accessing URIs.

Note: In order for the functionality described below to occur, specific APIs must be used by the underlying code related to the fields that capture or process the file path or URL information. If you find that there is a URI-related field that does not provide the functionality described here, please contact customer support.

Note: For schema elements in a business object that reference a Field with the URI data type or define the element with the URI data type configured in the schema will automatically use the appropriate API that validates the value that may reference a substitution variable or must be checked against the whitelist if applicable.

Next in This Section

- Validation Against a Whitelist

- URI Substitution

Validation Against a Whitelist

Based on a property setting, your implementation may be configured to define a whitelist of URIs. If this setting is enabled, the system will issue an error if the URI is not defined in the whitelist. Consult your system administrator to verify if this setting is enabled or not for your implementation.

Fastpath: Refer to URI Substitution for information about how defining substitution tokens for URIs using the properties file technique automatically adds the defined URI to the whitelist.

URI Substitution

The system supports the ability to define substitution variables (sometimes referred to as tokens) for all or part of a URI using the substitution variable properties file. This allows the system administrators to define the proper URI locations in a properties file whereas the configuration users only need to know the variable name. For example, when defining a location for an extract file in an extract batch job, instead of typing a file path of h:\oracle\serverName\1.0.0.0\batch\extract\, the batch user can enter @FILE_EXTRACT@, assuming there is an entry in the substitution variables file with a name of FILE_EXTRACT, and a value of h:\oracle\serverName\1.0.0.0\batch\extract\. Another example is that the batch user could enter @BATCH_FILES@\extract\, assuming that the URI variable for BATCH_FILES is defined as h:\oracle\serverName\1.0.0.0\batch\.

Note: The product automatically populates the value of SPLOUTPUT in the properties file so that this may be used in URI configuration. In addition, the product may supply some pre-defined variable names for other common references. As part of this, the 'advanced' menu in the system installation steps may prompt for installers to define the values of these pre-defined variables, if desired. Installations may opt to define additional substitution variables for various URI references. Refer to the System Administration Guide for more information.

Caching Overview

A great deal of information in the system changes infrequently. In order to avoid accessing the database every time this type of information is required by an end-user or a batch process, the system maintains a cache of static information on the web server and in the batch thread pool worker. These are referred to as the “application caches”. Some examples of application caches include

- System messages

- Field label and other field information

- Security Information

The framework product provides many specific caches for commonly used (and infrequently changed) data. In addition, specific edge applications may introduce additional caches as appropriate.

Information may also be cached on each user's browser.

The following topics highlight information about refreshing the various caches.

Next in This Section

- Server Cache

- Batch Cache

- Client Cache

Server Cache

The server cache refers to data that is cached on the web server. An important use of this cache is for users’ online access to the application. The caches aid in better performance while navigating throughout the system, allowing for data to be accessed from the cache rather than by always accessing the database. Besides user access to the web server cache, other functionality deployed to the web server uses caches in a similar way. For example, web services are deployed to the web server and access their own version of the cache.

The contents of the cache are cleared whenever the web server is restarted. This means that fresh values are retrieved from the database once users and web services start using the application again.

The product also supplies a flush command that one can issue in the browser's URL to immediately clear the contents of the cache. The command flushAll.jsp flushes every cache.

For example, assume the following:

- the web server and port on which you work is called OU-Production:7500

- you add a new record to a control table and you want it to be available on the appropriate transactions immediately

You would issue the following command in your browser's address bar: http://OU-Production:7500/flushAll.jsp. Notice that the command replaces the typical cis.jsp that appears after the port number.

If your system has been configured correctly, the flushAll command will submit a request to do a “global” flush of caches (including the web services cache and the thread pool worker cache). This functionality uses a JMS Topic to publish the flush request. Refer to the Server Administration Guide for details on how to configure the JMS topic.

Batch Cache

When submitting a batch job, the batch component uses a Hibernate data cache to cache administrative data that doesn’t change very often. The tables whose records are included in this cache are configured using the Caching Regime value of Cached for Batch. Refer to Table - Main for more information. When starting a thread pool worker, data in tables marked as cached is loaded and cached for as long as that thread pool is running.

In addition batch jobs may also access application caches when applicable. When starting a thread pool worker, application data that is cached is loaded and cached for as long as that thread pool is running.

If there is a change in cached data that should be available for the next batch job, the following points highlight how the cache can be refreshed:

- By default the system is configured to automatically refresh the Hibernate cache every 60 seconds. However, an implementation may override the configuration to either change the number of seconds between intervals or to disable the automatic caching altogether. Application caches used by the batch jobs are not impacted by this refresh.

- Restart the thread pool workers.

- Run the F1–FLUSH (Flush all Caches) background process. This background process will flush the application data cached for all thread pool workers for all thread pools.

- If your the region has configured the thread pool workers to “listen” to requests for global flush as described in the Server Cache topic, the thread pool worker caches are also refreshed when a flushAll command is issued.

Client Cache

In addition to the web server's cache, information is also cached on each user's browser. After clearing the cache that's maintained on the web server, you must also clear the cache that's maintained on your client's browser. To do this, follow the following steps:

- Select Tools on your browser's menu bar

- Select Internet Options... on the menu that appears.

- Click the Delete Files button on the pop-up that appears.

- Turn on Delete all offline content on the subsequent pop-up that appears and then click OK.

- And then enter the standard URL to re-invoke the system.

Note: Automatic refresh of the browser's cache. Each user's cache is automatically refreshed based on the maxAge parameter defined in the web.xml document on your web server. We recommend that you set this parameter to 1 second on development / test environments and 28800 seconds (8 hours) on production environments. Please speak to system support if you need to change this value.

Expression Parser

The product provides support for defining expressions that may be of a mathematical or logical/boolean nature. The expression may include variables and functions.

The data explorer column parameter is an example of where this may be used. That parameter supports the definition of a formula. Edge applications may include support for a formula or expression using this parser as well. For example, several application include a type of ‘rule’ object (calculation rule, form rule or usage rule) that is used for validation or calculation that may support applying a formula.

The following tables highlight what is supported in the expressions that use this parser.

Category

Supported in Expression

Description

Data types

Number

String

Boolean

List

Literals

Numbers

Strings surrounded with either single quote or double quote.
Note: 'Escaping' special characters is not currently supported.

Boolean values: true and false.

Operations

+

Plus

—

Minus

/

Division

*

Multiplication

^ or **

Power

%

Modulus

Logical operations

=

Equal

>

Greater than

>=

Greater than or equal to

<

Less than

<=

Less than or equal to

!= or <>

Not equal to

This table identifies the functions that are supported. Note that several of the functions are applicable to a list of values. Note that although the functions are listed in lower case, the column parameter syntax in data explorer indicates referencing the functions as all capital letters. The system converts the data explorer column formula to lowercase before being evaluated.

Function

Parameter

Results

Comments

size( )

List element

Number of elements in the list.

isEmpty( )

List element

Returns true if the list is empty.

sum( )

List element of type 'number'

Returns the sum of the numbers in the list.

avg( )

List element of type 'number'

Returns the average of the numbers in the list.

One or more numbers separated by commas

Returns the average of the number arguments.

max( )

List element

Returns the largest value in the list.

One or more comparable elements.

Returns the largest value of the number arguments.

min( )

List element

Returns the smallest value in the list.

One or more comparable elements.

Returns the smallest value of the number arguments.

abs( )

Number

Returns the absolute value.

ceiling( )

Number

Rounds the number to the ceiling.

exp10( )

Number

Raises 10 to the number power.

acos( )

Number

Returns the arc cosine of the number in radians.

The result will lose precision, as it uses the system's double float based functions.

asin( )

Number

Returns the arc sine of the number radians.

The result will lose precision, as it uses the system's double float based functions.

atan( )

Number

Returns the arc tangent of the number radians.

The result will lose precision, as it uses the system's double float based functions.

cos( )

Radian

Returns the cosine of the radian angle input.

The result will lose precision, as it uses the system's double float based functions.

exp( )

Number

Raises e to the number power.

The result will lose precision, as it uses the system's double float based functions.

log10( )

Number

Takes the log, base 10, of the number.

The result will lose precision, as it uses the system's double float based functions.

log( )

Number

Takes the natural log (base e) of the number.

The result will lose precision, as it uses the system's double float based functions.

sin( )

Radian

Returns the sine of the radian angle input.

The result will lose precision, as it uses the system's double float based functions.

sqrt( )

Number

Returns the square root of the number.

The result will lose precision, as it uses the system's double float based functions.

tan( )

Radian

Returns the tangent of the radian angle input.

The result will lose precision, as it uses the system's double float based functions.

floor( )

Number

Rounds the number to the floor.

round( )

Number

Assumes a scale of 0. The default rounding mode of “round half up” is applied.

Number, Scale

The default rounding mode of “round half up” is applied.

Number, Scale, Mode

The mode must be set to one of the following:

- “ROUND_CEILING”

- “ROUND_DOWN”

- “ROUND_FLOOR”

- “ROUND_HALF_DOWN”

- “ROUND_HALF_UP”

- “ROUND_HALF_EVEN”

- “ROUND_UP”

- “ROUND_UNNECESSARY”

negate( )

Number

Returns the negative value of the number.

Only available in data explorer.

The following are special functions supported in the application for a list of values. In each case, the syntax is function [ indexVariable in listName | expression using indexVariable ], where the indexVariable is chosen by the formula writer to represent each entry in the list and the expression used to evaluate each entry must reference that variable.

Note: The syntax supported for a given use of the formula in a functional area is driven by that particular functional area. For example, in Oracle Public Sector Revenue Management, a formula is supported in the “conditional element validation” form rule. In that form rule all variables including lists are declared in the form rule using letters and the formulas in turn use these letters. In that scenario, the functions below would reference the declared variable letter as the “listName”. Other specific functional area that use this expression parser may support different syntax for referencing elements or lists.

Function

Description

Examples

any [ ]

This function returns the value true if any of the entries in list satisfies the expression.

The following returns true if any entry in the Balance list is greater than 0.
any [ i in list/Balance | i > 0 ]

all [ ]

This function returns the value true if all of the entries in the list satisfy the expression.

The following returns true if all phone numbers are populated.
all [ i in list/phoneNumber | i != ' ' ]

collect [ ]

This function returns a new list of elements from the referenced list where the value of each entry of the new list is the result of the expression applied to each original value.

The following returns a new list with the tax rate applied to each amount.
collect [ i in list/amount | i * taxRate ]

select [ ]

This function returns a list of all the values of the original list that satisfy the Boolean expression.

The following returns a new list with only the amounts that are negative numbers.
select [ i in list/amount | i < 0 ]

reject [ ]

This function returns a list of all the values of the original list that do not satisfy the Boolean expression.

The following returns a new list with only the amounts that are not negative numbers.
reject [ i in list/amount | i < 0 ]

Debug Mode

Your implementation team can execute the system using a special mode when they are configuring the application. To enable this mode, enter ?debug=true at the end of the URL that you use to access the application. For example, if the standard URL was http://CD-Production:7500/cis.jsp, you'd enter http://CD-Production:7500/cis.jsp?debug=true to enable configuration mode.

When in this mode certain debugging oriented tools become available right below the main toolbar.

- Start Debug starts a logging session. During this session the processing steps that you perform are logged. For example, the log will show the data areas that are passed in at each step and the data areas returned after the step is processed.

- Stop Debug stops the logging session.

- Show Trace opens a window that contains the logging session. All of the steps are initially collapsed.

- Clear Trace clears your log file.

- Show User Log allows you to view your own log entries. The number of "tail" entries to view may be specified in the adjacent Log Entries field before clicking the button. Limiting the number of entries to view allows the user to quickly and easily see only the latest log entries without having to manually scroll to the end of the log.

- Checking the Global Debug indication starts various tracing options.

Other parts of the system may show additional configuration oriented icons when in this mode. For example, explorer zones may provide additional tools to assist in debugging zone configuration. These icons are described in the context of where they appear.

Also, in debug mode drop down lists in data explorer and UI map zones will contain the code for each item in addition to the item's display string.

Note: Show User Log button is secured. An application service F1USERLOG has been provided for this functionality to allow implementations to restrict user access to this button. Such restriction may be called for in production environments.

System Override Date

The system provides a way to override the system date used for online operations. This feature is available if the server administrator has enabled it in the environment properties. For instructions on configuring environment properties see the Server Administration Guide. The system date override feature is not recommended for production environments.

Under the General System Configuration Feature Configuration, the System Override Date Option Type holds the date the application will use as the global system date instead of retrieving the same from the database. This feature can be especially useful in running tests that require the system date to be progressed over a period of time.

The system override date feature is also available at the user level. This is useful when a user wants override the system date to run tests without affecting the system date for other users in the environment. In order to override the system date for the user, open the User — Characteristics page, add theSystem Override Date characteristic type with a characteristic value set to the desired date in the YYYY-MM-DD format.

If system override dates are defined at both the feature configuration level and the user level, the date set at the user level will take precedence.

Advanced Search Options

The product supports fuzzy searching in explorer zone types using the Oracle Text CONTAINS operator.

Refer to the DBA guide for details on setting up the database to support fuzzy searching. Note that there are some implementations where fuzzy searching will not be possible. For example, it's only available for implementations using the Oracle database. Additionally, not all languages are supported. Refer to the Oracle Database documentation for more information about fuzzy searching.

For information about the particular syntax to use in the explorer zones, refer to SQL Statement in the zone parameter details section.

To Do Lists

Certain events that occur within the system will trigger messages describing work that requires attention. For example, if a bill segment has an error, the system generates a To Do message to alert the person responsible for correcting such errors.

Each type of message represents a To Do list. For example, there are To Do lists for bill segment errors, payment errors, customer contact reminder, etc.

We refer to each message as a To Do Entry. Each To Do entry is assigned a specific To Do Role. The role defines the users who may work on the entry. A To Do entry has a To Do log that maintains record of the progress on the To Do entry. For example, the To Do log indicates when the To Do entry was created, when it was assigned to a user and to whom it was assigned, and when and by whom it was completed.

Fastpath: Refer to To Do Processing for a description of end-user queries and tools assisting in reviewing, assigning and processing To Do entries.

Next in This Section

- The Big Picture of To Do Lists

- Setting Up To Do Options

The Big Picture of To Do Lists

The topics below provide more information about To Do configuration.

Next in This Section

- To Do Entries Reference A To Do Type

- To Do Entries Reference A Role

- To Do Entries Can Be Rerouted (Or Suppressed) Based On Message Number

- The Priority Of A To Do Entry

- Working On A To Do Entry

- Launching Scripts When A To Do Is Selected

- To Do Entries Have Logs

- How Are To Do Entries Created?

- The Lifecycle Of A To Do Entry

- Linking Additional Information To A To Do Entry

- Implementing Additional To Do Entry Business Rules

- To Do Entries May Be Routed Out Of The System

- Periodically Purging To Do Entries

To Do Entries Reference A To Do Type

Every To Do entry references a To Do type. The To Do type controls the following functions:

- The To Do list on which the entry appears.

- The page into which a user is taken when they drill down on an entry.

- The message that appears in the user's To Do list. Note this message can be overridden for specific To Do messages by specifying a different message number in the process that creates the specific To Do entry. For example, the process that creates To Do entries associated with bill segments that are in error displays the error message rather than a generic "bill segment is in error" message.

- The To Do list's sort options. Sort options may be used on the To Do list page to sort the entries in a different order. For example, when a user looks at the bill segment error To Do list, they have the option of sorting it in error number order, account name order, or in customer class order. Note the default sort order is also defined on To Do type.

- Whether (and how) the To Do entry is downloaded to an external system (e.g., an email system).

- The roles to which an entry may be reassigned.

- The default priority of the To Do list in respect of other To Do lists.

- The To Do list's usage, which indicates whether a To Do of that type may be created manually by a user.

- The algorithms used to perform To Do list specific business rules.

- The characteristics applicable to the To Do list.

To Do Entries Reference A Role

Every To Do entry references a role. The role defines the users who may be assigned to Open entries.

The permissible roles that may be assigned to a To Do entry are defined on the entry's To Do type. After an entry is created, its role may be changed to any role defined as valid for the entry's To Do type.

An entry's initial role is assigned by the background process or algorithm that creates the entry. Because you can create your own processes and algorithms, there are an infinite number of ways to default an entry's role. However, the base package processes and algorithms use the following mechanisms to default an entry's role:

- The system checks if an entry's message category / number is suppressed (i.e., not created). If so, the entry is not created. Refer to To Do Entries Can Be Rerouted Or Suppressed Based On Message Number for more information.

- The system checks if an entry's message category / number is rerouted to a specific role. If so, it defaults this role. Refer to To Do Entries Can Be Rerouted Or Suppressed Based On Message Number for more information.

- Your specific product may introduce additional criteria for assigning a role, for example perhaps important accounts are assigned to a kind of account management group and the account management group includes configuration for special role for certain To Do types. Refer to Set Additional Information Before a To Do is Created for more information.

- If a Role wasn't determined in one of the previous steps and a Role is provided by the initiating process, the entry is created with that Role.

- If the entry does not have a role after the above takes place, the entry's To Do type's default role is assigned to the entry.

Note:

At installation time, the system provides a default role assigned to the system To Do types when first installed called F1_DFLT. This is done to allow testing of the system prior to implementing of appropriate To Do roles for your organization. The recommendation is to configure all the To Do Types with appropriate business oriented To Do roles once they are defined.

CAUTION:

Important! Most organizations have the notion of a supervisor who is responsible for all entries assigned to a given role. It's important for this user (or users) to be part of all such roles. Refer to To Do Supervisor Functions for information about transactions that can be used by supervisors to review and assign work to users.

To Do Entries Can Be Rerouted (Or Suppressed) Based On Message Number

Consider the To Do type used to highlight bill segments that are in error. To Do entries of this type reference the specific bill segment error number so that the error message can be shown when the Bill Segments in Error To Do list is displayed.

Note: Message Category / Message Number. Every error in the system has a unique message category / number combination. Refer to The Big Picture of System Messages for more information about message categories and numbers.

If you want specific types of errors to be routed to specific users, you can indicate such on the To Do type. For example, if certain bill segment errors are always resolved by a given rate specialist, you can indicate such on the To Do type. You do this by updating the To Do type's message overrides. On this page you specify the message category / number of the error and indicate the To Do role of the user(s) who should work on such errors. Once the To Do type is updated, all new To Do entries of this type that reference the message number are routed to the desired role.

Note: Reroute versus suppression. Rather than reroute an entry to a specific role, you can indicate that an entry with a given message number should be suppressed (i.e., not created). You might want to do this if you have a large volume of certain types of errors and you don't want these to clutter your users' To Do lists.

Obviously, you would only reroute those To Do types that handle many different types of messages. In other words, if the To Do type already references a specific message category / number rerouting is not applicable.

We do not supply documentation of every possible message that can be handled by a given To Do type. The best way to build each To Do type's reroute list is during the pre-production period when you're testing the system. During this period, compile a list of the messages that should be routed to specific roles and add them to the To Do type.

Keep in mind that if a message number / category is not referenced on a To Do type's reroute information, the entry is routed as described under To Do Entries Reference A Role.

Note: Manually created To Do entries cannot be rerouted or suppressed. The rerouting occurs as part of the batch process or algorithm processing when the To Do is created. The role or user to whom a manual To Do should be assigned is specified when the To Do is created online. A manually created To Do may also be forwarded to another user or role.

The Priority Of A To Do Entry

Some To Do entries may be more urgent to resolve than others. A To Do entry is associated with a priority level representing its relative processing order compared to other entries.

Priority level is initially assigned as follows:

- If a Calculate Priority plug-in is defined on the To Do entry's type, the system calls it to determine the entry's priority. You may want to use this method if an entry's priority is based on context or time-based factors. For example, when priority takes into consideration account specific attributes. When applicable, you may design a process that triggers priority recalculation of To Do entries "at will". For example, when priority is reassessed periodically based on factors external to the To Do entry's information. Refer to To Do Type for more information on priority calculation algorithms.

- If a priority value has not been determined by a plug-in, the system defaults a To Do entry's initial priority to the value specified on its type.

A user may manually override a To Do entry's priority at any time. Notice that once a To Do entry's priority is overridden, Calculate Priority plug-ins are no longer called so as to not override the value explicitly set by the user.

Note: The system does not use priority values to control order of assignment nor processing of To Do entries. Priority is available to assist your organization with supporting a business practice that ensures higher priority issues are worked on first.

Working On A To Do Entry

A user can drill down on a To Do entry. When a user drills down on an entry, the user is transferred to the transaction associated with the entry. For example, if a user drills down on a bill segment error entry, the user is taken to the Bill Segment - Main page. Obviously, the page to which the user is taken differs depending on the type of entry.

It is also possible to configure the To Do type to launch a script when a user drills down on an entry rather than taking the user to a transaction. The script would walk the user through the steps required to resolve the To Do entry. Refer to Launching Scripts When A To Do Is Selected for more information.

After finishing work on an entry, the user can mark it as Complete. Completed entries do not appear on the To Do list queries (but they are retained on the database for audit purposes). If the user cannot resolve the problem, the user can forward the To Do to another user.

Launching Scripts When A To Do Is Selected

Users can complete many To Do entries without assistance. However, you can set up the system to launch a script when a user selects a To Do entry. For example, consider a To Do entry that highlights a bill that's in error due to an invalid mailing address. You can set up the system to execute a script when this To Do entry is selected by a user. This script might prompt the user to first correct the customer's default mailing address and then re-complete the bill.

A script is linked to a To Do type based on its message number using the To Do type's message overrides. Refer to Executing A Script When A To Do Is Selected for more information.

To Do Entries Have Logs

Each To Do entry has a To Do log that maintains a record of the To Do's progress in the system. For example, the To Do log indicates when the To Do entry was created, when it was assigned to a user and to whom it was assigned, and when and by whom it was completed. Users can view the log to see who assigned them a particular To Do and whether any work has already been done on the To Do.

A log entry is created for all actions that can be taken on a To Do entry. Log entries are created for the following events:

- A To Do entry is created (either by the system or by a user)

- A To Do entry is completed (either by the system or by a user)

- A user takes an open To Do entry

- A supervisor assigns a To Do entry

- A user forwards an entry to another user or role

- A user sends back a To Do to the user who forwarded it

- A user manually adds a log entry to record details about the To Do's progress

- A user manually overrides the To Do entry's priority

Fastpath: For information about the contents of log entries for each of the events, refer to Log Entry Events.

How Are To Do Entries Created?

A To Do Entry may be created in the following ways:

- A background process can create To Do Entries.

- An algorithm can create entries of a given type. Because the use of algorithms is entirely dependent on how you configure the control tables, the number of types of such entries is indeterminate.

- A user can create entries of To Do types that have a Manual usage. Refer to To Do Entries Created Manually for information about setting up manual To Do types.

For any base product process that includes logic to create a To Do entry, the system supplies a sample To Do type that may be used. Although the To Do types provided by the product are system data, the following information related to each To Do type may be customized for an implementation and is not overwritten during an upgrade:

- The creation process. If the To Do is created by a background process where the background process is referenced on a To Do type. Refer to To Do Entries Created By Background Processes for more information.

- The routing process. Refer to To Do Entries May Be Routed Out of the System for more information.

- The priority. Refer to To Do Type - Main for more information.

- The roles that may be associated with the To Do type. Refer to To Do Entries Reference a Role for more information.

- The message override information. Refer to To Do Entries Can Be Rerouted (Or Suppressed) and Launching Scripts When a To Do Is Selected for more information.

Next in This Section

- To Do Entries Created By Background Processes

- To Do Entries Created By Algorithms

- To Do Entries Created Manually

To Do Entries Created By Background Processes

There are different types of To Do entries created by background processes:

- To Do entries created by dedicated To Do background processes

- To Do entries created for object-specific errors detected in certain background processes

- To Do entries created based on a specific condition

Next in This Section

- Dedicated To Do Background Processes

- To Dos Created for Object-Specific Error Conditions

- To Dos Created by Background Processes for Specific Conditions

Dedicated To Do Background Processes

There are To Do entries that are created by system background processes whose main purpose is to create To Do entries based on a given condition. For these background processes, the To Do Type indicates the creation background process.

Note: If you don't schedule the background process, the entries will not be created! The To Do entries of this type will only be created if you have scheduled the associated background process. Therefore, if you want the system to produce a given entry, schedule the background process.

To Dos Created for Object-Specific Error Conditions

A system background process may create a To Do entry when an error is detected during object-specific processing. This is applicable for processes that do not have built in error handling, for example where there is an explicit “error” state or where the record has an explicit “exception” record.

For these background processes, the To Do Type must reference the creation background process.

To have the system create To Do entries for some or all of the errors generated by one of these processes, you must do the following:

- If you want the system to generate To Do entries for errors detected by one of the background processes below, go to the appropriate To Do type and populate the creation background process.

- If you want the system to generate To Do entries for some errors for the process, but not for all errors, populate the creation background process and then proceed to the message overrides tab to suppress certain messages. To this by indicating the message category and message number you want to suppress. Any error that is suppressed is written to the batch run tree.

The functionality will only create a new To Do entry if there is not already an existing (non-complete) To Do for the same To Do type and drill key. It will also check for an existing To Do for a successfully processed record and complete that To Do.

If you do not populate the creation background process, the errors are written to the batch run tree.

Note: Errors received while creating a To Do entry. If the background process cannot successfully create a To Do entry to report an object-specific error, the error is written to the batch run tree along with the error encountered while attempting to create the To Do entry.

Note: System errors are not included. To Do entries are not created for a system error, for example an error related to validation of input parameter. These errors are written to the batch run tree. Refer to Processing Errors for more information.

To Dos Created by Background Processes for Specific Conditions

There are some system background processes that create a To Do entry when the process detects a specific condition that a user should investigate. For each background process, the To Do type is an input parameter to the process. The system provides To Do types for each base package background process that may create a To Do entry.

Note: No Creation Process. These To Do types do not need (and should not have) a Creation Process specified.

To Do Entries Created By Algorithms

There are To Do entries that are created by algorithm types supplied with the base package. The system supplies a To Do Type for each of these To Do entries that you may use.

If you want to take advantage of these types of entries for system algorithm types, you must do the following:

- Create an algorithm:

- This algorithm must reference the appropriate Algorithm Type.

- These algorithms have a parameter of the To Do Type to be created. You should specify the To Do Type indicated in the table.

- Plug the algorithm into the respective control table.

To Do Entries Created Manually

You must set up manual To Do entry types if you want your users to be able to create To Do entries online. Users may create a manual To Do entry as a reminder to themselves to complete a task. Online To Do entries may also be used like electronic help tickets in the system. For example, if a user is having a problem starting service, the user can create a To Do that describes the problem. The To Do can be assigned to a help resolution group that could either resolve the problem or send the To Do back to the initiating user with information describing how to resolve the problem.

If you want to take advantage of manual To Do entries, create a To Do type and specify the following information.

On the Main tab:

- Set the To Do Type Usage flag to Manual.

- Set the Navigation Option to toDoEntryMaint (To Do entry maintenance).

- Set the Message Category and Message Number to the message you want to be used for To Do entries of this type. The system will populate the message parameter with the Subject. To show only the subject in the To Do’s message, use a message with “%1” as its text.

On the Roles tab:

- Specify the To Do roles that may be assigned to To Do entries of this type.

- Indicate the To Do role that should be defaulted when you create To Do entries of this type.

On the Sort Keys tab:

When a user adds a manual To Do entry, the system creates an entry with three sort key values. (Sort keys may be used on the To Do list page to sort the entries in a different order.) The To Do type should be set up to reference the sort keys as follows:

Sequence

Description

1

Created by user ID

2

Created by user name

3

Subject

We recommend that the keys have an Ascending sort order and that the Subject is made the default sort key.

Note: It is possible to define additional sort keys and use a To Do Post Processing algorithm to populate the values. In this case, the base sort keys defined above should still be defined.

On the Drill Keys tab:

When a user adds a manual To Do entry, it is created with a drill key value equal to the To Do entry's ID. When the user clicks the Go To button next to the message in the To Do list, the system uses the drill down application service (defined on the main tab) and the drill key to display the associated To Do entry.

The To Do type must be set up with a drill key that reference the To Do entry table and the To Do entry ID:

Sequence

Table

Field

1

CI_TD_ENTRY

TD_ENTRY_ID

The Lifecycle Of A To Do Entry

The following state transition diagram will be useful in understanding the lifecycle of a To Do entry.

A To Do entry is typically created in the Open state. Entries of this type can be viewed by all users belonging to the entry's role. Refer to How Are To Do Entries Created? for information about how entries are created.

An Open entry becomes Being Worked On when it is assigned to a specific user or when a user proactively assumes responsibility for the entry. While an entry is Being Worked On, it is visible on the To Do Summary page only by the user who is assigned to it.

Note: To Do entries may be created in the Being Worked On state. Some To Do background processes may create To Do entries in the Being Worked On state. When a user adds a To Do entry online and assigns the To Do to a user (as opposed to a role), the To Do entry is also created in the Being Worked On state.

A Being Worked On entry may be forwarded to a different user or role. If the entry is forwarded to a role, it becomes Open again.

When an entry becomes Complete, it is no longer visible in the To Do list queries (but it remains on the database for audit purposes). There are two ways an entry can become Complete:

- A user can manually indicate it is Complete (there are several ways to do this).

- For To Do entries that are logically associated with the state of some object, the system automatically marks the entry Complete when the object is no longer in the respective state. For example, an entry that's created when an account doesn't have a bill cycle is completed when the account has a bill cycle.

CAUTION:

Important! The automatic completion of To Do entries occurs when the background process responsible for creating entries of a given type is executed. Therefore, if you only run these processes once per day, these entries remain Being Worked On even if the object is no longer in the respective state.

Linking Additional Information To A To Do Entry

Additional information may be linked to a To Do entry using characteristics. For example, when creating a manual To Do entry, a user may define the account related to the To Do.

When creating an automatic To Do entry, the program that generates the To Do may link related data to the To Do using characteristics. In addition, a system algorithm allows you to automatically to link related entities. For manually created To Dos, the valid characteristic types that may be linked to the To Do entry must be defined on the To Do type for that To Do entry.

If your To Do entries reference characteristics that are related to your global context data, you may want to configure an alert algorithm to display an alert if a related entry is Open or Being Worked On.

Implementing Additional To Do Entry Business Rules

If your business practice calls for additional validation rules or processing steps to take place after a To Do Entry is created or updated, you may want to take advantage of the To Do Post Processing plug-ins defined on To Do type.

For example, you may want to validate that To Do entries are only assigned to users with the proper skill levels needed to resolve them. Refer to F1-VAL-SKILL for a sample algorithm handling such validation.

To Do Entries May Be Routed Out Of The System

A To Do type can be configured so that its entries are interfaced to another system.

For example, a given To Do type can be configured to create an email message whenever a new To Do entry is created. The following points describe how to do this:

- Define the name of the background process responsible for interfacing the new To Do entries to another system on the respective To Do type. The base package contains a batch process called F1-TDEER that can be used for most situations. This batch process invokes the External Routing algorithms defined on each entry's To Do type.

- Plug in an appropriate External Routing algorithm on the respective To Do type. The logic in this type of algorithm performs the interface efforts for a specific To Do entry. For example, if an email message should be created for a To Do entry, the logic in the algorithm would compose and send the email message(s) for a specific To Do entry.

Click here to see the algorithm types available for this system event.

Periodically Purging To Do Entries

Completed To Do entries should be periodically purged from the system by executing the F1–TDPG background process. This background process offers you the following choices:

- You can purge all To Do entries older than a given number of days.

- You can purge To Do entries for a specific list of To Do types that are older than a given number of days.

- You can purge all To Do entries except for a specific list of To Do types that are older than a given number of days.

We want to stress that there is no system constraint as to the number of Completed To Do entries that may exist. You can retain these entries for as long as you desire. However, you will eventually end up with a very large number of Completed entries and these entries will cause the various To Do background processes to degrade over time. Therefore, you should periodically purge Completed To Do entries as they exist only to satisfy auditing and reporting needs.

Note: Different retention periods for different types of To Do entries. Keep in mind that the purge program allows you to retain different types of entries for different periods of time.

Setting Up To Do Options

The topics in this section describe how to set up To Do management options.

Next in This Section

- Installation Options

- Messages

- Feature Configuration

- Defining To Do Roles

- Defining To Do Types

- List of System To Do Types

- Implementing The To Do Entries

Installation Options

The following section describes configuration setup on the installation options.

Next in This Section

- To Do Information May Be Formatted By An Algorithm

- Set Additional Information Before A To Do Is Created

- Alerts

- Next Assignment Algorithm

To Do Information May Be Formatted By An Algorithm

A To Do Information algorithm may be plugged in on the installation record to format the standard To Do information that appears throughout the system. This algorithm may be further overridden by a corresponding plug-in on the To Do Type.

Set Additional Information Before A To Do Is Created

A To Do Pre-creation algorithm may be plugged in on the installation record to set additional information for a To Do entry before it is created. Algorithms of this type are used for two common purposes:

- Linking context specific data to the To Do entry using characteristics. For example, Oracle Utilities Customer Care and Billing provides an algorithm that attempts to link a related person, account, premise, service agreement or service point to a To Do entry based on its drill key value. Note, before you can set up this algorithm, you must define the characteristic types that you'll use to hold each of these entities. Also note that it is not necessary to define these characteristics as valid characteristic types on the To Do type.

- Overriding the Role of a To Do entry based on specific configuration related to the To Do’s context data. For example, Oracle Utilities Customer Care and Billing provides an algorithm to determine a To Do role based on overrides related to the account’s account management group or division.

Alerts

If your To Do entries reference characteristics related to your global context data and your product supports dashboard alerts generated by algorithms, you may want configure an algorithm to display an alert if the entry is Open or Being Worked On for the data currently in context.

Refer to your product’s documentation to determine if these types of alerts are supported.

Next Assignment Algorithm

If your organization opts to use the next assignment feature supported by the Current To Do dashboard zone, you need to plug-in a Next To Do Assignment algorithm into the installation options to determine the next To Do entry the user should work on. Make sure you provide users with security access rights to the zone's next assignment action.

Fastpath: Refer to the Current To Do zone for more information.

Messages

You need only set up new messages if you use algorithms to create To Do entries or prefer different messages than those associated with the base package's To Do types.

Feature Configuration

The base package is provided with a generic Activity Queue Management Feature Configuration type. You may want to set up a feature configuration of this type to define any To Do management related options supporting business rules specific to your organization.

For example, the base package provides the following plug-ins to demonstrate a business practice where To Do entries are only assigned to users with the proper skill levels to work on them.

- The base To Do Post Processing To Do Type algorithm F1-VAL-SKILL validates that a user has the necessary skill levels required to work on a given To Do entry.

- The base Next To Do Assignment installation options algorithm F1-NEXT-ASSG only assigns To Do entries to users that have the proper skills to work on them. This plug-in is only applicable if your organization practices work distribution "on demand."

You must set up such an Activity Queue Management feature configuration if you want to use any of the above base package plug-ins.

The following points describe the various Option Types provided with the base package:

- Skill. This option provides a reference to a skill category. For example, if you were using characteristics to represent skill categories then you should reference each characteristic type using this option.

- Override Skill. This option provides an override skill information reference for a specific message. For example, if you were using a To Do Type characteristic to specify an override skill category and level for a specific message category / number then you would reference this characteristic type using this option.

Note: Skill Setup. Refer to the description of the above base package algorithms for further details on how to setup skill level information.

Note: More Options. Your implementation may define additional options types. You do this by add new lookup values to the lookup field F1QM_OPT_TYP_FLG.

Note: Only one. The system expects only one Activity Queue Management feature configuration to be defined.

Defining To Do Roles

This section describes the control table used to maintain To Do roles.

Next in This Section

- To Do Role - Main

- To Do Role - To Do Types

To Do Role - Main

The Main page is used to define basic information about a To Do role.

To maintain this information, select Admin > General > To Do Role.

Description of Page

Enter a unique To Do Role and Description for the To Do role.

The grid contains the ID of each User that may view and work on entries assigned to this role. The First Name and Last Name associated with the user is displayed adjacent.

Note: System Default Role. The system supplies a default role F1_DFLT linked to each system To Do type. This is done so that To Do functionality may be tested prior to the creation of appropriate business oriented To Do roles.

Where Used

Follow this link to view the tables that reference CI_ROLE in the data dictionary schema viewer.

In addition, various “type” objects or algorithms may reference a To Do role to use when creating a To Do for a given business scenario. This is dependent on your specific product.

To Do Role - To Do Types

The To Do Types page defines the To Do types that may be viewed and worked on by users belonging to a given To Do role.

To maintain this information, select Admin > To Do Role > Search and navigate to the To Do Types page.

Description of Page

Enter the ID of each To Do Type whose entries may be viewed and worked on by the role.

Use As Default is a display-only field that indicates if the role is assigned to newly created entries of this type. You may define the default role for a given To Do type on the To Do Type maintenance page.

CAUTION:

If you remove a To Do type where this role is the default, you must define a new role as the default for the To Do type. You do this on the To Do Type maintenance page.

Defining To Do Types

This section describes the control table used to maintain To Do types.

Next in This Section

- To Do Type - Main

- To Do Type - Roles

- To Do Type - Sort Keys

- To Do Type - Drill Keys

- To Do Type - Message Overrides

- To Do Type - To Do Characteristics

- To Do Type - Algorithms

To Do Type - Main

The Main page is used to define basic information about a To Do type.

Fastpath: Refer to The Big Picture Of To Do Lists for more information about To Do types and To Do lists in general.

To maintain this information, select Admin > General > To Do Type.

CAUTION:

Important! If you introduce a To Do type, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Description of Page

Enter a unique To Do Type and Description for the To Do type.

Owner indicates if this entry is owned by the base package or by your implementation (Customer Modification).

Use the Detailed Description to provide further details related to the To Do Type.

Enter the default Priority of To Do entries of this type in respect of other To Do types. Refer to The Priority Of A To Do Entry for more information.

For To Do Type Usage, select Automatic if To Dos of this type are created by the system (i.e., a background process or algorithm). Select Manual if a user can create a To Do of this type online.

Define the Navigation Option for the page into which the user is transferred when drilling down on a To Do entry of this type.

Use Creation Process to define the background process, if any, that is used to manage (i.e., create and perhaps complete) entries of this type. A Creation Process need only be specified for those To Do types whose entries are created by a background process. Refer to To Do Entries Created By Background Processes for more information.

Use Routing Process to define the background process that is used to download entries of a given type to an external system, if any. A Routing Process need only be specified for those To Do types whose entries are routed to an external system (e.g., an Email system or an auto-dialer). Refer to To Do Entries May Be Routed Out Of The System for more information.

Use Message Category and Message Number to define the message associated with this To Do type's entries. Note: this message will only be used if the process that creates the To Do entry does not supply a specific message number. For example, the process that creates To Do entries that highlight bill segments that are in error would not use this message; rather, the entries are marked with the message associated with the bill segment's error.

Use the characteristics collection to define a Characteristic Type and Characteristic Value common to all To Do entries of this type. You may enter more than one characteristic row for the same characteristic type, each associated with a unique Sequence number. If not specified, the system defaults it to the next sequence number for the characteristic type.

Where Used

Follow this link to view the tables that reference CI_TD_TYPE in the data dictionary schema viewer.

To Do Type - Roles

The Roles page defines the roles who may view and work on entries of a given To Do type.

To maintain this information, select Admin > To Do Type > Search and navigate to the Roles page.

Description of Page

Enter each To Do Role that may view and work on entries of a given type. Turn on Use as Default if the role should be assigned to newly created entries of this type. Only one role may be defined as the default per To Do type.

Fastpath: Refer to To Do Entries Reference A Role for more information about roles and To Do entries.

To Do Type - Sort Keys

The Sort Keys page defines the various ways a To Do list's entries may be sorted. For example, when you look at the bill segment error To Do List, you have the option of sorting the entries in error number order, account name order, or in customer class order.

To maintain this information, select Admin > To Do Type > Search and navigate to the Sort Keys page.

CAUTION:

Do not change this information unless you are positive that the process / algorithm that creates entries of a given type stores this information on the entries.

Description of Page

The following fields display for each sort key.

Sequence is the unique ID of the sort key.

Description is the description of the sort key that appears on the To Do list.

Use as Default indicates the default sort key (the one that is initially used when a user opens a To Do list). Only one sort key may be defined as the default per To Do type.

Sort Order indicates whether the To Do entries should be sorted in Ascending or Descending order when this sort key is used.

Owner indicates if this entry is owned by the base package or by your implementation (Customer Modification).

To Do Type - Drill Keys

The Drill Keys page defines the keys passed to the application service (defined on the Main page) when you drill down on an entry of a given type.

To maintain this information, select Admin > To Do Type > Search and navigate to the Drill Keys page.

CAUTION:

Do not change this information unless you are positive that the process / algorithm that creates entries of a given type stores this information on the entries.

Description of Page

Navigation Option shows the page into which the user is transferred when drilling down on a To Do entry of this type.

The following fields display for each drill key.

Sequence is the unique ID of the drill key.

Table and Field are passed to the application service when you drill down on an entry of a given type.

Owner indicates if this entry is owned by the base package or by your implementation (Customer Modification).

To Do Type - Message Overrides

The Message Overrides page is used if you want To Do entries that reference a given message category / number to be routed to a specific To Do role (or suppressed altogether) or if you want to associate a script to a given message category / number.

Fastpath: Refer to To Do Entries Reference A Role and To Do Entries Can Be Rerouted Or Suppressed for more information.

To maintain this information, select Admin > To Do Type > Search and navigate to the Message Overrides page.

Description of Page

The following fields display for each override.

Message Category and Number allow the message to be overridden.

Exclude To Do Entry indicates if a To Do entry of this type that references the adjacent Message Category and Number should not be created.

Override Role indicates the to do role to which a To Do entry of this type that references the adjacent Message Category and Number should be addressed. This field is protected if Exclude To Do Entry is on.

Script indicates the script that should execute when a user drills down on a To Do entry of this type that references the adjacent Message Category and Number. This field is protected if Exclude To Do Entry is on. Refer to Working On A To Do Entry for more information.

To Do Type - To Do Characteristics

The To Do Characteristics page defines characteristics that can be defined for To Do entries of this type. The characteristic types for characteristics that are linked to the To Do entry as a result of a pre-creation algorithm do not need to be defined here.

To maintain this information, select Admin > General > To Do Type > Search and navigate to the To Do Characteristics page.

Turn on the Required switch if the Characteristic Type must be defined on To Do entries of this type.

Enter a Characteristic Value to use as the default for a given Characteristic Type when the Default switch is turned on. Use Sequence to control the order in which characteristics are defaulted.

To Do Type - Algorithms

The To Do Algorithms page defines the algorithms that should be executed for a given To Do type.

To maintain this information, select Admin > To Do Type > Search and navigate to the Algorithms page.

Description of Page

The grid contains Algorithms that control important To Do functions. If you haven't already done so, you must set up the appropriate algorithms in your system. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

The following table describes each System Event.

System Event

Optional / Required

Description

Calculate Priority

Optional

Algorithms of this type may be used to calculate a To Do entry's priority. They are called initially when a To Do entry is created and each time it gets updated so long as the To Do entry's priority has not been manually overridden. Once overridden, these algorithms are not called anymore.

Note that it is not the responsibility of the algorithms to actually update the To Do entry with the calculated priority value but rather only return the calculated value. The system carries out the update as necessary.

If more than one algorithm is plugged-in the system calls them one by one until the first to return a calculated priority.

Click here to see the algorithm types available for this system event.

External Routing

Optional

Algorithms of this type may be used to route a To Do entry to an external system.

The base package F1-TDEER background process invokes the algorithms for every To Do entry that its type references the process as the Routing Process and that the entry was not already routed. The background process marks an entry as routed by updating it with the batch control's current run number.

If more than one algorithm is plugged-in the batch process calls them one by one until the first to indicate the To Do entry was routed.

Click here to see the algorithm types available for this system event.

To Do Information

Optional

We use the term "To Do information" to describe the basic information that appears throughout the system to describe a To Do entry. The data that appears in "To Do information" is constructed using this algorithm.

Plug an algorithm into this spot to override the "To Do information" algorithm on installation options or the system default "To Do information" if no such algorithm is defined on installation options.

Click here to see the algorithm types available for this system event.

To Do Post-Processing

Optional

Algorithms of this type may be used to validate and/or further process a To Do entry that has been added or updated.

Click here to see the algorithm types available for this system event.

List of System To Do Types

The To Do types available to use with the product are found in the To Do Type page. In addition, they may be viewed in the application viewer's To Do type viewer. If your implementation adds To Do types, you may regenerate the application viewer to see your additions reflected there.

Implementing The To Do Entries

To enable the To Do entries visible in the To Do Type page and application viewer, you must configure the system as follows:

- Define the To Do roles associated with each To Do type and link the appropriate users to them. Once you have defined the roles appropriate for your organization's To Do types, remove the reference to this system default role F1_DFLT. Refer to To Do Entries Reference A Role for more information.

- For any To Do Type that is provided for a specific background process, the To Do simply needs to reference the appropriate Creation Background Process. When the background process is scheduled, To Dos are created based on the logic of the related background process. This applies to To Dos Created for Object-Specific Error Conditions and Dedicated To Do Background Processes.

- For any To Do Type that is provided for creation by an algorithm or other process, there may be configuration required to populate that To Do type as an algorithm parameter or as an attribute on a control table.

Note: Refer to the description of the To Do type for more information.

Background Processes

This chapter covers various topics related to background processes. Besides providing an overview of background process functionality, the various tools available within the application to define, submit and monitor background processes are covered.

Note: Your specific source application may have additional background process topics. Please refer to the documentation section that applies to your source application for more information.

Next in This Section

- Understanding Background Processes

- Defining Batch Controls

- On-Line Batch Submission

- Tracking Batch Processes

- Service Health Check

- The Big Picture of Requests

Understanding Background Processes

This section describes various topics related to the background processes that perform many important functions throughout your product such as:

- Processing To Do Entries

- Monitor processes that select records in a given state to progress them to their next state in their lifecycle

- Processes that purge data

- Processes that extract data

- And many more...

Next in This Section

- Background Processing Overview

- Parallel Background Processes

- Parameters Supplied To Background Processes

- Processing Errors

- Error Post-Processing Logic

- Post-Processing Logic

- Timed Batch Processes

- Monitor Background Processes

- Plug-in Driven Background Processes

- How to Re-extract Information

- How to Submit Batch Jobs

- How to Track Batch Jobs

- How to Restart Failed Jobs and Processes

- Assessing Level of Service

- System Background Processes

Background Processing Overview

While the system relies on a scheduler to secure and execute its background processes, there are additional issues that you should be familiar with:

- Batch control records are used for the following purposes:

- Define the code that executes the logic associated with the background process.

- For processes that extract information, the batch control record defines the next batch number to be assigned to new records that are eligible for extraction. For example, the batch control record associated with the process that routes To Do entries to an external system defines the next batch number to be assigned to new To Do entries that are configured with this batch control. When this To Do external routing process next runs, it selects all To Do entries marked with the current batch number (and increments the next batch number).

- The batch control record for each background process organizes audit information about the historical execution of the background process. The system uses this information to control the restart of failed processes. You can use this information to view error messages associated with failed runs.

- Many processes have been designed to run in parallel in order to speed execution. For example, the process that applies updates for a migration data set import for CMA can be executed so that multiple "threads" are processing a different subset of records (and multiple threads can execute at the same time). Batch control records associated with this type of process organize audit information about each thread in every execution. The system uses this information to control the restart of failed threads. Refer to Parallel Background Processes for more information.

- Some processes define extra parameters. These parameters are defined with the batch control. Default values may also be captured for each parameter. They will be used when the background process is submitted on-line.

The following diagram illustrates the relationships that exist for batch control records.

Results of each batch run can be viewed using the Batch Run Tree page.

Refer to Batch Scheduler Integration for information about the integration with the Oracle Scheduler.

Parallel Background Processes

Many processes have been designed to run in parallel in order to speed execution. This is referred to as running the process with multiple “threads”.

The system provides two strategies for distributing the data to the multiple threads.

- Thread Level SQL Select. This strategy is sometimes referred to as the “thread iterator” strategy. In this strategy, the batch job uses the primary key to figure out how to evenly distribute key ranges to each thread. Each thread is then responsible for selecting the records. In this strategy, the threads should also re-select the data periodically to release the cursor, which aids in performance. Note that this strategy is preferred but may only be used under the following conditions:

- The data from only one maintenance object is being processed.

- The primary key for the maintenance object is a single, numeric system generated key.

Note: Parameters may be used to override the low and high id. Refer to Parameters Supplied to Background Processes for more information.

- Job Level SQL Select. This strategy is sometimes referred to as the “standard commit” strategy. In this strategy, the keys for the records to be processed by the batch job are all selected first and stored in a temporary table. The batch job then supplies each thread with a range of keys that it should process. This strategy is used if multiple maintenance objects are being processed by the batch job; if the primary key of the maintenance object has multiple parts or if the primary key is non-numeric.

The multi-threading logic relies on the fact that primary keys for master and transaction data are typically system generated random keys. In addition, if the data is partitioned, it is expected to be partitioned based on the primary key.

Note: The detailed description in the metadata for each batch control provided with the system should indicate if it may be run in parallel. Note that the strategy used is not typically indicated in the detailed description.

Note: Overriding the thread ranges. Your implementation has the ability to override the thread ranges if certain data in your system takes longer to process. For example, imagine you have a single account in Oracle Utilities Customer Care and Billing that has thousands of service agreements (maybe the account for a large corporation or a major city). You may want to set up the thread ranges to put this large account into its own thread and distribute the other accounts to the other threads. To do this, you should create the appropriate batch thread records ahead of time in a status of Thread Ready ( 50) with the key ranges pre-populated. Note that the base product does not provide the ability to add batch thread records online. If you are interested in more information about this technique, contact Customer Support.

Next in This Section

- Optimal Thread Count

Optimal Thread Count

Running a background process in multiple threads is almost always faster than running it in a single thread. The trick is determining the number of threads that is optimal for each process.

Note: A good rule of thumb is to have one thread for every 100 MHz of application server CPU available. For example if you have four 450 MHz processors available on your application server, you can start with 18 threads to begin your testing: (450 * 4) / 100 = 18.

This is a rule of thumb because each process is different and is dependent on the data in your database. Also, your hardware configuration (i.e., number of processors, speed of your disk drives, speed of the network between the database server and the application server) has an impact on the optimal number of threads. Please follow these guidelines to determine the optimal number of threads for each background process:

- Execute the background process using the number of threads dictated by the rule of thumb (described above). During this execution, monitor the utilization percentage of your application server, database server and network traffic.

- If you find that your database server has hit 100% utilization, but your application server hasn't one of the following is probably occurring:

- There may be a problematic SQL statement executing during the process. You must capture a database trace to identify the problem SQL.

- It is also possible that your commit frequency may be too large. Commit frequency is a parameter supplied to every background process. If it is too large, the database's hold queues can start swapping. Refer to Parameters Supplied to Background Processes for more information about this parameter.

- It is normal if you find that your application server has hit 100% utilization but your database server has not. This is normal because, in general, all processes are CPU bound and not IO bound. At this point, you should decrease the number of threads until just under 100% of the application server utilization is achieved. And this will be the optimal number of threads required for this background process.

- If you find that your application server has not hit 100% utilization, you should increase the number of threads until you achieve just under 100% utilization on the application server. And remember, the application server should achieve 100% utilization before the database server reaches 100% utilization. If this proves not to be true, something is probably wrong with an SQL statement and you must capture an SQL trace to determine the culprit.

Another way to achieve similar results is to start out with a small number of threads and increase the number of threads until you have maximized throughput. The definition of "throughput" may differ for each process but can be generalized as a simple count of the records processed in the batch run tree. For example, in the Billing background process in Oracle Utilities Customer Care and Billing, throughput is the number of bills processed per minute. If you opt to use this method, we recommend you graph a curve of throughput vs. number of threads. The graph should display a curve that is steep at first but then flattens as more threads are added. Eventually adding more threads will cause the throughput to decline. Through this type of analysis you can determine the optimum number of threads to execute for any given process.

Parameters Supplied To Background Processes

This section describes the various types of parameters that are supplied to background processes.

General Parameters

The following information is passed to every background process.

- Batch code. Batch code is the unique identifier of the background process.

- Batch thread number. Thread number is only used for background processes that can be run in multiple parallel threads. It contains the relative thread number of the process. For example, if the billing process has been set up to run in 20 parallel threads, each of the 20 instances receives its relative thread number (1 through 20). Refer to Optimal Thread Count for Parallel Background Processes for more information.

- Batch thread count. Thread count is only used for background processes that can be run in multiple parallel threads. It contains the total number of parallel threads that have been scheduled. For example, if the billing process has been set up to run in 20 parallel threads, each of the 20 instances receives a thread count of 20. Refer to Optimal Thread Count for Parallel Background Processes for more information.

- Batch rerun number. Rerun number is only used for background processes that download information that belongs to given run number. It should only be supplied if you need to download an historical run (rather than the latest run).

- Batch business date. Business date is only used for background processes that use the current date in their processing. For example, a billing process may use the business date to determine which bill cycles should be downloaded. If this parameter is left blank, the system date is used. If supplied, this date must be in the format YYYY-MM-DD. Note: this parameter is only used during QA to test how processes behave over time.

- Override maximum records between commits. This parameter is optional and overrides each background process's Standard Commit. You would reduce this value, for example, if you were submitting a job during the day and you wanted more frequent commits to release held resources. You might want to increase this value when a background process is executed at night (or weekends) and you have a lot of memory on your servers.

- Override maximum minutes between cursor re-initiation. This parameter is optional and overrides each background process's Standard Cursor Re-Initiation Minutes. You would reduce these values, for example, if you were submitting a job during the day and you wanted more frequent commits to release held resources (or more frequent cursor initiations). You might want to increase these values when a background process is executed at night (or weekends) and you have a lot of memory on your servers.

- User ID. Please be aware of the following in respect of user ID:

- Both the user submitting the job and the user ID recorded on the batch submission should have access to the application service for the batch control that secures execution.

- Any batch process that stamps a user ID on a record it creates or updates uses this user ID in applicable processing.

- This user ID's display profile controls how dates and currency values are formatted in messages.

- Password. Password is not currently used.

- Language Code. Language code is used to access language-specific control table values. For example, error messages are presented in this language code.

- Trace program at start (Y/N), trace program exit (Y/N), trace SQL (Y/N) and output trace (Y/N). These switches are only used during QA and benchmarking. If trace program start is set to Y, a message is displayed whenever a program is started. If trace program at exist is set to Y, a message is displayed whenever a program is exited. If trace SQL is set to Y, a message is displayed whenever an SQL statement is executed. If output trace is set to Y, special messages formatted by the background process are written.

Note: The information displayed when the output trace switch is turned on depends on each background process. It is possible that a background process displays no special information for this switch.

Common Additional Parameters

Each batch control supports the definition of additional parameters. There are some additional parameters that are common to all batch processes or common to a specific type of batch process. The batch control should be delivered with the appropriate additional parameters. However, when new additional parameters are introduced, existing batch controls may not be updated with the new additional parameter.

The following table highlights the common parameters that may be linked to a batch control. Note that for batch parameters, although there is a sequence number that controls the displayed order of the parameter, the batch process does not use the sequence to identify a particular parameter but rather uses the parameter name. In some cases multiple parameter names are supported (a ‘camel case’ version and an ‘all caps’ version).

Parameter Name

Description

Additional Comments

MAX-ERRORS / maxErrors

Each of the batch processes has, as part of its run parameters, a preset constant that determines how many errors that batch process may encounter before it is required to abort the run. A user can override that constant using this parameter.

The input value must be an integer that is greater than or equal to zero. The maximum valid value for this parameter is 999,999,999,999,999.

DIST-THD-POOL

Each batch process executes in a thread pool. This parameter is only necessary if the batch process should execute in a different thread pool than the default thread pool.

The default thread pool name is DEFAULT.

emailMode

When the batch job is submitted with an associated email address, the default logic is to send an email when the job completes regardless of success or failure. Use this parameter to limit the email based on the status of the job when it ends.

Valid Values

- ERROR — send an email only when the job ends in Error status.

- SUCCESS — send an email only when the job ends in successfully.

- ALL — always send an email only when the job ends. (This is the default.)

The following parameters are only applicable to jobs that use the Thread Level SQL Select method of distributing work to threads as described in Parallel Background Processes.

overrideLowIdValue

Specifies a new low id to use in calculating the range for a thread. The framework by default assumes that the Id is between 0's (e.g. 000000000) and 9's (e.g. 9999999999), but this parameter will override the low value.

The parameter value can be an actual number or it can be set to auto. If auto is configured, it is set to the lowest current value on the database table associated with the background process.

overrideHighIdValue

Specifies a new high id to use in calculating the range for a thread. The framework by default assumes that the Id is between 0's (e.g. 000000000) and 9's (e.g. 9999999999), but this parameter will override the high value.

The parameter value can be an actual number or it can be set to auto. If auto is configured, it is set to the highest current value on the database table associated with the background process.

idRangeOverrideClass

Use this parameter to specify a custom class to do thread range calculation. During batch execution, this override class is instantiated and the setter methods called to initialize the Ids as required. The low and high getter methods are called to retrieve the high and low ids to be used for the run.

The class name specified must implement interface com.splwg.base.api.batch.BatchIdRangeOverride.

The following parameters are only applicable to jobs that perform a single commit, for example for extract batch jobs.

numRecordsToFlush

This parameter defines how frequently to flush the Hibernate cache to prevent high heap consumption and Out Of Memory Errors.

Specific Batch Parameters

Some background processes define additional parameters that are specific to their functionality. When a process receives additional parameters, they are defined and documented in the batch control entry in the application. They are also visible in the batch control viewer (part of the application viewer).

Next in This Section

- Indicating a File Path

Indicating a File Path

Some of the system background processes use extra parameters to indicate a File Path and/or File Name for an input file or an output file. For example, most extract processes use File Path and File Name parameter to indicate where to place the output file.

When supplying a FILE-PATH variable, the directory specified in the FILE-PATH must already exist and must grant write access to the administrator account for the product. You may need to verify a proper location with your systems administrator.

The syntax of the FILE-PATH depends on the platform used for the product application server. Contact your system administrator for verification. For example, if the platform is UNIX, use forward slashes and be sure to put a trailing slash, for example /spltemp/filepath/.

Processing Errors

When a background process detects an error, the error may or may not be related to a specific object that is being processed. For example, if the program finds an error during batch parameter validation, this error is not object-specific. However, if the program finds an error while processing a specific bill, this error is object-specific. The system reports errors in one of the following ways:

- Errors that are not object-specific are written to the error message log in the Batch Run Tree.

- Some batch processes create entries in an "exception table" for certain object-specific errors. For example, an error detected in the creation of a bill in Oracle Utilities Customer Care and Billing may be written to the bill exception table. If an error is written to an exception table, it does not appear in the batch run tree. For each exception table, there is an associated to do entry process that creates a To Do Entry for each error to allow a user to correct the problem on-line.

- For some background processes, errors that do not result in the creation of an exception record may instead generate a To Do entry directly. For these processes, if you wish the system to directly create a To Do entry, you must configure the To Do type appropriately. Refer to To Do entry for object-specific errors for information about configuring the To Do type. If the background process detects an object specific error and you have configured the system to create a To Do entry, the error is not written to the batch run tree. If you have configured your To Do type to not create To Do entries for certain errors, these errors are written to the batch run tree.

Note: Some processes create exceptions and To Do entries. It is possible for a background process to create entries in an exception table and create To Do entries directly, depending on the error. Consider batch billing in Oracle Utilities Customer Care and Billing; any conditions that cause a bill or bill segment to be created in error status result in a record added to the bill exception table or the bill segment exception table. However, any object-specific error that is not related to a specific bill or bill segment or any error that prevents a bill or bill segment from being created may result in a To Do entry for the object-specific error.

Error Post-Processing Logic

The product supports executing one or more algorithms when a batch process encounters an error that causes execution to stop. This allows for some special processing to occur to handle the failure of the batch job. Algorithms for this plug-in spot receive the batch control, batch run number, batch processing business date, number of threads and the list of the ad hoc parameters of the batch job. The following are some examples of functionality that may be executed when a batch job fails:

- Another object or record that is monitoring the batch job may have its status updated to reflect the batch status.

- An outbound message service may be invoked to perform a task related to the failure.

Note that the units of work for all threads are committed prior to executing the error post-processing logic.

Post-Processing Logic

The product supports executing one or more algorithms after all the threads of a given batch job have completed. This allows for some special processing to occur at the end of a batch job. Algorithms for this plug-in spot receive the batch control, batch run number, batch processing business date, number of threads and the list of the ad hoc parameters of the batch job. The following are some examples of functionality that may be executed at the end of a batch job:

- Another dependent batch job can be kicked off. Note that this use case is only needed when the multiple dependent jobs are not part of a scheduler (which can also detect the successful end of one batch job so as to submit the next job).

- Statistics for the batch run may be analyzed and based on results, a To Do Entry may be sent to an administrator.

- If the current batch job is processing a large number of child records in multiple threads, a parent record could be updated to a different status or with some other audit information.

Note that the units of work for all threads are committed prior to executing the post-processing logic. The algorithm should perform standard error handling. If an error occurs in one of the post-processing algorithms, the overall batch job’s status is set to Error so that it can be re-submitted to retry the logic in the finalize step.

Timed Batch Processes

Most batch jobs are submitted via a batch scheduler. In the absence of a scheduler, a batch control may be configured as “timed” triggering the framework to monitor and schedule these batch jobs as defined by the timer interval. The timer interval defines the desired interval between starts (in seconds). The system schedules new batch runs at each interval if the last instance of the job has completed.

When configuring a batch control as “timed”, other default information must be provided, including the User ID and Language to use for submitting the job and the email address for notification, if desired.

Timed batch controls also include an Active setting, allowing for an implementation to temporarily stop further executions of the batch job (but retain the other timer settings).

Timed jobs are controlled by the default threadpool and not by a scheduler. When the DEFAULT threadpoolworker starts it will start executing any job for a Batch Control configured as Timed with the Timer Active set to Yes. This is whether the batch daemon or batch server is enabled or not.

Monitor Background Processes

In many areas of the system, functionality is driven from business object configuration as a BO driven record progresses through its lifecycle. Refer to Business Object Lifecycle for details. As part of that functionality, it is possible that a background process, called a monitor batch process, is used to execute functionality for the record. A single program is provided for the BO monitor functionality and parameters are used to limit the records processed by maintenance object and other optional parameters that may further limit the records. The product typically provides at least one monitor batch control for each maintenance object that supports a configurable lifecycle on its business object.

This topic highlights the parameters supported by the monitor batch job. Not all parameters are applicable to all maintenance objects and therefore may not be configured on a give base monitor batch control.

Parameter Name

Description

Comments

maintenanceObject

Maintenance Object

For most base delivered batch controls, this parameter is delivered already populated with the value of the maintenance object value. Note that it is supported to leave this value blank, at which point, the program will determine the maintenance object (objects) to process by looking for an MO that refers to this batch control record as an option.

isRestrictedByBatchCode

Restrict by Batch Code

Set this to true to indicate whether the process should only select records that explicitly refer to this batch control on its current BO state. This is also referred to as “deferred” mode. If set to false, the program includes all records that refer to the current batch control in its BO state and records that don’t refer to any batch control in its current state (but monitor algorithms exist in the current state). This is commonly referred to as “periodic” mode. Note that if the value is not set at all, the program will determine whether to run it as “deferred” or “periodic” based on whether the batch code is configured on the MO option as a State Monitor Process (“deferred”) or a Periodic Monitor Process.

restrictToType

Restrict by Related Type

This parameter is only applicable to maintenance objects that have a related ‘type’ object and the maintenance object has configured an option indicating the field for the related type column. This parameter may be used to limit the processing to records that are in the indicated type.

restrictToBusinessObject

Restrict by Business Object

This parameter may be used to limit the processing to records that are in the indicated business object.

restrictToStatus

Restrict by Status

This parameter may be used to limit the processing to records that are in the indicated status.

sampleRecordNumber

Sample Record Number

This is not a commonly used parameter. It is only applicable when the monitor is used for a business use case that supports processing a subset of the records during a testing phase. For example, if the process is validating a large number of records, it may be an option to only validate every 100 records to determine if there are repeated validation errors that may indicate a common problem that may be solved to fix many errors.

Also note that when submitting a monitor process with multiple parallel threads, the program will use a Thread Level SQL Select strategy unless any of the following are true (in which case it will use the Job Level SQL Select strategy:

- The input maintenance object is left blank and the program finds more than one maintenance object that refers to this batch control in its options.

- A single MO is applicable but it has a multi-part primary key.

- A single MO is applicable and it has a single primary key, but it is a user defined key instead of a system generated key.

- The sample record number parameter is populated.

Plug-in Driven Background Processes

Although the product is delivered with a rich library of background processes, implementations may have business requirements that require new processes to be introduced. It is possible for an implementation to write a background process from scratch using a base process as a template. However, the product also provides base background processes that call algorithms to do the work that is needed. These are called plug-in driven background processes. There are two major types of plug-in driven batch processes:

- Processes that act on records that are stored in the database in the system. These types of processes require SQL to select the records along with the logic to process the records.

- Processes that import data from a file and store new records in the system as a result. These types of processes require an algorithm that is able to map the data from the file to appropriate new records in the system

The subsequent sections provide more detail about the two types of plug-in driven background processes.

Next in This Section

- Processing System Records

- Uploading Records

Processing System Records

Process that retrieve records in the system and do some action on them require an algorithm to select the records to be processed and another algorithm to process the records. The base processes implement standard background process functionality including parallel background process logic and the ability to create To Do entries for errors. This allows for an implementation to take advantage of the pre-built support and provide plug-ins that include the logic that is unique to the specific use case.

The system provides the following processes that support plug-ins for selecting and processing the records:

- Ad-hoc Process. This background process is provided for implementations that have some custom business logic that needs to be performed on a group of records. The base batch control Plug-in Driven Generic Template (F1-PDBG) may be used as a template.

- Extract Process. This background process is provided for implementations that have extract files to produce for integration with external systems. The process includes parameters to configure the file path and file name for the created file along with other parameters to control how the file is formatted. The base batch control Plug-in Driven Extract Template (F1-PDBEX) may be used as a template.

The following sections provide more information about implementing this type of functionality.

Select Records Algorithm

The first important algorithm to design when implementing a plug-in driven batch process is the Select Records algorithm, plugged in on the batch control page. This algorithm type must define the first parameter as the SQL. The batch job will directly access the SQL parameter value in the metadata (rather than invoking the algorithm). All other parameters are available for the algorithm to use for its own logic.

In addition, when invoking the algorithm, it must return the strategy to use (Thread Level SQL Select or Job Level SQL Select. Refer to parallel background processes for more information about the two strategies and when to use each. When choosing the Thread Level SQL Select strategy, the algorithm should return the name of the primary key in the Key Field parameter. In addition, the SQL should include a BETWEEN clause that includes the bind variables for the low and high ID for the ranges. See below for the bind variable syntax.

If the SQL statement includes variables that are determined at execution time, it must use bind parameters. Bind parameters are referenced in the SQL statement using a colon and a parameter name (for example :parameter). There are some variables provided by the system that are populated by the batch job at execution time. These have f1. as its prefix.

The system supports the following pre-defined bind parameters:

- :f1.lowID and :f1.highID - these should be used in the BETWEEN clause for the Thread Level SQL Select strategy. The batch job will substitute the appropriate ID range as required.

- :f1.batchCode and :f1.batchNumber - these are common attributes of the batch control that are referenced on a record for selection purposes. Note that the batch run number is set according to whether the batch job is a re-run of a previous run or not.

- :f1.businessDate - the batch job will populate the input batch business date, if populated otherwise the current date.

For any other custom parameters, the Select Records algorithm may return one or more sets of field name / variable name / value where the variable name matches a bind variable in the SQL. The field name provides information about data type and length that assists the SQL binding logic to properly substitute the values. Note that the variable name cannot start with f1. as its prefix. The batch job will use the value returned by the algorithm to set the bind parameter in the SQL statement.

The plug in spot receives a list of the ad hoc parameters for the batch job as name / value pairs. If the list includes parameters whose values are to be used in selecting records, your algorithm may be used to identify the relevant batch parameter passed as input and populate the field name and output bind variable appropriately.

The product provides a base algorithm type for this plug-in spot that simply defines a parameter for the SQL. It also includes parameters for the strategy and the key field name. This algorithm type may be used by any custom batch process where the SQL does not rely on any special bind variables that must be determined. Simply create an algorithm for the algorithm type and provide the appropriate SQL. Refer to the algorithm type Select Records by Predefined Query (F1-PDB-SR) for more information.

Process Records Algorithm

The other important algorithm to design when implementing a plug-in driven batch process is the Process Record algorithm, plugged in on the batch control page. This algorithm is called for each record selected for the process. It receives all the information that was selected from the Select Records plug-in.

For the ad-hoc processing batch process, algorithms plugged into this spot are responsible for doing the work for each record based on the desired logic.

For the extract batch process, algorithms plugged into this spot are responsible for returning the data that should be written to the file in one or more XML instances along with the schema name(s) that describes the XML instance(s). For XML output format, the batch process will write the XML instance data as returned by the plug-in. For fixed position or CSV output format, the batch process will convert the XML instance data to the appropriate format and add it to the file.

Also note that algorithms for this plug-in spot will be passed two Booleans, isFirst and isLast, to indicate if the current work unit is the first and/or last for that thread. This allows for the plug-in to do additional work if needed. Note that the isFirst indication is available for both types of batch processes, ad-hoc and extract. However, the isLast indication is only applicable for the file extract batch. For the ad-hoc batch process this value will always be set to false. Extracts will always execute in a single database transaction. In a single transaction run, any error causes the run to be aborted so that it restarts from the beginning when resubmitted. This is done to avoid partial files being written along with inaccurate setting of the isLast element.

The product provides a base algorithm type for this plug-in spot that illustrates the technique to follow when implementing an extract type of plug-in driven background process. Refer to the algorithm type General Process - Sample Process Record Extract (F1-GENPROCEX) for more information.

Configuring a New Process

The following points summarize the steps needed to implement a new background process that act on records in the system using plug-ins for the specific functionality:

- Verify the SQL that the background process should execute. Keep in mind that all the data selected in the SQL is available to pass to the plug-in that processes the records. If the performance of the background process is important, be sure to consult with a DBA when designing the SQL.

- If the SQL does not require any custom variables to substitute at runtime, create an algorithm for the base algorithm type F1-PDB-SR and configure the SQL. In addition, configure the strategy and the primary key name (for the Thread Level SQL Select strategy).

- If the SQL requires custom variables, a new plug-in script must be designed and coded to populate the variable names and values using the algorithm entity Batch Control - Select Records. Besides defining the variables, the algorithm must also indicate the strategy and the primary key name (for the Thread Level SQL Select strategy). Define the algorithm type for the newly created script. The first parameter of the algorithm type must be the SQL as illustrated in the base algorithm type. Note that the other parameters are available for use by this algorithm type if needed. Define the algorithm, populating the SQL as appropriate (using the custom variables).

- Design the logic required for each record and create a plug-in script where the algorithm entity is Batch Control - Process Record. Note that the plug-in receives all the information selected in the SQL defined in the Select Records plug-in

- For an ad-hoc process, the algorithm should perform whatever process is required based on the business use case. Note that the background process is responsible for committing the records.

- For an extract process, the algorithm is responsible for returning one or more schema instances populated with information that should be written to the file. If an existing schema satisfies the output requirements, it may be used. Otherwise, define a data area to indicate the output format of the records as appropriate.

In either case, define the algorithm type and algorithm for the newly created script.

- Create a batch control by duplicating the appropriate base template as per the type of background process needed. Plug in the algorithms created above and configure the parameters as appropriate. Note that you may configure custom ad hoc parameters on the batch control if required. Both base and custom batch parameter values are available to the Select Records and Process Records plug in algorithms.

Uploading Records

The base product provides a background process to upload data from a file. The batch control Plug-in Driven File Upload Template (F1-PDUPL) may be used as a template. The process includes parameters to configure the file path and file name for file to upload along with other parameters to control how to handle missing files and how to rename the file once processed. Refer to the description of the batch control and its parameters for more information.

This background process requires an algorithm plugged into the plug-in spot File Upload. This plug-in is called once for a given file. The batch process opens the file and passes to the algorithm the file reader element. The algorithm associated with the batch control is responsible for using provided APIs to read the content of the file and store the data in appropriate table(s) (for example, an appropriate staging table).  The base provided process supports uploading multiple files and may be run mutli-threaded to process multiple files. Each file is processed by one call to the File Upload algorithm and supports a single commit for the records uploaded in a given file.

Note: Plug-in scripts written to implement this type of algorithm must use Groovy as the APIs are not accessible using the scripting language. Refer to Additional Coding Options For Server Scripts for more information.

Note that this step in the upload of data is only one part of a typical upload end-to-end process. This step is sometimes referred to in the product as "Process X". The goal of this step is to get records from a file into database records, with minimal validation and processing. The data should be stored in records that are then processed by a second step (often referred to in the product as the "upload" step, for example "Payment Upload"). The second step, independent of the plug-in driven batch process described here, is responsible for validating the data and should be able to be threaded by individual records and have proper error handling for individual records. Note that depending on the type of data being uploaded, the product may already supply appropriate tables that the plug-in driven upload process may populate. These could be staging tables, such as payment upload staging. Or they may be records with business objects that have a lifecycle designed to handle uploaded data, for example Business Flag. In such cases, the product will typically supply out-of-the-box background processes to validate and further process the data and finalize the upload. If the data to upload does not already have a base provided staging table, be sure to work with your implementation team to identify an appropriate table to use for the plug-in driven batch upload. In addition, confirm the design for the second step that is responsible for the detailed validation and finalization of the data.

The product supplies sample algorithms to illustrate calling the supplied APIs for processing different types of source data: comma delimited, fixed position and XML. In every case, the sample data supported by the upload uses 'degree day' information to illustrate the process. The system provides sample target records (based on the Fact maintenance object) in order to illustrate the step to store records based on the input data. Note that only sample plug-in scripts have been provided. No algorithm, algorithm type or batch control is configured to use the sample plug-in scripts. To view the scripts, navigate to the Script page, search for a Script Type of Plug-in Script and Algorithm Entity of Batch Control - File Upload and look for the 'Sample' scripts.

Note that the sample plug-in scripts provided by the product are supplied to illustrate use of the provided APIs. They should not be considered a template for how to implement a plug-in script for a real use case. The following highlight some points to consider when designing a file upload algorithm:

- Error handling / resolution. The sample plug-in scripts do some basic error handling related to the data to illustrate error handling. However, any errors found in this step require processing of the whole file to stop. As such, this plug-in should only report errors that are not possible to fix, but where the whole file should be rejected. If there are errors that can be adjusted in the data, then the recommendation is to not check for those errors at this step. Rather, this plug-in should simply populate the appropriate staging tables and let the next step check for validity. As described above, the next step should include the ability to mark individual records in error, allowing for users to fix the data and retry.

- Target tables. The sample plug-in scripts use Fact as the target for the resulting insert statements. As mentioned above, the decision of where to store the uploaded data must be carefully considered. There may already be existing tables that are specific to a given use case. If the data being uploaded does not have existing tables to use, review the product to verify what existing tables may be useful, such as Inbound Sync Request or Service Task. Be sure that the tables chosen support error handling, either out-of-the box or via designing an appropriate business object with a lifecycle that supports an error status and the ability to resolve the error. Also note that the Sample Flat File Upload plug-in illustrates a header record / detail record scenario. In this case, the header record is linked to the child record via a CLOB element. This is not the recommended technique. In a real use case, the header record should be linked to the child record via a separate database column to allow for searching.

Configuring a New Process

The following points summarize the steps needed to implement a new file upload background process:

- Verify the details of the data in the upload file and map the data to fields in one or more appropriate tables in the system.

- Design the logic required for reading the record details and identifying each record to properly create the insert statements for storing the data. The sample plug-in scripts provided by the product illustrate using the various APIs available for use. Create a plug-in script where the algorithm entity is Batch Control - File Upload. Create an appropriate algorithm type and algorithm for this plug-in script.

- Create a batch control by duplicating the base template. Plug in the algorithm created above and configure the parameters as appropriate. Note that you may configure custom ad hoc parameters on the batch control if required. Both base and custom batch parameter values are available to the File Upload algorithm.

How to Re-extract Information

If you need to recreate the records associated with an historical execution of an extract process, you can - simply supply the desired batch number when you request the batch process.

How to Submit Batch Jobs

Most batch jobs are submitted via a batch scheduler. Refer to Batch Scheduler Integration for information about the integration with the Oracle Scheduler.

Batch jobs may be configured as Timed, which means they will automatically be run based on the timer frequency.

In addition, you can manually submit your adhoc background processes or submit a special run for one of your scheduled background processes using the online batch job submission page.

How to Track Batch Jobs

You can track batch jobs using the batch process pages, which show the execution status of batch processes. For a specified batch control id and run id, the tree shows each thread, the run-instances of each thread, and any messages (informational, warnings, and errors) that might have occurred during the run.

Fastpath: For more information, refer to Tracking Batch Processes.

How to Restart Failed Jobs and Processes

Every process in the system can be easily restarted if it fails (after fixing the cause of the failure). All you have to do is resubmit the failed job; the system handles the restart.

Assessing Level of Service

For some background processes, an implementation may wish to supply an algorithm that checks some conditions to assess whether or not the process is performing as expected. This algorithm could be simply verifying that the batch process is running as frequently as expected. Or it could be used to check the performance of the job to see if it is running as efficiently as expected. Or it could analyze the data processed by the background process to assess whether there may be some problem with the quality of the data.

The system provides a Level of Service plug-in spot on batch control to configure the appropriate algorithm for a given background process, if desired. The algorithm is expected to return a value to indicate the ‘level of service’ determined along with a message indicating the reason for the value. The following Level of Service values are supported:

- Normal. Indicates that the algorithm did not detect any issues.

- Warning. Indicates that the algorithm found some issues that may or may not indicate a problem.

- Error. Indicates that the algorithm found some issues that should be investigated.

- Disabled. Indicates that the algorithm could not properly execute the level of service logic.

When viewing a batch control record, if there is a level of service algorithm configured, its logic is executed and the results are displayed. The level of service is also part of the Health Check service.

System Background Processes

Note: List of system background processes. The list of background processes provided in the base product may be viewed in the application viewer's batch control viewer. In addition if your implementation adds batch control records, you may regenerate the application viewer to see your additions reflected there.

Defining Batch Controls

The system is delivered with all necessary batch controls. Implementations may define default values for parameters. In addition, implementations may define their own background processes.

To view background processes, open Admin > System > Batch Control. Refer to Background Processing Concepts for more information.

CAUTION:

Important! If you introduce a new batch process, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Description of Page

Enter an easily recognizable Batch Process and Description for each batch process.

Owner indicates if this batch control is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a batch control. This information is display-only.

Use the Detailed Description to describe the functionality of the batch process in detail.

Enter the Application Service that is used to provide security for submission requests for the batch control. The application service must have an Access Mode of Execute. Refer to Granting Access To Batch Submission for more information.

Use Batch Control Type to define the batch process as either Timed or Not Timed. A Timed batch process will be automatically initialized on a regular basis. A Not Timed process needs to be run manually or through a scheduler.

Use Batch Control Category to categorize the process for documentation purposes. The base values provided are as follows:

- Ad Hoc. Processes of this type are run on an ad hoc basis, only when needed. For example, if there is a process to do a mass cancel / correction of data, it would only be run when a situation occurs requiring this.

- Extract. Extract processes extract information that is interfaced out of the system. Processes of this type typically extract records marked with a given run number. If the requester of the process does not supply a specific run number, the system assumes that the latest run number should be extracted. If you need to re-extract an historical batch, you simply supply the respective run number when you request the batch process.

- ILM. Information Lifecycle Management jobs are crawler background processes that are associated with the ILM based storage solution.

- Monitor. Processes of this type are processes related to business objects with a lifecycle state that defines monitor algorithms. The monitor process selects records in a given state and executes its algorithms, which may cause the record to transition to another state or may trigger some other logic to occur. Using configuration, the monitor process may target only specific records. Refer to Monitoring Batch Processes for more information. Note that these types of background processes can be considered a subset of Process What’s Ready

- Process What’s Ready. Processes of this type create and update records that are “ready” for processing. The definition of “ready” differs for every process. For example, a payment upload process creates payments for every record that is pending. An overdue event monitor activates pending overdue events that have reached their trigger date.

- Purge. Processes of this type are used to purge historical records from certain objects that generate a large number of entries and may become unwieldy over time.

- To Do Entry. Processes of this type are used to detect a given situation and create or complete a To Do Entry. Refer to To Do Entries Created by Background Processes for more information.

- The following categories are related to the data conversion / migration processes, which are not applicable to all products:

- Conversion. Processes of this type are dedicated to converting or migrating data from external applications into the product.

- Object Validation. Processes of this type are dedicated to validate data within objects for conversion or migration purposes.

- Referential Integrity. Processes of this type are dedicated to validate referential integrity within objects for conversion or migration purposes.

Note: Additional categories may be introduced by your specific product.

If the batch process is Timed, then the following fields are available:

- Timer Interval is the number of seconds between batch process submissions. The system will start the next run this many seconds from the start time of the previous run.

- User ID is the ID under which the batch process will run.

- Email Address is the Email address to be used for notification if the batch process fails.

- Timer Active allows you to temporarily switch off the timer while retaining the other settings for the timed job.

- Batch Language is the language associated with the batch process.

Use Program Type to define if the batch process program is written in Java or Java (Converted), meaning that the program has been converted into Java.

Note: Java (Converted) program types are not applicable to all products.

Use Program Name to define the Java class / program associated with your batch process:

Note: View the source. If the program is shipped with the base package, you can use the adjacent button to display the source code of this program in the Java docs viewer.

Level of Service shows the output of the level of service algorithm for the batch control. It shows the level of service lookup value along with a message indicating the reason for the output value. Note that if no level of service algorithm is found, then the value Disabled is shown with a message indicating that no algorithm is provided for this batch control.

The Last Update Timestamp, Last Update Instance and Next Batch Nbr are used for audit purposes.

Turn on Accumulate All Instances to control how this batch control is displayed in the Batch Run Tree. If checked, the run statistics (i.e., "Records Processed" and "Records in Error") for a thread are to be accumulated from all the instances of the thread. This would include the original thread instance, as well as any restarted instances. If this is not turned on, only the ending (last) thread instance's statistics are used as the thread's statistics. This may be preferred for certain types of batch processes where the accumulation would create inaccurate thread statistics, such as those that process flat files and, therefore, always start at the beginning, even in the case of a restart.

The following fields are default values that are used when a batch job is submitted for the batch control:

- Use Thread Count to control whether a background process is run single threaded or in multiple parallel threads. This value defines the total number of threads that have been scheduled.

- Select Trace Program Start if you want a message to be written whenever a program is started.

- Select Trace SQL if you want a message to be written whenever an SQL statement is executed.

- Use Override Nbr Records to Commit to define the default number of records to commit. This is used as the default value for timed jobs as well as online submission of jobs that are not timed.

- Select Trace Program Exit if you want a message to be written whenever a program is exited.

- Select Trace Output if you want a message to be displayed for special information logged by the background process.

For more information about these fields, see Batch Job Submission - Main

The parameter collection is used to define additional parameters required for a particular background process. The following fields should be defined for each parameter:

Sequence. Defines the relative position of the parameter.

Parameter Name. The name of the parameter as defined by the background process program.

Description. A description of the parameter.

Detailed Description. A more detailed description of the parameter.

Required. Indicates whether or not this is a required parameter.

Parameter Value. The default value, if applicable. Note that an implementation may define a default value for base provided batch controls.

Security. Indicates whether the system should Encrypt the parameter value or not. A value of Encrypt means that the parameter value is stored in the database and written to the log files using encryption. In addition, the parameter is written to the log files with asterisks. The setting applies to values entered here as well as in the online Batch Submission. If there is no need to secure the parameter value, use the default setting of None.

Owner Indicates if this batch process is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add a batch process. This information is display-only.

Next in This Section

- Batch Control - Algorithms

Batch Control - Algorithms

Use this page to maintain a batch control's algorithms. Open this page using Admin > System > Batch Control and then navigate to the Algorithms tab.

Description of Page

The Algorithms grid contains algorithms that control important functions for instances of this batch control. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence Number and Algorithm for each system event. You can set the Sequence Number to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

- Owner indicates if this is owned by the base package or by your implementation (Customer Modification).

The following table describes the System Events.

System Event

Optional / Required

Description

Error Post-Processing

Optional

Algorithms of this type are called if the batch process fails to complete due to an error. Multiple algorithms are allowed and are executed in sequence order. Refer to Error Post-Processing Logic for more information.

Click here to see the algorithm types available for this system event.

File Upload

Optional

Algorithms of this type are only applicable to plug-in driven background processes and are used to upload all records for a file. Note that only one algorithm is allowed.

Click here to see the algorithm types available for this system event.

Level of Service

Optional

Algorithms of this type are called to determine the Level of Service provided by a batch control. Note that only one algorithm is allowed. Refer to Assessing Level of Service for more information.

Click here to see the algorithm types available for this system event.

Post-Processing

Optional

Algorithms of this type are called after all threads are complete. Multiple algorithms are allowed and are executed in sequence order. Refer to Post-Processing Logic for more information.

Click here to see the algorithm types available for this system event.

Process Record

Optional

Algorithms of this type are only applicable to plug-in driven background processes and are used to process a specific record.

Click here to see the algorithm types available for this system event.

Select Records

Optional

Algorithms of this type are only applicable to plug-in driven background processes and are used to define the SQL to use to select the records to process. Only one algorithm is allowed.

Click here to see the algorithm types available for this system event.

Note: You can add new system events. Your implementation may want to add additional batch control oriented system events. To do that, add your new values to the customizable lookup field F1_BATCH_CTRL_SEVT_FLG.

On-Line Batch Submission

The on-line batch submission page enables you to request a specific background process to be run. When submitting a background process on-line, you may override standard system parameters and you may be required to supply additional parameters for your specific background process. After submitting your background process, you may use this page to review the status of the submission.

The following topics further describe logic available for on-line submission of background processes.

Next in This Section

- Batch Submission Creates a Batch Run

- Jobs Submitted in the Background

- Email Notification

- Running Multi-Threaded Processes

- Batch Jobs May End in Error

- Submitting Jobs in the Future

- Lifecycle of a Batch Job Submission

- Granting Access To Batch Submission

- Batch Job Submission - Main

Batch Submission Creates a Batch Run

When you request a batch job to be submitted from on-line, the execution of the desired background process will result in the creation of a batch run. Just as with background processes executed through your scheduler, you may use the Batch Run Tree page to view the status of the run, the status of each thread, the run-instances of each thread, and any messages that might have occurred during the run.

Note: Your on-line submission record is assigned a status value so that you may know whether your job has been submitted and whether or not it has ended, however, it will not contain any information about the results of the background process itself. You must navigate to the Batch Run Tree page to view this detail.

Jobs Submitted in the Background

When you save a record on the batch job submission page, the batch job does not get submitted automatically. Rather, it saves a record in the batch job table. A special background process will periodically check this table for pending records and will execute the batch job. This background process will update the status of the batch job submission record so that a user can determine when their job is complete.

Note: At installation time, your system administrator will set up this special background process to periodically check for pending records in the batch job submission table. Your administrator will define how often the system will look for pending records in this table.

It should be noted that this special background process only submits one pending batch job submission record at a time. It submits a job and waits for it to end before submitting the next pending job.

Note: If you request a batch job to be run multi-threaded, the special background process will submit the job as requested. It will wait for all threads to complete before marking the batch job submission record as ended. Refer to Running Multi-threaded Processes for more information.

Email Notification

If you wish the system to inform you when the background process completes, you may supply your email address. The email you receive will contain details related to the batch job's output; similar to the job results you would see from your batch scheduler.

Note: This assumes that during the installation process, your system administrator configured the system to enable email notification. Your administrator may also override the amount of detail included in the email notification.

Running Multi-Threaded Processes

Many of the system background processes may be run multi-threaded. When submitting a background process on-line, you may also run a multi-threaded process or run a single thread of a multi-threaded process. The fields Thread Count and Thread Number on the batch submission page control the multi-threaded process requests:

- To run a multi-threaded process, indicate the number of threads in Thread Count and enter 0 in the Thread Number.

- To run a single thread in a multi-threaded process, indicate the number of threads in Thread Count and indicate the Thread Number you would like to run.

- To run a process as a single thread, enter Thread Count = 1 and Thread Number = 1. This will execute the background process single-threaded.

Note: When running a multi-threaded process, the special background process will wait until all threads are complete before marking the batch job submission record as Ended.

Batch Jobs May End in Error

It is possible for your background process to end with an error. When this occurs, your batch job submission record will still be marked as Ended. You will need to navigate to the Batch Run Tree page to determine the status of the batch run.

Submitting Jobs in the Future

If you wish to request a batch job to be submitted in the future, you may do so when creating your batch job submission record by entering a future submission date. The special background process, which looks for pending records in the batch job submission table, will only submit batch jobs that do not have a future submission date.

Lifecycle of a Batch Job Submission

The following diagram illustrates the lifecycle of a batch job submission record.

Pending — Records are created in Pending status. Records in this state are put in a queue to be submitted.

Canceled— Users may cancel a pending record to prevent the batch job from being submitted.

Started— Once a pending record has been submitted for processing, its status will be changed to Started. Records in this status may not be canceled.

Ended— When the batch job has finished processing, its status will be changed to Ended. Note that records in Ended status may have ended in error. Refer to Batch Jobs May End in Error for more information.

Granting Access To Batch Submission

Every batch control must reference an application service. When you link a batch control to an application service, you are granting all users in the group the ability to submit the associated batch job for execution.

Fastpath: Refer to The Big Picture Of Application Security for information about granting users access rights to an application service.

When the batch control is added to the batch job table, the system checks if both the user submitting the job and the user ID recorded on the batch submission record have access rights. Application security does not apply when viewing a batch control or an associated batch run.

Note: Base batch controls will be associated with base owned application services by default. Implementations will need to ensure the appropriate user groups are linked to these application services.

Batch Job Submission - Main

This page allows you to submit a batch job on-line. Navigate to this page using Menu > Tools > Batch Job Submission.

Description of Page

The Batch Job ID is a system generated random number that identifies a particular submission.

To submit a batch job, choose the Batch Code for the process you wish to submit.

Note: List of system background processes. The list of background processes provided in the base product may be viewed in the application viewer's batch control viewer.

The following parameters are provided with each background process:

Thread Number is used to control whether a background processes is run single threaded or in multiple parallel threads. It contains the relative thread number of the process. For example, if the process has been set up to run in 20 parallel threads, each of the 20 instances receives its relative thread number (1 through 20). Refer to Running Multi-threaded Processes for more information about populating this field.

Note: Not all processes may be run multi-threaded. Refer to the description of a batch control to find out if it runs multi-threaded.

Thread Count is used to control whether a background processes is run single threaded or in multiple parallel threads. It contains the total number of threads that have been scheduled. For example, if the process has been set up to run in 20 parallel threads, each of the 20 instances receives a thread count of 20. Refer to Running Multi-threaded Processes for more information about populating this field.

Batch Rerun Number is only used for background processes that download information that belongs to given run number. It should only be supplied if you need to download an historical run (rather than the latest run).

Batch Business Date is only used for background processes that use a date in their processing. In Oracle Utilities Customer Care and Billing, for example, a billing process can use the business date to determine which bill cycles should be downloaded. If this parameter is left blank, the system date is used at the time the background process is executed.

Note: Saving a record on this page does not submit the batch job immediately. A special background process will run periodically to find pending records and submit them. Depending on how often the special process checks for pending records and depending on how many other pending records are in the 'queue', there may be a slight lag in submission time. If the desired execution date/time is close to midnight, it is possible that your batch job will run on the day after you submit it. If you have left the business date blank in this case, keep in mind that your business date would be set to the day after you submit the job.

Override Nbr Records To Commit and Override Max Timeout Minutes. These parameters are optional and override each background process's Standard Commit Records and Standard Cursor Re-Initiation Minutes. (Each background process's Standard Commit Records / Standard Cursor Re-Initiation Minutes should be documented in the detailed description of the batch control record). Note that Max Timeout Minutes corresponds to the Cursor Re-initiation Minutes.

Fastpath: Refer to Parameters Supplied to Background Processes for more information.

User ID is the user ID associated with the run of the background process. Refer to Parameters Supplied to Background Processes for more information about the significance of the user id.

Note: This field defaults to the id of the current user.

Password is not currently used.

Language Code is used to access language-specific control table values. For example, error messages are presented in this language code.

If you wish the system to notify you when the batch job is complete, enter your Email ID. Refer to Email Notification for more information.

Note: This field defaults to the email address for the current user, if populated on the user record.

The Desired Execution Date/Time defaults to the current date and time. Override this information if you wish the background process to be executed at some future date and time. Refer to Submitting Jobs in the Future for more information.

The Batch Job Status indicates the current status of the batch job. Refer to Lifecycle of a Batch Job Submission for more information.

The Program Name associated with the batch control code is displayed.

The following trace parameters may also be supplied to a background process and are only used during QA and benchmarking.

- Trace Program Start Turn on this switch if you wish a message to be written whenever a program is started.

- Trace Program Exit Turn on this switch if you wish a message to be written whenever a program is exited.

- Trace SQL Turn on this switch if you wish a message to be written whenever an SQL statement is executed.

- Trace Output Turn on this switch if you wish a message to be displayed for special information logged by the background process.

Note: The information displayed when the trace output switch is turned on depends on each background process. It is possible that a background process displays no special information for this switch.

Note: The location of the output of this trace information is defined by your system administrator at installation time.

If additional parameters have been defined for this background process on the Batch Control page, the Parameter Name, Description, Detailed Description and an indicator of whether or not the parameter is Required are displayed.

If a default parameter value is configured on the batch control configuration, that value is shown and may be overridden. Confirm or enter the appropriate Parameter Value for each parameter. Note that if the parameter value is configured to be Encrypted on the batch control configuration, the value here will be shown encrypted.

Once you have entered all the desired values, Save the record in order to include it in the queue for background processes.

If you wish to duplicate an existing batch job submission record, including all its parameter settings, display the submission record you wish to duplicate and use the Duplicate and Queue button. This will create a new Batch Job Submission entry in pending status. The new submission entry will be displayed.

If you wish to cancel a Pending batch job submission record use the Cancel button. The button is disabled for all other status values.

Tracking Batch Processes

The batch process pages show the execution status of batch processes. For a specified batch control id and run id, the tree shows each thread, the run-instances of each thread, and any messages (informational, warnings, and errors) that might have occurred during the run. Refer to Defining Batch Controls for more information on how batch control codes are defined.

Next in This Section

- Batch Run Tree - Main

- Batch Run Tree - Run Control

Batch Run Tree - Main

This page allows you to view the status of a specific execution of a batch job. Navigate to this page using Menu > Tools > Batch Run Tree.

Description of Page

Select a Batch Control process and Batch Number to view information and statistics on the batch run's "threads". The following points should help understand this concept:

- Many batch jobs cannot take advantage of your hardware's processing power when they are run singularly. Rather, you'll find that a large percentage of the CPU and/or disk drives are idle.

- In order to minimize the amount of idle time (and increase the throughput of your batch processes), we allow you to set up your batch processes so that multiple instances of a given batch job are executed at the same time. For example, in Oracle Utilities Customer Care and Billing when you schedule the billing process, you can indicate that multiple parallel instances should be executed (rather than just one instance). You'd do this so that the processing burden of creating bills for your customers can be spread over multiple processes.

- We refer to each parallel execution of a batch process as a "thread".

- Statistics and information messages are displayed in respect of each thread. Why? Because each thread is a separate execution and therefore can start and end at different times.

The tree includes a node that displays the total number of records processed for the batch run, the total number of records in error for the batch run and the batch run elapsed time. The elapsed time is the longest elapsed time among the batch thread(s). The message is red if there are any records in error.

If the background process has been enabled to create To Do entries for object specific errors, information about the To Do entries are displayed in the tree. This information is not displayed for each thread, but rather all the To Do entries created for the batch run are grouped together. The To Do entries are grouped by their status.

If the application properties file has been configured with the location of the log files and the log files associated with the batch thread are still available, the links Download stdout and (if applicable) Download stderr are visible. Clicking either link allows you to view or save the log files.

Note: Compression. The log files are compressed and include a *.gz extension. Different browsers treat this type of file differently. Some browsers may automatically decompress the file as part of the download and they are viewable in any text viewer by changing the extension to one the text viewer recognizes. However, some browsers download the compressed file and a user will need to unzip the file prior to viewing.

Note: Security Access. The 'download' hyperlinks are only visible for users that have security access to the Download access mode for the batch run tree application service.

The messages that appear under a thread always show the start and end times of the execution instance. If errors are detected during the execution of the thread, these error messages may also appear in the tree. Refer to Processing Errors for information about the types of errors that appear in the batch run tree.

Batch Run Tree - Run Control

By default, if a batch process fails, it will restart. This tab allows you to modify the restart status of a failed run.

Navigate to this page using Menu > Tools > Batch Run Tree search for the desired batch control and then navigate to the Run Control page.

Description of Page

On the main page, you must select a Batch Control, Batch Number, and Batch Rerun Number to view a tree of the batch run. On this page, the following information is displayed:

- Last Update Timestamp contains the date and time this batch run last start or last completed.

- Batch Business Date is the business date that was supplied to the background process (this date is used as the "system date" by the process).

Run Status indicates the status of the batch run. Valid values are: In Progress, Error, and Complete.

If the Run Status is Error, the system will attempt to restart this run when you attempt to execute the Batch Control. In most situations, this is exactly what you want to happen. However, there are rare situations where you do not want the system to execute a given batch run (e.g., if this run is somehow corrupt and you cannot correct the data for whatever reasons). If you want the system to skip the execution of a batch run (and proceed to the next run), turn on Do Not Attempt Restart.

Service Health Check

The system provides a service that returns an overall assessment of the system’s health. The overall response is expressed using an HTTP code. The codes supported by the service are defined in the lookup HEALTH_RESPONSE_FLG and are as follows:

- A value of 500 (One or More Critical Functions Degraded) is returned if there is any critical issue detected by the service.

- A value of 203 (Non-Critical Function Degraded) is returned if no critical issues are found and there is at least one non-critical issue detected by the service.

- Otherwise a value of 200 (All Checks Successful) is returned.

This health check service is accessible through the business service F1–HealthCheck. Also note that the system provides an Inbound Web Service for this business service (also called F1–HealthCheck) allowing external systems to use a web service to retrieve this information.

In addition, the product provides a portal that allows a user to view the detailed results of the health check service.

Navigate using Admin > System > Health Check to view this portal.

The zone on the portal displays the following:

Overall Response is the HTTP response code returned by the business service as described above.

The grid displays the detail of each individual component checked as part of the system health check. See below for more detail about what components are checked.

- Health Component indicate the type of health check performed. Currently the system supports Batch Level of Service component type.

- Health Component Details provides information about the individual entity checked. The information displayed here depends on the type of health component. If supported by the type of component, the column may be hypertext, allowing the user to drill into the entity itself.

- Status displays the status returned by the health component check for this individual entity. The information displayed here depends on the type of health component.

- Status Reason provides more detail about why the individual entity is in the indicated status. The information displayed here depends on the type of health component.

- Response shows the health check response code assigned to this individual entity’s health check response. It is mapped based on the status returned by the health component check.

Health Component Type Details

The details returned by the business service for this portal depends on the health component type. The system supports the Batch Level of Service health component type.

This health component type finds all the batch controls that are configured with a level of service algorithm and invokes the algorithm for each batch control. The business service populates the output for this health service for each batch control as follows:

- The Health Component Detail is populated with the Batch Control code and description. In addition, the navigation information for being able to drill into the batch control are provided and used to build the column as hypertext.

- The Status is populated with the description of the Level of Service lookup value returned by the level of service algorithm for this batch control.

- The Status Reason is populated with the expanded text of the status reason returned by the level of service algorithm for this batch control.

- The Response is populated based on the value of the Level of Service status. It is set to All Checks Successful (200) when the Level of Service is Normal or Disabled; Non-Critical Function Degraded (203) when the Level of Service is Warning and One or More Critical Functions Degraded (500) when the Level of Service is Error.

The Big Picture of Requests

Requests enable an implementer to design an ad-hoc batch process using the configuration tools.

An example of such a process might be to send an email to a group of users that summarizes the To Do entries that are assigned to them. This is just one example. The request enables many types of diverse processing.

Next in This Section

- Request Type Defines Parameters

- Previewing and Submitting a Request

- To Do Summary Email

- Exploring Request Data Relationships

- Defining a New Request

- Setting Up Request Types

- Maintaining Requests

Request Type Defines Parameters

For each type of process that your implementation wants, you must configure a request type to capture the appropriate parameters needed by the process.

Previewing and Submitting a Request

To submit a new request, go to Menu > Tools > Request in add mode. You must select the appropriate request type and then enter the desired parameter values, if applicable.

After entering the parameters, the following actions are possible:

- Click Save to submit the request.

- Click Cancel to cancel the request.

- Click Preview to see a sample of records that satisfy the selection criteria for this request. This information is displayed in a separate map. In addition, the map displays the total number of records that will be processed when the request is submitted. From this map you can click Save to submit the request, Back to adjust the parameters, or Cancel to cancel the request.

When a request is saved, the job is not immediately submitted for real time processing. The record is saved with the status Pending and a monitor process for this record's business object is responsible for transitioning the record to Complete.

As long as the record is still Pending, it may be edited to adjust the parameters. The preview logic described above may be repeated when editing a record.

The actual work of the request, such as generating an email, is performed when transitioning to Complete (using an enter processing algorithm for the business object).

To Do Summary Email

The base product includes a sample request process that sends an email to users that have incomplete To Dos older than a specified number of days.

The following configuration tasks are required to use this process:

- Define an Outbound Message Type. The business object usually defined for the Outbound Message Type is F1-EmailMessage.

- Define an External System that contains the Outbound Message Type in one of its steps. In the configuration determine if the communication is through SOA, batch, or real-time processing method when sending the email notification. Refer to Outbound Messages for more information about configuration needed for the different processing methods.

- Create a Request Type that includes the Outbound Message Type and the corresponding External System.

- Create a Request for the created Request Type.

Exploring Request Data Relationships

Use the following links to open the application viewer where you can explore the physical tables and data relationships behind the request functionality:

- Click F1-REQ-TYPE to view the request type maintenance object's tables.

- Click F1-REQ to view the request maintenance object's tables.

Defining a New Request

To design a new ad-hoc batch job that users can submit via Request, first create a new Request Type business object. The base product BO for request type, F1-TodoSumEmailTyp, may be used as a sample.

The business object for the request includes the functionality for selecting the records to process, displaying a preview map for the user to review, and for performing the actual processing. The base product BO for request, F1-TodoSumEmailReq, may be used as a sample. The following points highlight the important configuration details for this business object:

- Special BO options are available for request BOs to support the Preview Request functionality.

- Request Preview Service Script. This script retrieves the information that is displayed when a user asks for a preview of a request.

- Request Preview Map. This map displays the preview of a request.

- The enter algorithm plugged into the Complete state is responsible for selecting the records that satisfy the criteria and processing the records accordingly.

Setting Up Request Types

Use the Request Type portal to define the parameters to capture when submitting a request. Open this page using Admin > General > Request Type.

This topic describes the base-package zones that appear on the Request Type portal.

Request Type List. The Request Type List zone lists every request type. The following functions are available:

- Click a broadcast icon to open other zones that contain more information about the request type.

- Click Add in the zone's title bar to add a new request type.

Request Type. The Request Type zone contains display-only information about a request type. This zone appears when a request type has been broadcast from the Request Type List zone or if this portal is opened via a drill down from another page. The following functions are available:

- Click Edit to start a business process that updates the request type.

- Click Delete to start a business process that deletes the request type.

- Click Deactivate start a business process that deactivates the request type.

- Click Duplicate to start a business process that duplicates the request type.

- State transition buttons are available to transition the request type to an appropriate next state.

Please see the zone's help text for information about this zone's fields.

Maintaining Requests

Use the Request transaction to view and maintain pending or historic requests.

Open this page using Menu > Tools > Request > Search. This topic describes the base-package portals and zones on this page.

Request Query. Use the query portal to search for an existing request. Once a request is selected, you are brought to the maintenance portal to view and maintain the selected record.

Request Portal. This portal appears when a request has been selected from the Request Query portal. The following base-package zones appear on this portal:

- Actions. This is a standard actions zone.

- Request. The Request zone contains display-only information about a request. Please see the zone's help text for information about this zone's fields.

- Request Log. This is a standard log zone.

Defining Algorithms

In this section, we describe how to set up the user-defined algorithms that perform many important functions including:

- Validating the format of a phone number entered by a user.

- Validating the format of a latitude/longitude geographic code entered by a user.

- In products that support payment and billing:

- Calculating late payment charges.

- Calculating the recommended deposit amount.

- Constructing your GL account during the interface of financial transactions to your GL

- And many other functions...

Next in This Section

- The Big Picture Of Algorithms

- Setting Up Algorithm Types

- Setting Up Algorithms

The Big Picture Of Algorithms

Many functions in the system are performed using a user-defined algorithm. For example, when a CSR requests a customer's recommended deposit amount, the system calls the deposit recommendation algorithm. This algorithm calculates the recommended deposit amount and returns it to the caller.

Note: Algorithm = Plug-in. We use the terms plug-in and algorithm interchangeably throughout this documentation.

So how does the system know which algorithm to call? When you set up the system's control tables, you define which algorithm to use for each component-driven function. You do this on the control table that governs each respective function. For example:

- You define the algorithm used to validate a phone number on your phone types.

- You define the algorithm in Oracle Utilities Customer Care and Billing used to calculate late payment charges on each Service Agreement Type that has late payment charges.

- The list goes on...

The topics in this section provide background information about a variety of algorithm issues.

Next in This Section

- Algorithm Type Versus Algorithm

- How To Add A New Algorithm

- Minimizing The Impact Of Future Upgrades

Algorithm Type Versus Algorithm

You have to differentiate between the type of algorithm and the algorithm itself.

- An Algorithm Type defines the program that is called when an algorithm of this type is executed. It also defines the types of parameters that must be supplied to algorithms of this type.

- An Algorithm references an Algorithm Type. It also defines the value of each parameter. It is the algorithm that is referenced on the various control tables.

Fastpath: Refer to How to Add A New Algorithm for an example that will further clarify the difference between an algorithm and an algorithm type.

How To Add A New Algorithm

Before you can add a new algorithm, you must determine if you can use one of the sample algorithm types supplied with the system. Refer to List of Algorithm Types for a complete list of algorithm types.

If you can use one of the sample algorithm types, simply add the algorithm and then reference it on the respective control table. Refer to Setting Up Algorithms for how to do this.

If you have to add a new algorithm type, you may have to involve a programmer. Let's use an example to help clarify what you can do versus what a programmer must do. Assume that you require an additional geographic type validation algorithm. To create your own algorithm type you must:

- Write a new program to validate geographic type in the appropriate manner. Alternatively, you may configure a plug-in script to implement the validation rules. The advantage of the latter is that it does not require programming. Refer to plug-in script for more information.

- Create an Algorithm Type called Our Geographic Format (or something appropriate). On this algorithm type, you'd define the name of the program (or the plug-in script) that performs the function. You'd also define the various parameters required by this type of algorithm.

- After creating the new Algorithm Type, you can reference it on an Algorithm.

- And finally, you'd reference the new Algorithm on the Geographic Type that requires this validation.

Minimizing The Impact Of Future Upgrades

The system has been designed to use algorithms so an implementation can introduce their own logic in a way that's 100% upgradeable (without the need to retrofit logic). The following points describe strong recommendations about how to construct new algorithm type programs so that you won't have to make program changes during future upgrades:

- Do not alter an algorithm type's hard parameters. For example, you might be tempted to redefine or initialize parameters defined in an algorithm type's linkage section. Do not do this.

- Follow the naming conventions for the new algorithm type code and your source code, i.e., both the source code and the algorithm type should be prefixed with "CM". The reason for this naming convention is to make it impossible for a new, base-package algorithm type from overwriting your source code or algorithm type meta-data (we will never develop a program or introduce meta-data beginning with CM).

- Avoid using embedded SQL to perform insert/update/delete. Rather, invoke the base-package's object routines or common routines.

- Avoid using base messages (outside of common messages, i.e., those with a message number < 1000) as we may deprecate or change these messages in future releases. The most common problem is caused when an implementation clones a base package algorithm type program because they need to change a few lines of logic. Technically, to be 100% upgradeable, you should add new messages in the "90000" or greater category (i.e., the category reserved for implementation-specific messages) for every message in your new program even though these messages may be duplicates of those in the base package.

Setting Up Algorithm Types

The system provides many algorithm types to support base product functionality. If you need to introduce a new type of algorithm, open Admin > System > Algorithm Type.

Fastpath: Refer to The Big Picture Of Algorithms for more information.

CAUTION:

Important! If you introduce a new algorithm type, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Description of Page

Enter an easily recognizable Algorithm Type and Description.

Owner indicates if this algorithm type is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add an algorithm type. This information is display-only.

Enter a Detailed Description that describes, in detail, what algorithms of this type do.

Use Algorithm Entity to define where algorithms of this type can be "plugged in". If a detailed description about an algorithm entity is available, a small help icon is visible adjacent to the dropdown. Click the icon to view the information.

Note: The values for this field are customizable using the lookup table. This field name is ALG_ENTITY_FLG.

Use Program Type to define if the algorithm's program is written using Java, a Plug-In Script, or Java (Converted), meaning the program has been converted to Java.

Note: Java (Converted) program types are not applicable to all products.

Use Program Name to define the program to be invoked when algorithms of this type are executed:

- If the Program Type is Java (Converted), enter the name of the converted program.

- If the Program Type is Java, enter the Java class name.

- If the Program Type is Plug-In Script, enter the plug-in script name. Only plug-in scripts defined for the algorithm entity may be used.

Note: View the source. If the program is shipped with the base package, you can use the adjacent button to display the source code of this program in the Java docs viewer. For plug-in scripts, drill into the plug-in script to view the details.

Use the Parameter Types grid to define the types of parameters that algorithms of this type use. The following fields should be defined for each parameter:

- Use Sequence to define the relative position of the Parameter.

- Use Parameter to describe the verbiage that appears adjacent to the parameter on the Algorithm page.

- Indicate whether the parameter is Required. This indicator is used when parameters are defined on algorithms that reference this algorithm type.

- Owner indicates if the parameter for this algorithm type is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add an algorithm type with parameters. This information is display-only.

Note: When adding a new algorithm type that is for a Java program, the parameters are automatically generated based on the Java code. Once an algorithm type exists, any additional parameters defined in the Java code should be manually added to the algorithm type. For other program types, algorithm type parameters must be manually defined.

Note: When a new algorithm type parameter is added for any program type, existing algorithms for the algorithm type do not automatically get updated with the new parameter. The algorithms must be manually updated.

Where Used

An Algorithm references an Algorithm Type. Refer to Setting Up Algorithms for more information.

Next in This Section

- List of Algorithm Types

List of Algorithm Types

The algorithm types available to use with the product may be viewed in the algorithm type page and in the application viewer's algorithm viewer. If your implementation adds algorithm types or adds algorithms to reference existing algorithm types, you may regenerate the application viewer to see your additions reflected there.

Setting Up Algorithms

If you need to introduce a new algorithm, open Admin > System > Algorithm. Refer to The Big Picture Of Algorithms for more information.

Description of Page

Enter an easily recognizable Algorithm Code and Description of the algorithm. Owner indicates if this algorithm is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new algorithm, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Reference the Algorithm Type associated with this algorithm.

Fastpath: Refer to Algorithm Type Versus Algorithm for more information about how an algorithm type controls the type of parameters associated with an algorithm.

The parameters available for an algorithm are defined on the algorithm type. The system allows a set of parameter values to change over time. Use the parameter scroll to view parameter values for a given Effective Date. The Owner of the collection of parameters is displayed. The collection shows the Parameter description, the Sequence and the Value for each parameter.

Note: If the product delivers an algorithm with parameter values defined, an implementation may override the base provided parameter values by adding an additional effective dated collection of parameters.

Note: If an algorithm is defined and subsequently a new parameter is added to the algorithm type, existing algorithms for the algorithm type should be updated as follows: Click the “+” to add a new effective dated entry to the parameter collection. At this point the latest list of parameters for the algorithm type are visible. Configure the parameters accordingly.

Where Used

Algorithms are plugged in on control tables throughout the system. Each algorithm type’s Algorithm Entity indicates the name of the control table where it is plugged in. The algorithm viewer in the application viewer may also be used to see a list of plug-in spots along with their algorithm types and algorithms.

Defining Script Options

We use the term "script" to define processing rules that your implementation sets up to control both front-end and back-end processing:

- Rules that control front-end processing are defined using Business Process Assistant (BPA) scripts. For example, your implementation could set up a BPA script to guide a user through your organization's payment cancellation process.

- Rules that control back-end processing are defined using Server-based scripts. For example, your implementation could set up a server-based script to control the processing that executes whenever a given type of adjustment is canceled.

The topics in this section describe how to configure your scripts.

Next in This Section

- The Big Picture Of Scripts

- The Big Picture Of BPA Scripts

- The Big Picture Of Server-Based Scripts

- Maintaining Scripts

- Merging Scripts

- Maintaining Functions

The Big Picture Of Scripts

This section describes features and functions that are shared by both BPA scripts and server-based scripts.

Next in This Section

- Scripts Are Business Process-Oriented

- A Script Is Composed Of Steps

- A Script May Declare Data Areas

- Securing Script Execution

Scripts Are Business Process-Oriented

To create a script, you must analyze the steps used to implement a given business process. For example, you could create a "stop auto pay" BPA script that:

- Asks the user to select the customer / taxpayer using an appropriate search page

- Asks the user to define the date on which the person would like to stop making automatic payments

- Invokes a server-based script that populates the end-date on the account's latest automatic payment instructions.

After you understand the business process, you can set up a script to mimic these steps. If the business process is straightforward (e.g., users always perform the same steps), the script configuration will be straightforward. If the business process has several logic branches, the composition of the script may be more challenging.

A Script Is Composed Of Steps

A script contains one or more steps. For example, a "stop auto pay" BPA script might have three steps:

- Ask the user to select the customer / taxpayer using an appropriate search page

- Ask the customer the date on which they'd like to stop making automatic payments (and default the current date)

- Invoke a server-based script that, in turn, updates the account's auto pay options.

Each step references a step type. The step type controls what happens when a step executes. It might be helpful to think of a script as a macro and each step as a "line of code" in the macro. Each step's step type controls the function that is executed when the step is performed.

Fastpath: Refer to How To Set Up Each Step Type for a detailed description of all available step types and how to set them up.

A Script May Declare Data Areas

Both BPA and server-based scripts may have one or more data areas:

- If the script contains steps that exchange XML documents, you must declare a data area for each type of XML document. For example, if a BPA script has a step that invokes a service script, the BPA script must declare a data area that holds the XML document that is used to pass information to and from the service script.

- You can use a data area as a more definitive way to declare your temporary storage. For example, you can describe your script's temporary storage variables using a stand-alone data area schema and associate it with your script.

Various step types involve referencing the script's data areas as well as support the ability to compare and move data to and from field elements residing in the data areas.

An Edit Data step supports the syntax to dynamically declare data areas as part of the step itself. This technique eliminates the need to statically declare a data area. Refer to Edit Data Syntax for more information on edit data commands and examples of the use of dynamic data areas.

Note: Some server based scripts may not use data areas as means of defining or exchanging data, depending on script type and the chosen scripting technique. Refer to The Big Picture Of Server Based Scripts for an overview of server scripts and their applicable scripting options.

Securing Script Execution

The system supports the ability to secure the execution of scripts by associating the script with an Application Service. Refer to The Big Picture of Application Security for more information. Application security is optional for user-invocable BPA scripts. If a script is not associated with an application service, all users may execute the script. Otherwise, only users that have Execute access to the application service may execute the script. For service scripts, the application service is required.

The Big Picture Of BPA Scripts

Fastpath: Refer to The Big Picture Of Scripts to better understand the basic concept of scripts.

Users may require instructions in order to perform certain tasks. The business process assistant allows you to set up scripts that step a user through your business processes. For example, you might want to create scripts to help users do the following:

- Add a new person to an existing account

- Set up a customer to pay automatically

- Modify a customer who no longer wants to receive marketing information

- Modify a customer's web password

- Record a trouble order

- Merge two accounts into one account

- Fix a bill with an invalid rate

- ... (the list is only limited by your time and imagination)

Users execute these scripts via the business process assistant (BPA). Users can also define their favorite BPA scripts in their user preferences. By doing this, a user can execute a script by pressing an accelerator key (Ctrl + Shift + a number).

Don't think of these scripts as merely a training tool. BPA scripts can also reduce the time it takes to perform common tasks. For example, you can write a script that reduces the "number of clicks" required to add a new person to an existing account.

CAUTION:

Future upgrade issues. Although we make every effort not to remove fields or tab pages between releases, there may be times when changes made by the base-package will necessitate changes to your scripts. Please refer to the release notes for a list of any removed fields or tab pages.

CAUTION:

Scripts are not a substitute for end-user training. Scripts minimize the steps required to perform common tasks. Unusual problems (e.g., a missing meter exchange) may be difficult to script as there are many different ways to resolve such a problem. However, scripts can point a user in the right direction and reduce the need to memorize obscure business processes.

The topics in this section describe background topics relevant to BPA scripts.

Next in This Section

- How To Invoke Scripts

- Developing and Debugging Your BPA Scripts

- Launching A Script From A Menu

- Launching A Script When Starting The System

- Executing A Script When A To Do Entry Is Selected

- The Big Picture Of Script Eligibility Rules

How To Invoke Scripts

Refer to Initiating Scripts for a description of how end-users initiate scripts.

Developing and Debugging Your BPA Scripts

We recommend considering the approaches outlined below when you construct scripts.

While designing your scripts, determine the most maintainable way to set them up. Rather than creating complex, monolithic scripts, we recommend dividing scripts into smaller sections. For example

- Determine if several scripts have similar steps. If so, set up a script that contains these common steps and invoke it from the main scripts using a Perform script step.

- Determine if a large script can be divided into logical sections. If so, set up a small script for each section and create a "master script" to invoke each sub script via a Transfer control step.

For debugging purposes, you may find it helpful to categorize the step types into two groups: those that involve some type of activity in the script area, and those that don't. The following step types cause activity in the script area: Height, Display text, Prompt user, Input data, Input Map, Set focus to a field.

The rest of the step types are procedural and involve no user interaction. There are two techniques you can use to assist in debugging these step types.

- You can instruct the system to display text in the script area.

- You can display an entire data area (or a portion thereof) in the script area by entering %+...+% where ... is the name of the node whose element(s) should be displayed.

Note: Time saver. When you develop a new BPA script, change your user preferences to include the script as your first "favorite". This way, you can press Ctrl+Shift+1 to invoke the script (eliminating the need to select it from the script menu).

Launching A Script From A Menu

You can create menu items that launch BPA scripts rather than open a page. To do this, create a navigation option that references your script and then add a menu item that references the navigation option.

If the navigation option is referenced on a context menu and the navigation option has a "context field", a temporary storage variable will be created and populated with the unique identifier of the object in context. For example, if you add a "script" navigation option to the bill context menu and this navigation option has a context field of BILL_ID, the system will create a temporary storage variable called BILL_ID and populate it with the respective bill id when the menu item is selected.

Launching A Script When Starting The System

You can set the system to launch a script upon startup.

For example, imagine that through an interactive voice response system, a customer has keyed in their account ID and has indicated that they would like to stop an automatic payment. At the point when the IVR system determines that the customer must speak to a user, the interface can be configured to launch the application. When launched it passes the script name and account ID. It can also pass a navigation option to automatically load the appropriate page (if this information is not part of the script).

To do this, parameters are appended to the standard system URL. The following parameters may be supplied:

- script=<scriptname>

- ACCT_ID=<account id>

- location=<navigation option>

Parameters are added to the standard system URL by appending a question mark (?) to the end and then adding the "key=value" pair. If you require more than one parameter, use an ampersand (&) to separate each key=value pair.

For example, the following URLs are possible ways to launch the CM-StopAutoPay script at startup, assuming your standard URL for launching the system is http://system-server:1234/cis.jsp:

- http://system-server:1234/cis.jsp?script=CM-StopAutoPay

- http://system-server:1234/cis.jsp?script=CM-StopAutoPay&ACCT_ID=1234512345

- Zoneshttp://system-server:1234/cis.jsp?script=CM-StopAutoPay&ACCT_ID=1234512345&location=accountMaint

It doesn't matter in which order the parameters are provided. The system processes them in the correct order. For example, the following examples are processed by the system in the same way:

- http://system-server:1234/cis.jsp?ACCT_ID=1234512345&script=CM-StopAutoPay&location=accountMaint

- http://system-server:1234/cis.jsp?ACCT_ID=1234512345&location=accountMaint&script=CM-StopAutoPay

These parameters are kept in a common area accessible by any script for the duration of the session. To use these parameters on a script you may reference the corresponding %PARM-<name> global variables. In this example, after the system is launched any script may have access to the above account ID parameter value by means of the %PARM-ACCT_ID global variable. Also note, these parameters are also loaded into temporary storage (to continue the example, there'd also be a temporary storage variable called ACCT_ID that holds the passed value).

Note: Minimizing the Dashboard. As described in Dashboard Portal, a URL parameter may be used to minimize the dashboard when launching the system, which may be included in the URL when launching the system with a script.

Determining the Target Navigation in the Script

By default, if a script is provided but the location attribute is not provided, the system navigates to the user's home page prior to executing the script. If the script itself includes a step to navigate to a target page as one of its initial steps, the navigation to the home page is unnecessary and may degrade performance. The system supplies an optional attribute to include in the URL to bypass the home page: initNav=false.

Note: The system still requires a page to be launched for technical reasons. A blank portal with no zones is used for this purpose. Users may see this portal (called Launching Application) briefly before the navigation initiated by the script. In addition, this is the portal that the user will remain on if there are any errors in the script or if the script does not navigate anywhere.

Navigate to a Given Record’s Maintenance Portal

If your use case is to simply navigate to the maintenance page for a given record and display that record, the script F1-GotoPrtl (Navigate to portal for an MO and key values) may be used. This script is only applicable to records that are governed by a business object (and define a navigation option as a BO option). It takes the incoming maintenance object code and primary key values, looks up the appropriate portal navigation option from the record's BO, populates keys into the 'page data model' and navigates to the portal.

The script expects the keys to be passed in using variable names pkValue1 through pkValue5. It is also recommended to include the initNav=false attribute. This example navigates to the appropriate Migration Data Set portal for the given ID's business object.

- http://system-server:1234/cis.jsp?script=F1–GotoPrtl&pkValue1=1234512345&mo=F1–MIGRDS&initNav=false

Executing A Script When A To Do Entry Is Selected

The system creates To Do entries to highlight tasks that require attention (e.g., records in error). Users can complete many of these tasks without assistance. However, you can set up the system to automatically launch a script when a user selects a To Do entry. For example, consider a To Do entry that highlights a bill that's in error due to an invalid mailing address. You can set up the system to execute a script when this To Do entry is selected by a user. This script might prompt the user to first correct the customer's default mailing address and then re-complete the bill.

The following points provide background information to help you understand how to implement this functionality:

- Every To Do entry references a To Do type and a message category and number. The To Do type defines the category of the task (e.g., bill errors). The message number defines the specific issue (e.g., a valid address can't be found.). Refer to The Big Picture of System Messages for more information about message categories and numbers.

- When a user drills down on a To Do entry, either a script launches OR the user is transferred to the transaction associated with the entry's To Do type. You control what happens by configuring the To Do type accordingly:

- If you want to launch a script when a user drills down on an entry, you link the script to the To Do type and message number. Keep in mind that you can define a different script for every message (and some To Do types have many different messages).

- If the system doesn't find a script for an entry's To Do type and message number, it transfers the user to the To Do type's default transaction.

Note: How do you find the message numbers? We do not supply documentation of every To Do type's message numbers (this list would be impossible to maintain and therefore untrustworthy). The best way to determine which message numbers warrant a script is during pre-production when you're testing the system. During this period, To Do entries will be generated. For those entries that warrant a script, simply display the entry on To Do maintenance. On this page, you will find the entry's message number adjacent to the description.

- These types of scripts invariably need to access data that resides on the selected To Do entry. Refer to How To Use To Do Fields for the details.

The Big Picture Of Script Eligibility Rules

You can configure eligibility criteria on the scripts to limit the scripts that a user sees in the script search. For example, you could indicate a script should only appear on the script menu if the user belongs to the level 1 customer service representative group. You may also indicate that a script should only appear if the data a user is viewing has certain criteria. For example, if you are using Oracle Utilities Customer Care and Billing, you can indicate that a script should only appear if the current account's customer class is residential. By doing this, you avoid presenting the user with scripts that aren't applicable to the current data in context or the user's role.

The topics in this section describe eligibility rules.

Next in This Section

- Script Eligibility Rules Are Not Strictly Enforced

- You Can Mark A Script As Always Eligible

- You Can Mark A Script As Never Eligible

- Criteria Groups versus Eligibility Criteria

- Defining Logical Criteria

- Examples Of Script Eligibility Rules

Script Eligibility Rules Are Not Strictly Enforced

The script search gives a user a choice of seeing all scripts or only scripts that are eligible (given the current data in context and their user profile). This means that it's possible for a script that isn't eligible for the given context data / user to be executed via this search. In other words, the system does not strictly enforce a script's eligibility rules.

It might be more helpful to think of eligibility rules as "highlight conditions". These "highlight conditions" simply control whether the script appears in the script search when a user indicates they only want to see eligible scripts.

You Can Mark A Script As Always Eligible

If you don't want to configure eligibility rules, you don't have to. Simply indicate that the script is always eligible.

You Can Mark A Script As Never Eligible

If you have scripts that you do not want a user to select from the script menu, indicate that it is never eligible. An example of a script that you wouldn't want a user to select from the menu is one that is launched when a To Do entry is selected. These types of scripts most likely rely on data linked to the selected To Do entry. As a result, a user should only launch scripts of this type from the To Do entry and not from the script menu.

Criteria Groups versus Eligibility Criteria

Before we provide concrete examples of eligibility criteria, we need to explain two concepts: Criteria Groups and Eligibility Criteria. A script's criteria groups control whether a user is eligible to choose a script. At a high level, it works like this:

- A criteria group has one or more eligibility criteria. A group's criteria control whether the group is considered true or false.

- When you create a group, you define what should happen if the group is true or false. You have the following choices:

- The user is eligible to choose the script

- The user is not eligible to choose the script

- The next group should be checked

We'll use the following example from Oracle Utilities Customer Care and Billing to help illustrate these points. Assume a script is only eligible if:

- The customer has electric service and the user belongs to user group A, B or C

- OR, the customer has gas service and the user belongs to user group X, Y or A

This script requires two eligibility groups because it has two distinct conditions:

- IF (Customer has electric service AND (User belongs to user group A, B or C))

- IF (Customer has gas service AND (User belongs to user group X, Y or A))

If either condition is true, the script is eligible.

You would need to set the following criteria groups in order to support this requirement:

Group No.

Group Description

If Group is True

If Group is False

1

Customer has electric service and the user belongs to user group A, B or C

Eligible

Check next group

2

Customer has gas service and the user belongs to user group X, Y or A

Eligible

Ineligible

The following criteria are required for each of the above groups:

Group 1: Customer has electric service and the user belongs to user group A, B or C

Seq

Logical Criteria

If Eligibility Criteria is True

If Eligibility Criteria is False

If Insufficient Data

10

Customer has electric service

Check next condition

Group is false

Group is false

20

User belongs to user group A, B or C

Group is true

Group is false

Group is false

Group 2: Customer has gas service and the user belongs to user group X, Y or A

Seq

Logical Criteria

If Eligibility Criteria is True

If Eligibility Criteria is False

If Insufficient Data

10

Customer has gas service

Check next condition

Group is false

Group is false

20

User belongs to user group X, Y or A

Group is true

Group is false

Group is false

The next section describes how you might configure the specific logical criteria in each of the groups.

Defining Logical Criteria

When you set up an eligibility criterion, you must define two things:

- The field to be compared

- The comparison method

You have the following choices in respect of identifying the field to be compared :

- You can execute an algorithm to retrieve a field value from somewhere else in the system.

- Some products may support choosing a characteristic linked to an appropriate object in the system (such as an account or person).

You have the following choices in respect of identifying the comparison method:

- You can choose an operator (e.g., >, <, =, BETWEEN, IN, etc.) and a comparison value.

- You can execute an algorithm that performs the comparison (and returns True, False or Insufficient Data). This is also a very powerful feature, but it's not terribly intuitive. We'll present a few examples later in this section to illustrate the power of this approach.

The Examples Of Script Eligibility Rules provide examples to help you understand this design.

Examples Of Script Eligibility Rules

The topics in this section provide examples about how to set up script eligibility rules.

Next in This Section

- A Script With A Time Span Comparison

- A Script With Service Type Comparison

A Script With A Time Span Comparison

A script that is only eligible for senior citizens has the following eligibility rules:

- Customer class = Residential

- Birth date equates to that of a senior citizen

These rules require only one eligibility group on the script. It would look as follows:

Group No.

Group Description

If Group is True

If Group is False

1

Residential and Senior Citizen

Eligible

Ineligible

The following criteria will be required for this group:

Group 1: Residential, Calif, Senior

Seq

Field to Compare

Comparison Method

If True

If False

If Insufficient Data

10

Algorithm: retrieve account's customer class

= R

Check next condition

Group is false

Group is false

30

Person characteristic: Date of Birth

Algorithm: True if senior

Group is true

Group is false

Group is false

The first criterion is easy; it calls an algorithm that retrieves a field on the current account. This value, in turn, is compared to a given value. If the comparison results in a True value, the next condition is checked. If the comparison doesn't result in a True value, the Group is false (and, the group indicates that if the group is false, the script isn't eligible). Refer to SECF-ACCTFLD in the product documentation for an example of an algorithm type that retrieves a field value from an account.

The last criterion contains a time span comparison. Time span comparisons are used to compare a date to something. In our example, we have to determine the age of the customer based on their birth date. If the resultant age is > 65, they are considered a senior citizen. To pull this off, you can take advantage of a comparison algorithm supplied with the base script as described below.

- Field to Compare. The person characteristic in which the customer's birth date is held is selected.

- Comparison Method. We chose a comparison algorithm that returns a value of True if the related field value (the customer's date of birth) is greater than 65 years (refer to SECC-TIMESPN for an example of this type of algorithm).

You'll notice that if a value of True is returned by the True if senior algorithm, the group is true (and we've set up the group to indicate a true group means the script is eligible).

Note: The time span algorithm can be used to compare days, weeks, months, etc. Refer to SECC-TIMESPN for more information about this algorithm.

A Script With Service Type Comparison

Imagine a script that is only eligible if the current customer has gas service and the user belongs to user groups A, B or C. This script would need the following eligibility rules:

- Customer has gas service

- User belongs to user group A, B, or C

These rules require only one eligibility group on the script. It would looks as follows:

Group No.

Group Description

If Group is True

If Group is False

1

Has gas service and user is part of user group A, B or C

Eligible

Ineligible

The following criteria are required for this group:

Group 1: Has gas service and user is part of user group A, B, or C

Seq

Field to Compare

Comparison Method

If True

If False

If Insufficient Data

10

Algorithm: check if customer has gas service

= True

Check next condition

Group is false

Group is false

20

Algorithm: check if user belongs to user group A, B or C

= True

Group is true

Group is false

Group is false

Both criteria are similar - they call an algorithm that performs a logical comparison. These algorithms are a bit counter intuitive (but understanding them provides you with another way to implement complex eligibility criteria):

The first criterion works as follows:

- Field to Compare. We chose a "field to compare" algorithm that checks if the current account has service agreements that belong to a given set of service types. It returns a value of True if the customer has an active service agreement that matches one of the service types in the algorithm. In our example, the "check if customer has gas service" algorithm returns a value of True if the customer has at least one active service agreement whose SA type references the gas service type. The "check if customer has electric service" algorithm is almost identical, only the service type differs.

- Comparison Method. We simply compare the value returned by the algorithm to True and indicate the appropriate response.

The second criterion works similarly:

- Field to Compare. We chose a "field to compare" algorithm that checks if the user belongs to any user group in a set of user groups. It returns a value of True if the user belongs to at least one user group defined in parameters of the algorithm. Refer to SECF-USRNGRP for an example of this type of algorithm.

- Comparison Method. We simply compare the value returned by the algorithm to True and indicate the appropriate response.

Note: Bottom line. The "field to compare" algorithm isn't actually returning a specific field's value. Rather, it's returning a value of True or False. This value is in turn, compared by the "comparison method" and the group is set to true, false or check next accordingly.

The Big Picture Of Server-Based Scripts

Fastpath: Refer to The Big Picture Of Scripts to better understand the basic concept of scripts.

Server-based scripts allow an implementation to configure backend business processes. The system supports three types of server-based scripts, Plug-In scripts, Service scripts and Groovy Library scripts.

- Plug-in scripts allow an implementation to develop routines that are executed from the system's various plug-in spots. For example, an implementation could configure a plug-in script that is executed every time an adjustment of a given type is frozen.

- Service scripts allow an implementation to develop common routines that are invoked from both front-end and back-end services. For example, an implementation could create a service script that terminates an account's automatic payment preferences. This service script could be invoked from a BPA script initiated by an end-user when a customer asks to stop paying automatically, and it could also be executed from a plug-in script if a customer fails to pay their debt on time. Service scripts are typically written using xpath scripting.

- Groovy Library scripts allow an implementation to develop groups of common routines written in the Groovy language which may be invoked from Groovy Member step types.

The topics in this section describe background topics relevant to server-based scripts.

Next in This Section

- Additional Coding Options For Server Scripts

- Plug-In Scripts

- Service Scripts

- Groovy Library Scripts

- Debugging Server-Based Scripts

Additional Coding Options For Server Scripts

Server based scripts often perform complex functions best supported by coding in languages with more comprehensive command sets than the base script steps. The system supports two common third-party languages for this purpose.

XML Path Language (XPath) is a language for querying and evaluating elements or nodes in an XML document. XPath commands and expressions can be used directly within Edit Data step types. The script engine version is used to define the applicable XPath version.

Groovy is an object-oriented, dynamic language for the Java platform. The framework supports the use of Groovy within server-based scripts to provide restricted and controlled access to Java-like code, particularly for cloud based implementations. The following topic provides more information on how to incorporate Groovy code into scripts.

Next in This Section

- Using Groovy Within Scripts

Using Groovy Within Scripts

Groovy code can be incorporated in scripts using the step type Groovy Members. For each script with Groovy code, there will be a single Groovy class created by concatenating all Groovy Members steps.

For security, the product and third party Java classes available for scripting in Groovy will be restricted. The allowable base classes may be viewed via the Groovy JavaDocs feature in the Application Viewer and also via the ‘View Groovy Javadocs’ link in the context sensitive Script Tips zone. The list of allowable third party classes can be viewed via the ‘View third party Groovy whitelist’ link in the Script Tips zone.

Note: This system supports the use of Groovy for back end processing purposes. It is not intended for user interfaces. Groovy is also not applicable to BPA scripts.

The following describes the two methods for using Groovy.

Using the Scripting Engine

If the script is configured to use a scripting engine version, it can include a mixture of regular and Groovy Members step types. The script step types will define the process to be executed. The Groovy Members steps will contain code that can be called from Edit Data step types within the script using the invokeGroovy command. Only Groovy methods that receive no arguments and return void are supported using this command. Refer to the section on edit data steps for more details.

For scripts using this option, the framework provides a superclass containing methods that support common scripting actions such as move commands, string evaluation, and methods to invoke business objects, business services and service scripts. Refer to the Groovy specific JavaDocs for details of the supported methods

Using the Groovy Engine

The system uses an engine version of Groovy to indicate that a script is written entirely in Groovy code and can be processed in a similar way to code written in Java. This avoids the need to convert the script to and from XML format and allows the use of code that acts directly on the system objects with consequent performance benefits.

The following script types support the Groovy engine version:

Plug In Scripts

Plug-in Scripts can be configured to use the Groovy engine if they contain only Groovy Members step types. The system provides an automatically generated superclass that defines the plug-in spot API. Internally, the Groovy code must conform to the system conventions for Java based algorithm types, including the inclusion of an 'invoke' method that is the plug-in entry point, and the definition of 'soft' parameters using annotations.

Groovy Library Scripts

Groovy Library Scripts provide the ability to create groups of common routines written in Groovy that can be called from within other scripts. Scripts of this type must include a single step type of Groovy Library Interface in which the publicly available methods in the library are listed. The supporting code for those methods is defined in one or more Groovy Members step types within the library script. The methods defined in the library can accept arguments and return values of any type. Scripts of this type use the Groovy engine by default and cannot include scripting step types.

Scripts that need to invoke methods from a Groovy library can use the createLibraryScript method provided by the system to instantiate the library interface.

Importing Groovy Classes

The system provides the ability to import one or more Groovy classes into a script. This simplifies coding by allowing those classes to be referenced without having to use the fully qualified package name for the class. The list of imports is defined within a script using a step type of Groovy Imports. Only the allowable base and third party classes may be imported. The ability to import Groovy classes applies to all script types that support Groovy coding.

Note: If your application stack includes classes with the same names as imported classes, the code will still need to reference the full class package name when invoking associated methods to avoid ambiguity.

Plug-In Scripts

Note: This section assumes you are familiar with the notion of plug-in spots (algorithm entities) and plug-ins. See The Big Picture Of Algorithms for more information.

As an alternative to writing a java program for a plug-in spot, the framework supports creating plug-ins using the defined script steps, Xpath commands, Groovy code or a combination of these three options.

The following topics describe basic concepts related to plug-in scripts.

Next in This Section

- A Plug-In Script's API

- Setting Up Plug-In Scripts

A Plug-In Script's API

Like program-based plug-ins, plug-in scripts:

- Run on the application server

- Have their API (input / output interface) defined by the plug-in spot (i.e., plug-in scripts don't get to declare their own API)

- Can only be invoked by the "plug-in spot driver"

For plug-ins configured to use a script engine version, the best way to understand the script's API is to use the View Script Schema hyperlink to view its parameters data area schema.

Notice the two groups: soft and hard. If you are familiar with plug-in spots, you'll recognize these as the classic soft and hard parameters:

- The soft parameters are the values of the parameters defined on the algorithm. Notice they are not named - if you want to reference them in your plug-in script, you must do it by position.

- The hard parameters are controlled by the plug-in spot (i.e., the algorithm entity). Notice that this plug-in spot has a single input parameter called " businessObject/id". Also notice the use= attribute - this shows that this parameter is input-only (i.e., you can't change it in the plug-in script).

Note: XPath. You can click on an element name to see the XPath used to reference the element in your script.

Plug-ins configured to use the Groovy engine version do not use an XML interface for the API and instead are processed in the same way as Java algorithms. The framework supplies a dynamically generated superclass that implements the plug-in spot for Groovy objects. Use the View Script Superclass hyperlink to view this superclass and the methods to set and get the hard parameters.

Note: For plug-in scripts using the Groovy engine version, soft parameters do not appear in the plug-in spot API as defined by the superclass. Plug-ins using only Groovy code define their soft parameters using annotations, in a similar way to Java algorithms, and fetch those values using methods defined in the algorithm code.

Setting Up Plug-In Scripts

The following points describe how to implement a plug-in script:

- Compose your plug-in script, associating it with the appropriate algorithm entity (plug-in spot).

- Create a new algorithm type for the respective algorithm entity, referencing your plug-in script as the program to carry out the algorithm type's function. Only plug-in scripts associated with the algorithm entity may be referenced on the algorithm type.

- Set up an algorithm for the respective algorithm type and plug it in where applicable. Refer to Setting Up Algorithm Types for more information.

Service Scripts

BPA scripts run on the client's browser and guide the end-users through business processes. Service scripts run on the application server and perform server-based processing for BPA scripts, zones and more. You may want to think of a service script as a common routine that is set up via scripting (rather than programming).

The following topics describe basic concepts related to service scripts.

Next in This Section

- A Service Script's API

- Invoking Service Scripts

A Service Script's API

As with any common routine, a service script must declare its input / output parameters (i.e., its API). A service script's API is defined on its schema.

Note: Refer to Schema Nodes and Attributes for a complete list of the XML nodes and attributes available to you when you construct a schema.

Invoking Service Scripts

Any type of script configured to use a scripting engine version may invoke a service script:

- A BPA script may invoke a service script to perform server-based processing.

- Plug-in scripts may invoke a service script (like a "common routine").

- A service script may call another service script (like a "common routine").

Map zones may be configured to invoke service scripts to obtain the data to be displayed. Refer to Map Zones for more information.

Inbound web services support interaction with service scripts allowing the outside world to interact directly with a service script.

You can also invoke a service script from a Java class.

Groovy Library Scripts

Just as service scripts can define common routines written in scripting language, Groovy library scripts are used to define groups of common components or methods written in Groovy. Groovy library code runs on the application server and performs server-based processing for scripts that utilize Groovy code.

The following topics describe basic concepts related to Groovy library scripts.

Next in This Section

- A Groovy Library Script's API

- Invoking Groovy Library Methods

A Groovy Library Script's API

A Groovy library script’s API is composed of one or more public methods whose code is defined in the script’s steps. Those methods are defined in a step type of Groovy Library Interface. A Groovy library script must have one (and only one) step of this type.

Invoking Groovy Library Methods

Any type of script that supports the Groovy Members step type may invoke common methods defined in Groovy library scripts.

Code within a Groovy Members step must create an instance of the Groovy library interface definition to enable the interface methods to be invoked. Refer to the topic Using Groovy Within Scripts for more information.

Debugging Server-Based Scripts

The server can create log entries to help you debug your server scripts.

The logs contain a great deal of information including the contents of the referenced data area for Move data, Invoke business object, Invoke business service and Invoke service script steps.

Refer to the Debug Mode topic in the Configuration Tools chapter for details of how to execute the application in debug mode.

Maintaining Scripts

The script maintenance transaction is used to maintain your scripts. The topics in this section describe how to use this transaction.

Fastpath: Refer to The Big Picture Of Scripts for more information about scripts.

Next in This Section

- Script - Main

- Script - Step

- Script - Data Area

- Script - Schema

- Script - Eligibility

Script - Main

Use this page to define basic information about a script. Open this page using Admin > System > Script.

Note: Script Tips. A context sensitive "Script Tips" zone is associated with this page. The zone provides links to Edit Data Syntax and Advanced Schema Topics so that users can quickly access those online help topics to aid in constructing scripts. In addition, the zone provides links to view the Groovy JavaDocs Viewer and the whitelist of third party Groovy classes so that users can verify the restricted list of classes available for Groovy coding in the script.

Description of Page

Enter a unique Script code and Description for the script. Use the Detailed Description to describe the purpose of this script in detail. Owner indicates if the script is owned by the base package or by your implementation (Customer Modification).

CAUTION:

Important! If you introduce a new script, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Script Type indicates if this is a BPA Script, Plug-In Script, Groovy Library Script or Service Script. Refer to The Big Picture Of BPA Scripts and The Big Picture Of Server Based Scripts for more information.

Accessibility Option appears only for BPA scripts. Set this value to Accessible from Script Menu for any script that may be launched as a stand-alone script. Scripts with this configuration may be linked to a navigation option so that they may be invoked from a menu and may be configured by a user as a favorite script. Set this value to Not Accessible from Script Menu for any script that cannot be launched on its own. For example, any script that is a invoked as a sub-script from another script should have this setting. In addition, any script that is designed to be launched from within a specific portal where certain data is provided to the script should include this setting.

Enter an Application Service if the execution of the script should be secured. The application service should include Execute as one of its access modes. Refer to Securing Script Execution for more information. This field does not appear if the script type is Groovy Library Script.

Algorithm Entity appears only for plug-in scripts. Use this field to define the algorithm entity into which this script can be plugged in.

Business Object appears only for business object related plug-in scripts. Enter the Business Object whose elements are to be referenced by the plug-in script.

Script Engine Version defines key information affecting the context and execution of the script.

- Script engine version values of 1, 2 and 3 define the version of the XML Path Language (XPath) to be used for the script. Versions 2 and 3 use the XPath 2 engine supplied by the XQuery team. This is the same engine used inside the Oracle database. The current script engine version 3 is a modified version that offers performance improvements without impacting existing version 2 scripts.

The default script engine version is 3.0 for plug-in and service scripts. The default version for BPA scripts is 1.0 as higher level versions are not applicable.

There are some additional details to note about script engine version 1.0:

- The XPath library used is Jaxen

- For BPA scripts, it uses the browser’s xpath and XML support except for Internet Explorer where the XSXML parser is used.

- Xpath 1 (and even JavaScript) uses floating point arithmetic, which means that adding a collection of numbers with two decimal places might end up with a value of 10779.079999999998 instead of 10779.08

- A Script Engine Version value of Groovy indicates that only Groovy Members step types are used in the script and signals to the system that there is no need to convert the data to and from an XML interface. This allows for greater efficient in script execution. Only plug-in scripts can select the Groovy engine version.

- The value Framework Version 2.1 Compatibility Mode remains for upgrade purposes. This value should only be applicable to early versions of BPA scripts using syntax that is incompatible with xpath syntax.

Note: The Script Engine Version field does not appear for Groovy Library scripts. The script engine version for these scripts is set to Groovy by default and cannot be changed.

Click the View Script Schema to view the script's data areas on the schema viewer window. This link does not appear if the script engine version is Groovy.

Click the View XSD hyperlink to view a script’s schema definition in XSD format. This link only appears if the script type is BPA Script or Service Script.

The View Script Superclass hyperlink appears only for plug-in scripts using an engine version of Groovy. Click this link to view the code of the runtime generated superclass for the related plug-in spot’s implementation.

The View Script As Text hyperlink appears for server-based scripts only. Click this link to view the internal scripting commands in a separate window.

The tree summarizes the script's steps. You can use the hyperlink to transfer to the Step tab with the corresponding step displayed.

Script - Step

Use this page to add or update a script's steps. Open this page using Admin > System > Script and then navigate to the Step tab.

Note: Time saver. You can navigate to a step by clicking on the respective node in the tree on the Main tab.

Description of Page

The Steps accordion contains an entry for every step linked to the script. When a script is initially displayed, its steps are collapsed. To see a step's details, simply click on the step's summary bar. You can re-click the bar to collapse the step's details. Please see accordions for the details of other features you can use to save time.

Select the Step Type that corresponds with the step. Refer to How To Set Up Each Step Type for an overview of the step types.

CAUTION:

The Step Type affects what you can enter on other parts of this page. The remainder of this section is devoted to those fields that can be entered regardless of Step Type. The subtopics that follow describe those fields whose entry is contingent on the Step Type.

Step Sequence defines the relative position of this step in respect of the other steps. The position is important because it defines the order in which the step is executed. You should only change a Step Sequence if you need to reposition this step. But take care; if you change the Step Sequence and the step is referenced on other steps, you'll have to change all of the referencing steps.

Note: Leave gaps in the sequence numbers. Make sure you leave space between sequence numbers so that you can add new steps between existing ones in the future. If you run out of space, you can use the Renumber button to renumber all of the steps. This will renumber the script's steps by 10 and change all related references accordingly.

Display Step is only enabled on BPA scripts for step types that typically don't cause information to be displayed in the script area (i.e., step types like Conditional Branch, Go to a step, Height, etc). If you turn on this switch, information about the step is displayed in the script area to help you debug the script.

CAUTION:

Remember to turn this switch off when you're ready to let users use this script.

Note: If Display Step is turned on and the step has Text, this information will be displayed in the script area. If Display Step is turned on and the step does not have Text, a system-generated messages describing what the step does is displayed in the script area.

Display Icon controls the icon that prefixes the Text that's displayed in the script area. Using an icon on a step is optional. This field is only applicable to BPA scripts.

Text is the information that displays in the script area when the step executes. You need only define text for steps that cause something to display in the script area.

Fastpath: Refer to How To Substitute Variables In Text for a discussion about how to substitute variables in a text string.

Fastpath: Refer to How To Use HTML Tags And Spans In Text for a discussion about how to format (with colors and fonts) the text that appears in the script area.

The other fields on this page are dependent on the Step Type. The topics that follow briefly describe each step type's fields and provide additional information about steps.

Click on the View Script Schema hyperlink to view the script's data areas. Doing this opens the schema viewer window.

The View Script As Text hyperlink appears for server-based scripts only. Click this link to view the internal scripting commands in a separate window. The presented script syntax is valid within edit data steps.

Next in This Section

- How To Set Up Each Step Type

- Additional Topics

How To Set Up Each Step Type

The contents of this section describe how to set up each type of step.

Next in This Section

- Common Step Types To All Script Types

- Step Types Applicable to BPA Scripts only

- Step Types Applicable to Server Based Scripts only

Common Step Types To All Script Types

The contents of this section describe common step types applicable to all script types using a scripting language engine version.

Next in This Section

- How To Set Up Conditional Branch Steps

- How To Set Up Edit Data Steps

- How To Set Up Go To Steps

- How To Set Up Invoke Business Object Steps

- How To Set Up Invoke Business Service Steps

- How To Set Up Invoke Service Script Steps

- How To Set Up Label Steps

- How To Set Up Move Data Steps

- How To Set Up Terminate Steps

How To Set Up Conditional Branch Steps

Conditional branch steps allow you to conditionally jump to a different step based on logical criteria. For example, you could jump to a different step in a script if the customer is residential as opposed to commercial. In addition, several fields are required for Conditional Branch steps:

Compare Field Type and Compare Field Name define the first operand in the comparison. The Field Type defines where the field is located. The Field Name defines the name of the field. The following points describe each field type:

- Current To Do Information. Use this field type when the field being compared resides on the current To Do entry. Refer to How To Use To Do Fields for instructions on how to define the appropriate Field Name.

- Data Area. Use this field type when the field being compared is one that you put into one of the scripts data areas in an earlier step. Field Name must reference both a data area structure name as well as the field, for example "parm/charType". Refer to How To Reference Fields In Data Areas for instructions on how to construct the appropriate Field Name.

- Page Data Model. Use this field type when the field being compared resides on one of the tab pages in the object display area. Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name.

- Predefined Value. Use this field type when the field being compared is a global variable.

- Temporary Storage. Use this field type when the field being compared is one that you put into temporary storage in an earlier step. The Field Name must be the same as defined in an earlier step.

- User Interface Field. Use this field type when the field being compared resides on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

Condition defines the comparison criteria:

- Use >, <, =, >=, <=, <> (not equal) to compare the field using standard logical operators. Enter the comparison value using the following fields.

- Use IN to compare the first field to a list of values. Each value is separated by a comma. For example, if a field value must equal 1, 3 or 9, you would enter a comparison value of 1,3,9.

- Use BETWEEN to compare the field to a range of values. For example, if a field value must be between 1 and 9, you would enter a comparison value of 1,9. Note, the comparison is inclusive of the low and high values.

Comparison Field Type, Comparison Field Name and Comparison Value define what you're comparing the first operand to. The following points describe each field type:

- Current To Do Information. Use this field type when the comparison value resides on the current To Do entry. Refer to How To Use To Do Fields for instructions on how to define the appropriate Field Name.

- Data Area. Use this field type when the comparison value resides in one of the scripts data areas. Field Name must reference both a data area structure name as well as the field, for example "parm/charType". Refer to How To Reference Fields In Data Areas for instructions on how to construct the appropriate Field Name.

- Page Data Model. Use this field type when the comparison value resides on one of the tab pages in the object display area. Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name.

- Predefined Value. Use this field type when the field being compared is a constant value defined in the script. When this field type is used, use Comparison Value to define the constant value. Refer to How To Use Constants In Scripts for instructions on how to use constants.

- Temporary Storage. Use this field type when the comparison value is a field that you put into temporary storage in an earlier step. The Field Name must be the same as defined in an earlier step.

- User Interface Field. Use this field type when the comparison value resides on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

Note: Conditional field types. The field types Current To Do Information, Page Data Model and User Interface Field are only applicable to BPA scripts.

The above fields allow you to perform a comparison that results in a value of TRUE or FALSE. The remaining fields control the step to which control is passed given the value:

- If TRUE, Go to defines the step that is executed if the comparison results in a TRUE value.

- If FALSE, Go to defines the step that is executed if the comparison results in a FALSE value.

Note: Numeric Comparison. Comparison of two values may be numeric or textual (left-to-right). Numeric comparison takes place only when values on both side of the comparison are recognized as numeric by the system. Otherwise, textual comparison is used. Fields for Current To Do Information, Data Area, Page Data Model, and User Interface Field types are explicitly associated with a data type and therefore can be recognized as numeric or not. This is not the case for fields residing in Temporary Storage or those set as Predefined Values . A Temporary Storage field is considered numeric if it either holds a numeric value moved to it from an explicitly defined numeric value (see above) or it is a resultant field of mathematical operation. A Predefined Value field is considered numeric if the other field it is compared to is numeric. For example, if a numeric field is compared to a Predefined Value the latter is considered numeric as well resulting in numeric value comparison. However, if the two fields are defined as Predefined Values the system assumes their values are text strings and therefore applies textual comparison.

How To Set Up Edit Data Steps

Edit data steps provide a free format region where you can specify commands to control your script processing.

In general, the syntax available within edit data mimics the commands available within the explicit step types. However, there are a few commands that are available only within edit data. For example, the two structured commands: For, and If.

For server-based scripts, you may find it useful to create a few explicit step types and then use the View Script as Text hyperlink on the Script - Step page to better understand the edit data syntax.

Note: Not all BPA step types are supported using the edit data syntax. Refer to the Edit Data Syntax topic below for more information on edit data commands and examples.

Additional field required for Edit data steps:

Enter your scripting commands in the Edit Data Text field. Click the adjacent icon to open a window providing more space for defining the edit data step.

Next in This Section

- Edit Data Syntax

- Script Engine Version 2 and Above Notes

Edit Data Syntax

The topics in this section provide detail of the syntax supported in the edit data step type.

Contents

Comments

Temporary Variables

Context Variables

Move Statement

Go To Statement

Conditional Branch Statement

If Statement

For Statement

List Processing

Functions for Processing a List

Declare and Invoke Schema Based Objects

System and Global Variables

Perform Script and Transfer

Navigate Statement

Invoke Map Statement

Declare BO with BO Group

Generate Edit Map Statements

Terminate Statement

Invoking Groovy Code

Debugging a BPA Script

Comments

You can place comments into your script using the double slash notation // in the first two characters of the edit data step. Example:

//

// quit with error

//

if ("not(customer/securityEnabled)")

terminate with error (8000, 1001 %1="customer/id" %1='not allowed');

end-if;

Temporary Variables

Temporary variables can be declared within all types of scripts. They should be referenced by a leading single dollar sign ('$'). However, temporary variables behave differently in the various script types:

- In BPA Scripts temporary variables remain persistent from one BPA script to another (refer to the Perform Script and Transfer Control statements), which means that you can use temporary variables to communicate between BPA scripts.

- Temporary variables cannot be passed from a BPA script to a service or plug-in script. Only data area elements can be passed between these types of scripts.

- Within service and plug-in scripts, temporary variables remain persistent only for the life of the particular script that declared the variable. This means that temporary variables cannot be passed between plug-in scripts and service scripts, only global variables, context variables and data area elements can be passed between these types of scripts.

Declaring / Initializing / Defaulting Temporary Variables

When using a temporary variable, it should be declared or initialized with an appropriate value before using it. A typical method for declaring a variable is to simply move data to it in a move statement, for example.

move "0" to $index;

Fastpath: Refer to Move to a Temporary Variable for more information on implicit declaration of a temporary variable within a move statement.

For BPA scripts, as mentioned above, temporary variables may be passed from one BPA script to another. As such, it is common to reference a temporary variable in a BPA that should have been initialized by a previous BPA. However, if there is any reason that a temporary variable did not get initialized by a previous BPA, a reference to it will cause an error. It is good practice, therefore, to use the default statement that will initialize temporary variables that are not already created / initialized.

- The following statement will initialize the temporary variable $InputAction – but only if the temporary variable has not yet been initialized:

default $InputAction;

- The following statement will set the value of the temporary variable $InputAction to 'read' – but only if the variable has not yet been initialized:

default $InputAction as 'read';

Note: Scripts should take care not to define variables using a reserved keyword. The following table lists the reserved keywords.

Keyword

add

as

asError

bpa

branch

data

declareBO

declareBS

declareDA

declareMap

declareSS

default

delete

edit

element

else

end-edit

end-for

end-if

error

escape

evaluate

fastAdd

fastUpdate

for

goto

if

in

invokeBO

invokeBS

invokeMap

invokeSS

label

map

move

navigate

navigateAndReloadDashboard

null

page

performScript

popup

read

readWithoutVersion

replace

suppress

target

terminate

to

transferControl

update

using

warn

with

Context Variables

Context variables are only available within service scripts. The context variable will be available for the duration of the service script and all that it invokes. Therefore, you can use a context variable within a service script to communicate information to a lower level service script or schema. They should be referenced by leading double dollar signs ('$$').

Note: Because context variables are available for lower level scripts, they may sometimes be referred to as global variables or global context variables. But they should not be confused with global variables.

Declaring / Initializing / Defaulting Context Variables

When using a context variable, it should be declared or initialized with an appropriate value before using it. A typical method for declaring a variable is to simply move data to it in a move statement, for example.

move 'context variable' to $$contextVariable;

Fastpath: Refer to Move using a Context Variable for more information.

Move Statement

The move statement copies a source value to a target. The following table highlights various options supported in the move statement.

Statement

Example Description

Example Syntax

Move to Element
move "xpath" to "xpath";

Note: An XPath expression is surrounded by double quotes.

Move statement with simple XPath reference.

move "acct/totalBalance" to

"parm/formattedValue";

Move statement with XPath concatenate function.

move "concat(person/firstName, ',',

person/lastName)"

to "parm/fullName";

Move statement with XPath substring-before function.

move "substring-before(parm/fullName,',')"

to "person/firstName";

Move statement with XPath substring-after function.

move "substring-after(parm/fullName,',')"

to "person/lastName";

Move statement with XPath substring function.

move "substring(parm/date,1,4)"

to "parm/year";

Move to Element
move 'literal' to "xpath";

Note: A literal value is surrounded by single quotes.

Move statement using a literal string.

move 'okay for mailing'

to "account/preferences[type="mail"]/text";

Move to Element
move 'Boolean' to "xpath";

Move statement with Boolean as literal string.

if ("account/balance > 0")

move 'true'

to "account/hasDebitBalance";

end-if;

Moving an expression, which results in a Boolean. Note that the filter in the example below is located on a group node.

<schema>

<account>

<hasDebitBalance type="boolean"/>

<balance/>

</account>

</schema>

move "boolean(account[balance>0])"

to "account/hasDebitBalance";

Move to Group
move "xpath" to "xpath";

Move a set of elements from one group with another – where the element names are valid for the target schema.

move "account/custInfo" to "person";

This statement is equivalent to the following statement:

move "account/custInfo/*" to "person/*";

Move using a Temporary Variable

When moving to a temporary local variable, it is not surrounded by double quotes.
move "xpath" to $variable;

move "count(Person/names/personName)

+ count(Person/ids/personId)"

to $PersonChildCount;

When moving from a temporary variable, the variable is surrounded by double quotes.
move "$variable" to “xpath”;

move "$AccountBalance"

to "parm/formattedValue";

Move using a Context Variable

move "xpath" to $$variable;

move $$variable to “xpath”;

Context variables, source or target, are referenced without any double quotes.

move 'context value'

to $$contextVariable;

//

// here, we move from a context variable.

move $$contextVariable

to "MarketMessage/sender";

Move using a Dynamic Location
move "xpath" | 'literal' to evaluate("xpath" | $variable);

move evaluate("xpath" | $variable) to "xpath" | $variable;

The evaluate statement allows your move source or target location to be dynamically derived from a variable or schema element location.

move 'literal'

to evaluate("schemaLocation");

//

move "schemaLocation"

to evaluate($Variable);

move evaluate("schemaLocation")

to $Variable;

//

move evaluate($Variable)

to "schemaLocation";

Move escape
move escape("xpath" | $variable) to "xpath" | $variable;

Move escape is only available for service scripts and plug-in scripts. The escape statement scans your source text value for HTML content and escapes it, i.e. replaces any HTML-like characters with special characters that are escaped from HTML rendering. By doing so the text would be displayed as plain text when displayed as part of an HTML element.
Note: You should only use this function if the text is to be displayed as part of an HTML element and is suspected to contain HTML-like characters or even malicious HTML that should not be rendered as HTML. If incorrectly displayed using a non HTML element, the special escape characters, if any would be visible as part of your text. Refer to the UI Map Attributes and Functions for more information on how to define an element to display HTML content.

move escape("schemaLocation")

to $Variable;

//

move escape($Variable)

to "schemaLocation";

Move null
move null to "xpath";

You can remove information from the XML instance document through the special syntax of move 'null'. Note that you can specify either a node name in the XPath expression or a group name. If you specify a group then the group and all child elements will be eliminated from processing.

Remove a node and all of its child nodes:

if ("boolean(customer/securityEnabled)")

goto updateInfo;

else

move null to "customer";

end-if;

Remove all child nodes of a group node with the suffix '/*'.

if ("boolean(customer/securityEnabled)")

move null to "customer/*";

end-if;

Go To Statement

The edit data step supports functionality analogous to the Go To step type. The syntax is goto label; where the label represents another location within the edit data text field (identified by this label) or represents another step in the script.

The following is an example of going to another location in the same step identified by the label addSpouse.

if ("string(parm/spouse/name) != $BLANK")

goto addSpouse;

end-if;

addSpouse: invokeBO 'Person' using "parm/spouse" for add;

The following is an example of going to a different step within the same script. The step sequence is the reference used as the label.

if ("string(parm/spouse/name) != $BLANK")

goto 110;

end-if;

.

.

.

110: invokeBO 'Person' using "parm/spouse" for add;

Conditional Branch Statement

The edit data step supports functionality analogous to the Conditional Branch step type. The syntax is branch (“xpath”) goto label else label; where:

- The XPath condition in the branch statement must evaluate to a Boolean value of True or False.

- The targets for the goto and else statements are labels that represent another location within the edit data text field (identified by this label) or represent another step in the script.

The following example uses labels for addSpouse and addAccount

branch ("string(parm/spouse/name) != $BLANK") goto addSpouse else addAccount;

If Statement

The if statement is similar to the conditional branch statement. Either can be used to structure the logic of your script. This statement may optionally include an else statement but it should always end with an end-if statement.

Note: This is an example of a statement that is not represented as a separate step type. It is only available within the edit data text.

The syntax is if (“xpath”) else end-if;. The XPath condition must evaluate to a Boolean value of True or False. The following are some examples.

Example where the XPath contains a simple logical condition.

if ("string(parm/spouse/name) != $BLANK")

//

// Create spouse since spouse name present

goto addSpouse;

else

//

// Create account without spouse

goto addAccount;

end-if;

Example where the XPath contains a complex condition.

if ("string(parm/spouse/name) != $BLANK and string(parm/hasSpouse) = true or boolean(parm/requireSpouse)")

//

// Create spouse since spouse name present

goto addSpouse;

end-if;

Example of a stacked set of statements used to evaluate multiple possible values of a field.

if ("parm/rowCount = 0")

//

// no rows found

goto quit;

end-if;

if ("parm/rowCount = 1")

//

// one row found

goto process;

end-if;

if ("parm/rowCount > 1")

//

// more than one row found

goto quit;

end-if;

quit: terminate;

The following XPath shows Boolean based on the existence of the node. In this example, if the node exists in the XML instance document being processed, the statement will evaluate to True. If no element is found, the statement evaluates to false.

Note: When treating XPath nodes as Boolean variables be aware that an empty node evaluates to True. Only a missing node return False.

if ("boolean(parm/spouse/name)")

goto addSpouse;

else

//

// Create account without spouse

goto addAccount;

end-if;

if ("not(parm/spouse/name)")

//

// Create account without spouse

goto addAccount;

else

goto addSpouse;

end-if;

For Statement

The for statement creates a list of nodes or values depending on your XPath expression. If you specify a list node then every child node of the list, along with its contents, will be available within the loop. If you specify a child node directly, then a list of values only will be available within the loop.

Note: For more information on creating new entries in a list, please refer to the creating a new list instance example.

Note: This is an example of a statement that is not represented as a separate step type. It is only available within the edit data text.

The syntax is for ($variable in "xpathList") end-for;. The XPath condition must evaluate to a Boolean value of True or False.

The following examples are based on this sample schema:

<schema>

<SAList type="list">

<id/>

<balance/>

</SAList>

<SAContributor type="list">

<id/>

</SAContributor>

</schema>

Example that specifies the list node in the XPath expression where all child nodes are available for processing.

move "0" to $AccountBalance;

move "0" to $index;

for ($SAList in "SAList")

move "$SAList/balance + $AccountBalance" to $AccountBalance;

//

// keep track of each SA contributing to the balance in the SA Contributor list

move "1 + $index" to $index;

move "$SAList/id" to "SAContributor[$index]/id";

end-for;

Example that specifies a child node within the list node in the XPath expression. Only values of that node are available for processing.

move "0" to $AccountBalance;

for ($SABalance in "SAList/balance")

move "$SABalance + $AccountBalance" to $AccountBalance;

end-for;

Example that shows that a filter can be used to limit the rows selected by the for loop.

move "0" to $AccountDebitBalance;

for ($SAList in "SAList[Balance>0]")

move "$SAList/balance + $AccountDebitBalance" to $AccountDebitBalance;

end-for;

Example that shows the use of a filter when specifying child nodes.

move "0" to $AccountCreditBalance;

for ($SABalance in "SAList[Balance<0]/balance")

move "$SABalance + $AccountCreditBalance" to $AccountCreditBalance;

end-for;

List Processing

This section provides details about processing lists. The examples in this section reference the following schema:

<schema>

<parm type="group">

<name/>

</parm>

<Person type="group">

<names type="list">

<type/>

<name/>

</names>

</Person>

</schema>

Referencing a List Element. You can move a value to a particular list instance by referencing an identifying node in the list within a filter. The syntax is move "xpath" to "xpathList[filter]/element"; Example:

move "parm/name" to "Person/names[type='main']/name";

Creating a New List Instance. A special notation can be used within a move target statement to indicate a new list instance should be created. The "+" indicates to the script processor that a new instance of a list should be initiated for the target element. The syntax is move "xpath" to "+xpathList"; Example:

move "parm/name" to "Person/+names/name";

Deleting a List Instance. An XML list entry can be deleted from the database by moving an action attribute of 'delete' to the element name. To cause a database delete of a list entry requires an attribute of action="delete" in the target node and a subsequent update BO interaction. The syntax is move 'delete' to "xpathList@action"); Example:

if ("parm/action = 'd'")

move "0" to $index;

for ($CCList in "CCList")

move "1 + $index" to $index;

if ("$CCList/id = parm/id")

move 'delete' to "CCList[$index]@action";

goto update;

end-if;

end-for;

end-if;

The following shows the resulting XML.

<root>

<CCList>

<id>9876538976</id>

<balance>309.98</balance>

</CCList>

<CCList action="delete">

<id>4321125899</id>

<balance>87.45</balance>

</CCList>

</root>

Note: Deleting a list instance through use of the action attribute is risky if iterative BO interactions are required. The XML document that contains the list instance to be deleted will not be altered after a successful BO interaction, which means the document will still contain the list instance even though it no longer exists. To solve this problem, it is essential to re-read the BO after any BO update where the action attribute of 'delete' has been used.

Note: An alternative to the delete attribute described here, is to use the BO action of replace. Manipulating a list to use the replace action avoids the problem described above concerning stale information in request documents post BO update.

Functions for Processing a List

XPath provides several functions that are useful to process elements of a list including count, sum and last.

The following examples are based on this sample XML document:

<xml>

<ft>

<type>bill</type>

<date>20100101</date>

<amt>30.30</amt>

<cat>tax</cat>

</ft>

<ft>

<type>adj</type>

<date>20100301</date>

<amt>20.20</amt>

<cat>int</cat>

</ft>

<ft>

<type>bill</type>

<date>20100201</date>

<amt>10.10</amt>

<cat>tax</cat>

</ft>

</xml>

The following is an example of a sum. The syntax is move "sum(xpathList/element)" to $variable; The example sums the total balance.

move "sum(ft/amt)" to $TotalBalance;

The following is an example of a sum using a filter to get a subtotal. The example sums the balance of the entries that have the ‘tax’ category.

move "sum(ft[cat='tax']/amt)" to $TaxBalance;

The following is an example of a count. The syntax is move "count(xpathList)" to $variable; The example finds the count of the number of FT entries in the list.

move "count(ft)" to $TranCount;

The following is an example of ‘last’, which is used to locate the last entry. The syntax is move "last(xpathList)" to $variable; The example finds the last amount in the FT list.

move "ft[last()]/amt" to $LastAmount;

Declare and Invoke Schema Based Objects

You can invoke a business object, business service or service script within the edit data step. To support the dynamic invoke, a dynamic data area name can be declared.

The schema being declared may be a business object (BO) schema, a business service (BS) schema, a service script (SS) schema, data area (DA) schema or a UI map schema. The declare statement will differ based on the type of schema, but the syntax is analogous.

- declareBO 'BO Name' | $variable | "xpath" as 'DynamicDataArea';

- declareBS' BS Name' | $variable | "xpath" as 'DynamicDataArea';

- declareSS 'SS Name' | $variable | "xpath" as 'DynamicDataArea';

- declareDA 'DA Name' | $variable | "xpath" as 'DynamicDataArea';

- declareMap 'Map Name' | $variable | "xpath" as 'DynamicDataArea';

When invoking a BO, BS or SS, the name of the object can be specified as a literal or it can be a value contained within an element or a variable. For every Invoke, you must supply an XPath reference to a group name.

- When invoking a business object, an action must be supplied. The syntax is invokeBO 'BO Name' | $variable | "xpath" using "xpath" for action;. The valid actions are as follows:

- read. This action reads the current view of the BO data.

- add. This action will add the object and read and return the resulting view of the BO.

- fastAdd. This action will add the object but does not perform a subsequent ‘read’ to return the resulting view of the BO.

- update. This action will update the object and read and return the resulting view of the BO. This action executes a 'merge' of the information specified in the invoke statement's request XML document with existing BO data. Using this action allows the script to only indicate the elements that are changing.

- fastUpdate. This action will update the object but does not perform a subsequent ‘read’ to return the resulting view of the BO.

- delete. This action deletes the object.

- replace. This action is an alternate to the update action. The replace action completely replaces existing BO data with the information in the request document. Typically, the replace action is used when a BO contains a list because it is easier to simply replace all instances of a list rather than attempt a list merge, which requires special logic to delete a list instance explicitly.

Note: The replace action must be used when using the UI map functionality to Upload a CSV File.

Examples:

invokeBO 'BusinessObject' using "dataArea" for fastAdd;

invokeBO $variableBO using "dataArea" for fastUpdate;

invokeBO "daName/boElement" using "dataArea" for replace;

- The syntax of the invoke statements for both a business service and service script are similar. The BS / SS is specified along with the XPath reference to the group name:

- invokeBS 'BS Name' | $variable | "xpath" using "xpath";

- invokeSS 'SS Name' | $variable | "xpath" using "xpath";

The examples use the invokeBS statement but the statements are similar for the invokeSS statement.

invokeBS 'BusinessService' using "dataArea";

invokeBS $variableBS using "dataArea";

invokeBS "daName/bsElement" using "dataArea";

Note that for BPA scripting, the invoke statements may also indicate how to handle warnings.

Syntax

Description

Examples

with warn asError

Indicates that a warning should be treated as an error displayed in the UI map. The text asError is optional.

invokeBO 'BusinessObject' using "dataArea" for add with warn asError;

invokeSS 'ServiceScript' using "dataArea" with warn;

with warn popup

Indicates that a warning should be presented in the standard framework popup. In this scenario, the user is presented with standard OK and Cancel buttons. If the user clicks OK, it means that the process should continue. If the user clicks Cancel, the processing should discontinue.

invokeBS "daName/bsElement" using "dataArea" with warn popup;

with warn suppress

Indicates that a warning should be suppressed. This is the default if no warning syntax is added to the invoke statement.

invokeBS "daName/bsElement" using "dataArea" with warn suppress;

invokeSS 'ServiceScript' using "dataArea";

Note: For service scripts, all objects invoked from the service script will inherit their warning level. Therefore, if the service script is invoked with warn, all nested invoke statements will also be invoked with warn.

For BPA scripts, there should also be logic following the invocation to handle errors and warnings (if with warn as popup is used). The system variables $ERROR and $WARNING are provided to interpret the results. $WARNING is set to true if the user has clicked the Cancel button. Also note that the product provides a BPA Script F1–HandleErr that may be used to display the error. The following is an example of typical error handling logic.

invokeBO "F1-DetermineBo/output/bo" using "boSchema" for update with warn popup;

if ("$WARNING")

terminate;

end-if;

if ("$ERROR")

transferControl 'F1-HandleErr';

end-if;

System and Global Variables

The following tables highlight system and global variables available for script writing.

System Variables - All Script Types

The following system variables are available for all script types (service scripts, plug-in scripts, and BPA scripts).

Variable

Description

Example

$BLANK

Represents an empty node.

if ("string(parm/spouse/name) != $BLANK")

goto addSpouse;

end-if;

$CURRENT-DATE

Represents the current date.
For BPA scripts, this is the browser date.

For server scripts this is the server date (and is affected by the system date override logic).

move "$CURRENT-DATE" to $tempDate;

$CURRENT-STD-DTTM

Represents the current date-time expressed in standard time (meaning without any adjustments for summer time / daylight savings time).

move "$CURRENT-STD-DTTM" to $tempDateTime;

$DEVICE-OS

Represents the user’s device operating system.

move "$DEVICE-OS" to $tempDeviceOs;

$DEVICE-BROWSER

Represents the user’s device browser.

move "$DEVICE-BROWSER" to $tempDeviceBrowser;

$DEVICE-DISPLAY-TYPE

Represents the user’s device screen display type whether it is Desktop size or Medium or Small size. Returned values may be like oraDesktop, oraTablet and oraPhone.

move "$DEVICE-DISPLAY-TYPE" to $tempDeviceDisplayType;

$DEVICE-INFO

Provides the combination of all three device properties (DEVICE-OS, DEVICE-BROWSER and DEVICE-DISPLAY-TYPE) and each property value is separated by semi-colon.

move "$DEVICE-INFO" to $tempDeviceInfo;

System Variables - BPA Scripts Only

The following system variables are only available / applicable for BPA script types.

Variable

Description

Example

$DOUBLE_QUOTE

Represents a double quote.

move "$DOUBLE_QUOTE" to $tempField;

$SINGLE_QUOTE

Represents an apostrophe.

move "$SINGLE_QUOTE" to $tempField;

$SPACE

Contains a single space value.

move "$SPACE" to $tempField;

$SYSTEM-DATE

Represents the server date. Note that this date is affected by the system date override logic)

move "$SYSTEM-DATE" to $tempDate;

System Variables - Server Scripts Only

The following system variables are only available / applicable for service script and plug-in script types.

Variable

Description

Example

$ADDITIONAL-IP-INFO

An HTTP request includes an "additional IP address" header field. This may be populated by an implementation if there is some information available on the proxy server or load balancer, such as the originating IP address.

move "$ADDITIONAL-IP-INFO" to "parm/request/headerIpAddress";

$CURRENT-DTTM

Represents the current date-time.

move "$CURRENT-DTTM" to $tempDateTime;

$F1-INSTALLATION-TIMEZONE

Represents the time zone code defined on the installation options.

move "$F1-INSTALLATION-TIMEZONE" to $timeZone;

$LANGUAGE

Represents the language code the script is using. Typically this is the user’s default language.

move "$LANGUAGE" to $tempLanguage;

$PROCESS-DATE

Represents the process date. The process date differs from the current date because the process date will remain consistent throughout the duration of the process being executed. For example, if a service script stores several business objects – the process date is initialized at the start of the service script execution and each business object will have the same process date defaulted. The current date, especially the current date time, will reflect the actual time of processing.

move "$PROCESS-DATE" to $tempDate;

$PROCESS-DTTM

Represents the process date-time. Note that the process date and time is initialized at the start of a particular process and will not reflect the exact date and time of an update.

move "$PROCESS-DTTM" to $tempDateTime;

$REQUESTING-IP-ADDRESS

Represents the IP address from the HTTP request. Note that if the request is routed through a proxy server or load balancer, this IP address is be the IP address of the proxy or load balancer, not the IP address of the end user. Refer to the $ADDITIONAL-IP-INFO variable for information.

move "$REQUESTING-IP-ADDRESS" to "parm/request/systemIpAddress";

$USER

Represents the user ID of the user executing the script.

move "$USER" to $tempUser;

Global Variables

BPA scripts and service scripts have access to the values defined in Global Context.

When a BPA script is launched from the user interface, these variables will be automatically initialized. They may be referenced with a single dollar sign in front of the field name. For example if PER_ID is a supported global variable, then $PER_ID can be referenced within the BPA script:

move "$PER_ID" to "schema/customerId";

For service scripts, global variables may only be referenced if the service script has been invoked directly from a BPA script or a zone on a portal. When a service script is invoked from a BPA script or portal zone, it will have access to the suite of global context variables populated in the UI session. For service scripting, the global fields must be prefixed by two dollar signs (instead of one like in BPA scripting). For example if PER_ID is a supported global context variable, then $$PER_ID can be referenced within the service script.

move $$PER_ID to "schema/customerId";

Note: As described in Context Variables, a service script may declare context variables that use the same two dollar sign syntax.

Perform Script and Transfer Control Statements

The edit data step supports functionality analogous to the Perform script step type and the Transfer Control step type. These are both applicable only to BPA scripts.

Syntax

Valid Values

Comments

performScript

'BPA Script Name'

Script to perform is explicitly provided.

$Variable

Script to perform is found in a variable.

"XPath"

Script to perform is found in an element, referenced by its XPath.

transferControl

Analogous to the performScript statement

Note: When the script named in the performScript statement has finished, control will be returned to the calling BPA script. When the script named in the transferControl statement has finished, you will not be returned to the calling script, complete control will be granted to the transferred to script.

Navigate Statement

The edit data step supports functionality analogous to the Navigate to a page step type. This is applicable only to BPA scripts.

Syntax

Valid Values

Comments

navigate

'Navigation Code'

Navigation option is explicitly provided.

$Variable

Navigation option is found in a variable.

"XPath"

Navigation option is found in an element, referenced by its XPath.

In addition, the edit data step supports the ability to indicate that the dashboard should be refreshed when navigating. This is only applicable to BPA scripts.

Syntax

Valid Values

navigateAndReloadDashboard

Analogous to the navigate statement

Declare BO with BO Group

This statement is specific to BPA scripts that plan to use the base script Main BO Maintenance Processing (F1–MainProc) for its Generate Edit Map statements. This script expects that the data used to display in the map is within a boGroup tag.

Syntax

Valid Values

Comments

declareBOWithBOGroup

'BO Name'

BO is explicitly provided.

$Variable

BO is found in a variable.

"XPath"

BO is found in an element, referenced by its XPath.

The following table highlights additional syntax for this statement.

Syntax

Valid Values

as

'Dynamic Schema Name'

Examples:

declareBOWithBOGroup 'BusinessObject' as 'newMapSchema';

declareBOWithBOGroup $variableBO as 'newMapSchema';

declareBOWithBOGroup "daName/boElement" as 'newMapSchema';

Invoke Map Statement

The edit data step supports functionality analogous to the Invoke map step type. This is applicable only to BPA scripts.

Syntax

Valid Values

Comments

invokeMap

'Map Name'

UI Map is explicitly provided.

$Variable

UI Map is found in a variable.

"XPath"

UI Map is found in an element, referenced by its XPath.

The following table highlights additional syntax for this statement.

Syntax

Valid Values

Comments

using

"Data Area group name"

Indicates the data area to be passed to and from the server when rendering the HTML form associated with the map.

target

bpa

page

popup

Refer to the Invoke map step type for more information about the target values.

If the UI map is configured to return a value, then it can be evaluated using the $MAP-VALUE variable.

invokeMap 'UI Map' using "dataArea";

invokeMap $variableMap using "dataArea";

invokeMap "daName/mapElement" using "dataArea" target bpa;

// $MAP-VALUE is a variable returned by the invoked map.

if ("$MAP-VALUE='continue' ")

goto 300;

else

terminate;

end if;

Generate Edit Map Statements

The 'generate edit map' statements are used to dynamically generate and launch a UI edit map based on a schema definition. The schema used may be a BO schema, a BS schema, an SS schema or a DA schema. This is applicable only to BPA scripts. The generate statement will differ based on the type of schema, but the syntax is analogous.

Syntax

generateBOEditMap

generateBSEditMap

generateSSEditMap

generateDAEditMap

The BO code / BS code / SS code / DA code may be specified using a literal (surrounded by single quotes), as a temporary variable or by referencing an XPath schema location (surrounded by double quotes).

The following table highlights additional syntax for this statement.

Syntax

Valid Values

Comments

using

"Data Area group name"

Indicates the data area to be passed to and from the server when rendering the HTML form associated with the map.

target

bpa

page

popup

The target values indicate where the generated map should be displayed as described in the Invoke map step type. If the UI map is configured to return a value, then it can be evaluated using the $MAP-VALUE variable.

The examples use the generateBOEditMap but the statements are similar for the other schema types.

generateBOEditMap 'BO Name' using "dataArea";

generateBOEditMap $variableMap using "dataArea";

generateBOEditMap "daName/mapElement" using "dataArea" target bpa;

// $MAP-VALUE is a variable returned by the invoked map.

if ("$MAP-VALUE='continue' ")

goto 300;

else

terminate;

end if;

Terminate Statement

The edit data step supports functionality analogous to the Terminate step type.

The following is an example of a simple terminate step that will stop the script.

if ("not(parm/spouse/name)")

terminate;

else

goto addSpouse;

end-if;

The terminate with error statement is only available in a service script.

Syntax

Attributes

Comments

terminate with error (x, y %n= element= )

'x' represents the message category

Required.

'y' represents the message number

Required.

%n="Element XPath" or %n='literal'

Specify the substitution parameters supported by the message using either literal values or XPath references.

element="Element XPath"

Optionally specify an element name within a UI map to highlight as part of the error.

Example:

if ("string(customer/lastName) = $BLANK")

terminate with error (8000, 1001 %1="customer/lastName" %2='Last name required' element='customer/lastName');

end-if;

Fastpath: For more information on presenting errors in a UI map, please refer to Display Errors.

Invoking Groovy Code

The edit data step supports the ability to invoke Groovy code using the syntax invokeGroovy 'method'; where 'method' is the name of a method defined in a Groovy Members step within the script. Only methods that do not receive arguments and return void can be invoked in this way. However, the method invoked from the edit data step can be supported by additional Groovy code in other Groovy Members step types.

Example Edit Data step:

invokeGroovy 'invoke';

Example Groovy Members step:

void invoke() {

initParms()

readBO()

initConfig()

retrieve()

updateBO()

}

Debugging a BPA Script

If a BPA script has height greater than zero, then selected nodes of the script's data area can be displayed at runtime. The XML data is displayed during script execution within the BPA script's display area. Specify the XPath of an XML node from any of the BPA script's data areas, between the paired characters: '%+' and '+%'.

For example, the entire contents of the schema group node named 'input', and the specific contents of the schema element named 'output/status' will be displayed in the BPA script's display area. The debug text must be entered into the BPA script's text area and not within the script's edit data field. Debug text can be declared for any explicit step of the script.

display input: %+input+% , and output status: %+output/status+%

Script Engine Version 2 and Above Notes

Scripting using the engine version 2 or above requires some extra syntax to take advantage of XPath 2 functionality. In general, any variable declared will be assumed to be a string. This means, that if you intend to construct a mathematical statement then it is necessary to explicitly declare the data type of variables as integers, numbers, or dates.

Note: Unless otherwise noted, all XPath examples in this topic are for the Version 1 engine – which means XPath 1. Statements that function using XPath 1 will not necessarily work for XPath 2. This is especially true when executing math, see below for examples.

Date and Time Arithmetic

XPath date/time and interval data types support arithmetic operations ('+', '-', '*' etc.) and functions, which can be used for time calculations in the same way as '1 + xs:integer(value)' is used for numeric calculations.

Compare time duration:

if ("(xs:dateTime(fn:current-dateTime()) - xs:dateTime($updateDateTimeX))

ge xs:dayTimeDuration(concat('PT', BO/hoursBetweenStatisticsUpdate, 'H'))")

goto 60;

end-if;

Compare one date to another:

if ("xs:date(parm/endDate) < xs:date(parm/startDate)")

terminate with error (11108, 11507 element='endDate');

end-if;

Compare a date against today's date:

if ("xs:date(parm/startDate) <= xs:date($CURRENT-DATE)")

terminate with error (11108, 11507 element='endDate');

end-if;

Calculate the end of month:

// covert to ISO

move "concat($year,'-',$mon2,'-01T00:00:00')" to $monthStart;

// calculate

move "xs:dateTime($monthStart) + xs:yearMonthDuration('P1M') - xs:dayTimeDuration('P0DT1S')"

to $monthEnd;

// convert from ISO to OUAF

move "concat($year,'-',$mon2,'-',substring(string($monthEnd),9,2),'-23.59.59')" to $endDateTime;

Note: XPath date/time/interval formats use the ISO standard, which needs to be converted to/from formats supported in the framework.

Comparing Date/Times in String Format

Any ISO-like string format for date/time preserves the YYYY MM DD HH MM SS sequence, which is zero-padded. Regardless of separators, this format will remain appropriate for comparison operations. In particular, date/time values in the framework format “YYYY-MM-DD.HH.MM.SS” can be used with “=”, “!=”, as well as “>”, “>=”, “<”, “<=” operators.

// retrieve framework date/time value

invokeBS 'CM-MAXMSRMT' using "CM-MAXMSRMT";

move "string(cm-MAXMSRMT/results[1]/measurementDateTime)" to $lastMsmtDT;

// construct another date/time

move "concat($year,'-01-01-00.00.00')" to $startDateTime;

// compare using string operators

if ("$lastMsmtDT >= $startDateTime")

move "substring($lastMsmtDT,1,4)" to $latestMsrmtYear;

Converting Date/Times Between Framework and ISO

Conversion of date/time from framework format to ISO is only necessary for date/time arithmetic. Comparisons can be done with the framework format directly. The only difference between the framework format and ISO date/time formats is in the separators:

Framework: “YYYY-MM-DD.HH.MM.SS”

ISO: “YYYY-MM-DDTHH:MM:SS”

Example of converting from the framework format to ISO:

move "concat(substring($ouafDT, 1, 10), 'T', translate(substring($ouafDT, 12),'.',':'))" to $isoDT;

Example of converting from ISO to the framework format:

move "concat(substring($isoDT, 1, 10), '.', translate(substring($isoDT, 12),':','.'))" to $ouafDT;

Round Money With a Dynamic Currency Scale

Because different currencies support a different number of decimals, the framework provides an API for rounding a monetary amount based on a given currency.

move "parm/amount" to $qnty;

move "currency/decimals" to $decimals;

move "fn:round(xs:decimal($qnty) * math:exp10(xs:double($decimals)))

div math:exp10(xs:double($decimals))" to "parm/roundedAmount";

Looping through Sequences

In XPath 2 it is possible to organize a for-loop over a sequence of integers, not only a node list.

This example shows a loop over a range of months. This is a sequence-forming construct in XPath. The XPath node list, which we are familiar with, is just another type of sequence.

for ($month in "1 to 12")

This example shows a loop over a give range of years in descending order:

for ($year in "fn:reverse(parm/startYear to parm/endYear)")

move "concat($year,'-01-01-00.00.00')" to $startDateTime;

move "concat($year,'-12-31-23.59.59')" to $endDateTime;

...

This example shows a loop through a node list using ‘index’, so that other node lists can be accessed:

for ($idx in "1 to count(parm/touData/touList)")

move "parm/touData/touList[$idx]" to $tou;   // access any list with this index

The above syntax can be used as an elegant alternative to maintaining indices separately, for example instead of the following:

move “0” to $idx;

for ($item in "parm/touData/touList")

move “1 + xs:integer($idx)” to $idx;

String Padding and Decimal Formatting

This is used with specific input formats or output formatting. It is applicable to zero, space and other types of padding.

This example shows prefixing for date/time components, for example producing “2010-01-02” instead of “2010-1-2”.

move "substring(concat('0',string($month)), string-length(string($month)), 2)" to $mon2;

This example shows suffixing for adding decimal zero-padded alignment, for example producing “12.30” and “4.00” instead of “12.3” and “4”. The example performs 3 tasks: rounding to 2 decimals, inserting a period if necessary, and zero padding.

// round and zero-pad to 2 decimals

move "$item/amount" to $qty;

move "fn:round(xs:double($qty) * 100) div 100" to $qty;

move "string($qty)" to $qty;

move "concat(substring-before(concat($qty,'.'),'.'),'.',substring(concat(substring-after($qty,'.'),'00'),1,2))" to $qty;

Ternary Operation

This makes a choice between values based on a condition, so that it could be used in a single expression instead of an if/else block. It is know in C/C++ as ‘cond ? value1 : value2’ or in BASIC as ‘IFF(cond, value1, value2)’. In XPath the syntax is: "if (cond) then value1 else value2". Note this is not the top-level scripting if-statement block.

In XPath this is an expression, which can be combined with other expressions. In scripting it can be used as:

move "if (string(D1-UnitOfMeasure/measuresPeakQuantity) = 'D1MP') then 'D1MX' else 'D1SM' " to $func;

Pipeline Processing

In scripting, it is not easy to create a simple reusable piece of code as there are no local functions, and a separate script call is a coding overhead and requires packing/unpacking parameters. To avoid copying and pasting the same code block between similar script stages, consider ‘pipelining’, which is breaking the overall process into separate top-level steps, some of which could be shared between alternating paths. This is common for parameter preparation and output formatting. An intermediate result between stages can be stored in a “parm” substructure.

Instead of this code:

if ("type = A")

prepare params ...

call services for A ...

format output ...

end-if;

if ("type = B")

prepare params ...

call services for B ...

format output ...

end-if;

Consider this alternative:

prepare params ...

if ("type = A")

call services for A ...

end-if;

if ("type = B")

call services for B ...

end-if;

format output ...

XPath 2 Functions

Script engine versions 2 and above support XQuery 1.0 Functions and Operators, and the XQuery 1.0 standard itself with some minor limitations. Below are the URLs to both specifications. The first link has the functions/operators available to use from XQuery.

- http://www.w3.org/TR/xpath-functions/

- http://www.w3.org/TR/xquery/

The following can only access local file systems. (For other protocols like http they will return an empty sequence):

- fn:doc

- fn:collection

How To Set Up Go To Steps

Go to steps allow you to jump to a step other than the next step. Additional fields required for Go To steps:

Next Step defines the step to which the script should jump.

How To Set Up Invoke Business Object Steps

Invoke business object steps allow you to interact with a business object in order to obtain or maintain its information.

The following additional fields are required for Invoke business object steps:

Use Warning Level to indicate whether warnings should be suppressed and if not, how they should be presented to the user. By default, warnings are suppressed. If Warn As Popup is used, the warning is displayed using the standard popup dialog. If Warn As Error is used processing is directed to the If Error, Go To step. This field is only applicable to BPA scripts.

Group Name references the data area to be passed to and from the server when communicating with the Business Object. Indicate the Action to be performed on the object when invoked. Valid values are Add, Delete, Fast Add (No Read), Fast Update (No Read), Read, Replace, Update.

Note: Performance note. The actions Fast Add and Fast Update should be used when the business object's data area does not need to be re-read subsequent to the Add or Update action. In other words, the Add and Update actions are equivalent to Fast Add + Read and Fast Update + Read .

The business object call will either be successful or return an error. The next two fields only appear when the call is issued from a BPA script, to determine the step to which control is passed given the outcome of the call.

If Success, Go To defines the step that is executed if the call is successful. This field is only applicable to BPA scripts.

If Error, Go To defines the step that is executed if the call returns on error. Please note that the error information is held in global variables. This field is only applicable to BPA scripts.

Note: Error technique. Let's assume a scenario where a business object is invoked from a BPA script and the call returned an error. If the BPA script is configured to communicate with the user using a UI map, you may find it useful to invoke the map again to present the error to the user. Alternatively, you may invoke a step that transfers control to a script that displays the error message information and stops.

How To Set Up Invoke Business Service Steps

Invoke business service steps allow you to interact with a business service.

The following additional fields are required for Invoke business service steps:

Use Warning Level to indicate whether warnings should be suppressed and if not, how they should be presented to the user. By default, warnings are suppressed. If Warn As Popup is used, the warning is displayed using the standard popup dialog. If Warn As Error is used processing is directed to the If Error, Go To step. This field is only applicable to BPA scripts.

Group Name references the data area to be passed to and from the server when the Business Service is invoked.

The business service call will either be successful or return an error. The next two fields only appear when the call is issued from a BPA script, to determine the step to which control is passed given the outcome of the call.

If Success, Go To defines the step that is executed if the call is successful. This field is only applicable to BPA scripts.

If Error, Go To defines the step that is executed if the call returns on error. Please note that the error information is held in global variables. This field is only applicable to BPA scripts.

Note: Error technique. Let's assume a scenario where a business service is invoked from a BPA script and the call returned an error. If the BPA script is configured to communicate with the user using a UI map, you may find it useful to invoke the map again to present the error to the user. Alternatively, you may invoke a step that transfers control to a script that displays the error message information and stops.

How To Set Up Invoke Service Script Steps

Invoke service script steps allow you to execute a service script.

The following additional fields are required for Invoke service script steps:

Use Warning Level to indicate whether warnings should be suppressed and if not, how they should be presented to the user. By default, warnings are suppressed. If Warn As Popup is used, the warning is displayed using the standard popup dialog. If Warn As Error is used processing is directed to the If Error, Go To step. This field is only applicable to BPA scripts.

Group Name references the data area to be passed to and from the server when the Service Script is invoked.

The service script call will either be successful or return an error. The next two fields only appear when the call is issued from a BPA script to determine the step to which control is passed given the outcome of the call.

If Success, Go To defines the step that is executed if the call is successful. This field is only applicable to BPA scripts.

If Error, Go To defines the step that is executed if the call returns on error. Please note that the error information is held in global variables. This field is only applicable to BPA scripts.

Note: Error technique. Let's assume a scenario where a service script is invoked from a BPA script and the call returned an error. If the BPA script is configured to communicate with the user using a UI map, you may find it useful to invoke the map again to present the error to the user. Alternatively, you may invoke a step that transfers control to a script that displays the error message information and stops.

How To Set Up Label Steps

Label steps allow you to describe what the next step(s) are doing. Steps of this type are helpful to the script administrators when reviewing or modifying the steps in a script, especially when a script has many steps. When designing a script, the label steps enable you to provide a heading for common steps that belong together. The script tree displays steps of this type in a different color (green) so that they stand out from other steps.

There are no additional fields for Label steps.

How To Set Up Move Data Steps

Move data steps allow you to move data (from a source to a destination). The following additional fields are required for Move data steps:

Source Field Type, Source Field Name and Source Field Value define what you're moving. The following points describe each field type:

- Context Variable. Use this field type in a plug-in or service script if the source value is a variable initiated in a higher level script. This is only applicable to Service Scripts and Plug-in Scripts.

- Current To Do Information. Use this field type when the source value resides on the current To Do entry. Refer to How To Use To Do Fields for instructions on how to define the appropriate Field Name. This is only applicable to BPA Scripts.

- Data Area. Use this field type when the field being compared is one that you put into one of the script's data areas in an earlier step. Field Name must reference both a data area structure name as well as the field, for example "parm/charType". Refer to How To Reference Fields In Data Areas for instructions on how to construct the appropriate Field Name.

- Global Context. Use this field type when the source value is a global context variable. This is only applicable to BPA Scripts.

- Page Data Model. Use this field type when the source value resides on any of the tab pages in the object display area (i.e., the source field doesn't have to reside on the currently displayed tab page, it just has to be part of the object that's currently displayed). Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name. This is only applicable to BPA Scripts.

- Portal Context. Use this field type when the source value is a variable in the portal context. This is only applicable to BPA Scripts.

- Predefined Value. Use this field type when the source value is a constant value defined in the script. When this field type is used, use Source Field Value to define the constant value. Refer to How To Use Constants In Scripts for instructions on how to use constants.

Note: Concatenating fields together. You can also use Predefined Value if you want to concatenate two fields together. For example, let's say you have a script that merges two persons into a single person. You might want this script to change the name of the person being merged out of existence to include the ID of the person remaining. In this example, you could enter a Source Field Value of %ONAME merged into person %PERID (where ONAME is a field in temporary storage that contains the name of the person being merged out of existence and PERID contains the ID of the person being kept). Refer to How To Substitute Variables In Text for a description of how you can substitute field values to compose the field value.

- Temporary Storage. Use this field type when the source value is a field that you put into temporary storage in an earlier step. The Field Name must be the same as defined in an earlier step.

- User Interface Field. Use this field type when the source value resides on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name. This is only applicable to BPA Scripts.

Destination Field Type and Destination Field Name define where the source field will be moved. The Field Type defines where the field is located. The Field Name defines the name of the field. The following points describe each field type:

- Context Variable. Use this field type in your plug-in or service script if you use a variable to communicate information to a lower level service script or schema. This is not applicable to BPA Scripts.

- Data Area. Use this field type when the destination field resides on one of the scripts data areas. Field Name must reference both a data area structure name as well as the field, for example "parm/charType". Refer to How To Reference Fields In Data Areas for instructions on how to construct the appropriate Field Name.

- Page Data Model. Use this field type when the destination field resides on any of the tab pages in the object display area (i.e., the field populated doesn't have to reside on the currently displayed tab page, it just has to be part of the object that's currently displayed). Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name. This is only applicable to BPA Scripts.

- Portal Context. Use this field type when the destination to be updated is in the current portal context. This is only applicable to BPA Scripts.

- Temporary Storage. Use this field type when the destination field resides in temporary storage. Use Field Name to name the field in temporary storage. Use Field Name to name the field in temporary storage. Refer to How To Name Temporary Storage Fields for more information.

- User Interface Field. Use this field type when the destination field resides on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name. This is only applicable to BPA Scripts.

Note: Conditional field types. The field types Current To Do Information, Page Data Model and User Interface Field are only applicable to BPA scripts.

How To Set Up Terminate Steps

Terminate steps cause a server-based script to end processing successfully or issue an error.

The following additional fields are required for Terminate steps:

Error indicates whether an error should be thrown or not. If error, Error Data Text must be specified, indicating the error message and any message substitution parameters. Refer to Edit Data Syntax the actual syntax of initiating an error message.

Note: The ability to terminate a step in error is only supported for server-based scripts.

Step Types Applicable to BPA Scripts only

The contents of this section describe step types that are only applicable to BPA scripts.

Next in This Section

- How To Set Up Display Text Steps

- How To Set Up Height Steps

- How To Set Up Input Data Steps

- How To Set Up Invoke Function Steps

- How To Set Up Invoke Map Steps

- How To Set Up Mathematical Operation Steps

- How To Set Up Navigate To A Page Steps

- How To Set Up Perform Script Steps

- How To Set Up Press A Button Steps

- How To Set Up Prompt User Steps

- How To Set Up Set Focus To A Field Steps

- How To Set Up Transfer Control Steps

How To Set Up Display Text Steps

Display text steps cause a text string to be displayed in the script area. Steps of this type can be used to provide the user with guidance when manual actions are necessary. In addition, they can be used to provide confirmation of the completion of tasks.

The information you enter in the Text field is displayed in the script area when the step is executed.

The text string can contain substitution variables and HTML formatting commands. Also note that for debugging purposes, you can display an entire data area (or a portion thereof) by entering %+...+% where ... is the name of the node whose element(s) should be displayed.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Height Steps

Height steps are used to change the height of the script area to be larger or smaller than the standard size.

The following additional fields are required for Height steps:

Script Window Height defines the number of Pixels or the Percentage (according to the Height Unit) that the script window height should be adjusted. The percentage indicates the percentage of the visible screen area that the script area uses. For example, a percentage value of 100 means that the script area will use the entire area.

Note: Standard Number of Pixels. The default number of pixels used by the script area is 75.

Note: Adjust script height in the first step. If you want to adjust the height of the script area, it is recommendation to define the height step type as your first step. Otherwise, the script area will open using the standard height and then readjust, causing the screen to redisplay.

Note: Hide script area. You could use this type of step to set the height to 0 to hide the script area altogether. This is useful if the script does not require any prompting to the user. For example, perhaps you define a script to take a user to a page and with certain data pre-populated and that is all.

Note: Automatically close script area. If you want the script area to close when a script is completed, you could define the final step type with a height of 0.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Input Data Steps

Input data steps cause the user to be prompted to populate an input field in the script area. The input value can be saved in a field on a page or in temporary storage. A Continue button always appears adjacent to the input field. You may configure steps of this type to display one or more buttons in addition to the Continue button. For example, you may want to provide the ability for the user to return to a previous step to fix incorrect information. The user may click on any of these buttons when ready for the script to continue.

The following additional fields are required for Input Data steps:

Destination Field Type and Destination Field Name define where the input field will be saved. The Field Type defines where the field is located. The Field Name defines the name of the field. The following points describe each field type:

- Page Data Model. Use this field type to put the input field into a field that resides on any of the tab pages in the object display area (i.e., the field populated doesn't have to reside on the currently displayed tab page, it just has to be part of the object that's currently displayed). Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name.

- Temporary Storage. Use this field type to put the input field into temporary storage. Use Field Name to name the field in temporary storage. Refer to How To Name Temporary Storage Fields for more information.

- User Interface Field. Use this field type to put the input field into a field that resides on the currently displayed tab page. Note, if you want to execute underlying default logic, you must populate a User Interface Field. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

The Prompt Values grid may be used to define additional buttons. A separate button is displayed in the script area for each entry in this grid.

- Prompt Text is the verbiage to appear on the button. Refer to How To Substitute Variables In Text for a description of how you can substitute field values into the prompts.

- Sequence controls the order of the buttons.

- Next Script Step defines the step to execute if the user clicks the button.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Invoke Function Steps

Note: Functions were implemented prior to the introduction of business services (BS), service scripts (SS) and business objects (BO). The functionality is still supported, but the recommendation for implementations going forward is to use a step that invokes one of the above configuration tool objects in a script rather than defining a function.

Invoke function steps may be used to retrieve or update data independent of the page currently being displayed. For example, if you design a script that takes different paths based on the customer's customer class, you could invoke a function to retrieve the customer's customer class.

Fastpath: You must set up a function before it can be referenced in a script. Refer to Maintaining Functions for the details.

The following additional fields are required for Invoke Function steps:

Function defines the name of the function. The function's Long Description is displayed below.

When a function is invoked, it will either be successful or return an error. The next two fields control the step to which control is passed given the outcome of the function call:

- If Success, Go to defines the step that is executed if the function is successful.

- If Error, Go to defines the step that is executed if the function returns on error. Refer to How To Use Constants In Scripts for a list of the global variables that are populated when a function returns an error.

Note: Error technique. If a function returns an error, we recommend that you invoke a step that transfers control to a script that displays the error message information and stops (note, the error information is held in global variables). You would invoke this script via a Transfer Control.

The Send Fields grid defines the fields whose values are sent to the function and whose field value source is not Defined On The Function. For example, if the function receives an account ID, you must define the name of the field in the script that holds the account ID.

- Field contains a brief description of the field sent to the function.

- Source Field Type and Mapped Field / Value define the field sent to the function. Refer to the description of Source Field under How To Set Up Move Data Steps for a description of each field type.

- Comments contain information about the field (this is defined on the function).

The Receive Fields grid defines the fields that hold the values returned from the function. For example, if the function returns an account's customer class and credit rating, you must set up two fields in this grid.

- Field contains a brief description of the field returned from the function.

- Destination Field Type and Mapped Field define the field returned from the function. Refer to the description of Destination Field under How To Set Up Move Data Steps for a description of each field type.

- Comments contain information about how the field (this is defined on the function).

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Invoke Map Steps

Invoke map steps are used to invoke a UI Map to display, capture and update data using an HTML form. You may configure steps of this type to display one or more buttons in addition to the Continue button. For example, you may want to provide the ability for the user to return to a previous step to fix incorrect information. The user may click on any of these buttons when ready for the script to continue.

The following additional fields are required for Invoke map steps:

Group Name references the data area to be passed to and from the server when rendering the HTML form associated with the Map.

Use Target Area to designate where the map will be presented.

- Select BPA Zone if the map should be presented within the script area.

- Select Page Area if the map should be presented in the object display area, i.e. the frame typically used to house a maintenance page.

- Select Pop-up Window if the map should be launched in a separate window.

The Returned Values grid contains a row for every button defined on the map.

- Returned Value is the value returned when the user clicks the button.

- Use as Default can only be turned on for one entry in the grid. If this is turned on, this value's Next Script Step will be executed if the returned value does not match any other entry in the grid. For example, if the user closes a pop-up (rather than clicking a button), the default value will be used.

- Next Script Step defines the step to execute if the user clicks the button.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Mathematical Operation Steps

Mathematical operation steps allow you to perform arithmetic on fields. You can also use this type of step to add and subtract days from dates. For example, you could calculate a date 7 days in the future and then use this value as the customer's next credit review date. The following additional fields are required for Mathematical Operation steps:

Base Field Type and Base Field Name define the field on which the mathematical operation will be performed. The Field Type defines where the field is located. The Field Name defines the name of the field. The following points describe each field type:

- Page Data Model. Use this field type when the field resides on any of the tab pages in the object display area. Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name.

- Temporary Storage. Use this field type when the field resides in temporary storage. You must initialize the temporary storage field with a Move Data step before performing mathematical operations on the field. Refer to How To Set Up Move Data Steps for more information.

- User Interface Field. Use this field type when the field resides on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

Math Operation controls the math function to be applied to the Base Field. You can specify +, -, /, and *. Note, if the base field is a date, you can only use + or -.

Math Field Type, Math Field Name and Math Field Value define the field that contains the value to be added, subtracted, divided, or multiplied. The following points describe each field type:

- Current To Do Information. Use this field type when the value resides on the current To Do entry. Refer to How To Use To Do Fields for instructions on how to define the appropriate Field Name.

- Page Data Model. Use this field type when the value resides on any of the tab pages in the object display area. Refer to How To Find The Name Of Page Data Model Fields for instructions on how to find the appropriate Field Name.

- Predefined Value. Use this field type when the value is a constant. When this field type is used, use Source Field Value to define the constant value. Refer to How To Use Constants In Scripts for more information. Note, if you are performing arithmetic on a date, the field value must contain the number and type of days/ months/ years. For example, if you want to add 2 years to a date, the source field value would be 2 years.

- Temporary Storage. Use this field type when the value is a field that you put into temporary storage in an earlier step. The Field Name must be the same as defined in an earlier step.

- User Interface Field. Use this field type when the value resides in a field on the current tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Navigate To A Page Steps

Navigate to a page steps cause a new page (or tab within the existing page) to be displayed in the object display area. Steps of this type are a precursor to doing anything on the page. The following additional field is required for Navigate to a page steps:

Navigation Option defines the transaction, tab, access mode (add or change) and any context fields that are passed to the transaction in change mode. For example, if you want a script to navigate to Person - Characteristics for the current person being displayed in the dashboard, you must set up an appropriate navigation option. Refer to Defining Navigation Options for more information.

Note: Navigating to a page in update mode. Before you can navigate to a page in change mode, the page data model must contain the values to use for the navigation option's context fields. If necessary, you can move values into the page data model using a Move Data step first. For example, before you can navigate to a page in change mode with an account ID in context, you may need to move the desired account ID into the ACCT_ID field in the page data model. The actual field name(s) to use are listed as context fields on the navigation option.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Perform Script Steps

Perform script steps cause another BPA script to be performed. After the performed script completes, control is returned to the next step in the original script. You might want to think of the scripts referred to on steps of this type as "subroutines". This functionality allows you to encapsulate common logic in reusable BPA scripts that can be called from other BPA scripts. This simplifies maintenance over the long term.

The following additional field is required for Perform script steps:

Subscript is the name of the script that is performed.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Press A Button Steps

Press a button steps cause a button or link text to be ‘pressed’ in the object display area, the application toolbar or the page title area. For example, you could use this type of step to add a new row to a person's characteristic (and then you could use a Move Data step to populate the newly added row with a given char type and value). The following additional fields are required for Press a button steps:

Button Name is the name of the button to be pressed. This button must reside on the currently displayed tab page (or in the application toolbar or page actions toolbar). Refer to How To Find The Name Of A Button for more information.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Prompt User Steps

Prompt user steps cause the user to be presented with a menu of options. The options can be presented using either buttons or in the contents of a drop down. You can also use steps of this type to pause a script while the user checks something out (and when the user is ready to continue with the script, they are instructed to click a prompt button). The following additional fields are required for Prompt User steps:

Prompt Type controls if the prompt shown in the script area is in the form of Button(s) or a Dropdown. Note, if you use a Dropdown, a Continue button appears adjacent to the dropdown in the script area when the step executes. The user clicks the Continue button when they are ready for the script to continue.

The Prompt Values grid contains a row for every value that can be selected by a user. Note, if you use a Prompt Type of Button(s), a separate button is displayed in the script area for each entry in this grid.

- Prompt Text is the verbiage to appear on the button or in the dropdown entry. Refer to How To Substitute Variables In Text for a description of how you can substitute field values into the prompts.

- Sequence controls the order of the buttons or dropdown entries.

- Use As Default can only be turned on for one entry in the grid. If this is turned on for a dropdown entry, this value is defaulted in the grid. If this is turned on for a button, this button becomes the default (and the user should just have to press Enter (or space) rather than click on it).

- Next Script Step defines the step to execute if the user clicks the button or selects the dropdown value.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Set Focus To A Field Steps

Set focus to a field steps cause the cursor to be placed in a specific field on a page. A Continue button always appears in the script area when this type of step executes. The user may click the Continue button when they are ready for the script to continue. You may configure steps of this type to display one or more buttons in addition to the Continue button. For example, you may want to provide the ability for the user to return to a previous step to fix incorrect information. The user may click on any of these buttons when ready for the script to continue.

The following additional fields are required for Set focus to a field steps:

Destination Field Name defines the field on which focus should be placed. This field must reside on the currently displayed tab page. Refer to How To Find The Name Of User Interface Fields for instructions on how to find the appropriate Field Name.

The Prompt Values grid may be used to define additional buttons. A separate button is displayed in the script area for each entry in this grid.

- Prompt Text is the verbiage to appear on the button. Refer to How To Substitute Variables In Text for a description of how you can substitute field values into the prompts.

- Sequence controls the order of the buttons.

- Next Script Step defines the step to execute if the user clicks the button.

Note: Conditional step type. This step type is only applicable to BPA scripts.

How To Set Up Transfer Control Steps

Transfer control steps cause the current BPA script to terminate and the control to pass to another BPA script. You might want to construct a BPA script with steps of this type when the script has several potential logic paths and you want to segregate each logic path into a separate BPA script (for ease of maintenance).

The following additional fields are required for Transfer control steps:

Subscript is the name of the script to which control is transferred.

Note: Conditional step type. This step type is only applicable to BPA scripts.

Step Types Applicable to Server Based Scripts only

The contents of this section describe step types that are only applicable to server based scripts.

Next in This Section

- How To Set Up Groovy Member Steps

- How To Set Up Groovy Imports Steps

- How To Set Up Groovy Library Interface Steps

How To Set Up Groovy Member Steps

Groovy Member steps provide a free format text area where you can enter Groovy code.

Enter a description of the code block in the Text field. Click the adjacent icon to open a window providing more space for entering text.

Enter your code in the Edit Data Text field. Click the adjacent icon to open a window providing more space for editing the code.

Note: While it is possible to set up multiple steps of type Groovy Member the system treats these steps as a single class for compilation and execution purposes. Refer to the topic Using Groovy Within Scripts for more information.

How To Set Up Groovy Imports Steps

Groovy Imports step types provide a free format text area where you can list the Groovy classes to be imported for use by the code in Groovy Member steps within the script.

Enter a description of the imports step in the Text field. Click the adjacent icon to open a window providing more space for entering text.

Enter the list of classes to import in the Edit Data Text field using the syntax import ‘class’; where ‘class’ is the fully qualified package name of the Groovy class. Click the adjacent icon to open a window providing more space for editing the text.

Note: For security, the classes that may be imported are restricted to those allowed by the Framework. Refer to the topic Using Groovy Within Scripts for more information.

How To Set Up Groovy Library Interface Steps

Groovy Library Interface steps are only applicable to Groovy Library Scripts. They provide a free format text area where you can list the Groovy methods defined within the script that are available for use by other scripts.

Enter a description of the interface step in the Text field. Click the adjacent icon to open a window providing more space for entering text.

Enter the list of interface methods in the Edit Data Text field. Click the adjacent icon to open a window providing more space for editing the list.

Note: Every Groovy Library Script must have one and only one step of type Groovy Library Interface. The supporting code for the available methods is defined using one or more Groovy Member steps in the same script. Refer to the topic Using Groovy Within Scripts for more information.

Additional Topics

The contents of this section provide additional information about steps.

Next in This Section

- How To Find The Name Of User Interface Fields

- How To Find The Name Of Page Data Model Fields

- How To Find The Name Of A Button

- How To Substitute Variables In Text

- How To Use HTML Tags And Spans In Text Strings and Prompts

- How To Use Constants In Scripts

- How To Use Global Variables

- How To Name Temporary Storage Fields

- How To Work With Dates

- How To Use To Do Fields

- How To Reference Fields In Data Areas

How To Find The Name Of User Interface Fields

Follow these steps to find the name of a field that resides on a page:

- Navigate to the page in question.

- Right click in the body of the page (but not while the pointer is in an input field). Note, if the field in question resides in a grid, you must right click while the pointer is in the section that contains the grid (but not while the pointer is in an input field in the grid) - this is because there's a separate HTML document for each grid on a page.

- Select View Source from the pop-up menu to display the source HTML.

- Scroll to the Widget Info section (towards the top of the HTML document). It contains a list of all of the objects on a page. For example, the following is an example from the Account - Main page:

The field names that you'll reference in your scripts are defined on the left side of the HTML (e.g., ENTITY_NAME, ACCT_ID, CUST_CL_CD, etc.).

The names of fields that reside in scrolls are in a slightly different format. The following is an example of the HTML for the persons scroll that appears on Account - Person. Notice that the fields in the scroll are prefixed with the name of the scroll plus a $ sign. For example, the person's ID is called ACCT_PER$PER_ID.

The names of fields that reside in grids are in a slightly different format. The following is an example of the HTML for the names grid that appears on Person - Main. Notice that the fields in the grid are prefixed with the name of the grid plus a :x$. For example, the person's name is called PER_NAME:x$ENTITY_NAME. When you reference such a field in your script, you have the following choices:

- Substitute x with the row in the grid (and keep in mind, the first row in a grid is row 0 (zero); this means the second row is row 1).

- If you want to reference the "current row" (e.g., the row in which the cursor will be placed), you can keep the x notation ( x means the "current row").

How To Find The Name Of Page Data Model Fields

You find the name of a Page Data Model field in the same way described under How To Find The Name Of User Interface Fields. The only restriction is that you cannot refer to hidden / derived fields. However, you can refer to any of the object's fields regardless of the tab page on which they appear. For example, if you position the object display area to the Main tab of the Account transaction, you can reference fields that reside on all of the tab pages.

CAUTION:

If you populate a Page Data Model field, none of the underlying default logic takes place. For example, if you populate a customer contact's contact type, none of the characteristics associated with the customer contact type are defaulted onto the customer contact. If you want the underlying defaulting to take place, you must populate a User Interface Field.

How To Find The Name Of A Button

If you want a Press a button step to press a button or click a link in the application toolbar, use one of the following names:

Button Name

IM_GOBACK

IM_HISTORY

IM_GOFORWARD

IM_menuButton

IM_USER_HOME

IM_MY_PREF

IM_helpButton

IM_aboutButton

If you want a Press a button step to press a button in the page actions toolbar, use one of the following names:

Button Name

IM_SAVE

IM_REFRESH

IM_CLEAR

IM_COPY

IM_DELETE

IM_ScrollBack

IM_ScrollForward

The following buttons are also supported:

Button Name

Comments

IM_TO_DO

IM_PrevTo Do

This brings you to the To Do Summary page.

IM_NextTo Do

This simulates clicking the Next To Do button in the Current To Do Zone.

IM_CurrentTo Do

This navigates to the To Do Entry page for the user’s current To Do. Refer to A User’s Current To Do for more information.

IM_MINIMIZE_DASHBOARD

Pressing this will collapse the dashboard. Note that when a script is finished, it will return the dashboard to the state it was when the script was launched.

IM_MAXIMIZE_DASHBOARD

Pressing this will expand the dashboard. Note that when a script is finished, it will return the dashboard to the state it was when the script was launched.

Follow these steps to find the name of other buttons that reside in the object display area:

- Navigate to the page in question.

- Right click in the body of the page (but not while the pointer is in an input field). Note, if the field in question resides in a grid, you must right click while the pointer is in the section that contains the grid (but not while the pointer is in an input field in the grid) - this is because there's a separate HTML document for each grid on a page.

- The option to select may differ based on the browser you are using. For example, for some browsers, the option may be View Source. For others, the option may be This Frame and then Frame Source

- Scroll to the Widget Info section (towards the top of the HTML document). It contains a list of all of the objects on a page, including buttons.

- Iconized buttons (e.g., search buttons) are represented as HTML images and their field names are prefixed with IM. The following is an example of the HTML on the To Do Entry - Main page (notice the IM fields for the iconized buttons).

* Widget Info:

*     Widget_ID , Element Type - label info - label

*     TD_ENTRY_INFO, IL - $TD_ENTRY_INFO -  To Do Info

*     TD_ENTRY_ID, IT - CI_TD_ENTRY$TD_ENTRY_ID -  To Do ID

*     IM_TD_ENTRY_ID, IM - $TD_ENTRY_ID_SRCH -  Search for Entry Id

*     TD_TYPE_CD, IL - $TD_TYPE_CD -  To Do Type

*     TYPE_DESCR, IL

*     ROLE_ID, IL

*     ROLE_DESCR2, IL - $DESCR -  Description

*     FULL_MSG, PL - $GOTO_TD_ACTION_LBL -  Work on To Do

*     IM_EXP_MSG_LONG, IM - $DISPLAY_MESSAG_LBL -  Display Message Explanation

- Transaction-specific actions buttons (e.g., the buttons use to complete or forward a To Do) are represented as switches. The following is an example of the HTML on the To Do Entry - Main page (notice the SW fields for the buttons). Note, if you want to Set focus to such a field, you would move a Predefined Value of TRUE to the switch.

*     COMPLETE_SW, BU - $COMPLETE_SW -  Complete

*     FORWARD_SW, BU - $FORWARD_SW -  Forward

*     SEND_BACK_SW, BU - $SEND_BACK_SW -  Send Back

How To Substitute Variables In Text

You can substitute field values into a step's text string. You do this by prefixing the field name whose value should be substituted in the string with a %. For example, the message, "On %COMPLETION_DTTM this bill was completed, it's ending balance was %ENDING_BALANCE" contains two substitution variables (the bill's completion date / time and the bill's ending balance).

To substitute the value of an element from a data area you need to reference its XPath location as follows: %=XPath=%. If you want to substitute the whole XML node, not just the value, you need to reference it as follows %+XPath+%.

Only fields linked to the current To Do and fields that reside in temporary storage and global variables can be substituted into a text string.

Note: You can substitute fields that reside in the User Interface or Page Data Model by first moving them into temporary storage (using a Move data step).

You can also substitute field values into the verbiage displayed in prompts using the same technique.

How To Use HTML Tags And Spans In Text Strings and Prompts

You can use HTML tags in a step's text string. For example, the word "Continue" will be italicized in the following text string "Press<i>Continue</i> after you've selected the customer" (the <i> and </i> are the HTML tags used to indicate that the surrounded text should be italicized).

The following are other useful HTML tags:

- <br> causes a line break in a text string. If you use <br><br> a blank line will appear.

- <font color=red> text </font> causes the surrounded text to be colored as specified (in this case, red). You can also use hex codes rather than the color name.

Please refer to an HTML reference manual or website for more examples.

You can also use "spans" to customize the look of the contents of a text string. For example, your text string could be "Press <span style="font-family:Courier; font-size:large; font-weight:bold;">Continue</span> after you've selected the customer". This would make the word "Continue" appear as large, bold, Courier text. Please refer to a Cascading Style Sheets (CSS) reference manual or website for more examples.

How To Use Constants In Scripts

Some steps can reference fields called Predefined Values. For example, if you want to compare an input value to the letter "Y", the letter Y would be defined as a Predefined Value's field value.

Special constants are used for fields defined as switches. When you move TRUE to a switch, it turns it on. When you move FALSE to a switch, it turns it off.

You can use a global variable as a Predefined Value. For example, if you wanted to move the current date to a field, you'd indicate you wanted to move a Predefined Value named %CURRENT_DATE.

How To Use Global Variables

Some explicit steps can reference fields called Predefined Values. In addition to referencing an ad hoc constant value (e.g., the letter Y), you can also reference a global variable in such a field value. A global variable is used when you want to reference system data.

Note that when using the Edit Data step type, the variable available are slightly different. Refer to Edit Data Syntax for details.

The following global variables exist for BPA scripts:

Variable Name

Comments

%PARM-<name>

This is the value of a parameter of that name passed in to the application when launched via the standard system URL. Refer to Launching A Script When Starting the System for more information on these parameters.

%PARM-NOT-SET

This is to be used to compare against %PARM-< > parameters to check if the parameter has been set or not when the application was launched. A parameter that has not been set would be considered equal to this global variable. It is recommended to compare parameters against this global variable before using them for the first time.

%BLANK

A constant that contains a blank value (no value).

%SPACE

A constant that contains a single space value.

%CURRENT-DATE

The current date as known by the browser, not the server.

%SYSTEM-DATE

The server date. Note that this date is affected by the system date override logic)

%SAVE-REQUIRED

A flag that contains an indication of whether the data on a page has been changed (and thus requires saving). You may want to interrogate this flag to force a user to save their work before executing subsequent steps. This flag will have a value of TRUE or FALSE.

%NEWLINE

A constant that contains a new line character (carriage return). Upon substitution, a line break is inserted in the resultant text.
Note: This constant does not have the desired effect when the resultant text is HTML. For example, a step's text and prompt strings. This is because HTML ignores special characters such as new lines. Refer to How To Use HTML Tags And Spans In Text to learn how to cause a line break in an HTML text.

To refer to a global context variable, use %FIELD_NAME. For example, if the field SP_ID is in the global context, you may reference %SP_ID to reference the ID of the service point currently in context. In addition, the following special values are supported:

Variable Name

Comments

%CONTEXT-PERSONID

A constant that contains the ID of the current person.

%CONTEXT-ACCOUNTID

A constant that contains the ID of the current account.

%CONTEXT-PREMISEID

A constant that contains the ID of the current premise.

In addition, if the script is invoking something else via one of the various “Invoke” step types and an error is returned, the following global variables contain information about the error:

Variable Name

Comments

%ERRMSG-CATEGORY %ERRMSG-NUMBER

The unique identifier of the error message number.

%ERRMSG-TEXT

The brief description of the error.

%ERRMSG-LONG

The complete description of the error.

How To Name Temporary Storage Fields

Input Data and Move Data steps can create fields in temporary storage. You specify the name of the temporary storage field in the step's Field Name. The name of the field must not begin with % and must not be named the same as the global variables. Besides this restriction, you can use any Field Name that's acceptable to JavaScript (i.e., you can name a field in temporary storage almost anything). Keep in mind that field names are case-sensitive.

How To Work With Dates

Before we discuss how to work with dates in your scripts, we need to point out that there are two types of date fields: date-only and date-time. Date-only fields only contain a date. Date-time fields contain both a date and a time. The following topics describe how to work with dates on the various step types.

Note: If you're working with a field that resides on the database (as opposed to a temporary storage field), the database field name will tell you what type of date it is: date-only fields are suffixed with DT, and date-time fields are suffixed with DTTM.

Next in This Section

- Move Data

- Mathematical Operation

- Input Data

Move Data

If you intend to use a Move data step to populate a date-time field, please be aware of the following:

- If the destination field resides in the page data model, the source field value must be in the format YYYY-MM-DD-HH.MM.SS or YYYY-MM-DD. If the field is in the format YYYY-MM-DD, the time of 12:00 am will be defaulted.

- If the destination field resides in the user interface, you must use two steps if you want to populate both date and time. To explain this, we'll assume the field you want to populate is called EXPIRE_DTTM:

- First, you populate the date portion of the field. To do this, you'd move a date (this value can be in any valid date format that a user is allowed to enter) to a field called EXPIRE_DTTM_FWDDTM_P1. In other words, you suffix _FWDDTM_P1 to the field name.

- If you want to populate the time, you'd move the time (again, the field value can be in any format that a user could use to enter a time) to a field called EXPIRE_DTTM_FWDTTM_P2. In other words, you suffix _FWDDTM_P2 to the field name.

If you intend to use a Move data step to populate a date-only field, please be aware of the following:

- If the destination field resides in the page data model, the source field value must be in the format YYYY-MM-DD.

- If the destination field resides in the user interface, the source field can be in any valid date format that a user is allowed to enter.

Note: %CURRENT-DATE. Keep in mind that the global variable%CURRENT-DATE contains the current date and you can move this to either a page data model, user interface, or temporary storage field. If you move %CURRENT-DATE to a temporary storage fields, it is held in the format YYYY-MM-DD.

Mathematical Operation

If you intend to use a Mathematical operation step to calculate a date, you can reference both date-only and date-time fields. This is because mathematical operations are only performed against the date portion of date-time fields.

Mathematical operations are limited to adding or subtracting days, months and years to / from a date.

Note: A useful technique to perform date arithmetic using the current date is to move the global variable%CURRENT-DATE to a temporary storage field and then perform the math on this field.

Input Data

If you intend to use an Input data step on a date-time field, please be aware of the following:

- If the field resides in the page data model, the user must enter a value in the format YYYY-MM-DD-HH.MM.SS (and therefore we do not recommend doing this).

- If the field resides in the user interface, you must use two steps if you want to populate both date and time. To explain this, we'll assume the field you want to populate is called EXPIRE_DTTM:

- First, you populate the date portion of the field. To do this, you'd input the date (this value can be in any valid date format that a user is allowed to enter) in a field called EXPIRE_DTTM_FWDDTM_P1. In other words, you suffix _FWDDTM_P1 to the field name.

- If you want to populate the time, you'd input the time (again, the field value can be in any format that a user could use to enter a time) in a field called EXPIRE_DTTM_FWDTTM_P2. In other words, you suffix _FWDDTM_P2 to the field name.

If you intend to use an Input data step to populate a date-only field, please be aware of the following:

- If the field resides in the page data model, the user must enter a value in the format YYYY-MM-DD (and therefore we do not recommend doing this).

- If the field resides in the user interface, the user can enter any valid date format.

How To Use To Do Fields

As described under Executing A Script When A To Do Entry Is Selected, you can set up the system to automatically launch a script when a user selects a To Do entry. These types of scripts invariably need to access data that resides on the selected To Do entry. The following points describe the type of information that resides on To Do entries:

- Sort keys. These values define the various ways a To Do list's entries may be sorted. For example, when you look at the bill segment error To Do List, you have the option of sorting the entries in error number order, account name order, or in customer class order. There is a sort key value for each of these options.

- Message parameters. These values are used when the system finds %n notation within the message text. The %n notation causes field values to be substituted into a message before it's displayed. For example, the message text The %1 non-cash deposit for %2 expires on %3 will have the values of three fields merged into it before it is displayed to the user (%1 is the type of non-cash deposit, %2 is the name of the customer, and %3 is the expiration date of the non-cash deposit). Each of these three values is stored as a separate message parameter on the To Do entry.

- Drill keys. These values are the keys passed to the page if a user drilled down on the entry (and the system wasn't set up to launch a script). For example, a To Do entry that has been set up to display an account on the account maintenance page has a drill key of the respective account ID.

- To Do ID. Every To Do entry has a unique identifier referred to as its To Do ID.

You can access this information in the following types of steps:

- Move Data steps can move any of the above to any data area. For example, you might want to move a To Do entry's drill key to the page data model so it can be used to navigate to a specific page.

- Conditional Branch steps can perform conditional logic based on any of the above. For example, you can perform conditional logic based on a To Do entry's message number (note, message numbers are frequently held in sort keys).

- Mathematical Operation steps can use the above in mathematical operations.

A To Do entry's sort key values are accessed by using a Field Type of Current To Do Information and a Field Name of SORTKEY[index]. Note, you can find an entry's potential sort keys by displaying the entry's To Do type and navigating to the Sort Keys tab. If you want to reference the first sort key, use an index value of 1. If you want to use the second sort key, use an index value of 2 (and so on).

A To Do entry's drill key values are accessed by using a Field Type of Current To Do Information and a Field Name of DRILLKEY[index]. Note, you can find an entry's potential drill keys by displaying the entry's To Do type and navigating to the Drill Keys tab. If you want to use the first drill key, use an index value of 1. If you want to use the second drill key, use an index value of 2 (and so on).

A To Do entry's message parameters are accessed by using a Field Type of Current To Do Information and a Field Value of MSGPARM[index]. Note, because a To Do type can have an unlimited number of messages and each message can have different parameters, finding an entry's message parameters requires some digging. The easiest way to determine these values is to display the To Do entry on To Do maintenance. On this page, you will find the entry's message category/number adjacent to the description. Once you know these values, display the message category/number on Message Maintenance. You'll find the message typically contains one or more %n notations (one for each message parameter). For example, the message text The %1 non-cash deposit for %2 expires on %3 has three message parameters. You then need to deduce what each of the message parameters are. You do this by comparing the message on the To Do entry with the base message (it should be fairly intuitive as to what each message parameter is). If we continue using our example, %1 is the non-cash deposit type, %2 is the account name, and %3 is the expiration date. You can access these in your scripts by using appropriate index value in MSGPARM[index].

A To Do entry's unique ID is accessed by using a Field Type of Current To Do Information and a Field Value of TD_ENTRY_ID.

In addition, any of the above fields can be substituted into a text string or prompt. Simply prefix the To Do field name with a % as you would fields in temporary storage. For example, assume you want your script to display the following text in the script area: "ABC Supply does not have a bill cycle" (where ABC Supply is the account's name). If the first sort key linked to the To Do entry contains the account's name, you'd enter a text string of %SORTKEY[1] does not have a bill cycle.

How To Reference Fields In Data Areas

Various step types involve referencing field elements residing in the script's data areas. To reference an element in a data area you need to provide its absolute XPath notation starting from the data area name. For example, use "CaseLogAdd/caseID" to reference a top-level "caseID" element in a script data area called "CaseLogAdd".

You don't have to type in long XPath notions. Use the View Script Schema hyperlink provided on the Script - Step tab page to launch the script's data areas schema.

Figure 1. Schema Viewer

Doing this opens the schema viewer window where you can:

- Click on the field element you want to reference in your script step. The system automatically populates the text box on the top with the element's absolute XPath notation.

- Copy the element's XPath notation from the text box to your script.

You can also use the View Data Area, View Service Script Data Area, or View Plug-In Script Data Area links on Script - Data Area to the same effect. These open up the schema viewer for a specific data area respectively.

Script - Data Area

Use this page to define the data areas used to pass information to and from the server or any other data area describing your temporary storage. Open this page using Admin > System > Script and then navigate to the Data Area tab.

Note: Conditional tab page. This tab page does not appear for Groovy Library scripts or plug-in scripts using the Groovy engine version.

Description of Page

The grid contains the script's data areas declaration. For steps that invoke an object that is associated with a schema, you must declare the associated schema as a data area for your script. In addition, if you have defined one or more data areas to describe the script's temporary storage, you need to declare them too. The following bullets provide a brief description of each field on a script data area:

- Schema Type defines the type of schema describing the data area's element structure.

- The data area's schema is the one associated with the referenced Object. Only objects of the specified Schema Type may be selected.

- Data Area Name uniquely identifies the data area for referencing purposes. By default, the system assigns a data area with the associated object name.

- Click on the View Data Area link to view the data area's schema in the schema viewer window.

The View Service Script Data Area link appears for service scripts only. Use this link to view the script's parameters data area schema in the schema viewer window.

The View Plug-In Script Data Area link appears only for plug-in scripts using a script engine version. Use this link to view the script's parameters data area schema in the schema viewer window.

Fastpath: Refer to A Script May Declare Data Areas for more information on data areas.

Script - Schema

Use this page to define the data elements passed to and from a service script. Open this page using Admin > System > Script and then navigate to the Schema tab.

Note: Conditional tab page. This tab page only appears for service scripts.

Description of Page

The contents of this section describe the zones that are available on this portal.

The General Information zone displays the script name and description.

The Schema Designer zone allows you to edit the service script's parameters schema. The purpose of the schema is to describe the input and output parameters used when invoking the script.

Note: Refer to Schema Nodes and Attributes for a complete list of the XML nodes and attributes available to you when you construct a schema.

The Schema Usage Tree zone summarizes all cross-references to this schema. For each type of referencing entity, the tree displays a summary node showing a total count of referencing items. The summary node appears if at least one referencing item exists. Expand the node to list the referencing items and use their description to navigate to their corresponding pages.

Script - Eligibility

Use this page to define a script's eligibility rules. Open this page using Admin > System > Script and then navigate to the Eligibility tab.

Note: Conditional tab page. This tab page only appears for BPA scripts.

Description of Page

Use the Eligibility Option to indicate whether the script is Always Eligible, Never Eligible or to Apply Eligibility Criteria. The remaining fields on the page are only visible if the option is Apply Eligibility Criteria.

CAUTION:

The following information is not intuitive; we strongly recommend that you follow the guidelines under The Big Picture Of Script Eligibility before attempting to define this information.

The Eligibility Criteria Group scroll contains one entry for each group of eligibility criteria. The following fields may be defined for each group:

- Use Sort Sequence to control the relative order in which the group is executed when the system determines if the script should appear in the script search.

- Use Description and Long Description to describe the criteria group.

- Use If Group is True to define what should happen if the eligibility criteria (defined in the following grid) return a value of True.

- Choose Eligible if this script should appear.

- Choose Ineligible if this script should not appear.

- Choose Check Next Group if the next criteria group should be checked.

- Use If Group is False to define what should happen if the eligibility criteria (defined in the following grid) return a value of False.

- Choose Eligible if this script should appear.

- Choose Ineligible if this script should not appear.

- Choose Check Next Group if the next criteria group should be checked.

The grid that follows contains the script's eligibility criteria. Think of each row as an "if statement" that can result in the related eligibility group being true or false. For example, you might have a row that indicates the script is eligible if the current account in context belongs to the residential customer class. The following bullets provide a brief description of each field on an eligibility criterion. Please refer to Defining Logical Criteria for several examples of how this information can be used.

- Use Sort Sequence to control the order in which the criteria are checked.

- Use Criteria Field to define the field to compare:

- Choose Algorithm if you want to compare anything other than a characteristic. Push the adjacent search button to select the algorithm that is responsible for retrieving the comparison value. Click here to see the algorithm types available for this plug-in spot.

- Some products may also include an option to choose Characteristic. Choosing this option displays adjacent fields to define the object on which the characteristic resides and the characteristic type. The objects whose characteristic values may be available to choose from depend on your product.

- Use Criteria Comparison to define the method of comparison:

- Choose Algorithm if you want an algorithm to perform the comparison and return a value of True, False or Insufficient Data. Push the adjacent search button to select the algorithm that is responsible for performing the comparison. Click here to see the algorithm types available for this plug-in spot.

- Choose any other option if you want to compare the Criteria Field using a logical operator. The following options are available:

- Use >, <, =, >=, <=, <> (not equal) to compare the Criteria Field using standard logical operators. Enter the comparison value in the adjacent field.

- Use IN to compare the Criteria Field to a list of values. Each value is separated by a comma. For example, if a field value must equal 1, 3 or 9, you would enter a comparison value of 1,3,9.

- Use BETWEEN to compare the Criteria Field to a range of values. For example, if a field value must be between 1 and 9, you would enter a comparison value of 1,9. Note, the comparison is inclusive of the low and high values.

- The next three fields control whether the related logical criteria cause the eligibility group to be considered true or false:

- Use If True to control what happens if the related logical criterion returns a value of True. You have the options of Group is true, Group is false, or Check next condition. If you indicate Group is true or Group is false, the script is judged Ineligible or Eligible based on the values defined above in If Group is False and If Group is True.

- Use If False to control what happens if the related logical criterion returns a value of False. You have the options of Group is true, Group is false, or Check next condition. If you indicate Group is true or Group is false, the script is judged Ineligible or Eligible based on the values defined above in If Group is False and If Group is True.

- Use If Insufficient Data to control what happens if the related logical criterion returns a value of "Insufficient Data". You have the options of Group is true, Group is false, or Check next condition. If you indicate Group is true or Group is false, the script is judged Ineligible or Eligible based on the values defined above in If Group is False and If Group is True.

Merging Scripts

Use the Script Merge page to modify an existing script by copying steps from other scripts. The following points summarize the many diverse functions available on the Script Merge transaction:

- You can use this transaction to renumber steps (assign them new sequence numbers).

- You can use this transaction to move a step to a different position within a script. When a step is moved, all references to the step are changed to reflect the new sequence number.

- You can use this transaction to delete a step.

- You can use this transaction to copy steps from other scripts. For example:

- You may want to create a script that is similar to an existing script. Rather than copying all the information from the existing script and then removing the inapplicable steps, this page may be used to selectively copy steps from the existing script to the new script.

- You may have scripts that are very similar, but still unique. You can use this transaction to build large scripts from smaller scripts. In this scenario, you may choose to create special 'mini' scripts, one for each of the various options that may make a script unique. Then, you could use the script merge page to select and merge the mini scripts that are applicable for a main script.

Note: The target script must exist prior to using this page. If you are creating a new script, you must first create the Script and then navigate to the merge page to copy step information.

Note: Duplicate versus Merge. The Script page itself has duplication capability. You would duplicate a script if you want to a) create a new script and b) populate it with all the steps from an existing script.

Next in This Section

- Script Merge

Script Merge

Open Admin > System > Script Merge to open this page.

Description of Page

For Original Script, select the target script for merging steps.

For Merge From Script, select the template script from which to copy the steps.

Note: You may only copy steps from one Merge From script at a time. If you want to copy steps from more than one script, select the first Merge From script, copy the desired steps, save the original script, and then select the next Merge From script.

The left portion of the page displays any existing steps for the Original Script. The right portion of the page displays the existing steps for the Merge From Script.

You can use the Copy All button to copy all the steps from the Merge From script to the Original script. If you use Copy All, the steps are added to the end of the original script.

Each time you save the changes, the system renumbers the steps in the original script using the Start From Sequence Number and Increment By.

Merge Type indicates Original for steps that have already been saved in the original script or Merge for steps that have been merged, but not yet saved. The Sequence, Step Type and Description for each step are displayed.

The topics that follow describe how to perform common maintenance tasks:

Resequencing Steps

If you need to resequence the steps:

- Use the up and down arrows in the Original Script grid to reorder the steps.

- Make any desired changes to the Start From Sequence Number or Increment By.

- Click Save.

The steps are given new sequence numbers according to their order in the grid.

Removing a Step from Script

If you want to remove a record linked to the Original script, click the delete button, , to the left of the record.

For example, to remove the Reset existing bundle XML step, click the icon.

After removal, the grid displays:

Note: You cannot delete a step that is referenced by other steps unless you also delete the referencing steps, such as Go to step or Prompt type steps. The system informs you of any missing referenced steps when you attempt to save the original script.

Adding a Step to a Script

You can move any of the steps from the Merge From script to the Original Script by clicking the left arrow adjacent to the desired step. Once a record is moved it disappears from the Merge From information and appears in the Original information with the word Merge in the Merge Type column.

For example, to copy the Navigate to a page step, click the left arrow.

The step is moved to the left portion of the page.

Note: If you add a step, such as Go to step or Prompt type steps, that references other steps, you must also add the referenced steps. The step references are updated to use the new sequence numbers when you save the original script. The system informs you of any referenced steps that haven't been added when you attempt to save the original script.

Removing an Uncommitted Step from a Script

Maintaining Functions

Note: Functions were implemented prior to the introduction of business services (BS), service scripts (SS) and business objects (BO). The functionality is still supported, but the recommendation for implementations going forward is to use one of the above configuration tool objects in a script rather than defining a function. The documentation has not been updated throughout this section to highlight where BS, SS or BO could be used to perform the equivalent logic.

Invoke function steps may be used to retrieve or update data independent of the page currently being displayed. For example, if you design a script that takes different paths based on the customer's customer class, you could invoke a function to retrieve the customer's customer class. Doing this is much more efficient than the alternative of transferring to the account page and retrieving the customer class from the Main page.

An Invoke function step retrieves or updates the relevant data by executing a service (on the server). These types of steps do not refer to the service directly. Rather, they reference a "function" and the function, in turn, references the service.

Note: Functions are abstractions of services. A function is nothing more than meta-data defining the name of a service and how to send data to it and retrieve data from it. Functions allow you to define a scriptwriter's interface to services. They also allow you to simplify a scriptwriter's set up burden as functions can handle the movement of data into and out of the service's XML document.

The topics in this section describe how to set up a function.

Note: You can retrieve data from all base-package objects. If you know the name of the base-package "page" service used to inquire upon an object, you can retrieve the value of any of its fields for use in your scripts. To do this, set up a function that sends the unique identifier of the object to the service and retrieves the desired fields from it.

Next in This Section

- Function - Main

- Function - Send Fields

- Function - Receive Fields

Function - Main

Use this page to define basic information about a function. Open this page using Admin > System > Function.

Description of Page

Enter a unique Function code and Description for the function.

Use the Long Description to describe, in detail, what the function does.

Define the Internal Service that the function invokes.

Note: In this release, only page services can be invoked.

Click the View XML hyperlink to view the XML document used to pass data to and from the service. Doing this causes the XML document to be displayed in the Application Viewer.

Note: XML document may not be viewable. If you create a new page service and do not regenerate the application viewer, you will not be able to view its XML document.

The tree summarizes the following:

- The fields sent to the service. You can use the hyperlink to transfer to the Send Fields tab with the corresponding field displayed.

- The fields received from the service. You can use the hyperlink to transfer to the Receive Fields tab with the corresponding field displayed.

- Scripts that reference the function. You can use the hyperlink to transfer to the script page.

Function - Send Fields

Use this page to add or update the fields sent to the service. Open this page using Admin > System > Function and then navigate to the Send Fields tab.

Note: Displaying a specific field. Rather than scrolling through each field, you can navigate to a field by clicking on the respective node in the tree on the Main tab. Also note, you can use the Alt+right arrow and Alt+left arrow accelerator keys to quickly display the next and previous entry in the scroll.

Note: You're defining the service's input fields. On this tab, you define which fields are populated in the XML document that is sent to the service. Essentially, these are the service's input fields.

Description of Page

Use Sequence to define the order of the Send Fields.

Enter a unique Function Field Name and Description for each field sent to the application service. Feel free to enter Comments to describe how the field is used by the service.

Use Field Value Source to define the source of the field value in the XML document sent to the service:

- If the field's value is the same every time the function is invoked, select Defined On The Function. Fields of this type typically are used to support "hard-coded" input values (so that the scriptwriter doesn't have to populate the field every time they invoke the function). Enter the "hard-coded" Field Value in the adjacent field.

- If the field's value is supplied by the script, select Supplied By The Invoker. For example, if the function retrieves an account's customer class, the script would need to supply the value of the account ID (because a different account ID is passed each time the function is invoked). Turn on Required if the invoker must supply the field's value (it's possible to have optional input fields).

Regardless of the Field Value Source, use XML Population Logic to define the XPath expression used to populate the field's value in the XML document sent to the service.

Note: Usability suggestion. You populate a field's value in an XML document by specifying the appropriate XPath expression for each field. Rather than referring to an XPath manual, the system can create the XPath expression for you. To do this, click the adjacent View XML hyperlink. This will display the XML document used to communicate with the Service defined on the Main page. After the XML document is displayed, click the XPath hyperlink adjacent to the desired field to see how the XPath expression looks. You can then cut / paste this XPath expression into the XML Population Logic Field.

Function - Receive Fields

Use this page to add or update the fields received from the service. Open this page using Admin > System > Function and then navigate to the Receive Fields tab.

Note: Displaying a specific field. Rather than scrolling through each field, you can navigate to a field by clicking on the respective node in the tree on the Main tab. Also note, you can use the Alt+right arrow and Alt+left arrow accelerator keys to quickly display the next and previous entry in the scroll.

Note: You're defining the application service's output fields. On this tab, you define which fields are populated in the XML document that is received from the service. Essentially, these are the service's output fields.

Description of Page

Use Sequence to define the order of the Receive Fields.

Enter a unique Function Field Name and Description for each field received from the service. Feel free to enter Comments to describe the potential values returned from the service.

Turn on Required if the invoker must use the field.

Regardless of the Field Value Source, use XML Population Logic to define the XPath expression used to retrieve the field's value from the XML document received from the service.

Note: Usability suggestion. You retrieve a field's value in an XML document by specifying the appropriate XPath expression for the field. Rather than referring to an XPath manual, the system can create the XPath expression for you. To do this, click the adjacent View XML hyperlink. This will display the XML document used to communicate with the Service defined on the Main page. After the XML document is displayed, click the XPath hyperlink adjacent to the desired field to see how the XPath expression looks. You can then copy / paste this XPath expression into the XML Population Logic Field.

Note: Fields in multiple lists. Note that the XPath expression generated in the application viewer refers to lists using a generic “list” reference. If a field within the list is unique across the service, the generic list reference is sufficient for the XML population logic. However, if the field you are trying to reference is in multiple lists, the XPath must include the list name. Adjust the Application Viewer’s generated XPath by adding the list name, which can be found in the overview panel in the Service XML viewer. For example, instead of /pageBody/list/listBody/field[@name=’FIELD_NAME’], the XPath Population Logic must read /pageBody/list[@name=’LIST_NAME’]/listBody/field[@name=’FIELD_NAME’].

Mobile Application

This section describes various entities and aspects involved in the configuration of a mobile application.

Next in This Section

- Understanding Mobile Devices

- Understanding Mobile Application Files

- Understanding Deployments

- Mobile Application Versioning

- Configuring Mobile Devices

- Configuring Deployment Options

- Mobile Application Master Configuration

Understanding Mobile Devices

Laptops, cellular phones, tablets, and other mobile devices may be used to interface with the system via the supported mobile applications. The mobile application and data reside locally on the mobile device allowing the user to work offline as needed.

This section describes concepts related to device management administration.

Next in This Section

- Mobile Platform

- Mobile Device Terminals (MDT)

- Registration

- Managing Attachments

- Device Data Encryption

Mobile Platform

The mobile solution consists of a thin runtime installed on the device, the mobile application files, and metadata. The mobile applications are built using HTML5 and JavaScript on top of the Oracle Utilities Mobile Library (OUML) platform. The application communicates with the server via RESTful Services exposed by the main application.

The mobile applications require metadata (such as lookups, business object definitions and more ) to function. All files for all mobile application reside in a shared location on the server. It is the metadata that controls the behavior and functionality unique to each mobile application. The metadata package for each mobile application is also known as a deployment.

The URL entered at application startup is the URL used for both communication with the server and locating the mobile application HTML5 and JavaScript files. The deployment is downloaded once the user selects which mobile application they will be using.

Refer to Understanding Deployments for more information.

This approach makes it easier to push out applications changes to crews without having to reinstall the application on the device. The footprint on the device is kept to the minimal allowing the rest to be downloaded at start time from the server. The thin runtime can be downloaded from the application store and is assumed to be rarely updated. Customers can make as many changes as they like to the application HTML5 and JavaScript files without having to physically reinstall anything on the device.

Mobile Device Terminals (MDT)

You must create an MDT record for each physical device that will use a mobile application to communicate with the main server application. The MDT record has to be uniquely identified by a device tag.

The product provides a replicator tool on the MDT portal that may be used to create many MDT records that share the same device tag prefix.

An MDT Type defines attributes common to mobile devices of a certain type such as synchronization settings, attachment maximum size, and so on.

Registration

The first time a mobile user runs the mobile application, they will be required to register their mobile device.

The system will ask for the MDT Tag and the URL of the server application. The MDT Tag is a unique, user-defined identifier that is assigned to the device when the MDT record is created on the server application.

As part of the registration process, the system posts the device's unique ID on the MDT record on the server. Various mobile platforms like iOS, Android, and Windows provide a system level API to get the device's unique hardware ID which is used as the device's unique ID.

Once the device is registered, the mobile user will be able to log on to the application from that device without further prompting.

All the platforms return the same ID consistently, except for iOS that assigns a unique ID for the application when it is installed. This means that for iOS, the MDT's unique ID changes each time the application is uninstalled and installed again. In this situation, you would need to reset the unique ID stamped on the MDT record after reinstalling the application. Use the Reset Registration action on the MDT portal to do so.

Managing Attachments

The MDT Type may also set a limit for the total size for attachments on mobile devices of that type. When a user attempts to download an attachment, the system validates that the total size of the download plus what is already on the mobile device will not exceed the maximum for the mobile device.

The total size specified should take into account common attachments that are included as part of the mobile application deployment part configuration. These are automatically downloaded along with the mobile application.

Device Data Encryption

You have the option of enabling or disabling data encryption globally as well as for specific devices.

Use the Data Encryption parameter on the Mobile Configuration (master configuration) record to turn device data encryption on or off globally.

Each MDT has a data encryption setting which you can set to either use the global default, or turn it on or off for this device.

Understanding Mobile Application Files

The mobile application consists of the Oracle Utilities Mobile library and application layers responsible for specific business functionality. It uses HTML5 and JavaScript to implement business logic, render the user interface and interact with mobile device services. RESTful services facilitate communication between the mobile application and the application server.

The following diagram illustrates the mobile application architecture in a high level.

Figure 1. Mobile Application Architecture

The following sections describe concepts related to the mobile application solution as well as how your implementation may extend it to meet your mobile application requirements.

Next in This Section

- Oracle Utilities Mobile Library (OUML)

- Business Logic Resides in Mobile Components

- Packaged by a Batch Process

- Testing

Oracle Utilities Mobile Library (OUML)

The Oracle Utilities Mobile Library provides a foundation layer and APIs for application development including offline storage, encryption, communication, logging, configuration, UI rendering, navigation, customization, deployment and so on.

The library of APIs is optimized to work with Oracle Utilities Application Framework (OUAF) based services, configurations and metadata mainly around supporting the notion of business objects.

Inbound and outbound communication between the mobile application and server is based on RESTFul services and JSON payload. Messages to the server are stored in the device’s local database and then forwarded to the server. In situations where device is offline at the time of making an outbound request the communication module of the mobile application ensures the delivery of the message when device is back online and communication with server is reestablished.

Business Logic Resides in Mobile Components

Business logic supporting the various types of mobile application deployments is implemented in the form of mobile components of the following types:

- Standalone pages.

- Business objects.

- Shared components include:

- Business Object Status Enter and Post Processing plug-ins. These implement business rules triggered when a business object transitions to a new state in its lifecycle or updated respectively. The same plug-in may be associated with multiple business objects.

- Services. A service implements an independent function that can be called from various places in the application.

- UI Sections. These model reusable form sections that can be references on multiple pages.

- A library of common functions. Implements a library of functions that can be shared across the application.

- Message to device. Implements a type of message that is sent from the server to be processed on a mobile device.

- Product Configuration. Defines global settings for the mobile application.

- Themes. Defines swatches and styles for the mobile application.

The following sections describe how mobile components are implemented and used.

Mobile Component Ownership

Mobile components are system-owned records stored in a designated maintenance object. The base product is released with all the necessary mobile components needed to support its mobile applications.

You may implement new custom mobile components to meet your organization’s mobile application requirements.

As a rule, only the component’s owner is allowed to change and delete it. However, some types of components allow custom extensions where custom content may be added to base components. For example, you may customize a base owned business object mobile component to add more plug-ins when it transitions to a specific state, etc.

Mobile Component Editor

Mobile components are implemented using a browser-based editor. Use the Mobile Component portal to author custom mobile components as well as extend the content of base components.

Packaged by a Batch Process

The source of mobile components is stored in the database and as such can me migrated from one environment to another using standard tools such as Bundling and CMA.

The mobile application requires this content (HTML, JavaScript and CSS etc) to be available in the form of files. The Build Mobile Component Package batch process needs to run to generate files based on mobile component content and package them into an application bundle file on a shared location on the server. The bundle is downloaded when the application is launched from the mobile device.

The following illustration shows how mobile components are converted to files and packaged along with the OUML files as the mobile application bundle.

Figure 1. Mobile Application Bundle

Note: The Build Mobile Component Package batch process should run on demand to package the mobile application bundle as a zip file. Refer to F1-BMCOM batch control for more information.

Testing

The mobile application is packaged and deployed as a client application in the format native to the supported runtime platforms. The files in the mobile application bundle are downloaded to the mobile device when the client application is launched.

The following illustration describes how to test the mobile application on a mobile device.

Figure 1. Mobile Device Testing Illustration

For testing and development purposes, the mobile application files be directly accessed as a web application using Chrome browser. This approach does not require the files to be bundled.

To simplify browser-based testing in a shared application server, content changes made via the mobile component editor are also automatically synced to the corresponding file in the shared file system. You do not need to run the packaging batch process when testing this way.

The following illustration describes this process.

Figure 2. Shared Development/Testing Illustration

Use these steps to test the application using Chrome:

- If not already installed, install the Google Chrome desktop browser.

- Create a shortcut to the executable on your desktop.

- Right-click the shortcut and choose Properties, then append the following to the Target property to disable cross-domain JavaScript security:

--user-data-dir="C:/Chrome dev session"  --disable-web-security --allow-file-access-from-files --allow-file-access

- Start Chrome via the shortcut and load the mobile application at: http://server:port/ouaf/mobility/rest/test/www/index.html

Note that certain device specific features, such as barcoding, capturing a picture, etc., are not available when the application is accessed this way. Testing these features must be done using the native application.

Warning: Chrome must NOT be used in a production environment. It is only certified to be used for development and debugging purposes.

Understanding Deployments

A deployment refers to a specific cut of application metadata and control records needed to support a mobile application of a specific type and language. The deployment is downloaded to the mobile device terminal (MDT) by the corresponding mobile application.

This section describes topics related to managing mobile application deployments.

Next in This Section

- Deployment Types

- Deployment Parts

- Deployment

- Out of Date Deployments

- Downloading Deployments

- Setting Up Deployments

Deployment Types

A deployment type represents the configuration needed to support an application of a given type. You can configure multiple types of applications by setting up a deployment type for each.

A deployment type configuration defines the following aspect of the mobile application:

- The application items included in the application, by referencing deployment parts.

- The initial function that starts the business flow on the device when the application is launched.

- The MDT Types compatible to run this type of application.

- The authorized user groups that are allowed to use the mobile application.

- The application message categories used by the mobile application.

Deployment Parts

Deployment parts provide a way to create reusable groups of application items. A deployment part is a collection of application components, such as business objects, lookups, task types, and many more that are needed to support the mobile application.

The base product provides preconfigured deployment parts that include the base mobile application components. You only need to configure parts to include your custom entities. Make sure to include your custom deployment parts as part of your deployment type setup.

Create deployment parts to represent subsets of your custom deployment items based on their type or usage. You should share deployment parts across deployment types when applicable to prevent redundancy and improve management of deployment configuration. For example, use a designated deployment part for control data, another for items that are common across platforms, another with user interface items for a specific platform etc.

To simplify the collection of items in a deployment part it is recommended that you create an export bundle per deployment part so that implementations can add their new or changed items directly to the corresponding bundle using the dashboard zone. Once items are collected, the bundle can be uploaded to the deployment part. You can always maintain items manually on a deployment part.

Consider where attachments must be automatically pushed to the mobile application as pat of the deployment and add them to your deployment parts.

Deployment

A deployment can only be created using the Create Deployment batch process. Once your deployment type setup is complete, submit the batch to create a new deployment for your deployment type for a specific language.

Once the batch job runs and the deployment has been created, it has to be manually activated on the deployment portal before it can be deployed to any devices.

Note: The Create Deployment batch process should run on demand or periodically based on your business needs to avoid situations where out of dates deployments are being used. Refer to F1-DPLOY batch control for more information.

Out of Date Deployments

Deployments become out of date when a new mobile application version is released, the deployment type configuration changes, or any underlying application component that is part of the configuration changes.

Mobile users are warned at login to their mobile device that they are using an out of date deployment. The user is allowed to continue, but is advised to contact their administrator to synchronize their deployment. Refer to Downloading Deployments for more information.

The product provides a batch process that evaluates existing active deployment records and marks those that are out of date if it detects any metadata changes. The background process also purges out of date deployments that are older than a specified number of days.

Note: The Deployment Evaluation and Purge batch process should run on demand or periodically based on your business needs to avoid situations where out of dates deployments are being used. Refer to F1-DPUTD batch control for more information.

Also note that as part of accepting a new product release, all existing deployments are marked as out of date. New deployments are required to be created and activated.

When an active deployment is marked out of date, the system creates a To Do entry in order for a user to create a new deployment as needed. Creating a new deployment for the same deployment type and language automatically closes any remaining To Do entries reported for out of date deployments for the same configuration.

Downloading Deployments

Once a deployment has been activated, it is available for download to mobile devices. When the mobile user logs on to the mobile application, the system looks for the most recent version of all active, qualified deployments based on the user's user group, language, and MDT type.

If no deployments are found, the system displays an authorization error message and prevents the user from continuing.

If only one deployment is found and it is the same as the one currently deployed, then the deployment is not downloaded.

If only one deployment is found and it is newer than the one currently deployed or there is none currently deployed, then the deployment is downloaded to the mobile device.

If more than one deployment is found, the user can select the one they want to download.

Note: A new deployment will not be downloaded if unprocessed data from a previous shift still exist on the device. The system warns that user of the situation. If the user is authorized to use the deployment currently on the device, it will be used; otherwise, an authorization error will be displayed

Setting Up Deployments

This section summarizes steps involved in configuring your deployment types:

- Review the various types of devices that needs to be supported and set up corresponding MDT types.

- Define MDT records for each mobile device.

- Create deployment parts to represent subsets of your custom deployment items based on their type or usage.

- Set up a deployment type for each type of application you need to support. For example, the product supports a mobile application for a crew to work their schedule, and another application for a contractor worker.

- Specify the deployment parts and message categories needed to support the application.

- List applicable MDT Types.

- Identify the user groups authorized to use the application and associate them with the deployment type.

- When you have finished defining each deployment type, you need to run the Create Deployment batch process to create a deployment for it for each language supported by your company. Refer to F1-DPLOY batch control for more information.

- Activate each deployment.

Mobile Application Versioning

The mobile application communication architecture involves both client side and server side elements. When a deployment is created on the server, it is marked with the version number of the server side mobile application components that created it. The same version number is also stamped on the mobile application bundle when generated on the server. The version of these elements on the device must match the latest version on the server else errors will occur.

With each new product version, existing deployments stamped with the older version are marked as out of date and existing application bundles are deleted. New deployments need to be created and activated and a new application bundle must be regenerated with each product upgrade.

Note: The Create Deployment batch process should run to create a new deployment for each mobile application type and language applicable to your organization. Refer to F1-DPLOY batch control for more information. Once created, each deployment should be activated.

Note: In addition, the Build Mobile Component Package background process should run to regenerate the mobile application bundle. Refer to F1-BMCOM batch control for more information.

To enforce compatibility, the system validates the mobile application version as follows:

- Only deployments and application bundles that are compatible with the server mobile application version can be downloaded.

- When the mobile device attempts to connect to the server, the system checks whether or not the mobile application version already on the device is compatible with the mobile application version on the server. If the versions are not compatible, the device is not allowed to work online and no communication is sent to and from the server. In this situation, the mobile device must be upgraded to the correct version before it can work online again. If there was data on the mobile device, the user can continue offline and manually collect any data they need before the mobile device is upgraded.

Note: Before the server is upgraded, all users using the mobile application must be allowed to end their work successfully from their mobile devices and logoff. This prevents the incompatible version situation described above.

The About section on the Settings menu option on the mobile device shows the mobile application version number. This version is also stamped on the MDT record on the online mobile device screen.

Configuring Mobile Devices

The following section describes mobile device configuration options.

Next in This Section

- Defining MDT Types

- Defining MDTs

Defining MDT Types

This portal is used to maintain MDT types.

Refer to Understanding Mobile Devices for more information.

You can access the portal from theAdmin Menu > Mobile > MDT Type.

The following zones may appear as part of the portal's Main tab page

- MDT Type List. This zone lists all MDT types. Broadcast a record to display the details of the selected deployment part.

- MDT Type. This zone provides information about the selected MDT type.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_MDT_TYPE.

Defining MDTs

This portal is used to display and maintain a mobile data terminal (MDT). You need to define a mobile data terminal (MDT) record for each mobile device that needs to communicate with the system to send and receive work using the mobile application.

You can access the portal from theAdmin Menu > Mobile > MDT. You are brought to a query portal with options for searching for a specific MDT. Once an MDT has been selected you are brought to the maintenance portal to view and maintain the selected record.

Refer to Understanding Mobile Devices for more information.

The MDT zone on the portal's Main tab page provides information about the mobile device.

The following zones may appear as part of the portal's Log Files tab page:

- Mobile Log Files Search. This zone allows you to search for log files that may have been sent in from the mobile device to a designated location on the sever.

- Mobile Log. This zone shows server logging information related to communications made using this mobile device, if this feature is enabled from the mobile device.

Replicate MDTs

You may use the Replicate button set up a bulk of MDT records based on the details of the current MDT. This function sets the device tag for each new MDT to the prefix text you provide and a running sequence number.

Getting the MDT Log Files

Log files are not sent to the server automatically; they are only sent on demand, usually for debugging or tracing purposes. Use the Get Log Files button to send a message to the device to send log files to the server. When the device sends the files, you may use the Log Files tab to view their content.

Changing the Mobile Device Log Level

Click the Set Log Level button to send a request to the device to change the logging level used by the mobile application. Once the mobile device is updated, it sends a response back to the server to update the current log level on the MDT record to reflect the change.

Reset Registration

If this MDT is used by an iOS device and the mobile application was reinstalled on the device, the unique ID has to be reset before the MDT can be used again. Click the Reset Registration button to do so.

Refer to Registration for more information.

Configuring Deployment Options

The following section describes mobile device configuration options.

Next in This Section

- Defining Deployment Parts

- Defining Deployment Types

- Maintaining Deployments

- Defining Mobile Components

Defining Deployment Parts

This portal is used to maintain deployment parts. You may upload a predefined bundle when adding or updating a deployment part.

Refer to Understanding Deployments for more information.

You can access the portal from the Admin Menu > Mobile > Deployment Part.

The following zones may appear as part of the portal's Main tab page

- Deployment Part List. This zone lists all deployment parts. Broadcast a record to display the details of the selected deployment part.

- Deployment Part. This zone provides information about the selected deployment part.

- Deployment Items. This zone lists the application items included in this deployment part.

- Referenced By Deployment Types. This zone lists the deployment types referencing this deployment part.

CAUTION:

Important! If you introduce a new deployment part, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_DEPLOYMENT_PART.

Defining Deployment Types

A deployment type represents a specific type of mobile application. This portal is used to maintain deployment types.

Refer to Understanding Deployments for more information.

You can access the portal from the Admin Menu > Mobile > Deployment Type.

The following zones may appear as part of the portal's Main tab page

- Deployment Type List. This zone lists all deployment types. Broadcast a record to display the details of the selected deployment type.

- Deployment Type. This zone provides information about the selected deployment type. You may use the New Deployment link to submit the batch process to create a new deployment.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_DEPLOYMENT_TYPE.

Maintaining Deployments

This portal is used to view existing deployments and change their status.

Note: A deployment has to be activated before it can be downloaded to mobile devices. You can also inactivate a deployment so that it can no longer be deployed.

Refer to Understanding Deployments for more information.

You can access the portal from the Admin Menu > Mobile > Deployment. You are brought to a query portal with options for searching for a specific deployment. Once a deployment has been selected you are brought to the maintenance portal to view and maintain the selected record.

The Deployment zone on the portal's Main tab page provides information about the mobile device.

The following zones may appear as part of the portal's Main tab page

- Deployment. This zone provides information about the selected deployment.

- Out of Date Items. This zone lists items that have changed and caused the deployment to become out of date. Expand the zone to request the system to evaluate the deployment now. If the deployment is out of date, it is marked as such and the zone lists the out of date items information.

Defining Mobile Components

This portal is used to maintain mobile components. You may use this portal to review the base components as well as extend them or implement new custom mobile components to support your mobile application requirements.

Note: You need to run the Build Mobile Component Package background process to include your custom mobile component content as part of the application bundle that is downloaded when the mobile application is launched from a mobile device. Refer to F1-BMCOM batch control for more information.

Refer Understanding Mobile Application Files for more information.

You can access the portal from the Admin Menu > Mobile > Mobile Component.

The following zones may appear as part of the portal’s Main tab page:

- Mobile Component. This zone provides general information about the selected mobile component.

- Mobile Component Content Editor. This zone is used to maintain the various contents associated with the selected mobile component.

CAUTION:

Important! If you introduce a new mobile component, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_MOBILE_COMPONENT.

Mobile Application Master Configuration

The Mobile Configuration (master configuration) record defines several system wide settings related to mobile application functionality. For more information about specific fields in the master configuration, refer to the embedded help.

Attachments

Some implementations may require that attachments be available from the application. These attachments can be stored in the Attachment table and then linked to other objects if applicable.

Next in This Section

- Attachment Overview

- Configuring Your System for Attachments

- Maintaining Attachments

Attachment Overview

The following topics provide additional information regarding attachment functionality.

Attachment Types

The system supports several different attachment content types, for example:

- PDF Document

- Excel Spreadsheet

- Jpeg Image

- Text Document

The attachment data itself may be text or binary. When storing the data in the application however, it is stored as text information only. As a result, the upload of an attachment that is a binary type requires a conversion prior to storing the data. When viewing the attachment, the data is converted again for display.

Each type of attachment is defined using an attachment business object. The business object includes configuration defining the supported file extensions, whether the data is binary or not and the content type that represents the type of data for the attachment.

Note: To view the attachment business objects provided with the base product, navigate using Admin > Business Object > Search and search for business objects related to the Maintenance Object for Attachments (F1-ATCHMT).

Owned Attachments

Attachments can be either ‘owned’ or ‘common’. An owned attachment is one that is related to a specific record. For example, the specific test results for a given device can be uploaded and linked to that device or to its test records. These types of attachments are typically uploaded and maintained via the object that owns it.

Common Attachments

Common attachments are ones that are uploaded independent of any transaction in the system. They can be used for general system or company information. Or they can be linked to more than one transaction. For example, instructions for performing a certain type of task can be uploaded as an attachment and linked to a task type where those instructions are relevant. These types of attachments are uploaded and maintained in the central Attachment portal. Objects that may refer to the attachments may link the attachments via characteristics or some other appropriate mechanism.

Emailing Attachments

The system supports a business service that may be used by system processing to send an email. The business service F1-EmailService supports receiving the IDs of one or more attachments as input parameters.

Refer to Sending Email for more information.

Configuring Your System for Attachments

In order to link attachments to objects in the system, there may be some configuration or implementation required to support the link. It is possible that one or more objects in your product already support attachments out of the box. Consult the product documentation for the specific object for confirmation. For objects in the system that do not support attachments out of the box, the following sections provide some guidelines for enabling support for attachments. Contact product support for more information.

Supporting Common Attachments

The attachments themselves are created / uploaded using the attachment portal. Refer to Maintaining Attachments for more information.

If your implementation has a use case where one or more common attachments may be linked to an object (and the object does not already support this functionality), the object may need to be extended to capture the attachments.

- If the object includes a characteristic collection, this is a recommended way to capture attachments. A characteristic type should be defined for each type of attachment. The characteristic type should be a foreign key type and should reference the Attachment FK reference. The characteristic entity collection should include the object that the common attachment will be linked to.

- Most characteristic collections are sequence based characteristics and would support multiple entries for the same characteristic types, if multiple attachments are applicable.

- If the object to support the attachments is governed by a business object, the implementation must extend the business object to define one or more appropriate elements used to capture the attachments. If only one attachment of a certain type is allowed, a single flattened characteristic may be used. If multiple attachments of a certain type are allowed, the BO schema may define a “flattened list” exposing the sequence and the characteristic type.

- If the object is maintained on a “fixed page” with a generic characteristic collection, no additional configuration is needed to allow users to link attachments to that object.

Supporting Owned Attachments

When creating an attachment for a specific record, the attachment itself captures the information about the related record, namely its maintenance object code and its primary key. For these types of attachments, no configuration is needed on the related business object to capture the attachments, as was the case with common attachments.

However, it is recommended to configure the user interface of the related object so that the owned attachments can be viewed and maintained from that page. To do this, you may use the generic attachment zone provided by the product: F1-ATTCHOWN.

Note that your product may already have support for viewing and maintaining owned attachments on one or more if its base delivered portals.

Defining a New Attachment Type

As mentioned, the product provides support for several content types. If your implementation needs to support attachments for a content type not currently supported, create a new business object copying the configuration of an existing attachment business object.

Configure the following option types for the BO:

- Binary indicates whether the attachment data must be converted from binary format. Binary attachments are stored in the database as text, and are then converted back to the original format when retrieved.

- Content Type represents the browser's mime type of the attachment.

- Supported File Extension specifies the valid file extensions for the content type.

Once the business object is defined, it is ready for use.

Maintaining Attachments

This section describes the functionality supported for viewing and maintaining attachments.

Navigate using Admin > General > Attachment. You are brought to a query portal with options for searching for common attachments.

Once an attachment has been selected, you are brought to the maintenance portal to view and maintain the selected record.

Note: The base search options for the attachments query only support searching for common attachments. Owned attachments may also be viewed on the attachment maintenance portal, but a user may only drill into the attachment maintenance from the maintenance portal of the “owning” entity.

The Attachment zone provides basic information about an attachment, including the ability to upload the file and to view an uploaded file.

Next in This Section

- Adding Attachments

Adding Attachments

Common attachments may be added from the attachments portal (or via the standard menu path). In addition, your product may support attachments associated with specific records (“entity owned attachments”) which may also provide the capability to add attachments.

In both cases, when adding an attachment, you are prompted for the file to upload. Once the file is chose, the system determines the appropriate business object to associate with the attachment based on the file extension. Typically one and only one business object is found at which point you are prompted to provide the Attachment Name. (Your specific product may also require additional information at this time). Fill in the details and save.

Please note the following:

- If no business object is found for the uploaded file’s file type, an error is issued. This type of file is not currently supported as an attachment.

- If multiple business objects are found, the user must choose the appropriate one. This should be rare.

Application Viewer

The Application Viewer allows you to explore meta-data driven relationships and other deliverable files online.

Note: Running Stand-Alone. You can also launch the Application Viewer as a stand-alone application (i.e., you do not need to start it from within the system). Refer to Application Viewer Stand-Alone Operation for more information about running the Application Viewer as a stand-alone application.

To open the application viewer from within your application, navigate to Admin > Implementation Tools > Application Viewer. The application viewer may also be launched from other locations for example when viewing a section of the online help files that contain hypertext for a table name, clicking on that hypertext brings you to the definition of that table in the data dictionary.

Next in This Section

- Application Viewer Toolbar

- Data Dictionary

- Maintenance Object Viewer

- Algorithm Viewer

- Batch Control Viewer

- To Do Type Viewer

- Service XML Viewer

- Java Docs Viewer

- Groovy Java Docs Viewer

- Application Viewer Preferences

- Application Viewer Stand-Alone Operation

- Application Viewer Generation

Application Viewer Toolbar

The Toolbar provides the main controls for using the Application Viewer. Each button is described below.

Next in This Section

- Data Dictionary Button

- Physical and Logical Buttons

- Collapse Button

- Attributes and Schema Button

- Maintenance Object Button

- Algorithm Button

- Batch Control Button

- To Do Type Button

- Description and Code Buttons

- Service XML Button

- Select Service Button

- Java Docs Button

- Groovy Java Docs Button

- Classic Button

- Preferences Button

- Help Button

- About Button

- Slider Icon

Data Dictionary Button

The Data Dictionary button switches to the Data Dictionary application.

Physical and Logical Buttons

The Physical button changes the display in the List Panel from a logical name view to a physical name view. Note that the Tables are subsequently sorted by the physical name and therefore may not be in the same order as the logical name view. Once clicked, this button toggles to the Logical button.

The Logical button changes the display in the List Panel from a physical name view to a logical name view. Note that the Tables are subsequently sorted by the logical name and therefore may not be in the same order as the physical name view. Once clicked, this button toggles to the Physical button.

These buttons are only available in the Data Dictionary.

Collapse Button

The Collapse button closes any expanded components on the list panel so that the child items are no longer displayed.

This button is only available in the Data Dictionary viewer.

Attributes and Schema Button

The Attributes button changes the display in the Detail Panel from a related tables view to an attribute view. Once clicked, this button toggles to the Schema button.

The Schema button changes the display in the Detail Panel from an attribute view to a related tables view. Once clicked, this button toggles to the Attributes button. Note that only tables have this view available. Columns are always displayed in an attribute view.

These buttons are only available in the Data Dictionary.

Maintenance Object Button

The Maintenance Object button switches to the Maintenance Object viewer application.

Algorithm Button

The Algorithm button switches to the Algorithm viewer application.

Batch Control Button

The Batch Control button switches to the Batch Control viewer application.

To Do Type Button

The To Do Type button switches to the To Do Type viewer application.

Description and Code Buttons

The Description button changes the display in the List Panel to Description (Code) from Code (Description). Note that the list is subsequently sorted by the description. Once clicked, this button toggles to the Code button.

The Code button changes the display in the List Panel to Code (Description) from Description (Code). Note that the list is subsequently sorted by the Code. Once clicked, this button toggles to the Description button.

These buttons are only available in the Batch Control and To Do Type viewers.

Service XML Button

The Service XML button switches to the Service XML viewer. This button is not available when you are already in the Service XML viewer.

You are prompted to enter the name of the service XML file you want to view. The name of the service XML file should be entered without the extension.

Select Service Button

The Select Service button loads another service XML file that you specify. This button is only available in the Service XML viewer.

You are prompted to enter the name of the service XML file you want to view. The name of the service XML file should be entered without the extension.

Java Docs Button

The Java Docs button switches to the Java Docs viewer.

Groovy Java Docs Button

The Groovy Java Docs button switches to the Groovy Java Docs viewer.

Classic Button

This button is only available in the Java Docs viewer.

The Classic button launches the classic Javadocs viewer on a separate window. If you are more comfortable with that look you can use this viewer instead.

Preferences Button

The Preferences button allows you to set optional switches used by the Application Viewer. Refer to Application Viewer Preferences for more information.

Help Button

The Help button opens the Application Viewer help system. You used this button to access this information.

About Button

The About button opens a window that shows when was each Application Viewer data component recently built.

Data for all application viewer components may be regenerated to incorporate up-to-date implementation-specific information. Refer to Application Viewer Generation for further details.

Slider Icon

This "slider" icon allows you to resize the list panel and detail panel to your preferred proportions.

Data Dictionary

The data dictionary is an interactive tool that allows you to browse the database schema and to graphically view relationships between tables in the system.

To open the data dictionary, click the Data Dictionary button. You can also open the data dictionary by clicking the name of a table in other parts of the application viewer or in the online help documentation.

Note: Data Is Generated. A background process generated the data dictionary information. Refer to Application Viewer Generation for further details.

Next in This Section

- Using the Data Dictionary List Panel

- Using the Data Dictionary Detail Panel

Using the Data Dictionary List Panel

The list panel displays a list of tables and their columns. The list panel can list the table names by either their logical names or their physical names. Click the appropriate button on the toolbar to switch between the two views. The list is displayed in alphabetical order, so the order may not be the same in both views. Both views function in a similar manner.

In the list panel, you can navigate using the following options:

- Click the right arrow icon to expand a table to show its columns.

- Click the down arrow icon to collapse the column list for a table. Optionally, collapse all column lists by using the Collapse button.

- Click the column name to display information about the column in the detail panel.

- If the detail panel is in related table view, click the table name to view its related tables. If the detail panel is in table detail view, click the table name to display its information.

Next in This Section

- Primary And Foreign Keys

- Field Descriptions Shown

Primary And Foreign Keys

The columns in the list panel may display key information as well as the column name:

- A yellow key indicates that the column is a primary key for the table.

- A light blue key indicates that the column is a foreign key to another table. If you hover the cursor over the icon, the tool tip indicates the foreign table.

- A dark blue key indicates that the column is a conditional foreign key. A conditional foreign key represents rare relationships between tables where a single field (or set of fields) may reference multiple primary key constraints of other tables within the application as a foreign key.

- A red key indicates that the column is a logical key field. A logical key represents an alternate unique identifier of a record based on a different set of fields than the primary key.

If you hover your cursor over an icon, the tool tip indicates the key type.

Field Descriptions Shown

The language-specific, logical name of each field is shown adjacent to the physical column name in the data dictionary. You can enter an override label for a table / field's to be used throughout the system as the field's logical name. Here too it is the override label that is shown.

Note: Regenerate. You should regenerate the data dictionary after overriding labels. Refer to Application Viewer Generation for further details.

Using the Data Dictionary Detail Panel

The Data Dictionary detail panel displays the details of the selected item. There are three main displays for the Detail Panel:

- Related tables view

- Table detail view

- Column detail view

Next in This Section

- Related Tables View

- Table Detail View

- Column Detail View

Related Tables View

The Related Tables view displays information about the table's parent tables and child tables. Click the Schema button in the toolbar to switch to related tables view.

In the related tables view, you can navigate using the following options:

- Click the left arrow and right arrow icons to view the related tables for that linked table. The List Panel is automatically positioned to the selected table.

- Click the maintenance object icon ( ) to view the table's maintenance object.

- If you want to position the List Panel to view the columns for different table click the name of the table for which you want to view the columns.

Table Detail View

The table detail view displays information about the selected table. Click Attributes (in the toolbar) to switch to the table detail view.

In the table detail view, you can navigate using the following options:

- If user documentation is available for the table, click the View User Documentation link to read the user documentation that describes the table's maintenance object.

- If the table has an associated Language Table, click the link to view the Language Table details.

- If there is an associated Maintenance Program, click the link to view the source code for the maintenance program (you are transferred to the Java Docs Viewer).

- If there is an associated Key Table, click the link to view the Key Table details.

Column Detail View

Click on a column name in the list panel to switch to the column detail view. The Column Detail view displays information about the selected column.

In the column detail view, you can navigate using the following options:

- If user documentation is available for the column, click the View User Documentation link to read about the column's related maintenance object.

- If the column is a foreign key, click the table name to switch to the Table Detail view for that table.

- If the column has a Value List available (normally only present for a subset of flag and switch fields), click the link to view the source code for the copybook (you are transferred to the Java Docs Viewer).

Next in This Section

- Lookup Values

Lookup Values

If the selected column is a lookup field its valid values are also listed. Notice that you can enter an override description for lookup values. In this case the override description is shown.

Note: Regenerate. You should regenerate the data dictionary after overriding lookup value descriptions. Refer to Application Viewer Generation for further details.

Maintenance Object Viewer

The maintenance object viewer is an interactive tool that allows you to view a schematic diagram of a maintenance object. A maintenance object is a group of tables that are maintained as a unit.

To open the Maintenance Object Viewer, click the Maint. Object button in the application viewer or click a maintenance object icon in the Data Dictionary.

Note: Data Is Generated. A background process generated the maintenance object information. Refer to Application Viewer Generation for further details.

Next in This Section

- Using the Maintenance Object List Panel

- Using the Maintenance Object Detail Panel

Using the Maintenance Object List Panel

The list panel displays a list of maintenance objects. In the list panel, you can click the maintenance object name to display information about the maintenance object in the detail panel.

Using the Maintenance Object Detail Panel

The Maintenance Object detail panel displays a schematic of the selected maintenance object.

In the detail panel, you can navigate using the following options:

- Click a table name to transfer to the Data Dictionary table detail view for a table. (Click the Maint. Object button in the toolbar to return to the maintenance object.)

- Click the service XML icon () to view the XML file of the Service Program used to maintain the displayed object. (Click the Maintenance Object button in the toolbar to return to the maintenance object.)

Algorithm Viewer

The algorithm viewer is an interactive tool that allows you to view algorithm types (grouped by their plug-in spot) and their related algorithms.

To open the Algorithm Viewer, click the Algorithm button in the application viewer. The Algorithm viewer may also be opened from certain locations in the online help documentation.

Note: Data Is Generated. A background process generates algorithm information. Refer to Application Viewer Generation for further details.

Next in This Section

- Using the Algorithm Viewer List Panel

- Using the Algorithm Plug-In Spot Detail Panel

- Using the Algorithm Type Detail Panel

- Using the Algorithm Detail Panel

Using the Algorithm Viewer List Panel

The list panel displays a list of algorithm types and their related algorithms, grouped by their plug-in spot.

In the list panel, you can navigate using the following options:

- Click the algorithm plug-in spot description to display information about the plug-in spot in the detail panel.

- Click the right pointer icon to expand a plug-in spot and view its algorithm types and their related algorithms.

- Click the down pointer icon to collapse the list of algorithm types for a plug-in spot.

- Click the algorithm type name to display information about the algorithm type in the detail panel.

- Click the algorithm name to display information about the algorithm in the detail panel.

Using the Algorithm Plug-In Spot Detail Panel

The Algorithm plug-in spot detail panel displays further information about the selected plug-in spot.

Using the Algorithm Type Detail Panel

The Algorithm Type detail panel displays further information about the selected algorithm type.

In the Algorithm Type detail panel, you can navigate using the following options:

- Click on the program name to view its source in the Java docs viewer.

Using the Algorithm Detail Panel

The Algorithm detail panel displays further information about the selected algorithm.

Batch Control Viewer

The batch control viewer is an interactive tool that allows you to view batch controls.

To open the Batch Control Viewer, click the Batch Control button in the application viewer. The Batch Control viewer may also be opened from certain locations in the online help documentation.

Note: Data Is Generated. A background process generates batch control information. Refer to Application Viewer Generation for further details.

Next in This Section

- Using the Batch Control Viewer List Panel

- Using the Batch Control Detail Panel

Using the Batch Control Viewer List Panel

The list panel displays a list of batch controls. The list panel can display the list of batch controls sorted by their code or sorted by their description. Click the appropriate button on the toolbar to switch between sorting by the code and description.

In the list panel, you can click the batch control to display information about the batch control in the detail panel.

Note: Not All Batch Controls Included. Note that the insertion and key generation programs for conversion (CIPV*) are not included.

Using the Batch Control Detail Panel

The batch control detail panel displays further information about the selected batch control.

In the batch control detail panel, you can navigate using the following options:

- Click on the program name to view its source in the Java docs viewer.

- If a To Do type references this batch control as its creation or routing process, click on the To Do type to view its detail in the To Do type viewer.

To Do Type Viewer

The to do type viewer is an interactive tool that allows you to view to do types defined in the system.

To open the To Do Type Viewer, click the To Do Type button in the application viewer. The To Do Type viewer may also be opened from certain locations in the online help documentation.

Note: Data Is Generated. A background process generates To Do type information. Refer to Application Viewer Generation for further details.

Next in This Section

- Using the To Do Type Viewer List Panel

- Using the To Do Type Detail Panel

Using the To Do Type Viewer List Panel

The list panel displays a list of To Do types. The list panel can display the list of To Do types sorted by their code or sorted by their description. Click the appropriate button on the toolbar to switch between sorting by the code and description.

In the list panel, you can click the To Do type to display information about the To Do type in the detail panel.

Using the To Do Type Detail Panel

The To Do type detail panel displays further information about the selected To Do type.

In the To Do type detail panel, you can navigate using the following options:

- If the To Do type references a creation process or a routing process, click on the batch process to view its detail in the batch control viewer.

- Click on the table listed in the drill key section to view its detail in the data dictionary.

- Click on the field(s) listed in the drill key section to view its detail in the data dictionary.

Service XML Viewer

The service XML viewer is an interactive tool that allows you to browse the XML files of service programs that execute on the application server.

You can access the service XML viewer as follows:

- The maintenance object viewer allows you to view the XML file of the maintenance object's service program. This feature is implemented by viewing the maintenance object and then clicking on the Service XML icon.

- When viewing a maintenance object on the Maintenance Object page, clicking the View XML hyperlink causes the service’s XML document to be displayed in the Service XML Viewer.

- When viewing a business service on the Business Service page, clicking the View XML hyperlink causes the service’s XML document to be displayed in the Service XML Viewer.

- When setting up a Function, you may want to view the XML document used to pass data to and from the service. Clicking the View XML hyperlink causes the XML document to be displayed in the Service XML Viewer.

Next in This Section

- Using the Service XML Viewer Overview Panel

- Using the Service XML Viewer Detail Panel

Using the Service XML Viewer Overview Panel

The overview panel displays a high level nodes and list names structure of the XML document.

In the overview panel, you can click on any node item to position the detail panel to view that item.

Using the Service XML Viewer Detail Panel

The detail panel displays nodes and attributes of the selected XML file.

Click the xpath button to view the XML path that should be used to reference the selected node in the XML document. The box at the top of the overview panel changes to display this information.

Note: Fields in multiple lists. Note that the generated XPath expression refers to lists using a generic “list” reference. For example: /pageBody/list/listBody/field[@name=’FIELD_NAME’]. If a service has a field that appears in more than one list, the above XPath may not be sufficient for referencing that field. In this case, references to the XPath should be adjusted to include the list name. The list name is visible in the overview panel. To add the list name, use [@name=’LIST_NAME’]. For example: /pageBody/list[@name=’LIST_NAME’]/listBody/field[@name=’FIELD_NAME’].

Java Docs Viewer

The Java Docs viewer is an interactive tool that allows you to browse Java documentation files (Javadocs) for Java classes that execute on the application server.

Note: Proprietary Java Classes. A small number of Java classes have been suppressed due to their proprietary nature.

Note: Classic view. If you are more comfortable using the classic Javadocs viewer you may use the Classic button.

To open the Java Docs viewer from within the application viewer, click the Java Docs button. Additionally, the algorithm viewer and the batch control viewer allows you to view the Javadocs of a program written in Java.

Next in This Section

- Using the Java Docs Viewer List Panel

- Using the Java Package Detail Panel

- Using the Java Interface / Class Detail Panel

Using the Java Docs Viewer List Panel

The list panel displays a tree of Java packages where each package may be expanded to list the Java interfaces classes it includes.

In the list panel, you can navigate using the following options:

- Click the right arrow icon to expand a Java package to view the Java interfaces and classes it includes.

- Click the down arrow icon to collapse the list for a Java package. Optionally, collapse all lists by using the Collapse button.

- Click the Java interface or class name to display information about it in the detail panel.

The list details panel designates the interfaces and the classes as follows:

- A green dot indicates Java interfaces.

- A blue key indicates Java classes.

If you hover the cursor over the icon, the tool tip indicates whether it's an interface or a class.

Using the Java Package Detail Panel

The package detail panel displays a summary of the various Java classes that are included in the selected Java package.

Click the Java class name to display information about the Java class in the detail panel.

Using the Java Interface / Class Detail Panel

The detail panel displays Java documentation information about the selected Java interface or class.

You can navigate using hyperlinks to other locations in the current detail panel or to view the details of other Java interfaces / classes.

Groovy Java Docs Viewer

The Groovy Java Docs viewer is an interactive tool that allows you to browse Java documentation files (Javadocs) for the Java classes that are accessible to Groovy code within scripts.

Note: For system protection, only a subset of the base Java classes are available for use by Groovy code.

To open the Groovy Java Docs viewer from within the application viewer, click the Groovy Java Docs button. You can also access the viewer via the ‘View Groovy Javadocs’ link in the context sensitive Script Tips zone. Refer to the additional topics in the Java Docs Viewer section for details of how to navigate the viewer panels.

Application Viewer Preferences

This panel displays the Available Languages and allows you to select the language in which the labels and buttons are displayed. Select your desired language and click OK.

Application Viewer Stand-Alone Operation

You can run the Application Viewer as a stand-alone application (i.e., you do not need to launch it from the online application environment). To run it as a stand-alone application, you should copy the Application Viewer files (all files in the appViewer directory) and the online help files (all files in the help directory) to the server on which you want to run the Application Viewer.

Note: Online Help. If you do not copy the online help files, online help will not be available for the Application Viewer, nor will you be able to view business descriptions of the tables' maintenance objects.

To start the application viewer in stand-alone mode, launch the appViewer.html file (located in the appViewer directory).

Next in This Section

- Stand-Alone Configuration Options

- Example Application Viewer Configuration

Stand-Alone Configuration Options

You can configure the Application Viewer for stand-alone operation by modifying options in a configuration file. The Application Viewer comes with a default configuration file called config_default.xml (located in the appViewer\config directory). Create a copy of the default configuration file and rename it to config.xml. Modify the options described in the following table to suit the needs of your installation.

Note: Default Configuration. If you do not create the config.xml file, the Application Viewer launches with its default (internal) configuration.

Option

Description

defaultLanguage

The default language used when the application viewer is started. Available values are those marked as language enabled on the language page.

defaultView

The default view then the application viewer is started. Available values include:

- Data Dictionary

dataDictionary

Whether the Data Dictionary is available or not:

- Y

- N

sourceCode

This property is not being used. Simply enter ‘N’.

baseHelpLocation

The location of the stand-alone online help in relation to the application viewer. Specify the directory structure relative to the location of the directory in which the Application Viewer files are located. Note that this is the directory in which the language subdirectories for the online help are located. The default location is:

../help

appViewerHelp

The default help topic that is launched when the Help button is clicked in the Application Viewer. Specify a help file and anchor that is under the appropriate language directory under the baseHelpLocation. The default is:

Framework/Admin/91AppViewer.html#SPLINKApplication_Viewer

Example Application Viewer Configuration

The following excerpt shows an example Application Viewer configuration.

<?xml version="1.0" encoding="UTF-8" ?>

<configuration>

<option id="defaultLanguage">PTB</option>

<option id="defaultView">Data Dictionary</option>

<option id="dataDictionary">Y</option>

<option id="sourceCode">N</option>

<option id="baseHelpLocation">../help</option>

<option id="appViewerHelp">Framework/Admin/91AppViewer.html#SPLINKApplication_Viewer</option>

</configuration>

Application Viewer Generation

The Application Viewer is initially delivered with service XML information only.

The other components of the application viewer are generated on site.

- Use the background process F1-AVALG to regenerate algorithm information

- Use the background process F1-AVBT to regenerate batch control information.

- Use the background process F1-AVMO to regenerate maintenance object information

- Use the background process F1-AVTBL to regenerate data dictionary information.

- Use the background process F1-AVTD to regenerate To Do type information.

These processes have been introduced so that you can more easily incorporate your implementation-specific information into the application viewer.

To keep the information shown in the application viewer current it is important to execute these background processes after you introduce changes to the corresponding system data.

Note: Data Generation Is Not Incremental. Each new execution of these processes first deletes existing data (if any) in the corresponding folder before it generates new data.

Note: Other Extensions. Service XML may also be extended to include implementation-specific information. The base package is provided with special scripts that handle this type of extension. Refer to the Software Development Kit User Guide for further information on application viewer extensions.

Note: War File. If your application is installed in war file format, each generation of application viewer data rebuilds the corresponding war file. The web application server then needs to be "bounced" in order to make the newly generated data available to the application viewer. Please consult your system administrator for assistance.

Note: Certain Web Application Servers Are Special. WebSphere and Oracle Application web application servers require an additional step in order to make the newly generated data available to the application viewer. These web application servers require a rebuild of the application ear file and its redeployment in the web application server. This step is described in the installation document. Please consult your system administrator for further details.

Reporting and Monitoring Tools

This chapter describes various tools provided in the product to support reporting and monitoring.

Next in This Section

- Reporting Tool Integration

- Measuring Performance

- Capturing Statistics

Reporting Tool Integration

This section describes how to configure your third party reporting tool and how to define your reports in the system to enable users to submit reports online.

Next in This Section

- The Big Picture Of Reports

- Configuring The System To Enable Reports

- Sample Reports Supplied with the Product

- How To Define A New Report

The Big Picture Of Reports

The topics in this section describe the approach for designing and defining your system reports. Note that the product includes an out-of-the-box integration with BI Publisher. However it is possible to use the reporting objects to integrate with a different third party tool.

Next in This Section

- Integration with BI Publisher

- How To Request Reports

- Viewing Reports

Integration with BI Publisher

Your DBMS, your product, and BI Publisher can work together to produce reports. You may choose to use a different reporting tool, but this may not be a trivial effort. This section provides high-level information about some of the business requirements that are being solved with the reporting solution.

Multi-Language and Localization Support

The integration supports a multi-language implementation and supports different localization settings.:

- All labels, headings and messages are defined using field and message meta-data in the application, which support multiple languages.

- The appropriate font, size, and layout are based on the requested report and the user's language.

- Dates and numbers are formatted as per the user's display profile.

- Currency based numbers are formatted as per the currency definition from the product

Next in This Section

- Requesting Reports from The System

- Overview of the Data - BI Publisher

Requesting Reports from The System

Although reports are rendered in your reporting tool, users must be able to request ad-hoc reports from within the system (assuming users have the appropriate security access).

- The prompts for the input parameters must be shown in the user's language

- Users should be able to use the standard search facilities to find parameter values

- Plug-ins can be optionally used to cross-validate input parameters

- Application security must authorize ad-hoc report requests

Overview of the Data - BI Publisher

The following diagram provides an overview of where data is stored for your reports for integration with BI Publisher.

Figure 1. Application and BI Publisher

The application contains:

- The application data that appears on your reports.

- The language-specific headings, labels and messages on your reports.

- The layout file name to be used for the report.

BI Publisher contains:

- How your reports look.

- Information about scheduled reports and reports that have already run.

The DBMS contains the SQL used to retrieve the data on your reports (residing in database functions).

Note: BI Publisher can be configured to retrieve data via a service call. Because every business object can be read via a service call, elements that reside in an XML based column can be displayed on reports produced using BI Publisher. See your product's Installation Guide or Optional Products Installation Guide for information on this configuration.

How To Request Reports

A user may request an ad hoc report from within your product:

- A report submission page enables a user to choose the desired report and enter the parameter values for the report

- The user must be granted security access to the report

- The request is passed to the reporting tool real time. Refer to Configure The System to Invoke BI Publisher for more information.

- The reporting tool generates the report and displays it in a new browser window

The reporting tools' scheduler creates reports (as per your schedule). This function is entirely within the reporting tool. No scheduling functions reside within your product.

A user can request an ad-hoc report from within the reporting tool. Note, the user's ID must be supplied as a parameter to the report in order for the user's profile to be used to format dates and numbers

Viewing Reports

As described above, ad-hoc reports requested from within your product are displayed immediately after they are generated in a new browser window

If your reporting tools supports it, the Report History page may be configured to open tool’s report execution history page and request a view of this report.

Note: The Report History page currently does not display historical reports for BI Publisher.

Configuring The System To Enable Reports

Next in This Section

- Configuring BI Publisher Reports

- Defining Reporting Options

- Defining Report Definitions

Configuring BI Publisher Reports

This section contains topics specific about configuring the product to interoperate with BI Publisher.

Next in This Section

- Configure the System to Invoke BI Publisher Real-time

- Batch Scheduling in BI Publisher

Configure the System to Invoke BI Publisher Real-time

The base product provides an installation algorithm plug-in spot called Reporting Tool. This plug-in spot should contain an algorithm that invokes the third party reporting tool real-time.

For BI Publisher, the system provides an algorithm type called F1-BIPR-INV, which invokes BI Publisher.

These algorithms rely on information defined in the Reporting Options table: the reporting server, reporting folder and the user name and password for accessing the reporting tool. The values in the reporting options should have been set up when the system was installed. Contact your system administrator if there are any problems with the values defined on the reporting options.

To use the algorithm types to invoke BI Publisher, perform the following steps:

- Create an algorithm for the appropriate algorithm type.

- On the installation options, add an entry to the algorithm collection with an algorithm entity of Reporting Tool and indicate the algorithm created in the previous step.

Batch Scheduling in BI Publisher

For many of your reports, you probably want the report to be produced on a regular basis according to a scheduler. The reporting solution relies on the BI Publisher software to provide the batch scheduler functionality. Refer to BI Publisher documentation for details about configuring the batch scheduler.

Defining Reporting Options

The reporting options are provided as a mechanism for defining information needed by your reporting solution. The base product uses the reporting options to define information needed to access the reporting tool from within the system using the algorithm defined on the installation option.

Navigate to this page using Admin > Reporting > Reporting Options.

Description of page

Reporting Folder defines the shared folder where reports are stored.

Reporting Server defines the URL of the web application where the reporting tool is installed. For example, using BI Publisher, the format is: http://<BI Publisher Server>:<port>.

Reporting Tool User ID is not applicable when integrating with BI Publisher.

Other reporting tools may require a user id to use when logging in.

Reporting Tool Password is not applicable when integrating with BI Publisher.

Other reporting tools may require a password to use when logging in.

Note: Customize Options. The reporting options are customizable using the Lookup table. This field name is RPT_OPT_FLG. The reporting options provided with the system are needed to invoke the reporting tool. If your implementation requires other information to be defined as reporting options, use the lookup table to define additional values for the reporting option flag.

Where Used

This information is used by the reporting tool algorithm on the installation option to invoke the reporting tool software.

Implementations may use reporting options to record other information needed for their reporting tool.

Defining Report Definitions

For each report supplied by your installation, use the report definition page to define various attributes of the report.

Next in This Section

- Report Definition - Main

- Report Definition - Labels

- Report Definition - Parameters

Report Definition - Main

Navigate to this page using Admin > Reporting > Report Definition.

CAUTION:

Important! If you introduce new report definitions, you must prefix the report code with CM. If you do not do this, there is a slight possibility that a future release of the application could introduce a new system report with the name you allocated.

Description of page

Enter an easily recognizable Report Code and Description for each report. Use the External Reference ID to define the identifier for this report in your external reporting tool.

Define an application service to enable users to request submission of this report online or to view report history for this report. Once you define an application service for each report, use application security to define which users may access this report.

Note: Access Mode. The access mode for application services related to reports must be set to Submit/View Report.

If you have more than one parameter defined for your report and you wish to perform cross-validation for more than one parameter, provide an appropriate Validation Algorithm. Click here to see the algorithm types available for this system event.

Enter a Long Description to more fully describe the functionality of this report. This information is displayed to the user when attempting to submit the report online or when viewing history for this report.

For BI Publisher, if you want to use one of the sample reports provided by the system, but with a different layout, indicate the layout to use for the report in the Customer Specific Font/ Layout field and BI Publisher uses this information instead. The name for base report layout is <report code>_Base. For example, a base layout for CI_VACANT is named CI_VACANT_Base.

Report Definition - Labels

Navigate to this page using Admin > Reporting > Report Definition and go to the Labels tab.

Note: Company name and logo. Note the company name used as a title in the sample reports is defined as a message on the installation options. For information about installing the company logo, refer to your product's Installation Guide or the Optional Products Installation Guide.

Description of Page

In order to provide multi-language capability for each report, the labels used for the report must support multiple language definitions. For each label used by your report, indicate a unique Sequence and the Field used to define the Label. The label defined here should be the same label that is defined in your report layout defined in the external reporting tool.

When rendering an image of the report, the external reporting tool retrieves the appropriate label based on the language used for the report.

Report Definition - Parameters

Navigate to this page using Admin > Reporting > Report Definition and go to the Parameters tab .

Description of Page

The Parameters scroll contains one entry for every parameter defined for the report. The following fields display:

Parameter Code is the identifier of the parameter. This must correspond to the parameter definition in the reporting tool.

Required indicates that a value for the parameter must be defined when submitting the report.

Sort Sequence must match the parameter order defined in the reporting tool's report. It is also used when displaying the list of parameters on the report submission page.

Characteristic Type indicates the characteristic type used to define this parameter.

Default Value is option and if populated is displayed to the user when the report is chosen on the report submission page.

Description is a brief description of the parameter. This description is used when displaying the parameter on the report submission page.

Long Description is a detailed description of the parameter. This description is used on the report submission page when the user requests more information for a given parameter.

Sample Reports Supplied with the Product

Depending on your specific product, there may be sample reports provided that your organization may use as they are or as a starting point for creating a new report. The following sections provide an overview of the sample reports along with instructions on how to use one of the sample reports in your implementation environment.

Next in This Section

- How to Use a Sample Report Provided with the System

How to Use a Sample Report Provided with the System

If you would like to use any of the sample reports, you need to perform some steps to be able to execute them in an implementation environment. This section walks you through the steps needed.

Next in This Section

- Steps Performed at Installation Time

Steps Performed at Installation Time

Refer to the Installation Guide or Optional Products Installation Guide for instructions for setting up and configuring your product and reporting tool to use the sample reports provided with the system. The following steps are described there.

- Setting up the stored procedures used by the sample reports.

- Defining the company title and logo used by the sample reports. Note the company name used as a title in the sample reports is defined as a message on the installation options.

- Defining a user for integration with your product.

- Publishing the sample reports in BI Publisher.

Contact your system administrator to verify that the above steps have occurred.

How To Define A New Report

Next in This Section

- Use a Sample Report as a Starting Point

- Publishing Reports in BI Publisher

- Designing Your Report Definition

Use a Sample Report as a Starting Point

- Make a copy of the report and save it in an appropriate directory. Prefix the new report name with CM.

- Review the stored procedure(s) used for this report. Refer to the installation guide for information about where the stored procedures should be defined. If you want to change the data that is being accessed, copy the stored procedure, prefixing the new stored procedure with CM. Make the appropriate changes in the new version of the stored procedure. Contact your database administrator to find out the procedure for creating a new stored procedure.

Note: Performance considerations. When designing a stored procedure, you must consider the performance of the report when executed. Consult your database administrator when designing your database access to ensure that all issues are considered.

Note: Defining Messages. The stored procedures provided with the system use messages defined in message category 30. If your new stored procedures require new messages, use message category 90000 or greater, which are reserved for implementations.

- Review the parameters used by the report. Make appropriate changes to the parameters required by the report. This affects how you define your report. Refer to Designing Parameters for more information.

- Determine whether or not you require cross validation for your report parameters. If any cross validation is necessary, you should design an appropriate validation algorithm to be executed when requesting a report in your product. Refer to Designing Validation Algorithms for more information.

Note: Cross Validation for On-line Submission Only. The cross validation algorithm is only executed for ad-hoc report submissions via your product. If you submit this report through your reporting tool, this algorithm is not executed.

- Review the labels used by the report. Labels and other verbiage are implemented in the sample reports using a reference to the field table in the system. This enables the report to be rendered in the appropriate language for the user. For any new report label you require, you must define a new field entry. Refer to Designing Labels for more information.

- Review the layout of the report and make any desired changes based on your business needs.

When you have finished designing and coding your new report in your reporting tool, you must do the following in order for it to be usable:

- Publish the report in BI Publisher. Refer to the documentation for this products for details about publishing a report. Refer to Publishing Reports in BI Publisher for configuration information specific to publishing a report for integration with your product.

- Define the report. Refer to Designing Your Report Definition for more information.

Publishing Reports in BI Publisher

Please refer to the documentation for BI Publisher for more information about publishing a report in this system. The remaining topics in this section provide information about settings needed to ensure that the report is accessible using BI Publisher.

Next in This Section

- BI Publisher Database Access

- Verify BI Publisher User Access Rights

BI Publisher Database Access

When publishing a report in BI Publisher, you are asked for database logon information. The logon user name and password must be the user name and password that has access to the database functions related to this report in your database.

Verify BI Publisher User Access Rights

To verify the user's access rights to folders in BI Publisher:

- Open the BI Publisher Enterprise Security Center.

- Check that the role for the user has access to the appropriate report folders.

For more information, refer to the "Understanding Users and Roles" section in the Oracle Business Intelligence Publisher User's Guide.

Designing Your Report Definition

When adding a new report, you must define it in the system to allow users to request ad-hoc reports from on-line and to take advantage of the multi-language provisions in the system. The following topics illustrate the steps to take to correctly configure your report definition.

Next in This Section

- Designing Main Report Definition Values

- Designing Characteristic Types

- Designing Parameters

- Designing Validation Algorithms

- Designing Application Services

- Designing Labels

Designing Main Report Definition Values

Refer to field description section of the report definition main page for information about defining general information about the report.

For the validation algorithm, preliminary steps are required. Refer to Designing Validation Algorithms for more information.

For the application service, preliminary steps are required. Refer to Designing Application Services for more information.

Designing Characteristic Types

The parameter tab on the report definition page uses characteristic types to define the report parameters. For each report parameter that you plan to use, you must define a characteristic type.

You do not need a unique characteristic type for each report parameter. For example, if Start Date and End Date are parameters your report, only one Report Date characteristic type needs to be defined. This characteristic type would be used on both date parameters.

Each characteristic type to be used as a report parameter must indicate a characteristic entity of Report.

To illustrate the characteristic type definitions, let's look at the sample report Tax Payables Analysis. It needs the following parameters: From Date, To Date, GL Account Type Characteristic Type and Account Type value.

Note: Account Type Parameters. The tax payables report must find general ledger entries that have posted to a certain distribution code. In order to find the appropriate distribution code, the report expects each distribution code to be defined with a characteristic indicating its GL account type (for example, Revenue, Asset, etc.) The report needs to know the characteristic type used to define this entry.

To support the required parameters, the following characteristic types are needed.

Char Type

Description

Type

Valid Values

Char Entities

CI_DATE

Date Parameter

Ad-hoc

(Uses validation algorithm to validate proper date entry)

Report

CI_CHTYP

Characteristic Type

FK Reference

CHAR_TYP

Report

CI_GLTY

GL Account Type

Pre-defined

A- Asset, E- Expense, LM- Liability/miscellaneous, LT- Liability/taxes, R-Revenue

Distribution Code, Report

Highlights for some of the above settings:

- We have defined a characteristic type for defining a characteristic type. This is to allow the user to indicate which Char Type on the Distribution Code is used for the GL account type. This is an FK reference type of characteristic.

- The GL account type characteristic type is referenced on both the Distribution Code entity and the report entity.

Designing Parameters

Your report definition parameters collection must define a unique parameter entry for each parameter sent to the reporting tool. The sequence of your parameters must match the sequence defined in your reporting tool.

Continuing with the Tax Payables Analysis report as an example, let's look at the parameter definitions.

Parameter Code

Description

Char Type

Default Value

P_FROM_DT

From Date

CI_DATE

N/A

P_TO_DT

To Date

CI_DATE

N/A

P_CHAR_TYPE

Account Type Characteristic

CI_CHTYP

CI_GLTY

P_TAX_ACCTY_CHAR

Account Type Char Value for Tax Related GL Account

CI_GLTY

LT-Liability/taxes

Highlights for some of the above settings:

- The from date and to date parameters use the same characteristic type.

- The characteristic type parameter is defined with a default value pointing to the GL account type characteristic type.

- The GL account type parameter defines the liability/taxes account type as its default value.

Note: User Id. The sample reports provided by the system pass the user id as the first parameter passed to the reporting tool. It does not need to be defined in the parameter collection for the report.

Designing Validation Algorithms

When designing your report definition, determine if cross validation should occur for your collection of parameters. In the Tax Payables Analysis report, there are two date parameters. Each date parameter uses the characteristic type validation algorithm to ensure that a valid date is entered. However, perhaps additional validation is needed to ensure that the start date is prior to the end date. To do this, a validation algorithm must be designed and defined on the report definition.

The system provides a sample algorithm RPTV-DT that validates that two separate date parameters do not overlap. This algorithm should be used by the Tax Payables Analysis report.

If you identify additional validation algorithm, create a new algorithm type. Create an algorithm for that algorithm type with the appropriate parameter values. Plug in the new validation algorithm to the appropriate report definition.

Designing Application Services

Application services are required in order to allow a user to submit a report on-line or to view history for a report. Define an application service for each report and define the user groups that should have submit/view access to this report.

Update report definition to reference this application service.

Designing Labels

The system supports the rendering of a report in the language of the user. In order to support a report in multiple languages, the verbiage used in the report must be defined in a table that supports multiple languages. Some examples of verbiage in a report include the title, the labels and column headings and text such as "End of Report".

The system uses the field table to define its labels.

Note: Report Definition. This section assumes that your new report in the reporting tool has followed the standard followed in the sample reports and uses references to field names for all verbiage rather than hard-coding text in a single language.

For each label or other type of verbiage used by your report, define a field to store the text used for the verbiage.

- Navigate to the field page using Admin > System > Field.

- Enter a unique Field Name. This must correspond to the field name used in your report definition in the reporting tool and it must be prefixed with CM.

- Define the Owner as Customer Modification.

- Define the Data Type as Character.

- Precision is a required field, but is not applicable for your report fields. Enter any value here.

- Use the Description to define the text that should appear on the report.

- Check the Work Field switch. This indicates to the system that the field does not represent a field in the database.

Update the report definition to define the fields applicable for this report in the Labels tab.

If your installation supports multiple languages, you must define the description applicable for each supported language.

Measuring Performance

Many implementations need the ability to track and view the performance of key system processes against a defined target level. The framework provides objects to allow an edge product or an implementation to calculate and display performance measures against a desired target for one or more use cases. The topics in this section provide information about what is supplied in the framework and guidelines for implementing a specific use case for batch processes. Your specific product may supply out of the box support for additional use cases. Refer to your product specific documentation for more information.

Next in This Section

- About Performance Targets

- Setting Up Performance Target Configuration

- Maintaining Performance Targets

About Performance Targets

The following are examples of use cases that would be well suited for tracking as performance targets:

- Track and view the duration of key batch processes, either individually or as a group, and how they relate to a defined target.

- Monitor used and free space on a database against critical levels.

- Check the performance of individual user interface zones against a defined performance expectation

- Compare the number of web service requests made to an application against a threshold where performance may be of concern.

Framework provides functionality to define and categorize performance targets and link them to objects such as business services, zones and portals. This supports the calculation and display of the metrics against desired results.

In addition, Framework supplies out of the box support for batch process performance targets. Individual edge applications may supply more specific functionality for other use cases, if applicable.

Ideally, users should have the ability to view these performance targets on a dashboard that groups related measures. Framework provides the necessary components to achieve this for batch process performance targets.

The following sections highlight functionality supported for performance targets in the framework. Refer to the edge application product documentation for more details of other supported use cases.

Next in This Section

- Performance Target Objects Overview

- Calculating and Displaying Performance Targets

- Performance Target Metrics and Metric Types

- Performance Target Categories and Types

- Performance Targets Define Specific Metrics

- Objects Linked to a Performance Target

- Creating Performance Target Zones

Performance Target Objects Overview

The setup of a performance target involves a unique combination of configuration data and processing logic that calculates and displays a specific measure.

The framework performance target functionality is supported by a combination of inter-related objects, as shown below. Some of these objects will be generic for use in all performance targets while some are specific to a functional area such as batch processes.

- Maintenance Objects for capturing performance target types and performance target instances.

- Extendable Lookups to define performance target categories and performance target metrics.

- Business Services to calculate known metrics for a group of performance targets, such as for batch processes.

- UI Maps to interpret the performance calculation results and display them in charts that show the comparison to the target.

- A Zone that serves as a template for system duplication to create specific zones related to each performance target. The zone invokes a business service to perform calculations and display performance measures in the related UI map.

- Business Objects to capture configuration data for a specific performance target instance and its related objects.

- Functionality to create Zone instances for specific performance targets based on the associated template zone.

Each edge application will deliver the following to compliment the objects delivered by the framework:

- Portals to group related performance target zones.

- Specific entries for the performance target category Extendable Lookup .

The following sections describe the combined use of these objects for performance targets in more detail.

Calculating and Displaying Performance Targets

Performance targets are intended to be displayed in a portal using an explicit object zone. The zone parameters define both the business service used to calculate the performance metrics and the UI map that displays the results. While an individual performance target needs to reference a zone with a unique configuration that calculates a particular metric, those zones will be based on a template zone which defines the core parameters.

Framework provides a base Batch Performance Target Metric Template zone (F1-PERFBA) for batch process performance targets. Refer to this zone and its parameters for more information about the batch performance zone configuration and the related business service and UI map.

Performance Target Metrics and Metric Types

The framework supports two types of metrics for performance monitoring:

- Value based metrics are used to record results against a specific numeric target.

- Time based metrics are used to track the results against a specific date and time target.

The list of valid metrics for a given performance target category and its associated performance target types is maintained using an extendable lookup. Framework uses the base business object Batch Performance Target Metric (F1-BatchPerfTargetMetric) to define batch process metric values. Refer to this lookup for the supported batch process metrics.

Note: While users are not prevented from adding new values to the lookup, the list is not intended to be extendable as new values will not be recognized by the business service that performs the base batch performance calculation logic.

Your edge product or implementation may supply other extendable lookup business objects for additional performance measurement use cases, if applicable.

Performance Target Categories and Types

There are key configuration details required by all performance targets. These are defined on two related objects.

Performance Target Categories

Target categories define the template zone and security setting for a group of performance measures. The list of valid categories is maintained using an extendable lookup.

The framework product supplies the business object Performance Target Category (F1-PerformanceTargetCategory) for this functionality. Refer to the business object description and configuration for more information.

Performance Target Types

Target types define the related performance target business object and the display portal for a group of performance measures. In addition, a target type references a target category which defines the associated zone details.

The framework product supplies the business object Performance Target Type (F1-PerformanceTargetType) for this functionality. Refer to the business object description and configuration for more information.

The framework does not deliver any standard type or category values for batch processing performance targets. Refer to your specific edge application products to verify if any standard values are delivered for the batch processes within your applications. Edge applications may also supply standard categories and types for additional performance target use cases.

Performance Targets Define Specific Metrics

Although the types of measures and the business services and UI maps that govern how they are calculated and displayed are defined using separate objects, a performance target record defines the additional configuration needed to measure a specific metric and compare the result to a desired value.

There are key configuration details required by all performance target instances. These include a reference to the metric being measured, the desired target value or time, the desired result for the target and the unique zone by which this performance target will be monitored.

Note: The performance target maintenance object has a direct foreign key link to the extendable lookup business object and value that define the performance metric. This is an unusual pattern as extendable lookup values are normally recorded only in an object's schema. The pattern has been adopted to allow the description of the metric to be displayed in the performance target maintenance portal.

A given performance target type may require additional details for its calculations. For example, the framework batch process performance target defines additional details to restrict the measurement to specific batch processes that have executed within a given time frame. These details are configured on the performance target business object. Refer to the embedded help text on the business objects supplied by the framework and your edge applications for more information.

The performance target type also defines the business object to use when creating the resulting performance target record.

Objects Linked to a Performance Target

Some performance measures such as batch process metrics, derive the data for the calculation from objects within the system. The performance target can be linked to one or more related objects to define the specific data sources included in that target metric. For example, when creating a batch process performance target, the framework supports linking specific batch codes to the performance target to indicate the group of batch processes that are included in the measure.

The performance target business object may be configured to allow only relevant objects types to be linked to a performance target record. Refer to the base Batch Performance Target business object (F1-BatchPerformanceTarget) for an example.

Creating Performance Target Zones

Once a performance target and its objects have been defined, a unique zone needs to be created to display and monitor the specific target.

The framework functionality for batch performance targets implements the zone creation via the related business object lifecycle. When a performance target is added, status enter plug-ins are responsible for generating the new zone using the template zone and prefix configured on the target category (or the override values) and adding the zone to the portal configured on the target type. When a performance target is inactivated, an enter plug in is responsible for removing the zone from the portal.

Note: While the template zone associated with the performance target category may be overridden, the zone generation algorithm makes certain assumptions about the zone type and parameters. In particular, the logic expects to configure a zone parameter that references the performance target code as input to the business service responsible for calculating the metrics.

Refer to the base Batch Performance Target business object (F1-BatchPerformanceTarget) for details of the lifecycle and the enter plug-ins responsible for performance target zone creation.

Setting Up Performance Target Configuration

The following topics highlight the general configuration steps required to use performance target functionality. Your particular product or implementation may supply additional functionality to support specific use cases for performance targets. Refer to your product’s documentation and the library of business objects supplied for performance target in your system for more information.

Next in This Section

- Performance Target Category Lookup

- Defining Performance Target Types

Performance Target Category Lookup

Refer to About Performance Targets for an overview of performance target functionality.

Each Performance Target Type is associated with a unique Performance Target Category. The categories are defined as an extendable lookup.

Navigate to the Extendable Lookup portal. Search for and select the Performance Target Category business object. Define values that are appropriate to the categories your implementation is assigning for the performance target types in use. In some cases, an edge application may already have delivered the appropriate performance target category for your use

Refer to the embedded help for more information about configuring this object.

Defining Performance Target Types

Refer to About Performance Targets for an overview of performance target functionality.

To maintain the performance target types applicable to your product or implementation, open Admin > Reports > Performance Target Type.

This is a standard All-in-One portal.

The information captured on the performance target type depends on the business objects supported by your product or implementation. Refer to the embedded help text for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_PERF_TGT_TYPE.

Maintaining Performance Targets

This section describes the functionality supported for viewing and maintaining performance targets.

Refer to About Performance Targets for an overview of performance target functionality.

Navigate using Main > Reporting > Performance Target. This is an All-in-One portal and includes the standard List and display zones for a performance target.

For information about the data defined on the performance target, refer to embedded help.

Capturing Statistics

The product provides objects to allow for an edge product or an implementation to periodically calculate and capture statistics for one or more use cases. The topics in this section provide information about what is supplied in the framework and guidelines for implementing specific use cases.

Next in This Section

- About Statistics

- Configuring Your System for Statistics

About Statistics

There are two objects that work together to capture the statistics related to a given business use case:

- The statistics control record which defines configuration related to capturing statistics. It also defines a category that is used to group similar types of statistics together.

- The statistics snapshot is the record where the actual calculated statistics are captured.

Statistics Control

The statistics control record whether or not statistics are automatically calculated and how frequently. In addition, you may control the retention policy of snapshot record. You may indicate that only the most recent snapshot is kept or all snapshot records are kept or that they are retained for a defined number of days.

The system provides a business object for statistics control (F1-Statistics) that is expected to be used for most use cases. Its lifecycle includes the support for periodic capturing of statistics snapshot records as well as on demand capture.

Statistics Snapshot

The statistics snapshot object is the object that is responsible for calculating and capturing the statistics details. A separate business object must be defined for each use case. The schema of the business object defines the details that are captured. In addition, it must include an algorithm as an enter plug-in on the Complete state that is responsible for capturing statistics.

The system provides a 'root' business object for statistics snapshot (F1-SnapshotRoot) which includes the lifecycle that statistics snapshot business objects should follow. No explicit statistics snapshot use case is provided by the Framework. Your specific product may supply some out of the box support for certain use cases, in which case specific statistics snapshot business objects are provided. Refer to your product specific documentation for more information.

Viewing / Reporting Statistics

The product provides the mechanism for defining statistics control and statistics snapshot records and viewing the data in basic format. If your product has provided support for specific use cases, there may also be additional portals used to display the statistics in a meaningful format. For example, the statistics snapshot may be capturing data that can be presented in graphical format. Additionally, if multiple historical statistics snapshot records are retained, a zone may be defined to graph changes over time.

Configuring Your System for Statistics

If your product provides statistics use cases that you are planning to implement, all that you need to do is configure the appropriate statistics control record and define the appropriate configuration for your business requirements. Refer to Defining and Monitoring Statistics for more information.

If your implementation has identified an additional use case where you would like to capture statistics, the following points highlight the steps needed to configure the system to support the use case.

- Determine whether an additional Statistics Category value is needed. This is captured on the statistics category record. Navigate to the Lookup page. Search for and select the STAT_CATEGORY_FLG field. Review the values and determine if additional values are needed.

- Define a new statistics snapshot BO. This should be a child BO of the base delivered BO (F1-SnapshotRoot). Its schema should define elements for the specific information that is captured by the statistics calculations. The schema should be designed in conjunction with an appropriate Enter Status algorithm for the Complete that calculates the statistics as appropriate for the business requirement.

- Once the snapshot business object is designed and implemented, configure the appropriate statistics control record.

Next in This Section

- Defining and Monitoring Statistics

Defining and Monitoring Statistics

Refer to About Statistics for an overview of the statistics functionality.

To define and maintain statistics control records and view a list of the current snapshot records, open Admin > Reporting > Statistics Control.

This is an All-in-One portal and includes the standard List and display zones for a statistics control.

For information about the data defined on the statistics control, refer to embedded help.

Statistics Snapshot

If there are any Statistics Snapshot records for the statistics control, the Statistics Snapshot List zone displays a list of the most recent records. A user may drill into any of the records to view more detail. You are brought to a maintenance portal where you may view details about the calculated statistics. The information captured will be unique to the particular use case. Refer to the embedded help for more information.

External Messages

This section describes mechanisms provided in the product that enable an implementation to configure the system to communicate with an external application.

Next in This Section

- Incoming Messages

- Outgoing Messages

- Web Service Category

- JMS Message Browser

- Integration Cloud Service Catalog

- Mobile Remote Messages

- XML Application Integration

Incoming Messages

This section provides information about support for incoming messages.

Next in This Section

- Inbound Web Services

- Guaranteed Delivery

Inbound Web Services

Inbound web service functionality is provided to support receiving web service requests from an external system.

Next in This Section

- About Inbound Web Services

- Configuring Inbound Web Service Options

- Deploying Web Services

About Inbound Web Services

The following topics provide overview information about inbound web services (IWS).

Multiple Operations

An inbound web service supports the configuration of one or more operation per web service. Each operation defines the schema-based object to invoke to perform the desired function. An operation may refer to a Business Service, a Business Object, or a Service Script. If the IWS supports multiple operations, each operation can refer to the same or a completely different schema-based object from other operations within the IWS. In addition, each operation may define a transaction type, which is essentially an action that is supported by the schema-based object.

By default, Inbound Web Services uses the Schema Name to dictate the Request and Response for the service. The API can be overridden with custom formats by specifying Request and Response Schemas with the appropriate Request and Response XSL to transform into the relevant schema formats.

For business object based operations, when invoking the web service an action is required. This may be passed into the web service as part of the invocation or alternatively, the action may be defined when configuring the operation using the transaction type.

Note: Using the transaction type Change requires all values to be passed in. Using the transaction type Update allows the web service to pass only the primary key and the values to be updated. All other elements will retain their existing values.

Annotations Used for Security

When preparing to deploy inbound web services, the security aspects of the service must be decided. The product provides a default security policy that is applied when no other policy is defined: @Policy(uri=”policy:Wssp1.2-2007-Https-BasicAuth.xml”, attachToWsdl=true) which requires HTTP Basic over SSL and a WS-Security Timestamp.

If a different security policy is desired, the following options are available:

- Security policies may be attached to the Inbound Web Service via the Java Enterprise Edition (Java EE) Web Application Server. This allows for multiple policies to be attached as supported by the Java EE Web Application Server. In order to enable this capability, explicit system configuration is required so that the product does not assume the default security policy. See the subsequent bullets for more information.

- Define a system wide security policy using a feature configuration option. Find the Feature Configuration record for the External Messages feature type. (It may need to be defined if it does not exist). Choose the option type Default security policy and define an appropriate value. If your implementation wishes for the policies to be attached at the Java EE Web Application Server, define this option type with an option value of <none>.

- Attach a security policy to the IWS via a Web Service Annotation. The base product provides annotation types that support the standard WS-Policy (F1POLICY) and OWSM Security Policy (F1-OWSM). No base annotation is supplied by the product for either annotation type.

If your implementation wishes for the policy of a particular IWS to be attached at the Java EE Web Application Server, define a special annotation for the F1POLICY annotation type and configure the uri parameter value to <none>.

Note: Refer to WebLogic documentation for more information on supported security policies.

Note: In order to use the OWSM Policy, additional system configuration is necessary. Contact your system administrator to confirm if your implementation supports OWSM.

Inbound Web Service Deployment

An Inbound Web Service must be deployed to the Java EE Web Application Server in order for it to be available to the Web Service Clients to access the system. Refer to Deploying Web Services for more information.

Next in This Section

- Deploying XAI Inbound Service via IWS

Deploying XAI Inbound Service via IWS

For implementations using XAI inbound services for external messages, the product recommends moving to the inbound web service mechanism, which uses the Java EE Web Application Server to communicate with the product rather than the XAI servlet.

For XAI inbound services that use the Business Adapter, it is straight forward to move to IWS because the configuration is similar. In both cases, the service is configured to reference a business object, business service or service script. The associated WSDL for each record is similar. Changing the interface for the incoming message to use IWS instead of XAI inbound services is similar.

However, for XAI inbound services that use the Core Adapter, these services reference an underlying “page service” in the product. For these services, the Request and Response schemas for the XAI inbound service were created using the Schema Editor. In order to support calling an underlying "page service" in IWS, first a business service must be created to reference the page service (if one doesn’t already exist). However, the resulting schema for the business service is different from the Request and Response schemas related to the XAI inbound service. Moving this functionality to IWS using business services requires changes to the format of the incoming messages.

Moving all incoming messages over to use IWS instead of XAI is the product recommendation. However, to aid in implementations that have many integrations in place using the XAI inbound services that use the Core Adapter (or any adapter whose message class is BASEADA), the product provides the ability to deploy these types of XAI inbound services to the Java EE Web Application Server along with the Inbound Web Services.

To take advantage of this capability, you must define a feature configuration option. Under the External Messages feature configuration type, the Support XAI Services via IWS is used to indicate if this feature is supported. Setting the value to true turns on the feature. If no option is defined for that option type, it is equivalent to setting the value to false.

When the system is configured to support XAI services via IWS, the Inbound Web Service deployment includes XAI inbound services (that are configured with an Adapter that references the BASEADA message class). The deployment portal will also include a zone showing the deployment status of these XAI Inbound Services.

Configuring Inbound Web Service Options

This topic describes the configuration needed for using inbound web services.

Next in This Section

- Technical Configuration

- Maintaining Web Service Annotation Types

- Maintaining Web Service Annotations

- Maintaining Inbound Web Services

Technical Configuration

In order to use inbound web services, there are tasks a system administrator must perform.

Refer to the Server Administration Guide for technical details of each of these processes.

Maintaining Web Service Annotation Types

The product provides some base annotation types. Refer to the metadata for more information. If your implementation wishes to define additional annotation types, use the Web Service Annotation Type portal. Open this page using Admin > External Message > Web Service Annotation Type.

You are taken to the query portal where you can search for an existing web service annotation type. Once an annotation type is selected, you are brought to the maintenance portal to view and maintain the selected record.

Note: Use of custom policies should only be considered if the policies supplied by the Java EE Web Application Server are not sufficient for your implementation's needs.

CAUTION:

Important! When adding new records, carefully consider the naming convention of the web service annotation type code. Refer to System Data Naming Convention for more information.

The Web Service Annotation Type zone provides basic information about the web service annotation type.

Please see the zone's help text for information about this zone's fields.

The system supports the ability for an IWS record to refer to multiple policies. In this situation, the annotation type for the policy should include a reference to a parent annotation type so that the system can properly build the array of annotations.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_IWS_ANN_TYPE.

Maintaining Web Service Annotations

If your implementation wishes to define annotations, use the Web Service Annotation portal. Open this page using Admin > Integration > Web Service Annotation.

This is a standard All-in-One portal.

CAUTION:

Important! When adding new records, carefully consider the naming convention of the web service annotation code. Refer to System Data Naming Convention for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_IWS_ANN.

Maintaining Inbound Web Services

Inbound Web Services are used to define a specific message that your implementation will receive from an external system and provides configuration needed to process the inbound message.

The product provides several inbound web services out of the box. By default, no annotations are defined for the base inbound web services. You may modify the message options or the annotations for any base IWS record. In addition, you may define additional IWS records for other incoming messages supported by your implementation.

To view an inbound web service, navigate using Admin > Integration > Inbound Web Service. You are brought to a query portal with options for searching for inbound web services.

Once an inbound web service has been selected, you are brought to the maintenance portal to view and maintain the selected record.

CAUTION:

Important! When adding new records, carefully consider the naming convention of the inbound web service code. Refer to System Data Naming Convention for more information.

The Inbound Web Service zone displays the configuration information for the record, including its annotations, if applicable and its operations.

Note that in addition to standard actions available on this portal, there is also a special Add to Category button in the page action area. Click this button to link an inbound web service to one or more web service categories.

Deploying Web Services

This topic describes the configuration needed for using inbound web services.

Once an Inbound Web Service is defined it is not automatically available to the Web Service Clients to access the system. The Deployment Status and the Active flag (set to true) indicate whether a Web Service is available or not. The last step is to deploy the Inbound Web Services to the Java EE Web Application Server. This deployment phase has a number of steps that are automatically performed when a deployment is initiated:

- The Web Service files are generated and policies are attached.

- The WSDL is generated with appropriate annotations and enumerations.

- The necessary Java stub code to implement the Web Service in the Java EE Web Application Server is generated and compiled.

- The Web Services are built into a valid Web Application Archive (WAR) file.

- Optionally, the newly created Web Services WAR file is deployed to the Java EE Web Application Server. This can also be done manually for clustered deployments, if desired.

There are two methods available for deploying inbound web services:

- Deployment at the command line using the iwsdeploy[.sh] command as outlined in the Server Administration Guide. This method is recommended for native installations and production implementations.

- Deployment using the Inbound Web Service Deployment portal. This method is only supported in development (non-production) environments.

Inbound Web Service Deployment Portal

To use the online Inbound Web Service Deployment portal, navigate using Admin > Integration > Inbound Web Service Deployment.

The following sections describe the base zones that are provided on the portal.

Deploy Inbound Web Services

The Deploy Inbound Web Services zone provides information about the last deployment. If the region is a development (non-production) region you may use the Deploy button to deploy or re-deploy inbound web services. All inbound web services whose Active switch is Yes will be deployed. All whose active switch is No will be undeployed.

Note: When an Inbound Web Service is deployed, the value of its service revision field is captured. Certain changes to configuration will require re-deployment to take effect. When any of the following changes occur, the IWS service revision value is incremented. This will cause the deployment status to show Needs Deployment.

- Active switch is changed

- An Annotation is added or removed

- An Operation is added or removed.

- The Operation Name, Schema Type / Schema Name, Request or Response Schema, Request or Response XSL for an Operation is changed.

Note: In addition, if the implementation supports XAI services deployed through IWS, the appropriate XAI inbound services will also be deployed or undeployed as required.

Deployment Status

The Deployment Status zone displays a list of inbound web services in the product, including the deployment status.

The deployment status is determined by comparing the internal Service Revision field on each IWS against the value captured at the time of deployment.

- Deployed. Indicates that the IWS has been deployed and no changes have been detected to the configuration.

- Needs Deployment. Indicates that the IWS has never been deployed or has been deployed but in the meantime, changes have been detected to the configuration that require redeployment.

- Undeployed. Indicates that the IWS is marked as inactive and the IWS is not found to be deployed at this time.

- Needs Undeployment. Indicates that the IWS is marked as inactive but the IWS is found to be deployed at this time.

If the IWS has been deployed, the View column will include a WSDL link allowing you to launch a separate window to view the WSDL definition.

Use the broadcast button adjacent to any of the inbound web services listed in the zone to view the details of the IWS record. This causes the Inbound Web Service zone to appear. It is the same zone that appears on the Inbound Web Service maintenance portal.

XAI Inbound Service Deployment Status

The XAI Inbound Service Deployment Status zone is only visible if the feature configuration option Support XAI Services via IWS is configured on the External Messages feature type or if the system detects that there are XAI inbound services that have been deployed. (The latter condition is checked for the case where an implementation has XAI inbound services deployed and then chooses to discontinue using this functionality. After changing the feature configuration option to false, one more deployment is required to "undeploy" the XAI services.) The zone displays a list of XAI inbound services in the product that are related to page services. Refer to Deploying XAI Inbound Service via IWS for more information.

The deployment status is determined by comparing the record’s Version field against the value captured at the time of deployment.

- Deployed. Indicates that the XAI inbound service has been deployed and no changes have been detected to the configuration.

- Needs Deployment. Indicates that the XAI inbound service has not been deployed or has been deployed but in the meantime, changes have been detected to the configuration.

- Undeployed. Indicates that the XAI inbound service is marked as inactive or the Support XAI Services via IWS is not set to true and the XAI inbound service is not found to be deployed at this time.

- Needs Undeployment. Indicates that the XAI inbound service is marked as inactive or the Support XAI Services via IWS is not set to true but the XAI inbound service is found to be deployed at this time.

XAI inbound service does not have the equivalent of a Service Revision field that inbound web service has, which is only incremented when changes are made to the record that impact deployment. For XAI inbound service, the version number on the record is used. This field is incremented when any changes are made, even ones that may not impact deployment. As a result, some XAI Inbound Services may indicate "Needs Deployment" in cases where a redeployment may not be necessary. The recommendation when this occurs is to simply Deploy again to be safe.

If the IWS has been deployed, the View column will include a WSDL link allowing you to launch a separate window to view the WSDL definition.

Guaranteed Delivery

There are alternatives for sending messages to the system besides using inbound web services. An external system may be able to send messages to the system in a generic manner where a new web service does not need to be defined for every new type of message. These types of messages may provide a payload (the message) and the service script or business service to invoke. An example of this type of communication is a message sent from a mobile application using RESTful operations.

The external system may have no mechanism for retrying failed messages. For this situation, the product provides an algorithm that may be used to capture incoming messages that should ‘guarantee delivery’. A servlet processing this type of message may invoke the installation algorithm - Guaranteed Delivery, passing the details of the message and an indication if a response should be returned. The algorithm is responsible for storing the message information in a table so that it can be subsequently processed.

Note: The framework does not provide a sample algorithm for this plug-in spot. Your specific product may provide an algorithm and additional support for guaranteeing messages. Refer to your product documentation for more information.

Outgoing Messages

"Outgoing messages" is the term used to describe messages that are initiated by our system and sent to an external system. Messages may be sent real time or near real time. The system provides the following mechanisms for communicating messages to external systems.

- Outbound Messages. This method allows implementers to use configurable business objects to define the message format and to use scripts to build the message. If sent near real-time the message is posted to the outbound message table waiting for Oracle Service Bus to poll the records, apply the XSL and route the message. If sent real time, the message dispatcher routes the message immediately.

- Web Service Adapters. Using a web service adapter, an implementation can consume a WSDL from an external system and create an “adapter” record that references the URL of the external system and creates appropriate request and response data areas to expose the payload information in a format understood by configuration tools. A script may then be written to build the request information and initiate a real-time web service call from within the system.

- Send Email. The system supplies a dedicated business service that may be used to send an email real-time from within the application.

All these methods are described in more detail in the following sections.

Next in This Section

- Outbound Messages

- Web Service Adapters

- Sending Email

Outbound Messages

Outbound messages provide functionality for routing XML messages to an external system real-time or in near real time. In addition the functionality supports collecting related messages into a batch to then be sent to an external system as a consolidate XML message.

For each outbound message that your implementation must initiate you define a business object for the outbound message maintenance object. Using the business object's schema definition, you define the fields that make up the XML source field. These are the fields that make up the basis for the XML message (prior to any XSL transformation).

Each outbound message requires the definition of its schema by creating a business object whose schema describes the information that is provided to the external system. An XSL transformation may then be performed when routing the message to an external system.

For each external system that may receive this message, you configure the appropriate message XSL and routing information.

Because the outbound message type is associated with a business object, your implementation can easily create outbound message records from a script using the Invoke business object step type. Such a script would do the following:

- Determine the appropriate outbound message type and external system based on business rules

- Access the data needed to populate the message detail

- Populate the fields in the schema and use the Invoke business object script step type for the outbound message type's business object to store the outbound message.

- The resulting outbound message ID is returned to the script and the scriptwriter may choose to design a subsequent step to store that ID as an audit on the record that initiated this message.

The following topics provide more information about functionality supported by outbound messages.

Note: For implementations that continue to use MPL and XAI, there is additional functionality related to outbound messages. Refer to Outgoing Messages for more information.

Next in This Section

- Polling Outbound Messages Using OSB

- Batch Message Processing

- Real Time Messages

- Designing the System for Outbound Messages

- Configuring the System for Outbound Messages

- Managing Outbound Messages

Polling Outbound Messages Using OSB

If the outbound message that needs to be sent to an external system can be sent as an asynchronous message (in ‘near real time’), the process initiating the outbound message should create a record in the outbound message staging table. Oracle Service Bus (OSB), is the recommended tool to use to process outbound messages in near real-time.

Outbound messages that should be processed by OSB should be configured with a processing method defined as SOA for the external system / outbound message type. No other information is required for defining outbound message types that are processed by OSB.

For the OSB part of the processing, the product provides a custom transport: OUAF Outbound Message that may be used by an implementation to define messages to process and how to process them.

This section provides an overview of steps required to develop OSB integrations for outbound messages created by your product.

Before developing OSB integrations, a developer should be familiar with OSB development such as creating proxy services, business services, and message flow/routing. These terms are defined as follows:

Proxy Service: In OSB, a Proxy Service is the entity that processes a given type of message and routes it to a Business Service. A separate proxy service should be defined for each type of outbound message. If a given outbound message type may be routed to different external systems, it is the responsibility of the proxy service to query the external system defined on the outbound message and invoke the appropriate business service (see below). If any transformation is required prior to routing a message to a business service, it is the proxy service’s responsibility to perform the transformation.

Business Service: In OSB, a Business Service is an entity that receives a message from OSB and routes it to the appropriate destination. This should not be confused with the Business Service object provided in the product in the configuration tools.

Fastpath: Refer to the whitepaper OSB Integration for more information.

Batch Message Processing

Your implementation may be required to send messages to the same destination as a single XML file with multiple messages include. The following points describe this logic:

- The individual messages that should be grouped together must have a processing method of batch on the external system / outbound message type record. The appropriate batch code that is responsible for grouping the messages must also be provided.

- A separate "consolidated message" outbound message type should be configured for the external system with a processing method of SOA.

- When outbound message records are created for the individual messages, the batch code and current batch run number are stamped on the record.

- When the batch process runs it is responsible for building the XML file that is a collection of the individual messages. This batch process should include the following steps:

- Format appropriate header information for the collection of messages

- Apply the individual message XSL to each message before including the message

- Insert a new outbound message for the external system with the "consolidated message" outbound message type.

- The consolidated message is ready to be processed by Oracle Service Bus.

Note: No process provided. The system does not supply any sample batch job that does the above logic.

Real Time Messages

The system supports the ability to make web service calls, i.e. sending real time messages, to an external system.

The system supports special functionality for sending an Email message real-time. Refer to Sending Email for more information.

For other types of real-time messages, the system also uses outbound message type and external system configuration to format and route the message. When defining the configuration for real time messages, an additional step is required to define the mechanism for routing the message using a message sender. The system supports routing messages via HTTP and via JMS. Note that for HTTP routing, the system also supports sending the message using a JSON format.

Just like near real-time messages, initiating a real-time outbound message may also be done from a script. When a real time message is added, the system immediately routes it to the external system. If the external system provided a response message back, the system captures the response on the outbound message. If the outbound message type for the external system is associated with a response XSL it is applied to transform the response. In this case the system captures the raw response as well on the outbound message. Note that the outbound message BO should be configured to capture a response XML in its schema.

Any error (that can be trapped) causes the outbound message to be in a state of Error. It is the responsibility of the calling process to check upon the state of the outbound message and take a programmatic action. When the outbound message state is changed back to Pending the message will be retried.

The base package provides two business services: Outbound Message Dispatcher (F1-OutmsgDispatcher) and Outbound Message Mediator (F1-OutmsgMediator) that further facilitate making web service calls. Both business services are similar, allowing the calling script to configure the following behavior (with differences noted):

- Whether or not exceptions encountered while sending the message are trapped. Trapping errors allows the calling script to interrogate any errors encountered and take some other programmatic action.

- Whether or not the sent message is persisted as an actual outbound message record.

- If a persisted message is desired, the recommendation is to use the Outbound Message Dispatcher. This business service creates the message using standard BO processing, relying on the outbound message logic to route the message and store the record. The message is routed after the BO pre-processing algorithm and after the record is persisted but before the BO post-processing and audit plug-ins are executed.

- If the message should not be persisted, then the business service to choose depends on whether you rely on the BO pre-processing algorithm. As mentioned, the Outbound Message Dispatcher creates the outbound message record, relying on the outbound message logic to route the message. If it should not be persisted, it is subsequently deleted. In contrast the Outbound Message Mediator routes the message explicitly without creating a message record. It is more efficient for scenarios that don't require persistence. However, it should only be used if the pre-processing algorithm on the outbound message BO is needed. Note that the Outbound Message Mediator also supports persistence, but it does so by creating the records without using BO processing. This is not recommended. The Dispatcher is the better option if persistence is desired.

Refer to the descriptions of the two business services for more information.

Designing the System for Outbound Messages

The following sections describe the setup required when using outbound messages to communicate with an external system. The configuration walks you through the steps to configure a single external system and all its messages.

Next in This Section

- Define the Outbound Message Business Object and Type

- Real-Time Message Configuration

- Define the External System and Configure the Messages

- Outbound Message Schema Validation

Define the Outbound Message Business Object and Type

The product supplies many outbound message Business Objects along with Outbound Message Types for out of the box functionality.

In addition, implementations may need to define configuration for custom outbound messages. For each outbound message that must be sent to an external system, create a business object for the outbound message maintenance object. Using the business object's schema definition, your implementation defines the elements that make up the XML Source field (XML_SOURCE). These are the elements that are the basis for the XML message. XSL transformations may be applied to this XML source to produce the XML message.

If your integration is real-time and a response is expected, the Outbound Message business object should also map to the XML Response field (XML_RESPONSE).

- You may decide to capture the response as is and define the element as “raw”. For example

<responseDetail mapXML="XML_RESPONSE" type="raw"/>

In this scenario, a Response XSL may or may not be needed.

- Alternatively, if the details of the response are needed, you may define specific elements for the response. For this option, depending on how the integration is designed, a Response XSL may be needed to transform the response into the expected XML format.

Once you have your business object and schema, define an outbound message type for each unique outbound message.

Capturing the Outbound Message ID in the Message

If your integration would like to use the system generated Outbound Message ID as a unique identifier with the external system, the following configuration is needed:

- Define an element within the XML Source that should be populated with the system generated outbound message.

- Configure a BO Option on the outbound message’s business object using the Option Type Outbound Message ID XPath and set the Option Value to the XPath of the element defined to capture the ID.

Note: This functionality is only applicable if the outbound message is persisted.

Support for Dynamic URLs

The product supports the ability to build a dynamic URLs. These are cases where the URL requires information determined at runtime. This is supported with a combination of BO schema definition, URL configuration and appropriate code when creating the outbound message. The following points highlight the steps needed to support this functionality.

- When defining the Message Sender’s URL, use the syntax ${pathParms} in the location of the URL where runtime information must be inserted. For example: http://my.server.com:1000/rest/services/${pathParms}

- Include the data area F1-OM-DynamicConfig (Outbound message dynamic configuration) in the schema of the business object for the outbound message. This data area includes elements for pathParms and queryParms.

- In the code that creates the outbound message, populate the pathParms and if applicable queryParms elements with the appropriate information. The system will build the URL by plugging in the pathParms element value followed by a question mark, followed by the queryParms element value into the ${pathParms} location in the URL.

The following is an example of run time values.

<dynamicConfiguration>

<pathParms>job/1234</pathParms>

<queryParms>firstName=John&lastName=Doe</queryParms>

<dynamicConfigureation>

Add SOAP Header Parameters at Runtime

The product supports the ability to add SOAP header parameters to an external message at runtime. The following points highlight the steps needed to support this functionality.

- Include the data area F1-OM-DynamicConfig (Outbound message dynamic configuration) in the schema of the business object for the outbound message. This data area includes the element soapHeaders .

- In the code that creates the outbound message, populate the soapHeaders element with the self contained XML to add to the SOAP header section of the outgoing SOAP request.

Real-Time Message Configuration

When messages are routed to an external system real-time using the outbound message dispatcher or using the real-time send email business service. The system supports routing messages using HTTP and routing messages using JMS. In addition, there is a special type of message sender used for sending emails. The following sections highlights the supported real-time communication and the configuration needed for each.

Email Messages

For sending emails, the following configuration is needed:

- Define a message sender configured for email. Senders of this type should be configured with the RTEMAILSNDR class. The sender context is used to configure the connection information for the connecting to the SMTP server.

- This sender may be defined as the default email sender on the message option table. Alternatively, the message sender can be provided to the business service as input. Refer to Sending Email for more information.

Outbound Messages

For other outbound messages that are routed using the real-time outbound message dispatcher, a message sender must be configured to define how to route the message. The following points highlight more detail related to this configuration.

Determine the communication mechanism prior to configuring the sender.

- When routing the message using JMS, the following configuration must be defined

- Define an appropriate JNDI Server that indicates where the JMS resources are located.

- Define a JMS Connection to define additional configuration needed for the connection.

- Define the JMS Queue or JMS Topic to define the queue or topic to use.

- When communicating using a JSON format, determine the method to use to convert the XML to JSON. The desired method is driven by how the request should be sent.

- If choosing the Base JSON Conversion method, if XSL transformation needs to be applied prior to the conversion to JSON, then the target XML Request Schema must be defined (using a data area) so that the conversion logic knows the format of the XML it is converting. The XSL is applied to the outbound message’s XML Source, resulting in the defined XML Request Schema, which is then converted to JSON. If XSL transformation is not required, then the outbound message’s XML Source is converted to JSON.

- If the XML source on the outbound message can be converted to JSON using an XSL, then the XSL Transformation method may be chosen.

- You may also choose to convert the XML Source to JSON via the Standard API Conversion method (using a Jettison library). With this method, an XSL may optionally be provided. The conversion will be performed on the transformed XML.

- For the response, if the outbound message BO defines detailed elements for the XML Response field, then the JSON should be converted to this format. If your conversion method is Base JSON Conversion, then if the JSON response cannot be converted directly to the XML Response elements on the outbound message BO, then define a Response Schema (data area) that represents the results for the base JSON conversion. In addition, define an XSL that can transform the response from the converted XML to the XML format expected on the BO. If the conversion method is Standard API Conversion or XSL Transformation, the standard API is used to convert JSON to XML. An XSL may be defined to convert the response to the XML Response if needed.

- If the outbound message BO defines a "raw" element to capture the response, then a response schema and XSL are not necessary. In this case, the system will perform a JSON to XML conversion using the Standard API Conversion method (regardless of the conversion method defined) and the result is captured in the XML response.

- For HTTP senders including JSON senders, the system provides support for sending messages secured by OAuth authentication using Oracle Web Services Manager (OWSM). The system provides a pre-configured set of policies for OAuth (F1-OAUTH) using a special extendable lookup. Note that the values of this policy set defines a specific CSF key repository that the implementation should use for capturing its CSF keys. In addition, there is a substitution value defined for the token URI: @F1_OAUTH2_URI@. Configure the appropriate URI for this implementation as described in URI Substitution. By default the system does not support additional policy sets to be defined. If your implementation requires a different policy set, contact support.

Define a message sender configured for each appropriate routing method. The invocation type should be configured as Real-time. For routing via HTTP, use the RTHTTPSNDR - HTTP sender class. For routing via HTTP with SOAP format automatically applied, use the SOAPSNDR - HTTP SOAP sender class. For routing via HTTP using JSON format, use the RTJSONSNDR - JSON sender class. For routing via JMS, use the RTJMSQSNDR - JMS queue sender class or RTJMSTSNDR - JMS topic sender class and configure the JMS Connection and JMS Queue or JMS Topic. Use the sender context to configure the required values for connecting to the appropriate destination.

Note: Refer to Support for Dynamic URLs for configuration needed to support dynamic URLs when sending an outbound message. There is specific configuration expected when defining the URL on the Sender in order to support dynamic URLs.

Configure the external system / outbound message type collection. The processing method defined for the external system / outbound message type must be Real-time.

Define the External System and Configure the Messages

Define an external system and configure the valid outgoing messages and their method of communication (processing method). Refer to Outbound Messages for more information.

Outbound Message Schema Validation

The outbound messages that are generated by the system should be well formed and valid so that they do not cause any issues in the external system. To ensure this validity you may configure the system to validate messages before they are routed to their destination. Note that the validation is applied just before communication with the sender and therefore after any Request XSL has been applied.

- Define a directory where the valid W3C schemas are located using the Message option Outbound Message Schema Location.

- Each external system message must indicate the appropriate W3C schema to use for validation.

You may turn on or off this validation checking using the Message option Schema Validation Flag.

Configuring the System for Outbound Messages

The following sections describe the setup required when using outbound messages to communicate with an external system.

Next in This Section

- JNDI Server

- JMS Connection

- JMS Queue

- JMS Topic

- Message Sender

- Defining Outbound Message Types

- External Systems

- Message Option

JNDI Server

If using JMS to communicate outbound messages, define a new JNDI Server. Open Admin > Integration > JNDI Server.

Description of Page

Enter a unique JNDI Server and Description.

Indicate the Provider URL to indicate the location of the JNDI server. A variable may be used in place of all or part of the URL. The variable must be predefined in the substitution variable property file. The value here should enclose the variable name with @. Refer to Referencing URIs for more information.

Indicate the Initial Context Factory, which is a Java class name used by the JNDI server provider to create JNDI context objects.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_JNDI_SVR.

JMS Connection

To define a JMS Connection, open Admin > Integration > JMS Connection.

Description of Page

Enter a unique JMS Connection and Description.

Indicate the JNDI Server to be used. Refer to JNDI Server for more information.

Use the JNDI Connection Factory to indicate the lookup keyword in the JNDI server used to locate the JMS connection.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_JMS_CON.

JMS Queue

To define your JMS Queue values, open Admin > Integration > JMS Queue.

Description of Page

Enter a unique JMS Queue and Description.

Enter the Queue Name as defined in the JNDI server. This is the JNDI lookup name identifying the queue.

Use the Target Client Flag to indicate whether or not the target client is JMS or MQ.

Select the JNDI Server where the queue is defined. Refer to JNDI Server for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_JMS_Q.

JMS Topic

To define your JMS Topic values, open Admin > Integration > JMS Topic.

Description of Page

Enter a unique JMS Topic and Description.

Select the JNDI Server where the topic is defined. Refer to JNDI Server for more information.

Enter the Topic Name as defined in the JNDI server. This is the JNDI lookup name identifying the topic.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_JMS_TPC.

Message Sender

The topics in this section describe the maintenance of a message sender

Next in This Section

- Message Sender - Main

- Message Sender - Context

Message Sender - Main

To define a new sender, open Admin > Integration > Message Sender.

Description of Page

Enter a unique Message Sender and Description.

Set Invocation Type to Real-time.

Note: The invocation type MPL remains in the product for upgrade purposes but is not recommended.

Indicate the Message Class for this sender, which indicates the method used to route the message. The real-time sender classes are as follows:

Message Class

Description

RTEMAILSNDR

Email sender.

RTHTTPSNDR

HTTP sender.

RTJMSQSNDR

JMS queue sender.

RTJMSTSNDR

JMS topic sender.

RTJSONSNDR

HTTP JSON sender.

SOAPSNDR

HTTP SOAP sender.

The following sender classes are related to MPL processing and remain in the product for upgrade purposes:

Message Class

Description

DWNSTGSNDR

Download Staging sender.

EMAILSENDER

Email sender.

FLATFILESNDR

Flat file sender.

HTTPSNDR

HTTP sender.

JMSSENDER

JMS Queue sender.

OUTMSGSNDR

Outbound Message sender.

STGSENDER

Staging Upload sender.

TPCSNDR

JMS Topic sender.

UPLDERRHNDLR

Upload Error Handler.

Indicate whether or not this sender is currently Active.

Indicate whether the MSG Encoding is ANSI message encoding or UTF-8 message encoding.

If the Message Class is one that connects to a JMS Queue or JMS Topic, indicate the appropriate JMS Connection

Fastpath: Refer to JMS Connection for more information.

If the Message Class is one that connects to a JMS queue, indicate the name of the JMS Queue to define where the message is to be sent.

Fastpath: Refer to JMS Queue for more information.

If the Message Class is one that connects to a JMS topic, indicate the name of the JMS Topic to define where the message is to be sent.

Fastpath: Refer to JMS Topic for more information.

The XAI JDBC Connection remains for legacy purposes but is not applicable for supported functionality.

Message Sender - Context

The sender may require context information to define additional information needed by the system to successfully send outgoing messages. Open Admin > Integration > Message Sender and navigate to the Context page.

Description of Page

Define the Context Type and Context Value, which contain parameters for senders when more information is required. See below for the supported context values for different types of senders.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_SENDER.

Email Sender Context

The email sender is used by the business service that sends email messages real-time.

An email sender must point to the Message Class RTHTTPSNDR. In addition, the following context records should be defined for senders of this type.

Context Type

Description

SMTP Host name

The SMTP server host name.

SMTP Username

The user ID used to access the SMTP server.

SMTP Password

The password used to access the SMTP server.

Response Time Out

The amount of time the system should wait for a real time response.

HTTP Sender

An HTTP sender is one that sends messages to an HTTP server using the HTTP protocol. HTTP senders should reference a Message Class of RTHTTPSNDR, RTJSONSNDR or SOAPSNDR.

Various parameters are required to establish a session with the target HTTP server. You specify these parameters by defining a collection of context values for the sender. A set of context types related to HTTP variables is provided with the product. The following section describes the context types and where appropriate, indicates valid values.

Before defining the HTTP sender, you need to find out how the HTTP server on the other side expects to receive the request, and in particular, to answer the following questions:

- What is the address of the HTTP server?

- Is the HTTP server using a POST or GET HTTP method?

- If the server is using POST, how are message contents passed? Does it use an HTTP FORM or does it pass the data in the body of an XML message?

Context Type

Description

Values

HTTP URL1 - URL9

Used to construct the URL of the target HTTP server.

Since the URL may be long and complex, you can break it into smaller parts, each defined by a separate context record. The full URL is built by concatenating the values in URL1 through URL9.

You may use substitution variables when entering values for URL parts. Note that the substitution string @XMLMSG@ may be used for GET calls if an XSL has been applied to convert the message into HTTP GET parameters. It is useful if the HTTP Form is not applicable to the type of message.

Refer to Support for Dynamic URLs for configuration needed to support dynamic URLs when sending an outbound message.

HTTP Method

The HTTP method used to send the message.
Note: The SOAP sender message class SOAPSNDR only supports the POST method.

POST or GET

HTTP Transport Method

Specifies the type of the message. You can either send the message or send and wait for a response.

Send or sendReceive

HTTP Form Data

Used when the message is in the format of an HTML Form (Content-Type: application/x-www-form-urlencoded).

This context specifies the form parameters (data) that should be passed in the HTTP message. Since a form may have multiple parameters, you should add a context record for each form parameter.

The value of a form parameter takes the format of x=y where x is the form parameter name and y is its value.

If y contains the string @XMLMSG@ (case sensitive) then this string is replaced by the content of the service response XML message. The @XMLMSG@ string can be used in the HTTP Form Data or in the HTTP URL, but not in both.

If a context record of this type is defined for a sender, the sender uses the HTML Form message format to send the message even if @XMLMSG@ is not specified in one of the context records.

If a context record of this type is not defined for a sender, then the XML is sent with Content-Type: text/plain. When using POST it is put in the HTTP message body.

Always required when using the GET method. If you are using the GET method and do not specify a Form Data context record, no message is transferred to the HTTP server.

The MPL server builds formData by concatenating the individual parts.

You may use substitution variables when entering values for Form Data.

HTTP Login User

The HTTP server may require authentication. Add a context record of this type to specify the login user to use.

HTTP Login Password

The HTTP server may require authentication. Add a context record of this type to specify the login password to use.

HTTP Header

Sometimes the HTTP server on the other side may require the addition of HTTP headers to the message.

For each HTTP header that has to be specified you should add a context record with a value having the following format x:y where x is the header name and y is the value for the header

HTTP Time Out

Indicates the amount of time to wait for a connection to be established with the remote system.

Character Encoding

Indicates if the message should be encoded. The sender will add to the HTTP's content type header the string ;charset=x where x is the value of this context and when sending the message it will encode the data in that encoding.

UTF-8 or UTF-16

Response Time Out

The amount of time the system should wait for the remote system to send a response.

Sender Security Type

Indicate the desired security type to apply.

BASIC (HTTP Basic), TEXT (Username Token plain text), DIGEST - Username Token Digest, OWSM - OAuth Security via OWSM.

OWSM Policy Set

Applicable only if the Sender Security Type is OWSM. Defines the policy set to apply.

Enter a valid value for the extendable lookup Set of Policies (F1-SetOfPolicies). The product provides the value F1-OAUTH that may be used here.

Real-time HTTP Sender

The following context type is only applicable to senders with the RTHTTPSNDR message class.

Context Type

Description

Content Type

Populate a value here to override the Content-Type attribute in the HTTP header, which defaults to text/xml.

SOAP Sender

A SOAP sender is an HTTP sender that automatically adds support for the SOAP format. For this type of sender (message class of SOAPSNDR), besides the context values listed above, the following context entries may also be supplied.

Context Type

Description

Values

Message Namespace URI

Used to indicate a specific namespace to be included in messages for this sender. Note that this value is used only when the External Message link to this sender is configured with a Namespace Option of Configured on Sender.

SOAP Insert Timestamp

Indicate whether a timestamp should be added. Default value is 'N'.

Y or N

SOAP Expiration Delay (in seconds)

Indicate an expiration delay to add to the timestamp. The default value is 60.

Note: Refer to Add SOAP Header Parameters at Runtime for information about dynamically including SOAP Header parameters when sending a message.

JMS Sender

A JMS sender is one that sends messages to a JMS queue or JMS topic. JMS senders should reference a Message Class of RTJMSQSNDR or RTJMSTSNDR, respectively.

The following parameters are used to connect to the JMS resource.

Context Type

Description

Values

JMS Message Type (Bytes(Y)/Text(N)

Indicates whether the data is sent as a bytes message or as a text message.

Y or N

JMS User Name

Enter the user name to connect to the JMS resource.

JMS User Password

Enter the password to use to connect to the JMS resource.

JMS Header

If JMS header values are required for the message, use this context type.

For each JMS header that has to be specified, add a context record with a value having the following format x:y where x is the header name and y is the value.

Defining Outbound Message Types

Refer to Outbound Messages for an overview of this functionality.

Use this page to define basic information about an outbound message type. Open this page using Admin > Integration > Outbound Message Type. You are brought to a query portal with options for searching for outbound message types.

Note: This page is not available if the External Message module is turned off.

Once an outbound message type has been selected, you are brought to the maintenance portal to view and maintain the selected record.

The Outbound Message Type zone provides basic information about a business flag. Refer to the embedded help for more information.

The External System Links zone is visible if the outbound message type is linked to any external systems.

CAUTION:

Important! When adding new records, carefully consider the naming convention of the outbound message type code. Refer to System Data Naming Convention for more information.

Note that in addition to standard actions available on this portal, there is also a special Add to Category button in the page action area. Click this button to link an outbound message type to one or more web service categories.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_OUTMSG_TYPE.

External Systems

Use this page to define an external system and define the configuration for communication between your system and the external system.

Next in This Section

- External System - Main

- External System - Template Use

External System - Main

Open this page using Admin > Integration > External System.

Note: This page is not available if both the External Message and the Open Market Interchange modules are turned off.

Description of Page

Enter a unique External System and Description.

Use the field Our Name In Their System to specify the identity of your organization (i.e., your external system identifier) in the external system.

Note: The workflow process profile and notification download profile are only applicable to products that support workflow and notification. They and are not visible in the product if the Open Market Interchange module is turned off.

If this external system sends inbound communications through notification upload staging, the type of workflow process that is created is controlled by the sender's W/F (Workflow) Process Profile.

If you send notifications to this external system, select a Notification DL (download) Profile that is used to define the configuration of the outgoing messages.

Note: The remaining fields are not visible if the External Message module is turned off.

Set Usage to Template External System for external systems whose outbound message type configuration is inherited by other external systems.

If the outbound message type configuration should be inherited from a template external system, define the Template External System. If this field is specified, the outbound message type collection displays the data defined for the template system as display-only.

The Outbound Message Type accordion contains an entry for every type of outbound message defined for this external system. For each type of outbound message identify its Outbound Message Type.

Define the Processing Method for messages of this type. Valid values are Batch, Real-time, SOA and XAI.

Define an appropriate Message Sender if the processing method is XAI or Real-time.

Namespace Option is used when your message should include a namespace in the resulting XML. The valid option are Standard Namespace and Configured on Sender. If the value is Standard Namespace, the system will generate a namespace for the resulting WSDL with the following value: http://ouaf.oracle.com/outbound/AAA_BBB, where AAA is the external system code and BBB is the outbound message type code. If the value is Configured on Sender, then the value of the namespace is taken from the sender context with context type Message Namespace URI.

Define an appropriate Batch Control if the processing method is Batch.

If the message sender is one with a message class of RTJSONSNDR, indicate the JSON Conversion Method. The valid values are Base JSON Conversion, Standard API Conversion and XSL Transformation. Refer to Real Time Message Configuration for more information about these methods and the additional configuration that may be applicable.

If the JSON Conversion Method is Base JSON Conversion, the Request Schema is enabled. Populate a data area that defines the schema for the XML format to convert the outbound message’s BO schema to prior to performing the JSON conversion. Refer to Real Time Message Configuration for more information.

The Message XSL is the schema used to transform information from the format produced by the system to a format understood by the sender, who receives a message of this type. This is not applicable for Processing Method of SOA.

Enter the file name of the appropriate W3C Schema if you want to validate the message built for outbound messages for this external system / outbound message type prior to being routed to their destination. Refer to Outbound Message Schema Validation for more information. This is not applicable for Processing Method of SOA.

If the JSON Conversion Method is Base JSON Conversion, the Response Schema is enabled. Populate a data area that defines the schema for the XML format that the JSON message is initially converted to. The XML is then converted to BO XML. Refer to Real Time Message Configuration for more information.

Response XSL will have the same search service as is used for the existing Message XSL field. This field will only be displayed when the processing method is Real-time. Refer to Real Time Messages for more information on how it is used.

External System - Template Use

If you are viewing an external system whose usage is a Template External System, use this page to view the other external systems that reference this one. Open this page using Admin > Integration > External System and then navigate to the Template Use tab.

Description of Page

The tree shows every external system that references this external system as its template.

Message Option

The Message Option page defines various system settings used by the system when processing external messages.

To define options for your environment, open Admin > Integration > Message Option.

Description of Page

The following options are supported.

Option

Description

MPL / XAI Option Name

Default Email Sender

This is the default Message Sender used for sending e-mails when no explicit Message Sender is specified.

defaultEmailSender

Default User

The default user is used by XAI to access your product when no other user is explicitly specified. Refer to Server Security for more information. Additionally, the Default User is used for MPL transactions where there is no facility to provide a User ID. For example, no facility exists to provide a user id when reading messages from a JMS Queue. In these messaging scenarios, the system will use the Default User for authorization purposes.

defaultUser

Email Attachment File Location

This is the default location of e-mail attachment files. If not specified, the e-mail service provided with the product assumes a full path is provided with each attachment file.

emailAttachmentFileLocation

Email XSL File Location

This is the default location of e-mail XSL files. If not specified, the e-mail service provided with the product assumes a full path is provided to an XSL file as part of an e-mail request.

emailXSLFileLocation

Messages Language

The default language to use for the messages.

language

Outbound Message Schema Location

Enter the full path of the virtual directory where valid W3C schemas are stored if your implementation wants to validate outbound message schemas. For example: http:/localhost/cisxai/schemas.

xaiOuboundSchemaLoc

Schema Validation Flag

Enter Y to turn on schema validation for outbound messages. Enter N to turn this off.

xaiSchemaValidationCheck

To Do Type for Inbound JMS Message Errors

To Do type for inbound JMS message errors. The inbound message processor uses this To Do type when creating To Do entries for inbound JMS messages that cannot be successfully processed. The system provides the To Do type F1-INJMS that may be used here.

toDoTypeforInboundJMSMessageErrors

To Do Type for Outbound Message Errors

To Do type for outbound message errors. The outbound message receiver uses this To Do type when creating To Do entries for outbound messages that cannot be successfully processed. The system provides the To Do type F1-OUTMS that may be used here.

outboundErrorTodo

Note that the following options are only applicable to implementations still using the XAI and MPL servers. The settings here may be overridden by the AdHoc Parameters section of the XAIParameterInfo.xml or MPLParameterInfo.xml.

Option

Description

MPL / XAI Option Name

Automatically Attempt Resend to Unavailable Sender (Y/N)

Set to Y if you wish to enable Automatic Resend. Set to N if you wish to log errors when the system fails to send an outgoing message.

shouldAutoResend

Default Response Character Encoding

Determines the character encoding to be used when a response is sent. For example, you may specify UTF-8 or UTF-16. If no value is specified then the default is UTF-8. If no special encoding should be done, then enter the value none.

defaultResponseEncoding

JDBC Connection Pool Max size

The MPL uses a pool of JDBC connections to connect to the database. This option determines the maximum number of JDBC connections that can be opened in the pool. The default value is 100.

JDBCConnPoolMaxSize

Maximum Errors for a Sender

This value is required if you have enabled Automatic Resend. It defines how many errors you receive from a sender when attempting to send an outgoing message before you mark the sender unavailable.

maxSendingErrors

Messages JDBC Connection

Specifies the JDBC connection that XAI uses to read the text for its messages.

messagesJDBCConnection

MPL Administrator Port

The port number to be used for receiving MPL operator commands.

adminPort

MPL HTTP Server Authentication Method

This setting, along with the MPL HTTP Server User and Password are used to secure commands received by your MPL (such as those issued via XAI Command) through HTTP. Currently only BASIC authentication is supported.

MPLHTTPAuthMethod

MPL HTTP Server Password

This setting, along with the MPL HTTP Server Authentication Method and User are used to secure commands received by your MPL (such as those issued via XAI Command) through HTTP. The password should be in encrypted form, using the same encryption that is used for the database password. .

MPLHTTPAuthPassword

MPL HTTP Server User

This setting, along with the MPL HTTP Server Authentication Method and Password are used to secure commands received by your MPL (such as those issued via XAI Command ) through HTTP.

MPLHTTPAuthUser

MPL Log File

The MPL Log File setting is used to specify the name of the file where MPL log information is to be written. The log contains technical information about the operation of the MPL.

MPLLogFile

MPL Trace File

The MPL Trace File setting is used to specify the name of the file where MPL trace information is to be written.

MPLTraceFile

MPL Trace Type

The MPL Trace Type is used to enable or disable tracing of the MPL. The possible values are FULL- All trace messages are written to the log file and NOLOG- No information is written to the log file.

MPLTraceType

Privileged Users

Comma separated list of users that are allowed to specify an effective User or effective User Id via framework custom SOAP Headers.

superUsers

Records MPL Receiver Will Process At a Time

If your implementation has configured multiple MPL servers, indicate the number of records that each MPL receiver should process.

Not currently used

Schema Directory

The full path of the virtual directory where XML schemas are stored. For example: http:/localhost/cisxai/schemas. If this option is not specified, the XAI uses the current directory, from where it is being run, to locate schemas.

schemaDir

Send SOAP Fault as HTTP 500

Enter Y to ensure that a SOAP error is reported as an HTTP 500 "internal server error".

sendErrorAsHttp500

Sender Retry Seconds

This value is required if you have enabled Automatic Resend. It defines how many seconds to wait after marking a sender unavailable before you mark the sender available again (and retry sending messages to it).

senderWaitTime

System Error JDBC Connection

When a request fails to execute due to a system error, the MPL retries its execution several times. The MPL registers the system error in a table and uses this table for the retries. This setting specifies the JDBC connection required to access this table. Only enter a value in this field if it is different from the database environment used to read the XAI registry.

systemErrorTableJDBCConnection

System Error Max Retry

When a request fails to execute due to a system error, the MPL retries its execution several times until a maximum number of retries is reached. This option specifies the maximum number of retries.

systemErrorMaxRetries

System Error Retry Interval

When a request fails to execute due to a system error, the MPL retries its execution several times. This option specifies the number of seconds the MPL server waits between retries.

systemErrorRetryInterval

Thread Pool Initial Size

The MPL uses a thread of pools to enhance performance. The MPL starts with a minimum number of threads and grows/shrinks the pool based on the MPL system load. This option specifies the initial number of threads in the thread pool. The minimum number of threads is 12.

threadPoolInitialSize

Thread Pool Max Size

This option specifies the maximum number of threads in the thread pool.

threadPoolMaxSize

Thread Pool Non Activity Time

This option specifies how long a thread in the pool may be inactive before it is timed out and released from the pool.

poolNoneActivityTime

WSDL Service Address Location

Specifies the SOAP address location that XAI uses in creating a WSDL. If no value is present, the XAI's URL is used.

wsdlAddressLocation

XAI Authentication Password

The multi-purpose listener uses this field in combination with the XAI Authentication User when attempting to communicate with the XAI server over HTTP, which is running on a secured servlet and requires authentication.

HTTPBasicAuthPassword

XAI Authentication User

The multi-purpose listener uses this field in combination with the XAI Authentication Password when attempting to communicate with the XAI server over HTTP, which is running on a secured servlet and requires authentication.

HTTPBasicAuthUser

XAI Trace File

The full path name for the file, where the XML messages should be written. For example: c:\inetpub\wwwroot\cisxai\xai.log.

traceFile

XAI Trace Type

Use this option to specify the level of logging. The possible values are FULL - All XML messages are written to the log file and NOLOG - No information is written to the log file.

Fastpath: Refer to Server Trace for more information about tracing.

traceType

XSD Compliance

XSD does not allow empty elements for xsd:dateTime, xsd:date, and xsd:time. Request documents should specify xsi:nil="true" attribute on dateTime elements with an empty value. Enter xsd:permissive if you wish to enable noncompliant behavior to allow empty elements without xsi:nil="true". Enter xsd:strict if it is desired to enforce strict compliance on dateTime, date, and time elements. The default value is xsd:strict.

xsdCompliance

XSL Directory

The full path of the virtual directory where XSL transformation scripts are located. XSL transformation scripts can be defined for each service. By default, this is the same directory as the schemas directory.

XSLDir

Managing Outbound Messages

Use this page to view information about outbound messages.

Next in This Section

- Outbound Message - Main

- Outbound Message - Message

- Outbound Message - Response

Outbound Message - Main

Open this page using Menu > Integration > Outbound Message.

Description of Page

Outbound Message ID is the system-assigned unique identifier of the outbound message. These values only appear after the outbound message is added to the database.

The Processing Method indicates whether this record will be processed by a Batch extract process, through the XAI tool or Real-time. The value defined on the external system / outbound message type collection populates this value.

When records are created with a processing method of Batch, the system sets Extract to Can Be Extracted. Change the value to Not to be extracted if there is some reason that processing should be held for this record.

For records with a processing method of Batch, Batch Control indicates the process that will extract this record. This value is populated based on the on the external system / outbound message type's value. Batch Number indicates in which batch run this record was extracted or will be extracted.

The Retry Count is used by the XAI tool to keep track of how many times the tool tried to process this record and could not process the record, resulting in an error.

The Creation Date indicates the date that this record was created.

If the processing method is XAI, Status defines the state of the outbound message record. Refer to Lifecycle of Outbound Message for more information.

For messages in error status, click Pending to change the status back to pending for reprocessing.

For messages in pending, error, or in progress status, click Cancel to cancel the message and prevent further processing.

Outbound Message - Message

Use this page to view the XML source used to build an outbound message. Open this page using Menu > Integration > Outbound Message and then navigate to the Message tab.

Description of Page

The XML Source is displayed.

If a message XSL is defined on the external system / outbound message type record linked to this outbound message, the Show XML button is enabled. Click this button to view the XML that is a result of applying the Message XSL to the XML source.

Outbound Message - Response

Use this page to display the XML response. Open this page using Menu > Integration > Outbound Message and then navigate to the Response tab.

Description of Page

The XML Response and optionally the XML Raw Response is displayed.

XML Response displays the response data from the system called by the real-time message. If a response XSL is defined on the external system / outbound message type record linked to this outbound message, a transform is performed and the XML Raw Response displays the original, unchanged response.

Web Service Adapters

The base product provides a configuration object called Web Service Adapter that is used to help build configuration objects to allow for functionality in the system to initiate a web service call from within the system. A Web Service Adapter provides the following functionality:

- WSDL (web service description language) import. An implementer can use the WSDL import functionality to read the details of a WSDL into the system

- Internal API generation. The system generates internal data areas that have two main purposes: they provide the API for custom code to define the appropriate input and they provide output data for the web service call using Oracle Utilities Application Framework schema language. In addition, the web service dispatcher uses element mapping defined in the data areas to transform the internal XML into the structure expected by the external system as described in the WSDL.

- Defines the URL needed to perform the web service call at runtime.

Next in This Section

- Understanding Web Service Adapters

- Setting Up Web Service Adapters

Understanding Web Service Adapters

The following topics describe the system functionality in more detail.

Importing a WSDL

Configuring a Web Service Adapter starts by identifying the WSDL (the web service description language document used to define the interface) that will be provided by the external system. The following steps describe the base product functionality provided to allow a user to import a WSDL.

- Navigate to the Web Service Adapter page in add mode and select the appropriate base business object.

- Enter a meaningful Web Service Name and appropriate descriptions.

- Provide the URL of the given WSDL.

- Click Import to retrieve the details of the WSDL. The system then parses the WSDL details and populates the WSDL Service Name, WSDL Source, WSDL Port, URL and a list of Operations (methods) defined in the WSDL.

- Determine which Operations should be active based on the business requirements for invoking this web service. Active operations are those that the implementation is planning to invoke from the system. These require appropriate request and response data areas generated for them. The following section provides more information about that.

- Specify the appropriate Security Type to configure the type of security to use when invoking this web service.

- Click Save.

At this point, a web service adapter record is created in pending status. The next step is to generate the request and response data areas for the operations configured as active.

Generating Request and Response Data Areas

Each active operation for the web service adapter requires a pair of data areas, request and response, that represent the request and response XML messages for the operation.

The base product provides steps to generate the data areas as follows:

- As described in the Importing a WSDL section above, the operations listed in the WSDL are generated for the web service adapter and the implementer should indicate which operation to activate.

- After saving the pending web service adapter, the display lists all the active operations and for each one includes a Generate button.

- After clicking Generate for an operation, a window appears where the names of the new Request and Response Data Areas may be defined. Click Save to generate the data areas.

The generated data areas provide the API for the implementer to use when implementing the web service call in an appropriate algorithm or service in the system. The data areas contain the appropriate mapping from the elements that the implementer works within the code that invokes the web services and the WSDL definitions.

To facilitate generating the request and response data areas, the base product invokes a special business service used to create the appropriate mapping. The business service is defined as a BO option on the Web Service Adapter business object. This allows an implementation to provide a custom business service to further enhance the request and response mapping where appropriate.

Note:

Generated data areas. It is possible to edit and modify the generated data areas after they are created. An implementer can change element names or remove unneeded elements if desired. Manually changing the generated data areas must be done only when absolutely necessary. This is because the system is not able to validate manual changes and issues with the data areas would only be detected at run time.

Activating Web Service Adapters

The business objects provided by the base package for web service adapters include a simple lifecycle of Pending and Active. Configure the web service adapter and its data areas while in Pending status and activate it when it is ready to be implemented in the appropriate system functionality.

Invoking Web Services

To make a call to a web service using a web service adapter, the system has provided a Web Service Dispatcher business service (F1-InvokeWebService) to submit a web service call. The calling program is responsible for retrieving all the information to correctly populate the request data required by the web service call before invoking the business service.

Note:

Refer to the detailed description of the business service for more information.

Limitations

The following points highlight limitations associated with the types of web services that the system supports:

- It is possible for one WSDL document to contain definitions for several web services. The system currently supports only one port or service per WSDL document.

- It is possible for a WSDL to support multiple message patterns. The system currently supports only request / response.

Setting Up Web Service Adapters

Use the Web Service Adapter portal to define the configuration needed to communicate with an external system using a web service call. Open this page using Admin > Integration > Web Service Adapter. You are brought to a query portal with options for searching for web service adapters.

Once a web service adapter has been selected, you are brought to the maintenance portal to view and maintain the selected record.

The Web Service Adapter zone provides basic information about the web service annotation type.

Please see the zone's help text for information about this zone's fields.

Fastpath: Refer to Understanding Web Service Adapters for information about common web service adapter functionality.

Sending Email

The framework provides the ability to initiate an email from within the system. The following topics highlight the functionality available.

- Sending email “real time” using a specific business service. The framework provides a business service F1–EmailService that supports sending an email. The schema supports elements for all the information required to create an email real time. It also supports sending attachments. The SMTP information (host, user name and password) may be provided or may be defined on a message sender, that may be provided as input. In addition, the business service supports using a default message sender defined as a message option. Review the business service schema for information about the input elements.

Note: Validating attachments. If a Validate Email Attachment algorithm is plugged into the installation record, it is called to validate the attachments supplied, if applicable.

Note: Retry setting. An option in the system properties file allows your implementation to configure the number of times to retry (if any) if the SMTP server is unavailable. Refer to the server administration guide for more information.

- Using an outbound message to send an email. This option allows for different variations as described in Outbound Messages.

- Some emails may be created en masse (for example a large group of emails routed to users for a given set of To Do entries). In this case, the records can be created in the staging table for processing using OSB.

- Messages may still be sent real time using one of two business services described in Real Time Messages. This option is an alternative to the dedicated email service described above when aspects of the outbound message functionality are needed, such as the ability to instantiate a record as an audit or to include additional logic via BO plug-ins as part of sending the email.

Web Service Category

The product provides the ability to categorize web services that are defined in the system. The term web services refers to Outbound Message Types, Inbound Web Services, and for those implementations where they are applicable, XAI Inbound Services.

A given web service may be linked to more than one category. The product supplies web service categories and most base delivered web services are configured with appropriate categories. Implementations may define new categories and may link custom web services to base delivered categories or to custom categories. In addition, implementations may link additional categories to base delivered web services. However, implementations may not remove base delivered web services from base delivered categories.

If your implementation uses the Integration Cloud Service Catalog, the integration provides the categories for each web service that is sent to the catalog.

The web service category portal supports adding and removing web services from the category. In addition, the Outbound Message Type portal and Inbound Web Service portal each provide a page action button to Add to Category.

Next in This Section

- Defining Web Service Categories

Defining Web Service Categories

Refer to Web Service Category for an overview of this functionality.

Use this page to define basic information about a web service category. Open this page using Admin > Integration > Web Service Category. You are brought to a query portal with options for searching for web service categories.

Note: This page is not available if the External Message module is turned off.

Once a web service category has been selected, you are brought to the maintenance portal to view and maintain the selected record.

The Web Service Category zone provides basic information about a web service category.

CAUTION:

Important! When adding new records, carefully consider the naming convention of the web service category code. Refer to System Data Naming Convention for more information.

Once a web service category exists, an Add Web Services zone is provided to find and select web services to link to the web service category.

When viewing a category that already has web services linked to it, they are visible in the zone Included Web Services . This zone allows a user to remove a customer owned web service from the list.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_WEB_CAT.

JMS Message Browser

The JMS Message Browser portal allows you to select a JMS queue and view messages currently in the queue.

In order for a JMS queue to be available on the portal, a message sender must be defined that is configured for the appropriate JMS queue with the credentials to connect to the queue.

- If your organization sends real-time outgoing messages to a JMS queue, this configuration would exist as per the details in Real-Time Message Configuration.

- If inbound web service messages are routed to the system via a JMS queue, no configuration is needed in the system. However, if you would like to view the messages in the queue in the JMS message browser portal, configuration for the JMS queues as described for outgoing messages is required.

Navigate to the portal using Main > Integration > JMS Message Browser.

The JMS Senders zone provides a list of configured message senders eligible for selection.

The JMS Message List zone is visible for the JMS Sender broadcast from the first zone. This zone supports selecting one or more records to delete from the queue. Use the message selector to limit the results to messages that satisfy the message selector. This uses standard JMS API message selector functionality. Refer to the zone embedded help for information about the supported syntax.

The JMS Message Details zone displays a message broadcast from the list zone.

Integration Cloud Service Catalog

Integration Cloud Service (ICS) is an offering that serves as integration infrastructure for Oracle cloud solutions. The product provides an adapter for ICS to streamline integration between your edge application and ICS.

ICS Adapter

The product provides a web service that ICS can invoke (referred to here as the ICS adapter) to retrieve information about available web services supported by one or more edge products. The information retrieved by the adapter includes the name, the source system, the WSDL location and namespace.

It is possible that not every web service supported by an edge product is managed by ICS. In order to only include the appropriate web services in the ICS adapter, configuration is needed to identify which web services to include.

The web service catalog is used to identify the records that should be retrieved by the adapter:

- For inbound messages, the system supports both the use of inbound web services and XAI inbound services that are deployed via IWS. Each IWS or XAI inbound service that should be included in the catalog must be flagged. Note that only deployed services are returned to the catalogue.

- For outbound message, the system requires the creation of an External System that includes each outbound message type that the external system receives. For outbound messages that are integrated through ICS, the external system itself will represent ICS. Rather than identifying each outbound message type to include in the catalog, only the external system needs to be flagged. The ICS adapter will return web service information for all the outbound message types configured for the external system.

Fastpath: Refer to Maintaining the Web Service Catalog for more information.

Master and Subordinate Catalogs

For installations that support multiple edge products, each with their own list of web services, the system includes functionality to allow ICS to make one call to the adapter and receive all the services for all the products. This is handled by nominating one of the edge products as the "master". The "master" receives the ICS adapter request and this product includes configuration for how to connect to the other products to gather their web service catalog information and merge it with its own web services.

Next in This Section

- Web Service Catalog Configuration

Web Service Catalog Configuration

The topics in this section describe the configuration needed in your edge application to integrate with ICS.

Next in This Section

- Web Service Catalog Master Configuration

- Maintaining the Web Service Catalog

Web Service Catalog Master Configuration

The Service Catalog Configuration (master configuration) record defines several system wide settings related to integrating with the service catalog.

It includes configuration for the WSDL base URL. Note that this element supports the functionality described in Referencing URIs.

This includes defining subordinate servers if the current product is considered the "master". The record supports encrypting the subordinate server password. To do this, additional configuration is required. You need to define an entry in the 'encryption' feature configuration referencing USER_PASSWORD in the field= setting and ENCR_USER_PASSWORD in the encryptedField= setting. Refer to Application Encryption for more information and for additional configuration needed.

For more information about specific fields in the master configuration, refer to the embedded help.

Maintaining the Web Service Catalog

Refer to Integration Cloud Service Catalog for an overview of web service catalog functionality.

To add or remove services that are reported to the ICS catalog, navigate to the portal using Admin > Integration > Web Service Catalog.

The Catalog zone provides a list of services that are currently in the catalog. Users may use this zone to remove services from the catalog.

The Candidate Services zone provides a list of external systems, inbound web services and XAI inbound services (if applicable) that are not currently linked to the catalog. Users may use this zone to add services to the catalog.

Note: For inbound web services and XAI inbound services, they may be selected for the catalogue at any time. However, only deployed services are returned to the catalogue by the ICS adapter.

Mobile Remote Messages

This section provides information about the functionality supporting a message exchange with a mobile application.

Next in This Section

- About Remote Messages

- Maintaining Remote Messages

About Remote Messages

Remote messages are used to send data to and from a mobile device. This section describes the mechanism that allows the main application to send and receive messages to a mobile device.

Next in This Section

- Messages From A Mobile Device

- Messages To A Mobile Device

Messages From A Mobile Device

Asynchronous messages from the field may be received continually throughout the day. The processing of such messages ensures against data loss by saving the message before processing it. This approach guarantees message delivery despite of potential processing errors. Refer to Guaranteed Delivery for more information.

If message processing fails at any time, a To Do entry is created for a user to review and resolve the problem. You can view the content of any message, try to reprocess the message as is, or edit the message content and then reprocess.

Some errors may arise due to a temporary situation and may resolve on their own when the system tries to process the erroneous message again by the remote message monitor batch process.

Note: It is important to schedule the Remote Message Monitor batch process to retry failed messages periodically. Refer to F1-RMMSG batch control for more information.

Messages To A Mobile Device

Depending on your mobile application requirements, certain business events triggered by the main application may need to be communicated to a mobile user’s specific mobile device.

The payload and rules associated with such message are defined using a Message To Device mobile component. You may use the Add Message To Device (F1-AddMessageToDevice) business service to post a message to be processed by a mobile device. Refer to the description of this business service for more information.

The mobile device periodically polls for queued messages and process them in the order they were posted. You may configure an expiry time on the message’s mobile component. If specified, messages of this type that have not been picked up by the specified time are automatically discarded by the remote message monitor batch program.

Note: It is important to schedule the Remote Message Monitor batch process to expire messages and finalize the state of processed messages. Refer to F1-RMMSG batch control for more information.

Maintaining Remote Messages

This portal is used to view a messages sent to and from a mobile device.

Refer to About Remote Messages for more information.

You can access this portal from the Main > Integration > Mobile Remote Message. You are brought to a query portal with options for searching for a specific remote message. Once a remote message has been selected, you are brought to the maintenance portal to view and maintain the selected record.

The Remote Message zone on the portal's Main tab page provides information about the remote message, including the various maintenance actions applicable to its current state.

XML Application Integration

This section describes the XML Application Integration (XAI) utility, which enables you to configure your system to receive information from and to send information to external applications using Extensible Markup Language (XML) documents.

Note: The XAI functionality is legacy functionality and not recommended for new implementations. The topics for the functionality outlined in the previous sections describe the recommended features for supporting sending and receiving external messages. The XAI information remains in the documentation for upgrade purposes.

Next in This Section

- The Big Picture of XAI

- Designing Your XAI Environment

- Schema Editor

- Setting Up Your XAI Environment

- Running Your XAI Environment

- Maintaining Your XAI Environment

The Big Picture of XAI

The XML Application Integration (XAI) module provides the tools and infrastructure that businesses require for integrating their applications with your product. The integration your product with other systems across organizational boundaries or business is made possible, regardless of the platforms or operating system used. XAI provides an integration platform that enables the following:

- Integrate with Customer Relationship Management (CRM) systems

- Provide information feeds for web based customer portals

- Fit seamlessly with web based applications

- Facilitate fast implementation of batch interfaces

- Integrate with other XML compliant enterprise applications

XAI exposes system business objects as a set of XML based web services. The service can be invoked via different methods, e.g., Hypertext Transfer Protocol (HTTP) or Java Message Service (JMS). Consequently, any application or tool that can send and receive XML documents can now access the rich set of system business objects. Business-to-Business (B2B) or Business-to-Consumer (B2C) integration with other enterprise applications as well as the setup of web portals is made very simple and straightforward.

Next in This Section

- XAI Architecture

- XML Background Topics

- Inbound Messages

- Outgoing Messages

XAI Architecture

The XAI architecture contains 3 major components:

- The Core Server Component

- The Multi Purpose Listener (MPL)

- The Client Component

Next in This Section

- The Core Server Component

- The Multi Purpose Listener (MPL)

- The XAI Client Component

The Core Server Component

The core server component is responsible for receiving XML requests, executing the service and returning the response to the requester.

The following diagram shows the XAI tool operating on a web server and providing integration between the system business objects and various external applications.

The core is built in Java, using a layered, scalable architecture. The basic transport protocol supported by the core is SOAP/HTTP.

Fastpath: Refer to SOAP for more information.

The XAI core server provides a Java servlet to process requests through HTTP. You may also use other messaging mechanisms such as message queuing, publish/subscribe or a staging table. The multi-purpose listener processes the messages.

The Multi Purpose Listener (MPL)

Note: Multi Purpose Listener functionality is legacy functionality that is not recommended going forward. The Oracle Service Bus (OSB) is the recommended tool. This section remains in place for upgrade purposes.

The Multi Purpose Listener (MPL) is a multi-threaded Java server that constantly reads XML requests from various external and internal data sources, such as a Java Message Service (JMS) message queue, a JMS topic or system staging tables.

The MPL can be used to process inbound messages (those sent by an external application to invoke a system service), or outgoing messages (those sent by your product to external applications). The MPL uses different receivers to process messages from different data sources.

A receiver is implemented using 3 distinct layers:

- The Receiving Layer

- The Execution Layer

- The Response Layer

Next in This Section

- The Receiving Layer

- The Execution Layer

- The Response Layer

The Receiving Layer

This layer deals with polling various locations to determine if new records, files or incoming requests exist. The various locations include:

- Staging tables, including XAI staging control, XAI upload staging, notification download staging (certain products only), and outbound message.

- An external directory that contains a file, for example a comma delimited file or an XML file.

- A JMS queue/topic.

A separate receiver is defined to read requests from each of these locations. When the MPL server starts, it looks for all defined active receivers in the XAI Receiver table, and for each receiver it starts a thread that constantly fetches messages from the message source.

Once a request message is read, it is passed to an execution thread that implements the execution layer. Each receiver references an Executer that is responsible for executing the request.

Next in This Section

- Configuring Multiple MPL Servers

Configuring Multiple MPL Servers

A single MPL server may only run one of each of the above staging table receivers for a given JDBC connection. To enhance the performance of the processing of the staging tables, you may define multiple MPL servers where each one runs the active receivers defined in the receiver table.

To ensure that each staging table receiver processes its own set of records in the staging table, the receiver selects a set number of records (specified as Message option Number of Records an MPL Receiver Will Process At a Time) and marks those records with the IP address and port number of the MPL.

The Execution Layer

The execution layer sends the XML request to the XAI core server and waits for a response.

Note: Currently the only type of executer supported is the XAI servlet running either on an XAI server or locally under the MPL. However the architecture allows for executing a request on other execution environments.

The executer is invoked and is passed in an XAI Inbound Service that specifies an XML request schema and an adapter. Adapters tell XAI what to do with a request. The adapters point to a specific Java class that renders a service.

For example you can configure an Adapter to invoke any published application object (by pointing it to the appropriate java class). This adapter accesses system objects through the page service. You can think of an adapter as a plug-in component.

Once the executer processes the request and a response is received, it is transferred to the next layer, the response layer.

The Response Layer

The response layer is responsible for "responding" to the execution. The responses are handled by invoking an appropriate sender defined on the receiver's response information. Each sender defined in the system knows how to process its response. For example:

- The JMS queue sender and the JMS topic sender post responses to the appropriate queue / topic.

- The staging control sender handles errors received during the execution of the staging control request.

- The upload staging sender updates the status of the upload staging record based on the success or failure of the staging upload request.

- The download staging sender is a bit unusual because it is helping to build the message being sent (Oracle Customer Care and Billing only).

Note: There are some cases where a response is not applicable. For example, the file scan receiver creates a staging control record to process a file that exists in a directory. There is no "response" applicable for executing this request.

The XAI Client Component

The XAI Client component is the set of online control tables and tools used to manage your XAI environment.

The Schema Editor is a tool used to create and maintain XAI schemas.

Fastpath: Refer to XAI Schema for more information.

The Registry is a term used to refer to all the tables required to "register" a service in the system. It includes the XAI Inbound Service and a set of control tables defining various options.

The Trace Viewer is installed with your XAI client tools and is used to view traces created on the XAI server.

XML Background Topics

The following section introduces some background information related to XML.

Next in This Section

- XAI Schemas

- XSL Transformations

- SOAP

- XPATH

- Server Security

XAI Schemas

Note: Business Adapter. The BusinessAdapter adapter supports communication to configuration tool objects: business objects, business services and service scripts through their own schema API. When communicating to these objects, it is not necessary to create XAI schemas for the schemas associated with the objects. As a result, there is no need to use the XAI schema editor when defining XAI Inbound Services for this adapter.

At the core of XAI are XML web services based on XML schemas. XML schemas define the structure of XML documents and are the infrastructure of e-business solutions. They are used to bridge business applications and enable transaction automation for e-commerce applications. Industry standard schemas document common vocabularies and grammars, enhancing collaboration and standardization. Validating XML processors utilize XML schemas to ensure that the right information is made available to the right user or application.

The system exposes its application objects as XML schemas that define the interface to system services. Every service (e.g., CreatePerson or AccountFinancialHistory) is defined using a pair of schemas: the Request Schema and the Response Schema. The request and response schema can be identical.

The Request Schema defines the XML document structure describing the "inputs" for a service.

The Response Schema defines the XML document structure describing the "outputs" of a service.

Next in This Section

- The Schema Editor

The Schema Editor

CAUTION:

This schema editor is a separate legacy tool that is no longer recommended. The documentation remains for upgrade purposes

To facilitate the process of exposing business objects as XML schemas, we use the Schema Editor, a graphical tool to create, import and maintain schemas. The Schema Editor provides automated wizards to import schemas residing in existing data structures and documents. The Schema Editor can import schemas from the following sources: system business objects, ODBC data sources, sequential files.

Before the XAI tool can use a service, it must be registered or published.

Fastpath: Refer to Schema Editor for more information.

XSL Transformations

XSL Transformations (XSLT) is a language used to transform an XML document into another XML document or another document format such as HTML. It is part of the Extensible Stylesheet Language (XSL) family of recommendations for defining XML document transformation and presentation. It is defined by the World Wide Web Consortium (W3C) and is widely accepted as the standard for XML transformations. Several tools are available on the market to generate XSLT scripts to transform an XML document defined by a source schema to an XML document defined by a target schema.

In XAI you can use XSL to:

- Transform an inbound message into the structure required by the XAI request schema for that service.

- Transform the response to an inbound message into a format defined by a schema provided by the requesting application.

Fastpath: Refer to XAI Inbound Service for more information.

- Transform an outgoing message before it is sent out.

Fastpath: Refer to XAI Route Type for more information.

- Transform data from an external source before it is loaded into the staging upload table.

Fastpath: Refer to XAI Inbound Service Staging for more information.

SOAP

SOAP stands for Simple Object Access Protocol. The SOAP "Envelope" is the wrapping element of the whole request document that may be used by messages going through the XAI tool.

The following diagram shows a simple XML request using the SOAP standard.

XPATH

The XML Path Language (XPath) is an expression language used by XSLT to access or refer to parts of an XML document. It is part of the XSL recommendations maintained by the W3C. XPath provides the syntax for performing basic queries upon your XML document data. It works by utilizing the ability to work with XML documents as hierarchically structured data sets.

In the following XML document, some examples of XPath references are:

- authors/author/name

- authors/*/name

- authors/author[nationality]/name

- authors/author[nationality='Russian']/name

- authors/author[@period="classical"]

In the XAI tool, XPath is used to construct outgoing messages.

Server Security

XAI server security supports the basic HTTP authentication mechanism as well as web service security (WS-Security) to authenticate the user requesting service. When authenticating using WS-Security, the SOAP header contains the authenticating information.

The base package provides two XAI server URLs, one that uses basic HTTP authentication ('/classicxai') and another that supports both methods ('/xaiserver'). Regardless of which authentication method is practiced, it is the latter you should expose as your main XAI server. The main XAI servlet gathers authentication information from the incoming request (HTTP or SOAP header) and further calls the internal ("classic") servlet for processing.

The "classic" XAI server security uses the basic HTTP authentication mechanism to authenticate the user requesting service. It assumes the requester has been authenticated on the Web server running the XAI servlet using the standard HTTP (or HTTPS) basic authentication mechanism. The authenticated user-id is passed to the application server, which is responsible for enforcing application security. This requires the system administrator to enable basic authentication for the Web server running the XAI servlet. To enable HTTP basic authentication, the XAI server '/classicxai' should be defined as a url-pattern in the web resource collection in the web.xml file. When the XAI server is not enabled for basic authentication, it transfers the user-id specified on the Default User Message option to the application server.

By default, the system would always attempt to further authenticate using SOAP header information. This is true even if the request has already been authenticated via the Web server. Use the Enforce SOAP Authentication Message Option to override this behavior so that a request that has been authenticated already by the Web server does not require further authentication by the system.

If SOAP authentication information is not provided, the system attempts to authenticate this time using information on the HTTP header. You can force the system to solely use SOAP authentication using the Attempt Classic Authentication Message Option.

Currently the system only supports the standard Username Token Profile SOAP authentication method where "Username", "Password" and "Encoding" information is used to authenticate the sender's credentials. The following is an example of a Username Token Profile in a SOAP header:

<SOAP-ENV:Envelope xmlns:SOAP-ENV = "urn:schemas-xmlsoap-org:envelope">

<SOAP-ENV:Header xmlns:wsse="http://www.w3.org/2001/XMLSchema-instance">

<wsse:Security>

<wsse:UsernameToken>

<wsse:Username>MYUSERID</wsse:Username>

<wsse:Password Type="PasswordText">MYPASSWORD</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

<SOAPActionVersion>2.0.0</SOAPActionVersion>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

...

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

By default both user and password are authenticated. You can use the System Authentication Profile Message Option to change this.

Note: Custom authentication. You can override the base package user credentials authentication logic using the System Authentication Class Message Option.

Inbound Messages

Inbound messages are XML messages sent by an external application to invoke a system service. Inbound messages can be sent one at a time or in batches of several messages in a file. Third party integration points can import web services for inbound service calls. The standard method of doing this is by publishing a WSDL (Web Service Definition Language) definition for each exposed service.

Next in This Section

- Synchronous Messages

- Asynchronous Messages

- Inbound Message Error Handling

- Integration Scenarios

- WSDL Catalog

Synchronous Messages

Synchronous service requests are sent using the HTTP protocol to the XAI servlet, which runs under a web application server such as WebLogic.

- The service request XML document must conform to the request schema that defines the service.

- The XAI servlet on the web server receives the service request XML document and based on the service name in the document identifies the appropriate XAI Inbound Service. Once the service is identified, the XAI servlet accesses the XAI Inbound Service record to find out the properties of the service.

- Based on the service properties, the XAI module loads the request and response schemas from the schemas repository (and caches them in memory).

- Based on the Adapter referenced by the service, it calls the appropriate adapter. The adapter performs most of the work to service the request.

- The adapter connects to the application server, based on the connection information in the registry control tables.

- It then parses the request document using the request schema.

- Once the request document has been validated, the adapter converts the XML request document into a call to the application server.

- The response returned by the application server is then converted into a service response XML document, based on the response schema.

- The XML response document is shipped back to the caller over HTTP.

Next in This Section

- Using HTTP for Synchronous Service Execution

Using HTTP for Synchronous Service Execution

Invoking a service is not much different from sending a regular HTTP request. Here the HTTP request contains the XML as a parameter. The XAI server handling requests via the HTTP protocol is implemented using a Java servlet running on the web server.

Microsoft Visual Basic/C Example

Microsoft provides an easy way to send XML requests over HTTP. To send and receive XML data over HTTP, use the Microsoft XMLHTTP object

set xmlhttp = createObject("Microsoft.XMLHTTP")

xmlhttp.Open "POST", http://Localhost:6000/xaiserver, false

xmlhttp.Send XMLRequest

XMLResponse = xmlhttp.ResponseText

Here http://localhost:6000/xaiserver is the URL of the XAI server. XMLRequest contains the XML request to be processed by XAI and XMLResponse contains the XML response document created by the XAI runtime.

Java Example

Java provides a very simple way to send a request over HTTP. The following example shows how a request can be sent to XAI from an application running under the same WebLogic server as the one XAI runs. In this example, we use the "dom4j " interface to parse the XML document.

import com.splwg.xai.external.*;

import org.dom4j.*;

String xml;

xml = "<XML request>";

XAIHTTPCallForWebLogic httpCall = new XAIHTTPCallForWebLogic();

String httpResponse = httpCall.callXAIServer(xml);

Document document = DocumentHelper.parseText(httpResponse);

Asynchronous Messages

Various types of receivers running under the MPL server (rather than the XAI server) handle asynchronous inbound messages from several sources.

Requests may be received via the following:

- MQSeries, TIBCO or any JMS compatible messaging system

- The XAI Upload Staging table

The response is returned to the JMS queue/topic or to the staging table.

Fastpath: Refer to Designing XAI Receivers for more information about the different receivers provided by the product for the different data sources.

The following diagram shows the flow for asynchronous inbound messages.

Next in This Section

- Using JMS

- Staging Upload

- Staging Control

Using JMS

Java Message Services (JMS) is a standard Java Enterprise Edition (Java EE) protocol to send/receive asynchronous messages using a queue or topic message protocol.

XML messages may be received and sent via JMS using either a JMS Queue or JMS Topic. In order to access a JMS provider such as MQSeries, TIBCO or WebLogic, the MPL must first connect to the appropriate server using a JMS Connection.

The following diagram depicts a message sent and received through a JMS Queue.

Next in This Section

- Using JMS Queues

- Using JMS Topics

Using JMS Queues

JMS Queues are used to receive and send messages using the message queue protocol. Products that support this protocol include MQSeries.

The following describes events that take place when a JMS queue is used:

- The requester places the XML request message on a JMS queue. The request contains both the XML message and the name for the reply queue.

- The JMS Queue Receiver waits for messages on that queue. When the message arrives it is selected from the queue and executed using the adapter for the requested service.

- The XML response message is placed on the reply queue specified in the request. It is the requester's responsibility to fetch the response message from the queue.

The MPL uses a JNDI server to locate the queue resource.

Using JMS Topics

JMS Topics are used to send and receive messages using the publish/subscribe messaging model. Products that support this protocol include TIBCO, MQSeries and WebLogic.

The MPL uses a JNDI server to locate the topic resource.

- Define a JMS Topic receiver, listening to a predefined JMS Topic.

- The other application builds an XML message based on the schema defined for that service.

- It sends the XML request to the predefined topic and specifies the reply topic name.

- The MPL reads the message from the Topic, executes the service and returns the response to the reply topic specified in the inbound message.

Staging Upload

The system provides a staging table, where an interface can store XML requests to perform a service in the system.

Some external systems interfacing with the system are not able to produce XML request messages. Or you may have external systems that produce XML messages but the messages are sent in a batch rather than real time. The system provides the capability to read an external data source containing multiple records, map the data to an XML request and store the request on the XAI upload staging table. These records may be in XML requests, sequential input files or database tables.

The XAI upload staging table may be populated in one of the following ways:

- When a collection of messages in a file or database table must be uploaded, a staging control record should be created for each file/database table. The Staging Control Receiver processes each file or database table and creates records in the XAI upload staging table for each message.

- The XML File Receiver creates records directly in the XAI upload staging table. Note, in addition, the XML File Receiver creates a staging control record to group together these records.

- XAI creates records in the XAI upload staging table for inbound messages in error that are configured to post the error.

- It is possible that when a response to a notification download staging message is received (Oracle Customer Care and Billing only), the response requires some sort of action. If this is the case, the system creates an XAI upload staging record (and an XAI staging control record) for the response.

Next in This Section

- Staging Upload Receiver

- Staging Upload Sender

Staging Upload Receiver

Once the XML requests are in the staging table, the Staging Upload Receiver reads the requests from the XAI upload staging table and invokes the XAI server (via the executer) with the appropriate XAI inbound service. Inbound service records typically point to the core adapter used to invoke system services.

Staging Upload Sender

The staging upload sender handles "responses" to the execution of the message in XAI upload staging. If the execution is successful, the sender updates the status of the upload staging record to complete. If the execution is unsuccessful, the sender updates the status to error and creates a record in the XAI upload exception table.

Note: Configuration required. The above explanation assumes that you have correctly configured your upload staging receiver to reference the upload staging sender. Refer to Designing Responses for a Receiver for more information.

Staging Control

The staging control table is used to indicate to XAI that there is a file or table with a collection of records to be uploaded. The special Staging Control Receiver periodically reads the staging control table to process new records.

The XAI staging control table may be populated in one of the following ways:

- To process a specific sequential input file, manually create a staging control record and indicate the location and name of the file and the XAI inbound service to use for processing. Use this mechanism to process ad-hoc uploads of files.

- If a file is received periodically, you may define a File Scan Receiver, which periodically checks a given file directory for new files. The file scan receiver creates a new staging control record to process this file.

- The XML File Receiver processes a file containing a collection of XML messages to be uploaded. The XML file receiver creates a staging control record and creates records directly into the XML upload table. The staging control record is automatically set to a status of Complete and is used to group together the XML upload records. Refer to Processing Staging Upload Records for a Staging Control for more information.

- To upload records from a database, manually create a staging control record and indicate an appropriate XAI inbound service, which contains the information needed by the system to access the appropriate table. Use this mechanism to process ad-hoc uploads of files.

Note: To upload records from a database table, you must create a staging control record. There is no receiver that periodically looks for records in a database table.

- Whenever an XAI upload staging record is created, an XAI staging control record is created as well.

Fastpath: Refer to Batch scenarios for more information about configuring the system to populate the staging control with requests from external files.

Next in This Section

- Staging Control Receiver

- Processing Staging Upload Records for a Staging Control

- Processing Staging Records in Sequential Order

- Staging Control Parameters

- Staging Control Sender

Staging Control Receiver

The Staging Control Receiver processes staging control records and invokes XAI (via the executer) to execute the request. The executer uses the appropriate adapter to generate records in the XAI Upload Staging table - one for reach record in the file or table.

The diagram below illustrates the information used by the staging control receiver to load data onto the staging table from a sequential input file.

The staging control adapter does the actual work. It reads the individual records in the input file and applies the XSL transformation script indicated on the XAI inbound service record to the input data to produce an XML request in the XAI upload staging table.

Processing Staging Upload Records for a Staging Control

In some cases, a process may populate records directly into the XML staging upload table. An example of such a process is the XML File Receiver. In this case, a staging control record is also created and used to group together the staging upload records.

The staging control contains information needed to process a group of staging upload records:

- The user related to these records. This user is for application security purposes. The user indicated here must have the proper rights for the application service and transaction type to be executed by XML upload records processed for this staging control.

- An indication of whether or not the records should be processed sequentially.

Processing Staging Records in Sequential Order

In some cases, a collection of messages uploaded together in a file must be processed in the order the messages are received. For example, if messages to add a person and add an account for this person are received together, the message to add the person must be processed before the message to add the account.

If messages received in a file must be processed sequentially, turn on the Sequential Execution switch on the staging control record. When the staging control receiver creates records in the XML upload table, the identifier of each record is built as a concatenation of the staging control record and a sequential number. If your staging control record indicates that the XML upload records should be processed in sequential order, the records are processed in primary ID order.

Note: Non-sequential processing. If your staging control does not indicate that the related XML records should be processed in sequential order, the records are processed by the staging control receiver using a random, multi-threaded mechanism.

If you have defined a receiver to periodically search for files and populate records in the staging control table, you may turn on the Sequential Execution switch on the receiver. This ensures that records processed as a result of this receiver are executed in sequential order.

Staging Control Parameters

If your staging control accesses the data from a database table, you have the capability of defining the selection criteria. XAI inbound services that reference the CISStagingUpload adapter may contain a collection of fields that are used in an SQL WHERE clause. When adding a new XAI Staging Control record, you can define the values for the WHERE clause.

For example, imagine that you have a work management system where new premises are defined. Rather than waiting for this system to "push" new data to you, you design the interface to have the system "pull" the new data by looking directly at the "new property" database table.

The Request XML for your XAI service contains SQL statements used to access the data. You could define a Staging Control Parameter of "Add Date". When creating your staging control, you may enter a parameter value of today's date. When this record is processed, it only retrieves new properties from this work management table whose Add Date is today.

The following example shows part of the Request XML schema for an XAI Service that SELECTs premises based on postal code.

The postal code value to substitute into the WHERE clause is defined on the individual XML Staging Control records.

Fastpath: Refer to XAI Staging Control for more information.

Staging Control Sender

Before the staging control receiver invokes the executer, it changes its status to complete, assuming that there will be no problems. If the executer detects an error condition, the staging control sender updates the status of the staging control record to error and removes any XAI upload staging records that may have been created.

Note: Configuration required. The above explanation assumes that you have correctly configured your staging control receiver to reference the staging control sender. Refer to Designing Responses for a Receiver for more information.

Inbound Message Error Handling

For messages that are processed using the staging upload table, application errors that prevent XAI from successfully processing the message cause the staging record to be marked in error and highlighted via a To Do entry.

For messages that are not processed via staging upload, your implementation should consider what should happen to application errors. If the origin of the message is able to handle an immediate error returned by XAI, then no special configuration is needed. An example of this is an HTTP call to our system where the originator of the message is waiting for a real-time response.

Otherwise, for messages where errors should not be returned to the originator, but should be highlighted in this system for resolution, be sure to mark the Post Error switch on the XAI inbound service. When this switch is turned on and an application error is received by XAI when processing the message an XAI upload staging record is created (along with a staging control record) and marked in error.

For example, if a message is received via a JMS queue, application errors that prevent XAI from processing the message should not be returned to the queue because there is no logic to route the error to the sending system.

Integration Scenarios

Next in This Section

- Integration Using an EAI (or Hub)

- Batch Scenarios

Integration Using an EAI (or Hub)

It is possible for your various systems to be integrated with each other using a hub. The hub is implemented using an Enterprise Application Integration (EAI) tool provided by a third party vendor. Most hubs support HTTP and/or JMS and can work with XML schemas or document type definitions (DTDs).

- XAI services are presented to the EAI tool as schemas or as DTDs, immediately making the system callable from the hub.

- Integration scripts or workflow processes are defined in the EAI tools.

- At run time the hub uses HTTP or JMS to access the system using inbound messages.

- Outgoing messages are used to notify the hub about events occurring in the system. The messages are sent using HTTP or JMS.

Batch Scenarios

Messages may be sent in batch files, or may be retrieved from a database. In all cases, the system needs to be able to read the file and identify each individual message in order to create an XML request that can be processed by the XAI server. Once each individual message is identified, a request is stored on the XAI Staging Upload table for later execution.

Next in This Section

- XML Message File

- Sequential Input File

- Database File

XML Message File

It is possible for you to receive a file containing a collection of XML messages. The system identifies each separate message within the file and creates an entry for each message on the XAI upload staging table. It also creates a staging control record to group together each newly created XAI upload record. This staging control is created in Complete status and is not processed by the staging control receiver.

Since external applications may send messages in a format unknown to XAI, the system needs a mechanism for identifying the messages and mapping them to an XAI service.

Next in This Section

- XAI Groups

- Attachments and Rules

XAI Groups

First the system associates the entire XML file with an XAI Group. You can think of the XAI Group as a categorization of the collection of messages. For example, you may have a separate XAI Group for each third party who sends you a collection of XML messages.

The system uses an XPath and XPath value to identify the correct XAI Group for the XML file.

Attachments and Rules

After identifying the appropriate group to which an XML file belongs, the system takes each message in the file and applies the appropriate XSL transformation to the message to produce a record on the upload staging table.

To process the messages in a file, the system needs to know how to identify each message in a file containing multiple messages. A file may use the same root element for each message or different root elements for different types of messages. For each XAI group, you must indicate the root element(s) that identifies a message by defining one or more attachments. Each attachment defines a root element, which tells the system when a new message begins.

Once the system has identified each separate message in the file, it must determine the correct XSL transformation script to apply. Once again the system uses an XPath and XPath value to identify the correct XSL to apply. For each XAI group, you define one XAI rule for every possible type of message you may receive in the file. Each XAI rule defines an XPath, XPath value and XSL transformation script.

Note you may assign a priority to each of your rules. The rules for more common messages may be assigned a higher priority. This enhances performance by ensuring that rules for more common messages are processed before rules for less common messages.

Note: Include parent elements. If the XML message includes parent elements (such as a transmission id or a date/time) that are needed for any of the separate child messages that are posted to the upload staging table, you can configure the appropriate attachment to include parent elements.

Fastpath: Refer to Designing an XML File Receiver for more information about defining receivers that process XML files.

Sequential Input File

You may receive messages in a sequential input file, such as a comma-delimited file.

The following steps should be performed when configuring the system to enable data to be uploaded from an input file into the staging upload table:

1. Create an XML Schema that describes the records in the sequential input file.

2. Create the XSLT transformation that maps a record in the input file to an XML service request in your product.

3. Create an XAI service representing the batch process that loads the input file into the staging table.

4. If desired, create a new file scan receiver, which waits for an input file to appear in a particular directory. (If you do not take this step, then you need to create a staging control when you want a file to be processed.)

Note: Character Encoding. If the file is encoded with a specific character encoding, you may indicate the encoding as part of the file name to be uploaded. If the file name ends with ?enc=?x, where x is the file character encoding, the adapter processes the file accordingly. For example, the file name may be specified as premiseUpload.csv?enc=?UTF-8. If the encoding is not specified as part of the file name and the file is in UTF-16 or UTF-8 with byte order mark, then the adapter can recognize the encoding.

Database File

It is possible for you to define an interface where inbound messages are retrieved by reading records in a database table.

The following steps should be performed when configuring the system to enable data to be uploaded from a database table into the staging upload table:

- Create an XML Schema that describes the records in the database table.

- Create the XSLT transformation that maps a record in the database table to an XML service request in your product.

- Create an XAI service representing the process that loads the records from the database table into the staging table.

WSDL Catalog

Web Service Definition Language (WSDL) is a language for describing how to interface with XML-based services. It acts as a "user's manual" for Web services, defining how service providers and requesters communicate with each other about Web services.

The base package provides the ability to publish a WSDL definition for each service exposed as an XAI Inbound Service. In addition, it is possible to request a catalog of all the XAI Inbound Services and a link to each WSDL. To view the catalog, launch a new browser session and enter the URL http://$host:$port/XAIApp/xaiserver?WSDL where $host and $port are replaced by the appropriate values for the current environment.

Outgoing Messages

This section describes outgoing message functionality related to MPL, which is no longer recommended.

- Outbound messages. As described in Outbound Messages, outbound messages are supported for sending outgoing messages. This functionality includes support that is only related to MPL.

- Notification download staging (NDS) messages. This method is only supported by Oracle Utilities Customer Care and Billing. Using this method near real-time, a record is written to the NDS staging table referencing only key fields. MPL then polls the records, invokes a service to build the message, applies the XSL and routes the message. If sent real-time, no record is posted to the staging table but rather the message dispatcher routes the message immediately. Refer to Oracle Utilities Customer Care and Billing help, Workflow and Notifications, Notification and XAI for more information.

The following sections describe the outbound messages topics specific to MPL in more detail.

Next in This Section

- Outbound Message Receiver

- Lifecycle of Outbound Message

- Outbound Message Sender

- Outbound Message Error Handling

- Automatic Resend

Outbound Message Receiver

The outbound message receiver processes records in the outbound message table that have a processing method flag equal to XAI and a status of pending and changes the status to in progress. The receiver then retrieves the message XSL and the message sender defined for the external system / outbound message type.

Note: Template external system. If the outbound message's external system references a template external system, the outbound message type configuration for the template external system is used.

It applies the message XSL (if supplied). If the option to validate outbound message schemas is turned on, the schema validation is performed.

Refer to Outbound Message Error Handling for information about error handling.

If no errors are received, control is turned over to the outbound message sender for routing.

Note: Initialization of receiver. During the initialization of this receiver (for example if there is a problem with MPL and it is restarted) any records that are found to be in progress are changed to pending so that those messages are sent properly.

Lifecycle of Outbound Message

The outbound message receiver processes outbound message records based on their status. The following diagram describes the lifecycle of an XAI type outbound message.

- Records are created in pending status.

- The outbound message receiver processes pending records and changes the status to in progress.

- If the message is sent successfully the system changes the status to complete.

- If there was a problem sending the message the system changes the status to error.

- When the user resolves the error they can change the status back to pending.

- A user can change the status of a pending or error record to canceled.

- For the rare cases where there is a problem with MPL and a message is left in the status in progress, users may manually change the status to canceled. In addition the outbound message receiver includes a step at startup to find in progress messages and change them to pending.

Outbound Message Sender

The outbound message sender is responsible for routing the message to the Message sender determined by the receiver. If the routing is successful the outbound message status is marked complete. If the routing is unsuccessful, the status is marked in error.

Refer to Outbound Message Error Handling for information about error handling.

Note: Automatic Resend. If you have configured the system for automatic resend and the system detects that the error is due to the sender being unavailable, the message remains in pending status.

Note: Configuration required. The above explanation assumes that you have correctly configured your outbound message receiver to reference the outbound message sender. Refer to Designing Responses for a Receiver for more information.

Outbound Message Error Handling

If the outbound message receiver or the outbound message sender detects an error while attempting to process the outbound message, it marks the message in error, captures the error message and its parameter values and creates a To Do entry using the To Do type specified in the Message option To Do Type for Outbound Message Errors.

A separate background process F1-DTDOM is responsible for completing To Do entries for outbound messages no longer in Error.

Automatic Resend

If a system error is received by the MPL when attempting to route the message to a sender, (using the outbound message method or the NDS message method), the system marks the appropriate table in error. This is true even if the reason for the error is that the connection to the sender is unavailable. When the connection is restored, a user must change the status of the appropriate record to pending (for outbound messages) or retry (for NDS messages) in order for the message to be resent.

Alternatively, you can configure your system to attempt to automatically resend the message. This section describes the logic available for auto resend. To enable automatic resend, you must set the flag Automatically Attempt Resending to Unavailable Senders on Message option appropriately.

If an error is received by the MPL when it attempts to invoke a sender and the auto resend option is on, the system does not mark the record in error. It continues to attempt sending messages to the sender until the number of errors has reached a predefined maximum error number (defined as an Message option). When the maximum is reached, the sender is marked as unavailable and an MPL log entry is created. The MPL ignores messages for unavailable senders.

The system tries to resend messages to this sender the moment the sender is reset to be available. The following points describe how a sender becomes available:

- MPL attempts to retry sending messages to unavailable senders every X minutes, where X is defined on Message option.

- On MPL startup all senders are marked as available

- A user may navigate to the XAI Command page and issue a command MPL Refresh Sender to refresh the cached information for a particular sender

Designing Your XAI Environment

This section guides you through the steps required to design the tables that control your XAI processing.

Next in This Section

- Installation

- Designing XAI Inbound Services

- Designing XML Schemas

- Designing XSL Transformations

- Designing Your Registry Options

- Configuring the System for NDS Messages

Installation

The XAI server is installed with default configuration. This section describes how you may customize the XAI server configuration.

Startup parameters are defined in two parameters files

- The XAIParameterInfo.xml file is used by the XAI HTTP server. This file is found within the XAI directory in the path (...\splapp\xai).

- The MPLParameterInfo.xml file is used by the MPL server. This file is found within the XAI directory in the path (...\splapp\mpl).

Both files store the parameters as XML files with the following elements (sections):

- Source

- ParameterVariables

- AdHocParameters

Next in This Section

- The XAI Source Section

- The MPL Source Section

- The Parameter Variables Section

- The AdHoc Parameters Section

The XAI Source Section

The XAI tool accesses XAI registry information through the standard system programs. The <Source> section in the XAIParameterInfo.xml file tells XAI the user ID for accessing the registry information. It contains the following attributes:

Attribute Name

Description

Source Type

This should be set to CorDaptix, which tells XAI to access the registry through the standard access to system programs.

CorDaptixUser

The user ID to use when accessing the registry data.

The MPL Source Section

The <Source> section in the MPLParameterInfo.xml file defines the database connection information used to connect to the database storing the XAI table information. It contains the following attributes:

Attribute Name

Description

Source Type

Defines the source of the data, for example ORACLE or DB2.

jdbcURL

The URL used to connect to the product database. For example: jdbc:oracle:thin:@//server-name:1234/DBNAME

databaseUser

The Oracle User Id used to connect to the database.

databaseUserPassword

The Oracle password used to connect to the database.

The Parameter Variables Section

When defining values for fields in certain control tables in the registry, you may reference substitution variables that point to the <ParameterVariables> section of the installation files. Substitution variables provide for dynamic substitution of values based on parameters provided at server startup.

To specify a substitution parameter in a string value you enter the name of the substitution parameter enclosed with @.

For example if you have a field in the XAI control tables that should contain the URL for the XAI HTTP servlet, you could enter the value in the following way: http://@HOST@:@PORT@/xaiserver.

In the parameters section, define the appropriate values for these parameters, for example:

<ParameterVariables>

<ParameterVariable name="HOST" value="localhost" />

<ParameterVariable name="PORT" value="8001" />

</ParameterVariables>

At run time, the system builds the URL as http://localhost:8001/xaiserver.

Every substitution parameter is defined using an <ParameterVariable> element with the following attributes:

Attribute Name

Description

Name

The name of the substitution parameter

Value

The value to replace an occurrence of the substitution parameter in an XAI control table field

Note: Substitution parameters can only be used for string fields, and not for fields that are foreign keys to other objects.

The AdHoc Parameters Section

The <AdHocParameters> section is used to provide registry definitions that override the existing ones. Unlike the <ParameterVariables> section, a whole registry object definition can be specified in this section. When the XAI server starts, it first reads the registry definitions from the database and then it reads the <AdhocParameters> section. If it finds an object definition in this section, it uses it to replace the one read from the database.

Attribute Name

Description

Object Name

The object name may be one of the following objects:

Option

Receiver

Sender

Object Attributes

The attributes of the object. Each object type has its own set of attributes:

'Option' object attributes

name

The option flag. Must be defined in the OPTION_FLG table

value

The value for that option

'Receiver' object attributes

name

The receiver ID

Class

The JMS provider. May be 'MQ'

TargetClient

The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries

JMSProvider

The JMS provider. May be 'MQ'

TargetClient

The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries

Executer

The XAI Executer ID for this receiver

'Sender' object attributes

Class

The JMS provider. May be 'MQ'

JMSProvider

The JMS provider. May be 'MQ'

TargetClient

The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries

Designing XAI Inbound Services

When designing your XAI environment, you should first identify the services that you would like to perform. Determining your services facilitates your design for the other registry options.

The following points highlight how to design your inbound services:

- Determine each service that needs to be performed

- Determine the correct adapter that is needed by your service.

- Determine the required layout of the request and response messages and specify the request schema and response schema.

- If a transformation of the data is required, you need to design the appropriate request XSL and response XSL transformation scripts.

- If the service references the staging upload adapter, determine the staging file type and design the record XSL transformation script. In addition, determine if you want to enter an input file name and interface name. Finally, determine whether or not you need to indicate a special JDBC connection.

- As new releases of the system are installed, it may be necessary to modify your service for the new release. If this is the case, you need to design separate versions of the inbound service.

Fastpath: Refer to XAI Inbound Services for more information.

Designing XML Schemas

You need XML schemas for the services you designed in Designing XAI Inbound Services.

For each message, identify what service you need to invoke and what action you need to perform. If you have multiple actions that you may need to perform for the same service, you may choose to create a single generic XML schema or you may choose to create multiple schemas, which are more specific. For generic messages, the transaction type, indicating the action to perform would be passed in on the XML request document to indicate what must be done. For more specific messages, you may be able to indicate the transaction type directly on the schema and it would not need to be overwritten at run time.

You need to create a response schema for each request schema. It is possible for you to use the same schema for both functions.

Fastpath: Refer to Schema Editor for more information.

Designing XSL Transformations

You need an XSL transformation script for each service you designed in Designing XAI Inbound Services, where you determined a transformation is necessary. In addition, you need XSLT scripts for your outgoing messages. Each sender, which receives a message, probably requires a transformation of the message into a local format. Refer to Outgoing Messages for more information.

For each message requiring transformation, determine the format used by the external system. In most cases, it is not the same format recognized by the system. For each case, you must create an XSL transformation, which maps the message format from the external format to one expected by your product or from your product format to one expected by the external system.

When identifying the required XSL transformations, remember to take into consideration the data that is processed by the staging control table. This service reads data stored in a file or database table and uses the Record XSL to map the individual records to an individual service request.

Fastpath: Refer to XAI Inbound Service for more information.

Designing Your Registry Options

The XAI registry is a set of control tables that is used to store service definitions as well as various system information required by the XAI and MPL servers. The following sections describe each table in the registry.

Next in This Section

- Designing XAI JDBC Connections

- Designing XAI Formats

- Designing XAI Adapters

- Designing XAI Executers

- Designing Message Senders

- Designing XAI Groups

- Designing XAI Receivers

Designing XAI JDBC Connections

If you need to access a database table to process your messages, XAI needs to know the location of the database and how to access it. If the tables are located in the same database used for the system (defined in your Installation), then you do not need to enter any extra JDBC Connections. If you need to access data that lives in another database, design the additional JDBC Connections and determine the type of connection and connection information.

Fastpath: Refer to XAI JDBC Connections for more information about defining XAI JDBC Connections.

Designing XAI Formats

The Formats section of the registry is used to define data formats. Data formats can be used in schema definitions to specify data transformations. To determine what data formats you need to define for your XAI environment, you must review the expected format of data that you will be exchanging and determine whether or not data transformation is required.

The following sections describe the four different types of formats and some guidelines in their use.

Next in This Section

- Date Formats

- Currency Formats

- Phone Formats

- Text Formats

Date Formats

Date formats may be specified using any valid Java format supported by the java.text.SimpleDateFormat class.

To specify the time format use a time pattern string. For patterns, all ASCII letters are reserved. The following usage is defined:

Symbol

Meaning

Presentation

Example

G

era designator

Text

AD

y

year

Number

1996

M

month in year

Text & Number

July & 07

d

day in month

Number

10

h

hour in am/pm (1~12)

Number

12

H

hour in day (0~23)

Number

0

m

minute in hour

Number

30

s

second in minute

Number

55

S

millisecond

Number

978

E

day in week

Text

Tuesday

D

day in year

Number

189

F

day of week in month

Number

2 (2nd Wed in July)

w

week in year

Number

27

W

week in month

Number

2

a

marker for am/pm

Text

PM

k

hour in day (1~24)

Number

24

K

hour in am/pm (0~11)

Number

0

z

time zone

Text

Pacific Standard Time

'

escape for text

Delimiter

''

single quote

Literal

'

Currency Formats

Currency formats are used to specify formatting for elements representing currencies. They may include the following:

Symbol

Meaning

#

Number place holder

,

Thousands separator

.

Decimal point

$

Currency sign

For example to define the currency format for US dollar, indicate: $#,#.00

Phone Formats

Phone formats can be used to specify formats for telephone numbers. The supported format specification is limited to the following format characters:

Symbol

Meaning

0

number place holder

\0

0

Any other character appearing in the formatting expression is a placeholder for that character. To specify the '0' character, use '\0'.

Phone Format Example: (000) 000-0000

Text Formats

Text formats are used to specify formats for character string attributes. The following expressions are supported:

Symbol

Meaning

\cUpperCase

Translate the string to upper case.

\cLowerCase

Translate the string to lower case.

\cProperCase

Translate the string to proper case. The first character of every word is translated to uppercase. The remaining characters are translated to lowercase.

Fastpath: Refer to XAI Format to define your XAI Formats.

Designing XAI Adapters

The product provides a set of adapters to process your XML requests. The adapters point to a specific Java class that renders a service. If you find that you need to use a protocol, which is not supported by the adapters provided, you will need to add a new Message Class (which points to a Java class) and a new XAI Adapter. It is recommended that your implementers contact customer support. The following adapter classes are provided.

- BUSINESSADA: This is the adapter class that provides access to schema-based objects. This adapter accesses business objects, business services and service scripts through their schema API. Services with this adapter need to indicate the schema of the object, which should be invoked. When communicating to these objects, it is not necessary to create XAI schemas for the schemas associated with the objects. XAI is able to directly communicate with these objects using their existing schema definitions. As a result, there is no need to use the XAI schema editor when defining XAI Inbound Services for this adapter.

- BASEADA: This is the core adapter class that provides access to any published system service. This adapter accesses system objects through the page server. Services with this adapter need to indicate the object (application service), which should be invoked.

- STGUPADA: This staging upload adapter class is used when an extra step is required prior to using a service with the core adapter. For example, perhaps you need to read a file, which is not in XML format, and convert it to an XML format recognized by the system. Services with this type of adapter do not need to indicate an application service but must indicate information about the file to be converted. Refer to XAI Staging Control for more information.

- XAICMNDADA: This is an internal adapter. It is used to send commands to the XAI Server.

- SIEBELADA: This adapter is no longer supported.

Designing XAI Executers

The executer is responsible for executing messages received through a message receiver. The product provides an executer, which uses the XAI server; however the architecture allows for implementing additional execution classes. If you require a different executer and therefore a different execution class, it is recommended that your implementers contact customer support.

Fastpath: Refer to XAI Executer for more information.

Designing Message Senders

This section only describes message sender functionality that is only related to the XAI/MPL processing. Refer to message sender for details about other types of senders that are supported independent of XAI/MPL.

Message senders are responsible for define outgoing message destinations and for " responding" to the XAI executer.

- For NDS messages, the sender to use is defined on the XAI route type for the notification download profile.

- For outbound messages, the sender to use is defined on the external system / outbound message type collection.

- For responding to the XAI executer, the sender to use is defined on the receiver.

For each sender, you must reference an appropriate Message Class. The information in this section describes the sender classes that are provided with the system.

You must create senders to "respond" to the various staging table receivers in the system.

- Create a sender to be used for "responses" to messages processed by the staging control receiver. You should create one sender, which points to the Message Class UPLDERRHNDLR. Refer to Staging Control Sender for more information about this sender.

- Create a sender to be used for "responses" to messages processed by the upload staging receiver. You should create one sender, which points to the Message Class STGSENDER. Refer to Staging Upload Sender for more information about this sender.

- Create a sender to be used for messages processed by the download staging receiver. You should create one sender, which points to the Message Class DWNSTGSNDR. (DWNSTGSNDR is not supported in all products.)

- Create a sender to be used for messages processed by the outbound message receiver. You should create one sender, which points to the Message Class OUTMSGSNDR. Refer to Outbound Message Sender for more information about this sender.

Next, design the senders for "responses" to other receivers, for example the JMS queue receiver or JMS topic receiver. The system provides message classes to use for these senders. Use the class JMSSENDER for a JMS queue sender and TPCSNDR for a JMS topic sender.

Finally, review all your outgoing messages and determine the mechanism for communicating with the target system for each message.

- For all senders that are used for real time messages, define a context entry with a context type of Response Time Out to define the amount of time the system should wait for a real time response.

- An HTTP sender is one that sends messages to an HTTP server using the HTTP protocol. For an HTTP sender, reference a message class of HTTPSNDR. In addition, the context described in Message Sender — Context for the RTHTTPSNDR apply to this sender as well.

- An email sender allows for XML messages to be sent as email messages through an SMTP server. It can be used in notification download processes to send a response as an email message. The email sender supports standard email functionality such as "CCs" and attachments. The content of the email message is controlled by the XSL script defined in the XAI route type of the NDS message. The XSL script has access to all context records of the NDS message as well as the input XAI message that was created by processing the NDS. Reference a message class of EMAILSENDER. In addition, the context described in Message Sender — Context for the RTHTTPSNDR apply to this sender as well.

- If you want XML messages to be written to a flat file, use a flat file sender. For example, it can be used in the notification download process to write a response message to a flat file. Flat file senders should reference a Message Class of FLATFILESNDR. In addition, the following context records should be defined for senders of this type.

Context Type

Description

Values

Flat file output directory

Directory in the file system where to write the file

Flat file filename pattern

The name of the output file. The file name may be a literal constant, or generated dynamically.

To create a dynamic filename use <file name>$$ID, where $$ID is replaced at run time by the ID of the NDS message that triggered the response message. If no file name is defined for the sender, the XAI server generates a file name with the following format 'XAI$$ID.xai'.

Append data to file

This parameter controls whether the content of the response message is appended to an existing file, or a new file is created (possibly replacing an existing one).

YES or NO

Character Encoding

Indicates if the message should be sent with character encoding. The sender will write the content of the file with encoding specified in the context value. If no value is specified, the sender uses the default Java system encoding, which is determined according to the operating system locale.

UTF-8 or UTF-16

Designing XAI Groups

XAI groups are used by the system to process an XML file containing multiple messages to be uploaded into the system. One or more groups may be defined for an XML file receiver.

Fastpath: Refer to XML Message File for more information about how groups are used to process an XML file.

When setting up your XAI environment, identify the interfaces that require uploading an XML file containing multiple XML messages into the system through XAI.

First you need to categorize the XML files that you may receive. Define an XAI Group for each logical categorization. For example, you may want to define a separate XAI Group for each third party who may send you a collection of XML messages. Or, if all third party service providers send direct access messages in a standard format, you may want to define a single XAI Group for direct access messages.

For each group, you need to identify the root elements that indicate when a new message is starting. This collection of unique root elements for a group is called the attachments.

For each group, you must identify every possible message that may be sent. For every message, define an XAI Rule. The rule indicates the XSL transformation script to be executed along with the XPath and XPath value that the system uses to identify each message.

Fastpath: Refer to XAI Group to define groups, their attachments and their rules.

Designing XAI Receivers

Receivers define small pieces of code that wait for requests to be received through various sources. Each receiver references a Message Class where the small piece of code is defined. The following receiver classes are provided:

Class

Description

STGRCVR

Polls the XAI upload staging table for new inbound requests.

STGCTLRCVR

Polls the XAI staging control table for new upload processes.

DWNSTGRCVR

Polls the notification download staging table (NDS) for new messages. (Not available in all products).

OUTMSGRCVR

Polls the outbound message table for new messages.

JMSRCVR

Receives requests through a message queue that supports the JMS Queue interface, such as IBM MQSeries.

TPCRCVR

Receives requests through a publish/subscribe model, such as TIBCO, or any system supporting the JMS Topic interface.

FILESCANRCVR

Polls a given directory for files with a given file name pattern.

XMLFILERCVR

Polls a given directory for XML files with a given file name pattern.

Multiple receivers may be defined for these receiver classes. For example, the XML file receiver defines the scan directory. If you have multiple directories that contain files to be uploaded, define a receiver for each directory.

All types of receivers reference a Message Class and XAI Executer. If you require a new Message Class or Executer because you use a protocol that is not currently supported, it is recommended that your implementers contact customer support.

Next in This Section

- Designing Responses for a Receiver

- Designing Receivers that Poll Staging Tables

- Designing a JMS Queue Receiver

- Designing a JMS Topic Receiver

- Designing a File Scan Receiver

- Designing an XML File Receiver

Designing Responses for a Receiver

Once a request has been sent for execution to the XAI server (via the executer), the response layer processes the response. For some receivers, a response may not be applicable. For example, a file scan receiver reads flat files in a given directory and posts records to the XAI staging control table. Responses are not applicable for this type of receiver.

The response may be conditional on the outcome of the request and may be sent to more than one destination (sender). To design your receiver responses, determine the conditions under which a response should be sent for each request processed by each receiver:

- Never send a response

- Send a response if the request was successful

- Send a response if the request was unsuccessful due to a system error

- Send a response if the request was unsuccessful due to an application error

Once you determine when to send a response, you must determine where to send the response. Responses for different conditions may be sent to different Message Senders or to the same Message Sender.

Designing Receivers that Poll Staging Tables

The following receivers are needed to poll the various system staging tables.

- Create a staging upload receiver that references the Message Class STGRCVR. For responses, All Events should reference the staging upload sender.

- Create a staging control receiver that references the Message Class STGCTLRCVR. For responses, All Events should reference the staging control sender.

- If your implementation uses the NDS message method of communicating outgoing messages, create a staging download receiver that references the Message Class DWNSTGRCVR. For responses, All Events should reference the download staging sender. NDS messaging is not supported in all products.

- If your implementation uses the outbound message method of communicating outgoing messages, create an outbound message receiver that references the Message Class OUTMSGRCVR. For responses, All Events should reference the outbound message sender.

For all the above receivers, if you need to access multiple environments, simply create receivers for each JDBC connection. Note that you should not add more than one of each of the above receivers pointing to the same JDBC connection. To improve performance for a single JDBC connection you may configure multiple MPL servers.

Note: Sample Data for Initial Install. When first installing the system, records for each of the above receivers are provided. Your implementation may use these records or remove them and create your own.

Designing a JMS Queue Receiver

If you need to receive messages through a JMS compatible queue, you need to define a JMS Queue receiver. When designing a JMS Queue receiver you first need to design a JMS Connection and a JMS Queue.

If you would like to post responses back to the JMS queue, you may create a message sender to send the response to the JMS queue.

Designing a JMS Topic Receiver

If you need to receive messages through a JMS Topic using the publish/subscribe model, you need to define a JMS Topic receiver, which receives messages published under a specific topic. When designing a JMS Topic receiver you first need to design a JMS Connection and a JMS Topic.

If you would like to post responses through a JMS Topic using the publish/subscribe model, you may create a message sender to send the response to the JMS topic.

Designing a File Scan Receiver

The file scan receiver constantly looks in a given directory for files with a given pattern. When it finds a matching file, it creates a record in the staging control table to upload the contents of the file into the upload staging table.

When setting up your XAI environment, identify the interfaces that require uploading a file from a directory into the system through XAI. For each unique file, define a file scan receiver. For each receiver record, indicate the Scan Directory, where new files will be placed, the Scan File, which is the naming pattern to look for and the XAI Inbound Service to use for mapping the data into a system service.

In addition, if you want to specify a character encoding, the following Context record should be defined.

Context Type

Description

Values

Character Encoding

Indicates that the message is character encoded. When the receiver creates a staging control entry for a file, it will add ?enc=?x to the name of the file in the table where x is the value of this parameter. Refer to Sequential Input File for more information.

UTF-8 or UTF-16

Designing an XML File Receiver

The XML file receiver constantly looks in a given directory for XML files with a given pattern. When it finds a matching file, it goes through steps to identify each separate message in the file, determine the appropriate XSL transformation and create a record in the staging upload table.

Fastpath: Refer to XML Message File for more information.

When setting up your XAI environment, identify the interfaces, which require uploading an XML file containing multiple XML messages into the system through XAI. For each unique file, define an XML file receiver. For each receiver record, indicate the Scan Directory, where new files will be placed, the Scan File, which is the naming pattern to look for and the collection of XAI groups. XAI groups are used by the system to identify each separate message in the file and to determine the appropriate XSL transformation for each message.

Fastpath: Refer to Designing XAI Groups for more information.

Configuring the System for NDS Messages

Refer to the documentation for your product to find out if NDS messaging is supported.

Schema Editor

CAUTION:

This schema editor is a separate legacy tool that is no longer recommended. The documentation remains for upgrade purposes

The Schema Editor is a Graphical User Interface (GUI) tool to create XML schemas. The tool provides wizards to generate schemas from various sources.

Next in This Section

- Opening the Schema Editor

- Schema Editor Window

- Validating a Schema

- Registering a Service

- Testing a Schema

- System Wide Functions for Schema Editor

Opening the Schema Editor

After launching the schema editor, you are asked to connect to a database. On the Connect dialog:

- Select an ODBC data source pointing to the desired database.

- Enter the data source, user ID, password and database owner required to log on to that database.

- Click Connect.

After connecting, the schema editor appears.

Use the File/Open dialogue to select a schema from the schema directory. Refer to The Options Menu for information about setting the default schema directory.

Note: When opening a schema, the schema editor validates the schema and any errors are displayed. Refer to Validating a schema for more information.

Schema Editor Window

CAUTION:

This schema editor is a separate legacy tool that is no longer recommended. The documentation remains for upgrade purposes

The schema editor allows you to modify individual elements and attributes of a given schema.

Description of Page

Refer to System Wide Functions for Schema Editor for information about the various menu options available for the schema editor.

Service Name Enter the name of the service to be created in the service name text box. This is the name of the first element under the Body element in the XML document.

CAUTION:

Important! When adding new schemas, carefully consider the naming convention for the Service Name. Refer to System Data Naming Convention for more information.

Adapter The adapter used to process services using this schema.

Internal Service Name If the schema is for an adapter that should invoke a system service, this is the internal name of the service.

Transaction Type Select the transaction type performed by the service. The available values are Read, Add, Change, Update, Delete, List and Search.

Note: The difference between Change and Update is that for Change, all field values must be passed in with the request. Field values that are not passed in to the request are set to null. For Update, you need only pass the primary key field values and the values of the fields to be updated. All other fields retain their existing values.

Left Panel

The left panel of the schema editor displays a tree view of the hierarchical elements in the schema. The (+) expands a node, the (-) collapses a node.

Right Panel

The following attributes appear on the right panel of the Schema Editor. Some fields cannot be modified in the schema editor. The field description indicates when the field is protected.

Tag Name The XML element tag name. This field is protected, but you may modify this attribute to give the element a self-explanatory name by right-clicking on the element name in the left tree-view.

MetaInfo Name Maps the element to a fully qualified field name in the service, for example PER_ID. This field is protected.

Internal Type This property is populated automatically when you generate the schema from your product. The values further define elements and attributes. The values are page, pageBody, list, listHeader, listBody, searchHeader, codeTableDesc, Private. The values of codeTableDesc and Private are used to define special types of attributes.

Private attribute A field that does not exist on the server side, but one that you still want to have in the schema.

Description A description of this field.

Content The element type. This field is only available for elements. Possible values are eltOnly- element may contain only other elements and no text, TextOnly- element may only contain text.

Search Type Services, which perform a Search, may allow searching based on different criteria. The values are taken from the system meta information when the schema is generated. The possible values are Main, Alternate1, Alternate2, Alternate3, Alternate4, Alternate5 and Alternate6.

Note: You would not typically modify this value because it corresponds to a value in the meta information. However, the value is modifiable to accommodate the rare case in which a service may change in a new release. In this scenario, you may prefer to update the schema manually rather than regenerate a new schema for the new version.

Is Part of Primary Key Used to indicate to the XAI server whether or not this field makes up part of the primary key of the record. The values are taken from the metadata information when the schema is generated. Value may be true or false.

Note: Typically you would not modify this value because it corresponds to a value in the meta data information. However, the value is modifiable to accommodate the rare case where a service may change in a new release. In this scenario, you may prefer to update the schema manually rather than regenerate a new schema for the new version.

Min Occurs This field is available for elements only and is used for repeating elements. It defines the minimum number of occurrences for an element. Value may be 0 or 1.

Schema Max Occurs This field is available for elements only and is used for repeating elements. It defines the maximum number of occurrences for an element. Value may be 0, 1 or *.

Limit Number of occurrences This field is available for elements only and is used for repeating elements. If the Schema Max Occurs field has been set to '*', define the number of max occurrences here.

XML Data Type The data type for the attribute. Possible values are number, string, decimal, date, dateTime, and boolean.

Server Data Type Indicates the data type of this attribute on the server. This field is protected.

Service Format The format expected by the service. At runtime, XAI converts the Tag format to the Service Format before executing the request. Formats are defined in XAI Format.

Tag Format The format used to format an element/attribute in the schemas. Formats are defined in XAI Format.

Min Length Use this property to define the minimum length of the attribute, if applicable.

Max Length Use this property to define the maximum length of the attribute, if applicable.

Precision This is used for decimal attributes to define the maximum number of digits.

Scale This field is used for decimal attributes to define the number of digits at the right of the decimal point.

Required A value of Y indicates that the element must appear in XML document. A value of N indicates that the element is optional.

Default value Default value to be used for Request schema, when the element is not supplied as part of the XML request document.

Fixed Value Fixed value to be used for Request schema. This value is used regardless of the value supplied in the request document.

Code Table Field This property is used for attributes that are descriptions of a code table, where the description is not automatically returned by the system service. Use this property to indicate the code whose description should be retrieved by the XAI server.

Code Table Program This property is used for attributes that are descriptions of a code table, where the description is not automatically returned by the system service. Use this field to indicate the program that XAI should call to access the description for the Code Table Field.

Creating a Schema

Usually you do not create schemas from scratch; rather you use Schema Creation Wizards to import existing data structure definitions from a variety of data sources:

- System services

- Comma Delimited Files

- Database Extract

- Any XML document

Once a schema is created based on the existing data structure, it is displayed in a TreeView on the left panel. Once the imported schema has been edited, it serves as the basis for creating the request and response schemas. When imported, the schema exposes all fields defined in the service. You may want to remove some attributes/elements from the request or response schema.

Note: Although the main purpose of the editing process in the creation of the request and response schemas is the elimination of elements, which makes the schema shorter and more understandable, it is not required for processing purposes. Therefore, if you don't mind that you have not used elements in your schemas, you could stay with one schema, which serves as both the request and response schema.

1. Save the Schema as a Request schema with an appropriate name, for example PersonInfoRequestSchema.xml

2. To create the Response schema, which is identical to the request schema, use the Save As Response menu option. This renames the top element of the schema to ServiceNameResponse, for example PersonInfoResponse and save the schema under a different name i.e. PersonInfoResponseSchema.xml. Note that if the request and response schemas are identical then one schema may be used for both and there is no need to create separate schemas.

3. Read in the Request Schema (File/Open) and modify its structure. Depending on the service type, you'll have to modify the contents of the Request Schema. This is usually required when the service is an "Info" service, which requires very few input elements. In such cases you'll delete most of the elements on the schema and only leave the necessary elements required to invoke the service. For example: in the PersonInfo request, you only need the PersonId and the Company elements in the request schema.

4. Read in the Response Schema (File/Open) and Modify its structure. Depending on the service type, you'll want to modify the contents of the Response Schema. This is usually required when the service is an "Add" or "Delete" service, which returns very few input elements. In such cases you'll delete most of the elements on the response schema and only leaves the necessary elements required by the requester of the service.

Adding an Element/Attribute

Usually, you won't have to add element or attributes to a schema. However if the schema already exists and you want to add an element/attribute, you can follow this procedure. Be aware that any element/attribute added here must also exist on the xml metainfo.

- Select the element's node on the TreeView.

- Right click on it and select the 'Add Element' or 'Add Attribute' option in the pop-up menu

- Enter the element/attribute name in the prompt dialog box and click OK.

Removing Elements/Attributes

When generating a schema using one of the wizards, the generated schema may contain information that you do not want to publish as part of the service, or is not required for a particular service. You can remove elements/attributes from the schema, and though these elements/attributes may still exist on the service they are not seen by the XAI service using this schema. To remove an element or attribute:

- Select the node to be removed.

- Right click and select "Delete" from the popup menu.

Renaming an Element

To rename an element:

- Select the element's node on the TreeView.

- Right click it and select the Rename option in the pop-up menu

- Enter the new name in the prompt dialog box and click OK.

Note: The information in this table is cached by the XAI server and by the MPL server. Changes to values in this table do not affect the runtime copy of these servers. Refer to XAI Command for information about refreshing a schema.

Validating a Schema

CAUTION:

This schema validation is part of a separate legacy tool that is no longer recommended. The documentation remains for upgrade purposes

Although a schema is validated against the metainfo XML file when it is read into the editor or before it is saved, you can perform the validation at any time while the schema is being edited. To validate a schema, click on the toolbar "Validate" button . If the schema fails to validate the schema errors dialog is displayed.

When the editor fails to validate a schema against the xml metainfo file, it pops up a dialog that lists the errors found in the schema definition. These errors may be of two types:

- An element or attribute in the schema could not be found in the xml metainfo file. You can click Remove to remove the element from the schema.

- The data type of an attribute does not match the one defined in the metainfo file. You can click Correct, and the editor fixes the data type so it does match.

The Correct All button can be used to correct all fields that have data types that do not match the one in the XML metainfo file.

Note: Correcting errors does not save the schema definition into a file. You have to save it manually.

If you Exit without correcting the errors, the schema displays with the mismatch information highlighted in red.

Registering a Service

Before a service can be used it must be defined in the XAI Inbound Service table in the XAI registry. A service can be registered in the XAI registry directly from the schema editor. Go to the menu item 'Register Service' in the 'Schemas' menu. The Register service UI page appears. Fill in the required fields.

Note: The registry entry for the service can be later modified using the XAI Inbound Service page.

Testing a Schema

The XAI schema editor provides a testing option.

Note: Testing in your product. You may also test your schemas and your services using XAI Submission.

System Wide Functions for Schema Editor

Because the schema editor is in an application outside of the standard products, this section introduces some general functions related to the application.

Next in This Section

- Application Standards

- The File Menu

- The View Menu

- The Schemas Menu

- The Options Menu

- The Tools Menu

Application Standards

- The schema editor is a Multiple Document Interface (MDI) windows application. It may contain multiple active windows. You may jump from one window to the other using the Window menu option.

- The Editor window is always active. Closing the schema editor window quits the application.

- In the Editor window, a splitter bar is available to resize the schema tree view horizontally.

- Actions may be performed using menu items or by clicking on toolbar buttons.

- All messages are displayed on a status bar at the bottom of the screen. Some may also be displayed using message boxes.

The File Menu

Use the File menu to open existing schemas and to save a schema to a file.

Connect — Connects to the database.

Open — Loading an existing schema into the editor

You can read an existing schema into the editor.

1. Click on the Open toolbar button or select the File/Open menu option.

2. A file selection dialog is shown. Select the schema file name.

3. The editor first validates the schema against the xml metainfo file. If it fails to validate it shows the Schema Validation Errors dialog. Refer to Validating a schema for more information.

Save — Save the current schema to a file. Using the current file name.

To save a Schema, click on the Save toolbar button, or select the File/Save menu option. When you save a schema, the editor first attempts to validate the schema. If it fails to validate it against the XML Metainfo file, you are prompted to save it with inconsistency errors or to return to the editor.

Save As — Save the current schema to a file. Use a different file name.

Save As ResponseSave a copy of the current schema to a file as a response schema. Use a different file name.

The View Menu

Use the view menu to perform actions on the Tree View nodes or to view errors. The following menu options are available:

Expand All — Expand all nodes in the Tree View

Collapse All — Collapse all nodes in the Tree View

Expand Branch — Expand the selected node and all the node's children

Search (Ctrl+F) — Find a node with a node name containing a given string

Search Again (F3) — Find the next node with containing the search string

View Schema Errors — Display the Schema Validation Errors dialog.

Web Browser — Display the current schema definition on a web browser page

The Schemas Menu

Use the Schemas menu to create, test, validate and register schemas.

- To create schemas from various sources use the Create menu.

- To validate a schema select the Validate option (Ctrl+V).

- To create a sample instance and test the schema, select the Test option (Ctrl+T).

- To create an entry in the service registry for a service represented by the current schema, select the Register Service option (Ctrl+R). Refer to Registering a Service for more information.

The Options Menu

Always Save As W3C — Turn on this option to save schemas in W3C format by default instead of XDR format.

Always Save As DTD — Turn on this option to save schemas in DTD format by default instead of XDR format.

Preferences

The following options may be set on the preferences dialog (Select Options and then Preferences):

- The Default Date Time Format - used for schema date fields

- The default Schema Directory - used to read/save schemas

- The default Metainfo Directory - used to create/validate schemas

- The XAI Servlet URL - used when executing requests from the test schema dialog.

- The Default Account Id - used when generating sample instances of a schema

- Language - used to access language specific data

The Tools Menu

Schemas tools can be invoked from the Schema Editor Tools menu.

Converting Schemas to a W3C compatible schema — Schemas generated in the Microsoft BizTalk-compatible format (XDR format) may be saved in a format compatible with the October 2000, W3C XML schema standard. To save a schema in a W3C format:

- Select Convert to W3C from the Tools menu. The Convert to W3C dialog box appears.

- Select the schema(s) to be converted. Multiple schemas may be converted in a single step.

- The name of the W3C schema is the same name as the schema but with an ".xsd" file extension, and is saved to the same directory as the original schema.

- Click Convert.

Converting Schemas to a DTD — Schemas generated in the Microsoft BizTalk-compatible format (XDR format) may be saved as a DTD.

- Select the Convert to DTD option from the Tools menu. The convert DTD dialog box appears.

- Select the schema(s) to be converted. Note that multiple schemas may be converted in a single step.

- The name of the W3C schema is the same name as the schema but with a ".dtd" file extension, and is saved to the same directory as the original schema.

- Click Convert.

Validating multiple schemas — The schema validation tool can be used to validate the correctness of an XAI schema when compared to the metainfo xml definition used to generate the schema. For each validated schema, the validation tool scans the list of elements/attributes and compares them with those defined in the XML metainfo file. Select Validate Schemas in the Tools menu.

- The Validate Schema dialog box appears.

- The left list box is used to select the directory where the schemas to be validated are stored. By default this is the Schema Directory as defined in the preferences.

- On the right, the list of schemas is displayed on a grid.

- Multiple schemas may be validated in a single step.

- To select a schema click on the left button (the first column in the row).

- To select multiple schemas, hold the Ctrl key and select the required schemas.

- Click Validate Schemas.

- The schema grid is updated. When an attribute defined in the schema is missing from the metainfo file or when the properties of the element do not match defined in the metainfo, a button is displayed at the right of the schema name. Clicking on the edit button loads the schema into the editor and displays the Schema Validation Errors dialog for that schema. You can correct the schema and save it. Refer to Validating a schema for more information.

Setting Up Your XAI Environment

This section describes the control tables available to administer your XAI environment.

Next in This Section

- Message Class

- XAI Envelope Handler

- Setting Up Your Registry

- XAI Route Type

Message Class

The Message Classes are references to actual Java classes. The Message Class defines the Java class used to implement Receivers, Senders, Adapters and Executers. This information is provided with the system and does not need to be modified for a specific installation.

To view a Message Class, open Admin > XAI > Message Class.

Description of Page

The Message Class and Description are unique identifiers of the Message Class. The Class Definition indicates the Java class, implementing the adapter, receiver, sender or executer.

Owner indicates if this Message Class is owned by the base package or by your implementation ( Customer Modification). The system sets the owner to Customer Modification when you add a Message Class. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_CLASS.

XAI Envelope Handler

To view your envelope handlers, open Admin > XAI > XAI Envelope Handler. This information is provided with the system and does not need to be modified for a specific installation.

Description of Page

Enter a unique XAI Envelope Handler ID and Description.

Indicate whether the Envelope Type is Custom SOAP Envelope, Default (no SOAP environment) or SOAP Envelope. Note that the values of Siebel Integration Message and Siebel VBC are not supported.

When the envelope type is SOAP Envelope, indicate the Envelope URI.

Owner indicates if this XAI envelope handler is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add an XAI envelope handler. This information is display-only.

Setting Up Your Registry

The following section describes the control tables that are logically considered part of the XAI Registry.

Next in This Section

- XAI JDBC Connection

- XAI Format

- XAI Adapter

- XAI Executer

- XAI Group

- XAI Receivers

- XAI Inbound Services

XAI JDBC Connection

To view an XAI JDBC Connection, open Admin > XAI > XAI JDBC Connection.

Description of Page

Enter a unique XAI JDBC Connection and Description.

Use the Connection Type to indicate how the JDBC connects to a database. The following connection types are valid:

- Oracle Defined Connection indicates the connection is to an Oracle database through a JNDI entry.

- DB2 Defined Connection indicates the connection is to a DB2 database through a JNDI entry.

- JNDI Defined Connection indicates the connection is using the MQ series classes implementing JMS.

- Determined by parameter file indicates that the connection information should be determined by looking at the parameters defined at Installation.

For connection types of Oracle or DB2, use the JDBC URL to indicate URL of the database connection to be initialized at XAI/MPL startup time. Indicate the Database User and Database Password required for accessing the database. The JDBC connection URL can either be a Type 2 or a Type 4. For example:

- Type 2: jdbc:oracle:oci8:@CD200ODV

- Type 4: jdbc:oracle:thin:@myhost:1521/ CD200ODV

For a connection type of Determined by parameter file, indicate the parameter substitutions, which should be accessed from the parameter file for the JDBC URL, database user and database password, for example, @JDBCURL@, @DBUSER@ and @DBENCPASS@.

When the connection type is JNDI, indicate the JNDI Server and the JNDI Data Source name as defined in the JNDI.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_JDBC_CON.

XAI Format

Open Admin > XAI > XAI Format to define the various formats.

Description of Page

For each new format, specify a unique XAI Format name and Description.

Indicate whether the Format Type is a Currency formatting string, a Date/Time formatting string, a Phone formatting string or a Text formatting string.

Finally, indicate the Format Expression, which defines the formatting pattern to be applied.

Owner indicates if this format is owned by the base package or by your implementation ( Customer Modification). The system sets the owner to Customer Modification when you add an XAI format. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_FORMAT.

XAI Adapter

To define a new adapter, open Admin > XAI > XAI Adapter.

Description of Page

Indicate a unique Adapter Name and Description.

Indicate the Message Class, which is the name of the Java class, implementing the adapter. The class should be one that is defined for an adapter. The adapter classes provided with the product are BASEADA- Core Adapter, BUSINESSADA- Business Requests Adapter and XAICMNDADA- XAI Command Adapter. Note that the values SIEBELADA and STGUPADA are no longer supported.

Fastpath: Refer to Message Class for more information.

The following fields are not applicable for the BusinessAdapter adapter.

Use the JNDI Server to indicate the name of the WebLogic JNDI server running your product. Refer to JNDI Server for more information.

Indicate the Default User to be passed to your product server when this adapter is executed.

Note: If the XML request is sent over an HTTP connection, which has been authenticated, the authenticated User Id is passed to your product.

The Default Date format and the Default DTTM (date / time) Format specify date and date/time formats to use when a schema does not explicitly indicate formats.

Owner indicates if this XAI adapter is owned by the base package or by your implementation (Customer Modification). The system sets the owner to Customer Modification when you add an XAI adapter. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_ADAPTER.

XAI Executer

To define a new Executer, open Admin > XAI > XAI Executer.

Description of Page

Enter a unique Executer ID and Description.

Indicate the Message Class for this executer. The class should be one that is defined for an executer. The executer class provided with the product is XAIURLEXEC- XAI Executer.

Indicate the appropriate Executer URL.

Owner indicates if this XAI executer is owned by the base package or by your implementation ( Customer Modification). The system sets the owner to Customer Modification when you add an XAI executer. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_EXECUTER.

XAI Group

XAI groups are used to process XML files, which contain a collection of XML messages to be uploaded in batch.

Next in This Section

- XAI Group - Main

- XAI Group - Attachments

- XAI Group - Rules

XAI Group - Main

To define your XAI groups, open Admin > XAI > XAI Group.

Description of Page

Enter a unique Group and Description for the XAI Group.

Indicate the Parser used for this group. Possible values are Dom Parser and StAX Parser.

Note: Dom Parser reads the full XML document into memory and therefore is not ideal for larger XML documents.

Indicate the XPath and XPath Value, which an XML file receiver uses to identify which group a given XML file belongs to.

- For StAX Parsers the XPath is limited to the root element.

- For Dom Parsers, the XPath supports defining elements at a lower level than the root element.

XAI Group - Attachments

Open Admin > XAI > XAI Group and navigate to the Attachments tab to define attachments for your group.

Description of Page

For each entry in the attachments collection, indicate the Sequence and the Root Element. Use Include Elements to indicate if Parent elements should be included along with the current element when applying the XAI rules.

Fastpath: Refer to XML Message File for more information about how this is used.

XAI Group - Rules

Open Admin > XAI > XAI Group and navigate to the Rules tab to define rules for your group.

Description of Page

For each entry in the rules collection, indicate the Sequence, the Priority, the XPath name and XPath Value and the XSL File Name.

Note: Include Parent. If your attachment indicates that Parent elements should be included, be sure that the parent element is included in the XPath defined here.

Fastpath: Refer to XML Message File for more information about how this is used.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_RGRP.

XAI Receivers

Next in This Section

- XAI Receiver - Main

- XAI Receiver - Context

- XAI Receiver - Response

- XAI Receiver - Groups

XAI Receiver - Main

To define your XAI receivers, open Admin > XAI > XAI Receiver.

Description of Page

Enter a unique Receiver ID and Description for the XAI Receiver.

Indicate the Message Class for this receiver. The class should be one that is defined for a receiver. The receiver classes are DWNSTGRCVR- Download Staging receiver, FILESCANRCVR- Upload Files from a directory, JMSRCVR- JMS Queue receiver, OUTMSGRCVR- Outbound Message receiver, STGCTLRCVR- Staging Control receiver, STGRCVR- Staging Upload Receiver and TPCRCVR- JMS Topic receiver, XMLFILERCVR- XML File receiver.

Fastpath: For more information, refer to Designing XAI Receivers about different types of receivers.

Indicate whether or not this receiver is currently Active.

Identify the Executer ID. Select the XAILOCAL executer if the Message Class for this receiver is STGCTLRCVR. Select the BYPASSXAI executer if the Message Class for this receiver is OUTMSGRCVR. For all other receivers select the XAIURL executer. For more information, refer to XAI Executer.

Indicate whether the MSG Encoding is ANSI message encoding or UTF-8 message encoding.

The Read Interval indicates the number of seconds between read cycles.

Start At Time and Duration are not currently in use.

If the Message Class for this receiver is FILESCANRCVR, STGRCVR, STGCTLRCVR or XMLFILERCVR, indicate the XAI JDBC Connection.

Fastpath: Refer to XAI JDBC Connection for more information.

Turn on Sequential Execution if the received requests should be processed in sequential order (instead of multithreaded). If this value is turned on then XAI staging control records created by this receiver are marked for sequential execution.

JMS Information

The following information is only available if the Message Class is JMSRCVR or TPCRCVR.

Indicate the appropriate JMS Connection

Fastpath: Refer to JMS Connection for more information.

Indicate the appropriate JMS Queue.

Fastpath: Refer to JMS Queue for more information.

Indicate the appropriate and JMS Topic.

Fastpath: Refer to JMS Topic for more information.

File Information

The following information is only available if the Message Class is FILESCANRCVR or XMLFILERCVR.

Use the Scan Directory to indicate where to look for new files.

In Scan File, indicate the file pattern. All files with names matching the pattern are uploaded into the staging upload table. For each file found, a record in the staging control table is created.

CAUTION:

WARNING. MPL expects all files conforming to the Scan File pattern to be complete. If a file is in the process of being copied into the scan directory and its name conforms to the naming pattern, MPL still attempts to process it and may issue an error for the incomplete file. It is suggested that files first be copied into the scan directory with a different name that does not conform to the naming pattern, for example filename.xml.inprocess. Once the file copy/transfer is complete, rename the file to one that conforms to the naming pattern, for example, filename.xml.

The following information is only available if the Message Class is FILESCANRCVR.

Use the XAI In Service Name to indicate how the records in the file are mapped and how they are transformed to match a system service request structure.

XAI Receiver - Context

Open Admin > XAI > XAI Receiver and navigate to the Context tab to define context for your receiver.

Description of Page

The Context collection enables you to define a collection of Context Types and Context Values defining. Use this collection when you need to store an attribute of a receiver that is not catered for in the current table.

Note: The values for the Context Type field are customizable using the Lookup table. This field name is RCVR_CTXT_FLG.

XAI Receiver - Response

Open Admin > XAI > XAI Receiver and navigate to the Response tab to define where to send responses to requests made by this receiver. Refer to Designing Responses for a Receiver for more information.

Description of Page

The response collection enables you to define the destination (Message Sender) where responses to a request may be sent under various circumstances (Event). The events currently defined with the product are All events, Message executed OK, Application Error, System Error.

Note: The values for this field are customizable using the Lookup table. This field name is ON_EVENT_FLG .

XAI Receiver - Groups

Open Admin > XAI > XAI Receiver and navigate to the Groups tab to the valid XAI groups for an XML file receiver.

Description of Page

This collection is only available if the Message Class is XMLFILERCVR.

For each entry in the Group collection, indicate the Priority and the Group. Refer to XAI Groups for more information about defining groups.

Where Used

Receivers are used by the XAI server and by the MPL server to process messages sent to the system from various sources.

XAI Inbound Services

The XAI Inbound Services section in the registry is the main section of the registry. It is used to define the service characteristics. Basically, a service is defined by an Adapter responsible for executing the service, a pair of XML schemas and connection attributes. The Adapter defines the interface with the target application server, while the schemas define the structure of the request XML document expected by the service and the structure of the response XML document generated by the service.

Next in This Section

- XAI Inbound Service - Main

- XAI Inbound Service - Staging

- XAI Inbound Service - Parameters

XAI Inbound Service - Main

To update an inbound service, open Admin > XAI > XAI Inbound Service.

CAUTION:

Important! When adding new inbound services, carefully consider the naming convention of the XAI In Service Name. Refer to System Data Naming Convention for more information.

Description of Page

Define a unique XAI In Service Name. This information is used in the system to identify the service. The service name is also the first XML element after the <Body> element in the XML request/response document. The system generates a unique XAI Service ID, which serves as the primary key.

Owner indicates if this XAI inbound service is owned by the base package or by your implementation ( Customer Modification). The system sets the owner to Customer Modification when you add an XAI inbound service. This information is display-only.

Indicate the Adapter, which defines the interface with the target application server.

Fastpath: Refer to XAI Adapter for more information.

If adapter for this service should invoke a system service, then indicate the appropriate Service Name.

Fastpath: Refer to Service Program for more information about defining services.

If adapter is the base package Business Adapter then Service Name does not appear. Instead, use Schema Type to indicate the type of object this service invokes and Schema Name to reference the object to invoke. Using this adapter, you may set up service to invoke business objects, business services and service scripts.

Fastpath: Refer to Designing XAI Adapters for more information about the Business Adapter.

Web Service Category is visible if the XAI inbound service is linked to one or more web service categories.

Use the Description and Long Description to describe the service.

Check the Active switch if this service is enabled and available for execution. If this switch is unchecked, then the service is defined in the registry, but not yet available for public use.

Check the Post Error switch to support inbound message error handling for messages that are not processed via the staging upload table.

Check the Trace switch if you would like the trace to be on for this particular service. If the general trace option is not activated, you can force a trace for a particular service.

Fastpath: Refer to Server Trace for more information about trace functionality.

When the Debug switch is checked, debug information is generated on the XAI console when this service is executed. The debug information can be useful to resolve problems.

Schema Definitions

Note: Request Schema and Response Schema are not applicable to services invoking schema-based objects. They do not appear when the Business Adapter is used.

The next two properties define the request and response XML schemas. The schemas were created using the Schema Editor and are SOAP compatible. The schema XML files are expected to be stored in the Schemas Directory on the Web server running the XAI server.

The Request Schema is the XML schema defining the service request. The request sent to the server must adhere to the schema definition.

The Response Schema is the XML schema defining the service response. The response generated by the XAI server corresponds to the response schema definition.

The same service may perform several actions on a business object. Use the Transaction Type to define the default action performed by a service. The transaction type can be provided when invoking a service, by dynamically specifying a transaction type attribute on the Service element of the XML request. This field may take the following values: Read, Add, Change, Update, Delete, List and Search.

Note: The difference between Change and Update is that for Change, all field values must be passed in with the request. Field values that are not passed in to the request are set to null. For Update, you need only pass the primary key field values and the values of the fields to be updated. All other fields retain their existing values.

Services, which perform a Search, may allow searching based on different criteria. When the Transaction Type value is Search, use the Search Type to define the default search criteria. The possible values are Main, Alternate1, Alternate2, Alternate3, Alternate4, Alternate5 and Alternate6.

Note: This is a default definition only and it may be overridden at run time when the service is invoked. To override the search type at run time, you should specify the searchType attribute on the Service element of the XML request.

XSL Transformation Definitions

Sometimes, the XML request document does not conform to the request schema, or the response document expected by the service requestor is not the one generated by the adapter. In such cases the request and/or the response documents must be transformed. The XAI server supports transformation through XSL transformation scripts. Transformation scripts may be applied to the request before it is passed to the adapter or applied to the response document before it is sent to the service requestor.

The Request XSL is the name of the XSL transformation to be applied to the request document before processing it. The transformation is usually required when the incoming document does not correspond to the XAI service request schema therefore it has to be transformed before it can be processed by the adapter.

The Response XSL is the name of the XSL transformation to be applied to the response document when the requester of the service expects the response to have a different XML document structure than the one defined by the response schema for the service.

Click the WSDL URL hyperlink to launch a separate window that contains the WSDL definition for the inbound service. Note that the server name and port number for the URL are built using a setting in the common properties file using the XAI HTTP Caller URL setting.

Note: Refer to WSDL Catalog for information on how to obtain the WSDL catalog for all XAI Inbound Services.

XAI Inbound Service - Staging

The staging tab is used to define parameters for services that use the Staging Upload adapter.

Fastpath: Refer to XAI Upload Staging for more information.

Open Admin > XAI > XAI Inbound Service and navigate to the Staging page to define attributes for your upload staging adapters.

Description of Page

Indicate the Staging File Type to be processed by the staging upload service. Possible values are Comma Delimited file, Database Extract and Sequential file.

The format of the records in the input file are not in an XML format and do not correspond to an XAI service schema. As a result, the input record must be transformed into an XML message that conforms to an XAI service request schema. Enter the Record XSL, which indicates the XSL transformation script used to transform the input record into the appropriate XML message.

For sequential files and Comma delimited files, indicate the Input File Name to be processed.

Note: This parameter can be overridden in the Staging Control table when a request to execute such a service is made.

When the service takes its input from a Database extract, indicate the JDBC Connection used to connect to the database that contains the input data.

Note: If this value is not populated XAI uses the default JDBC connection, which is the current product database.

Fastpath: Refer to XAI JDBC Connection for more information about defining these values.

Use the Interface Name to provide a description of the interface being implemented through this service.

XAI Inbound Service - Parameters

This tab enables you to define parameters that are used as selection criteria by the DB Extract staging upload service.

Open Admin > XAI > XAI Inbound Service and navigate to the Parameters page.

Description of Page

The Parameters that were defined under the Request element in the schema are displayed here. They are used to drive the extraction process. This tab only displays the list of parameters. The values for these parameters can later be entered when the control record to invoke this service is created.

Fastpath: Refer to Staging Control Parameters for more information.

Owner indicates if this XAI inbound service is owned by the base package or by your implementation ( Customer Modification). The system sets the owner to Customer Modification when you add an XAI inbound service. This information is display-only.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_XAI_IN_SVC.

Note: The information in this table is cached by the XAI server and by the MPL server. Changes to values in this table do not affect the runtime copy of these servers. Refer to XAI Command for information about refreshing a service.

XAI Route Type

Refer to the documentation for your product to find out if XAI Route Type is supported.

Running Your XAI Environment

Note: The XAI functionality is legacy functionality and not recommended for new implementations. This information remains in the documentation for upgrade purposes. Refer to Incoming Messages and Outgoing Messages for information about the recommended features for supporting sending and receiving external messages.

The XML Application Integration (XAI) module provides the tools and infrastructure that businesses require for integrating their third-party systems with the application.

This section describes the pages used to manage incoming and outgoing information via the XAI tool.

Next in This Section

- XAI Staging Control

- XAI Upload Staging

- Uploading XAI Staging Records

- XAI Upload Exception

- XAI Download Staging

- XAI Download Exception

XAI Staging Control

Refer to Staging Control for more information about the purpose and functionality of this page.

Navigate to this page using Menu > Integration > XAI Staging Control.

Description of Page

The XAI Staging Control ID is a system generated unique identifier of this record.

The XAI Staging Control Status indicates the current state of this record.

Pending This status indicates that this record needs to be processed.

In Progress This status indicates that the background process, which uploads the staging records, is currently processing this record.

Error This status indicates that the background process found a problem with this record. When the data related to this record has been fixed, change the status back to Pending so that it will be processed again.

Complete This status indicates that this record has been processed.

The Number of Uploaded Records indicates how many XAI staging records related to this staging control record were uploaded.

The Run Date Time indicates the date and time this record was processed by the upload process.

The User, who created this staging control record, is captured.

If the data to be uploaded is found in a file, indicate the Upload File Name, which should include the directory path and file name.

Note: Character Encoding. Refer to Sequential Input File for information about specifying character encoding for a file.

Note: Complete File. MPL expects this file to be complete. If the file is in the process of being copied into the directory, MPL still attempts to process it and may issue an error for the incomplete file. The staging control record should only be created once the complete file is ready for upload.

Enter a description of the XAI Interface Name. This is simply information and is not used by the system.

Turn on Sequential Execution if you want the XAI upload staging records related to the staging control record to be processed in sequential order (instead of multithreaded).

The XAI Service ID tells the system how to create the XML related to the XAI upload staging record to be created. In Oracle Utilities Customer Care and Billing, for example, XAI Services with an adapter type of CISStagingUpload may be indicated here.

Fastpath: For more information about XAI services, refer to XAI Inbound Service.

Use the Comments to provide free format information related to this staging control record.

The collection of staging control parameters is used to define selection criteria when the staging control is accessing data from a database table. The Staging Control Parameter defines the field used in the WHERE clause and XAI Staging Control Parm Value defines the value to be used in the WHERE clause.

Refer to Staging Control Parameters for more information.

The Message collection displays any completion messages for XML requests related to the staging control record.

XAI Upload Staging

The XAI upload page allows you to view the details or to fix errors for a request in the Staging Upload table. This page displays the text of the XML request document linked to the upload.

Next in This Section

- XAI Upload Staging - Main

- XAI Upload Staging - Response

XAI Upload Staging - Main

To view or modify an XAI upload document, navigate to Menu > Integration > XAI Upload Staging and navigate to the main tab.

Description of Page

The XAI Upload Staging ID is a system assigned identifier of the XAI upload staging record.

The Application Service identifies the internal system service called by the XAI tool to load/update the system data.

Note: The upload process does not use this. Rather, the application service is part of the XML Request. This field is used to help in searching for XAI Upload records.

The XAI Staging Control ID related to this XAI upload staging record is displayed.

The status of the upload is indicated by the XAI Upload Staging Status. Values are Pending, In Progress, Complete, and Error. If the record is in error, an error is written to the XAI Upload Exception table.

Create Date/Time indicates when the record was posted.

Completion Date/Time indicates when the work was completed.

If this XAI upload staging record is a response to an XAI Download Staging record, information about the related download staging record is displayed.

If there is an error with this record, you will see the error Message associated with this record. The message area is suppressed if there are no problems with the record.

Click the adjacent button to view the long explanation. The long explanation provides information about the cause of the error (and how to fix it).

The upload staging data appears in the XML Request text box.

XAI Upload Staging - Response

To view the response to a completed XAI upload staging document, navigate to Menu > Integration > XAI Upload Staging and go to the Response page.

Description of Page

The XAI Upload Staging ID is a system assigned identifier of the XAI upload staging record.

The system's response to the upload XML appears in the XML Response text box.

Uploading XAI Staging Records

Next in This Section

- Staging Control Layout

- Staging Control Parameters Layout

- Upload Staging Layout

- XMLUP-PR - Purge XAI Upload Objects

Staging Control Layout

In order to load XML requests from flat sequential files, comma separated value (CSV) files and from database tables, you need to create a staging control record. The name of this table is CI_XML_STG_CTL. The following table describes each column on this table.

Column Name

Length

Required

Data Type

Comments

XML_STG_CTL_ID

10

Y

N

This is the unique identifier of the record. This value does not have to be a random number, but it does need to be unique.

RUN_DTTM

26

N

Date/Time

Date and time this record was executed.

XAI_IN_SVC_ID

10

Y

A/N

This is the XAI service associated with this record. This service should have an adapter of CISStagingUpload.

XML_STG_FILE_NAME

250

N

A/N

This is the location and name of the file containing the data to be uploaded. This is used for comma delimited files and flat sequential files.

XML_INTFC_NAME

30

N

A/N

The name of the interface used to populate this table. This is simply information and is not used by the system.

XML_STG_STATUS_FLG

2

Y

A/N

Must be set to P (Pending).

NT_XID_CD

30

N

A/N

This field is not in use.

NT_UP_XTYPE_CD

30

N

A/N

This field is not in use.

USER_ID

8

Y

A/N

The ID of the user who created this record.

COMMENTS

254

N

A/N

Use the free format comments, if necessary.

NBR_RECORD_UPLD

10

N

A/N

Leave this blank. This will be populated by the process which creates upload staging records for this control record.

Staging Control Parameters Layout

If your staging control record should read a database table, the XAI service may include selection criteria in its WHERE clause. If that is the case, then your staging control record should populate the selection criteria. The name of this table is CI_XML_STGCTL_P. The following table describes each column on this table.

Column Name

Length

Req'd

Data Type

Comments

XML_STG_CTL_ID

10

Y

N

The unique identifier of the staging control record.

XML_STG_CTL_PARM

18

Y

A/N

Indicate the element in the WHERE clause whose value will limit the selection of records.

XML_STG_CTL_PVAL

250

Y

A/N

Use this to indicate the value used to limit selection of records.

Upload Staging Layout

You create an XAI upload staging record directly for each XML request you wish to make. The name of this table is CI_XML_STGUP. The following table describes each column on this table.

Column Name

Length

Required

Data Type

Comments

XML_STGUP_ID

15

Y

N

This is the unique identifier of the record. This value does not have to be a random number, but it does need to be unique.

APP_SVC_ID

20

Y

A/N

This is the foreign key to the application service table, and identifies the application service that is being requested.

COMPLETE_DTTM

26

N

Date/Time

Completion date and time.

CRE_DTTM

26

Y

Date/Time

Creation date and time.

RETRY_COUNT

3

Y

N

Number of retries to process the request.

XML_REQUEST

30,000

Y

A/N

The XML request document.

XML_RESPONSE

30,000

Y

A/N

The XML response document.

XML_STG_CTL_ID

10

Y

A/N

The id of the staging control record linked to this record.

XML_STG_STATUS_FLG

2

Y

A/N

Must be set to P (Pending).

XMLUP-PR - Purge XAI Upload Objects

Completed XAI upload staging objects should be periodically purged from the system by executing the XMLUP-PR background process. This background process allows you to purge all Completed XAI upload staging objects older than a given number of days.

We want to stress that there is no system constraint as to the number of Completed XAI upload staging objects that may exist. You can retain these objects for as long as you desire. However we recommend that you periodically purge Completed XAI upload staging objects as they exist only to satisfy auditing and reporting needs.

XAI Upload Exception

A record is written to the XAI upload exception table for every XAI upload staging record that is in error.

To view the messages associated with the exception records, schedule the TD-XAIUP background process. This process generates a To Do entry for every record in the XAI upload exception table.

After correcting the cause of the error, drill into the XAI Upload Staging page and change the status from Error to Pending and the system will attempt to process the record again.

XAI Download Staging

Next in This Section

- XAI Download Staging - Main

- XAI Download Staging - Request

- XAI Download Staging - Response

XAI Download Staging - Main

To view individual XAI download staging records associated with a notification download staging record, open Menu > Integration > XAI Download Staging.

Description of Page

XAI Download Staging displays information about the record.

The Download Staging ID and XAI Route Type are the primary identifiers for this record.

The XAI Download Status is displayed. The values are Pending, Complete, Canceled or Error. When a record is in Error, it is displayed on the XAI Download Exception table.

Values from the NDS record associated with this XAI download staging record are displayed including Service Provider, Notification Download Type, NT Download Status Flag, Retry Count and the Context collection.

XAI Download Staging - Request

To display the XAI Request built by the download staging receiver, open Menu > Integration > XAI Download Staging.

Description of Page

The XML Request built by the download staging receiver is displayed.

XAI Download Staging - Response

To display the Response to this request, open Menu > Integration > XAI Download Staging.

Description of Page

The XML Response to this message is displayed.

XAI Download Exception

A record is written to the XAI download exception table for every XAI download staging record that is in error.

To view the messages associated with the exception records, schedule the TD-XAIDN background process. This process generates a To Do entry for every record in the XAI download exception table.

Maintaining Your XAI Environment

This section describes various tools provided to enable your XAI administrators to more easily maintain your XAI environment.

Next in This Section

- XAI Submission

- Additional XAI Tools

- Server Trace

XAI Submission

This page exists for testing purposes. It allows you to create an XML request document and submit it to the system, to ensure that the XML has been built correctly.

Next in This Section

- XAI Submission - Main

- XAI Submission - Response

XAI Submission - Main

To submit an XML document for testing, navigate to Admin > XAI > XAI Submission and navigate to the main tab.

Description of Page

This page is used to test XML schemas, which are defined for the XAI tool. Enter an appropriate XML document in the XML Request field. Typically, you define the XML schema using the schema editor in the XAI application. Then you would copy and paste the document here, then modify the schema to enter actual data for testing purposes.

When you have entered the document, choose Save to submit this document to the system. Note that this request information is not saved anywhere. It simply calls the system with the appropriate service name and executes the XML request.

Navigate to the Response tab to view the response.

XAI Submission - Response

To view the response to a XML document for testing, navigate to the response tab.

Description of Page

After choosing Save on the main tab to submit a test for an XML request, the response to your request is displayed in the XML Response text box.

Additional XAI Tools

This section introduces some additional tools to help you maintain your XAI environment.

Next in This Section

- XAI Service Export

- XAI Service Import

- XAI Command

- MPL Exception

XAI Service Export

The service export page allows you to export the definition of an XAI Inbound Service to a file. This function may be helpful if you need to copy the definition of this service to a separate environment. To export a service, open Admin > XAI > XAI Service Export.

Description of Page

Upon entry into this page, you are provided with the current list of XAI In bound Services and their Description s. Use the XAI In Service Name search field to find the XAI service that you would like to export.

Use the Export? column to indicate which XAI service(s) you would like to export. Once you have selected your services, choose Save.

Note: If multiple services are selected, they are exported together into the same output file.

You are presented with the standard File Download dialogue where you can open or save the file.

XAI Service Import

The service import page allows you to import the definition of an XAI Inbound Service from a file into the XAI service table. This function may be helpful if you need to copy in the definition of this service from a separate environment. To import a service, open Admin > XAI > XAI Service Import.

Description of Page

Upon initial entry into this page, you are provided with an input field, where you can enter the file name to import. Click Browse to search for the desired file in a directory.

Once the file is identified, click Read File, to read in the contents of the file.

Note: The format of the file must include tags indicating the column names for XAI Inbound Service table along with the values of the columns. For an example of how the format should be, simply go to the XAI Service Export page, export a Service and view the format of the resulting file.

Once the file has been read in, the list of XAI services found defined within the file is displayed in the Import grid, identified by their XAI In Service Name and Description. In the Import? column, indicate which services to import.

If a service with this service name already exists in the table, you must check the Overwrite Existing switch in order to indicate that the imported file information should replace the current service. An XAI Inbound Service that is provided as part of the system (i.e., with an owner of Base Product) may not be overwritten.

Click Save to proceed with the import. If any problems are found, information is displayed in the Message Text column.

XAI Command

Use the XAI Command page to send commands to the XAI and MPL server. To execute a command, open Admin > XAI > XAI Command.

Description of Page

The following operator commands may be sent to the XAI server. For each of these commands, you may check Also Sent to MPL URL, in which case, the command is also sent to the MPL server. You need to indicate the URL of the MPL server.

Display Registry Use this command to display the current registry information that the XAI instance is running with.

Refresh Code and Description This is related to an attribute in the schema editor where you may indicate that the description of a control table code should be returned along with the code itself. This information is kept in cache memory in the server. As a result, changes made to descriptions have no effect on the runtime server. This command clears the cache of control table codes and descriptions accessed by the server.

Refresh Registry The registry contents are kept in cache memory in the server. As a result, making changes to the registry control tables has no effect on the runtime server. Use this command to refresh the contents of the registry cache with the new values in the registry control tables. The command reloads all registry control table data into the server.

Refresh Schema Schema definitions are stored in cache memory on the XAI server. As a result, modifying a schema definition has no effect on the runtime server. To refresh schema definitions, use the Refresh Schemas command.

Refresh Service Service definitions are stored in cache memory on the XAI server. As a result, modifying an XAI inbound service definition has no effect on the runtime server. To refresh service definitions, use the Refresh Service command. You are prompted to indicate which service to refresh.

Refresh XSL XSL Transformation script definitions are stored in cache memory on the XAI server. As a result, modifying an XSL transformation definition has no effect on the runtime server. To refresh XSL transformation definitions, use the Refresh XSL command.

Trace On Use this command to start the XAI server trace.

Trace Off Use this command to stop the XAI server trace.

XAI Trace Clear Use this command to clear the contents of the trace file.

XAI Trace Swap Use this command to rename the current trace file by appending the date and time to the end. A new trace file is then created with the name as defined in the Message option page.

The following operator commands can be sent to the MPL server. You must set the URL of the MPL server first.

MPL Refresh Executer Executer definitions are stored in cache memory. As a result, adding or modifying executer definitions has no effect on the runtime server. Use this command to refresh executer definitions. You are prompted to indicate the executer to refresh.

MPL Refresh Receiver Receiver definitions are stored in cache memory. As a result, adding or modifying receiver definitions has no effect on the runtime server. Use this command to refresh receiver definitions. You are prompted to indicate the receiver to refresh.

MPL Refresh Sender Sender definitions are stored in cache memory. As a result, adding or modifying sender definitions has no effect on the runtime server. Use this command to refresh sender definitions. You are prompted to indicate the sender to refresh.

MPL Start Receiver Use this command to start a particular receiver. You are prompted to indicate the receiver to start.

MPL Stop Use this command to stop all MPL activity. It stops all receivers and waits for all executers and senders to complete.

MPL Stop Receiver Use this command to stop a particular receiver. You are prompted to indicate the receiver to stop.

MPL Trace On Use this command to start the MPL server trace.

MPL Trace Off Use this command to stop the MPL server trace.

When you have chosen the appropriate command and indicated any extra information, click Send Command to send the command to the server(s).

If you have sent a command to the XAI Server, then the bottom portion of the screen displays the response in the XAI Response. If you have sent a command to the MPL Server, then the bottom portion of the screen displays the response in the MPL Response. If you have sent a command to both servers, the bottom portion of the screen displays both responses.

MPL Exception

The MPL Exception table is used by the MPL to keep information about requests that resulted in a system error. These are errors that occurred inside the MPL. For example, if the MPL fails to send a request to XAI (maybe WebLogic is down), this is a system error, which would be logged in the MPL exception table.

There are errors that are defined recoverable. This means that the MPL will retry the action that failed, according to the parameters it received.

Server Trace

The XAI server traces every request and response. The requests/responses are written to a trace file on the server. The trace file may be viewed using the Trace Viewer.

Next in This Section

- Starting the Trace

- Stopping the Trace

- Trace Viewer

Starting the Trace

The log starts automatically based on definitions in the Message Options in the traceType and traceFile options. To manually start the trace:

- Navigate to Admin > XAI > XAI Command.

- Select the Start Trace command from the command dropdown

- Click Send Command

Stopping the Trace

- Navigate to Admin > XAI > XAI Command.

- Select the Stop Trace command from the command dropdown

- Click Send Command

Trace Viewer

Use the Trace Viewer utility to view the log file. The Trace Viewer is installed when you install the XAI client tools. It can be found in the XAI program group under Start/Programs.

Next in This Section

- Main Page

- Statistics Page

Main Page

When the Trace Viewer starts, select a trace file to view. A trace file may be opened in one of two ways:

- To open a trace file directly from its location on the web application server, use the File, Open HTTP menu item and provide the appropriate URL.

- To open a trace file on the local/network file system use the File, Open menu item

Description of Page

Once a trace file is opened, it displays a list of all the requests on the left side including the Service Name, the Start Time and the End Time.

To display the XML contained in the request and response entries for a displayed request, select a request entry.

Filtering Options

Since the trace file may contain a very large number of messages, the trace viewer limits the number of messages that can be displayed. It does that by displaying messages traced within the last x number of Minutes, Hours or Days.

Use the Max Messages to limit the number of messages displayed.

Note: Default Note. By default, the Trace viewer displays the first 200 messages in the trace file.

To view only errors in the trace, check the Show only Errors option.

Note: Refresh Display. After changing any of the above filtering options, click the refresh button in order to redisplay the request entries based on the new options.

The First Message Found field indicates the date and time of the earliest entry in the trace file.

Viewing as Text

To view the trace file as text rather than viewing each entry in its XML format, use the View, As Text menu option. The contents of the trace file are displayed in text format in a separate window.

Statistics Page

Use the View, Statistics menu item to view the statistic page, which displays performance statistics about the XAI services that were executed in the XAI trace file.

For each type of XAI Service and transaction type, it displays the following information based on the requests traced in the XAI trace file:

- The Service Name with the transaction type in parentheses

- The Number of calls for this service in the listed trace records

- The Average duration Time (in seconds)

- The Max imum duration Time (in seconds)

- The Min imum duration Time (in seconds)

Note: Requests Included in Statistics. Only requests falling in the time selection criteria and listed on the main log viewer are processed for calculating the statistics.

To display a Duration Chart for a particular service, check the Service. A chart such as the one below is displayed.

Integrations

This chapter provides high level information about product integrations supported for all products that use Oracle Utilities Application Framework.

Next in This Section

- LDAP Integration

- Oracle Identity Manager Integration

- Batch Scheduler Integration

- Data Synchronization

- Analytics Integration

- Business Flags

LDAP Integration

Organizations commonly use a Lightweight Directory Access Protocol (LDAP) security repository as a source of security credentials. The system provides support for importing users and groups from an external LDAP repository into the product to populate Users and User Groups in the system. Once imported, all user and group functions are available. You can resynchronize your LDAP users and groups at any time.

Note: Import only. The system currently supports importing LDAP information. Exporting users and groups from the system to LDAP is not provided.

Note: Additional configuration. When importing new users and / or groups, additional configuration is needed in the base product. For example, after importing a new user group and its users, the user group configuration should be updated to define the valid application services for the user group. After importing a new user, additional configuration may be needed on the user such as valid To Do Roles, valid Home Page, etc.

Fastpath: Refer to Defining Security and User Options for more information about the application security and what it controls.

This section the functionality provided in the framework application that supports LDAP. Refer to the LDAP Integration white paper for more information about typical steps related to the full integration.

Next in This Section

- LDAP Integration Overview

- Configuring LDAP Integration

LDAP Integration Overview

This topic provides a high level overview of the integration process.

At a high level, the base product provides a process to import user group and / or user definitions from and LDAP repository. This is a one way integration.

- When importing a user, if it is not already found in the system, it will be added; otherwise its attributes will be updated according to the imported information.

- When importing a user group, if it is not already found in the system, it will be added; otherwise its attributes will be updated according to the imported information.

- When importing a user, its user group links will be updated as per the information in the import file. In addition, if there are any user groups linked to the user that are not found system, they will be added (however, the other users linked to that group in the LDAP repository will not be added as part of this step).

- When importing a user group, its user links will be updated as per the information in the import file. In addition, if there are any users linked to the user group that are not found system, they will be added (however, the other user groups linked to that user in the LDAP repository will not be added as part of this step).

- The import will not cause any deletions of the User or User Group to occur.

A Batch Process Initiates the Import

A batch process is used to initiate the import of information from the LDAP repository. F1–LDAP may be submitted ad hoc or may be set up in a scheduler to periodically re-sync the information from the LDAP repository into the application.

The batch process uses parameters to define how to connect to the LDAP repository. In addition, parameters are used to indicate which user or group is being imported.

Adjusting Data to Import

The system provides several mechanisms for adjusting data that is being added to the system:

- There is an LDAP Import Preprocess algorithm plug-in spot on the installation record. Algorithms plugged in here are called by the batch process prior to the add or update of any records. It may be used to make adjustments to the data before doing updates in the application.

- Specifically for creating or updating Users, the F1–IDMUser business object is used to add and create the user. The standard BO Preprocessing algorithm plug-in spot may be used to adjust data prior to creation.

- The LDAP mapping file supports some attributes to perform simple modifications to data.

- The transform attribute supports values to truncate values or to convert data to upper case.

- The autoGenerate attribute is specific to the User ID field. Setting this to true will trigger code that will automatically populate the User ID based on the user’s name. Refer to LDAP Mapping for more information.

Performing Additional Processing After Import

The system provides a plug-in spot on the installation record called LDAP Import. Algorithms plugged into this spot are called after users or user groups have been added or updated. It may be used to perform any extra processing that may need to be executed.

In addition, for any additional processing related to the creation or update of a User, the standard Business Object plug-ins may be used for the F1–IDMUser business object which the LDAP batch process uses to create or update users.

Configuring LDAP Integration

To interface the LDAP based security repository with the authorization component of the Oracle Utilities Application Framework product the following must be performed:

- The location and port number of the LDAP based security repository must be defined to in the JNDI Server.

- • The LDAP based security repository must be mapped to the Oracle Utilities Application Framework security model. This mapping is expressed as an XML file containing the LDAP query, rules and defaults used in the transformation.

- • The mapping file must be configured on the F1-LDAP batch job.

Define the JNDI Server

The first step in the configuration process is to define the location of the LDAP based security repository server so that the interface can connect to the physical attributes of the interface. This is done by creating a JNDI Server.

Note: The LDAP server is strictly not a JDNI source but is treated as a JNDI source for the integration.

Enter a reasonable JNDI Server name and description.

Populate the Provider URL using the format ldap://<hostname>:<portnumber> where <hostname> is the host of the LDAP server and <portnumber> is the port used for the interface.

For the Initial Context Factory, the interface uses the standard com.sun.jndi.ldap.LdapCtxFactory provided with java for the LDAP interface. If your vendor supplies a custom context factory it may be used. Refer to the documentation provided with your LDAP based security repository for further information.

Define Mapping

The critical component of the interface is a file that describes the mapping between the LDAP based security repository and the system’s security model. This file contains the mapping, rules and queries used by the LDAP batch program to provide the interface. The LDAP batch job includes the reference to the mapping file as a parameter. Refer to LDAP Mapping for more information on defining the mapping file.

Configure LDAP Batch Process

At this point, many parameters for the F1–LDAP batch control can be updated with system wide configuration.

- JDNI Server, User and Password may all be configured appropriately. Note that it is recommended that the Security setting for the Password be set to Encrypt.

- The LDAP Configuration File should be populated with the name and location of the LDAP Mapping file.

- If the LDAP service has any limitation to the number of objects that may be imported, configure the LDAP Query Page Size parameter to enable querying.

Note: Group and User Parameters. The assumption is that the Group or User input parameters are specific to a given import request and as such would not be populated as part of a configuration step.

Note: L2 Cache. The LDAP Import batch process requires the L2 Cache to be disabled since it needs to perform some updates in the outside of the worker threads. Any environment using LDAP Import must set spl.runtime.batch.L2CacheMode=OFF in the threadpoolworker.properties file. It is recommended to run the LDAP import in its own dedicated threadpoolworker.

Next in This Section

- LDAP Mapping

LDAP Mapping

An LDAP repository consists of multiple entries. Each entry represents an object in the directory that is identified by a Distinguished Name (DN) and may contain one or more attributes. In a typical LDAP repository there is usually an entry for users and an entry for groups. The connection between users and groups may be implemented in two different ways:

- The users belonging to a group are defined in a special multiple-value attribute on the Group entry.

- The groups to which a user belongs are defined in a special multiple-value attribute on the User entry.

The mapping between LDAP security objects and base security objects is stored in an XML document that can be processed by the LDAP import batch job. As part of setting up your system for LDAP import, you need to define this mapping. The base package provides a sample mapping file called ldapdef.xml that can be used as a starting point and changed per your business requirements and your particular LDAP repository.

Once you have defined the mapping XML document, this is configured as a parameter in the F1-LDAP batch job.

The XML structure:

- The LDAPEntry element maps the LDAP entries to system objects (User or Group). The mapping file must contain one and only one LDAPEntry element for User and one for Group.

- The LDAPCDXAttrMapping element within the LDAPEntry element maps attributes in the LDAP entry to attributes in the system object.

- The LDAPEntryLinks element describes objects linked to the LDAP entry. When mapping the user entity you need to describe how the groups the user belongs to are retrieved. When mapping the group entity you need to describe how the users contained in the group are retrieved.

The following table describes the attributes to define for each element.

Element

Attribute

Description

LDAPEntry

name

The name of the LDAP entry:

- Group

- User

baseDN

The base distinguished name in LDAP for this entry.

cdxEntity

The name of the base product entity to which the LDAP entry is mapped:

- Group

- User

searchFilter

An LDAP search filter that is used to locate LDAP entries. A %searchParm% string in that filter is replaced by the value from the user or group parameter from the F1-LDAP batch job submission.

Scope

Sets the scope of the search. Valid values are:

- onelevel (the value normally used)

- subtree

LDAPCDXAttrMapping

ldapAttr

The name of the LDAP attribute to be mapped. Note that this may be referenced more than once to allow one LDAP element to map to multiple base product elements. For example, if an email address should be used both for the Login ID and the Email Address.

cdxName

The name of the base product attribute to be mapped.

For User, this is the element within the F1-IDMUser business object.

For Group, this is either the ‘group’ or the ‘description’.

default

The default value that will be assigned to the element referenced in the cdxName attribute when one of the following occurs:

- The LDAP attribute contains a null or empty value

- The LDAP attribute does not exist or is not specified.

Default values are applied only when creating a new entity and are not applied to updated entities.

autoGenerate

Set this to true in order to turn on auto generation of the user ID. If this is true, the system will define the user id as <first initial of first name>+<last name> all uppercase, to a maximum of 8 digits. If an existing user is found for the generated ID, a number will replace the eight digit (or be appended to the end). The system will increment the number until a unique ID is found.

transform

Use this attribute to indicate if a transformation of the data should occur. Valid values: uppercase|truncate. Note that this attribute should not be used in conjunction with the autoGenerate attribute.

LDAPEntryLink

linkedToLDAPEntity

The name of the linked entity (User or Group). Use User when describing the Group entity. Use Group when describing the User entity.

linkingLDAPAttr

The multiple-value attribute name on the LDAP entity that contains the linked entity.

linkingSearchFilter

The search filter to be applied to retrieve the list of linked objects, for example:

(&amp;(objectClass=group)(memberOf=%attr%))

The search filter may contain the string % attr % that acts as a substitution string and is replaced at run time by the value of the attribute named "attr" of the imported entity. If the LDAP entry you are describing is a Group and the string is %name%, it is replaced by the value of the "name" attribute of the group you are importing. If the LDAP entry you are describing is a User and the string is %dn%, it is replaced by the "dn" attribute of the User you are importing.

linkingSearchScope

Sets the scope of the search. Valid values are:

- onelevel (the value normally used)

- subtree

Sample Mapping

The following XML describes a sample mapping. The example makes the following assumptions:

- The base product attribute displayProfileCodeis defaulted to "NORTHAM" when adding a new user.

- The LDAP Group entry contains the list of users belonging to the group in the departmentNumber attribute.

- The groups to which a user belongs are retrieved by applying a search filter.

<LDAPEntries>

<LDAPEntry name=" User" baseDN="ou=people,dc=example,dc=com" cdxEntity="

user" searchFilter=" (&amp;(objectClass=inetOrgPerson)(uid=%searchParm%))">

<LDAPCDXAttrMappings>

<LDAPCDXAttrMapping ldapAttr="uid" cdxName=" user" />

<LDAPCDXAttrMapping ldapAttr="cn" cdxName="externalUserId" />

<LDAPCDXAttrMapping cdxName="language" default=" ENG" />

<LDAPCDXAttrMapping ldapAttr="givenName" cdxName="firstName"/>

<LDAPCDXAttrMapping ldapAttr="sn" cdxName= "lastName"/>

<LDAPCDXAttrMapping cdxName="displayProfileCode" default="NORTHAM" />

<LDAPCDXAttrMapping cdxName="toDoEntriesAge1" default="30" />

<LDAPCDXAttrMapping cdxName="toDoEntriesAge2" default="90" />

<LDAPCDXAttrMapping cdxName="userEnable" default="ENBL"/>

</LDAPCDXAttrMappings>

<LDAPEntryLinks>

<LDAPEntryLink linkedToLDAPEntity="Group" linkingLDAPAttr="departmentNumber" />

</LDAPEntryLinks>

</LDAPEntry>

<LDAPEntry name="Group" baseDN="ou=people,dc=example,dc=com" cdxEntity="

Group" searchFilter=" (&amp;(objectClass=organizationalUnit)(ou=%searchParm%))">

<LDAPCDXAttrMappings>

<LDAPCDXAttrMapping ldapAttr="name" cdxName="Group" />

<LDAPCDXAttrMapping ldapAttr="description" cdxName=" Description" default="Unknown" />

</LDAPCDXAttrMappings>

<LDAPEntryLinks>

<LDAPEntryLink linkedToLDAPEntity="User" linkingSearchFilter="

(&amp;(objectClass=inetOrgPerson)(departmentNumber=%distinguishedName%))"

linkingSearchScope="onelevel" />

</LDAPEntryLinks>

</LDAPEntry>

</LDAPEntries>

Oracle Identity Manager Integration

The Oracle Identity Manager product allows a site to centralize their user definitions and password rules to manage and deploy across the enterprise set of products. When an employee joins an organization, changes their name or departs an organization their security presence across an enterprise must be appropriately managed. Oracle Identity Manager allows for users to be provision and managed in a central location.

An integration is provided to allow the ability to create, maintain and remove users in the identity management product and sync those changes to the users defined in the application. The following sections provide additional details about the integration with respect to configuration steps required in an Oracle Utilities Application Framework based product. For more information about the configuration required in the identity management product, refer to the Identity Management Suite Integration white paper.

In order to use this functionality, feature configuration options for the External Messages feature type must be configured.

- Set option type Support SPML Deployment in IWS to true.

- Set option type Default SPML service security policy to an appropriate value per your implementation rules.

Template User Functionality

The user object in this product captures configuration used to control access but also preferences. The identify management product allows for extending the configuration to capture user configuration that is specific to this product. However, it does not support providing searches or dropdowns to select valid values. For example, to define the user’s Home Page requires the reference to a navigation option. To set up your business process such that the home page is configured when defining the user in the identity management product dictates that the security user types in the correct navigation option reference.

On the other hand, to define a minimal amount of user information in the identity management product may result in a two step process for defining users: first define them in the identity management product with the basic authentication details and setting system defaults for some important fields, then after submitting the new user to be added to this product, navigate to the user page in this product and fill in all the configuration that is specific to this product.

The product provides support for defining a template user that can facilitate the definition of users and reduce some of the challenges listed above. The concept is as follows:

- Define a template user for each broad category of users in the system. For example, Oracle Utilities Mobile Workforce Management may define the following template users: Dispatcher, Mobile Worker, System Administrator and Contractor. Each user would define the typical configuration for users of that type including the home page, the user groups, the To Do roles, the portal preferences, etc.

- When extending the configuration in the identity manager product, simply map the information that is unique to a user and in addition, define a field for the template user. For example, you may choose to only capture the Name (first and last), Email address and User IDs for the user along with its Template User (which is mapped to a user characteristic). Additional fields may be included for capture in the identity management product when defining new users as per an implementation’s business needs. For example, if the organization covers multiple time zones, perhaps it is easier to define the user’s time zone when defining the user in the identity management product.

- When the new user is uploaded to the system, the interface uses the user BO F1–IDMUser to create the user. The BO includes a preprocessing algorithm that looks for the existence of a template user (sent as a characteristic of type F1-TMUSR). All the information from the template user will be copied onto the new user record except for the information passed in from the identity manager. The template user is captured on the newly created user via a characteristic for information / audit purposes.

- Once the new user is created, its configuration can now be adjusted, if applicable. Note that the template user is only a tool used when adding a user. Updates to the template user will not “ripple” to all the other users that were created based on this template.

Configuring Template Users

Before configuring template users, all the administrative control tables that are part of User configuration must be defined, including time zones, display profiles, To Do roles, data access roles and user groups.

The next step is to define the user configuration for your system users. During this exercise, you will find that you have broad categories of users. But you will also see that within a given category of user there may be variations in the user privileges and preferences. For example, perhaps there are supervisors within the Mobile Worker role that have more security privileges than a typical Mobile Worker. In addition, there may be variations based on the attributes of the users themselves. For example, maybe your organization exists in multiple time zones and some of your workers are in one time zone and some are in the other.

At this point your security users that are designing their user provisioning procedures must decide the following:

- What information about a new user will be captured in the identity system (besides the expected information like Name, Email and the User IDs)? For example, for the case of multiple time zones, maybe the best solution is to capture the time zone when defining the user.

What information is defined on the template user and how many template users should be created to reduce the need for manual steps or additional data captured in the identity management system? In the case of multiple time zones, proliferating the template users to have one set for one time zone and another set for the other time zone may not make sense since this is one field that is different. However it may be reasonable to create additional templates in the case of striations in the levels of privileges for workers of a different category. So rather than template users for Dispatcher, Mobile Worker, System Administrator and Contractor, your organization may have template users for Dispatcher, Mobile Worker, Mobile Worker (Supervisor), System Administrator, Contractor (Short Term) and Contractor (Long Term).

What information is must be configured one the User record in the application after the user is added? If only a small number of users have a variation from other users, it may be that the easiest way to deal with those variations is to simply update those user records manually. Using the above examples:

- If your organization covers 2 time zones but only a small group of people work in one of the time zones whereas the bulk of the users are in the other time zone, the simplest procedure may be to define the template users for the main time zone and use that for the creation of all users. Then for the small group of users in the separate time zone, navigate to the User page to adjust the time zone after the record is added.

- If only a small number of Mobile Workers are supervisors with separate privileges, rather than defining a special template user for those type of workers, the simpler procedure may be to use the Mobile Worker template and then navigate to the User page to add the additional privileges to the supervisor users after the record is added.

To create a template user, navigate using Admin > Security > User.

- Define a User ID that will become the template user reference in the identity management system.

- Be sure to choose a User Type of Template User.

- Define all the information that should be copied onto a new user that references this user as a template user. Note that Bookmarks are not included in the data that is copied from a template user.

Note: There is configuration needed in Oracle Identity Management to capture the template user and any other information that the implementation has chosen to define in the identity management product when provisioning a new user. Refer to the Identity Management Suite Integration white paper for more information.

Batch Scheduler Integration

The Oracle Database includes an enterprise wide scheduler to simplify the scheduling of background processes. The scheduler is implemented by the DBMS_SCHEDULER package. The product provides an integration with the Oracle Scheduler to facilitate scheduling background processes shipped with the product.

At a high level, the integration with the Oracle DBMS Scheduler supports the following entities:

- DBMS Program. A program should be defined for each Batch Control that needs to be scheduled by the DBMS scheduler. A program would typically invoke a batch job, but it could be configured to set certain options instead.

- DBMS Chain. A Chain defines a series of steps with dependency rules between them. A step references a program, with the program performing the actual work for that step. A rule is attached to each step to identify its dependent steps and the condition for when that step should be executed. For example, in a chain consisting of STEP_A and STEP_B, where STEP_B can only start if STEP_A was successful, the rule for STEP_B to start would specify a condition of "STEP_A SUCCEEDED".

- DBMS Schedule. A predefined frequency for jobs that need to be run periodically, for example, nightly jobs.

- DBMS Job. Defines a plan to perform a specific program or a chain periodically on a specific schedule or ad-hoc.

The product provides a set of business services to maintain these entities as well as submit jobs, manage submissions and report on past submissions. Refer to business services that start with the prefix "F1-DBMS" for more information.

Note: For details on the integration, refer to the Server Administration Guide which contains the API. In addition, refer to the white paper Oracle Scheduler Integration that provides guidelines for using this integration.

Data Synchronization

Your implementation may need to communicate certain data to external systems. This may be part of a data warehousing requirement or an integration effort. The synchronization process has two main parts. First, the change to the data must be detected and captured. Once that is accomplished, the next step is to manage the communication of that change to the external systems involved. The changes must be captured in chronological order so as to avoid systems going out of sync.

Next in This Section

- About Data Synchronization

- Maintaining Sync Requests

About Data Synchronization

The following sections describe general supported functionality in more detail using the logic supplied in the base business object F1-SyncRequest. Note that each edge application delivers an appropriate child business object for this BO for each specific synch scenario supported in that product. Some of the functionality below is accomplished using configuration on the parent BO delivered by the framework while other functionality may be delivered by the child BO. In addition, there may be more complex use cases supported by your specific product integration. Refer to your specific application’s library of Sync Request business object along with the documentation related to your specific product integration for more information.

Capturing the Change

The base product uses the Audit plug-in spot on the maintenance object to allow for logic to be performed by the system when a change is detected to a record for that MO. The framework calls the algorithm defined on this plug-in spot in the event a change to the MO has been detected. Refer to the description of the plug-in spot on Maintenance Object — Algorithms for more information about when this plug-in is called.

The base product provides an change data capture algorithm F1-GCHG-CDCP that may be used by maintenance objects. This algorithm creates a Sync Request record for each changed record, capturing the MO code and the primary key, if it doesn’t find an existing sync request for the same record (and the same business object) in the initial state. The sync request business object used is the one defined in the Sync Request BO option on the MO for the record that was changed.

Your specific product may also introduce additional Audit algorithms to cater for more sophisticated examples. Click here to see the algorithm types available for this system event.

When creating the sync request record, typically the Sync Request BO will have a pre-processing plug-in that captures a snapshot of the record’s data prior to its change. This will be used in subsequent steps to verify that the external system needs to be notified of the change.

Confirming that a Sync is Needed

Once a sync request is captured, there are several steps performed prior to any information being sent to the external system.

Note: This section only highlights key steps. Please refer to the business object configuration, its lifecycle and algorithms for a thorough picture of the full functionality..

- When a Sync Request record is created, its initial state (Pending) is configured to be processed by a batch monitor. That way, records are added to the sync request table added throughout the day but all are processed together. The MO audit algorithm ensures that a new synch request is not created if a Pending record already exists for a given MO / PK combination (for the same business object). However, it is possible that a record for that MO / PK exists in a subsequent “non-final” (such as Awaiting Acknowledgement). This state includes a monitor algorithm to check for that condition and to skip transitioning if another record exists. This is done to ensure that the existing record is fully processed before this new record is processed.

- The next state of the lifecycle is Determine if Sync Needed. This step uses an algorithm to take a snapshot (called the ‘final snapshot’) of the data and compare it against the initial snapshot taken when the record was created. Based on the logic of the algorithm, it may decide to proceed (transition to Send Request or to discontinue (transition to Discarded.

Communicating to the External System

Once it is confirmed that the sync should occur, a message must be sent to the external system. The following points highlight the basic functionality.

- An algorithm linked to the Send Request state. The expectation is that this algorithm creates an outbound message that routes the information to the external system appropriately. The algorithm must determine the external system and outbound message type to use. Business objects for Sync Request support BO options to define the external system and outbound message type to use for this algorithm.

- Once the outbound message is triggered, the record transitions to the Awaiting Acknowledgement status. This state is used to hold the sync request from further state transitions until an acknowledgement is received from the external system. Note that this step relies on implementation of a response mechanism from the external system. It is recommended to implement a response as this helps control the chronological flow of information. The product supplies the business service F1-UpdateSyncRequest that transitions the sync request to either the next default state (in this case the Synchronized state) if a positive acknowledgement is received; or the state associated with the Rejection transition condition (in this case the Error state) if a negative acknowledgement is received. In addition, this state may be configured with a monitor algorithm that detects that a timeout limit has been reached.

- For records that enter the Error state, it is recommended to configure an algorithm that creates a To Do entry to alert someone of the problem. Refer to the integration documentation for more information. The state is already preconfigured with an algorithm to complete To Dos when exiting the state.

- The final state Synchronized is used to mark the successful synchronizations. However, for more complicated use cases, this state may be used to trigger some additional action. Refer to the documentation for your specific product integration for more information.

Maintaining Sync Requests

The system provides a Sync Request portal that is used to view the in progress or completed sync request records.

The menu location of the portal depends on your specific edge product. It may be in a Data Synchronization menu or perhaps in the Batch menu. You are brought to a query portal with options for searching. The options may differ based on your specific product.

Once a sync request has been selected, you are brought to the maintenance portal to view and maintain the selected record.

An Actions zone may appear to display specific actions. Alternatively, the actions may be displayed directly in the display area of the Sync Request zone.

The Sync Request zone provides basic information about the sync request record.

Depending on your specific product additional zones may appear.

Analytics Integration

The framework provides several building blocks and tools that the edge applications may use to implement integration with the Oracle Utilities Analytics product (referred to in this section as the analytics product). The following sections provide more information about this functionality.

Next in This Section

- About Analytics Integration

- Maintaining Bucket Configurations

- ETL Mapping Control

About Analytics Integration

The following sections describe the type of configuration supported in your product to integrate with the analytics product. Refer to the Oracle Utilities Analytics documentation for more information.

Master Configuration

Edge applications that include an integration to the analytics product typically include a master configuration record that captures information needed for the extract, load and transformation step, such as extract parameters. These records are provided by the specific edge products and my be viewed and maintained on the master configuration portal.

Note that your specific edge application may deliver an Analytics Configuration portal that displays the information from the master configuration record along with other analytics related configuration.

Bucket Configuration

The analytics product provides support for defining a set of ranges, each representing a bucket for which extracted measures can be grouped and classified under the relevant bucket. The framework product provides support for viewing and defining the buckets. Refer to Bucket Configuration for more information.

Characteristic Mapping

The product provides objects to allow mapping configuration of characteristics in the product to user defined fields on dimensions in the analytics product. Refer to ETL Mapping Control for more information.

Change Data Capture Using Sync Request

Depending on the specific edge application and version you are using, there may be components of the integration that use Sync Request for the change data capture step. If that functionality applies to your implementation, the following points highlight how to get more information:

- Refer to the administration guide for Oracle Utilities Analytics to confirm if your product integration is using Sync Request for any change data capture functionality.

- Review the Sync Request Business Objects provided by your product for analytics integration.

- Refer to Data Synchronization for a high level understanding of the process.

Maintaining Bucket Configurations

Several key performance indicators in the analytics product look at measurement values (for example: the age of an asset or the age of debt) classified into a number of pre-defined groups also known as buckets. The overall metric can then be reported by the different buckets and allow various analyses.

For example, the age of an asset can be classified into the following buckets:

- Less than 6 Months

- 6-12 Months

- One Year and Older

The age of debt, also known as arrears can be classified onto the following buckets:

- 0-30 Days

- 30-60 Days

- 60-90 Days

- 90+ Days

The definition of the buckets is extracted to the Business Intelligence data warehouse, to be used as dimensions.

Bucket Definition Considerations

Each type of bucket is defined using a bucket configuration Business Object. The bucket definition considerations and/or rules will vary based on the bucket configuration business object used. The business objects available are driven by your specific product. For a list of available bucket configurations business objects, navigate to the business object page and view the business objects for the Bucket Configuration maintenance object.

Setting Up Bucket Configurations

To maintain the bucket ranges for the bucket configuration(s) applicable to your product, open Admin > Analytics Configuration > Bucket Configuration.

You are taken to the query portal where you can search for an existing bucket configuration. Once a record is selected, you are brought to the maintenance portal to view and maintain the selected record.

Note: Your specific product may also include an Analytics Configuration portal that displays the list of existing and potential bucket configuration records, allowing you to drill into this page to view the record in detail.

The Bucket Configuration zone provides basic information about the bucket configuration.

For more information about the elements supported refer to the zone’s help or to the relevant analytics integration documentation for your product.

ETL Mapping Control

If your implementation would like to map characteristic data in your application to user defined fields on dimensions in the analytics product, the ETL mapping control provides configuration to support this.

ETL mapping control relies on configuration in the Allowed Target Dimensions extendable lookup. The extendable lookup is used to define each Target Table in the analytics product that has one or more user defined fields that may be populated with characteristic values. It also defines the valid characteristic entities that may act as the source for the characteristic data.

Note: The framework does not provide any values in this lookup, but edge products that support mapping provide values in this lookup. Please refer to your specific product’s integration chapter and refer to the Oracle Utilities Analytics documentation for more information.

Setting up ETL Mapping Control

Use the ETL mapping control to define how to populate each target table (dimension) and target column (user defined field) by indicating the characteristic entity, characteristic type and for sequence-based characteristic, the sequence number.

Note: For sequence based characteristics, if the source entity captures multiple characteristic values for a given characteristic type, each characteristic type and sequence combination must be mapped to a specific target table and target column.

Note: Only Adhoc and Pre-defined characteristic types are supported.

To maintain the ETL mapping control records, open Admin > Analytics Configuration > ETL Mapping Control.

This is a standard All-in-One portal.

Refer to the embedded help text for more information.

Business Flags

It is possible that information detected in one product may be useful or even critical to share with another product. The framework provides functionality for receiving information from an external system that acts as a type of flag or alert that may need investigation. This allows any system to store detected business flags in a common way and share that information with one or more other systems.

Next in This Section

- About Business Flags

- Setting Up Business Flag Configuration

- Maintaining Business Flags

About Business Flags

The following is an example of a use case for business flags. Imagine that DataRaker highlights potential theft of service at a certain location. That product may initiate a business flag alert to various products owned by the implementation with a recognized "standard name" for the business flag, such as "TAMPER".

- If Oracle Utilities Meter Data Management receives this business flag, it may initiate a service investigation monitor.

- If Oracle Utilities Mobile Workflow Management receives this business flag, it may initiate a service investigation activity.

- If Oracle Utilities Customer Care and Billing receives this business flag, it may initiate a hold on billing for that location.

Note that the framework product supplies basic functionality to support logic that is common to all edge applications that implement business flag functionality. However it is the individual edge applications that supply more specific functionality (business objects and algorithms) for specific use cases, if applicable.

The following sections highlight functionality supported for business flags in the framework. Refer to the edge application product documentation for more details for supported use cases.

Next in This Section

- Standard Name

- Business Flag Type Defines Behavior for a Standard Name

- Business Flag Type Algorithms

- Objects Linked to a Business Flag

- Impacted Business Process

- Dates

- Creating Business Flags

- Confidence

Standard Name

To ensure that Business Flags are universally understood across all edge applications and to simplify integration each Business Flag will have a Standard Name. This is a name that is used by all the products when sending information to each other. That way, if DataRaker product sends Oracle Utilities Meter Data Management a "TAMPER" business flag, it should result in the same functionality as when Utilities Customer Care and Billing sends a "TAMPER" business flag.

Business Flag Standard Names are defined using an extendable lookup. In addition to standard extendable lookup fields, the standard name also references a category. In addition, the lookup supports defining one or more external names, for cases where information is communicated from an external system that does not send the expected Standard Name.

The framework does not deliver any standard names or category values. Refer to your specific edge application products to verify if any standard names or categories are delivered. Your implementation may configure appropriate standard names and categories based on your business rules.

Business Flag Type Defines Behavior for a Standard Name

Although the definition of the business flag standard names should be universally understood by the various integrated products that support them, each individual product defines what should occur when a business flag with a given standard name is created. This is configured using a business flag type. Only one active business flag type may exist for a given standard name. Business flags that are received from an external system will define the standard name, but will not have knowledge of the specific business flag types defined. The business flag type is determined based on the standard name.

The business flag type defines the business object to use when creating the resulting business flag record. The business object defines the lifecycle of a resulting business flag record.

Business Flag Type Algorithms

The business flag type includes support for algorithms. This allows for an implementation to define a common business object that may be used for different business flag types (if a common lifecycle is followed) but allow for different functionality to kick in depending on the business flag type.

The product supplies a plug-in spot for Additional Processing that may be invoked by a business flag that enters the Additional Processing state. Refer to your product’s library of business objects to determine if there is an Additional Processing state that supports calling algorithms on the business flag type.

Click here to see the algorithm types available for this system event.

Objects Linked to a Business Flag

There are two types of links between an object in the system and a given business flag.

Affected Entity

Each business flag is associated with a single record in the system that is considered the “affected entity” or the entity that the business flag is associated with. The affected entity is defined by the specific business objects designed for the use cases supported by your edge product. For example, many utility base products may configure service point as the affected entity for its business flag use cases. Each business flag created is linked to a specific service point. Linking a specific entity to each business flag allows for algorithms to trigger functionality for that entity such as an investigation order. In addition, algorithms may be implemented in other business process areas that look for the existence of a business flag and act accordingly.

Related Objects

The business flag supports linking one or more related objects to a business flag to make it easier to trigger functionality or for impacted business processes to look for business flags. For example, when creating a business flag for a given service point, it may be useful to link all the accounts that are currently linked to the service point. Then, if an account oriented process should check for a business flag, it can look directly for a business flag linked to the account in its related object.

Impacted Business Process

The product supplies support for associating one or more impacted business processes to a business flag type. This configuration is used when functionality for that business process is impacted in some way based on the existence of a business flag of a given type. For example, maybe some process is put on hold when a certain type of business flag exists.

Note that configuring a business process on business flag type is not enough to trigger any impact on that business process when a business flag exists. There must also be some logic implemented in the business process functionality itself that knows to look for a business flag for a given record that is configured to impact the business process.

The definition of the business process is at the discretion of the edge application that supplies functionality to support this. For example, the business process could be defined as something broad such as “billing” or could be something more granular such as “billing estimation”. The system supplies an extendable lookup to use for configuring the supported business processes. Refer to the values of the business process extendable lookup in your edge application or to the edge application specific Business Flag documentation for more information about supported business processes.

Dates

A business flag supports two dates: a Business Flag Date/Time and a Business Flag End Date/Time

- The business flag date / time is required for all business flags. For some types of business flags only one date is needed.

- For business flags that have a start and end period, the business flag date/time acts as the start date and the other field is the end date.

For a business flag that has a date range, it may be important for functionality implemented for impacted business processes. How the process treats the date will depend on its functionality.

- For some processes, the business flag is essentially expired after the end date has passed. This applies to impacted processes that are only looking at the current status of data in the system. For example, collection processing could be held if there is a business flag currently in effect (where the current date is within the date range). It would never look at historical business flags.

- For some processes where historical data may be relevant, a business flag effective during that same historical period may impact the process. For example if a business flag denotes an outage event for a given time period, perhaps estimated consumption should never be calculated for that time period.

Note that because business flags have a status, the design for the lifecycle of the business objects for the above effective dated use cases must carefully consider the states. For business flags that are considered expired after the end date passes, the BO lifecycle may be designed to transition to a final state after that date such that the record is no longer included in active processing. For business flags that continue to impact processing for a historic period, the BO lifecycle may be designed to remain in a non-final state such that it is clear that the record is still applicable.

Creating Business Flags

Business flags may be created in a system for one of the following reasons:

- A message is received from an external system that initiates the creation of a business flag. In this case, logic in the external system has detected some situation that this product is being alerted about.

- Business logic in this product detects a situation that should be investigated or should act as a flag. In this scenario, there may not be any integration needed depending on the business rules.

- Business logic in this product detects a situation that another integrated product should be alerted about. In this scenario, the business flag record is used to send out information to the integrated product.

- A user manually creates a business flag based on knowledge of the affected entity. For example, a customer service representative may create a business flag as a result of contact with the customer.

Creating a Business Flag from a Web Service

The system supplies an inbound web service Business Flag Sync Driver (F1-BusinessFlagSync) that may be used for an external system to initiate (or update) a business flag. It references a service script whose ultimate responsibility is to determine the appropriate Business Flag Type, based on the standard name or external standard name, and therefore the appropriate business object for the new business flag. Because different products may have different logic related to creating a business flag, the service script calls another service script linked to the maintenance object using the Business Flag Sync MO option.

The framework does not supply a Business Flag Sync service script, however individual edge applications supply a service script based on the use cases it supports out of the box.

Note: For products that are continuing to use XAI for external messages, the product also includes an XAI inbound service for the same Business Flag Sync Driver service script. Note that the product recommendation is to discontinue use of XAI and use inbound web services instead.

Error Handling

If there is a problem in trying to create a business flag based on incoming information, the Business Flag Sync Driver service script creates a special business flag record using the Business Flag Error Business Object. This is also configured on the maintenance object as an option. The framework product supplies the business object Business Flag Error (F1-BusinessFlagError) for this functionality. Refer to the business object description and configuration for more information.

Confidence

There may be use cases where a condition is suspected, but not confirmed. The originating system should be able to assign a "confidence" level to the business flag.

For example, DataRaker through aggregating and analyzing large amounts of data identifies potential revenue protection issues that need investigation. It triggers business flags with a Suspected confidence.

An application receiving this business flag may adjust the confidence to either Confirmed or Rejected. That update can be communicated to the other products that received the same business flag.

Note that the application that receives a business flag is responsible for acting on the value based on business rules.

Because a utility implementation may have multiple applications installed that support business flags, the following guidelines are suggested for designing where the confidence flag should be updated.

- If Oracle Utilities Service Order Management is implemented, it has the responsibility of updating the confidence flag and communicating the update to other products.

- Otherwise, the assumption is that Oracle Utilities Customer Care and Billing owns field work orchestration and that it will have the responsibility for updating the confidence flag and communicating the update to other products.

No product logic is provided to enforce the above suggestions, however, the business objects supplied by the different edge applications will support the recommended implementation.

Business Flag Updates from External System

When the product that is responsible for updating the Confidence flag makes a change, it should initiate an outbound message to alert other products. On the receiving side, the same inbound web service and Business Flag Sync service script is responsible for the update. Refer to Creating Business Flags for more information.

Setting Up Business Flag Configuration

The following topics highlight the general configuration steps required to use business flag functionality. Your specific product may supply additional functionality to support specific use cases for business flags. Refer to your specific product’s documentation and the library of business objects supplied for Business Flag in your product for more information.

Next in This Section

- Standard Name Category Characteristic Type

- Business Flag Standard Name Lookup

- Business Process Lookup

- Integration Configuration

- Defining Business Flag Types

Standard Name Category Characteristic Type

Define one or more categories for grouping your standard names into logical business groupings.

Navigate to the Characteristic Type page. Search for and select the Business Flag Category characteristic type (F1–BUSFC).

Define desired category values and descriptions to be used for the standard names.

Business Flag Standard Name Lookup

Navigate to the Extendable Lookup portal. Search for and select the Business Flag Standard Name business object.

Define values that are recognized in the external systems that your implementation is receiving business flag details from.

Define a Category for the standard name that is appropriate for your product. Note that the category does not have to be in sync with standard name definitions in external products.

Refer to the embedded help for more information about configuring this object.

Business Process Lookup

If your specific product supports configuring business processes that may be impacted by the existence of a business flag, they are defined as an extendable lookup.

Navigate to the Extendable Lookup portal. Search for and select the Business Process business object.

Integration Configuration

The following points highlight configuration required to support receiving business flag information from an external source:

- Define a record for each External System that the product may be receiving business flag records from. This should be a value known by the external system and provided when new business flags are sent to this product.

When this product should initiate business flag information to be sent to an external system, configure one or more Outbound Message Type records. For each one, update the External System to configure how each outbound message type is communicated to the external system.

Defining Business Flag Types

Refer to About Business Flags for an overview of business flag functionality.

To maintain the business flag types applicable to your product, open Admin > Integration > Business Flag Type.

This is a standard All-in-One portal.

The information captured on the business flag type depends on the business objects supported by your product. Refer to the embedded help text for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_BUS_FLG_TYPE.

Maintaining Business Flags

This section describes the functionality supported for viewing and maintaining business flags.

Refer to About Business Flags for an overview of business flag functionality.

Navigate using Main > Integration > Business Flags. You are brought to a query portal with options for searching for business flags.

Once a business flag record has been selected, you are brought to the maintenance portal to view and maintain the selected record.

The Business Flag zone provides basic information about a business flag. Refer to the embedded help for more information.

Configuration Migration Assistant (CMA)

This chapter describes the Configuration Migration Assistant (CMA), a facility to enable the export of customer-owned configuration data from one environment to another.

CAUTION:

This chapter is intended for users responsible for testing configuration data and performing "what if" analysis in non-production databases.

Next in This Section

- Understanding CMA

- CMA Configuration

- The CMA Execution Process

- Running Batch Jobs

- CMA Reference

Understanding CMA

The Configuration Migration Assistant (CMA) provides implementers with a flexible, extensible facility for migrating configuration data from one environment to another (e.g., from a development environment to a production environment). Data is exported from the source system to a file. The file can then be checked in to a version control system for reuse, or can be immediately imported into the target system and applied.

Note: As used in this chapter, source systems are those on which export-related activities are conducted and target systems are those on which migration updates are to occur. The two system preparation tasks described in Migration Assistant Configuration must be performed on both source and target systems.

Next in This Section

- The CMA Process Flow

- Migration Assumptions, Restrictions and Recommendations

The CMA Process Flow

The high-level CMA process comprises the following tasks and flows. Each is described in more detail later in this section.

- Configuration steps are used to define the data to migrate. This task is performed on the source system and may be defined at any time. Note that the products provide base delivered configuration that may be used as is or used as a template for building more specific configuration for a given implementation.

- Specify the source and target paths and a file extension for import and export data files in the Migration Assistant Configuration master configuration record.

- Each type of record that may be copied requires a Migration Plan. The migration plan is used to identify the maintenance object (MO) for the record (using a business object) and allows for instructions to specify related records that may be included in the migration. Multiple migration plans may exist for a given maintenance object if there are different requirements for migrating records in that MO under different circumstances.

- The primary instruction in the migration plan could define the physical BO of the record. This signals to CMA that all records for the MO are eligible to be migrated.

- The primary instruction may define a specific BO, in which case only records that reference that BO in its parental hierarchy are considered.

Note: Refer to Understanding the BO Filtering Process for more information.

- Subsequent instructions may include references to related records. There may be some circumstances where a migration should include subsequent records and some circumstances where they shouldn’t based on requirements.

- A Migration Request is used to define the data to include in a given migration. There are several types of migration requests:

- Criteria-based. This type of migration request defines a set of migration plans to be logically included together as part of a migration. For each migration plan, selection criteria may be defined to limit the migration to a subset of data for each MO. Selection may be defined using SQL, an algorithm or explicit primary key values.

- Entity List. This type of migration request allows the user to choose explicit MO / prime keys. It is meant for a targeted migration of specific objects. Note that although the user views and maintains MO / PK values when configuring this type of migration request, a migration plan is still used internally for the CMA migration processing.

- Group. This type of migration request points to other migration requests. This allows you to define separate migration requests that represent logical groupings of migration plan instructions for ease of maintenance, but to combine all the separate migration requests into a single "grouped" migration request for streamlined export / import purposes.

Fastpath: For more information, refer to CMA Configuration.

- The Export process includes all the steps needed to select records to be exported from the source environment and create the export file.

- A Migration Data Set Export object is created for a specific migration request.

- The lifecycle of the Migration Data Set Export business object includes algorithms that select the appropriate records according to the migration request, determine dependencies between records to build groupings of related objects and create the export file.

- Because there may be a large volume of data in the export, many of the steps in the lifecycle of the migration data set export are executed via the Migration Data Set Export Monitor.

Fastpath: For more information, refer to Exporting a Migration.

- The file created by the export, which is a BINARY file, needs to be transferred from the export directory to the import directory. The transfer needs to be done in such a way as to preserve the file structure. Refer to Migration Assumptions, Restrictions and Recommendations for more information.

- The Import processes include all the steps needed to read an imported file, compare the data in the file to the data in the target, review the proposed changes and apply the updates. The following is a high level overview of the process.

- A Migration Data Set Import object is created for a given file to import.

- The next step reads the import file and creates Migration Transactions and Migration Objects based on the information in the import file. A migration object is created for every maintenance object record to potentially be created or updated. The migration transaction is a grouping record that groups together related migration objects.

- The next step is for the objects to Compare the data being imported against the data for that record in the target environment. If it is found that the migration object is new or represents a change to the existing record in the target environment, appropriate SQLs are generated. If no changes are found, the object is marked “unchanged” and doesn’t progress.

- Once all the objects are compared, the user may review the objects for acceptance or rejection.

- When the migration objects are all accepted or rejected, the next step is to apply the objects and update the target environment.

Fastpath: For more information, refer to Importing and Applying a Migration.

Migration Assumptions, Restrictions and Recommendations

The following sections describe miscellaneous topics that are important to learn with respect to CMA.

Type of Data Migrated

CMA is designed to migrate configuration data.

The comparison step of the import process will generate appropriate insert or update SQL statements for the following data found in the export:

- Configuration data in a maintenance object with no owner flag. This is purely implementation data.

- Configuration data in a maintenance object with owner flag, where the owner is Customer Modification. For example, implementer-specific business objects.

- Configuration data in a maintenance object with owner flag, where the main record is owned by the product but where a child record exists with an owner of Customer Modification. For example, implementer-specific algorithms added to a base owned business object.

- Customizable fields in a record that is owned by the product. For example, the priority of a based owned To Do type.

Data with System Generated Primary Keys

The tool provides support for administrative data with system-generated primary keys. The logic relies on the maintenance object to use a method that looks at other attributes of the record (considered a “logical key”) to detect whether the record being migrated already exists in the target region or not. The examples in this section will use the Attachment maintenance object as an example. Common attachments are considered administrative data. The attachment MO uses the file name and the creation date as the “logical key”.

Imagine a common attachment for the "standard rate codes" file exists in a source region with the key 123456789. The table below highlights possible situations at the target region and actions supported in CMA.

Scenario

Target Situation

Action

Comments

1

No matching record

Record can be added with key 123456789.

2

Record exists with key 123456789 and logic confirms that it is also the "standard rate codes" attachment.

Record can be updated.

3

Record exists with key 123456789, but logic detects that it is not the "standard rate codes" attachment.

Record is not updated. An error is issued.

The system cannot update this record because it's not the right attachment record.

4

The system detects that another attachment record exists for the "standard rate codes" attachment with a different ID.

Record is not updated. An error is issued.

Assumption is that the record was created directly in the target or was copied from a different source.

The use cases described in scenarios 3 and 4 above would require key mapping to keep track of the id from the source to the id in the target so that any other records from the source that reference this key as a foreign key would be updated as part of the migration. This functionality is not supported.

Scenarios 1 and 2 above are supported for maintenance objects that use the method to detect the logical key.

Note: If a maintenance object with a system generated key does not supply a method to detect the logical key, CMA will update an existing record with the same ID. For maintenance objects in the framework that provide this method, refer to Framework Provided Migration Configuration. For your specific edge application, refer to the CMA addendum for information about support for admin data with system generated keys.

The product recommends that an implementation establishes a migration strategy such that administrative records with system generated keys are always created in the same region and always follow a standard migration path for promoting the data from this source region to other regions. Following this strategy, you would minimize or eliminate the possibility that a record for the same logical key is created in multiple places such that different IDs would be generated as described by scenario 4 above.

MOs with a Mixture of Administration and Non-Administration Data

There are some MOs that contain a mixture of master or transaction data and administrative data. The Attachment is an example of this. The product supports common attachments and owned attachments. Owned attachments are records that are specific to its owner. The owner could be master or transaction data and its attachments are therefore considered master or transaction data. Owned attachments are not candidates for migration using CMA. Common attachments on the other hand are considered administrative data and may be candidates for migration using CMA. For these use cases, an implementation may follow the suggested strategy of only creating the administrative data in one region so that IDs for common attachments are not reused. However, it is reasonable and expected that owned attachments are being created in the target region and may receive a system generated key that matches the key of a common attachment from the source region.

To try to minimize this issue, the system includes special logic to be used by any MO that may contain administrative data mixed in with master or transaction data. This special logic generates the key of an administrative record with a zero (0) in the middle of the key and ensures that the keys for master and transaction data do not include a zero in this spot. For maintenance objects in the framework that use this method, refer to Framework Provided Migration Configuration. For your specific edge application, refer to the CMA addendum for information about additional maintenance objects that may be in this category.

No Record Deletion

The CMA process allows users to define records to copy from a source environment to a target environment. In that way, the import process for the migrated records is able to identify objects to add and objects to change. There is no mechanism for indicating that records in the target environment should be deleted. The absence of those records in the import is not enough because the migration may be only importing a subset to add or update. If data on the target system must be deleted, users must delete the records in the target accordingly.

Note that CMA does support the deletion of child rows of an object as a result of a comparison. This is only applicable to child records that are owned by the implementation.

File Transfer Considerations

When moving the export file between systems, use the binary transfer option of whatever tool you use to move the file so that line-end characters are not converted from Linux-style to Windows-style or vice versa.

It is recommended to avoid using 'txt' for the export file's extension (defined in the master configuration). That file extension by default implies a non-binary file and tools that perform file transfer may treat this as a non-binary file unless explicitly stated. The recommendation is to define 'cma' as the extension. This is not a recognized file extension and most file transfer tools will transfer the file as is.

Note that if the file gets converted, there are two likely outcomes - either a numeric conversion error, or a buffer under-run error may be received when attempting to import the file.

Multi-Language Environment Considerations

If your implementation uses a language other than English, it means that migrated objects may have multiple language rows (because English is always enabled). There are some important points with respect to multiple languages and CMA:

- As described in User Language, there are steps to follow when supporting an additional language. The steps outlined in that topic highlight that for system data, translation of the strings may be provided via a language pack provided by the product or may be the responsibility of your implementation. In either case, this effort is non-trivial and will have its own established plan. The expectation is that the translation of the system data is applied for each region at your implementation site. CMA should not be used to create a new language in a target region.

- For administrative / control data that your implementation develops as part of your project, the expectation is that descriptions for your supported language are entered in the region that is considered the source region used to promote changes to regions in the “chain”. For example, control data is entered in a development region and promoted to a test with the supported language enabled in both regions.

- What if you export data from a region with more languages enabled than your target? This scenario is perhaps a case where the source region is a type of test or playpen region where the additional language is enabled for other purposes. In this case, if the language code does exist at all in the target region, the import will produce an error given that the code is invalid. If the language code exists but is not enabled, this will cause the extra language rows to be inserted in the target region, but will not cause any issues. They are simply ignored.

- What if you export data from a region with fewer languages enabled than your target? In this situation, the import process will only create language rows for the languages that were copied from the source. It will not automatically create language rows in the target as part of the import. For this situation, the recommendation is to run the New Language batch program (F1–LANG) that creates any missing language entries.

CMA Configuration

The following sections describe tasks required for CMA configuration.

Next in This Section

- Master Configuration - Migration Assistant

- Migration Plans

- Defining a Migration Request

- Wholesale and Targeted Migrations

- Identifying Tables to Exclude From Migrations

- Configuring Custom Objects for Migration

Master Configuration - Migration Assistant

In both the source environment and the target environment, the system needs to know the location of the export directory and the import directory along with the expected file suffix. Implementations may define the information explicitly for each region using the Migration Assistant Configuration master configuration record.

For more information about specific fields in the master configuration, refer to the embedded help.

Note: This record can be updated at any time to change details. The new configuration takes effect on all subsequent exports and imports.

Implementations may also rely on the system defaults. If no Migration Assistant Configuration record is found, the system assumes that there is an entry defined in the system's substitution variable list for F1_CMA_FILES. Further it defaults the values as follows:

- Export directory is the value for this variable plus "\export".

- Import directory is the value of this variable plus "\import".

- File suffix is set to cma

Refer to Referencing URIs for more information about the substitution variable list.

Migration Plans

A migration plan defines one or more types of objects that are eligible for migration. It is essentially a set of instructions describing how the data to be exported is structured, allowing objects to be migrated together as a logical unit to ensure consistency and completeness.

The following topics describe defining a migration plan as well as other topics for a migration plan.

Next in This Section

- Defining a Migration Plan

- Understanding the BO Filtering Process

- Migration Plans for Objects with XML-Embedded Links

Defining a Migration Plan

To view or define a migration plan, navigate using Admin > Implementation Tools > Migration Plan.

Use the Migration Plan Query portal to search for an existing migration plan. Once a migration plan is selected, you are brought to the maintenance portal to view and maintain the selected record.

CAUTION:

Important! If you introduce a new migration plan, carefully consider its naming convention. Refer to System Data Naming Convention for more information.

The following points provide information about defining Instructions for a migration plan.

The Instruction Sequence uniquely identifies the instruction. The recommendation is to use increments of 10 to allow insertion of other instructions in the future.

Select Primary for the first Instruction Type. All migration plans must contain one and only one primary instruction. All subsequent instructions require a Subordinate instruction type. In this case, the Parent Instruction Sequence must be entered. This number, used to maintain the defined relationships in the exported data, must match an instruction sequence number at a higher level in the hierarchy.

The instruction Description provides a business description of the instruction.

Select a Business Object (BO) to define the type of object from which data will be derived.

Note: Though BOs are specified in each instruction, it's important to understand that each BO is used only for filtering purposes. The migrated data set comprises the complete contents of the maintenance object that the business object structure is defined against. For a more detailed explanation of this, see Understanding the BO Filtering Process.

Note: Refer to Identifying Tables to Exclude From Migrations for information about defining child tables to always exclude from a migration.

Traversal Criteria is used to define the relationship between each of the objects in a migration plan. The system provides three options to define how the child object is connected to the parent object so the system knows how to traverse from one object to another. Traversal Criteria Type options are Constraint, SQL and XPath. The following points explain each option:

- Constraint allows you to select a table constraint that represents a given record's relationship to another record in the system via a foreign key constraint defined in the meta-data. If Constraint is selected, the following additional fields are enabled:

- Constraint ID is a unique identifier for the constraint. The search will show the valid table constraints for the MO of the instruction’s BO and the MO of the parent instruction’s BO.

- Constraint Owner is used to define the owner of the constraint. This is populated automatically when selecting a constraint from the search.

- SQL lets you specify SQL join criteria between the parent instruction’s object and the child object in the SQL Traversal Criteria. The syntax of the the traversal criteria is a WHERE clause (without including the word WHERE). When referring to a field on the parent instruction’s object, use the syntax #PARENT.TABLE_NAME.FIELD_NAME. When referring to a field on the current instruction’s object, use the syntax #THIS.TABLE_NAME.FIELD_NAME. For example, the following statement is used on a migration plan for Business Object, where the parent instruction is the BO and the subordinate instruction is used to reference the UI Map that is referred to as a BO option with the option type “F1DU”:#PARENT.F1_BUS_OBJ_OPT.BUS_OBJ_OPT_FLG = 'F1DU' AND @trim(#THIS.F1_MAP.MAP_CD) = @trim(#PARENT.F1_BUS_OBJ_OPT.BUS_OBJ_OPT_VAL).

- The XPath option lets you apply syntax in an XPath expression referencing elements in the instructions’ referenced business objects. This is entered in the XPath Traversal Criteria. For example, the display map collection statement in the SQL example noted above would be written as follows in XPath: #this/mapCd = #parent/businessObjectOption/businessObjectOptionValue AND #parent/businessObjectOption/businessObjectOptionType = 'F1DU'. This technique allows foreign key references that are mapped inside an XML column to be referenced.

Note: The #parent expressions may access elements that are stored in an XML column and described using mapXML and mdField. However, the #this expressions must refer to fields available in the business object using the mapField reference.

Defining Next Migration Plan provides the ability to indicate that in addition to copying the object defined in the instruction, any additional instructions included in that referenced migration plan will also be included in an export.

The Algorithms grid contains algorithms associated with each instruction. You must define the following for each algorithm:

- Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).

- Specify the Sequence and Algorithm for each system event. You can set the Sequence to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.

System Event

Optional / Required

Description

Pre-Compare

Optional

Algorithms of this type may be used to adjust the data after it is moved to the target system. These may only be defined on the primary instruction.

Refer to Adjusting Imported Data for more information.

Click here to see the algorithm types available for this system event.

Import

Optional

Algorithms of this type are no longer supported.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_MIGR_PLAN.

Understanding the BO Filtering Process

Migration plan instructions require the definition of a business object to provide CMA with information about the record related to the instruction.

If the business object is the physical business object for the maintenance object, then CMA assumes that the instruction applies to all records that satisfy the traversal criteria. CMA recognizes the physical BO by comparing the BO to the value defined in the maintenance object option. If the business object defined is not the physical BO, then CMA will limit the records in the instruction to those that explicitly reference this BO or reference a child of this BO as its identifying BO value. (In other words, this BO must be in the parentage hierarchy of the records to be included in the instruction.)

Note: Unlike Bundling, CMA does not use the BO schema to drive what data is copied for a given record. The BO is only used as a filtering mechanism for selecting records. Refer to Identifying Tables to Exclude from Migration for information about how to ensure a child table is not included in a migration.

For example, if you define a migration plan for Master Configuration and use the physical business object for the instruction (F1-MstCfgPhysicalBO) then all master configuration records are considered for the instruction. If instead the business object you define is Migration Assistant Configuration (F1-MigrationAssistantConfig) then only the record related to this business object is included in the instruction.

Migration Plans for Objects with XML-Embedded Links

When migrating objects where foreign key references are captured in the object's XML based field, subordinate instructions are needed to define the foreign key references in order for CMA to understand the relationships. This is in contrast to direct foreign keys where CMA can determine the relationships using constraints. The instructions provide two purposes. For wholesale migrations, where all data (or a large amount of data) is being migrated, the instructions allow CMA to group related objects into transactions. This helps in the apply process at import time to ensure that related objects are grouped together. However, the apply process includes iterative steps to try to overcome dependencies like this so defining the instructions is not critical for this type of migration. For targeted migrations, defining instructions ensures that the related objects are included in the migration, if appropriate.

The following are options for creating migration plans with XML-embedded links:

- One option is to use the specific logical (business) BO in the primary instruction to define the object you are copying. With this option, the subordinate instructions may use XPath criteria to define the related foreign key. When this approach is used, a separate Migration Plan must be created for each logical BO. (Refer to Understanding the BO Filtering Process for more information.) This option would only be used in isolated cases.

- Another option is to create a migration plan that uses the Physical BO as the primary instruction, and then include a subordinate instruction for the real logical BO, using SQL Traversal to join the object to itself by its primary key. Note that with this technique, the records that reference the logical BO will still only be included in the export file once. At this point further subordinate instructions may use XPath notation to define the foreign key data. Using the physical BO as the primary instruction ensures that all records in the MO are considered. The subordinate instructions with the logical BO and XPath notations will only apply to the records that are applicable to that BO. This option is useful for MOs that have a small number of logical business objects with disparate foreign keys.

- Another option is to use the physical BO in the primary instruction and use raw SQLs in the subordinate instruction's traversal criteria to identify the foreign keys using substring commands. A separate Subordinate Instruction is needed for each SQL corresponding to each element occurrence. Using this technique has the same advantages of the previous in that all records for the MO are included in the migration. However, this technique may be useful for maintenance objects with a larger number of business objects expected where each has one or more foreign keys. It's especially useful if many business objects reference the same foreign key. Then only one instruction is required for that foreign key. Note that a single migration plan may use this technique and the XPath technique for different elements.

A migration request may have multiple migration plans for the same maintenance object. That allows for some flexibility and long term maintainability in that the above techniques may be used in multiple migration plans. Consider the following example:

- A product provides base business objects with foreign keys defined in the XML field and provides the appropriate migration plan with instructions. An implementation extends this business object or perhaps creates their own business object for the same maintenance object and includes different additional foreign keys in the XML. Rather than duplicating the base migration plan and adding additional instructions for the additional foreign keys, the implementation can create a second migration plan for the MO with the additional foreign keys defined. A migration request should be defined to include both migration plans. In this case if the implementation has only one custom BO, they can choose to use the custom BO as the primary instruction as described above in the first option.

Defining a Migration Request

Migration Requests are used to define the data to be included in a migration. To view or define a migration request, navigate using Admin > Implementation Tools > Migration Request.

Use the Migration Request Query portal to search for an existing migration request. Once a migration plan is selected, you are brought to the maintenance portal to view and maintain the selected record.

There are three types or classes of migration request. The system provides a base business object for each along with a migration request class, which matches the business object. The subsequent sections provide more information about each class of migration request.

Note that all migration requests support defining a Category, which allows implementers to categorize the migration request.

In addition, all classes of migration request include the following zones:

- Migration Request This zone contains display-only information about the selected record. Please see the zone's help text for information about this zone's fields.

- Referencing Migration Requests This zone is only visible if the displayed migration request is included in a Group migration request. It lists each group migration request that includes it.

Other zones may appear for specific classes of migration requests. See the following sections for more information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_MIGR_REQ.

Criteria-based

This type of migration request defines a set of migration plans to be logically included together as part of a migration. For each migration plan, selection criteria is defined to indicate which records for each MO should be included. Selection may be defined using SQL, an algorithm or explicit primary key values.

- For selection using SQL Statement, refer to the embedded help for examples.

- For selection using Algorithm, the algorithms that are eligible to be plugged in here are those valid for the Migration Request - Select system event. Click here to see the algorithm types available for this system event.

- For selection using Specific Keys, the primary key (1 through 5) must be explicitly specified. Multiple rows are allowed.

Entity List

This type of migration request allows the user to choose explicit MO / prime keys. The MOs that are eligible are those that are configured with a Default Migration Plan option. Although the user is managing MO / PKs, the migration instructions are still defined with a migration plan. The system maps the migration instructions in a similar way to a Criteria-based migration requests that use a Specific Key selection type. Note however that it will create a separate migration instruction for each MO / PK combination. It does not try to group all PKs for the same MO / migration under one migration instruction.

For this type of migration request, a user adds a migration request record with its description and other main information. Then, a special zone Add Entities is provided to find and select records based on a selected maintenance object and add to the migration request. The user is prompted to provide a reference and comments, if desired. If the category selected is one that requires a reference, then this will be validated.

When maintaining a migration request with existing entities, they are visible in the zone Migration Request Entities . This zone allows a user to remove the entity from the list.

Group

This type of migration request points to other migration requests. This allows you to define separate migration requests that represent logical groupings of migration plan instructions for ease of maintenance, but to combine all the separate migration requests into a single "grouped" migration request for streamlined export / import purposes.

The CMA export process will build an extract that includes the union of all the objects that qualify for the export and group them together based on their relationships.

Wholesale and Targeted Migrations

The Configuration Migration Assistant is used for two general types of migrations: wholesale and targeted. The following sections provide some additional information about these concepts.

Next in This Section

- Wholesale Migrations

- Targeted Migrations

Wholesale Migrations

Wholesale migrations are used when migrating all the configuration and/or administrative data from one environment to another. For example, a wholesale migration might be used when migrating administrative data from a development or test environment to a production environment.

A wholesale migration may be comprised of one or more migration requests that in total include all the administrative data to move. With the ability to group migration requests, the expectation is that implementations follow these guidelines:

- Multiple migration requests using the Criteria-based or Entity List migration request classes are used to group information logically together to allow for more reuse.

- A Group migration request is used for the export. This allows for one data set to export and one data set on the import side, simplifying the process. Note that depending on the amount of data, this may be a large import set to process. An implementation may find it easier to create multiple migration requests that break down the process into several steps.

You should consider that the framework product provides base migration requests and your specific edge product may provide base migration requests as well that may or may not include framework migration plans. Using the product provided migration requests is beneficial with respect to maintenance. As features are added to the product (including new administrative maintenance objects), any impact on CMA should be included in the product owned migration requests. If your implementation introduces new custom administrative maintenance objects that should be included in CMA, then custom migration plans and a custom migration request should be added. Your implementation can build a Group migration request that includes the base migration request and your custom migration requests to have a consolidated export.

Migration plans used in wholesale migrations may be designed to omit subordinate instructions related to explicit foreign keys that are identified through constraints as they are not needed, assuming that the data they are referring to will also be included in the migration.

Note: Refer to Framework Provided Migration Objects for information about migration requests provided in the framework product. Refer to your specific product's documentation for information about addition base provided migration requests.

Targeted Migrations

A targeted migration refers to migrating a specific subset of data from one environment to another. Examples of targeted migrations include:

- Migration of a new Business objects with its options and algorithms.

- Migration of a new maintenance portal, its zones, and its application service.

- Migration of all outbound message types.

It is expected that the Entity List migration request is used for these types of migrations.

Identifying Tables to Exclude From Migrations

Some maintenance objects that are eligible to be migrated may include child tables that should not be included in the migration. For example, if an object includes log tables, the entries in the log should reflect the actions on the object in that system, and will be different between the source system and the target system. If you have a custom Maintenance Object that includes tables you don't wish to migrate (such as a log table), use the Non-Migrated Table option on the MO to specify this table. All child records for this table will also be ignored during migration.

Another use case to consider is a child "many-to-many" table that connects two administrative objects and exists in the maintenance object of both tables. The child table may be in both MOs for convenience sake, but it may be that one MO is considered more of a "driver" object and the other more of a subordinate. If you are doing a targeted migration where you want to copy a subset of objects, you may want to only copy the driver object and its children and their data but not their children. For example, in Oracle Public Sector Revenue Management, a Form Type includes a collection of valid Form Change Reasons and in turn the Form Change Reason refers to its Form Types. If an implementation wants to do a targeted migration of a form type and include all its related information, including form rules and form change reasons, it does not want the migration of a form change reason to in turn copy all its form types (and their data).

Note: The MO option must be set in both the Source and Target systems for a given MO.

Configuring Custom Objects for Migration

During the implementation and extension of the product, new custom administrative maintenance objects may be introduced. If your implementation would like to migrate records in those maintenance objects using the Configuration Migration Assistant, additional steps must be performed, which are highlighted in the following sections.

Physical Business Object

As described in Understanding the BO Filtering Process, the migration plan requires a business object for its instruction. The business object is used to identify the records eligible for inclusion in the migration. Assuming your custom tables use one or more “logical” business objects for their processing, your implementation must decide if these business objects are appropriate for use by the migration plans, or if a physical BO is warranted. If so, create an appropriate physical BO.

Review MO Option Configuration

The following points highlight maintenance object (MO) configuration that should be reviewed or updated to support CMA:

- If a physical BO was created (above), link it to the MO as an option using the appropriate option type.

- Be sure that your MO defines an appropriate FK Reference and includes an Option on the MO that identifies the FK Reference. This is used by various portals and zones for CMA when showing detail about records being imported into the target region. Also be sure that this FK reference defines an Information program.

- As described in Identifying Tables to Exclude From Migrations, an MO option is used to identify child tables for an MO that should never be included in a migration. If your custom maintenance object includes a standard Log table, than the recommendation is to list that table as an excluded table. Depending on the specific design of the maintenance object, there may be other child tables to define.

Characteristic Type Configuration

The CMA import process will attempt to create a log record for any administrative object that includes a log table. If your implementation has introduced any custom administrative tables that you plan to include in a migration request and it includes a log table, you must, to ensure that the log creation is successful, add your log table as a valid characteristic entity to the characteristic type F1-MGO (Migration Object).

Navigate to Characteristic Type and select the characteristic type F1-MGO. Navigate to the Characteristic Entity tab and add a row to include the characteristic entity for your custom maintenance object's log table.

Standard CMA Configuration

Create one or more migration plans for the new object, depending on the type of data in the maintenance object and the types of migrations you envision:

- If you have implemented only one "logical" business object used to define the data in the MO, then a single migration plan that references the this BO (or the maybe the MO's physical BO) is appropriate.

- If you have implemented more than one "logical" business object, would the data for multiple business objects get copied together? Then perhaps a single migration plan that references the MO's physical BO is appropriate.

- Are there additional foreign keys defined using mapXML in the business object(s) for the MO? If so, then it is recommended to include sub-instructions to define the links. At this point, if multiple "logical" BOs exist, your implementation may choose to define all the additional elements in the same migration plan or choose to define separate migration plans for each logical BO.

- Your implementation may decide to define more than one migration plan for the same type of record based on the types of migrations you plan to include. For example, you may decide to include a migration plan that copies only the records in this maintenance object. You may decide to define another migration plan that copies the records in this MO along with related records in another MO (for a special type of migration). Having said that, be sure to design the migration plan with reuse in mind to minimize maintenance efforts.

In order to support Entity List migration request, a default migration plan must be defined as an option on the maintenance object. This should be a single migration plan that supports all types of business objects for the MO.

If your implementation has a template migration request to use for targeted or wholesale migrations, include the new migration plan(s) as appropriate.

CAUTION:

Important! New migration plans and migration requests should follow naming conventions. Refer to System Data Naming Convention for more information.

The CMA Execution Process

The following diagram illustrates a high-level view of the Configuration Migration Assistant execution process. The subprocesses illustrated here are described in more detail in the following sections.

Next in This Section

- Exporting a Migration

- Importing and Applying a Migration

Exporting a Migration

The migration export process begins in the source environment by defining a Migration Data Set Export, which specifies a defined Migration Request and provides a file name and description for the export file. After the data set is defined and saved, the Migration Data Set Export Monitor batch job can be submitted generate the export file.

The following topics provide more detail about this process.

Next in This Section

- Migration Data Set Export

- Export Lifecycle

Migration Data Set Export

To migrate data from one region to another, define a Migration Data Set Export. This establishes the export file name and identifies the migration request.

To view an existing migration data set export, navigate using Admin > Implementation Tools > Migration Data Set Export. Use the query criteria to locate the desired data set.

Note that you can also initiate the creation of an export data set from the Migration Request portal using the Export button.

The export requires the name of an existing Migration Request.

Enter a unique File Name for the export. Do not use spaces in the name, and do not enter the file extension or a path. The output location and file extension of the intended export file, which should appear in the Export Directory and File Suffix labels, are defined as described in the topic Migration Assistant Configuration.

Enter an Export Description to provide information about the purpose of the export. Note that this field is not language enabled.

The Source Environment Reference is for information purposes. It should be populated with text that provides a meaningful description of the source environment. The default value is the URL of the source environment.

Export Lifecycle

The following diagram describes the lifecycle of a Migration Data Set Export (data set).

The following points describe the lifecycle.

- The data set is created in Pending status.

- A user may choose to temporarily Cancel a pending data set to prevent it from being processed. The user can later return it to the Pending state when desired.

- The record remains in Pending until its monitor batch job is submitted. The Migration Data Set Export Monitor (F1–MGDPR) selects pending records and transitions them to Set up data. Refer to Running Batch Jobs for more information.

- Set up data is a transitory state that includes the algorithm that does the work of determining the objects to include in the export and group related objects together into a transaction. If everything is successful, the export file is written to the appropriate file location and the record transitions to Exported. If an error is detected, the process stops and the record transitions to Error.

- If a record is in error and it is possible to correct the error, the record may be transitioned back to Pending to try again.

When the process is marked as Exported, the export file can be imported into the target system.

Note: The export process creates a file, providing the benefits of having a standalone file. It can be stored in a version control system for audit purposes or provided to others for import purposes.

CAUTION:

Under no circumstances should exported data files be edited manually. Doing so could cause data corruption when the file content is applied to the target environment.

Note: The export functionality is supported using the business object Migration Data Set Export (F1-MigrDataSetExport). The expectation is that implementations will use the delivered base business object and its logic and will have no reason to implement a custom business object for the CMA export process.

Importing and Applying a Migration

The import process is broken down into four general steps: Import, Compare, Approve, Apply. The following points provide an overview of the steps.

- Import. The first step covers importing the file and creating appropriate Migration Import records in the target environment to facilitate the subsequent steps.

- Compare. The compare step reviews each object that is in the import file and compares the object in the import against the equivalent record in the target environment. The comparison step results in noting which objects are unchanged, which are new (and the appropriate SQL to insert them) and which objects are changed (and the appropriate SQL to update them). Based on user configuration at import time, the objects that qualify for the import may be in a state that requires review or may be pre-approved.

- Approve. Once the comparison is complete, the user should review the results. There may be records marked for review. All of these records must be approved or rejected before the import can proceed. When the user is satisfied with the results of the comparison and has completed the review, the import is marked to proceed to the Apply step. Optionally, a migration import may be configured to automatically apply.

- Apply. This is the final step and is the step where the records in the target environment are added or updated. Because of potential high volumes of data and because of possible dependencies between records, this step supports two levels of attempting to apply the records. There is an apply step at the object level and an apply step at the transaction level. This will be described in more detail below.

Next in This Section

- Import Step

- Compare Step

- Approval Step

- Apply Step

- Adjusting Data Prior to Comparing

- Import Process Summary

- Cancelling a Data Set

- Additional Note Regarding Imports

- Caching Considerations

- Maintaining Import Data

Import Step

The import process starts with verifying the import directory configured as described in the following topic Master Configuration - Migration Assistant and ensuring that the exported file is located in that directory. Then, in the target environment, a Migration Data Set Import record should be created. The user indicates the file name.

In addition, the user decides what the default status should be for resulting objects.

- The Default Status for Add sets the default status for objects that are determined to be new during the import comparison process. The default is to automatically set new objects to Approved status. Other options are to set any new objects to Rejected or Needs Review status.

- The Default Status for Change sets the default status for objects that are determined to be changed during the import comparison process. As with new objects, the default for changed objects is Approved, with Rejected or Needs Reviewoptions available.

The user may also configure the Automatically Apply flag to Yes. This allows for use cases where the migration is repetitive and has been tested and the user feels that there is no need for manual approval. Note that when configuring this setting, neither of the Default Status values may be set to Needs Review and at least one must be set to Approved.

The file to import contains a list of all the objects included in the export. Any objects that the export step determined to be related have been grouped into “transactions”. Once the Migration Data Set Import is created, the next step is for the system to read in the file and create Migration Transactions and Migration Objects.

The following is a portion of the Migration Data Set Import lifecycle as it pertains to the import step.

The following points describe the lifecycle.

- The data set is created in Pending status.

- The record remains in Pending until its monitor batch job is submitted. The Migration Data Set Import Monitor (F1–MGDIM) selects pending records and transitions them to Ready to Compare. Refer to Import Process Summary and Running Batch Jobs for more information.
The Ready to Compare state has an algorithm that is responsible for reading the related import file and creating the migration transactions and migration objects. The data set remains in this state until the comparison step is complete.

Note: A user may choose to Cancel a data set. Refer to Cancelling a Data Set for more information.

The following diagram highlights the relationships of the resulting migration import records.

The migration transaction and migration object each have their own lifecycle that will help manage the subsequent compare and apply steps. At the end of the import step, the status values of the three types of records are as follows:

- Migration Data Set Import is in the Ready to Compare state.

- Migration Transaction is in the Pending state.

- Migration Object is in the Pending state.

Note: The import functionality is supported using business objects supplied by the base product. The expectation is that implementations will use the delivered base business objects and their logic and will have no reason to implement a custom business objects for the CMA import process. The base business objects are Migration Data Set Import (F1-MigrObjectImport), Migration Transaction (F1-MigrTransactionImport) and Migration Object (F1-MigrObjectImport).

Compare Step

The import step results in the creation of one or more migration objects, one for each record selected in the export based on the export's migration request and its configuration. Related objects are grouped together in migration transactions. The next step in the import process is the Comparison step. In this step, the data captured by the import file for each object is compared to the view of that object in the target environment.

To cater for a possible large volume of objects, the comparison is done via a batch monitor. To aide in performance of the process, the monitor is performed on the migration objects so that it can be run multi-threaded. Once the objects are finished with the comparison, the migration transactions and the migration data set should be updated with an appropriate overall status before continuing to the next step. As a result, the comparison actually requires three steps: Migration Object Comparison, Migration Transaction Status Update and Migration Data Set Export Status Update. The steps are explained in detail in the following sections.

Note: Refer to Running Batch Jobs for more information about streamlining the various steps in the process.

Migration Object Compare

This is the main step of the comparison. The Migration Object Monitor (F1–MGOPR) selects pending migration object records and transitions them to Comparing. This is a transitory state that includes the algorithm that does the work of comparing. There are various possible outcomes that could occur based on the logic in the algorithm. The following diagram illustrates a portion of the migration object lifecycle that pertains to comparison.

The following points describe the lifecycle.

- When Pending records are selected by the monitor batch job, it transitions to Comparing. If the migration object refers to one or more pre-compare algorithms, they are executed to adjust the data prior to comparison. Then algorithm will determine the appropriate next state by comparing the source data to the target data.

- If the record in the migration object is found in the target environment and the data is exactly the same, the record transitions to Unchanged (with the object action value also set to Unchanged).

- If the record in the migration object is found in the target environment and the data is different, the algorithm sets the object action value to Change and generates the appropriate SQL to be used later in the Apply step to update the record. It then transitions to Approved, Needs Review or Rejected based on the Default Status For Change setting captured on the Data Set.

- If the record in the migration object is not found in the target environment, the algorithm sets the object action value to Add and generates the appropriate SQL to be used later in the Apply step to insert the record. It then transitions to Approved, Needs Review or Rejected based on the Default Status For Add setting captured on the Data Set.

- If there is any issue with attempting to parse the object data from the import, the record transitions to Error Comparing.

- If there is any reason that the imported object is not valid for import, the record transitions to Cannot Apply. The log will be updated with the error that caused the record to transition to this state. An example is that perhaps the record was exported in a different version of the product and has additional elements that are not recognized in this version.

Note: Refer to Cancelling a Data Set for information about cancelling a data set and its impact on its related objects.

Migration Transaction Status Update

After the import step, the migration transaction remains in the Pending state until all its objects have completed the comparison step. At that point, the status of the transactions should be updated based on the results of their objects. The Migration Transaction Monitor (F1–MGTPR) selects pending migration transaction records and runs its monitor algorithms. There are various possible outcomes that could occur based on the logic in the algorithms. The following diagram illustrates a portion of the migration transaction lifecycle that pertains to comparison.

The following points describe the lifecycle possible next states after Pending.

- If any related migration object is in the Error Comparing state, the transaction transitions to Error Comparing.

- If all related migration objects are in the Unchanged state, the transaction transitions to Unchanged.

- Otherwise, the transaction transitions to Ready to Apply. This means that at least one object is in an “apply-able” state.

The transaction remains in the Ready to Apply state until a user has approved the data set to move to the Apply step and the transaction’s related objects have attempted to apply themselves. This is described in more detail below.

Note: Refer to Cancelling a Data Set for information about cancelling a data set and its impact on its related objects.

Migration Data Set Import Status Update

Once all the objects and all transactions have been updated via the previous two steps, the migration data set export must be updated based on the results of their transactions. The Migration Data Set Import Monitor (F1-MGDIM) selects Ready to Compare data sets and runs its monitor algorithms. Note that this is the same monitor process that is used to select Pending data sets. There are various possible outcomes that could occur based on the logic in the algorithms. The following diagram illustrates the portion of the migration transaction lifecycle that pertains to comparison.

The following points describe the lifecycle possible next states after Ready to Compare.

- If any related migration transactions is in the Error Comparing state, the data set transitions to Error.

- If all related migration transactions are in the Unchanged state, the data set transitions to Unchanged.

- Otherwise, the transaction transitions to Awaiting Approval. This means that there are no errors and at least one object is in an “apply-able” state.

The data set remains in the Awaiting Approval state until a user decides that the data set and all its records are ready to progress to the Apply step.

Note: A user can choose to cancel a data set at any time while it is in progress. Refer to Cancelling a Data Set for more information.

Approval Step

Once the comparison is complete and the data set transitions to the Awaiting Approval state, a user needs to progress the data set to Apply Objects to trigger the Apply step. The following points describe steps a user may take during the approval step.

- If the data set configuration for the Default State for Add and Change was set to Approved, then any migration object that is determined to be eligible for the Apply step will be in the Approved state. In this situation, a user may want to review the data set and its transactions and objects to see verify that the results make sense. At that time, the user is able to move an object to Needs Review or Rejected as appropriate.

- If the data set configuration for the Default State for Add and Change was set to Needs Review for either option, then each migration object in the Needs Review state must be reviewed and the user must either Reject or Approve each object before moving to the Apply step.

- If the data set configuration for the Default State for Add and Change was set to Rejected for either option, the assumption is that the rejected records don’t need to be reviewed. But if a user finds a rejected record that shouldn’t be rejected, it may be transitioned to Approved (or Needs Review) as appropriate.

Once the user is comfortable with the data set's results and no more objects are in the Needs Review state, the user should transition the record to Apply Objects. This will initiate the Apply step.

Alternatively, if the Automatically Apply flag was set to Yes when creating the import record, the import data set will progress from Awaiting Approval to Apply Objects. Refer to Import Process Summary for more information.

Note: Refer to Maintaining Import Data for details about the pages provided to help the user review a data set and its transactions and objects to help in the approval step.

Note: A user can choose to cancel a data set at any time while it is in progress.

Apply Step

The apply step is the step where records in the target environment are added or updated. Like the comparison step, the apply step is actually multiple steps to optimally handle high volume and dependencies between records as smoothly as possible.

Note: Refer to Running Batch Jobs for more information about streamlining the various steps in the process.

Before explaining the apply steps in detail, the following points highlight the type of data that may be included in a given data set.

1. Records that have no foreign keys and therefore no dependencies on other records. Examples: Message, Display Profile.

2. Records that have foreign keys that may already be in the target. Examples: Algorithms for existing algorithm types, To Do Roles for existing To Do Types.

3. Records that have foreign keys that are new records but also part of the migration. CMA detected the relationship at export time and grouped the objects in the same transaction. Example: Script-based Algorithm Type where the script is also in the migration.

4. Records that have foreign keys that are new records but also part of the migration. CMA did not detect the relationship. This may occur if the reference the foreign key is in a XML or parameter column and the migration plan did not include an instruction to explicitly define the relationship. Example, a Zone that references a visibility script.

5. Records that have circular references where both records are new and are part of the migration. CMA detected the relationship at export time and grouped the objects in the same transaction. Example: plug-in Script for a BO plug-in spot. The script references the BO and the BO references an algorithm for the script’s algorithm type.

To handle high volume data, the first step in the apply process is to perform the apply logic at the migration object level via a multi-threaded batch job. This should result in all records in categories 1 and 2 above being applied successfully.

For records in categories 3 and 4 above, if a record with a foreign key is added or updated before its related record, the validation will fail. However, if the related record is added first and then the record referring to it is added, validation will pass. Because the migration objects are not ordered, the multi-threaded batch process may not process records in the desired order. To overcome this potential issue, the Apply step has special functionality, described in detail below.

For records in category 5 above, the circular reference will mean that the apply process at the object level will not successfully add or update these records. The apply process at the transaction level will cover these records. This is described in detail below.

Apply Objects

Once the Data Set is in the state of Apply Objects, the Migration Object Monitor - Apply process (F1-MGOAP) runs to attempt to apply the objects. The background process in conjunction with the Apply algorithm have special functionality to ensure records in categories 3 and 4 (above) successfully apply during this step:

- The Migration Object Monitor - Apply process is a special one that continually re-selects records in the Approved state until there are no more eligible records to process.

- When an error is received in the Apply Object algorithm, the algorithm increments an "iteration count" on the migration object record. If the iteration count does not exceed a maximum count (noted in the algorithm), the object remains in the Approved state and is eligible to be picked up for processing again. If the iteration count exceeds the maximum defined in the algorithm, the record transitions to the Error Applying state.

Note: When submitting this Apply batch job, be sure to set the number of threads to a number that does not exceed the number of threads supported by the thread pool worker. Doing this will cause the ‘excess’ threads to wait for the supported number of threads to finish.

The following diagram is the portion of the migration object lifecycle that pertains to the Apply step.

At the completion of the Apply monitor process, typically the objects will be in the Applied state or the Error Applying state. The records in the Error Applying state are in that state for one of two reasons.

- They are in category 5 described above where the records have a circular reference with another record. For this scenario, the Apply Transactions step described below should successfully apply the records.

- There is some other error that is unrelated to the records in the current migration. In this case, manual intervention may be required. Refer to the Resolving Errors section below for more information.

As shown in the diagram, the Apply Objects algorithm may also detect a reason that the object cannot be applied. This may occur if the object in the target environment has been updated since the comparison step, making the SQL captured at that point no longer applicable. If this occurs, after the current migration is fully applied, the original file may imported again, and new comparisons can be generated and applied.

Apply Transactions

Ideally, after the Apply Objects step, all the objects are Applied or are in Error Applying due to the "circular reference" situation. The typical next step is to turn over responsibility to the transactions. The migration transactions can then attempt to apply their objects in bulk.

In order to ensure that multiple background processes are not trying to select migration objects to run the Apply step, the Transactions are only eligible to attempt to "apply my objects" if the Data Set is in the Apply Transactions state.

A monitor algorithm (executed by the data set monitor batch process) on the Apply Objects state checks to see if all migration objects are no longer Approved or the count of records in Error Applying does not exceed a configured limit. If so, it automatically transitions the record to the Apply Transactions state.

If the number of objects in Error Applying exceeds a configured limit, the monitor algorithm does not automatically transition the record. In that case, a user must determine if the large number of errors can be resolved or manually transition to Apply Transactions (despite the large number of errors). The Resolving Errors section below describes alternative steps that the user may take if there are errors.

Once the Data Set is in the state of Apply Transactions, the Migration Transaction Monitor - Apply process (F1-MGTAP) runs. It attempts to apply the transaction's objects. If no migration objects are in error, the migration transaction simply transitions to Applied. If any of the migration objects are in Error Applying, the background process and the Apply algorithm have special functionality to try to overcome dependencies in migrated objects:

- The Apply algorithm selects all migration objects in error and performs all their SQL, then validates all the records. If there are objects in the transaction with circular references, they should pass validation at this point.

- Because there may still be some dependencies across transactions, similar error handling described in the Apply Objects step occurs here. When an error is received in the Apply Transaction's Object algorithm for any of the objects in the transaction, the algorithm increments an "iteration count" on the migration transaction record. If the iteration count does not exceed a maximum count (noted in the algorithm), the transaction remains in the Ready to Apply state and is eligible to be picked up for processing again. If the iteration count exceeds the maximum, the record transitions to the Error Applying state. Note that if any objects in the transaction are in error, none of the objects are applied. They all remain in error.

- The Migration Transaction Monitor - Apply process is a special one that continually re-selects records in the Ready to Apply state until there are no more eligible records to process.

Note: When submitting this Apply batch job, be sure to set the number of threads to a number that does not exceed the number of threads supported by the thread pool worker. Doing this will cause the 'excess' threads to wait for the supported number of threads to finish, erasing the benefit of the iteration processing.

The following diagram is the portion of the migration transaction lifecycle that pertains to the Apply step illustrating the points above.

If at the end of the transaction level Apply process there are transactions in error (and therefore there are still objects in error), a user must review the errors and determine how to fix them. Refer to the Resolving Errors section below for more information.

Resolving Errors

As mentioned in the previous sections, errors may be received after the Apply Objects process runs. If the number of records in error is below a certain limit (and the data set monitor batch job is submitted to execute the monitor algorithms) the system will automatically transition the data set to the Apply Transactions. If the monitor batch job is not run or if the number of objects in error exceeds a certain limit, a user must make the decision after viewing the errors in the Objects in Error zone on the Migration Data Set Import portal.

- If the errors appear to be dependency related, the user can decide to let the "transactions apply their objects" and transition the data set to Apply Transactions, described above.

- If the errors appear to be related to an outside issue that can be manually resolved, the user may choose to fix the issue and redo the Apply Objects step.

- The user may also decide to reject one or more objects to remove them from the migration.

After the Apply Transactions step, if there are still errors, a user must review the records and determine how to proceed. Errors are visible in the Transactions in Error zone on the Migration Data Set Import portal.

- The user may decide to reject one or more objects to remove them from the migration.

- The user may manually resolve an issue external to the migration and then decide to do one of the following:

- Redo the Apply Objects step. This is recommended if there are a large number of Objects still in error and not a large number of dependencies expected. The benefits of running the Apply Objects multi-threaded will ensure that the process runs efficiently.

- Redo the Apply Transactions step.

Because the objects and transactions are in Error Applying, in order to "retry" the Apply step after manually fixing an error, the system needs to move the records back to the state that allows them to be picked up by the appropriate Apply process. For migration objects, records need to be moved back to Approved. For migration transactions, records need to be moved back to Ready to Apply. The following points describe the Retry logic for migration objects.

- If a user decides to Retry Objects (using an action button on the Migration Data Set Import page), the data set transitions to the Retry Objects state. At this point the Migration Object monitor must be run.

- The monitor on the Error Applying state for the objects detects that the data set is in the state of Retry Objects and that triggers the transition back to Approved.

- The next step is to transition the data set from Retry Objects to Apply Objects. This may be done manually or by running the Migration Data Set Import monitor process.

- Now the objects are eligible to be picked up by the object level Apply process.

Analogous logic exists for the migration transactions.

- If a user decides to Retry Transactions (using an action button on the Migration Data Set Import page), the data set transitions to the Retry Transactions state. At this point the Migration Transaction monitor must be run.

- The monitor on the Error Applying state for the transactions detects that the data set is in the state of Retry Transactions and that triggers the transition back to Ready to Apply.

- The next step is to transition the data set from Retry Transactions to Apply Transactions. This may be done manually or by running the Migration Data Set Import monitor process.

- Now the transactions are eligible to be picked up by the transaction level Apply process.

The retry logic may also occur when transitioning between the Apply Objects and Apply Transactions depending on whether or not there are errors. The following scenario highlights this point.

- After the Apply Objectsstep there are objects in Error Applying. The data set transitions to Apply Transactions and the Apply step is done at the transaction level.

- After the Apply Transactions step there are transactions in Error Applying.

- User chooses to try to apply objects again (by clicking Retry Objects). The steps outlined above for retrying objects are followed at this point.

- After the apply objects, user may choose to retry objects again (after fixing errors if applicable).

- At some point the user will transition toApply Transactions again. If there are transactions in Error Applying, the system will automatically transition the data set to Retry Transactions and the steps outlined above for retry transactions are followed.

Finalize Apply Step

Once all the migration objects for a migration transaction are in a final state (Applied, Rejected or Cannot Apply), the migration transaction transitions to the Applied state. Once all the migration transactions are in the Applied state, the Migration Data Set record transitions to the Completed and the import is complete.

Note: To review the full lifecycle for each record, refer to the Business Object - Summary tab in the application metadata for the base business objects Migration Data Set Import (F1-MigrObjectImport), Migration Transaction (F1-MigrTransactionImport) and Migration Object (F1-MigrObjectImport).

Adjusting Data Prior to Comparing

Some records may have data that is specific to the environment it is in and won't apply in the target environment. In such cases, an algorithm plugged into the migration plan primary instruction may be used to adjust the data when importing. This algorithm is executed by the comparison algorithm before any comparison is performed. Algorithms of this system event receive the view of the source record (being imported) and the view of the existing record in the target region, if it exists. The data is provided using the physical BO of the migration plan’s maintenance object. The algorithm may make changes and pass a new view of the record that should be used for the comparison. This system event supports multiple algorithms that are executed in sequence. Each algorithm receives the original record’s data, the target record’s data (if applicable) and the ‘new’ view of the data (as populated by previous algorithms, if any). The final ‘new’ view of the data is used for the object comparison.

Fastpath: Refer to Base Business Objects for more information about physical BOs.

Some examples of records that may require import algorithms.

- Batch Control references its next batch sequence number along with snapshot information like the last run date / time. This information is only relevant with respect to its environment. The instruction for a batch control can include an algorithm to not overwrite the batch sequence number when copying a batch control.

- Some products include administrative objects that reference a master data object. Master data objects are not copied as part of CMA. An import algorithm may be used to adjust the referenced master data foreign key when importing, for example to reset it (or not overwrite when updating). If the algorithm knows how to find the appropriate master data record to link, that may also be included.

Note that it is possible to use the algorithm to "reset" the source data as a way of indicating that the record should not be imported. For these situations, the migration object comparison step will transition the record to Unchanged and will use an object action value of Canceled. (Note that object action is a simple lookup value. The record is not transitioned to the Canceled BO state as to reserve that status for user initiated cancellations of the object or one of its parent records). This technique not expected to be used often because ideally using appropriate selection criteria at export time should ensure that the only records exported are those that should be imported.

Note: Legacy ‘Import’ system event. The system originally provided an Import system event / plug-in spot. The purpose of algorithms for this plug-in spot were similar in that they were meant to adjust imported data prior to adding or updating. The algorithms were executed in the Apply step. The logic does not allow for easily interacting with the record using a BO. This makes it difficult to use a plug-in script as the plug-in type. In addition, it is difficult to update elements in an XML column. The support for the plug-in spot will be removed in a future release. Algorithms to adjust the data should be using the pre-compare system event.

Import Process Summary

The following table summarizes the steps required to complete the import process from start to finish. Note that this section only a summary and assumes that you are familiar with the details described in the previous sections. It highlights what steps are manual and what steps are performed by a batch monitor process. For each step, the table highlights the Next Action sequence that would occur. For the Apply steps, there are two parts where multiple next actions are possible based on whether there are errors and the user’s decision on how to resolve the error. Refer to Resolving Errors for more information. The possible next actions have the same sequence with a letter following the sequence highlighting the action to take based on the results of the previous step.

Note: When running the Apply batch jobs, be sure to set the number of threads to a number that does not exceed the number of threads supported by the thread pool worker.

Also note that a sequence and action marked in bold is considered the “normal path”.

Step

Seq

Action

Manual / Batch

Portal - Action

Batch Control

Record Impacted - Resulting Status

Next Action Sequence

Import

10

Create Import record

Manual

Migration Data Set Import - Add

Migration Data Set Import - Pending

11

11

Import file

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Ready to Compare

Migration Transaction - Pending

Migration Object - Pending

20

Compare

20

Migration Object Compare

Batch

F1-MGOPR - Migration Object Monitor

Migration Object - Approved, Needs Review, Rejected, Unchanged or Error Comparing

21

21

Migration Transaction status update

Batch

F1-MGTPR - Migration Transaction Monitor

Migration Transaction - Ready to Apply, Unchanged or Error Comparing

22

22

Migration Data Set Import status update

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Awaiting Approval, Apply Objects (if configured for Automatic Apply), Unchanged or Error

30

Approval

30

Review comparison results, approve / reject as needed

(This step is skipped if the data set is configured for Automatic Apply)

Manual

Migration Data Set Import, drill in to the Transactions / Objects as necessary.

Migration Object - Approved or Rejected (no records should be in Needs Review)

Migration Data Set Import - Apply Objects

40

Apply

40

Apply Objects

Batch

F1-MGOAP - Migration Object Monitor - Apply

Migration Object - Applied or Error Applying

41

Appropriate next action is based on error review, if applicable.

41a

Migration Data Set Import status update - auto transition to Apply Transactions.

Only applicable if the number of migration objects in Error Applying is below a threshold

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Apply Transactions

42

41b

Migration Data Set Import status update - manual transition to Apply Transactions.

Occurs if user reviews errors and determines that they may be resolved in the Apply Transaction step.

Manual

Migration Data Set Import - click Apply Transactions

System detects that all the transactions are in the Ready to Apply state and proceeds to the Apply Transactions state.

Migration Data Set Import - Apply Transactions

42

System detects that there are transactions in the Error Applying state and transitions instead to the Retry Transactions state.

Migration Data Set Import - Retry Transactions

45

41c

Migration Data Set Import status update - manual transition to Retry Objects.

Occurs if user reviews errors and decides to fix an external error and wants to try the batch level Apply again at the object level.

Manual

Migration Data Set Import - click Retry Objects

Migration Data Set Import - Retry Objects

44

42

Apply Transactions

Batch

F1-MGTAP - Migration Transaction Monitor - Apply

Migration Transaction - Applied or Error Applying

Migration Object - Applied or Error Applying

43

Appropriate next action is based on error review, if applicable.

43a

Migration Data Set Import status update - auto transition to Completed

Applicable if all transactions are Applied

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Completed.

N/A

43b

Migration Data Set Import status update - manual transition to Retry Objects.

Occurs if user reviews errors and decides to fix an external error and wants to try the batch level Apply again at the Object level.

Manual

Migration Data Set Import - click Retry Objects

Migration Data Set Import - Retry Objects

44

43c

Migration Data Set Import status update - manual transition to Retry Transactions.

Occurs if user reviews errors and decides to fix an external error and wants to try the batch level Apply again at the Transaction level.

Manual

Migration Data Set Import - click Retry Transactions

Migration Data Set Import - Retry Transactions

45

44

Migration Objects status update from Error Applying back to Approved.

Occurs if user chose to Retry Objects.

Batch

F1-MGOPR - Migration Object Monitor

Migration Object - Approved

Migration Data Set Import status update from Retry Objects to Apply Objects

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Apply Objects

40

45

Migration Transactions status update from Error Applying back to Ready to Apply.

Occurs if user chose to Retry Transactions or if the user transitions to Apply Transactions and the system detects that there are Transactions in the Error Applying state.

Batch

F1-MGTPR - Migration Transaction Monitor

Migration Transaction - Ready to Apply

42

Migration Data Set Import status update from Retry Objects to Apply Objects

Batch

F1-MGDIM - Migration Data Set Import Monitor

Migration Data Set Import - Apply Transactions

42

The following table summarizes the batch monitor jobs that are used in the import process. You can see that there are special monitor processes for the Apply step for both the Object and Transaction. However, for all other states that have monitor logic, the standard monitor process for that MO is used.

Batch Control

Description

Comments

F1-MGDIM

Migration Data Set Import Monitor

Processes data set records in the following states:

- Pending

- Ready to Compare

- Apply Objects

- Retry Objects

- Apply Transactions

- Retry Transactions

F1-MGTPR

Migration Transaction Monitor (Deferred)

Processes transaction records in the following states:

- Pending

- Error Applying

F1-MGTAP

Migration Transaction Monitor - Apply

Processes transaction records in the Ready to Apply state where the data set is in the Apply Transactions or Canceled state.

Note: Be sure to set the number of threads to a number that does not exceed the number of threads supported by the thread pool worker.

F1-MGOPR

Migration Object Monitor

Processes object records in the following states:

- Pending

- Needs Review (check for Data Set cancellation)

- Rejected (check for Data Set cancellation)

- Error Applying

F1-MGOAP

Migration Object Monitor - Apply

Processes object records in the Approved state where the data set is in the Apply Objects or Canceled state.

Note: Be sure to set the number of threads to a number that does not exceed the number of threads supported by the thread pool worker.

Refer to Running Batch Jobs for more information about managing the batch jobs, including ways to automate the above steps.

Cancelling a Data Set

A user may choose to Cancel a data set to prevent it from being processed at any point during the process.

If related migration transactions or migration objects have already been created, they will not be canceled as part of the data set getting canceled (due to possible high volumes of related records). They will be canceled the next time an appropriate monitor batch process runs. The child records checks to see if the data set has been canceled prior to any state transition.

Additional Note Regarding Imports

The following points describe miscellaneous comments related to Migration Import.

- CMA relies on the fact that database referential integrity constraints are not in place, and that the SQL statements can be run in any order within the transaction. Any archiving solution that requires referential integrity constraints (such as Information Lifecycle Management) would not be possible on this data. Given that CMA migrations comprise administrative data and not transactional data, this should be a reasonable exception.

- The validation that is performed is only via the Page Validate service. BO validation algorithms are not executed. Page validation does not include validation of the business object against the schema (for example, for required fields, field sizes, etc.).

- If multiple migration requests are exported at the same time, on the import side, you should consider importing, reviewing, and applying an entire file/data set before moving on to the next one. The reason is that if objects are included in more than one file, two sets of "inserts" will be generated, but only the first will succeed. The second will cause the object to transition to "Cannot Apply". If instead you wait until the first file is completed before importing the second, the second data set will not generate any SQL for the object, since it has already been inserted. It's a matter of efficiency: If you first import all files and then try to apply all, you'll have to identify the duplicated object as an error and then mark the object as rejected before applying the transaction. This may also be avoided by using a Group migration request to include all objects in one file rather than multiple files.

Caching Considerations

Because CMA updates administrative data that is usually read from a cache, after a successful migration, the target region now has new administrative data which needs to be part of various caches. It is recommended to flush the server cache (which will trigger a 'global' flush of the cache). If the thread pool workers in the target region are configured to refresh their caches when a global flush is requested, then this is the only step required. If not, then the F1–FLUSH batch job should also be submitted to refresh the caches used in batch processing.

Fastpath: Refer to Caching Overview for more information.

Maintaining Import Data

This section describes the portals provided to add, view and maintain migration import data.

Next in This Section

- Migration Data Set Import

- Migration Transaction Portal

- Migration Object Portal

Migration Data Set Import

Use the Migration Data Set Import portal to view and maintain migration data set import records. Refer to Importing and Applying a Migration for an overview of the import process.

Navigate using Admin > Implementation Tools > Migration Data Set Import. You are brought to a query portal with options for searching for import data sets. In addition, the query provides an option to specifically search for data sets that have either objects in error or transactions in error.

Once a data set has been selected, you are brought to the maintenance portal to view and maintain the selected record. The following zones are visible on the main tab:

- Migration Data Set Import. This zone contains display-only information about the selected record. Please see the zone’s help text for information about this zone’s fields.

- Migration Data Set Transactions. This zone is visible once the Import Step has occurred and lists all the transactions that are related to the data set. To see more information about a specific migration transaction, click the hypertext for its ID. This brings you to the Migration Transaction portal.

- Migration Data Set Impacted Object Summary. This zone is visible once the Import Step has occurred and lists the objects that are related to the data set. To see more information about a specific migration object, click the hypertext for its ID. This brings you to the Migration Object portal. A user may choose to update the status of one or more records by checking the records and clicking Approve, Reject or Needs Review accordingly.

- Migration Data Set Objects in Error. This zone is only visible if there are objects for this data set in a non-final status that have errors. It indicates the error for each object. A user may use this zone to review errors after the monitor batch job to apply objects completes. Using the error information shown, the user can choose to drill into the record to transition it to Error Applying or choose to manually fix the cause of the errors and click Retry Objects. The user may also choose to select one or more records to Reject.

Note: Refer to Apply Step for more information about resolving errors.

- Migration Data Set Transactions in Error. This zone is only visible if there are transactions for this data set in a non-final state that have errors. It indicates the error for each transaction. A user may use this zone to review errors after the monitor batch job to apply transactions completes. The errors received when attempting to apply objects at the transaction level may differ from those received when attempting to apply objects at the object level. A transaction log is created for each object error received and these exceptions are shown in this zone.

Note: Refer to Apply Step for more information about resolving errors.

Migration Transaction Portal

This page appears after drilling into a specific migration transaction from the migration data set portal or from the migration object portal.

Refer to Importing and Applying a Migration for an overview of the import process.

The following zones are visible on the main tab:

- Migration Transaction. This zone contains display-only information about the selected record. Please see the zone’s help text for information about this zone’s fields.

- Migration Transaction Objects. This zone lists the objects that are related to the data set. To see more information about a specific migration object, click the hypertext for its ID. This brings you to the Migration Object portal. A user may choose to update the status of one or more records by checking the records and clicking Approve, Reject or Needs Review accordingly.

Migration Object Portal

This page appears after drilling into a specific migration object from the migration data set portal or from the migration transaction portal.

Refer to Importing and Applying a Migration for an overview of the import process.

The Migration Object zone contains display-only information about the selected record. Please see the zone’s help text for information about this zone’s fields.

The Migration Object - List of SQL Statements zone lists the SQL statements that have been generated as a result of the comparison step.

The Migration Object - Algorithms zone displays any pre-compare algorithms that are associated with the migration plan for this migration object.

Running Batch Jobs

There are several batch jobs that are part of the CMA process, especially the import step (which are highlighted in Import Process Summary). And in some cases, a single batch jobs may process multiple states in the same business object lifecycle. Implementations must decide the best way to manage the batch job submission depending on how they plan to work.

- Batch scheduler. If an implementation wishes to put these batch jobs in the batch scheduler, a given job may need to be included several times to manage progressing the records to completion.

- Timed Batches. The batch controls can be configured as timed batches so that they run every N minutes based on the setting. This allows for the batch jobs to run periodically and process whatever is ready. A user doesn’t have to manually submit a batch request. Navigate to the Batch Control page and select the appropriate batch controls. For each one, change the Batch Control Type to Timed. Fill in the additional information that appears for timed batches.

- Event Driven. The system provides BO enter plug-in algorithms and batch control post processing plug-in algorithms that automatically submit the appropriate next batch job for that step in the process. This allows for as much automation as possible for the steps that don't require user input. Note that configuration is required because the BOs / batch controls are not configured for this scenario by default. The following table highlights the BO and status where an algorithm may be plugged in and the name of the algorithm to use.

Business Object

Status

Algorithm

Migration Data Set Export

Pending

F1-MGDPR-SJ (Submit Migration Data Set Export Monitor).

Migration Data Set Import

Pending

F1-MGDIM-SJ (Submit Migration Data Set Import Monitor).

Ready To Compare, Retry Objects

F1-MGOPR-SJ (Submit Migration Object Monitor).

Apply Objects

F1-MGOAP-SJ (Submit Migration Object Apply Monitor).

Apply Transactions

F1-MGTAP-SJ (Submit Migration Transaction Apply Monitor).

Retry Transactions

F1-MGTPR-SJ (Submit Migration Transaction Monitor).

The following table highlights the batch controls where an algorithm may be plugged in and the name of the algorithm to use.

Batch Control

Algorithm

F1-MGTPR (Migration Transaction Monitor)

F1-MGDIM-NJ (Submit Migration Data Set Import Monitor).

F1-MGTAP (Migration Transaction Monitor - Apply)

F1-MGDIM-NJ (Submit Migration Data Set Import Monitor).

F1-MGOAP (Migration Object Monitor - Apply)

F1-MGDIM-NJ (Submit Migration Data Set Import Monitor).

F1-MGOPR (Migration Object Monitor)

F1-MGTPR-NJ (Submit Migration Transaction Monitor).

- Manual submission. The user managing the CMA import process submits the appropriate batch jobs on demand when a particular step is ready. Navigate to Batch Job Submission, select the appropriate batch control and fill in the parameters as needed.

Note that after successfully applying the migrated data, the L2 cache of all thread pools must be refreshed. For more information, see Caching Considerations.

CAUTION:

Be sure that the Thread Count set when submitting the batch job does not exceed the number supported by the thread pool. Otherwise the extra threads will wait until the supported number of threads are finished, possibly resulting in a large number of errors in the Apply steps.

Refer to the parameter descriptions in the batch control metadata for more information about filling in the parameters.

For additional details on submission controls, refer to the topic Batch Job Submission - Main in the Batch Jobs section.

CMA Reference

This section provides additional reference information.

Next in This Section

- Framework-Provided Migration Configuration

Framework-Provided Migration Configuration

This topic describes special information relating to migration objects provided for use by CMA in the product. Additional objects may be provided by your specific product. Any special information for objects is provided separately in each product's documentation.

The following points highlight some information about Framework-provided migration requests. Navigate to the migration request page in the application to view the details of all provided objects.

- Several base migration requests are supplied to logically group system and administrative tables. For example, there is a migration request for Framework System Configuration F1-SystemConfig where most system configuration objects are included. There is another one provided for CMA related configuration objects.

- There are several different security related migration requests that include different combinations of migration plans to support multiple possible business requirements related to security migration.

- The system supplies a group migration request F1–FrameworkConfig (Framework Configuration), which includes several other migration requests. The expectation is that this migration request includes all the typical objects that are included in a wholesale migration. Your specific product may include this migration request into its own group migration request to support a wholesale migration of all the framework and product administrative tables. An implementation may choose to build a custom group migration request. In this case, review the various migration requests provided by base to see if any may be included as components for the custom migration request. Then any new migration plans added to the base migration request in future releases are automatically included in future migrations.

Note: Refer to your specific product's CMA documentation for its recommendation on which migration requests to use for a full migration of framework and product administrative tables.

The following points highlight some information about the Framework-provided migration plans. Navigate to the migration plan page in the application to view the details of all provided objects.

- Fields and characteristic types are not migrated with an object (like a business object or a data area) unless specifically indicated.

- The Application Service used by an object is migrated only if it is CM-owned.

- The Batch Control object optionally references a User. If this user does not exist on the target system, CMA cannot apply the requested changes. Also note that when running a batch job, snapshot information is captured on the batch control. Updates like this increment the version number. If a batch control record is part of the migration and the comparison step has detected a change to the batch control, the Apply step will error out for this batch control if a batch job is submitted between the compare and apply step.

Note: CMA batch controls that are part of the import step are executing and as such, the system does not include these records in a migration. If your implementation changes default parameters for any of the batch controls, the recommendation is to manually make those changes to the target region.

- The base migration plans for MO and BO include instructions to copy option types that use foreign key references to refer to other objects. Note that the data stored in the options are not validated, so defining these instructions is not required when doing wholesale migrations. However, including subordinate instructions for foreign key references is useful for targeted migrations to ensure that the related data is included in the migration. If you add additional MO or BO option types that use foreign keys and you want to support targeted migrations, you must create custom migration plans and requests for MO and BO, respectively to include these referenced objects in the migration plan. Note that you do not need to duplicate the instructions in the base migration plans. You may define the additional migration plans to only have the additional custom option types. When submitting a migration request for MO or BO you must include both the base migration plans and the custom migration plans in the request.

- For scripts, schema-based objects and zones, the migration plans provided by the product migrate, through constraints, some of the typical associated data with them. However, data specified through alternate formats (such as through Edit Data steps in scripts, referenced in schemas for schema-based objects, or data from mnemonics in zone parameters, etc.) are not identified and combined in the same transaction. The iterative processing functionality of the import step should resolve any timing issues that may result in validation errors for these types of objects.

- There are two migration plans for Scripts. The migration plan F1-ScriptOnly migrates just the script and its Application Service (provided the Application Service is CM-owned). The migration plan F1-Script includes most related objects, but does not migrate any objects referenced in the edit data area steps. It does not move the Function maintenance object. It may be included in any appropriate custom targeted migration request where scripts and related data should be migrated.

- If your implementation includes a Feature Configuration setting for the F1_DBCONINFO entry that will be included in a migration request, be sure that the import user on the target region has the appropriate security rights to this entry (Administrator access mode for the Feature Configuration application service (CILTWSDP).

- The common attachments in the Attachment maintenance object may be considered administrative data to include in a migration. Because this MO has a system generated key, as described in Migration Assumptions, Restrictions and Recommendations, it uses a logical key of the file name and the creation date to determine if the record exists in the target environment. In addition, this MO contains admin data (common attachments) and non-admin data (owned attachments). To try to minimize the possibility of key “collision”, new common attachments receive a generated key that includes a zero in the middle whereas owned attachments receive a generated key that does not have a zero in the middle.

- The Menu maintenance object has a user defined key, however, its menu lines and menu items have system generated keys. To avoid the possibility of overriding a menu line or menu item incorrectly, the menu MO will check the menu line’s menu name in the source and target to be sure they match and will check the menu item’s menu line in the source and target to be sure they match otherwise an error will be issued in the comparison step.

- For the system messages, the product provides three different migration plans.

- Message Category and its Messages (F1-MessageCategory). This migration plan is included in the F1-SystemConfig migration request.

- Message Category (F1-MessageCategoryOnly). This migration plan is provided to support a targeted migration where an implementation has created a custom message category and wants to move it but doesn’t want to move all its messages.

- Message (F1-Message). This migration plan is provided to support a targeted migration where only specific messages within a message category should be migrated.

- For lookup values, the product provides two different migration plans.

- Lookup Field and its Values (F1-Lookup). This migration plan is included in the F1-SystemConfig migration request.

- Lookup Value (F1-LookupValue). This migration plan is provided to support a targeted migration where only specific lookup values within a lookup field should be migrated.

- There are some system data objects where no information in a base delivered record may be modified by an implementation. For these records, the base delivered migration requests include selection criteria to only select CM-owned records (because the base records will always exist in the target region assuming both regions have the same release). An example is Algorithm Type. The F1-SystemConfig migration request only includes CM-owned algorithm types. However, many system data objects support custom changes to one or more fields, for example the Zone object allows an implementation to override the zone text or certain parameters. Other system data objects support custom additions to a collection. For example, the Maintenance Object allows an implementation to add algorithms or options. For the migration plans related to these system data objects, all records are included in the base delivered migration requests to allow for any customized configuration to be migrated. It means that during the Import / Compare step many base delivered objects that are not customized will be marked Unchanged.

- Many of the integration related maintenance objects that include references to environment-specific data, such as Message Senders. This data should be migrated with extreme care. When appropriate, consider taking advantage of URI substitution. Refer to Referencing URIs for more information.

Configuring Facts

Fact is an optional configuration tool for simple workflow-type business messages or tasks. The base package does not provide a dedicated Fact user interface because fact is generic by design. Implementations configure their own user interface to visualize the desired custom business process. The topics in this section describe the generic Fact entity and how it can be customized.

Next in This Section

- Fact Is A Generic Entity

- Fact's Business Object Controls Everything

- Fact Supports A Log

Fact Is A Generic Entity

The Fact maintenance object is a generic entity that can be configured to represent custom entities and support automated workflows for a variety of applications. Each fact references a business object to describe the type of entity it is. A status column on the fact may be used to capture its current state in the processing lifecycle controlled by its business object.

The maintenance object also supports a standard characteristic collection as well as a CLOB element to capture additional information.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference F1_FACT

Fact's Business Object Controls Everything

A fact's business object controls its contents, lifecycle and various other business rules:

- Its schema defines where each piece of information resides on the physical Fact maintenance object.

- If may define a lifecycle for all fact instances of this type to follow. Each fact must exist in a valid state as per its business object's lifecycle definition.

- It may define validation and other business rules to control the behavior of facts of this type.

Fastpath: For more information about business objects, refer to The Big Picture of Business Objects.

Fact Supports A Log

The Fact maintenance object supports a log. Any significant event related to a Fact may be recorded on its log. The system automatically records a log record when the fact is created and when it transitions into a new state. In addition, any custom process or manual user activity can add log entries.

Fastpath:

Refer to State Transitions Are Audited for more information on logging.

Cloud Service Foundation

This chapter provides information on how to administer features associated with Oracle Utilities Cloud Service Foundation functionality.

Note: This chapter does not apply to all implementations. Contact your system administrator to confirm if your implementation includes Oracle Utilities Cloud Service Foundation.

Next in This Section

- Process Automation Tool

- Data Conversion Support for Cloud Implementations

Process Automation Tool

Note: This section does not apply to all implementations.  Contact your system administrator to confirm if your implementation includes Oracle Utilities Cloud Service Foundation and the Process Automation Tool.

The Process Automation Tool allows customers and implementers to orchestrate and automate a set of infrastructure related multi-step processes. The tool provides the ability to monitor the progress of such process and each of the steps. The tool also supports user actions at the process and step level.

The process automation tool is made out of the following system entities:

- Infrastructure Process - a Business Object of the Service Task MO.

- Infrastructure Process Step - a Business Object of the Service Task MO.

- Infrastructure Process Type - a Business Object of the Service Task Type MO.

- Infrastructure Process Step Type - a Business Object of the Service Task Type MO.

An Infrastructure Process references a type that includes the steps that are a part of that process. The steps are executed one by one according to their sequence as long as the previous step ended successfully. When a step in a process fails, the process will stop and wait for a user to take further actions.

An Infrastructure Process can span up to two product environments. This means that it can invoke and monitor steps in two systems. This, for example, allows it to orchestrate a configuration migration (using the Configuration Migration Assistant) from one product environment to another. Such a migration can include steps to create the export data on the source environment, move the export file to the target environment and execute all the import tasks on the target environment, all as a single Infrastructure Process. In this case the Infrastructure Process will be created on the target environment and will pull the configuration from the source environment.

Note:

This is done in order to ensure that only application users with sufficient security privileges in any system environment can create Infrastructure Processes that can update that environment.

The rule is that when an Infrastructure Process is created to run processes on two systems, the process will always be created on the environment with the higher security requirements. For example, if you need to run processes on the Development and Test environments, the infrastructure process will be created and executed from the Test environment (assuming that the Test environment has higher security requirements than the Development environment).

The steps that make an Infrastructure Process reference a step type that governs their behavior. A comprehensive set of process and step types is provided with the product. This set can be extended by implementers as needed.

Next in This Section

- Creating an Infrastructure Process

- Executing an Infrastructure Process

- Monitoring Infrastructure Process Progress

- Process Automation Tool Setup

- Configuring New Infrastructure Processes

- CMA Migration Infrastructure Process Types

- Integration Configuration (SOA) Infrstructure Process Types

Creating an Infrastructure Process

To create a new process, navigate using Admin > Implementation Tools > Infrastructure Process. Use the Infrastructure Process Query to search for an existing process. One an Infrastructure Process is selected, you are brought to the maintenance portal to view and maintain the selected record.

The following points provide information about creating a new Infrastructure Process.

Infrastructure Process references an Infrastructure Process Type. When creating a new process you need to select the type that the process will be based on.

The Name of the process is used for tracking purposes. The name doesn’t have to be unique in the system.

The Process Steps list is read-only and represents the steps that were configured on the Infrastructure Process Type.

Note:

Changing information on the Infrastructure Process Type, including the steps, will not affect existing Infrastructure Process records.

The Process Details section represents additional information that is required according to the corresponding process type definition.

Executing an Infrastructure Process

Infrastructure Process Lifecycle

New processes are created in a Pending status. While in this status the Infrastructure Process record can be modified, deleted or duplicated.

Note: Once an Infrastructure Process record is created, its type cannot be changed. To change the type, you can delete the process that was created with the wrong type (if it is still in Pending status) and create a new process with the correct type.

Use the Start action, on the maintenance portal to begin the process execution. The process status will change to In Progress.

Note: While the Infrastructure Process is in Pending status, the steps will not have a status or any available actions. When the process transitions to In Progress status the process step records are created. From that point on they have a status and actions according to the step that and status.

While the process is In Progress the steps of the process will execute one by one according to their sequence. The process can be stopped using the Stop action. In this case the current step that is in progress will continue but the next step will not be executed. If any of the steps fail, the process will also transition into Stopped status and will not execute the next step.

When the process is in Stopped status it can be resumed by selecting the Resume action, or it can be cancelled by selecting the Cancel action.

Infrastructure Process Step Lifecycle

A process steps is created in Pending status and is transitioned to In Progress by the process logic when its turn to execute arrives.

When a step is In Progress, the following transitions are possible:

- Transition the step into Completed status upon successful completion of the step’s work or by selecting the Complete action.

- Transition the step into Failed status when an error was detected during the step’s work or by selecting the Fail action.

- Steps may include logic that will transition the step into Skipped status if that logic determines that the step should not be executed.

When the step is In Progress, selecting the Job Status action will display information about the job running status (if it is a batch job type of step).

Note: Manually changing the step status to Completed or Failed while the step is In Progress should be carefully considered. This should only be done when step stays In Progress status for a long time and upon investigation it is clear that some manual intervention is required.

When a step is in Failed status it is still possible to manually transition the step into Completed status.

Note: Transitioning the step from Failed to Completed status should only be done if it is clear that the step was able to successfully accomplish its task. This will likely be established after some investigation.

Monitoring Infrastructure Process Progress

Next in This Section

- Infrastructure Process Control

- Monitoring a Running Infrastructure Process

- Dealing with Exceptions

Infrastructure Process Control

The Infrastructure Process Control portal provides an overview of Infrastructure Processes that are active (i.e. in Pending or In Progress status) or processes that did not complete (i.e. in Stopped status) within the last X days.

Navigate to Infrastructure Process Control portal, using Admin > Implementation Tools > Infrastructure Process Control.

Available actions on this portal are:

- New Process - creates a new Infrastructure Process

- Environment Setup - directs the user to the master configuration related to the process automation tool

Select any of the processes from the portal lists for more information.

Monitoring a Running Infrastructure Process

When a process is running (in In Progress status), you can monitor its progress by refreshing the page. To configure automatic page refresh, refer to the User Portal Preferences for this portal.

The Infrastructure Process maintenance portal provides information about the status of the overall process as well as each of the steps.

You can also view the details of each individual step including their log for more information or to investigate exceptions.

Dealing with Exceptions

Infrastructure Process steps can be divided into two main categories:

- Steps that start a batch process (job)

- Steps that are not batch process related

In addition, steps can be local or remote. Local steps execute on the same product environment that the process is executing while remote steps are executed on a different product environment.

Next in This Section

- Batch Job Step Exceptions

- Non-Batch Step Exceptions

Batch Job Step Exceptions

Batch job steps start a batch job either locally or on a different product environment.

Batch job step in Failed status as a result of a batch job error

When a batch process (local or remote) ends with an error, the process step is automatically transitioned to Failed status.

In this case, you should:

1. Ascertain the cause of the job failure (in the local or remote environment).

2. If the issue is temporary or can be fixed, fix it and then rerun the batch job manually using the Batch Job Submission page (in the local or remote environment). If the resubmitted job ended successfully, you can transition the process step to the Completed status and use the Resume action at the process level to continue the process execution.

If the issue cannot be resolved, further investigation is required. In this case the process should remain in Stopped status.

Batch job step in In Progress status while batch job ended with an error

When an Infrastructure Process Step that is associated with a batch job stays in In Progress status while the batch job ended with an error, further investigation is required. One possible cause for that situation could be an error that causes the job to fail and at the same time also prevents the job from communicating its status back to the originating process step.

In this case you should manually transition the step into Failed status and continue your investigation.

Note: If you decide to stop the Infrastructure Process altogether (as a result of the exception), it is a good idea to mark the batch job that failed as “Do Not Attempt Restart” in the Batch Run Control for that batch run. This will ensure that the next time the Infrastructure Processes runs, when it gets to that batch process step it will not attempt to resume the execution that ended with an exception, possibly causing a repeat of the exception.

Batch job step in In Progress status while batch job ended successfully

When an Infrastructure Process Step that is associated with a batch job stays in In Progress status while the batch job ended successfully, further investigation is required. In this case, once you ascertained that the job did actually end successfully, you can manually transition the process step into Completed status and use the Resume action at the process level to continue its execution.

Non-Batch Step Exceptions

Infrastructure Process Steps that are not associated with batch jobs can experience errors as well and therefore can fail. As a reminder, the logic for these steps can experience local or remote errors. When such a step fails, information about the failure can be found in the process step log.

Process Automation Tool Setup

The process automation tool requires the setup of the following components:

- Master Configuration

- External Systems

- Message Senders

In addition, a security setup is required.

The setup itself is done automatically as part of the environment provisioning process. The information in this section is provided for reference and in case changes in existing setup are required.

Next in This Section

- Security Setup

- Master Configuration Setup

- External Systems and Message Senders

Security Setup

Before the process automation tool can be used, the security credentials of the Message Senders, used by the process automation tool, must be updated.

In order to execute the security setup, navigate using Admin > Implementation Tools > Process Automation Security Setup.

The setup script will ask you to provide a User ID, a Password and to indicate whether or not to override the existing security setup.

Please contact your system or security administrator for more information about what User ID should be used for this setup.

You should select to override existing security setup when you need to update the User ID or the Password on the existing Messages Senders, used by the process automation tool. A common use case will be mandatory periodic password rotation for the user account that was selected for the setup.

Note: At the end of the process, you will be asked to flush all the system cache. This is required in order for the information update to take effect.

Master Configuration Setup

The process automation tool relies on master configuration settings in order to identify all the product environments that are available to it. The Master Configuration is automatically setup as part of the system provisioning process.

This section describes the setup options in case manual changes are needed.

To access the configuration for the process automation tool, navigate using Admin > General > Master Configuration and look for Process Automation Configuration.

The Main section includes the definition of the Current Environment code and the default file extension for CMA export files.

The Current Environment code is a unique code that is given to each product environment.

The Environment List section describes all the existing product environments and integration (SOA) environment that the process automation tool need to interact with, for example, in order to run a process that moves integration configuration from one environment to another.

The environment in the list includes the following details:

- Environment: the environment code.

- Product: defined in the Process Automation Product extendable lookup.

- Domain: defined in the Process Automation Domain extendable lookup.

- Migration Source: select “Yes” if you can migrate configuration data from this environment.

Note: You should not allow automated migration of configuration from your development environment directly to your production environment but you would allow migrating from the development to test environments.

- External System: reference to the External System definition that will support communication with the row’s environment.

- SFTP Alias: this is a name of the SSH file that will be used to support file transfer capabilities between system environment directories.

External Systems and Message Senders

The process automation tool communicates with other product environments (including SOA environments) through Outbound Messages.

The automated setup for the process automation tool creates a set of Message Senders and External Systems to support communication with other product environments.

Each product environment which is defined on the Process Automation Configuration has a corresponding unique External System. Each External System contains the details of all the message types that it supports, the message sender for each message type and additional data if required (for example, message or response XSLs).

Configuring New Infrastructure Processes

The process automation tool configuration is essentially a collection of process types and step types that support the automation of various multi-step processes. A set of Infrastructure Process Types and Infrastructure Process Step Types is provided with the base product. Customers and implementers can create new process and step types.

This section describes the actions required to configure new Infrastructure Process Type and Infrastructure Process Step Type.

Next in This Section

- Configuring a New Infrastructure Process Step Type

- Configuring a New Infrastructure Process Type

Configuring a New Infrastructure Process Step Type

In order to configure a new step type, navigate using Admin > Implementation Tools > Infrastructure Process Step Type. Use the Infrastructure Process Step Type Query to view existing step types.

CAUTION:

Base product step type names start with “K1” and should not be change. Changing these step types can break the process and step types that are provided with the product.

The following points provide information about creating a new Infrastructure Process Step Type.

When creating a new step type, a business object has to be selected first. The Infrastructure Process Step Type BO contains the information necessary for the Infrastructure Process Step that references that step type. For example, a batch process step type BO contains information related to the batch code that should be submitted and the parameters that will be passed to it. You can use existing Infrastructure Process Step Type BOs or create new BOs according to your business requirements.

The Related Transaction BO references the Infrastructure Process Step BO. The step BO contains the business logic associated with the step. For example, a batch process step BO is responsible to submit a batch job with to the information from the step type. You can use existing Infrastructure Process Step BOs or create new BOs according to your business requirements.

The Process Step Type Details section represents additional information that is required for this specific step type BO.

Configuring a New Infrastructure Process Type

In order to configure a new process type, navigate using Admin > Implementation Tools > Infrastructure Process Type. Use the Infrastructure Process Step all-in-one portal to view existing process types.

CAUTION:

Base product process type names start with “K1” and should not be change. Changing these process types can break the base product process types that are provided with the product.

The following points provide information about creating a new Infrastructure Process Type.

When creating a new process type, a business object has to be selected first. The Infrastructure Process Type BO contains information necessary for the Infrastructure Process that references that process type. You can use existing Infrastructure Process Type BOs or create new BOs according to your business requirements.

The Related Transaction BO references the Infrastructure Process BO. The process BO contains the business logic associated with the process. This includes the orchestration of the process steps. The process BO also contains information that is shared by step business logic during the process. For example, a process BO that handles migration of data between product environments can have a buffer that will hold the information pulled from the source environment using one step so that another step can use it to push that to the target environment. You can use existing Infrastructure Process BOs or create new BOs according to your business requirements.

The Process Type Steps section includes a collection of step types. The sequence of steps has to be unique and this will be sequence of execution.

CAUTION:

When selecting step types for a process type you need to consider the fact that not all step types can be used on all process types. For example, some steps need to get or save information in the process itself so it can be used by other steps of that process. These types of steps can only work with a certain type of process. Please refer to the detailed description in each of the base product provided Infrastructure Process Step Types to see what process types they can be referenced on.

The Infrastructure Process Type Details section represents additional information that is required for the specific process type BO.

CMA Migration Infrastructure Process Types

The following Infrastructure Process Types are provided to support the following configuration migration use cases:

- CMA Accelerator Load - import an exported file created by the Configuration Migration Assistant export process.

- CMA Migration - a wholesale or piecemeal configuration migration (using the Configuration Migration Assistant), exporting configuration from a source environment and importing it to a target environment.

Next in This Section

- CMA Accelerator Load (K1-CMA-LOAD)

- CMA Migration (K1-CMA-MIGRATE)

CMA Accelerator Load (K1-CMA-LOAD)

The K1-CMA-LOAD Infrastructure Process Type supports importing of an exported CMA file.

K1-CMA-LOAD is based on K1-CMAMigrationProcessType Infrastructure Process Type BO and uses the K1-CMAMigration as the Infrastructure Process BO.

The CMA Accelerator Load process type includes all the necessary steps to download an exported CMA file (that was uploaded to the system via FTP) into the environment that the process is running on (via FTP) and to run all the batch processes that are a part of the CMA import.

Note: This process type does not include a step for a manual user review. It is assumed that when loading an accelerator, there shouldn’t be anything to review and the new configuration content is expected to be new for the most part or OK to override existing configuration.

Using the CMA Accelerator Load Infrastructure Process Type

In order to import a CMA export file (e.g. an accelerator), you need to:

- Upload the file to the system via FTP.

- Create a new infrastructure process with the K1-CMA-LOAD Infrastructure Process Type and provide the following additional details:

- Name.

- The Process Steps list is for reference only.

- Export filename: specify the CMA export file name that was uploaded to the system. You should specify the full name including the file extension name.

- User Review Needed: select “Yes” only if you are expecting the CMA file to include data that already exists in the system and need to be reviewed before changes are applied.

- Default Status For Add, Default Status For Update are relevant in case you selected to have a user review. In this case define the default status of migration data items when imported into the target environment.

- Once the process is saved, you can start it by selecting the Start action.

CMA Migration (K1-CMA-MIGRATE)

The K1-CMA-MIGRATE Infrastructure Process Type supports a full or partial migration of configuration data, from a remote environment (the source) to the environment that the process is running on (the target).

Note: The configuration migration process is done as a PULL (running on the target environment and pulling data from the source environment) to make sure that users without security privileges to make changes in a product environment “A” won’t be able to run a process from a remote environment “B” that will force changes into “A”.

K1-CMA-MIGRATE is based on K1-CMAMigrationProcessType Infrastructure Process Type BO and uses the K1-CMAMigration as the Infrastructure Process BO.

This configuration migration process type includes all the necessary steps to create an export CMA file from a migration request on the source environment, move the file into the target environment (via FTP) and to run all the import batch processes on the target environment to process the file. This process type also includes a step for a manual user review of the imported data if needed.

Using the CMA Migration Infrastructure Process Type

In order to migrate configuration data from a remote environment (the source environment) to the current environment (the target environment) you need to:

- Create a new infrastructure process with the K1-CMA-MIGRATE Infrastructure Process Type and provide the following additional details:

- Name.

- From Environment: select the source environment from which the data will be migrated to the target environment (the current environment). The list of valid environments to choose from is taken from the Process Automation Master Configuration. The target environment is always the current environment - the one that this process is created on.

- The Process Steps list is for reference only.

- Migration Request: specify the CMA Migration Request ID that will be used for the migration process. The migration request should exists on the source environment and will be validated against that environment.

- Export filename: specify the CMA export file name that will be used for the export and import process. You should specify the full name including the file extension name. If you leave this field empty, the system will default the file name according to the migration request ID and the default file extension name.

- User Review Needed: select “Yes” only if you are expecting the CMA file to include data that already exists in the system and need to be reviewed before changes are applied.

- Default Status For Add, Default Status For Update are relevant in case you selected to have a user review. In this case define the default status of migration data items when imported into the target environment.

- Once the process is saved, you can start it by selecting the Start action.

Integration Configuration (SOA) Infrstructure Process Types

The K1-INTEG-CONFIG-MIGR Infrastructure Process Type supports the migration of integration configuration data from a source to a target environment for the following configuration types:

- DVM data

- Integration Configuration Properties

The migration is done by using REST APIs that are provided by the integration infrastructure to get and post data. Migration of integration configuration will include a step to get the data from the source environment and then post it to the target environment.

Next in This Section

- Integration Configuration Migration (K1-INTEG-CONFIG-MIGR)

Integration Configuration Migration (K1-INTEG-CONFIG-MIGR)

K1-INTEG-CONFIG-MIGR is based on K1-IntegConfigMigProcessType Infrastructure Process Type BO and uses the K1-IntegrationConfigMigration as the Infrastructure Process BO.

This migration process type includes all the steps to migrate DVM and Integration Configuration Properties.

Using the Integration Configuration Migration Infrastructure Process Type

In order to migrate integration configuration data from a remote environment (the source) to the current environment (the target) you need to:

- Create a new infrastructure process with the K1-INTEG-CONFIG-MIGR Infrastructure Process Type and provide the following additional details:

- Name.

- Product: select the integration product whose configuration you wish to migrate.

- From Environment: select the source environment to migrate the configuration from. The environment should be one of environments of the product that was selected. The list of valid environments to choose from is taken from the Process Automation Master Configuration according to the product that was selected.

- The target environment is set to the current domain of the product that was selected. For example, if you are creating a process in the Test environment and you select an integration product “A”, then the target environment will be the “A”-Test environment.

- Migrate DVM: select Yes to migrate DVM data. Selecting No will cause the process to skip this step.

- Migrate Configuration File: select Yes to migrate the integration configuration properties file. Selecting No will cause the process to skip this step.

- Once the process is saved, you can start it by selecting the Start action.

Data Conversion Support for Cloud Implementations

This chapter provides information and requirements on data conversion in support of Oracle Utilities Cloud implementations.

Note: This section does not apply to all implementations. Contact your system administrator to confirm if your implementation includes Oracle Utilities Cloud Service Foundation and Data Conversion Support for cloud implementations.

Next in This Section

- Data Conversion Overview

- Configuring Conversion

- Input Data Files

- Conversion Orchestration

- Security Setup for Conversion

- Conversion Reconciliation Reports

Data Conversion Overview

The ability to covert customer data from legacy systems to OUAF based products is critical for every implementation. The following chapter describes the overall process, tools and considerations for customer data conversion to SaaS OUAF based product on Oracle Cloud.

Next in This Section

- Conversion Steps

- SQL Loader

- Conversion Artifacts

Conversion Steps

In general data conversion effort in the cloud is divided into the following steps:

- Prepare for conversion

- Create conversion data files

- Upload conversion data files to the cloud

- Process conversion data files

- Process converted data in cloud application

- Approve converted data for production mode

Note:

It is important to note that the conversion process is a highly iterative process. All the steps above are likely to be done (completely or partially) multiple times during the conversion process.

For example, customer typically start with a small set of data to convert, they fix issues discovered with that data and then re-create new data files and proceed to convert them. This can happen many times, each time with either a different data sample or bigger and bigger data conversion sets until all the required data has gone through the conversion process.

Next in This Section

- Prepare for Conversion

- Create Conversion Data Files

- Upload Data Conversion Files to the Cloud

- Process Conversion Data Files

- Process Converted Data in Cloud Application

- Approve Converted Data for Production Mode

Prepare for Conversion

Preparing for conversion will typically include the following actions:

- Identify the OUAF product entities (Maintenance Objects) for which data will be converted. Refer the specific OUAF product documentation for information about converted entities for that product. Each of the product converted entities will have a set of conversion staging tables that will receive the data from your legacy system before they get processed into the system.

- Identify tables and maintenance objects whose data requires special treatment. That may include high volume tables, extremely large CLOB data, tables with multiple CLOB fields or any other special considerations related to the legacy data being converted.

Address the special circumstances by customizing the default configurations:

- Enable conversion for tables that are not marked for conversion in the metadata use the Master Configuration

- If your table(s) contain multiple CLOBs, but you don’t plan to supply the legacy data for all of them, create Conversion Task Type for this table(s) and populate Exclude CLOB Field list and then add a corresponding entry to Master Configuration’s Special Instructions

- If you dealing with high volumes of data, you may want to adjust the load parameters and options for the SQL Loader.. In this case, create a custom Control File Header (Managed Content), configure a dedicated Conversion Task Type referencing this custom Control File Header and then add a corresponding entry to Master Configuration’s Special Instructions. Note that creating the custom Control File Header will result in a control file composed from the custom fragment and the generated fields list.

- If the generated field definitions list in the control file doesn’t satisfy your requirements, you may completely override the control file. In this case, create a custom Control File (Managed Content, same as above), configure a dedicated Conversion Task Type referencing this custom Override Control File and then add a corresponding entry to Master Configuration’s Special Instructions. Make sure your custom Control File contains all the run-time substitution variables that appear in the base Control File Header.

See Conversion Task Types and Conversion Master Configuration chapters for more details.

- Generate the conversion artifacts for the product entities you plan to convert data for. This will include, for example, a set of data specification files that describe the format of data required for each file.

- Run the batch job to copy the generated conversion artifacts to sFTP server. Download and examine the input data specifications and determine the expected data formats and input file names.

- Identify your various sources of data and extraction methods.

Create Conversion Data Files

In this step you create the set of data conversion files that were identified for the conversion process. You can choose to generate data files for each staging table or create a smaller set for each converted Maintenance Object.

The data conversion files typically do not include all the data to begin with but start small and grow with every iteration of the conversion process until they reach their maximum size at the end.

Note: When performing data conversion in the cloud, customers don’t have access to the database staging tables. Data scrubbing and transformation activities has to take place before the data files are generated (in each conversion iteration) so the result of these activities is reflected on the data files that are moved to the cloud to be loaded into the staging tables.

Upload Data Conversion Files to the Cloud

Since data conversion files are created locally they have to be uploaded to the cloud environment in order to be processed and loaded into the conversion staging tables.

In this step you can use any sFTP client with the account credentials that were provided at provisioning time to upload all the files via FTP to the cloud environment.

For more details refer to Input Data Files .

Process Conversion Data Files

After uploading the files to the cloud, you should run a set of batch processes that will process the data files using Oracle SQL Loader and insert the data to the product conversion staging tables.

The staging table load process also produces output files that provide feedback on the load process.

You can download these output files for review using the same sFTP client you used to upload the data file.

Note: The process that imports the data in the files to the staging tables, using Oracle SQL Loader, is using the artifacts that were generated in the “Prepare for Conversion” step.

For more details refer to Understanding Load Data Process .

Process Converted Data in Cloud Application

When the data intended for conversion (for a conversion iteration) is loaded into the appropriate conversion staging tables, the OUAF application in the cloud can process that data according to the product’s data model, technical and business rules.

Refer to the OUAF product specific documentation for further guidelines and information on the specific processes and guidelines related to data conversion.

Note:

This is one step of the overall iterative process but it is also includes many internal steps, for example:

1. Validation of the data in the conversion staging tables.

2. Generation of the system assigned keys for the converted entities.

3. Migration of the converted data from the staging tables into the actual system tables.

When the processing of the converted data in this iteration is completed, information from the system is used to identity changes necessary to source data, the extraction process or other activities involved in producing the data to be converted.

The process can then start over by loading a new set of data into data conversion files, load them to the staging tables in the cloud and process them once more to get more feedback.

Approve Converted Data for Production Mode

When the quality and scope of data converted has reached its target, the process can stop. Once the overall data has been approved for production mode the conversion process comes to an end. The process of approving the data includes many activities, for example:

- Running various reports to compare converted data with legacy data to verify the quantity and quality of the data.

- Running reports and tests in the new application to verify the data and the system’s behavior using that data.

- Manual review of random and key data in the system.

SQL Loader

Loading the data in the data conversion files into the product conversion stating tables is done using Oracle SQL Loader.

Oracle SQL Loader is an Oracle Database Tool that enables mass upload of data from various sources into database tables in a fast and safe way.

SQL Loader processing is determined by Control Files. The control files for the data conversion process are provided for each of the product conversion staging tables as part of the artifact generation which is a part of the preparations activities before starting the conversion process.

The Control Files typically define:

- The location of input files to load.

- The character set of the input data.

- The target table(s) for the load and how to insert the data (e.g. append to or override).

- How to map the data in the input file to tables and fields.

- The location of the output files (e.g. log, bad or rejected records).

- Options for parallel processing and load balancing.

The control files that are generated for the product include all the parameters necessary to load the product conversion staging tables. There are some customization options for these files that are discussed later.

After loading the control files, SQL Loader reads the records in the input data file(s), converts the input into database tables and columns that are inserted into the database.

SQL Loader has 2 modes of operation:

- Conventional Path Load – data is inserted to the database by using database SQL INSERT statements.

- Direct Path Load – data is inserted into the database using data blocks that are written directly to the database. This method is much faster and therefore is the method selected for the data conversion process.

SQL Loader has the ability to deal with multiple data files mapped to multiple tables as well as loading data into CLOB fields.

Next in This Section

- Using SQL Loader When Processing Conversion Data Files

Using SQL Loader When Processing Conversion Data Files

Processing of uploaded conversion data files is done via a Batch Process (for each staging table or MO) that does the following:

- Prepare parameters for invoking SQL Loader.

- Invoke SQL Loader for loading one staging table or one MO, using the data files that was uploaded to the cloud (using sFTP). The data file is processed directly from the sFTP server and is NOT copied to a local directory on the server.

- Archive the input file(s) and upload the results output files to the sFTP server so they can be subsequently downloaded by the customer for review.

Conversion Artifacts

The base product includes a set of artifacts that support the conversion process. These artifacts are provided on demand (generated as a result of a user request in the system).

The available artifacts are:

- Input Data Specifications

- SQL Loader Control Files

Next in This Section

- Conversion Input Data Specifications

- SQL Loader Control Files

Conversion Input Data Specifications

The system will generate a text file with data specification instructions for each of the conversion tables that are supported by the base product.

The specification files are for reference ONLY and are not used by the system at run time. These files describe the data format for each table so that the data specified can be loaded correctly with the Control File that is also generated by the system.

For more details refer to Conversion Artifact Generator .

SQL Loader Control Files

The control files are for internal use and are generated for each of the conversion tables that are supported by the product. These files are used by SQL Loader to interpret and load the data that is provided in the conversion data files.

The control file contains:

- General load parameters and options

- Data field specifications and table-specific load instructions

For more details refer to Conversion Artifact Generator .

Configuring Conversion

The following sections describe the settings and configurations used by various conversion processes.

Next in This Section

- Conversion Master Configuration

- Conversion Task Types

- Conversion Artifact Generator

- Conversion Tasks

- Conversion Batch Controls

Conversion Master Configuration

The Conversion Data Upload Master Configuration controls generic aspects of legacy data load process.

Main section captures the definitions globally applicable for all converted objects (tables and/or maintenance objects):

- Default Conversion Instructions for Artifact Generator reference conversion task types that define load parameters for individual tables or maintenance objects.
The Master Configuration captures conversion task types with default configurations for both table and maintenance object-level loads.

- Conversion Artifacts options. You can indicate that the snapshot of the generated file(s) should be Stored as an Attachment. If the indicator is set to Y , the Business Object to use for the Attachment has to be specified, otherwise, it is not required.

Special Instructions section captures the definitions that support various idiosyncratic data upload scenarios

- Override Instructions for Tables and Maintenance Objects define Conversion Instructions (conversion task types) for objects that require special processing or data formatting

- Override Conversion Eligibility list allows you to specify tables that are not marked for conversion in metadata, but your implementation wishes to include in the conversion scope. NOTE: if the table you wish to convert has a related key table, this key table has to be explicitly added to this list.

Conversion Task Types

To configure a new conversion task type, navigate using Admin –> Conversion Support –> Conversion Task Type.

The definitions on the conversion task type control the data load parameters for the target table or maintenance object. Conversion Task Type also defines the transactional business object for Conversion Task. The algorithms linked to the transactional business object are responsible for the generation of the Conversion Artifacts: control files and input data specifications.

Conversion Task Types defines:

General Input Data Instructions (all Conversion Task Types Business Objects)

- Strings to use as data delimiters and enclosing characters. These attributes are referencing the Extendable Lookup values for K1–ConvFileDelimiterLookup and K1–ConvFileEnclosingCharLookup

- Date and DateTime fields’ formats. These attributes are referencing the Extendable Lookup values for K1–ConvLoadDateFormatLookup and K1–ConvLoadDateTimeFmtLookup

- CLOB data extract rule indicates whether the CLOB data is supplied as part of the input data file or as a separate, secondary file

- Control File Header - a fragment of the control file that contains general load parameters. This fragment is included in the generated control file. This is a Foreign Key reference to the Managed Content entry.

- Override Control File - a full text of the control file that contains both load parameters and field definitions. The entire text is copied into generated control file ‘as is’. This is a Foreign Key reference to the Managed Content entry.

CLOB Field Instructions for Tables/MO-s that contain multiple CLOB fields (Business Objects K1-ConvArtMultClobMOTaskType and K1-ConvArtMultClobTblTaskType)

- Target Object — Table or Maintenance Object

- Exclude CLOB Fields list — the list of CLOB fields that are not expected to be provided with the legacy data extract and therefore should be excluded from the generated control file.

The following Conversion Task Types are pre-configured in the product:

- K1-CNV-TABLE - meant to be used for a single table load. It is referencing a Transactional Conversion Task Business Object whose algorithms generate Table Conversion Artifacts

- K1-CNV-MO - meant to be used for a single maintenance object load. It is referencing a Transactional Conversion Task Business Object whose algorithms generate Maintenance Object Conversion Artifacts

- K1-CNV-KEY-TABLE – meant to be used for the Key Tables. Key Tables are index-organized tables (IOT) and as such cannot be loaded in multiple concurrent sessions of SQL loader. This Task Type is referencing a Control File Header (Managed Content) where Parallel Load parameter is set to false

Conversion Artifact Generator

Conversion Artifacts is a set of supporting files used for data upload with SQL Loader. The artifacts are generated based on the table and maintenance object metadata and the definitions from Conversion Master Configuration and Configuration Task Types. Conversion artifacts include SQL Loader control files and input data file specifications.

Input data file specifications provide detailed field-by-field description of the expected data type and format, field order and other instructions. Your implementation may use these specifications to create the legacy data extract.

The generator reads Conversion Master Configuration in order to determine the conversion task type associated with the table or maintenance object.

You can choose to generate artifacts for table-level and/or maintenance object-level load, orfor the entire system or for specific Table or Maintenance Object:

- Navigate to Admin —> Conversion Support —> Generate Conversion Artifacts.

- Select one of the options:

- Generate All – performs a complete refresh of the conversion artifacts. It deletes existing and creates new Conversion Tasks for every table that is marked for conversion in the metadata. It also creates Conversion Task for every Maintenance Object that includes tables marked for conversion.

- Include All Tables – recreates artifacts for all Tables that are marked for conversion in the metadata

- Table search allows you to select specific target table

- Include All maintenance Objects – recreates artifacts for all Maintenance Objects whose tables are marked for conversion in the metadata

- Maintenance Object search allows you to select specific target Maintenance Object.

Note: The process overrides all previously generated artifacts and replaces existing files.

The generator creates Conversion Tasks, one instance per table and/or per maintenance object and creates attachment that stores the input data file specifications file. The attachment is linked to the Conversion Task as a Related Object.

The regeneration is necessary each time the metadata or conversion configurations are amended.

Conversion Tasks query is provided with the base product.

Accessing the Artifacts

In order to make the generated input data file specifications available for download, submit the batch process K1-CNVUS.

After successful batch completion, locate the files under corresponding folder. Refer to Input and Output File Location for more details. You can also view the individual specifications by searching for a Conversion Task and exploring the linked attachment.

Note:

- The specification file name for the table is composed as <table name>_spec .txt

- The specification file name for the maintenance object is composed as <maintenance object code>_spec.txt

Conversion Tasks

The following sections provide information about Conversion Tasks and generated conversion artifacts.

Next in This Section

- Conversion Task Query

- Conversion Task

Conversion Task Query

Conversion Task query allows to search by variety of criteria:

- Creating User, Conversion Task Type and Status

- Linked Object – Table or Maintenance Object

- Exact Conversion Task ID

Conversion Task

The purpose of the Conversion Task is to maintain the conversion artifacts for Table or Maintenance Object. Please consider the following with respect to conversion tasks.

- The business object lifecycle supports multiple attempts to re-generate the artifacts.

- The re-generation could be triggered either manually or by the Conversion Artifact Generator. Only one set of the artifacts is relevant at any point of time, hence only one Conversion Task at the time can exists for a given Table or Maintenance Object.

- Typically, Conversion Tasks are created by Conversion Artifact Generator. However, it can also be created manually by navigating to Admin —> Conversion Support —> Conversion Task.

- Use the Conversion Task Query to search for an existing entry. Select the entry from the search results to navigate to the maintenance portal to view and maintain the selected record.

- Conversion Task references a Conversion Task Type and contains standard business object record information, including the creation date/time, status update date/time and creating user.

- The task references the object – Table or Maintenance Object – for which the artifacts are generated.

- The collection of task’s Related Objects store references to the Attachments that store a snapshot of the generated files. A new attachment is created after each generation run and linked to the Conversion Task for audit purposes.

Conversion Batch Controls

The following batch controls are delivered with base product:

Note:

Batch processes that interact with sFTP server include Source Host Alias parameter (required). This parameter should be populated with SSH configuration file name of the sFTP account.

The value will be different for each of the OUAF-based products; the file is generated upon service subscription. Contact your security administrator to obtain the file name.

Batch Control

Description

K1-CNVLD

Conversion - Load Data using SQL Loader.

This process facilitates the legacy data extract upload using SQL Loader. The input data files are expected to be compressed using gzip and uploaded to the sFTP site.

One run uploads the data into a target Table or Maintenance Object.

The process is multi-threaded.

K1-CNVDS

Conversion - Disable Conversion

This process resets the environment indicators and prevents further conversion activities. Once conversion is disabled, the following actions are blocked:

- Switching between Conversion and Production

- Table truncation

- Disable Indexes and Rebuilding the Statistics

- Data insertion into Production

- Data upload into staging

K1-CNVEN

Conversion - Enable Conversion

This process resets the environment indicators and enables it for conversion activities. It should be executed at the start of the Conversion project.

K1-CNVUS

Conversion - Upload Specification Files

This process is copying the input data specification files into sFTP location and makes them available for the download

K1-DRPIN

Conversion - Disable Indexes on Production Tables

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the process disables indexes on all converted tables in Production schema

K1-SDSIN

Conversion - Disable Indexes on Staging Tables

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the process disables indexes on all converted tables in Staging schema

K1-RIUSP

Conversion - Rebuild Indexes and Update Statistics in Production

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the process rebuilds indexes and updates statistics on all converted tables in Production schema

K1-RIUSS

Conversion - Rebuild Indexes and Update Statistics in Staging

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the process rebuilds indexes and updates statistics on all converted tables in Staging schema

K1-CLNTB

Conversion - Truncate Tables in Production

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the truncates all converted tables in Production schema

K1-SCLTB

Conversion - Truncate Tables in Staging

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the truncates all converted tables in Staging schema

K1-CLNKY

Conversion - Truncate Key Reference Tables

This process can be used in two modes:

- Populate Table or Maintenance Object batch parameter to process specific object

- If no specific target is populated, the truncates all Key Reference tables in Staging schema

Next in This Section

- Configuring Data Load Batch Controls for Conversion Project

Configuring Data Load Batch Controls for Conversion Project

The generic batch process K1-CNVLD performs the load of the input data file(s) into a target table or maintenance object, specified as one of the batch parameters.

Consider creating individual batch controls per object (table or maintenance object).

It allows leverage the parallel processing capacity of the system; the data load processes for all objects can be submitted near-simultaneously, thus minimizing the time needed for the legacy data upload, which is only an initial step in the overall data conversion process.

Use batch control K1-CNVLD for rehearsal load batch run for various tables and/or maintenance objects and determine the optimal load strategy:

- Whether the data should be extracted and loaded as single Tables and/or Maintenance Objects

- Whether and how to split the data files and the number of threads for the batch

- Potential log file size and the feasible logging level

Configure data load Batch Controls for each individual Table or Maintenance Object. Pattern the configuration after K1-CNVLD and set the default parameter values for:

- Target Table or Maintenance Object

- File Extension

- Log Level

- Retain Input Option

- Max Number of Upload Error

Default Thread Count depends on the type of the uploaded table. Regular tables can be uploaded in a single or multiple threads. Key tables must be uploaded in a single thread

Source Host Alias parameter value is environment-specific. The default value cannot be pre-configured, but would be the same for all batch jobs submitted in a specific environment. Obtain the value for the parameter by navigating to Implementation Tool —> Process Automation Configuration, locate the entry corresponding to the current environment in the Environment list and find the sFTP Alias.

Input Data Files

This section provides information on inputting data files for data conversion.

Next in This Section

- Overview

- Input Data for a Staging Table

- Input Data for Maintenance Object

- Limitations for Input Data

Overview

This section provides information on the requirements and details for file upload, loading table, maintenance object, CLOB, layout, data formatting, and so on related to inputting data files for data conversion.

Next in This Section

- File Creation and Upload

- Loading Table or Maintenance Object

- Multiple Data Files

- Loading CLOB Data

- File Layout and Data Formatting

- Defining Custom Data Delimiters and Enclosing Characters

File Creation and Upload

The extract data is expected to be uploaded in compressed form. Use gzip to create compressed input data files.

File Creation

Use your sFTP account to retrieve input data specifications from conversion/reference directory. Create the data extract text file, using field delimiters, enclosing characters and data formatting according to the specifications.

If the files were created under Windows operating system, it is recommended to remove the carriage return character prior to compression (not applicable for secondary files with CLOB data).

File Compression with gzip

Use gzip utility to compress the file.

- For Windows operating system, download and install gzip utility for Windows. Run the following:

# Navigate to the gzip folder

cd C:\gzip-1.3.12-1-bin\bin

# Run gzip.

# New file will be created in the same directory as the original the input file

gzip -k <full path to the input data file>

# Sample command for the file TABLE_NAME.txt located under

# C/myDataDirectory/:

gzip –k C/myDataDirectory/TABLE_NAME.txt

- For Unix/Linux operating systems, run the following command:

gzip < <inputFile name> > <outputFile name with .gz suffix>

# Sample command for the file TABLE_NAME.txt

gzip < TABLE_NAME.txt > TABLE_NAME.txt.gz

Loading Table or Maintenance Object

The conversion data upload supports two types of the extract:

- Data extract that contains the data for a single target staging table.

In this case, the upload process inserts records into a single staging table. The input data file consists of similar records, each represents a row in the target table.

- Data extract that contains the data for the group of target staging tables that represent a Maintenance Object.

In this case, the upload process populates all the tables that belong to a maintenance object. The input data file contains multiple types of records that are inserted into various tables. Each record is prefixed with the table name that is used as record type indicator.

Multiple Data Files

The large volume of the converted data may require the extract to be split into multiple parts.

In this case the multi-part extract for a target staging Table or Maintenance Object is loaded with a multi-threaded batch run.

Sample scenario:

10M of the Person records are being converted. The extract file is split into 10 files, PERSON1, PERSON2 PERSON3 etc., each file contains 1M records. All 10 files are uploaded to sFTP.

Batch process ‘Load Person data’ is submitted with 5 threads; each thread picks up 2 files and uploads the data into staging tables.

Loading CLOB Data

The CLOB data can be loaded in two ways:

- Extracted as part of the main data file. This method is suitable for the relatively small CLOB data size. Refer to Limitations for more details.

- Extracted into a separate file. This method is suitable for larger CLOB data sizes and also for large volume tables or maintenance objects. In this scenario, the secondary file has to be uploaded at the same time as the primary data file.

Next in This Section

- Notes on Secondary Data Files (CLOB Data)

Notes on Secondary Data Files (CLOB Data)

Secondary data file is loaded simultaneously with the primary data file. The CLOB data extract should contain exactly the same number of records as a primary file.

Note:

When splitting the extract into multiple data files, make sure that the numbers of extracted records in the primary and secondary files are matching.

It is applicable for both table-level and maintenance-object level load.

Sample Scenario:

Table CI_PER includes CLOB column C1_PER_DATA_AREA.The CLOB field is used to store customer’s resume.

The legacy table contain 10K records and the CLOB data is available for some of the records

The primary data file, CI_PREM.csv contains 10K lines, one line per record

The secondary data file, CI_PREM_CLOB, contains 10K records too. The records with the empty CLOB are represented by CLOB delimiter.

Splitting single table data extract with CLOB

The following example illustrates how to split the single table large volume extract correctly if the CLOB data is supplied in the secondary file:

Assuming the table has 10K records, split into two equal parts. The following files should be created:

- Primary File 1 with 5K records

- Secondary File 1 with 5K CLOB entries

- Primary File 2 with 5K records

- Secondary File 2 with 5K CLOB entries

Splitting maintenance object data extract with CLOB

The following example illustrates how to split the maintenance object large volume extract correctly if the CLOB data is supplied in the secondary file:

Assuming the maintenance object has two tables, one of the tables includes CLOB column and the primary table has 10K records. The data supposed to be split into two equal parts. The following files should be created:

- Primary File 1 with 5K records for the primary table and corresponding records for the child table

- Secondary File 1 with CLOB entries corresponding to the table in the Primary File 1

- Primary File 2 with 5K records for the primary table and corresponding records for the child table

- Secondary File 2 with CLOB entries corresponding to the table in the Primary File 2

Note:

For Maintenance Object-level load consider supplying CLOB data in the primary file, to avoid complicated logic of data splitting.

Refer to CLOB Data - XML for limitations concerning XML CLOB data

File Layout and Data Formatting

The input data specifications for each table or maintenance object that are subject to conversion specification files are available for download. Refer to Input and Output File Location for details.

Specifications are generated based on the metadata and conversion configurations. Configurations control delimiters and enclosing characters and define CLOB data processing rules.

The data extract file is expected to contain one record per each target table row. The data field order in the record has to be exactly the same as it is listed in the specification file.

The specifications contain field-by-field data formatting rules for:

- Data type and size

- Date, DateTime and Time formatting

- Special notes on CLOB fields

The fields in the record are expected to be separated by a delimiter character (or string).

The CLOB data in the main record has to be enclosed in the CLOB Delimiter string, for example <clobend>some clob data<clobend>

For the not-nullable columns with no data, a single space enclosed in the enclosing character (or string) has to be supplied, for example “ “

Enclosing character (or string) can also be used to encapsulate data that includes a field delimiter, for example “Hello, World”

Defining Custom Data Delimiters and Enclosing Characters

The default configurations are delivered with the base product.

Your entire legacy data or a specific table may require use of a different data delimiter and/or enclosing characters.

- Define new data delimiter string, CLOB delimiter string and/or enclosing string

- Configure Conversion Task Type using newly created delimiters

- Amend Conversion Master Configuration, setting default (for all tables or maintenance objects) or override (for specific table or maintenance Object) instructions.

- Regenerate Conversion Artifacts

Now you can create data extract according to the newly generated specifications.

Input Data for a Staging Table

The extract for a single table contains delimited data records. Depending on the conversion configuration, the CLOB data should be supplied either inline or in a separate, secondary file.

Input Data File Names

Input data file names has to follow the rules described in this chapter. The names are key-sensitive.

File Type

File Name

Single data file per table, no CLOB

File name equal target table name, i.e. CI_PREM

Single data file per table, CLOB data in secondary file

Primary file name equal target table name, i.e. CI_PREM

Secondary file name composed as target table name concatenated with ‘_CLOB’, i.e. CI_PREM_CLOB

Multiple data file per table, no CLOB

File name is composed as target table name concatenated with file number, i.e. CI_PREM1, CI_PREM2 etc

Multiple data file per table, CLOB data in secondary file

Primary file name is composed as target table name concatenated with numeric file number, i.e. CI_PREM1, CI_PREM2 etc

Secondary file name composed as target table name concatenated with ‘_CLOB’ and file number, i.e. CI_PREM_CLOB1, CI_PREM_CLOB2 etc

Input Data for Maintenance Object

The extract for a maintenance object contains delimited data records for all tables included in the maintenance object. Depending on the conversion configuration, the CLOB data should be supplied either inline or in a separate, secondary files, one file per table containing CLOB. Refer to Notes on Secondary Data Files (CLOB Data) for limitations concerning XML CLOB data and more details.

Input Data File Names

Input data file names has to follow the rules described in this chapter. The names are key-sensitive.

File names for Maintenance Object contain Maintenance Object Code. If the code includes spaces or special characters, it should be replaced with ‘_’, for example:

For actual MO Code: SP/MTR HIST, in the file name, use SP_MTR_HST

File Type

File Name

Single data file per Maintenance Object, no CLOB

File name equal target maintenance object name, i.e. PREMISE

Single data file per Maintenance Object, CLOB data in secondary file

Primary file name equal maintenance object name, i.e. PREMISE

Secondary files name composed as maintenance object name concatenated with table name concatenated with ‘_CLOB’.

For example, if CI_PREM table contains CLOB, the secondary file name is. PREMISE_CI_PREM_CLOB

Multiple data file per Maintenance Object, no CLOB

File name is composed as target maintenance object name concatenated with file number, i.e. PREMISE1, PREMISE 2 etc

Multiple data file per Maintenance Object, CLOB data in secondary file

Primary file name is composed as target maintenance object name concatenated with file number, i.e. PREMISE1, PREMISE 2 etc

Secondary files name composed as maintenance object name concatenated with table name concatenated with ‘_CLOB’ concatenated with file number.

For example, if CI_PREM table contains CLOB, the secondary file name is. PREMISE_CI_PREM_CLOB1, PREMISE_CI_PREM_CLOB2, etc

Limitations for Input Data

Key Tables

Due to the technical limitations, the Key tables cannot be loaded in the multi-threaded mode. If you decided to create input data files using the Maintenance Object method, consider the following:

- Created data extract(s) for a Maintenance Object data, but exclude the Key table(s) and run data upload in the multi-threaded batches

- Create separate extract for the Key table(s) only and upload them in the single threaded batches.

CLOB Data Size

The maximum size of the CLOB data included in the main data file is 10K. If you converted CLOB data size is expected to be larger than 10K, create secondary data file.

CLOB Data - XML

The XML data formatted using new line character cannot be uploaded as part of the primary data file. If your CLOB data includes formatted XML, you should create secondary data file(s) for CLOB columns.

Conversion Orchestration

This section provides information on orchestrating a data conversion.

Next in This Section

- Input and Output File Location

- Understanding Load Data Process

- Understanding the Conversion Orchestration Process

Input and Output File Location

Locations for conversion input and output files on the sFTP server:

- Upload input data files: download/upload-download/conversion/upload

- Download the process output: logs, discard and bad files: download/upload-download/conversion/download

- Download archived (processed) input data files: download/upload-download/conversion/archive

- Download input data specifications: download/upload-download/conversion/reference

Understanding Load Data Process

The setup of the batch controls that is necessary to support data conversion and legacy data extract upload is described in Data Load Batch Controls .

The following sections explain the process of legacy data extract upload with SQL loader.

Next in This Section

- Load Data Batch Run Parameters

- Multi-Threading

- Load Outcome – Log, Bad and Rejected Files

- Interrupted Load

- Tables Cleanup and Index Maintenance

- Load Performance Tuning

Load Data Batch Run Parameters

The data upload batch is processing single target object – Table or Maintenance Object. The data extract may be supplied in one or multiple files, created and named according to the Input File instructions for a Staging Table and Maintenance Object .

The process is multi-threaded and optimized for the parallel load.

Using the batch parameters you can control:

- Level of logging

- Data extract retention

- Maximum number of load errors

Multi-Threading

The process is threading by dividing the multiple data files between the threads. Each thread in turn, is processing its files one by one.

The exception is Key Tables. They are index-organized tables and have to be loaded in the single thread, due to the SQL Loader restrictions.

Load Outcome – Log, Bad and Rejected Files

SQL Loader output files are available for download after each run . Refer to Input and Output File Location for details. To ensure file name uniqueness, the output file names are concatenated with the current timestamp.

- Log file contains the information about the run, including number of record processed, errors encountered and other useful information. The level of logging is controlled by the batch parameter log .

- Bad and Rejected files contains the records that were rejected by either the SQL Loader or the database.

Interrupted Load

The data load process can be re-started. Once SQL Loader reached the maximum number of errors allowed for the run, it records the position of the last record in error in the log. The restarted load begins pulling the data from the file after skipping certain number of records.

In order to continue processing interrupted load, perform the following steps:

- Retrieve the log file. Find statement 'Specify SKIP= n when continuing the load .' in the log file.

- Re-upload the input data file to the server

- Submit the batch once again, this time specifying the n as a skip batch parameter

Tables Cleanup and Index Maintenance

The SQL Loader is running in parallel mode in order to maximize the performance. Therefore the target tables are not emptied prior to the data insertion and it has to be done implicitly, by running corresponding batch jobs.

Indexes are disabled during the data upload. The product provides batch processes that support index disabling/re-building and statistics update.

- User batch control K1-SCLTB to truncate tables in Staging area and batch control K1-CLNTB to truncate tables in Production

- Use batch control K1-SDSIN to disable indexes in Staging area and batch control   K1-DRPIN to disable indexes in Production

- Use batch control K1-CLNKY to truncate Key Reference tables in Staging area

The supported scenarios are:

- Truncate Specific Table or Maintenance Object: In order to truncate the specific table, submit the corresponding batch job, specifying table parameter. In order to truncate the data that stored in a specific Maintenance Object, submit the corresponding batch job, specifying maintenanceObject parameter. The process will also disable indexes in the truncated tables.

Note: If the truncated table’s metadata defines a Key table, the Key table gets truncated too.

- Truncate all Converted Tables: In order to truncate all converted tables run the corresponding batch job without specifying table or maintenanceObject parameters. The process will disable indexes and truncate all tables marked for conversion in the metadata.

- Truncate Key Reference Tables for Specific Table or Maintenance Object: In order to truncate Key Reference table linked to a staging table, submit the corresponding batch job, specifying table parameter. In order to truncate Key Reference tables for a specific Maintenance Object, submit the corresponding batch job, specifying maintenanceObject parameter.

- Truncate all Key Reference Tables: Submit the corresponding batch job without specifying table or maintenanceObject parameters to truncate all Key Reference tables.

- Disable Indexes for Specific Table or Maintenance Object: In order to disable indexes for the specific table, submit the corresponding batch job, specifying table parameter. In order to disable indexes for the specific Maintenance Object’s tables, submit the corresponding batch job, specifying maintenanceObject parameter.

- Disable Indexes for all converted Tables: In order to disable indexes on all converted tables run the corresponding batch job without specifying table or maintenanceObject parameters. The process will disable indexes and truncate all tables marked for conversion in the metadata.

Load Performance Tuning

The data specifics – volumes, structure and other aspects – may justify customizing the default configurations for all or some tables.

The SQL Loader is processing data according to the Control File. The fragment that contains general load parameters is stored as Managed Content that is referenced on the Conversion Task Type.

You can create new Managed Content, configure the Conversion Task Type and specify the new settings on Conversion Master Configuration, for all or specific Tables or Maintenance Objects.

Understanding the Conversion Orchestration Process

The following sections provide information on general aspects of conversion orchestration.

Enabling Conversion

Conversion activities are possible as long as conversion is enabled in the environment. The authorized Conversion Administrator may run the corresponding batch job to enable conversion.

Switching between Staging and Production Schema

In the environment enabled for conversion, the online application is running against the database schema that contains synonyms pointing to either Staging or Production tables.

The synonyms could be switched by running the corresponding batch job.

The switching is possible only while Conversion is Enabled

Navigate to Admin –> Conversion Support –> Switch Schema to perform the action.

Preparing for Conversion

The preparation steps include evaluating initial conversion configurations provided by the product, customizing the configurations if needed, and finally, generating conversion artifacts.

The preparation should be done when the environment is running against Production schema

Conversion Development

The creation of the legacy data extract and rehearsal of the data load and subsequent conversion data processing is done while the environment is running against Staging schema.

Consider creating and scheduling the sequence of the batch processes for both data load and following validation and insertion.

Include table truncation, index maintenance and statistic updates into batch chains.

Conversion Run

For the mock-up, or dress rehearsal or the actual go-live conversion run you may choose to amend data load batch controls for tables/maintenance objects to improve performance:

- Reduce the logging level – set log batch parameter to NOLOG

- Do not retain input data – set retaininput batch parameter to PURGE

Disabling Conversion

After conversion is completed, the various activities such as table truncation and index maintenance should not be allowed.

Upon conversion project completion, switch the schema to Production and request that the authorized Conversion Administrator run the corresponding batch job to disable Conversion in the environment.

Enabling Incremental Conversion

The legacy data conversion may be done in stages. After the first chunk is converted and the system begins running in production, you may need to convert the next portion(s) of the data. This orchestration macro-scenario is called incremental conversion; it imposes certain limits and restrictions on the conversion activities and it has to be approved by the management.

If the incremental conversion has been approved , request that the authorized Conversion Administrator run the corresponding batch job to enable the incremental conversion in the environment.

Security Setup for Conversion

The services associated with data conversion are combined into the following user groups

- Conversion Administrators includes the services linked to the most sensitive database operations: enable/disable conversion and switching database synonyms between production and staging schema

- Conversion Development includes the services associated with conversion-related configurations

- Conversion Operations provides access to services associated with data load batch processes. This group could be extended to include services associated with specific table(s) or maintenance object data loads

These user groups are included in the base product. Your implementation may chose to use it as is or create a different setup.

Conversion Reconciliation Reports

Your cloud service subscription includes an access to the BI Publisher instance that can be used to create and run data reports against both production and staging tables. Contact your Security Administrator for access information.

Work and Asset Management Administrative User Guide

The topics in this section describe how to administer Oracle Utilities Work and Asset Management.

Next in This Section

- System Wide Oracle Utilities Work and Asset Management Configuration

This section provides information on general system wide settings which fall outside of the major functional areas within the application.

- Approval Processing Options

The following sections provide information on configuring approval processing.

- Asset Management Options

The following sections provide information on concepts related to managing assets and components.

- Condition Assessment Options

The following sections provide information abpit concepts related to managing condition assessment options.

- Operational Device Management Options

The following sections provide information on configuring for operational device management functionality.

- Inventory Management Options

The following sections provide information on configuring inventory management.

- Purchasing Options

The following sections provide information on configuring purchasing.

- Resource Management Options

The following sections provide information on concepts related to managing resources.

- Work Management Options

The following sections provide information on concepts related to managing work including work requests, work orders, activities , and so on.

- Construction Work Management Options

The following sections provide information on configuring for construction work management functionality.

- Preventive Maintenance Options

The following sections provide information on configuring for preventive maintenance functionality.

- Financials Options

The following sections provide information about the portals and objects related to financial transactions throughout the system.

- Integrations

This chapter provides information related to integrating with other applications.

- Table Setup Sequence

This section provides a checklist of the primary data that must be configured as part of your implementation. This can be used as a useful map of the relationship between objects in the system.

- Batch Control Configuration

Batch controls are used to process and organize information throughout the system. For example, reorder review relies upon batch processing to complete the reorder processing and generate the appropriate purchasing documents. Likewise, shift plan templates use batch patch processing to generate shifts and make updates to shift plans. This section describes the base package batch controls provided with Oracle Utilities Work and Asset Management.

System Wide Oracle Utilities Work and Asset Management Configuration

This section provides information on general system wide settings which fall outside of the major functional areas within the application.

Next in This Section

- Defining Home Page Configuration

The Oracle Utilities Work and Asset Management home page provides a comprehensive dashboard where users can access all of the information they need to review and complete their work.

- Defining General System Master Configuration

This section provides information about general system master configurations.

- About Access Control

Access control provides a way for your organization to limit or classify record information by "plant", varying work locations or work functions. For example, you may have asset types that are only used at your northern location, so you would use an access type to designate those asset types as restricted to that location. You can also use access controls to hide or show areas of the application to users based on any other business requirements as needed. This is referred to as “row level security” in the application framework.

- About Statistics

The Statistics portal captures metrics that are collected via batch processing. These embedded analytics are not present in real time, but rather are accumulated and presented as they are processed by batch. These analytics are displayed on the Home Page.

- E-Mail Configuration

This section provides information about requirements to configure settings for emails sent from within the system regarding objects such as approvals, purchase orders, timekeeping, and so on.

- Three Decimals Places for Currency

Oracle Utilities Work and Asset Management supports up to three digits after the decimal for currency.

- Communication

This section provides the configuration guidelines related to communication types.

- BI Configuration Administration

This section provides information about requirements for defining Oracle Utilities Advanced Spatial and Operational Analytics configurations.

Defining Home Page Configuration

The Oracle Utilities Work and Asset Management home page provides a comprehensive dashboard where users can access all of the information they need to review and complete their work.

Configure User Settings for the Home Page

Please refer to About the Home Page in the Business User Guide for a conceptual overview of home page functionality.

Beyond entering Master Configuration settings for the home page, you might also consider the following:

Users can add or remove zones on the Home Page by navigating to Preferences and selecting the Portal Preferences tab. Here, under the various Home Page sections, you can select which defaults zones display, whether or not they are initially collapsed or expanded, and the order in which they appear. Depending on your business practices, you can choose to disable this ability for users by modifying their access to these settings by assigning a Template User for Portal Preferences to each User record. Refer to The Big Picture of Portals and Zones , or the User - Portal Preferences section under User Preferences in the Oracle Utilities Application Framework documentation for more information on using portal preferences. in the Oracle Utilities Application Framework documentation for more information.

Add Zones to the Home Page

You may find that it is beneficial to include additional zones on the Main tab of the Home Page such as a zone to show Saved Searches, Bookmarks or Favorites. You may also want to add organizational information such as a company news zone or additional custom zones. You can configure the Home Page, or any portal, to display the zones that you choose by configuring zone settings as described under The Big Picture of Portals and Zones in the Oracle Utilities Application Framework documentation.

Defining General System Master Configuration

This section provides information about general system master configurations.

Use the following to locate information about master configuration:

- Refer to the embedded help for descriptions of the specific settings on the Master Configuration pages for functional areas.

- Refer to the Defining Master Configurations section for more technical details on using master configurations.

Note: Note that for most system functionality, master configurations must be set before other settings or configurations. However, there are some master configurations that depend upon initial configuration of admin settings. Please refer to the embedded help for each individual master configuration for more information.

About Access Control

Access control provides a way for your organization to limit or classify record information by "plant", varying work locations or work functions. For example, you may have asset types that are only used at your northern location, so you would use an access type to designate those asset types as restricted to that location. You can also use access controls to hide or show areas of the application to users based on any other business requirements as needed. This is referred to as “row level security” in the application framework.

Access groups are defined in the Access Group portal and are assigned to records as an Owning Organization.

Objects in the system can be assigned an Owning Organization. Some administrative “type” objects which have a corresponding transactional object also have an Instance Organization which is used as the default Owning Organization on the transactional object. For example, the Instance Organization identified on an asset type is used as the Owning Organization for assets of that type. The Instance Organization can be used to add a more finite level of control. The search screen for assets includes an Owning Organization field so that users can search by this categorization.

Extending the example from above, you can restrict users in the southern location from viewing records related to the northern location (and vice versa) by limiting access to Owning Organizations. If your implementation needs to restrict access, you will need to implement data access roles for users, in addition to assigning Owning Organization values and rights.

Refer to The Big Picture of Row Security in the Oracle Utilities Application Framework documentation for more information on data access roles and how they work with access groups.

About Statistics

The Statistics portal captures metrics that are collected via batch processing. These embedded analytics are not present in real time, but rather are accumulated and presented as they are processed by batch. These analytics are displayed on the Home Page.

This portal is mainly used as a method to speed up the processing associated with presenting complex statistics or statistics that represent a large amount of data. Processing these in batches rather than in real time significantly increases system performance.

Authorized users can also use the portal to manipulate the statistical data that is displayed on the Home Page such as selecting crews or dates. The Log tab tracks who made changes to the data, and when.

Refer to the section or the Defining Home Page Configuration section for more information.

During configuration, you will want to review this portal to ensure that the metrics are set up to reflect your business requirements.

E-Mail Configuration

This section provides information about requirements to configure settings for emails sent from within the system regarding objects such as approvals, purchase orders, timekeeping, and so on.

To configure the system for sending emails complete the following:

1. Create or update a Feature Configuration for email configuration (EMAILCONFIG ).

The Feature Type should be set as External Messages

2. Add the System Email From Option Type with a valid from address in the Value field.

This identifies the sender to use for system emails.

Example:

3. Create a message sender with the following:

- Invocation Type: Real-time

- Message Class: RTEMAILSNDR

4. Select the Context tab on the message sender and add the SMTP information.

This includes the following:

- SMTP Host Name: Example: inernal-mail-router.yourcompany.com

- SMTP Password: Your SMTP password

- SMTP Username: Example: admin@oracle.com

Refer to the Real-Time Message Configuration topic and the Message Sender - Context topic in the Oracle Utilities Application Framework section for more information.

Three Decimals Places for Currency

Oracle Utilities Work and Asset Management supports up to three digits after the decimal for currency.

To configure the system for three decimal currency, set the number of decimal positions when defining currency codes.

Refer to the Defining Currency Codes section and the Currency Formats section in the Oracle Utilities Application Framework documentation for more information.

Communication

This section provides the configuration guidelines related to communication types.

Next in This Section

- About Communication Types

Communication types define the information required for the system to receive messages from external systems.

- Defining Communication Types

Navigate to the Communication Types portal under Admin, select Add, complete the required fields according to your business practices and Save.

About Communication Types

Communication types define the information required for the system to receive messages from external systems.

Communication Data Mapping

Communication Data Mapping information is used to populate communication business object elements from information within the inbound communication's raw message.

Attachment Suppression

When a message is received from an external system, the message may contain attachment data which is very large. The substitution text entered in this section can be used in place of that large data in the completion event list on the inbound communication. The attachment element xpath identifies the data to match it to the substitution text. This serves to prevent transfer delays in cases where large amounts of data might overload the browser.

Defining Communication Types

Navigate to the Communication Types portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

BI Configuration Administration

This section provides information about requirements for defining Oracle Utilities Advanced Spatial and Operational Analytics configurations.

BI configuration administration involves creating, maintaining and working with Oracle Utilities Advanced Spatial and Operational Analytics configurations. Refer to the Oracle Utilities Advanced Spatial and Operational Analytics documentation for more information and the specific data mapping and metric reference guidelines for business intelligence.

Master Configuration for Business Intelligence

Ensure that you define extract parameters as required for your implementation using the Master Configuration portal.

BI Configuration Portal

The BI Configuration portal holds information about the configuration tasks related to Oracle Utilities Advanced Spatial and Operational Analytics.

This is a display-only portal that provides a bird's eye view of the configuration for Oracle Utilities Advanced Spatial and Operational Analytics. The portal also provides links and guidelines for the areas that need configuration to successfully run the extract transfer and load processes from Oracle Utilities Advanced Spatial Analytics.

Users can leverage the reporting capabilities of Oracle Utilities Advanced Spatial and Operational Analytics to view various measures such as:

- How many Assets have failed acceptance testing

- How many Assets have been in store for a given period

- How many Assets have been installed for a given period

- and so on.

Bucket Configuration

Key performance indicators can be defined to measure the age of assets grouped into ranges, or buckets, which are defined in the Bucket Configuration portal.

Analysts can use these metrics to review the overall asset ages classified into various ranges, or buckets, such as 0 - 100 days, 100 - 300 days or more than 300 days, and so on.

Use the Bucket Configuration portal to define age buckets, such as:

- Asset age

- Asset installation age

- Asset in storage age

- Asset criticality

- Asset condition score

- Number of cycles overdue

- Work priority

These buckets can be defined for a specific asset type or as a default set of buckets that will be applicable to all assets that do not have any specific buckets defined on the asset type.

Approval Processing Options

The following sections provide information on configuring approval processing.

Next in This Section

- Understanding Approval Processing Configuration

This section provides the configuration guidelines related to approval processing.

- Configuring Approval Processing

This section provides configuration tasks for approval processing administrative support records.

Understanding Approval Processing Configuration

This section provides the configuration guidelines related to approval processing.

One of the ways that the system simplifies and speeds up work is by routing records when they require approval. For example, purchase requests, work requests, employee leave, and other functions can be configured to require approvals.

Approval requests use approval profiles to determine the properties and requirements for the approval. The approval profile contains the rules for a certain kind of approval process, including the To Do Type to send out, the Approval Hierarchy with To Do Roles and approval limits, the type of objects that the profile pertains to, and the work calendar to use. A common structure defines the approval process, users, and limits for each given functional area using approval processing.

Please refer to the Approval Processing section in the Business User Guide for a conceptual overview of approval functionality.

Next in This Section

- About Approval Profiles

Approval profiles are used to define the approval hierarchy within your organization.

About Approval Profiles

Approval profiles are used to define the approval hierarchy within your organization.

Based on To Do Roles, approval profiles define:

- the types of documents the role can approve

- the working calendar to use when determining approval time lines and when to send To Dos

- dollar amount maximums that the role is authorized to approve

An approval profile can have one or many To Do Roles, and it is possible for an approver to be assigned to more than one To Do Role in the same approval profile.

Depending on the notification setting designated on the approval profile, the approver receives an email and/or an alert in their To Do List.

Note: Individual approvers can choose to modify their notification settings for approvals. Navigate to the User portal and access the Characteristic tab to set the Approval Profile E-Mail Override setting to disable email notifications for approval requests. When this is set, the approver does not receive any emails and must rely on the approval dashboard or To Dos.

Configuring Approval Processing

This section provides configuration tasks for approval processing administrative support records.

Please refer to the Approval Processing section in the Business User Guide for a conceptual overview of approval functionality.

Refer to the Understanding Approval Processing Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining an Approval Profile

Navigate to the Approval Profile portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Setting the Approval Profile for a Record Type

Your organization should configure your system with the To Do Types, To Do Roles, and Approval Profiles in combination so that when a user selects the Submit for Approval option, the list of possible approval profiles is limited to a finite selection of approvers based on the type of document they are trying to approve.

- Defining the Approval Hierarchy

Approval profiles can reference one or many To Do Roles. The way in which you structure your approval profiles depends on how regulated the structure needs to be for your organization.

- Defining To Do Types, To Do Roles, and To Do Entries for Approvals

It is recommended that you follow the delivered naming convention and preface your To Do Types and To Do Roles with “Approval” so that they are easy to find when adding them to approval profiles.

Defining an Approval Profile

Navigate to the Approval Profile portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: Work calendars and related document types must be created in order to reference them on the approval profile.

The base product provides a To Do Type for each base maintenance object that needs approval. Your implementation must add To Do Roles and assign users to those roles.

To Do Types are associated on the approval profile to determine which To Do Types are responsible for that profile.

Establish the approval hierarchy for the profile by entering To Do Roles, approval types, notification methods and amount limits for each To Do Role.

Setting the Approval Profile for a Record Type

Your organization should configure your system with the To Do Types, To Do Roles, and Approval Profiles in combination so that when a user selects the Submit for Approval option, the list of possible approval profiles is limited to a finite selection of approvers based on the type of document they are trying to approve.

Defining the Approval Hierarchy

Approval profiles can reference one or many To Do Roles. The way in which you structure your approval profiles depends on how regulated the structure needs to be for your organization.

Your business practices may be such that your approvals can go to a limited number of Supervisor and Manager roles, or they can be more advanced having detailed levels. To this end, the To Do Roles you create for can be shared across Document Types or they can all be kept discrete to business process and functionality. This is also true for the No Approval user group. There can be one to be reused across your approval processing configuration, or you can set more to address different functions.

One type of record, such as work order, might require several different Approval Profiles to address different situations. For example,

- PM work might be “auto-approved” since the work needed has already been analyzed, planned and approved.

- Emergency work might bypass normal approval processing since it might come in at off hours or will otherwise be subject to different approval than regular work.

- Regular work will likely require general approval processing.

Approval Types

Approval Types indicate whether the approval role is standard, mandatory or notification only:

- Standard: A standard approver might appear on the approval hierarchy with other approvers with equal approval authority. Any standard approver can record the decision before the record moves on to the next approver in the hierarchy.

- Mandatory: Indicates that this approver must provide an approval decision on the record. Approval processing is not complete until this decision is recorded.

- Notification Only: Notification only approvers are only sent a To Do that the approval is pending. The system does not validate an amount limit and the approver does not have to respond in order for the record to be approved.

Additional Approval Profile Settings

- Initial Notification Method: Indicates whether the approver receives an e-mail, an alert in their To Do List, both or none.

- Authorized to Approve: (Non-Amount Based only) When multiple To Do Roles are added to the profile, this field identifies which is authorized to approve. At least one to do role must be added with this value set to Yes.

- Amount Limit: Provides the maximum amount that the approver in the indicated role is allowed to approve. If the value on the record in need of approval exceeds this limit for the role, the approval path must move on to the next approver or the requester is notified that no one on the approval profile has sufficient authority to approve the request.

- Timeout Threshold: Indicates the amount of time that the approver has to respond to the approval request, in days. For example, if the threshold is set to “2”, the approver has 2 days to approve requests.
If the approver does not respond within the set time, another alert is sent. Additional alerts are sent up to the set number of retries.

- Maximum Retry: Indicates the number of times that the system will retry sending the approval request to approvers with the ToDo Role before timing out the request. For example, of the Timeout Threshold is set to “2” and the Maximum Retry is set to “3” the system will try three times for a total of 6 days resending the alert or email every 2 days. If the approvers fail to respond, the request is routed to the next approver in the hierarchy and that person receives the email or alert.

The following table provides examples of the types of roles you may need to create to support your approval hierarchy:

Admin Object

Example of Data to Create

To Do Types

These default types are delivered with the base package with the ToDo Type Usage set to Automatic:

- Approval Type — Employee Unavailability

- Approval Type — ODC

- Approval Type — Project

- Approval Type — Purchase Order

- Approval Type — Purchase Requisition

- Approval Type — Timesheet

- Approval Type — Work Order

- Approval Type — Work Request

To Do Role

- General Approver

- General Director

- General Manager

- General Notification Only Approver

- General Supervisor

- General Work Management Supervisor

- General Work Management Manager

- General Purchasing Manager

- General Purchasing Supervisor

User Groups

- Authorized for No Approval

Approval Profiles

- Approval Amount

- General Purchasing Approver

- High Value Purchasing Approver

- General Work Request Approver

- General Work Order Approver

- High Value Work Order Approver

- Project Approver

- Other Direct Charges Approver

- No Approval

- Emergency Work Approval

- No Amount

- Employee Unavailability Approver

- Timesheet Approver

Using a scenario of a moderate structure with a separate approval profile for each document type, refer to the following table for an example of the hierarchy:

Seq

To Do Role

Approval Type

Initial Notification Method

Amount Limit

Time Out Threshold

Maximum Retry

10

Supervisor

Standard

To Do List Only

$1000

2 (days)

1 (retry)

20

General Manager

Mandatory

Both (email and To Do List)

$5000

2 (days)

2 (retries)

This example establishes a hierarchy where the first role to receive the approval request is at the supervisor level with a minimal approval limit. This supervisor would approve the request only to inform the general manager that he or she approves, but since the General Manager has been set with a mandatory approval type, he or she must approve the request for the processing to be considered complete.

Next in This Section

- About No Approval Required Profiles

User groups are referenced on No Approval Required approval profiles to indicate the user groups that can create an approval request routed to the indicated approval profile.

- About No Amount Profiles

No amount profiles are used for documents that do not have explicit amounts/costs associated - for instance a Work Request would not support Amount-based Approval since there is no cost estimate associated with it. In this case you would use the no amount based approach in configuring To Do Roles.

About No Approval Required Profiles

User groups are referenced on No Approval Required approval profiles to indicate the user groups that can create an approval request routed to the indicated approval profile.

This helps to control which users are allowed to submit “no approval” requests. User groups are defined as a listing of user profiles in the User Group portal.

About No Amount Profiles

No amount profiles are used for documents that do not have explicit amounts/costs associated - for instance a Work Request would not support Amount-based Approval since there is no cost estimate associated with it. In this case you would use the no amount based approach in configuring To Do Roles.

Defining To Do Types, To Do Roles, and To Do Entries for Approvals

It is recommended that you follow the delivered naming convention and preface your To Do Types and To Do Roles with “Approval” so that they are easy to find when adding them to approval profiles.

When an object, such as a work order, is submitted for approval, an approval request record is created showing the related document, the person who submitted it and when, and which roles need to approve. Background processing creates a To Do Entry for each step of the approval process, and the entry gets linked to the approver when action is taken. Administrators can review To Do Entries to audit how approval processing is working.

Please refer to the Oracle Utilities Application Framework section titled To Do Processing in the Oracle Utilities Application Framework documentation for more information about To Do functionalities.

Asset Management Options

The following sections provide information on concepts related to managing assets and components.

Next in This Section

- Understanding Asset Management Configuration

This section provides configuration guidelines for Asset Management functionality.

- Configuring Assets

This section provides configuration tasks for asset records.

Understanding Asset Management Configuration

This section provides configuration guidelines for Asset Management functionality.

The Oracle Utilities Work and Asset Management system provides functionality to configure assets

Next in This Section

- About Asset Types, Assets and Components

Asset types define the attributes for assets of a certain type.

- About Asset Location Types

Asset location types define the details of asset or component locations of a certain type.

- About Service History Types and Service History

Service history types define the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement, and so on.

- About Asset Inspections (Assessments)

This section provides information on the setup needed to configure asset inspections.

- About Measurement Identifiers, Types, and Measurements (Operational Readings)

Measurement types define the units to use for a particular measurement and establish the values needed to support the evaluation of measurements such as upper and lower reading thresholds, maximum reading value, and so on. Asset measurements, or operational data, might include mileage, hours of uptime, number of start-stops, and so on.

About Asset Types, Assets and Components

Asset types define the attributes for assets of a certain type.

This includes determining information such as the valid location types and service history types for the assets and whether or not such assets can have attached components. Average cost statistics are displayed graphically on the Asset Type record. An asset is an object in an infrastructure, such as a smart meter, poles, pipes, transformer or any other material item owned or managed by an organization. Components are devices or other objects that are attached to another device, usually an asset.

Assets and Components

The application provides a number of utilities specific business objects that can generally be used to create assets and components for specific purposes. However, your implementation will likely require several business objects to define assets and components of other types.

Specifications

Specifications can include a wide variety of possible fields, so the definitions of your specifications should be considered carefully. The base package specifications provide a general starting point for your specification set-up including the following:

- General Maintenance Specification

- Operational Maintenance Specification

- Operational Device Specification

- Fleet Specification

- General Specification

- IT Specification

- Infrastructure Specification

In Oracle Utilities Operational Device Management

- Analog Meter Specification

- Communication Component Specification

- Communication Relay Specification

- Firmware Specification

- Smart Meter Specification

For example, your implementation may want to include additional fleet/vehicle specification details by extending the data area - W1-VehicleDetail. Specification detail values may also be extended by adding values to the following look-up fields:

Specification detail values may also be extended by adding values to the following look-up fields:

- MODEL_YEAR_FLG - model year

- VEHICLE_COLOR_FLG - vehicle color

- DRIVE_TYPE_FLG - drive type

- FUEL_TYPE_FLG fuel type

Tracked Assets, Stock Items and Inventory

Link a specification to stock items to associate the items to the tracked assets that are also associated with the specification. This allows the stock item to be used to track the asset. Only specifications with asset types configured with an ‘inventory controlled storeroom’ node type can be added.

Extending Asset Statuses

If your implementation needs to create a new Asset Lifecycle BO with a status which differs from the base package, you can choose to create them by extending W1-AssetDisposition. With this extension, note the following:

- ‘assetRelationship’ on the Asset Disposition has 3 values: Installed, Attached and Not Installed. Installed is applicable to assets when they are installed in service.

- Attached is applicable to components when they are attached to an asset.

- Not Installed is applicable when assets or components are in other statuses (in store, in receipt, in repair, rejected or retired).

- Since the assetRelationship is in a clob, the base package uses a naming convention using the asset disposition code. The first two characters should be ‘IN’ for installed, ‘AT’ for attached and ‘NI’ for not installed.

Linear Assets

Setting up your assets so that they are recognized as a “system” can help you to manage maintenance. If your organization uses GIS, this functionality can also help to position your assets on the mapping system that you have in use. Please consider the following when configuring linear assets:

- The Asset Location Type and Asset Location determine where the linear asset is connected.

- Linear assets include “Connected to” fields which allow you to define the connections between assets

For example, a pipe system would consist of a pipe connected to a manhole connected to the next pipe, and so on.

About Asset Location Types

Asset location types define the details of asset or component locations of a certain type.

Valid asset locations might be service points, other locations for installed assets, or any other location as defined by your organization, for example:

- General asset location types define a type of asset location that is used to indicate the physical location where assets or components are installed.

- Plant asset location types define a type of asset location for a fixed organizational structure such as a building, factory, or other facility.

- Linear asset location types define a type of asset location that is part of a system such as pipes and manholes or poles and cables.

Out of Service Location Types

When assets are changed to statuses such as “In Repair” or “Pending Disposition” the asset location is typically transitioned to an out of service location. This may be a warehouse or garage where the asset is stored, dispositioned or repaired.

About Service History Types and Service History

Service history types define the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement, and so on.

The base package service history business objects can be used out of the box, however it is likely that your implementation will want to configure special business objects to capture specific service history events.

Planned Service History Types

Your implementation can create “planned” service history types for use with template activities. These service history types can be selected by users when creating the completion event to add service history on an activity.

About Asset Inspections (Assessments)

This section provides information on the setup needed to configure asset inspections.

Each Asset Type can be associated with many Service History Types, each of which falls into a Service History Category (the lookup values are downtime, repair, inspection, maintenance).

Each Service History Type can define a set of Questions that are used to standardize the work that is performed. A Question can be set up as single or multiple choice, with predefined Question Answers for the user to select. Assessment Class and Assessment Group are additional categorization mechanisms to define how the Assets of an Asset Type are to be maintained and reviewed.

Preventive Maintenance Schedules link Service History Types with (template-like) Work Orders.

Comprehensively, an asset inspection is configured with the following:

- Condition Assessment Questions and Answers
Questions reference a service history subclass which is based upon the types of service history that can be created such as deficiency, general purpose, general weighted, operational device, percent of new, and questionnaire. These represent the types of inspection scoring that is used to inspect and evaluate assets. The weight of each question is defined on the question itself. The overall scoring is a calculation of the overall weights on every condition assessment group which is included on every service history type included on the inspection. The Calculation Flag in the question is used to determine if the answer is used in the calculation of asset condition rating.

- Service History Type (referencing questions and answers and an inspection condition inspection group)
Refer to About Service History for information on inspection types.

- Condition Assessment Group (referencing the service history type and defining the aging factors)

- Condition Assessment Class (referencing the condition assessment group)

- Asset Type (referencing an inspection service history type)

- Preventive Maintenance Schedule (referencing the asset type with the inspection service history)

- Preventive Maintenance Trigger (referencing the maintenance schedule, a template work order, and the activity type)
When the maintenance is triggered, the system uses the template work order to generate the work order then activity to complete the inspection. Service history is generated from the completion of the inspection, and the inspection calculations are created as processing transitions through the inspection lifecycle. Refer to the Sample Asset Inspection Processing section for examples.

Note: These concepts can also be used to configure general preventive maintenance.

Aging Factors

Aging Factors define a numerical value which, when applied, decreases the validity of the inspection score as the inspection date becomes less relevant. Confidence rating is a percentage scoring method for assets where 100% means complete confidence that the asset is in good condition. The percentage drops as asset condition data ages.

The ranges and aging factor can be determined as best derived by your business practices. As an example, you may break the ranges down into quarters:

- 1.00 for 0 to 90 days

- .75 for 91 to 180 days

- .50 for 181 to 270 days

- .25 for 271 to 99,999 days

Sample Data Configuration

Example of Assessment Class Data

Assessment Class

Assessment Group

Service History Type

Description

Group

Weight

Participate in Calculations?

Assessment Weight

Rotate Equipment

Electrical

0.25

Yes

Insulation

Assess the insulation

Yes

0.60

Conductivity

Assess the conductivity

Yes

0.40

Performance

0.75

Yes

Performance

Curve test

Yes

0.50

Reliability

Reliability testing

Yes

0.50

Example of Service History Type (General Weighted) Data

Service History Type

Question

Weight

Answer

Point Value

Rotating Equipment Electrical Insulation

How is the appearance?

Apparently near infinite insulation resistance

1

Good condition, only slight discoloration

2

No cracks or deterioration. Aging and discoloration okay.

3

Detectable cracks / deterioration - non-penetrating

4

Cracked / deteriorated to conductors

5

Heat distribution

0.50

Appears "new", with no heat imbalance between winding

1

No heat imbalance between windings or at the junction box

2

Factors indicate equipment is in later half of normal life

3

Detectable heat imbalance between windings or junction box

4

Significant heat imbalance between windings or junction box

5

Sample Asset Inspection Processing

This section provides sample processing examples for a local asset and an asset worked from an external system using inspection as an example. This general processing concept can be applied to other maintenance and activities performed on assets.

Example: Configuring and Performing an Inspection for a Local Activity

1. Create a scheduled activity type configured with:

- Local Activity BO

- Inspection Service History Type (e.g. Percent of New, General Weighted or Deficiency Inspection Type)

- Service History from Activity Type Completion Event Type (configured with Create Service History Using Payload Completion Event)

2. Create an activity for an asset using the activity type.

3. Create a Create Service History Using Payload Completion Event.

4. Perform the inspection and record the answers in the service history.

5. Set the activity to complete to execute the completion event.
This triggers the following:

- Create the service history from the payload.

- The service history total inspection points are calculated and normalized to a grade by looking up the grade based on the total points using extendable lookup.

- The condition rating and confidence rating are calculated and the asset is updated with the values.

Example: Configuring and Performing an Inspection from an External System

1. Create an outbound activity type configured with :

- Outbound Activity BO

- Inspection Service History Type (e.g. Percent of New, General Weighted or Deficiency Inspection Type)

- Service History from Activity Type Completion Event Type (configured with Create Service History Using Payload Completion Event)

2. Create an activity for an asset using the outbound activity type.

3. Send the activity to external system.
This triggers the following:

- WAM creates the outbound message containing questions and answers from the service history type on the outbound activity type

- External system receives message from WAM, does the inspection and sends the answers to the questions back to WAM

- TFW/Integration layer creates the inbound communication containing the raw message from external system

- Inbound communication gets processed

- Based on the completion event type on the activity type, a Create Service History Using Payload Completion Event gets created (Pending state)

- The inbound communication transitions the activity to next default state

- The outbound activity transitions from Sent to Execute Completion Events

- The completion event gets transitioned to the next state

- Completion event transitions from Pending to Executed

- The completion event creates the service history based on the service history type on the activity type using the payload on the completion event

- Service History moves from Pending to Compute Score (via FW auto transition monitor)

- The service history total inspection points are calculated and normalized to a grade by looking up the grade based on the total points using extendable lookup

- The condition rating and confidence rating are calculated and the asset is updated with the values

About Measurement Identifiers, Types, and Measurements (Operational Readings)

Measurement types define the units to use for a particular measurement and establish the values needed to support the evaluation of measurements such as upper and lower reading thresholds, maximum reading value, and so on. Asset measurements, or operational data, might include mileage, hours of uptime, number of start-stops, and so on.

Please note the following with regard to of implementing measurement types.

- Each asset is assigned a list of valid measurement types to regulate the types of measurements taken for that asset.
An Asset can have many measurement types, but the measurement identifiers of the asset must be unique. In other words, if two measurement types share the same measurement identifier, then they will not be allowed on a single asset, at the same time. This rule enforces the notion that when a user enters data, or when a report queries data, there will never be any overlap in measurement history.

- Typically measurement types would be metered reads or gauge reads. Gauge reads are usually compared to a threshold or valid range of values. For example, tire pressure for a typical truck tire should be between 34 and 36 psi. These would be defined as the lower limit and upper limit for the measurement type.

- Measurement type identifiers can be used if the measurement type needs to be identified in an external system.

- Measurement types can be configured to trigger to dos or automatically create work when readings are recorded that fall inside or outside of defined tolerances.

Measurement Type Exception Handling

The exception handling fields define the parameters for how the system should respond if there are issues with the reading such as the To Do Type and Role that should receive alerts, retries, and discard reason. For example, if the reading is outside of the measurement range, the system sends an alert to the indicated To Do Role.

About Measurement Identifiers

Measurement identifiers establish the units used to measure assets. Each measurement type is meant to represent a unique combination of Unit of Measure, Time of Use, and a Special Identifier to uniquely describe the set of measurement readings taken for an asset. This might include tire pressure (psi), temperature ratings (degrees), daytime usage (kWh) (peak), and so on. The special identifier is used to uniquely describe unusual measurement configurations, like pressure input vs. pressure output (psi input, psi output) or even gas compositions (% argon, % helium).

Measurements

Measurements manage the asset operational and runtime data which is collected and tracked for assets. Asset measurements might include mileage, hours of uptime, number of start-stops, and so on.

Please note the following with regard to measurements:

- Configure the extendable lookup for Gauge Reason as needed.

- Measurement readings are entered in the Measurement maintenance portal via the Measurement Quick Entry zone.

Configuring Assets

This section provides configuration tasks for asset records.

Next in This Section

- Defining Measurement Identifiers

Navigate to the Measurement Identifier portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Measurement Types (Operational Readings)

Navigate to the Measurement Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Questions

Navigate to the Question portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Service History Types

Navigate to the Service History Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Asset Location Types

Navigate to the Asset Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Out of Service Location Types

Navigate to the Out of Service Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Asset Types

Navigate to the Asset Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Component Types

Use this procedure to define component types.

- Defining Condition Assessment Groups

Navigate to the Condition Assessment Group portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Condition Assessment Classes

Navigate to the Condition Assessment Class portal under Admin, select Add mode, complete the required fields according to your business practices and Save.

Defining Measurement Identifiers

Navigate to the Measurement Identifier portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites:

- Unit of Measure

- Time of Use

- Special Identifier

Defining Measurement Types (Operational Readings)

Navigate to the Measurement Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the measurement type record:

Note: This list does not represent required fields.

- Measurement Identifier

- Template Work Order (depending on the type of measurement)

Defining Questions

Navigate to the Question portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Service History Types

Navigate to the Service History Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the service history type record:

Note: This list does not represent required fields.

- Questions

Defining Asset Location Types

Navigate to the Asset Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the asset location type record:

Note: This list does not necessarily represent required fields.

- Location Class/Subclass

- Service Type

- Parent Location or Organization Type (as applicable)

Defining Out of Service Location Types

Navigate to the Out of Service Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the out of service location type record:

Note: This list does not necessarily represent required fields.

- Location Class/Subclass

- Parent Location Type (as applicable)

- Organization Type (as applicable)

You can also enter a parent location or organization to establish the position of storerooms of this type in the location hierarchy.

Defining Asset Types

Navigate to the Asset Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the asset type record:

Note: This list does not represent required fields.

- Assessment Class

- Asset Location Type or Out of Service Location Type

- Service History Type

- Failure Profile

Defining Component Types

Use this procedure to define component types.

Prerequisites: The following are referenced by the asset type record:

Note: This list does not represent required fields.

- Assessment Class

- Asset Location Type

- Storeroom

- Service History Type

1. Navigate to the Asset Type portal under the Admin menu and select Add.

2. Complete the required fields according to your business practices and Save

- Valid Location Types where the component can be received, stored, installed, repaired, and so on.

- Valid Attached to Asset Types to indicate the asset types where the component can be attached/installed.

- Valid Service History Types which define the types of service that can be performed on components of this type.

You can now create components based on the component type.

Condition Assessment Options

The following sections provide information abpit concepts related to managing condition assessment options.

Next in This Section

- Condition Assessment Options

The following sections provide information abpit concepts related to managing condition assessment options.

- Configuring Assets

This section provides configuration tasks for asset records.

- About Condition Assessment Questions

Questions and related answers can be entered to define “inspection templates” which guide asset inspections. Questions are associated to service history types which are then associated to asset types.

- About Condition Assessment Groups

Condition assessment groups are used with asset assessment/condition rating functionality. They group assessment service history types (i.e. inspection types) and factor in asset aging factors to comprise a weighted combination of elements that affect how condition ratings are calculated.

- About Condition Assessment Classes

Assessment classes are sets of condition assessment groups, and are necessary for asset assessment/condition rating functionality. They are used to manage assets according to a set of inspection criteria and to define an inspection rating system for inspections. The purpose of this rating system is to measure the deterioration of the assets and the effect of the deterioration on the service levels that are expected of the asset.

About Condition Assessment Questions

Questions and related answers can be entered to define “inspection templates” which guide asset inspections. Questions are associated to service history types which are then associated to asset types.

When it comes time to complete an inspection, the previously defined set of questions and answers guides the process for inspectors as the complete the inspection out in the field. Answers may be presented as a check box, multiple choice, or free-form text.

Sample Questions and Answers

What is the condition of the pipe?

- Good no severe cracks and less than 2 small defects per 100 ft.

- Acceptable no severe cracks and less than 5 small defects per 100 ft.

- Needs Attention no severe cracks but 5 or greater small defects per 100 ft.

- Needs Immediate Attention One or more severe cracks detected.

Note: The bulleted items would appear as radio buttons in the actual questionnaire as answers.

Questionnaires also support a "fill in the blanks" format. A similar question to that above might appear as follows with “fill in the blanks” t:

Assess the condition of the pipe:

- Small Defects per 100 ft.: |_________|

- Number of severe Cracks: |_________|

Note: In this case, each blank would appear as text boxes in the actual questionnaire to capture the answers.

About Condition Assessment Groups

Condition assessment groups are used with asset assessment/condition rating functionality. They group assessment service history types (i.e. inspection types) and factor in asset aging factors to comprise a weighted combination of elements that affect how condition ratings are calculated.

Use the Service History Type section to establish a list of valid service history types that can be used with this assessment group.

- Weight: Represents the importance of the service history type as it relates to the overall group. For example, you might add 2 types, one for visual inspection and one for mechanical inspection. The visual inspection might have a weight of .25 where the mechanical inspection is weighted more heavily at .75. The overall total weight must equal 1.

- Calculation: Indicates whether or not the service history type should be included in the overall scoring calculation for the inspection.

Note: Any service history type that is used for scoring must have a weight. The sum weight of all service history types used for that scoring must be equal to 1.

Use the Aging Factors section to define the parameters for calculating the confidence rating for inspections related to the assessment. Confidence rating is a percentage scoring method for assets where 100% means complete confidence that the asset is in good condition. The percentage drops as asset condition data ages. Note that the older the data, the lower the percentage because the less reliable the inspection data. The confidence rating is shown on the related asset record.

- Sequence

- Start Range/End Range: Define an age range, in number of days.

- Aging Factor: A numerical value which, when applied, decreases the validity of the inspection score as the inspection date becomes less relevant.

The ranges and aging factor can be determined as best derived by your business practices. As an example, you may break the ranges down into quarters:

- 1.00 for 0 to 90 days

- .75 for 91 to 180 days

- .50 for 181 to 270 days

- .25 for 271 to 99,999 days

Note the final end range is entered as “99,999” since the system requires a fail safe end range. The confidence rating resets each time a new, “fresh”, inspection is completed.

About Condition Assessment Classes

Assessment classes are sets of condition assessment groups, and are necessary for asset assessment/condition rating functionality. They are used to manage assets according to a set of inspection criteria and to define an inspection rating system for inspections. The purpose of this rating system is to measure the deterioration of the assets and the effect of the deterioration on the service levels that are expected of the asset.

Inspections are performed to assess the asset's current physical condition via a scoring method that grades the asset based on severity and number of deficiencies found. The results of the inspection program are used to determine the residual life (i.e. effective remaining life) of an asset and to support the review of preventative maintenance activities to ensure optimization of the asset's life. Please note the following with respect to assessment classes:

- Assessment classes are associated to assets on the asset type.

- Assessment classes are formed by a grouping of condition assessment groups. The total of all weights must equal 1.

The Assessment Class Summary Information section displays a pie chart to represent the percentage of assets by score and a cluster chart to show the number of inspections, per type, per month (for the most recent months).

The Group Weight field represents the importance of the assessment group as it relates to the class. For example, you might add 2 classes, one for visual inspection and one for mechanical inspection. The visual inspection might have a weight of .25 where the mechanical inspection is weighted more heavily at .75. The overall total weight must equal 1.

Defining Condition Assessment Groups

Navigate to the Condition Assessment Group portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the condition assessment record:

Note: This list does not represent required fields.

- Service History Type

Service history type defines the questions and answers used when completing an inspection. Set up the condition assessment group to define which service history types are valid for the condition assessment. This will then be referenced on the condition assessment class to provide the comprehensive criteria for an inspection.

Defining Condition Assessment Classes

Navigate to the Condition Assessment Class portal under Admin, select Add mode, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the assessment class record:

Note: This list does not necessarily represent required fields.

- Condition Assessment Group

A condition assessment class may consist of one or many condition assessment groups which define the comprehensive criteria for a type of inspection.

Operational Device Management Options

The following sections provide information on configuring for operational device management functionality.

Next in This Section

- Understanding Operational Device Management Configuration

This section provides configuration guidelines for Operational Device Management functionality.

- Configuring Operational Device Management

This section provides configuration tasks for operational device management administrative support records.

Understanding Operational Device Management Configuration

This section provides configuration guidelines for Operational Device Management functionality.

Oracle Utilities Operational Device Management provides functionality to handle large volumes of assets and to manage the receipt, installation, maintenance, tracking and removal of those assets. Oracle Utilities Operational Device Management is purchased as a separate license to further enhance Oracle Utilities Work and Asset Management. However, since these two products are typically always sold together, this guide includes documentation for both products seamlessly. Contact your sales representative or Oracle Support for more information.

Please refer to the Operational Device Management section in the Business User Guide for a conceptual overview of asset functionality.

Device Assets and Components

The application provides a number of utilities specific business objects that can generally be used to create assets and components for specific purposes. However, your implementation will likely require several business objects to define assets and components of other types. Refer to the About Asset Types, Assets and Components section for general information on configuring assets and components.

Next in This Section

- About Asset and Component Configuration Types

Configuration types define the information required for various asset configurations with other assets, components, firmware, and other aspects of a functioning configured system.

About Asset and Component Configuration Types

Configuration types define the information required for various asset configurations with other assets, components, firmware, and other aspects of a functioning configured system.

Configurations are referenced on specifications which are then referenced on assets and components to indicate the best way that these entities can work with the other entities that they are connected to in the field.

In general configuration classes define the types of connections that are being configured. The generic classes that are available include:

- Single Asset

- Asset/Component

- Asset to Asset

- Asset/Component to Asset

- Asset to Asset/Component

- Asset/Component to Asset/Component

Configuring Operational Device Management

This section provides configuration tasks for operational device management administrative support records.

Please refer to the Operational Device Management section in the Business User Guide for a conceptual overview of asset functionality.

Refer to the Understanding Operational Device Management Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Asset Configuration Types

Navigate to the Configuration Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Defining Asset Configuration Types

Navigate to the Configuration Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Inventory Management Options

The following sections provide information on configuring inventory management.

Next in This Section

- Understanding Inventory Configuration

This section provides guidelines for configuring inventory functionality.

- Configuring Inventory Management

This section provides configuration tasks for inventory processing administrative support records.

Understanding Inventory Configuration

This section provides guidelines for configuring inventory functionality.

Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. Materials are purchased and received, then as that inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available.

Please refer to the Inventory section in the Business User Guide for a conceptual overview of inventory functionality.

Master Configuration

Ensure that you create master configuration settings in Inventory Management Master Configuration.

Next in This Section

- About Stock Items, Stock Item Details and Storerooms

Stock items are defined as material resources that are held in storerooms and issued to activities that require the materials to be completed. The stock item record determines whether or not the type of stock can be purchased, repaired, tracked, and so on. Storerooms define the physical location where stock items are stored.

- About Commodity Codes

Commodity Codes are an alternate way to describe stock items which can be helpful when you need to locate a specific stock code because they form a ‘logical’ segmented code for a stock item. Codes are segmented by commodity category, name, type, and composition. The Stock Item portal can be searched by commodity code where you can filter by a variety of criteria.

About Stock Items, Stock Item Details and Storerooms

Stock items are defined as material resources that are held in storerooms and issued to activities that require the materials to be completed. The stock item record determines whether or not the type of stock can be purchased, repaired, tracked, and so on. Storerooms define the physical location where stock items are stored.

The Stock Item Detail (SID) record determines whether or not the type of stock can be purchased, repaired, tracked, and so on. An SID is a particular stock item in a particular storeroom. For example, in one storeroom, a particular stock item might be stored whereas in another storeroom that same stock item might only be direct purchased. The item would have a different SID in each storeroom. In cases where an item can only be direct purchased for activities, the storeroom only acts as the receiving dock and courtesy storage location until the workers from the activity come to pick them up.

Types of Stock Items

Stock Item Details manage various types of stock items. The type determines how the stock is handled and managed, and when and how it can be ordered.

- Regular Stock Items:

Regular stock items are kept in inventory until they are needed.

These types of items are controlled by the following rules:

- created with the trackable flag set to “false” and the lot managed flag set to “false” on the stock item record

- can be repairable

- can be expensed at receipt

- can be designated as direct purchase items

- can be configured for reorder review, trackable items have a “safety stock” flag

- Direct Purchase Stock Items:

Direct purchase stock items can only be directly purchased when needed for work.

These types of items are controlled by the following rules:

- created with the trackable flag set to “false” and the lot managed flag set to “false” on the stock item record

- can be repairable

- can be expensed at receipt

- can be designated as direct purchase items

- can be configured for reorder review, trackable items have a “safety stock” flag

- Lot Managed Stock Items:

Lot managed items are tracked in a special way in the system. These types of items are fabricated, sold, and delivered in “lots” or “batches” of the item. This is significant when there are qualities or details about the item that might vary between lots. If this item is lot managed, the system tracks a lot number with any transaction that changes the quantity of the item for the storeroom. Since each received lot also has its inventory tracked independently, lot managed item details all have “child" stock item details for each lot that is received. This means a “master” stock item detail that is classified as "lot managed" on its stock item detail with many “lot" stock item details (one for every lot that is received). When an activity references lot managed items as a resource requirement, the master stock item detail is referenced. Lots only become relevant when material is issued from or received into inventory. This means the material issue for lot managed stock items reference a lot stock item detail, but the planned activity references the master stock item detail. During receiving of a lot managed stock item, the system verifies whether or not the storeroom has a lot specific SID for that lot number and creates one if one does not exist.

These types of items are controlled by the following rules:

- created with the trackable flag set to “false” and the lot managed flag set to “true” on the stock item record

- cannot be expensed at receipt

- cannot be designated as direct purchase items

- Trackable Stock Items:

Trackable stock items merit being individually identified and followed from initial receipt on-site through complete usage. These are typically large, expensive or specialized assets or materials which are inspected when they are received into inventory, repaired if they break, can be installed on other assets, and are otherwise carefully dispositioned in the system.

These types of items are controlled by the following rules:

- created with the trackable flag set to “true” and the lot managed flag set to “false” on the stock item record.

- can be repairable

- cannot be expensed at receipt

- cannot be designated as direct purchase items

- when configured for reorder review, trackable items have a “safety stock” flag

- indicate the specification for the trackable item on the stock item record

- Capital Spare:

Capital Spare items are identified during accept and return as fixed assets so that an external Fixed Asset Management system can maintain their depreciation. A property unit is required on capital spare items.

These types of items are controlled by the following rules:

- created with the trackable flag set to “true” and the lot managed flag set to “false” on the stock item record.

When defining stock items, crafts, equipment and miscellaneous resources, there is an option, Default Values to Activity, to define whether or not the information should be defaulted onto activities when resource requirements reference the resource. If this option is set to No for a stock item, then the item can only be added to stock item details as a direct purchase item.

ABC Classification

Represents a system used to classify stock items based on their frequency of use and value. Class A items have the highest dollar usage value and are the most often counted while Class C items have the lowest dollar usage value and are the least often counted.

Material Lifecycle

Materials are typically purchased and received into storerooms. Material Issue and Return tracks the movements of stock items as they go from storerooms to work activities and potentially back again. When materials are requested for work, and if the storeroom can fulfill the request, then material issue lines are created to specify one stock item each. Stock Transactions and Financial Transactions are created at time of issue to record both the inventory impact and the accounting for the use of the items.

There will be occasions when the material that was issued is not actually used and material returns are created and processed to return the items into inventory. This again will create reversing transactions on inventory and accounting.

Material Disposition

Material Disposition is used to log and track the repair of assets. Typically there are two Material Disposition Lines, one for the old asset (Initial Relationship of ‘In Service’) that needs repair and the other for the new asset (Initial Relationship of ‘Issued’) that replaces the old asset.

Physical Inventory

Physical inventory is the act of counting actual numbers of items on hand to reconcile with numbers calculated by the system. A Physical Inventory is related to a storeroom, and is one of three types of inventory (inventory, lot inventory, tracked inventory). The user defined Stock Category lookup can be used to group Stock Items together as needed.

Inventory Adjustments

Inventory adjustments allow authorized users to adjust not only the inventory quantity, similar to Physical Inventory, but also inventory value such as average unit price.

About Commodity Codes

Commodity Codes are an alternate way to describe stock items which can be helpful when you need to locate a specific stock code because they form a ‘logical’ segmented code for a stock item. Codes are segmented by commodity category, name, type, and composition. The Stock Item portal can be searched by commodity code where you can filter by a variety of criteria.

Commodity codes cannot be created directly. Instead they are constructed as a combination of the following:

- Commodity Category — Commodity Category is the most general description of the item. A sample category code might be “M” for a piece of mechanical equipment.

- Commodity Name — For each category, there is a unique list of Commodity Names. A sample commodity name for mechanical equipment might be a “Check Valve”.

- Commodity Type — For each category and name combination, there is a unique list of Commodity Types. A sample commodity type for a check valve might be a high-pressure pneumatic check valve.

- Commodity Composition — For each category/name/type combination, there is a unique list of Commodity Compositions. The composition code is used to indicate the primary material in the item (e.g. titanium alloy).

These attributes must be created in sequence within the commodity code hierarchy itself.

Configuring Inventory Management

This section provides configuration tasks for inventory processing administrative support records.

Please refer to the Inventory section in the Business User Guide for a conceptual overview of inventory functionality.

Refer to the Understanding Inventory Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining a Storeroom

Navigate to the Storeroom portal under Inventory, select Add, complete the required fields according to your business practices and Save.

- Defining Storeroom Types

Navigate to the Storeroom Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Commodity Codes

Use this procedure to create a commodity code with the four levels of category, name, type and composition.

Defining a Storeroom

Navigate to the Storeroom portal under Inventory, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the storeroom record:

Note: This list does not represent required fields.

- Storeroom Type

- Organization (as applicable)

- Contacts (as applicable)

- Address information

- Accounting information — Cost Centers and Expense Codes

- Buyer

Make sure that the Location Disposition is set to Active if you want to make the location available for reference on other records.

You can also enter a parent location or organization to establish the position this storeroom in the location hierarchy. This might be defaulted from the out of service location type.

Defining Storeroom Types

Navigate to the Storeroom Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the storeroom type record:

Note: This list does not necessarily represent required fields.

- Location Class

- Parent Location Type (as applicable)

- Organization Type (as applicable)

You can also enter a parent location or organization to establish the position of storerooms of this type in the location hierarchy.

Storeroom type is referenced when creating Storerooms.

Defining Commodity Codes

Use this procedure to create a commodity code with the four levels of category, name, type and composition.

Prerequisites: It is a good idea to have a detailed spreadsheet or plan for creating commodity codes for your organization.

1. Navigate to the Commodity Code portal.

2. Select the Add Category link.

3. Create the Commodity Category with a description.

4. Create a Commodity Name as needed and Save.

It is recommended that you create one name at a time. If you need to create additional names, create them after completing this process through the commodity composition for each name.

5. From the hierarchy tree, select the Expand icon next to the Category you just created.

6. Select one of the commodity names just created and click the Edit button.

7. Enter a Commodity Type as needed and Save.

It is recommended that you create one type at a time. If you need to create additional types, create them after completing this process through the commodity composition for each name and type.

8. From the hierarchy tree, select the Expand icon next to the Category you just created then expand the full hierarchy down to the Type.

9. Select the Type you just created and click the Edit button.

10. Enter Commodity Compositions as needed and Save.

This is the last level of the hierarchy, so you can create as many as you need for each category, name, and type.

Purchasing Options

The following sections provide information on configuring purchasing.

Next in This Section

- Understanding Purchasing Configuration

This section provides configuration guidelines for purchasing functionality.

- Configuring Purchasing

This section provides configuration tasks for purchasing administrative support records.

Understanding Purchasing Configuration

This section provides configuration guidelines for purchasing functionality.

Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items.

Refer to the Purchasing section in the Business User Guide for a conceptual overview of purchasing functionality.

Master Configuration

Ensure that you create master configuration settings in Purchasing Master Configuration.

Next in This Section

- About Contact Types and Contacts

Contact types establish parameters for contact of a specific type.

- About Buyers

Buyers are persons designated within your organization to make purchases and purchasing decisions.

- About Purchase Commodities

Purchase commodities are used to assign a specific buyer to a classification of stock items in the storeroom.

- About Capability Types

Capability types refer to the types of products and services provided by a vendor. They are referenced on vendor locations to help identify what the vendor can provide, per location.

- About Payment Terms

Payment terms represent the payment and credit agreement between your organization and the vendor such as the number of days your organization has to pay the invoice or the forms of payment that are accepted.

- About FOB (Freight on Board or Free on Board)

Freight on Board or Free on Board (FOB) represents the delivery charge terms negotiated for purchase orders from the vendor. This also includes the vendor or the seller's obligation to deliver goods at a designated place.

- About Invoicing

Please note the following with regard to invoicing:

About Contact Types and Contacts

Contact types establish parameters for contact of a specific type.

Contacts are referenced on locations to provide an associated person or business. The main attributes for contacts are managed in the Contact portal. For example, a contact might be referenced as the main person on site for assets or storerooms.

About Buyers

Buyers are persons designated within your organization to make purchases and purchasing decisions.

Buyers can be referenced on purchase requisitions and purchase orders to provide an official point of contact for the purchasing transaction. Depending on your business process and configuration settings, buyers may also be able to make changes on approved purchasing documents that affect price and quantity without re-obtaining approval.

Buyers also manage automatic reordering.

About Purchase Commodities

Purchase commodities are used to assign a specific buyer to a classification of stock items in the storeroom.

A buyer is specified on the purchase commodity so that when the commodity is then referenced on a stock item, the buyer association to that item is made. This allows buyers to be associated with a specialization over specific materials, equipment, etc. When items of that type are needed, the purchase commodity helps you to identify the buyer with that specialty.

About Capability Types

Capability types refer to the types of products and services provided by a vendor. They are referenced on vendor locations to help identify what the vendor can provide, per location.

Since they are primarily informational, your organization may use capability types in a variety of ways. For example, you might run reports on which vendors provide particular goods or services to have this information handy for buyers' reference when making purchasing decisions.

About Payment Terms

Payment terms represent the payment and credit agreement between your organization and the vendor such as the number of days your organization has to pay the invoice or the forms of payment that are accepted.

About FOB (Freight on Board or Free on Board)

Freight on Board or Free on Board (FOB) represents the delivery charge terms negotiated for purchase orders from the vendor. This also includes the vendor or the seller's obligation to deliver goods at a designated place.

This information is referenced on vendor locations, blanket contracts and expedite orders to help define delivery terms.

About Invoicing

Please note the following with regard to invoicing:

Master Configuration

Ensure that you create master configuration settings in Purchasing Master Configuration and Financial Master Configuration to process invoicing transactions.

Default Approval Profile for Invoice Submission

If your implementation would like to define a default approval profile and status reason when users submit an invoice for approval processing, you must configure each individual user record with an approval title.

- Navigate to the user and click the Characteristics tab.

- In the Characteristic Type of Invoice Approval Profile field, enter an approval profile for characteristic value.

To have the invoice go straight to approved status, select an approval profile based on a No Approval Required type of profile.

Invoice Total Cost Validation

The Check Invoice Total algorithm validates that any manually entered invoice total matches the system calculated invoice total. If your implementation wants to enforce matching totals, you can introduce two new algorithms to enforce matching totals:

- Create a validation algorithm to make the Manually Entered Total field on the invoice required.

- Create a copy of W1-CKINVCTTL and modify it so that it produces an error rather than a warning.

This will force the user to correct the invoice before the system allows it to be processed. Once this copy is created, you should inactivate W1-CKINVCTTL.

Automatic Invoicing

In order for the system to complete automatic invoicing against purchase orders, the vendor on the purchase order must be set as an “auto pay” vendor. When the purchase order is created, it must also be set as “auto pay”. After items are received against the purchase order, the system automatically creates an invoice with line items. When an invoice is automatically created, no additional line items can be added to the created invoice and none of the line items can be deleted. If the receipt included more items received than ordered, these invoice line items are placed in “Pending Resolution” status when the invoice is submitted for approval. An authorized user must then change the quantity on the purchase order before the invoice can be reprocessed successfully.

Note that when Require Receipt for Services is set to “No” in Purchasing Master Configuration, users cannot create a receipt against a purchase order which was created for services. This also affects automatic invoicing in that when this is set to "No", invoices for services must be created manually even when the vendor is set as an "Auto Pay" vendor.

A/P Interface

If WAM owns invoice in your implementation and you need to interface invoices to your A/P system, the base product provides support to batch your invoices. You need to define an algorithm based on the W1-ADENTRYGP algorithm type and plug this algorithm onto the appropriate status of the invoice header BO, e.g. ‘Posted’. This algorithm writes a record in F1_GEN_PROC table for that invoice with a batch code, which should be defined in the ‘Invoice A/P Extract’ parameter of the Purchase Master Configuration, and batch run number.

Please note that the base product doesn’t deliver the actual batch process that extracts and formats the data. It’s the implementation team’s responsibility to develop such batch process. You can use the base GL batch extract as a template. The batch control for the GL extract is ‘W1-GLDL’.

If invoice is owned by your ERP system, there is a productized integration to transfer WAM related invoices into WAM, please refer to the ERP integration documentation for more information.

Tax Rate Schedule Selection

As the default, the Tax Rate Schedule drop-down does not include the option to select a blank value. If your implementation requires the option to not select a tax rate schedule, you must create a Tax Rate Schedule such as “No Tax Rate” with Tax Rate Components containing factors with zero values. Users can then select this option to not include taxes on an invoice.

Configuring Tax Characteristics for Invoice Lines

Your implementation must complete the following to ensure that tax component characteristics are captured on Invoice line items:

- For each required tax component, create one characteristic type with an entity flag of Tax Component and one characteristic type with an entity flag of Factor.

This ensures that the characteristic type will be included on the Factor Characteristic Types drop down on Factors.

- Introduce a flattened characteristic element for the characteristic type in the Invoice Line business object.

In order to include these elements in the base business object, the corresponding Invoice Info data area included in the business object can be extended to add the characteristic element(s).

- Configure a pre-processing algorithm for the BO to set default values for the tax characteristic element, if necessary.

- Use the Retrieve Characteristic Value from Input Factor Characteristic List characteristic source algorithm for the factor that will be referenced for the tax component.

Cost Allocation

Note that if any of the cost allocation settings for invoicing are set as “general” the system creates a financial transaction with the following entries:

- Freight:

- Debit Freight Expense; cost center/expense code from Purchasing Master Configuration

- Credit Payables Clearing; cost center/expense code from Financial Master Configuration

- Extra Cost:

- Debit Extra Cost Expense; cost center/expense code from Purchasing Master Configuration

- Credit Payables Clearing; cost center/expense code from Financial Master Configuration

- Discount:

- Debit Payables Clearing; cost center/expense code from Financial Master Configuration

- Credit Discount; cost center/expense code from Purchasing Master Configuration

Configuring Purchasing

This section provides configuration tasks for purchasing administrative support records.

Please refer to the Purchasing section in the Business User Guide for a conceptual overview of purchasing functionality.

Refer to the Understanding Purchasing Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Contact Types

Navigate to the Contact Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Buyers

Navigate to the Buyer portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Purchase Commodities

Navigate to the Purchase Commodity portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Capability Types

Navigate to the Capability Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Vendor Payment Terms

Navigate to the Payment Terms portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining a Blanket Contract Access List

Navigate to the Blanket Contract Access List portal, select Add, complete the required fields according to your business practices and Save.

- Granting User Access to a Blanket Contract

Use this procedure to grant users access to a blanket contract.

- Defining FOB (Freight on Board or Free on Board)

Navigate to the FOB portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Exchange Rates

To properly set up exchange rates for alternate currencies, you must configure the following:

Defining Contact Types

Navigate to the Contact Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Contact type is referenced when creating contacts.

Defining Buyers

Navigate to the Buyer portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the buyer record:

Note: This list does not represent required fields.

- User ID

Make sure that you activate the buyer after the record is created. Buyers are not available to reference on other records until they are active. Click the Activate button on the Buyer record.

Defining Purchase Commodities

Navigate to the Purchase Commodity portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the purchase commodity record:

Note: This list does not represent required fields.

- Buyer

Defining Capability Types

Navigate to the Capability Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Vendor Payment Terms

Navigate to the Payment Terms portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining a Blanket Contract Access List

Navigate to the Blanket Contract Access List portal, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the blanket contract access list record:

Note: This list does not represent required fields.

- User ID

Granting User Access to a Blanket Contract

Use this procedure to grant users access to a blanket contract.

1. Navigate to the Blanket Contract Access List portal in Edit mode.

2. Add users and the dollar limit that each user is allowed to “use” for the blanket contracts where they have authorization.

When a blanket contract with access list restrictions is being applied toward creating a purchase order, the system verifies that the user is valid based on this list and that the limit is not exceeded. Blanket contract access restrictions are determined by your business practices and configuration settings.

Defining FOB (Freight on Board or Free on Board)

Navigate to the FOB portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Exchange Rates

To properly set up exchange rates for alternate currencies, you must configure the following:

Note: Refer to the demo environment for the full example.

- Define the currency in the Currency portal.
Demo Example:

- Canadian Dollars (CAD)

- Configure a Characteristic Type and Value to define a single value.
Demo Example:

- Single Value

- Configure a Characteristic Source Algorithm for the factor which will define the conversion.
Demo Example:

- Factor Retrieve Single Value Characteristic

- Configure a factor to define the exchange rate to use.
Demo Example (U.S. to Canadian exchange rate):

- Factor: USD to CAD Exchange Rate

- Factor Characteristic Type: Single Value

- Factor Characteristic Value: Single Value

- Effective Date/Time: 01–01–2015

- Factor Value: 1.2200000
This value represents the value of your base currency converted to the foreign currency. In this case, 1 US dollar converted to Canadian.

- Add the factor to the Purchasing Master Configuration under Alternate Currency Exchange Rates.

When the currency is referenced on a vendor location and processing completes from issued purchase order through to receipt, the system calculates the converted unit price and total. The purchase order displays both values: In this example, Order Total in USD and Converted Total in CAD.

Resource Management Options

The following sections provide information on concepts related to managing resources.

Next in This Section

- Understanding Resource Management Configuration

This section provides guidelines for configuring resource management functionality.

- Configuring Resource Management

This section provides configuration tasks for resource management administrative support records.

Understanding Resource Management Configuration

This section provides guidelines for configuring resource management functionality.

Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on.

Refer to the Resources section in the Business User Guide for a conceptual overview of resource functionality.

Master Configuration

Ensure that you create master configuration settings in Resource Management Master Configuration.

Next in This Section

- About Organization Types and Organizations

Organization types define the main attributes for organizations of a certain type.

- About Organizations

Organizations are used for categorization and reporting for locations.

- About Attachments, Document Types and Documents

The Documents portal is used to track, store and manage electronic reference materials for use throughout the system. Documents are based on Document Types, which are managed under Admin to establish the types of documents or URLs that can be used by your organization. This does not limit the file type, but can be used as a categorization for your organization’s documents or URLs.

- About Documents (Attachments, Standard Notes and URL Attachments)

The Documents portal is used to track, store and manage electronic reference materials for use throughout the system. Documents are based on Document Types, which are managed under Admin to establish the types of documents or URLs that can be used by your organization. This does not limit the file type, but can be used as a categorization for your organization’s documents or URLs.

- About Service Classes

Service classes categorize activity types and indicate the type of work a shift is responsible for. Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity.

- About Service Areas

Service areas define a logical boundary of your organization's territory. Every crew shift is populated with a list of service areas that the crew shift is allowed to work. This is matched up with the service area indicated on the activity to help determine which crew shift can work the activity.

- About Resource Unit of Measurement

Resource units of measurement (UOM) establish the acceptable units used to quantify resources such as stock items, materials, equipment, or other used by your organization.

- About Business Units

Business units are used as cost reporting entities for timekeeping expenses.

- About Employee Types and Employees

Employee types define the kinds of employees that can be defined for your organization. For example, your organization might use employee types to define regular employees, skilled employees, and novice employees.

- About Employees

Employee records are used to manage human resource level information for the workers within your organization.

- About Employee Unavailability Types and Employee Unavailability

Employee unavailability types define kinds of situations where employees may be unavailable such as general leave, jury duty, vacation, sick leave, and so on.

- About Employee Unavailability

Employee unavailability records establish periods of time where an employee has been given leave from his or her regular job duties. This might be due to circumstances such as vacation, sick leave, attending a training, jury duty, and so on. Logging employee unavailability allows the system to know when an employee is not available to perform work on the crews that he or she is associated with.

- About Crew Shift Types, Crew Types, Crew Shifts and Crews

Crew shift types establish the kind of crew shift such as day, night, swing, and so on.

- About Crews

A crew is a group of workers that can be assigned to complete work. Crews are used to group workers, schedule work, and help organize work schedules.

- About Crafts, Equipment and Miscellaneous Resources

Crafts define a skill or work specialty for crew members such as mechanic, electrician, plumber, arborist, and so on.

- About Crafts

Crafts define a skill or work specialty for crew members such as mechanic, electrician, plumber, arborist, and so on.

- About Equipment

Equipment is defined by your organization to be referenced as a resource type available for use to complete work. This might include machinery, tools or other equipment required to work activities (crane, bulldozer, drill, etc.).

- About Miscellaneous Resources

Other resources are defined by your organization to be referenced as a resource type available for use to complete work.

- About Shift Plan Templates

Shift plan templates are used to automatically generate crew shifts based on a set of pre-defined shift criteria such as the shift type, the shift rotation, the defined calendar, and so on.

About Organization Types and Organizations

Organization types define the main attributes for organizations of a certain type.

Organizations are used for categorization and reporting for locations.

For example, your reporting may include a hierarchy that groups locations by a structure of parent and child organizations.

Valid Parent Types

Parent organization types define the set of valid location types and organization types that can be used to define a parent location or parent organization.

About Organizations

Organizations are used for categorization and reporting for locations.

For example, your reporting may include a hierarchy that groups locations by a structure of parent and child organizations.

A basic Organization record shows the organization type, whether the organization is active or inactive, a description and any parent organization or location if applicable. The main attributes for organizations are managed in the Organizations portal.

About Attachments, Document Types and Documents

The Documents portal is used to track, store and manage electronic reference materials for use throughout the system. Documents are based on Document Types, which are managed under Admin to establish the types of documents or URLs that can be used by your organization. This does not limit the file type, but can be used as a categorization for your organization’s documents or URLs.

For example, document types might be used to classify the types of documents or URLs being used such as “work order doc”, “purchase order doc”, or “asset information URL” to help users find the documents they need by type. Your business process might also dictate that document descriptions include such information to help with searching for documents or URLs to attach.

Refer to About Documents (Attachments, Standard Notes and URL Attachments) in the User Guide for more information.

Attachments Portal

As you are implementing, you may also notice that the system includes an Attachment portal on the Admin menu. These are generic Oracle Utilities Application Framework attachments which supply basic attachment functionality. However, creating attachments through the Documents portal is the recommended method for adding and referencing any attachments. Refer to Attachment Overview in the Oracle Utilities Application Framework documentation for more information about Oracle Utilities Application Framework attachments.

About Documents (Attachments, Standard Notes and URL Attachments)

The Documents portal is used to track, store and manage electronic reference materials for use throughout the system. Documents are based on Document Types, which are managed under Admin to establish the types of documents or URLs that can be used by your organization. This does not limit the file type, but can be used as a categorization for your organization’s documents or URLs.

Each Document record contains information such as the document type and description. These electronic reference materials can be created as attachments/documents, standard notes or as a URL, and can be added in the Documents portal or on the Referenced Attachments section of most records.

- Attachments/Documents: General documentation such as PDFs, Word docs, spreadsheets, images, text files, and so on can be added as an attachment or document.

- URL Attachments: A URL can be added as a type of document within the system and can then be associated to records wherever it might be necessary to provide a link to additional information.

- Standard Notes: Standard notes allow you to create boilerplate text, a note, which can be attached to records wherever a note might be needed to provide additional information. Standard notes are created and modified in the Standard Notes portal.

Owned Attachments and Referenced Attachments

Most portals include an Owned Attachments zone and a Referenced Attachments zone:

- Referenced attachments are created in the Document portal and can be added to records throughout the system. If an update is made to the document in the Document portal, those changes are reflected where the document is attached. This way, the same documents can be attached on multiple records, and updates are easy to manage in one place. When you want to add a document attachment to a record, the system prompts for a Document ID because the attachment should have already been added in the Document portal.

You can also reference any Owned Attachment in the Referenced Attachments zone. For example, if you have an asset with an owned attachment, you can reference that attachment on an activity in the Referenced Attachments zone by picking the asset as the referenced record and then the asset’s attachment. This also applies for the Owned Attachments that are added to any Document record.

- Owned attachments can be added “on the fly” on a record (such as on a warranty or specification). These attachments are directly related to their record. When you add an owned attachment, the system prompts for a file upload and the attachment is added directly to that record.

An Owned Attachments zone is also included on Document records so that you can include multiple files and/or URLs to the Document record. Each of these files then applies whenever the Document record is referenced on other records throughout the system. When any one of the owned attachments on the Document record is updated in the Document portal, the changes are reflected wherever that Document record is attached.

About Service Classes

Service classes categorize activity types and indicate the type of work a shift is responsible for. Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity.

Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity.

Renewal Work

The service class includes a flag to indicate whether or not the work type is work that is completed to restore or replace an asset towards its original size, condition, or capacity. The system separately calculates costs for renewal work.

About Service Areas

Service areas define a logical boundary of your organization's territory. Every crew shift is populated with a list of service areas that the crew shift is allowed to work. This is matched up with the service area indicated on the activity to help determine which crew shift can work the activity.

About Resource Unit of Measurement

Resource units of measurement (UOM) establish the acceptable units used to quantify resources such as stock items, materials, equipment, or other used by your organization.

About Business Units

Business units are used as cost reporting entities for timekeeping expenses.

Employees are associated with a specific business unit so that when they report time charges, the costs are charged against that business unit. Your implementation will use the business unit to indicate whether to cost timesheets by employee wage rate or craft rate.

The system uses double entry accounting. For example, when time is booked against an activity, the system debits the cost centers on the activity and credits an offset account. In this case the offset account would be the payroll cost center defined on the crew member/employee's business unit.

About Employee Types and Employees

Employee types define the kinds of employees that can be defined for your organization. For example, your organization might use employee types to define regular employees, skilled employees, and novice employees.

Employee types are referenced on Employee records when they are defined.

Employees

Employee records are used to manage human resource level information for the workers within your organization.

Details such as name and personal information, work status, the main craft worked by the employee, their business unit, payroll information, hire date, and default timesheet information can be maintained. The employee record can also tie the employee to a service area where they are allowed to work as well as track training completed by the employee, assign assets (such as computer equipment or vehicles), and define the employee’s billable rate.

Employees are defined with the Employee Type, and belong to a Business Unit (which defines a Payroll Clearing Cost Center). An employee who performs work will have a Principal Craft. The Employee can be set up with effective dated Employee Billable Rates, and the Employee Training keeps a record of courses the employee has taken. Employee Unavailability is used to indicate times when the employee is not available to work, due to leave, training or other Employee Unavailability Type.

About Employees

Employee records are used to manage human resource level information for the workers within your organization.

Details such as name and personal information, work status, the main craft worked by the employee, their business unit, payroll information, hire date, and default timesheet information can be maintained. The employee record can also tie the employee to a service area where they are allowed to work as well as track training completed by the employee, assign assets (such as computer equipment or vehicles), and define the employee’s billable rate.

Employee records are not required to reference a corresponding user profile. When there is no associated user profile, the module can be used to simply store information about employees who do not use the application. Information from the employee portal can be integrated with your external human resources system.

Employee is referenced throughout the system on other records such as crews and crew shifts, contacts, direct charges, timesheets, on leave requests, to indicate which employee is responsible for or in possession of an asset, and so on. Various records can also be searched by employee.

Employee type determines the kind of employee that is being created on an Employee record.

Refer to Working with Employees for more information.

Leave Requests

Employees can request leave or it can be requested on their behalf through the Employee Unavailability portal. Refer to About Employee Unavailability for more information.

Employee Calendar

The employee calendar is available on the Employee record when the employee is assigned to at least one shift or the employee has scheduled leave.

About Employee Unavailability Types and Employee Unavailability

Employee unavailability types define kinds of situations where employees may be unavailable such as general leave, jury duty, vacation, sick leave, and so on.

Employee unavailability types are referenced on Employee Unavailability records.

Employee unavailability records establish periods of time where an employee has been given leave from his or her regular job duties. This might be due to circumstances such as vacation, sick leave, attending a training, jury duty, and so on. Logging employee unavailability allows the system to know when an employee is not available to perform work on the crews that he or she is associated with.

There are two classes of employee unavailability; leave (general leave, jury duty, vacation and sick leave) and work function (meetings and training). The base system has two employee unavailability type business objects, one for each class with the employee unavailability class defaulted in the schema. There are two corresponding employee unavailability business objects as well. Unlike leave, work function employee unavailability can have a list of employees defined on a particular employee unavailability record.

In terms of scheduling, employees indicated on the attendees list are not available as work resources. This means that during scheduling, the crafts available to the shift are reduced so that the employee on leave cannot be included. Timesheet generation is completed for the leave according to your settings and business practices.

About Employee Unavailability

Employee unavailability records establish periods of time where an employee has been given leave from his or her regular job duties. This might be due to circumstances such as vacation, sick leave, attending a training, jury duty, and so on. Logging employee unavailability allows the system to know when an employee is not available to perform work on the crews that he or she is associated with.

Employee unavailability types define the kinds of leave that might be used when creating an Employee Unavailability record.

Refer to Working with Employees for more information.

Standard approval processing facilitates approval or rejection of employee leave. After the leave is approved, employees indicated on the attendees list are not available as work resources. This means that during scheduling, the crafts available to the shift are reduced so that the employee on leave cannot be included. Timesheet generation is completed for the leave according to your settings and business practices.

About Crew Shift Types, Crew Types, Crew Shifts and Crews

Crew shift types establish the kind of crew shift such as day, night, swing, and so on.

Please note the following with respect to configuring crews and shifts:

- Crew types define the kinds of crews that can be defined for your organization. For example, your organization might use crew types to define regular crews, skilled crews, and novice crews.

- A crew is a group of workers that can be assigned to complete work. Crews are used to group workers, schedule work, and help organize work schedules.

- A crew shift is a planned period of time in which a crew (one or more workers) is scheduled to perform work. For example, a crew shift might be defined as Crew A, consisting of Jack and his van, working on a specific date from 9 am – 5 pm.

- Crew shifts are associated with a crew shift type, that defines attributes common to all crew shifts of that type, including whether the shift is daily or weekly. For example, night shifts would have a different start time and duration than morning shifts, so they would have different shift types.

- Once a crew is created, shifts can be generated. Work order labor requirements can be assigned to the crew shift, and to a particular individual on the crew.

- Shift plan templates are used to automatically generate crew shifts based on a set of pre-defined shift criteria such as the shift type, the shift rotation, the defined calendar, and so on.

- Schedule Plan is a container for many daily schedules.

- Schedule Period defines if the crew shift type is a daily schedule or a weekly based planned schedule.

- Daily crew shift type determines whether crews receive extra pay (and the amount) when working such a shift.

About Crews

A crew is a group of workers that can be assigned to complete work. Crews are used to group workers, schedule work, and help organize work schedules.

Once a crew is created, shifts can be generated. Work order labor requirements can be assigned to the crew shift, and to a particular individual on the crew.

Note that an employee can be assigned to more than one crew.

About Crafts, Equipment and Miscellaneous Resources

Crafts define a skill or work specialty for crew members such as mechanic, electrician, plumber, arborist, and so on.

When crafts are defined, a secondary craft can be added as part of the craft definition. Secondary crafts are regarded as additional or complementary skills to the primary craft.

Equipment is defined by your organization to be referenced as a resource type available for use to complete work. This might include machinery, tools or other equipment required to work activities (crane, bulldozer, drill, etc.).

Other resources are defined by your organization to be referenced as a resource type available for use to complete work.

Crafts, equipment and miscellaneous resources are referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity.

When defining stock items, crafts, equipment and miscellaneous resources, there is an option, Default Values to Activity, to define whether or not the information should be defaulted onto activities when resource requirements reference the resource.

About Crafts

Crafts define a skill or work specialty for crew members such as mechanic, electrician, plumber, arborist, and so on.

When crafts are defined, a secondary craft can be added as part of the craft definition. Secondary crafts are regarded as additional or complementary skills to the primary craft.

Every employee, i.e. crew member, is defined with a principal craft. The principal craft is used when scheduling activity labor requirements to shifts. Secondary crafts are also used during scheduling and appear as less important capacities to schedule. The secondary crafts are presented as available crafts during scheduling.

Likewise, a default set of crafts can be defined in the Crew Type Labor Profile zone at the crew type level. Crafts listed in this zone supersede the crafts defined for employees listed on the crew shift and total available hours for a particular craft is multiplied by the number of people.

Crafts, equipment and miscellaneous resources are referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity.

About Equipment

Equipment is defined by your organization to be referenced as a resource type available for use to complete work. This might include machinery, tools or other equipment required to work activities (crane, bulldozer, drill, etc.).

Crafts, equipment and miscellaneous resources are referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity.

About Miscellaneous Resources

Other resources are defined by your organization to be referenced as a resource type available for use to complete work.

Crafts, equipment and miscellaneous resources are referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity.

About Shift Plan Templates

Shift plan templates are used to automatically generate crew shifts based on a set of pre-defined shift criteria such as the shift type, the shift rotation, the defined calendar, and so on.

Templates can be created as basic common templates for multiple crews, basic templates for a specific crew or templates that crews are subscribed to:

- Common templates: Common templates establish an initial date for rotations to start, number of weeks for rotation, work calendar and the type of schedule plan. These templates do not specify details such as the specific crew. Since they do not specify the crew, common templates cannot be directly used to generate shifts. Shifts are actually generated from the subscription template that references the common template. If a common template is changed after shifts have been generated, the changes are not reflected until the next time batch processing runs. You can apply changes to the specific crew shift manually.
The initial rotation date ensures that all generated shifts for crews subscribing to the template are at the same rotation position regardless of when the crew subscribed to the template. Rotation is calculated based on the common initial rotation date and not the subscription effective date.

For example, if a common template has a 2 week rotation where on the first week the crew works on Monday but on the second week the crew works on Tuesday. If one crew subscribes to this template just prior to the first week and another subscribes just toward the end of the first week, then for the first crew the first generated shifts is a Monday whereas the second crew’s first generated shift is a Tuesday.

- Subscription templates: Subscription templates are used to subscribe a particular crew to a common shift plan template. They define an effective period to which shifts for the crew can be generated based on the details on the common template.

- Crew templates: Crew templates establish an effective and expiration date, a number of rotation weeks, work calendar and the shift plan type for a specific crew.

Daily vs. Weekly Templates

The shift plan type defined on common templates and crew templates, designate whether the template is for daily or weekly shifts. The type also defines the details for those shifts such as the daily start and end times for daily shifts, or the schedule period for weekly shifts. Weekly crew shifts represent a set of daily shifts, typically with one crew shift template per day of the week. A weekly template can map crew templates for rotating cycles of one or many weeks. This is used to account for shift variations across multiple week cycles.

Configuring Resource Management

This section provides configuration tasks for resource management administrative support records.

Refer to the Resources section in the Business User Guide for a conceptual overview of resource functionality.

Refer to the Understanding Resource Management Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Resource Unit of Measurements (UOM)

Navigate to the Unit of Measure — Resource portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Organization Types

Navigate to the Organization Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining an Organization

Navigate to the Organization portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining Service Classes

Navigate to the Service Class portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Service Areas

Navigate to the Service Area portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Document Types

Navigate to the Document Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining a Document

Use this procedure to create an attachment, standard note or URL in the Document portal for general access from within the application.

- Defining a Common Attachment from the Attachment Portal

Use this procedure to create an attachment from the Attachment portal for general access from within the application. Use Documents if the attachment needs to apply to many records throughout the system.

- Defining Business Units

Navigate to the Business Unit portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Employee Types

Navigate to the Employee Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining an Employee

Navigate to the Employee portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining Employee Unavailability Types

Navigate to the Employee Unavailability Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Equipment

Navigate to the Equipment portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining a Miscellaneous Resource

Navigate to the Miscellaneous Resources portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining a Craft

Navigate to the Craft portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining an Hourly Rate to a Craft

Use this procedure to add an hourly rate to a craft.

- Defining a Secondary Craft

Use this procedure to define a secondary craft.

- Defining a Crew Type

Navigate to the Crew Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining a Crew

Navigate to the Crew portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

- Defining a Crew Shift Type

Navigate to the Crew Shift Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining a Shift Plan Template

Navigate to the Shift Plan Template portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Defining Resource Unit of Measurements (UOM)

Navigate to the Unit of Measure — Resource portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Organization Types

Navigate to the Organization Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

You might define an organization type as a child organization type. In this case, the parent organization needs to be defined first.

Organization types are referenced when creating organizations.

Defining an Organization

Navigate to the Organization portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the organization record:

Note: This list does not represent required fields.

- Organization Type

- Parent Organization (as applicable)

Defining Service Classes

Navigate to the Service Class portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Service Areas

Navigate to the Service Area portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Document Types

Navigate to the Document Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining a Document

Use this procedure to create an attachment, standard note or URL in the Document portal for general access from within the application.

1. Navigate to the Document portal under Resource Management and select Add.

2. Complete the fields according to your business practices, and save.

The system navigates back to the main portal where you can upload the file as a separate step.

3. Browse to and select the file and click Upload.

If you are adding a URL reference, you can cancel this step. When the Document record that you created opens, enter the URL in the Owned Attachments section.

Defining a Common Attachment from the Attachment Portal

Use this procedure to create an attachment from the Attachment portal for general access from within the application. Use Documents if the attachment needs to apply to many records throughout the system.

1. Navigate to the Attachments portal in edit mode.

2. Choose the attachment format by selecting from the Attachment Business Object field and click Ok.

This allows you to indicate whether the attachment is a spreadsheet, an image, video or audio, a text document, or any other file type available.

3. Enter the file name and click Save.

The system navigates back to the main portal where you can upload the attachment file as a separate step.

4. Click the Upload button.

5. Browse to the attachment file and click Upload.

Make sure that you select a file with the same file type that you selected when you initially created the attachment.

Defining Business Units

Navigate to the Business Unit portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the business unit record:

Note: This list does not represent required fields.

- Payroll Cost Center

Note that the business unit is used to indicate whether to cost timesheets by employee wage rate or craft rate.

Defining Employee Types

Navigate to the Employee Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

An employee type is referenced when creating an employee.

Defining an Employee

Navigate to the Employee portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the employee record:

Note: This list does not represent required fields.

- Employee Type

- User ID

- Craft

- Business Unit

- Service Area

In order for the employee to charge timesheets in the system, he or she must have a billable rate added to his or her Employee record.

Note that “secondary crafts” or additional skills for a craft are defined on the craft. Any primary craft that is attributed to the employee will also attribute the secondary crafts for that primary craft.

Defining Employee Unavailability Types

Navigate to the Employee Unavailability Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the employee unavailability type record:

Note: This list does not represent required fields.

- Cost Center

- Expense Code

An employee unavailability type is referenced when entering employee unavailability.

Employee unavailability is typically created for leave time or for work functions such as training or meetings. When you create the employee unavailability type, this is specified by the business object that is selected on the initial screen.

Defining Equipment

Navigate to the Equipment portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the equipment record:

Note: This list does not represent required fields.

- Resource UOM — Non material class

- Cost Center — Typically should be of the type that does not allow user charges. However this option can be allowed or disallowed.

- Expense Code

Defining a Miscellaneous Resource

Navigate to the Miscellaneous Resources portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the miscellaneous resources record:

Note: This list does not represent required fields.

- Resource UOM — Non material class

- Cost Center — Typically should be of the type that does not allow user charges. However this option can be allowed or disallowed.

- Expense Code

Defining a Craft

Navigate to the Craft portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the craft record:

Note: This list does not represent required fields.

- Resource UOM

- Expense Code

Ensure that you Activate the craft after it is created so that it is available to be added to other records. You can also enter the hourly rate for the craft after it is created.

Defining an Hourly Rate to a Craft

Use this procedure to add an hourly rate to a craft.

1. Search for and select the appropriate Craft record.

2. Navigate to the Hourly Rate section and select the Add link.

3. Enter an Effective Date and the Hourly Rate and Save.

Defining a Secondary Craft

Use this procedure to define a secondary craft.

Prerequisites:

Crafts are considered as “skills” of a worker. You might define a secondary craft that would act as backup or which would be scheduled in cases where the primary craft is not available.

1. Search for and select the appropriate Craft record.

2. Click the Edit button.

3. Navigate to the Secondary Crafts section and enter or search for and select the secondary craft ID.

4. Save.

Defining a Crew Type

Navigate to the Crew Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining a Crew

Navigate to the Crew portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the crew record:

Note: This list does not represent required fields.

- Crew Type — Defines the default planning horizon days for the crew.

- Employee ID

Defining a Crew Shift Type

Navigate to the Crew Shift Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining a Shift Plan Template

Navigate to the Shift Plan Template portal under Resource Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the shift plan template record:

Note: This list does not represent required fields.

- Crew

- Schedule Plan Type

- Work Calendar

Work Management Options

The following sections provide information on concepts related to managing work including work requests, work orders, activities , and so on.

Next in This Section

- Understanding Work Management Configuration

This section provides guidelines for configuring work management functionality.

- Configuring Work Management

This section provides configuration tasks for work management administrative support records.

Understanding Work Management Configuration

This section provides guidelines for configuring work management functionality.

Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked.

Please refer to the Work Management section in the Business User Guide for a conceptual overview of work management functionality.

Master Configuration

Ensure that you create master configuration settings in Work Management Master Configuration.

Next in This Section

- About Planners and Maintenance Managers

Planners and maintenance managers are defined for your organization as personnel authorized to perform certain functions or who are responsible for overseeing specific work. For example, planners are usually responsible for planning work and materials for assets. Maintenance managers are typically more specifically involved with an aspect of work such as managing hazardous materials or specialized equipment. The usage of these roles depends entirely upon your business practices.

- About Activity Types and Activities

Activity types define the main attributes for activities of a certain type and act as a model and template for Activity records.

- About Work Priority and Criticality Fields

Work priority and criticality custom lookups require special configuration since they can be searched by range and by greater than and/or less than values.

- About Checklist Types

Checklist Types define a set of criteria and steps that workers should complete as part of a work activity. Checklists can include optional and mandatory steps. Steps marked as mandatory will require the user to select a radio button to complete the step.

- About Completion Events

Completion events are used to execute business events within the application. For example, completion events may be configured for several types of asset processing such as asset update, state transition, replication, service history and activity creation.

- About Completion Event Types

Completion event types are used to define completion events of a particular type.

- About Inbound Communications

The Inbound Communication portal provides details related to the information received from an external system such as Oracle Utilities Mobile Workforce Management. Use inbound communication to create a completion event using information defined within the raw message coming from an external system.

- About Projects and Subprojects

Projects provide a way to group work so that it can be planned and charged against large efforts. Typically, a project will be a task that is out of the ordinary, or that requires extra planning and resources. Examples would be adding new facilities or conducting a major overhaul of an assembly line.

- About Timekeeping

Timesheets are used to record the amount of time that workers (labor resources) spend on activities or work orders. Once charges are entered, processing allows employees to receive proper compensation for their work and labor charges are applied to the appropriate cost buckets.

About Planners and Maintenance Managers

Planners and maintenance managers are defined for your organization as personnel authorized to perform certain functions or who are responsible for overseeing specific work. For example, planners are usually responsible for planning work and materials for assets. Maintenance managers are typically more specifically involved with an aspect of work such as managing hazardous materials or specialized equipment. The usage of these roles depends entirely upon your business practices.

Every planner and maintenance manager references the User ID of the assigned person. Work statistics on the Home Page can be configured to display by planner or by maintenance manager.

About Activity Types and Activities

Activity types define the main attributes for activities of a certain type and act as a model and template for Activity records.

The activity type specifies the applicable service class, scheduling information as applicable, default requirements, how to handle errors or exceptions, and completion details for activities of the type. The Service History Type linked to the Activity Type acts as the ‘default’ for creating Service History records as a result of an Activity. Users can specify on an activity or template activity whether a service history for a specific service history type should be mandatory or optional. If set as mandatory, the service history would need to be completed before the activity or template activity can be closed. This is used when reviewing an asset’s service history for preventive maintenance purposes.

Identifier fields on an activity type define additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria.

An activity is a task which needs to be completed. Activities manage asset changes, work, inspections maintenance and other actions that are performed on assets or components.

Each activity on a work order is defined with one or more “resource requirements” which define resources that are needed to perform the activity. Typically planned work orders specify resource requirements on the related activities, and approvers can verify the requirements before the work order is approved. Requirements may be categorized as materials, labor, equipment or other. Refer to About Activity Resource Requirements for more information.

Cost Tracking

Cost tracking is enabled, as default, for all work activities. For field activities (activities sent to an external system), the option to track costs can be enabled or disabled on each activity type. To configure the default for this setting, use the Schema Constants Feature Configuration.

Note: For Oracle Utilities Operational Device Management users also using Oracle Utilities Work and Asset Management: Activity types are delivered in ODM with the cost tracking default set to No on all ODM activity types.

Capital Work

Work orders that are worked by outside contractors are considered “capital work”. If your implementation will use contractors to complete activities, ensure that you configure:

- a work category of “capital”

- external system to the contractor

- outbound activity type with the external system set and at least one required service history completion event type

About Work Priority and Criticality Fields

Work priority and criticality custom lookups require special configuration since they can be searched by range and by greater than and/or less than values.

The system will multiply location criticality by activity work priority to derive a usable total risk value.

To this end, you must configure these lookups, WORK_PRIORITY and CRITICALITY, with the following considerations:

- The Field Value or code must be a 2-digit number.
This is required even if your codes do not exceed 09. They must be 2 digits for sorting to function properly.

- The description of the value must have the same two digits at the beginning. Since lookup values show up as drop-downs and drop-down values are sorted by description, starting the description with the code will ensure proper sorting.

Refer to the demo environment and navigate to these lookups to review the demo example.

About Checklist Types

Checklist Types define a set of criteria and steps that workers should complete as part of a work activity. Checklists can include optional and mandatory steps. Steps marked as mandatory will require the user to select a radio button to complete the step.

Checklist types specify the checklist business object, whether printing is enabled, default requirements, and any processing constraints.

Note: If printing is enabled, activity with the checklist is able to be printed.

About Completion Events

Completion events are used to execute business events within the application. For example, completion events may be configured for several types of asset processing such as asset update, state transition, replication, service history and activity creation.

All activities have a set of required and optional completion events that can be executed to see the activity to completion.

The Relationship Information section shows any other system objects that are associated to the completed object. For example, if you are looking at the completion event for an activity, the relationship information shows the asset, any components, the location, service history, etc.

Completion Event Common Attachments

Attachments added here are used as part of the completion event processing. For example, a completion event may be used to update a picture or other supporting file about an asset.

About Completion Event Types

Completion event types are used to define completion events of a particular type.

For example, completion event types might be configured for several types of asset processing such as asset installation, asset removal, replication, service history creation, and activity creation.

Completion event types are referenced on activity types to indicate which completion events should be included as part of the lifecycle of activities of that type. As examples, this can affect when service history is created for an activity, and the disposition of the assets on an activity as the activity is processed.

Note that if you add activity types to the completion event type, you cannot set whether or not the completion event type is required for the activity type. Add the completion event type to the activity type using the Activity Type portal to also set the completion event types as optional or required.

Also note that the setting of the Default Event Date Time field on completion event types controls whether or not the completion event can be created automatically without user input. Valid options include:

- Default: When this field is set to Default, the system can automatically create the completion event of this type without any user input. This should only be used for completion events which create a generic object. The system uses the current date and time when the completion event is being created.

- Do Not Default: If this field is set to Do Not Default, the system prompts for the date and additional information during the creation of the completion event. For example, to create an Install Asset completion event, this must be set to Do Not Default so that the exact install date and time and asset ID of the asset being installed can be entered.

The base package completion event type business objects can be used out of the box, however, it is likely that your implementation will want to configure special business objects to capture specific system events.

It is also important to note where there are optional completion event types might need to be used to capture incidental or unexpected events such as:

- Create follow-up activity

- Create service history

- Create attachment (asset and/or location)

Your implementation may want to carefully consider these types of events and possibly add them as optional on every completion event type where they might be needed.

About Inbound Communications

The Inbound Communication portal provides details related to the information received from an external system such as Oracle Utilities Mobile Workforce Management. Use inbound communication to create a completion event using information defined within the raw message coming from an external system.

Inbound communication events receive completion event information from the external system and then process the necessary transactions to see the activity or other event to completion.

Inbound Communication Configuration Notes

An inbound communication business object must be created for each type of message to be received from an external system. For most external systems, this is based on the types of messages the system is designed to send.

You must also create an XAI Inbound Service for each type of message to be received from an external system. XAI inbound services define the details of how messages are received from an external system, including the inbound communication business object (or business service or service script) to be invoked when the response message is received. As in the case of inbound communication business objects, the set of XAI inbound services you need to create is based on the types of messages the system is designed to send.

About Projects and Subprojects

Projects provide a way to group work so that it can be planned and charged against large efforts. Typically, a project will be a task that is out of the ordinary, or that requires extra planning and resources. Examples would be adding new facilities or conducting a major overhaul of an assembly line.

Projects in Context

Please note the following with respect to using projects in your implementation:

- Projects can be linked to many of the transactional records in the system. This is primarily used for cost reporting. They can be linked to many cost centers.

- Projects can be organized into a hierarchical structure.

- Projects can be configured to require approval processing.

- Key data components on a project include the estimated and actual start/end dates, budgeted and actual amounts, and the project supervisor.

Project Categories

Your organization can define project categories to create classifications for projects such as maintenance, capital, construction, and so on.

About Timekeeping

Timesheets are used to record the amount of time that workers (labor resources) spend on activities or work orders. Once charges are entered, processing allows employees to receive proper compensation for their work and labor charges are applied to the appropriate cost buckets.

Please note the following with respect to using timekeeping in your implementation:

Costing for timesheets is defined on business units. The business unit includes a Labor Cost Source field which specifies whether the system should use the billable rate on the employee record or the unit rate on the specified craft when calculating time based cost. Each employee is then assigned to a business unit, and the system uses this association to determine costing when the employee charges time.

Master Configuration

Your organization must configure the Allow Timesheet Against Completed Activity parameter in the Work Management Master Configuration to determine if timesheet creation is allowed on activities that have already reached completed status.

Time Periods

Your organization must create time periods to define valid from and to dates for labor costing and timesheet reporting. Time periods have to be distinct and cannot overlap. When a new timesheet is created, the system defaults to the current time period.

Labor Earning Types

Labor earning types define earnings codes for your organization which includes an adder and a multipler to calculate labor costs.

Overtime Types

Overtime types define overtime codes for your organization which includes a multiplier to calculate the premium rate that workers earn for overtime.

Deferred Monitor

Once a timesheet is approved, user will need to run batch job Monitor Move Timesheet to Next Default Status to transition the timesheet to Posted status. The Timesheet will transition all the Timesheet Details in the initial state to Posted and when all the non cancelled timesheet detail records have been posted and the timesheet’s time period end date is less than current date. Reason for this is that we don’t want to post future timesheet detail records and we shouldn’t show the timesheet as posted until all the timesheet detail records for the timesheet have been posted.

Configuring Work Management

This section provides configuration tasks for work management administrative support records.

Refer to the Work Management section in the Business User Guide for a conceptual overview of work management functionality.

Refer to the Understanding Work Management Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Maintenance Managers

Navigate to the Maintenance Manager portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Planners

Navigate to the Planner portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Activity Types

Navigate to the Activity Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Checklist Types

Navigate to the Checklist Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Adding a Checklist Type for a Template Activity

This section describes a basic procedure for automatically generating checklists for a work activity created from a template activity.

- Defining Completion Event Types

Navigate to the Completion Event Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Time Periods

Navigate to the Time Period portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Labor Earning Types

Navigate to the Labor Earning Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Overtime Types

Navigate to the Overtime Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Project Categories

Navigate to the Project Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

Defining Maintenance Managers

Navigate to the Maintenance Manager portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the maintenance manager record:

Note: This list does not represent required fields.

- User ID

Defining Planners

Navigate to the Planner portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the planner record:

Note: This list does not represent required fields.

- User ID

Defining Activity Types

Navigate to the Activity Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the activity type record:

Note: This list does not represent required fields.

- Service Class

- Completion Event Type (should be configured for the specific type of activity)

Defining Checklist Types

Navigate to the Checklist Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites:

Adding a Checklist Type for a Template Activity

This section describes a basic procedure for automatically generating checklists for a work activity created from a template activity.

Prerequisites:

- Checklist Type

1. Navigate to the Work Order Template portal under Work Management and select Add.

2. Fill in the required information for a work order template and an activity template.

3. Add a Checklist Type to the activity template.

4. The Checklist Type appears on the activity template in the Checklist Types zone.

Defining Completion Event Types

Navigate to the Completion Event Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the completion event type record:

Note: This list does not represent required fields.

- Activity Type

Defining Time Periods

Navigate to the Time Period portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Labor Earning Types

Navigate to the Labor Earning Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Overtime Types

Navigate to the Overtime Type portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Project Categories

Navigate to the Project Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

The project category is referenced when creating project.

Construction Work Management Options

The following sections provide information on configuring for construction work management functionality.

Next in This Section

- Understanding Construction Work Management Configuration

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

- Configuring Construction Work Management

This section provides configuration tasks for construction work management administrative support records.

Understanding Construction Work Management Configuration

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

In a standard workflow, an organization configures compatible units based on the materials, labor and equipment needed to install (construct) or remove (demolish or retire) an asset at a given location. Compatible units are classified as Base, Functional, or Accessory depending on how they are to be used and what they define. They are grouped into CU Sets according to their equipment group and size (every CU must belong to a set (only one).

Next, work designs are created to estimate the construction work with all of the materials, labor, equipment and any other costs associated to the work. Compatible units are usually utilized on the design to define these requirements. Multiple design versions can be created so as to compare cost estimates and resource requirements.

Once ready, work designs can be submitted for standard approval processing. After approval, the work design can be transitioned to a “work generated” status and construction work orders and construction work activities can be created from the work design to plan and manage the work. Additional construction work activities can be created on that construction work order or an existing construction work order that has not been associated to any work design as long as the work order is in a non-final state. Existing construction work activities that have been associated to the work design can also be updated from the work design. Costs and scheduling are managed just as they are for regular work.

In the context of Construction Work Management, the term ‘asset’ is used to refer to fixed assets, also called capital assets by some. Not all fixed assets are Oracle Utilities Work and Asset Management assets, i.e. a record in the asset table with an asset ID. For example, you may not track wires as individual asset within Oracle Utilities Work and Asset Management. Whether a Oracle Utilities Work and Asset Management asset should also be created as a result of a construction work is determined by the presence/lack of Oracle Utilities Work and Asset Management asset type on the CU definition.

Please refer to the Construction Work Management section in the Business User Guide for a conceptual overview of construction work management functionality. You can also refer to the Construction Work Management Processing Examples section for configuration examples.

Next in This Section

- About Construction Work Management Configuration

- About Compatible Units (CU)

Compatible Units define the materials, labor, and equipment necessary to install or remove assets in relationship to construction work. Compatible units can be referenced by other compatible units to build more complex configurations and allow users to properly group resources together.

About Construction Work Management Configuration

Configuring for this functionality involves setting up the construction work management specific objects discussed in this section.

Refer to Construction Work Management Control Data Setup for the setup sequence and prerequisites.

Property Units

Property units group capital/fixed assets that have similar depreciation characteristics. Depreciation is currently not managed within WAM. WAM can interface fixed assets, e.g. Property Unit, Quantity, In Service Date, Value and etc, to an external Fixed Asset Management system.

CU Category

CU Category provides a categorization for compatible units.

Every CU Category must belong to a CU Class. A CU Category can be referenced by one or many CU Equipment Groups (e.g. Pipes, Poles, or Wires).

Equipment Groups

Equipment groups categorize CU Sets. Every CU Set must reference a single equipment group, however an equipment group can have many CU Sets.

Every equipment group has a single CU Category, but a CU category can have many equipment groups.

CU Usage

Defines usage categories for compatible units. When planners add compatible unit(s) to a Work Design or Construction Work Order, they can choose a CU Usage, which filters the cost centers to use for the CU. For each usage you specify the cost center that is specific for that usage.

Overhead

Overhead defines how to apply expenses against work designs and construction work orders.

There are two classes of overhead, Direct Overhead and Indirect Overhead. Direct Overhead refers to cost charged to a general Construction Overhead activity. For example, a Construction Work Order could have many actual construction work activities, but only one construction overhead activity for people to book the time they spend designing the entire construction project. Direct Overhead cost is distributed among those actual construction activities when they close.

Indirect Overhead refers to cost that’s not tracked within WAM, but should be considered as part of the capital expenditure. For example, some construction work is funded by loan and/or bond, which have cost of their own. Indirect Overheads are applied as a percentage of the actual cost of the construction activities.

Master Data Objects

In addition to configuring admin objects, you will need to set up transactional objects accessed on the Construction Work Management menu.

Refer to the Construction Work Management Master Data Setup section as well as the corresponding business user guide sections to learn more about these objects.

Additional Objects to Configure

To use construction work management functionality, the following additional system elements must also be set up with construction work specific elements.

Master Configuration

Ensure that you create master configuration settings in Work Management Master Configuration.

Service Class

Every construction work activity must reference a service class to identify whether or not the activity is overhead or an activity used for construction, renewal or maintenance. Part of the service class is to define the construction work in progress (WIP) cost center on the activity. Service class is defaulted from the construction work activity type.

Construction Work Activity Types

Construction work activity types define the main attributes for scheduled activities of a certain type.

Vendor

You must define contractors as vendor locations in order to create contractor bids.

When creating contractor related vendor locations, ensure that the Contractor field is set to Yes.

CU Materials (Stock Items, Crafts, Equipment, and Misc Resources)

Create the stock items, crafts and equipment that will be referenced as materials on compatible units.

Capital Spare items are identified during accept and return as fixed assets so that an external Fixed Asset Management system can maintain their depreciation. A property unit is required on capital spare items.

Crew Type

Design specific crew types for construction work. On the crew type you can add a list of crafts and a list of equipment to each crew type to indicate the number and type of each resource that are available for the crew type. This is not required, but can help to more easily identify the craft and equipment related to crew types. If crafts and equipment are defined on a Crew Type, users can easily add those craft(s) and equipment(s) onto a design through the Crew Type.

Asset

A property unit must be added to tracked and in/out service assets that will be referenced for compatible unit processing. Pre-capitalized assets reference the stock item’s property unit when they are accepted at receipt. Constructed assets reference the compatible unit stock item property unit when the asset is created during construction processing. When either of these kinds of assets are retired the fixed extract batch retrieves those retired assets via their property unit.

GIS

The GIS Map Viewer within WAM, when configured, is leveraged within the construction work management process in two important ways:

- A Design Element for a Work Design can be created through the GIS Map Viewer by clicking on the “Add Design Element (Map)” button in the Record Actions section of the Work Design. This will launch the GIS map where you can drop a pin on the map then follow on by clicking the “Create Design Element” button in the dashboard for the GIS Map Viewer. This will create a Design Element for that exact work location.

- Once construction work orders and work activities have been created then these can also be viewed through the GIS Map Viewer along with any other kind of work activity.

Documents and Notes

As needed, create notes and documents to provide additional information on any construction work management object.

About Compatible Units (CU)

Compatible Units define the materials, labor, and equipment necessary to install or remove assets in relationship to construction work. Compatible units can be referenced by other compatible units to build more complex configurations and allow users to properly group resources together.

The Compatible Unit Type determines how a compatible unit can be used:

- Compatible Unit Base: A simple compatible unit only consists of materials and serves as a building block for function compatible units. They cannot be selected directly on a work design and do not reference a property unit. Base compatible units are meant to model basic stock items used to build up a functional or accessory compatible unit. Changes to the stock item will be reflected on the compatible unit.

- Compatible Unit Function: The primary compatible unit which is added on work designs. Functional compatible units can have materials, labor and equipment and require a function to install or remove the compatible unit. They can also be defined with a condition and property unit. Functional compatible units are intended to model an asset (such as a pole) and do create fixed or physical assets.

- Compatible Unit Accessory: This CU is meant to be used in conjunction with other CUs and is not meant to be capitalized. An accessory can be directly selected on a work design and can be designated with a function and condition, but not a property unit. Accessory compatible units are meant to model optional asset accessories that can be added onto a work design to accompany the build out of an asset but which don’t directly contribute to the asset as a whole. A CU Accessory can also inherit from a Base CU if there is a desire to abstract the stock items in the Base CU from the various ways the CU can function as a CU Accessory. Note that CU Accessories do not create fixed or physical assets.

Function al and Accessory compatible units are primarily used in two ways:

- On a work design to determine a quote, and perhaps pick between various design options,

- On a construction work order to initially populate the planned estimates and to drive the assets that will be created.

The accounting information on the compatible unit is used during the construction reconciliation process to produce the true cost of the new asset as well as the appropriate accounting codes.

About CU Sets

CU Sets group related compatible units, usually by factors such as equipment group and size. Every compatible unit must belong to only one CU Set.

The main goal of a CU Set configuration is to make it easy to add CUs to work designs by these groupings. A best practice is to ensure that a CU Set is defined for every equipment group and size combination, and to ensure that a set includes the Functional CUs and Accessory CUs together. This will ease the selection of CUs when creating a work design or construction work order.

About CU Contractor Bids

CU Contractor bids define the details of a contractor’s proposal to perform the work for a particular Compatible Unit on a construction project.

Contractors must be defined in the system by a vendor location. Bids can only be added to functional or accessory compatible units and they may or may not include materials. Bids have both an effective date and an expiration date.

Activating the bid will ensure that it can be included on the construction work activity where the compatible unit is referenced.

Configuring Construction Work Management

This section provides configuration tasks for construction work management administrative support records.

Please refer to the Construction Work Management section in the Business User Guide for a conceptual overview of construction work management functionality.

Refer to the Understanding Construction Work Management Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Property Units

Navigate to the Property Unit portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining a Compatible Unit Set

Navigate to the CU Set portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

- Defining a Compatible Unit

Navigate to the Compatible Unit portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

- Defining a CU Contractor Bid

Navigate to the CU Contractor Bid portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

- Defining a CU Category

Navigate to the CU Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Equipment Groups

Navigate to the Equipment Group portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining CU Usage

Navigate to the CU Usage portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Overhead

Navigate to the Overhead portal under Admin, select Add, complete the required fields according to your business practices and Save.

Defining Property Units

Navigate to the Property Unit portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining a Compatible Unit Set

Navigate to the CU Set portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the compatible unit set record:

Note: This list does not necessarily represent required fields.

- CU Category

- Equipment Group

Once the CU Set is defined, compatible units can be added to it.

Defining a Compatible Unit

Navigate to the Compatible Unit portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

You can also add Compatible Units via the Add link on the related CU Set.

Prerequisites: The following are referenced by the compatible unit set record:

Note: This list does not necessarily represent required fields.

- CU Set

- Property Unit (for constructed asset)

- Asset Type (for constructed asset)

After creating compatible units, you add materials, labor and equipment requirements as well as contractor bids.

Defining a CU Contractor Bid

Navigate to the CU Contractor Bid portal under Construction Work Management, select Add, complete the required fields according to your business practices and Save.

You can also add a CU Contractor Bid via the Add link on the related Compatible Unit .

Prerequisites: The following are referenced by the cu contractor bid record:

Note: This list does not necessarily represent required fields.

- Vendor Location

- Compatible Unit

Defining a CU Category

Navigate to the CU Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: CU Class (custom lookup)

Defining Equipment Groups

Navigate to the Equipment Group portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: CU Category

Defining CU Usage

Navigate to the CU Usage portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: Cost Center (capital account)

Defining Overhead

Navigate to the Overhead portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites:

It is not required to have different resource types for each indirect overhead.

- Other Resource Type used to apply indirect overhead on Material cost.

- Other Resource Type used to apply indirect overhead on Labor cost.

- Other Resource Type used to apply indirect overhead on Equipment cost.

- Other Resource Type used to apply indirect overhead on Other cost.

- Other Resource Type used to apply additional overhead cost.
This is typically for additional overhead cost not related to any particular resource class. For example, cost associated with a loan or bond used to fund the construction project. This resource type typically is different from those for each resource class, e.g. Material or Labor.

Preventive Maintenance Options

The following sections provide information on configuring for preventive maintenance functionality.

Next in This Section

- Understanding Preventive Maintenance Configuration

This section provides configuration guidelines for preventive maintenance functionality.

Understanding Preventive Maintenance Configuration

This section provides configuration guidelines for preventive maintenance functionality.

Refer to the Preventive Maintenance section in the Business User Guide for a conceptual overview of preventive maintenance functionality.

Next in This Section

- About Preventive Maintenance Configuration

Preventive maintenance helps manage the creation of work activities to maintain assets as per defined calendars and schedules.

About Preventive Maintenance Configuration

Preventive maintenance helps manage the creation of work activities to maintain assets as per defined calendars and schedules.

About Preventive Maintenance

Preventive maintenance can help your organization manage costs by reducing downtime due to unexpected asset failures, reducing incidents where maintenance is needed in response to a problem (reactive maintenance), and ensuring the proper care and maintenance of assets. One common example of preventive maintenance is routine maintenance on a pump. It is clear that proper maintenance depends on timely visual inspections and regular cleaning to prevent costly problems, failures and repairs. Preventive maintenance programs are based on time or operational usage. Template work orders are set up to plan detailed work requirements, and the preventive maintenance functionality manages when and how the related work orders are automatically created based on the established preventive maintenance cycles. The system supports scheduled preventive maintenance and event based maintenance.

About Event Based Maintenance

Event based maintenance is work that is performed based on trigger dates. Events differ from maintenance schedules because the system does not manage when to cycle the work. Instead, planners decide upon the next schedule date for the event and enter it on the Maintenance Event record. Work performed can include inspections, repairs, replacements, and so on, but it is typically associated to planned outages or other event based maintenance. Work records are generated on the trigger date based on the indicated defaults and templates.

Configuration Guidelines

Set up preventative maintenance for your assets by completing the following general steps:

1. Decide on the type of maintenance schedule needed for the asset:

Preventive Maintenance

- A Maintenance Schedule is associated with an Asset Type and provides a series of pre-defined Maintenance Triggers which define when to perform specific activities on the asset to ensure its continued operation.

- There are four methods of calculating the maintenance schedule, as defined by the Trigger Type — calendar anniversary, calendar interval, runtime anniversary and runtime interval. The triggers are defined in terms of either time duration (for calendar-based methods) or runtime values.

Refer to About Preventive Maintenance Triggers for more on maintenance triggers.

- Assets inherit their maintenance schedule from their specification. One specification can be linked to multiple maintenance schedules: one for each applicable asset situation. For example, you might configure a maintenance schedule for “in Service” and another for “in Stores”.

- See additional notes below if failure conditions need to be considered for the asset. Failure profile is defined on the Asset Type.

Event Based Maintenance

Instead of using scheduled preventive maintenance, you might find that event based maintenance is more appropriate for the asset. Event based maintenance is typically used to execute planned outages.

- Maintenance plan triggers are used to configure a specific work order for a particular location for use by a maintenance event. They define the maintenance plan, template work order, activity type, service history type, work order defaults and asset location for the work being created for the maintenance event, as applicable. The work order template indicated on the trigger defines the pre-planned requirements for the work that is created for the event. The trigger location can either be defined on the work order template specified, or on the trigger itself. Specifying an asset location on the trigger allows for the reuse of a common work order template.

2. Plan for the preventive or event based maintenance work by setting up a template work order.

3. Schedule the work plan:

- Preventive Maintenance Set up a maintenance schedule and maintenance triggers.

- Event Based Maintenance Set up a maintenance plan and maintenance triggers.

4. Trigger, execute and closeout the work.
Preventive Maintenance

- Monitor algorithms generate Asset Maintenance Trigger Forecast records with the date at which the asset is due for the preventive maintenance.

- The trigger creates the preventive maintenance work order and activity, (using the template work order) which then becomes part of the asset’s service history.

- The forecast is based on the horizon days set on the asset monitor.

- Forecast information is displayed on the Asset Maintenance Trigger Forecast zone in Asset portal.

Event Based Maintenance

- Planners decide upon the next schedule date then create or modify Maintenance Event records.

5. Evaluate results and plan effectiveness then modify the maintenance work plans as needed.

About Failure Mitigation

Failure profiles group failure types, failure modes, failure repairs, and failure components into a profile which can be attached to an asset type to define valid failure information for assets of that type. Effective use of failure profiles can help to ensure that assets run without fail, increase cost effectiveness, improve machine uptime, and help your organization to understand the level of risk you have undertaken with certain assets.

Generally the process includes the following:

- Define Failure Modes Effects and Critically Analysis:

- Identify assets, asset functionality, and the standards of performance for those assets.

- List all possible ways that the assets could fail and provide the required functions.

- Provide detail on the types of events that could cause these failures.

- Identify the effects on the system when failures happen.

Define the following according to your business practices:

- Failure Cause — Represents the specific manner or way by which a failure occurs in terms of failure of the part. This may generally describe the way a failure occurs such as due to corrosion, debris, or distortion.

- Failure Mode — Describes what has failed.

- Failure Repairs — Indicates the repair that will be performed on the asset in case of failure.

- Failure Component — Indicates the part of the asset for which the failure has occurred.

- Indicate the maintenance that can be performed to prevent or avoid such failures. This maintenance contains cost effective tasks to preserve functions that are important to the system.

- Set up preventive maintenance plans in the same way as described above using maintenance schedules, triggers and linking these to the assets using specifications. Base package Maintenance Schedule Activity Types and Completion Event Types can be used when setting up schedule plans and work requirements.

Financials Options

The following sections provide information about the portals and objects related to financial transactions throughout the system.

Next in This Section

- Understanding Financials Configuration

This section provides the configuration guidelines related to financial entities throughout the system.

- Configuring Financials

This section provides configuration tasks for financials administrative support records.

Understanding Financials Configuration

This section provides the configuration guidelines related to financial entities throughout the system.

Financials management involves creating and managing entities such as expense codes, distribution codes, cost centers, cost categories, tax rate schedules, accounting calendars, and so on.

Financial Transactions (FTs) are created in quite a few situations, in general associated with the purchase or use of resources, such as the time cost of labor, the invoicing or receipt of materials, etc. There is always some system transactional record that drives the creation of the FT, which is referred to as the Creating Sibling record. The system also captures that sibling record on the FT. Each FT belongs to a single Accounting Period, which must be open at the time of creation, and is related to a particular currency.

Each FT consists of two or more balanced financial transaction general ledger (FT GL) lines (at least one debit and one credit). This information can be sent to your organization's general ledger. On the FT GL record, the system can capture an associated Project, Cost Center and Expense Code, as applicable. Each transaction is booked to a particular GL Account code via a distribution code and its associated GL Account Detail. The distribution code specifies how the GL Account string is to be constructed via the GL Construction Algorithm. The Financial Master Configuration specifies which Distribution Code to use for particular scenarios.

Please refer to the Financial Transactions section in the Business User Guide for a conceptual overview of financials functionality.

Master Configuration

Ensure that you create master configuration settings in Financial Master Configuration.

Next in This Section

- About Accounting Calendars

Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application.

- About Currency

The overall system uses the base currency defined in Installation Options, and all financial transactions use the base currency. However, the purchasing system supports other currencies which can be defined in the Currency portal.

- About Colors

Your organization can use the Colors portal to define custom colors used to represent transactions and other entities in various portals. For example, colors defined here are used to distinguish cost categories as they are represented in graphs and/or pie charts.

- About Cost Categories

Cost categories group expenses or costs into logical buckets for reporting purposes.

- About Cost Centers

As costs are incurred, the system tracks them and accumulates them at different levels or cost centers within your organization. Cost centers are part of the accounting hierarchy.

- About Expense Codes

Expense codes are codes assigned to a financial expenditure indicating which payment category the cost falls into. They are part of the accounting hierarchy.

- About Factors and Factor Values

Factors are defined by your organization as a tax component needed to calculate tax values related to anything which incurs costs for your organization and must be taxed (such as purchases and resources used to complete activities). For example, you might define different factors for city tax, state tax and federal tax. Each type of factor would define a factor values list providing numerical values used to calculate the tax. The factor is then referenced on a Tax Rate Schedule.

- About Distribution Codes

Distribution codes simplify the process of generating accounting entries by defining valid combinations of values for “charts of accounts”.

- About Tax Rate Schedules

A Tax Rate Schedule defines the type of taxes that are applicable at various instances in time for related resources (materials, labor, equipment, and other). The tax rate can be defined on a resource type, but this can be overridden for specific storerooms if necessary.

About Accounting Calendars

Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application.

As part of your general configuration your organization will define the accounting calendar in the Accounting Calendar portal then designate that calendar as the default in Financial Master Configuration. Only one accounting calendar is allowed for the entire system. Accounting calendars include a series of accounting periods with a start and end date. They also specify to and from dates when the calendar is “open” or when transactions can be posted to that calendar.

About Currency

The overall system uses the base currency defined in Installation Options, and all financial transactions use the base currency. However, the purchasing system supports other currencies which can be defined in the Currency portal.

Enter standard currency codes such as USD or GBP, a description, symbol and the number of decimal places to use. The currency code will then appear as an option wherever a currency code is required on purchasing records, such as on a blanket contract or purchase order. Any currency codes used in the purchasing system which are different from the base currency are converted into the base when the system creates financial transactions.

About Colors

Your organization can use the Colors portal to define custom colors used to represent transactions and other entities in various portals. For example, colors defined here are used to distinguish cost categories as they are represented in graphs and/or pie charts.

The Color record provides a hex value, description and color sample. Once this is defined, the color can be specified on the Cost Category record as the designated color for that category. Each color should only be referenced by one cost category.

About Cost Categories

Cost categories group expenses or costs into logical buckets for reporting purposes.

The following details apply for cost categories:

- Each expense code references a cost category.

- Each cost category can be assigned a specific color so that the category is represented by that color in graphs and pie charts throughout the system. Each color should only be referenced by one cost category.

About Cost Centers

As costs are incurred, the system tracks them and accumulates them at different levels or cost centers within your organization. Cost centers are part of the accounting hierarchy.

Cost center records display financial statistics such as a budget amount, year to date actual amount, and committed amount for the cost center. These amounts represent the fiscal year rather than the calendar year. A monthly statistics section also allows you to display more detailed information by month in a graph.

General ledger account numbers are a concatenation of the cost center, project, and expense code, as applicable.

Allow User Charge

User records that result in costs or charges need to reference a cost center that has this value set to Yes. For example, when users create activities, the referenced cost centers must “allow user charges”. This value is set to No on cost centers that are specifically designated for general ledger or system generated costs. For example, an inventory cost center is referenced on storerooms to balance the debit and credit sides of the general ledger (issue materials for an activity to charge the debit side and reduce the inventory value adjusts the debit side).

About Expense Codes

Expense codes are codes assigned to a financial expenditure indicating which payment category the cost falls into. They are part of the accounting hierarchy.

Expense codes reference a cost category, resource class, and an account segment. This means that each expense code is only valid for a particular resource class (labor, material, equipment, or other), and must be defined accordingly. General ledger account numbers are a concatenation of the cost center, project, and expense code, as applicable.

About Factors and Factor Values

Factors are defined by your organization as a tax component needed to calculate tax values related to anything which incurs costs for your organization and must be taxed (such as purchases and resources used to complete activities). For example, you might define different factors for city tax, state tax and federal tax. Each type of factor would define a factor values list providing numerical values used to calculate the tax. The factor is then referenced on a Tax Rate Schedule.

About Distribution Codes

Distribution codes simplify the process of generating accounting entries by defining valid combinations of values for “charts of accounts”.

The system uses the distribution code as a flexible way to construct the final account number to send to the GL system. That algorithm can be coded to construct the final GL account number from data available anywhere in the system.

When creating distribution codes you specify the general ledger account algorithm that will be used by the system when it interfaces financial transactions that reference this distribution code to the general ledger. This account algorithm will construct the actual GL Account Number. For example, the base algorithm constructs the account by concatenating account segments from cost center, project and expense code.

If some accounts are static and do not need dynamic construction, the entire account number can be defined in the GL Account Detail and a simple algorithm can retrieve the account number from the same distribution code.

About Tax Rate Schedules

A Tax Rate Schedule defines the type of taxes that are applicable at various instances in time for related resources (materials, labor, equipment, and other). The tax rate can be defined on a resource type, but this can be overridden for specific storerooms if necessary.

Your implementation will need to configure attributes so that tax rates are included on purchase requisitions, purchase orders and blanket contracts.

Configuring Financials

This section provides configuration tasks for financials administrative support records.

Please refer to the Financial Transactions section in the Business User Guide for a conceptual overview of financials functionality.

Refer to the Understanding Financials Configuration section in the Administrative User Guide for configuration guidelines.

Next in This Section

- Defining Accounting Periods

Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application.

- Defining Account Segments

Account segment fields appear on various records such as on cost centers, expense codes and projects. This is a free form text field which builds the general ledger account which is shown in the financial transaction log when costs are posted.

- Creating Accounting Calendars

Navigate to the Accounting Calendar portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Currency

Navigate to the Currency portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Colors

Navigate to the Color portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Cost Categories

Navigate to the Cost Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Cost Centers

Navigate to the Cost Center portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Reviewing Cost Center Statistics

Use this procedure to review cost center statistics.

- Deactivating Cost Centers

Use this process to deactivate a cost center.

- Defining Expense Codes

Navigate to the Expense Code portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Deactivating Expense Codes

Use this process to deactivate an expense code.

- Defining Factors

Navigate to the Factor portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Distribution Codes

Navigate to the Distribution Code portal under Admin, select Add, complete the required fields according to your business practices and Save.

- Defining Tax Rate Schedules

Navigate to the Tax Rate Schedule portal under Admin, select Add, complete the required fields according to your business practices and Save.

Defining Accounting Periods

Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application.

As part of your general configuration your organization will define the accounting calendar in the Accounting Calendar portal then designate that calendar as the default in Financial Master Configuration. Only one accounting calendar is allowed for the entire system. Accounting calendars include a series of accounting periods with a start and end date. They also specify to and from dates when the calendar is “open” or when transactions can be posted to that calendar.

When defining your accounting calendar, take the following into consideration:

- In general, your organization’s finance department should handle the creation of accounting periods.

- Number of periods cannot be less than 0.

- Defined accounting periods must be less than or equal to the Number of Periods.

- You cannot define a calendar with gaps between the periods. Each period must follow the previous period consecutively.
For example, you may forget to include February 29th for leap years.

- You cannot define a calendar with gaps between years. For example, the fiscal year cannot jump from 2013 to 2015 in consecutive periods.

- Dates cannot overlap between periods.

- Period start dates should be on or before the defined end dates.

- The open from date should be on or before the open to date.

Example:

Fiscal Year

Accounting Period

Description

Start Date

End Date

Open from Date

Open to Date

2015

1

Period 1

06/01/2014

06/30/2015

06/01/2014

07/10/2015

2015

2

GD Period 2 (July) FY2015

07-01-2014

07-31-2014

07-01-2014

08-10-2014

2015

3

GD Period 3 (August) FY2015

08-01-2014

08-31-2014

08-01-2014

09-10-2014

2015

4

GD Period 4 (September) FY2015

09-01-2014

09-30-2014

09-01-2014

10-10-2014

2015

5

GD Period 5 (October) FY2015

10-01-2014

10-31-2014

10-01-2014

11-10-2014

2015

6

GD Period 6 (November) FY2015

11-01-2014

11-30-2014

11-01-2014

12-10-2014

2015

7

GD Period 7 (December) FY2015

12-01-2014

12-31-2014

12-01-2014

01-10-2015

2015

8

GD Period 8 (January) FY2015

01-01-2015

01-31-2015

01-01-2015

02-10-2015

2015

9

GD Period 9 (February) FY2015

02-01-2015

02-28-2015

02-01-2015

03-10-2015

2015

10

GD Period 10 (March) FY2015

03-01-2015

03-31-2015

03-01-2015

04-10-2015

2015

11

GD Period 11 (April) FY2015

04-01-2015

04-30-2015

04-01-2015

05-10-2015

2015

12

GD Period 12 (May) FY2015

05-01-2015

05-31-2015

05-01-2015

06-10-2015

Defining Account Segments

Account segment fields appear on various records such as on cost centers, expense codes and projects. This is a free form text field which builds the general ledger account which is shown in the financial transaction log when costs are posted.

Your business practices determine how you set up account segments and your interface with your general ledger. Use the general ledger construction algorithms to set up account segments. The Simple GL Construction algorithm (W1-SIMPLEGL) retrieves the current effective GL number defined on the distribution code and use the retrieved value as the general ledger account number. Beyond this, the remaining GL algorithms are used to construct the GL account number by concatenating the account segments from Cost Center, Project and Expense Code. The Delimiter parameter on each algorithm is the separator between the segments. The Project Placeholder parameter on each algorithm is used as the segment for project if a GL entry is not related to a project.

Creating Accounting Calendars

Navigate to the Accounting Calendar portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Defining Currency

Navigate to the Currency portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: One currency must be defined in Installation Options as the system's base currency.

Defining Colors

Navigate to the Color portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Cost categories will need to reference a unique color.

Defining Cost Categories

Navigate to the Cost Category portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the cost category record:

Note: This list does not represent required fields.

- Color — you must have a unique color to represent each cost category.

Expense codes will need to reference a cost category.

Defining Cost Centers

Navigate to the Cost Center portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the cost category record:

Note: This list does not represent required fields.

- Expense Code — Add Valid Expense Codes to the cost center after it is defined, as required by your business practices.
This is determined by the Financial Master Configuration.

Reviewing Cost Center Statistics

Use this procedure to review cost center statistics.

1. Navigate to the appropriate Cost Center record in Edit mode.

2. Search for and select the cost center with the statistics to review.

3. Click the Accumulate Monthly Statistics button.

The system renders the graphs or pie charts to represent the statistics in the Cost Center Monthly Statistics section.

Deactivating Cost Centers

Use this process to deactivate a cost center.

Cost centers must be in active status to be referenced elsewhere in the system.

1. Navigate to the appropriate Cost Center record in Edit mode.

2. Search for and select the cost center that should no longer be used.

3. Click the Deactivate button.

Defining Expense Codes

Navigate to the Expense Code portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the expense code record:

Note: This list does not represent required fields.

- Cost Category

Expense codes must be in active status to be used. Cost centers reference a list of valid expense codes, as required by your business practices.

Deactivating Expense Codes

Use this process to deactivate an expense code.

Expense codes must be in active status to be used.

1. Navigate to the appropriate Expense Code record in Edit mode.

2. Search for and select the expense code that should no longer be used.

3. Click the Deactivate button.

Defining Factors

Navigate to the Factor portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: None.

Add factor values in the Factor Characteristic Values section after creating the factor.

Tax rate schedules will need to reference a factor.

Defining Distribution Codes

Navigate to the Distribution Code portal under Admin, select Add, complete the required fields according to your business practices and Save.

Defining Tax Rate Schedules

Navigate to the Tax Rate Schedule portal under Admin, select Add, complete the required fields according to your business practices and Save.

Prerequisites: The following are referenced by the tax rate schedule record:

Note: This list does not represent required fields.

- Factor

- Cost Center

- Expense Code

Your implementation will need to take steps to include attributes which determine the tax rates on purchasing record line items.

Complete the steps, as indicated below, to properly configure tax rate schedules and include tax rates on purchasing documents. Refer to the demonstration environment for an example and to the Oracle Utilities Application Framework Administration Guide for more information as needed.

1. Navigate to Admin → Characteristic Type and create a tax characteristic type.
See WD-TAXST in demo.

2. Navigate to Admin → Factor and create factors under the tax characteristic type.
See WD-StateTax in demo.

Add factor values to the factor as needed.

3. Navigate to Admin → Tax Rate Schedule and create a tax rate schedule
See WD-Tax1 in demo.

Add tax components for the schedule by using the previously created factors.

4. Navigate to Admin → Data Area to introduce a flattened characteristic element for the characteristic type in the Purchase Requisition Line business object.
See %tax in Data Area demo.

Note that this characteristic type should be the same one referenced by the Tax Component’s Factor and that it should be configured for Tax Component and Purchase Requisition Line entities. You can simply create a new data area that extends the Requisition Info data area of the base business object if you don’t want to create a new business object implementation.

Sample Schema:

< schema xmlns:uiHint="http://oracle.com/ouafUIHints">

< sequence mapField="SEQ_NUM"/>

< rateSchedule mapField="TAX_RATE_SCHED_CD" uiHint:select="table:W1_TAX_RATE_SCHED"

fkRef="W1-TXRTS"/>

< effectiveDate mapField="EFFDT"/>

< factor mapField="W1_FACTOR_CD" uiHint:select="table:W1_FACTOR"/>

< factorValue mapField="W1_FACTOR_VALUE"/>

< charType mapField="CHAR_TYPE_CD" uiHint:select="table:CI_CHAR_TYPE"/>

< charValue mapField="CHAR_VAL"/>

< taxAmount mapField="W1_TAX_AMT"/>

< /schema>

5. Update the flattened tax element to trigger the tax calculation service.

Once configuration is complete, you can navigate to a purchase requisition line item to see the result.

Integrations

This chapter provides information related to integrating with other applications.

Next in This Section

- About Integrations

Oracle Utilities Work and Asset Management can be configured to integrate with external systems through inbound and outbound messaging, or communications. Communications are records of messages sent between the source system and an external system and are most often created as a result of an activity.

- Specific Product Integrations

Integrations with other Oracle Utilities applications help to provide clients with a complete application solution. This section identifies the specific product integrations that include Oracle Utilities Work and Asset Management, including:

- Defining External Systems

You must create an External System record for each external system to which Oracle Utilities Work and Asset Management will communicate. Each external system defines a set of outbound message types that will be sent to that system. Refer to the documentation for your specific integration for more information.

- Data Synchronization for Integrations

In most integrations, synchronization of data between the two systems is supported through a set of business objects, master configurations, batch controls, and pre-configured XAI Inbound Services.

- BI Publisher Integration

BI Publisher Reports allow users to generate and print reports for certain entities, such as operational data, activity reports, purchasing reports, inventory reports, and so on.

- GIS Integration

GIS applications are widely used to manage assets, locations and other spatial data. The Oracle Utilities Work and Asset Management GIS Integration interfaces with an Esri ArcGIS Portal/Server to allow users to view asset layers on a map, and to create and view work requests and work orders on the map. Access the map from the Oracle Utilities Work and Asset Management GIS Map Viewer menu after the configuration steps have been completed.

About Integrations

Oracle Utilities Work and Asset Management can be configured to integrate with external systems through inbound and outbound messaging, or communications. Communications are records of messages sent between the source system and an external system and are most often created as a result of an activity.

Refer to the External Messages section in the Oracle Utilities Application Framework Administration Guide for more details.

Specific Product Integrations

Integrations with other Oracle Utilities applications help to provide clients with a complete application solution. This section identifies the specific product integrations that include Oracle Utilities Work and Asset Management, including:

- BI Publisher Enterprise:
BI Publisher Reports allow users to generate and print reports for certain entities, such as operational data, activity reports, purchasing reports, inventory reports, and so on.

Refer to the Installation Guide for information on installing and configuring.

Refer to BI Publisher Integration for more information and configuration details.

- Esri ArcGIS:
GIS applications are widely used to manage assets, locations and other spatial data. The Oracle Utilities Work and Asset Management GIS Integration interfaces with an Esri ArcGIS Portal/Server to allow users to view asset layers on a map, and to create and view work requests and work orders on the map.

Refer to GIS Integration for more information and configuration details.

- Enterprise Resource Planning (ERP): Oracle Utilities Work and Asset Management processing can be tied to an Enterprise Resource Planning (ERP) application such as Enterprise Business Suite to manage human resources, processing and procurement functions.
Refer to the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning documentation for more information.

- Mobile Workforce Management:
Oracle Utilities Work and Asset Management integration with Oracle Utilities Mobile Workforce Management is managed through the Oracle Utilities Field Work Process Integration Pack.

Refer to the Oracle Process Integration Pack for Oracle Utilities Field Work 12.1 - Implementation Guide for more information.

- Oracle Utilities Analytics:
Oracle Utilities Analytics Dashboards provide analysis of data from Oracle Utilities Work and Asset Management or Oracle Utilities Operational Device Management using Oracle Business Intelligence Enterprise Edition built-in metrics. Non-spatial analytics, information that is not tied to geography, is represented in a series of dashboards showing tables, bar graphs, pie charts, and gauges.

Refer to the Oracle Utilities Analytics documentation for more information.

- Oracle Utilities Integration for Device Operations:
(ODM only). Oracle Utilities Operational Device Management integration with Oracle Utilities Meter Data Management

Refer to the Oracle Utilities Integration for Device Operations documentation for more information.

Defining External Systems

You must create an External System record for each external system to which Oracle Utilities Work and Asset Management will communicate. Each external system defines a set of outbound message types that will be sent to that system. Refer to the documentation for your specific integration for more information.

Data Synchronization for Integrations

In most integrations, synchronization of data between the two systems is supported through a set of business objects, master configurations, batch controls, and pre-configured XAI Inbound Services.

Types of Synchronization Requests

Data synchronization is performed via synchronization requests sent from the external system via a middleware integration component. The application supports three types of synchronization requests:

Initial Synchronization Requests

Initial synchronization requests are used during the initial configuration of the integration. They facilitate import of data that synchronizes service points, locations, and contact information.

Ongoing Synchronization Requests

Ongoing synchronization requests are used when updating existing data in Oracle Utilities Work and Asset Management based on changes in corresponding data in the external system. Ongoing synchronization requests can be used to update locations, assets or components and to send activity completion information.

Composite Synchronization Requests

Composite synchronization requests are requests that contain synchronization requests for multiple types of data within a single request. For example, a composite request could contain requests to update a location, and complete an activity. This supports situations where multiple types of data must be updated based on a single change in the external system.

Navigate to Admin > Business Object and search for “W1%sync%” to locate business objects used for data synchronization.

Base Package Synchronization Request Business Objects

Navigate to Admin > Business Object and search for “W1%sync%” to locate these objects.

Master Configurations for Data Synchronization

Master configurations are used to define aspects of the synchronization process, including resolution of foreign keys and the type of synchronization business objects to use for each type of data being synchronized.

Navigate to Admin > Master Configuration to review or modify master configuration settings.

Batch Controls for Data Synchronization

Batch controls perform processing for initial synchronization requests such as allocating keys to data, resolving foreign keys, and loading data (instantiating business objects representing entities such contacts, assets, etc).

“Initial Sync Request - Resolve Keys [maintenance object]” batch controls invoke a generic maintenance object transition process to invoke the “Resolve Keys - Initial Sync” algorithm for synchronization requests of the appropriate type. Parameters used by “resolve keys” batch controls include:

- Maintenance Object: (Required) the maintenance object (asset, contact, etc.) to be processed. This must be set to the Sync Request maintenance object for the batch control.

- Restrict By Batch Code: Restricts processing to synchronization requests whose current state is linked to this batch code.

- Restrict By Business Object: Restricts processing to synchronization requests linked to this business object.

- Restrict By Status Code: Restricts processing to synchronization requests of this status (default: KEY_ALLOCATD).

- Max Errors: Specifies the maximum number of errors allowed before the process exits.

Refer to the Oracle Utilities Work and Asset Management Batch Controls section for a list of these synchronization batch controls.

Batch Scheduling for Data Synchronization

The following sequence indicates the order in which the batch controls on the Initial Sync Request BO life cycle should be executed.

1. Transformation / Schema Validation Job

2. Key Allocation Job

3. Foreign Key Resolution / BO Validation Job ( all key allocation jobs must finish)

4. Load Job

XAI Inbound Services for Data Synchronization

XAI inbound services are used to facilitate invoking the Sync Request Seeder business object by the middleware components upon receipt of a synchronization request.

Navigate to Admin > XAI Inbound Service to review or modify master configuration settings.

Next in This Section

- Understanding Synchronization Request Processing for Integrations

This section provides an overview of the processing that takes place when a synchronization request is sent. For each step in the process, the table below provides a brief description of the processing that takes place, and lists the specific objects involved.

Understanding Synchronization Request Processing for Integrations

This section provides an overview of the processing that takes place when a synchronization request is sent. For each step in the process, the table below provides a brief description of the processing that takes place, and lists the specific objects involved.

1. The external system sends a synchronization request to the middleware integration layer.
For example, consider a request to update information about an asset installation.

2. The middleware components transform the request from the external system to the format, to the format used by Oracle Utilities Operational Device Management (this format is based on the business object schemas of the synchronization request business objects).

3. The middleware component invoked the appropriate XAI Inbound Service, and sends the transformed request.
XAI Inbound Service: W1-SyncRequestInbound (mapped to the W1-SyncRequestSeeder business object)

4. The XAI Inbound Service invokes the Sync Request Seeder business object, which in turn, determines which synchronization request business object to create (based on the type of data in the synchronization request and the Seeder Sync Master Configuration).
Synchronization Request BO: W1-SyncRequestSeeder

5. For initial synchronization requests, background processing creates master data for each synchronization request, including the following steps:

- Data Transformation / Schema Validation

- Allocate Keys

- Resolve Foreign Keys / Validate Business Object

- Load Data

BI Publisher Integration

BI Publisher Reports allow users to generate and print reports for certain entities, such as operational data, activity reports, purchasing reports, inventory reports, and so on.

Complete the following to configure your BI Publisher integration:

Next in This Section

- Create a BI Publisher Report

Complete the following to create a BI Publisher report.

- Configure a BI Report in Oracle Utilities Work and Asset Management

Complete the following to configure a BI Publisher report in Oracle Utilities Work and Asset Management.

- Add the Valid Business Object Option Type to the Maintenance Object

Complete the following to add the Valid Business Object Option Type for the report to the appropriate Maintenance Object.

- Add the Report Code Option Type to the Business Object

Complete the following to add the Report Code Option Type to the appropriate Business Object.

- Enable the Print Report Function

Complete the following to add the Print button to the Business Object record actions.

- Configure Reports Dispatch

Complete the following to configure reports dispatch for BI Publisher reports.

Create a BI Publisher Report

Complete the following to create a BI Publisher report.

1. Open BI Publisher Enterprise and navigate to the BI Publisher Server Catalog .

2. Choose a folder where the new report will be created.

3. Create a folder for the report. The report folder should not be more than 12 characters since this will also be used as a report code in the Report Definition.

4. Create a report Data Model.

1. In the Properties section define the following:

- Default Data Source - select a data source from the list. This will be the default data source for each new SQL data set you define.

Example: W22110Q1

- Oracle DB Default Package - W1_BI_RPT
.

2. Configure the Data Model.

- Data Sets – contain the logic to retrieve data from a single data source.

Refer to the “Overview of Creating Data Sets” section in the BI Publisher Help for detailed information.

- USER_WHERE_CLAUSE – this variable must be included to the main dataset’s SQL script. The variable will be populated at the Before Report trigger.

Format: Where 1=1 AND <cold_name> = <value>

- Event Trigger - checks for an event. When the event occurs the trigger runs the PL/SQL code associated with it.

- Before Report - fires before the data set is executed. Enter the following for the trigger:

- Name: Before Report

- Type: Before Data

- Language: PL/SQL

- Event Trigger Function - W1_BI_RPT.BEFOREREPORT – will retrieve the where clause, order by, the user language, the user time format and the user date format from report queue table and will update the report queue record status to Started.

- After Report - will fire after the data engine executes all data sets and generates the XML.

- Name: After Report

- Type: After Report

- Language: PL/SQL

- Event Trigger Function - W1_BI_RPT.AFTERREPORT - this will update the run date/time field in the table and will update the report queue record status to Completed.

- Input - Report Queue ID

- Return - Boolean (True/False)

- Parameters - a variable whose value can be set at runtime. The following parameters should be added in the report:

- P_USER_ID - current logged in user ID.

- P_REPORT_QUEUE_ID - Auto generated ID.

5. Create the report. The report name must be the same with the folder name.

Configure a BI Report in Oracle Utilities Work and Asset Management

Complete the following to configure a BI Publisher report in Oracle Utilities Work and Asset Management.

1. Navigate to the Report Definition portal under Admin and select Add and complete the following fields:

1. Report Code - report code must be the same with the BI report name.

2. Description - short description of the report.

3. External Reference ID - the application external reference.

Example: Activity

4. Application Service - application service for the report.

Example: W1ACTRPT

5. Long Description - detailed description of the report.

2. Navigate to the Parameters tab and complete the following fields:

1. Parameter Code - P_REPORT_QUEUE_ID

2. Sequence - 1

3. Characteristic - select from the dropdown list.

4. Description - Report Sequence ID

5. Long Description - Report Sequence ID

3. Save.

Add the Valid Business Object Option Type to the Maintenance Object

Complete the following to add the Valid Business Object Option Type for the report to the appropriate Maintenance Object.

1. Navigate to the Maintenance Object portal under Admin and select Search.

2. Search for the Maintenance Object related to the Business Object where the report function will be added.

3. Navigate to the Maintenance Object details.

4. Open the to Options tab and add W1BI for the Valid Option Type.

Add the Report Code Option Type to the Business Object

Complete the following to add the Report Code Option Type to the appropriate Business Object.

1. Navigate to the Business Object portal under Admin and select Search.

2. Search for the Business Object where the Report Code will be added.

3. Navigate to the Business Object details.

4. Add the Report Code Option Type.

5. Set the report code from Report Definition.

Report Code: < REPORT_CODE >

Configure Report Definition settings to allow your implementation to import and export definition report records from one server to another. Navigate to the Report Definition portal under Admin and select Search.

Refer to Defining Report Definitions in the Oracle Utilities Application Framework documentation for information on the parameters and settings.

Enable the Print Report Function

Complete the following to add the Print button to the Business Object record actions.

1. On the business object where you added the report code option type, navigate to the Business Object Schema tab.

2. Look for the Record Actions section.

3. Update the Record Actions section to add the Print button.

Add button in schema

Add button in UI Map fragment

Configure Reports Dispatch

Complete the following to configure reports dispatch for BI Publisher reports.

1. Create a UI Map for the report filter.

This will contain the filter fields for the query to the report. Fields where UI Map elements are mapped should be identical to the table fields.

Ensure that you include the W1-GenerateReportActions UI Map fragment.

This will display the button which will be used to process the report.

Example:
<tr>

<td>

<oraInclude map="W1=GenerateReportActions"/>

</input></td>

</tr>
Refer to Defining UI Maps in the Oracle Utilities Application Framework documentation for more information.

2. Create a report filter Zone.

Refer to Setting Up Portals and Zones in the Oracle Utilities Application Framework documentation for more information.

3. Create new Portal where the report filter zone will be included.

Refer to Setting Up Portals and Zones in the Oracle Utilities Application Framework documentation for more information.

Sample Layout of Final Report Portal

GIS Integration

GIS applications are widely used to manage assets, locations and other spatial data. The Oracle Utilities Work and Asset Management GIS Integration interfaces with an Esri ArcGIS Portal/Server to allow users to view asset layers on a map, and to create and view work requests and work orders on the map. Access the map from the Oracle Utilities Work and Asset Management GIS Map Viewer menu after the configuration steps have been completed.

Typically the GIS server includes distributed asset layers. Oracle Utilities Work and Asset Management has corresponding records for these assets and creates work requests and work orders with activities which are tied to the assets represented in both systems.

The Oracle Utilities Work and Asset Management Esri Viewer is certified for Esri ArcGIS, using the ArcGIS Portal with Web maps:

- Web maps bundle the base map choice plus feature layers and controls.

- Web maps can be public or they can be secured to authorized users.

- Multiple web maps can also be accessed via the Oracle Utilities Work and Asset Management map viewer.

- Oracle Utilities Work and Asset Management accesses the web maps via the Esri JavaScript API using REST-based services.

- The web maps can be accessed from an on-premise ArcGIS Portal, or you can configure it to be accessed via Esri’s cloud (arcgis.com).

The GIS Map Viewer in Oracle Utilities Work and Asset Management allows users to:

- Select assets from the map layer and tie them to existing work records.

- View asset layers on the map for spatial distribution.

- Create new work requests at points on the map or tied to an asset.

- Create new work orders based on selected assets on the map.

- View work requests and work orders on the map.

- Create new construction work designs at points on the map or tied to an asset.

Refer to the About GIS in Oracle Utilities Work and Asset Management section in the Business User Guides for functionality guidelines.

Data Synchronization Between Esri and WAM

- Esri supports versioning, to allow for various long-running edits and designs to be stored concurrently with the current ‘default’ version which represents features as built.

- WAM uses a ‘WAM Version’ in the ArcGIS Server which can be compared at any time with the default version to detect changes since the last comparison.

- The results of the comparison contain all adds/updates/deletes to tracked features. We then feed those results to WAM, where we have a set of data mapping tools that must be configured for the client’s Esri model to get features loaded into WAM as Asset Locations and Assets.

- For WAM data changes, we use standard Oracle Utilities Application Framework data synchronization processing to detect changes and export.

Next in This Section

- GIS Integration Setup Steps

Configuration to support the GIS Viewer in Esri ArcGIS includes making updates to existing GIS Asset data, cross referencing GIS Asset data with system assets, and adding new layers that are used to track and display work records.

GIS Integration Setup Steps

Configuration to support the GIS Viewer in Esri ArcGIS includes making updates to existing GIS Asset data, cross referencing GIS Asset data with system assets, and adding new layers that are used to track and display work records.

In Oracle Utilities Work and Asset Management, configuration involves specifying the details of where the GIS Server is located, what layers it hosts, and how to send messages to the GIS Server to keep it in sync with Oracle Utilities Work and Asset Management work objects.

The following software is required to facilitate integration functionality:

- ArcGIS Desktop: Includes a package of client tools such as ArcMap, ArcCatalog, ArcToolbox etc. These tools allow you to view, create, administer and publish the spatial data as map documents.

- ArcGIS Server: Publishes the map content that is authored using ArcGIS Desktop as a service.

- Portal for ArcGIS: An extension to the ArcGIS server which aids in generating the application ID that is required to run the application built on the ArcGIS WebApp Builder. This also helps in authorizing the users through LDAP integration. The Portal for ArcGIS software is optional if the organization is having subscription to ArcGIS Online.

- ArcGIS Online: Esri hosted cloud based mapping platform that facilitates making and sharing maps. The subscription provides access to generate the application ID that is required to run the application built on ArcGIS WebApp Builder. ArcGIS Online subscription is optional if the organization is licensed to Portal for ArcGIS.

Complete the steps indicated in the following sections to install and set up this software and the integration.

Next in This Section

- GIS Configuration Steps in ArcGIS Server/Portal

The following sections provide guidelines for the configuration steps that need to be completed in ArcGIS.

- GIS Configuration Steps in Oracle Utilities Work and Asset Management

The following sections provide guidelines for the configuration steps that need to be completed in the Oracle Utilities Work and Asset Management application.

GIS Configuration Steps in ArcGIS Server/Portal

The following sections provide guidelines for the configuration steps that need to be completed in ArcGIS.

Next in This Section

- Set Up ArcGIS Geodatabase

This section provides guidelines for setting up the ArcGIS Geodatabase.

- Complete the Set Up of Version Comparison and GIS Sync

This section provides guidelines for completing the setup of version comparison and GIS synchronization.

- Publish Data as Services on the ArcGIS Server

This section provides guidelines for publishing data as services in ArcGis Server.

- Connect Portal for ArcGIS with Enterprise LDAP

This section provides guidelines for connecting Portal for ArcGIS with Enterprise LDAP.

Set Up ArcGIS Geodatabase

This section provides guidelines for setting up the ArcGIS Geodatabase.

1. Feature Classes: For all Feature Classes which will be synced with Oracle Utilities Work and Asset Management, a Global Unique Identifier (GUID) column/attribute must be enabled - this is the cross-reference value that Oracle Utilities Work and Asset Management will capture and utilize.

The GLOBALID field mapping needs to be added in each data set and should be enabled to be shown in each feature class.

2. Versioning: Versioning in ArcGIS must be turned on. Oracle Utilities Work and Asset Management introduces a 'WAM Sync Version' to support data synchronization from GIS to WAM.

3. Work Locations: Oracle Utilities Work and Asset Management introduces one new feature class called Work Locations. A layer for Work Locations should be included on any web maps to be used in Oracle Utilities Work and Asset Management.

4. Map Notes Layer: A Map Notes layer for Work Locations must be included on any web maps to be used in Oracle Utilities Work and Asset Management.

Map Notes is a layer similar to Work Locations but must be configured by your implementation. This needs to be configured on the ArcGIS server so that it can be part of the web map.

The attachment feature also needs to be enabled for the map notes layer.

Complete the Set Up of Version Comparison and GIS Sync

This section provides guidelines for completing the setup of version comparison and GIS synchronization.

1. Deploy the .jar File

2. Configure the Property File

3. Use ArcCatalog to Execute the .jar

4. Publish the Results as a Geoprocessing Service

Note: WAM updates are only published to the Default map version.

Next in This Section

- Deploy the .jar File

This section provides guidelines for deploying the .jar file.

- Configure the Property File

The property file, or config file, will be located in the same location as the .jar file. This file needs to be copied to the location where .jar file was copied after deployment.

- Use ArcCatalog to Execute the .jar

This section provides guidelines for using ArcCatalog to execute the .jar file.

- Publish the Results as a Geoprocessing Service

This section provides guidelines for publishing the .jar execution results as a geoprocessing service.

Deploy the .jar File

This section provides guidelines for deploying the .jar file.

A .jar file is provided with WAM for geoprocessing to execute version comparison, along with a configuration file. Locate spl‐w1‐2.x.x.x.x‐gis.jar. Example: spl‐w1‐2.1.1.1.0‐gis.jar. The .jar file should be placed in both ArcGIS Desktop and ArcGIS Server running locations.

This file extracts the changes from the GIS database and provides XML that can be consumed by WAM service to generate inbound data synchronization. The deployment of this .jar requires ArcGIS Desktop (to execute the .jar and generate the results) and ArcGIS Server (to publish the results as Geoprocessing service). The .jar file should be placed in both ArcGIS Desktop and ArcGIS Server running locations.

1. Place the .jar file in the ArcGIS Desktop installation folder path.

Example: “C:\Program Files (x86)\ArcGIS\Desktop10.4\java\lib\ext”.

2. Place the .jar file in ArcGIS Server installation folder path.

Example: “C:\Program Files\ArcGIS\Server\usr\lib\ext”.

Configure the Property File

The property file, or config file, will be located in the same location as the .jar file. This file needs to be copied to the location where .jar file was copied after deployment.

Property file configuration is one time configuration that needs to be completed by the administrator to setup the synchronization process. The property file consists of input parameters that are required for the GIS Extractor program to establish a connection to the Geodatabase.

Configure the following required properties:

- keyDBServer: DB server name (Example: SLC07ZJQ.us.oracle.com)

- keyDBInstance: DB instance name (Example: sde:oracle11g:WAMV2200DEV)

- keyDBName: Database name (Example: WAMV2200DEV)

- keyDBUser: Database user name (Example: sde)

- keyDBPwd: Database user password

Use ArcCatalog to Execute the .jar

This section provides guidelines for using ArcCatalog to execute the .jar file.

1. Open the ArcCatalog application.

2. Expand Toolboxes, in the Catalog window.

3. Create a new toolbox in My Toolboxes.

Right click My Toolboxes, select New and Toolbox.

4. Provide the name WAMGPTools.tbx and press Enter.

Now you can add new or custom tools.

5. Right-click the new toolbox and select Add then Tool.

6. In the Add Tool dialog box, select WAMGIGPFF and click OK.

7. To execute the tool in ArcToolbox, double-click the tool.

8. View the tool's parameters in the dialog that pops up.

9. Provide inputs to the parameters accordingly:

- Task_Name: QueryIDs

- Execution_Mode: Initial

- Feature_Class_List: SDE.ZZ_wControlValve

- Source_Version: SDE.DEFAULT

- Temp_Version: Temp

- WKID: Well Known identifier for the target spatial reference

- WAM Sync Version: The version name that should be created in Geodatabase to track incremental changes (Ex: WAMSyncVersion)

10. Keep remaining parameters with value “NA” as it is.

11. Click on “OK” button.

The tool runs upon completion.

Publish the Results as a Geoprocessing Service

This section provides guidelines for publishing the .jar execution results as a geoprocessing service.

Once the configuration file is setup and tool is executed, the results of the tool are needed to be published as Geoprocessing service in ArcGIS server.

1. Start the ArcGIS server.

2. Select the Geoprocessing Menu and then Results.

3. Right click on the main node with the label Extract_Delta_Changes […] and select Share As > Geoprocessing Service.

4. On the Share as Service window, select Publish a service and click on Next.

5. Select ArcGIS Server connection from the drop down for Choose a connection, give Service name and click on Next. Use the ArcGIS Server connection that was established earlier.

6. Select Create new folder named GPServices (Note: only when this folder is not available in the drop down of Use existing folder) and click Continue.

The Service Editor dialog opens.

7. Select various parameters under Extract_Delta_Changes node (right side) and provide below values for Description field:

- Task_Name: This value allows the service to retrieve GUIDs of the requested feature classes. The other possible values for task are Query Specific changes, Query complete changes, Query Inserts, Query Updates and Delete Version.

- Execution_Mode: The execution mode assists in retrieving all the GUIDs of the feature class or updated GUIDs of the feature class. The possible values are Initial and COU, where COU refers to Change Only Updates.

- Feature_Class_List: This value enables querying of the GUIDs in the feature class of interest. At a time, only one feature class name should be passed to service.

- Feature_Class_Name

- Fields: This value helps the GP service to extract the information only for the fields of interest. An OUAF batch process reads the list of fields from the extendable lookup and passes the value as a comma separated list.

- GUIDs: The list of GUIDs is required to extract the attribute information.

- Source_Version: This value is used to establish a connection with the underlying Geodatabase.

- Temp_Version: This value is used to create a temporary version on top of the DEFAULT / parent version.

- WAM_Sync_Version: This value is used to connect to WAMSync Version and perform Version difference between Temp Version and WAMSync Version Execution_Mode.

- Response_XML: Output XML response.

8. Provide Summary, Tags and Description (optional).

9. Click on Analyze and Publish.

10. On success, the interface displays a confirmation message.

Publish Data as Services on the ArcGIS Server

This section provides guidelines for publishing data as services in ArcGis Server.

Prerequisites:

- GIS client (ArcGIS Desktop) and ArcGIS Server is installed

- Enterprise Geodatabase is configured and Oracle client 11g is installed on the machine to connect to Geodatabase

- Connection to Enterprise Geodatabase is established

- Data is imported into Geodatabase

Next in This Section

- Set the Data Source in Map Documents

This section provides guidelines for configuring data sources in map documents.

- Publish Map Documents as Services in ArcGIS Server

This section provides guidelines for publishing map documents as services in ArcGIS Server.

- Create and Publish Web Maps in Portal

Using map services and feature services that have been published, configure web maps as needed for use with WAM. Include the Work Locations and Map Notes services. Then configure access to the web maps.

Set the Data Source in Map Documents

This section provides guidelines for configuring data sources in map documents.

1. Before setting the data source, copy the database connection path:

1. Launch ArcCatalog.

2. Click on the previously established connection in the Catalog tree. (Ex: sde@WAMV2200DEV)

3. Use the location toolbar, copy the path using the context menu.

4. Using the Catalog tree, navigate to the Map Documents folder in the Customer Specific Data folder, which is in the previously established connection.

2. Change the data source for Map Notes.

1. Right click on the map document, MapNotes.mxd, and choose the option to Set Data Source(s).

2. Click the Select All button to select all of the layers.

3. Click the Replace All button.

4. In the Replace With text box, paste the previously copied database connection path. (Ex: Database Connections\sde@WAMV2200DEV.sde)

5. Verify that the “new data source” column is updated with the provided connection information for all the layers.

6. Change the output file name for the map document output file path.

7. Click the OK button to set the data source for the map document.

3. Change the data source for Work Locations.

1. Navigate to the Work Locations Map document located in the WAMOwned or WAMSpecificData folder.

2. Follow the same steps as above with the map document, WorkLocations.mxd.

Publish Map Documents as Services in ArcGIS Server

This section provides guidelines for publishing map documents as services in ArcGIS Server.

Once the data source is set, map documents can be published as map / feature services.

1. Publish the Work Locations Map Document.

1. Launch ArcCatalog and navigate to the folder where updated map documents are placed using the catalog tree.

2. Right click on the map document, and choose theShare as Service option.

The command launches ArcMap on a new window and opens the Share as Service wizard.

3. Choose the Publish a service option then click Next.

4. Select the ArcGis server from the Choose a Connection drop-down, and click Next.

- Use the folder that was created when the map document was published.

- In the Service Editor wizard capabilities, choose the feature access capability enabled so that the features in Work Locations layer can be modified.

5. The continue button launches the Service Editor wizard. The wizard provides many options to increase the number of map instances and capabilities. The default values for the parameters can be kept as is.

6. Click on Publish button in the service editor wizard to publish the map document as service.

A progress bar is displayed during the package / service definition creation process.

7. Once service is published, The wizard displays a message that the service is published successfully.

8. Using the web browser and ArcGIS Server REST directory link https://<server name>:6443/arcgis/rest/services/<Folder Name>, the published map service can be viewed.

Clicking on the Map Server link will display the layers that are configured in the service.

2. Publish the Map Notes Map Document.

- Complete the steps as described above on the map document, MapNotes_Updated.mxd.

- Use the folder that was created when the map document was published.

- In the Service Editor wizard capabilities, choose the feature access capability enabled so that the features in Map Notes layer can be modified.

- Complete the remaining steps as described above.

Create and Publish Web Maps in Portal

Using map services and feature services that have been published, configure web maps as needed for use with WAM. Include the Work Locations and Map Notes services. Then configure access to the web maps.

Connect Portal for ArcGIS with Enterprise LDAP

This section provides guidelines for connecting Portal for ArcGIS with Enterprise LDAP.

The integration of Portal for ArcGIS with Enterprise LDAP ensures that the users in an organization need to be created / managed in the Portal page. Authentication will happen using LDAP. The configurations that need to be applied in Portal for ArcGIS are detailed in this section.

1. Login with the administrator account(Ex: gisadmin); navigate to My Organization tab and click on Edit Settings.

2. Verify that the portal is accessible through HTTPS protocol only by navigating to the Security tab and checking the Allow access to the portal through HTTPS only check box.

3. Update the identity store to configure the LDAP settings by navigating to the portal admin page: https://<Server Name>/arcgis/portaladmin/login.

Use the initial administrator account to login to the Portal Administrator Directory page.

4. Navigate to the Update Identity Store page located at Home ->Security -> Config -> Update Identity Store.

5. Configure the JSON accordingly:

{

"type": "LDAP",

"properties": {

"userPassword": "weblogic",

"caseSensitive": "false",

"userEmailAttribute": "description",

"usernameAttribute": "uid",

"user": "cn=Admin",

"userFullnameAttribute": "cn",

"ldapURLForUsers": "ldap://slc07zjq.us.oracle.com:7001/ou=people,ou=myrealm,dc=base_domain",

"isPasswordEncrypted": "true",

"userSearchAttribute": "uid"

}

}

In the above configuration, ldapURLForUsers refers to the URL that the portal to check with for authenticating the users. user and userPassword refers to the administrator credentials to connect to the LDAP store. For more information about the above mentioned parameters, refer to http://server.arcgis.com/en/portal/latest/administer/linux/use-your-portal-with-ldap-and-web-tier-authentication.htm.

Next in This Section

- Import Users to Portal for ArcGIS

This section provides guidelines for importing existing users from Portal for ArcGIS.

Import Users to Portal for ArcGIS

This section provides guidelines for importing existing users from Portal for ArcGIS.

This section describes how to add users one at a time. Users can also be imported in bulk as long as the Portal for ArcGIS license is Enterprise level.

1. Launch the Portal for ArcGIS home page and log in with the administrator account that was created in the earlier section and navigate to My Organization tab.

2. Click on Add Members button.

The wizard for adding members launches showing:

- Add built in users — choose if the users are to be created manually.

- Add members for enterprise logins via SAML — choose if SAML is configured to authenticate the users.

- Add members based on existing enterprise users — choose if users are to be imported from configured LDAP.

3. Choose option 3 and click Next.

4. Add Users.

1. To import the user one at a time, use the Find option to select the user from the list of users.

2. The Find User interface brings up the list of available users from the configured LDAP.

3. Select each user from the list and click the Select User button to add.

4. Optionally, Find user text box can be used to find out the user of interest from the list of users.

5. Once the user is selected, the wizard enables the option to choose the role for the selected user.

5. Click the Review Additions button.

The wizard displays the list of identified resources for verification.

6. Once the review is complete, click on Add Members button.

7. Clicking on Add Members button adds the user to Portal users with the specified role and wizard will take back to My Organization tab.

GIS Configuration Steps in Oracle Utilities Work and Asset Management

The following sections provide guidelines for the configuration steps that need to be completed in the Oracle Utilities Work and Asset Management application.

Next in This Section

- GIS Batch Processing

- Configure Extendable Lookups

Configure the following extendable lookups:

- Create Message Senders

This section provides guidelines for configuring message senders.

- Create Outbound Message Types

This section provides guidelines for creating outbound message types.

- Create GIS External System

This section provides guidelines for configuring external systems.

- Set Up Master Configuration

This section provides guidelines for setting the master configurations required in Oracle Utilities Work and Asset Management.

GIS Batch Processing

The following batch process need to run to sync data from GIS to WAM:

- W1-DELVR: GIS Delete Version

This multi-threaded batch process is responsible for communicating to the GIS system to delete the version that was created while retrieving the GIS ID's and data from the system. This will also update the One-time Data Conversion value in the ESRI WAM Integration Master Configuration to Complete after the initial load process is completed.

- W1-GISID: Retrieve GIS IDs

This multi-threaded batch process is responsible for communicating to the GIS system and retrieving the GUID's grouped by feature classes (configured in the GIS to WAM extendable lookup BO) from the GP service program that would be deployed in the Esri server.

- W1-PRGIS: Process GIS Data

This multi-threaded batch process is responsible for communicating to the GIS system with the GIS ID’s returned from the batch job, W1-GISID, and retrieving the data for each GUID and creating the composite sync request (W1-CompositeSyncReqGISAsset).

- W1-CMSYN: Composite Sync Request

When a composite sync request is created by W1-PRGIS and is in PENDING state, W1-CMSYN also needs to be run. This creates Location and Asset Sync requests. If the One-time Data Conversion value in the ESRI WAM Integration Master Configuration is set to Convert all Esri data then the request is an Initial Load and W1-InitialSyncRequestLocation sync request records are in created for locations. If the value of One-time Data Conversion is set to Complete then the sync is an Incremental Load and W1-OngoingSyncRequestLocation sync request records are in created for locations.

Additionally, the following processes are needed based on the event indicated:

- For processing Location sync request records (W1-InitialSyncRequestLocation) execute the following:

- F1-SYSRQ – When W1-InitialSyncRequestLocation records are in PENDING state.

- F1-SAKRQ - When W1-InitialSyncRequestLocation records are in DATA-TRANSFD state.

- W1-SIKSP - When W1-InitialSyncRequestLocation records are in KEY-ALLOCATD state.

- W1-SILSP - When W1-InitialSyncRequestLocation records are in KEYS-RESOLVD state.

- W1-SILDD – When W1-InitialSyncRequestLocation records are in LOADED state.

- For processing Location sync request records (W1-OngoingSyncRequestLocation ) during Incremental Load execute the following:

- W1-SIOPE - When W1-OngoingSyncRequestLocation records are in PENDING state.

- For processing asset sync request records (W1-InitialSyncRequestAsset) execute the following:

- F1-SYSRQ - When W1-InitialSyncRequestAsset records are in PENDING state.

- F1-SAKRQ - When W1-InitialSyncRequestAsset records are in DATA-TRANSFD state.

- W1-SIKAS - When W1-InitialSyncRequestAsset records are in KEY-ALLOCATD state.

- W1-SILAS - When W1-InitialSyncRequestAsset records are in KEYS-RESOLVD state.

- W1-SILDD - When W1-InitialSyncRequestAsset records are in LOADED state.

Note: Always run location sync request batch jobs first and then asset sync request batch jobs.

Configure Extendable Lookups

Configure the following extendable lookups:

Navigate to the Extendable Lookup portal under the Admin menu and add or update the Esri Web Maps lookup.

This step is required before you can Set Up Master Configuration.

- Esri Web Maps: (F1-EsriWebMap)

Configure web maps using the “Esri Web Maps” extendable look up. Every web map has a unique identifier – this value should be used as the key.

Ex: “Water Distribution Network”.

- GIS Projected Coordinate Systems: (W1-GISProjectedCoordinateSys)

This lookup provides the default projected coordinated system needed to ensure that the proper coordinate model is used in your map. This is referenced on the Esri WAM Integration Master Configuration.

- GIS to WAM Sync Mapping: (W1-GISToWAMSyncMapping)

This lookup provides the values needed for inbound synchronization from Esri to WAM.

A record is needed for each feature class which will be mapped into WAM. Use this record to specify default values for Asset Type and Asset Location Type, as well as specific field mappings.

- WAM To GIS Sync Mapping: (W1-WAMToGISSyncMapping)

This lookup provides the values needed for outbound synchronization from WAM to Esri.

A record is needed for each WAM Asset Type which will support attribute updates flowing back to GIS.

Create Message Senders

This section provides guidelines for configuring message senders.

Navigate to the Message Senders portal under the Admin menu. Add or update message senders according to the following.

Work Location Sync: Main (SOAP)

Field

Value

Message Sender

ESRIWLSNDR

Description

Work Location to ESRI

Invocation Type

Real-time

Message Class

RHTTPSNDR (Send post messages via HTTP real-time)

Active

Yes

MSG Encoding

UTF-8 message encoding

Work Location Sync: Context (SOAP)

Context Type

Context Value

HTTP Method (POST/GET)

POST

HTTP URL 1

Set to Work Location feature server.

Ex: https://...WorkLocations/MapServer/FeatureServer

Work Location Sync: Main (REST)

Field

Value

Message Sender

ESRIWLSNDR

Description

Work Location to ESRI

Invocation Type

Real-time

Message Class

RTJSONSNDR (Sender for real-time HTTP/JSON messages)

Active

Yes

MSG Encoding

UTF-8 message encoding

Work Location Sync: Context (REST)

Note: The URL for REST should always use applyEdits for the common xsls that are delivered out of the box.

Context Type

Context Value

HTTP Method

POST

HTTP URL 1

<To be provided by ESRI team>

Ex: https://den02bvz.us.oracle.com:6443/arcgis/rest/services/WAM/WorkLocations_W22000Dev/FeatureServer/0/applyEdits?f=pjson

HTTP Header

Content-Type:application/x-www-form-urlencoded

HTTP Header

Accept:application/json

HTTP Header

application/json

HTTP Form Data

adds=@XMLMSG@

Asset Sync: Main (SOAP)

Field

Value

Message Sender

ESRIASTSNDR

Description

Asset to ESRI

Invocation Type

Real-time

Message Class

RHTTPSNDR (Send post messages via HTTP real-time)

Active

Yes

MSG Encoding

UTF-8 message encoding

Asset Sync: Context (SOAP)

Context Type

Context Value

HTTP Method (POST/GET)

POST

HTTP URL 1

Set to Map Server feature server.

Ex: https://.../arcgis/services/WAM/WaterDistributionNetwork/MapServer/FeatureServer

Asset Sync: Main (REST)

Field

Value

Message Sender

ESRIWLSNDR

Description

Asset to ESRI

Invocation Type

Real-time

Message Class

RTJSONSNDR (Sender for real-time HTTP/JSON messages)

Active

Yes

MSG Encoding

UTF-8 message encoding

Asset Sync: Context (REST)

Note: The URL for REST should always use applyEdits for the common xsl’s that are delivered out of the box.

Context Type

Context Value

HTTP Method

POST

HTTP URL 1

<To be provided by ESRI team>

Ex: https://slc12pjb.us.oracle.com:6443/arcgis/rest/services/WAM/WaterDistributionNetwork/FeatureServer/applyEdits?f=pjson

HTTP Header

Content-Type:application/x-www-form-urlencoded

HTTP Header

Accept:application/json

HTTP Header

application/json

HTTP Form Data

Edits=@XMLMSG@

Create Outbound Message Types

This section provides guidelines for creating outbound message types.

Navigate to the Outbound Message Types portal under the Admin menu. Add or update outbound message types according to the following:

Work Location – Add

Field

Value

Outbound Message Type

WL-ADD

Description

GIS Work Location - Outbound message type

Detailed Description

Sends work location details to ESRI

Business Object:

W1-GISWorkLocSyncReqOutMsg

Priority BO

50

Asset - Update

Field

Value

Outbound Message Type

ASSET-UPDATE

Description

GIS Asset - Outbound message type

Detailed Description

Sends asset details to ESRI

Business Object:

W1-GISAssetSyncReqOutMsg

Priority BO

50

Create GIS External System

This section provides guidelines for configuring external systems.

Navigate to the External System portal under the Admin menu. Add or update external systems according to the following:

Main

Field

Value

External System

GIS

Description

GIS system

Our Name in Their System

WAM

GIS Work Location - Outbound Message Type (SOAP)

Field

Value

Outbound Message Type

GIS Work Location - Outbound message type

Processing Method

Real-time

Message Sender

ESRIWLSNDR

Date/Time Format

XSD

Batch Control

N/A

Message XSL

W1-GISWorkLocation.xsl

W3C Schema

<Leave Blank>

Response XSL

W1-GISWLResponse.xsl

GIS Asset - Outbound Message Type (SOAP)

Field

Value

Outbound Message Type

GIS Asset - Outbound message type

Processing Method

Real-time

Message Sender

ESRIASTSNDR

Date/Time Format

XSD

Batch Control

N/A

Message XSL

CM-GISAsset.xsl

W3C Schema

<Leave Blank>

Response XSL

CM-GISAssetResponse.xsl

Note: Note: The xsl files are not delivered and must be created according to yourAsset layers in ESRI.

GIS Work Location - Outbound Message Type (REST)

Field

Value

Outbound Message Type

GIS Work Location - Outbound message type

Processing Method

Real-time

Message Sender

ESRIWLSNDR

Date/Time Format

<Leave Blank>

Batch Control

N/A

JSON Conversion Method

XSL Transformation

Message XSL

W1-CommonGISRequestForREST.xsl

W3C Schema

<Leave Blank>

Response XSL

W1-CommonGISResponseForREST.xsl

GIS Asset - Outbound Message Type (REST)

Field

Value

Outbound Message Type

GIS Asset - Outbound message type

Processing Method

Real-time

Message Sender

ESRIASTSNDR

Date/Time Format

<Leave Blank>

Batch Control

N/A

JSON Conversion Method

XSL Transformation

Message XSL

W1-CommonGISRequestForREST.xsl

W3C Schema

<Leave Blank>

Response XSL

W1-CommonGISResponseForREST.xsl

Set Up Master Configuration

This section provides guidelines for setting the master configurations required in Oracle Utilities Work and Asset Management.

Prerequisites:

- The extendable lookup for web maps must be configured.

- Portal for ArcGIS or ArcGIS Online is installed and configured.

1. Navigate to the Master Configuration portal under the Admin menu.

2. Add or update Esri Maps Master Configuration.

This master configuration defines maps and default map positioning and zoom when the GIS viewer is launched.

3. Add or update Esri WAM Integration Master Configuration .

These master configuration objects define the map viewer integration with the application.

Table Setup Sequence

This section provides a checklist of the primary data that must be configured as part of your implementation. This can be used as a useful map of the relationship between objects in the system.

It includes:

- Listing of the objects that must be defined as part of the setup process

- Identification of the order in which objects should be defined and any prerequisites for setup

- Identification of any custom lookups that must be defined in relationship to each setup object

- Identification of objects associated with or referenced by each setup object

Setup Sequence

Use the following tables as your roadmap for creating system data.

Here we list the order in which you perform tasks and the pages you'll use to set up your system. The order is important because some information must exist before other information can be defined (i.e., many dependencies exist).

Note: The sequence in which you configure system objects is important. By following this sequence carefully, you can streamline the configuration process and reduce the amount of time required for setup.

In the setup tables, the Sequence column displays the following codes:

- L1 = No setup prerequisites. These should be defined before the remaining objects.

- L2 = Some L1 prerequisites. These should be defined after all L1 objects and before L3 objects.

- L3 = Defined after all L1 and L2 objects.

- L4 = Defined after all L1, L2, and L3 objects.

- L5 = Defined after all L1, L2, L3, and L4 objects.

Next in This Section

- Control Data Setup

To implement the system, you must set up your organization's business rules in "control tables". Setting up these tables is time-consuming because we allow you to tailor many aspects of the system to meet your organization's requirements. We strongly recommend that you take the time to document how you plan to set up all of these tables before you use the following roadmap to enter the control data. Time spent understanding the interrelationships between this data will reap the rewards of a clean system that meets your current and long term needs.

- Master Data Setup

These objects are typically defined during initial system setup and are then updated regularly as new updates are needed.

Control Data Setup

To implement the system, you must set up your organization's business rules in "control tables". Setting up these tables is time-consuming because we allow you to tailor many aspects of the system to meet your organization's requirements. We strongly recommend that you take the time to document how you plan to set up all of these tables before you use the following roadmap to enter the control data. Time spent understanding the interrelationships between this data will reap the rewards of a clean system that meets your current and long term needs.

Next in This Section

- OUAF Control Data Setup

These setup tasks are typically performed by an administrative user and are accessed from the Admin menu. Most of these objects establish global configuration. They are defined at implementation and usually do not change again.

- General Control Data Setup

These setup tasks are typically performed by an administrative user and are accessed from the Admin menu. These objects are defined at implementation and are only updated as needed when system configuration or foundation data changes. In general these objects establish he “Type” upon which the master data objects are based.

- Approval Processing Control Data Setup

One of the ways that the system simplifies and speeds up work is by routing records when they require approval. For example, purchase requests, work requests, employee leave, and other functions can be configured to require approvals.

- Financial Control Data Setup

Financials management involves creating and managing entities such as expense codes, distribution codes, cost centers, cost categories, tax rate schedules, accounting calendars, and so on.

- Resource Control Data Setup

Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on.

- Inventory Control Data Setup

Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. Materials are purchased and received, then as that inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available.

- Work Management Control Data Setup

Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked.

- Asset Control Data Setup

The Oracle Utilities Work and Asset Management system provides functionality to configure assets

- Construction Work Management Control Data Setup

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

- Purchasing Control Data Setup

Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items.

OUAF Control Data Setup

These setup tasks are typically performed by an administrative user and are accessed from the Admin menu. Most of these objects establish global configuration. They are defined at implementation and usually do not change again.

Seq

Object

Description

Prerequisites

Framework Administration Guide Reference

L1

Country

Your organization's country.

None

Defining Countries

L1

Currency

Your organization'snative currency.

None

Defining Currency Codes
The overall system uses the base currency defined in Installation Options, and all financial transactions use the base currency. However, the purchasing system supports other currencies which can be defined in the Currency portal.

L1

Display Profile

Controls how dates, times, and numbers displayed.

None

Defining Display Profiles

L1

Language

The language to use for this implementation.

None

Defining Languages

L1

Time Zone

Your organization’s base time zone.

None

Defining Time Zones

L1

To Do Role

Used to associate users with To Do entries.

None

Defining To Do Roles

L1

Work Calendar

The work calendar for your organization, which identifies your public holidays.

None

Defining Work Calendar

L1

Geographic Type

If your company uses geographic coordinates for dispatching or geographic information system integration, you need to setup a geographic (coordinate) type for each type of geographic coordinate you capture for assets.

None

Defining Geographic Types

L1

Outbound Message Type

Establishes a categorization for outbound messages.

Business Object and Schema

Defining Outbound Message Types

L1

Extendable Lookups

The "lookup" table is a single table that holds valid values for many columns on many tables. Extendable lookups are custom fields where valid values are limited to a predefined list.

None

Defining Extendable Lookups

L1

Lookups

The "lookup" table is a single table that holds valid values for many columns on many tables. Lookups are custom fields where values can be added. Only lookups where the “Custom” flag is checked can be modified.

None

Defining Lookup Options

L2

Feature Configuration

Add a feature configuration of feature type ‘Schema Constants’ and set the value for ‘Default Country’.

Country

Defining Feature Configurations

L2

Installation Options

Control various aspects of the system. You must set up ‘Address Information’ and ‘Global Context’ algorithms.

Time Zone, Language, Currency

Defining Installation Options

L2

Master Configuration

Enables an implementation to capture various types of information in the system.

None

Defining Master Configurations

L2

To Do Type

Used to define types of To Do Entries.

To Do Role

Defining To Do Types

L2

Global Context Algorithm

You will need to set up an algorithm that populates global context values. The global context is used by various zones in the system to display relevant data. This algorithm is plugged-in on the installation record.

Global Context Overview

L2

Characteristic Types & Values

If you need to introduce additional fields to objects that were delivered with minimal fields, you can add a characteristic type for each field you want to capture.

None

Setting Up Characteristic Types & Values

L2

External System

If you are using an integration you must configure the external system in this portal.

Outbound Message Type

External Systems

L3

Phone Type

Defines the phone number format to use throughout the system.

Phone Number Format Algorithm

Defining Phone Types

Security Setup

Refer to Defining Security & User Options for more information.

Object

Description/Notes

Framework Administration Guide Reference

Application Service

All base package transactions are automatically populated

Defining Application Services

Security Type

Only needed if field-level security is being implemented

Defining Security Types

User Group

A group of users who have the same degree of security access.

One user group, ALL-SERVICES, is automatically setup. This group references all other application services and a single user called SYSUSER.

WAM also provides two additional user groups, WAM_SERVICES and ODM_SERVICES.

Note, you may be able to import sample user groups from the demonstration database. Also, you may be able to import user groups if your organization has already defined them using LDAP.

Note, you won't be able to set up users at this point

Defining User Groups

Data Access Role

Used to provide rights to Access Groups (Owning Organization)

Defining Data Access Roles

Access Group

Used to provide data segregation by ‘Owning Organization’ which is found on most objects in WAM.

Defining Access Groups

User

Defines a user’s user groups, data access roles, portal preferences, default values, and To Do roles.
SYSUSER is automatically set up, along with WAM_USER and ODM_USER. Note, you may be able to import your users if your organization has already defined them using LDAP.

You must return to your user groups and define all of their users.

Defining Users

General Control Data Setup

These setup tasks are typically performed by an administrative user and are accessed from the Admin menu. These objects are defined at implementation and are only updated as needed when system configuration or foundation data changes. In general these objects establish he “Type” upon which the master data objects are based.

For more detailed information on the functionality related to the objects described, refer to the related section in this guide.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Communication Type

None

Inbound Communication

L1

Statistic

None

Home Page

L1

Color

None

Cost Category
Related Master Configuration must be configured.

L2

Inbound Communication

Communication Type

Completion Event Type
Completion Event

Note: this option is on the Work Management menu under Menu.

L5

Attachment

Attachment BO

Completion Event

Assets

Configuration

Specifications

Locations

Service History

Warranty

Note: it is recommended that you use Document Types and Documents instead of attachments in Oracle Utilities Work and Asset Management.

Approval Processing Control Data Setup

One of the ways that the system simplifies and speeds up work is by routing records when they require approval. For example, purchase requests, work requests, employee leave, and other functions can be configured to require approvals.

Refer to Understanding Approval Processing Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

To Do Types (for Approvals)

OUAF Setup

Approval Profile

L1

To Do Roles (for Approvals)

OUAF Setup

Approval Profile

L1

User Group (for Approvals)

OUAF Setup

Approval Profile

L2

Approval Profile

To Do Type

To Do Role

User Group

System-Wide
Refer to the Defining the Approval Hierarchy section for examples of profiles to create.

Related Master Configuration must also be configured.

Financial Control Data Setup

Financials management involves creating and managing entities such as expense codes, distribution codes, cost centers, cost categories, tax rate schedules, accounting calendars, and so on.

Refer to Understanding Financials Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Accounting Calendar

None

Related Master Configuration must also be configured.

L1

Cost Center

None

Expense Code
Business Unit

Tax Rate Schedule

Employee Unavailability Type

Related Master Configuration must be configured.

L1

Factor and Factor Value

None

Tax Rate Schedule

L1

Distribution Code

GL Account
Construction Algorithm

Financial Transactions
Related Master Configuration must also be configured.

L2

Cost Category

Color

Asset Type
Expense Code

L2

Expense Code

Cost Category

Tax Rate Schedule

Employee Unavailability Type

Related Master Configuration must also be configured.

L3

Tax Rate Schedule

Factor

Cost Center

Expense Code

Purchase Requisition

Purchase Order

Blanket Contract

Stock Item

Related Master Configuration must also be configured.

Resource Control Data Setup

Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on.

Refer to Understanding Resource Management Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Contact Type

None

Locations

L1

Unit of Measurement — Resource

Resource Class
(custom lookup)

Stock Item

Equipment

Miscellaneous Resource

Craft

L1

Organization Type

None

Organization
Asset Location Type

Storeroom Type

L1

Service Class

None

Crew Shift

Activity Type

Crew

L1

Service Area

None

Asset Location

Asset

Employee

Crew Shift

L1

Document Type

None

Document

L1

Employee Type

None

Employee

L1

Crew Shift Type

None

Crew Shift

L1

Crew Type

None

Crew

L2

Business Unit

Payroll Cost Center

Employee

L3

Employee Unavailability Type

Cost Center

Expense Code

Employee Unavailability

Inventory Control Data Setup

Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. Materials are purchased and received, then as that inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available.

Refer to Understanding Inventory Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Storeroom Type

None

Storeroom

L2

Commodity Code

None

Stock Item

Work Management Control Data Setup

Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked.

Refer to Understanding Work Management Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Project Category

None

Project

L1

Time Periods

None

System-Wide for timekeeping

L1

Labor Earning Type

None

Timesheet

L1

Overtime Type

None

Timesheet

L2

Completion Event Type

Activity Type

Activity Type

L2

Activity Type

Completion Event Type
Service Class

Category (custom lookup)

Activity

L2

Maintenance Manager

User ID

Work Order

L2

Planner

User ID

Work Order
Template Work Order

Statistics

Related Master Configuration can be configured for home page metrics.

L3

Failure Profile (Failure Cause, Modes, Repair, Component)

None

Preventive Maintenance
Asset Type/Component Type

Asset Control Data Setup

The Oracle Utilities Work and Asset Management system provides functionality to configure assets

Refer to Understanding Asset Management Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Measurement Identifier

- Unit of Measure (characteristic type)

- Time of Use (characteristic type)

- Special Identifier (lookup)

Measurement Type
Measurement Type Identifier (custom lookup)

L1

Question
( Condition Assessment )

None

Service History Type

L2

Configuration Type
(ODM)

Configuration Type BOs and Lookups

- Configuration Type BO

- Configuration Class

- Configuration Category

Configurations

Asset

Configuration Class (custom lookup)

L2

Measurement Type

Measurement Identifier

Measurement

L2

Service History Type

Condition Assessment Question

Service History
Asset Type

Condition Assessment

Activity Type

L2

Asset Location Type

Parent Asset Location
Organization Type (optional)

Asset Type

L2

Out of Service Location Type

Organization (optional)

Parent Storeroom Type

Asset Type

L2

Maintenance Plan

Event Category (custom lookup)

L3

Condition Assessment Group

Service History Type

Condition Assessment Class

L4

Condition Assessment Class

Condition Assessment

Vehicle Assessment
Building Assessment

L5

Asset Type/Component Type

Location Type

Service History Type

Assessment Class

Failure Profile

Asset Location Type

Asset

Construction Work Management Control Data Setup

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

Refer to Understanding Construction Work Management Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Notes

L1

Property Unit

None.

Compatible Units

L1

Cost Center

L1

CU Category

CU Class (custom lookup)

L2

Equipment Group

CU Category

L2

CU Usage

Cost Center (capital account)

L2

Resource Type for Contractor Service

None.

Related Work Management Master Configuration must be configured with a Resource Type for Contractor Service.

L2

Overhead

Resources

- Material

- Labor

- Equipment

- Miscellaneous Resource

Resource Types needed on Overhead are meant for indirect overhead. They are used to create Other Direct Charges to account for the overhead adjustments.

L2

Service Class (construction or construction overhead)

Cost Center

Typically this is the default Work In Progress (WIP) account.

L3

Construction Work Activity Types

Service Class (construction or construction overhead)

Craft

Related Financial Master Configuration must be configured with a Reconciliation Distribution Code.

L3

Crew Type

Craft (optional)

Equipment (optional)

L3

Approval Profiles

Refer to Approval Processing Control Data Setup

Create Approval Profiles and To Do Types to be used for approval processing.

Create Approval Profiles for Construction Activity Reconciliation and Construction Work Order. The base package includes a unique To Do Type for each maintenance object such as Activity Reconciliation. Your implementation will need to configure To Do Roles as required by your business.

Purchasing Control Data Setup

Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items.

Refer to Understanding Purchasing Configuration for more specific configuration guidelines related to these objects.

Seq

Object Type

Prerequisites

Associated with / Referenced by

L1

Capability Type

None

Vendor Capability (on the Vendor record)

L1

Payment Terms

None

Vendor

L1

Free on Board

None

Vendor

L2

Buyer

User ID

Purchase Commodities

Related Master Configuration can be configured for home page metrics.

L3

Purchase Commodity

Buyer

Stock Item

Related Master Configuration can be configured for home page metrics.

Master Data Setup

These objects are typically defined during initial system setup and are then updated regularly as new updates are needed.

For more detailed information on the functionality related to the objects described, refer to the “User Guide” section in the online help or printed user’s guide.

Note: All basic Framework setup, including system and database setup and any modifications or extensions to base business objects, must have been completed before beginning these setup tasks.

To access the maintenance portals for the following objects, select Menu >[submenu]>[object name].

The chapters related to the functionality related to these objects in the remainder of this guide are organized in order the same order as indicated by this sequence.

Next in This Section

- Resource Master Data Setup

Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on.

- Purchasing Master Data Setup

Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items.

- Inventory Master Data Setup

Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. Materials are purchased and received, then as that inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available.

- Asset Master Data Setup

The Oracle Utilities Work and Asset Management system provides functionality to configure assets

- Work Management Master Data Setup

Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked.

- Construction Work Management Master Data Setup

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

Resource Master Data Setup

Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on.

Refer to Understanding Resource Management Configuration for more specific configuration guidelines related to these objects.

Seq

Resource Object

Prerequisites

Example/Notes

L2

Document

Document Type
Category (custom lookup)

Document Attachments

Standard Notes

URLs

L2

Organization

Organization Type
Parent Organization (optional)

L2

Contacts

Contact Type

Business Contact

Person Contact

- Employees

- Vendors

L3

Crafts

Resource UOM — Non material class

Expense Code

L3

Equipment

Resource UOM — Non material class

Cost Center

Expense Code

L3

Miscellaneous Resources

Resource UOM — Non material class

Cost Center — Typically the type that does not allow user charges

Expense Code

L3

Employee

Employee Type

User ID

Craft

Business Unit

Service Area

Course (custom lookup)

Employee Information

Employee Billable Rate

L4

Crews

Crew Type

Employee

L5

Crew Shifts

Crew

Crew Shift Type

Schedule Plan Template

Employee

Service Class

Service Area

Crew Shift Template

Daily Schedule

Schedule Plan

Crew Shift with Activity Schedules

Related Master Configuration must also be configured.

L5

Shift Plan Templates

Crew

Schedule Plan Type

Work Calendar

Shift Plan Templates

Common Shift Plan Template

Subscription Shift Plan Template

Purchasing Master Data Setup

Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items.

Refer to Understanding Purchasing Configuration for more specific configuration guidelines related to these objects.

Seq

Purchasing Object

Prerequisites

Examples/Notes

L1

Manufacturer

None

L1

Vendor

None

L2

Vendor Locations

Vendor

L3

Blanket Contract Access List

User ID

L4

Blanket Contracts/w Line Items

Stock Items

Blanket Contract Access List

Vendor

Payment Terms

Cost Center

Inventory Master Data Setup

Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. Materials are purchased and received, then as that inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available.

Refer to Understanding Inventory Configuration for more specific configuration guidelines related to these objects.

Seq

Inventory Object

Prerequisites

Examples/Notes

L2

Storeroom

Storeroom Type

Contact (optional)

Organization (optional)

Storeroom

Storeroom with Inventory Management

L3

Stock Items

Resource UOM

Usage Expense Code

Inventory Expense Code

Purchase Commodity

Commodity Code

Vendor Location

Manufacturer

Stock Item Category (custom lookup)

L3

Stock Item Details

Stock Item

Storeroom

Cost Center

Buyer

Vendor

Bin Information

Stock Item Detail - Inventory

Stock Item Detail - Direct Purchase

Stock Item Detail - Specific Direct Purchase

Stock Item Detail - Specific Lot

Stock Item Detail - Expensed At Receipt

L4

Material Request Template

Storeroom Location

Stock Item Detail

Expense Code

L4

Reorder Review

Stock Item Detail

Related Master Configuration must also be configured.

Asset Master Data Setup

The Oracle Utilities Work and Asset Management system provides functionality to configure assets

Refer to Understanding Asset Management Configuration for more specific configuration guidelines related to these objects.

Seq

Asset Object

Prerequisites

Examples/Notes

L2

Assets

Asset Type

Tracked General Assets

Tracked IT Asset / In Out Service IT Asset

In Out of Service General Asset

In Out of Service Infrastructure Asset

Communication Component

Communication Relay

L2

Components (Asset Components)

Asset Type

In/Out of Service General Component

In Out Service IT Component

Operational Device Tracked Component

Tracked General Component

Tracked IT Component

L2

Vehicles (Fleet Assets)

Asset Type

In Out Service Fleet Asset

L2

Operational Devices (Assets)

Asset Type

Operational Device Tracked Asset

Operational Device In/Out of Service Asset

Smart Meter

Manual Meter

L2

Asset Location

Asset Location Type

Site Location (custom lookup)

RCM System(custom lookup)

General Asset Location

Linear Asset Location

Plant Asset Location

Service Point

Operational Device Asset Location

L2

Out of Service Location

Out of Service Location Type

Warehouse

Repair Shop

L2

Configuration (Asset Configuration — ODM only)

Configuration Type

Single Asset Configuration

Asset/Component Configuration

Asset to Asset Configuration

Asset/Component to Asset Configuration

Asset to Asset/Component Configuration

Asset/Component to Asset/Component Configuration

L2

Operational Reading

Measurement Type

Measurement Numeric Gauge Reason (custom lookup)

L3

Bills of Materials

Stock Item

General Stock Item

Independent Part BOM

L3

Warranty Term

Vendor

Calendar Warranty Term

Runtime Warranty Term

L3

Specification

Specification BO

Asset Type

Manufacturer

BOM ID

Maintenance Schedule (as applicable)

L3

Fleet Specification

Vehicle Detail (custom lookups)

L3

Service History

Activity

Failure Profile

Deficiency (custom lookup)

General Weighted (custom lookup)

Percent of New (custom lookup)

Asset Disposition (custom lookup)

Downtime Reason (custom lookup)

General

Preventive Maintenance

Inspection

Operational Device

L4

Warranty

Warranty Term

Calendar Warranty

Runtime Warranty

L4

Configuration Reports (Asset Configuration — ODM only)

Configuration Report BOs
Specification

Reporting Mode (custom lookup)

Single Asset

Asset/Component

Asset to Asset

Asset/Component to Asset

Asset to Asset/Component

Asset/Component to Asset/Component

Work Management Master Data Setup

Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked.

Refer to Understanding Work Management Configuration for more specific configuration guidelines related to these objects.

Seq

Work Management Object

Prerequisites

Examples/Notes

L1

Preventive Maintenance Calendar

None

L1

Maintenance Event Plan

None

L2

Preventive Maintenance Schedule

Asset Type

Maintenance Schedule

L2

Work Order Template

Planner

Approval Profile

Work Class (custom lookup)

Work Category (custom lookup)

Work Priority (custom lookup)

General Template Work Order

Asset Location Specific Template Work Order

Note: Refer to special instructions for the work priority field.

L3

Preventive Maintenance Trigger

Maintenance Trigger Business Object

Maintenance Schedule

Template Work Order

Activity Type

Service History Type

Service Class

Approval Profile

Outage Type (custom lookup)

Backlog Group (custom lookup)

Asset Condition

Asset Location

Calendar Anniversary

Calendar Interval

Runtime Anniversary

Runtime Interval

Asset Location Maintenance Trigger

L3

Maintenance Event Plan Trigger

Maintenance Plan

Template Work Order

Activity Type

Service History Type

Work Priority

Service Class

Approval Profile

Asset Location

L4

Template Activity

Resources

General Template Activity

Asset Location Specific Template Activity

L5

Activity

Activity Type

Completion Event Type (as applicable)

Storeroom

Asset

Project

Work Order

Service Class

Cost Center

Phase (custom lookup)

Crew (as applicable)

Backlog Group (custom lookup)

L5

Work Order

Project

Cost Center

Crew

Planner

Criticality (custom lookup)

Work Class (custom lookup)

Work Category (custom lookup)

Work Priority (custom lookup)

Note: Refer to special instructions for the work priority and criticality fields.

Related Master Configuration must also be configured.

Construction Work Management Master Data Setup

Oracle Utilities Construction Work Management provides functionality to manage the work, resources, and assets related to construction work.

Refer to Understanding Construction Work Management Configuration for more specific configuration guidelines related to these objects.

Seq

Construction Work Management Object

Prerequisites

Examples/Notes

L2

CU Set

CU Class (custom lookup)

CU Category

Equipment Group

L2

Capital Spare Stock Item

Refer to Inventory Master Data Setup

L2

Vendor / Vendor Location (Contractors)

None.

L3

Compatible Units

CU Set

Property Unit (for constructed asset)

Asset Type (for constructed asset — optional)

CU Condition (lookup)

CU Account Usage (lookup)

CU ID Type (lookup)

If populated, Asset Type on the CU indicates that the constructed fixed asset is also a WAM asset.

L3

Work Designs

Work Design Type (lookup)

Work Design Priority (lookup)

Work Design Phase (lookup)

Vendor Location (Contractor)

L4

Design Element

Price Type (lookup)

Responsibility Party (lookup)

Service Position (lookup)

Batch Control Configuration

Batch controls are used to process and organize information throughout the system. For example, reorder review relies upon batch processing to complete the reorder processing and generate the appropriate purchasing documents. Likewise, shift plan templates use batch patch processing to generate shifts and make updates to shift plans. This section describes the base package batch controls provided with Oracle Utilities Work and Asset Management.

Use the Batch Control portal and Application Viewer for more details about these batch controls.

To verify the status of a batch process you can check the Batch Job Submission portal and search for the related batch control. For example, if you have scheduled activities to be created by batch processing from a work order, you would search for W1-WO.

- Navigate to Main Menu > Batch > Batch Job Submission.

- Search for the appropriate batch control to find out the status of a job.

Refer to the Background Processes section in the Oracle Utilities Application Framework documentation for more information about tracking batch processes, the Batch Run Tree, and other functionality related to batch processing.

Next in This Section

- About Monitors

The main batch controls that might require configuration are monitors. Monitors determine when an event has taken place within the system and trigger another event in response. These may or may not require modification to the interval, or frequency of doing a status check on events and launching triggers.

- Oracle Utilities Work and Asset Management Batch Controls

It is important to properly manage the order and frequency with which batch processes are run. Below is a list of batch jobs which, if scheduled, must be in the order listed. These are recommended settings (not requirements) based on which aspects of the system you are using and your business practices.

About Monitors

The main batch controls that might require configuration are monitors. Monitors determine when an event has taken place within the system and trigger another event in response. These may or may not require modification to the interval, or frequency of doing a status check on events and launching triggers.

As a general rule, all monitors are executed the first time an entity enters a given state. After that event, the system relies upon the batch process configuration to determine when the process is called again.

Non-Timed Monitors

Monitor type batch controls can be configured with no defined timer interval so that they can be run whenever required. Typically, organizations that use a third-party software to manage monitoring and batch triggers would configure monitors in this way.

Timed Monitors

Monitor type batch controls that do not have third-party software to trigger the processes can use the simple processing in base package batch controls to launch the batches at whatever time interval is set as the timer interval.

Oracle Utilities Work and Asset Management Batch Controls

It is important to properly manage the order and frequency with which batch processes are run. Below is a list of batch jobs which, if scheduled, must be in the order listed. These are recommended settings (not requirements) based on which aspects of the system you are using and your business practices.

To find the details for batch controls, reference the Batch Control record and then look at the maintenanceObject Parameter.

Refer to Defining Batch Controls in the Oracle Utilities Application Framework documentation for information on controlling the order in which the processes run, scheduling processes, and other details.

Scheduled Monitor Processes

Batch controls are listed here in the general sequence that they should be run:

Batch Control

Description

Suggested Freq.

W1-FTM

Financial Transaction Periodic Monitor Process

Invokes monitoring rules associated with the current state of financial transactions. All monitoring rules throughout the financial transaction's business object's inheritance chain are considered.

By default, the process periodically monitors financial transactions whose current state is not associated with a batch code.

Batch parameters govern whether the processing is further restricted by batch code, business object and status.

This processing also transitions objects from Created status to Populate GL Details to Frozen, as applicable. If the system encounters errors, the object is transitioned to Error. For example the GL number might not be able to be generated because of an incorrect cost center/expense code combination. There is a monitor on the error state to try again.

The error state creates a To Do. Users can always manually try to freeze the FT. However if the issue that caused the error has been fixed, the monitor will take care of the FT and To Do before users take actions.

The W1-GLDL process, GL Download Extract, extracts and downloads the general ledger details.

Hourly.

W1-APVRQ

Approval Request Periodic Monitor Process

Manages transitioning of approval requests and routing them to the appropriate approvers. For example, if the current approver times out due to not responding in the alotted amount of time, this processing moves the approval request to the next approver.

Daily. Approver time out is defined as number of days.

W1-ACTRR

Activity Resource Requirement

Users can indicate a future ‘Reservation’ date on Material Requirements and the system will try to reserve the material when that date becomes current.

Run several times a day.

W1-ACT

Activity MO Periodic Monitor Process

Updates the activity Held For Parts flag based on availability in inventory. The monitor can be scheduled to re-evaluate the Held for Parts flag on all active activities against inventory quantity changes causes by stock re-order, material issue or return.

This monitor also auto-activates approved activities based on the Activation Date/Time on an activity which defines a future activation date. The system will activate the activity once it is both approved and the ‘Activation Date’ becomes current.

Daily. Available inventory changes by the hour, however your implementation should avoid running this batch job too often, as it places a heavy burden on the system.

W1-WO

Work Order MO Periodic Monitor Process

Causes the system to automatically close completed work orders after the indicated number of days after completion.

This is relevant for auto close and service schedules.

Daily.

W1-TMST

Timesheet MO Periodic Monitor Process

Posts approved timesheets to create financial transactions and entries in the general ledger.

Daily or weekly (if time period on timesheets is weekly).

W1-ODCTR

ODC MO Periodic Monitor Process

Posts approved direct charges to create financial transactions and to the general ledger.

Daily.

W1-COSTM

Cost Center Periodic Monitor Process

Calculates monthly and year to date statistics per cost center.

Note that users can also click a button online to calculate the statistics on demand.

Daily.

W1-ASTYP

Asset Type Monitor Process

Calculates asset type average cost statistics.

Daily.

W1-CRSHF

Crew Shift Periodic Monitor Process

Maintains crew shift status.

Daily.

W1-ASSET

Asset Periodic Monitor Process

Monitors preventive maintenance triggers to create the related work orders.

This monitor also creates PM Forecast records for the Asset. Your implementation can define the number of days to generate the future forecast, or planning horizon. For example, 1825 days would be 5 years of PM forecasts for all triggers. The planning horizon is controlled by a parameter on the W1-ASTMNTMON algorithm.

Daily.

W1-BCHDR

Blanket Contract Header Monitor Process

Transitions blanket contracts that are awaiting activation to Active when future blanket contracts become current.

Daily.

W1-SID

Stock Item Detail MO Periodic Monitor Process

Causes the stock item detail to monitor itself to check it’s reorder levels and creates the reorder review as necessary.

This batch control also monitors lot expiration dates.

Note that W1–SID is the batch job for reorder review, not W1–RR. W1–RR is the standard monitor batch control delivered with the reorder review maintenance object, however, it does not perform the processing of creating reorder review records.

Daily.

W1-BSRR

Batch Stock Reorder Monitor Process

Creates the purchasing documents based on reorder review records.

Daily. (after W1-SID)

W1-GLDL

GL Download Extract

Extracts and downloads the general ledger details by creating a flat file.

The GL batch control code is defined in the Financial Master Configuration.

Daily.

W1-STAT

Statistic Monitor Process

Calculates home page statistics.

Daily.

W1-SFWKT

Shft Wkly Templt Periodic Monitor Process

Creates new shifts based on templates.

Daily.

W1-COMIN

Inbound Communication Periodic Monitor Process (both ODM and WAM)

If an external system sends inbound communications to WAM, e.g. to complete activity, this batch job needs to be run to process those inbound communications. Base BO’s have a deferred monitor algorithm on the initial state, which moves the inbound communication to the next state and is only executed when the batch is run. The reason why that monitor is a deferred is to avoid error(s) upon creation of the message.

As often as needed.

W1-MTRDP

Material Disposition Monitor Process

Closes material dispositions after the assets have been processed (e.g. the new asset has been installed and the old asset have been either repaired and returned to a storeroom or retired).

Daily.

W1-SSWO

Svc Sched WO MO Periodic Monitor Process

ODM only— this monitor is only relevant to activity generators in ‘Template’ state.

Create activity generator, from a template, based on the schedule defined on service history.

Daily.

W1-MNTSC

Maintenance Schedule Periodic Monitor Process

Calculate preventive maintenance statistics. This batch job must run in order to generate the statistics that are displayed on the Analytics tab in the PM Schedule portal.

Daily.

W1-MNTTR

Maintenance Trigger Periodic Monitor Process

Calculate failure statistics.

Daily.

W1-WRNTY

Warranty Periodic Monitor Process

Monitor warranty, e.g. create To Do when a warranty is about to expire.

Daily.

W1-CUCTR

CU Contractor Bid Periodic Monitor Process

Moves CU Contractor Bids through various lifecycle states including activating the bid once it reaches its effective date and expiring it once the expiration date is reached.

Daily.

W1-FIXAS

Fixed Asset Extract

For use with construction work management functionality: An external Fixed Asset Management system which manages the depreciation of fixed assets can interface with Oracle Utilities Work and Asset Management to retrieve fixed assets. This batch code creates a flat file to send these fixed assets to the external system. This batch code must also be referenced on the Construction Parameter Work Order Master Configuration to complete the following for fixed assets:

- send fixed assets to an external system

- to add a retired fixed asset entry to the general process table

- to add an accept or return line entry to the general ledger for fixed assets

- to add a cancel line entry to the general ledger for a stock item that is a capital spare

Daily.

General Monitor Processes

Monitor controls are available in the base package so that if your implementation does add monitor algorithms to a business object for the related maintenance object, the batch control already exists to run. As delivered, the maintenance object instances current state does not reference a monitor process.

Table of Contents

Administrative User Guide

Defining General Options

Defining Installation Options

Installation Options - Main

Installation Options - Messages

Installation Options - Algorithms

Installation Options - Accessible Modules

Installation Options - Installed Products

Support For Different Languages

User Language

Customer Language

Defining Languages

Defining Countries

Country - Main

Country - States

Defining Currency Codes

Defining Time Zones

Designing Time Zones

Setting Up Time Zones

Setting Up Seasonal Time Shift

Defining Geographic Types

Defining Work Calendar

Defining Display Profiles

Additional Hijri Date Configuration

Defining Phone Types

Setting Up Characteristic Types & Values

There Are Four Types Of Characteristics

Searching By Characteristic Values

Characteristic Type - Main

Characteristic Type - Characteristic Entities

Setting Up Foreign Key Reference Information

Information Description Is Dynamically Derived

Navigation Information Is Dynamically Derived

Search Options

Foreign Key Reference - Main

Defining Feature Configurations

Feature Configuration - Main

Feature Configuration - Messages

Defining Master Configurations

Defining Security & User Options

The Big Picture of Application Security

Application Security

Action Level Security

Field Level Security

Encryption and Masking

System Encryption

User Interface Data Masking

Application Encryption

The Base Package Controls One User, One User Group, And Many Application Services

Importing Security Configuration from an External Source

The Big Picture of Row Security

Defining Application Services

Application Service - Main

Application Service - Application Security

Defining Security Types

Security Type - Main

Defining User Groups

User Group - Main

User Group - Application Services

User Group - Users

Defining Access Groups

Defining Data Access Roles

Data Access Role - Main

Data Access Role - Access Group

Defining Users

User Interface Tools

Defining Menu Options

Menu - Main

Menu - Menu Items

The Big Picture of System Messages

Defining System Messages

Message - Main

Message - Details

The Big Picture of Portals and Zones

There Are Three Types of Portals

Common Characteristics of All Portals

Portals Are Made Up of Zones

Configuring Zones for a Portal

Granting Access to Zones

Common Characteristics of Stand-Alone Portals

Putting Portals on Menus

Granting Access to A Portal

Custom Look and Feel Options

User Interface

UI Map Help

Setting Up Portals and Zones

Defining Zone Types

Defining Zones

Zone - Main

Zone - Portal

Zone Configuration Topics

Zone Help Text

Zone Parameter Details

Zone Visibility Service Script

SQL Statement

Column Parameters

Zone Action

User Filters

Hidden Filters

Multi-Select Action

Pagination Configuration

Use Data Explorer for Derived Data

Configuring Timeline Zones

Defining Context-Sensitive Zones

Defining Portals

Portal — Main

Portal — Options

Defining Display Icons

Defining Navigation Keys

Navigation Key Types

Navigation Key vs. Navigation Option

The Flexibility of Navigation Keys

Linking to External Locations

Overriding Navigation Keys

Maintaining Navigation Key

Defining Navigation Options

Navigation Option - Main

Navigation Option - Tree

Database Tools

Defining Table Options

Table - Main

Table - Table Field

Table - Constraints

Table - Referred by Constraints

Defining Field Options

Field - Main

Field - Tables Using Field

Defining Maintenance Object Options

Maintenance Object - Main

Maintenance Object - Options

Maintenance Object - Algorithms

Maintenance Object - Maintenance Object Tree

Defining Valid Values

Defining Look Up Options

Lookup - Main

Defining Extendable Lookups

Extendable Lookup Advanced Topics

The Big Picture Of Audit Trails

Captured Information

How Auditing Works

The Audit Trail File

How To Enable Auditing

Turn On Auditing For a Table

Specify The Fields and Actions To Be Audited

Audit Queries

Audit Query by User

Audit Query by Table / Field / Key

Bundling

About Bundling

Sequencing of Objects in a Bundle

Recursive Key References

Owner Flags on Bundled Entities

Configuring Maintenance Objects for Bundling

Making Maintenance Objects Eligible for Bundling

Adding a Foreign Key Reference

Creating a Physical Business Object

Creating a Bundling Add Business Object

Adding the Current Bundle Zone

Adding a Customized Entity Search Query Zone to the Bundle Export Portal

Working with Bundles

Creating Export Bundles

Creating and Applying Import Bundles

Editing Export Bundles

Editing Import Bundles

Revision Control

About Revision Control

Turning On Revision Control

Configuring Maintenance Objects for Revision Control

Working with the Revision Control Zones

Checking Out an Object

Checking In an Object

Reverting Changes

Forcing a Check In or Restore

Deleting an Object

Restoring an Object

Working with the Revision Control Portal

Revision Control Search

Information Lifecycle Management

The Approach to Implementing ILM

Batch Processes

Eligibility Algorithm

Enabling ILM for Supported Maintenance Objects

Ongoing ILM Tasks

Archived Foreign Keys

Configuration Tools

Business Objects

The Big Picture of Business Objects

What Is A Business Object?

A Business Object Has a Schema

A Business Object May Define Business Rules

A Business Object Defines its User Interface

Invoking A Business Object

Determine the Identifying BO

Base Business Objects

Business Object Inheritance

Each Business Object Can Have A Different Lifecycle

Valid States versus State Transition Rules

One Initial State and Multiple Final States

State-Specific Business Rules

Logic To Take Place When Entering A State

Logic To Take Place When Exiting A State

Monitor Rules

Inheriting Lifecycle

Auto-Transition

Keeping An Entity In Its Last Successful State

Monitoring Batch Processes

Transitory States

State Transitions Are Audited

Required Elements Before Entering A State

Capturing a Reason for Entering a State

BO Algorithm Execution Order

Granting Access To Business Objects

Defining Business Objects

Business Object - Main

Business Object - Schema

Business Object - Algorithms

Business Object - Lifecycle

Business Object - Summary

Advanced BO Tips and Techniques

Managing To Do Entries

Submitting a Batch Job

Defining Status Reasons

Business Services

Service Program

Defining Business Services

Business Service - Main

Business Service - Schema

Useful Services and Business Services

User Interface (UI) Maps

Defining UI Maps

UI Map - Main

UI Map - Schema

UI Map Attributes and Functions

UI Map Standards

UI Unique Element Name

Maintaining Managed Content

Managed Content - Main

Managed Content - Schema

Data Areas

Defining Data Areas

Data Area - Main

Data Area - Schema

Advanced Schema Topics

Schema Syntax

UI Hint Syntax

Schema Designer

Schema Viewer

Business Event Log

Miscellaneous Topics

Module Configuration

Menu Item Suppression

Menu Suppression

Turn Off A Function Module

Global Context Overview

System Data Naming Convention

Base Product System Data

Implementation System Data

Referencing URIs

Validation Against a Whitelist

URI Substitution

Caching Overview

Server Cache

Batch Cache

Client Cache

Expression Parser

Debug Mode

System Date Override

Advanced Search Options

To Do Lists

The Big Picture of To Do Lists

To Do Entries Reference A To Do Type

To Do Entries Reference A Role

To Do Entries Can Be Rerouted (Or Suppressed) Based On Message Number

The Priority Of A To Do Entry

Working On A To Do Entry

Launching Scripts When A To Do Is Selected

To Do Entries Have Logs

How Are To Do Entries Created?

To Do Entries Created By Background Processes

Dedicated To Do Background Processes

To Dos Created for Object-Specific Error Conditions

To Dos Created by Background Processes for Specific Conditions

To Do Entries Created By Algorithms

To Do Entries Created Manually

The Lifecycle Of A To Do Entry

Linking Additional Information To A To Do Entry

Implementing Additional To Do Entry Business Rules

To Do Entries May Be Routed Out Of The System

Periodically Purging To Do Entries

Setting Up To Do Options

Installation Options

To Do Information May Be Formatted By An Algorithm

Set Additional Information Before A To Do Is Created

Alerts

Next Assignment Algorithm

Messages

Feature Configuration

Defining To Do Roles

To Do Role - Main

To Do Role - To Do Types

Defining To Do Types

To Do Type - Main

To Do Type - Roles

To Do Type - Sort Keys

To Do Type - Drill Keys

To Do Type - Message Overrides

To Do Type - To Do Characteristics

To Do Type - Algorithms

List of System To Do Types

Implementing The To Do Entries

Background Processes

Understanding Background Processes

Background Processing Overview

Parallel Background Processes

Optimal Thread Count

Parameters Supplied To Background Processes

Indicating a File Path

Processing Errors

Error Post-Processing Logic

Post-Processing Logic

Timed Batch Processes

Monitor Background Processes

Plug-in Driven Background Processes

Processing System Records

Uploading Records

How to Re-extract Information

How to Submit Batch Jobs

How to Track Batch Jobs

How to Restart Failed Jobs and Processes

Assessing Level of Service

System Background Processes

Defining Batch Controls

Batch Control - Algorithms

On-line Batch Submission

Batch Submission Creates a Batch Run

Jobs Submitted in the Background

Email Notification

Running Multi-threaded Processes

Batch Jobs May End in Error

Submitting Jobs in the Future

Lifecycle of a Batch Job Submission

Granting Access To Batch Submission

Batch Job Submission - Main

Tracking Batch Processes

Batch Run Tree - Main

Batch Run Tree - Run Control

Service Health Check

The Big Picture of Requests

Request Type Defines Parameters

Previewing and Submitting a Request

To Do Summary Email

Exploring Request Data Relationships

Defining a New Request

Setting Up Request Types

Maintaining Requests

Defining Algorithms

The Big Picture Of Algorithms

Algorithm Type Versus Algorithm

How To Add A New Algorithm

Minimizing The Impact Of Future Upgrades

Setting Up Algorithm Types

List of Algorithm Types

Setting Up Algorithms

Defining Script Options

The Big Picture Of Scripts

Scripts Are Business Process-Oriented

A Script Is Composed Of Steps

A Script May Declare Data Areas

Securing Script Execution

The Big Picture Of BPA Scripts

How To Invoke Scripts

Developing and Debugging Your BPA Scripts

Launching A Script From A Menu

Launching A Script When Starting The System

Executing A Script When A To Do Entry Is Selected

The Big Picture Of Script Eligibility Rules

Script Eligibility Rules Are Not Strictly Enforced

You Can Mark A Script As Always Eligible

You Can Mark A Script As Never Eligible

Criteria Groups versus Eligibility Criteria

Defining Logical Criteria

Examples Of Script Eligibility Rules

A Script With A Time Span Comparison

A Script With Service Type Comparison

The Big Picture Of Server-Based Scripts

Additional Coding Options For Server Scripts

Using Groovy Within Scripts

Plug-In Scripts

A Plug-In Script's API

Setting Up Plug-In Scripts

Service Scripts

A Service Script's API

Invoking Service Scripts

Groovy Library Scripts

A Groovy Library Script's API

Invoking Groovy Library Methods

Debugging Server-Based Scripts

Maintaining Scripts

Script - Main

Script - Step

How To Set Up Each Step Type

Common Step Types To All Script Types

How To Set Up Conditional Branch Steps

How To Set Up Edit Data Steps

Edit Data Syntax

Script Engine Version 2 Notes

How To Set Up Go To Steps

How To Set Up Invoke Business Object Steps

How To Set Up Invoke Business Service Steps

How To Set Up Invoke Service Script Steps

How To Set Up Label Steps

How To Set Up Move Data Steps

How To Set Up Terminate Steps

Step Types Applicable to BPA Scripts only

How To Set Up Display Text Steps

How To Set Up Height Steps

How To Set Up Input Data Steps

How To Set Up Invoke Function Steps

How To Set Up Invoke Map Steps

How To Set Up Mathematical Operation Steps

How To Set Up Navigate To A Page Steps

How To Set Up Perform Script Steps

How To Set Up Press A Button Steps

How To Set Up Prompt User Steps

How To Set Up Set Focus To A Field Steps

How To Set Up Transfer Control Steps

Step Types Applicable to Server Based Scripts only

How To Set Up Groovy Member Steps

How To Set Up Groovy Imports Steps

How To Set Up Groovy Library Interface Steps

Additional Topics

How To Find The Name Of User Interface Fields

How To Find The Name Of Page Data Model Fields

How To Find The Name Of A Button

How To Substitute Variables In Text

How To Use HTML Tags And Spans In Text Strings and Prompts

How To Use Constants In Scripts

How To Use Global Variables

How To Name Temporary Storage Fields

How To Work With Dates

Move Data

Mathematical Operation

Input Data

How To Use To Do Fields

How To Reference Fields In Data Areas

Script - Data Area

Script - Schema

Script - Eligibility

Merging Scripts

Script Merge

Maintaining Functions

Function - Main

Function - Send Fields

Function - Receive Fields

Mobile Application

Understanding Mobile Devices

Mobile Platform

Mobile Device Terminals (MDT)

Registration

Managing Attachments

Data Encryption

Understanding Mobile Application Files

Oracle Utilities Mobile Library (OUML)

Business Logic Resides in Mobile Components

Packaged by a Batch Process

Testing

Understanding Deployments

Deployment Types

Deployment Parts

Deployment

Out of Date Deployments

Downloading Deployments

Setting Up Deployments

Mobile Application Versioning

Configuring Mobile Devices

Defining MDT Types

Defining MDTs

Configuring Deployment Options

Defining Deployment Parts

Defining Deployment Types

Maintaining Deployments

Defining Mobile Components

Mobile Application Master Configuration

Attachments

Attachment Overview

Configuring Your System for Attachments

Maintaining Attachments

Adding Attachments

Application Viewer

Application Viewer Toolbar

Data Dictionary Button

Physical and Logical Buttons

Collapse Button

Attributes and Schema Button

Maintenance Object Button

Algorithm Button

Batch Control Button

To Do Type Button

Description and Code Buttons

Service XML Button

Select Service Button

Java Docs Button

Java Docs Button

Classic Button

Preferences Button

Help Button

About Button

Slider Icon

Data Dictionary

Using the Data Dictionary List Panel

Primary And Foreign Keys

Field Descriptions Shown

Using the Data Dictionary Detail Panel

Related Tables View

Table Detail View

Column Detail View

Lookup Values

Maintenance Object Viewer

Using the Maintenance Object List Panel

Using the Maintenance Object Detail Panel

Algorithm Viewer

Using the Algorithm Viewer List Panel

Using the Algorithm Plug-In Spot Detail Panel

Using the Algorithm Type Detail Panel

Using the Algorithm Detail Panel

Batch Control Viewer

Using the Batch Control Viewer List Panel

Using the Batch Control Detail Panel

To Do Type Viewer

Using the To Do Type Viewer List Panel

Using the To Do Type Detail Panel

Service XML Viewer

Using the Service XML Viewer Overview Panel

Using the Service XML Viewer Detail Panel

Java Docs Viewer

Using the Java Docs Viewer List Panel

Using the Java Package Detail Panel

Using the Java Interface / Class Detail Panel

Groovy Java Docs Viewer

Application Viewer Preferences

Application Viewer Stand-Alone Operation

Stand-Alone Configuration Options

Example Application Viewer Configuration

Application Viewer Generation

Reporting and Monitoring Tools

Reporting Tool Integration

The Big Picture Of Reports

Integration with BI Publisher

Requesting Reports from The System

Overview of the Data - BI Publisher

How To Request Reports

Viewing Reports

Configuring The System To Enable Reports

Configuring BI Publisher Reports

Configure the System to Invoke BI Publisher Real-time

Batch Scheduling in BI Publisher

Defining Reporting Options

Defining Report Definitions

Report Definition - Main

Report Definition - Labels

Report Definition - Parameters

Sample Reports Supplied with the Product

How to Use a Sample Report Provided with the System

Steps Performed at Installation Time

How To Define A New Report

Use a Sample Report as a Starting Point

Publishing Reports in BI Publisher

BI Publisher Database Access

Verify BI Publisher User Access Rights

Designing Your Report Definition

Designing Main Report Definition Values

Designing Characteristic Types

Designing Parameters

Designing Validation Algorithms

Designing Application Services

Designing Labels

Measuring Performance

About Performance Targets

Performance Target Objects Overview

Calculating and Displaying Performance Targets

Performance Target Metrics and Metric Types

Performance Target Categories and Types

Performance Targets Define Specific Metrics

Objects Linked to a Performance Target

Creating Performance Target Zones

Setting Up Performance Target Configuration

Performance Target Category Lookup

Defining Performance Target Types

Maintaining Performance Targets

Capturing Statistics

About Statistics

Configuring Your System for Statistics

Defining and Monitoring Statistics

External Messages

Incoming Messages

Inbound Web Services

About Inbound Web Services

Deploying XAI Inbound Service via IWS

Configuring Inbound Web Service Options

Technical Configuration

Maintaining Inbound Web Service Annotation Types

Maintaining Inbound Web Service Annotations

Maintaining Inbound Web Services

Deploying Web Services

Guaranteed Delivery

Outgoing Messages

Outbound Messages

Polling Outbound Messages Using OSB

Batch Message Processing

Real Time Messages

Designing the System for Outbound Messages

Define the Outbound Message Business Object and Type

Real Time Message Configuration

Define the External System and Configure the Messages

Outbound Message Schema Validation

Configuring the System for Outbound Messages

JNDI Server

JMS Connection

JMS Queue

JMS Topic

Message Sender

Message Sender - Main

Message Sender - Context

Defining Outbound Message Types

External Systems

External System - Main

External System - Template Use

Message Option

Managing Outbound Messages

Outbound Message - Main

Outbound Message - Message

Outbound Message - Response

Web Service Adapters

Understanding Web Service Adapters

Setting Up Web Service Adapters

Sending Email

Web Service Category

Defining Web Service Categories

JMS Message Browser

Integration Cloud Service Catalogue

Web Service Catalogue Configuration

Web Service Catalogue Master Configuration

Maintaining the Web Service Catalogue

Mobile Remote Messages

About Remote Messages

Messages Sent From A Mobile Device

Messages Sent To A Mobile Device

Maintaining Remote Messages

XML Application Integration

The Big Picture Of XAI

XAI Architecture

The Core Server Component

The Multi Purpose Listener (MPL)

The Receiving Layer

Configuring Multiple MPL Servers

The Execution Layer

The Response Layer

The XAI Client Component

XML Background Topics

XAI Schemas

The Schema Editor

XSL Transformations

SOAP

XPATH

Server Security

Inbound Messages

Synchronous Messages

Using HTTP for Synchronous Service Execution

Asynchronous Messages

Using JMS

Using JMS Queues

Using JMS Topics

Staging Upload

Staging Upload Receiver

Staging Upload Sender

Staging Control

Staging Control Receiver

Processing Staging Upload Records for a Staging Control

Processing Staging Records in Sequential Order

Staging Control Parameters

Staging Control Sender

Inbound Message Error Handling

Integration Scenarios

Integration Using an EAI (or Hub)

Batch Scenarios

XML Message File

XAI Groups

Attachments and Rules

Sequential Input File

Database File

WSDL Catalog

Outgoing Messages

Outbound Message Receiver

Lifecycle of Outbound Message

Outbound Message Sender

Outbound Message Error Handling

Automatic Resend

Designing Your XAI Environment

Installation

The XAI Source Section

The MPL Source Section

The Parameter Variables Section

The AdHoc Parameters Section

Designing XAI Inbound Services

Designing XML Schemas

Designing XSL Transformations

Designing Your Registry Options

Designing XAI JDBC Connections

Designing XAI Formats

Date Formats

Currency Formats

Phone Formats

Text Formats

Designing XAI Adapters

Designing XAI Executers

Designing XAI Senders

Designing XAI Groups

Designing XAI Receivers

Designing Responses for a Receiver

Designing Receivers that Poll Staging Tables

Designing a JMS Queue Receiver

Designing a JMS Topic Receiver

Designing a File Scan Receiver

Designing an XML File Receiver

Configuring the System for NDS Messages

Schema Editor

Opening the Schema Editor

Schema Editor Window

Validating a Schema

Registering a Service

Testing a Schema

System Wide Functions for Schema Editor

Application Standards

The File Menu

The View Menu

The Schemas Menu

The Options Menu

The Tools Menu

Setting Up Your XAI Environment

XAI Class

XAI Envelope Handler

Setting Up Your Registry

XAI JDBC Connection

XAI Format

XAI Adapter

XAI Executer

XAI Group

XAI Group - Main

XAI Group - Attachments

XAI Group - Rules

XAI Receivers

XAI Receiver - Main

XAI Receiver - Context

XAI Receiver - Response

XAI Receiver - Groups

XAI Inbound Services

XAI Inbound Service - Main

XAI Inbound Service - Staging

XAI Inbound Service - Parameters

XAI Route Type

Running Your XAI Environment

XAI Staging Control

XAI Upload Staging

XAI Upload Staging - Main

XAI Upload Staging - Response

Uploading XAI Staging Records

Staging Control Layout

Staging Control Parameters Layout

Upload Staging Layout

XMLUP-PR - Purge XAI Upload Objects

XAI Upload Exception

XAI Download Staging

XAI Download Staging - Main

XAI Download Staging - Request

XAI Download Staging - Response

XAI Download Exception

Maintaining Your XAI Environment

XAI Submission

XAI Submission - Main

XAI Submission - Response

Additional XAI Tools

XAI Service Export

XAI Service Import

XAI Command

MPL Exception

Server Trace

Starting the Trace

Stopping the Trace

Trace Viewer

Main Page

Statistics Page

Integrations

LDAP Integration

LDAP Integration Overview

Configuring LDAP Integration

LDAP Mapping

Oracle Identity Manager Integration

Batch Scheduler Integration

Data Synchronization

About Data Synchronization

Maintaining Sync Requests

Analytics Integration

About Analytics Integration

Maintaining Bucket Configurations

ETL Mapping Control

Business Flags

About Business Flags

Standard Name

Business Flag Type Defines Behavior for a Standard Name

Business Flag Type Algorithms

Objects Linked to a Business Flag

Impacted Business Process

Dates

Creating Business Flags

Confidence

Setting Up Business Flag Configuration

Standard Name Category Characteristic Type

Business Flag Standard Name Lookup

Business Process Lookup

Integration Configuration

Defining Business Flag Types

Maintaining Business Flags

Configuration Migration Assistant (CMA)

Understanding CMA

The CMA Process Flow

Migration Assumptions, Restrictions, and Recommendations

CMA Configuration

Migration Assistant Configuration

Migration Plans

Defining a Migration Plan

Understanding the BO Filtering Process

Migration Plans for Objects with CLOB-Embedded Links

Defining a Migration Request

Types of Migrations

Wholesale Migrations

Targeted Migrations

Identifying Tables to Exclude From Migrations

Configuring Custom Objects for Migration

The CMA Execution Process

Exporting a Migration

Migration Data Set Export

Export Lifecycle

Importing and Applying a Migration

Import Step

Compare Step

Approval Step

Apply Step

Adjusting Data While Importing

Import Process Summary

Cancelling a Data Set

Additional Note Regarding Imports

Caching Considerations

Maintaining Import Data

Migration Data Set Import

Migration Transaction Portal

Migration Object Portal

Running Batch Jobs

CMA Reference

Framework-Provided Migration Objects

Configuring Facts

Fact Is A Generic Entity

Fact's Business Object Controls Everything

Fact Supports A Log

Cloud Service Foundation

Process Automation Tool

Creating an Infrastructure Process

Executing an Infrastructure Process

Monitoring Infrastructure Process Progress

Infrastructure Process Control

Monitoring a Running Infrastructure Process

Dealing with Exceptions

Batch Job Step Exceptions

Non-Batch Step Exceptions

Process Automation Tool Setup

Security Setup

Master Configuration Setup

External Systems and Message Senders

Configuring New Infrastructure Processes

Configuring a New Infrastructure Process Step Type

Configuring a New Infrastructure Process Type

CMA Migration Infrastructure Process Types

CMA Accelerator Load (K1-CMA-LOAD)

CMA Migration (K1-CMA-MIGRATE)

Integration Configuration (SOA) Infrstructure Process Types

Integration Configuration Migration (K1-INTEG-CONFIG-MIGR)

Data Conversion Support for Cloud Implementations

Data Conversion Overview

Conversion Steps

Prepare for Conversion

Create Conversion Data Files

Upload Data Conversion Files to the Cloud

Process Conversion Data Files

Process Converted Data in Cloud Application

Approve Converted Data for Production Mode

SQL Loader

Using SQL Loader When Processing Conversion Data Files

Conversion Artifacts

Conversion Input Data Specifications

SQL Loader Control Files

Configuring Conversion

Conversion Master Configuration

Conversion Task Types

Conversion Artifact Generator

Conversion Tasks

Conversion Task Query

Conversion Task

Conversion Batch Controls

Configuring Data Load Batch Controls for Conversion Project

Input Data Files

Overview

File Upload

Loading Table or Maintenance Object

Multiple Data Files

Loading CLOB Data

Notes on Secondary Data Files (CLOB Data)

File Layout and Data Formatting

Defining Custom Data Delimiters and Enclosing Characters

Input Data for a Staging Table

Input Data for Maintenance Object

Limitations for Input Data

Conversion Orchestration

Input and Output File Location

Understanding Load Data Process

Load Data Batch Run Parameters

Multi-Threading

Load Outcome – Log, Bad and Rejected Files

Interrupted Load

Tables Cleanup and Index Maintenance

Load Performance Tuning

Understanding the Conversion Orchestration Process

Security Setup for Conversion

Conversion Reconciliation Reports

Work and Asset Management Administrative User Guide

System Wide Oracle Utilities Work and Asset Management Configuration

Defining Home Page Configuration

Defining General System Master Configuration

About Access Control

About Statistics

E-Mail Configuration

Three Decimal Currency

Communication

About Communication Types

Defining Communication Types

BI Configuration Administration

Designing Approval Processing

Understanding Approval Processing Configuration

About Approval Profiles

Configuring Approval Processing

Defining an Approval Profile

Setting the Approval Profile for a Record Type

Defining the Approval Hierarchy

About No Approval Required Profiles

About No Amount Profiles

Defining To Do Types, To Do Roles, and To Do Entries for Approvals

Asset Management Options

Understanding Asset Management Configuration

About Asset Types, Assets and Components

About Asset Location Types

About Service History Types and Service History

About Asset Inspections (Assessments)

About Measurement Types and Measurements (Operational Readings)

Configuring Asset Management

Defining Measurement Identifiers

Defining Measurement Types (Operational Readings)

Defining Questions

Defining Service History Types

Defining Asset Location Types

Defining Out of Service Location Types

Defining Asset Types

Defining Component Types

Condition Assessment Options

Understanding Condition Assessment Options

About Condition Assessment Questions

About Condition Assessment Groups

About Condition Assessment Classes

Configuring Condition Assessment

Defining Condition Assessment Groups

Defining Condition Assessment Classes

Operational Device Management Options

Understanding Operational Device Management Configuration

About Asset and Component Configuration Types

Configuring Operational Device Management

Defining Asset Configuration Types

Designing Inventory Management

Understanding Inventory Configuration

About Stock Items, Stock Item Details and Storerooms

About Commodity Codes

Configuring Inventory Management

Defining a Storeroom

Defining Storeroom Types

Defining Commodity Codes

Designing Purchasing

Understanding Purchasing Configuration

About Contact Types and Contacts

About Buyers

About Purchase Commodities

About Capability Types

About Payment Terms

About FOB (Freight on Board or Free on Board)

About Invoicing

Configuring Purchasing

Defining Contact Types

Defining Buyers

Defining Purchase Commodities

Defining Capability Types

Defining Vendor Payment Terms

Defining a Blanket Contract Access List

Granting User Access to a Blanket Contract

Defining FOB (Freight on Board or Free on Board)

Defining Exchange Rates

Designing Resource Management

Understanding Resource Management Configuration

About Organization Types and Organizations

About Organizations

About Document Types and Documents

About Documents (Attachments, Standard Notes and URL Attachments)

About Service Classes

About Service Areas

About Resource Unit of Measurement

About Business Units

About Employee Types and Employees

About Employees

About Employee Unavailability Types and Employee Unavailability

About Employee Unavailability

About Crew Shift Types, Crew Types, Crew Shifts and Crews

About Crews

About Crafts, Equipment and Other Resources

About Crafts

About Equipment

About Miscellaneous Resources

About Shift Plan Templates

Configuring Resource Management

Defining Resource Unit of Measurements (UOM)

Defining Organization Types

Defining an Organization

Defining Service Classes

Defining Service Areas

Defining Document Types

Defining a Document

Defining a Common Attachment from the Attachment Portal

Defining Business Units

Defining Employee Types

Defining an Employee

Defining Employee Unavailability Types

Defining Equipment

Defining an Miscellaneous Resource

Defining a Craft

Defining an Hourly Rate to a Craft

Defining a Secondary Craft

Defining a Crew Type

Defining a Crew

Defining a Crew Shift Type

Defining a Shift Plan Template

Designing Work Management

Understanding Work Management Configuration

About Planners and Maintenance Managers

About Activity Types and Activities

About Work Priority and Criticality Fields

About Checklist Types

About Completion Events

About Completion Event Types

About Inbound Communications

About Projects and Subprojects

About Timekeeping

Configuring Work Management

Defining Maintenance Managers

Defining Planners

Defining Activity Types

Defining Checklist Types

Adding a Checklist Type for a Template Activity

Defining Completion Event Types

Defining Time Periods

Defining Labor Earning Types

Defining Overtime Types

Defining Project Categories

Construction Work Management Options

Understanding Construction Work Management Configuration

About Construction Work Management Configuration

About Compatible Units (CU)

Configuring Construction Work Management

Defining Property Units

Defining a Compatible Unit Set

Defining a Compatible Unit

Defining a CU Contractor Bid

Defining a CU Category

Defining Equipment Groups

Defining CU Usage

Defining Overhead

Preventive Maintenance Options

Understanding Preventive Maintenance Configuration

About Preventive Maintenance Configuration

Financials Options

Understanding Financials Configuration

About Accounting Calendars

About Currency

About Colors

About Cost Categories

About Cost Centers

About Expense Codes

About Factors and Factor Values

About Distribution Codes

About Tax Rate Schedules

Configuring Financials

Defining Accounting Periods

Defining Account Segments

Creating Accounting Calendars

Defining Currency

Defining Colors

Defining Cost Categories

Defining Cost Centers

Reviewing Cost Center Statistics

Deactivating Cost Centers

Defining Expense Codes

Deactivating Expense Codes

Defining Factors

Defining Distribution Codes

Defining Tax Rate Schedules

Integrations

About Integrations

Specific Product Integrations

Defining External Systems

Data Synchronization for Integrations

Understanding Synchronization Request Processing for Integrations

BI Publisher Integration

Create a BI Publisher Report

Configure a BI Report in Oracle Utilities Work and Asset Management

Add the Valid Business Object Option Type to the Maintenance Object

Add the Report Code Option Type to the Business Object

Enable the Print Report Function

Configure Reports Dispatch

GIS Integration

GIS Integration Setup Steps

GIS Configuration Steps in ArcGIS

Set Up ArcGIS Geodatabase

Complete the Set Up of Version Comparison and GIS Sync

Deploy the .jar File

Configure the Property File

Use ArcCatalog to Execute the .jar

Publish the Results as a Geoprocessing Service

Publish Data as Services on the ArcGIS Server

Set the Data Source in Map Documents

Publish Map Documents as Services in ArcGIS Server

Create and Publish Web Maps in Portal

Connect Portal for ArcGIS with Enterprise LDAP

Import Users to Portal for ArcGIS

GIS Configuration Steps in Oracle Utilities Work and Asset Management

GIS Batch Processing

Configure Extendable Lookups

Create Message Senders

Create Outbound Message Types

Create GIS External System

Set Up Master Configuration

Table Setup Sequence

Control Data Setup

OUAF Control Data Setup

General Control Data Setup

Approval Processing Control Data Setup

Financial Control Data Setup

Resource Control Data Setup

Inventory Control Data Setup

Work Management Control Data Setup

Asset Control Data Setup

Construction Work Management Control Data Setup

Purchasing Control Data Setup

Master Data Setup

Resource Master Data Setup

Purchasing Master Data Setup

Inventory Master Data Setup

Asset Master Data Setup

Work Management Master Data Setup

Construction Work Management Master Data Setup

Batch Control Configuration

About Monitors

Oracle Utilities Work and Asset Management Batch Controls