Tables – Sage X3 – Tips, Tricks and Components

Sage X3 has provided the developers with an extensive feature called Miscellaneous Tables, Miscellaneous Tables are logical tables to store codes/List of Values for e.g. Rules, Terms, Payment Methods, etc.. it comes handy whenever we need to provide users with options/drop downs to have strict data integrity.

There are 2 types of Miscellaneous table:

Independent Miscellaneous table: This Table is individual table not dependent on any other Misc Tables for e.g. Payment Modes. As seen in the below screen shot the Dependent Table field is empty which shows the table is independent.

Payment mode is a good example of independent Miscellaneous Table, while we create Payment Terms we need to select the payment Modes, and Payment Modes are defined in the Miscellaneous Table as shown below.

Relational/Hierarchal Miscellaneous Table: We can create a Miscellaneous Table using the menu Development-à Data and Parametersà Miscellaneous Tables. We initially define the miscellaneous table where in we can relate 2 miscellaneous tables similar to parent, child relationship.

· Parent table is defined in child table record

· Child table records reference the parent record.

As shown in the below screen shot the Table Product Sub Category is child of Product Category. Thus the Values of Product Sub Category will be listed depending on Product Category selected.

While we are defining the data for table 21 we need to define the dependence of table 20 on each of the values

Let’s proceed with an Example:

While creating the Product Categories we need to enter the Statistical Group Information, suppose we select the Group1 as 010 then as per the above pictorial data 010 has 4 dependent members in Group2. They are 011,012,013, 014.

Thus when we select the Group1 = 010 in that case the Group2 will show only 4 values as seen below. This is how the relational Miscellaneous table work.

Miscellaneous Tables have default 3 columns added however you can add 4 more columns. As you can see in the below screenshot there is a Section called COLUMNS, which has 4 text where in 2 have Alpha numeric datatypes and other 2 with Numeric datatypes.

Here you can use these fields for additional columns taking care that only 2 Alphanumeric and 2 Numeric fields can be added.

Just for an example you can check the definition of Miscellaneous table 1 which stated BP Tax Rules using the below 4 columns and displaying the

· Tax Code

· Sales Class

· Rule Type

· Type

Apart from this Miscellaneous have some additional features of seen in the General Section:

Changeable: If this box is un-checked, it will not be possible to modify the contents of this miscellaneous table.

Modifiable length: Define if the length of the code in the miscellaneous table is modifiable. The user will then define the length of these codes by means as a function of personalization of the miscellaneous tables, within the limit of the maximum length defined in the folder parameters.

Filter company : This checkbox is used to display also the column ‘Company’ in the Management of Miscellaneous tables:

Checked : The column “Company group” is displayed in the management of Miscellaneous tables. If the variable GCURLEG is assigned, a filter will be applied on selection and the legislation of the current company will be controlled.

Not checked : Not additional field, no filter

Filter legislation :This checkbox is used to display also the column ‘Legislation’ in the Management of Miscellaneous tables:

Checked : The column “Legislation” is displayed in the management of Miscellaneous tables. If the variable GCURLEG is assigned, a filter will be applied on selection and the legislation of the current company will be controlled.

Not checked : Not additional field, no filter

Usage of Miscellaneous Table: Whenever you create a table, we can define a field of type “ADI” which will accept the Miscellaneous Table ID. This field can be displayed as combo box/drop down/check boxes which will display set of default values.

Let us know if we can be of any help, please drop us an email at sage@greytrix.com.

In one of our blogs we have talked about creating the dependency Misc. Tables but during one of our development acquaintances we have come up with another alternative solution as well and are really excited to post it here.

Also Read : Using Miscellaneous Tables in Sage ERP X3

For achieving the above functionality we need to follow below mentioned steps:

1) Define miscellaneous table for each field and give the name of dependent table as defined in below screen shot:

2) Now add the fields on the screen. The type of the field will be ‘ADI’. Right click on the type and select Parameters (refer below screen shot)

3) Now give the table name in ADI and the name of the field on which the value of current field has to depend (refer below screen shot).

Sage ERP X3 has come up with an interesting feature through which users can now easily Monitor or Audit any changes in X3 Table. For example, if the user wants to Audit new additions into BP Customer table between a selected date ranges then they just have to activate the Audit conditions in the Customer Table.

Also Read: Auditing Fields in Sage ERP X3

Below is the procedure to activate the Audit table feature for any X3 table.

1. Navigate via Development->Data and Parameters->Tables->Tables and select the Table on which auditing has to be done.

2. Go to “Audit” tab and select the “Type of Audit” as according to your Auditing need, i.e. In case the user wants to audit table whenever a new entry is made in the Table then “Creation” has to be selected; If audit needed for any change in Table entry then select “Modification” and if while Deleting any entry then “Deletion” has to be selected.

3. In order to monitor any Workflow execution associated with the Table, the Workflow checkbox has to be checked.

4. In order to monitor the Table through its Index then the Index Key has to be selected under Tracking Key section.

Below is the screenshot of the Audit tab under Table Maintenance screen

After making changes in the Table to adapt Auditing, any of the changes made in the table would be reflected in the Audit Table screen whenever the Auditing criterion is met. “Audit Table” screen can be opened via Navigating Usage->Audit->Tables where you can select the criteria for check the Audited entries i.e. Data range or/and Table, etc.

Below is the screenshot of the Audit Table screen

“ATABLE” is the table to maintain Audited entries in Sage X3.

Please Note few points,

1. To avail the feature of auditing in your Sage ERP X3, the “AUDIT” activity code has to be made Active.

2. In order to audit Workflow, the “Trigger tracking” checkbox has to be checked under Workflow Rules.

Hope this post is useful…

This is in continuation to our last post Auditing Tables in Sage ERP X3. In addition to Auditing the changes in X3 Tables, you can now easily audit specific fields of any Table. For example, if the user wants to Audit the entries in Customer screen whose ABC Class has been modified to “Class A” then the user has to just activate the Audit conditions in the Customer Table and choose the Class Field condition for Audit.

Below is the procedure to enter the Audit condition specific to any Field of an X3 table.

1. Navigate via Development->Data and Parameters->Tables->Tables and select the Table on which auditing has to be done.

2. Go to the “Audit” tab and select the header selections i.e. “Type of Audit”, “Functions” and “Tracking Key” as according to your Auditing need.

3. The “Fields audited” is the section where the audit condition for fields are selected.

Below is the screenshot which shows the “Fields Audited” section along with the condition for “ABC Class” which set to “= Class A”.

Considering the above condition, whenever the ABC Class of any customer is changed to “Class A”, the customer would be saved in Auditing table (ATABLE).

To view all the Audited Field entries, please navigate via Usage->Audit->Fields and select the selection criteria in the Header viz. Date Period and/or table, etc.

Please refer the below screenshot displaying the selected Audit field records based on above condition on BPCUSTOMER table.

Note – To avail the feature of auditing in your Sage ERP X3, the “AUDIT” activity code has to be made Active.

Function name: Link

Description: Link is used to define a set of links between various tables, as well as single abbreviation to access these tables with one instruction.

New Stuff: How to get the number of records modified by Update Command.

Syntax: Link class_p with list_links as class_l

Refer below snippet of code for better clarification.

Also Read:
1.How to get number of hits on a table.
2.How to get the number of records modified by Update Command.
3.Export transactions to MS Word from Sage X3.
4.How to create Automatic order invoicing?
5.Revalidate database objects using activity code.

Sometimes we may come under a situation where we need to update fields in the same time when the workflow gets triggered.

To update field on running workflow firstly we need to select a workflow rule. I.e. at what action you need to update the field (For e.g. on Validation, rejection, notification, cancellation etc.)

The action we need to add for this is AWRKUPDFLD. This action has parameters where you can define the name of the table which is linked to the object, fields which needs to be updated and the value of the fields.

We can update only 4 fields with the help of AWRKUPDFLD. We can also define when this action is need to be triggered in ‘triggering’ field and also set a condition for its execution in ‘execution condition’ field.

Kindly refer the below fig to know how the parameters should be added.

From the above figure, we have mentioned the table abbreviation in ABREV field, mentioned the field name in FLD field and gave the value in VALEUR field.

In the same way we can update maximum 4 fields from the table at a time.

Hence, make sure the action checkbox is checked for this workflow rule. The fields get updated once this workflow get triggered.

About Us

Greytrix – a globally recognized and one of the oldest Sage Development Partner is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development and implementation competence.

Greytrix caters to a wide range of Sage X3, a Sage Business Cloud Solution, offerings. Our unique GUMU integrations include Sage X3 for Sage CRM, Salesforce.com, Dynamics 365 CRM and Magento eCommerce along with Implementation and Technical Support worldwide for Sage X3. Currently we are Sage X3 Implementation Partner in East Africa, Middle East, Australia, Asia, US, UK. We also offer best-in-class Sage X3 customization and development services, integrated applications such as POS | WMS | Payment Gateway | Shipping System | Business Intelligence | eCommerce and have developed add-ons such as Catch – Weight and Letter of Credit and India Legislation for Sage X3 to Sage business partners, end users and Sage PSG worldwide.

Greytrix is a recognized Sage champion ISV Partner for GUMU Sage X3 – Sage CRM integration also listed on Sage Marketplace; GUMU integration for Sage X3 – Salesforce is a 5-star rated app listed on Salesforce AppExchange and GUMU integration for Dynamics 365 CRM – Sage ERP listed on Microsoft AppSource.

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com, We will like to hear from you.

Signature workflow feature of Sage X3 helps in tracking of transactions. Sometimes there might be a requirement if the end user needs to add additional field in left list of any transaction which will display user’s name for whom the signature is pending for approval. We can achieve this by using the following steps.

Consider a purchase order transaction in which the signature workflow is active.

Navigate to All -> Development -> Data and parameters -> Tables

***Fig: Workflow tracking archive table***

Enter the table code “AWRKHISSUI” as shown in above figure.

This table holds the tracking data for signature workflows.

Go to “Index” section of the “AWRKHISSUI” table and add new index as shown above which consists of combination of “CLEDEC” and “FLGSIG” field. “CLEDEC” field represents the transaction number of any transaction and “FLGSIG” field represents the signature flag.

Navigate to All -> Development -> Script Dictionary -> Objects

As we are considering purchase order transaction, so enter its object code and go to its “Environment” section in which we need to add workflow tracking archive table and the index we created above with the expression as “[F:POH]POHNUM;3” as shown in above figure, where POHNUM represents transaction number field and “3” is signature field which will represent “To be signed” status for the user signature pending in the workflow.

***Fig: Adding new field to selection***

Go to “Selection” section in the object screen and add the table “AWRKHISSUI”, User signature pending field “DEST” which will display for whom the signature is pending for approval, as show in above figure.

Navigate to All -> Setup -> Workflow -> Workflow rules

As shown above, select the purchase order workflow code which is “POHSIG” and jump to the assignment rules selected for the workflow. Here, it is “YPOHSIG”.

Add the desired users in the values of assignment rule as shown in above figure.

Now, if we navigate to Purchase order transaction, create one transaction and check its signature circuit, we will be able to see “YUSR1” which is first user yet to be signed as shown in below figure.

Since, “YUSR1” is yet to be signed. Hence, we are able to see “YUSR1” in “User Signature pending” field of left list.

After Signature of first user, that is “YUSR1”, if we open signature circuit, we will be able to see second user “YUSR2” is yet to be signed as shown in below figure.

And also we can see “YUSR2” in left list of transaction as expected in the below figure for that transaction.

This blog helps us to add additional field to the left list of any transaction showing which user’s approval is pending for that transaction.

About Us

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com, We will like to hear from you.

Now days Every company wants to upgrade the system or data with newly functionality on the higher version. In Some industries the company wants to migrate the data from lower version to higher version in Sage X3. For those needs to done some steps in Sage X3 i.e., Execution of Pre-migration and Post-migration script in the source and destination system. After post-migration process user needs to delete the U tables (Temporary tables) which are created at the time of pre-migration process. This phase is manual It will be triggered by the execution of the TRTMIGDEL processing from the processing execution function. Its execution will provoke the deletion of all the tables bearing the activity code MIG.

As this phase is irreversible, it is important to have made sure, previously, that the migration processing routines have been carried out properly.

Since keeping temporary tables in the folder does not prevent from resuming operations (this supposes of course that there is enough space on the disk), it is possible to keep these tables in line during several weeks after resuming operations. Therefore, should any problem rise in the weeks following the migration, it will be possible to have some original data available for comparison or analysis.

This phase is manual It will be triggered by the execution of the TRTMIGDEL processing from the processing execution function. Its execution will provoke the deletion of all the tables bearing the activity code MIG.

As this phase is irreversible, it is important to have made sure, previously, that the migration processing routines have been carried out properly.

Follow the below steps:

After migrated folder validation process one log will be generated with the below message as shown in below figure,

If the folder validation process is not successfully completed, we cannot proceed for further process, as shown in below figure,

After the folder validation process run the post-migration utility through a sequencing monitor screen from X3.
Once post-migration script process is successfully done, then we need to check the data are successfully transferred into the original tables.
Once your upgrade has been validated, you may drop the temporary U* tables which have the MIG activity code by launching the TRTMIGDEL program from process execution function.

Navigate to: Development> Utilities > Miscellaneous > Run process

Enter the TRTMIGDEL in a script file field and click on Ok button, as shown in below fig,

Now select the folder in which folder you want to run this script, as shown in below figure.

Clicking on the OK button the process will run and one log file will be generated.

With the help of above process, you can delete the Temporary tables (i.e., U tables) after post-migration process.

About Us

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com, We will like to hear from you.

Consider a purchase order transaction in which the signature workflow is active.

Navigate to All -> Development -> Data and parameters -> Tables

Enter the table code “AWRKHISSUI” as shown in above figure.

This table holds the tracking data for signature workflows.

Navigate to All -> Development -> Script Dictionary -> Objects

Navigate to All -> Setup -> Workflow -> Workflow rules

As shown above, select the purchase order workflow code which is “POHSIG” and jump to the assignment rules selected for the workflow. Here, it is “YPOHSIG”.

Add the desired users in the values of assignment rule as shown in above figure.

Since, “YUSR1” is yet to be signed. Hence, we are able to see “YUSR1” in “User Signature pending” field of left list.

After Signature of first user, that is “YUSR1”, if we open signature circuit, we will be able to see second user “YUSR2” is yet to be signed as shown in below figure.

And also we can see “YUSR2” in left list of transaction as expected in the below figure for that transaction.

This blog helps us to add additional field to the left list of any transaction showing which user’s approval is pending for that transaction.

About Us

The GUMU Cloud framework by Greytrix forms the backbone of cloud integrations that are managed in real-time for processing and execution of application programs at the click of a button.

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com, We would like to hear from you.

As this phase is irreversible, it is important to have made sure, previously, that the migration processing routines have been carried out properly.

Follow the below steps:

After migrated folder validation process one log will be generated with the below message as shown in below figure,

If the folder validation process is not successfully completed, we cannot proceed for further process, as shown in below figure,

After the folder validation process run the post-migration utility through a sequencing monitor screen from X3.
Once post-migration script process is successfully done, then we need to check the data are successfully transferred into the original tables.
Once your upgrade has been validated, you may drop the temporary U* tables which have the MIG activity code by launching the TRTMIGDEL program from process execution function.