Oracle Release Management Profile Options

This chapter covers the following topics:

Oracle Release Management Profile Options

During implementation, you set a value for each user profile option to specify how Oracle Release Management controls access to and processes data.

Generally, your system administrator sets up and updates profile option values. The Oracle E-Business Suite System Administration User's Guide - Maintenance contains more information on profile options, including the internal names of each Release Management profile option. The following information is included here for your convenience.

This chapter assumes that you have defined the profile options for the other Oracle applications that you are using to ensure that they work properly.

Viewing and Updating Oracle Release Management Profile Options

To view and update Oracle Release Management profile options:

  1. Navigate to the Find System Profiles window.

  2. Enter RLM% into the Find field and click Find.

    This will return all Oracle Release Management profile options.

You can set or view the following profile options in Oracle Release Management. The table also indicates whether you (the “User”) can view or update the profile option and at which System Administrator level the profile options can be updated. The System Administrator level includes User, Responsibility, Application, and Site levels. Profile options are either Optional or Required:

The following terms are used in the table to identify if you can view or update the profile option information:

Oracle Release Management Profile Options
Profile Option User System Admin. User System Admin. Resp. System Admin. App. System Admin. Site Required Default Value
RLM: Debug Mode Updatable Updatable Updatable Updatable Updatable No Null
RLM: MRP Forecast Selection List View Only View Only Updatable View Only Updatable No No Default
RLM: MSC/MRP Default Assignment Set View only No Update or View No Update or View No Update or View Updatable No No Sourcing to be applied
RLM: Print Cum Data on Shipping Documents Updatable Updatable Updatable Updatable Updatable No Yes
RLM: Workflow Enabled Updatable Updatable Updatable Updatable Updatable No No

RLM: Debug Mode

Determines if a debug file is written for running the Demand Processor. Available values are:

The default value is Null (Off).

This profile is updatable at all levels.

RLM: MRP Forecast Selection List

Provides a means to specify the forecast source list that will house all the names of forecasts that are candidates for the inbound Automotive forecast demand items to be assigned.

The default value is none.

This profile can be set at the Site and Responsibility levels.

Note: This profile option is required if you import forecast data into Oracle Advanced Planning and Scheduling using the Demand Time Fence Forecast to Planning. See Processing Rules for more information.

RLM: MSC/MRP Default Assignment Set

Determines if the Supply Chain Sourcing Rules should be used to derive the ship from organizations. If these rules should be used (the profile option is set to something other than No Sourcing to be applied) the Demand Processor looks for a unique Sourcing rule for the item. If a unique rule is found, then this is the rule that is used. If more than one rule exists for the item, then the default assignment set designated in the profile option is used to determine which rule should be used.

The default is No Sourcing to be applied.

This profile is updatable only at the site level.

RLM: Print CUM Data on Shipping Documents

Determines whether or not CUM data should be printed on shipping documents. Available values are:

The default is Yes.

This profile is updatable at all levels.

RLM: Workflow Enabled

Determines whether or not the Demand Processor is enabled to run in workflow mode. Available values are:

The default is No.

This profile is updatable at all levels.

Other Necessary Profiles

This table includes profile options from other applications that you must set for full Oracle Release Management functionality.

You can set or view the following profile options in Oracle Release Management. The table also indicates whether you (the “User”) can view or update the profile option and at which System Administrator level the profile options can be updated. The System Administrator level includes User, Responsibility, Application, and Site levels. Profile options are either Optional or Required:

The following terms are used in the table to identify if you can view or update the profile option information:

Oracle Release Management Profile Options
Profile Option User System Admin. User System Admin. Resp. System Admin. App. System Admin. Site Required Default Value
ECE: DSNO- Enabled View only No Update or View No Update or View No Update or View Updatable No No default
ECE: INO- Enabled View only No Update or View Updatable No Update or View Updatable No No default
ECE: Input File Path View only No Update or View Updatable No Update or View Updatable Yes No default
ECE: Output File Path View only No Update or View Update No Update or View Updatable Yes No default
ECE: PSQI- Enabled View only No Update or View Updatable No Update or View Updatable Yes No default
ECE: SPSI- Enabled View only No Update or View Updatable No Update or View Updatable Yes No default
ECE: SSSI- Enabled View only No Update or View Updatable No Update or View Updatable Yes No default
OM: Invoice Numbering Method No Update or View No Update or View No Update or View No Update or View Updatable Yes Automatic
MO: Security Profile Updatable Updatable Updatable No Update or View Updatable Yes No default
MO: Default Operating Unit Updatable Updatable Updatable No Update or View No Update or View Yes No default

ECE: DSNO Enabled

Specifies whether or not the DSNO transaction is enabled.

There is no default value.

This profile can only be set at the site level.

ECE: INO Enabled

Specifies whether or not the INO transaction is enabled at the site level.

There is no default value.

This profile can only be set at the site and responsibility levels.

ECE: Input File Path

Specifies the directory where inbound data files are expected. This value must match the actual directory on disk and that designated in the INIT.ORA file.

There is no default value.

This profile can only be set at the site and responsibility levels.

ECE: Output File Path

Specifies the directory where outbound interface data files are written. This value must match the actual directory on disk and that designated in the INIT.ORA file.

There is no default value.

This profile can only be set at the site and responsibility levels.

Note: For e-Commerce Gateway, you must create inbound and outbound directories on your server, and then specify them in the INIT.ORA file and in the ECE: Inbound File Path and ECE: Out­bound File Path profile options, respectively. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.

ECE: PSQI Enable

Determines whether or not inbound sequenced shipping schedule transaction is enabled.

There is no default value.

This profile can only be set at the site and responsibility levels.

ECE: SPSI Enabled

Determines whether or not inbound planning schedule transaction is enabled.

There is no default value.

This profile can only be set at the site and responsibility levels.

ECE: SSSI Enabled

Determines whether or not inbound shipping schedule transaction is enabled.

There is no default value.

This profile can only be set at the site and responsibility levels.

OM: Invoice Numbering Method

Determines whether invoice numbers are automatically generated or mapped to the delivery name. Available values are:

MO: Security Profile

Determines whether you have access to one, multiple, or all multiple organizations operating units through a single responsibility.

There is no default value.

This profile can only be set at the site and responsibility levels.

See: Oracle Applications Multiple Organizations Implementation Guide.

MO: Default Operating Unit Profile

Determines operating unit as the default operating unit value.

There is no default value.

This profile can only be set at the site and responsibility levels.

See: Oracle Applications Multiple Organizations Implementation Guide.