Jde 920 Inventory Management
Jde 920 Inventory Management
Jde 920 Inventory Management
October 2015
Describes the JD Edwards EnterpriseOne Inventory
Management system, that provides multiple methods of
identifying items. You can use actual item numbers,
numbers that you designate, or a combination of both.
JD Edwards EnterpriseOne Applications Inventory Management Implementation Guide, Release 9.2
E63922-02
Copyright © 2014, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to
the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.
Contents
iii
2.2.1.1 Branch/Plant ALL ........................................................................................................ 2-3
2.2.1.2 Accelerated Pricing Resolution Engine ..................................................................... 2-4
2.2.2 Prerequisites ......................................................................................................................... 2-4
2.2.3 Forms Used to Set Up Constants ....................................................................................... 2-4
2.2.4 Defining Branch/Plant Constants ..................................................................................... 2-6
2.2.5 Defining Batch Control Constants.................................................................................. 2-14
2.2.6 Setting Up ABC Analysis Codes..................................................................................... 2-16
2.2.7 Defining Item Availability............................................................................................... 2-17
2.2.8 Defining System Constants ............................................................................................. 2-18
2.2.9 Defining the Location Format ......................................................................................... 2-22
2.2.10 Defining Segments for Locations.................................................................................... 2-24
2.2.10.1 Location Segment Specification............................................................................... 2-25
2.3 Setting Up Warehouse Locations........................................................................................... 2-27
2.3.1 Understanding Warehouse Locations Setup ................................................................ 2-27
2.3.2 Understanding Multiple Location Entry....................................................................... 2-28
2.3.2.1 Elements...................................................................................................................... 2-28
2.3.2.2 Steps............................................................................................................................. 2-29
2.3.3 Prerequisites ...................................................................................................................... 2-29
2.3.4 Forms Used to Set Up Warehouse Locations ............................................................... 2-30
2.3.5 Setting Processing Options for Location Master (P4100) ............................................ 2-30
2.3.5.1 Display ........................................................................................................................ 2-30
2.3.6 Entering Individual Locations ........................................................................................ 2-30
2.3.7 Entering Multiple Locations............................................................................................ 2-32
2.4 Setting Up Default Location Information............................................................................. 2-33
2.4.1 Understanding Default Location Information Setup .................................................. 2-33
2.4.2 Prerequisites ...................................................................................................................... 2-34
2.4.3 Forms Used to Set Up Default Location Information.................................................. 2-34
2.4.4 Defining the Default Location and Approval Route Code......................................... 2-35
2.4.5 Assigning Default Print Queues..................................................................................... 2-36
2.5 Setting Up Standard Units of Measure ................................................................................. 2-36
2.5.1 Understanding Standard Units of Measure.................................................................. 2-36
2.5.1.1 Example: Conversion Factors for Units of Measure............................................. 2-37
2.5.2 Prerequisite ........................................................................................................................ 2-38
2.5.3 Forms Used to Set Up Standard Units of Measure ...................................................... 2-38
2.5.4 Defining Standard Units of Measure ............................................................................. 2-38
2.6 Setting Up Item Cross-References ......................................................................................... 2-39
2.6.1 Understanding Item Cross-Reference Setup ................................................................ 2-39
2.6.1.1 Cross-References for Promotional Items................................................................ 2-41
2.6.1.2 Cross-References for Related Items ........................................................................ 2-42
2.6.2 Prerequisites ...................................................................................................................... 2-42
2.6.3 Forms Used to Set Up Item Cross-References .............................................................. 2-43
2.6.4 Setting Processing Options for Item Cross Reference (P4104) ................................... 2-44
2.6.4.1 Processing ................................................................................................................... 2-44
2.6.5 Setting Up Cross-References for Promotional Items ................................................... 2-45
2.6.6 Setting Up Price Cross-References for Related Items .................................................. 2-47
2.7 Setting Up Messages................................................................................................................ 2-49
2.7.1 Understanding Message Setup ....................................................................................... 2-49
iv
2.7.2 Forms Used to Set Up Messages..................................................................................... 2-50
2.7.3 Setting Up Messages ........................................................................................................ 2-51
2.7.4 Printing Messages on Program Reports ....................................................................... 2-52
2.7.5 Defining Document Type Exceptions ............................................................................ 2-53
2.8 Setting Up Document Type Information.............................................................................. 2-53
2.8.1 Understanding Document Type Information............................................................... 2-53
2.8.2 Forms Used to Set Up Document Type Information................................................... 2-55
2.8.3 Setting Up Document Types ........................................................................................... 2-55
2.8.3.1 Inventory..................................................................................................................... 2-56
2.8.3.2 Sales ............................................................................................................................. 2-57
2.8.3.3 Procurement ............................................................................................................... 2-59
2.8.3.4 S/WM.......................................................................................................................... 2-60
2.8.3.5 Work Order Definition ............................................................................................. 2-60
2.8.3.6 Shipping ...................................................................................................................... 2-61
2.9 Setting Up AAIs in Distribution Systems............................................................................. 2-61
2.9.1 Understanding AAIs in Distribution Systems.............................................................. 2-61
2.9.2 Understanding AAIs in the JD Edwards EnterpriseOne Inventory Management
System .................................................................................................................... 2-62
2.9.3 Prerequisites ...................................................................................................................... 2-63
2.9.4 Forms Used to Set Up AAIs in Distribution Systems.................................................. 2-64
2.9.5 Setting Processing Options for Distribution AAIs (P40950)....................................... 2-64
2.9.5.1 Defaults ....................................................................................................................... 2-65
2.9.6 Set Up AAIs ....................................................................................................................... 2-65
v
3.2.6.1 Basic Item Data .......................................................................................................... 3-23
3.2.6.2 Additional Info........................................................................................................... 3-25
3.2.6.3 Lot Processing ............................................................................................................ 3-26
3.2.7 Entering Alternate Descriptions ..................................................................................... 3-30
3.2.8 Attaching Messages to Items........................................................................................... 3-30
3.2.9 Entering Notes for Items.................................................................................................. 3-31
3.2.10 Adding Classification Codes to Items ........................................................................... 3-32
3.2.10.1 Sales Classification Codes ........................................................................................ 3-33
3.2.10.2 Purchasing Classification Codes ............................................................................. 3-35
3.2.10.3 Inventory and Transportation Classification Codes ............................................ 3-36
3.2.10.4 Warehouse Classification Codes ............................................................................. 3-37
3.2.11 Entering Default Units of Measure for Items ............................................................... 3-37
3.2.11.1 Weights and Measures.............................................................................................. 3-37
3.2.12 Defining Item Unit of Measure Conversions................................................................ 3-39
3.2.13 Specifying a Dual Unit of Measure for an Item............................................................ 3-40
3.2.13.1 Weights and Measures.............................................................................................. 3-40
3.2.13.2 Additional Info........................................................................................................... 3-40
3.2.14 Setting Up Search Sequence Using Price Units of Measure ....................................... 3-41
3.2.15 Setting Up Manufacturing Information ........................................................................ 3-43
3.2.15.1 Manufacturing Data .................................................................................................. 3-44
3.2.15.2 Grade and Potency ................................................................................................... 3-51
3.2.15.3 Service/Warranty ...................................................................................................... 3-52
3.2.15.4 Supply Chain Planning............................................................................................. 3-53
3.2.15.5 Blend Management ................................................................................................... 3-53
3.2.15.6 Demand Flow® ......................................................................................................... 3-54
3.3 Entering Branch/Plant Information...................................................................................... 3-55
3.3.1 Understanding Branch/Plant Information ................................................................... 3-55
3.3.1.1 Item Locations............................................................................................................ 3-57
3.3.1.2 Country of Origin ...................................................................................................... 3-58
3.3.1.3 Blend Management ................................................................................................... 3-59
3.3.2 Prerequisites ...................................................................................................................... 3-59
3.3.3 Forms Used to Enter Branch/Plant Information ......................................................... 3-60
3.3.4 Setting Processing Options for Item Branch Plant (P41026) ...................................... 3-62
3.3.4.1 Process......................................................................................................................... 3-62
3.3.4.2 Versions....................................................................................................................... 3-64
3.3.4.3 Interop ......................................................................................................................... 3-64
3.3.5 Assigning Items to Branch/Plants ................................................................................. 3-65
3.3.6 Assigning a Primary Location to an Item...................................................................... 3-65
3.3.7 Assigning a Secondary Location to an Item ................................................................. 3-65
3.3.8 Entering Classification Codes for Branch/Plants ........................................................ 3-66
3.3.9 Entering Tax Information ................................................................................................ 3-67
3.3.10 Locating Item Sources ...................................................................................................... 3-68
3.3.11 Entering Item Reorder Quantities .................................................................................. 3-69
3.3.12 Entering Branch/Plant Manufacturing Information ................................................... 3-70
3.3.13 Setting Processing Options for Item Branch Duplication (P41015) ........................... 3-74
3.3.13.1 Defaults 1 .................................................................................................................... 3-74
3.3.13.2 Default 2...................................................................................................................... 3-74
vi
3.3.13.3 Process......................................................................................................................... 3-74
3.3.14 Duplicating Individual Items for Multiple Branch/plants......................................... 3-75
3.3.15 Reviewing the Item/Branch Dup-Batch Report........................................................... 3-76
3.4 Entering Segmented Items...................................................................................................... 3-76
3.4.1 Understanding Segmented Items ................................................................................... 3-77
3.4.2 Forms Used to Enter a Segmented Item ........................................................................ 3-77
3.4.3 Creating a Template for Segmented Items.................................................................... 3-78
3.4.4 Entering Segmented Items .............................................................................................. 3-79
3.5 Working with Matrix and Parent Items................................................................................ 3-79
3.5.1 Understanding Matrix and Parent Items ...................................................................... 3-80
3.5.2 Understanding Matrix Order Entry ............................................................................... 3-81
3.5.3 Prerequisites ...................................................................................................................... 3-81
3.5.4 Forms Used to Work with Matrix and Parent Items ................................................... 3-82
3.5.5 Setting Processing Options for Matrix Items (P4101E) ............................................... 3-83
3.5.5.1 Versions....................................................................................................................... 3-83
3.5.6 Reviewing Matrix Items................................................................................................... 3-84
3.5.7 Setting Processing Options for Matrix Order Entry (P41902) .................................... 3-84
3.5.7.1 Display ........................................................................................................................ 3-84
3.5.8 Ordering Matrix Items ..................................................................................................... 3-85
3.6 Entering Item Cost Information............................................................................................. 3-85
3.6.1 Understanding Item Cost Information .......................................................................... 3-86
3.6.1.1 Item Cost Update....................................................................................................... 3-86
3.6.2 Forms Used to Enter Item Cost Information ................................................................ 3-88
3.6.3 Setting Processing Options for Cost Revisions (P4105) .............................................. 3-89
3.6.3.1 Process......................................................................................................................... 3-89
3.6.3.2 Interop ......................................................................................................................... 3-89
3.6.3.3 Flex Acct...................................................................................................................... 3-89
3.6.4 Assigning a Cost Level to an Item.................................................................................. 3-89
3.6.5 Assigning a Cost Method and Cost to an Item............................................................. 3-91
3.6.6 Entering Manufacturing Setup Cost Information ........................................................ 3-92
3.7 Entering Sales Price Information ........................................................................................... 3-93
3.7.1 Understanding Sales Price Information ........................................................................ 3-94
3.7.2 Forms Used to Enter Sales Price Information............................................................... 3-94
3.7.3 Assigning Price Levels and Price List Groups to an Item........................................... 3-95
3.7.3.1 Additional Info........................................................................................................... 3-96
3.7.4 Entering Item Prices ......................................................................................................... 3-97
vii
4.3.3.4 Interop ............................................................................................................................ 4-8
4.3.3.5 Agreement ..................................................................................................................... 4-8
4.3.4 Issuing Inventory ................................................................................................................. 4-8
4.4 Adjusting Inventory ................................................................................................................... 4-9
4.4.1 Understanding Inventory Adjustments ........................................................................... 4-9
4.4.2 Forms Used to Adjust Inventory .................................................................................... 4-10
4.4.3 Setting Processing Options for Inventory Adjustments (P4114) ............................... 4-10
4.4.3.1 Defaults ....................................................................................................................... 4-10
4.4.3.2 Versions....................................................................................................................... 4-11
4.4.3.3 Process......................................................................................................................... 4-11
4.4.3.4 Interop ......................................................................................................................... 4-13
4.4.3.5 Agreement .................................................................................................................. 4-13
4.4.3.6 Warehouse .................................................................................................................. 4-13
4.4.4 Adjusting Inventory ......................................................................................................... 4-14
4.5 Transferring Inventory............................................................................................................ 4-14
4.5.1 Understanding Inventory Transfers .............................................................................. 4-14
4.5.1.1 Example: Transfer Transaction................................................................................ 4-15
4.5.2 Forms Used to Transfer Inventory ................................................................................. 4-15
4.5.3 Setting Processing Options for Inventory Transfers (P4113) ..................................... 4-16
4.5.3.1 Defaults ....................................................................................................................... 4-16
4.5.3.2 Versions....................................................................................................................... 4-16
4.5.3.3 Process......................................................................................................................... 4-17
4.5.3.4 Interop ......................................................................................................................... 4-18
4.5.3.5 Agreement .................................................................................................................. 4-19
4.5.3.6 Warehouse .................................................................................................................. 4-19
4.5.4 Transferring Inventory..................................................................................................... 4-19
viii
5.3.1.3 Quality Mode ............................................................................................................. 5-11
5.3.2 Prerequisites ...................................................................................................................... 5-12
5.3.3 Forms Used to Locate Quantity Information................................................................ 5-12
5.3.4 Setting Processing Options for Item Availability (P41202)......................................... 5-13
5.3.4.1 Versions....................................................................................................................... 5-13
5.3.4.2 Display ........................................................................................................................ 5-14
5.3.4.3 Lot Options ................................................................................................................. 5-15
5.3.5 Locating Summary Quantity Information .................................................................... 5-15
5.3.5.1 Item Availability ........................................................................................................ 5-15
5.3.5.2 Additional Selections 1 ............................................................................................. 5-17
5.3.6 Reviewing Detailed Quantity Information ................................................................... 5-17
5.3.7 Setting Processing Options for Segmented Item Availability (P41206).................... 5-19
5.3.7.1 Defaults ....................................................................................................................... 5-19
5.3.7.2 Versions....................................................................................................................... 5-19
5.3.8 Reviewing Segmented Item Availability....................................................................... 5-19
5.3.9 Setting Processing Options for Location Segment Inquiry (P4100142)..................... 5-20
5.3.9.1 Mode............................................................................................................................ 5-20
5.3.10 Reviewing Quantities in Locations with Segments ..................................................... 5-21
5.3.11 Setting Processing Options for Lot Master Availability (P41280) ............................. 5-21
5.3.11.1 Versions....................................................................................................................... 5-22
5.3.11.2 Display ........................................................................................................................ 5-22
5.3.12 Locating Quantity Information by Lot .......................................................................... 5-22
5.3.13 Setting Processing Options for Item Ledger Inquiry (CARDEX) (P4111) ................ 5-23
5.3.13.1 Default......................................................................................................................... 5-24
5.3.13.2 Versions....................................................................................................................... 5-24
5.3.13.3 Display ........................................................................................................................ 5-24
5.3.14 Locating On-Hand Quantity Information..................................................................... 5-24
5.3.15 Reviewing Current Inventory Levels Online ............................................................... 5-25
5.4 Reviewing Supply-and-Demand Information..................................................................... 5-25
5.4.1 Understanding Supply-and-Demand Information...................................................... 5-25
5.4.2 Form Used to Review Supply-and-Demand Information .......................................... 5-26
5.4.3 Setting Processing Options for Supply and Demand Inquiry (P4021) ..................... 5-26
5.4.3.1 Process......................................................................................................................... 5-26
5.4.3.2 Display ........................................................................................................................ 5-29
5.4.3.3 Versions....................................................................................................................... 5-29
5.4.4 Reviewing Supply-and-Demand Information.............................................................. 5-30
5.5 Reviewing Performance Information.................................................................................... 5-32
5.5.1 Form Used to Review Performance Information ......................................................... 5-32
5.5.2 Setting Processing Options for Buyer Information (P4115)........................................ 5-32
5.5.2.1 Versions....................................................................................................................... 5-32
5.5.3 Reviewing Performance Information ............................................................................ 5-32
5.6 Working with Transaction Records....................................................................................... 5-34
5.6.1 Understanding Transaction Records ............................................................................. 5-35
5.6.2 Forms Used to Work with Transaction Records .......................................................... 5-36
5.6.3 Running the Item Ledger As Of Generation Program ................................................ 5-36
5.6.4 Setting Processing Options for Item Ledger As Of Record Generation (R41542) ... 5-37
5.6.4.1 GENERATION........................................................................................................... 5-37
ix
5.6.5 Updating Balance Forward Records for Inactivity in the Fiscal Year....................... 5-37
5.6.6 Setting Processing Options for As Of Updating (R41548) .......................................... 5-37
5.6.6.1 Defaults ....................................................................................................................... 5-38
5.6.7 Entering Individual Transactions................................................................................... 5-38
5.6.8 Reviewing Multiple Transactions and Balances ......................................................... 5-39
5.6.9 Reviewing the Item Ledger Detail Print Report........................................................... 5-40
5.6.10 Setting Processing Options for Item Ledger Detail Print (R41540) ........................... 5-40
5.6.10.1 REPORT DISPLAY .................................................................................................... 5-40
5.6.11 Reviewing the Item Ledger by GL Class Code Report ............................................... 5-40
5.6.12 Setting Processing Options for Item Ledger By GL Class Code (R41541)................ 5-40
5.6.12.1 Report Option ............................................................................................................ 5-41
5.6.13 Reviewing the General Ledger by Object Account Report......................................... 5-41
5.6.14 Reviewing the Trial Balance by Object Account Report ............................................. 5-41
5.7 Reconciling Inventory to General Ledger (G/L) (Release 9.1 Update) ........................... 5-41
5.7.1 Understanding Inventory to General Ledger Reconciliation..................................... 5-42
5.7.2 Reviewing the Automatic Inventory to GL Reconciliation Report .......................... 5-43
5.7.3 Setting Processing Options for Automatic Inventory to GL Reconciliation
(R41500) .............................................................................................................................. 5-43
5.7.3.1 Default......................................................................................................................... 5-43
5.7.3.2 Process......................................................................................................................... 5-44
5.7.3.3 WO Document Type ................................................................................................. 5-44
5.7.3.4 Interbranch ................................................................................................................. 5-45
5.7.3.5 Print ............................................................................................................................. 5-45
5.7.4 Form Used To Reconcile Inventory and General Ledger Records ........................... 5-45
5.7.5 Reconciling Inventory to General Ledger .................................................................... 5-45
5.7.6 Setting Processing Options for Manual Inventory to G/L Reconciliation Program
(P41500) ............................................................................................................................. 5-47
5.7.6.1 Defaults ....................................................................................................................... 5-47
5.7.6.2 WO Document Type ................................................................................................. 5-47
5.7.6.3 Interbranch ................................................................................................................. 5-48
x
6.2.12 Reviewing Cycle Count Variances .................................................................................... 6-7
6.2.13 Revising Cycle Count Quantities ...................................................................................... 6-9
6.2.14 Printing a Variance Report ................................................................................................. 6-9
6.2.15 Setting Processing Options for the Print Variance Detail (R41403).............................. 6-9
6.2.15.1 Processing ...................................................................................................................... 6-9
6.2.16 Approving Cycle Counts ................................................................................................. 6-10
6.2.17 Running the Cycle Count Update Program.................................................................. 6-10
6.2.18 Setting Processing Options for Cycle Count Update (R41413) .................................. 6-11
6.2.18.1 Defaults ....................................................................................................................... 6-11
6.2.18.2 Process......................................................................................................................... 6-12
6.2.18.3 Interop ......................................................................................................................... 6-12
6.3 Processing Tag Counts ............................................................................................................ 6-12
6.3.1 Understanding Tag Counts ............................................................................................. 6-13
6.3.1.1 Tag Distribution Information .................................................................................. 6-13
6.3.2 Forms Used to Process Tag Counts................................................................................ 6-13
6.3.3 Running the Select Items for Count Program............................................................... 6-14
6.3.4 Printing Inventory Tags ................................................................................................... 6-14
6.3.5 Setting Processing Options for Print Inventory Tags (R41607).................................. 6-15
6.3.5.1 Defaults ....................................................................................................................... 6-15
6.3.6 Recording Tag Distribution and Receipt Information ................................................ 6-15
6.3.7 Setting Processing Options for Tag Status Review (P41604)...................................... 6-15
6.3.7.1 Defaults ....................................................................................................................... 6-15
6.3.7.2 Warehouse .................................................................................................................. 6-16
6.3.8 Entering Tag Count Results ............................................................................................ 6-16
6.3.9 Reviewing Tag Count Variances .................................................................................... 6-16
6.3.10 Running Tag Count Updates .......................................................................................... 6-17
6.3.10.1 Data Sequence ............................................................................................................ 6-17
6.3.11 Setting Processing Options for Tag Inventory Update (R41610) ............................... 6-18
6.3.11.1 Process......................................................................................................................... 6-18
6.3.11.2 Interop ......................................................................................................................... 6-18
7 Updating Costs
7.1 Updating Item Costs................................................................................................................... 7-1
7.1.1 Understanding Item Cost Updates ................................................................................... 7-2
7.1.2 Prerequisite ........................................................................................................................... 7-2
7.1.3 Forms Used to Update Item Costs .................................................................................... 7-3
7.1.4 Setting Processing Options for Speed Cost Maintenance (P41051) .............................. 7-3
7.1.4.1 Defaults .......................................................................................................................... 7-3
7.1.4.2 Process............................................................................................................................ 7-3
7.1.5 Updating Costs for an Item Across Multiple Branch/Plants ........................................ 7-4
7.1.6 Updating Costs for Multiple Items Across Multiple Branch/Plants ........................... 7-4
7.1.7 Setting Processing Options for Batch Cost Maintenance (R41802)............................... 7-5
7.1.7.1 Process............................................................................................................................ 7-5
7.1.7.2 Defaults .......................................................................................................................... 7-5
7.1.7.3 Print ................................................................................................................................ 7-5
7.1.7.4 Edits ................................................................................................................................ 7-6
7.1.8 Updating Average Costs for Items.................................................................................... 7-6
xi
7.1.9 Updating Current Item Costs with Future Costs............................................................ 7-7
7.1.10 Setting Processing Options for Future Cost Update (R41052) ...................................... 7-7
7.1.10.1 PROCESS CNTRL......................................................................................................... 7-7
7.1.10.2 Interop ............................................................................................................................ 7-8
7.2 Working with Detail Costing in Distribution ......................................................................... 7-8
7.2.1 Understanding Detail Costing ........................................................................................... 7-9
7.2.2 Forms Used to Work with Detail Costing in Distribution............................................. 7-9
7.2.3 Setting Up Detail Costing in Distribution ........................................................................ 7-9
7.2.4 Creating Simulated Costs for Distribution .................................................................. 7-10
7.2.5 Setting Processing Options for Simulated Cost Update (R30840) ............................. 7-11
7.2.5.1 Process......................................................................................................................... 7-11
7.2.5.2 Defaults ....................................................................................................................... 7-11
7.2.5.3 Print ............................................................................................................................. 7-11
7.2.6 Copying Manufacturing Cost Components.................................................................. 7-12
7.2.7 Setting Processing Options for Copy Cost Components (R41891) ............................ 7-12
7.2.7.1 From............................................................................................................................. 7-12
7.2.7.2 Landed Costs.............................................................................................................. 7-12
7.2.7.3 Default......................................................................................................................... 7-13
xii
9.2.4.1 Process............................................................................................................................ 9-4
9.2.4.2 Defaults .......................................................................................................................... 9-5
9.2.4.3 Lot Options .................................................................................................................... 9-6
9.2.5 Entering Lot Information for Items................................................................................... 9-6
9.2.5.1 Lot Processing ............................................................................................................... 9-6
9.2.6 Creating Lots ........................................................................................................................ 9-8
9.2.7 Entering Availability Information..................................................................................... 9-9
9.3 Working with Lot Availability.................................................................................................. 9-9
9.3.1 Forms Used to Work with Lot Availability ..................................................................... 9-9
9.3.2 Setting Processing Options for Lot Master Availability (P41280) ............................. 9-10
9.3.2.1 Versions....................................................................................................................... 9-10
9.3.2.2 Display ........................................................................................................................ 9-10
9.3.3 Viewing Lot Availability ................................................................................................. 9-10
9.3.4 Reviewing Lot Quantities ................................................................................................ 9-12
9.3.5 Revising Lot Activity Dates............................................................................................. 9-13
9.3.6 Assigning Lot Status Codes............................................................................................. 9-13
9.4 Setting Up Allowed Lot Status Codes .................................................................................. 9-14
9.4.1 Understanding Lot Status Codes.................................................................................... 9-14
9.4.2 Forms Used to Set Up Allowed Lot Status Codes ....................................................... 9-16
9.4.3 Adding Allowed Lot Status Codes ................................................................................ 9-16
9.5 Viewing Lot Transactions ....................................................................................................... 9-16
9.5.1 Understanding Tracking and Tracing ........................................................................... 9-17
9.5.2 Understanding Faulty Lot Tracing................................................................................. 9-17
9.5.3 Understanding Electronic and Device Quality Records ............................................. 9-17
9.5.3.1 Item Information........................................................................................................ 9-18
9.5.3.2 Quality Results........................................................................................................... 9-18
9.5.3.3 As Built Comparison................................................................................................. 9-18
9.5.3.4 Engineering History .................................................................................................. 9-19
9.5.3.5 Production History.................................................................................................... 9-19
9.5.3.6 Audit and Signature.................................................................................................. 9-19
9.5.4 Forms Used to View Lot Transactions........................................................................... 9-19
9.5.5 Setting Processing Options for Track/Trace Inquiry (P41203) .................................. 9-20
9.5.5.1 Display ........................................................................................................................ 9-20
9.5.5.2 Document Type.......................................................................................................... 9-21
9.5.5.3 Defaults ....................................................................................................................... 9-21
9.5.5.4 Version ........................................................................................................................ 9-22
9.5.6 Reviewing Lot Trace and Track Information................................................................ 9-23
9.5.6.1 Driver .......................................................................................................................... 9-24
9.5.6.2 Additional Filter ........................................................................................................ 9-24
9.5.6.3 Additonal Elements................................................................................................... 9-24
9.6 Reclassifying Lots .................................................................................................................... 9-25
9.6.1 Understanding Lot Reclassification ............................................................................... 9-25
9.6.1.1 Effective Date Calculations ...................................................................................... 9-26
9.6.2 Prerequisites ...................................................................................................................... 9-26
9.6.3 Forms Used to Reclassify Lots ........................................................................................ 9-27
9.6.4 Setting Processing Options for Item Reclassifications (P4116) .................................. 9-27
9.6.4.1 Defaults ....................................................................................................................... 9-27
xiii
9.6.4.2 Versions....................................................................................................................... 9-27
9.6.4.3 Process......................................................................................................................... 9-27
9.6.4.4 Interop ......................................................................................................................... 9-28
9.6.4.5 Agreement .................................................................................................................. 9-28
9.6.5 Reclassifying Items and Lots........................................................................................... 9-28
9.7 Setting Up Dates for Lots ........................................................................................................ 9-30
9.7.1 Understanding Lot Date Information............................................................................ 9-30
9.7.1.1 Expiration Date Calculation Method...................................................................... 9-30
9.7.2 Prerequisite ........................................................................................................................ 9-31
9.7.3 Forms Used to Set Up Dates for Lots............................................................................. 9-31
9.7.4 Entering Lot Date Information ....................................................................................... 9-31
9.7.4.1 Lot Processing ............................................................................................................ 9-32
9.7.5 Calculating Active Components or Ingredients........................................................... 9-33
9.7.5.1 Manufacturing Data .................................................................................................. 9-33
9.8 Defining Effective Dates for Future Availability ................................................................ 9-33
9.8.1 Understanding Future Availability Dates..................................................................... 9-34
9.8.1.1 Effective Days Calculations...................................................................................... 9-35
9.8.1.2 Availability and Commitment Calculations.......................................................... 9-35
9.8.1.3 Purchasing Commitments........................................................................................ 9-35
9.8.1.4 Manufacturing Commitments ................................................................................. 9-35
9.8.1.5 Material Requirements Planning (MRP) ................................................................ 9-35
9.8.2 Form Used to Define Effective Dates for Future Availability .................................... 9-37
9.8.3 Defining Effective Days ................................................................................................... 9-37
9.8.3.1 Lot Processing ............................................................................................................ 9-37
9.8.4 Running the Update Effective Lots Program ............................................................... 9-37
9.8.5 Setting Processing Options for Update Effective Lots (R41083) ................................ 9-38
9.8.5.1 Defaults ....................................................................................................................... 9-38
9.8.5.2 Omit ............................................................................................................................. 9-38
9.8.5.3 Process......................................................................................................................... 9-38
9.9 Setting Up Lot Shipment Ascending Dates.......................................................................... 9-38
9.9.1 Understanding Shipment Ascending Date Rules ........................................................ 9-38
9.9.2 Prerequisites ...................................................................................................................... 9-39
9.9.3 Forms Used to Set Up Lot Shipment Ascending Dates............................................... 9-40
9.9.4 Setting Up Preference Names for Advanced Lots ....................................................... 9-40
9.9.5 Attaching Preference Names to Schedules ................................................................... 9-41
9.9.6 Setting Up Lot Shipment Ascending Date Rules ......................................................... 9-41
10 Managing Containers
10.1 Understanding Container Management............................................................................... 10-1
10.1.1 Prerequisite ........................................................................................................................ 10-1
10.1.2 Container Management Features ................................................................................... 10-2
10.1.3 Inventory and the Container Life Cycle ........................................................................ 10-2
10.1.4 Container Management System Flow............................................................................ 10-3
10.1.5 Tasks That Integrate with Container Management ..................................................... 10-5
10.1.5.1 Recording the Container Receipt ............................................................................ 10-5
10.1.5.2 Filling the Container ................................................................................................. 10-6
10.1.5.3 Processing Sales Orders............................................................................................ 10-6
xiv
10.1.6 Container Types ................................................................................................................ 10-6
10.1.7 Deposits and Rental Fees ................................................................................................. 10-7
10.1.7.1 Deposit Layers ........................................................................................................... 10-7
10.1.8 Billing Methods ................................................................................................................. 10-8
10.1.8.1 Summary Method...................................................................................................... 10-8
10.1.8.2 Transaction Method .................................................................................................. 10-9
10.2 Understanding Setup Tasks .................................................................................................. 10-9
10.2.1 Order Line Types .............................................................................................................. 10-9
10.2.2 Order Activity Rules ...................................................................................................... 10-10
10.2.3 Item Types ....................................................................................................................... 10-11
10.2.4 User-Defined Codes ....................................................................................................... 10-12
10.2.5 Print Messages................................................................................................................. 10-12
10.2.6 AAIs .................................................................................................................................. 10-13
10.2.7 Invoice Cycle Calculation .............................................................................................. 10-13
10.3 Understanding Pricing Schedules ....................................................................................... 10-13
10.4 Setting Up Container Codes and Items .............................................................................. 10-14
10.4.1 Understanding Container Codes.................................................................................. 10-14
10.4.2 Forms Used to Set Up Container Codes and Items ................................................... 10-14
10.4.3 Identifying Container Codes......................................................................................... 10-14
10.4.3.1 UCC 128 .................................................................................................................... 10-15
10.4.4 Identifying Item Numbers for Empty Containers ..................................................... 10-15
10.5 Setting Up Container Preferences........................................................................................ 10-16
10.5.1 Understanding Container Preferences ........................................................................ 10-16
10.5.2 Prerequisites .................................................................................................................... 10-17
10.5.3 Forms Used to Set Up Container Preferences............................................................. 10-17
10.5.4 Creating a Container Deposit/Rental Preference ...................................................... 10-18
10.5.5 Creating an Invoice Cycle Preference .......................................................................... 10-21
10.5.6 Creating a Pricing Unit of Measure Preference.......................................................... 10-22
10.5.7 Creating a Print Message Preference ........................................................................... 10-22
10.6 Setting Up Serial Number Tracking .................................................................................... 10-23
10.6.1 Understanding Serial Number Processing.................................................................. 10-23
10.6.2 Forms Used to Set Up Serial Number Tracking ......................................................... 10-23
10.6.3 Setting Up Serial Number Information ....................................................................... 10-23
10.7 Processing Container Transactions ..................................................................................... 10-24
10.7.1 Understanding Container Transactions ...................................................................... 10-24
10.7.2 Prerequisites .................................................................................................................... 10-24
10.7.3 Forms Used to Process Container Transactions ......................................................... 10-25
10.7.4 Running Container Management Extraction.............................................................. 10-25
10.7.4.1 Data Selection........................................................................................................... 10-25
10.7.5 Processing Rental Fees, Deposits, and Refunds ........................................................ 10-26
10.7.6 Creating Sales Order Lines for Rental Fees................................................................. 10-26
10.7.7 Creating Sales Order Lines for Deposits and Refunds.............................................. 10-26
10.7.8 Processing Sales Order Lines for Rental Fees, Deposits, and Refunds ................... 10-27
10.7.9 Reviewing Container Deposits ..................................................................................... 10-27
10.7.10 Reviewing Container Transactions .............................................................................. 10-29
xv
11 Managing Data Purges
11.1 Understanding Data Purges ................................................................................................... 11-1
11.2 Purging Data............................................................................................................................. 11-1
11.2.1 Understanding Purge Programs..................................................................................... 11-1
11.2.2 Prerequisites ...................................................................................................................... 11-2
11.2.3 Running the Item Master Purge ..................................................................................... 11-2
11.2.4 Setting Processing Options for Item Master Purge (R4101P) ..................................... 11-2
11.2.4.1 Process......................................................................................................................... 11-2
11.2.5 Running the Item Balance Purge ................................................................................... 11-3
11.2.6 Setting Processing Options for Item Balance Purge (R4102P).................................... 11-3
11.2.6.1 Process......................................................................................................................... 11-4
xvi
12.3.7 Updating the Location Format...................................................................................... 12-12
xvii
B.3.21.1 Data Sequence ............................................................................................................ B-13
B.3.22 R41543 – Processing Options for the Item Ledger/Account Integrity Report ........ B-14
B.3.22.1 Report Display ........................................................................................................... B-14
B.3.23 Reviewing the Item Balance/Ledger Integrity Report................................................ B-14
B.3.24 R41544 — Processing Options for the Item Balance/Ledger Integrity Report........ B-14
B.3.24.1 Process......................................................................................................................... B-15
B.3.25 Reviewing the Inventory Journal Report ...................................................................... B-15
B.3.26 R41550 — Processing Options for the Inventory Journal Report .............................. B-15
B.3.26.1 Print Options .............................................................................................................. B-15
B.3.27 Reviewing the Item Master Directory Report .............................................................. B-15
B.3.28 R41560 — Processing Options for the Item Master Directory Report ...................... B-15
B.3.28.1 Process......................................................................................................................... B-16
B.3.29 Reviewing the Unit Cost Warnings Report .................................................................. B-16
B.3.30 R41580 — Processing Options for the Unit Cost Warnings Report .......................... B-16
B.3.30.1 Variance ...................................................................................................................... B-16
B.3.31 Reviewing the Valuation Analysis Report.................................................................... B-16
B.3.31.1 Data Sequence ............................................................................................................ B-16
B.3.32 R41590 — Processing Options for the Inventory Valuation Analysis Report ......... B-17
B.3.32.1 Costing Method ......................................................................................................... B-17
B.3.33 Reviewing the ABC Analysis Report ............................................................................ B-17
B.3.34 Prerequisites ...................................................................................................................... B-17
B.3.35 R4164 — Processing Options for the ABC Analysis Report ....................................... B-18
B.3.35.1 Display ........................................................................................................................ B-18
B.3.35.2 Process......................................................................................................................... B-19
B.3.35.3 Update......................................................................................................................... B-19
B.3.36 Reviewing the Inventory Cost/Price Comparison Report ......................................... B-19
B.3.37 R41700 — Processing Options for the Inventory Cost/Price Comparison Report . B-19
B.3.37.1 Defaults ....................................................................................................................... B-19
B.3.38 Reviewing the Country of Origin Update for Items Report....................................... B-19
B.3.39 R41806— Processing Options for the Country of Origin Update for Items Report B-20
B.3.39.1 Default......................................................................................................................... B-20
B.3.40 Reviewing the Country of Origin Update for Lots Report......................................... B-20
B.3.41 R41807— Processing Options for the Country of Origin Update for Lots Report.. B-20
B.3.41.1 Default......................................................................................................................... B-20
B.3.42 Running the Update Sellable Field Report (R41900) ................................................... B-20
B.3.43 R41900 — Processing Options for the Update Sellable Field Report ........................ B-21
B.3.43.1 Process......................................................................................................................... B-21
Index
xviii
Preface
Audience
This guide is intended for implementers and end users of the JD Edwards
EnterpriseOne Inventory Management system.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
See Also:
■ JD Edwards EnterpriseOne Applications Financial Management
Fundamentals Implemenation Guide.
xix
Related Information
For additional information about JD Edwards EnterpriseOne applications, features,
content, and training, visit the JD Edwards EnterpriseOne pages on the JD Edwards
Resource Library located at:
http://learnjde.com
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements
associated with an action, or terms defined in text or the glossary.
Italics Italic type indicates book titles, emphasis, or placeholder
variables for which you supply particular values.
Monospace Monospace type indicates commands within a paragraph. URLs,
code in examples, text that appears on the screen, or text that you
enter.
xx
1
Introduction to JD Edwards EnterpriseOne
1
Inventory Management
1.1.5 Lots
You can identify and segregate inventory by lots within locations for special lot control
or layered costing. This feature enables you to provide unique descriptions, cost
information, and expiration dates.
Some companies purchase or manufacture a single item from/in more than one
country. In JD Edwards EnterpriseOne system, you can identify and segregate
inventory by attaching country of origin to lots. Country of Origin is a code (00/CN)
that identifies the country in which the item originates.
The system treats the country of origin as an attribute of the new lot in the similar
manner as expiration date, which you can enter during transactions. Therefore,
subsequent transactions do not update the country of origin. Updates to the country of
origin after the lot has been created must occur from the Lot Master program (P4108).
The Country of Origin affects the following programs:
■ Item Master (P4101).
■ Item Branch (P41026).
■ Lot Master (P4108).
■ Inventory Adjustments (P4114).
■ Item Reclassifications (P4116).
■ Purchase Order Receipts (P4312).
■ Supplier Self Service Receipts (P4312S).
■ Work Order Completions Matrix Entry (PCW46).
■ Work Order Completion Detail (P31114).
■ Edit Weigh Tag Master (P31B77).
does not physically exist. You designate a logical warehouse to resemble an actual
physical warehouse, and define its locations in a format that fits the needs.
This table lists and describes the systems with which JD Edwards EnterpriseOne
Inventory Management integrates:
The inbound conversion program moves the translated data into the JD Edwards
EnterpriseOne EDI interface tables. The JD Edwards EnterpriseOne Electronic
Commerce system then moves the data into the appropriate application tables. When
you send documents, the system performs these procedures in reverse order.
See "Setting Up the General Accounting System, " in the JD Edwards EnterpriseOne
Applications General Accounting Implementation Guide.
8. Enter address book records.
See "Entering Address Book Records" in the JD Edwards EnterpriseOne Applications
Address Book Implemenation Guide.
9. Set up inventory information, such as branch/plant constants, default locations
and printers, manufacturing and distribution automatic accounting instructions,
and document types.
See Setting Up the Inventory Management System.
10. Set up shop floor calendars.
Feature Description
Constants Constants provide the following types of default
information:
■ System constants specify which functions to
perform.
■ Batch control constants specify whether a
program requires management approval and
batch control.
■ Branch/plant constants define the day-to-day
transactions within a branch/plant.
■ Location format defines item storage areas in a
branch/plant.
■ Item availability defines how the system
calculates the quantity of items that are available
in each branch/plant.
Warehouse locations Warehouse locations define the locations that are
available in branch/plants.
Feature Description
Default location and printers Default location and printer settings provide the
system with branch/plant, printer output queue, and
approval route code information to use as default
settings.
Item cross-references Item cross-reference numbers enable the system to
associate internal and external items.
Messages Messages appear depending on which programs you
specify and which messages you determine should
print.
Document type information Document type information is typically set up in a
user-defined code (UDC). You can use the Document
Type Maintenance program to set up and maintain
this information for Distribution.
AAIs AAIs provide accounting information and the general
ledger relationships for interacting with the JD
Edwards EnterpriseOne General Accounting system.
2.2.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up the branch/plant as a business unit.
See "Setting Up Organizations" in the JD Edwards EnterpriseOne Applications
Financial Management Fundamentals Implemenation Guide.
■ Create an address book record for the branch/plant.
See "Entering Address Book Records" in the JD Edwards EnterpriseOne Applications
Address Book Implemenation Guide.
Branch Plant
Enter an alphanumeric code that identifies a separate entity within a business for
which you want to track costs.
Before you enter a value in this field, you must set up the branch/plant as a business
unit in the
Note: Only one of the fields for item number symbols (SYM1, SYM2,
SYM3, or SYM6) can be blank to identify it as the primary number. All
others must include a unique symbol.
Note: Only one of the fields for item number symbols (SYM1, SYM2,
SYM3, or SYM6) can be blank to identify it as the primary number. All
others must include a unique symbol.
If you do not want to use this number as the primary number, you must enter a special
symbol to identify it. Use a symbol that is not significant for any other purposes of
entry, such as /,*, or &. Do not use a period or a comma as a symbol. When you enter
this item number on any other form, you must include this symbol as the first
character.
Note: Only one of the fields for item number symbols (SYM1, SYM2,
SYM3, or SYM6) can be blank to identify it as the primary number. All
others must include a unique symbol.
Symbol Customer/Supplier
Enter a character that identifies the customer's or supplier's number. When you enter a
number preceded by this character, the system recognizes the number as the
customer's or supplier's number. The system then uses the cross-reference table to
match the number to the item number. You must complete this field if you want the
system to perform cross-referencing.
Commitment Method
Enter a code from UDC table H40/CM that specifies how the system commits lot items
to inventory. Values are:
1: The normal commitment method for inventory. The system commits inventory from
the primary location and then from secondary locations. The system commits
inventory from the locations with the most inventory before committing inventory
from locations with the least. The system commits backorders to the primary location.
2: The inventory commitment method by lot number. The system commits inventory
by lot number, starting with the lowest lot number and committing orders to available
lots.
3: The inventory commitment method by lot expiration date. The system commits
inventory from the locations with the earliest expiration date first. The system
considers only locations with expiration dates greater than or equal to the sales order
or parts list requested date.
EOQ = Square root of ((2S/I) × (Y/C)) = the square root of (2(15) divided by .09)) ×
(3000/10) = 316.23
Note: Review the field help for the Economic Order Quantity field
for more information about the EOQ formula.
Commitment Method
Enter a code to indicate the method that you want the system to use to commit lot
items from inventory. Values are:
1: The normal commitment method for inventory. The system commits inventory from
the primary location and then from secondary locations. The system commits
inventory from the locations with the most inventory before committing inventory
from locations with the least. The system commits backorders to the primary location.
2: The inventory commitment method by lot number. The system commits inventory
by lot number, starting with the lowest lot number and committing orders to available
lots.
Foreign Depot
Select this check box to indicate that another company owns the branch/plant.
The Bulk and Packed Load Confirmation programs use this code to determine
whether the depot from which product is being loaded is a foreign depot. If it is a
foreign depot, you must enter a valid borrow agreement during load confirmation.
System Code
Review the system codes. Values include:
During ABC analysis, the system compares the total sales of a single item to the total
sales of all items to calculate the value of each item. An item's value is its percentage of
the total sales. The system then arranges the values of all items from those of highest
value to those of lowest value and adds the values together beginning with the
highest. After it reaches the limit for A items, it continues to add values until it reaches
the limit for B items. All items for which value is included in the total between the A
limit and the B limit are B items. If an item's value causes the total to go over the B
limit, the system assigns that item to the C group.
Clear the check box to send email messages that are generated by distribution
programs to the JD Edwards EnterpriseOne mail box.
Scientific Rounding
Select this check box to indicate that scientific rounding should be performed.
Currently, this feature is enabled only for Quality Management Test Results.
Preference Schedule
Enter a code from UDC table (40/AP) that identifies the advanced preference schedule
that the system uses when resolving preferences. The advanced preference schedule
determines which preferences the system resolves when using the advanced
preference functionality. You cannot maintain preference schedules directly through
UDCs, but you can maintain preference schedules by using the Price Adjustment
Schedule program (P4070).
Separator Character
Enter a character that divides the elements of the location when you display them on
forms or reports. For example, you might use a /as a separator character to divide
elements such as aisle, bin, and shelf in a location code. The location code can contain
up to 20 characters, including separators.
Separators are not stored in the tables, but are used to edit a location on a form or
report. If you do not want to use separators, leave this field blank. However, you must
enter characters and spaces to equal the correct length of each element in the location
code. The system then displays the location as one string of characters. The system
uses the character that you enter in this field to separate the combination of
tank/owner and aisle/bin as it appears on forms or reports.
Companies commonly use a . (period) as the separator character.
Aisle
Enter a number that identifies the number of characters to represent the tank (or aisle
for packaged stock). Values are the numbers 1 through 8.
Bin
Enter a number, 1 through 8,that identifies the number of characters to represent the
owner for commingled bulk stock (or bin for packaged stock).
Code 3throughCode 10
Enter the number of characters to represent codes 3 through 10 in the location format
specification.
Aisle
Enter a code from UDC table (41/ER) that specifies which edit rule the system uses to
validate segment 1. Values are:
Blank: The system does not perform any validation.
1: The system uses an address book number for validation.
2: The system uses a UDC for validation.
Note: You cannot use this rule with location segment specification.
If you want to assign location ownership, you must enter 1 in either the Aisle or Bin
field to enable an address book number for that segment.
Bin
Enter a code from UDC table (41/ER) that specifies which edit rule the system uses to
validate segment 2.
If you want to assign location ownership, you must enter 1 in either the Aisle or Bin
field to enable an address book number for that segment.
Additionally, you can define pseudo locations that represent physical locations for
products that you sell but do not stock, such as products that are stocked at the
supplier's facility and shipped from there.
Location control is a feature that you activate through the branch/plant constants.
Location control is required for the JD Edwards EnterpriseOne Warehouse
Management system but optional for all other distribution systems.
The system stores location information in the Location Master table (F4100).
2.3.2.1 Elements
You can use up to 10 elements to define the location. These elements consist of aisle,
bin, and location codes 03 through 10. Each element can consist of either alphabetic
characters or numbers. You cannot combine numbers and letters in a single element.
You can, however, use multiple elements, some consisting of numbers (such as aisles)
and some consisting of letters (such as bins).
The system completes the spaces that precede the elements with either blank spaces or
zeros, depending on the business requirements. Some bar code readers do not
correctly process blank spaces. To precede elements with zeros, you must specify on
the Speed Location Maintenance Revisions form that the system completes the leading
spaces with zeros. If you activated location segment control in the Branch/Plant
Constants program (P41001) and are using the address book numbers to validate the
new locations, then the system creates locations that do not contain zeros.
2.3.2.2 Steps
A step is a number that the program uses to create locations from a specified range of
locations. After the program creates each new location, it increments the location,
either by the step number that you enter for locations that are numeric, or by 1 for
locations that are alphabetic. Therefore, by entering a range of locations in
combination with a step, you can enter many locations at once.
For example, assume that you want to enter new locations for a flow zone in
Warehouse A. The flow zone consists of aisles and bins. Three aisles are marked A, B,
and C, and six bins are marked 1 through 6.
■ For aisles, the range is A through C.
The program creates aisles A, B, and C because it always uses a step 1 for
alphabetic locations.
■ For bins, the range is 1 – 6 and the step number is 1.
The program creates bins 1 – 6 for each aisle, resulting in aisle and bin locations
A1, A2, A3, A4, A5, A6, B1, B2, and so on.
In this example, if you enter a step number of 2, the program creates the bin
locations of 1, 3, and 5 for each aisle, resulting in aisle and bin locations A1, A3,
A5, B1, B3, B5, C1, C3, and C5.
2.3.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up the information on the Location Format Specification tab on the Branch
Location Definition form.
■ Verify that Location Control is activated on the Branch/Plant Constants form
(optional).
See Setting Up Constants.
2.3.5.1 Display
1. Location Records
Specify whether to include item location records with no available quantity or
inbound/outbound quantity when reviewing availability by location.
Blank: Include item location records.
1: Do not include item location records.
Location
Enter a location but do not use a separator character. If you enter the location identifier
without the separator character, you must enter characters and spaces to equal the
correct length of each element. The system displays the location with the correct
separator and spaces.
LOD(level of detail-location)
Enter a code from UDC table (H40/LL) that summarizes or classifies locations and
provides a hierarchy of locations for review purposes. For example, you can assign
aisles to level 2, and individual bins within the aisle as level 3.
Use the Detail Level field to specify the beginning level of detail that you want the
system to display for the location.
Mix Item/Lot
Enter a code from UDC table (41/ML) that specifies whether to prohibit or enable the
system to combine different items into one location or to combine different lot or serial
numbers of the same item into one location.
Leading Zeroes
Specify whether the system populates leading spaces with zeroes instead of blank
spaces.
2.4.2 Prerequisites
Before you complete the tasks in this section, you must verify that branch/plants are
set up.
Terminal/User ID
Enter the workstation ID number.
Output Queue
Enter the waiting area that a job goes to after it has processed. Output queues (OUTQ)
are sometimes attached to printers. If you do not enter an OUTQ, the system uses the
default value from the user's job description.
can also set up conversion factors that associate each unit of measure with the primary
unit of measure.
2.5.2 Prerequisite
Before you complete the tasks in this section, you must verify that units of measure are
set up in UDC table (00/UM).
Conversion Factor
Enter the factor that the system uses to convert one unit of measure to another unit of
measure.
To Unit of Measure
Enter a code from UDC table (00/UM) that specifies the unit of measure the value in
the From Unit of Measure field is converting to.
You set up promotional item information at the customer or supplier level. For
supplier promotions, you can order a regular item and replace it with the promotional
item, or order the promotional item itself.
This table describes how the system handles promotional line items for sales orders
and purchase orders:
The system uses the F4104 table to process promotional items, as well as these activity
status codes in UDC table (40/AT):
■ 917: Added Promotional Item.
■ 990: Canceled by Promotional Item.
2.6.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up Purchasing Promotional Items (PP) and Sales Promotional Items (SP)
cross-reference types in UDC table (41/DT).
Use special handling codes to prevent multiple promotional items within the same
time frame.
■ Verify that you entered Y in the Advanced Procurement Pricing field and the
Advanced Sales Pricing field on the Pricing Constants form if you need to apply
adjustments.
You can access the Pricing Constants form by selecting Price Constants from the
Form menu on the Branch/Plant Constants form.
See "Setting Up EnterpriseOne Advanced Pricing, " in the JD Edwards
EnterpriseOne Applications Advanced Pricing Implementation Guide.
Note: Depending on how you set the processing options, the system
displays either the Item Cross Reference Revisions By Address form or
the Item Cross Reference Revisions By Item form.
2.6.4.1 Processing
1. Revise by Item or Address
Specify whether to enter cross-references by item number or by address book number.
Values are:
Blank: Use the Item Cross Reference Revisions By Address form to revise by address
book number.
1: Use the Item Cross Reference Revisions By Item form to revise by item number.
Note: This processing option does not affect the appearance of the
Work with Item Cross Reference form.
Item Number
Enter the number of the original item.
Adjustment Indicator
Enter a code from UDC table (42/IA) that indicates which price adjustment to use for
related items. These adjustments can include the original item's adjustment, a
substitute item's adjustment, the best adjustment, or no adjustment, depending on the
item's value.
Values are:
Blank: If you leave this field blank, the system uses the code that is specified in the
Pricing for Substitute Items processing option on the Cross Ref tab in the Sales Order
Entry program (P4210).
1: Use original item price.
2: Use substitute item price.
3: Use best price.
4: No adjustment.
Card Number
Enter an OEM-assigned code from UDC table (40R/CD) that further describes the part
number.
See Also:
■ "Entering Sales Orders" in the JD Edwards EnterpriseOne
Applications Sales Order Management Implementation Guide.
■ "Entering Purchase Orders" in the JD Edwards EnterpriseOne
Applications Procurement Management Implementation Guide.
Note: You can optionally enter the effective date, expired date,
cross-reference description, and customer supplier item revision level.
Address Number
Enter the address number of the customer or supplier. Leave this field blank to apply
to all customers or suppliers.
Item Number
Enter a number that the system assigns to an item. It can be in short, long, or third
item number format. The format is determined by branch/plant ALL. The item
identifier that is blank is the primary item number. Enter the primary item number.
Expired Date
Enter the date on which a transaction, text message, agreement, obligation, or
preference expired or was completed.
Print Message
Enter a code from UDC table (40/PM) that identifies a predefined message from the
Print Message Revisions form. You can print the message on sales orders, purchase
orders, and so forth.
Print on Report
Enter a value that specifies whether the print message/item note text should print on a
specific report. Values are:
Y: Print.
N: Do not print.
You can set up and maintain information about document types in the Document Type
Maintenance program (P40040). The P0040 program updates the Document Type
Master table (F40039), a single repository for information that is currently stored in
various UDCs. The P0040 also updates the User Defined Codes table (F0005).
The P40040 program maintains document type information in these UDC tables:
■ Trace/Track Document Types in UDC table (40/DC).
■ Commitment Document Types in UDC table (40/CT).
■ Blanket Order Types in UDC table (40/BT).
■ Inventory Update Types in UDC table (40/IU).
■ Transaction Type in UDC table (39/TT).
■ Nature of Transaction in UDC table (40/NT).
■ Category of Order in UDC table (40/OC).
■ Other Quantity in UDC table (40/OQ).
■ Interbranch Orders in UDC table (40/IB).
■ Service Contract Type in UDC table (17/CM).
■ Work Order Type in UDC table (48/OT).
■ Carton Status in UDC table (46/RS).
Note: When you add information directly into any of these UDC
tables, the system updates the F0005 table . The system does not
updated the F40039 table.
On the Edit Document Type Exclusion form, you can specify which branch/plants to
exclude from certain document types. When processing specific document types, the
excluded document type does not appear in the Item History table (F4115).
2.8.3.1 Inventory
Select the Inventory tab.
Nature of Transaction
Enter a code from UDC table (40/NT) that specifies how the system processes
inventory transactions that have a From side and a To side, as well as Bottom and Top
levels.
Examples of From/To transactions are inventory transfers, inventory reclassifications,
and work order issues/completions. Examples of Bottom/Top transactions are sales
orders and purchase receipts. An inappropriate value causes the inventory transaction
to process incorrectly.
2.8.3.2 Sales
Select the Sales tab.
Order Category
Enter a code from UDC table (40/OC) that identifies blanket order types in the JD
Edwards EnterpriseOne Sales Order Management system and the JD Edwards
EnterpriseOne Procurement system. Values are:
0: Regular order
1: Blanket order
2: Quote - No quantity release
3: Quote - QuantityrRelease
In the JD Edwards EnterpriseOne Sales Order system, when the Order Type option is
selected, if the order is set up as type 2 or 3 (Quotes), a value will be hard coded into
the Order Type Indicator field to specify that a particular order is a quote.
Interbranch Orders
Enter a value of 1 to identify this order type as an interbranch order type. When you
create an interbranch order using the Sales Order Entry program (P4210), the system
processes additional order information such as cost markup. You would use an
Interbranch order in a situation in which the customer places an order with a sales
office, but the sales office ships the inventory to the customer from a warehouse
facility. The system creates accounting transactions and intercompany invoices for
interbranch sales orders during Sales Update and Invoice Print.
Other Quantity
In the JD Edwards EnterpriseOne Sales Order Management system, this field
determines whether the Quantity on Other Sales Order 1 or 2 field in the Item Location
file is updated instead of the Soft Commit field or the Hard Commit field.
In the JD Edwards EnterpriseOne Procurement system, this field determines whether
the Quantity on Other Purchase Order field is updated in the Item Location file instead
of the On Purchase Order field.
2.8.3.3 Procurement
Select the Procurement tab.
Publish Externally
Select this check box to allow external publishing of a document type.
2.8.3.4 S/WM
Select the S/WM tab.
Contract Type
Enter a code from UDC table (17/CM) that the system uses to define whether the
document type relates to either a service or supplier contract. The service contract can
be either a regular or quote contract.
Order Type
Enter a code that the system uses to determine the type of work order, based on the
value in the Order Type field. Values are:
01: Unrelated to work order.
02: Manufacturing work order.
03: Manufacturing rework work order.
04: Equipment work order.
05: Service work order.
06: Warranty claim order.
07: Supplier recovery order.
08: Engineering change order.
09: Engineering change request order.
10: Property Management order.
11: Engineer to Order summary order.
12: Rate schedule order.
2.8.3.6 Shipping
Select the Shipping tab.
AAI Description
3910 An AAI to identify the inventory account for the
inflation adjustment process.
3911 An AAI to identify the results account, which
serves as the offset to the inventory adjustments
account.
4122 An inventory AAI that provides the balance sheet
inventory valuation account.
4124 An inventory AAI that provides the expense or
cost of goods sold account.
4126 A zero balance adjustment AAI that provides the
inventory offset account.
4128 A zero balance adjustment AAI that provides the
expense or cost of goods offset account.
AAI Description
4134 An item balance cost change AAI that determines
the inventory offset account.
4136 An item balance cost change AAI that determines
the expense or cost of goods offset account.
4141 A standard cost variance AAI that determines the
cost of goods offset account.
4152 A physical inventory update AAI that determines
the inventory offset account.
4154 A physical inventory update AAI that determines
the cost of goods offset account.
4162 An AAI that determines the average cost
update-inventory
4164 An AAI that determines the average cost
update-cost of goods sold
4172 A batch cost maintenance AAI that determines the
inventory offset account.
4174 A batch cost maintenance AAI that determines the
expense or cost of goods offset account.
4182 A bulk product gain/loss AAI that determines the
bulk inventory offset account.
4184 A bulk product gain/loss AAI that determines the
expense or cost of goods offset account.
2.9.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up companies.
■ Verify transaction types in UDC table (00/DT).
■ Set up document types in UDC table (00/DT).
■ Set up GL class codes in UDC table (41/9).
■ Set up accounts.
See "Setting Up Organizations" in the JD Edwards EnterpriseOne Applications Financial
Management Fundamentals Implemenation Guide.
See "Creating the Chart of Accounts" in the JD Edwards EnterpriseOne Applications
Financial Management Fundamentals Implemenation Guide.
2.9.5.1 Defaults
AAI Table Number
Specify the default value that the system displays in the Skip To AAI field.
Co (company)
Enter a code that identifies a specific organization, fund, or other reporting entity. The
company code must already exist in the Company Constants table (F0010) and must
identify a reporting entity that has a complete balance sheet. At this level, you can
have intercompany transactions.
Note: You can use company 00000 for default values, such as dates
and AAIs. You cannot use company 00000 for transaction entries.
Do Ty (document type)
Enter a code from UDC table (00/DT) that identifies the origin and purpose of the
transaction. The system reserves several prefixes for document types, such as
vouchers, invoices, receipts, and time sheets.
Branch Plant
Enter an alphanumeric code that identifies a separate entity within a business for
which you want to track costs. For example, a business unit might be a warehouse
location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for purposes of
responsibility reporting. For example, the system provides reports of open accounts
payable and accounts receivable by business unit to track equipment by responsible
department.
Business unit security might prevent you from viewing information about business
units for which you have no authority.
If you leave this field blank, the system uses the business unit in the Charge to Cost
Center field on the work order.
Note: If you use a flexible chart of accounts and the object account is
set to six digits, you should use all six digits. For example, 000456 is
not the same as 456 because, if you enter 456, the system enters three
blank spaces to fill a six-digit object.
Sub (subsidiary)
Enter a subset of an object account. Subsidiary accounts include detailed records of the
accounting activity for an object account.
Note: If you are using a flexible chart of accounts and the object
account is set to six digits, you must use all six digits. For example,
entering 000456 is not the same as entering 456. If you enter 456, the
system enters three blank spaces to fill a six-digit object.
If you leave this field blank, the system uses the value in the Cost Code field on the
work order.
includes item information that applies throughout the branch, such as category codes
and planner/buyer numbers. When you enter branch/plant information for an item,
the JD Edwards EnterpriseOne Inventory Management system creates records in the
Item Branch File (F4102) and the Item Location File (F41021), which includes item
information that is specific to certain locations, such as on-hand quantities and General
Ledger GL class codes.
3.1.1 Prerequisites
Before you complete the tasks in this chapter, you must:
■ Review and modify branch/plant constants.
See "Setting Up Next Numbers" in the JD Edwards EnterpriseOne Applications
Financial Management Fundamentals Implemenation Guide.
■ Set up default locations and printers.
See Setting Up Default Location Information.
■ Set up applicable user-defined codes (UDCs), including:
– GL class codes in UDC table (41/9).
– Stocking type codes in UDC table (41/I).
– Units of measure in UDC table (00/UM).
– Classification code categories
– Cost method codes
– Language preference codes in UDC table (01/LP).
See Also:
■ "Working With Inventory Management for Brazil" in the JD
Edwards EnterpriseOne Applications Localizations for Brazil
Implementation Guide.
■ "Setting Up Localizations for Brazil" in the JD Edwards
EnterpriseOne Applications Localizations for Brazil Implementation
Guide.
If you work with an item in multiple units of measure, you must specify how to
convert one unit of measure to another. For example, if you stock items in boxes and
crates, you must specify the number of individual items in a box and the number of
boxes in a crate.
In some instances, the JD Edwards EnterpriseOne Inventory Management system
must work with an item in its smallest (primary) unit of measure. The item
conversions that you specify must enable the JD Edwards EnterpriseOne Inventory
Management system to trace all units of measure back to the primary unit of measure.
You can set up unit of measure conversions that are specific to an item or to an item
and branch/plant combination. You specify whether item conversions are specific to a
branch/plant on the System Constants form. You can also set up units of measure that
are standard for all items.
Units of measure for an item are stored in the Item Unit of Measure table (F41002) or
the Unit of Measure Standard Conversions table (F41003). The JD Edwards
EnterpriseOne Inventory Management system verifies the item unit of measure
conversions before using standard unit of measure conversions.
The system converts the dual unit of measure using the special handling code. For a
dual unit of measure item, the special handling code of the primary and secondary
units of measure is different. For similar units of measure, such as ounces, pounds, and
tons, the special handling code is the same. For example, weight might have pounds as
the dual unit of measure. A dual transaction quantity could be entered for tons. In this
case, pounds and tons must have the same special handling code.
The system uses these tables when processing information for dual units of measure:
■ F4101
■ F4111
■ F41021
■ F4602
3.2.1.4 Attachments
Typically, you enter attachments for an item to provide graphical information, such as
a picture or diagram. Unlike item notes, you can view and print attachments
regardless of the language in which those attachments were entered. Therefore, if you
attach a diagram that contains text to an item, the system displays the text only in the
language in which the text was entered.
You can set up an attachment, by selecting Attachments from the Form menu of the
Item Notes Revisions form or selecting Internal Attachment from the Row menu on
the Work With Item Master Browse form.
active ingredient in a product (for example, the percentage of alcohol in cough syrup).
When you activate grade or potency control for an item, you can enter a standard
grade or potency for the item and a range of acceptable values. If you receive or issue
items that are not within the range, the system provides a warning message. You
cannot complete sales transactions on items that are not within the range of acceptable
values.
You can specify an acceptable grade or potency range for each of the customers using
preference profiles. Item grade and potency are applicable only to items that are
produced in lots. You cannot use both grade control and potency control for the same
item. You can specify the grade or potency of all items in a lot on the Work With Lot
Master form. If you do not specify a grade or potency, the system uses the standard
grade or potency from the Additional System Information form.
See Also:
■ "Managing Additive Operations" in the JD Edwards EnterpriseOne
Applications Blend Management Implementation Guide.
3.2.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Verify that Branch/Plant ALL is available.
The system uses Branch/Plant ALL as a source of default information.
■ Set up the special handling code in the UDC table (00/UM).
■ Specify the values for unit of measure in the Sales Price Retrieval UOM and
Purchase Price Retrieval UOM fields on the System Constants form of the
Branch/Plant Constants program (P41001).
See Setting Up Constants.
■ Specify a primary item identifier on the Branch/Plant Constants form.
3.2.5.1 Defaults
1. Primary Unit of Measure
Specify a user-defined code from UDC table (00/UM) that identifies the primary unit
of measure that the system uses. If you leave this processing option blank, the system
uses EA (each).
4. Template
Specify a template name to use when entering items in the Item Master program
(P4101). This name is case-sensitive. If you leave this field blank, the system does not
use a template.
3.2.5.2 Process
1. Notes From Date
Specify the effective-from date that the system uses in the Item Notes table (F4016). If
you leave this processing option blank, the system uses the system date.
3. Category Codes
Specify whether the system displays the Category Codes form when you add or
change information on the Item Master Revisions form. Values are:
Blank: Do not display.
I: Display.
I: Display.
5. Storage/Shipping
Specify whether the system displays the Storage/Shipping form when you add or
change information on the Item Master Revisions form. Values are:
Blank: Do not display.
1: Display.
9. Item Branch
Specify whether the system displays the Item Branch form when you add or change
information on the Item Master Revisions form. Values are:
Blank: Do not display the Item Branch form.
1: Display the Item Branch form, but return to the Item Master form.
2: Display and remain on the Item Branch form.
10. Attachments
Specify whether the system displays the Item Notes form when you select a media
object on the Work With Item Master Browse form. Values are:
Blank: Display only the internal attachments.
1: Display the Item Notes form.
1. Transfer Changes
Specify which tables the system updates when you make changes to item numbers in
the item branch records. Use UDC table (40/IC) to compile the list of tables. Values
are:
Blank: The system does not update any tables.
1: The system updates only those tables that contain item branch information with
changes to the second and third item numbers.
2: The system updates only selected tables that contain item branch information with
changes to the second and third item numbers.
3.2.5.4 Versions
If you leave any of the following processing options blank, the system uses version
ZJDE0001.
3.2.5.5 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the default
transaction type, such as an invoice or a sales order, the system uses. If you leave this
processing option blank, the system does not perform outbound interoperability
processing.
3.2.5.6 Style
1. Additional Style Item Information
Specify whether the system displays the Additional Style Item Information form
(WCW45A) when you add or change information on the Item Master Revisions form
for a style item. Values are:
Blank: Do not display the form.
1: Display the form.
2. Composition
Specify whether the system displays the Work With Composition form (WCW44A)
when you add or modify style item information on the Item Master Revisions form.
Values are:
Blank: Do not display the form.
1: Display the form.
3. Structure Definition
Specify whether the system displays the Item Structure Definition form (WCW02C)
when you add information on the Item Master Revisions form (W4101A) for a style
item. Values are:
Blank: Do not display the Item Structure Definition form.
1: Display the Item Structure Definition form.
Note: You can also translate item descriptions and search text into
multiple languages to locate items using alternate languages. The
system administrator can make descriptions in other languages
available based on user profiles.
If you revise the second and third item identifiers, the program can transfer these
changes to other selected files, depending on how you activate the related processing
option.
You can also specify the persons or businesses that are responsible for the item,
including the buyers, planners, and preferred carriers. Before you can assign
responsible persons or businesses to an item, each person and business must have an
address book number in the JD Edwards EnterpriseOne Address Book system.
Item Number
Enter an identifier for an item.
Catalog Number
Enter an identifier for an item.
Description
Enter a user-defined description of the item. The system will use this value to search
for items.
Search Text
Enter a user-defined phrase that describes the item. Enter specific and descriptive text
that a user might enter when searching for an item. The system will use this value to
search for items.
In single-byte environments, where computer storage space can hold only Latin-based
language character sets, the system inserts the first 30 characters from the item's
description if you do not enter search text.
In double-byte environments, where computer storage space can hold more complex
language character sets (in languages such as Japanese, Chinese, and Korean), you
must complete this field. It is a single-byte field that you complete with single-byte
characters to phonetically represent the item description (which can be single-byte,
double-byte, or both).
Stocking Type
Enter a code from UDC table (41/I) that specifies how you stock an item, for example,
as finished goods or as raw materials. Some stocking types are hard-coded and should
not be changed.
In UDC table (41/I), the first character in the Description 2 field indicates whether the
item is purchased, (P), or manufactured, (M).
GL Class
Enter a code from UDC table (41/9) that specifies which general ledger accounts
receive the monetary amount of inventory transactions for this item.
Planner Number
Enter the address number of the material planner for this item.
Buyer Number
Enter the address number of the person responsible for setting up and maintaining the
correct stocking levels for the item.
Backorders Allowed
Select this check box to enable backorders for this item. You can enable backorders by
item in the Item Master (P4101) program or the Item Branch/Plant (P41026) program,
by customer in the Customer Billing Instructions program (P03013), or by
branch/plant in the Branch/Plant Constants program (P41001).
Check Availability
Select this check box to enable availability checking. You might want to enable
availability checking for certain items. For other items, if you assume that an adequate
supply is available, leave availability checking disabled.
C group: If an item's value causes the accumulated total to exceed the B accumulated
percentage, the system assigns the item to the C group. The percentage that you
usually enter for the C group is 999.
Language Preference
Enter a user-defined code from UDC table (01/LP) that specifies the language to use
on forms and printed reports. Before you specify a language, a code for that language
must exist at either the system level or in the user preferences.
Print Message
Enter a code from UDC table (40/PM) that represents a predefined message from the
Print Message Revisions form. You can print the message on sales orders, purchase
orders, and so forth.
Item Number
Enter a number that the system assigns to an item. It can be in short, long, or
third-item number format.
Effective Date
Enter the date when a transaction, contract, obligation, preference, or policy rule
becomes effective.
Effective Date
Enter the date on which a transaction, text message, agreement, obligation, or
preference has expired or been completed.
Sub Section
Enter a code from UDC table (41/S2) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
This field is one of 10 classification categories that are available primarily for sales
purposes.
This value serves as the carrier default when you enter a purchase order for the item.
Category Code 6
Enter a code from UDC table (41/S6) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
This field is one of 10 classification categories that are available primarily for sales
purposes.
Category Code 7
Enter a code from UDC table (41/S7) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
This field is one of 10 classification categories that are available primarily for sales
purposes.
Category Code 8
Enter a code from UDC table (41/S8) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
This field is one of 10 classification categories that are available primarily for sales
purposes.
Category Code 9
Enter a code from UDC table (41/S9) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
This field is one of 10 classification categories that are available primarily for sales
purposes.
Category Code 10
Enter a code from UDC table (41/S0) that represents an item property type or
classification, such as color or material content. The system uses this code to sort and
process like items.
Use this field as one of 10 classification categories that are available primarily for sales
purposes.
Primary
Enter a code from UDC table (00/UM) that indicates the primary unit of measure for
the item. The primary unit of measure must be the smallest unit of measure in which
you handle the item.
This is the PSAU of measure that the system uses to store all inventory. If you change
the primary unit of measure, the conversion factors in the item-level conversion table
are no longer valid.
The default value for this field is the unit of measure that you specify for the item on
the Item Master Revisions form.
Secondary
Enter a code from UDC table (00/UM) that indicates an alternate unit of measure for
the item.
Purchasing
Enter a code from UDC table (00/UM) that identifies the unit of measure in which you
usually purchase the item.
Pricing
Enter a code from UDC table (00/UM) that indicates the unit of measure in which you
usually price the item.
Shipping
Enter a code from UDC table (00/UM) that indicates the unit of measure in which you
usually ship the item.
Production
Enter a code from UDC table (00/UM) that indicates the unit of measure in which you
produce the item.
Component
Enter a code from UDC table (00/UM) that indicates the unit of measure for an item
when the item serves as a component, for example, for a bill of material or work order
parts list.
Weight
Enter a code from UDC table (00/UM) that identifies the unit of measure that the
system uses to indicate weight for this item. As weight standards, you can specify
ounces, grams, kilograms, and so on. The system uses this unit of measure for the item
or overrides it for an individual item or container.
The default value for this field is the weight unit of measure that you specify in
processing options for the Item Master program.
Volume
Enter a code from UDC table (00/UM) that indicates the unit of measure by metric
conversion for ambient volume. For example, the unit of measure code for a gallon
might be GL, or for a liter it might be LT.
Quantity
Enter the factor that the system uses to convert one unit of measure to another unit of
measure.
Secondary
Enter a code from UDC table (00/UM) that indicates an alternate unit of measure for
the item.
Note: For a dual unit of measure item, the system might require a
tolerance check for inventory transactions (excluding inventory
adjustments) between the primary unit of measure and the secondary
unit of measure.
Note: For a dual unit of measure item, the system might require a
tolerance check for inventory transactions (excluding inventory
adjustments) between the primary unit of measure and the secondary
unit of measure.
The system uses the conversion factors to convert adjustments into the other unit of
measure. For example, if the system locates an adjustment using the transaction unit of
measure, the system also displays the pricing unit of measure. The system uses the
unit of measure conversion factors to recalculate the adjustment in the pricing unit of
measure
You can set up two price unit of measure sequences: one for sales and another for
procurement.
The system uses these tables for processing search sequences using units of measure:
■ F41001
■ F41002
■ F4072
■ F4106
See Also:
■ "Configuring the Sales Order Management System" in the JD
Edwards EnterpriseOne Applications Sales Order Management
Implementation Guide.
■ "Setting Up UCC 128 Compliance" in the JD Edwards EnterpriseOne
Applications Sales Order Management Implementation Guide.
■ "Setting Up Bulk Items" in the JD Edwards EnterpriseOne
Applications Bulk Stock Inventory Implementation Guide.
Note: If you enter a order policy code other than 2,4, or 5, the value
has no significance in MRP.
Planning Code
Enter a user-defined code from UDC table (H41/MP) that indicates how MPS, MRP, or
DRP processes this item. The hard coded values are:
0: Not planned by MPS, MRP, or DRP.
1: Planned by MPS or DRP.
2: Planned by MRP.
3: Planned by MRP with additional independent forecast.
4: Planned by MPS, Parent in Planning Bill.
5: Planned by MPS, Component in Planning Bill.
Planning Fence
Enter the number of days that the system uses in conjunction with the time fence rule
to determine how the forecast is used. Enter the number of days after the start date
when the time fence rule changes from the first rule to the second rule.
For example, if the planning fence rule is S, the generation start date is 01/03/05, and
the planning time fence is three days, the system plans using customer demand
through 01/06/05. Beginning on 01/07/05, the system plans using the forecast.
Note: The system does not count the generation start date; that is,
the day after the generation start date is day 1.
For manufactured items, the system counts working days, as defined
in the calendar in the JD Edwards EnterpriseOne Shop Floor
Management system. For purchased items, the system counts calendar
days.
Freeze Fence
Enter the number of days from the generation start date within which the system does
not generate action messages.
For example, if the generation start date is 01/03/05, and the freeze time fence is three
days, the planning system does not generate messages with required dates that are
before or equal to 01/06/05.
Note: The system does not count the generation start date; that is,
the day after the generation start date is day one.
For manufactured items, the system counts working days, as defined
in the calendar in the JD Edwards EnterpriseOne Shop Floor
Management system.
For purchased items, the system counts calendar days.
Note: The system does not count the generation start date; that is,
the day after the generation start date is day one.
For manufactured items, the system counts working days, as defined
in the calendar in the JD Edwards EnterpriseOne Shop Floor
Management system.
For purchased items, the system counts calendar days.
Replenishment Hours
Enter the time that is required before a consuming location has a replacement kanban
available from its supplying location.
This value is used only for kanban card processing in the JD Edwards EnterpriseOne
Shop Floor Management system.
Leadtime Level
Enter a value that represents the leadtime for an item at its assigned level in the
production process, as defined on Plant Manufacturing Data. The system uses this
value to calculate the start dates for work orders using fixed leadtimes. Level leadtime
is different for purchased and manufactured items:
Purchased: The number of calendar days that are required for the item to arrive at the
branch/plant after the supplier receives the purchase order.
Manufactured: The number of workdays that are required to complete the fabrication
or assembly of an item after all the components are available.
You can enter level leadtime manually on the Plant Manufacturing tab of the
Additional System Information form, or you can use the Leadtime Roll up program to
calculate it. To calculate level leadtime using the Leadtime Roll up program, you must
first enter a quantity in the Manufacturing Leadtime Quantity field in the F4102 table.
Leadtime Manufacturing
Enter the total number of days that are required to build an item from its lowest level
components to the final assembly. This value is the total of the level leadtimes for all
manufactured items, plus the highest manufacturing leadtime for all its components.
If all components are purchased, the manufacturing leadtime equals the item's level
leadtime. Purchased item leadtimes are not included in the calculation of
manufacturing leadtimes.
You can enter the manufacturing leadtime manually, or you can have the system
calculate it when you run the Leadtime Roll up program.
Leadtime Cumulative
Enter the total number of days that are required to build an item from its lowest level
components to the final assembly. The system calculates the value differently for
manufactured and purchased items.
Manufactured: The total of all level leadtimes for all manufactured items, plus the
highest cumulative leadtime of all its components.
Purchased: The item's level leadtime. Purchased item leadtimes are included in the
calculation of cumulative leadtimes.
You can enter this value manually, or you can have the system calculate it when you
run the Leadtime Roll up program.
Fixed/Variable
Enter a user-defined code from UDC table (H41/MS) that determines whether the
system uses fixed or variable leadtimes. This value works in conjunction with the
value from either the Level Leadtime field or the Leadtime Per Unit field. Values are:
F: The system calculates work order start dates using the value from the Leadtime
Level field.
V: The system calculates work order start dates using the value from the Leadtime Per
Unit field.
Drawing Size
Enter a code that represents the engineering drawing size. For example:
A: A-size drawing
D: D-size drawing
Drawing Number
Enter an engineering drawing number. This number might be the same as the part or
item number.
Grade/Potency Pricing
Enter a user-defined code from UDC table (41/05) that groups several items that
contain the same requirements for the Stock Valuation system. Valuation methods are
set up by item or pool. The items that are assigned to the pool use the pool's
designated valuation methods for extracting and valuing the inventory.
Potency Control
Enter a value that specifies whether you control the item by potency. Values are:
N: Do not control the item by potency.
Y: Control the item by potency.
Standard Potency
Enter the percentage of active ingredients that are normally found in an item.
Grade Control
Enter a code that indicates whether you control the item by grade.
N: Do not control the item by grade.
Y: Control the item by grade.
Standard Grade
Enter a user-defined code from UDC table (40/LG) that represents the normal grade
for an item.
3.2.15.3 Service/Warranty
Select the Service/Warranty tab.
Cost Type
Enter a user-defined code from UDC table (30/CA) that designates the item. Values
include:
A1: Material
B1: Labor
X1: Freight
X2: Travel
Return Policy
Enter a user-defined code from UDC table (17/RT) that specifies whether to return the
part with the claim.
Constraints Flag
Enter a user-defined code from UDC table (42/AC) that specifies whether to include
an item in Supply Chain Planning (SCP). Values are:
Sellable Item
Specify whether an item is sellable. Use the Update Sellable Flag program (R41900) to
update this field for multiple items.
Operational Threshold
Enter the minimum and maximum threshold values for the active ingredient of an
additive that you use in the JD Edwards EnterpriseOne Blend Management system.
Threshold information is not required. You can use operational thresholds, cumulative
thresholds or both.
The system compares this value with the quantity of active ingredient in the current
operation and issues a warning if the quantity is below the minimum value or above
the maximum value in an active operation. For actual or closed operations, the system
generates an error.
You enter the operational or the cumulative threshold values using a unit of measure
from the Blend Management Unit of Measure UDC table (31B/UM).
Cumulative Threshold
Enter the minimum and maximum cumulative threshold values for the active
ingredient of an additive that you use in the JD Edwards EnterpriseOne Blend
Management system. The system compares this value with the PPM quantity of the
accumulated additives for the operation and issues a warning if the quantity is below
the minimum value or above the maximum value in an active operation. For actual or
closed operations, the system generates an error.
Primary Line
Enter a number that you have previously set up in the F30006 table to define which
product line primarily produces the end item. You can define detailed work center
operations within the line or cell.
The functionality of this option applies only when the item is a Demand Flow item
and you are performing BOM explosion using the Volume Design and Product
Synchronization program (PF30L201). Normal BOM explosion remains as it is in base
manufacturing.
See Also:
■ "Working with Item Information and Inventory Inflation
Adjustment" in the JD Edwards EnterpriseOne Applications
Localizations for Argentina Implementation Guide.
See Also:
■ "Setting Up Bulk Depots" in the JD Edwards EnterpriseOne
Applications Bulk Stock Inventory Implementation Guide.
■ "Setting Up Bulk Items" in the JD Edwards EnterpriseOne
Applications Bulk Stock Inventory Implementation Guide.
■ Setting Up Allowed Lot Status Codes.
■ Setting Up Manufacturing Information.
3.3.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up the origin of imported items in UDC table (41/L9).
3.3.4.1 Process
These processing options specify whether the system displays additional Item Branch
forms when you add or change information on the Item Branch/Plant Info. form.
1. Category Codes
Specify whether to display the Category Codes form when you add or change
information. Values are:
Blank: Do not display.
1: Display.
2. Quantities
Specify whether to display the Quantities form when you add or change information.
Values are:
Blank: Do not display.
1: Display.
5. Cost Revisions
Specify whether to display the Cost Revisions form when you add or change
information. Values are:
Blank: Do not display.
1: Display.
6. Price Revisions
Specify whether to display the Price Revisions form when you add or change
information. Values are:
Blank: Do not display.
1: Display.
7. Unit of Measure
Specify whether to display the Unit of Measure form when the unit of measure
conversions are at the branch level and you are adding or changing information.
Values are:
Blank: Do not display.
1: Display.
3.3.4.2 Versions
If you leave either of the following processing options blank, the system uses version
ZJDE0001.
3.3.4.3 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the default
transaction type, such as an invoice or a sales order. You can enter a transaction type or
select one from the Select User Define Code form.
If you leave this processing option blank, the system does not perform export
processing.
Branch/Plant
You must enter a branch/plant number that is set up in the F41001 table.
Location
Enter the area in the warehouse where you receive inventory. The format of the
location is user defined, and you enter the location format for each branch/plant.
Lot/Serial
Enter a number that identifies a lot or a serial number. A lot is a group of items with
similar characteristics.
To assign a secondary location to an item, enter the location and lot/serial information.
Sales Taxable
Enter a code from UDC table (H00/TV) that indicates whether the item is subject to
sales tax when you sell it. The system calculates tax on the item only if the customer is
also taxable.
Purchasing Taxable
Enter a code from UDC table (H00/TV) that indicates whether the item is subject to
sales tax when you purchase it. The system calculates tax on the item only if the
supplier is also taxable.
See Also:
■ "Entering Sales Orders" in the JD Edwards EnterpriseOne
Applications Sales Order Management Implementation Guide.
Supplier Number
Enter a user-defined name or number that identifies an address book record. You can
use this number to locate and enter information about the address book record. If you
enter a value other than the address book number (AN8), such as the long address or
tax ID, you must precede it with the special character that is defined in the Address
Book constants. When the system locates the record, it returns the address book
number to the field.
For example, if address book number 4100 (Total Solutions) has a long address TOTAL
and an * distinguishes it from other entries (as defined in the Address Book constants),
you could type *TOTAL into the field, and the system would return 4100.
Country of Origin
Enter a code from UDC table (00/CN) that identifies the country in which an item
originates. This information is useful to organizations that must periodically separate
their inventory by source. You can specify your home country as the default value in
UDC table (00/CN).
Reorder Quantity
Enter the estimated reorder quantity for an item. You can enter this quantity if the
system does not have enough sales history to accurately calculate a reorder quantity.
Maximum Reorder Qty (maximum reorder quantity) and Minimum Reorder Qty
(minimum reorder quantity)
Enter the maximum and minimum order quantities for an item. You can calculate the
quantity on factors other than usage, such as perishability, storage capacity, and so
forth.
Reorder Point
Enter a quantity for an item that specifies when replenishment occurs. Typically, this
occurs when the total quantity on hand plus the quantity on order fall to or lower than
a specified quantity. You can enter this quantity, or the system can calculate the
quantity if a sufficient sales history is available.
Safety Stock
Enter the quantity of stock that is kept on hand to cover high-side variations in
demand.
Most of the items on Plant Manufacturing Data tab are identical to those on
Manufacturing Data. The system uses the default values that you specified on
Manufacturing Data.
Shrink Factor
Enter a fixed quantity or percentage that the system uses to determine inventory
shrinkage for an item. If you are entering a percentage, enter 5 percent as 5.00 and 50
percent as 50.00.
The system increases the planned order quantity by this amount in MPS/MRP/DRP
generation. The shrink factor method that you specify for the item determines whether
the shrink factor is a percentage or a fixed quantity.
Replenishment Hours
Enter the time that is required before a consuming location has a replacement kanban
available from its supplying location.
This value is used only for kanban card processing in the JD Edwards EnterpriseOne
Shop Floor Management system.
Setup Labor
Enter the standard setup hours that you expect to incur in the normal completion of
this item. This value is not affected by crew size.
Queue Hours
Enter the total hours that an order is expected to be in queue at work centers and
moving between work centers.
The system stores this value in the F4102 table. You can calculate this value using the
Leadtime Roll up program, or you can enter it manually. When you run the Leadtime
Roll up program, the system overrides manual entries and populates the table with
calculated values.
Time Basis
Enter a code from UDC table (30/TB) that indicates how machine or labor hours are
expressed for a product. Time basis codes identify the time basis or rate to be used for
machine or labor hours that are entered for every routing step. Examples are 25 hours
per 1,000 pieces and 15 hours per 10,000 pieces. You can maintain the time basis codes
in Time Basis Codes.
The system uses the values in the Description-2 field for costing and scheduling
calculations. The description is what the code represents, but is not used in
calculations.
Kanban Item
Identify an item as a kanban item.
3.3.13.1 Defaults 1
Branch One through Branch Six
Specify the branch/plants to which you want to duplicate the items.
3.3.13.2 Default 2
Branch Seven through Branch Ten
Specify the branch/plants to which you want to duplicate the items.
3.3.13.3 Process
Enter 1 to duplicate the file. If you leave this processing option blank, the system will
not duplicate the file.
See Also:
■ Setting Up Warehouse Locations.
■ Pricing rules
■ Preferences
You can use segments to accommodate these types of items, for example:
■ Polo shirts with segments of size and color.
■ Fruit drinks with segments of flavor, packaging, and type.
A segmented item can have up to 10 identifying characteristics or attributes.
Template
Enter a template name that you can use when entering items on the Item Master
Revisions form. This name is case-sensitive. If you use any capital letters in the
template name when you add it, you must enter those letters in capitals whenever you
search for or attach the template to the Item Master Revisions form.
No Separators
Select this check box if separators are not used in this template and all 25 character
spaces can be allotted to the segmented item number.
Note: You must also leave the Segment Separator Character field in
the Branch/Plant Constants program (P41001) blank.
Length Used
Enter a running total of the number of spaces, including separators, that are used in all
the segments.
3.5.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Complete the Segment Separator Character field if you want to use all 25
characters; otherwise, this information is populated in the Branch/Plant Constants
program (P41001).
■ Set the appropriate processing options for the matrix version to be used in the
Item Branch Duplication - Batch Selection (R41826) program to copy item cost,
item price, and unit of measure conversion information.
■ Create a template that contains the product attributes.
See Creating a Template for Segmented Items.
■ To enter orders, set the appropriate processing option in the Sales Order Entry
(P4210) or the Purchase Orders (P4310) programs.
3.5.5.1 Versions
If you leave either of the following processing options blank, the system uses version
ZJDE0001.
3.5.7.1 Display
1. Display quantities
Specify whether to display quantities. Values are:
Blank: Do not display quantity on hand or available items.
1: Display quantity on hand.
2: Display quantity available.
3: Display both.
3.6.3.1 Process
Standard Cost
Specify whether to change the standard cost. Values are:
Blank: Change.
1: Do not change.
3.6.3.2 Interop
Transaction Type
Specify a user-defined code from UDC table (00/TT) that specifies the transaction type
for the interoperability transaction. If you leave this processing option blank,
outbound interoperability processing is not performed.
See Also:
■ "Generating Supplier Prices in an Alternate Currency" in theJD
Edwards EnterpriseOne Applications Procurement Management
Implementation Guide.
Sales/Inventory
Enter a code from UDC table (40/CM) that indicates the cost method that the system
uses to calculate the cost of goods that is sold for the item. Cost methods 01–19 are
reserved.
If you maintain costs at the item level, the system retrieves the default value for this
field from the data dictionary. If you maintain costs at the item and branch/plant level,
the system retrieves the default value from Branch/Plant Constants (P41001) program.
Purchasing
Enter a code from UDC table (40/CM) that indicates the cost method that the system
uses to determine the cost of the item for purchase orders. Cost methods 01–19 are
reserved.
If you maintain costs at the item level, the system retrieves the default value for this
field from the data dictionary. If you maintain costs at the item and branch/plant level,
the system retrieves the default value from Branch/Plant Constants (P41001) program.
Cost Method
Enter a code from UDC table (40/CM) that specifies the basis for calculating item
costs. Cost methods 01–19 are reserved.
Unit Cost
Enter an amount for each cost method. When you review costs for the item, the system
displays only those methods for which you entered an amount.
See Also:
■ Entering a Bill of Material.
■ "Setting Up Base and Standard Pricing" in the JD Edwards
EnterpriseOne Applications Sales Order Management Implementation
Guide.
Component B: 100
Configured Cost Adjustment 1: 15
Configured Cost Adjustment 2: 10
Advanced Price Discount: 10 percent
Methods:
1: 50 + 100 = 150 + 15 + 10 = 175 −17.50 = 157.5
2: 12 + 1510 = 150 −15 = 135
3: 15 + 10 + 25 −2.5 = 22.5
4: (50 −5) + (100 - 10) = 135 + 15 + 10 = 160
Enter sales prices for an item by entering an amount for the unit of measure, currency,
and effective dates for which the price is applicable. You also can enter a currency code
for a price if you use multiple currencies.
Unit Price
Enter the list or base price to be charged for one unit of this item. In sales order entry,
you must set up all prices in the F4106 table.
Credit Price
Enter credit orders in the JD Edwards EnterpriseOne Sales Order Management system.
To enter a credit order, use a line type for which the Reverse Sign Flag (RSGN) is set to
Y in the F40205 table. The system stores all credit prices in the F4106 table.
Percentage
Select this check box if the factor value is a multiplier (percent) when applied to an
order's price.
Amount
Select this check box if the factor value is an additional/deductible amount when
applied to an order's price.
■ F41021
■ F0911
■ F4108
Every transaction affects accounting information in the system if you have set the
branch/plant constant for the general ledger interface. The system uses automatic
accounting instructions (AAIs) to update the general ledger with all of the accounting
information that is related to transactions. AAIs direct inventory transactions to a
specific account in the GL.
Use these programs to review the updated accounting information when you are
working with a transaction:
Program Description
General Journal Review (P0911B) Provides information on two levels:
Summary or detailed batch level. The summary level
displays batch information by user, status, number, and
entry date. The detailed level presents batch information
by journal entry, such as the transaction type for the
document.
Individual document level. The individual document
level displays information for each journal entry, such as
the updated account and the amount that is posted to
the account balance.
Journal Entries (P0911) Displays the GL accounts that a transaction is written to
before it is posted.
Item Ledger Inquiry (P4111) Displays all transactions for an item.
See Also:
■ Setting Up AAIs in Distribution Systems.
4.2 Prerequisites
Before you complete the tasks in this chapter, you must verify that the following
information is set up:
■ Item and branch/plant information in the Item Branch File (F4102) and the Item
Location File (F41021) tables.
■ General ledger accounts in the Account Master table (F0901).
See "Creating the Chart of Accounts" in the JD Edwards EnterpriseOne Applications
Financial Management Fundamentals Implemenation Guide.
■ AAIs for distribution transactions.
See Setting Up AAIs in Distribution Systems.
Format Description
Standard format Issue inventory items from a branch/plant.
Equipment format Record inventory that is issued to a specific piece
of equipment.
Subledger format Debit a specific general ledger account for an issue.
Equipment and subledger format Record the specific piece of equipment that was
issued to a job, and debit a specific general ledger
account for an issue.
If you work with a kit, you can issue all of the kit components at once by accessing the
Copy Bill of Material function from the Inventory Issues form. This function enables
you to issue components without affecting the parent item quantity. If you do not use
this function, the parent item quantity might be affected, but the component quantities
remain the same. However, never enter an issue for a kit that contains a feature.
Depending on how you set the processing options, you may be able to issue a quantity
that is greater than the on-hand quantity for the parent item in a kit. The system
displays the parent quantity as a negative number.
You can correct an issue that was made in error by creating a reversing entry. A
reversing entry enters a positive quantity and cost amount back into the item
information. Because records of each inventory transaction are kept for accounting
purposes, you cannot delete the record.
4.3.3.1 Defaults
1. Document Type
Specify a user-defined code from UDC table (00/DT) that specifies the document type.
The default document type is typically II (inventory issues).
If you leave this processing option blank, the system does not provide a default value.
2. Location/Lot
Specify whether the system supplies default values for the Location and Lot Serial
fields. Values are:
Blank: Do not supply default values.
1: Supply the default values.
Note: You can use the primary location as the default only if all
secondary locations have a physical location (for example, aisle and
bin). If any of the secondary locations has a blank location and lot, you
cannot set the primary location as the default.
4.3.3.2 Versions
If you leave any of the following processing options blank, the system uses version
ZJDE0001.
4.3.3.3 Process
1. Issue Type
Specify whether equipment and subledger information appears in the detail area of
the Inventory Issues form. Values are:
Blank: Display the standard issue format, without equipment and subledger
information fields. The Inventory Issues program disables the Subledger Information
selection from the Form menu.
1: Display the Equipment field and hide the Account Number,Subledger, and
Subledger Type fields in the detail area. When you select Subledger Information from
the Form menu, the Account Information form displays the Equipment field but does
not display fields for account number and subledger information.
2: Display the Account Number,Subledger, and Subledger Type fields and hide the
Equipment field in the detail area. When you select Subledger Information from the
Form menu, the Account Information form displays the fields for account number and
subledger information, but does not display the Equipment field.
3: Display the Equipment,Account Number,Subledger, and Subledger Type fields in
the detail area. When you select Subledger Information from the Form menu, the
Account Information form displays fields for equipment, account number, and
subledger information.
Note: If you enter 2 or 3 for this processing option, you can set the
Account Number processing option to require entry in the Account
Number field on the Inventory Issues form.
2. Account Number
Specify whether the system requires entry of account numbers (for example, business
unit.object.subsidiary) in the detail area of the Inventory Issues form. This field is
available only when you enter 2 or 3 in the Issue Type processing option. Values are:
Blank: Enable transactions that use the expense account from the inventory default
AAI item 4124.
1: Require a value in the Account Number field in the detail area.
3. Cost Entry
Specify whether to display the Unit Cost and Extended Amount fields on the
Inventory Issues form. Values are:
Blank: Display the fields.
1: Display the fields with default values from the F4105 table, but do not enable them
to be updated.
2: Do not display the fields.
4. Journal Entries
Specify whether detailed or summarized journal entries should be created from the
Inventory Issues (P4112) program in the general ledger. Values are:
Blank: Create one journal entry for each detail line in an issue.
1: Create journal entries that are summarized by account number.
If detailed journal entries are created, the system creates one journal entry (debit and
credit) for each detail line in an issue, using a batch type of N. This processing option
affects journal entries in the F0911 table only. The AAIs that are most commonly used
are 4122 (Inventory) and 4124 (Expense or COGS). If you use standard costs, the
system might create journal entries for the variance based on AAI item 4141 (Inventory
or Expense COGS). The F4111 table contains information for each detail line in each
issue regardless of the value of this processing option.
If summarized journal entries by account number are created, the system creates a
summarized debit total and a summarized credit total per account number for all lines
in an issue.
5. Issue Quantity
Specify whether to allow an issue quantity that is greater than the available quantity,
which could result in a negative on-hand quantity. Values are:
Blank: Do not allow.
1: Allow.
6. Lots on Hold
Specify whether the system enables issues to lots that are on hold. If the Lot Status
Code field on the Item/Branch Plant Information form is blank, the lot is not on hold.
Values are:
Blank: Do not enable.
1: Enable.
If you process inventory selection blindly, then the system consumes production
number on hand quantity in the following order:
1. Generic inventory.
2. Inactive production numbers.
3. Orphaned production numbers.
4. Production number with the farthest end item demand date.
If you process inventory selection interactively, then you can select the production
number from the options available on the Select Inventory for Consumption form
(W42054A). Values are:
Blank: The program performs blind selection of inventory.
1: The program enables interactive selection of inventory.
4.3.3.4 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that specifies the transaction type
to use when creating outbound interoperability transactions. If you leave this
processing option blank, the system does not perform outbound interoperability
processing.
4.3.3.5 Agreement
1. Agreement Assignment (FUTURE)
Specify how the system searches for agreements. This processing option applies only if
you are using the JD Edwards EnterpriseOne Inventory Management system with the
JD Edwards EnterpriseOne Agreement Management system from Oracle. Values are:
Blank: Do not search for agreements.
1: Display one agreement. If the system finds multiple agreements, the system displays
a check mark in the row header that is located in the detail area and in the Agreement
Exists column, and you must select an agreement.
2: Display all agreements.
3: Search for and display the agreement that has the earliest expiration date.
Note: If you attempt to issue quantity from a lot where lot master
record does not have a country of origin and the item branch requires
a country of origin, the system displays an error message.
Secondary Quantity
If the secondary unit of measure option in Inventory Constants is selected, this field
appears on data entry screens.
4.4.3.1 Defaults
1. Document Type
Specify a user-defined code from UDC table (00/DT) that identifies the default
document type for inventory adjustments. Typically, the default is document type IA
(inventory adjustments). If you leave this processing option blank, the system does not
enter a default document type.
2. Location/Lot
Specify whether to the system uses a default location when entering adjustments.
Values are:
Blank: Do not provide default values for the location and lot fields.
1: Use the primary location and lot as the default values. You can use the primary
location as the default only if all secondary locations have a physical location (for
example, aisle and bin). If any of the secondary locations have blank location or lot,
you cannot set the primary location as the default.
4.4.3.2 Versions
If you leave any of the following processing options blank, the system uses the version
ZJDE0001.
4.4.3.3 Process
1. Cost Entry
Specify whether to display the Unit Cost and Extended Amount fields on the
Inventory Adjustments form and whether they can be updated. Values are:
Blank: Display the fields.
1: Display the fields with default values from the F4105 table but do not enable them to
be updated.
2: Do not display the fields.
2. Journal Entries
Specify whether detailed or summarized journal entries are created for the general
ledger. For summarized journal entries, the system creates a summarized debit total
and a summarized credit total by account number for each line in an adjustment. For
detailed journal entries, the system creates one journal entry (debit and credit) for each
line in an adjustment.
The Inventory Adjustments (P4114) program creates batch type N. This processing
option affects journal entries for the F0911 table only. The AAIs that are most
commonly used are 4122 (inventory valuation account) and 4124 (expense or cost of
goods sold account). If you use standard costs, the system might create journal entries
for the variance, based on AAI 4141. The F4111 table contains entries for each detail
line in each adjustment regardless of how you set this processing option. Values are:
Blank: Create one journal entry (debit and credit) for each detail line in an adjustment.
1: Create journal entries that are summarized by account number.
4. Adjustment Quantity
Specify the way the system validates a transaction that results in a negative quantity.
Values are:
Blank: Do not enable negative quantity available.
1: Enable negative quantity available.
2: Do not enable negative quantity on-hand.
5. Lots on Hold
Specify whether to enable adjustments to lots that are on hold. If the Lot Status Code
field on the Item/Branch Plant Information form is blank, the lot is not on hold. Values
are:
Blank: Do not enable adjustments.
1: Enable adjustments.
4.4.3.4 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the transaction
type that the system uses when creating outbound interoperability transactions. If you
leave this processing option blank, the system does not perform outbound
interoperability processing.
4.4.3.5 Agreement
1. Agreement Assign (agreement assignment) (FUTURE)
Specify how the system searches for agreements when you are using the JD Edwards
EnterpriseOne Inventory Management system with the JD Edwards EnterpriseOne
Agreement Management system from Oracle. Values are:
Blank: Do not search for agreements.
1: Display one agreement. If the system finds multiple agreements, the system displays
a check mark in the row header of the line and in the Agreement Exists column. You
must select an agreement.
2: Search for and display all agreements.
3: Search for and display the agreement that has the earliest expiration date.
4.4.3.6 Warehouse
These processing options determine how the system processes license plate numbers
when transferring inventory.
You can also enter the license plate number from which to transfer inventory. If the
branch/plant in the To Branch/Plant field has license plates functionality activated,
you use the processing options Warehouse Control and license plate branch/plant
constants to process license plate information for the To Location value.
4.5.3.1 Defaults
If you leave these processing options blank, the system does not supply default values
during transaction entry.
1. Document Type
Specify a user-defined code from UDC table (00/DT) that specifies the default
document type for transfers. The default document type is typically IT (inventory
transfers).
2. FROM Location/Lot
Specify the primary location and lot as the default location for the From Location and
From Lot/Serial fields when you are entering a transfer. Values are:
Blank: Do not supply default values for the From Location and From Lot/Serial fields.
1: Use the primary location and lot as the default value for the From Location field.
Note: You can use the primary location as the default only if all
secondary locations have a physical location (for example, aisle and
bin). If any of the secondary locations have blank location or lot, you
cannot set the primary location as the default.
3. TO Location/Lot
Specify the primary location and lot as the default location for the To Location and To
Lot Number fields when you are entering a transfer. You can use the primary location
as the default location only if all secondary locations have a physical location (for
example, aisle and bin). If any of the secondary locations has a blank location and lot,
you cannot set the primary location as the default. Values are:
Blank: Do not provide default values for the To Location and To Lot Number fields.
1: Use the primary location and lot as the default for the To Location field.
4.5.3.2 Versions
If you leave either of these processing options blank, the system uses the version
ZJDE0001.
4.5.3.3 Process
1. Cost Entry
Specify whether to display the To Unit Cost and To Extended Amount fields on the
Inventory Transfers form. Values are:
Blank: Display the fields.
1: Display the fields with default values from F4105, but do not enable them to be
updated.
2. Journal Entries
Specify whether to use detailed or summarized journal entries in the general ledger
from the Inventory Transfers (P4113) program. For summarized journal entries, the
system creates a summarized debit total and credit total per account number for all
lines in a transfer. For detailed journal entries, the system creates one journal entry
(debit and credit) for each detail line in a transfer.
The batch type that the Inventory Transfers program creates is N. This processing
option affects journal entries for the F0911 table only. The AAIs that are most
commonly used are 4122 (Inventory) and 4124 (Expense or COGS). If you use standard
costs, the system might create journal entries for the variance, based on AAI 4141
(Inventory or Expense/COGS). The F4111 contains entries for each detail line in each
transfer regardless of the way that you set this processing option. Values are:
Blank: Create one journal entry (debit and credit) for each detail line.
1: Create journal entries that are summarized by account number.
3. Lots on Hold
Specify whether to enable transfers from and to lots that are on hold. If the Lot Status
Code field on the Item/Branch Plant Information form is blank, the lot is not on hold.
Values are:
Blank: Do not enable transfers.
1: Enable transfers.
4. Transfer Quantity
Specify whether to enable the transfer of quantities that results in a negative on-hand
quantity. In this case, the quantity of the transfer is greater than the on-hand quantity.
Values are:
Blank: Do not enable.
1: Enable.
4.5.3.4 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the transaction
type that the system uses when creating outbound interoperability transactions. If you
leave this processing option blank, the system does not perform outbound
interoperability processing.
4.5.3.5 Agreement
1. Agreement Assignment (FUTURE)
Specify how the system searches for agreements when you are using the JD Edwards
EnterpriseOne Inventory Management system with the JD Edwards EnterpriseOne
Agreement Management system from Oracle. Values are:
Blank: Do not search for agreements.
1: Display one agreement. If the system finds multiple agreements, the system displays
a check mark in the row header of the line and in the Agreement Exists column. You
must select an agreement.
2: Search for and display all agreements.
3: Search for and display the agreement that has the earliest expiration date.
4.5.3.6 Warehouse
These processing options determine how the system processes license plate numbers
when transferring inventory.
Quantity Definition
Available The number of items that you can use based on
user-defined calculations. You determine how the system
calculates item availability by defining the factors that
subtract from or add to the available quantity of an item.
This calculation can include quantities that do not
immediately affect on-hand amounts.
For example, you can set up the availability calculation to
subtract any quantities that are committed to sales or work
orders and add any quantities that are on purchase orders
or in transit.
On-hand The number of items (expressed in the primary unit of
measure) that are physically in stock. The on-hand
quantity of items is affected by:
■ Variances that are recorded after a physical inventory.
■ Daily removals, additions, or transfers of items.
■ Shipment confirmations or updated sales information.
■ Locations with lots on hold, such as items requiring
inspection or placed in quarantine.
Available to promise (ATP) The number of items that are uncommitted (available for
sales or distribution) until the next replenishment orders
arrive.
You select whether to use the basic method or the
cumulative method to determine ATP.
The basic method assumes:
■ Customer demand only, such as sales orders.
■ Demand for all periods until the next replenishment
order arrives, such as purchase orders.
■ Complete consumption of existing quantities during
the current period, resulting in no carry-over
quantities for the next period.
When you use the cumulative method, which provides a
running total, the system:
■ Does not assume consumption within the current
period.
■ Does not enable a negative ATP within a period but
does enable a negative cumulative ATP.
Other Quantity 1 and 2 When you commit inventory for other quantities, the
system assigns inventory to different types of sales and
procurement documents, such as quote and blanket
orders, that do not affect availability.
Type Definition
Sources of supply Starting with the requested date on purchase
orders, the system calculates the supply
quantity from these sources:
■ On-hand inventory, where the supply
quantity is the quantity on hand less hard
commitments and quantities on sales and
work orders.
■ Purchase orders, where the supply
quantity is the quantity entered on
purchase orders.
■ Manufacturing work orders, where the
supply quantity is the quantity entered on
a work order less the quantity shipped.
Type Definition
Sources of demand Starting with the requested date on sales
orders, the system calculates the demand
quantity from these sources:
■ Sales orders, where the demand quantity
is the quantity entered on sales orders less
the quantity shipped and the quantity
canceled.
■ Safety stock, where the demand quantity
is any quantity reserved as protection
against fluctuations in demand and
supply.
■ Work order requirements and parts lists,
where the demand quantity for sources
such as the quantity required less the
quantity issued.
See Also:
■ Setting Up Constants.
You can define specific criteria for an item search. Use this type of search when you
know what the item is but you want to limit the search. For example, you can limit the
search for an item to a specific branch/plant and supplier. You can use search text only
to locate items that have search text information in the item master records. You can
set up processing options to display sales or purchasing category codes that are
applicable to items.
When you define search criteria, the system searches these tables for items with
matching information:
5.2.3 Prerequisites
Before you complete the tasks in this section, you must verify that:
■ The item cross-reference types for cross-reference numbers are set up in UDC table
(41/DT).
■ Any external item numbers, such as supplier or substitute numbers, are set up in
the Item Cross-Reference program (P4104).
■ Any internal item numbers, such as the second or third item numbers, are set up
in the Item Master program (P4101).
5.2.6 Setting Processing Options for Item Word Search Build (R41829)
Processing options enable you to specify the default processing for programs and
reports.
Note: If you do not know the item number when you are entering
transactions, use Item Word Search Build (R41829) to locate the item
number.
X-Ref Type
Enter a code from UDC table (41/DT) that identifies the type of cross-reference setup
for this customer. Examples of cross-reference types include substitutes, replacements,
and customer or supplier item numbers.
Address Number
Enter the address number of the customer or supplier.
Card Number
Enter a OEM-assigned value from UDC table (40R/CD) that further describes the part
number.
Calculation Description
Days available Reflects the number of days in the future that an item will
be available.
On-hand Reflects the total number of items in a particular
branch/plant.
Commitments This calculation includes soft commitments, hard
commitments, and quantities on work orders.
Available Defines how the system performs this calculation.
Typically, it includes on-hand quantities minus any
outstanding commitments, reservations, and backorders.
On receipt Reflects quantities that are on open purchase orders.
Reorder point Specifies the minimum item quantity for which
replenishment should occur, or you can have the system
calculate it.
Economic Order Quantity (EOQ) Determines a minimum quantity for an item based on an
economic analysis of the cost of placing an order and
keeping inventory.
■ Enable the Quality Control constant in the Branch/Plant Constants for each
branch plant to include in quality tests.
To review only the records that passed quality testing, set the related processing option
for Summary Availability. In quality mode, you can enter an address book number.
The system does not enable changes to the Branch/Plant, Grade Range, or Potency
Range fields, regardless of the processing options settings. The system displays only
the branches that are set up in the user preferences.
You can set processing options that enable you to:
■ Indicate the available quantity in both primary and requested units of measure
when the requested unit of measure is not the primary unit of measure.
■ Review available information in Shopping Cart mode.
In this mode, the address book number appears. Not all fields that usually appear
in the detail area are available in this mode.
5.3.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Set up the system to calculate availability for manufacturing processes if you are
using the JD Edwards EnterpriseOne Product Data Management system.
See "Setting Up Product Data Management" in the JD Edwards EnterpriseOne
Applications Product Data Management Implementation Guide.
■ Set up location segments.
■ Verify that the system is set up to calculate availability for inventory items.
See Setting Up Constants.
See Also:
■ Reviewing Quantities in Locations with Segments.
5.3.5.1 Versions
If you leave any of the following processing options blank, the system uses the
ZJDE0001 version.
1. Item Master
Specify which version of the Item Master (P4101) program to use.
2. Item Notes
Specify which version of the Item Notes (P40163) program to use.
3. Item Search
Specify which version of the Item Search (P41200) program to use.
8. Bill of Material
Specify which version of the Bill of Material Inquiry (P30200) program to use.
9. Lot Availability
Specify which version of the Lot Master Availability (P41280) program to use.
5.3.5.2 Display
1. Grade Information
Specify whether the system displays grade information. Values are:
Blank: Do not display.
1: Display.
2. Potency Information
Specify whether the system displays potency information. Values are:
Blank: Do not display.
1: Display.
3. Quality Management
Specify whether the system displays information from the JD Edwards EnterpriseOne
Quality Management system. Values are:
Blank: Do not display.
1: Display.
5. Truncate/Round
Specify the manner in which the system truncates or rounds the information in the
detail area. Values are:
Blank: Round the information in the detail area. The system uses normal mathematical
rounding. For example, with no display decimals specified, 2.3 remains 2 and 2.6 is
rounded up to 3.
1: Truncate the information in the grid. The system always removes additional
positions. For example, with no display decimals specified, 2.3 and 2.6 are both
truncated to 2.
2: Round up the information in the grid. The system always rounds to the next higher
number. For example, with no display decimals specified, 2.3 and 2.6 are both rounded
up to 3.
6. Customer Self-Service
Specify whether the system uses the standard mode or customer self-service
functionality. Values are:
Blank: Bypass customer self-service functionality and use the standard mode.
1: Activate customer self-service functionality.
3. Calculation Date
Specify a date that the system uses to calculate the remaining number of days until a
lot expires. If you leave this processing option blank, the system uses today's date.
Note: The system does not display decimal quantities if the Display
Decimals field in the Quantity On Hand-Primary Quantity (PQOH)
data item has no display decimals specified (default).
Summary Only
Select this check box to indicate that the system will display information that is
summarized by item, company, currency code, and cost rule. If you do not select this
check box, the system displays individual receipt records.
On Hand
Enter the number of units that are physically in stock. The system displays the
quantity on-hand in the primary unit of measure.
Committed
Enter the total quantity that is committed to a specific location. The total quantity is
the sum of all quantities that have been sold, soft committed, or hard committed to
sales orders and work orders.
Available
Enter a number that indicates the quantity that is available. For example, the available
quantity might consist of the on-hand quantity minus commitments, reservations, and
backorders.
On Receipt
Enter the total number of items that are on receipt for a specific location. The total is
the sum of all quantities of an item that are on order and in route for a location.
Future Commit
Enter the quantity on sales order for which the requested shipment date is beyond the
standard commitment period that has been specified in the branch/plant constants for
that branch. As an example, if you normally ship most orders within 90 days, then an
order for an item with a requested ship date a year from now would have its quantity
reflected in this field.
Backorder
Enter the number of units that are backordered in primary units of measure.
In Transit
Enter the quantity that is currently in transit from the supplier.
In Inspection
Enter the quantity that is currently being inspected. This quantity is received, but is
not considered on hand.
Grade Range
Enter a code from UDC table (40/LG) that indicates the minimum grade that is
acceptable for an item.
The system displays a warning message if you try to purchase or issue items with
grades that do not meet the minimum grade acceptable. The system does not enable
you to sell items with grades that do not meet the minimum acceptable level.
Potency Range
Enter a number that indicates the minimum potency or percentage of active
ingredients that is acceptable for an item.
The system displays a warning message if you try to purchase or issue items that do
not meet the minimum acceptable potency. The system does not enable you to sell
items that do not meet the minimum acceptable potency.
Future Commit
Enter the quantity on sales order for which the requested shipment date is beyond the
standard commitment period that has been specified in the branch/plant constants for
that branch. As an example, if you normally ship most orders within 90 days, then an
order for an item with a requested ship date a year from now would have its quantity
reflected in this field.
Backorder
Enter the number of units that are back ordered in primary units of measure.
On SO Other 1
Enter the first of two quantities that can be specified as additional offsets (subtractions
from on-hand) in the determination of quantities that are available for sale (primary
unit of measure).
On SO Other 2
Enter the second of two quantities that can be specified as additional offsets
(subtractions from on-hand) in the determination of quantities that are available for
sale (primary unit of measure).
On PO Other 1
Enter the quantity that appears on documents such as bid requests, which are not
formal commitments to buy on the part of the organization.
In Transit
Enter the quantity that is currently in transit from the supplier.
In Inspection
Enter the quantity that is currently being inspected. This quantity is received, but is
not considered on hand.
5.3.8.1 Defaults
1. Template
Enter a template name that you can use when entering items in the Item Master
Revisions (P4101) program. The name is case sensitive.
5.3.8.2 Versions
1. Summary Availability (P41202)
Specify the version of the P41202 program to use. If you leave this processing option
blank, the system uses version ZJDE0001.
5.3.10.1 Mode
Mode
Specify the mode in which to run the program. Values are:
Blank: Client mode
1: Web mode
The system displays only the item and location information that is related to you
based on the user ID and address book number. If you are signed into the system
using the web, Item Availability is disabled.
Summary Only
Select this check box to display individual receipt records. If you do not select this
check box, the system displays information that is summarized by item, company,
currency code, and cost rule.
5.3.12.1 Versions
1. Trace/Track
Specify the version of the Trace/Track Inquiry (P41203) program to use.
5.3.12.2 Display
1. Lot Status
Specify whether to update the lot status. Values are:
Blank: Update.
1: Do not update.
2. Grade Range
Specify whether to display the grade range. Values are:
Blank: Do not display.
1: Display.
3. Potency Range
Specify whether to display the potency range.
Blank: Do not display.
1: Display.
Lot/Serial
Enter the number that identifies a lot or a serial number. A lot is a group of items with
similar characteristics.
Item Number
Enter the number that the system assigns to an item. The value can be in short, long, or
third-item number format.
Grade
Enter the code that indicates the grade of a lot. The grade is used to indicate the
quality of the lot. Examples include:
A1: Premium grade
A2: Secondary grade
The grade for a lot is stored in the Lot Master table.
Potency
Enter the code that indicates the potency of the lot expressed as a percentage of active
or useful material (for example, the percentage of alcohol in a solution). The actual
potency of a lot is defined in the Lot Master table.
Display Lots with Qty on Hand (display lots with quantity on hand)
Select whether to display all lots or with quantity on hand.
5.3.14 Setting Processing Options for Item Ledger Inquiry (CARDEX) (P4111)
Processing options enable you to specify the default processing for programs and
reports.
5.3.14.1 Default
1. Document Type
Specify a user-defined code from UDC table (00/DT) that identifies the document
type. If you leave this processing option blank, the system uses the default value* and
all document types appear.
5.3.14.2 Versions
1. Load and Delivery Ledger Inquiry (FUTURE)
Specify the version to be used for each program. If this processing option is left blank,
the system uses version ZJDE0001.
5.3.14.3 Display
1. Quantity
Enter 1 to display quantity in primary units of measure along with quantity in
transaction units of measure.
Quantity
Enter a value that represents the available quantity, which might consist of the
on-hand balance minus commitments, reservations, and backorders. This is calculated
in the Branch/Plant Constants program (P41001).
See Also:
■ Working with Transaction Records.
5.4.3 Setting Processing Options for Supply and Demand Inquiry (P4021)
Processing options enable you to specify the default processing for programs and
reports.
5.4.3.1 Process
1. Deduct Safety Stock From Available Quantity
Specify whether the system deducts the safety stock from the available quantity.
Values are:
Blank: Do not deduct.
1: Deduct.
Quantity in Transit
Specify whether the system considers the quantity in transit a part of the on-hand
quantity. In a manufacturing environment, sometimes you must establish where stock
is to determine whether it is available for immediate use. Values are:
Blank: The system displays the quantity in transit for the appropriate date.
1: The system includes quantity in transit as on-hand inventory.
Quantity in Inspection
Specify whether the system considers the quantity in inspection a part of the on-hand
quantity. Values are:
Blank: The system displays the quantity in inspection for the appropriate date.
1: The systems includes quantity in inspection in on-hand inventory.
Note: When you enter 1, the system includes past-due orders in the
rate schedule unadjusted (+RSU) and rate schedule adjusted (+RS)
lines in the Master Planning Schedule - Multiple Plant (R3483) and the
MRP/MPS Requirements Planning (R3482) programs.
5.4.3.2 Display
1. Convert Quantities to Standard Potency
Specify whether to convert quantities to the standard potency. Values are:
Blank: Do not convert.
1: Convert.
Note: If you enter 1, you cannot use the Subtract Expired Lot
Quantities processing option.
5.4.3.3 Versions
If you leave any of the following processing options blank, the system uses the
ZJDE0001 version.
Thru Date
Enter the date that an item is scheduled to arrive or that an action is scheduled for
completion. Values include:
Promise Date: The planned effective date for work orders and purchase orders.
Requested Date: The planned effective date for sales orders.
Lot Effective and Lot Expiration Date: The planned effective date for lots.
Forecast Date: The planned effective date for forecast.
Demand
Enter the number of units that are committed for shipment in Sales Order Entry. Use
either the entered or the primary unit of measure that is defined for this item.
In the Manufacturing system and Work Order Time Entry, this field can indicate
completed or scrapped quantities. The quantity type is determined by the type code
entered.
Supply
Enter a value that represents the available quantity, which might consist of the
on-hand balance minus commitments, reservations, and backorders. You enter this
value in the Branch/Plant Constants (P41001) program.
Quantity Available
Enter a number that indicates the quantity that is available. For example, the available
quantity might consist of the on-hand quantity minus commitments, reservations, and
backorders.
Availability is user defined. You can set up availability in the Branch/Plant Constants
program (P41001).
Order No
Enter a number that identifies an original document. This document can be a voucher,
sales order, invoice, unapplied cash, journal entry, and so on.
Type
Enter a code from UDC table (00/DT) that identifies the type of document. This code
also indicates the origin of the transaction.
5.5.2.1 Versions
If you leave any of the following processing options blank, the system uses version
ZJDE0001.
Buyer Number
Enter the address number of the person who is responsible for setting up and
maintaining the correct stocking levels for the item.
Reorder Point
Enter a quantity for an item that specifies when replenishment occurs. Typically, this
occurs when the total quantity on hand plus the quantity on order fall to or lower than
a specified quantity. You can enter this quantity, or the system can calculate it if a
sufficient sales history is available.
Safety Stock
Enter the quantity of stock that is kept on hand to cover high-side variations in
demand.
Leadtime Level
Enter a value that represents the leadtime for an item at its assigned level in the
production process, as defined on Plant Manufacturing Data. The system uses this
value to calculate the start dates for work orders using fixed leadtimes.
Level leadtime is different for purchased and manufactured items:
Purchased: The number of calendar days that are required for the item to arrive at the
branch/plant after the supplier receives the purchase order.
Manufactured: The number of workdays that are required to complete the fabrication
or assembly of an item after all the components are available.
You can enter level leadtime manually on Manufacturing Values Entry, or you can use
the Leadtime Roll up program to calculate it. To calculate level leadtime using the
Leadtime Roll up program, you must first enter a manufacturing leadtime quantity in
the F4102 table.
Method Description
Complete regeneration Typically, you run the R41542 program only the
first time that you create the F41112 table.
However, if you change the fiscal date patterns on
the general ledger, you must completely regenerate
this table. During a complete regeneration, the
system processes the information in this way:
1. Verifies records, including those that were in
the previous complete regeneration.
2. Builds the table based on transactions in the
F4111 table as of the current date.
3. Marks all transactions in the table as
summarized so that they are not included in
any partial regeneration.
Partial regeneration When you create the F41112 table for the first time,
you can run this process at the end of each GL
period to enter new transactions and keep the
balance forward records current.
If records have been purged from the F4111 table or
if you do not know whether a purge has been run,
use the partial regeneration method.
The system records a transaction for this information, using the primary unit of
measure:
■ Data for the entire year, based on the fiscal date pattern.
■ Cumulative quantity and cost amount totals from the previous years.
■ Location.
■ Lot.
■ GL class.
■ Fiscal year.
When you enter individual transactions to the F41112 table, you create a record for
each of the unique combinations of the levels. When one of these records changes, the
system creates a new balance forward record at each level. However, the system
bypasses the item ledger and GL transaction accounts.
Use this data sequence when you run the R41542 program:
1. Item Number - Short
2. Branch/Plant
3. Location
4. Lot
5. GL Class
6. GL Date
Do not delete transactions from the F41112 table. You will lose total results if you
delete transactions because:
■ The system updates the balance-forward information but not the Item Ledger File
and other general ledger transaction accounts.
■ The system marks any transactions that you delete as summarized in the Item
Ledger File. The system does not select the transactions again if you run a partial
regeneration of the Item ASOF File table.
For the R41542 report, the system loads only the records for sales orders that have
been processed through sales update. The system cannot load purged item ledger
records into the F41112 table. If you load purged item ledger records, there will be
inaccurate totals.
5.6.4 Setting Processing Options for Item Ledger As Of Record Generation (R41542)
Processing options enable you to specify the default processing for programs and
reports.
5.6.4.1 GENERATION
1. Regenerate Option
Specify whether to regenerate the entire F41112 table. Values are:
Blank: The As Of file is updated with any transactions in the F4111 table that have not
yet been processed by the As Of generation.
1: Regenerate the entire F41112 table.
2. Completion Report
Specify whether to print a completion report. Values are:
Blank: Print a completion report only if errors occur.
1: Print a completion report.
5.6.5 Updating Balance Forward Records for Inactivity in the Fiscal Year
To include items with no transactions in the current fiscal year in the balance forward
records, select As Of Processing (G4122), As Of Updating.
The Item Ledger As Of Record Generation (R41542) program creates records in the
Item ASOF File only when a record exists in the Item Ledger table. If no transaction
occurs during the year for an item, the system does not create a record in the F4111
table. Therefore, the system does not subsequently create a record in the F41112 table.
To include records of prior year activity, run the As Of Updating (R41548) program
after you run the R41542 program. The R41548 program searches for an item record in
the Item ASOF File and then determines whether a corresponding record exists for the
next year. If a record does not exist for that year, the program inserts a record, carrying
forward the cumulative amounts and quantities. The program continues to fill in any
gaps until processing is complete for the year that is specified in the processing
options.
For example, if the first generation of the F41112 table occurs in 2007 and you specify
2010 in the processing option, the program starts with 2007 balances. If item 1001 had
transactions only in 2007, the program creates records for 2008, 2009, and 2010,
carrying the 2007 balances forward.
5.6.6.1 Defaults
1. Year
Enter a four-digit fiscal year (for example, 2008) through which the file is to be
updated. If you leave this processing option blank, the system enter the current year as
the default. The R41548 program will not run if you enter an invalid year.
Important: Enter only those item quantities that actually exist in the
Item Ledger table (F4111). If you add entries that do not match records
in the F4111 table, the Item Balance/Ledger Integrity report will have
errors. In addition, you will not have an adequate audit trail to
reconcile any differences.
Fiscal Year
Enter a number that identifies the fiscal year. Generally, you can either enter a number
in this field or leave it blank to indicate the current fiscal year (as defined on the
Company Setup form).
Specify the year at the end of the first period rather than the year at the end of the
fiscal period. For example, a fiscal year begins October 1, 2008, and ends September 30,
2009. The end of the first period is October 31, 2008. Specify the year 08 rather than 09.
Cumulative Amount
Enter the total amount of all transactions in the item ledger for an item.
If cumulative amounts and quantities for the previous year are in the system, the
system displays them after you enter the fiscal year, branch/plant, and item number
on Direct As Of Entry form. If the system does not display this information because no
balance-forward records exist for the previous year, you can enter them manually.
However, any amounts that you enter must match the previous year's totals.
Cumulative Quantity
Enter the cumulative total quantity from all transactions in the item ledger for an item.
Amount
Enter a number that represents the net amount posted during the accounting period.
The system uses the accounting periods from the F0010 table. The net amount posted
is the total of all debits and credits, beginning with the first day of the period through
the last day of the period.
Ending Period
Enter a user-defined name or remark.
Period Quantity
Future use. The historical quantity, in primary units of measure, on the bill of material.
Cumulative Quantity
Enter the total quantity of an item to be reworked or scrapped as a result of an
engineering change order (ECO) disposition.
The GL date that you select is based on the user-defined GL dates that you set up in
the processing options.
5.6.10 Setting Processing Options for Item Ledger Detail Print (R41540)
Processing options enable you to specify the default processing for programs and
reports.
2. End Date
Specify the ending general ledger date.
5.6.12 Setting Processing Options for Item Ledger By GL Class Code (R41541)
Processing options enable you to specify the default processing for programs and
reports.
documents. The system accesses information for this report from the F0006 and F0901
tables. The report includes:
■ Balance forward summaries
■ Account mode selection
■ Subledger selection
■ Object account summaries
See "JD Edwards EnterpriseOne General Accounting Reports" in the JD Edwards
EnterpriseOne Applications General Accounting Implementation Guide.
When you run the Automatic Inventory to G/L Reconciliation report, the system
reconciles documents where the total amount of the document in the Item Ledger
matches the total amount for the same document in the General Ledger.
When you run the Manual Inventory to G/L program, the system displays
summarized totals and variances by document, for all documents in your data
selection. When you select a specific document, the system displays additional details
from the item ledger and the general ledger. To reconcile a document, you may select
adjustment journal entries you previously created to reconcile the transactions.
You can also unreconcile a previously reconciled transaction or remove adjustment
journal entries previously selected to reconcile a transaction. When you unreconcile a
transaction, the system clears the adjustment journal entry that you used to reconcile
the transaction.
When you reconcile a transaction either by the batch process or the application, the
system updates the General Ledger (F0911) records to include the reconciliation date,
reconciliation code and reconciliation ID, and the Item Ledger (F4111) records with the
reconciliation date.
The following diagram illustrates the Inventory to G/L Reconciliation process:
When you run the Automatic Inventory to G/L Reconciliation report, the system
reconciles documents where the total amount of the document in the item ledger
matches the total amount of the same document in the general ledger.
The system reconciles matching records by updating the general ledger (F0911) records
to include the reconciliation date, reconciliation ID and reconciliation code, and by
updating the item ledger (F4111) records to include reconciliation date.
5.7.3.1 Default
1. Reconciliation Code
Enter a code that indicates that the transaction in the Account Ledger table (F0911) is
reconciled.
5.7.3.2 Process
1. Proof or Final Mode
Specify whether the system runs the program in proof or final mode. Values are:
Blank: The system runs the R41500 in proof mode.
1: The system runs the R41500 in final mode and reconciles the transactions in Item
Ledger table (F4111) and Account Ledger table (F0911).
In proof mode, the system generates a report but does not update the item ledger and
general ledger tables.
5.7.3.4 Interbranch
1. Interbranch Order Type
Identify the order type used for interbranch orders. If you leave this processing option
blank, the system uses the order type ’SI’.
Note: The processing setup for interbranch orders may cause the
item ledger and general ledger amounts to be different. In this case,
the system does not automatically reconcile the records.
5.7.3.5 Print
1. Print Option
Specify how the system displays the records in the output. Values are:
Blank: The system displays both reconciled and variance records.
1: The system displays only variance records.
2: The system displays only reconciled records.
Note: If the variance amount for a record is more than the tolerance
amount specified in the processing options, you must select an
adjustment journal entry to reconcile the transaction.
You can unreconcile a record that was previously reconciled. To unreconcile a record,
select the record in the Reconciliation Summary grid, and click the Unreconcile button.
The system updates the item ledger record by clearing the reconciliation date, and the
general ledger record by clearing the reconciliation date, reconciliation ID and
reconciliation code.
Company
Enter a number that, with the document number, document type and G/L date,
uniquely identifies an original document, such as invoice, voucher, or journal entry.
You must enter a value in the Company field to run the Manual Inventory to G/L
Reconciliation program.
Through
Enter a date that identifies the end of the financial period.
Minimum Variance
Enter a number that represents the variance amount which the system uses to filter
records. If you enter a value here, the system displays only those records where the
variance amount is greater than or equal to the amount you enter in this field.
Use the Percentage Combo box to enter the minimum variance in the form of
percentage.
5.7.6 Setting Processing Options for Manual Inventory to G/L Reconciliation Program
(P41500)
Processing options enable you to specify the default processing for programs and
reports.
5.7.6.1 Defaults
1. Reconciliation Code
Enter a value that indicates that the transaction in the Account Ledger table (F0911) is
reconciled.
3. Tolerance Limit
Specify the tolerance amount by which the item ledger and general ledger amounts
can be out of balance. If you enter an amount, you can reconcile the records with a
variance up to the tolerance amount, either negative or positive.
If you leave this processing option blank, the item ledger and general ledger amounts
must match.
5.7.6.3 Interbranch
Interbranch Document Type
Enter the order type used for interbranch orders.
The processing setup for interbranch orders may cause the item ledger and general
ledger amounts to be different. If you enter a value for this processing option, the
system does not reconcile the records automatically.
6.2.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Verify that these automatic accounting instructions (AAIs) are set up:
– AAI table 4152, which provides the inventory account to offset against any
count variance.
– AAI table 4154, which provides the cost of goods sold account to update.
– AAI table 4141, which provides the variance account to update (set up only if
you use standard costs).
– AAI tables 4122, 4124, 4126, and 4128, which provide the accounts for
zero-balance adjustments.
■ Set up the Cycle Count Category Code field using the Item Master (P4101) and
Item Branch (P41026) programs. This field must be set up for you to use the
associated method of updating in the Cycle Count Update program (R41413).
See Adding Classification Codes to Items.
■ Verify that you have not changed any printer file override information before you
print cycle count sheets.
Any changes to information, such as report length or width, might affect the
appearance of the report.
– Amount on hand.
■ Produces the Select Items for Count report, which lists the selected items for each
location and the quantity on hand at the time of the count.
You can use data selection to group items by:
■ Cycle count categories (for example, monthly and semiannually).
■ ABC codes (for example, count A items monthly).
You cannot change this sequence for the Select Items for Count report:
1. Item number (short)
2. Lot
3. Location
See Also:
■ Running the Cycle Count Update Program.
6.2.5 Setting Processing Options for Select Items for Count (R41411)
Processing options enable you to specify the default processing for programs and
reports.
6.2.5.1 Print
1. Cycle Count Description
Specify a user-defined cycle count description.
Item Number
Enter an identifier for an item.
Quantity On Hand
Enter the total quantity on hand in the primary unit of measure for an item at the
beginning of the cycle count.
Quantity Counted
Enter the total quantity that is counted for the item in all locations.
6.2.8 Setting Processing Options for Print Cycle Count Sheets (R41410A)
Processing options enable you to specify the default processing for programs and
reports.
6.2.8.1 Print
Print Non-canceled sheets
Specify whether to print non-canceled sheets. Values are:
Blank: Print all cycle sheets.
1: Print non-canceled sheets.
After you have performed the cycle count and recorded the information on the cycle
count sheets, you must enter the results in the online inventory records, even if the
result of the count is zero.
If the count included an item that is found in a new location, you can add the new
location on a blank line of the Cycle Count Entry form. However, if the Location
Control constant is turned on, you must set up the new location in the F4100 table
before you can enter the quantity on the Cycle Count Entry form.
When you enter a new location, the system creates an item location record and a
variance for the entire quantity and amount after you enter the cycle count results and
then run the Cycle Count Update.
Quantity
Enter the number of units that the system counts in the primary unit of measure.
UM (unit of measure)
Enter a code from UDC table (00/UM) that indicates the quantity in which to express
an inventory item, for example, CS (case) or BX (box).
Total Quantity
Enter the total quantity that is counted for the item in all locations.
Secondary Quantity
If the secondary unit of measure option in Inventory Constants is selected, this field
will appear on data entry screens.
See Also:
■ Setting Up Warehouse Locations.
If no license plate item detail record exists in the F46L11 table, you cannot access the
Cycle/Tag Count LPN Detail Entry form. Also, the system cannot process license plate
detail under these conditions:
■ The branch/plant is not warehouse controlled.
■ LPN processing is not activated for this branch/plant.
■ LPN item detail does not exist for this location.
■ The stocking type is not valid.
■ The inventory interface option is not valid.
■ The item is a bulk item.
Quantity Counted
Enter the total quantity that is counted for the item in all locations, in a primary unit of
measure.
Amount
Enter a number that identifies the amount that the system will add to the account
balance of the associated account number. Enter credits with a minus sign (–) either
before or after the amount.
Absolute Value
Specify whether a variance amount appears when it is greater than an absolute value
or greater than a percentage of the original.
Percentage
Specify whether a variance amount appears when it is greater than an absolute value
or greater than a percentage of the original.
Relationship
Enter a code from UDC table (00/VA) that indicates the relationship between the
ranges of variances that you display. Values are:
EQ: Equal to
LT: Less than
LE: Less than or equal to
GT: Greater than
GE: Greater than or equal to
See Also:
■ Reviewing the Print Variance Detail Report.
See Also:
■ Reviewing the Print Variance Detail Report.
6.2.15 Setting Processing Options for the Print Variance Detail (R41403)
Processing options enable you to specify the default processing for programs and
reports.
6.2.15.1 Processing
1. Enter '1' to select on Quantity Variance (default) or '2' to select on Amount
Variance
Specify a value that determines the type of variance the system uses. Values are:
1: Quantity Variance (default)
2: Amount Variance
2. Enter the Relation to use for the variance selection. (Default is greater than)
Specify a user-defined code from UDC table (00/VA) that identifies the relationship
between the range of variances that appear.
3. Enter the Quantity or Amount to use to compare with the variance for selection.
Specify a value that determines the quantity or amount to use to compare with the
variance for selection.
4. Enter '1' to compare the Percent Variance or '2' to compare the Unit Variance
(default).
Specify a value that determines the type of variance to compare. Values are:
1: Percent Variance
2: Unit Variance (default)
See Also:
■ Reviewing the Print Variance Detail Report.
6.2.18.1 Defaults
These processing options define the dates that the system will use for general ledger
posting and for the next cycle count.
6.2.18.2 Process
1. Delete Detail Records from Cycle Count and Warehouse Transaction tables
Specify whether the system deletes detail records from the F4141 and F4142 tables after
processing. Detail records contain the on-hand quantities and amounts that are stored
in the general ledger. They also contain the quantities that were counted for locations,
the unit cost, the name of the person who performed the count, and the date. Values
are:
Blank: Do not delete detail records. You can use file utilities or create a batch program
to delete the detail records from the Cycle Count Transaction File and Warehouse
Count Transaction tables at a later time.
1: Delete detail records from the Cycle Count Transaction File table and the Warehouse
Count Transaction table. You must run a variance report before you run the Cycle
Count Update (R41413) program. After you run the program, no detail records will
exist to calculate the variance.
6.2.18.3 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the transaction
type that the system uses when creating outbound interoperability transactions. If you
leave this processing option blank, the system does not perform outbound
interoperability processing for cycle count transactions.
and record their data on two different parts of the tag. Later, you use each team's data
to compare results and resolve variances.
Consider using a tag count in conjunction with a cycle count to ensure accuracy. You
also can use the following programs to indicate that counted quantity is on certain
existing license plates. You can access LPN Detail Entry program (P46L42) from the
Row menu on Cycle Count Entry form or from the Form menu on the Tag Count Entry
form.
See Also:
■ Processing Cycle Counts.
6.3.5.1 Defaults
Number of Tags
Specify the number of tags that you want to print.
Branch / Plant
Specify the branch/plant to print on the tags.
Tag Status
Enter a code from UDC table (41/TS) for the status of a tag in the tag inventory count
process.
6.3.7.1 Defaults
Status One through Status Four
Specify user-defined codes from UDC table (41/TS) that identify the statuses that are
valid for a tag change.
6.3.7.2 Warehouse
Location Detail
Specify how to select location detail records. Values are:
Blank: The system selects the location detail records.
1: Use the Location Detail Selection Window to enter counts for specific location detail
records.
After the tag count is complete, you must enter the information from each tag into the
system.
6.3.11.1 Process
1. Tag Delete
Specify whether the system deletes tags from the F4160 table after an update. Values
are:
Blank: Do not delete.
1: Delete.
2. GL Date
Specify the GL date that the system associates with the tag inventory update. Enter a
specific date or select a date from the calendar. If you leave this processing option
6.3.11.2 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies whether the
system processes outbound interoperability transactions through the subsystem. If you
leave this processing option blank, the system does not perform outbound
interoperability processing.
See Also:
■ Setting Up AAIs in Distribution Systems.
■ Entering Item Cost Information.
7.1.2 Prerequisite
Before you complete the tasks in this section, you must verify that automatic
accounting instructions (AAIs) for changes to inventory costs are set up.
See Setting Up AAIs in Distribution Systems.
7.1.4.1 Defaults
Default cost method
Specify a user-defined code from UDC table (40/CM) that indicates the cost method
that the system uses to determine the cost of the item for purchase orders. The system
reserves cost methods 01–19.
7.1.4.2 Process
Standard Cost
Specify whether to change the standard cost. Values are:
Blank: Change
1: Do not change.
If you maintain costs at the item level, the system retrieves the default value for this
field from the data dictionary. If you maintain costs at the item and branch/plant level,
the system retrieves the default value from Branch/Plant Constants program (P41001).
7.1.7.1 Process
Cost Change
Specify the cost change to use for update. If you enter a percentage, enter it as a whole
number.
7.1.7.2 Defaults
1. Reason Code
Specify a user-defined code from UDC table (41/RC) that identifies a reason for a
transaction.
2. Document Type
Specify a user-defined code from UDC table (00/DT) that identifies a document type.
3. GL Date
Specify the date for the journal entry. If you leave this field blank, the system uses the
current period date.
7.1.7.3 Print
Print Report
Specify whether to generate a report. Values are:
Blank: Do not generate.
1: Generate.
7.1.7.4 Edits
Mode
Specify whether to update files. Values are:
Blank: Proof mode. Do not update files.
1: Final mode. Update files.
See Also:
■ Setting Up Constants.
Document Type
Specify a user-defined code from UDC table (00/DT) that identifies the document type
to be used when writing General Ledger and Item Ledger records.
If you leave this processing option blank, the system uses document type WD.
7.1.10.2 Interop
Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the transaction
type for the interoperability transaction. If you leave this processing option blank, the
system does not perform outbound interoperability processing.
See Also:
■ Setting Up Constants.
7.2.5.1 Process
Purchased Cost Method
Specify the cost method (for example, 01,02, or 03) to move from the F4105 to the
F30026 table. If you leave this processing option blank, the system does not move
costs.
Cost Type
Specify the cost type (for example, A1 or X1) to use when bringing cost from the F4105
table.
7.2.5.2 Defaults
Cost Method to Calculate
Specify the cost method to calculate (for example, 01,02, or 03 ). If you leave this
processing option blank, the system uses cost method 07 (standard).
7.2.5.3 Print
Report Selection
Specify how the report will print. Values are:
1: Print all the selected items.
2: Print only changed items.
7.2.7.1 From
1. Cost Method
Specify a user-defined code from UDC table (40/CM) that identifies the cost method to
copy. If you leave this processing option blank, the system does not copy costs.
2. Costs to be Copied
Specify which costs should be copied. Values are:
1: Simulated
2: Frozen
7.2.7.3 Default
5. GL Class Code
Specify a user-defined code from UDC table (41/9) that identifies the GL category
code.
6. Supplier Number
Specify an address book number for your supplier.
In this example, the kit consists of a stereo, which is the parent item, and these
components and options:
■ Wiring jacks (component)
■ Receiver (component)
■ Speakers (component)
■ Cassette deck (option
■ Five-platter CD player (option)
■ Single CD player (option)
A compact disc (CD) player is a feature in the kit, and two versions of the feature are
available:
■ 5-platter CD player
■ Single CD player
When you create a work order, you are preparing to produce a product. The parts
list indicates the material and quantity that you will need.
Stocking Type
Enter a code from UDC table (41/I) that indicates how you stock an item. These
stocking types are hard coded and you should not change them. Examples are:
F: Feature
K: Kit parent item
The first character of Description 2 in UDC table (41/I) indicates whether the item is
purchased (P) or manufactured (M).
8.2.2 Prerequisite
Before you complete the tasks in this section, you must verify that the parent,
components, features, and options for the kit are set up in the Item Master (F4101).
See Entering Kit Information.
8.2.4.1 Defaults
1. Component Branch
Specify whether to use the parent branch or a component branch as the default value
in the bill of material records when you copy the bill of material to add a new bill of
material. Values are:
Blank: Use the component branch.
1: Use the parent branch.
3. As Of Date
Specify whether the system uses the current date as the default value in the As Of Date
field in the header area of the Work with Bill of Material form. Values are:
Blank: The system uses all dates.
1: The system uses the current date.
4. Display Sequence
Specify how the system sorts the information on the Enter Bill of Material Information
form. You can choose whether to sequence the data by component line number or by
operation sequence number. The component line number indicates the sequence of the
components on a bill of material. The operation sequence number indicates the
sequence of the fabrication or assembly steps in the manufacture of an item. Values
are:
Blank: The system sequences by component line number.
1: The system sequences by component line number.
2: The system sequences by operation sequence number.
8.2.4.2 Display
1. Bill Type
Specify whether to display the Bill Type field in the header area of both the Work With
Bill of Material and Enter Bill of Material Information forms. Values are:
Blank: Do not display.
1: Display.
2. Batch Quantity
Specify whether to display the Batch Quantity field in the header area of the Enter Bill
of Material Information form. Batch quantity is the quantity of finished units that you
expect a specific bill of material to produce. Values are:
Blank: Do not display.
1: Display.
8.2.4.3 Versions
If you leave any of the following processing options blank, the system uses version
ZJDE0001.
8.2.4.4 Edit
1. Item Branch Validation
Specify whether to validate the existence of an item branch record of a component in
the Item Branch table (F4102). Values are:
Blank: Do not validate.
1: Validate.
8.2.4.5 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies the transaction
type that the system uses for export processing. If you leave this processing option
blank, the system does not use export processing.
See Also:
■ Setting Up Constants.
See Also:
■ "Working with Fixed Assets and Inventory Management for
Russia" in the JD Edwards EnterpriseOne Applications Localizations
for Russia Implementation Guide.
constants to restrict a lot to one type of item and still enable that lot to exist in multiple
warehouses.
You can use one of these methods to assign lot number to items:
■ Allow the system assign lot numbers.
■ Assign the owner lot numbers.
■ Assign supplier lot numbers.
After you create a lot, the system adds a record to the Lot Master table (F4108).
See Also:
■ Setting Up Constants.
If you later find that a particular lot of tires is defective, you can immediately identify
and recall all bicycles that were assembled with the defective tires.
A lot usually contains one type of item, but you can set up system constants to enable
different types of items in the same lot. If a lot contains different items, the system
maintains lot information for each lot number and item. You can also set up system
constants to restrict a lot to one type of item and still enable that lot to exist in multiple
warehouses.
You can use one of these methods to assign lot number to items:
■ Allow the system assign lot numbers.
■ Assign the owner lot numbers.
■ Assign supplier lot numbers.
You must determine how to identify item locations and lots in the system to enable
you to locate items quickly and perform daily operations efficiently. After you create a
lot, the system adds a record to the Lot Master table (F4108).
Note: For the system to update all lot dates in all branches, you must
set the Enable Duplicate Lots option for the branch/plant record in the
system constants to 2, which enables you to have the same item and
lot number in multiple branch plants. The system does not update a
lot that exists in multiple branches if the item numbers that are
associated with that lot are different.
9.2.4.1 Process
1. Update lot status
Specify whether to update the lot status. Values are:
Blank: Update.
1: Do not update.
9.2.4.2 Defaults
1. Document type to be used when updating lot grade
Specify a user-defined code from UDC table (00/DT) that identifies the document type
to use when updating lot grade. If you leave this processing option blank, the system
uses default document type CG.
3. Calculation Date
Specify the calculation date. If you leave this processing option blank, the system uses
today's date.
Lot / Serial
Enter a number that identifies a lot or a serial number. A lot is a group of items with
similar characteristics.
Lot Grade
Enter a code that indicates the grade of a lot. The grade indicates the quality of the lot.
Examples include:
A1: Premium grade
A2: Secondary grade
The grade for a lot is stored in the F4108 table.
Lot Potency
Enter a code that indicates the potency of the lot expressed as a percentage of active or
useful material (for example, the percentage of alcohol in a solution). The actual
potency of a lot is defined in the F4108 table.
Supplier
Enter the address book number of the preferred provider of this item.
Received/Created
Enter a type of quantity. This field represents quantity category 1. You specify the
document types that update this category in UDC table (40/LQ).
The system updates user-defined quantities in the F4111 table.
9.3.2.1 Versions
1. Trace/Track Inquiry
Specify the version of the Trace/Track Inquiry program to use.
9.3.2.2 Display
1. Lot Status
Specify whether to update the lot status. Values are:
Blank: Update.
1: Do not update.
2. Grade Range
Specify whether to display the grade range. Values are:
Blank: Do not display.
1: Display.
3. Potency Range
Specify whether to display the potency range. Values are:
Blank: Do not display.
1:: Display.
You can view the availability of items in a lot as well as the activity dates, item
quantities, and hold statuses that pertain to the lot. Activity dates and item quantities
reflect receipts, issues, sales, and so on for items in a lot
You can view lot availability for:
■ All items in a lot.
■ All lots that contain a specific item.
You can select to view only those items or lots for which on-hand balances are
available. If the same item or lot appears more than once, each item or lot exists in a
different location.
Display Lots with Qty on Hand (display lots with quantity on hand)
Enter an option that indicates whether the system displays all lots or lots with quantity
on hand. A check mark indicates that the system displays only lots with quantity on
hand.
Lot Status
Enter a code from UDC table (41/L) that indicates the status of the lot. Leaving this
field blank indicates that the lot is approved. All other codes indicate that the lot is on
hold.
You can assign a different status code to each location in which a lot resides on
Item/Location Information or Location Lot Status Change.
Expiration Date
Enter the date on which a lot of items expires.
The system automatically enters this date if you specified the shelf life days for the
item on the Item Master Information or Item Branch/Plant Information forms.
The system calculates the expiration date by adding the number of shelf life days to
the date that you receive the item.
You can commit inventory based on the lot expiration date for items. You select how
the system commits inventory for an item on the Item Master Information or Item
Branch/Plant Information forms.
Quantity On Hand
Enter the number of units that are physically in stock. The system displays the
quantity on-hand in the primary unit of measure.
Quantity Available
Enter a number that indicates the quantity that is available. For example, the available
quantity might consist of the on-hand quantity minus commitments, reservations, and
backorders.
Availability is user-defined. You can set up availability in the Branch/Plant Constants
(P41001) program.
■ Issued
■ Adjusted
■ Completed
■ Approved
■ Sold
You set up UDC table (40/LQ) to indicate for which document types the system tracks
lot quantities. You must associate each document type with one of the quantity type
categories in the Lot Master (P4108) program.
For example, if you specify the Received category for document type OP (purchase
orders) each time that you receive items on a purchase order, the system records the
quantity to the Received category for the lot.
For certain items, you should enter grade and potency information. If you do not
specify a grade or potency for items that require this information, the system uses the
standard grade or potency from the Grade & Potency Profile Revisions form.
might process items out of locations on hold, depending on the program in which you
are working and the way that processing options are set.
Run the Hold Expired Lots program (R41082) to place expired lots on hold. You can
preview a list of all lots that will be placed on hold by running the program in proof
mode.
Program Description
Shipment Confirmation (P4205) You can ship on-hold items that have an
allowed lot status assigned. Use the Enter
Allowed Lot Status Group to Validate
processing option on the Edits tab to validate
the lot status group.
■ Print Pick Slips (R42520) You can commit items with an allowed lot
status. Use the Enter Allowed Lot Status
■ Package Pick Slips (R42521)
Group processing option on the Edits tab to
■ Control Pick Slips (R42522) specify the lot status group.
Location Selection Driver (R46171) You can transfer on-hold items that have the
allowed lot status. Use the Enter Allowed Lot
Status Group processing option on the Edits
tab to specify the lot status group.
Warehouse Movement Confirmations (P4617) You can move items with an allowed lot status
in Warehouse. Use the Enter Allowed Lot
Status Group processing option on the Edits
tab to specify the lot status group.
Backorder Release (P42117) You can release backorder items with allowed
lot status. Use the Enter Allowed Lot Status
Group processing option on Edits to specify
the lot status group.
Backorder Release and Report (R42118) You can release backorder items with allowed
lot status. Use the Enter Allowed Lot Status
Group processing option on the Edits tab to
specify the lot status group.
Program Description
Sales Order Entry (P4210) You can process an on-hold item with allowed
lot status. Use the Enter Allowed Lot Status
Group processing option on the Commitment
tab to specify the lot status group.
Kit Selection (P41351) You can use sales orders to process on-hold kit
components with allowed lot status. The
system uses the same processing option that
was specified in the Sales Order Entry (P4210)
program.
Configured Item Revisions (P3210) You can validate the lot status code against
specified lot status group. You can use sales
orders to process configured on-hold
components with allowed lot status. The
system uses the same processing option that
was specified in the Sales Order Entry (P4210)
program.
Configured Item Segment Search (P32202) You can use sales orders to process configured
on-hold components with allowed lot status.
The system uses the same processing option
that was specified in Sales Order Entry
(P4210) program.
Select Configured Items (P32053) You can use sales orders to process configured
on-hold components with allowed lot status.
The system uses the same processing option
that was specified in the Sales Order Entry
(P4210) program.
Order Processing (R31410) You can release on-hold items with allowed
lot statuses. Use the Enter Allowed Lot Status
Group processing option on the Edits tab to
specify the lot status group.
WO Component Shortage List Report The system uses the same processing option
(R31418) that was specified in the Order Processing
(R31410) report.
Work Order Inventory Issue (P31113) You can issue on-hold items with allowed lot
statuses to a work order. Use the Enter
Allowed Lot Status Group processing option
on the Edits tab to specify the lot status group.
Work Order Parts List (P3111) You can hard commit on-hold items with
allowed lot statuses. Use the Enter Allowed
Lot Status Group processing option on the
Edits tab to specify the lot status group.
Work Order Completions (P31114) You can require the user to enter a nonblank
lot status code for a finished lot when on-hold
items were consumed. Use the Hold Code
Requirement processing option on the Edits
tab to specify the lot status group.
Item/Branch Locations (P41LOCN) You can enable item/branch locations to
display available quantity for items with an
allowed lot status.
Inventory Transfers (P4113) You can process on-hold items with allowed
lot statuses. Use the Enter Allowed Lot Status
Group processing option on the Process tab to
specify the lot status group.
Program Description
Inventory Issues (P4112) You can process on-hold items with allowed
lot statuses. Use the Enter Allowed Lot Status
Group processing option on the Process tab to
specify the lot status group.
Inventory Adjustments (P4114) You can process on-hold items with allowed
lot statuses. Use the Enter Allowed Lot Status
Group processing option on the Process tab to
specify the lot status group.
During the print pick slip, ship confirmation, and warehouse location selection
processes, the system validates the nonblank lot status codes against the user-defined
status code values. If nonblank lot status codes exist in the F41081 table, the system
considers the user-defined lot status codes as blank and the on-hold item continues
through these processes.
Lot Group
Enter a lot group. This value is the name of a user-defined list of allowed nonblank lot
status codes. If you enter a value in this processing option, the system uses the
Allowed Lot Status table (F41081) to validate lots for which lot status code is nonblank
against the specified lot group name.
Branch/Plant
Enter the alphanumeric code that identifies a specific entity within a business, such as
a warehouse location, branch, or plant.
You can use any value in the Enter Trace/Track processing option on the Display tab
of the Track/Trace Inquiry program (P41203) as it is not significant if you trace or track
an item when performing a product audit.
The system uses the document type entered in the Enter WO Document Type to
Inquire processing option on the Defaults tab to determine whether to enable the As
Built Comparison, Engineering History, and Production History buttons when you
select a row on the Lot Management Workbench form. For example, the system
enables all three buttons when the processing option is set to WO for work order.
When you access the Lot Management Workbench form for the first time, the system
disables all buttons except the Signature and Audit button. On the Lot Management
Workbench form, you enter an item number and lot/serial number to trace or track a
specific item. You then select the parent line for the Lot B/P (lot branch/plant) and the
system enables the Item Information and Quality Results buttons.
You next select the line that contains an inventory completion (IC). The system enables
the As Built Comparison, Engineering History, and Production History buttons based
on the document type setting in the Enter WO Document Type to Inquire processing
option on the Defaults tab.
You click Find and evaluate the comparison on the Display Comparisons form. You
click Close on both the Display Comparisons and Work With Comparisons forms to
return to the Lot Management Workbench form.
9.5.5.1 Display
1. Enter Track/Trace
Specify which method the system uses to trace or track lot usage. If you select to trace
the lot, the system traces, from the time of shipment to the time of manufacture, all of
the items that made up the current item. If you select to track the item, the system
determines all of the assemblies of which this item is to be a component, from the time
of manufacture to the time of shipment. Values are:
Blank: Trace lot usage.
1: Track lot usage.
Blank: Display all transactions, but exclude IB, IX, and IZ types.
1: Display only those transactions that may have created new derivative lot.
9.5.5.3 Defaults
1. Enter PO Document Type to Inquire
Specify a user-defined code from UDC table (00/DT) that identifies the purchase order
document type on which to inquire. If you leave this processing option blank, the
system uses default document type OP.
9.5.5.4 Version
1. Enter Lot Master (P4108) Version
Specify a version of the Lot Master program to use. If you leave this processing option
blank, the system uses version ZJDE0001.
9.5.6.1 Driver
Trace Backward
Select to trace specified lot backward across multiple branch plants and multiple levels
within manufacturing and transfer process to the initial purchase receipt.
Trace Forward
Select to track specified lot forward across multiple branch plants and multiple levels
within manufacturing and transfer process to last shipment made.
System/Supplier/Memo1
Enter the type to indicate that the lot that you entered is a supplier lot, or select
Memo1 type to indicate that it is a lot memo 1. The system type indicates that it is
internal lot number.
Branch/Plant
Enter the branch/plant as an additional filter.
Quality Results
Click to acces the Test Results Revisions form.
As Built Comparison
Click to access the Work With Comparisons form.
Engineering History
Click to access the Work With ECO Workbench by Item form.
Production History
Click to access the Production Cost Inquiry form.
You can reclassify an item and any associated lot when the item properties change.
You can reclassify only uncommitted quantities of items and lots. You can review
uncommitted quantity information for the item and related lot in the Item Availability
(P41202) program. When you reclassify in the Reclassifications Transactions program
(P4116), you create new item numbers and combine or split existing lots within
locations.
For example, property changes that occur over time in technical grade sulfuric acid
can result in a less potent grade of acid. You can create a new lot for this acid by
specifying a different potency and grade. Similarly, if you blend several lots of sulfuric
acid together and dilute them with water, you can create a new lot with a new potency
and grade.
You can change a lot and any of the associated items in these ways:
■ Change the item number, location, lot, and lot status.
■ Create a new lot from an existing lot.
■ Combine several lots into a single lot.
■ Split one lot into several lots.
After you reclassify an item and lot, the system displays the document type, batch
number, and document number that you use to locate the transaction. The system then
adjusts inventory balances and performs related tracking and accounting tasks. The
system updates these tables with item and lot change information:
■ F4111
■ F0911
■ F41021
■ F4602 (if you are using the JD Edwards EnterpriseOne Warehouse Management
system)
You can view detailed or summarized journal entries for these transactions on the
Journal Entries and the Item Ledger Inquiry forms.
After you enter several reclassifications, you can group them together for processing.
After you group transactions, the system assigns the same number to each transaction
in the group and processes all of the From and To lines with the same transaction
number. Depending on how you have set the processing options, the system validates
that the From and To quantities balance.
If you make an error when you reclassify an item or lot, you can correct the mistake by
entering a reversing entry. The system reverses the item in the same document number
and batch as the original reclassification. Because the system stores records of each
reclassification for accounting purposes, you cannot delete the record.
Note: You cannot use the P4116 program to reclassify bulk inventory.
See "Setting Up Bulk Items" in the JD Edwards EnterpriseOne Applications Bulk Stock
Inventory Implementation Guide.
9.6.2 Prerequisites
Before you complete the tasks in this section, you must verify that:
■ The general ledger accounts are set up in the F0901 table.
See "Creating the Chart of Accounts" in the JD Edwards EnterpriseOne Applications
Financial Management Fundamentals Implemenation Guide.
■ AAIs for distribution are set up.
9.6.4.1 Defaults
1. Document Type
Specify a user-defined code from UDC table (00/DT) that identifies the default
document type. If you leave this processing option blank, the system does not provide
a document type.
9.6.4.2 Versions
If you leave any of the following processing options blank, the system uses version
ZJDE0001.
9.6.4.3 Process
1. Cost Entry
Specify whether the system displays and protects costs. Values are:
Blank: Display cost and enable the cost to be updated.
1: Display cost, but do not enable the cost to be updated.
2: Do not display cost.
2. Journal Entries
Specify how the system processes GL accounts. Values are:
Blank: Run in detail mode.
1: Summarize by account number.
3. Lots on Hold
Specify whether the system enables transfers from held lots. Values are:
Blank: Do not enable transfers from held lots.
1: Enable transfers from held lots.
4. Reclassification Quantity
Specify whether the system enables the reclassification of a quantity to be greater than
the quantity that is available. Values are:
Blank: Do not enable the reclassification of quantity to be greater than the quantity that
is available.
1: Enable the reclassification of quantity to be greater than the quantity that is
available.
5. Quantity Validation
Specify which method of quantity validation the system uses for from and to
quantities in a transaction. Values are:
Blank: Do not validate quantities.
1: Display a warning if the quantity is out of balance.
2: Display an error if the quantity is out of balance.
9.6.4.4 Interop
1. Transaction Type
Specify a user-defined code from UDC table (00/TT) that identifies a type of
transaction, such as an invoice or a sales order. If you leave this processing option
blank, the system does not perform export processing.
9.6.4.5 Agreement
1. Agreement Assignment (FUTURE)
Future use.
Transaction Date
Enter the date that the transaction occurred.
From Branch/Plant
Enter the lowest value of the range that a given user is authorized to view and process
data. This value is used in conjunction with the Business Unit Through Code, which
defines highest value. If no record exists for a user and file, the user is completely
authorized to the file. If the file name is blank for a given user, the business unit range
applies to all users of the file.
To Branch/Plant
Enter an alphanumeric code that identifies a separate entity within a business for
which you want to track costs. For example, a business unit might be a warehouse
location, job, project, work center, branch, or plant.
From/To
Enter a code that indicates whether a line in a transaction is a From line or a To line.
This field enables you to combine multiple existing products or locations into a single
product or location. For example, you can create three From lines and one To line. You
can also split one existing product or location into several new products or locations.
Or, you can create one From line and two To lines. The information that is contained in
a From transaction line is always existing item location information.
This table presents the three methods for calculating a lot expiration date:
Method Description
Shelf Life Days + Work Order If you use this method, the expiration date of the
Completion Date item is calculated by adding the date that it was
completed plus the shelf life days that are defined
for the item. If Shelf Life Days field is blank, then
the default value for the Lot Expiration Date is the
latest system date. You can override this value
during work order completions.
Shelf Life Days + Based On Date If you use this method, the expiration date of the
item is calculated by adding the shelf life days
plus the based-on date. You can specify the
based-on date when you run the Work Order
Completions (P31114) program. This type of
calculation is required when the end product
starts to expire before the last step of the routing
process.
Shelf Life Days + Least Expiration Date of If you use this method, the expiration date of the
Active Ingredients or Components item is calculated for the manufactured parent lot
based on a lower-level component. For example, if
milk is used to produce ice cream, the expiration
date for the lot of ice cream can be based on the
expiration date of milk.
Use this method in conjunction with the Active
Ingredient option on the Additional System
Information form (Manufacturing Data or Plant
Manufacturing), where you specify whether the
component is an active ingredient.
See Also:
■ Setting Up Dates for Lots.
■ Defining Effective Dates for Future Availability.
9.7.2 Prerequisite
Before you complete the tasks in this section, you must verify that UDC table (40/VF)
contains the value 03 CPGLC with a special handling code of Y.
User Lot Date 1 Default Days through User Lot Date 5 Default Days
Enter the number of days that the system uses to calculate the value for these fields of
the Lot Master table (F4108). The system calculates the value for these fields using one
of two methods, depending on whether the number that you enter in this field is
positive or negative. If you enter a positive value, the system adds the days to the
based-on date to determine the value for the field. If you enter a negative value, the
system subtracts the days from the lot expiration date to determine the value for the
field.
Active Ingredient
Select this check box to indicate that an item is an active component of a parent item.
When the item is an active component, the system can calculate a parent item's
expiration date by comparing all component expiration dates and choosing the earliest
date. Values are:
Blank: The item is not an active component of a parent item.
1: The item is an active component of a parent item.
See Also:
■ Running the Update Effective Lots Program.
■ Reclassifying Lots.
9.8.5.1 Defaults
1. Lot Effective Date
Specify the effective date. If the effective date of a lot is less than or equal to the date
that you enter here, the system changes the status code of the lot to the new lot status
code. If you leave this processing option blank, the system uses the current date.
3. Reason Code
Specify a user-defined code from UDC table (42/RC) that identifies the reason code for
changing the lot status. If you leave this processing option blank, the system does not
provide a default reason code.
9.8.5.2 Omit
1.–5. Excluded Lot Status Code
Specify a user-defined code from UDC table (41/L) that identifies the lot status code
that the system omits while updating the effective lots.
9.8.5.3 Process
1. Proof/Final Mode
Specify whether to run the program in proof or final mode. Values are:
Blank: Proof mode.
1: Final mode.
2. Print Mode
Specify whether to generate a report. Values are:
Blank: Do not generate.
1: Generate.
Note: After you set up ascending date rules for lot shipment, verify
that Lot Shipment Ascending Dates is enabled in the system constants,
as well as the Display Warning/Error for Ascending Date Rule Check
processing option on the Process tab in Sales Order Entry program
(P4210). The system displays a warning when you manually enter a
lot number on the order. You can also override the schedule for
advanced preferences on the Preferences tab in processing options for
the P4210 program.
See Also:
■ Setting Up Dates for Lots.
9.9.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Select the Ship Ascending Date Rule check box for the branch/plant and assign
the preference schedule in UDC table (40/AP) on the System Constants form.
See Setting Up Constants.
■ Enter 1in the Preference Profile Processing processing option on the Preference tab
in the Sales Order Entry (P4210) program.
See "Entering Sales Orders" in the JD Edwards EnterpriseOne Applications Sales Order
Management Implementation Guide.
Preference Name
Enter a code from UDC table (40/TY) that specifies an adjustment definition. You
define adjustments on Price Adjustment Names.
this option, the system ensures that each lot that is being shipped has a sell by date
that is greater than or equal to the date on which the last lot was shipped.
10.1.1 Prerequisite
Before you complete the tasks in this chapter, you must verify that container
information and container transactions have been entered and processed through the
JD Edwards EnterpriseOne Procurement system and the JD Edwards EnterpriseOne
Sales Order Management system.
See Also:
■ Entering Item Master Information.
Normally, the supplying company purchases the container and introduces it into the
cycle at the filling plant. After you fill and test the container, you either deliver it to the
customer or send it to storage for future delivery. You can also send the full container
to a distributor who, in turn, delivers it to the customer. The customer and distributor
return the empty container to you after the product that it contains is depleted.
As the container repeats this cycle for a period of time, it eventually requires
maintenance. Maintenance is critical for storing the product safely in the container.
You must inspect the container after every cycle through the filling plant. After a
number of cycles, you can no longer use the container because it is damaged beyond
repair, and you must scrap it.
You use container management to track the container through the cycles and manage
the deposits and refunds that must be generated for these exchanges.
Figure 10–2 Integration between Container Management and other JD Edwards EnterpriseOne systems
This chart illustrates the processing in container management and the associated
tables:
Procurement system detects a variance, it writes a new record to the Item Ledger table
and updates the GL accounts.
Usually, you enter the empty container in the JD Edwards EnterpriseOne Procurement
system with no cost so that when it is filled with the bulk product, the cost of the full
container will equal the cost of the bulk product. You can process the empty container
as either an expenditure or a fixed asset. If you select the latter, you can use the JD
Edwards EnterpriseOne Fixed Asset system to track the empty container.
■ Environmental gases.
The environmental gases that are supplied in metal cylinder containers can be
oxygen, argon, helium, nitrogen, hydrogen, and carbon dioxide. Because
government agencies such as the US Environmental Protection Agency (EPA)
require specific storage and transportation procedures for these gases, an even
greater need to track them exists.
Metal cylinders do not have significant structural differences. They vary primarily in
size and capacity but are typically of the same design. They are built to be portable for
the specialized uses that are required by each customer.
Description Quantity
Quantity Delivered 5,000
Quantity Returned 8,000
Net Delivered/Returned –3,000
Closing Balance 6,000
See Also:
■ "Configuring the Sales Order Management System" in the JD
Edwards EnterpriseOne Applications Sales Order Management
Implementation Guide.
You should set up order activity rules for each line type to be processed in these ways:
See Also:
■ "Configuring the Sales Order Management System" in the JD
Edwards EnterpriseOne Applications Sales Order Management
Implementation Guide.
See Also:
■ "Configuring the Sales Order Management System" in the JD
Edwards EnterpriseOne Applications Sales Order Management
Implementation Guide.
■ "Setting Up Bulk Items" in the JD Edwards EnterpriseOne
Applications Bulk Stock Inventory Implementation Guide .
See Also:
■ "Setting Up Bulk Items" in the JD Edwards EnterpriseOne
Applications Bulk Stock Inventory Implementation Guide .
■ Setting Up Container Preferences.
10.2.6 AAIs
AAIs are the user-defined bridge between the day-to-day functions, the chart of
accounts, and financial reports. The system uses AAIs to determine how to distribute
the GL entries that it generates.
For distribution systems, you must create AAIs for each unique combination of
company, document type, and GL class that you anticipate using. Each AAI points to a
specific GL account consisting of a business unit, an object, and a subsidiary.
After you define AAIs, the system knows how to record the transactions. When you
run the Sales Update program, the system creates entries in the appropriate accounts.
You should set up the document type that you defined for container deposit/refund
sales orders in combination with AAI number 4230 (Revenue). You should set up this
AAI to create records in a separate liability account for customer deposits and rentals,
rather than the revenue account. You draw against this account only for container
refunds.
See Also:
■ Setting Up AAIs in Distribution Systems.
See Also:
■ Setting Up Container Preferences.
■ "Invoicing" in the JD Edwards EnterpriseOne Applications Sales
Order Management Implementation Guide.
You normally set up the deposit and rental rates that a customer pays for the use of
containers before you start business with that customer. You can use the standard
method of setting up base pricing in the JD Edwards EnterpriseOne Sales Order
Management system to define the deposit or rental rates for any combination of
customers, customer groups, items (containers), or item groups. If you install the JD
Edwards EnterpriseOne Advanced Pricing system from Oracle, you can also set up
pricing schedules for deposits and rentals in that system.
You can set up the base price of the empty container to equal the deposit or rental rate
if you are not using the JD Edwards EnterpriseOne Advanced Pricing system. The
system uses this price only when processing deposit and refund sales order lines. You
can set up the base price of the full container to equal the price of the product. This
amount is the customer invoice amount for the sale of the product.
See Also:
■ "Setting Up Base and Standard Pricing" in the JD Edwards
EnterpriseOne Applications Sales Order Management Implementation
Guide.
You must enter items for both the full and the empty container codes. For all items that
container management will track as full containers, you must identify a container
code. For example, if item F11 represents a full container, you might assign a container
code of C1 to that item.
Container Code
Enter a code from UDC table (46/EQ) that identifies a storage container or a shipping
carton. A storage container can be an open container where items are stored on the
container (for example, a pallet) or a closed container where items are stored in the
container (for example, a box). You use the Container and Carton Codes program
(P46091) to define storage containers.
Before you can create a preference, you must make sure it exists on the preference
master. If it does not exist, you must add it to the preference master. When the
preferences exist in the preference master, you activate all of the preferences that you
need to use in container management. You then define the preference hierarchy to
indicate the order in which you want the system to apply the preferences. You must
also set the appropriate processing options for specific programs, such as the Sales
Order Entry program (P4210), to use preference information.
10.5.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Verify that the GL offset account for container deposits or rentals has been created
before creating a container deposit/rental preference.
■ Verify that the invoice cycle calculation rule has been set up before creating an
invoice cycle preference.
See "Invoicing’ in the JD Edwards EnterpriseOne Applications Sales Order
Management Implementation Guide.
■ Verify that a base price record exists for the pricing unit of measure to be entered
in this preference before creating a pricing unit of measure preference.
See "Setting Up Base and Standard Pricing" in the JD Edwards EnterpriseOne
Applications Sales Order Management Implementation Guide.
■ Verify that print messages have been created before creating a print message
preference.
See Understanding Setup Tasks.
The system can use the GL offset that is defined in the preference rather than the
one that is defined in the Item Master table so that you can separate potential sales
of empty containers from the actual deposits.
Note: On the Work With Preference Master form, you must ensure
that the effective quantities fields for the Container Deposit/Rental
preferences are not enabled. If the effective quantities fields are
enabled, the system does not process credit orders.
Customer Group
Enter a code from UDC table (40/17) that identifies a group to which you can assign
customers for the Container Deposit/Rental preference. Enter a customer group when
the customers are similar and you want to group them together to define preferences
quickly and easily.
You can define the preference for this group alone or for a combination of customer
group and item or item group.
If you leave both the Customer Number and Customer Group fields blank, the system
applies the preference to all customers. If you select a hierarchy using a customer
number or group, you must enter a value for them.
Item Group
Enter a code from UDC table (40/17) that identifies a group to which you can assign
items for the Container Deposit/Rental preference when you have a group of similar
items.
You can define the preference for this group alone or for a combination of item group
and customer or customer group.
If you leave both the Item Number and Item Group fields blank, the system applies
the preference to all items. If you select a hierarchy using a customer number or group,
you must enter a value for them.
GL Offset
Enter a code that determines the trade account that the system uses as the offset when
you post invoices or vouchers. The system concatenates the value that you enter to the
AAI item RC (for accounts receivable) or PC (for accounts payable) to locate the trade
account. For example, if you enter TRAD, the system searches for the AAI item
RCTRAD (for receivables) or PCTRAD (for payables).
You can assign up to four alphanumeric characters to represent the GL offset, or you
can assign the three-character currency code (if you enter transactions in a
multicurrency environment). You must, however, set up the corresponding AAI item
for the system to use; otherwise, the system ignores the GL offset and uses the account
that is set up for PC or RC for the company that is specified.
If you set up a default value in the GL Offset field of the customer or supplier record,
the system uses the value during transaction entry unless you override it.
Note: Do not use code 9999. It is reserved for the post program and
indicates that offsets should not be created.
all shipments that are made during that month. Another customer might want a daily
invoice.
After orders are confirmed for delivery, the orders are processed by the Cycle Billing
program. The program accesses the invoice cycle preference and calculates the
scheduled invoice date based on the invoice cycle calculation rules and scheduled
invoice date ranges. Generally, you set up invoice cycle calculation rules and
scheduled invoice date ranges during the install process. At a minimum, you should
revise scheduled invoice dates on an annual basis.
You can access the invoice cycle calculation rules from the Work With Invoice Cycle
form. You do not have to set up invoice cycle calculation rules each time that you add
a preference.
Invoice Cycle
Specify the method of invoicing that is used (for example, daily, weekly, monthly, and
so forth).
Note: If you leave any of the key fields blank, you are specifying all
values for that field. For example, a blank in the Business Unit field
causes the system to apply the Print Messages preference to all
business units.
Print Message
Enter a code from UDC table (40/PM) to assign to each print message. An example of
text that is used in messages is hours of operation during holiday periods.
Unlike other preferences, the system does not use the Print Message preference to
override fields. The system adds the print message that you enter here to any other
print messages that you have selected.
10.7.2 Prerequisites
Before running container management extraction, you must verify that:
■ The order line types and order activity rules are set up.
■ The container codes and items are set up.
■ The container deposit/rental and invoice cycle preferences are set up.
Before processing rental fees, deposits, and refunds, you must verify that:
■ The container deposit/rental and invoice cycle preferences are set up.
■ The processing options for the container billing programs are set up to use the
correct version of the preferences, depending on which ones you created for the
company.
■ A sales order line type for container rentals and deposits is set up.
■ A separate document type for container rentals and deposits is set up.
10.7.8 Processing Sales Order Lines for Rental Fees, Deposits, and Refunds
After you have created container deposit charge, rental fee, and refund sales order
lines, you can print invoices for customers who are due to be billed and update all
applicable records. Sales order lines for deposit charges, rental fees, and refunds are
sent through the normal invoicing process and customer sales updates in the JD
Edwards EnterpriseOne Sales Order Management system.
The customer sales update posts entries to the GL and updates these tables with
container transaction information:
■ Sales Order Header File (F4201)
■ Sales Order Detail File (F4211)
■ Item Location File (F41021)
■ Account Ledger (F0911)
■ Customer Ledger (F03B11)
■ Item Ledger File (F4111)
When you process rental fees, deposit charges, or refunds through invoicing, the
system will generate either a transaction or summary invoice, depending on whether
the container billing programs created transaction or summary sales order detail lines.
The transaction invoice contains separate lines for each container transaction that is
recorded for the customer. The summary invoice summarizes all transactions over a
specified period for a single combination of branch/plant, customer, and item.
See Also:
■ "Setting Up Base and Standard Pricing" in the JD Edwards
EnterpriseOne Applications Sales Order Management Implementation
Guide.
■ "Updating Prices" in the JD Edwards EnterpriseOne Applications
Sales Order Management Implementation Guide.
Customer Number
Enter a user-defined name or number that identifies an address book record. You can
use this number to locate and enter information about the address book record. If you
enter a value other than the address book number (AN8), such as the long address or
tax ID, you must precede it with the special character that is defined in the Address
Book constants. When the system locates the record, it returns the address book
number to the field.
For example, if address book number 4100 (Total Solutions) has a long address TOTAL
and an * distinguishes it from other entries (as defined in the Address Book constants),
you could type *TOTAL into the field, and the system would return 4100.
Item Number
Enter a number that the system assigns to an item. This number can be in short,
second, or third-item number format.
Branch/Plant
Enter the appropriate symbol identifier for the nonprimary format for the
branch/plant that is entered. Branch/Plant *ALL will be used if no branch/plant is
entered.
Quantity Ordered
Enter the quantity of units that are affected by this transaction.
Current Quantity
Enter the current quantity of containers that are owned by the supplying company the
customer possesses.
UM (unit of measure)
Enter a code from UDC table (00/UM), such as eaches or boxes, that identifies the unit
of measure for an item.
Deposit Rate
Enter the current rate for the deposits that must be paid by the customer for a
container in their possession.
Current Amount
Enter the amount that the customer must pay for the containers in this transaction,
determined by multiplying the current quantity by the deposit rate.
Document Number
Enter a number that identifies a secondary purchase order, sales order, or work order
that is associated with the original order. This number is for informational purposes
only.
Unreconciled
Select whether the system displays only the container transactions that have not been
reconciled, or all container transactions. Values are:
Blank: Display all transactions.
1: Display only transactions that have not been reconciled.
Special purges have built-in criteria that the system checks before removing any data.
For example, you might want to purge an item master record that has an associated
record in the F41021 table. The built-in selection criterion prevents the system from
purging the item location file record.
You can set processing options to save purged records, which enables you to recover
data that was inadvertently purged.
You can also purge interoperability transactions.
See "Processing Interoperability for Inventory Management" in the JD Edwards
EnterpriseOne Applications Interoperability Fundamentals Implementation Guide.
11.2.2 Prerequisites
Before you complete the tasks in this section, you must:
■ Save copies of the files that will be affected in the purge.
■ Verify that no users are working with the data that you want to purge.
11.2.4.1 Process
Purge Library - FUTURE
Specify whether to save purged records. Values are:
Blank: Do not save any purged records.
1: Save the purged records to a special purge library.
11.2.6.1 Process
Purge Library - FUTURE
Specify whether to save purged records. Values are:
Blank: Do not save any purged records.
1: Save the purged records to a purge library.
Print Mode
Specify whether to print records. Values are:
Blank: Print all purged records. (default)
1: Print deleted records.
2: Print errors.
12.1 Prerequisite
Before you complete the tasks in this chapter, you must verify that only the users who
have been designated to perform system updates have security access to system
update programs.
12.2.3 Setting Processing Options for Item Master Global Update (R41804)
Processing options enable you to specify the default processing for programs and
reports.
12.2.3.1 Process
Proof Mode
Enter Y to run the program in proof mode. The system does not update the Item
Master.
12.2.3.2 Defaults 1
If you leave any of the following processing options blank, the field retains the current
value.
Sub Section
Specify a user-defined code from UDC table (41/S2) that is used for sales coding
purposes. These codes can represent such classifications as color, material content, or
use.
12.2.3.3 Defaults 2
If you leave any of the following processing options blank, the field retains the current
value.
Commodity Class
Specify a user-defined code from UDC table (41/P1) that represents an item property
type or classification, such as commodity type, planning family, and so forth. The
system uses this code to sort and process like items.
12.2.3.4 Defaults 3
If you leave any of the following processing options blank, the field retains the current
value.
12.2.3.5 Defaults 4
If you leave any of the following processing options blank, the field retains the current
value.
Buyer Number
Specify the address number of the person who is responsible for setting up and
maintaining the correct stocking levels for the item.
Leadtime Level
Specify a value that represents the leadtime for an item at its assigned level in the
production process, as defined on Plant Manufacturing Data. The system uses this
value to calculate the start dates for work orders using fixed leadtimes.
Level leadtime is different for purchased and manufactured items:
■ Purchased: The number of calendar days that are required for the item to arrive at
your branch/plant after the supplier receives your purchase order.
■ Manufactured: The number of workdays that are required to complete the
fabrication or assembly of an item after all the components are available.
You can enter level leadtime manually on Manufacturing Values Entry, or you can use
the Leadtime Rollup program to calculate it. To calculate level leadtime using the
Leadtime Rollup program, you must first enter a quantity in the Manufacturing
Leadtime Quantity field in the Item Branch table (F4102).
12.2.3.6 Defaults 5
If you leave any of the following processing options blank, the field retains the current
value.
Planner Number
Specify the address number of the material planner for this item.
Important: When you use this update, you are changing values that
may affect processing and history.
– F4105
Use data selection to specify whether the scope of the update is:
■ A single warehouse only.
■ A combination of warehouses.
■ All except one warehouse.
Verify the changes on the Item/Branch Plant Info. form.
12.2.5 Setting Processing Options for Global Reporting Code Update (R41803)
Processing options enable you to specify the default processing for programs and
reports.
12.2.5.1 Process 1
1. Update Sales Report Code 1 through 6. Update Sale Report Code 5
Enter 1 to duplicate these processing options into the Item Branch record.
12.2.5.2 Process 2
7. Update Reprice Rule
Enter 1 to duplicate this processing option into the Item Branch record.
9. Update Purchasing Report Code 1 through 11. Update Purchasing Report Code 3
Enter 1 to duplicate this processing option into the Item Branch record.
12.2.5.3 Process 3
13. Update Purchasing Report Code 5
Enter 1 to duplicate this processing option into the Item Branch record.
12.2.5.4 Process 4
19. Update Backorders Allowed
Enter 1 to duplicate this processing option into the Item Branch record.
12.2.5.5 Process 5
25. Update ABC Override Indicator
Enter 1 to duplicate this processing option into the Item Branch record.
12.2.7 Setting Processing Options for Segment Cross Reference Generation (R41045)
Processing options enable you to specify the default processing for programs and
reports.
12.2.7.1 Defaults
Cross Reference
Specify a user-defined code from UDC table (41/DT) that identifies the cross-reference
type.
If you leave this field blank, the system will use default value S.
12.2.7.2 Process
Segment Number
Specify the segment number on which to cross-reference. Values are 1 through 10.
Depending on the number of tables that you are updating, the batch program might
require a substantial amount of time. Therefore, schedule this program accordingly.
redefinition program references UDC table (41/LU) to determine the application tables
to include.
12.3.3 Prerequisites
Before you complete the tasks in this section, you must:
■ Save a version of all of the tables.
■ Update the location format for the model branch in the branch/plant constants
and on the Branch Location Definition form, as needed to redefine the new size
and format of the location.
12.3.5 Defining the New Location Format for the Model Branch
Access the Location Field Redefinition Revision form.
Aisle
Enter a code that identifies a location in a warehouse. This code is used in conjunction
with a bin and lot identifier to indicate a specific, tangible storage area within a
warehouse or yard.
Bin
Enter a specific storage location within a warehouse or store. The system uses the bin
with an aisle location to identify a storage area for which width, depth, and height can
be readily measured.
New Size
Displays the number of characters that you can enter in the adjacent location code
field, as defined in the branch/plant constants.
Use the letters A through T to represent the positional values, including separator
characters, in the new location field. The location redefinition batch program starts
with the character at the left of the existing information and moves it to the position
that you indicate. The program continues sequentially, character by character, for a
maximum of 20 characters.
For example, if you enter FG (the sixth and seventh letters in the alphabet) in the Aisle
field, the batch program moves the character at the left to the sixth position and the
Bin
Enter 1 to clear the value in the bin. If you are using the location code for general
reporting purposes and you do not want it to be cleared, leave this processing option
blank.
defined for the model branch and in UDC table (41/LU), correct as needed, and run in
proof mode again.
Important: When you run the R41821 batch program in final mode,
do not enable other users on the system.
In either proof or final mode, the system sends messages to the employee work center
to report a successful completion or to indicate errors that the program found. The
system terminates the program if it finds more than 100 errors.
If errors occur during final mode, the procedure that you use to correct errors depends
on the table in which the error occurred. Generally, the procedure is:
1. Restore all tables that were selected for the run.
2. Correct the problem.
3. Rerun the program for the selected tables.
Use a processing option to specify whether to replace existing values in location
segments with the new values. You might not want to clear location segments that you
use for general reporting purposes.
System
Table Description
F4100 Stores basic information about each warehouse location,
such as zones and level of detail.
F4101 Stores basic information about each item, including:
■ Item number
■ Description
■ Search keys
■ Category codes
■ Default units of measure
■ Process groups for the JD Edwards EnterpriseOne
Warehouse Management system
■ Item dimension group
F4102 Stores default item information, including each item's
process and dimension groups, and other parameters that
are common to every unit of that item in the warehouse.
F4104 Stores item descriptions that the Item Search program
(P41200) uses.
F4105 Stores inventory cost records.
F4106 Stores inventory price records.
F4108 Stores information used in lot processing
F4111 Stores a history of all inventory movements.
F4115 Stores item master history.
Table Description
F4140 and F4141 Stores information about physical inventories using the
cycle count method.
F4160 Stores information about physical inventories using the
tag count method.
F4170 Stores information about activity rules for lot statuses.
F41001 Stores information for day-to-day transactions, including:
■ Location number definition
■ Warehouse control data
■ Default units of measure
■ Inclusion rule, which determines the document types
and status codes to process through the system
F41002 Stores the unit of measure conversion equations that are
unique to the warehouse item and its default unit of
measure structure information.
F41003 Stores the unit of measure conversion equations that are
common to all warehouse items.
F41006 Stores information required to print the Inventory Turn
Report (R41116).
F41013 Stores information about product numbers.
F41021 Stores each item's quantity information, general ledger
class, and lot status in each location.
F41023 Stores definitions for item locations.
F41081 Stores information about lot statuses.
F41112 Stores information summarized from the Item Ledger File
table (F4111), which the Item Ledger - Running Balance
program (P41112) creates and updates.
F41113 Stores information about lot ledgers.
F41829 Stores information that the Item Word Build program
extracted from the F4101, F4102, F4100, F4108, F4101D,
and F4104 tables.
The JD Edwards EnterpriseOne Inventory Management system also uses these tables
from other systems:
Table Description
F4009 Stores information that specifies whether the item
unit of measure conversions are unique for each
item or applicable to each item in the warehouse.
F4016 and F4017 Stores predefined messages that print on
documents such as sales orders and purchase
orders.
F4095 Stores the AAIs used by JD Edwards
EnterpriseOne Logistics and Manufacturing
systems.
F00090, F00090D, and F00091 Stores information used by the Supplemental
Data Setup program (P00091).
Table Description
F00092 Stores information used by the Supplemental
Data by Item or by Item/Branch program
(P00092).
F34004 Stores the order types (sales, procurement, and so
on) and the order statuses at which the system
will create a request.
F40039 Stores information about document types for the
JD Edwards EnterpriseOne Inventory
Management system, the JD Edwards
EnterpriseOne Sales Order Management system,
the JD Edwards EnterpriseOne Procurement
system, and the JD Edwards EnterpriseOne
Customer Service Management system.
F40095 Stores the default warehouse code (branch/plant)
and the default printer output queue for
transactions that you process through the
subsystem.
B.3.2.1 Process
1. Deduct Safety Stock From Available Quantity
Specify whether to deduct safety stock from available quantity. Values are:
Blank: Do not deduct.
1: Deduct.
2. Receipt Routing Quantities Considered On Hand for the following fields: Quantity
in TransitQuantity in InspectionUser-Defined Quantity 1User-Defined Quantity 2
Values are:
Blank: Do not consider.
1: Consider.
B.3.2.2 Display
1. Display Unit Of Measure
Specify a user-defined code from UDC table (00/UM) that identifies the unit of
measure in which to express an inventory item, for example, CS (case) or BX (box).
If you leave this field blank, the system uses the primary unit of measure.
B.3.4.1 Processing
Print Text
Specify if test information will be printed on the report. Values are:
Blank: Print. (default)
1: Do not print.
B.3.6 R410410 — Processing Options for the Profile Information by Data Type Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.6.1 Process
Print Text
Specify if test information will be printed on the report. Values are:
Blank: Print. (default)
1: Do not print.
B.3.8.1 Selections
Enter the Transaction Family Document Types to Include: Based on the UDC 41/TT
Transaction Family 1
Transaction Family 2
Transaction Family 3
Transaction Family 4
Transaction Family 5
Transaction Family 6
B.3.8.2 Dates
Enter the date range to be used in calculating the beginning and ending inventories.
From Date
To Date
You can run the R41185 program in proof or update mode. If you run the program in
update mode, it creates records by item and branch/plant in the Container
Reconciliation table. It also places a 1 in the reconciliation flag field in the Container
Transaction table. The next time you run the Container Reconciliations program, it will
not read these transactions.
B.3.12 R41403 — Processing Options for the Cycle Variance Print Detail Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.12.1 Processing
Variance type
Specify which variance type to use. Values are:
1: Quantity Variance. (default)
2: Amount Variance.
Relation
Specify a user-defined code from UDC table (00/VA) that identifies the relation to use
for the variance selection.
Quantity/Amount
Specify a number that identifies the amount that the system will add to the account
balance of the associated account number. Enter credits with a minus sign (-) either
before or after the amount.
Variance Comparison
Specify which variance to compare. Values are:
1: Compare the percent variance.
2: Compare the unit variance. (default)
displays tracing or tracking information by using processing options for the report.
B.3.14.1 Display
1. Enter Track/Trace
Specify which method the system uses to trace or track lot usage. If you trace the lot,
the system traces from the time of shipment to the time of manufacture all of the items
that made up the current item. If you track the item, the system determines all of the
assemblies of which this item is to be a component from the time of manufacture to the
time of shipment. Values are:
Blank: Trace lot usage.
1: Track lot usage.
2. Mode
Specify the processing mode that the system uses to indicate when specific orders are
being processed. Values are:
1: Use single level track or trace. The system displays only top level items that can be
tracked or traced.
2: Use no intermediates. The system displays only top level items that cannot be
tracked or traced.
3: Use multilevel track or trace. The system displays all items from all levels that can
be tracked or traced.
4: Use multilevel indented track or trace. The system displays all items from all levels
that can be tracked or traced and indents all of the levels based on their value.
Inventory price groups have unique pricing structures that direct the system in
incorporate discounts or markups on items on sales and purchase orders. The
discounts or markups are based on the quantity, amount, or weight of the item
ordered. When you assign a price group to an item, the item takes on the same pricing
structure defined for the inventory price group.
You must assign an inventory price group to the supplier or customer, as well as to the
item. The system interactively calculates discounts and markups on sales orders and
purchase orders.
B.3.18.1 Display
Reorder Point
Specify the reorder point. Values are:
1: Print all items.
2: Print only items at/or lower than the reorder point.
Item Notes
Enter 1 to print item notes.
item or if you leave this field blank, the system will use the primary unit of measure.
5. Calculation Date
Specify the date the system uses to calculate the remaining number of days until the
lot expires.
Rule Description
Rule 0: Used for Manufacturing Issues of Exception rule 0 is necessary because the F0911
Material table uses frozen standard costs and the F4111
table uses the inventory costing method that the
user has chosen. If the methods are not the same,
set up this code.
For documents to which the integrity check
applies, this rule ensures that if records exist in
the Item Ledger table, they also exist in the
Account Ledger table.
Rule 1: Used for Sales Invoices Exception rule 1 is necessary because journal
entries such as revenue or loss entries, taxes,
freight, and intercompany settlements are written
to the Account Ledger table when sales
transactions take place.
The program checks AAI 4240 from the F4095
table to determine which object accounts to
include. The program compares only journal
entries with these object accounts in the Account
Ledger table to the journal entries in the Item
Ledger table.
Rule 2: Used for Purchase Vouchers Exception rule 2 is necessary because journal
entries such as favorable or unfavorable price
variances, taxes, and freight are written to the
Account Ledger table when purchase transactions
take place.
The program checks AAI items 4330, 4340, and
4350 from the Distribution/Manufacturing - AAI
Values table to determine which object accounts to
include. The program compares only journal
entries with these object accounts in the Account
Ledger table to the journal entries in the Item
Ledger table.
Rule 3: Default Rule This is the default rule used by all other inventory
transactions. If the Document Type is not defined
as a Rule 1 or Rule 2 type in 41/IN UDC table,
Rule 3 applies.
Note: If the exception rules in UDC table (41/IN) are set up correctly,
the report prints only incorrect transactions.
B.3.22 R41543 – Processing Options for the Item Ledger/Account Integrity Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.24 R41544 — Processing Options for the Item Balance/Ledger Integrity Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.24.1 Process
Printed Flag
Specify which items to print on the report. Values are:
Y: Print all items on the report.
N: Print only those items with the variance. (default)
Percentage - Acceptance
Specify the amount variance percentage which will cause only items with an amount
variance higher than this percentage to print. If you leave this processing option blank,
the system will print all amount variances. Items with a quantity variance will always
be printed.
Cost Method
Specify a user-defined code from UDC table (40/CM) that identifies the costing
method to use to calculate the unit cost for each item. If you leave this processing
option blank, the costing method for each item will be retrieved from the F4105 table.
2. Ending Date
Specify the date of the batch. If you leave this processing option blank, the system date
is used.
B.3.28 R41560 — Processing Options for the Item Master Directory Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.28.1 Process
Item Notes
Specify whether to include item notes on the report. Values are:
Blank: Do not include item notes.
1: Include item notes.
Print Message
Specify whether to include print message on the report. Values are:
Blank: Do not include print message.
1: Include print message.
B.3.30 R41580 — Processing Options for the Unit Cost Warnings Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.30.1 Variance
Variance Percentage
Specify the variance percentage. For example, if you enter 5 in this processing option,
the system will select any transaction where transaction cost was 5 percent greater or 5
percent less than the current average cost for the item.
B.3.32 R41590 — Processing Options for the Inventory Valuation Analysis Report
Processing options enable you to specify the default processing for programs and
reports.
Cost Number 2
Specify a user-defined code from UDC table (40/CM) that identifies which costing
method to print for the second cost number.
Last In - 01: Default
Cost Number 3
Specify a user-defined code from UDC table (40/CM) that identifies which costing
method to print for the third cost number.
Layer - 06: Default
B.3.34 Prerequisites
Before reviewing the ABC Analysis report, you must:
■ Set up the ABC code percentage breaks in the branch/plant constants.
■ If you plan to run the sales version or the gross margin version of the ABC
Analysis report, verify that you have set the processing options for the Sales
Update program (R42800) so that the system updates the F4115 table.
■ If you decide to include forecasted records in the ABC calculations, you must first
run DRP (Distribution Requirements Planning).
■ Determine which inventory items to exclude from the ABC analysis rankings. To
exclude an item when you run this report, you must set the code on Branch/Plant
Information to bypass the item.
■ Determine which inventory items to exclude from the ABC analysis rankings. To
exclude an item when you run this report, you must set the code on Branch/Plant
Information to bypass the item.
Before reviewing the Supply and Demand report, you must:
■ Ensure that you have correctly identified all sources of supply and demand and
have specified all sources in the supply and demand inclusion rules.
■ Review the formula for determining supply and demand.
■ Review the formula for available to promise.
Before reviewing the Item Ledger/Account Integrity report, verify that you have set
up exception rules in UDC table (41/IN).
Before printing the Customer/Distributor Balance report, verify that the correct items
and container codes have been set up for full and empty containers.
Processing options enable you to specify the default processing for programs and
reports.
B.3.35.1 Display
Rank
Specify how to rank and display the items. Values are:
Blank or 1: Rank and display the items by Sales Amount.
2: Rank and display the items by Gross Margin.
3: Rank and display the items by On Hand Value.
Quantities
Blank: The Item History file will be used for past quantities.
1: Retrieve forecasted quantities from the MPS Summary file if you are displaying the
items by Sales or Gross Margin.
(FUTURE - Forecasting)
B.3.35.2 Process
Amount Totals
Enter 1 to consolidate the amount totals of multiple cost centers. The ABC codes are
based on the ABC percentages for the Branch/Plant ALL.
B.3.35.3 Update
Update Files
Specify whether to update files. Values are:
Blank: No files will be updated.
1: Update files with the new ABC Codes.
B.3.37 R41700 — Processing Options for the Inventory Cost/Price Comparison Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.37.1 Defaults
Override Code
Specify a user-defined code from UDC table (40/CM) that identifies an override sales
costing code. This field is mandatory for costing.
Minimum Margin
Specify warning minimum margin percentage. Items lower than this percentage will
be denoted with **.
Print
Specify which items to print on the report. Values are:
Blank: Print all items. (default)
1: Only print those items that fall lower than the warning minimum margin percent.
B.3.39 R41806— Processing Options for the Country of Origin Update for Items Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.39.1 Default
Turn on the Country of Origin Required Flag in the Item Master Record
Specify whether to turn on the Country of Origin Required flag in the item master
record. Values are:
Blank: Do not turn on the Country of Origin Required flag.
1: Turn on the Country of Origin Required flag.
Enter a Value to be Updated to Item Branch Records with a Blank Country of Origin
Enter the value of country of origin to update the field in item master record. If you
leave the field blank, the system turns on the Country of Origin Required flag in item
master but leaves the value of country of origin field blank.
B.3.41 R41807— Processing Options for the Country of Origin Update for Lots Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.41.1 Default
Enter the Value to be Updated to the Country of Origin in the Lot Master
Enter a value (00/CN) to update the country of origin in the lot master records. If you
leave this field blank, the system uses the value of country of origin from item branch
record to update the lot master.
B.3.43 R41900 — Processing Options for the Update Sellable Field Report
Processing options enable you to specify the default processing for programs and
reports.
B.3.43.1 Process
Update Sellable Field
Specify a user-defined code from UDC table (34A/SA) that identifies whether to
update the Sellable field in the F4101 and F4102 tables. This functionality is for SCP
integrations. Values are:
Blank or 0: Do not update.
1: Update.
Item Number
A number to be assigned to an item. The number can be in short, long, or third item
number format.
Line Type
A user-defined code (UDC) that controls how the system processes lines on a
transaction. The line type controls the systems with which the transaction interacts,
such as JD Edwards EnterpriseOne Job Cost, JD Edwards EnterpriseOne Accounts
Payable, JD Edwards EnterpriseOne Accounts Receivable, and JD Edwards
EnterpriseOne Inventory Management. It also specifies the conditions under which a
line prints on reports, and it is included in calculations. Values include:
S: Stock item
J: Job cost
N: Non-stock item
F: Freight
T: Text information
M: Miscellaneous charges and credits
W: Work order
Order Type
A user-defined code that the system uses to determine the type of work order, based
on the value in the Order Type field. Values are:
01: Unrelated to work order.
02: Manufacturing work order.
03: Manufacturing rework work order.
04: Equipment work order.
05: Service work order.
06: Warranty claim order.
07: Supplier recovery order.
08: Engineering change order.
09: Engineering change request order.
10: Property Management order.
Glossary-1
Document Type
Document Type
A user-defined code from UDC table (00/DT) that identifies the origin and purpose of
the transaction. The system reserves several prefixes for document types, such as
vouchers, invoices, receipts, and time sheets. The reserved document type prefixes for
codes are:
P: Accounts payable documents.
R: Accounts receivable documents.
T: Time and Pay documents.
I: Inventory documents.
O: Purchase order documents.
S: Sales order documents.
Lot/Serial Number
A number that identifies a lot or a serial number. A lot is a group of items with similar
characteristics.
Stocking Type
A user-defined code from UDC table (41/I) that indicates how you stock an item, for
example, as finished goods or as raw materials. These stocking types are hard coded
and you should not change them:
F: Feature
K: Kit parent item
The first character of Description 2 in UDC table (41/I) indicates if the item is
purchased (P) or manufactured (M).
Unit of Measure
Enter a user-defined code from UDC table (00/UM) that indicates the primary unit of
measure for the item. The primary unit of measure must be the smallest unit of
measure in which you handle the item.
This is the primary stock accounting unit (PSAU) of measure that the system uses to
store all inventory. If you change the primary unit of measure, the conversion factors
in the item level conversion table are no longer valid.
The default value for this field is the unit of measure that you specify for the item on
the Item Master Revisions form.
Glossary-2