Sage X3 – Tips, Tricks and Components

An inquiry screen is used to extract information from one or more table and present it in the from of a grid. It help us to display the records based on the filter criteria we entered.

In Sage X3, we have a multiple inquiry screens available such as Stock by product, stock by lot,stock by site etc where we can search a stock available by product wise, lot wise and site wise etc. Stock by product screen help us to check the stock of a product we want to search by specifying the name of the product in the field. But if want to search based on some condition we can search the same by creating a formula. Sage X3 provide us a functionality of creating a formula where we can create a formula based on any condition.

Sage X3 allows the user to add formula to inquiries criteria that can help to filter a specific record based on the condition specified in the formula. Here we want to search a stock of a product only whose product status is active.

To create a formula follow the below steps:

Navigate to : Set up > General Parameters > Formula

Click new to create a formula.
Select the formula type as “Stock selection”.
Provide the code , description and short description.
Enter the condition in the formula based on which you need to search a product.

We have specified [F:ITM]ITMSTA=1 as we want to search the product whose status is active.

Click on the create button. Refer the below figure

In this way we have to created a formula named as ZSP and now we can use the same formula in inquiry screen.

Follow the below steps to add the formula in inquiry screen:

Navigate to : Stock > Inquiries > Stock by Product.

Here we have specified the product in the From product and To product field and clicked on search so we can see the stock available for those product. If we wont specify any product and click on search then all the products will get display whose status is active as well as in active.

Since we need to search for all those product whose status is active. Click on the criteria button on the right side. Refer the below figure.

The below window will get pop up. Scroll down to enter the formula.

Select the formula you have created by clicking on the selection. Then click ok.

Once you click on OK, then all the product will get display whose status is active.

Refer the below figure.

**Fig: Criteria in product stock inquiry screen**

In this way we can create a formula based on which we want to search a product and can be used in the inquiry screen.

In this blog, we came to know how we can create a formula and to use those formula in the inquiry screen.

About Us

Greytrix – a globally recognized and one of the oldest Sage Gold 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.

There are many instances when client wants to give multiple copies of the invoices to their customers, where they must segregate multiple copies into original and duplicate. So we have given option on the report for those client where at the header part Original and Duplicate check boxes are given. So if the specific invoice is printing for the first time then Original checkbox should be ticked and if it is printing for more than once then the checkbox for duplicate should be ticked.

To achieve this working in Crystal report please refer the below steps:

Step 1:-
Create subreport using below SQL query and add that subreport into main report.
For example, your report code is ZSINVOICE i.e. for Sales Invoice Report. Add our subreport in this main report.

Refer below screenshot for SQL Query snippet:-

New Stuff: http://www.greytrix.com/blogs/sagex3/2020/07/01/how-to-solve-if-new-field-added-in-inquiry-screen-and-still-not-visible-after-global-validation-of-window/

Where variable “NUMDEB” holds the Invoice Number and variable “FOLDER” holds the name of the Sage X3 folder in which you are working.

Step 2:-
Insert 2 ticked and 2 unticked check box images in report headers like below screenshot:-

Step 3:-
Add suppress condition for both of the header sections using Section Expert.

Below is the Condition for ‘Report header a’ section :-
{Command.COUNT}=1

Below is the Condition for ‘Report header b’ section :-
{Command.COUNT}<>1

Whenever user tries to print the Sales Invoice report from Sage X3, it will show checkbox ticked based on the counter.

Refer below screenshot of the sample output.

In this way anyone can identify whether the invoice copy is original or duplicate by looking at checkbox.

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.

Some companies would like to create their Finished Good products with a Lot Number that is the same as the Work Order Number that created the product. Finished goods are goods that have been completed by the manufacturing process, or purchased in a completed form, but which have not yet been sold to customers.

Why we make the Lot number same as Work order number because this can make the tracing of the Lot easier. In Sage X3, there is a standard functionality of doing this.

Follow below steps for the setup:

Steps:

First make sure the Lot Management setting of product is checked as a ‘Mandatory lot’ and under the Lot Sequence field this MUST be blank as shown in below figure.

Also, Product category set up should be same as product setup, as shown in below figure.

In short product and that respective product category set up should be set as defined above.

Navigate To: Common Data> Product category > Receipts Tab > Management Rules Grid

Select Movement type as ‘Work order receipt’
Change the value of Lot entry as a ‘Free’
Change the value of Lot by default as a ‘Document number’
Click on Save or OK button.

Please refer the below figure for the same.

**Fig : Product Category > Receipts tab**

Now we have done the setup for product master and product category.

Navigate To: Set up > General parameter > Parameter values

Select GPA chapter from left panel
Select MIS group
Click on the detail of MIS group from action button
Change the value of LOTMGT as a “In release”
Click on OK button
Save the changes.

Refer the below screenshot for the same.

Now follow the below path for the Work order creation,

Navigate To > Manufacturing > Planning > Work order

While creating the work order transaction, keep LOT no. as blank on line level and after creation you can see LOT no. is coming same as a Work order transaction number. Refer below figure for the same.

With the help of this setup you can align the Lot numbers with Work order numbers.

Hence after doing all the above steps we can able to align the same lot number with work order number.

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.

Fiscal Period is the period of time reflected in financial statements. Usually, the fiscal period is either the calendar year or a quarter. Fiscal period is also known as an accounting period.

The fiscal year is the consecutive 12-month period during which a business or organization plans its budget. It does not have to be from January to December.

In Sage X3, sometimes we may find difficulties like while running accounting task error comes for closing a period. So, for solving these Sage X3 has a some in build functionality. Kindly follow below steps for closing a period for particular month and for country.

Just follow the periodic tasks in the sequential order:

Step1:

Run accounting interface before closing the fiscal period: This is to check all the stock journals are posted properly and no error is pending.

Navigate to : Stock -> Periodic Processing -> Valuation -> Accounting Interface

Refer above screen shot, just open the accounting interface screen . Enter processing date and then click on OK button. This will show, the journals are posted properly or not.

Step2: This step is important for only those companies which are manufacturing company. For non manufacturing companies we can skip this step:

Run WIP posting for all the Work Orders which are closed: Make sure all the work order journals are posted properly.

Navigate to: Costing -> WIP -> WIP Posting

Refer above screen shot, open the WIP Posting screen.

Mark the ‘All Sites’ and ‘All transactions ’checkbox as checked then click on OK button. This will show, all the WO’s journals are posted properly or not.

Step3:

To check accounting task, all the task status should always be ‘Active’ and also check no journals are o hold status.

Navigate to: Usage -> Batch Server -> Accounting task

Step4:

Final Validation: This process is used to finalize all accounting journals. Select all the mandatory fields and then click on OK button in the Final Validation screen.

Navigate to: Financial -> Current Processings -> Final Validation

Step5:

Period Closing Process: For period closing process, just open the fiscal period screen. Follow below path:

Navigate to : Common Data -> G/L accounting tables -> General -> Fiscal Period.

Now here as you can see the above screen shot, all the stock status are open. Close them first from the drill down.

Now for closing accounting period, follow below path.

Navigate to: Common Data -> G/L accounting tables -> General -> Fiscal Period -> Closing button.

Now in this screen, select the period month for which we have to close the period status and then click on the OK button.

After clicking on the Okay button, the period status of all the selected period months gets closed.

Hence, after doing all the above steps we can close the fiscal period for particular month or year.

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.

There are many situation where user want to implement SSL certificate with Sage X3 syracus web server and want to be able to access Sage X3 without first attaching to their network. So in this blog we will learn how to implement the SSL Certificate in to Sage X3 syracus as well as all the necessary term required for the same.

First we will see what is exactly SSL means and definitions of all the terms to get clear understanding:

HTTPS over SSL is an internationally recognized protocol for secure communication over a computer network which is widely used on the internet traffic. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security or its predecessor, Secure Sockets Layer. The main motivation for HTTPS is authentication of the visited website and protection of the privacy and integrity of the exchanged data.

Definitions of certificate format mostly use to configure SSL certificate:-

SSL – SSL Stands for Secure Socket Layer
.csr – csr stands for Certificate Signing Request
.pem – PEM stands for Privacy Enhanced email
.crt .cer .cert – A .pem (or rarely .der) formatted file with a different extension, one that is recognized by Windows Explorer as a certificate, which .pem is not.
.key – This is a PEM formatted file containing just the private-key of a specific certificate and is merely a conventional name and not a standardized one. In Apache installs, this frequently resides in /etc/ssl/private. The rights on these files are very important.

If you want to use SSL certificates you need to generate a Certificate Signature Request (CSR) and obtain a server certificate issued by a Certificate Authority (CA).

User need to Purchase a trusted Certificate from a Recognized 3rd Party provider. They will create and own the Root CA (Certificate of Authority) from where the authentication is verified at the highest level of the authentication chain. The 3Rd Party will then provide you with a PFX file and a secure password that will be used to generate an Intermediate CA certificate (.crt) and Public Key (.key).

Examples of some 3rd Party Providers of Trusted SSL Certificates: Digicert , Thawte , Verisign, GoDaddy , TrustTheSite Etc.

In order to configure the certificate in to sage X3 we required the certificate in two format i.e. .CRT and .Key Format.

Note: – We can also generate the .crt and .key file using the .pfx file format.

We will see how to register the Intermediate CA certificate on the Web syracus server:-

This is done by navigating to Administrator >>Certificates function in Syracuse:

Select Create “New certificate” option to create and upload new certificate in to sage X3.

You will get below window where you can upload your Certificate i.e. (.Crt) file and Private Key i.e. (.Key) file.

This will complete the registration of certificate in to syracus.

Now we will see how to setup Syracuse Hosts to communicate using HTTPS over SSL.

Once the intermediate CA certificate is registered in Syracuse the Syracuse hosts have to be setup to use the new certificate. To do the steps navigate to the Application >> Host. You need to host your created certificate with port 443 or 7777.

There are two options at this point, the standard SSL port (443) can be used or we can assign a custom port (7777). Ensure that the SSL tick box is selected and the certificate that was registered in the previous step is populated.

This is how you can configure the SSL Certificate with the sage X3 syracus to secure your website and to secure communication over a computer network which is widely used on the internet traffic

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.

In sage X3, we have a functionality of printing various types of reports such as Order, Invoice, Payments, and Receipt etc. This report is created by using crystal report. Crystal Report is a very powerful tool used to pull data from sage and present it in a ways you want.

Sometimes in crystal report, we may have to develop sales history report. The report should shows the Order No, Invoice No, order date, invoice date, shipment date and how many days it takes to ship an order from the day we received the order until the day it is invoiced. We may also want to calculate how many days early or late based on the date promised to the customer. If the deliveries won’t be done on weekends then in that case we may need to exclude the weekends from the number of days. Refer the below figure of report.

We need to create two different formulas, one for calculating Days to ship and other for Days late.

Calculation Needed:

Days To Ship= Invoice Date – Order Date(exclude weekends)

Days Late= Invoice Date – Promise(Shipment) Date (exclude weekends)

Crystal report has a various types of built in function and operators that includes String function, math function, date and time function, date ranges, arithmetic ,conversion, array operators, etc. We may use that pre-defined function to perform various calculation etc. Some of the Date Time function are as follows:

Date and Time Function includes:

Current Date : This function display the current date.

Current Time: This function display the current time.

DayOfWeek(): This function diplays the day of the specified date.

Syntax: DayOfWeek(date)

DateAdd(): The DateAdd() function can be used to add an interval of time to a date.

Syntax: DateAdd(interval type,number,start date)

DateDiff():The DateDiff() function is used to calculate date difference between two dates.

Syntax: DateDiff(interval type,date 1,date 2)

DatePart(): The DatePart() function returns the part of a date such as a day, month and year.

Syntax: DatePart(date_part,input date)

Interval type description:

yyyy: years

d: Day

m: month

w: Weekday

ww: Weeks

q : quarters

h: hours

m: minutes

s: second

As we have to calculate here difference between two dates we will use DateDiff() function.

Crystal Formula to exclude weekends:

Set Variables for the fields to be used in the calculation.

Define the variable of datatype datetime to be used in the calculation i.e. d1 and d2.

Formula to calculate Days to Ship:

DateTimeVar d1:= {SORDER.ORDDAT};

DateTimeVar d2:={SINVOICE.ACCDAT};

DateDiff(“d”,d1,d2)-DateDiff(“ww”,d1,d2,crSaturday)- DateDiff(“ww”,d1,d2)

Formula to calculate Days Late:

DateTimeVar d1:= {SORDER.SHIDAT};

DateTimeVar d2:={SINVOICE.ACCDAT};

DateDiff(“d”,d1,d2)-DateDiff(“ww”,d1,d2,crSaturday)- DateDiff(“ww”,d1,d2)

Where “d” is no. of days

“ww” is no. of weeks

“crSaturday” is used to exclude all the saturday between dates

“crSunday” is used to exclude all the sunday between dates

This blog help us to calculate the number of days between two different dates using date function i.e DateDiff() excluding the weekends.

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.

Sometime we may come under a situation where we need to restrict the purchase order if there is no purchase request. This scenario can be handled on the basis of product. We may have a condition where we need to apply this restriction only for some type of product. We can apply this restriction for the whole category of product. This can help users in their business scenario if they wish to setup such restriction on particular products. In the same way we can also apply the restriction i.e. if there is no open order of a particular product, we won’t be able to create its purchase order. But standard allows this restriction only on product not on whole product category.

New Stuff:- Implement SSL Certificates with Sage X3 Syracuse web server

Steps to follow:

To restrict PO if there is no request-

There is a checkbox named “Mandatory PO request” placed in the PURCHASING tab of product master as shown in the below figure. As the field name it-self says that open order for this product is mandatory. Kindly check this checkbox if you want to apply restriction on that particular product.

Navigate: ALL -> COMMON DATA -> PRODUCT

If we want to restrict the whole product category we do have same checkbox in product category window as shown below figure.

Navigate: ALL -> COMMON DATA -> PRODUCT CATEGORY

Once we have checked this checkbox on product master and try to create the purchase order with this product, standard displays the below error and do not allow us to create the purchase order.

Hence, when we want to create a purchase orders for such kind of product we will always have to create the purchase request with respect to the restricted product and then convert the purchase request to purchase order.

To restrict PO if there is no open orders-

In the same way we can add restriction i.e. if there is no open order of a particular product, we won’t be able to create its purchase order.

There is a checkbox named “Mandatory open order” placed in the PURCHASING tab of product master as shown in the below figure. As the field name it-self says that open order for this product is mandatory. Kindly check this checkbox if you want to apply restriction on that particular product. We cannot apply this restriction on the whole category of the product.

Navigate: ALL -> COMMON DATA -> PRODUCT

Hence, when we want to create a purchase orders for such kind of product we will always have to create open order with respect to the restricted product and then convert the purchase request to purchase order. In this manner we have multiple conditions in product, product master and product site that can restrict product to create transactions.

In this way by marking up those check boxes we can apply the restriction for products in the process of purchase order creation.

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.

In sage X3, enter key has some default functionality for e.g. in some screens it is used to trigger OK button functionality while in grid level it is used to jump on the next line and so on. So, depending on the requirement and screen type Enter key has different types of functionalities. But with the help of some coding and actions of screens we can actually block the default functionality of Enter key and can replace it with some other functionalities.

Steps to be followed :

So, in sage X3 when Enter key is pressed, X3 assigns the value of GSTARET to the variable RESPONSE. We can check that condition in the “After choice” action depending on the screens and template that we are using. For different screens and templates different actions are used but most notably APRES_CHOI or AP_CHOIX are used. For the below example we can use APRES_CHOI but depending on the template use we have to see which action is exactly used so it might be differ between the two.

So, in the list of actions we have to specify our action in the specific processing file of the script editor:

APRES_CHOI action gets called before executing an action (button, menu, left list, etc.)). A status that defines the action is sent by the supervisor in the RESPONSE variable.

It is possible to short-circuit the normal processing of a button, menu, etc.: This action is used to launch its own processing instead of the template processing, then to put RESPONSE back to 0.

The various possible values for the RESPONSE variable are given by global variables and various global variables stored the values of the various actions of button clicks. For example, GSTAENR is used to store Record button action response and so there are different global variables within X3 which are used for all sorts of buttons to hold their values and all.

AP_CHOIX action is called right after “clicking” on a button or a menu.

It is used to execute a processing after having “clicked” on a button or a menu. In effect, for most of the buttons, the processing has no standard processing. The processing needs to be written in this action. The buttons managed by the template are the following:

“END”, “PRINT-OUT”, “LIST”, “ATTACHMENTS”, “COMMENTS”, “PROPERTIES”.

This action takes place before the actions on button ( AVANT_BOUTON, BOUTON and AVANT_XXX, XXX ) where XXX represents the identifier of the predefined button.

This action takes place before the actions on menu (AVANT_MEN, MEN) The RESPONSE variable contains the status of the button and therefore indicates the button activated by the user and global variables used by buttons to hold the values of their status and response.

Then in the action handler we can stop the execution of standard functionality when we assign the value GSTARET to the variable RESPONSE. We can replace it with new customized functionality which might be useful.

Once we can make sure that Infbox statement is getting executed when we press “Enter” on screen, we can place something actually useful in its place depending on our needs.

With the help of above steps, you can change the functionality of Enter key.

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.

In Sage X3 V12, a new functionality is added which will help in enhancement in quality standard. In any organization it’s important to maintain Quality control process be it at sales level, manufacturing level or purchasing level.

Quality control is a critical aspect of the development cycle of a product also on handling return products from customers. We can use this new function Non Conformance Management to raise incidents on a transaction level which will provide a never before insight of the exact transaction level details.

There is a new menu added as ‘Non Conformance Management’, under which following three functions has been added.

Non-conformance
Non-conformance plan
Actions

Non-conformance plan: This screen is used to get information and schedule corrective or preventive actions against a reported non-conformity.

Actions: This function to link business processes which is defined as action code with specific types of transactions.

Non-conformance: Quality control is a critical aspect of the development cycle of a product also on handling return products from customers. We can use this new function Non Conformance Management to raise incidents on a transaction level which will provide a never before insight of the exact transaction level details.

A managed reports of incidents of non-conformance raised directly from an associated transaction such as a Purchase receipt, customer returns and production tracking level.

If a user observes that a product does not comply with organization standard user locks incident forms with the details it becomes the source of the information to support investigations into the root cause, or failure.

Below are the details of section which handles different level of information which will be used in resolving the incidents effectively.

Path: All>Non-conformance’s>Non-conformance management

Home section > The Home section provides key tracking information.

Identification > This is the main section for this function. It is critical to the root cause analysis.

Review > This section to support root cause analysis. The information in this block is critical to the success of incident. It will be used when defining the corrective and preventive actions required to eliminate the root cause or failure.

Rejection > This section is used by the QA manager for this non-conformance incident when this incident is formally rejected. Access to the fields is controlled by the Status field in the Home section.

Close > This section provides closure information for this non-conformance incident.

Reported by > This section provides contact information of reporters who raised the Non-conformance incident.

QA manager has ultimately have full control over Non Conformance incident and the progress of it and

Below are the three actions which can be performed on the Non-conformance incident.

Review
Plan
Reject

Review: Once incident has been raised QA can review all the details and check all information provided in the Non-conformance incident. This is an optional stage QA can directly go for planning.

Plan: Once review is done, on the click of Plan status changes to ‘In planning’. In this stage a better approach/plan to deal with this incident is decided and assigned to respective person of QA department.

Reject: Once proper checking/analysis of the incident is done by the QA department and it is found that there is no defect in the product then QA can reject the Non-conformance incident. The status of this non-conformance will change to status ‘Rejected’. QA must define the reason the Quality control team is rejecting this non-conformance incident.

The Non-conformance function is the central function for managing incidents of a ‘problem’ or ‘defect’ reported. It controls every stage of the ‘corrective and preventive’ process which is need by an organization to maintain its quality standard.

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.

In Sage X3, we may come across a situation where we need to create query tool by adding fields from the table also while adding field we may get the below error as shown in fig 3.

Step1 :- To create query tool Go To -> Set up -> Usage -> Reports -> Query tools.

Create first query code and keep the active check box enable and then in field tab add Table and fields as shown in fig1.In Representation block we can select from drop down list here we have selected character and graph.

Step 2 :- While adding fields. In Graph type (as shown in below fig 2) there should atleast one value type field (here we have taken YLINE which is line number) and one description type field (here we have taken the field YBP as description which is BP). We can add multiple fields in value type but we cannot add multiple description type . As shown in Fig 2.

It is not possible to add more than one description type field in Graph Type which is alphanumeric data type . We may come across one error as shown in fig 3 i.e. There already is description type field.

So we need to change this graph type to None by clicking on drop downlist. Therefore, we can now add multiple fields with alphanumeric data type by keeping the graph type to None.(i.e shown in fig 4).We should also add atleast value type field like YOAMT is amount type field having data type is based on currency .We may add many graph type having value also when we add value type the Representation block automatically sets to Default. So the graph is designed on the bases of graph type i.e value .

Step 3:- We can also the graph type we have set the Default Graph—Bars. There are many option in Default graph like line type,Bar type etc.

Now we can click on VALIDATE button , once it is validated we can click on RUN button to see the desired output. As shown in fig 5. Here graph varies according to the amount and at the bottom we get the description which we have set in graph type. That is why we require we set the graph type as value, description and none.

**Fig6: My Open amount per customer screen**

Once we have created the query tool we can now use them to create Landing Pages i.e (Home pages) in Sage X3. For creating home pages we need to create the Menu items .

Go To -> All ->Administration -> Authorising -> Pages -> Menu Items -> Create menu items

Once we have created the menu item now we can add them in Home pages .

Go To -> All -> Administration -> Authorising -> Home Pages

This blog will help to create query tool as well solve the above error as shown on above fig 3.

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.

An inquiry screen is used to extract information from one or more table and present it in the from of a grid. It help us to display the records based on the filter criteria we entered.

To create a formula follow the below steps:

Navigate to : Set up > General Parameters > Formula

Click new to create a formula.
Select the formula type as “Stock selection”.
Provide the code , description and short description.
Enter the condition in the formula based on which you need to search a product.

We have specified [F:ITM]ITMSTA=1 as we want to search the product whose status is active.

Click on the create button. Refer the below figure

In this way we have to created a formula named as ZSP and now we can use the same formula in inquiry screen.

Follow the below steps to add the formula in inquiry screen:

Navigate to : Stock > Inquiries > Stock by Product.

Since we need to search for all those product whose status is active. Click on the criteria button on the right side. Refer the below figure.

The below window will get pop up. Scroll down to enter the formula.

Select the formula you have created by clicking on the selection. Then click ok.

Once you click on OK, then all the product will get display whose status is active.

Refer the below figure.

In this way we can create a formula based on which we want to search a product and can be used in the inquiry screen.

In this blog, we came to know how we can create a formula and to use those formula in the inquiry screen.

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.

In Sage X3, Users can check all the purchase related data using inquiry screens. But there is one drawback of this functionality that any user can check the data of all the other users also using inquiry screens. To overcome from this drawback, we did customization on Purchase Inquiry screens. By doing which users can check only those POs and GRNs in Inquiry screen which have been created by them. Users will be restricted to fetch other user’s data.

But there can be some users in the system who needs to see all the user’s data.

For this purpose, we have added “Full User” checkbox in the user master screen as shown in the below screenshot:

New Stuff: https://www.greytrix.com/blogs/sagex3/2020/08/25/how-to-create-and-add-formula-on-inquiry-screen/

[User Master]

If the Full User checkbox is ticked, then that particular user will have full rights to check the all user’s purchase related data and if it is not ticked then user can check only those entries which are created by him. As you can see in the above screenshot, full user checkbox is ticked for “ADMIN” user and not ticked for “ABHI” user in the user setup. So there can be two scenarios that either the user is a FULL USER who will have access to check other user’s Purchase entries or he is not a FULL USER who will be restricted and can check only Purchase entries which are created by him.

After that, we have added “My PO” and “None” radio buttons on Order Lines Inquiry Screen and “MY GRN” and “None” radio buttons on Receipt Lines Inquiry screen. Now, we will check how the functionality will work for both the Scenarios.

First scenario: Admin user is logged in. (FULL USER)

[Order Lines Inquiry screen – ADMIN User (My PO Option)]

As you can see, when admin user has selected “My PO” option in inquiry screen, only POs created by him are getting displayed but when he has selected “None” option in the below screenshot, he is able to see all the POs which are created by other users also.

[Order Lines Inquiry screen – ADMIN User (None option)]

Second scenario: ABHI user is logged in. (not a FULL USER)

[Order Lines Inquiry screen – ABHI User (My PO option)]

In the above screenshot, when ABHI user has selected “My PO” option in inquiry screen, only POs created by him are getting displayed and even when he has selected “None” option as shown in the below screenshot, same data is getting displayed i.e. POs which are created by him. He doesn’t have rights to check other user’s POs because he is not a FULL User as per the user master settings saved in the User setup.

[Order Lines Inquiry screen – ABHI User (None option)]

Also we have added “My Department” and My Sub-Department” radio buttons on both the screens. If department of the users is same and he has selected my department option then he can see POs created by him and other users as well who are having same department saved in user master. Same functionality will work for Sub-Department option.

Hence with the help of this customization, User will get restricted as per the given rights. And he will not get access to check other user’s Purchase related data.

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.

As we know, Sage X3 supports multiple date formats as per the users requirement. The default date format in Sage X3 is setup in setup–> Parameters. For the developers who wants to manipulate date field value, can use date functions in 4GL. Also there is inbuilt string function which can be useful for the developers to manipulate date using 4GL.

In this blog, we will see how we can manipulate date format using “format$”string function.

New Stuff: User Restrictions on Purchase Inquiry Screen

Syntax: format$(“format required”,”Date value”)

Let’s consider an example, format$(“YYYY[-]MM[-]DD”,date$) , Here we considered.

“YYYY-MM-DD” format and “date$” function gives us current date and we change the current date format of system to required format in our code.

In the above format square brackets i.e. “[ ]”are used to represent the constant value or spaces between date characters. The given date format is stored as a string in the system.

Below are some examples of the date formats with output which helps you to change the date format in 4GL script.

So by using Format$string function 4GL scripts, developers can change the date format according to users requirement& also can used in 4GL.

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.

Sage X3 reports are developed in Crystal reports and can be modified as per user needs if you have required Crystal version installed on developer system. One of our client has requested to add ‘Terms and conditions’ on last page of the Purchase Order report. This was one of the easy task to add on the crystal for any developer but here we had one challenge to hide company Name & address for last page which was placed on the Page header and was printing on each page. So we come up with the solution and thought of sharing information with everyone.

This blog can be helpful when user wants to add summary or terms & conditions on the last page of the report and doesn’t want to include the page header details (company name, address, logo, contact details etc.) on last page.

To achieve this working in crystal report please refer the below steps:

Step 1:- Click on “Report” menu and select “Section Expert”.

New Stuff: Change the Date Format using 4GL

Report Menu

Step 2:- Select “Page Header” section from Sections.

Section Expert

Step 3:- Click on the icon at the right side of “Suppress(No Drill-Down)” and enter below formula in “Formula Workshop”

PageNumber = TotalPageCount

Formula Workshop

Step 4:- Click on “Save and close” to save changes.

Step 5:- Click on “OK” to save changes.

Output:-

Output-Fig. 1

Output-Fig. 2

In this way we can exclude the page header from last page of any report.

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.

As we all know, in Sage X3 when users want to create Purchase invoice against purchase receipt, he/she has to select receipt from the left list one by one. Recently one of our client wanted to have an option to select all Receipts in a single click from the left side panel while creating purchase invoice against a particular vendor.

New Stuff: How to exclude header part on the last page on Purchase Order

Purchase Invoice Screen

Previously user has to select receipt one by one which is very time consuming in case of 100 Receipts . So, we did modified invoice object PIH to have a check box in the left side panel of Purchase Invoice screen besides Receipt header as shown in the above screenshot which will select all the available Receipts in a single click.

Refer below steps that need to follow:

Step1 : Go to Development -> Select ‘PIH’ object.

Step2 : In General tab -> Management tab and then select management type as “ Simple selection “.

Step3 : Do validation of the object ‘PIH’ and also do global validation of that ‘OPIH’.

So using standard option available at object level, we did provided solution to our customer for selection all receipts on left panel.

In this blog post, we will discuss how to create manual remittance entries in Sage X3. As we all know, in Sage X3, payments can be done against invoices that are generated from Purchase Invoice and Supplier BP invoice from the AP-AR accounting module. Payments transactions are created bank-wise as per the selected supplier/vendor. Payments are also done against multiple invoices and users can create the remittance entry against multiple payments. The purpose of Remittance entry is to provide the payment transactions to a particular bank in proper format with cash settlement, bill exchange issues, collections, check payments, discounts, etc.

GUMU Integration App

By using manual remittance creation, users can create a group of payments manually which are linked to the same bank, same transaction, same site, and same company in a single remittance. They can also modify, delete, or update previously created entry but once it is posted they can’t do any amendments in the same.

Now let’s take an example, the user has to create the payment transactions against an invoice first,

To navigate, AP-AR Accounting–>Payments Section–>Payment/Receipt Entry.

Create some payment transactions against the purchase invoices and then post those entries. Generated payment are PCHQ1612102000340, PCHQ1612102000161, PCHQ1610102000332, This payment can be done against purchase invoice or supplier BP invoice transactions.

Now we will create Manual remittance entry by navigating to AP-AR Accounting–>Remittances Section–>Manual Remittance Creation, refer below screenshot:-

New Stuff:

In above screen, first we have to select site, bank and then payment type (so that only particular payments will be selected as per the selected payment type)discount type, check type. After that select one or more than one payment entry to create the remittance entry in the bank and then deposit slip in particular bank. This all payments will be manually remitted in the bank which was selected at the header level.

The status will be shown in the status field as per the transaction whether it is posted or created. After the creation of remittance entry, the status will be “Slip Entered”, when a user clicks on Bank file button to create the electronic/EDI file then the status will be changed to “Slip-on file” and after posted the remittance entry, the status will be changed to “In the bank”.

Users can also click on the post button to post the remittance transaction in the bank. Based on the payment type, supplier, and bank details the system can provide a remittance on a transitional account or directly in the particular bank. This button is also used to validate remittance entry.

Bank File button is used if user transmission of a deposit planned in the payment transactions with the bank at its target. By clicking on this button, an electronic file or EDI file will be sent in a specific format.

In this way by using the manual remittance creation screen, the user can create the remittance transaction with the group of payments to the bank for a company through a single remittance entry.

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.

There are many situations where user need to set up the important information or messages for specific customer in ERP. Now Sage X3 is also provide the provision of setting up the messages or notes for specific customer which will further reflect in to sales document.

Today in this blog we will discuss how user can setup the messages/notes for specific customer.

New Stuff: – Manual Remittance Entry in Sage X3

Navigate to below path to setup a notes in customer screen:

Common Data >> BP’s >> Customers >> management Tab. In the management tab you can see the notes section and Customer notes icon.

Once you click on Customer notes icon the system will redirect you to the Notes screen where you can mentioned all the details such as Description, Short description and Comment under the section of Notes. You can also set the start and end date i.e. Validity period of the particular notes.

Kindly check below screenshot for detail view.

Basically this function can be accessed from the Products, Suppliers, Prospects and Customers management functions.

You can use the notes function to enter information related to the product, supplier, prospect or customer as a note. This information is displayed or inquired from the functions that have been selected at the Note category level.

User can create multiple notes for the same product, supplier, prospect, customer, and indicate if they must be displayed as a priority.

Let us see the use / function of all the fields present:

Note: – This is basically use to enter mentioned the Note code which will further use to identify the notes.
Category: – Use this function to set up and maintain note categories for products (including product-sites), customers, suppliers, prospects, or customer relations. When creating a note, this note is assigned a category that determines in which functions this note will be available. These functions may belong to the Purchasing, Sales, Customer relation and Production module
Description and Short description: – This is use to add the particular description. For both the field there is a Translation option is present form the Actions menu in order to open the Line Translation function.
Effective Date: – This field use to determine from which date the note can be access in the function selected in the category. By default it is the system date. If this field is blank, the note takes effect the same day it is created.
Expiration date: – This field use to determine till when this note will be available. By default, the expiry date corresponds to the default system date + 1 year. If this field is blank, the note does not expire.
Auto Display: – User can specify if the note must be displayed automatically by using the option Auto display. This option helps user to display the notes automatically during the data entry.
Priority: – This field is use to assign the note as a priority.

As per the mentioned above in the category section we have created this particular notes with category “ALLC” and we assigned all the modules for this category. So during further data entry if user wants to create the sales order then this created notes will be pop up once user enters the Customer in the sales order transaction. You see below screenshot for details.

This is how user can setup the comments for specific customer in Sage X3. This will helps user to easily maintain the important notes / Message for customers. This feature is very user-friendly and it is introduced updated version of Sage X3 i.e. in V12.

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.

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

A sales invoice is an accounting document that records a business transaction. Sales invoices provide the business with a record of the services they’ve provided to a client, when the services were rendered and how much money the client owes the business. Typically, a sales invoice will include a description of the service provided, the amount owed and the deadline for payment. A sales invoice is created by the business after they’ve provided products or services to a client, as a way to request payment.

We may need a basic important points to make a sales invoice such as:

Customer Details
Payment Terms.
Payment Due Date.

Payment Terms: Its is a condition under which a seller will complete a sales . Typically, these terms may demand cash in advance, cash on delivery. Also the payment terms on your sales invoice, including the payment methods you accept (i.e. cash, cheque, credit card, debit card, visa etc.).

Payment Due Date: It is the date when payment should be received by the company. Also it clearly list the deadline for payment on your sales invoice. Eg(Payment due in 30 Days etc etc.).

Now sometimes in Sage X3, we may find difficulties in entering the serial number manually in sales invoice screen as this field is always seen disabled in the screen. So, for solving these Sage X3 has a some in build functionality. Kindly follow below steps for enabling the serial number field in Sales Invoice screen.

Navigate to: Sales -> Invoices -> Invoices

As we can see in above screen shot, serial number field is disable. Now follow below steps to enable this field.

Step1:

Open Sales Invoice screen.
Click on new button.
Enter site, customer
Set stock transaction field as ‘Yes’. Refer below screen shot:

Navigate to : Sales -> Invoices -> Invoices -> Management tab

By doing above steps , serial number field will get enabled in the lines grid.

Now follow below steps to display data in serial number filed in lines grid.

Step1:

Create new product or select product whose serial number management is set as ‘Issued’.

Navigate to: Common Data -> Products -> Products -> Management tab

Now create sales invoice.
Set stock transaction field as ‘Yes’.
Enter product in lines grid.
After entering quantity, new screen is getting open name as ‘Stock issue entry’.
Now go to action button and select ‘serial number issue’ button from the lines grid. Refer below screen shot of the same:

After this, new screen getting opened named as ‘Serial Numbers in issue’.
Enter quantity to issue.
Enter ‘Starting Serial number’.
Click on Save button.

Now check serial number field data is visible in lines grid.

By doing all the above steps, the field will get enabled and data will get populated on the field.

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.

In some business scenario customer wants to change the expiry date when product exist in multiple sites, of the existing Lot numbers of its existing stock, and they were hunting for a solution which could help them with this.

A lot number is an identification number assigned to a particular quantity or lot of material from a single manufacturer. Lot numbers can typically be found on the outside of packaging. For cars, a lot number is combined with a serial number to form the vehicle Identification Number.

The lot number enables tracing of the constituent parts or ingredients as well as labour and equipment records involved in the manufacturing of a product. This enables manufacturers and other entities to perform Quality control checks, calculate expiry date and issue corrections or recall information to subsets of their production output. It also gives consumers an identifier that they can use in contacting the manufacturer and researching the production of goods received. For example, to trace back the origin of fish or meat, in case of a public health problem.
The expiry date is associated with a lot in stock. It indicates a usage end date for the stock of a product and is controlled in the issue movements. In Sage X3, there is a standard functionality, with the help of this user can modify the LOT’s expiration date for multiple sites.

Follow the below steps to modify or change the LOT’s expiration date:

Steps:

For example, we have FIN501 product at two different sites which has LOT expiration date is 08/09/20, as shown in below figure.

Now we will modify the existing Product LOT expiry date with the help of below screen.

Navigate To: Stock > Lot modification > Lot mass change

Select the All sites check box when the lot number is existing at multiple sites for respective product.
Enter product
Enter LOT number
Enter the LOT expiration date
Click on OK.

Please refer the below figures for the same,

After clicking on OK button, it will display one screen to verify the entry.

Now after saving the entry it will show one pop up message Entry validation select as a Yes, as shown in below figure.

After this process log file will be generated with the modified data, as shown in below figure.

Now the Lot expiration date has successfully modified. You can check the modified expiration date with the help of stock inquiry screen i.e. Stock by lot screen.

Navigate To: Stock > Inquires > Stock by lots

1. Enter a product and click on search button

2. It will show the multiple no. of LOT number, you can check the respective Lot number expiry date, as shown in below figure.

With the help of above steps user can modify or edit the LOT expiration date for multiple sites.

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.

In Sage X3, we are working on payment integration from x3 to the third party payment gateway. Here, we are doing sale/auth/refund/void transactions on the client’s payment gateway through Sales Order/Invoice transactions from X3. Here, we will provide prepayment & payment deletion functionality through the void button.

New Stuff:- How to change the LOT’s expiration date (for multiple sites) in Sage X3

Prepayment & Payment deletion in x3

As per the requirement analysis and the functionality provided, we are creating automated prepayment and payment in x3 on the click of sale button from Sales Order which will create Sale transaction in the payment gateway respectively. After the successful payment & prepayment creation, if the user wants to cancel or refund the transaction created on payment gateway, the adverse effect in x3 will be deleting the payment & prepayment created against the sales order.

Note:This will be only applicable if the respective payment and prepayment against the sales order is not posted in x3.

If the payment is posted for the sales order in x3, then the user need to manually run account cancellation process from the payment entry in x3 to cancel/refund the payment transaction in x3. There are many validations which we need to check while deleting the payment which are as follows:

Payment and prepayment should exist for the particular sales order.
Sales Order status should not be closed.
Payment against the sales order should not been posted.
Closing table whichever opened while deleting the payment and prepayment entry to avoid systematic error I.e. “Too many tables opened in x3”

In our analysis, we have found out there are few hurdles coming in the way while deleting the payment which we need to handle through code i.e to set default mask as sales order mask again to avoid different system errors.

Working:

Call AV_ANNULE2([L]CODE,FLGLOT) From SUBPAY3:

The above statement is written to call specific standard delete function from x3.

Delete [ZPYH] where NUM=ZPAYNUM

The above statement is written to delete payment entry from the payment table from x3.

Delete [ZDUD] where NUM=ZVCRNUM

The above statement is written to delete prepayment entry from the prepayment table from x3.

Gosub AP_ANNULE From SUBPAY3

The above statement is written to call the functions used after the deletion of the payment and prepayment entry from x3.

Gosub APRES_ANNULE From SUBPAY3

The above statement is written to call the functions used after the deletion of the payment and prepayment entry from x3.

Note: We need to handle any system error occurred during the customization of deletion of payment and prepayment entry against the sales order/invoice screen. Supposedly if we are opening masks or tables opened for our process then we need to close the tables and masks to avoid any type of crashing/error in Sales order/delivery/invoice transactions.

We can also provide the same functionality from sales delivery and invoice as well, whenever the user delete/close the sales order and the payment with prepayment is created (payment not posted)

Advantages:

Here, we are having the advantages :-

We don’t have to manually delete the payment & prepayment entries or run any account cancellation document from payment entry
All the functionalities runs from a single click from custom button to delete/cancel/refund transaction from Sales order/delivery/invoice.

This blog is used for understanding the process of deletion of payment and prepayment from Sales Order through code before payment posting and without effecting standard functionalities or crashing the screen. This blog’s functionality will provide users to delete payment and prepayment through sales order/delivery/invoice screen from a single click whenever the user want to cancel/delete/refund any sale transactions.

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.

How to create and add formula on inquiry screen

How to add checkbox in Crystal Report

How to Align Lot numbers with Work order numbers

How to do Period End procedure in Sage X3

Implement SSL Certificates with Sage X3 Syracuse web server

How to exclude weekends from total number of days in crystal report

Restricting purchase order creation if there is no request/open order

How to change Enter key functionality

Non Conformance Management in Sage X3 V12

How to create query tool to get desired output in Sage X3 V12

How to create and add formula on inquiry screen

User Restrictions on Purchase Inquiry Screen

Change the Date Format using 4GL Script

How to exclude header part on the last page on Purchase Order Report

How to enable select all check box in the left side panel in Sage X3

Manual Remittance Entry in Sage X3

How to Set Notes for Customer in Sage X3

How to enable serial number field in sales invoice screen in Sage X3

How to change the LOT’s expiration date (for multiple sites) in Sage X3

Payment & Prepayment deletion through the custom button from Sales Order