Lot number

(2) Share

Report

Posted on by MH-03040810-0

Hi! Some of our suppliers use simple lists for batchnumber allocation, this means that the same or several products can have the same batch number but different BBD. Most often it just passes the system quietly, but from time to time the batch from before is reported to our EDI-customers. It seems that the system is hard coded to go by FIFO-allocation, although the date is sometimes years back. Has any of you encountered the same problem, and what can be done to solve it, besides from never using the same batch/lot number?

Kind regards

Mårten

Categories:

Dynamics 365 Supply Chain Management

batch lot.pdf

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Holly Huffman 6,530 Super User 2025 Season 2 on at

Like (2)

Report
Good morning, afternoon, or evening - depending on your location :)
Hope you are well today!

This issue arises because the system is likely configured to use FIFO (First In, First Out) allocation for batch numbers, which doesn't account for differing Best Before Dates (BBD) when the same batch number is reused. Here are some steps and recommendations to address this problem:

Steps to Address the Issue:

Review Batch Allocation Rules:

Check the system's batch allocation settings. If FIFO is the default, consider switching to FEFO (First Expired, First Out) allocation, which prioritizes batches based on their expiration dates rather than their entry dates.

Enable Batch Attributes:

Ensure that the system is configured to consider both batch numbers and their associated attributes, such as BBD, during allocation. This can help differentiate between batches with the same number but different expiration dates.

Customize Allocation Logic:

If the system doesn't natively support FEFO or similar logic, consider customizing the allocation process. This might involve creating a script or rule that checks the BBD before allocating a batch.

Implement Validation for EDI:

Add a validation step in the EDI process to ensure that the correct batch (based on BBD) is reported to customers. This can act as a safeguard against incorrect allocations.

Educate Suppliers:

While avoiding duplicate batch numbers is ideal, you can also work with suppliers to ensure that batches with the same number are clearly distinguished by their BBD in documentation and labeling.

Test and Monitor:

After making changes, thoroughly test the system to ensure that the new allocation logic works as intended. Monitor the process to catch any discrepancies early.

Switching to FEFO allocation or implementing custom logic should help resolve this issue without requiring a complete overhaul of your batch numbering practices.

Hope this helps :)

Was this reply helpful? Yes No
MH-03040810-0 9 on at

Like (0)

Report

Hello Holly, mid day in Sweden.

Thanks for the input, now we can take these ideas to our support and see if this can be solved.

Have a great week!

Kind regards

Mårten

Was this reply helpful? Yes No

Join the conversation

Community site session details

Lot number

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Supply chain | Supply Chain Management, Commerce

Featured topics

Product updates

Community site session details

Lot number

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Supply chain | Supply Chain Management, Commerce

Featured topics

Product updates