Skip to main content
Solved

Duplicate Serial Numbers


Forum|alt.badge.img+8
  • Sidekick (Customer)
  • 21 replies

I have a user requesting that we make it so that there can’t be duplicate serial numbers in IFS where there are different part numbers. As far as I can tell, this seems to be a feature of IFS. Is my thinking on this correct? We have a few cases with duplicate serial numbers but different part numbers associated with each. 

Best answer by Thom C

As far as I can tell, this seems to be a feature of IFS. Is my thinking on this correct? We have a few cases with duplicate serial numbers but different part numbers associated with each. 

You are correct - this is by design. 

An interesting topic for a Custom Event. On insert check the Serial No value against the table and error out if the new value exists. 

Some places IFS creates the Serial Number (e.g. in advance on Shop Orders). I suppose certain background operations would just fail if you already had a Serial No value for a different part when one of those processes executed. 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

5 replies

Kelum Pradeep Kumara
Superhero (Employee)
Forum|alt.badge.img+18

Please check the answer of the below community thread and check whether it is related to your query
Serailaized Part in Inventory | IFS Community


Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • 21 replies
  • March 7, 2022

It is slightly related but it doesn’t seem to answer whether it is expected or not. 


Thom C
Hero (Customer)
Forum|alt.badge.img+8
  • Hero (Customer)
  • 22 replies
  • Answer
  • March 7, 2022

As far as I can tell, this seems to be a feature of IFS. Is my thinking on this correct? We have a few cases with duplicate serial numbers but different part numbers associated with each. 

You are correct - this is by design. 

An interesting topic for a Custom Event. On insert check the Serial No value against the table and error out if the new value exists. 

Some places IFS creates the Serial Number (e.g. in advance on Shop Orders). I suppose certain background operations would just fail if you already had a Serial No value for a different part when one of those processes executed. 


Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • 21 replies
  • March 8, 2022

That is very interesting. I wonder how one would go about creating such an event. 


Thom C
Hero (Customer)
Forum|alt.badge.img+8
  • Hero (Customer)
  • 22 replies
  • March 8, 2022
craryit wrote:

 I wonder how one would go about creating such an event. 

Leaving aside the framework necessary to create a New Custom Event upon Insert to PART_SERIAL_CATALOG_TAB you might be able to do something like

DECLARE

V_DUPLICATE    NUMBER;

BEGIN

SELECT COUNT(*) FROM PART_SERIAL_CATALOG_TAB WHERE SERIAL_NO = new:SERIAL_NO INTO V_DUPLICATE;

IF

V_DUPLICATE > 0 THEN Error_SYS.Item_General('Serial No value exists',' ',' ');

END IF;

END;

Invoke the IFS  ERROR handling PROCEDURE Error_SYS.Item_General() passing parameters to create the error message prompt.  

I make no claim that the pseudocode above is suitable for any purpose, much less won’t corrupt your data and destroy your environment. 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings