This chapter covers the following topics:
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.
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.
To run the Demand Status Inquiry Report:
Through Reports on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Demand Status Inquiry Report from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
The following parameters are included in the Demand Status Inquiry Report.
Define the title that will be printed on the report. The default is Demand Status Inquiry Report.
Select the operating unit name. This parameter is mandatory.
Enter the shipping organization or supplier to limit the report to demand for a specific organization.
Enter the customer name to limit the report to demand for a specific customer.
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.
Enter the delivery location to limit the report to demand for a specific location associated with the selected trading partner.
Select a range of sales orders to limit the report to requirements associated with a specific range of sales orders.
Enter beginning and ending requirement dates to limit the report to requirements within a specific range of scheduled ship dates.
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.
Select a range of items to be printed in the report.
Select the desired requirement status for the report: firm, forecast, or both. The default is Both.
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.
Shipped includes only shipped sales order lines or release order lines; excludes unshipped and canceled lines. This option supersedes the value for the Include Canceled Lines parameter.
Unshipped includes only unshipped sales order lines or release order lines; excludes shipped lines. Canceled lines can be included or excluded based on the value for the Include Canceled Lines parameter.
Both includes both shipped and unshipped sales order lines or release order lines. Canceled lines can be included or excluded based on the value for the Include Canceled Lines parameter.
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.
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.
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.
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.
To run the Net Change Report:
Through Reports on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Net Change Report from the available list of values.
Enter required and optional parameters.
Click Submit.
Define the title that will be printed on the report. The default is Net Change Report.
Select the operating unit name. This parameter is mandatory.
Enter the external customer for which this report is to be run. This field is mandatory if no trading partner is selected.
Select the schedule type to be compared: Planning/Release, Sequenced or Shipping.
Enter a new schedule number to restrict the report to specific schedule numbers.
Enter a valid old schedule number. This schedule must be of the same type as the schedule entered in New Schedule.
Enter the ship-from location for which this report is to be run.
Enter the shipping address for which this report is to be run. You can enter the address of a related ship-to customer.
Select a customer item starting range for the schedules to be compared. This field is mandatory if Customer Item End is completed.
Select a customer item ending range for the schedules to be compared. This field is mandatory if Customer Item Start is completed.
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.
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.
Enter Yes to include authorized quantities in this report. The default value is Yes.
Enter Yes to include other detail types in the report. The default value is Yes.
Enter Yes to include lines with no change in this report. The default value is No.
Include in the report only those lines changed by at least this percentage. The default value is 0 percent.
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:
Customer, billing, and shipping addresses must exist in Accounts Receivables,
Orders, including Sales Order and Order Type, or Sales Agreement and Agreement Type, must already exist in Order Management.
Items must be active items defined in Inventory.
Forecast names must be defined in Advanced Planning and Scheduling.
Redundant firm requirements are encountered.
A discrepancy is found in the CUM.
The Release Management Exceptions Report prints a report cover page section and a report main section that includes:
Request ID and schedule header identifiers
Sales order number, sales order type and message category or sales agreement number, sales agreement type, and message category
Schedule line identifiers and exception message text
Optional detailed exception text
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.
Through Reports on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Release Management Exceptions Report from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
Select the operating unit name. This parameter is mandatory.
Enter a range of request numbers to limit the report to exceptions noted for specific request identifiers.
Enter the shipping location to limit the report to exceptions noted for a specific location.
Enter a range of customer names to limit the report to exceptions noted for specific customers.
Enter a range of trading partners to limit the report to exceptions noted for specific trading partners.
Enter the trading partner location to limit the report to exceptions noted for a specific trading partner location.
Enter a range of customer items to limit the report to exceptions noted for specific customer items.
Enter a range of inventory items to limit the report to exceptions noted for specific items.
Enter a range of sales order numbers to limit the report to exceptions noted for specific sales order numbers.
Enter a range of active sales order types to limit the report to exceptions noted for specific sales order types.
Enter a range of schedule numbers to limit the report to exceptions noted for specific schedules.
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.
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:
Error
The report will include only fatal errors. Warnings and informational messages will not print.
Warning
The report will include fatal errors and warnings, but informational messages will not print. This is the default.
Information
The report will include fatal errors, warnings, and informational messages.
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.
Enter a range of dates to limit the report to exceptions generated on a specific date.
Select from a list of criteria to sort the report using a specific parameter value.
The EDI Inbound Transactions concurrent program enables you to process an EDI transaction and load Release Management interface tables.
Through Process Inbound Transactions on the menu, navigate to the Submit Requests window.
Select Single Request.
Select EDI Inbound Transactions from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
Select the operating unit name. This parameter is mandatory.
Enter the location of the inbound flat file. The default value is the current value set for the profile option ECE: Input File Path.
Enter the name of the inbound transaction.
Select the transaction type from the list of values for this inbound transaction. The default is SPSI.
Select the map code, as defined in the e-Commerce Gateway, from the list of values.
Select the level of detail for the debug mode. The default value is 0.
Enter Yes to execute the Demand Processor. Enter No to bypass immediate execution of the Demand Processor. The default is No.
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'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:
EDI planning, shipping, and production sequence schedules processed through the e-Commerce Gateway
XML planning and shipping schedules processed through the XML Gateway
Manually entered schedules via the Release Management Workbench
External system schedules loaded into the Demand Processor interface via a custom process
The Demand Processor performs the following procedures:
Defaulting, Derivation, and Validation of schedule.
Archive validated schedule.
Manage New Demand: CUM discrepancy check, cumulative to discrete demand quantity conversion, application of Supply Chain Sourcing Rules, application of delivery pattern rule and lead time offset to calculate ship/delivery dates, check customer's receipt or shipment to calculate in-transit, application of frozen, firm and forecast fences, aggregation of demand, and rounding to standard pack quantity using the Processing Rules in effect for a particular ship-from, customer, ship-to, or customer item.
Reconcile Old/New Demand: Processing appropriate for schedule purpose code, getting eligible and matching sales order lines, performing reconciliation of customer and supplier shipments, cancellation or reconciliation of Past Due sales order lines, reconciliation of Restricted demand, matching of new demand to existing sales order lines, and updating the sales order or the release orders forecast.
The Demand Processor generates appropriate warning and error exceptions and informational messages during each step.
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:
Define Customer Addresses. See: Define Customer Addresses, Oracle Receivables User's Guide, Oracle Receivables User's Guide.
Define Customer Receiving Calendar. See: Defining Transportation Calendars, Oracle Shipping Execution User's Guide, Oracle Shipping Execution User's Guide.
Define Warehouse Shipping Calendar. See: Defining Transportation Calendars, Oracle Shipping Execution User's Guide, Oracle Shipping Execution User's Guide.
Set up shipment delivery rules. See: Overview of Shipment Delivery Rules.
You should perform the following tasks for each customer that sends demand transactions:
Define transportation lead times. See: Release Management Processing Rules .
Define Intransit Calculation Basis on Shipment, Receipt, Match on Partially Shipped Lines, or None. See: Release Management Processing Rules .
Verify the system defined ship delivery pattern rules.
Add ship delivery pattern rules.
Determine default ship delivery pattern for each processing rule. See:Ship Delivery Pattern Rules
Define Release Management processing rules.
Using the Release Management Processing Rules window, set up relationships among the ship-from organizations, customers, addresses, and customer items defining attributes that are dependent on this relationship and used in the Release Management Demand Processor. Identify the sales order or sales agreement to which all demand for the customer item should be loaded. Optionally, define the standard pack quantity, rounding rule, intransit lead time, and calculation basis. Optionally, select a Default Ship From value. See: Processing Rules.
Set up Supply Chain sourcing rules
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.:-
the customer demand schedule specifies an incorrect ship-from organization for the customer item
Define a new sourcing rule for the schedule's ship-from organization or the default warehouse associated with the customer ship-to site, with shipping organization type of “Make At” and allocation percentages for the desired ship-from organization(s). Then, create an assignment set for the sourcing rule, and assign the sourcing rule to the ship-to customer and site, and to the most preferred inventory item for the customer item specified on the customer demand schedule.
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.
Through Demand Transactions on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Release Management Demand Processor from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
Select the operating unit name. This parameter is mandatory.
Select a code from the list of valid purpose codes to limit processing to demand schedules of a specific purpose code type.
Enter a range of dates to limit processing of demand schedules within certain Generation Dates.
Enter the customer code to limit processing to demand schedules for a particular customer.
Enter the shipping address to limit processing to demand schedules for a specific shipping address.
Enter the supplier code for the particular ship-to location. This parameter is disabled when the schedule number is defined.
Enter the schedule number to limit processing to a specific demand schedule
Enter yes to receive a warning for dropped items.
Enter yes to order schedules by schedule type first.
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.
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.
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.
To run the Release Management Purge Schedule, Option 1:
Through Demand Transactions on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Release Management Purge Schedule from the available List of Values.
Enter required and optional parameters.
Select Submit to submit the process.
To run the Release Management Purge Schedule, Option 2:
Navigate to Release Management Workbench Tools Menu.
Enter required and optional parameters.
Select Submit to submit the process.
The Release Management Purge Schedule program has the following parameters in the Parameters field of the Run Concurrent Programs window:
Select the operating unit name. This parameter is mandatory.
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.
Enter the range of Trading Partners to limit the Purge process to schedules associated with specified trading partners.
Enter the customer name to limit the purge process to schedules associated with a specified customer name.
Enter the ship-to address range to limit the purge process when a single trading partner is specified.
Enter a specific date range to purge schedules that have an issue date that is within the range.
Enter a specific schedule type to limit the purge to a particular schedule type.
If you want to purge a single schedule, enter the schedule reference number.
Enter a number so that any schedules that are older than the specified number of days will be deleted.
Enter No if you do not want schedules with authorizations deleted. The default is No.
Select the schedule status to limit the purge process to schedules associated with a schedule status. The default is All Values.
Use the Adjust CUM Transactions CUM Key ID concurrent program to:
Change the CUM key identifier on previously shipped Release Management sales order lines or release order if the customer has reset the CUM by back-dating the current cumulative start date.
Assign a Cum Key ID in the case of a new installation of Release Management on an existing installation of Order Management, where shipped sales order lines or release order lines exist.
Assign a CUM Key ID if the customer turns on CUM management after Release Management has been in use for that customer.
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:
Bill-To/Ship-From
Select sales order lines or release order lines associated with the specified shipping location and the corresponding billing location and shipping organization.
Ship-To/Ship-From
Select sales order lines or release order lines associated with the specified shipping location and shipping organization.
Intermediate Ship-To/Ship-From
Select sales order lines or release order lines associated with the specified intermediate shipping location and shipping organization.
Ship-To/All Ship-Froms
Select sales order lines or release order lines associated with the specified shipping location without regard to shipping organization.
This program is applicable only to the following CUM management types:
By date only
By date and record year
By date and purchase order
Before using the Adjust CUM Transactions CUM Key ID program, you should:
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.
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.
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.
Create a Cum Key. See: Creating a CUM Key.
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.
To run CUM Transactions CUM Key Adjustment:
Through CUM Key Adjustment on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Cum Transactions Cum Key Adjustment from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
The Adjust CUM Transactions CUM Key ID program has the following parameters in the Parameters field of the Run Concurrent Programs window:
Select the operating unit name. This parameter is mandatory.
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.
Enter the customer to whom the shipment transaction CUM identifier adjustment applies.
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.
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.
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.
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.
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.
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
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.
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:
Planning/Material Release
Shipping
Production Sequence
Customer demand schedules processed by the Release Management Demand Processor can come from any of the following sources:
Inbound electronic schedules via the EDI Gateway
Manually entered schedules via the Release Management manual schedule Entry window
Schedules loaded from another external system into the Release Management Demand Processor interface tables
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:
Applicable Schedule Type, Horizon, and Purpose Code.
Applicable Frozen, Firm, and Forecast Time Fences.
Applicable Shipment/Delivery Codes.
In Transit time.
To run the Demand Status Report:
Through Reports on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Demand Status Report from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
Select the operating unit name. This parameter is mandatory.
Enter the schedule reference number for the given requirement.
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.
Enter Customer Name to which this Demand Status Report is to be run.
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.
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.
Select the Schedule Types to be compared.
Enter the From and To Trading Partner for which you want to limit the report.
Enter the From and To Trading Partner Location Code for which you want to limit the report.
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.
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.
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.
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.
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.
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.
Enter the Ending Production Sequence number for which you want to run this report. This field applicable for sequence Schedule only. No default exists.
Should lines that have not been changed be included in the report? The default value is No.
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.
Trading Partner requirements reflected in sales order demand come from the following sources:
The netted result of any of three types of customer demand schedules processed by the Release Management system via the Demand Processor:
Planning / Material Release
Shipping
Production Sequence
Manual entry on a sales order with a Release Management sales order type
Customer demand schedules processed by the Oracle Release Management Demand Processor can come from any of the following sources:
Inbound electronic schedules via the EDI Gateway
Manually entered schedules via Release Management Manual Schedule Entry window
Schedules loaded from another external system into the Release Management Demand Processor interface tables
To run the Schedule / Release Report:
Through Reports on the menu, navigate to the Submit Requests window.
Select Single Request.
Select Schedule / Release Report from the available list of values.
Enter required and optional parameters.
Select Submit to submit the process.
Select the operating unit name. This parameter is mandatory.
Enter the name of the customer for whom you want to print the report
Enter the schedule type for which you want to limit the report. The available values are Planning, Shipping, and Production Sequence.
Enter the schedule reference number of the schedule for which you want to generate the report.
Enter the Ship From organization if you want to limit the report to print the schedules of a specific ship from organization.
Enter the Ship To location if you want to limit the report to print the schedules of a specific ship to location.
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.
The source of the schedule. For example, the name of the EDI transaction (such as 830, 862, or 866) or Manual.
Enter the horizon start and end dates for which you want to limit the report.
Enter the From and To values of the issue date for which you want to print the report.
Enter the From and To trading partner for which you want to limit the report.
Enter the From and To trading partner location code for which you want to limit the report.
Enter the From and To processed date if you want to limit the report based on the processed date.
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.