Skip to content

x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 127 subscribers
  • Views 790 views
  • Users 0 members are here
Browse Forums
Announcements
288
topics
43
replies
General Discussion
5k
topics
15k
replies
Sage Data & Analytics
46
topics
108
replies
Sage Enterprise Intelligence
183
topics
479
replies
Sage Intelligence Reporting
116
topics
325
replies
Britt Madden

Product Numbering

Posted By

Hello Sage X3 Community,

We are in the early stages of implementing Sage X3.  Several of our product numbers have a period in the number.  Our product guides are printed with the numbers with periods and we do not want to have to retrain our customers with new part numbers.

My questions are...

Does anyone have product numbers using a period?  If so, how did you work around the field format type limitation?  Is there a way to change a setting to allow for a period to be used in this field?  Anyone using a user defined field or dimension to overcome this issue? 

Below is an image of the message we get when we try to set up an item using a period.

Parents
  • 0

    One more follow-up to this topic, is there a way to increase the item number field from 20 to 30 characters?  Below is an example of an item that is 24 characters long.  

    HDAMTLN450-3545-180TJ-25 

    HD =      heavy duty version

    AMT =    a particular style of #######, with a 185 front housing and standard rear housing

    LN =       fits a ##### #### with the old-style ######### ### bushing

    450 =     450 ###

    3545 =   for .035 to .045 #######

    180TJ = has a ###### installed, instead of the standard AMT ####### front end fitting

    25 =        25' long ########

    This part number gives our assembly department all the information they need.

Reply
  • 0

    One more follow-up to this topic, is there a way to increase the item number field from 20 to 30 characters?  Below is an example of an item that is 24 characters long.  

    HDAMTLN450-3545-180TJ-25 

    HD =      heavy duty version

    AMT =    a particular style of #######, with a 185 front housing and standard rear housing

    LN =       fits a ##### #### with the old-style ######### ### bushing

    450 =     450 ###

    3545 =   for .035 to .045 #######

    180TJ = has a ###### installed, instead of the standard AMT ####### front end fitting

    25 =        25' long ########

    This part number gives our assembly department all the information they need.

Children
  • 0 in reply to Britt Madden

    Hi  

    I have always considered this change being too impacting because this change the size of the ITMREF field in so many screens and reports that the cost will be very large (especially the testing). In addition, you are not sure that some processes will not failed due to this change, so again a massive effort in testing (up to 3rd party integration).

    I would recommend you to change the product codification rules to stick under 20 digits. This still offer over billions of combinations.

    Is there anyone in this forum with experience on doing this kind of change?

    To soften the impact of a prodcut code, you can offer to store this old value in the ITMDES3 field and make available upon product selection or try to enlarge the UPC code (less impacting) to store this value. But from experience, if you decide to change the product code, it is better to avoid letting the end-users using both the old or the new code. Else, the transition will never be complete.

  • 0 in reply to Julien Patureau

    Thank you !  I appreciate your help and guidance.

*Community Hub is the new name for Sage City