Part C: Transaction History | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 19: Print Inventory Transaction History (PITH) |
Chapter 18: Display Inventory Transaction History (DITH)
Purpose: Inventory transaction history provides a record of all the transactions performed in your company. Transactions you enter, transactions the system performs in the background, and transactions processed through the Generic Inventory Transaction Upload are available through this menu option. You can restrict the display by scanning on different fields, including location, date, item number, SKU, and transaction codes.
How long is history available? Inventory transaction history remains on the system for at least the number of days specified in the Inventory Transaction History Retention Days (A24) system control value. When you run the Inventory Transaction History Purge function (Fast path = MITH), the system deletes any inventory transaction history older than this number of days.
Inventory transaction history outbound: If the Create Generic Item Transaction Download Trigger Records (J52) system control value is set to Y, the system creates an item transaction history trigger when a record is created in the Item Transaction History file. When the Item Transaction History Outbound job in the Working with Integration Layer Processes (IJCT) menu option processes this trigger, the system generates and sends an Item Transaction History Outbound XML Message (CWInvXActionOut) to a remote system. See Generic Item Transaction History Outbound API for more information.
In this chapter:
• Inventory Transaction History Screen (1 of 2)
• Inventory Transaction History Screen (2 of 2)
• Display Inventory Transaction History Screen
• Item Transaction Cost Detail Screen
Inventory Transaction History Screen (1 of 2)
Purpose: Use this screen to review inventory transaction or to select a particular transaction for detail review.
How to display this screen: Enter DITH in the Fast path field at the top of any menu or select Display Inventory Transaction History from a menu.
INR1344 DISPLAY Inventory Transaction History 12/23/98 9:08:31 EZK Mail Order FIFO
Whs . . . 2 QUALITY ASSURANCE WAREHOUSE C --- On Hand --- Opt Date Item CLR SIZE WDTH Loc D Rsn Qty Old New 12/01/98 AB100
Type options, press Enter. 5=Display 8=FIFO Cost History
12/01/98 AB100 * 0 500 500 12/01/98 AB100 * 0 1 1 12/01/98 AB100 * 0 1 1 12/16/98 AB100 PRIM1 A 0 1- 521 520 12/16/98 AB100 PRIM1 A 0 1- 520 519 12/16/98 AB100 PRIM1 A 0 1 519 520 12/16/98 AB100 PRIM1 A 0 1 520 521 12/16/98 AB100 PRIM1 V 0 5 521 516 12/16/98 AB100 PRIM1 V 0 5- 516 52 + F3=Exit F12=Cancel F7=View by LIFO F15=Inv Trans Sum Dsp F21=Select I/T Print Opts F24=Select company |
Field |
Description |
Whs (Warehouse) |
The number of the warehouse where the transactions took place. Numeric, 3 positions, optional. |
Date |
The date the transaction took place. Numeric, 6 positions (MMDDYY format); optional |
Item |
A code that represents a unit of inventory. Alphanumeric, 12 positions; optional. |
Clr/size/wdth (SKU codes) |
The item's unique characteristics, such as its color and size. Alphanumeric, three 4-position fields (split SKU) or one 14-position field (full SKU); optional. |
Loc |
The item's location at the time the transaction took place. The location is blank for drop shipments, non-inventory transactions, and FIFO cost changes (* transactions). Alphanumeric, 7 positions; optional. |
C/D (Code) |
The inventory transaction code. These may be system- or user-defined. The system-defined codes are: A Adjustment C Customer Return E Express Bill G Item to Item Transfer I Issue Note: The system writes an issue (I) type transaction history record when non-inventory and drop ship items go through billing if the Create Item Transaction History for Non-Inventory Items (E39) system control value is set to Y |
|
M Make up Finished Good O Reset On-Hand Quantity P Physical R Receiving T Transfer V Return to Vendor Additionally, the system creates a * transaction when you change the cost of a FIFO layer. See * = Change FIFO Cost. Note: The system does not create a * transaction history record when you update the standard or average cost of an item. See * = Change Average or Standard Cost. See Work with Inventory Transaction Codes (WITC). Alphanumeric, 1 position; optional. |
Rsn (Reason) |
A code that represents the reason why the inventory transaction was performed. See Work with Inventory Transaction Reason Codes (WIT1). Numeric, 2 positions; optional |
Qty (Quantity) |
The number of units that this transaction affected. Numeric, 8 positions; display-only. |
On-Hand Fields- |
|
Old |
The on-hand quantity for the item/location before the transaction was processed. Numeric, 6 positions; display-only. |
New |
The on-hand quantity for the item/location after the transaction was processed. Numeric, 6 positions; display-only. |
Screen Option |
Procedure |
Display details of a transaction's history |
Enter 5 next to a transaction to display its history. See Inventory Transaction History Screen (2 of 2). See Display Inventory Transaction History Screen for more information on displaying transaction history records for non-inventory and drop ship items. |
Review the cost of each unit involved in a transaction |
Enter 8 next to a transaction to advance to the Item Transaction Cost Detail Screen. Note: This screen contains information on the transaction only if you use FIFO Costing. |
Toggle the display of transaction history records between ascending and descending date order |
Press F7. |
Display inventory transaction summary |
Press F15 to advance to the First Inventory Transaction Summary Screen. |
Print inventory transaction history |
Press F21 to advance to the Print Inventory Transaction History Screen. |
Inventory Transaction History Screen (2 of 2)
Purpose: Use this screen to review detail information about an inventory transaction.
How to display this screen: From the Inventory Transaction History Screen (1 of 2), enter 5 next to a transaction; or press Enter at the Display Inventory Transaction History Screen to review transaction history detail for a non-inventory or drop ship item.
INR0055 DISPLAY Inventory Transaction History 2/13/98 15:44:30 The KL Mail Order Company
Warehouse . . . . . : 3
Item/SKU . . . . . . : RE786 MARBLE ROLLING PIN Date/Time/Seq# . . . : 2/13/98 10:04:44 1
Cde Location Quantity Old O/H New O/H Id# I T010101 1 77 76
Batch# . . . . . : 0 Transaction# . . . . . : 0 Order# . . . . . : 2427 Invoice# . . . . . . . : 225 Purchase order# : 0 Vendor Charge Back No. : Reason . . . . . : 0 License Plate Number . : 0 User . . . . . . : NSCANLON G/L account # . : 0 Cost . . . . . . : 10.0000
F3=Exit F12=Cancel |
Field |
Description |
Warehouse |
A code that represents the warehouse where the transaction was performed. Numeric, 3 positions. |
Item/SKU |
Item = A code representing a unit of inventory. Alphanumeric, 12 positions. SKU = The item's unique characteristics, such as its color and size. Alphanumeric, three 4-position fields (split SKU) or one 14-position field (full SKU). |
Date/Time/Seq# (Date, time and sequence number) |
The date and time when the transaction was performed, and a unique number to identify how many transactions for the same warehouse and item/SKU took place at this same date and time. Date: Numeric, 8 positions (MMDDYY format). Time: Numeric, 8 positions (HHMMSS format). Sequence number: Numeric, 3 positions. |
Cde (Code) |
A code that identifies types of inventory transactions. Certain codes are supplied by the system, and you can also create your own. System-supplied codes are: A Adjustment C Customer Return E Express Bill G Item to Item Transfer I Issue M Make up Finished Good |
|
O Reset On-Hand Quantity P Physical R Receiving T Transfer V Return to Vendor Note: Any RF transactions will have a code of T. The system uses a transaction code of * for changes to the cost of a FIFO layer. See * = Change FIFO Cost. Note: The system does not create a * transaction history record when you update the standard or average cost of an item. See * = Change Average or Standard Cost. See Work with Inventory Transaction Codes (WITC). Alphanumeric, 1 position. |
Location |
The warehouse location affected by the inventory transaction. For example, if you are viewing an adjustment transaction, the location where the inventory was adjusted displays. The location is blank for drop shipments, non-inventory transactions, and FIFO cost changes (* transactions). Note: Two inventory transaction history records are created for transfer transactions. One record contains the “from” location; the other contains the “to” location. Each completed RF transaction will create four records: two each for the “pull” and the “put.” See Radio Frequency. Alphanumeric, 7 positions. |
Quantity |
The number of units that this transaction affected. Numeric, 8 positions. |
Old O/H (Old on-hand quantity) |
The on-hand quantity before this transaction took place. This field is blank for non-inventory items and drop ship items, since inventory is not affected. This field is the same as the New O/H quantity for changes to FIFO cost (* transactions). Numeric, 8 positions. |
New O/H (New on-hand quantity) |
The on-hand quantity after this transaction took place. This field is blank for non-inventory items and drop ship items, since inventory is not affected. This field is the same as the Old O/H quantity for changes to FIFO cost (* transactions). Numeric, 8 positions. |
ID# |
The identification number entered when the inventory transaction was created. In the case of item-to-item transfers (transaction code = G), the system assigns this number; both "from" and "to" transactions will share the same ID number. The code NONINVISSU displays for all non-inventory and drop ship inventory transaction records. See the Item Transaction Cost Detail Screen. The code AUTOTRANS displays for all transactions processed using the Working with Automated Inventory Transactions (WAIT) menu option. The work order number displays in this field for all finished good make up type transactions (transaction code = M) that are created through the finished good work order process. See Finished Good Work Order Processing (WWOR). Alphanumeric, 10 positions. |
Batch# |
The number of the batch containing the inventory transaction. The system assigns batch numbers in both immediate and batch inventory transactions. Numeric, 7 positions. |
Transaction# |
The number of transactions within the batch. Numeric, 7 positions. |
Order # |
The number of the order affected by the inventory transaction. Numeric, 7 positions. |
Invoice # |
The number of the invoice affected by the inventory transaction. Numeric, 7 positions. |
Purchase order # |
The number of the purchase order affected by the inventory transaction. Numeric, 7 positions. |
Vendor charge (Vendor charge back number) |
A system-assigned number identifying a vendor charge back, when you return merchandise back to the vendor and receive a credit for the return. This number is sequentially assigned from the Vendor Charge Back # field in the Number Assignment file. See Accounts Payable Vendor Charge Back Overview for more information on the Vendor charge back process. Numeric, 7 positions |
Reason |
A code that represents the reason the inventory transaction was performed. Not all transactions have reason codes. See Work with Inventory Transaction Reason Codes (WIT1). Numeric, 2 positions. |
License plate number |
The number the system assigned to the case, carton or pallet to track the inventory through the warehouse if you use radio frequency (RF). License plate numbers do not appear for R (receipt) inventory transactions, when the license plate number is actually created. This number displays only if the LPN Tracking (E16) field in the System Control file is set to Y. See Radio Frequency. Numeric, 6 positions. |
User |
The User ID of the person who performed the transaction. PKMS displays if the transaction was processed through the PIX ASYNC; see WMS Inventory Transaction Setup. Alphanumeric, 10 positions. |
G/L Acct.# |
The General Ledger number to which this transaction was posted. See General Ledger Overview for more information on how the system determines which general ledger account number to use for inventory transactions. Numeric, 8 positions. |
Cost/Extended cost |
The Costing Method (A25) system control value controls how the system determines the cost of an item. Average Cost: If you use average costing, this is the unit cost of the item. The system uses the Average cost from the SKU file for both SKU’ed and non-SKU’ed items. Standard Cost: If you use standard costing, this is the unit cost of the item. The system uses the Standard cost from the SKU file for both SKUed and non-SKUed items. FIFO Cost: If you use FIFO costing, this is the extended cost of all units. In FIFO costing, a single transaction may derive unit costs from more than one FIFO cost layer, making it impossible to display a single unit cost on this screen. See Item Transaction Cost Detail Screen. Numeric, 10 positions with a four-place decimal. |
Display Inventory Transaction History Screen
Purpose: Use this screen to review information about non-inventory and drop ship transactions. Drop ship items with available inventory will not display on this screen, because they are reserved and picked from the warehouse like other items.
The system writes an issue (I) enter transaction history record when non-inventory and drop ship items go through billing if the Create Item Transaction History for Non-Inventory Items (E39) system control value is set to Y.
How to display this screen: From the Inventory Transaction History Screen (1 of 2), enter 5 next to a non-inventory transaction record.
INR0055 DISPLAY Display I/T History 2/13/98 15:48:23
Company description . . . . . . . : The KL Mail Order Company
Company . . . . . . . . . . . . . : 555
Item number . . . . . . . . . . . : JUICER
SKU . . . . . . . . . . . . . . . :
Warehouse . . . . . . . . . . . . : 0
Date . . . . . . . . . . . . . . . : 1/13/98
Time . . . . . . . . . . . . . . . : 18:06:06
* Non-Inventory/Drop Ship Issue. Press Enter to Display Additional Details.*
F3=Exit |
.
Field |
Description |
Company description |
The description of the company where the transaction was performed. Alphanumeric, 40 positions. |
Company |
The code that identifies the company where the transaction was performed. Numeric, 3 positions. |
Item number |
A code that represents a unit of inventory. Note: Drop ship items that have on-hand inventory will not appear on this screen. Alphanumeric, 12 positions. |
SKU |
The item's unique characteristics, such as its color or size. Alphanumeric, three 4-position fields (split SKU); or one 14-position field (full SKU). |
Warehouse |
A code that represents the warehouse the item is located in. Numeric, 3 positions. |
Date |
The date the transaction was performed. Numeric, 6 positions (MMDDYY format). |
Time |
The time the transaction was performed. Numeric, 6 positions (HHMMSS format). |
Displaying additional details: A message displays at the bottom of the Display Inventory Transaction History Screen giving you the option to display additional details for this record:
* Non-Inventory/Drop Ship Issue. Press Enter to Display Additional Details.*
Press F3 to exit the screen or press Enter to display additional details for this inventory transaction history record. You advance to the Inventory Transaction History Screen (2 of 2).
Item Transaction Cost Detail Screen
Purpose: Use this screen to review the costs provided by each FIFO layer toward the extended cost of an inventory transaction.
This screen displays transaction cost detail information only if you use FIFO Costing.
How to display this screen: Enter 8 next to a transaction at the Inventory Transaction History Screen (1 of 2).
INR1284 DISPLAY Item Transaction Cost Detail 12/23/98 10:18:46 EZK Mail Order
Warehouse . . . . . . . : 2 Item/SKU . . . . . . . : DE400 ACME 4000 STAPLER Date/Time/Seq# . . . . : 12/23/98 9:24:53 1
FIFO Seq # FIFO Date Qty FIFO Cost Extended Cost 1 11/10/98 5 1.0000 5.0000 1 12/23/98 5 2.0000 10.0000
F3=Exit F12=Cancel |
.
Field |
Description |
Warehouse |
The warehouse where the transaction took place. Numeric, 3 positions; display-only |
Item/SKU |
The item and SKU affected by the transaction. Item: alphanumeric, 12 positions; display-only. SKU: alphanumeric, one 14-position field (full SKU) or three 4-position fields (split SKU); display-only. |
Item description (Unlabeled field below the item/SKU) |
The description of the item. Alphanumeric, 40 positions; display-only. |
Date/time/seq # (Date/time/sequence number) |
The date and time when the transaction took place, followed by a number to identify how many transactions for the same warehouse and item/SKU took place at this same date and time. Date: numeric, 6 positions (MM/DD/YY format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. Sequence number: numeric, 7 positions; display-only |
FIFO Seq # (FIFO sequence number) |
A unique number to identify which FIFO cost layer for the warehouse, creation date, item, and SKU provided the cost for this inventory transaction. Numeric, 7 positions; display-only. |
FIFO date |
The date when the FIFO cost layer was created. Typically, FIFO layers are created through a purchase order receipt, but the system also creates them due to customer returns, adjustments, physical inventory counts, vendor charge back reversals, or when you convert to FIFO costing from another costing method. Numeric, 5 positions (MM/DD/YY format); display-only |
Qty (Quantity) |
The number of units using the FIFO cost indicated. The system selects a FIFO layer for costing an inventory transaction based on a standard hierarchy; see FIFO Costing Overview. Sometimes the on-hand quantity of the first selected FIFO layer is lower than the total quantity of the transaction. In this situation, the system exhausts the quantity of the first FIFO layer and selects the next FIFO layer in the standard hierarchy to cost the remaining quantity of the transaction. |
|
Example: The screen sample provided above displays an issue transaction of 10 units. There were two FIFO layers for the item in warehouse 2. The first FIFO layer, created on 11/10 through a purchase order receipt, had an on-hand quantity of 5 units remaining. The second FIFO layer, created on 12/23 through a customer return, had an on-hand quantity of 10 units. The system selected the older FIFO layer and exhausted those 5 units. Then the system selected the next available FIFO layer to provide the cost of the remaining 5 units of the issue transaction. Numeric, 7 positions; display-only. |
FIFO cost |
The unit cost from the FIFO layer selected for the transaction. Numeric, 11 positions with a 4-place decimal; display-only. |
Extended cost |
The total cost of the transaction from this FIFO layer. The extended cost is calculated by multiplying the FIFO cost by the quantity for the FIFO layer. Numeric, 13 positions with a 4-place decimal; display-only. |
Part C: Transaction History | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 19: Print Inventory Transaction History (PITH) |
WH03_01 CWDirect 18.0 August 2015 OTN