Completed Order Private Data Purge
The Completed Order Private Data Purge job in the Data Hygiene folder anonymizes customer data on sales orders that closed (fulfilled, canceled, unfulfillable, completed) and purchase orders that have been closed (shipped, complete, or canceled) and that are older than the number of days specified in the Days Old field.
If the same external order number is assigned to multiple sales or purchase orders, each purchase order is purged only if if is closed and is older than the retention days. For example, order number 12345 is assigned to two purchase orders created on February 1 and another was created on February 6. If the current date is February 15 and the retention days is set to 10, then the third purchase order cannot yet be purged.
The order’s age is calculated based on the CREATE_TIMESTAMP from the XOM_ORDER table or the CREATED_DATE from the PO_HEADER table. This is the date and time when Order Broker created the sales order or purchase order, which might be different from when the order was created in the originating system.
About anonymization: When the customer data is anonymized, all information is replaced with asterisks. Anonymized data cannot be recovered. Data that is anonymized includes sold-to and ship-to customer names, address, email addresses, and phone numbers for sales orders and purchase orders. Even if a field, such as one of the address lines, did not previously contain data, the purge populates the field with asterisks. See Anonymizing Data for a discussion.
A Transaction Note is written for each order line: Private Data Anonymized.
Scheduling the Completed Order Data Purge
• Select the Day of Week when the job should run.
• Enter the Time when the job should run in 24-hour format (HH:MM).
• Enter the Days Old an order or purchase order must be to be eligible for anonymization.
• Select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Orders across all organizations are anonymized.
Completed Order Data Purge Fields
• Schedule Interval: Set to Weekly. Display-only.
• Time
• Days Old: The number of days old a completed order must be to be eligible for purge.
• Last Run
• Next Run
For more information: See the Operations Guide for information on web service requests that support inquiring on private data and requesting to anonymize it.
The Daily Clean Up job in the Daily Hygiene folder clears outdated information, including:
• Pack slip records generated through the Vendor Portal, after the number of days specified in the Pack Slip Files field under Retention Settings at the Tenant-Admin screen.
• Reports, after the number of days specified in the Report Files field under Retention Settings at the Tenant-Admin screen.
• Pack slip records generated through Store Connect, after one day.
• Shipping label records generated for integrated shipping with ADSI, in either the Vendor Portal or Store Connect, after one day.
• Email notification records, after three days.
•
• Records in the RICS_LOG table of messages between Order Broker and Oracle Retail Integration Cloud Service (RICS), based on the number of days specified in the RICS Log History field under Retention Settings at the Tenant-Admin screen. See Order Fulfillment through RICS Integration for background.
RICS log records whose Retry Status is Failed are not eligible to be purged.
• Sales Extract Job History records, as displayed at the View Sales Order Data Extract Job History screen, which are older than the Extract Log History setting at the Tenant - Admin screen.
• Shopping logic trace records shopping logic trace records for closed, completed, canceled, and unfulfillable orders, when the records are older than the number of days specified in the Trace Log History field under Retention Settings at the Tenant-Admin screen, if shopping logic tracing is enabled; see Trace Shopping Log for background.
The Daily Clean Up job does not clear log files. It is the responsibility of the retailer to clear these files. Also, the job does not clear product import error files.
Scheduling the Daily Clean Up Job
• Enter the Time in 24-hour format (HH:MM) when the job should run.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
• Schedule Interval: Set to Daily. Display-only.
• Time
• Last Run
• Next Run
For more information: See the Tenant - Admin screen for information on Retention Settings fields.
Purpose: Use the Fulfilled Inventory Export to generate a pipe-delimited file of recent order fulfillments, so the inventory system of record can use this information to update its own inventory based on activity in Order Broker.
Export updates: The export program:
• identifies each order line within the system since the last time the export was run, based on the export update date and time in the xom_status_history table:
• delivery, pickup, and ship-to-store orders: the order line assigned to the location for fulfillment has gone into fulfilled status
• retail pickup orders: the order line assigned to the location for sourcing (transferring or shipping the item to the originating location) has gone into intransit status
• for each order line whose fulfilled or intransit quantity was included in the export, updates the export update date and time in the xom_status_history table
• for each product location included in the export:
• if the Track Fulfilled Quantity setting is Reset During Inventory Export, sets the Fulfilled Quantity to 0
• decreases the Available Quantity by the total quantity of fulfilled order lines included in the export, based on the quantity from the xom_status_history table
• updates the Last Updated Date for the product location
• generates the export file:
• File Storage API for Imports and Exports: The program creates the export record in the FILE_STORAGE table. The CONTAINER setting for the record is OROB-EXPORT. You can use the File Storage API to download export file records from the FILE_STORAGE table.
• Secure FTP for imports and exports: The program creates the file in the Export Files path specified in the Data Folder Settings section of the Tenant - Admin screen.
• generates the export file, creating the export record in the FILE_STORAGE table. The CONTAINER setting for the record is OROB-EXPORT. You can use the File Storage API to download export file records from the FILE_STORAGE table. See File Storage API for Imports and Exports for details.
For more information: See the Fulfilled Inventory Export File.
Fulfilled quantity used in availability calculation: Both the Reserved Quantity and the Fulfilled Quantity are subtracted from the product location’s Available Quantity when calculating the Available to Promise quantity. See Calculating the Available to Promise Quantity for an overview.
Typically, you would set the Track Fulfilled Quantity field at the System screen to Reset During Inventory Export. See that field.
Note: The Fulfilled Quantity is not tracked for ship-to-store orders; however, they are included in the export file for the location where they were fulfilled (picked up by the customer).
Fulfilled Inventory Export File
• File format: The file is pipe-delimited (|).
• File location: If you use secure FTP, in a folder on the Order Broker server, based on the Export Files path specified in the Data Folder Settings section of the Tenant - Admin screen. Otherwise, if you use File Storage API for Imports and Exports, in the FILE_STORAGE table.
• File naming: Named FULFILLED_QUANTITY_EXTRACT_SYSCD_150831_165819.csv, where SYSCD is the code for the system, and 150831_165819 the date (August 31, 2015) and time when the file was created, in the retailer’s time.
File contents:
• Location code: The code identifying the location that shipped the delivery order, where the ship-to-store or pickup order was picked up, or that shipped or transferred the retail pickup order.
• Order type: Either DELIVERY, PICKUP, SHIPTOSTORE, or RETAILPICKUP.
• Order number: The number or code identifying the order in the originating system.
• System product code: The number or code identifying the item in the fulfilling system.
• Quantity fulfilled: The quantity of the item shipped, picked up, or in transit.
• Unit price: The unit price of the item on the order.
• Date and time: The date and time when the item was shipped or picked up. YYYY-MM-DDTHH:MM:SS:XXX format, where XXX is milliseconds (for example, 2019-11-15T16:15:34.710).
Scheduling the Fulfilled Inventory Export
• Click the plus sign next to the Fulfilled Inventory Export job in the left-hand panel to display a list of existing organizations.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
• Click the organization whose fulfilled inventory data should be extracted. When you select an organization, the systems within the organization are displayed.
• When you select an organization, the Fulfilled Inventory Export Fields are displayed to the right.
• Select one or more Days of Week when the job should run.
• Use the Time field to enter each time when the job should run, in 24-hour format (HH:MM). If entering multiple times, separate each with a comma and no spaces.
• Optionally, select Run Now to run the job immediately.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Fulfilled Inventory Export Fields
• system
• Schedule Interval: Set to Day(s) of Week. Display-only.
• Time
• Run Now
Job Summary
• Last Run
• Next Run
Probable quantity update and export: If the Aggregate by Product flag is unselected, the probable quantity update and export:
• subtracts the current reserved quantity for updated product locations.
• subtracts the fulfilled quantity for product locations, populated if it has not been cleared by the Fulfilled Inventory Export.
• updates the probable quantity field, if necessary, in the product location table in Order Broker, as well as the probable updated date. See Probable Quantity, below, for a discussion.
• creates a pipe-delimited export file for all product locations in the organization whose probable quantities were updated since the last time the export ran for the system running the update and export, provided the Probable Qty Export flag is selected at the Inventory tab of the System screen.
Aggregate by product? Otherwise, if the Aggregate by Product flag is selected, the update and export:
• sums the quantities for each product across product locations, regardless of whether there has been any activity since the last export
• creates a pipe-delimited export file containing the products and totals. In this situation, the file does not include the location code.
No other uses of probable quantity: Order Broker does not use the probable quantity field in any calculation, return it in any web service, or display it on any screen. Its only use is to be available for in the probable quantity export.
Which product locations are included in the export file? If the Aggregate by Product flag is unselected, the export file includes product locations that:
• are part of a system that has the Probable Qty Export flag selected.
• has been updated since the last time the export file was generated for the requesting system.
If the Aggregate by Product flag is selected, the export file includes products that are part of a system that has the Probable Qty Export flag selected.
Note: This information is available for an external system, such as your ecommerce site.
Job notifications: If the Event Notifications settings are configured at the Event Logging screen, a job notification message is generated each time the export job runs. See Event Notifications settings and the Job Notification Messages appendix of the Operations Guide for more information.
Typical probable quantity export usage: An example of how you might use the probable quantity export would be an ecommerce system that requires an estimate of availability for display at the ecommerce site:
• System A is your ecommerce system. For this system:
• the Probable Qty Export flag is not selected, because the system does not require its own product locations in the export file
• at the probable quantity entries at the Schedule Jobs screen, the Enabled flag is selected, a schedule is defined, and the Apply Probable Qty Rule flag is selected
• Systems B and C are additional systems in your organization that can fulfill orders. For these systems, the Probable Qty Export flag is selected, because updated inventory should be included in the probable quantity export file.
• When the probable quantity export runs for system A, it includes all product locations in systems B and C that have been updated since the last probable quantity export for system A.
• The probable quantity specified in the export file may be the same as the available to promise quantity, based on the conditions described under Probable Quantity, below. Since the Apply Probable Qty Rule flag is selected for system A, the program applies assigned rules for product locations included in the export.
Note: The Default Unfulfillable Location is not included in the probable quantity export.
See below for more details.
Usage: If the Apply Probable Qty Rule flag is selected, the probable quantity export program updates the probable_qty and the probable_updated fields in the product location table. The probable_qty is not used in any additional process or displayed on any screen in Order Broker; however, it is included in the probable quantity export so that a remote system, such as your ecommerce system, can display a more accurate picture of an item’s availability, without the need for interactive inquiries.
However, if the Apply Probable Qty Rule flag is unselected, the system uses the available to promise quantity as the probable quantity.
Which product locations evaluated? If the Apply Probable Qty Rule flag is selected, when the probable quantity export program runs for a system, it evaluates, and potentially updates, the probable_qty for all product locations that are flagged as eligible to be included in the export file (based on a probable_updated field set to NULL). The product location is flagged as eligible by setting this field set to NULL when:
• a product import, including the incremental inventory import, updates the product location
• you update a product location at the Edit Product Location screen
• the product location is updated through an interactive inventory update (for example, triggered by a submit order request or a locate items search)
• you assign a probable quantity rule, modify an assigned probable quantity rule, or delete a probable quantity rule assignment for the location type that includes the location through the Probable Quantity Location screen, even if the product does not qualify for that particular rule
When the probable quantity export program evaluates and resets the probable_qty based on whether the Apply Probable Qty Rule flag is selected, it updates the probable_updated field with the current date and time, indicating that the product location is not currently eligible for probable quantity update until the next activity that updates the probable_updated field.
Backorders? For the purposes of calculating the probable quantity for export, a negative available quantity is treated the same way as an available quantity of zero.
Calculation details: To determine the probable_qty for a product location, the program uses the following rules:
1. The calculation starts with the current on-hand quantity (the available_qty in the product_location table).
2. The update calculates the available to promise quantity by:
• Subtracting the reserved quantity, if any, based on the Reserved Statuses at the Reservation tab at the System screen.
• Subtracting the fulfilled quantity, if any, for recently fulfilled orders in the store location that have not been reset to 0 through the Fulfilled Inventory Export.
3. If:
• The Apply Probable Qty Rule flag is unselected for the system, or if no probable quantity rules apply to the product location based on the location type, the probable_qty = the available to promise quantity; however, if the available to promise quantity is less than zero, then the probable_qty is set to zero.
• Otherwise, if the Apply Probable Qty Rule flag is selected for the system, and there are any probable quantity rules that apply to the product location based on the location type, then the probable_qty is calculated by applying the probable quantity rule to the available to promise quantity. If the result is less than zero, then the probable_qty is set to zero.
About probable quantity rules: Probable quantity rules can add or subtract a quantity, increase or decrease by a percentage, or set the probable_qty to a specified quantity.
Examples:
If the available to promise quantity (Available quantity - reserved quantity) = 10 and...
• Probable quantity rule is Available + 5, then the probable_qty is 15.
• Probable quantity rule is Available - 15, then probable_qty is 0.
• Probable quantity rule is 5, then probable_qty is 5.
• Probable quantity rule is Available - 10%, then probable_qty is 9.
If the available to promise quantity is negative: The program still applies the probable quantity rule if the available to promise quantity is negative. For example, if the available to promise quantity is -3, but the probable quantity rule indicates to add 10, then the probable_qty is 7. However, if the result after applying the probable quantity rule is still negative, then the probable_qty is 0.
Probable quantity rules that apply a percentage increase or decrease do not affect the probable_qty if the available to promise quantity is less than 0. The result is still negative, so the probable_qty is still 0. For example, if the available to promise quantity is -5, and the rule increases the quantity by 25%, the result is still less than 0, so the probable quantity is 0.
Evaluating Probable Quantity Rules
You can set up probable quantity rules based on:
• matching system product code, or
• matching master style code
• matching department, class, or category
• no required matching
Also, you can assign probable quantity rules at the location type level or at the location level.
If multiple probable quantity rules could apply to the same product location, the program applies only the last possible rule as follows to calculate the probable_qty:
First, evaluate rules assigned to the location type:
• 1: no matching required
• 5: matching master style
• 6: matching system product
Next, evaluate rules assigned to the location, using the same sequence listed above; however, rules assigned at the location level might not apply if there was no additional activity, such as a product import, that flagged the product location as eligible for probable quantity calculation.
Example: For a particular product, rules have been assigned to:
• the location type, specifying a matching master style
• the location, without any matching required
• the location, specifying a matching system product
Result: The rule that is assigned at the location level and specifies a matching system product is applied to the product location and updates the probable_qty.
Important: Rules assigned at the location level are eligible to be applied only if another activity, such as an inventory import, updates the product location.
For accurate calculation of the probable_qty, do not apply multiple probable quantity rules at the same level and with the same criteria.
Date and time updated: When it updates the probable_qty, the program also updates the probable_updated date and time in the product location table. This update occurs regardless of whether the probable_qty was updated solely because of a change in probability rule assignment.
What if the probable_qty doesn’t change? If the probable_qty does not change as a result of the probable quantity update program, the program does not update the probable_updated field unless the probable_updated field was set to NULL because of one of the activities listed above.
Example: If a user advances to the Edit Product Location screen in Order Broker and then clicks Save, this changes the probable_qty and probable_updated date for the product location to NULL; as a result, the update program includes this product location in its updates, and the product location is then eligible to be included in the extract file, even if there has not been any actual inventory change or change to the resulting probable_qty.
Note: Even if the probable_qty for a product location is more than zero, this does not indicate if the location supports a particular transaction type, such as pickup.
Probable Quantity Export File Layout and Contents
When the probable quantity export runs:
• If you use File Storage API for Imports and Exports: The program creates the export record in the FILE_STORAGE table. The CONTAINER setting for the record is OROB-EXPORT. You can use the File Storage API to download export file records from the FILE_STORAGE table.
• If you use secure FTP for imports and exports: The program creates the file in the Export Files path specified in the Data Folder Settings section of the Tenant - Admin screen.
File naming: The file name is Probable_Quantity_Extract_SYS_150702_123456.txt, where SYS is the system (in all uppercase) running the export, and 150702 is the date when the file was generated, in YYMMDD format, and 123456 is the time when the file was generated, in HHMMSS format, and in the retailer’s time.
File contents:
• SYSTEM_CD: The code identifying the system associated with the product.
• PRODUCT_CD: The system product code for the item in the system generating the extract. The process trims any blank, trailing spaces.
• LOCATION_CD: The code identifying the location. This field is not included when the Aggregate by Product flag is selected. In this case, the following quantities are totals across all eligible product locations, and all products are included in the export file regardless of whether there has been any activity since the last export.
• AVAILABLE_QTY: The current on-hand quantity of the product, without factoring in any reserved quantity or rules. From the available_qty in the product_location table, or the total available quantity across all product locations if the Aggregate by Product flag is selected.
• RESERVED_QTY: The current quantity reserved for the product, based on the selected Reserved Statuses for the system. From the reserved_amt in the product_location table, or the total reserved quantity across all product locations if the Aggregate by Product flag is selected.
• PROBABLE_QTY: See Probable Quantity.
Scheduling the Probable Quantity Export Job
• Click the plus sign next to the Probable Quantity Export job in the left-hand panel to display a list of existing organizations.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
• Click the organization whose probable quantity data should be exported. When you select an organization, the systems within the organization are displayed.
• When you select an organization, the Probable Quantity Export Fields are displayed to the right.
• Enter the Time in HH:MM format (24-hour clock) when the job should run.
• Use the Days of Week to select each day when the export job should run.
• Use the Time field to enter each time when the job should run, in 24-hour format (HH:MM). If entering multiple times, separate each with a comma and no spaces.
• Optionally, select the Apply Probable Qty Rule flag.
• Optionally, select the Aggregate by Product flag.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Probable Quantity Export Fields
• Schedule Interval: Set to Day(s) of Week. Display-only.
• Time
Job Summary
• Last Run
• Next Run
For more information: See the Tenant - Admin screen for information on Retention Settings fields.
You can use the sales order data extract to export data related to sales orders and purchase orders. The data that you can extract includes:
• sold-to and ship-to customers
• customization details
• items ordered
• status history
The extract writes the information to pipe-delimited files, which are bundled into a compressed zip file. See File Storage API for Imports and Exports for more information on obtaining export files, and see Sales Order Data Extract Files for information on the naming and contents of these files.
Extract by organization: You need to schedule this job separately for each organization whose order data should be extracted. Click the plus sign next to the job name in the left-hand panel to display a list of existing organizations.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
Scheduling the Sales Order Data Extract
• Click the plus sign next to the Sales Order Data Extract job in the left-hand panel to display a list of existing organizations.
• Click the organization whose sales data should be extracted. When you select an organization, the Sales Order Data Extract Fields are displayed to the right.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
• Use the Schedule Interval field to select:
• Day(s) of Week to have the extract run at a regular time on one or more days of the week to periodically extract all orders with any activity since the last extract, or,
• Initial Load to extract:
• All order data, if you do not specify an Extract Orders with Activity From and Activity To date, or
• Data for orders that have had activity during the Activity From and Activity To dates.
Note: The job fails if the total number of orders to extract exceeds 500,000. If this occurs, you can use the Initial Load option with the Activity From and Activity To dates to complete the extract of historical orders in increments until the extract is up to date. For example, if there is a total of 750,000 orders from the past year, you might use the Initial Load option with the Activity From and Activity To dates to break the extract into two six-month increments, each for less than the 500,000-order limit.
• If you selected a Schedule interval of Day(s) of the Week, select one or more Days of Week when the job should run.
• Enter the Time when the job should run.
• If you selected Initial Load as the Schedule Interval, optionally enter the Extract Orders with Activity From and To, as described above.
• Optionally, select Include Private Data to have the extract files include personal data, such as name, address, and email address; otherwise, leave this flag unselected to have personal data for customers replaced with asterisks or with text such as ***** Data Privacy Blocked *****.
Note: User names are not replaced in the extract files, regardless of the setting of the Include Private Data flag.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Sales Order Data Extract Fields
• Organization: The code and name of the organization selected in the left-hand panel. Display-only.
• Schedule Interval:
• Day(s) of Week to have the extract run at a regular time on one or more days of the week to periodically extract all orders with any activity since the last extract, or,
• Initial Load to extract:
• All order data, if you do not specify an Activity From and Activity To date, or
• Data for orders that have had activity during the Activity From and Activity To dates.
See Scheduling the Sales Order Data Extract, above, for a discussion.
• Day(s) of Week: Use these fields to select one or more Day(s) of Week when the job should run.
• Time: The time of day, in HH:MM format (24-hour clock) when the job runs. Required, regardless of the selected Schedule Interval.
• Extract Orders with Activity From and To: Optionally, enter a From and To date to include order data for orders with activity during this date range. These fields are enterable only when the Schedule Interval is set to Initial Load.
• Include Private Data: Select this flag to include personal data, such as names, addresses, and email addresses in the data extract files; otherwise, leave this flag unselected to have this information anonymized. See anonymized in the glossary for more information.
Job Summary
• Last Run
• Next Run
For more information: See Sales Order Data Extract Files for information on the content of the extract files.
Identity Cloud User Synchronization
Note: This option is not currently implemented.
Overview: The incremental inventory update uses the following process:
• If you use File Storage API for Imports and Exports: The program checks for an incremental inventory record in the FILE_STORAGE table.
• If you use secure FTP for imports and exports: The program checks for any incremental inventory pipe-delimited files in the Product Import Files folder specified in the Data Folder Settings area of the Tenant- Admin screen.
Identifying the incremental inventory file: The file in the folder or specified in the FILE_STORAGE table needs to be named INCREMENTAL_INVENTORY_SYS_xxx.TXT, where SYS is the system code and xxx is a user-defined alphanumeric sequence number. The sequence number indicates to the program the order in which to process multiple import files for the system. For example, if the files are named INCREMENTAL_INVENTORY_ABC_AB1.TXT and INCREMENTAL_INVENTORY_ABC_AB.TXT, the program first processes the file with the AB1 sequence number, and then the file with the AB2 sequence number. If there are records for the same product location in both import files, the record from the second file overwrites the first.
You cannot submit an import if another import process, including the product import, is already running in your organization.
Job Batch Size: The Job Batch Size controls the number of records to process in each batch.
• The program creates or updates the product location records in the Order Broker database.
• If there are any errors that prevent the program from processing a record in one of the files:
• If you use File Storage API for Imports and Exports: The program creates an error record in the FILE_STORAGE table. The CONTAINER setting for the record is OROB-ERRORS. You can use the File Storage API to download export file records from the FILE_STORAGE table.
• If you use secure FTP for imports and exports: The program creates a copy of the file, including just the records in error, in the error folder below the Product Import Files folder, naming the file INCREMENTAL_INVENTORY_SYS_xxx.TXT.20170703.105108.err, where SYS is the system code, 20170703 is the date in YYMMDD format, and 105108 is the time in HHMMSS format. Errors that result from database validation, such as data that exceeds the length of the field in the database, are not captured in the error file.
Errors that might occur include an invalid number of columns, alphabetical characters in a numeric field, or a numeric field that is null: for example, the next PO quantity is blank rather than 0 or another number.
• If the Incremental Inventory Import field at the Event Logging screen is set to Administrator, the program sends the Incremental Inventory Import Status Email to your system administrator (the Administrative Email addresses) if the incremental inventory update fails.
Records imported regardless of system: The incremental inventory update program processes all records in the pipe-delimited file or FILE_STORAGE record if they are product locations for the organization, regardless of whether they are associated with the system selected for import; however, if they are not associated with the organization, they are skipped and are not reported as errors.
Resolving a scheduling issue: If the import does not run as scheduled, you can use the Reschedule All option at the View Active Schedules screen to stop and restart the schedules for all jobs and periodic programs. For example, you might need to use this option after a server shuts down unexpectedly, or after applying an upgrade.
History: Use the Incremental Imports History to review incremental imports that have run.
Job notifications: If the Event Notifications settings are configured at the Event Logging screen, a job notification message is generated each time the import job runs. See Event Notifications settings and the Job Notification Messages appendix of the Operations Guide for more information.
Sample Incremental Inventory Import File
The pipe-delimited incremental inventory import file needs to include the following fields. The first row is the header information, which is informational only, and the following row is the product location data to update.
SYSTEM_CD|LOCATION_CD|PRODUCT_CD|AVAILABLE_QTY|NEXT_PO_QTY|NEXT_PO_DATE
6|1|PEN123|100|123|2015-08-27
Incremental Inventory File Mapping
• system_cd: The code identifying the system importing the updated inventory for the product locations into Order Broker. Alphanumeric, 10 positions. Required.
• location_cd: The code identifying the location where the product is stocked in the external system. Alphanumeric, 10 positions. Required.
• product_cd: The system product code identifying the product in the external system. The system product code might differ from the product code if the external system is not the default system for the organization. Alphanumeric, 35 positions. Required.
• available_qty: The current quantity of the product available to sell in this location as of the time of the import process. A negative quantity, preceded by a minus sign (-), indicates that the item is backordered. Numeric, 6 positions. Required, but can be set to 0.
• next_po_qty: The quantity ordered for this product on the next purchase order for this location. Numeric, 6 positions. Required, but can be set to 0.
• next_po_date: The next date when a purchase order for this product is expected for delivery in this location. Datetime format; if set to YYYY-MM-DD, a time of 12:00:00 AM is appended. Can be empty, even if there is a next_po_qty.
Incremental Inventory Import Status Email
Order Broker sends this email to the Administrative Email address specified at the Event Logging screen if the incremental inventory program was unable to import the pipe-delimited file and if the Email Notifications flag for the Incremental Inventory Import option is set to Administrator.
The language used for the email is based on the Language specified for the organization, and the formatting of dates, times, and numbers is also based on the organization-level settings. See the Edit Organization screen for more information.
The Uploaded By entry always indicates a user of SYSTEM.
****ATTENTION****
Your Incremental Inventory Import has failed.
System Code 6
Date/Time File Failed 2016-11-02 13:01:06.257
Uploaded By SYSTEM
Please do not respond to this message.
--Order Broker
Scheduling the Incremental Inventory Import Job
• Click the plus sign next to the Incremental Inventory Import job in the left-hand panel to display a list of existing organizations.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
• Click the organization where incremental inventory data should be imported. When you select an organization, the systems within the organization are displayed.
• When you select a system, the Incremental Inventory Import Fields are displayed to the right.
• Enter the Time in HH:MM format (24-hour clock) when the job should run.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Incremental Inventory Import Fields
• Schedule Interval: Set to Daily. Display-only.
• Time: The time of day, in HH:MM format (24-hour clock) when the job runs. Required.
Job Summary
• Last Run
• Next Run
For more information: See the Tenant - Admin screen for information on Retention Settings fields.
Process overview: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database for an overview.
Merchandising Cloud Services applications (RMFCS) imports through the MOMZIP file: Importing products and barcodes from Merchandising Cloud Services applications (RMFCS) uses a different process than the one described under Import Process Overview (Other than RMFCS File Upload or OCDS). Importing from RMFCS takes place if the RMS Location is specified at this screen. See Importing Product or Product Barcode Data from Merchandising Cloud Services Applications (RMFCS) through a MOMZIP File Upload for background.
Omnichannel Cloud Data Service (OCDS) imports: Importing store and warehouse locations, products, and inventory from OCDS also uses a different process from the one described under Import Process Overview (Other than RMFCS File Upload or OCDS). If you have configured the OCDS Integration tab of the System screen to enable any of the available imports from OCDS, then submitting an import at the System Import Schedule screen triggers the request(s) to OCDS for data, rather than any of the other import options described here. Also, the fields described under OCDS Integration are used to control the import from OCDS. See OCDS Imports for background and more information.
Import products from the default system first to prevent import errors: Unless you are Importing Product or Product Barcode Data from Merchandising Cloud Services Applications (RMFCS) through a MOMZIP File Upload, it is important to schedule the product import for the default system before the other systems in the organization. Order Broker requires that the product exist in the default system before you can create the system products or product locations for the other systems. However, if you import products from Merchandising Cloud Services applications (RMFCS), each product has the same product and system product code across systems, and the product code is created automatically if it does not already exist in the default system; see Importing Product or Product Barcode Data from Merchandising Cloud Services Applications (RMFCS) through a MOMZIP File Upload for background.
Important: Oracle recommends that you run this job daily at a time when demands on the system are limited, and when it does not interfere with the database backup.
Additional consideration when scheduling import processes for systems:
• Oracle recommends that you allow about 30 minutes between scheduled import processes to help make sure that each process completes before the next one begins.
• If you use File Storage API for Imports and Exports, a copy of each import file, including the MOMZIP file if you import from RMFCS, must be uploaded to the OROB-IMPORTS container of the FILE_STORAGE table through a putFile request message.
• If you use secure FTP in a multi-server environment, a copy of each import file, including the MOMZIP file if you import from RMFCS, must be in the Product Import Files folder specified at the Tenant-Admin screen on each server in order for the import to take place. This must be a shared folder. You need to make sure that the files are propagated on all servers, or are in a shared folder that is available to all servers.
Note: Each import is optional. For example, you can run the import for products and product locations without also importing locations or UPC barcodes. When the import runs, it includes any import files it finds for the system in the OROB-IMPORTS container or the Product Import Files folder specified in the Data Folder Settings area of the Tenant-Admin screen.
File cleanup: It is the responsibility of the retailer to clear log files and product import error files.
For more information: See:
• Process overview: Importing Items/Products, Inventory, Barcodes, and Locations into the Database for background on the import process, including File Storage API for Imports and Exports.
• OCDS imports: OCDS Imports.
• RMFCS imports: Importing Product or Product Barcode Data from Merchandising Cloud Services Applications (RMFCS) through a MOMZIP File Upload.
• Additional supported imports:
• Location imports: Importing Locations through File Upload or File Storage API and Location Import Errors Report.
• Product and system product imports: Importing Products and System Products through File Upload or File Storage API and Product Import Errors Report.
• Product location imports: Importing Product Locations through File Upload or File Storage API.
• Product UPC barcode imports: Importing UPC Barcodes through File Upload or File Storage API and Product Barcode Import Errors Report.
When the import process is complete, Order Broker sends an email to the email address(es) specified at the Administrative email field at the Event Logging screen if the Email Notifications flag for the Location Product Import option is set to Administrator.
The language used for the email is based on the Language specified for the organization, and the formatting of dates, times, and numbers is also based on the organization-level settings. See the Edit Organization screen for more information.
Sample email contents:
***ATTENTION****
Your Product Import Process has Failed.
System Code store
Import ID 201
Date/Time File Finished
2018-01-22 09:37:53.762
Uploaded By example
# of Product Records 850
# of Product Records In Error 12
# of Inventory Records 1,445
# of Inventory Records In Error 14
# of Location Records 1,300
# of Location Records In Error 14
# of Upc Records 0
# of Upc Records in Error 0
Please do not respond to this message.
--Order Broker
Information in this email includes:
• Success or failure: The email indicates that the process failed if any product, product location, location, or UPC records failed to update; otherwise, it indicates a success.
• System code: the system scheduled for import, or the selected system when you ran the import on demand.
• Import ID: A unique ID number assigned by Order Broker to identify an import process. This number is displayed at the Product Imports History screen and listed on the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report.
• Uploaded By: the user ID of the person who scheduled the import process, or ran it on demand.
• # of Product Records: The total number of product records that were successfully created or updated as a result of the import process.
• # of Product Records in Error: The total number of product import records that were in error for this import process.
• # of Product Location Records: The total number of product location records that were successfully created or updated as a result of this import process.
• # of Product Location Records in Error: The total number of product location import records that were in error for this import process.
• # of Location Records: The total number of location records that were successfully created or updated as a result of this import process.
• # of Location Records in Error: The total number of location import records that were in error for this import process.
• # of Upc Records: The total number of product UPC barcodes that were successfully created or updated as a result of this import process.
• # of Upc Records In Error: The total number of UPC barcodes that were in error for this import process.
Always generated? If the Email Notifications flag for the Location Product Import option at the Event Logging screen is set to Administrator, Order Broker generates this email regardless of whether the import process ran because you scheduled it, or you ran it on demand.
Negative number? A negative number of records generally indicates that an error occurred. Check the server log for more information.
If number of records and number of records in error are both 0: The email lists a number of records and a number of records in error as 0 if there was no import file to process. This situation might occur if:
• you did not import a particular type of record; for example, there were no product barcodes to import; or you used the OCDS Imports process, which doesn’t import barcodes; or
• the name of an import file did not match the naming convention; for example, a product barcode file was named PRODUCT_BARCODE.TXT (no system specified) or PRODUCT_BARCODE_SYS.txt (the txt extension was lowercase).
• In a multi-server environment, the import file was not propagated to all servers.
In any of these cases, the email indicates that the import was successful.
For more information: See the Product Imports History screen and the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report for more troubleshooting information related to these imports.
Note: Some errors that can occur from the data in a flat import file are not written to the related import database table, so in that case the error is noted only in the error file and not on the related report; for example: an invalid number of columns in the flat file or an empty file.
advance to Product Import options
• Click the plus sign next to the Product Import job in the left-hand panel to display a list of existing organizations.
Note: The list of organizations is available only if Use Routing Engine is selected at the Tenant - Admin screen.
• Click the organization where data should be imported. When you select an organization, the systems within the organization are displayed.
• When you select a system, the Scheduling the Product Import Job are displayed to the right.
schedule the import for an integrated system
• When you select an organization, the Scheduling the Product Import Job are displayed to the right.
• Select one or more Days of Week when the job should run.
• Use the Time field to enter the time when the job should run, in 24-hour format (HH:MM). Entry of more than one time is not supported.
• Optionally, change the Days to Keep Errors to any number from 1 to 99.
• Specify the RMS Location if you are using the import described under Importing Product or Product Barcode Data from Merchandising Cloud Services Applications (RMFCS) through a MOMZIP File Upload.
• If you are running the OCDS Imports, complete the additional OCDS Options if OCDS Configured is set to Yes.
• Select Schedule Enabled.
• Optionally, select Run Now to run the job immediately.
• Select Save.
• Select Cancel to exit the screen.
Reviewing results: You can review the import process at the Product Imports History screen, and you can review errors through the Product Barcode Import Errors Report, Product Import Errors Report, and Location Import Errors Report.
• Run Now
• Schedule Interval: Set to Day(s) of Week. Display-only.
• Time: The time of day, in HH:MM format (24-hour clock) when the job runs. Required.
OCDS Options (If OCDS is configured):
• Time
Job Summary
• Last Run
• Next Run
For more information: See the Tenant - Admin screen for information on Retention Settings fields.
Auto Cancel Unclaimed Pickup Orders
This job cancels unclaimed pickup or ship-for-pickup orders based on the settings of the Auto Cancel Days of Unclaimed Pickup Orders and Auto Cancel Days of Unclaimed Ship For Pickup Orders at the Preferences screen. This job uses a Schedule Interval of Daily, and runs at the specified Time.
Scheduling the Auto Cancel Unclaimed Pickup Orders Job
• Enter the Time in HH:MM format (24-hour clock) when the job should run.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Auto Cancel Unclaimed Pickup Order Fields
• Schedule Interval: Set to Daily. Display-only.
• Time: The time of day, in HH:MM format (24-hour clock) when the job runs. Required.
• Last Run
• Next Run
For more information: See Auto-Cancel Unclaimed Orders for a discussion.
This job generates email notifications to store locations, vendors, customers, retailers, or systems operations staff based on the unprocessed records that are currently in the EMAIL_NOTIFICATION table.
Scheduling the Email Notifications Job
• Use the Minutes field to enter the number of minutes to wait before generating any emails to store locations, vendors, customers, retailers, or systems operations staff.
• Optionally, select Schedule Enabled.
• Select Save.
• Select Cancel to exit the screen.
Auto Cancel Unclaimed Pickup Order Fields
• Schedule Interval: Set to Minutes. Display-only.
• Minutes: Enter the number of minutes to wait before generating any emails to store locations, vendors, customers, retailers, or systems operations staff.
• Last Run
• Next Run