14 Days of Sage ERP X3 – Day 14 of 14 – X3 Connection Settings Configuration


Well I am sure if you have been following these that you are ready for me to finish. Let me assure you that I am happy to be coming to an end as well. I promise I will continue to add to my ramblings for the last 14 days in the future. I want to thank you for stopping by and I hope you enjoyed what I have shared. It was my pleasure to finally put down on paper what I have been compiling in my head.

The connection Settings for available folders on the login screen must be configured for each profile that logs into a workstation with the client software installed. We use this simple process to copy the connection settings across all profiles on a workstation by executing a windows batch file. Here are the steps involved:

  1. Log on to a workstation as a local administrator and launch the X3 client
  2. Click the screwdriver icon to create new connection settings

  3. Set up all the pertinent folders you wish to connect to
  4. Log into X3 via each connection to verify it is configured correctly
  5. Navigate through Windows Explorer to the profile you are logged in as:
    1. C:\Users\[username]\AppData\Roaming\Sage\Safe X3 Client\V1
  6. The contents of the AdxCnx.cfg file in this directory contain all the connection settings you just configured. Here is a sample file with 4 folders configured:
    1. X3#[sqlserver]#1806#########1#X3 (1806)#admin##DOMAIN\sagert#vqrgrQmsxuTrrw3uvatvauvaWdo#[sqlserver]#1#[sqlserver]#0#0#####BRY#1#X3V6##Sage ERP X3#V6.2#TRAINV6#[sqlserver]#1806#########1#TRAINV6 (1806)#admin##DOMAIN\sagert#vqrgrQmsxuTrrw3uvatvauvaWdo#[sqlserver]#1#[sqlserver]#0#0#####BRY#1#X3V6##Sage ERP X3#V6.2#PILOT#[sqlserver]#1806#########1#PILOT (1806)#admin#vmvvaTo2vccUm#DOMAIN\sagert#vqrgrQmsxuTrrw3uvatvauvaWdo#[sqlserver]#1#[sqlserver]#0#0#####BRY#1#X3V6##Sage ERP X3#V6.2#PROD#[sqlserver]#1806#########1#PROD (1806)#admin#ukrgrTevccTkrqweor#DOMAIN\sagert#vqrgrQmsxuTrrw3uvatvauvaWdo#[sqlserver]#1#[sqlserver]#0#0#####BRY#1#X3V6##Sage ERP X3 #V6.2#
  7. Copy the AdxCnx.cfg file to the X3 SQL server to a shared folder that is accessible to the X3 workstations
  8. In the same shared folder, create a windows batch file with the following command. This will copy the AdxCnx.cfg file from the server to the computer the bat file is executed on, search through the existing profiles for the existing AdxCnx.cfg file, and replace it with the configured one from the server
    1. replace “\\[servername]\[sharename]\AdxCnx.cfg” “C:\Users” /S/P
  9. Log into an X3 workstation and navigate to the shared directory and execute the bat file you just created (as an administrator). This will execute the copy to each profile.

I want to thank Cliff Horst from our team for his assistance with this posting.

I will be offline for you few days spending time with my wife…talk to you when I get back!

Advertisements

14 Days of Sage ERP X3 – Day 13 of 14 – Commissions in Sage ERP X3


The reason I picked this topic was it was an area we need some additional clarification on. So we compiled some information. Before I begin, I need to thank Tom, from the Sage ERP X3 team for his valuable input that I used as a baseline for this post.

The Commissions are not presented in the documentation, as there are many ways to configure them.  If you want to link specific products with specific reps, and, specific customers then Price books will be the best way to manage this. Sage ERP X3, at a basic level, will assign a commission at time of sales order based upon rep assignment to the line ordered.  For example, if no rep is referenced, then, no commission is calculated.  Also, the sales rep must be referenced on the ship-to customer address for the default to occur at the line during sales order entry.

 

Set up a sales rep with the commission factors:


 

The customer must also have commission set up:


 


 

Optional Price book with Commission factor over-ride:


 

Sales order entry:


 

There are many additional configuration and variations way too many to cover here… remember to start with this from the simplistic level and work your way up to the complex, the complex level being managed with price book definitions. I will try to make a more complex sample in a future post.

14 Days of Sage ERP X3 – Day 12 of 14 – How to Deploy Sage ERP X3 Web Services


Sage ERP X3 Web Services

You have to install the necessary Patches for the version of Sage ERP X3 you are on to get the Web Services functionality. Once you these installed it will require configuration in the following areas.

  • X3 Console
  • X3 Client
  • X3 Web Server

The order of these steps is important. The purpose of the steps is to publish the Web Services to the various X3 Folders. I am assuming that the Apache servers are already configured properly.

 

Installing the Patch containing Web Services (this may not be necessary depending on what version of Sage ERP X3 you are starting with)

As of this writing the Patch necessary for Sage ERP X3 v6.1 is A41. (NAV6-XA41.dat)

Login into the Client of Sage ERP X3 under Folder ‘X3’ and navigate to the Development -> Utilities -> Patches -> Patch Integration function.

Locate the patch file directory where you placed the dat file. Make sure you select Patch Integration and Comment Overwrite then click OK.

 

 

Publish the Web Services

Create an X3 User for the Web Services –

Parameters -> Users -> Users by copying from the User WEB.

Make sure to create a password for this new User. In order for the connection to work properly it needs a Password, plus it is just good practice to have a password on this user. Make sure this user has the checkbox for Web Services connection as shown above.

You need to logout of the current user and login as the User you are using above then go to Usage -> Users -> Password Change.

 

 

On the Server running the X3 ConsoleLaunch the SAGE X3 V1 Management Console and click on Web Servers section.

You need to select the X3 Web Server from the Left List, then Click on the Solution Identifier in the Right Window. The Folders will be displayed in the bottom window pane. Check the Folders you wish to publish to. Then click the Apply to publish the Web Services to the selected Folders.

NOTE: If you are unable to open adxinstalls.xml verify that the Windows Service for ADXADMIN is running.

You can see the process running under the Details button as shown below during the Publication process.

 

Now select the Folder you wish to configure the Web Services for. You will need to do this for each Folder individually if you want to enable Web Services for more than one Folder.

 

 

You need to provide the following information for each Web Service pool.

Pool Alias: This must be unique. This is how you will call the Web Service for this Folder.

Pool Language: This relates to the

Pool Userid: This is the X3 user you configured in the previous step.

Pool Password: This is the password for the X3 user.

Operating System Userid: This is a valid user for the OS.

Operating System Password: This is the password for the OS user.

MaxSize: Yo

InitSize: Yo

Autostart: This states if this Web Service pool should be auto-started.

Reserved: t

 

See the following screen as a sample of a completed configuration.

Once you have this configured then click Apply. In the picture above once this is applied you will see the (0) switch to a (1) in the upper window pane, this being the first instance.

Then in the X3 client you should see you valid Web Services Pool in Development-> Utilities -> Miscellaneous -> Web Services Pool.

 

You can also verify that the Sage ERP X3 Web Service patch is installed at Development->Utilities->NA Utilities->System Inquiry.

Now to configure and test the Sage ERP X3 Webservice Server (this will provide the Website ID for the next steps)

NOTE: If you get this message it means that the latest web service is not published. You can try reinstalling the XA41 patch. If the patch is installed and you see the Web Services in Sage ERP X3 then you can just perform validation on the Web Services to republish them.

The pool tried to invoke subprogram XTDSOH but the XML service description file for XTDSOH did not match the program’s expectations. In .net’s world this would be like an out of date wsdl file.

If you need to verify and validate the Object go to Development->Processes->Object select the Object and click on Validation.

 

If you need to generate the Web Services go to Development->Processes->Processes->Web Services. The XA41 Patch contains the Web Services that begin with ‘X’.

 

If everything appears to be installed correctly to this point you may just need to publish the Web Services. You can do this by selecting the Web Service and click on Validation.

 

Additional Web Service Configuration

In order for the Web Services to process orders into Sage ERP X3 you will need to configure the following information for each Folder you wish to use.
This information at Website Web Services->Web Service Parameters is used to determine certain default values when submitting orders.

It is important that you fill in the Defaults values on the General tab. If you do not fill in these values you will receive errors when trying to process orders, especially the Sales Site and Shipping Site fields.

The Websites tab above should show the published Website ID for you to associate to this Folder.

Then create login id’s to be used by your Web Commerce solution. These login id’s will be linked with a Customer in Sage ERP X3.

For the Credit Card Customer field if you select No then this customer can create orders based on the Terms on their Customer account or they can use a Credit Card. If you choose Yes then they are only able to place orders with a Credit Card.

One additional area to verify that Web Services license is activated.

 

To Verify the Web Service using the WebService tester

Go to the Web Server that is hosting the Web Services. Click on the WebService tester link. You need to fill in the following information. After you have entered the information then click the Save Context button.

Pool entry Group: This is the Web Service Pool name you created earlier.

User id: The Sage ERP X3 user you created.

Password: The password for the user.

Language: Select the language you wish to use for this Web Service.

 

Click on the Sub program link, key in one of the Web Services to consume. I have entered XTDSOH below, click on the “WebService Description” button. This should contain valid information in the Reply as shown below.

 

The Sage ERP X3 Web Services are more like a mapping interface API. They are not what you might be used to in traditional SOAP development. They are a wrapper around the base Sage ERP X3 logic. I only point this out so you are aware of this before you start looking for traditional WSDL files.

14 Days of Sage ERP X3 – Day 11 of 14 – How to Import Data from Sage ERP X3


This process describes importing of transactions from two different systems. The first example is a Point of Sale (POS) system. The second example is an eCommerce system. They are both disparate systems. The assumption in this is example is that the transactions are being exported on a daily basis from the respected source system. The import jobs in these examples are used to bring the transactions into Sage ERP X3 on a daily basis.

In the steps described below I also realize that once you are logged into Sage ERP X3 that you would just be switching functions and it would not require you to log in each time. I just did that to avoid any confusion if you were beginning at just that step. I have also not supplied any of the SSIS scripts to massage the example files. Your instance may not require any massaging of files.

POS Import:

Create the Files to import: (this is just for this example and your unique situation may differ)

  1. Generate a data file from POS for invoices to import called “LS POS.txt” and place it on the X3 server at \\servername\X3V6DOC
  2. Generate a data file from POS for payments to import called “Payments_(To_Import).iif” and place it on the X3 server at \\ servername \X3V6DOC
  3. Run the following jobs in SQL Server to manipulate the files for import into Sage ERP X3:
    1. POS Import Stock Issues: Creates file for Miscellaneous Stock Issues in Sage ERP X3 (all line items with a positive quantity on the invoice)
    2. POS Import Stock Receipts: Creates file for Miscellaneous Stock Receipts in Sage ERP X3 (all line items with a negative quantity on the invoice)
    3. POS Import GL: Creates file for a summarized GL Posting for everything in the LS POS.txt source
    4. POS Import GL Payments: Creates file for a summarized GL Posting for everything in the Payments_(To_Import).iif source

    NOTE: The 4 SQL Jobs outlined above are SSIS scripts created to manipulate the file format to from the POS system to the layout of the Sage ERP X3 import format. This step may not be necessary if you have the files already in the format for the import routines. These jobs can be manually executed from SQL Server Management Studio, or scheduled to automatically run on a set schedule.

 

Import the data into Sage ERP X3:

Template “SMO” – Imports the Miscellaneous Stock Issues:

  1. Log into Sage ERP X3 and go to Usage -> Imports /Exports -> Imports
    1. Key in “SMO” in the template field
    2. Choose Server as the location and Tab to enter the path to the data located at C:\Sage\SageX3V6\X3V6DOC\LSPOSX3.txt

  1. Click OK to import the data into Sage ERP X3

Template “SMR” – Imports the Miscellaneous Stock Receipts:

  1. Log into Sage ERP X3 and go to Usage -> Imports/Exports -> Imports
    1. Key in “SMR” in the template field
    2. Choose Server as the location and Tab to enter the path to the data located at C:\Sage\SageX3V6\X3V6DOC\LSPOSX3Ret.txt

 

Template “GASRKL” – Imports the Summarized GL for the POS Invoices and Payments:

  1. Log into Sage ERP X3 and go to Usage -> Imports/Exports -> Imports
    1. Key in “GASRKL” in the template field
    2. Choose Server as the location and Tab to enter the path to the data located at C:\Sage\SageX3V6\X3V6DOC\LSPOSGLX3.txt

 

  1. Log into Sage ERP X3 and go to Usage -> Imports/Exports -> Imports
    1. Key in “GASRKL” in the template field
    2. Choose Server as the location and Tab to enter the path to the data located at C:\Sage\SageX3V6\X3V6DOC\LSPOSGLPMTX3.txt

 

eCommerce Site Import:

Create the File to import:

  1. Generate data files from the eCommerce site for sales orders to import called “OrderHeader.txt” and “OrderDetail.txt” and place it on the X3 server at \\servername\X3V6DOC
  2. Run the following job in SQL Server to manipulate the files for import into Sage ERP X3:
    1. BW Import: Create file for Sales Orders in Sage ERP X3

     

    NOTE: The 1 SQL Job1 outlined above are SSIS scripts created to manipulate the file format to from the eCommerce site to the layout of the Sage ERP X3 import format. This step may not be necessary if you have the files already in the format for the import routines. These jobs can be manually executed from SQL Server Management Studio, or scheduled to automatically run on a set schedule.

     

Import the data into Sage ERP X3:

  1. Log into Sage ERP X3 and go to Usage -> Imports/Exports -> Imports
    1. Key in “SOHFL” in the template field
    2. Choose Server as the location and Tab to enter the path to the data located at C:\Sage\SageX3V6\X3V6DOC\BWOrderX3.txt

  1. Click OK to import the data into Sage ERP X3

14 Days of Sage ERP X3 – Day 10 of 14 – How to Export Data from Sage ERP X3


I picked this to set up my next blog which is going to focus on Importing Data. These two topics are always highly requested tasks. People want to know how to get data out and get data into Sage ERP X3. The other thing that is not so obvious is where are these tasks located both in terms of how to run existing import/exports as well has creating new templates or customizing existing ones.

I picked the Products table because they want to do cleanup of things related to the Product master or they want to export it to provide it to their customers or vendors.

  1. Go to Usage -> Imports-Exports -> Exports
  2. Choose a template (ITM for example)
    1. Uncheck the Chrono Management box.
    2. Choose whether to create the file on the server or the client. This selection will determine where the Data file path is located on the Sage ERP X3 Application Server or on the client that is running the Export.
    3. Click OK.
    4. Choose the location of the export file you are creating.

 

The above was simple running an existing Export Template. The creation of Import/Export templates and other related tasks is located under Parameters -> Usage -> Import/Exports. I am not going to go through all of the tasks or even the Window fields. You can find this information in the Help system.

One thing to remember if you create anything new or modify an existing Sage ERP X3 function to use the Activity Code field to help you identify your changes as well as prevent them from being overwritten by a future patch.

 

 

14 Days of Sage ERP X3 – Day 9 of 14 – How to Add a Custom Report in Sage ERP X3


Most times clients do not use the AP Check format that is delivered with Sage ERP X3. So for this example I am going to be creating a custom version of AP Checks. We will be starting with the base format and just making a copy of it to use instead of starting from scratch.

  1. Go to Development -> Processes -> Reports
  2. Pull up an existing report code (e.g. XBCHECKS)
  3. Add a “Z” in front of the report code to indicate it is a customer changed report
  4. Change the Crystal Report Name to reference ZXBCHECKS

  5. Click on the Parameters tab and change any references to the old report name

  6. Click the Create button to save the new report code
  7. Go to Parameters -> Destinations -> Print Codes
  8. Sort the list by Print Code and check through the list to see if the report you are copying exists
  9. If the report exists, insert a new line in the grid referencing the new print code

  10. Click Save to save your changes for the new report
  11. Go to Parameters -> Destinations -> Default Values
  12. Search through the list on Report Code for the existing report
  13. Pull up the entry for the existing report
  14. Select the contents of the grid and copy/paste them into Excel
  15. Add a “Z” in front of the reports field to reference the newly created report
  16. Add the default values by copying and pasting from Excel into the grid (each field individually)

  17. Once the parameter defaults match, click the Create button
  18. In windows explorer, make a copy of the existing crystal report file and rename it with a Z in front

    (\\servername\C$\SAGE\SAGEX3V6\X3V6\Folders\X3\REPORT\ENG\ZXBCHECKS.rpt)

  19. To have a report specific to an individual folder, create it in PILOT or PROD respectively. Otherwise the individual folders use the report from the X3 reference folder.

    (\\servername\C$\SAGE\SAGEX3V6\X3V6\Folders\PROD\REPORT\ENG\ZXBCHECKS.rpt)

  20. In X3, go to Reports -> Reports and select the newly created report code, enter the parameters and click the Print button to run the new report

  21. Make any needed changes in Crystal Designer to the Z form.

     

 

14 Days of Sage ERP X3 – Day 8 of 14 – Additional Learning Resources from the Sage U ERP Team


While I have been working through this process I have received some emails from the Sage U ERP Learning Team. The ‘U’ stands for University. I was going to discuss 2 of these topics but they have done an outstanding job, it would be a better resource for you than my writing.

Their online home is located at www.SageU.com. However they have continued to publish mini overview videos and post them on YouTube. Here are the latest videos released this week.

Sage ERP X3 Enterprise Webtop

The Sage Enterprise Webtop allows you to connect to Sage ERP X3 through widgets using the Netvibes publishing platform. You have secure access to the Sage ERP X3 system on any mobile device in a personalized dashboard environment.

Sage Search Utility

Sage Search is a powerful search engine that allows you to search all the data within your ERP system. It provides a single point of access to information regardless of source, format, or location.

New Dashboard Layout Options

Learn about the new layout options in the Sage ERP X3 that allow you to easily mix and match gadgets of information to personalize your dashboard.

Sales Signature Workflows

New features regarding sales workflows allow for the definition of signatures for quotes, sales orders, and sales open orders.

New Inquiry Functions (version 6.2)

A new task, List of WOs, allows you to view a list of work orders according to criteria entered. This new task can be accessed from many areas in Sage ERP X3.

There are more videos under the SageUERPLearning category on YouTube. Make sure you check those out as well. Randy Bacchus and the rest of the SageU team do a great job.

14 Days of Sage ERP X3 – Day 7 of 14 – How to Configure Order Entry to Default to Ship-To tab, etc…


Well we are half way through this crazy adventure I decided to take on. I hope you are finding it useful. Today we will discuss several enhancements you can make to Sales Order. Some of these changes are done to the Customer screen because the values from the Customer Ship-To carry through to the creation of a new order for the said Customer. I have broken this down into 3 enhancements in the blog just for clarity.

Enhancement #1: Default to Ship-To Customer tab to have the Pick Ticket and Pack Ticket and Work Days automatically checked on new customer

The purpose of this change is so that when you create a Sales Order for this Customer and corresponding Ship-To the Pick Ticket and Pack Ticket will automatically be checked on the new order. The first thing you need to know is what form and what fields. One of the easiest ways to determine this, we have already covered, the use of the F6 hot-key. So go to the Customer window, Common Data -> BPs -> Customers, then the Ship-To Customer tab. Click on the Picking Tick or Packing Slip under the Reports section. Now press F6. I pressed F6 while on the Picking Ticket field in this screen shot. Now I know the Screen name (BCP4) and the Field Name (XNPRFLG).

Picking Ticket

Packing Slip

Working Days (here is Monday, you get the idea for the rest of the Work Days)

 

All of these changes can be made using Development -> Processes -> Screens -> Screens.

Select the BPC4 screen and click on the Fields tab. You want to change the Default Value column to 2 for the Picking Tick, Packing Ticket and Days of Week (Monday – Friday). First locate the Field. It will have the same name without the ‘X’. Scroll to the right to the column Default Value. Save your changes. Then you need to perform Validation on the screen to publish the change.


NOTE: The reason this Default Value is 2 is that this is 1 for unchecked and 2 for checked.

 

Enhancement #2: When entering sales order lines, product and quantity are the only fields to which we need to tab, how to limit the columns of entry on Order Lines…

Navigate to Development -> Processes -> Screens -> Screens.

Select Screen SOH4 and go to the Fields Tab. Scroll to the right to the Input column. Change the Input values to meet your requirements. In the case I was trying to satisfy, I would change the Input value to Display for all of the Fields except the ITMREF and QTY. Save your changes. Then you need to perform Validation on the screen to publish the change.

 

 

Enhancement #3: Can we default a sales quantity of 1 to each order line that we add?

Navigate to Development -> Processes -> Screens -> Screens.

Select Screen SOH4 and go to the Fields Tab. Select the QTY Field and scroll to the right. Enter the Default Value, in this case we were making it 1. Save your changes. Then you need to perform Validation on the screen to publish the change.

I hope you found this assortment of enhancements valuable. While you may not need these exact changes, I was also trying to cover a wide range of changes so that you could see how the SAFE X3 framework can be used to enhance your installation.

14 Days of Sage ERP X3 – Day 6 of 14 – How Can I Track Changes I Make to My System


Let me start by saying there are a lot of moving parts inside of Sage ERP X3. This makes it extremely important for you to do all you can to track any changes that you make to the system. This allows you to do all you can to protect yourself from overwriting changes. This blog is not all inclusive and is to server as a general overview. If you want more information on this topic please refer to the Sage ERP X3 help. You can also take various Sage ERP X3 training. This is covered in System Administration as well as the Developer Track in more detail.

Activity Codes
can and are used for a variety of reasons in Sage ERP X3. I am outlining here how they can protect your changes from being overwritten. All changes should be marked with an activity code because patching will not overwrite a component that has an activity code that is not included in the patch.

 

  • When the folder is revalidated, the object dictionary (tables, screens, etc.) is copied from the reference folder, overwriting existing objects. Only objects or object elements (field, indexes, etc.) that are flagged with a specific activity code are protected. Header level is the General Tab, do this on your own custom tables.
  • Do not put a value in the Activity Code at the header level of a base X3 table. This will prevent any table alterations with a patch from being deployed which can cause errors with code.
  • You can also put an Activity Code at the field level which will protect the field level from patches.
  • You can put an Activity Code on Screens, Objects, Windows, as well as Fields within these components.

Activity Code that we would create should start with X, Y or Z. This allows you to inquiry on the enhancements. These rules are loosely enforced meaning they are for guidance and best practices recommendations. They are not strictly enforced rules by the system.

  • X is used for US created and vertical enhancements
  • Y is used for what you create for a customer as a Partner (Sage recommends to use one activity code per customer no matter how many mods)
  • Z is used for a customer to use for anything they may do by themselves

Activity Code in relation to Database Tables

  • The Activity Code field is used in conjunction with the Module field to determine whether or not the table will be created in the database of the folder.
  • A table starting with X, Y, or Z is considered to be specific/custom and is not affected by a version change. These activity codes can be placed at the line level.

 

How to create an Activity Code in your implementation?

How to use the Activity Code in your implementation?

How to identify an Activity Code used within your implementation?

  • Searching: Development -> Utilities -> Searches -> Activity Code

     

  • Mass Validation of all screens, objects, windows, etc by Activity Code. Development -> Utilities -> Dictionary -> Validation

     

  • Patches: This can be to test a patch install or even to create a patch from your customized enhancement. Development -> Utilities -> Patches ->

Patch Creation

Test a Patch

Custom modifications are protected by an activity code and Patch Test will display the Sage ERP X3 element (screen, table, window, etc.), along with the activity code when a potential conflict is present.

 

Configuring an Activity Code

 

You can create a new Activity Code at Development -> Data and Parameters -> Development Setup -> Activity Codes. Once you have an Activity Code Created you can use this for all of your changes. Here are 3 examples of how to use this Activity within the system for tracking. For the examples I have created an Activity Code ‘RES’ for tracking my changes.

 

  • Create a Table – You can put an Activity Code at the Table, Fields, Index, or View levels.

     

    Header

     

     

    Field

     

     

Index

 

 

 

  • Create a Screen – If you create a new screen or just want to flag an existing screen as changed, you can attach an Activity Code like ‘RES’ at the Screen level. This is true for Object and Window as well.

 

 

  • Modify a Field on a Screen – You can attach an Activity Code like ‘RES’ to any Field you add to a screen.

 

    

 

 

It might have been better for me to do this sooner based on the fact that we made some changes and I could have included how to track these changes during those discussions. By doing it this way I am able to use those prior examples along with the best practices outlined above. I will use these practices in future blogs for repetition sake. Thanks again for taking the time to stop by my blog.

14 Days of Sage ERP X3 – Day 5 of 14 – How to Configure a Field to be Mandatory


This topic is not that flashy but has been very useful, easy to configure and highly requested. It is basically configuring a field to be mandatory in a Sage ERP X3 function. I have 2 examples just to show different scenarios that this might be used.

SCENARIO 1: Shipping Site needs to be entered on ship-to Customer tab on the customer record when they are created

This is to make sure that when a Customer record is created that a default Shipping Site is added to the Ship-To Customer so it is set when creating an Order for the Customer. You configure this in the Development -> Processes -> Screens -> Screens function of Sage ERP X3.

Select the BPC4 screen and click on the Fields tab. You want to change the Mandat column to Yes for the Field, Shipping Site. This will make it Mandatory. You right-click in the Mandat column for the Shipping Site row on the BPC4 Screen, a new form will pop-up. You select the field and change the value to Yes. Click Ok to return. Save your changes. Then you need to perform Validation on the screen to publish the change.

 

SCENARIO 2: Making sure that Products get created with Normal Tax

This is to make certain that when you create a new Product that you have to apply it a Tax class. You want to make sure this is assigned that way when you add this item to a Sales Order it has a Default Tax class. You configure this in the Development -> Processes -> Screens -> Screens function of Sage ERP X3.

Select the ITM5 screen and click on the Fields tab. You want to change the Mandat column to Yes for the Tax Level. This will make it Mandatory. You right-click in the Mandat column for the Tax Level row on the ITM5 Screen, a new form will pop-up. You select the field and change the value to Yes. Click Ok to return. Save your changes. Then you need to perform Validation on the screen to publish the change.

 

Again this was nothing earth but I know it is not the most intuitive thing to uncover until you know what you are looking for. I give you a word of caution, make sure that you keep track of what you are doing in case you need to undo anything or redo anything at a future time. Please change things with caution, you could find yourself making changes that you did not expect and could cause frustration trying to track it down.

As for how can you make changes to the system, comment those changes and track them down later, we will cover that in the next blog. Stay tuned…

%d bloggers like this: