Sage X3 – Tips, Tricks and Components

Recently in Sage X3, we had got a requirement from the client to add the Location field in Physical elements screen in the Fixed Asset tab.

New Stuff: How to create process flows in Sage X3 V12

[Fixed Asset Screen – Physical element]

For this we first need to add the field in “PHYELT” table and later add the Location field in Physical element “PHY0” screen and global validate the window “OPHY”. Once the field is added in the window, still it does not get displayed in the screen when we open it.

[Physical Elements Screen]

Therefore, here then comes the concept of Classes and Representation. Further we have to add the Location field in the Class which is linked to the Physical element screen. For this we need to navigate into the Development -> Data and Parameters -> Classes. The class code is same as that of Table i.e. PHYELT. Further we scroll down to Properties tab and add the Location field to the desired location and define the order for the same and Global validate the class as shown in the below screenshot.

[Physical Elements Class]

Now we have to add the Location field in the Representation tab i.e. navigate into Development -> Data -> Representations -> PHYELT. In this scroll down to Available Properties and add the Location field and define in block in which the field is to be displayed. In our case we will be adding the location field into “S1B1” block and define order for the field and save the changes. Once done global validate the representation screen so that changes will be reflected on the screen as shown in below screenshot.

[Physical Elements Representation]

Once all of these above steps are done, now we will check if the Location field is added on the Physical elements screen.

[Field added on Physical elements screen]

As you can see in the above screenshot, the Location field is now added on the Physical elements screen successfully and also data is getting saved on the screen.

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 Sales Commission App for Sage X3 simplifies commission calculations and postings on sales transactions.

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.

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 would like to hear from you.

All users play a very critical role in Sage X3, also it has a feature where we can set a permissions and access to a particular user, so that there is no mishandling of information.

The need to restrict users to access ERP Modules can be based on the employees’ role and their department. User security and access should be the top most priority as there is a lot of data involved in it. By providing limited rights, access and Security controls, we can control data corruption and data leakage, which is very much necessary for X3 system.

Thera are few important points which are main by doing the restriction process.

Menu Profile
Function Profile
Roles
Groups

Menu Profile : Sage X3 provides a very useful feature called menu profile which can be defined in users screen to restrict the users to access all modules, screen, and reports in Sage X3. We can create a menu profile for example “Common Data”, “Financial”, wherein we will only add Common Data and Financial Module related screen and report and that profile can be assigned to a particular set of users.

Function Profile: Sage X3 provides another feature called function profile, which can be defined in the users screen to restrict users based on their function. For example, if a person is only doing expense types of entries in the system then he should have only access for expense types GL accounts, he shouldn’t have access for other GL account. In this case we can create an access code let’s say “ACCTRESTRICT” and add this access code in function profile and define same access code in GL account to give access function type for the users.

In Sage X3, there is a functionality to restrict user for accessing screen. Follow below steps to achieve this:

Steps1:

Login into X3 with admin user.
Create a new user (User5) in Sage X3.

Navigate to: Administration -> Administration -> users

Now create same user in below path.

Setup -> users -> users

Create new Menu profile and Function profile and assign to it.

Note: Add only those module and sub-module in the menu profile which user will access it. Example: Module ‘Common Data’ and under this sub-module will be only ‘Currency and Currency rate’. So add that only and create the function profile of that menu profile from the menu profile screen only. Refer Fig1.2 for creating function profile.

**Fig 1.1: User Menu profile and Function profile**

Step 2:

Now, create new roles and groups for that user (user5)
Create new navigation page and in that page add newly created modules and its sub modules. Refer Fig2.1

Also refer below paths for creation:

For creating new Navigation page: Navigate to: Admininstration -> authoring -> pages -> Navigation page.

For creating new Module: Navigate to: Administration -> Authoring -> Pages -> menu module.

For creating new sub modules: Navigate to: Administration -> Authoring -> Pages -> menu sub module

Note: In navigation page, add only those newly created modules which are needed and restrict others.

And also in menu module add only those newly created sub modules which are needed for the user.

As you can see in the above screen shot, I have added only those modules which are needed. Also add the new roles with full user access to it.

Now assign these all the points ‘Groups, navigation page’ to a user (user5) and see the result once you login with that user into the X3. You will see only needed module will be accessible to the user rest will be restricted. Refer below screen shot.

By doing all the above steps, we can achieve restriction process to a user.

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.

A Work order is an order to make one or more products. Conventionally, the work order uses a bill of materials (BOM) to create a list of materials to be issued, and a routing to make a list of operations to be performed on work centers. Work orders dictate what product need to be manufactured, what raw materials are going to be required to manufacture the product, and which work center that the product needs to pass through in the manufacturing process.

Basically, work order uses a bill of materials (BOM) to create a list of materials to be issued, and a Routings to make a list of operations to be performed on work centers. An operational routing defines the formalization of the steps required for a manufactured product (finished or semi-finished). Its production process, as well as the sequencing of the operations to be completed. In Standard Sage X3 user can create a work order without routing code with the help of below steps.

Follow the below steps for the setup:

Navigate to: Setup >Manufacturing > Entry transactions > Work orders

Select Automatic generation entry transaction from left list
In the work order entry transaction reserved for automatic generation, the Transaction reserved for automatic generation checkbox in the Parameters section is selected.
Select the Materials only checkbox in the Release mode block and clear the Full checkbox, as shown in below figure. With these options selected there will be no checks run for the routing and routing code.

WO entry Transaction — **Fig01: Work Order Entry transaction**

4. After changes do the validation of entry transaction.

With these options selected there will be no checks run for the routing and routing code.

Now, we will create Production BOM without routing code.

Navigate to:Common Data >BOMs > Production BOMs

Enter a Parent product, BOM code, validity dates and components values.
Use status should be mark as an “Available to use”
Create a BOM, as shown in below figure.

BOM screen — **Fig02: Manufacturing BOM**

We will create now Work order with help of above created production BOM.

Navigate to: Manufacturing > Planning > Work order

Select that Automatic Generation transaction
Enter Mandatory fields values as shown in below figure.
Create a work order.

Now, you can see in below figure system allowed user to create work order without entering routing code in routing section.

With the help of above steps, we user can create or import Work order without routing.

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.

Sage X3 is enterprise resource planning (ERP) product which helps organization to manage all the operation of organization and database into a single software solution. Sage X3 contains list of modules like sales, purchase, inventory, project, financial and many more.

In sales module, sometimes an error occurs – “Transaction stopped” while creating sales invoice as shown in below screenshot. Because of which users could not create invoices.

New stuff: How to create work order without routing in Sage X3

Error coming while creating sales invoice

To solve above error we have to follow below steps:

Step 1: Navigate to Sales Invoice screen , then Jump to Type” field in sales invoice transaction as shown in the below screenshot.

Jump to Invoice type

Step 2: you will be redirected to new screen of Customer invoices types. Here you can see “Entry type” field in the setup section.

Step 3: click on action button of the same field and jump to Document types option as shown in the below screenshot.

ump to document type

Step 4: Once you redirected to the Document type master, you can see Default journal field is blank in identification section as shown in the below screenshot.

Default journal missing

Step 5: you have to jump to Journal code screen by clicking on action button of Default journal field present in identification section of Document types master , and then you have to create one Journal code for sales module as shown in the below screenshot.

Create Journal code

Step 6: Before creating a journal code, check availability of journal code with sales module in system. If it is available then assign same code to default journal field at document types screen or else create a code and then assign the same code as shown in the below screenshot.

ssign default journal to document types

Once journal code is assigned in Default Journal field in document types master then save and close all the screens and try to create sales invoice. Now, you will be able create Sales Invoice without any error.

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.

You may come across a scenario where you want to export a file in the sage x3 server itself but in this scenario sage x3 allows you to only export the file in the SAGE folder of D drive, if you wish to export it in different path (Outside Sage folder) or in a different drive in the sage x3 server it won’t get exported. Therefore this can be achieve by assigning the path in the configRuntime file. For that you have to perform the below given steps.

For exporting the file, We have to assign a path outside the sage folder. We have to navigate to All >> setup >> General parameter >> Parameter values As we know, In parameter values we assign the path where we want to export our file. So we will assign the path outside of the Sage folder of D drive, as shown in the below figure 1. We have assigned the path as “ D:\Test\Demo ” in sage X3.

2. We have to also assign the path in the JSON file. In X3 server navigate to “ D:\\Sage\\EMV12SP\\runtime\\cfg ” in the file manager, here you can locate a JSON file which is named as “ configRuntime ”. You need to add your directories in this JSON file.

3. Now we have to do logout from the sage X3 system and also we will have to restart the Safe x3 Syracuse service node in sage x3 server as shown in the below figure 2.

**Figure 2 : Syracuse service restarted in Sage X3 server**

4. Now when you export your file it will get exported outside the sage folder. As shown in below figure 3, We can see our file is exported on the path which we have given in the parameter values and configRuntime file.

**Figure 3 : File got exported outside the sage folder**

Hence by following the above steps, We can export the file outside the sage folder of D drive in sage X3 server.

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.

In Sage X3, we had developed one custom report for our client where the detail section continues to the next page of the report but the heading/captions did not get printed on each page as captions were placed on the group header section (please refer below screen shot). One would think that placing the captions in ‘Page header’ would solve the problem but this solution would not solve the problem with many reports. So we will see in this blog, how we can overcome such a situation.

New Stuff: How to export a file outside the SAGE folder in the X3 server

Detail Line Issue in Crystal

To fix this issue you have one feature in Crystal Reports that will be used to repeat the group header data (Ex : Headings for detail line fields) on each page.

Follow the below steps to achieve the above requirement:

Step 1: Go to Report menu and click on Group Expert (the group for which you want to do this)

Group Expert

Step 2: Click on ‘options’ button

Step 3: Select the ‘options’ tab

Step 4: Check on ‘Repeat group header on each page’ as per below screenshot:

Change Group Options

After saving the above option, group header will be repeated on each page. Refer below screenshot:

Output

This is how we can repeat the captions for group header details on each page of the report using Crystal Reports feature.

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.

In Sage X3, we recently had a requirement to generate custom product code based on the product category, specifications selected by the user, and to generate product description based on the product code.

Screen path:
Miscellaneous tables:
Development – > Miscellaneous tables – > Definition
Development – > Miscellaneous tables – > Data
Window:
Development -> Script Dictionary-> Windows ->OITM

Based on the product categories we had several specifications for each product which users capture in other details tab on Product master. Using these specification we need to generate Product code and descriptions. For which we first created Miscellaneous table definition and in the Miscellaneous Data of each table we created the category code and the specifications related to that category.

New Stuff: How to repeat group header on each page in Crystal Reports

Other Details in product screen

Miscellaneous table Data

Once we created miscellaneous tables for all the specifications, we created a custom screen “Other details” which has all the fields of the specifications with the type as ADI.

Once all the specification is selected from the “Other Details” tab in the Product screen, on creation, the Product code and description gets generated. To get the code we will use the “Short description” column and for the description we will use the “Description” column present in the Miscellaneous table for each of that specification.

Once the code and description are fetched, we programmatically concatenate the code and description. For example, in the “Other Details” tab we have selected the specifications as per the below image.

Other Details Output after selection

Based on the specification selected we will get the Product Code and the Product Description

Generated Product Code and Product Description

This way we generated Product code and description using Miscellaneous tables.

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.

Sage X3 has provided us a function which is named as ‘Customer extension’ (function PROROGC). Sometimes there can be a situation where we need to extend the due date of payments which is pending from a customer. Here by using customer extension function we can update the new date of the payments for specific customers. Use this function to extend the due date of customer notes payable/receivable entered for a payment. The due date specified on the corresponding entries (e.g. entry generated on notes P/R posting) is also updated. Below we will check how this function works.

We need to make sure that only the payments posted for a type of payment set by Due date in entry transaction mode are subject to extension. If it is not managed sage X3 will not allow extending the due date of those payment entry types. To check the setup navigate to

ALL -> SETUP -> A/P – A/R ACCOUNTING -> PAYMENT ENTRY TRANSACTIONS

We need to check the ‘due date management’ checkbox as shown in the below image.

Also we need to note is if the payment has completed the notes payable/receivable posting stage, it can no longer be processed in this function. Therefore, all payments posted to a paying bank notice can no longer be processed.An authorization can be granted for this function to limit the processes to a company or a site.

To reach this function navigate to

ALL -> A/P – A/R ACCOUNTING -> PAYMENTS -> CUSTOMER EXTENSION

The customer open item due date extension is carried out in a grid where each line represents a payment.

Only the first column (payment number) has to be assigned. To search for a payment number, a Selection context menu opens a selection window for payments by type of payment, BP, etc.

Once the payment number has been entered, the information relating to this payment is displayed. The cursor is directly positioned on the Open item column where the new due date needs to be entered for this payment.

Once all the payments to be processed and the new extended due dates are displayed, you use the Save action to validate your change and apply it to the payment and journals generated for this payment.

Below are the errors a user can face while processing this function.

Function not authorized: This message appears if the user does not have the correct access rights
Journal pending validation: This message appears if the batch processing for journal validation has not generated an entry referring to the payment yet.
Unsettled payment: Impossible to extend a payment that has not been settled.
Payment deposited in bank: Impossible to extend a payment that has been deposited in the bank.
Payment number already entered: The payment has already been entered in the grid.
Invalid customer: The BP entered is not a customer.
Due date not managed for this type of payment: The DACDUDDAT field is set to 3 in the TABPAYTYP file for the entered settlement type.
You have no rights for this site: You do not have access to the payments carried out for this site.

Hence by performing all the above steps and prerequisites we can process the customer due date extension function.

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.

A revised standard cost is usually created in order to prepare for an upcoming new standard cost following the revaluation of a material, an hourly rate, etc. Revised standard costs for the same product and site are retained and can be viewed.

A revised standard cost calculation can be associated with an accounting interface, which makes it possible to re-evaluate the stock value for semi-finished and finished products during the update of the revised standard cost.

This function is used to calculate the revised standard cost of a product, a selection of products, all the products at a site from a cost type routing alternative, a cost type BOM alternative , with or without immediate update, to print a document summarizing or detailing the calculation.

The calculation with or without the lower BOM levels consists of reading the component costs at the first level and transferring them to the cost of the parent product.

Navigation:

All >> Costing >> Revised cost calculation.

Filter Parameters:

Site

The user must indicate the site for the calculation.

Selection of the products

The user must indicate either a product, or a group of products at the site or a selection of products. To choose to calculate the standard cost for all the products at the site, tick the “All” box. To carryout the revised standard cost calculation for a selection of products, it is necessary to create the selection filter via the contextual menu accessible in the Product field.

Validity

The user has to specify the validity period of the calculated revised standard cost.

Calculation quantity

This is the quantity that will be used in the calculation. In the case of a calculation for a single product, this filed is loaded by default by the economic quantity for the product but can be modified.

Calculation parameters:

BOM routings

The user must indicate an alternative routing of the cost type, this alternative must be associated with a BOM alternative that is also of the type cost.

BOM code

The BOM alternative is displayed and is non modifiable. This is the first BOM alternative associated with the routing alternative previously entered.

Distribution of the fixed costs

The fixed overheads (material loss, setup rate, operation loss rate, fixed rate) are distributed either as a totality or pro rata for the calculation quantity/economic quantity.

Material cost choice

The material cost choice is initialized by default (CLCCUTMAT setup), it is used to value the material cost.

Dimension rate choice

The dimension rate choice is initialized by default (CLCCUTRAT setup), it is used to value the labor and machine elements in the calculation.

OH column choice

The OH column choice (Overheads) is initialized by default (OVECOLCUT setup), it is used to value the overhead element in the calculation, detailed by the nature of the overhead and calculated by applying the fixed rate or the formula in the chosen calculation column.

With the help of above steps user can do the revised cost calculation.

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.

The automatic deallocation processing of material linked to production for a given site, a given period and selected work orders can be initiated using this function. This processing can deallocate the materials based on the initial allocation type (global or detailed).

A deallocation processing can be initiated based on the type of initial allocation (global or detailed) for materials assigned to a given site, a given period, and selected work orders.

Below are the selection criteria for automatic deallocation function.

Navigation:

All >> Manufacturing >> Automatic Deallocation.

Selection criteria:

Production site: The site associated with the user is suggested by default.

Requirement cut off: This field makes it possible to select the materials which requirement date is prior to the date mentioned. By default this date us initialized to the current date. Material requirement dates that are prior to the mentioned date are selected by this field. By default, this field is initialized with the current date.

Deallocation screen — **Fig2. Selection Criteria**

Processing type:

This block is used to select the materials that must be deallocated based on their current allocation status.

Deallocation mode:

Complete deallocation: The materials in the selection are deallocated irrespective of their allocation status of origin (global, detailed, shortage).
By allocation type: It is possible to choose to deallocate only those materials in the selection that were initially globally allocated, or only the materials that very initially allocated in detail.

Selection order:

The purpose here is to specify the order in which the allocations must be executed for the various WOs in the selection. The purpose of the order specification is to specify the order in which the allocations must be performed for the various WOs which make up the selection.

By start date: the WOs are processed in the order of their start dates: For a similar start date, the priority code of the WO is taken into account. In addition to processing WOs in order of their start dates, priority codes are taken into consideration when WOs have similar start dates.
By priority code: the WOs are processed by decreasing priority order (Very urgent, Urgent, Normal). With an equal priority level, the system examines the material requirement dates. With identical priority levels, the system examines the material requirement dates for each WO in decreasing order (Very urgent, Urgent, Normal).

Processing modes — **Fig3. Processing type**

Start/End ranges:

These ranges are used to select the materials to be processed. The possible ranges are:

Priority
Work order no.
Project
Destination
Order number
Released product
Material

At the end of the processing, a log file can be printed. This log mentions the deallocated quantities for each work order and material.

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.

In a normal business scenario, work order plays an important role as it can be for both products or services.

In a manufacturing environment, a work order is an essential part of the whole business process where a complete production cycle can be affected. These orders are used to build a complete product from different components which can be used to make the same.

Production tracking is the next part of work order where a work order can be tracked and converted into production tracking.

Production tracking is a strategy used to measure, analyse, and improve visibility throughout the manufacturing process. From the sourcing of raw materials to the shipping of final products, production tracking allows businesses to monitor the performance of each production step and improve their processes using aggregate data.

In some scenarios, there might be certain conditions in which we want to prevent the closing of work orders like if work orders do not satisfy certain conditions then we do not want to close them without fulfilling those criteria’s.

So, in this blog we will see how we can set a parameter which can help us to prevent the closing of work order.

Steps to follow:

So, in order to prevent closing of work order, we need to navigate to All -> Setup -> General Parameters and open the ‘CTL’ group (i.e. Production tracking controls) of the ‘Manufacturing’ chapter. Kindly refer below screenshot for the same.

After opening the ‘CTL’ group of the ‘Manufacturing’ chapter, just change parameter CTLCLE (i.e. Blocked in Closing) from ‘No control’ to any required values. Kindly refer below screenshot for the same.

So, this parameter can be set to either folder wise or legislation wise or company wise whichever way is preferred we can set the same.

This parameter is used with work orders. Use it to prevent closure of a work order if one, or both of the following circumstances are detected:

The quantity of components required to manufacture the product have not been tracked in full. The Remaining quantity field is not zero or blank for one or more components.
The progress and status of an operation required to manufacture the product is not complete and closed.

This parameter has 4 values to select which described below :

Blocking outstanding materials and operations – This is the default value for this parameter. A work order cannot be closed if one component line has an outstanding quantity against it, or if one routing operation remains incomplete and has not been closed.

No control – No controls are required. A work order can be closed without checking for outstanding component quantities or incomplete routing operations. A warning is however displayed if either of these circumstances are detected.

Blocking outstanding materials – A work order cannot be closed if one component line has an outstanding quantity against it. Incomplete routing operations that have not been closed are ignored.

Blocking outstanding operations – A work order cannot be closed if one routing operation remains incomplete and has not been closed. Any component line with an outstanding quantity against it is ignored.

By the help of the above blog, we can prevent the closing of work orders.

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.

A marketing campaign is a strategic marketing effort aimed at promoting a specific endeavor or goal on behalf of a company, brand or individual. Marketing campaigns are designed to get consumers’ attention in several ways, such as television, print advertising, social media and email marketing. Each campaign expresses a marketing objective to be attained for a given period.
These campaigns also constitute a unique method to create marketing operations, which represent the actual activity destined to realize a marketing objective.

In Sage X3, below four wizards are available that correspond to each marketing operation type that is available to the user:
⦁ Mass mail wizard
⦁ Phone campaign wizard
⦁ Professional trade show wizard
⦁ Media campaign assistant
The wizards control a large number of critical tasks:
⦁ They control the execution of certain mandatory actions;
⦁ They ensure the correct sequencing of the numerous operations necessary for the creation of an operation;
⦁ They manage the clean-up of the different application tables in case of cancellation;
⦁ They automatically perform Marketing Campaign – Marketing Operation associations.
Etc.

These wizards are only accessible from a marketing campaign record.
The marketing campaigns are also used to carry out miscellaneous closing operations (campaign closing, associated operation closing).

Below are the list of fields present in Saxe X3 marketing campaign functionality:

⦁ Site: It identifies the site on which the marketing campaign is principally managed.

⦁ Denomination: This field must contain several words that are used to identify a marketing campaign in an effective manner.

⦁ Closed campaign: This field is used to close a marketing campaign and all its associated operations. Once the campaign is closed, it gets automatically removed from marketing planning function. All the associated operations are also excluded from the planning. If one or more phone campaigns currently being processed are associated with the closed campaign, all the calls remaining to be carried out for these operations are deleted. The phone campaigns are then themselves closed.

⦁ Start and End: These fields indicate the period over which a certain number of marketing operations are likely to take place. In fact, ideally the marketing campaign duration should cover the totality of the periods for all the associated marketing operations.

⦁ Planned budget: A marketing campaign represents a marketing objective to be attained. This field is used to enter the amount that the marketing manager is planning to expend on realizing this objective. The Currency field is used to value the entered amount.

⦁ Committed budget: This field is automatically calculated by the system. It represents the total of the committed budgets for carrying out each marketing operation.

⦁ Associated operations :
Each marketing campaign contains a list of the operations belonging to it. The grid displays the type, the start date and the name for each of them. The relation between a campaign and its operations is automatically established by all the marketing wizards.
As far as the mass mailing type operations are concerned, if the start date has not been assigned it means that the mailing has not yet been issued.

⦁ Description: It helps to explain the campaign objective in detailed manner.

⦁ Return/Budget/Wizards:
⦁ Return: This button is used to view and to analyze the ⦁ returns generated by the mass mailing.
⦁ Budget: This button is used to view and analyze the budget allocated for the campaign.

Thus, marketing campaigns can be considered as important aspect to expand the business with proper marketing strategies.

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.

Functional authorizations are used to restrict access to functions within X3. If a user needs to create a sales order, we need to give them the functional authorization to GESSOH (sales orders). If we don’t want a user to have access to purchase orders, make sure they don’t have the functional authorization for GESPOH (purchase orders). The functional authorizations are grouped together by a function profile to make it easier to create users in Sage X3.

We can access functional authorizations in two ways.

Navigate to: Setup> Users > Functional authorization.

Navigate to: Setup > Users> Function profile and click on Authorizations

Most of the time, you will want to go through Function profile.

Go to Function Profile, we will create a new profile code ZTEST. Now we have a Function profile ZTEST but if we assign this to a user, they won’t have access to anything. A function profile is just a way to group authorizations to make user administration easier. We need to add all the needed authorizations. If we click on Authorizations at this point, the Functional authorization screen won’t really show anything because there are no authorizations for this profile. We need to add them. Refer below figure.

Now, click on New and enter a function we need. Here we will enter GESSOH (sales order)and save. Refer below figure.

On the function profile screen, we will choose the profile we want to copy the authorizations from, in this case, ADVT. Then click on Authorizations at the top right. This screen will show a bunch of authorizations on the left list. Then click on merging.

If we want to copy all the authorization from ADVT to the authorization we have created then go to the ADVT authorization click on the merging button select the profile code ZTEST then click OK. The message box will appear for confirmation of merging click yes. Refer below figure.

Now, if we go back to the function profile, choose ZTEST and click on Authorizations, we will see all the same authorizations that were on the ADVT profile.

In the ZTEST function profile if we want to add access to everything in the Stock module. We could go to the navigation menu and figure out all the functions that are in that module and add them manually but of course there’s an easier way.

Choose the ZTEST function profile and click on Authorizations. Now click on Addition. On Click of addition below screen will display.

There are two ways to do this. We can expand the Stock module on the left list and choose the options we want or we can click on Module at the top right. When we use Module, it checks all the options under stock but we can accomplish the same thing by checking the check box next to stock.

In this way we can make addition of functional authorization easier.

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.

Recently, we had a requirement from one of our client for a new insurance module, in which we have customized the company master and policy master screens to ensure the policy of the product. In policy master, there are “From and To date” fields that indicate the period between which the policy will remain active. After the “To Date”, the policy gets expires and will become in-active. This policy master will help users to top up their policy easily based on the “From and To date” fields. So, when the user enters “To date” and if it is smaller than “From date” then the warning message should be displayed on- the screen that ‘To date should be greater than From date’.

New stuff: How to make adding a functional authorization easier

We will see the functionality in detail:

Navigate to : More -> Insurance -> Insurance Set Up -> Insurance Company master

Insurance Company Master

Initially, users have to create the insurance company and fill in all the details which are mandatory on that screen and once an insurance company is created then these company details will get fetched on the policy master screen automatically while creating the policy of the company in the policy master.

To Open the policy master screen – Navigate to: More -> Insurance -> Insurance Set Up -> Insurance Policy Master

To Date field

If the user tries to select a date in the “To date” field which is smaller than the “From date” as shown in the above screenshot. Then the Warning message is getting displayed and it is not allowing the user will to create the policy as shown in the below screenshot.

Warning message

As a result, the user cannot add further details on the screen and policy would not be created. In this way, we can restrict policy creation if “To Date” is smaller than the: From Date”.

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.

In Sage X3, the maximum credit amount for the customer can be defined in the authorised credit field in the Customer master.

There are 3 options available in the in Management tab in Customer master:
-Check
-No check
-Hold

With the help of these options we can easily manage the Credit limit of the customer.
We had a requirement from one of our client to add a validation on the sales order screen that if transaction amount for the particular customer exceeds than the amount defined in the authorized credit limit then we need to hold the sales order.

As shown in the below screenshot customer ‘CD0001’ is having Authorized credit amount of 50000 INR.

New Stuff: Warning message on the screen when “To date” is smaller than “From date”

Customer Master

So to add a validation, we have added a code on the SPESOH scrip.t Now when we will try to create or modify the sales order for the customer whose transaction amount has already reached to it’s credit limit, then it will not allow you to create a sales order and you will get a popup – “The Customer’s total outstanding balance exceeds overdue amount limit of 50,000. Total Outstanding amount is 54,000.” as shown in the below screenshot.

Credit Limit Popup on Sales Order

Only after posting the payment of the same amount for that customer, it will allow to create new Sales Order transaction.

Thus, in this way we can add validation on the sales order screen for the customer who has already reached to the defined credit limit and will restrict the user to create sales order for that particular customer.

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.

In Sage X3, one of the client’s requirement was to have a dynamic “Policy Status” field which will reflect the current status where the policy is Active or De-active for the selected module. Here another condition was that at a given time span only one policy per module can be kept Active, rest will stay deactivated and will get activated automatically once the date condition is satisfied.

First to navigate to the screens that’ll be used for the below steps:

Window management: All -> Development -> Script dictionary -> Window management
Script editor: All -> Development -> Script dictionary -> Scripts -> Script editor
Tables: All -> Development -> Data and parameters -> Tables

To fulfill the above mentioned requirement we need to follow the below steps:

Step 1: Below are the locations showing the “Status and Applicable module” fields on screen, on window management and on the linked table of the screen. Refer the screenshots for reference:

New Stuff: Validation on the Sales order screen if credit limit exceeds

Module and Status fields on screen

Status field under Header tab in Window management

Status field in linked table of Header screen

Step 2: For this customization we need to add some action events. The script code for the screen can be identified from Window management > Header screen > Specific script.

The logic for them will be as follows:
Once the user clicks the “New” button on screen to create a new policy and selects the Applicable Module our logic part will trigger that will check whether there is any existing Policy already for the given Module and if it does then whether it’s currently Active or Inactive.
In case the Policy exists and is Active, the Status field is made non-editable using the DISZO command followed by AFFZO command and set to DEACTIVE. Whereas if the Policy exists but is in Inactive status, then it’ll allow the user to select the status as per choice.

Case of Active existing Policy on module

Step 3: Now when a new policy is created for a given date range, then another logic is added on the LIENS action event in script which gets triggered whenever the Entry no. is browsed from left list selection or opening the screen.

This logic checks if the current date is within the Policy date range first and then:
If the current date is within the date range then it’ll check if the status is Active or De-active.
For the Active case the logic will return from the event without any change.
For the De-active case the logic will check if there is any existing Active policy for the module, if not then it’ll change the status to ACTIVE on the screen and trigger an Update instruction on the table.

If the current date exceeds the To date of Policy:
For the Active case the logic will change the status to DEACTIVE and make the field non-editable using the DISZO command followed by AFFZO command, and update the table using the Update instruction.
For the De-active case logic will return from the event without any change.

This way we can dynamically set the status field on screen based on the policy date range.

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.

Sage X3 has a feature of BP net settlement, with the help of this feature we can settle open items like open invoices, unapplied prepayment, credit memos and debit memos against suppliers & customers.

One of our client tried to create BP net settlement against one vendor but an error occurred as shown in the below screenshot:

New stuff: How to set dynamic Status field on screen based on date range

Error MRK(501) Index Incorrect

This error occurred because the screens BPOINET & BPOINET3 having a grid length of 501 as shown in the below screenshot and transactions against the vendor which is selected for for BP net settlement is exceeding that length.

BPOINET

BPOINET3

To solve the above error, we have to follow below steps:

Launch Development, Script Dictionary, Screen Dictionary, Screens
Select BPOINET & BPOINET3 screens
On the General tab where 501 is entered on the Details line in the Lines column, increase the value to a larger number to allow more records on the BP Net Settlement. (Maximum 32,267)
Click Save.
Click Validation.
Kill session by doing logout from application.
Log-in and check message does not occur again, error got fixed now.

Hence by following the above steps, we can solve the Error: “MRK(501): Index Incorrect” in Sage X3.

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.

Sage X3, is a complete business management solution designed to drive productivity and give you total control and visibility of your enterprise. With customizable configuration, the flexible solution equips you with everything you need to drive business success. Easy to understand all the modules.
We had a requirement from one of our client to freeze the Supplier Invoice No and Supplier Invoice Date fields in GRN but the condition was it should freeze only when the user create a Purchase Invoice against the same GRN. Once the Purchase Invoice is created the user cannot modify the data in the GRN screen for the Supplier Invoice and Supplier Invoice Date fields. Even the user cannot enter the same data which is been used for the previous entries Which means the system will not allow the duplication of data in the Supplier Invoice No and Supplier Invoice Date fields.

New stuff: Error “MRK(501): Index Incorrect” in Sage X3

We will see the functionality in detail:

Navigate to : Purchasing -> Receipt -> Receipts

Supplier Invoice No and Date Fields in GRN

While creating GRN users can enter data in both fields even they can modify the entered data before creating the Purchase Invoice against the Purchase Receipt.

Navigate to: Purchasing > Invoices > Invoices

Creation of Purchase Invoice

The user will create a Purchase Invoice against the same GRN.

Fields are frozen

After that in the GRN entry, the Supplier Invoice No and Date fields will get freeze as per the condition – once the Invoice is created the system will freeze those fields and cannot be further modified.

Pop-up for Duplication

When the user creates a new GRN with the same Supplier No and Date which is used for another entry number then the system will generate a pop-up as shown in the above screenshot.
As a result, the user cannot modify or enter duplicate data in the Supplier Invoice No and Date fields once the Invoice is created.

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.

In Sage X3, one of the client’s requirement was to have a dynamic departure time field update based on Arrival time field data under Management tab of Sales invoice module. The field takes value in the form of HH:MM. Below is the
Customization done for achieving the same.

New Stuff:
https://www.greytrix.com/blogs/sagex3/2022/03/30/error-mrk501-index-incorrect-in-sage-x3/

First to navigate to the screens that’ll be used for the below steps:

Sales Invoice: All > Sales > Invoices > Invoices (GESSIH)
Window Management: All > Development > Script dictionary > Windows
Scripts: All > Development > Script dictionary > Scripts

Refer the screenshots for reference:

Step 1: Head over to Sales invoice > Management tab and locate the fields. The initial default values in these fields are set to current system time.

Fields in SI screen before customization.jpg

Step 2: For the customization we require a couple of Action events to be assigned to Invoice Preparation time (Arrival time) and Invoice Preparation date (Arrival date) fields. The purpose of these events is to trigger our customization on Departure time and Departure date fields upon changes made.

Step 3: The customization logic performs 3 parts which are as follows:
1) If a new Invoice is being created through New button press then the Arrival time field and Arrival date field will default to Current system time and date and the Departure time field will default to +20mins (as per requirement) from Arrival time field and Departure date field will default to Arrival date.

1st Customization

2) After defaulting if the user changes the Arrival time/date fields then the respective changes will reflect on Departure time/date fields.

2nd Customization

3) If the Invoice creation takes time, then upon creation the Arrival time field will reflect the Creation time and Departure time field will reflect change as per Arrival time.

3rd Customization

Step 4: The key part is the conversion from Date-time data to CLBFile format (HH:MM format) and vice-versa to get the required changes made to the Departure time field. For this GDATETIME$, DATE$, VAL(expression) and FORMAT$ Sage X3’s keywords for achieving this.

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.

Sage X3 has a special feature of prepayment in the sales order screen which can be created against sales order. Using this feature, user can create prepayment with the order amount against sales order and then user has to create advance payment for the same amount.

New stuff: Validation of Supplier Invoice No and Date in GRN

One of our client came up with a requirement that if user has created prepayment in the Sales Order screen for any particular entry by clicking on Prepayment button and entering amount in the grid then system will restrict user to create further Sales transactions such as Sales Delivery, Pick Ticket or Invoice etc. until advance payment is not done against the same sales order.

Let’s see the functionality with an example. Here we have created a Sales Order and created prepayment against the same sales order as shown in the below screenshot by clicking on Prepayment button from the Sales Order.

Prepayment Against Sales Order

Now as per our requirement, we have to make advance payment against that sales order. But if advance payment is not done and we are going to create further transaction for same order then system will not allow to do further Sales transactions.

Here we haven’t created any advance payment against this order and we will try to create sales delivery by clicking on delivery button from sales order screen as shown in below screenshot.

Delivery Creation Against Sales Order

As we haven’t created any advance payment against that sales order, system is restricting to create delivery of that SO by giving a popup message as shown in the below screenshot.

Restriction Message Popup

After clicking on “Ok” button of the popup message system will terminate further steps and will not allow us to create us delivery against this order.

As explained above, we have added same restriction on the preparation of pick ticket, invoice or proforma creation from sales order screen if Advance Payment is not done.

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.

Addition of Location in Physical elements screen in Fixed Asset Module

How to restrict user for accessing certain modules & sub-modules in Sage X3

How to create work order without routing in Sage X3

How to solve “Transaction stopped” error while creating sales invoice in Sage X3

How to export a file outside the SAGE folder in the X3 server

How to repeat group header on each page in Crystal Reports

Product Code and Description Automation

Working of customer extension in Sage X3

Revised cost calculation in Sage X3

Automatic deallocation function in Sage X3

Use of CTLCLE parameter

Marketing campaign in Sage X3

How to make adding a functional authorization easier

Warning message on the screen when “To date” is smaller than “From date”

Validation on the Sales order screen if credit limit exceeds

How to set dynamic Status field on screen based on date range

Error: “MRK(501): Index Incorrect” in Sage X3

Validation of Supplier Invoice No and Date in GRN

Dynamic Departure time change based on Arrival time selection

Restriction on Sales Order if Advance Payment is not done