Updating the Inventory Count for Emory
Purpose: Use this function to create a file with updated item inventory counts for periodic transmission to Emory Worldwide. Emory needs this information so that when they perform remote Order Entry they can provide accurate item availability information to your customers.
There are three steps to the process of providing Emory with accurate item inventory counts:
1. Run PO layering to capture any new information about expected delivery dates or quantities due for items being ordered.
2. Generate the inventory count update to capture any new or changed item information, such as status or quantities.
3. Transmit the inventory count file to Emory regularly.
You can define the Emory inventory count update to run as a periodic function or execute the update on-demand.
In this topic:
• Defining the Emory Inventory Count Update as a Periodic Function
Defining the Emory Inventory Count Update as a Periodic Function
Purpose: When you define the Emory inventory count update as a periodic function, it will run as part of a periodic process daily (or at another interval you choose). This helps you make sure Emory receives up-to-date inventory information.
The program INR0927 runs when you use this option. This program creates the file INEIC on disk in library CWMPDTA that contains all updates to item inventory.
Instructions: Follow these steps to add this program to a periodic process that runs nightly.
1. Select Working with Periodic Functions (WPER).
2. Press F6 to advance to the Create Periodic Function Screen.
3. Enter EM_INV (or any descriptive name) in the Function field, Update Emory Inventory Count in the Description field, Y in the Company parameter field, All in the Applic (Application area code) field, and INR0927 in the Program name field.
4. Select Working with Periodic Processes (WPPR).
5. Enter 7 next to the periodic process you want to add this job to, such as a daily periodic process.
6. Enter the sequence number (which specifies when you want this job to run during the periodic process) in the Seq # (Sequence number) field, type the name of the periodic function (specified in Step #3) in the Function field, and type a Y in the Select field (so that the job runs each time the periodic process runs).
On-demand: If you choose, you can also create a menu option to update the inventory count on-demand.
1. Select Setting Up Menu Options (WOPT).
2. Press F6 to create an option.
3. Enter UEIC in the Option field, Update Emory Inventory Count in the Description field, P (program) in the Type field, INR0927 in the Program name field, N in the Authority parameter field, INV in the Appl area field, and All in the Appl group field.
Purpose: The PO Layering program updates the expected delivery dates for items ordered on purchase orders if the quantity due or date expected has changed.
You must run PO Layering before you generate the Emory Inventory Count file to ensure that the expected delivery dates are accurate.
PO layering is the method by which expected item deliveries are matched to backorders, based on order date. The oldest orders on the system receive stock before new orders.
Selecting this option: You can run PO layering during a daily periodic process or on-demand, by advancing to the Batch Purchase Order Layering Screen (BPOL).
You can also set up the PO Layering program as a periodic function to run before the Emory inventory count update. See Defining the Emory Inventory Count Update as a Periodic Function.
Example: |
The customer places an order for an item with an availability of 100- (the item is backordered 100 units). In Order Entry, the date 07/20/95 appears next to the order detail line. This means that a purchase order has been placed with the vendor for this item and is due to be received on this date. Although this date appears, this may not be the first time you receive this item. In fact, several other purchase orders will be received for this item, but the items are already committed to earlier orders. The system monitors the quantity due and the date due and determines which purchase order can fulfill the backorder. |
Field |
Description |
Company |
A code that identifies your company, which is a single, isolated set of files and data. A company is an organization of financial information, inventory, and customers that is completely separate from another company. Company codes are defined in and validated against the Company file; see Installation Setting Up Companies (WCMP). Numeric, 3 positions. |
SKU |
A SKU is a code that identifies the unique style of an item, such as its color or size. Alphanumeric, 14 positions. |
Item |
A code for a unit of inventory. Item codes are defined in and validated against the Item file. Alphanumeric, 12 positions. |
Offer |
A catalog, space or television advertisement from which you accept orders. Offer codes are defined in and validated against the Offer file; see Marketing Working with Offers (WOFR). Alphanumeric, 3 positions. |
Item description |
The description of the item, as defined in the Item file. Alphanumeric, 40 positions. |
Quantity |
The quantity currently available to sell from all shippable warehouses, from the Item/Warehouse file. The calculation is:
On-hand - Protected - Reserved - Reserve transfer - Backordered Numeric, 7 positions. |
Expected delivery date |
The date when a delivery of the item is expected to arrive from the vendor. An expected delivery date is available only if open (unreceived) purchase orders exist for the item and if the Quantity is zero. This date is included for drop ship items only if the Assign Drop Ship Expected Ship Date (I59) system control value is set to Y. See that system control value for more information. Numeric, 7 positions (CYYMMDD format). |
SKU status |
The status of the item in your inventory, as defined in the Status field in the Item file. Typical status codes are ' ' (item is active), discontinued, damaged, etc. Status codes are defined in and validated against the Item Status file; see Merchandising Working with Item Status (WIST). Alphanumeric, 1 position. |
Send |
This value indicates whether the item will be included in the next transmission of the Emory Inventory Count file. Only new items or items that have had changes to their availability, expected delivery date, or item status are included in the file. Valid values are: Y = Include the item in the Emory Inventory Count file N = Do not include the item in the Emory Inventory Count file Alphanumeric, 1 position. |
Alias |
The “dummy” item number under which the item is advertised in the offer, if you place the same item in multiple places in a single offer. You may use alias item numbers to determine whether item placement in an offer affects sales of the item. Alias item numbers are defined in and validated against the Item/Offer file; see Merchandising Assigning Items/SKUs to Offers. Note: The Inventory Count file contains a single record for every alias for an item/SKU. If the item has multiple aliases, the quantity available will be the same for each alias. As a result, the quantity available for the item will be overstated. Alphanumeric, 12 positions. |
Page number |
The page number on which the item appears in the catalog. Page number assignments are defined in and validated against the Item/Offer file. Numeric, 5 positions. |
Page letter |
The letter assignment for an item in an offer. Page letter assignments are defined in and validated against the Item/Offer file. Alphanumeric, 6 positions. |
| Orders Released from Time Hold Report | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Using the STS Sales Interface (WSTS) |
SO02_07 CWDirect 18.0.x 2018 OTN