System Assigned Lot Number Format per Process Type (F4102.SRCE)

Purpose of Document

This note is to guide possible issues in dealing with formatting lot number in EnterpriseOne when Lot Number is to be created on the fly.

Table of Contents

Currently SRCE (Lot Process Type) in (tab) Lot Processing of Item/Branch Plant Info.(P41026) though LayerCodeSource or Layer Code - Source.

In dealing with Automatic Lot Numbering, you may have the following questions:

Q1. When does a certain application create/populate lot/serial number automatically?

When it meets the below condition it populates lot number,

Note:

Q2. What is the maximum size of the string for LOTN?

: 30 when you populate it manually with proper SRCE value.
However if you choose to use SRCE 1, 2, 5 and 6 the maximum value will be:


Q3. What is the primary key of Table F4108 - Lot Master?

The primary Key of F4108 is:

Note: This is important to understand how a certain routine is checking/assigning a new lot number based upon your setup

Q4. What is the routine to create lot number?

Currently Lot number is assigned through:
--> X41LOT - AssignLotNumber (F0002 Get Next Lot Number)
----> B4000620 - GetLotNumberFromNextNumber (F0002 Get Next Lot Number) (only when SRCE is 2 or 6)

Note:

Q5. Where does it store next number for SRCE = '1' and SRCE = '2'?

It stores the next available lot number to be at F0002 - Next Numbers - Automatic as below,

Note:

Q6. How does it format lot number when SRCE=1 or 5?

If (Lot) Process Type = 1 or 5 :
Convert Date passed in to YYYYMMDD string and load Lot with format of YYYYMMDD9999.
Verify that the lot number is unique by checking data from F4108 (Lot Master) based on primary key defined above (LOTN, ITM and MCU). If lot number computed does exist from F4108 then increment it by 1


Q7. How does it format lot number when SRCE=2 or 6?

If (Lot) Process Type = 2 or 6:
Based on next number returned (F0002.N001 where SY='40') check whether data does exist from F4108 based on primary key of F4108. If so, increment it by 1. So for this setup lot number has to be unique across system.


Q8. How does the system know the date format - which can vary (F00921.FRMT - Date Format) user by user?

Regardless of user specific date format it re-formats based on date format mask OSASE,
Date Mask Information:

Refer to <Document 626493.1> E1: BSFN: Date Business Functions in the EnterpriseOne

Actual Implementation:

1 Initialization 0 0 0 0 0 0 0 0 0 0 0 1
Index 0 1 2 3 4 5 6 7 8 9
2 Value ("OSASE") 0 8 / 2 3 / 2 0 1 1
3 Swap it 4 5 6 7 0 1 2 3
Index -new 0 1 2 3 4 5 6 7
4 Result 2 0 1 1 0 8 2 3
5 Final Result 2 0 1 1 0 8 2 3 0 0 0 1
Format y y y y 0 m d d 9 9 9 9

Note:

Q9. Is it possible to have different lot numbering for SRCE value 1 or 5?

No. As explained above, there is a single output format which is YYYYMMDD9999 and note that daily limit is 9999


Q10. In assigning date formatted lot number, which date does the system use?

Transaction Date (date today in client) but if this value is null date then system date in your logic server will be assigned through API JDEDATEToday().