Thursday Aug 25, 2011

Feature Configuration

I am continually surprised at the amount of functionality hidden within the Feature Configuration reference tables, and whilst I recognize the fact that this is not the best documented component of the system, I feel that it makes sense to list the functionality built in to FW2.2 and CC&B 2.2/2.3.1, so as a followup to my earlier posting in relation to the PPM controls let’s dive into Feature Configuration:

System Metadata and Controls
Analytics Extract

 File Path

Indicates the file path in which the flat files produced by the extract processes will be placed. The syntax of the File Path depends on the platform used for your application server. Contact your system administrator for verification. For example if the platform is Unix use forward slashes and be sure to use a trailing slash e.g. /extracts/filepath/ [CC&B 2.2-2.3.1]


Application Workbench

 Image Accessbility

 Enforces accessibility standards on image elements.  Valid values are 'Y' to enforce and any other value to not enforce. [CC&B 2.2-2.3.1]

 System Data Logging Enabled

 Indicates whether the system data logging is enabled in this environment. Valid values are 'Y' or 'N'. This option is added and set by System data logging installation process. [CC&B 2.2-2.3.1]


Batch Scheduler

Batch Code FK Char Type

[CC&B 2.2-2.3.1]

Batch Job ID FK Char Type            

[CC&B 2.2-2.3.1]

Batch Run Number Ad hoc Char Type

[CC&B 2.2-2.3.1]

Business Date Ad hoc Char Type         

[CC&B 2.2-2.3.1]

Email Address on Batch Jobs            

[CC&B 2.2-2.3.1]

Batch Code of WF Event Activation Process            

[CC&B 2.2-2.3.1]

SMTP Port Number            

[CC&B 2.2-2.3.1]

SMTP Server Name            

[CC&B 2.2-2.3.1]

User ID on Batch Jobs         

[CC&B 2.2-2.3.1]

Default Work Calendar           

[CC&B 2.2-2.3.1]

Active Job Stream (WF Template Code)          

[CC&B 2.2-2.3.1]

Custom Look and Feel

 Style Sheet

Specifies the name and location of the custom style sheet file.

An example would be:  cm/styles/localStyle.css

The file (localStyle.css) should be created and placed in the cm/styles folder on the web server.
[CC&B 2.2-2.3.1]

UI Map Help Icon

Specifies the location of help icon image that overrides the system default icon.

For example. cm/images/sample.gif.
[CC&B 2.2-2.3.1]

UI Map Help Position

Specifies the position of the icon before or after the element for which it is defined.
Possible values are 'after' (default) or 'before'.
[CC&B 2.2-2.3.1]

UI Map Help

Specifes whether the automatic UI Map Help is off or not.  Anything other than 'off' implies 'on'. [CC&B 2.2-2.3.1]

Data Masking

Field Masking

Define the field to mask along with the masking algorithm.  

The configuration for the field to mask depends on how the data is accessed.  See the following details.  To reference the masking algorithm, enter alg="algorithm name".  The algorithm's algorithm type must reference the Data Masking algorithm entity.  

Field Masking details.  (Only fields defined as strings are supported.)

- For data that is accessed via a schema-based object call, the field to be masked must reference a meta-data field name in its schema definition.  For example, if you want to mask a credit card number, let's assume that field is defined in the schema is <creditCard mdField="CCNBR" mapField="EXT_ACCT_ID"/>.  In this case, the option value should be
  field="CCNBR", alg="algorithm name"

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

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

- 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.

- For data that is displayed 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.
[CC&B 2.2-2.3.1]

Email Configuration

 Number of concurrent senders

 Specifies the number of concurrent email senders that can be active at one time. [CC&B 2.2-2.3.1]

General System Configuration

Use Legacy Alerts

Certain system-generated alerts have been converted to installation record algorithms. This implies that the order in which these alerts appear might differ to the prior system-generated alerts order. If your implementation wishes to retain the legacy order for these alerts, this option must be defined with a value of Y, and the alert algorithms should not be plugged-in on the installation record. Note that if both the feature option and alert algorithms are configured, these alerts may appear twice on the Alert Zone. [CC&B 2.2-2.3.1]

System Override Date

 This option provides a way to override the system date for on-line operations.  Specify a system override date in the format YYYY-MM-DD. If populated, the system will use this date as the system date instead of retrieving the system date from the database. [CC&B 2.2-2.3.1]

Allow Bill Cycle Synchronisation

This option allows the system to automatically update the account’s bill cycle to be in sync with a service point’s service cycle when the service cycle is updated and the account’s bill cycle is not protected. Valid values are 'Y' and 'N'. [CC&B 2.3.1 Only]

MDM URL

This option allows navigation to MDM from the SA or SP context menus (if these menus have been configured accordingly). Specify the URL for the MDM application in the format http:///Portal=MDMPORTAL&Target=, where hostlocation is either an IP address, or a server name and port number, portalname is constant and the targetname is the name of the page that the user will be navigated to in the target system. For example: http://localhost/lodestar/ccs/Default.aspx?Portal=MDMPORTAL&Target=MainWebPart.aspx [CC&B 2.3.1 Only]

Module Configuration

 Turned Off

 Specify a function module to turn off.  Refer to the "MODULE_FLG" lookup field for the complete list of the application's function modules. [CC&B 2.2-2.3.1]


Online Help

Online Help Root URL

 Specify the URL that points to the Online Help application, e.g. http://<hostname>:<port>/<web-app-context-path>/ [CC&B 2.2-2.3.1]



Oracle Utility Suite Integration
Field Activity Integration (Work Force Management in 2.3.1)

Account Rel. Type - Company Contact

Identify the account relationship type used to define a company's contact person. [CC&B 2.2-2.3.1]

Appointment Forced Characteristic Type

[CC&B 2.2-2.3.1]

Allow Forced Appointments

[CC&B 2.2-2.3.1]

Allow Manual Appointment Cancellation

[CC&B 2.2-2.3.1]

Allow Manual Appointment

[CC&B 2.2-2.3.1]

Allow Multiple Reservations

[CC&B 2.2-2.3.1]

Allow Narrowing Of Appointment Window

[CC&B 2.2-2.3.1]

Default Days of Available Appointment

[CC&B 2.2-2.3.1]

Phone Type – Business    

Indicate the phone type used to identify a business phone number. [CC&B 2.2-2.3.1]

Allow Slot Group

[CC&B 2.3.1 Only]

Phone Type – Fax

Indicate the phone type used to identify a fax number. [CC&B 2.2-2.3.1]

Hi-Low Review

Indicated if meter reads added from this external system should be reviewed for Hi-Low failures and trended. Valid values: Y/N [CC&B 2.2-2.3.1]

Phone Type – Home

Indicate the phone type used to identify a home phone number. [CC&B 2.2-2.3.1]

Intermediate Status To Prevent FA Cancel

Create an entry in the option collection for any FA Intermediate Status value that should prevent the system from automatically canceling a Field Activity.  This should be used if there are situations where a field activity is in a state where a message cannot be sent real time to inform someone that a field activity has been canceled.

The value entered here should correspond to a valid lookup value for the field FA_INT_STATUS_FLG. 
[CC&B 2.2-2.3.1]

Intermediate Status To Skip Message

Create an entry in the option collection for any FA Intermediate Status value used when a Field Activity is created by an external system or when other information for a field activity is updated by an external system.  

The base FA integration algorithm uses this information to ensure that messages sent to the external system to highlight new field activities or changes to field activities are only triggered when additions / changes are initiated in our system.  

The value entered here should correspond to a valid lookup value for the field FA_INT_STATUS_FLG.
[CC&B 2.2-2.3.1]

Appointment Java Class Interface

[CC&B 2.2-2.3.1]

Message ID Database Sequence Name

[CC&B 2.2-2.3.1]

No Address Premise Type

[CC&B 2.2-2.3.1]

Phone Number Characteristic Type

[CC&B 2.2-2.3.1]

Plant Source

Indicates where the Plant field will be defined.
- enter FECO if the plant field is defined in Feature Configuration
- enter OPAR if the plant field is defined in the SP Operations Area
- enter SPCH if the plant field is defined in the SP Characteristic
[CC&B 2.2-2.3.1]

Plant Value

If the Plant Source is FECO (Feature Configuration) enter the value of the Plant.

If the Plant Source is OPAR (Operations Area) enter the field service class used to identify the plant value on the SP operations area.

If the Plant Source is SPCH (SP Characteristic) enter the characteristic type used to identify the plant value on SP characteristic.

Only one Plant Value may be defined for this feature configuration. [CC&B 2.2-2.3.1]

Reservation Characteristic Type

[CC&B 2.2-2.3.1]

Service Provider

[CC&B 2.2-2.3.1]

To Do Type for FA Response            

[CC&B 2.2-2.3.1]

User Defined Criteria Field            

[CC&B 2.2-2.3.1]

User Defined Result Field          

[CC&B 2.2-2.3.1]

NMS Integration

Outage Group Code Characteristic Type Prefix    

Defines the prefix used for trouble call outage group code characteristic types. The system uses this to build a dropdown of outage group codes during trouble call processing. [CC&B 2.3.1 Only]

External System

Defines the external system used for query outbound messages created from the outage management information portal page. [CC&B 2.3.1 Only]

Outbound Message Type - Call History

Defines the outbound message type used for the call history query outbound messages created from the outage management information portal page. [CC&B 2.3.1 Only]

Outbound Message Type - Job History

Defines the outbound message type used for the job history query outbound messages created from the outage management information portal page. [CC&B 2.3.1 Only]

Outbound Message Type - Planned Outages

Defines the outbound message type used for the planned outage query outbound messages created from the outage management information portal page. [CC&B 2.3.1 Only]


Outage Management

Account ID Characteristic Type            

[CC&B 2.2 Only]

Phone Nbr Type to Use When Person is of Type 'Business'  

[CC&B 2.2 Only]

Delimiter to split Instructions and Comments passed to NMS

If the delimiter is provided, Field Activity Instructions and Comments are passed to NMS System [CC&B 2.2 Only]

Use expanded Comments field in NMS interface table (Y/N)

Default value is N. Use expended Comments field if OMS_CALL table is changed to accept 518 characters in Comments field. Otherwise standard productized integration will use 255 characters Comments field [CC&B 2.2 Only]

Callback Date/Time Characteristic Type            

[CC&B 2.2 Only]

Callback Number Characteristic Type            

[CC&B 2.2 Only]

Callback Request Characteristic Type            

[CC&B 2.2 Only]

City Characteristic Type            

[CC&B 2.2 Only]

Number Of Days To View Outage Events            

[CC&B 2.2 Only]

Device Geographic Type            

[CC&B 2.2 Only]

Complete FA Remark Type         

[CC&B 2.2-2.3.1]

Feeder Geographic Type            

[CC&B 2.2 Only]

Location Characteristic Type      

[CC&B 2.2 Only]

Phone Nbr Type to Use When Person is of Type 'Person'            

[CC&B 2.2 Only]

Priority (Critical) Characteristic Type            

[CC&B 2.2 Only]

Priority (Key) Characteristic Type            

[CC&B 2.2 Only]

Priority (Medical) Characteristic Type       

[CC&B 2.2 Only]

Service Provider            

[CC&B 2.2 Only]

Default Service Type      

[CC&B 2.2 Only]

Premise ID for Outage Calls Without A Premise            

[CC&B 2.2 Only]

Outage Code Group 1 Characteristic Type            

[CC&B 2.2 Only]

Outage Code Group 2 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 3 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 4 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 5 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 6 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 7 Characteristic Type           

[CC&B 2.2 Only]

Outage Code Group 8 Characteristic Type 

[CC&B 2.2 Only]


CC&B Functional Area

Activity Queue Management

Override Skill

Provide 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.
[CC&B 2.2-2.3.1]

Skill    

Provide 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.
[CC&B 2.2-2.3.1]

Disable Role Validation On Completion    

Use this option for disabling the role validation on ToDo completion.

Valid values are 'Y' or 'N'.
By default the system performs user role validation when user completes a ToDo.
[CC&B 2.2 Only]


Case Options

Exception To Do Type

The To Do type to be used to record case transition exceptions.

The system populates the To Do Entry with the sort keys and drill keys as shown in the base package To Do Type C1-CSEXC, which you may use here.  If you want to create your own To Do Type, you must set up the values to match those in the base To Do Type.
[CC&B 2.2-2.3.1]

Collections, Severance and Write-Off

Champion Template$Challenger Template$Percentage (1 - 100) 

You need only set up options of this type if your implementation uses Champion / Challenger functionality. The format of the option type value is A$B$nnn where A is the collection process template of the champion template, B is collection process template of the challenger templace and C is the percent of time that the system should create the challenger template. [CC&B 2.3.1 Only]


Data Management Options

Enforce Rate Validation

Indicate Y if rate components referenced on existing bill segment calc lines may not be deleted via Config Lab [CC&B 2.2-2.3.1]



Fieldwork Options

Cancel Reason Required (Y/N)

Indicates whether the system should require a cancel reason when a field order is cancelled. Cancel reason is only displayed on the field order maintenance transaction if this option is set to 'Y'. Valid values are 'Y' or 'N'. [CC&B 2.2-2.3.1]

Default Reschedule Reason

Indicates the reschedule reason to use when a field activity or field order's schedule date/time is automatically updated by the system. This option is required if Reschedule Reason Required is set to 'Y'. A valid reschedule reason must be referenced. [CC&B 2.2-2.3.1]

Reschedule Reason Required (Y/N)

Indicates whether the system should require a reschedule reason when the schedule date/time on a field activity or field order is changed. Reschedule reason is only displayed on the field activity and field order maintenance transactions if this option is set to 'Y'. Valid values are 'Y' or 'N'. [CC&B 2.2-2.3.1]

Financial Transaction Options

Adjustment Cancel Reason For Payment Linked To Adjustment

Indicate the adjustment cancel reason to use when the system automatically cancels an adjustment linked to a payment being canceled. [CC&B 2.2-2.3.1]

Default Auto Pay Method            

This option is used for defaulting the auto pay method on new account auto pay records. [CC&B 2.2-2.3.1]

Allow Manual Tender Authorization Override

Indicates if the system should prevent users from overriding the automatic tender authorization on the payment portal. Enter a value of 'N' to suppress the Authorization Override checkbox display when a credit card payment is posted. Valid values are 'Y' and 'N'. [CC&B 2.2-2.3.1]

Raw Calc Amount Characteristic Type

Defines the bill segment calc line characteristic type used to store the raw calculated amount from a rate component. [CC&B 2.2-2.3.1]

CIS Payment Event Add BO

Indicates the business object to use to incorporate additional logic in the processing of CIS payments via the payment portal. It enables the BO's options to be recognized during CIS payment processing from the payment portal. [CC&B 2.2-2.3.1]

Default Distribution Rule

This option states your default distribution rule that appears throughout the system. [CC&B 2.2-2.3.1]

Always Enable Distribution Rule (Y/N)

This option controls whether the system should only use the distribution rule method to add payment events or rather allow both the default method and the distribution rule method to coexist. Enter 'Y' if the system should always use distribution rules. With this setting, navigation to the Payment Event page in add mode opens up the Payment Event Quick Add page (defaulting it to the single payment event dialog). This dialog is designed to create a payment event using distribution rules Entter 'N' if the system should allow both methods. With this setting, navigation to the Payment Event page in add mode opens up the standard Payment Event - Add Dialog that uses the default method to create a payment event. If you want to use the distribution rule method, navigate to the Payment Event Quick Add page from the menu. [CC&B 2.2-2.3.1]

Always Use Manual Payment Distribution By SA (Y/N)

Indicates the type of grid to display when a user is transferred to the Payment - Manual Distribution page to manually distribute a payment amongst an account’s service agreements. Enter 'Y' if the system should always display the manual distribution by service agreement grid. Enter 'N' if the system should display an alternate grid for open item accounts. The alternate grid is designed to break down payable balances by individual bill and service agreement. Both unpaid bill balances and new charges are displayed. [CC&B 2.2-2.3.1]

Payment Advice Functionality Supported (Y/N)

This option controls whether the system allows for payment advice processing. Enter 'Y' if the system should allow for both direct debit and payment advice processing. Enter 'N' if the system should only allow for direct debit processing. Valid values are 'Y' and 'N'. [CC&B 2.2-2.3.1]

Invoke Step Algorithm to Adjust Service Quantity (Y/N)

Rate component step algorithms are invoked during rate application to adjust step values prior to the system performing step value proration. Depending on the step value proration that occurs, the step value may be modified by the system after it has been adjusted by the rate component step algorithm. If you wish the adjusted step value to be modified by the system during step value proration, you must set up the Adjust Rate Component Step Values After Proration option type on the Financial Transaction Options Feature Configuration. The Adjust Rate Component Step Values After Proration option must have a value of Y in order to have the adjusted step values modified by the system. Valid values are 'Y' and 'N'. [CC&B 2.2-2.3.1]

Adjust Rate Component Step Values After Proration

Rate component step algorithms are invoked during rate application to adjust step values prior to the system performing step value proration. Depending on the step value proration that occurs, the step value may be modified by the system after it has been adjusted by the rate component step algorithm. If you wish the adjusted step value to be modified by the system during step value proration, you must set up the Adjust Rate Component Step Values After Proration option type on the Financial Transaction Options Feature Configuration. The Adjust Rate Component Step Values After Proration option must have a value of Y in order to have the adjusted step values modified by the system. Valid values are 'Y' and 'N'. [CC&B 2.3.1 Only]

Allow Consumption Zero Suppression In Bill Description

This option allows for the suppression of trailing zeroes after the decimal in the service quantity that appears in the bill line description. The option is used in conjunction with the %Q substitution character available for use with the rate component's Description on Bill. Valid values are 'Y' and 'N'. [CC&B 2.3.1 Only]


Meter Management Options

Allow Duplicate UOM/TOU Combination

Indicate Y if same UOM/TOU combination is allowed for meters. [CC&B 2.2-2.3.1]

Always Estimate And Apply High/Low Factors

When a meter read is added, the system checks that the meter reads consumption is reasonable by comparing the actual read to high and low read values (calculated by the Meter Read High Low Limits installation algorithm). The system sets the high and low read values to the previous register read if a meter is off at the SP (instead of estimating a read and applying the high/low factors).  Indicate Y if you'd like the system to always estimate and apply high/low factors regardless of the meter SP status. [CC&B 2.2-2.3.1]

Always Mark Removal Meter Read Useable On Bill

Indicate Y if removal meter read should always be marked useable on bill [CC&B 2.2-2.3.1]

Negative Consumption Meter Type Characteristic Type

Indicate the characteristic type used on meter types to identify meters capable of rolling backwards. Both characteristic type and value options must be defined. [CC&B 2.3.1 Only]

Negative Consumption Meter Type Characteristic Value

Indicate the characteristic value used on meter types to identify meters capable of rolling backwards. Both characteristic type and value options must be defined. [CC&B 2.3.1 Only]

Negative Consumption SP Characteristic Type

Indicate the characteristic type used on service points to denote generation capacity. Both characteristic type and value options must be defined. [CC&B 2.3.1 Only]

Negative Consumption SP Characteristic Value

Indicate the characteristic value used on service points to denote generation capacity. Both characteristic type and value options must be defined. [CC&B 2.3.1 Only]

Net MeteringParameters

Bill Factor

Applied Rollover Credit Bill Factor. Identifies applied rollover credit recorded on the SA Contract Value. [CC&B 2.3.1 Only]

NEM Adjustment Type

Rollover Credit Adjustment Type (Net Metering SA). The adjustment type to use refunding rollover credits back to the net metering SA [CC&B 2.3.1 Only]

Service Quantity Identifier (SQI)

Service Quantity Identifier. Combination of UOM/TOU/SQI identifies the rollover credit bill segment SQ. MUST be the same UOM/TOU/SQI combination used by Rates and Billing to store the rollover/banked credits [CC&B 2.3.1 Only]

Time Of Use (TOU)

Time of Use. Combination of UOM/TOU/SQI identifies the rollover credit bill segment SQ. MUST be the same UOM/TOU/SQI combination used by Rates and Billing to store the rollover/banked credits [CC&B 2.3.1 Only]

Unit Of Measure (UOM)

Unit of Measure. Combination of UOM/TOU/SQI identifies the rollover credit bill segment SQ. MUST be the same UOM/TOU/SQI combination used by Rates and Billing to store the rollover/banked credits. Required if TOU is specified. [CC&B 2.3.1 Only]

Order Configuration

Eligibility Tree - Suppress Error Packages node

Indicates if the system should suppress the display of the Error Packages on the Order - Eligibility Tree. [CC&B 2.2-2.3.1]

Eligibility Tree - Suppress Ineligible Packages node           

Indicates if the system should suppress the display of the Ineligible Packages on the Order - Eligibility Tree. [CC&B 2.2-2.3.1]

Eligibility Tree - Suppress Other Campaigns node          

Indicates if the system should suppress the display of the Other Campaign on the Order - Eligibility Tree. [CC&B 2.2-2.3.1]


Overdue Processing

Champion Template$Challenger Template$Percentage (1 - 100) 

You need only set up options of this type if your implementation uses Champion / Challenger functionality. The format of the option type value is A$B$nnn where A is the collection process template of the champion template, B is collection process template of the challenger templace and C is the percent of time that the system should create the challenger template. [CC&B 2.2-2.3.1]

Payment Arrangement Type (B/S/A)            

The system uses this option to determine the navigation key and label for payment arrangements in the Account Activity History List and Credit and Collection Zone as follows:

If the option value is B, the user is navigated to the Pay Arrangement By Bill page

If the option value is A, the user is navigated to the SA Maintenance Page

If the option value is S, the user is navigated to the Payment Arrangement Maintenance Page

The default option value is S. [CC&B 2.2-2.3.1]

Trigger Date: Y-Workdays, N-Calendar Days

This option defines if calendar days or work days are used to compute overdue event and cut event trigger dates. This option is used by the online and background processes that compute trigger dates. [CC&B 2.2-2.3.1]

About

Stuart Ramage

I am a Consulting Technical Manager for Oracle Corporation, and a member of the OU Black Belt Team, based in Hobart Tasmania.
I have worked in the Utility arena since 1999 on the Oracle UGBU product line, in a variety of roles including Conversion, Technical and Functional Architect.

Contact me on:

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today