This batch process pulls in specific order records (as determined by your batch process parameters) currently listed as “Active” and/or “Proforma” and changes the order line status to “Cancelled". For example, using the Order Line Status parameter, you can run ORD500 so that "Proforma" lines are cancelled while leaving the "Active" lines alone.
Associations commonly use this process on orders expired or still unpaid after an extended amount of time that they no longer want to maintain as “Proforma.” For example, you can choose to have the ORD500 process update any “Proforma” Subscription order lines that have not updated in the last six months. Usually this occurs with Membership and Subscription orders, but you can set the process to work on Inventory orders as well.
If the order line being cancelled is invoiced, ORD500 will set all of the amount fields in Order_Detail to 0.00 except BASE_UNIT_PRICE. If the order line being cancelled has not been invoiced, all of the amount fields including BASE_UNIT_PRICE will be set to 0.00.
In order to preview orders to be cancelled, ORD500 can be run in EDIT or PROD mode. If run in EDIT mode, the process generates the report but does not update the data. If run in PROD mode, the report is generated, order line records are updated and financial transaction records are created or updated.
ORD500 uses the value entered in the “Months from Order Date” parameter to identify orders to be updated. The logic used by system varies based on subsystem, as described below:
Subsystem |
Date to Which “Months From Order Date” is Added |
Description |
---|---|---|
Membership |
Order_Detail.CYCLE_BEGIN_DATE |
If month/year of CYCLE_BEGIN_DATE + “Months From Order Date” <= system date, order line will be selected. |
Subscription |
Order_Detail.CYCLE_BEGIN_DATE |
If month/year of CYCLE_BEGIN_DATE + “Months From Order Date” <= system date, order line will be selected. |
Meeting |
Mtg_Product.START_DATE of the meeting product in the order line |
If month/year of START_DATE + “Months From Order Date” <= system date, order line will be selected. |
Exhibition |
Xbt_Product.START_DATE of the exhibition product in the order line |
If month/year of START_DATE + “Months From Order Date” <= system date, order line will be selected. |
All Other Subsystems |
Order_Detail.ORDER_DATE |
If month/year of ORDER_DATE + “Months From Order Date” <= system date, order line will be selected. |
When an order line is cancelled, if there are related sub-order lines or components that do not contain shipped INV products, those order lines will also be cancelled.
Proforma Order Lines – When ORD500 cancels proforma order lines, the process updates the amount on the order line and on the Type 4 sales transaction to zero, along with any Type 9 scheduled future payment.
Active, Invoiced Order Lines – When ORD500 cancels active, invoiced order lines, the process creates the Type 6 adjustment transaction and updates the amount for any Type 9 scheduled future payment to 0.
Active, Un-Invoiced Order Lines – When ORD500 cancels active, un-invoiced order lines (e.g., INV order lines that have not shipped), the process updates the amount on the order line and on the Type 4 sales transaction to zero, along with any Type 9 scheduled future payment.
If active order lines are cancelled by ORD500, ORD500 assumes that no revenue should be recognized and will create the necessary Type 7 transactions to reverse any previously recognized transaction.
A application parameter "NUMBEROFRECORDSPROCESS" has been added for defining the number of records to process in a batch. The default value is to process 1000 records per a batch; if you are processing more than 1000 records, increase this value. In addition, a the new error report has been created that will show the exception records. Refer to Setting Up Application Parameters for additional information.
Parameter |
Description |
Required? |
---|---|---|
Subtitle |
This field is used to enter in a subtitle that appears underneath the report heading. |
No |
Run Mode |
Mode in which the report runs: · EDIT – the process creates a report listing the order line numbers that qualify, but does not update the order line status values in the database. · PROD – the process creates a report listing the order line numbers that qualify, and updates the database as defined in the “Financial Impact” section above. |
Yes |
Organization |
The Organization for which you want to run the report. |
Read-only |
Organization Unit |
The Organization Unit for which you want to run the report. |
Read-only |
Subsystem |
Chooser. Determines the subsystem to run the process against. |
Yes |
Months From Order Date |
Text. Enter in the number of months since the order was created and has not been paid in full. For other order types this value is added to the date the order was placed. You can set this parameter to a negative number if you want to cancel orders that have a cycle begin date in the future instead of in the past. |
Yes |
Cancellation Reason Code |
Chooser. Determines the value entered in the Cancellation Reason field for each order line the process cancels. Options are populated based on the non-fixed codes defined for the ORD "LINE_STATUS_REASON" system type. |
Yes |
Order Line Status |
Chooser. Determines the Order Line Status
you want the batch process to search for and then replace with
“Cancelled.” For example, P (Proforma) or A (Active). |
Yes |
Advanced Job Parameter |
||
Filter Criteria |
Additional filter clause for record selection. Filter should be in the following format TableName.FieldName = condition. For example, Order_detail.Order_No = '1000000125'. Filter can be based on fields from Order_Master, Order_Detail & Customer table only. |
No |