Periodic Functions Available to Schedule
Purpose: The tables below provide a list of the periodic functions you can use to schedule certain functions in Order Administration.
See How to Schedule a Job for information on how to schedule a periodic process.
Periodic Functions Available to Schedule
General Usage (ALL) Periodic Functions
The table below lists the periodic functions associated with General Usage processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
AUTHALL |
PFR0131 |
|
As needed |
Authorize All Open Orders Calls Performing Batch Authorization (SATH), which processes online authorizations for all open orders that contain a credit card or stored value card payment that requires authorization. This periodic function allows you to use the job scheduler to schedule when you wish to process the Batch Authorization Program (SATH). |
BO_REAS |
PFR0024 |
|
Daily |
Evaluate Backorder Reasons without Backorder Warehouse Tries to reserve order detail lines that have a backorder reason, but no backorder warehouse. If inventory is not available, this function assigns a backorder warehouse so that the order detail line will process through Evaluate Backorders. See Working with the EBO_ASYNC Job. If an order line on backorder is reserved, the system determines whether the order line is eligible for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
BROKER |
PFR0083 |
|
As needed |
Generate Order Orchestration Requests Generates Order Orchestration requests for currently eligible orders that have not previously been submitted to the Order Broker. You might use this function when you are first starting to use the Order Orchestration integration, or on a periodic basis to generate requests for backordered lines that were not previously eligible because, for instance, the order was held. See the Order Orchestration Integration for an overview. |
CLR_MTH |
MSR0576 |
|
Monthly |
Monthly Clear Process Clears (updates the zero) the MTD (month-to-date) fields in all tables. Tables affected include Flash Report, Item Warehouse, Location. |
COPYCMP |
PFR0200 |
FROM TO Y/N where: FROM is the From company number TO is the To company number Y/N is a Y or N setting indicating whether the system should delete the data in the To company before copying. Unless you can verify that you are not copying over any records that already exist in the target company, this setting should be set to N. Note: Separate each parameter setting with a single space. |
|
Copy Company Uses the following parameters to create a company:
Note: Separate each parameter setting with a single space. For example, enter the following in the Parameter field, where 1 is the From company number, 2 is the To company number, and N is the Delete To company parameter: 1 2 N . COPYCMP will not run if the “from” company has any EFTConnect configured merchant accounts. That is, having any merchant account record in the Payment Configuration screen. The copy company (COPYCMP) should only be done from 49 or 51 where EFTConnect is not enabled in the "From" company. If EFTConnect is enabled, the Copy Company periodic function cannot be run for copy or delete processes. Delete Company To use this periodic function to delete a company, enter the company you wish to delete in the From and To company parameters and set the Delete parameter to Y. For example, enter the following in the Parameter field, where 1 is the company you wish to delete and Y is the Delete parameter: 1 1 Y |
|
|
|
|
Note: Do not run this periodic function while users are still using the applications listed above. If you delete Active Procedures records while a user is still in the application, the user job will not be ended; that user can still enter transactions in the application, but transaction records cannot be sent to the data queues for processing because the data queues are reorganized when the ASYNC jobs end. No back end table updates for that user's transactions will be posted, which will cause your data tables to be out of sync. |
DLYCLR |
MSR0574 |
|
Daily |
Clear Daily Journals
Tables affected include Flash Report, Division, Item Warehouse, Order Type/User, Ship Via. You should run daily reports before executing this periodic function. Add this function as the last one (or just before reorganizing data tables) in a daily periodic process. |
DSHPROC |
FLRDSHP |
|
Daily |
Process Drop Ship Orders Processes all drop ship orders by vendor, and generates vendor drop ship worksheet, purchase orders and invoices, or pick slips. Output depends on the Drop ship output selection in the Second Create Vendor Screen. You can also submit this process on demand at the Select Vendors for Drop Ship Screen. |
DSLJPAY |
ACR0315 |
|
Daily |
Daily Sales Journal by Pay Type Generates the Daily Sales Journal by Pay Type. |
DSLJRN |
ACR0216 |
|
Daily |
Daily Sales Journal Generates the Daily Sales Journal. |
ECOMERR |
ECR0295 |
|
Daily |
Batch OM Transaction Error Listing Generates the E-Commerce Order Maintenance Errors Report. See Working with Batch Order Maintenance Transactions (WBOM). |
ENDIJCT |
ILENDGENER |
The Process ID for the integration layer process you wish to end. |
As needed |
End IJCT Process Passed Ends the integration layer process whose Process ID is defined in the Parameter field. Example: If you define ITEM_OUT in the Parameter field, this periodic function ends the ITEM_OUT integration layer process. |
FUTURE |
FLR0246 |
|
Daily |
Evaluate Future Orders Evaluates and
reserves orders. If the If the order is reserved and updated to an open status, the system determines whether the order is eligible for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
JOBCLN |
PFJOBCLNUP |
|
After server restart or as needed |
The function:
Requirement: The user submitting this function must be flagged as a Security Administrator, with a User Rank of 1. Note: If you run this function by submitting it through the ProcessIn service, the wait_for_completion flag should be set to N. For more information: See Using the JOBCLN Function to Resolve Job Status Across Servers. |
MDADRCG |
CSX1069 |
|
Daily |
Marketing Download Address Change Report Generates the Marketing Download Change of Address Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDCSCHG |
CSX1061 |
|
Daily |
Marketing Download Customer Status Change Report Generates the Marketing Download Customer Status Change Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDEXTR |
CSX1041 |
|
Daily |
Marketing Download Extract Extracts information from the Marketing Download Trigger table and populates the Marketing Download order-related and customer-related tables, based on the setting of the Populate Marketing Download Trigger File (G33) system control value. Once populated, deletes the associated records in the Marketing Download Trigger table. |
MDEXPRT |
PFR0130 |
|
Daily |
Marketing Download Export Exports the data in the Marketing Download order-related and customer-related tables to pipe-delimited files and places the files in the OMS-MARKETING container of the FILE_STORAGE table. Once the extract files are created, the system deletes the records in the associated Marketing Download tables. See Working with the Marketing Download Extract. |
MDINQSM |
CSX1066 |
|
Daily |
Marketing Download Inquiry Summary Report Generates the Marketing Download Customer Inquiry Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDORDHD |
CSX1044 |
|
Daily |
Marketing Download Order Header Report Generates the Marketing Download Order Header Interface Summary Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDORDTL |
CSX1058 |
|
Daily |
Marketing Download Order Detail Change Report Generates the Marketing Download Order Detail Interface Summary Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDSRCSM |
CSX1036 |
|
Daily |
Marketing Download Source Summary Report This download is no longer supported. |
ONHAND |
PFR0005 |
|
Monthly |
On Hand by Warehouse Generates the On Hand by Warehouse Report. |
OMS-OKM |
PFR0135 |
|
As needed |
OMS to OKM Switch Encryption Key Not currently used.. |
ORDSUM |
PFR0062 |
|
Daily |
Order Summary
Note: This periodic function performs updates similar to the THRESHD periodic function. |
PFSDOUT |
CSSDOUT |
|
Daily |
Sold Out Processing Generates the soldout notifications. .You can also submit this process on demand through the Generating Soldout Notifications (MSON). |
POSLOGX |
PFPOSX |
|
As needed |
POSLOG for XLink Generates and sends a custom POSLog to Xlink using the POSLOG XLink properties, or places it in the OMS-POSLOG container in the FILE_STORAGE table if the file storage API is enabled for exports. See the File Storage API for background. Note: To use this periodic function, you need to have a valid store number specified in the Default Location for ORCE Integration (K69) system control value. Also, you need to set up the store location in Work with Store Cross Reference (WSCR). |
PRMOUPL |
PRMOUPL |
|
|
Create or Delete Promotions Creates or updates promotions and related tables based on the information in the Promotion Upload table. See Promotion Upload for more information. |
PSJD |
ACR0321 |
|
Daily |
Print Sales Journal by Division Generates the Sales Journal by Division. |
PURGECS |
PFR0137 |
The number of days old the sold to customer must be to be eligible for purge. The system uses the last change date to determine the age of the customer sold to record. |
Daily |
Purge Sold To Customers Purges sold to customers that are older than the number of days specified. If the Parameter is blank or 0, records must be 365 days old to be eligible for purge. To be eligible for purge, the system verifies that:
See Purging Sold To Customers for background and for the list of tables that are purged. |
PURGEJH |
oracle.retail.oms.services.job.functions.PurgeJobHistoryJob |
None |
As needed |
Purge Job History Records The PURGEJH periodic function purges all records in the:
When a pod/server is started up, the JOBHISTORY and JENASYSJOB tables are not purged. |
PURGEOR |
PFR0114 |
Set the parameter to Y in order to generate the Purged Order List; otherwise, the report is not generated. |
Daily |
Purge Orders Purges orders that are closed or canceled, and that:
See Purging Orders (MPOR) for background and for the list of order-related tables that are purged. |
PURGEUA |
PFR0125 |
The number of days old a User Audit or Password Audit record must be to be eligible for purge. |
Daily |
Purge User Audit Table Purges User Audit and Password Audit records that are older than the number of days specified. If the Parameter is blank or 0, records must be 365 days old to be eligible for purge. See Tracking User, Authority, and Password Updates for background. |
PURGEUH |
PFR0126 |
The number of days old a Upload History record must be to be eligible for purge. |
Daily |
Purge Upload History Table Purges Upload History records that are older than the number of days specified in the Parameter field. If the Parameter is blank or 0, records must be 21 days old to be eligible for purge. See Work with File Uploads (WUPL) for more information. |
Inventory Quantity Reset |
MSR0698 |
|
Run when a problem is detected Note: Run this function only when you have a dedicated system; do not run this periodic function when the Billing Async is active, you are running pick slip generation or performing inventory transaction processing. |
Inventory Quantity Reset
Note: You can use Reset Allocation Quantities (MRPC) to reset the printed quantities for orders, as stored in the Order Detail, Reserved Order Line and the Item Location tables. The system uses the information in the Pick Control Detail and the Pick Location tables to determine the correct quantities. |
RESETOH |
PFR0093 |
|
Run when a problem is detected. |
Reset On Hand Quantity Resets the quantity on-hand for each Item Warehouse record based on the total quantities on-hand for related Item Locations within the warehouse. See Reset Item Warehouse Quantity On Hand (MRIW). Note: Run this function only when you have a dedicated system; do not run this periodic function when the Billing Async is active, you are running pick slip generation or performing inventory transaction processing. |
REVERSE |
PFR0133 |
|
Daily |
Send Reversals for Expired Authorizations Processes all open Authorization History records that are eligible for authorization reversal processing. Note: Run this periodic function daily so that expired authorizations are reversed in a timely manner without incurring penalty fees. Also, this function should be scheduled to run before the REAUTH periodic function. When you run this periodic function for a specified company, the system:
Note:
|
RFRECON |
PFR0008 |
|
Monthly |
Refund Reconciliation and Purge Purges refund checks once you have reconciled or voided the checks. Generates the Check Reconciliation List. |
RLTSLSF |
PFR0102 |
|
Daily |
Submit ORCE Sales Feed Sends sales information to Oracle Retail Customer Engagement. See Customer Engagement Sales Feed. The ORCE File Service URL (M62) and ORCE Import Folder Path (M63) system control values must be specified for the company in order for this periodic function to run. |
RSLTME |
CSR0557 |
|
Daily |
Release Order on Time Hold Releases prepaid orders from hold automatically when the number of days to hold the order (in the Hold days field in the Pay Type table) has passed, and releases orders held for credit card authorization. |
SCHDDEP |
Set the class name to: oracle.retail.oms.services.job.functions.DepositBatchSingleRunJob |
Positions 1-3: 3 position Authorization service code Positions 4-10: 7 position Purchases transactions to generate For example, where AUT is the authorization service code and 1234567 is the maximum number of deposits for purchases: AUT1234567 |
Daily |
Schedule Deposits Submits the deposit processing job. You can use the Parameter field to generate deposit transactions for a specific authorization service and/or define the maximum number of deposits to process for purchases. Note: You can define a Purchases transactions to generate number in the Parameter field only if the Preload Deposits (L78) system control value is unselected. If you do not define any parameters, the system uses the same settings as if you used the Auto Deposit Screen with all the default settings selected. This function requires you to specify a company when you set up the periodic process. |
|
|
|
|
The AUTO_DEP job selects records from the Invoice Payment Method table for the service bureau(s) selected for deposit that have not yet been processed for deposit or credit, and whose deposit release date is the current date or earlier. You can review the submitted AUTO_DEP job at the Job Management Screen. See Processing Deposits for more information. |
SCVREV |
PFR0077 |
|
Daily |
Stored Value Card Reversal Processes stored value card reversal trigger records (File type AHR) that are in a ready (R) status. See Transmitting Activation and Reversal Transactions (SSVC). |
SLSSMOT |
PFSLSSUMOT |
Date, in MMDDYY format |
Daily |
Sales Journal Summary by Order Type Generates the Sales Journal Summary by Order Type for the date specified in the parameter. If no date is specified, generates the report for the previous date. |
SLSUPLD |
PFR0109 |
|
As needed |
Sales Associate Upload Upload a Sales Associate file to create records in the Salesman table. See Salesman Associate Upload. |
STOP_EC |
ECX0243 |
|
Daily |
Stop E-Commerce Order Cleanup Stops the ORDER_CLN job. |
STRASYN |
MSSTRASYNC |
|
Daily |
Start Asyncs If the asyncs are currently Inactive, this periodic function calls the Controlling Data Queue (CNTL_ASYNC) in Background Job Control (MBJC) and starts the background jobs. This periodic function performs the same updates as selecting Start for the controlling data queue to start the background jobs. |
STRIJCT |
ILSTRGENER |
The Process ID of the integration layer process you wish to start. |
As needed |
Start IJCT Process Passed Starts the integration layer process whose Process ID is defined in the Parameter field. Example: If you define ITEM_OUT in the Parameter field, this periodic function starts the ITEM_OUT integration layer process. |
STRT_EC |
ECX0242 |
|
Daily |
Start E-Commerce Order Cleanup Starts the ORDER_CLN job. See Integration Layer Processes. |
SUSPEND |
OER0756 |
|
Daily |
Suspended Orders List |
SVCACT |
PFR0076 |
|
Daily |
Stored Value Card Activation Processes stored value card activation trigger records (File type SVC) that are in a ready (R) status. See Transmitting Activation and Reversal Transactions (SSVC). |
SYNCUSR |
PFRSYNUSR |
|
Daily |
Synchronize Users from IDCS or OCI IAM Create user records in Order Administration based on user records in IDCS or OCI IAM, using the settings defined for the DEFAULTCSU user. See User Configuration in the Administration Guide for more information. Note: You should schedule the function to run daily, or include the function in multiple periodic processes to run more than once a day, in order to keep user records in Order Administration synchronized with IDCS or OCI IAM. |
THRESHD |
PFTHRESHMO |
|
Daily |
Threshold Monitor
See Working with Threshold Values (WTHR). Note: This periodic function performs updates similar to the ORDSUM periodic function. |
TICKLER |
PFR0072 |
|
Daily |
Evaluate Create/Resolve Ticklers Evaluates the:
|
UPACSTP |
PFR0134 |
CSACST |
As needed |
UPACSTP Upload ACS Tape File Uploads an ACS Tape file named CSACST from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the ACS Tape table (CSACST). You must use the Process Address Changes (PACS) menu option to process the records in the ACS Tape table. See Work with File Uploads (WUPL) and Loading Address Updates. |
UPCATRQ |
PFR0134 |
IXCRIN |
As needed |
UPCATRQ Upload Catalog Request File Uploads a Catalog Request file named IXCRIN from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Catalog Request Interface table (IXCRIN). You must use the Work with Catalog Request Interface (WCRU) menu option to process the records in the Catalog Request Interface table. See Work with File Uploads (WUPL) and Working with the Catalog Request Interface (WCRU). |
UPCSTPG |
PFR0134 |
CUSTPGEUP |
As needed |
UPCSTPG Upload Customer Price Group Exclusion File Uploads a Customer Price Group Exclusion file named CUSTPGEUP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Customer Price Group SKU Exclusion Upload table (CUSTPGEUP). You must run the CPGIXUP Customer Price Group SKU Exclusion Upload periodic function (Program name PFRCPGEXUP) to process the records in the Customer Price Group SKU Exclusion Upload table. See Work with File Uploads (WUPL) and Customer Price Group SKU Exclusion Upload. |
UPLSDTA |
PFR0094 |
|
As needed |
Supporting Data Upload Creates supporting data records based on the information in the Supporting Data Upload table. See Importing Item-Related Supporting Data (SDUP) for more information. |
UPLSETS |
PFR0095 |
|
As needed |
Set Component Upload Creates set headers and components based on the information in the Set Component Upload table. See Importing Set Components (WCUP) for more information. |
UMPBSTP |
PFR0134 |
CSMBST |
As needed |
UPMBSTP Upload MBS Tape file Uploads an MBS Tape file named CSMBST from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the MBS Tape table (CSMBST). You must use the Process Address Changes (PACS) menu option to process the records in the MBS Tape table. See Work with File Uploads (WUPL) and Loading Address Updates. |
UPPOLAY |
PFR0134 |
POLAYR |
As needed |
UPPOLAY Upload PO Layering File Uploads a PO Layering file named POLAYR from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the PO Layering table (POLAYR) and then uses the newly uploaded records to update the due date and backorder quantity for order lines on backorder. See Work with File Uploads (WUPL) and Purchase Order Layering. |
UPPRCCD |
PFR0134 |
PRICECDUPLOAD |
As needed |
UPPRCCD Upload Price Code File Uploads a Price Code file named PRICECDUPLOAD from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Price Code Upload Table (PriceCdUpload). You must run the PCUPLD Price Code Upload periodic function (Program name PFPRCCODUP) to process the records in the Price Code Upload table. |
UPPROMO |
PFR0134 |
PRMUPLD |
As needed |
UPPROMO Upload Promotion Code File Uploads a Promotion file named PRMUPLD from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Promotion Upload Table (PRMUPLD). You must run the PRMOUPL Create or Delete Promotions periodic function (Program name PRMOUPL) or use the Work with Promotion Values (WPRO) menu option to process the records in the Promotion Upload table. |
UPRITEM |
PFR0134 |
RIIUPP |
As needed |
UPRITEM Upload Retail Item File Uploads a Retail Integration Item file named RIIUPP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the RI Item Upload Table (RIIUPP). You must run the RIUPLD Retail Integration Item Upload periodic function (Program name PFR0084) or use the Work with Retail Integration Item Upload (RIIU) menu option to process the records in the RI Item Upload table. See Work with File Uploads (WUPL) and Working with Retail Integration Item Upload (RIIU). |
UPSETCM |
PFR0134 |
INSCUP |
As needed |
UPSETCM Upload Set Component File Uploads a Set Component file named INSCUP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Set Component Upload Table (INSCUP). You must run the UPLSETS Set Component Upload periodic function (Program name PFR0095) or use the Work with Set Component Upload (WCUP) menu option to process the records in the Set Component Upload table. See Work with File Uploads (WUPL) and Importing Set Components (WCUP). |
UPSRCCD |
PFR0134 |
IXSRCE |
As needed |
UPSRCCD Upload Source Code File Uploads a Source Code file named IXSRCE from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Source Upload Table (IXSRCE). You must use the Work with Source Code Upload (WSRW) menu option to process the records in the Source Code Work table. See Work with File Uploads (WUPL) and Generating Source Codes Using the Source Upload Table (WSRW). |
UTSTSRP |
UTSTSRPT |
|
As needed |
Managed Services Report Generates the Managed Services report, used by Oracle staff to manage system processing. |
UPVENDR |
PFR0134 |
VNDUPL |
As needed |
UPVENDR Upload Vendor File Uploads a Vendor file named VNDUPL from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Vendor Upload Table (VNDUPL). You must run the VNDUPLD Vendor Upload periodic function (Program name PFR0086) or use the Submit Vendor Upload (LVUP) menu option to process the records in the Vendor Upload table. |
WEEKCLR |
MSR0575 |
|
Weekly |
Weekly Clear Clears week-to-date (WTD) fields in the SKU Offer Page table (INSKOP). |
YEARCLR or CLR_YR |
MSR0577 |
|
Yearly |
Clear Yearly Totals Clears (zeros) yearly (YTD) buckets in tables such as Flash Report table (FLFLSH). |
Customer Service (C/S) Periodic Functions
The table below lists the periodic functions associated with Customer Service processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
EFTSTA |
PfrEFTStatus |
|
As needed (see notes) |
Request Payment Status Update for Pending Transactions in EFTConnect Checks the current status in EFTConnect of each order payment transaction record that is currently in SENT status, as this status indicates that Order Administration previously received a PENDING result code from EFTConnect for the transaction. The records can be in SENT status because the payment provider does not respond immediately to EFTConnect for a capture or refund message, but sends these updates to EFTConnect as they are available. When Order Administration receives a PENDING result code in an authorization reversal (VOID) response message from EFTConnect, the IL outbound record status will be changed to P (PENDING). Based on the status response received from EFTConnect for each transaction record, the periodic function updates the order payment transaction to:
Afterward, when you process deposits through SDEP:
Note:
|
OPENPP |
PFR0006 |
|
Monthly |
Open Prepaid Orders List Generates the Open Prepaid Order List. |
REAUTH |
PfrReauth |
|
Daily |
Reauthorize Expired Payment Authorizations This function submits reauthorization requests for expired authorizations, and processes updates based on whether the reauthorization is approved or declined. See Reauthorizing Expired Authorizations for more information. Oracle recommends that you schedule this function to run after the REVERSE periodic function. Also, it should not be scheduled to run during shipping. This job submits an active procedure. See Purge Active Procedures Across Users (MACX) for more information. Note: You need to select the Perform Reauthorization for Expired Authorizations (M61) system control value in order to use this function. |
REFCCCR |
PFR0115 |
|
Daily |
Process Credit Card Credit Refunds Process credit card credits with no limit on the amount to generate. The system generates a Credit Card Credit Register that identifies the amount, customer name, and order number of each credit processed. The system also produces either a Credit Card Credit Acknowledgement (if the Print Credit Card Credit Acknowledgements (C35) system control value is selected) or an email notification when the Credit Card Credit Acknowledgement E-Mail Program (H08) is set to CCCNOTF, (regardless of the setting of the Print Credit Card Credit Acknowledgments (C35) value) for each credit as appropriate; see When Does the System Generate an Email Notification? See Processing Refunds (MREF) for processing information. |
REFDUET |
CSR0986 |
|
Monthly |
Refund Due List by Type Generates the Refund Due List by Type. |
REFPROC |
CSR0533 |
|
Monthly |
Refunds Processed Generates the Processed Refund Register. |
REFSVCR |
PFR0118 |
|
Daily |
Process SVC Credit Refunds Process stored value card credits with no limit on the amount to generate. The system issues a new stored value card to the sold to customer for the refund amount. The system also:
You can then follow the normal process of activating, billing, and shipping the stored value card to the customer. See Generating Stored Value Card Refunds for an overview. |
REFWRO |
PFR0009 |
|
Monthly |
Refunds Written Off Writes off refunds and generates the Refund/Write Offs - Refund Checks report. See Working with Refunds, Writeoffs and Balances Due (WREF). |
RSTCONO |
CSRSTONORD |
|
Run when a problem is detected |
Reset Customer Sold To Amount On Order Resets the On order amount field in the Customer Sold To Order History table so that it matches the amount of any existing open orders for the customer. See Resetting Customer Sold To Amount On Order (RONO). Note: End all background async jobs so that the On order amount is not changed while the reset job recalculates the On order amount. |
UNACTSV |
PFR0075 |
|
Daily |
Unactivated Stored Value Cards Generates the Unactivated Stored Value Card Report. You can use this report to review any stored value cards that require attention because:
|
EMAILUD |
PFR0089 |
|
Daily |
Customer Email Status Updates Matches a record in the Customer Email Updates Table to a sold to customer and, if an exact match is found, updates the sold to customer’s Opt in/opt out field with the Email Status defined for the customer email updates record. Generates the Unmatched Email Status Report, which lists records in the Customer Email Updates table that were not matched to a sold to customer. See Receiving Customer Email Status Updates From an External System for an overview and the required setup. |
E-Commerce (EDC) Periodic Functions
The table below lists the periodic functions associated with E-Commerce processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
ECOMINV |
ECR0389 |
|
Daily |
E-Commerce Item XRef All Items Downloads all items that contain a long SKU style number to the EC SKU Retail XRef table and EComm SKU Extract table. |
ECOMNEW |
ECR0390 |
|
Daily |
E-Commerce Item XRef New Items Downloads new items that contain a long SKU style number to the EC SKU Retail XRef table and EComm SKU Extract table. |
ECSHCNF |
ECR0154 |
See description. |
Daily |
Shipment Confirmation Emails Sends shipment confirmation emails. See Sending Internet Order Ship Confirmation (ESCF). Note: If you use the Narvar Integration, Narvar generates shipment confirmation emails to the customer based on an order request message sent through billing, and the shipment confirmation is not generated through the process described here. Optionally, enter a parameter of the days prior to the current date for the function to use when selecting shipment confirmation emails, based on invoice date. Example: The current date is January 21. In order to generate shipment confirmation emails for orders billed on January 19, set the parameter to 2. Note: The new parameter also controls the generation of return confirmation emails. |
Fulfillment (FUL) Periodic Functions
The table below lists the periodic functions associated with Fulfillment processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
Description of the pick slip generation template you wish to run |
PFR0107 |
The Description of the pick slip generation template you wish to run. Note: The Parameter must match the Description defined for the pick slip generation template. For example, if the description of the pick slip generation template is ORDER #, the parameter must also be ORDER # and not ORDER#. |
Daily |
Scheduled Pick Slip Generation Runs pick slip generation using the pick slip generation template specified in the Parameter field. See Scheduling Pick Slip Generation for more information. |
CARRYOV |
PFR0033 |
|
|
Carryover Report Prints the Carryover Report. |
LOBSTAT |
PFR0034 |
|
Daily |
Reset Line of Business Stats Updates line of business order queue statistics. |
RESRVBO |
FLR0804 |
|
Daily |
Reserve Backorders Evaluates backorders by searching for any item warehouse that has a backorder quantity greater than 1 and whose on-hand quantity - reserved quantity is greater than 0. Will try to reserve the order detail line (as long as a cancel date does not exist). See Working with the EBO_ASYNC Job. If an order line on backorder is reserved, the system removes any pick slip preparation from the order and then reevaluates the order for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
RSTPICK |
PFR0111 |
|
As needed |
Reset Pick Control Resets the printed quantities for orders, as stored in the Order Detail, Reserved Order Line and the Item Location tables. The system uses the information in the Pick Control Detail and the Pick Location tables to determine the correct quantities. You can also perform the same updates using the Reset Allocation Quantities (MRPC) menu option. |
STRCDC |
ILStrCDC |
|
Daily |
Start External Drop Ship Integration Starts the CDC Async job used to process transactions between Order Orchestration’s Drop Ship Manager and Order Administration in the Order Orchestration Drop Ship Integration. |
ENDCDC |
ILEndCDC |
|
Daily |
End External Drop Ship Integration Ends the CDC Async job used to process transactions between Order Orchestration’s Drop Ship Manager and Order Administration in the Order Orchestration Drop Ship Integration. |
PURGPCL |
PFR0091 |
|
Weekly |
Purge Unused Pick Control Labels Submits the PURGPCL job, which:
|
BILLUPD |
Set the class name to: oracle.retail.oms.services.job.functions.BillingUpdateBatchJob |
Number, up to 3 positions, to indicate the number of seconds to wait between processing; if no number is specified, an interval of 60 seconds defaults |
Daily |
Delay Billing Updates Submits the BILLUPD job, which processes deferred billing updates for records in the Invoice Header table whose Process Date field is 0. You must run the Delay Billing Updates Process if you select the Delay Billing Updates (K85) system control value; see this system control value for more information. Also, see Batch Billing Updates for a table that lists the billing updates that are deferred until you run the Delay Billing Updates Process. Note: You can also submit the Delay Billing Updates Process using the BILL_UPD Billing Updates integration layer job. When this job is active, at defined intervals the job processes deferred billing updates for records in the Invoice Header table whose Process Date field is 0. The Outbound delay time defined for the BILL_UPD integration layer job defines how often the job processes the deferred billing updates. Example: If the Outbound delay time is 60, the system looks for deferred billing updates to process every 60 seconds. |
BATSTPC |
PFSTPBATCH |
As needed |
Stop Batch Billing Update Job for All Companies Stops the BILLUPD job for all companies. The Company Parameter should be unselected. |
|
BATSTPA |
PFSTPBATCH |
As needed |
Stop Batch Billing Update Job Company Specific Stops the BILLUPD job for the specified company. The Company Parameter should be selected. |
|
PICKRFH |
PFR0103 |
|
Daily |
Pick Gen Refresh Submits a process that evaluates orders for pick slip preparation, and if eligible: 1. Removes any pick slip preparation that may have already occurred for the order; see Removing Pick Slip Preparation from an Order for the updates that are performed. 2. Applies pick slip preparation to the order; see Applying Pick Slip Preparation to an Order for the updates that are performed. See Batch Pick Slip Preparation for additional details. |
Interface (INT) Periodic Functions to Start and Stop IJCT Jobs
The table below lists the periodic functions provided for starting and stopping IJCT jobs on a regular basis. Each “start” program starts the related IJCT job if it is currently inactive, while each “end” job ends the job if it is currently active. You would normally schedule these jobs to start and stop on a daily basis, but this schedule may vary based on your business requirements.
See Working with Integration Layer Processes (IJCT) for more information on each IJCT job.
Start Function | Start Program | End Function | End Program |
---|---|---|---|
BROKER: Generates Order Orchestration fulfillment requests, inquiry requests, and update requests, and receives responses. |
|||
STRBROK |
ILSTRBROKR |
ENDBROK |
ILENDBROKR |
BROKER_ORD: Generates Order Orchestration requests for new orders and cancellations, sends status updates, and receives responses. |
|||
STRBRO |
ILSTRTBROK |
ENDBRO |
ILENDBROK |
CUST_OUT: Generates an outbound message for each customer that you create, change, or delete. |
|||
STRCSTD |
LSTRCSTOT |
ENDCSTD |
ILENDCSTOT |
EMAIL: Receives email messages and creates Correspondence History and Correspondence History Detail records. |
|||
STREML |
ILSTREMLIN |
ENDEML |
ILENDEMLIN |
INV_INQURY: Receives a request for inventory availability on a specific item/SKU and generates a response. |
|||
STINVIQ |
ILSTRINVIQ |
ENINVIQ |
ILENDINVIQ |
INV_DOWNLD: Sends inventory availability information to another system. |
|||
STRINVD |
ILSTRINVDN |
ENDINVD |
ILENDINVDN |
INVOIC_OUT: Sends invoice information to another system. |
|||
STRINVO |
ILSTRINVOT |
ENDINVO |
ILENDINVOT |
INVTRAN_IN: Receives inventory transactions and updates inventory information, such as in the Item Location and Item Warehouse tables. |
|||
STRITRN |
ILSTRINVIN |
ENDITRN |
ILENDINVIN |
ITEM_OUT: Sends item and SKU information to another system. |
|||
STRITEM |
ILSTRITMOT |
ENDITEM |
ILENDITMOT |
ORDER_IN: Receives new orders through a generic order interface and optionally generates detailed or simple acknowledgments, as indicated by the inbound order message. |
|||
STRORDR |
ILSTRORDIN |
ENDORDR |
ILENDORDIN |
PICK_OUT: Sends a pick slip message for each generated or voided pick slip. |
|||
STRPICK |
ILStrPickO |
ENDPICK |
ILEndPickO |
PO_OUT: Sends purchase order information to an external system. |
|||
STRPOOU |
ILStrPOOut |
ENDPOOU |
ILEndPOOut |
RETURN_OUT: Sends customer return information to an external system. |
|||
STRRTO |
ILStrRtOut |
ENDRTO |
ILEndRtOut |
SVC_REVRSL: Sends stored value card reversal transactions to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVR |
ILStrSVCRv |
ENDSVR |
ILEndSVCRv |
VENDOR_OUT: Sends vendor information to another system. |
|||
STRVEND |
ILSTRVNDOT |
ENDVEND |
ILENDVNDOT |
Additional Interface (INT) Periodic Functions
The table below lists additional periodic functions associated with integration layer processing besides those listed above under Interface (INT) Periodic Functions to Start and Stop IJCT Jobs. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
ACTPO |
PFR0205 |
|
As needed |
Submit Active PO Order Lines to Order Orchestration and Generate RICS Backorder Message Requests inventory availability, submits existing active PO order lines to Order Orchestration for fulfillment and generates the backorder quantity update notification message to RICS. For more information: See Enterprise Order Integration (Future Receipts and Active PO/Pre-Order Processing) for background. |
CAINV |
PFCAINV |
|
As needed |
ChannelAdvisor Inventory Upload Generates a file of current inventory levels for send to ChannelAdvisor. See Sending Current Inventory Information to ChannelAdvisor for an overview. |
CAORDUP |
PFCAOUP |
|
As needed |
ChannelAdvisor Order Upload Sends ChannelAdvisor a request for new orders and creates orders based on the information in the order response message. See Importing Orders from ChannelAdvisor for an overview. |
CAPRICE |
PFCAPRICE |
|
|
ChannelAdvisor Price Upload Generates a file of current pricing for items sold through the ChannelAdvisor integration. See Sending Current Prices to ChannelAdvisor for an overview. |
CAREQAC |
PFRCAREQS |
Enter connection information using the following format: REQUEST ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS cb12d3b4-f123-1234-1234-12a3c456e7d8 12345678 |
As needed |
ChannelAdvisor Request Access Run this periodic function to request access to ChannelAdvisor for the specified AccountID. Before running this periodic function, enter connection information in the Parameter field using the following format: REQUEST ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS ab12d3b4-f123-1234-1234-12a3c456e7d8 12345678 Note: This periodic function should be run one time for each account as part of initial setup of the ChannelAdvisor integration. In addition, once you establish a connection with ChannelAdvisor, you can change the Parameter field to the following format: STATUS ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS ab12d3b4-f123-1234-1234-12a3c456e7d8 12345678 Run the periodic function to write information to the Application log about the status of the access to ChannelAdvisor. See ChannelAdvisor Setup. |
CASHIP |
PFCASHIP |
|
As needed |
ChannelAdvisor Ship Confirmation Upload Sends shipment confirmation messages to Channel Advisor. See Sending Shipment Confirmations to ChannelAdvisor for an overview. |
CPGIXUP |
PFRCPGEXUP |
|
Daily |
Customer Price Group SKU Exclusion Upload Submits the Customer Price Group SKU Exclusion Upload Process to upload customer price group item exclusion information from an external system to create, update, or delete records in the Customer Price Group SKU Exclusion table. See Customer Price Group SKU Exclusion Upload for an overview. |
IHDWOIT |
PFR0106 |
|
As needed |
Invoice Download Comparison Matches invoices created for the previous day to records in the IL Trigger table with a record type of IHD. If an invoice exists without a corresponding IHD trigger, the system creates an Add IHD trigger record and writes a message similar to the following in the Trace log: Periodic Function IHDWOIT may have created a IHD WOIT Transaction for Company#:7 Order # : 2844 Invoice #: 573. See Generic Invoice Download API for an overview on the Invoice Download process and the required setup in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1) |
IMPSTLC |
PFR0122 |
Example: If the parameter is set to NPOS, the periodic function imports location records for system POS in Order Orchestration, and leaves the Ship for pickup flag for each imported location unselected. |
As needed |
Import Store Cross Reference Locations through Order Orchestration’s Discovery Web Service Uses Order Orchestration’s discovery web service to request information on all existing location associated with a specified system in Order Orchestration, and create Store Cross Reference records for locations if they do not already exist. See Importing Store Cross Reference Locations through Order Orchestration’s Discovery Web Service. |
INVOVRL |
PFINVOVR |
|
Daily |
Processes an inventory upload file if it is found in the directory defined in the CWDIRECTCP_UPLOAD_DIRECTORY property or uploaded through the File Storage API, updating the Item Location record with the on-hand quantity, or creating it if the Item Warehouse exists. See Batch Inventory Overlay Upload for more information. |
INVDWNL |
ILR0081 |
|
Weekly |
Inventory Download Creates inventory download triggers (File type ITW) for an item/SKU if:
See Generic Inventory Download API in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
OBPROD |
PFR0127 |
|
As needed |
Order Orchestration Product Output File Generates a Product output file for import into Order Orchestration. This file contains product information for a specified company. See Order Orchestration Product Output File for details. |
OBPRLOC |
PFR0128 |
|
As needed |
Order Orchestration Product Location Output File Generates a Product Location output file for import into Order Orchestration. This file contains product location information for a specified company. See Order Orchestration Product Location Output File for details. |
OBINCIN |
PFR0129 |
|
As needed |
Order Orchestration Incremental Inventory Output File Generates an Incremental Inventory output file for import into Order Orchestration. This file contains inventory updates for a specified company. See Oracle Retail Order Orchestration Incremental Inventory Output File for details. |
OCDSFA |
PFR0203 |
|
Daily |
OCDS Import Future Availability Updates the Active PO flag for active PO items, and updates item warehouse quantities to support identifying when to release eligible active PO items to Order Orchestration for fulfillment. See Enterprise Order Integration (Future Receipts and Active PO/Pre-Order Processing) for background. |
OCDSITM |
PFR0202 |
FULL or INCREMENTAL |
As needed |
OCDS Import Product Data Generates requests to Omnichannel Cloud Data Service OCDS) for item-related data, including merchandise hierarchy, items, item prices, and item images. See Importing Enterprise Foundation Data through Omnichannel Cloud Data Service (OCDS) for an overview, and see OCDSITM Periodic Function for information on scheduling options. This function also deletes Enterprise Data History records older than the OCDS_JOB_HISTORY_RETENTION_DAYS defined through Working with Admin Properties. These records track activity for the OCDSITM and OCDSFA periodic functions. You can review history at the Enterprise Data Import History screen in Modern View. |
PCUPLD |
PFPRCCODUP |
|
Daily |
Price Code Upload Submits the Price Code Upload Process to upload price code information from an external system to create, update, or delete records in the Price Code, Price Code Customer, and Price Code Details tables. See Price Code Upload for an overview. |
PURGIJT |
ILR0026 |
|
Weekly |
Purge IJCT Trigger Records Purges IL Outbound Trigger records older than the number of days specified in the Outbound Interface Trigger File Purge Days (I14) system control value, using the following calculation: Last processed date is less than the current system date by the number of purge days and Status is X. |
RCVRTLG |
PFR0207 |
The name of each RTLOG log file to recover, separated by double pipes |
As needed |
Recover Sales Audit RTLOG to Object Storage Retrieves the RTLOG file specified in the Parameter for this periodic function, and resubmits the file to object storage for the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service, using the same process that was used in the SNDRTLG function. Use when? You would resubmit an RTLOG file if the SNDRTLG periodic function did not succeed when submitting the file to object storage for the Sales Audit Module, although no error was returned to the POST or PUT request messages. You would not use this function when an error was returned to the SNDRTLG function, because in this case the file is not saved to the FILE_STORAGE table. Instead, you should correct whatever caused the SNDRTLG to fail, such as an authentication issue, and then submit SNDRTLG again. Determining the file name to resubmit: The SNDRTLG periodic function saves each RTLOG file to the OMS-SALES-AUDIT container of the FILE_STORAGE table. You can use the getFiles web service request to request a list of records in the table, and identify the file name based on when the FILE_STORAGE record was created. Parameter format: Use the Parameter field for the periodic function to indicate the name of the RTLOG file that requires recovery. For example: RTLOG_1234567890_23456789012345678.zip. For more information: See:
|
REVXAHP |
PFREVXAHP |
Stored value card pay type code that uses the External Payment Service |
Daily |
Reverse Partial Auth for External Payment Service Generates SVC reversal request messages for the external payment service, provided the parameter specified is a stored value card pay type code that is configured to use the external payment service. See Stored Value Card Reversal with the External Payment Service in Stored Value Card Authorization Reversal for an overview. |
RIPRCUP |
PFRRIPRCUP |
|
Daily |
Pricing Upload Submits the Pricing Upload Process to upload records from the Pricing Upload table to the Special Pricing by Source table and QPM Detail table. See Pricing Upload Interface for an overview. |
RLTCSUP |
PFRBCC |
|
As needed |
Customer Upload to Oracle Retail Customer Engagement Sends all Order Administration sold to customers, excluding any sold to customers whose Ghost field in the Customer Sold To table is Y, to Oracle Retail Customer Engagement using the batch Customer Engagement Add or Update Customer Message. See Customer Engagement Batch Customer Conversion. Note that the ORCE File Service URL (M62) and ORCE Import Folder Path (M63)system control values must be specified for the company in order for this periodic function to run. |
RTLOG |
PFR0201 |
Store number in the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service |
Daily |
Export Transactions to Sales Audit Module Exports sales and returns information to the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service. Transaction information is collected in a temporary file throughout the day. The periodic function adds file header and footer information, deletes the temporary file, and creates a DAT file for the Sales Audit module. When integrating with Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service (Sales Audit module) 21.0 or above, you can use the SNDRTLG periodic function to submit the RTLOG file to object storage. See Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service. |
SLSUPLD |
PFR0109 |
|
Daily |
Upload Salesman Associates Submits the Salesman Associate Upload Process to upload salesman information from an external system to create or update records in the Salesman table. See Salesman Associate Upload for an overview and the required setup. |
SNDRTLG |
PFR0206 |
Store number in the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service |
Daily |
Transmit Sales Audit RTLOG to Object Storage Retrieves the RTLOG file from the CWDIRECTCP_FTP_FOLDER, where the RTLOG periodic function placed it, and transmits the file to object storage. Object storage: Use of object storage is supported for the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service (Sales Audit module) 21.0 and above. This function also saves a copy of the RTLOG file in the OMS-SALES-AUDIT container of the File Storage table. If this function fails to transit the file to file storage table, you can use the RCVRTLG periodic function to resubmit the file. See that periodic function for more information, and see Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service for background. |
STRUPLD |
PFR0110 |
|
Daily |
Upload Stores Submits the Store Upload Process to upload store information from an external system to create or update records in the Store Cross Reference table. See Store Upload for an overview and the required setup. |
SYNCRDB |
PFR0105 |
|
As needed |
Synchronize Remote Customers Submits unsynchronized customers to Oracle Retail Customer Engagement, using the Synchronize with remote DB field in the Customer Sold To table as a trigger. You would use this periodic function to support the interactive customer integration with Oracle Retail Customer Engagement. See Synchronizing Customer Information through a Periodic Function for more information. |
Inventory (INV) Periodic Functions
The table below lists the periodic functions associated with Inventory processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
CLROH99 |
PFRCLROH99 |
|
As needed |
Clear On Hand for Division 99 Allows you to clear the on-hand inventory for each warehouse whose Division is 99. The system clears the on-hand quantity for the warehouse in the Item Warehouse table and Item Location table. |
FGUPDT |
PHR0049 |
|
Monthly
Note: Do not run this periodic function when Asyncs are active. |
Update Cost of Finished Goods
Note: If a component item changes and you do not run this periodic function, the finished good item cost will not be accurate and reports will not be correct. |
PFR0063 |
PFR0063 |
|
Daily |
Drop Ship On Hold Report Generates the Drop Ship Integration Items on Hold from Vendor report. |
PFR0064 |
PFR0064 |
|
Daily |
Drop Ship Revised Due Date Report Generates the Drop Ship Integration Items with Revised Due Date report. See Printing Drop Ship Reports (PDSR). |
PFR0065 |
PFR0065 |
|
Daily |
Drop Ship Pending Cancel Report Generates the Drop Ship Integration Items Pending Cancellation report. See Printing Drop Ship Reports (PDSR). |
PORST |
OER1018 |
|
As needed |
PO Reset Resets the open PO quantities in the Item Warehouse table based on purchase order detail lines that are open or held, or received into suspense or into a pending putaway warehouse location. |
RIUPLD |
PFR0084 |
|
As needed |
Retail Integration Item Upload Submits the retail integration item upload process. Once completed, if the Create Generic Item Download Trigger Records (I15) system control value is selected, the system submits the secondary job RISECU to create item download triggers. See Working with Retail Integration Item Upload (RIIU) and RI Item Upload Process. |
VNDUPLD |
PFR0086 |
|
As needed |
Vendor Upload Submits the vendor upload process. |
Order Entry (O/E) Periodic Functions
The table below lists the periodic functions associated with Order Entry processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Function | Program or Class | Parameter | Schedule | Description |
---|---|---|---|---|
PURGEPR |
PFR0112 |
The number of days from the promotion end date that a completed promotion will be eligible for purge. Example: promo1 end date = 1/15/12 promo2 end date = 3/18/12 purge days = 15 If you run this periodic function on 3/20/12, the system deletes any promotion with an end date less than 3/5/12. In this example, the system deletes promo1 and retains promo2. |
As needed |
Purge Promotions When you run this periodic function, the system uses the current date - the purge days parameter to determine the promotions to purge. Any promotions whose end date is equal to or earlier than the calculated purge date will be purged. If the Parameter is set to 0, the system does not purge any promotions. The system purges promotions from the following tables:
|
SUMVIA |
OER1024 |
|
Daily |
Update Ship Via/Item Summary Runs a batch job to collect information on the current number of available order lines for each item/ship via combination in your company and populates the Ship Via Item Summary Header (OESVIH) table and Ship Via Item Summary Detail (OESVID) table. You can review the total open orders, shippable units, and oldest arrival dates for each item with a particular ship via assigned using the Ship Via/Item Inquiry (SVII) menu option. |