x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 134 subscribers
  • Views 473 views
  • Users 0 members are here
Browse Forums
Announcements
259
topics
35
replies
General Discussion
5k
topics
14k
replies
Sage Data & Analytics
58
topics
97
replies
Sage Enterprise Intelligence
220
topics
442
replies
Sage Intelligence Reporting
121
topics
322
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

    In the child folder, go to Setup > General parameters > Parameter values:  in the left list open the "ADX Adonix" chapter.  Open the FMT Formats Group, select "Detail".  In the TUL01 parameter value, the standard setting is cA#:-/_   Add the period after the underscore.  Select <OK> then Save.  Log out of X3 then re-login for it to take effect.  This will allow the period character in product codes, customers, etc.  Must be done in all child folders the period is to be allowed in key fields.

Reply
  • 0

    In the child folder, go to Setup > General parameters > Parameter values:  in the left list open the "ADX Adonix" chapter.  Open the FMT Formats Group, select "Detail".  In the TUL01 parameter value, the standard setting is cA#:-/_   Add the period after the underscore.  Select <OK> then Save.  Log out of X3 then re-login for it to take effect.  This will allow the period character in product codes, customers, etc.  Must be done in all child folders the period is to be allowed in key fields.

Children
  • 0 in reply to Larry Walker xkzero

    This should be considered as a customization so that change can be done in the early period of an implementation without having a large impact on the cost (because most of the testing is still ahead of you).
    BUT if anyone else is using this discussion for a different context, please beware this should not be done without proper testing.

*Community Hub is the new name for Sage City