Reports and Processes

This chapter covers the following topics:

Overview of Reports and Processes

Release Management provides you with a variety of reports that display release and demand management information and processes that enable the automation of the Release Management process. Each of the following sections includes an overview of the report and the submission process, as well as a description of submission parameters.

Reports

Process Inbound Transactions

Demand Transactions

CUM Key Adjustment

Demand Status Inquiry Report

The Demand Status Inquiry Report provides date about netted demand, demand in the context of CUM Management, and current resource authorizations issued by trading partners. Use this report to see details about sales order demand or sales agreement demand for a particular warehouse, customer, customer ship-to, or item in Order Management.

The Demand Status Inquiry Report prints the Firm and Forecast Requirements from Order Management. This report includes information about the customer item, requirement date, order number, address abbreviation, unit of measure, required quantity, shipped quantity, cancelled quantity, pick released quantity, back-ordered quantity, invoiced quantity, job number, and production sequence number.

Submission

To run the Demand Status Inquiry Report:

  1. Through Reports on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Demand Status Inquiry Report from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

The following parameters are included in the Demand Status Inquiry Report.

Title

Define the title that will be printed on the report. The default is Demand Status Inquiry Report.

Operating Unit

Select the operating unit name. This parameter is mandatory.

Ship-From

Enter the shipping organization or supplier to limit the report to demand for a specific organization.

Customer Name

Enter the customer name to limit the report to demand for a specific customer.

Ship-To

Enter the shipping address to limit the report to demand for a specific shipping location associated with the selected trading partner. You can select the address of a related ship-to customer.

Intermediate Ship-To

Enter the delivery location to limit the report to demand for a specific location associated with the selected trading partner.

Sales Order Range

Select a range of sales orders to limit the report to requirements associated with a specific range of sales orders.

Requirement Date Range

Enter beginning and ending requirement dates to limit the report to requirements within a specific range of scheduled ship dates.

(C)ustomer or (I)nventory Item

Enter “I” to limit the report to requirements for a range of inventory items. You can then enter a range of inventory items for the report.

Enter “C” to limit the report to requirements for a range of customer items. You can then enter a range of customer items for the report.

Item Range

Select a range of items to be printed in the report.

Requirements (F)irm, F(O)recast, (B)oth

Select the desired requirement status for the report: firm, forecast, or both. The default is Both.

(S)hipped, (U)nshipped or (B)oth

Select from the options for reporting on sales order lines or release order lines based on their shipment status: Shipped, Unshipped, or Both. The default is Both.

Include Canceled Lines (Y/N)

Enter Yes to include fully canceled sales order lines or release order lines. Enter No to omit canceled sales order lines or release order lines. The default is No.

Summarize by Date & Bucket (Y/N)

Enter Yes to summarize demand from sales order lines or release order lines that have the same requirement date and bucket. Enter No to view specific identifiers that have resulted in multiple sales order lines or release order lines for the same requirement date and bucket. The default is No.

Include Current Resource Authorizations (Y/N)

Enter Yes to include current resource authorizations on the report. Enter No to omit current resource authorizations. The Current Resource Authorizations section of the report will print only that demand from planning and /release schedules that include resource authorizations. The default is Yes.

Net Change Report

The Net Change Report displays any changes that a trading partner has made to requirements based on a comparison of any two schedules. Use this report to track increases or decreases in requirements from the trading partner. This report better enables you to monitor requirement fluctuations for seasonal or sporadic changes. This report better enables you to monitor changes by customer, customer ship-to, item, or item range. You can define a percentage of change acceptable and report only those items that change outside of the tolerance limits.

The information contained in this report is obtained from archived schedule data within Release Management. This report can only be run for those schedules which have been successfully validated and archived.

Submission

To run the Net Change Report:

  1. Through Reports on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Net Change Report from the available list of values.

  4. Enter required and optional parameters.

  5. Click Submit.

Parameters

Title

Define the title that will be printed on the report. The default is Net Change Report.

Operating Unit

Select the operating unit name. This parameter is mandatory.

Customer

Enter the external customer for which this report is to be run. This field is mandatory if no trading partner is selected.

Schedule Type

Select the schedule type to be compared: Planning/Release, Sequenced or Shipping.

New Schedule

Enter a new schedule number to restrict the report to specific schedule numbers.

Old Schedule

Enter a valid old schedule number. This schedule must be of the same type as the schedule entered in New Schedule.

Ship-From

Enter the ship-from location for which this report is to be run.

Ship-To

Enter the shipping address for which this report is to be run. You can enter the address of a related ship-to customer.

Customer Item Start

Select a customer item starting range for the schedules to be compared. This field is mandatory if Customer Item End is completed.

Customer Item End

Select a customer item ending range for the schedules to be compared. This field is mandatory if Customer Item Start is completed.

Production Sequence Start

Enter a date for the customer's production sequence starting range for the schedules to be compared. This field is mandatory if Production Sequence End is completed.

Production Sequence End

Enter a date for the customer's production sequence ending range for the schedules to be compared. This field is mandatory if a Production Sequence Start is completed.

Include Authorization Quantity (Y/N)

Enter Yes to include authorized quantities in this report. The default value is Yes.

Include Other Detail (Y/N)

Enter Yes to include other detail types in the report. The default value is Yes.

Include Lines with no change (Y/N)

Enter Yes to include lines with no change in this report. The default value is No.

Include Percentage Change More Than

Include in the report only those lines changed by at least this percentage. The default value is 0 percent.

Release Management Exceptions Report

The Release Management Exceptions Report provides explanatory information for errors generated when a problem is encountered during demand processing. These are examples of exceptions generated when requirements have not been met:

Submission

The Release Management Exceptions Report is automatically generated when the Demand Processor runs if exceptions (information, warning and error) were generated during processing. See: Release Management Demand Processor.

To run the Release Management Exceptions Report manually:

  1. Through Reports on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Release Management Exceptions Report from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

Operating Unit

Select the operating unit name. This parameter is mandatory.

Request ID Range

Enter a range of request numbers to limit the report to exceptions noted for specific request identifiers.

External Ship-From

Enter the shipping location to limit the report to exceptions noted for a specific location.

External Customer Name Range

Enter a range of customer names to limit the report to exceptions noted for specific customers.

Trading Partner Range

Enter a range of trading partners to limit the report to exceptions noted for specific trading partners.

External Trading Partner Location

Enter the trading partner location to limit the report to exceptions noted for a specific trading partner location.

External Customer Item Range

Enter a range of customer items to limit the report to exceptions noted for specific customer items.

Inventory Item Range

Enter a range of inventory items to limit the report to exceptions noted for specific items.

Sales Order Number Range

Enter a range of sales order numbers to limit the report to exceptions noted for specific sales order numbers.

Sales Order Type Range

Enter a range of active sales order types to limit the report to exceptions noted for specific sales order types.

Schedule Number Range

Enter a range of schedule numbers to limit the report to exceptions noted for specific schedules.

Message Category Range

Enter a range of exception message categories to limit the report to specific message categories. Leave this field blank to include all message categories in the report.

Exception Severity

Enter exception severity to limit the report to a minimum level of exception severity. Exception severity may be reported at an error, warning, or information level:

Print Details

Enter Yes to display the report with detailed information including incoming schedule and matching sales order lines or release order lines. Enter No for a simple view of the report. The default is No.

Creation Date Range

Enter a range of dates to limit the report to exceptions generated on a specific date.

Sort by

Select from a list of criteria to sort the report using a specific parameter value.

EDI Inbound Transactions

The EDI Inbound Transactions concurrent program enables you to process an EDI transaction and load Release Management interface tables.

Submission

To run EDI Inbound Transactions:

  1. Through Process Inbound Transactions on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select EDI Inbound Transactions from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

Operating Unit

Select the operating unit name. This parameter is mandatory.

Inbound File Path

Enter the location of the inbound flat file. The default value is the current value set for the profile option ECE: Input File Path.

Inbound File Name

Enter the name of the inbound transaction.

Transaction Type

Select the transaction type from the list of values for this inbound transaction. The default is SPSI.

Map Code

Select the map code, as defined in the e-Commerce Gateway, from the list of values.

Debug Mode?

Select the level of detail for the debug mode. The default value is 0.

Execute DSP Flag?

Enter Yes to execute the Demand Processor. Enter No to bypass immediate execution of the Demand Processor. The default is No.

Issue Warning for Dropped Items

This field is only active if the Execute DSP Flag is set to Yes. Enter Yes to get a warning for dropped items.

Release Management Demand Processor

Release Management's processing engine, the Demand Processor is an Open Interface that provides complete default, derivation, and validation for inbound demand schedules regardless of their source. The Demand Processor can process customer demand schedules from diverse sources, including:

The Demand Processor generates appropriate warning and error exceptions and informational messages during each step.

Prerequisites

To ensure that the Demand Processor works effectively, you should prepare Order Management and Release Management for any new customer demand data that you want to import, including customers, pricing agreements, items, shipment and delivery rules, and CUM Management.

Before using the Demand Processor, you should:

You should perform the following tasks for each customer that sends demand transactions:

You can define the schedule sourcing and splitting rules using the Supply Chain Sourcing Rules window if the customer demand schedule specifies an incorrect ship-from organization for the customer item.:-

Workflow

Release Management is workflow-enabled in Release 12. By setting the RLM: Workflow Enabled profile option, you can run the Demand Processor with or without the workflow option.

Submission

To run the Release Management Demand Processor:

  1. Through Demand Transactions on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Release Management Demand Processor from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

Operating Unit

Select the operating unit name. This parameter is mandatory.

Schedule Purpose Code

Select a code from the list of valid purpose codes to limit processing to demand schedules of a specific purpose code type.

Issue Date Range

Enter a range of dates to limit processing of demand schedules within certain Generation Dates.

Trading Partner Range

Enter the customer code to limit processing to demand schedules for a particular customer.

TP Location Code Range

Enter the shipping address to limit processing to demand schedules for a specific shipping address.

The Ship From External

Enter the supplier code for the particular ship-to location. This parameter is disabled when the schedule number is defined.

Schedule Reference Number

Enter the schedule number to limit processing to a specific demand schedule

Issue Warnings for Dropped Items

Enter yes to receive a warning for dropped items.

Order Schedules by Schedule Type First

Enter yes to order schedules by schedule type first.

Maximum Number of Child Processes

Enter the maximum number of child processes to be spawned. A null, zero, or 1 value means that the Demand Processor will process all Sales Orders, Blanket Orders, or both associated with the schedule sequentially. A value greater than 1 means that orders are processed in parallel, which results in improved performance.

Release Management Purge Schedule

The Release Management Purge Schedule is used to purge unnecessary archived schedules from the system. It enables you to purge schedules based on specified criterion. It will not allow you to purge schedules that have a link to an active order line.

Prerequisites

To be able to purge a schedule, it must have no link to active order lines, that is, the order lines must be completely processed.

Submission

To run the Release Management Purge Schedule, Option 1:

  1. Through Demand Transactions on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Release Management Purge Schedule from the available List of Values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

To run the Release Management Purge Schedule, Option 2:

  1. Navigate to Release Management Workbench Tools Menu.

  2. Enter required and optional parameters.

  3. Select Submit to submit the process.

Parameters

The Release Management Purge Schedule program has the following parameters in the Parameters field of the Run Concurrent Programs window:

Operating Unit

Select the operating unit name. This parameter is mandatory.

Execution Mode

Enter the execution mode: View Purge Schedules to preview the available schedules to purge or Purge Schedules to purge the schedules that match the entered parameters.

Trading Partner Range

Enter the range of Trading Partners to limit the Purge process to schedules associated with specified trading partners.

Customer Name

Enter the customer name to limit the purge process to schedules associated with a specified customer name.

Ship-To Address Range

Enter the ship-to address range to limit the purge process when a single trading partner is specified.

Schedule Issue Date Range

Enter a specific date range to purge schedules that have an issue date that is within the range.

Schedule Type

Enter a specific schedule type to limit the purge to a particular schedule type.

Schedule Reference Number

If you want to purge a single schedule, enter the schedule reference number.

Delete Beyond Days

Enter a number so that any schedules that are older than the specified number of days will be deleted.

Delete Schedules with Authorizations? (Y/N)

Enter No if you do not want schedules with authorizations deleted. The default is No.

Schedule Status

Select the schedule status to limit the purge process to schedules associated with a schedule status. The default is All Values.

CUM Transactions CUM Key Adjustment

Use the Adjust CUM Transactions CUM Key ID concurrent program to:

This applies to the CUM key ID on the shipment transactions and on the CUM adjustment transactions that have occurred since the start of the new CUM rule.

The following values of CUM Org Level determine which sales order lines or release order lines will be selected and updated in this program:

This program is applicable only to the following CUM management types:

Prerequisites

Before using the Adjust CUM Transactions CUM Key ID program, you should:

  1. Set Up CUM Management.

    Define the CUM Rule for each customer destination and establish each customer item's initial CUM quantity value based on the CUM Rule defined.

    • Use the processing rules window to set up the CUM Management Rule for each customer destination sending demand transactions.

  2. Set Up Customer Items for Release Management.

    Define ship-from/ship-to relationships for each customer item using the Processing Rules window. For each shipping organization effective for the customer item, identify the sales order or sales agreement to which all demand for the customer item should be loaded. Optionally, define standard pack quantity and rounding rule, and the lead time for shipment date calculations.

  3. Have sales order or release order shipments of Release Management demand.

    A sales order line or release order line must have a matching value for each applicable component of the CUM Key to be processed in the Adjust CUM Transactions CUM Key ID program.

  4. Create a Cum Key. See: Creating a CUM Key.

  5. In order to process all sales order lines, you must ship all sales order lines that correspond to the active CUM Key, or bring in a new customer schedule that will update the open order lines with the new CUM key information.

Submission

To run CUM Transactions CUM Key Adjustment:

  1. Through CUM Key Adjustment on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Cum Transactions Cum Key Adjustment from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

The Adjust CUM Transactions CUM Key ID program has the following parameters in the Parameters field of the Run Concurrent Programs window:

Operating Unit

Select the operating unit name. This parameter is mandatory.

Ship-From Organization

Enter the shipping organization to which the shipment transaction CUM identifier adjustment applies. You can choose from any inventory organization that has been defined as a ship-from business entity for the customer in Release Management.

Customer Name

Enter the customer to whom the shipment transaction CUM identifier adjustment applies.

Ship-To Organization

Enter the shipping address of the customer to which the CUM identifier adjustment applies. You can choose from any address for the customer that is currently assigned a ship-to business purpose.

Intermediate Ship-To Organization

If the CUM organization level for this ship-from/ship-to business entity is intermediate ship-to, enter the intermediate shipping location of the customer to which the CUM identifier adjustment applies. You can choose from any address for the customer that is currently assigned a ship-to business purpose.

Bill-To Location

If the CUM organization level for this ship-from/ship-to business entity is bill-to/ship-from, enter the billing address of the customer to which the CUM identifier adjustment applies. You can choose from any customer address currently assigned a bill-to business purpose. This field is provided by default to the billing address associated with the specified shipping address.

Customer Item

Select a customer item from which you want to adjust the CUM key from the list of values. If no selection is made here, all the customer items for the above selected criteria will be adjusted.

Transaction Start Date

Enter the shipment transaction start date. Shipment transactions within the range you specify will be eligible for CUM identifier adjustment if they are associated with the eligible CUM key components. This date must be less than the shipment transaction end date.

Transaction End Date

Enter the shipment transaction end date. Shipment transactions within the range you specify will be eligible for CUM identifier adjustment if they are associated with the eligible CUM key components. This date must be greater than the shipment transaction start date. The default is the current system date.

Related Topics

Processing Rules

Compare Schedule to Demand Report

The Compare Schedule to Demand Report provides a reporting tool that facilitates the comparison of a Processed and Partially Processed Schedule to the sales order demand.

Sources of Sales Order Demand

Trading Partner requirements reflected in sales order demand can come from the processing of any of three types of customer demand schedules processed the Release Management system via the Demand Processor:

Sources of Schedules

Customer demand schedules processed by the Release Management Demand Processor can come from any of the following sources:

This report compares the requested quantity of an item in the Processed Schedule to the quantity that was interfaced into the sales order for the given requested date.

The sales order lines reflect the demand for an item for a given Schedule processed by the Demand Processor. The discrepancy between the item quantity in the given Processed Schedule and the quantity that was interfaced into the sales order might be due to:

Submission

To run the Demand Status Report:

  1. Through Reports on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Demand Status Report from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

Operating Unit

Select the operating unit name. This parameter is mandatory.

Schedule Reference Num (Optional)

Enter the schedule reference number for the given requirement.

Customer Name From (Optional / Mandatory)

Enter the Customer Name from which this Demand Status Report is to be run. This parameter is mandatory if no schedule reference number is specified.

Customer Name To (Optional)

Enter Customer Name to which this Demand Status Report is to be run.

Ship From (Optional / Mandatory)

Enter Plant (or Ship From) for which this Demand Status Report is to be run. This field is mandatory if no customer is selected and if ship from is selected.

Ship To (Optional / Mandatory)

Enter a ship-to location for which this Demand Status Report is to be run. This field is mandatory if no customer is selected and if ship from is selected.

Schedule Type (Optional)

Select the Schedule Types to be compared.

TP Code Range (Optional)

Enter the From and To Trading Partner for which you want to limit the report.

TP Location Code Range (Optional)

Enter the From and To Trading Partner Location Code for which you want to limit the report.

Request Date Range (Optional)

Enter the From and To Date if you want to limit the report to requirements within a specific range of Customer request dates. No default exists.

Issue Date Range (Optional)

Enter the From and To Date if you want to limit the report to requirements within a specific range of Schedule Issue dates. No default exists.

Processed Date Range (Optional)

Enter the From and To Date if you want to limit the report to requirements within a specific range of Processed date range. No default exists.

Customer Item Range (Optional)

Enter the From and To Customer Item for which you want to run this report. This field is skipped if you do not choose to limit the report by Item. No default exists.

Internal Item Range (Optional)

Enter the From and To Internal Item for which you want to run this report. This field is skipped if you do not choose to limit the report by Item. No default.

Production Sequence Start (Optional)

Enter the Starting Production Sequence number for which you want to run this report. This field is applicable for a sequence Schedule only. No default exists.

Production Sequence End (Optional)

Enter the Ending Production Sequence number for which you want to run this report. This field applicable for sequence Schedule only. No default exists.

Include Lines with No Change? (Mandatory)

Should lines that have not been changed be included in the report? The default value is No.

Schedule/Release Report

Schedule/Release Report provides you with a reporting tool to print raw or processed schedules. The report should be similar to what is presented on the Release Management Workbench. This report will facilitate the reconciliation process for large schedules.

Sources of Demand

Trading Partner requirements reflected in sales order demand come from the following sources:

Sources of Schedules

Customer demand schedules processed by the Oracle Release Management Demand Processor can come from any of the following sources:

Submission

To run the Schedule / Release Report:

  1. Through Reports on the menu, navigate to the Submit Requests window.

  2. Select Single Request.

  3. Select Schedule / Release Report from the available list of values.

  4. Enter required and optional parameters.

  5. Select Submit to submit the process.

Parameters

Operating Unit

Select the operating unit name. This parameter is mandatory.

Customer Name (Optional)

Enter the name of the customer for whom you want to print the report

Schedule Type (Optional)

Enter the schedule type for which you want to limit the report. The available values are Planning, Shipping, and Production Sequence.

Schedule Reference Num (Optional)

Enter the schedule reference number of the schedule for which you want to generate the report.

Ship From (Optional)

Enter the Ship From organization if you want to limit the report to print the schedules of a specific ship from organization.

Ship To (Optional)

Enter the Ship To location if you want to limit the report to print the schedules of a specific ship to location.

Schedule Purpose (Optional)

Enter the schedule purpose code if you want to limit the report to print the schedules for a specific schedule purpose code. It can have values such as Original, Replace, Replace All, Add, and Update.

Schedule Source (Optional)

The source of the schedule. For example, the name of the EDI transaction (such as 830, 862, or 866) or Manual.

Horizon Date Range (Optional)

Enter the horizon start and end dates for which you want to limit the report.

Issue Date Range (Optional)

Enter the From and To values of the issue date for which you want to print the report.

Trading Partner Range (Optional)

Enter the From and To trading partner for which you want to limit the report.

TP Location Code Range (Optional)

Enter the From and To trading partner location code for which you want to limit the report.

Processed Date Range (Optional)

Enter the From and To processed date if you want to limit the report based on the processed date.

Process Status (Optional)

Use this parameter if you want to limit the report for a specific process status. It can have values such as Processed Successfully, Available toProcess, Error, and Partially Processed.