Skip Headers

Oracle Order Management User's Guide
Release 12.1
Part Number E13408-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Concurrent Programs

Details

All Order Management concurrent programs are classified as single-org, multi-org or global.

Single Org Concurrent Programs

You can run the following Concurrent Program for one Operating Unit (from the ones you have access to) at a time, without switching responsibility:

The mandatory Operating Unit parameter in the submit request window displays a default value.

Multi-Org Concurrent Programs

These programs have the Operating Unit as a parameter. You can run these Concurrent Programs either for an Operating Unit at a time (by specifying an Operating Unit value) or for all Operating Units that you have access to (by leaving the Operating Unit parameter blank):

For these programs the Operating Unit parameter in the submit request window is disabled and you can optionally specify an Operating Unit in the parameter window.

Operating Unit Sensitive Parameters

The parameter LOVs for Operating Unit sensitive data (see list below) show the Operating Unit name. If there is no default or user specified Operating Unit Value then the LOVs show data across all Operating Units accessible to you. If you have specified an operating unit, then the LOVs restrict data to that particular Operating Unit.

These are the various concurrent request parameters that are Operating Unit sensitive:

* - While the LOVs for these fields will show Operating Unit, if you do not specify an Operating Unit parameter, specifying these alone will not necessarily restrict output by Operating Unit. If you want to restrict data by Operating Unit, specify an operating unit as a parameter.

Important: It is recommended that if you want to pick Operating Unit sensitive parameter(s), you should first select the Operating Unit, as this will automatically restrict all the OU sensitive parameter LOVs to the selected Operating Unit.

In the case where you have not specified an Operating Unit and you then pick an Operating Unit sensitive parameter value, the Operating Unit parameter field will remain blank (it is not defaulted based on the other parameter value selection) and other OU sensitive parameter LOVs will continue showing data across all accessible OUs. Provided that all the different Operating Unit sensitive parameters are for the same OU then the program will process data in that specific Operating Unit alone. If they are not, then the concurrent program will process nothing.

Concurrent Programs that let users specify an Inventory Item value as a parameter: The LOV for the Item parameter relies on the Item Validation Org System Parameter. If you have specified an Operating Unit parameter, the item LOV will show data based on the Item Validation Org for that Operating Unit. If you have not specified an Operating Unit, then the LOV will show data based on the Item Validation Org for your default Operating Unit. If you do not have a default Operating Unit then the LOV will return no values.

Global Concurrent Programs

The following concurrent programs are global (process data across Operating Units).

For these programs the Operating Unit parameter in the submit request window is disabled and they do NOT have an Operating Unit parameter in the parameters window.

Schedule Orders Concurrent Program

You can schedule lines that have failed workflow scheduling by running the concurrent program. The concurrent program:

The Schedule Orders concurrent program scheduled only those lines that had failed workflow scheduling. In the current release, apart from being able to schedule lines that have failed workflow scheduling, manually entered lines in the Entered status can be scheduled periodically using the Schedule Orders concurrent program, or unscheduled lines imported in Entered status can be scheduled. Additionally, orders that have been imported and are in Entered status can also be scheduled using the enhanced Schedule Orders concurrent program.

If the program fails such as the schedule date for an item could not be found, Order Management returns an error for the line. The lines which fail scheduling can be scheduled in the next run of the program. All lines that are successfully scheduled are placed on demand and the next planning run and pick this line up as demand.

Schedule Orders concurrent program processes order lines you specify by using the parameters listed above, if the line is not already scheduled. The Schedule Orders Concurrent program performs the following:

For each line of the order, the Schedule Orders Concurrent Program:

User Procedures

  1. Navigate to the Run Requests window, and select Schedule Orders in the Name field.

    Schedule Orders Input Parameters Window

    the picture is described in the document text

  2. Determine the order(s) you wish to schedule. You can use the following parameters for scheduling orders:

    Note: A business flow could require a customer service representative (CSR) to enter orders without scheduling, to save time. Later, Schedule Orders will schedule the order lines.

  3. Select OK, then Submit

Sorting

You can sort the sequence of line scheduling; setting the scheduling priority, using the sorting parameters First Order By and Second Order By and the following:

For items with no supply constraints, all lines will schedule, lowering the dependence on the Sort By parameters. For ATP items, the Sort By parameter is useful, especially if an API is written to implement specific business rules.

Note: Note : Sorting is based on line level columns. Sorting for the Shipment Priority and Demand Class is based on the internal lookup codes and not the values

Schedule Date and Warehouse

You can query lines, and assign either a new Schedule Ship Date (this can be Schedule Ship Date or Schedule Arrival date; depending on the Order Date Type value) or Warehouse when re-scheduling a line, and have the flexibly to change to a location meeting the schedule requirements.

This is currently possible with Scheduling Across Orders (SAO), but for high volume, you can change the Schedule Date in batch mode.

Unscheduling

You can run this program with Scheduling mode set to ' Unschedule ' to unschedule all scheduled lines or using Schedule Orders concurrent program, you can choose to unschedule selected lines, formerly accomplished through the Sales Orders window.

Rescheduling

Schedule Orders provides two new scheduling modes to reschedule orders; Re-Schedule and Re-scheduling with Request Date. You can query scheduled lines and perform a reschedule. You can move schedules in and out based on the item’s availability, and if orders or delivery schedules from suppliers are changed or cancelled, then the allocated product can be rescheduled to meet other demands earlier or later.

Scheduling Mode

Schedule Orders concurrent program works for all unscheduled lines and the sales order lines may or may not be waiting at Schedule – Eligible activity.

Lines at Eligible Activity

Only selected lines waiting at the Schedule-Eligible workflow activity are selected. The default is no value entered. Note that the lines may or may not be scheduled and still could be waiting at the activity. If no value is entered for the Scheduling Mode parameter, this will be the default mode.

Schedule (all Unscheduled lines)

All unscheduled lines are chosen and scheduled. If a line is waiting at the Schedule-Eligible activity, then the activity is progressed after scheduling completion. You can also specify the Scheduling attributes (warehouse, date).

Unschedule: Unschedules all the selected lines. Only scheduled lines are queried.

Re-Schedule with Request Date:Lines are re-scheduled by using the Request Date instead of Schedule Ship Date or Schedule Arrival Date. Only scheduled lines will be queried.

Re-Schedule: Lines are re-scheduled by using the specified scheduling attributes (warehouse, date). If no scheduling attributes are entered, then the existing line level attributes (warehouse, date) will be used for re-scheduling.

If the re-scheduling action is not successful, then the line is left unchanged, so the line remains scheduled. You can avoid high-risk failures by performing an unschedule and then schedule appropriately. Scheduling attributes are supported only for Schedule or Re-schedule modes.

Sets (Ship, Arrival) and Configurations

If the query includes one line in a Set (ship, arrival) SMC PTO Model, or ATO Model, then all the lines in the Set or SMC PTO Model or ATO Model will be scheduled. The exception is when the Schedule Mode is Schedule without any scheduling attributes. In this case the top model with included item/Optional item/Optional class are scheduled. If the query includes a line with PTO Model, Kit, or a PTO Class, then the included items will also be scheduled with the parent. The Unschedule action is not supported for lines belonging to Sets (Ship, Arrival).

Other Scheduling User Procedures

Scheduling Orders that were never scheduled

  1. Set the profile option OM: Auto Schedule to No. The lines will not schedule at the time of entry.

  2. Enter a sales order header and lines, and then save the order making sure it was not scheduled.

  3. Schedule Order concurrent program – Enter the search parameters. Enter the value Schedule in the parameter Scheduling Mode. Optionally enter a scheduling attribute and submit the request:

  4. Verify that the request has completed, then view the order in the Sales Orders window, checking any scheduling attributes you have made. To schedule lines that have failed workflow scheduling, and only those lines, choose the value Lines at Eligible Activity, in the Scheduling Mode parameter.

Scheduling Booked orders

  1. Set the profile option OM: Auto Schedule to No. The lines will not schedule at the time of entry.

  2. Create two sales orders, headers and lines, and book only one.

  3. Schedule Order concurrent program – Enter the search parameters. Enter the value Yes in the parameter New Query, and submit the request.

  4. Verify that the request has completed, and then view the orders in the Sales Orders window, checking to see if only the booked order was scheduled.

Re-Schedule Lines that have been scheduled

  1. Enter a sales order header and lines, schedule the lines, and then save the order.

  2. Schedule Order concurrent program – Enter the search parameters. Enter the value Re-Schedule in the parameter Scheduling Mode. You need to enter either or both scheduling attribute(s) and submit the request:

  3. Verify that the request has completed, and then view the orders in the Sales Orders window, checking to see if the values entered are there.

    Some factors to consider: If the re-scheduling action is not successful, the line is unchanged, which implies that the line will still be scheduled. You have to determine the number of failed lines from the concurrent request log or the Process Messages window. It is advisable to follow a two-step re-scheduling process, which is to unschedule first and then schedule appropriately. Please note that Scheduling attributes will be supported only for Schedule or Re-schedule modes.

Un-Schedule the Lines that have been scheduled

  1. Enter a sales order header and lines, schedule the lines, and then save the order.

  2. Schedule Order concurrent program – Enter the search parameters. Enter the value Unschedule in the parameter Scheduling Mode. Submit the request.

  3. Verify that the request has completed, and then view the orders in the Sales Orders window, checking to see if the lines are unscheduled with the Scheduled Ship Date blank.

    Results and Exceptions

    Scheduling failures are written to the concurrent request log file. In addition, error messages will also be stored in the process messages table with the Concurrent Request ID, Order and Line Details. Process Messages Form can be used to query the messages for the Request Run or a particular order.

    Summary processing statistics like the number of processed lines and number of failed lines will be printed at the end of the concurrent request log file.

    If the number of Sales order lines scheduled in the batch are small, then Schedule Across Orders module can be used to query back the results by using the appropriate fields in the find window.

Workflow - Manual Scheduling Sub-Process

A scheduling sub-process named Schedule-Line, Manual handles situations where you want to control scheduling manually after the order is booked. If the new sub-process is used in the line workflow, then after booking the order, the lines will be blocked at the Schedule-Eligible activity. You can progress the Schedule-Eligible activity from Sales Orders window or use the Schedule Orders program to schedule the lines.

the picture is described in the document text

Release Expired Holds Concurrent Program

Order Management provides the ability to release all expired holds by effectivity date.

There are no enterable input parameters for this program: When the concurrent program is called, all expired holds with an ending Effectivity Date less than or equal to the system date will automatically be released.

To release Expired Holds:

  1. Navigate to the Run Requests SRS window, and select Release Expired Holds in the Request Name field.

  2. Select OK, then Submit.

the picture is described in the document text

Defaulting Generator Concurrent Program

The Defaulting Generator concurrent program enables you to quickly update existing defaulting packages for defaulting rules and conditions. From the Order Management Standard Request Submission window, you can choose to submit the program for

You may execute the Defaulting Generator concurrent program while users are still on the system, although the defaulting package may not generate successfully. This can be due to the package currently being called by other users who are processing orders on the system. Common errors within the output log file for this concurrent program may contain text that a time-out occurred while waiting to lock object.

Note: If you are running Defaulting Generators for an Entity and do not specify an Attribute, it is recommended that users log off the system to decrease the concurrent processing run time.

Note: If defaulting packages do not generate successfully, you must choose to run the concurrent program at a later time, or have users briefly log off the system while defaulting packages are being regenerated in order for your modifications to take effect.

To submit the Defaulting Generator concurrent program from within the Defaulting Rules window:

  1. Within the Defaulting Rules main window, from the Tools menu, select Defaulting Generator.

    You can only submit the concurrent program from the Defaulting Rules main window. If you choose to submit the concurrent program from the Defaulting Rules window, input parameters are based upon the current cursor location. The Defaulting Generator is run for whatever attribute is highlighted.

    For example, if the field Application has a value of Oracle Order Management, the field Entity has a value of Order Header, and the cursor was positioned on the row displaying the attribute Agreement, the concurrent program will be executed with the above values as input parameters.

    Note: From within the Defaulting Rules window, the Defaulting Generator concurrent program is always submitted with a value for the input parameter Attribute, which is based upon the cursor location when the concurrent program is invoked.

    To submit the Defaulting Generator concurrent program from the Order Management SRS window:

    Navigate to the Run Requests SRS window, and select Defaulting Generator in the Request Name field.

    Run Requests SRS Window

    the picture is described in the document text

  2. Select a value for the Application. This field is required.

  3. Select a value for the Entity. This field is required.

    Running this program with only a value for the input parameter 'Entity' will result in re-generating defaulting packages for every defaultable attribute for the entity value selected.

  4. Select a value for the Attribute. This field is optional.

    Running this program with a value for the input parameter 'Attribute' results in re-generating the defaulting logic for the attribute value selected only. All other attribute rules and conditions of the entity will not be re-generated.

  5. Select OK, then Submit.

Inventory Interface No Ship Concurrent Program

The Inventory Interface concurrent program processes interfacing orders or lines to inventory if:

In order for the Inventory Interface concurrent program to properly function, you must customize order or line workflow processing flows to include the Inventory Interface - Eligible block activity before the Inventory Interface sub process.

The Inventory Interface concurrent program creates a standard Oracle log file containing processing results for the programs execution.

the picture is described in the document text

To process Inventory Interface transactions via concurrent program:

  1. Navigate to the Run Requests SRS window, and select Inventory Interface in the Request Name field.

    Run Requests SRS Window

    the picture is described in the document text

  2. In the parameters window, select a value for the following parameters, based upon your processing needs:

  3. Select OK, then Submit.

Credit Check Processor Concurrent Program

The Credit Check Processor program can be run on demand to re evaluate Booked orders that have not been shipped yet.

Use the Credit Check Processor when you suspect that your customers credit exposure has changed and you want to re evaluate their sales order status (releasing or applying credit check holds accordingly).

Also use Credit check Processor whenever you change your customer or default credit set up and you want this changes to immediately take affect in your booked sales orders.

The program only can be used if you run credit checking at Book, only for booked orders (all orders are booked).

To re evaluate booked orders not yet shipped via concurrent program:

  1. Navigate to the Run Requests window, and select Credit Check Processor in the Name field.

    the picture is described in the document text

  2. Determine which customer credit profile classes to include when updating your credit balances. Select either a value for Customer Profile Class From, Customer Profile Class To, or by selecting a value for both fields.

  3. Determine which customers to include when updating your credit balances. Select either a value for Customer Names From, Customer Names To, select a value for both fields, or choose to include or exclude customer names within the range selected for Customer Names From/To by selecting additional limiting values for the input parameters Customer Numbers From/To.

  4. Determine which customers to include when updating your credit balances. Select either a value for Customer Numbers From, Customer Numbers To, select a value for both fields, or choose to include or exclude customer numbers within the range selected for Customer Numbers From/To by selecting additional limiting values for the input parameters Customer Names From/To.

  5. Determine the order dates to include when updating your credit balances. Select a value for Order Date From, an optional value for Order Date to, or by selecting a value for both fields. Order Date From is required.

  6. Determine the processing order when updating credit balances. Select a value for the Order sequence field. This field is required. Possible values are:

  7. Select OK, then Submit.

Initialize Credit Summaries Table Concurrent Program

Order Management enables you to periodically rebuild a credit exposure image (orders, invoices and payments) for all customers or customer sites for all possible credit rule definitions. When you submit the, The Initialize Credit Summaries Table concurrent program, changes to customer or customer site credit exposure are calculated and updated, based upon your exposure setup for each credit check rule defined. Exposure information is stored in a summary table so that the credit check process can refer to summary credit data as opposed to real time transactional data, reducing the effort needed to evaluate credit standing.

Additionally, if you wish to import exposure details from an external system, you can use the Credit Exposure Import concurrent program. See: Credit Exposure Import Concurrent Program.

To initialize or update credit exposure via concurrent program:

  1. Navigate to the Run Requests SRS window, and select Initialize Credit Summary Table in the Request Name field.

    Run Requests SRS Window - Initialize Credit Summary Table

    the picture is described in the document text

  2. Determine whether or not you wish to lock database tables when submitting this program. Select from:

  3. Select OK, then Submit.

Credit Exposure Import Concurrent Program

The Credit Exposure Import concurrent program enables you to import external credit exposure details (such as transaction amounts for sales orders created outside of Oracle Applications) into Oracle Order Management, provided you have correctly populated the corresponding Order Management Exposure Interface table.

External exposure details can then be:

Order Management will determine whether to include external exposure amounts imported within the overall exposure amount when performing credit checking based upon the credit checking rules you define.

Program Details

External exposure details imported within Order Management are stored in the same exposure summary table used by the Initialize Credit Summaries Table concurrent program. Successfully imported external exposure records within the summary exposure table can be determined by the value for the field BALANCE_TYPE; all externally imported exposure detail records will have the value 18 for the field BALANCE_TYPE.

Note: when you submit the Initialize Credit Exposure concurrent program, externally imported exposure records are never overwritten.

When importing credit exposure details from an external system, Order Management will import all records selected, provided each record successfully passes validation. If a single record fails validation, Order Management will not import any records within the exposure interface tables which were selected for processing. If you encounter exceptions during run time, review the exception details within the concurrent program output and log files, correct the issues, and then resubmit the program.

The Credit Exposure Import concurrent program can be submitted in two different modes, Update and Insert. Interface records are processed based upon the mode, which is determined by the value of the column OPERATION_CODE within the exposure interface table.

This program will never delete records from the credit exposure summary table.

Note: The current value of the profile option MO: Operating Unit is used as a input parameter to this concurrent program. This parameter is hidden by default, and is used to prevent the Credit Exposure Import program from importing exposure records into incorrect operating units.

Note: If you need to input exposure details for multiple operating units, Order Management recommends you set this profile option at the Responsibility level, and then switch to the corresponding Responsibility when importing exposure details.

To import credit exposure details from an external system:

  1. Navigate to the Run Requests SRS window, and select Credit Exposure Import in the Request Name field.

    Run Requests SRS Window - Credit Exposure Import

    the picture is described in the document text

  2. Select the Exposure Source. Exposure Sources are based upon user defined values for the Order Management Quick Code ONT: Credit Exposure Import Source. If you select a value for this parameter, only records which have the same value (case sensitive) within column EXPOSURE_SOURCE_CODE within the exposure import interfaces tables will be processed. This field is not required.

  3. Enter a numeric value, greater than zero, if you wish to specify a batch number to process a portion of the records with the exposure import interface tables.

    You can use a batch number for auditing purposes, or to improve performance when large amounts of exposure records are to be imported (choose to process only a portion of the exposure records within one submission and the remaining records within additional submissions - running the concurrent program in parallel with the initial request).

  4. If you select a value for this parameter, only records which have the same value within column BATCH_ID within the exposure import interfaces tables will be processed. This field is not required.

  5. Validate Only:

    Select Yes to validate records within the credit exposure interface tables only. No records are imported into summary exposure tables during submission.

  6. Select No to validate and process records within the credit exposure interface tables.

    This field is required.

  7. Select OK, then Submit.

    Note: When importing exposure details using the Credit Exposure Import, only interface records that belong to a Bill To Site for the current operating unit can be imported. Therefore, ensure your records are grouped accordingly.

    Note: For example, if you have multiple Bill To sites within the exposure interface table, ensure that each Bill To Sites has been previously defined for the current operating unit you are currently working within.

    Note: Additionally, if you specify either an Exposure Source or a Batch Id as an input parameter, ensure the corresponding records (marked with values for either Exposure Source or Batch ID) within the interface table utilize Bill To Sites defined for the same operating unit you are submitting the program for.

Output

The Credit Exposure Import concurrent program produces a standard Oracle log file, along with a Standard Order Management Report output.

Concurrent Program Log File

Concurrent Program Output (report)

Purge Imported Credit Exposure Concurrent Program

The Purge Imported Credit Exposure concurrent program enables you to purge imported external credit exposure records by operating unit and exposure source. If you have imported external credit exposure records for multiple operating units, in order to purge all external credit exposure records you will need to submit the concurrent program for each operating unit you have imported external credit exposure records for.

To purge credit exposure details which were imported from an external system:

  1. Navigate to the Run Requests SRS window, and select Purge Imported Credit Exposure in the Request Name field.

    Run Requests SRS Window - Purge Imported Credit Exposure

    the picture is described in the document text

  2. Select the Exposure Source, Exposure Sources are based upon user defined values for the Order Management Quick Code ONT: Credit Exposure Import Source. Prior to selecting a value for this parameter, ensure that external credit exposure records have previously been imported successfully. Otherwise, the program will fail.

  3. Select ok, then Submit.

    Note: The current value of the profile option MO: Operating Unit is used as a input parameter to this concurrent program. This parameter is hidden by default, and is used to prevent the Credit Exposure Import program from importing exposure records into other operating units.

    If you need to purge exposure details for multiple operating units, Order Management recommends you set this profile option by responsibility, and then switch to the corresponding responsibility when purging exposure details.

Process Pending Payments Concurrent Program

The Process Pending Payments concurrent program enables you to submit credit card orders for payment processing and to additionally process orders on hold (for select hold types only). Orders using both a Payment Term that enables prepayments and a Payment Type of Credit Card, and orders with the following hold type are processed by this concurrent program:

When you submit this concurrent program, orders with the above hold types are first released (provided the validation of removing the hold is successful); the order and order lines are then able to continue within their respective workflows.

This concurrent program produces an output log file and output listing with any error messages generated during processing. The following additional details can be located in the both the log file and concurrent program outputs:

Additionally, you can use the Process Messages window to view concurrent program runtime details such as warning or error messages generated.

To process pending payments via concurrent program:

  1. Navigate to the Run Requests window, and select Process Pending Payments in the Name field.

    the picture is described in the document text

    All input parameters to this concurrent program are optional.

  2. Pending Payment Process Hold: Select Yes to process orders currently on Pending Payment Process Hold, or select No to not process orders on Pending Payment Process Hold. The default value for this parameter is Yes.

  3. ePayment Failure Hold: Select Yes to process orders currently on ePayment Failure Hold, or select No to not process orders on ePayment Failure Hold. The default value for this parameter is Yes.

  4. ePayment Server Failure Hold: Select Yes to process orders currently on ePayment Server Failure Hold, or select No to not process orders on ePayment Server Failure Hold. The default value for this parameter is Yes.

  5. Payment Authorization Hold: Select Yes to process orders on Payment Authorization hold. Select No to bypass these orders. This hold is used if you set up payment authorization to be a deferred process. Then this request will attempt to process those authorizations in a batch mode.

  6. Order Type: Select a specific order type to limit credit card payment processing of orders.

  7. Order Number (Low/High): Enter a value for Order Number Low, Order Number High, or both to limit credit card payment processing to specific order numbers. If you wish to process a single order, enter the same value in both fields.

  8. Customer Number (Low/High): Enter a value for Customer Number Low, Customer Number High, or both to limit credit card payment processing to orders for specific Customer numbers. If you wish to process credit card orders for a single customer, enter the same value in both fields.

  9. Customer Class: Select a specific customer class to process credit card payments.

  10. Credit Card Number: Enter a specific credit card number to process orders for credit card payment. Only orders with the specific card number entered will be processed.

  11. Credit Card Type: Select a credit card type to process orders for credit card payment. Only orders with the specific credit card type will be processed.

  12. Bill to Org: Select a specific Bill To to process credit card payments.

  13. Booked Date Since: Enter a specific date to process all orders which have a creation date greater than or equal to the date entered for processing credit card payments.

  14. Select OK, then Submit.

Message Purge Concurrent Program

The Message Purge concurrent program purges Order Management messages that are generated during order processing. To keep the Oracle Order Management Message tables at manageable sizes, you should submit the Message Purge concurrent program at periodic intervals. After the concurrent program has successfully completed, you can use the Process Messages window and to verify that the Order Management message tables have been purged as specified by the input selection criteria.

If you leave any of input parameters blank, the concurrent program will process all possible values for the parameter.

To purge Order Management messages via concurrent program:

  1. Navigate to the Message Purge menu entry.

    Message Purge Window

    the picture is described in the document text

  2. Determine the number of messages you wish to purge per database commit by entering a value for the Messages per Commit input parameter.

    If you enter a value of 100, 100 messages will be purged (based upon all input parameters) prior to the database actually performing the commit. Once a commit has successfully completed, you are unable to rollback changes that occurred prior to the commit. In the event of a system failure, a rollback will be performed, rolling back any changes that took place immediately after the last successful commit. The default for this field is 500, and the field is optional.

  3. Determine if you wish to purge messages created on a specific date or range of dates by selecting a value for the Creation Date Low, the Creation Date High, or both input parameters. All messages created for the date range specified are purged, provided other input parameters also enable purging. These fields are optional.

  4. Determine a Message Source to purge Order Management messages. All messages created with the source specified by the input parameter Message Source will be purged, provided other input parameters also enable purging. Select from:

    C: Concurrent Program

    U: On Line (U/I)

    W: Workflow

    This field is optional.

  5. Determine if you wish to purge messages generated for a specific Customer Name by selecting a Customer Name in the Customer Name input parameter, provided other input parameters also enable purging. This field is optional.

  6. Determine if you wish to purge messages for a specific Customer Number by selecting a Customer Number in the Customer Number input parameter, provided other input parameters also enable purging. This field is optional.

  7. Determine if you wish to purge messages for a specific Order Type by selecting a value in the Order Type input parameter. All messages generated for the Order Type selected will be purged, provided other input parameters also enable purging. This field is optional.

  8. Determine if you wish to purge messages for a single order number or range of order numbers, by entering values for Order Number Low, Order Number High, or both input parameters. All messages created for order numbers entered will be purged, provided other input parameters also enable purging.

    These fields are optional.

  9. Select OK, then Submit.

Calculate Party Totals Concurrent Program

The Calculate Party Totals concurrent program calculates the total number of orders and the summary order amount of all orders, and determine the last date an order was placed, by customer Party number.

The following order attributes determine eligibility for inclusion within the concurrent program calculations during program execution:

The concurrent program does not produce a report output. However, within the standard submission request log file, Party Total amount is listed by Party number, and whether or not the Party totals were successfully updated. The Calculate Party Totals program results are stored within the following columns within table HZ_PARTIES:

The data stored in the within HZ_PARTIES is intended to be an approximate value indicating the volume of orders and approximate revenue generated by customer Party number. It is not intended to be accurate per accounting standards, and is not maintained real time, unless the request submission parameters are set so the program is continually executed after each successful completion.

Note: The total number of orders and the summary order amount of all orders reflect the number of orders that are currently active within Order Management tables.

Note: If you have submitted the Order Purge concurrent program and successfully purged orders, when you submit the Calculate Party Totals concurrent program, only the orders remaining within Order Management tables are used during concurrent program calculations.

Submission

Navigate to the Order Management Standard Request submission window, select Calculate Party Totals, and select Submit. There are no parameters to enter for the concurrent program.

Audit History Consolidator Concurrent Program

The Audit History Consolidator concurrent program, when submitted populates an Order Management table with consolidated audit trail details recorded for orders and lines. Each subsequent submission of the program updates any additional order audit trail details that have been captured since the previous successful submission of the program. For details on capturing order audit trail details, see Order Audit Trail.

Order Management consolidates the following four order entities within the table:

The data within the table is can be viewed within Oracle Applications via the View Audit History window or printed for display via the Order Management Audit History Report.

To consolidate order audit trail history via concurrent program:

  1. Navigate to the Run Requests window, and select Audit History Consolidator in the Name field.

    the picture is described in the document text

  2. Enter the History Date From. This field is optional.

  3. Enter the History Date To.This field is optional.

  4. Enter the Order Number From. This field is optional.

  5. Enter the Order Number To. This field is optional.

    Note: Note: If the order number is more than 10 characters then the order number in the audit history report is displayed as @ *********.

  6. Enter a numeric value in the Changes in Last N days field to capture audit history changes captured over a period of days. For example, if you wish to consolidate order changes captured for audit purposes during the last 7 days, enter the value 7.

  7. Select OK, then Submit.

    Note: Order Management recommends your schedule this report based upon your business needs.

Re-Schedule Ship Sets Concurrent Program

The Re-Schedule Ship Sets concurrent program is utilized to re-schedule Ship Sets to the earliest finite supply date, for all order lines within the set. The time fenced used in the calculation is the time fence defined for the ATP rule linked to the order line item.

Note: If order lines are scheduled based on the Infinite Supply Time Fence you can submit this program to reschedule order lines to secure a more practical (and the best) Earliest Available Date. This program will process order lines only if the lines are part of the set.

To re-schedule Ship sets via concurrent program:

  1. Navigate to the Order Management Standard Request Submission window, and select Re-Schedule Ship Sets.

    Order Management Standard Request Submission Window

    the picture is described in the document text

  2. Determine the orders you wish to attempt Ship Set rescheduling for. Select a value for the Sales Order Number (low), Sales Order Number (high), or a combination of sales order numbers. These fields are optional.

  3. Determine the date or dates you wish to include re-scheduling of Ship Sets from or to. Enter a value for the Relative Start Date (in days), Relative /End Date (in days), or a combination of Relative Start/End Dates (in days). These fields are required.

  4. Re-schedule a Ship Set by Set Name. Select a value in the Ship Set Name field. This field is optional.

  5. Select OK, then Submit.

Reserve Orders Concurrent Program

The Reserve Orders concurrent program attempts to reserve items as specified by input parameters. The concurrent program attempts to reserve any order lines (for order line types that support Reservations) that are scheduled, and have quantity for complete fulfillment. Reserve Orders supported two modes for scarce inventory (Fair Share and Percentage). It supports a third mode, Partial. Using Reserve Orders, you can choose whether to reserve or simulate reservations.

Note: For input parameters where you can specify a range (Low and High values):

Note: When the parameter Reservation Run Type is Create Reservation for Set, only the Set Name parameter will be honored and all other parameters will be ignored. The concurrent program will attempt to process the data within the specified Set.

To Reserve Orders via concurrent program:

In this release Reserve Orders Concurrent Program can be run across operating units.

  1. Navigate to the Order Management Requests window, and select Reserve Orders.

    the picture is described in the document text

  2. Operating Unit: This parameter can be defaulted or specified at run time. If this program is run for a specific Operating Unit then list of values for operating unit dependent parameters will be validated against the Operating Unit entered. Else those parameters will show appropriate values for all Operating Units the user has access to.

  3. Use Reservation Time Fence: Select from

  4. Order Number (High): Select an order number to reserve order lines for. If you do not specify an order number, the system will attempt to reserve all order lines during concurrent program execution.

  5. Reserve orders for a specific customer by selecting a value for Customer. All order lines for a customer that are not currently reserved will be processed for reservations during the execution of this concurrent program.

  6. Reserve orders for a specific Order Type by selecting a value for Order Type.

  7. Reserve order lines for a specific Line Type by selecting a value for Line Type.

  8. Reserve orders by warehouse (organization) by selecting a value for Warehouse.

  9. Reserve order lines by item by selecting a value for Item.

  10. Reserve orders by Line Requested Date by entering a value for Line Request Date Low, Line Request Date High, or a range of line requested dates by entering a value for Line Request Date (Low/High).

  11. Reserve orders by Scheduled Ship Date by entering a value for Scheduled Ship Date Low, Scheduled Ship Date High, or a range of Scheduled Ship Dates by entering a value for Scheduled Ship Date (Low/High).

  12. Reserve orders by Scheduled Arrival Date by entering a value for Scheduled Arrival Date Low, Scheduled Arrival Date High, or a range of Scheduled Arrival Dates by entering a value for Scheduled Arrival Date (Low/High).

  13. Reserve orders by Ordered Date by entering a value for Ordered Date Low, Ordered Date High, or a range of ordered dates by entering a value for Ordered Date (Low/High).

  14. Reserve orders by Demand Class. Enter a Demand Class previously defined within the system.

  15. Reserve orders by Planning Priority. Enter the Planning priority previously defined within the system

  16. Determine the processing order that the concurrent program will utilize during execution within the Order By field. Existing supply will be reserved on the basis of you choice. If you choose a value that utilizes a date, the earliest date available will be the first order processed for reservations, based upon you other input parameters selected.

    For example, if you select Date Ordered, then the order with the earliest Order Date (based upon all other input parameter values) will be processed initially. Select from:

  17. Select OK, then Submit.

    The log file generated as a result of a submission of the Reserve Orders concurrent program displays all internal order line ids' selected for processing based upon the input parameters entered.

Export Compliance Screening Concurrent Program

The Export Compliance Screening concurrent program can be used to progress order lines that are currently waiting at the Export Compliance Screening Eligible workflow activity. If an order line has initially failed export compliance screening due to data errors, you can attempt to correct the order data, and submit the Export Compliance Screening concurrent program to progress orders and lines past the Export Compliance Screening Eligible workflow activity; export compliance routines are called to perform the compliance screening again.

To progress waiting at the Export Compliance Screening Eligible activity:

  1. Navigate to the Order Management Standard Request Submission window, and select Export Compliance Screening.

    the picture is described in the document text

  2. Progress export compliance order lines by Order Number. Enter a value for in the Order Number Low, Order Number High, or range of order numbers to include by entering a value for both fields. Additionally, leave these fields blank to progress all order lines.

  3. Progress export compliance order lines by Customer. Enter a value in the Customer field.

  4. Progress export compliance order lines by Customer PO. Enter a value in the Customer PO number that corresponds with the purchase order received from your customer.

  5. Progress export compliance order lines by Order Type. Select a value for the Order Type field.

  6. Progress export compliance order lines by Warehouse (organization). Select a value for the Warehouse field.

  7. Progress export compliance order lines by Line Ship To Location. Select a value for the Line Ship To location.

  8. Progress export compliance order lines by Item. Select or enter an value in the Item field.

  9. Progress export compliance order lines by Line Scheduled Date. Select a value for Line Schedule Date Low, an optional value for Line Schedule Date High, or by selecting a value for both fields.

  10. Progress export compliance order lines by Order Date. Select a value for Order Date From, an optional value for Order Date To, or by selecting a value for both fields. This field is required.

  11. Select OK, then Submit.

Export Compliance Workbench

Diagnostics: Apps Check Concurrent Program

This program provides summary output details for Oracle Application schema's. Details such as product installation status, application profile values, invalid objects, package versions, database triggers, and form versions are displayed within the program output based upon the Oracle Applications you select as an input.

You can choose to display an output for a single Oracle Application, up to five Oracle Applications, or all Oracle Applications. Order Management recommends that you submit the program with at least one Application Name for the input parameters defined; each subsequent Application Name selected increases the program run time.

The following lists the entities, along with the current value, for each Oracle Application selected by the input parameters that will be displayed within the program logfile.

To review Oracle Application details:

  1. Navigate to the Order Management Standard Request Submission window, and select OM Diagnostics: OM Check.

    Apps Check Input Parameters Window

    the picture is described in the document text

  2. Enter or select a value for the optional input parameters Application1 through Application5.

    Oracle Order Management, Oracle Pricing, and Oracle Shipping are automatically defaulted for input parameters Application1through Application 3, respectively; these values may be changed. If you clear the Application1 through Application3 input parameter defaults, the program output will display data for all Oracle Applications.

  3. Select OK, then Submit.

Diagnostics: OM Debug File Retrieval Concurrent Program

This concurrent program will retrieve Order Management Debug files generated by a user for review on-line. The value of the profile option OM: Debug Log File Directory determines the location the concurrent program will search for the log file specified in the input parameter to this program.

You can also submit this concurrent program to validate your setup for generating Order Management Debug files. Results are displayed within the program output and will include possible suggestions on how your Debug setup can be fixed.

To retrieve an Order Management Debug file for viewing on-line:

  1. Navigate to the Order Management Standard Request Submission window, and select Diagnostics: OM Debug File Retrieval.

    OM Debug File Retrieval Input Parameters Window

    the picture is described in the document text

  2. Enter the Order Management Debug file name to retrieve (debug file which was displayed to a user when Debug was turned on). This field is optional.

    If you leave this parameter blank, the program will attempt to validate your Debug setup and provide results based upon the validations performed.

  3. Select OK, then Submit.

  4. Navigate to the View Requests window.

    Enter the appropriate criteria in the Find Requests window, select Find, locate your request with your cursor within the Request window, and then select View Output.

Diagnostics: OM Order Information Concurrent Program

This program selects order related data from various Oracle Application product database tables and provides a detailed output for the order selected. Additionally, you can choose to limit order details to a specific order line by specifying the line number prior to submission.

The following lists the entities or attributes and their associated current value which will be displayed within the program output for the order or order line selected by the program:

Entities or Attributes and their Associated Current Values
- - -
Order/Line Details Order/Line Workflow Status Order/Line Workflow Notifications
Order/Line Workflow Errors Line History Holds
Price Adjustments Drop Ship Sources PO Requisition Interface Details
PO Requisition Details Requisition Workflow Approval Status Requisition Workflow Approval Notifications
Requisition Workflow Approval Errors Receiving Shipment Lines Receiving Transactions
Receiving Transactions Interface Material Supply Item Reservations
WIP Job Schedule Interface WIP Discrete Jobs WIP Discrete Job Transactions
WSH Trips WSH Trip Stops WSH Delivery Legs
WSH New Deliveries WSH Delivery Assignments WSH Delivery Details
WSH Freight Costs Material Transactions Interface Material Transactions Temp
Material Transactions Move Transactions Receivable Interface Details
Receivable Interface Errors Invoice Details Order Cancellation Report

To display detailed order or order and order line information:

  1. Navigate to the Order Management Standard Request Submission window, and select OM Order Information.

    OM Order Information Input Parameters Window

    the picture is described in the document text

  2. Enter the order number you wish to view details for. This field is required.

  3. Optionally, choose to limit the program output to display line number details for a specific order by entering a line number.

  4. Select OK, then Submit.

Order Import Statistics Concurrent Program

Order Import uses the Cost Based Optimizer of the database for optimizing queries. The Cost Based Optimizer uses generated statistical information to optimize queries. The Order Import Statistics concurrent program gathers statistics that will be used by the cost based optimizer. This concurrent program should be run after data is populated into the interface tables.

The Cost Based Optimizer performs a table analysis of all interface tables related to Order Import for determining optimum record processing. You can choose to submit this program (or not) prior to each submission of the Order Import concurrent program. If you normally process a similar number of interface records, you typically do not need to submit this program. There are no parameters for the submission of the Order Import Statistics concurrent program.

To schedule orders via concurrent program:

  1. Navigate to the Run Requests SRS window, and select Order Import Statistics in the Request Name field.

  2. Click Submit.

Below is a list of columns that are present in the interface tables, but not available via the Corrections Window:

Purge Set/ Order/Quote Purge Selection Concurrent Programs

The Purge concurrent program enables you to purge selected closed orders/quotes and their workflow history. You first determine which documents you wish to purge by creating a Purge Set. Once orders/quotes have been selected for purging within a purge set, you can then choose to purge the entire set, a subset of the Purge set, or to cancel the purge. Purging old data creates space in your database and can improve performance of transactions and maintenance.

Purge Set Creation

A purge set is a set which will contain orders to be purged based upon user specified criteria. Purge set can be created in the two following ways:

Flexible Order/Quote Purge Selection Criteria

You can purge, using selection criteria, from the eligible pool of headers and lines. Once all processing steps for this transaction have been completed, you can view them and choose to purge all orders from the eligible pool which are for a particular customer.

The criteria for Order Purge selection will be based on:

The criteria for Quote Purge selection will be based on:

Review Data to be Purged

You can view all closed orders/lines that meets purge criteria. You can preview preliminary purge candidate listings on the Purge Set window.

Cancel the Purge or Change the Batch Run Time

Order/quote purge is submitted in batch mode, and you can cancel the batch job or change the batch runtime.

View Purged Data

After a purge is complete you can only view the purged data in the Purge Set window. Navigate to the Order/Quote Purge Set window and query by Purge Set name. Purge sets can be submitted for purge, exclude certain orders/quotes within the set from being purged, or completely deleted (provided the records have been previously purged).

Purge Option for Sales Orders with Terms and Conditions

When purging sales orders, you can select the Purge Orders with Contract Terms parameter that specifies whether orders with contractual terms and conditions are eligible for purging. If you select No for this parameter, then the order will not be eligible for purging if it has terms and conditions.

OM: Transactions Purged Per Commit

This profile option can be set only at the site level. The value of this profile option indicates the number of orders/quotes per commit, in order/quote purge processing.

Purge Set Creation using the Purge Set Selection Concurrent Program

To create a purge set by specifying the where (selection) condition

  1. Navigate to the Order Purge Selection concurrent Program

    Order Purge Selection Parameters Window

    the picture is described in the document text

  2. Within the Purge Set name field, enter a unique name to identify the purge set.

  3. Within the Purge Set Description, enter a description for your purge set.

  4. Optionally, determine if you wish to purge a single order number or range of order numbers, by entering values for Order Number Low, Order Number High, or both input parameters. All orders created within the range entered will be selected for purging, provided other input parameters also enable purging.

  5. Optionally, determine if you wish to purge orders for a specific Order Type by selecting a value in the Order Type input parameter. All orders created that utilize the Order Type selected will be purged, provided other input parameters also enable purging.

  6. Optionally, determine if you wish to purge orders for a specific Order category by selecting a value in the Order Category input parameter. All orders created that utilize the Order Category selected will be purged, provided other input parameters also enable purging.

  7. Optionally, determine if you wish to purge orders for a specific Customer Name by selecting a Customer Name in the Customer Name input parameter, provided other input parameters also enable purging.

  8. Optionally, determine if you wish to purge orders created on a specific date or range of dates by selecting a value for the Creation Date Low, the Creation Date High, or both input parameters. All orders created for the date range specified are selected within the purge set, irrespective of the current order status.

  9. Click Submit.

To create a purge set using Quote Purge selection

  1. Navigate to the Quote Purge Selection concurrent Program.

    Quote Purge Selection - Parameters

    the picture is described in the document text

  2. Within the Purge Set name field, enter a unique name to identify the purge set.

  3. Within the Purge Set Description, enter a description for your purge set.

  4. Optionally, determine if you wish to purge a single quote number or range of quote numbers, by entering values for Quote Number From, Quote Number To, or both input parameters. All quotes created within the range entered will be selected for purging, provided other input parameters also enable purging.

  5. Optionally, determine if you wish to purge quotes for a specific Order Type by selecting a value in the Order Type input parameter. All quotes created that utilize the Order Type selected will be purged, provided other input parameters also enable purging.

  6. Optionally, determine if you wish to purge quotes for a specific Customer Name by selecting a Customer Name in the Customer Name input parameter, provided other input parameters also enable purging.

  7. Optionally, determine if you wish to purge quotes created on a specific date or range of dates by selecting a value for the Creation Date From, the Creation Date To, or both input parameters. All orders created for the date range specified are selected within the purge set, irrespective of the current order status.

  8. Click Submit.

    Purge Set Creation by multi-selection

    Create a purge set by selecting multi-selecting orders within the Order Organizer, and then, from the menu, selecting Tools, Purge, Purge Set.

    Enter the Purge Set name and a description for the purge set.

  9. Click Submit to create a purge set with all the records (orders) you have selected within the Order Organizer.

Process Exceptions

If the selection criteria includes orders/quotes that do not meet the purge restrictions (order is not closed, outstanding reservations exist, etc.) or if the purge process encounters an issue, a process error occurs. These errors can be viewed by viewing the purge set within the Purge Set window.

For example, suppose when submitting the Order Purge Selection concurrent program a user specified all orders for customer Business World. When you navigate to the Order Purge window, you may find certain orders were ineligible for purge, and have been marked as such (within error column, a note would display the order is not closed, and the Eligible check box is not enabled).

To review purge set details:

Purging within Operating Units

You can process only those purge sets that you have created, though you can view all the purge sets created. If a purge set you process has orders in an Operating Unit that you no longer have access to, the Order Purge program will not purge those orders and an error message will be displayed.

  1. Navigate to the Purge Set window.

    Purge Set Window - Purge Criteria Tab

    the picture is described in the document text

    The Purge Set window displays the following attributes of a Purge Set:

    Purge Criteria Tab

  2. Choose to:

    To purge orders or quotes using a purge set in the Order Organizer:

    Navigate to the Order Organizer window and query your closed orders or closed quotes to purge.

  3. Choose Tools > Create Purge Set. The Order Organizer, Create Purge Set window appears.

  4. Choose Submit to create the purge set.

    Note: This method of creating a purge set is recommended only for a low volume of orders. For high a volume of purge data (e.g greater than 100 orders) the order/quote purge selection (using the concurrent program) is recommended.

    To create an order purge set by specifying a where condition:

    To create a purge set by specifying a where (selection) condition, select the Purge > Order Purge Selection from the navigator.

    1. Enter the Purge Set Name, Description, and the desired selection criteria and click OK.

    2. Click Submit on the subsequent request screen.

      To create a purge set repeat steps 1-3 and replace the order purge selection with the quote purge selection in step1.

View Order Purge

After creating the purge set using either of the above methods, the orders or quotes in that purge set can be viewed on the Purge Set window. The purge set now can be either submitted for purge, or if required some of the orders or quotes can be excluded from the purge set using this window, or the purge set can be deleted. To review the purge set open the following window from Navigator Purge > Purge Set. This window is also available from Purge option of Tools menu of Order Organizer. On this window purge sets can be queried by purge set name. If the purge set has been created using a selection criteria the purge criteria can also be viewed.

Messages

Message Name: OE_PUR_ADD_ORDER

Message Text: This Order is ineligible for purging.

Description: This message is issued when the user tries to include an order into purge set.

Message Name: OE_PUR_DELETE_PURGE_SET

Message Text: You cannot delete a purge set that has some orders that have already been purged.

Description: This message is issued when user tries to delete a purge set, from which some orders have been purged.

Message Name: OE_PUR_DELETE_PURGE_SET_OK

Message Text: Delete Purge Set &PURGE_SET_NAME

Description: This message is for confirmation of delete.

Message Name: OE_PUR_PURGE_SET_DELETED

Message Text: Purge Set &PURGE_SET_NAME Deleted.

Description: This note is issued after the deletion of a purge set.

Message Name: OE_PUR_PURGE_SET_PURGED

Message Text: You cannot delete a purge set that has already been purged.

Description: This message is issued when a user tries to delete/submit a purge set.

Message Name: OE_PUR_REQUIRED

Message Text: Field must be entered.

Description: Message for a required field.

Message Name: OE_SRS_TITLE_GENERATE_PURGESET

Message Text: Order Purge Selection.

Description: Title for order purge selection.

Message Name: OE_PUR_CREATE_SUBMITTED

Message Text: Create purge set submitted with request id = &REQUEST_ID.

Description: Message issued when create purge set is submitted.

Message Name: OE_PUR_ORDER_PURGE_SUBMITTED

Message Text: Order purge submitted with request id = &REQUEST_ID.

Description: Message issued when order purge is submitted.

Message Name: OE_PUR_OPEN_ORDER

Message Text: Order is open.

Description: Message issued when an order is open.

Message Name: OE_PUR_OPEN_INVOICES

Message Text: Open invoices exist for this order.

Description: Message issued when open invoices exist for an order.

Message Name: OE_PUR_OPEN_RETURNS

Message Text: Open returns exists for this order

Description: Message issued when open returns exists for an order.

Message Name: OE_PUR_CANNOT_SUBMIT

Message Text: Purge set is already purged.

Description: Message issued when a user tries to submit order purge for a purge set which has already been purged.

Messages For Quotes

Message Name: OE_PUR_ADD_QUOTE

Message Text: This quote is ineligible for purging.

Description: This message is issued when a user tries to include a quote into purge set.

Message Name: OE_PUR_OPEN_QUOTE

Message Text: Quote is open.

Description: Message issued when Quote is open.

Message Name: OE_SRS_TITLE_GENERATE_QUOTE_PURGESET

Message Text: Quote Purge Selection

Description: Title for Quote purge selection.

Purchase Order Related Purge Changes

Message Name: OE_PUR_OPEN_PO_REQ

Message Text: Open drop ship PO/Requisition exists for externally sourced line of this order.

Description: This message is issued when there is an open PO or requisition existing for an order that has drop ship order lines.

Batch Price Concurrent Program

The Batch Price concurrent program attempts to price orders or order lines as specified by input parameters. The concurrent program attempts to price any orders or lines that have an open status. Batch Pricing honors the Calculate Price Flag on the individual order lines.

For input parameters where you can specify a range (Low and High values):

To perform batch price via the concurrent program:

Preview Mode: This is a mandatory parameter. If you select Yes, then the concurrent program will not price or re-price the orders or lines, it will only list the order and line details that will be impacted if batch pricing is run with the specified parameters. Preview mode is useful if you want to see the effect of the pricing or re-pricing on the orders and lines for the specified input parameters. You can then decide if you wish to run the concurrent program in execute mode (when Preview Mode is No) or not. If you select No, then the concurrent program runs with the parameters you specify and prices or re-prices the orders and lines. The price is fetched from the price list defaulted on the order / line by the relevant API.

Pricing Level: This is a mandatory parameter. You can select between order level pricing and line level pricing to determine whether line level or list level modifiers get applied. If you select order level pricing, and the order status is Entered, then the Pricing API is called with the Batch event. If at order level pricing, the order status is Booked, then the Pricing API is called with the Batch, Book and Ship events. If you select line level pricing, the Pricing API is called with the Line event only, irrespective of the line status (booked or otherwise).

Operating Unit: The Batch Price concurrent program can be run across operating units. You can specify All or a given operating unit for the orders/lines that you want priced or re-priced.

Order Number (Low/High): Select an order number to price or reprice order lines for. If you do not specify an order number, the system will attempt to reprice all order lines during concurrent program execution.

Order Type: Select an Order Type that you want to specify.

Line Type: Select a Line Type. This parameter is disabled if you have selected Order Level pricing at the Pricing Level parameter.

Booked Orders: If you select Yes, then only booked orders will be priced/re-priced. If you select No, then orders with a status Entered will be priced/re-priced. If you leave this parameter blank, then the concurrent program will select all open orders/lines irrespective of their booked status.

The following parameters are enabled only if the Pricing Level selected is Line:

Select OK, then Submit. The log file generated as a result of a submission of the Batch Price concurrent program displays all order details selected for processing based upon the input parameters entered.

Purge Order Management Workflow Concurrent Program

This concurrent program purges workflow items associated with Oracle Order Management, such as OM Order Line and OM Order Header. Unlike the Purge Obsolete Workflow Runtime Data program provided by Oracle Workflow, the Purge Order Management Workflow program purges workflows of closed sales order lines even if the sales order header is still open. It tries to close open workflows in a few very specific cases to make more workflow items eligible for purge. Use this purge program to reduce the size of workflow tables and improve high volume order processing performance.

To purge Order Management workflows of closed sales orders:

  1. Navigate to the Submit Request window and select Purge Order Management Workflow.

  2. Select the workflow item type to purge the closed workflows corresponding to a single item type. The default value for this parameter is All Item Types. If you do not select any item type, then the concurrent program purges all the closed workflows, corresponding to workflows of type OM Order Header.

  3. Enter the unique identifier of the workflow item that you want to purge. The application uses this information to purge the workflow corresponding to the workflow item key.

  4. Enter the number of elapsed days after closure to purge workflows that were completed no later than this many days ago.

  5. Select an applicable Attempt to Close option. If the workflow item type is OM Order Header or All Item Types, then the concurrent program identifies and attempts to close all the header workflows that are open due to pending line closure, even though all the lines in the order are in fact closed. If the workflow item type is OM Error, then the concurrent program identifies all the OM Error and WF Error flows that are either orphan, or those that are associated with OM flows that are no longer in error. The program completes the error flows and purges them.

  6. Enter the purge frequency of the workflow data. The default value is 500. The application issues commits to the database engine after every 500 purged workflow items.