Ir al contenido principal

How to Configure Auto-Number on Customers


We were recently asked during an installation of Sage ERP X3 if it was possible to have the Customers Auto-number when adding new Customers. The answer is of course yes. So I thought this can't be a unique request, which lead to this blog post.
Before I go any further I should explain that Sage ERP X3 has a high-level category known as Business Partners (BP for short). A Business Partner can be a Customer as well as other types of interactive alliances that you may have. Yes they can even be multiple Business Partner types at the same time. This is a nice feature but I thought it worth mentioning since at first it may be confusing but also just to outline this before actually exposing it later in the article. The Seq Counter is then attached to the Customer Category. In this case you see it as 'US'.
The field that we will be adding this functionality to is show in Figure 1.
Figure 1 – See the BP Partner Customer field (Common Data -> BPs -> Customers)
So let's now go to configure the Parameter within the SAFE X3 framework that controls this setting. What we are looking to alter is the Sequence Number Definition for the Sequence Counter for the Customer. This Sequence Counter is 'BPC'. You can find this by pressing the F6 key while on the Customer ID field on the Customer maintenance window. I will cover hot-keys in a future blog.
Now that we know what we want to change we can go to the Parameter->General Parameter->Sequence Number Definition->Structures task from the All Menus section. (see Figure 2) Then select the Seq Counter 'BPC'. You will see the Components listed. You can configure how you would like the mask defined for the Customer including the ability to Auto-Number. This is just to prepare a type of Customer Counter. You can create a new one off of the BPC as a template or just create a new one. I am just using the base BPC counter of Sage ERP X3 for this blog.
Figure 2 – Structures maintenance window
To complete the configuration you go into the customer category and assign the sequence number BPC so it allows the system to use the sequence counter.
Figure 3 – Customer Category (Common Data -> BPs -> Customer Category)
Now when you add a Customer and you select the Category 'US' it will use the Customer Counter mask you defined.
You can also use this basic logic to do the same to Items, Vendors, Salespersons, etc.
I hope you found this useful. Until next time!

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más