In Sage X3 there is some multiple type of movement code , found in Miscellaneous table 14. Basically movement code is used to specify when a product is received or issued . One of the predefined code is Status Change CHS which is used to further define the management rules on the product category by… Read More »
In the context of the sales order process in Sage X3, this implementation focuses on creating an outbound process for sales orders. Specifically, we aim to enhance the functionality by introducing a new button on the Sales Delivery Screen. This button will be selectively enabled only for inter-site deliveries, which involve transferring stock between different… Read More »
Recently we had a requirement from one of our client in which we have done customization on Requirement Quantity field of components tab in the Work Order screen. They are using stocking unit in “KG” in Sales Order but for work Order they require quantity to be converted in the “NOS”. So now by using… Read More »
In Sage X3, user can create products manually by setting the product code sequence and entering description for the same product in the product master. But now we have added a customization for automatic Product Code and Description generation to fulfil the client’s requirement. In this customization we have used one standard field “Product Line”… Read More »
In Sage X3, we recently had a requirement to configure an email to be triggered to send the Payment Voucher report as an attachment on posting the Payment entry to the respective supplier against whom the Payment entry has been created. So let’s see how we can create and configure an email. Step 1: Deploy… Read More »
In Sage X3, we often work on data grid screens/masks where managing operations on multiple lines such as deletion, copying etc. becomes a hassle. However Sage X3 offers the users a way which operates with ease as shown below in an example of a patch creation where we want to remove several objects which are… Read More »
In Sage X3, did you ever face a requirement where you wanted to set up a signature workflow without triggering a value to recipients to sign the transaction and use the workflow monitor instead to manage all their signatures? This blog shows you a neat trick to stop the mail from being sent to the… Read More »
Signature workflow is a feature provided by Sage for Automatic signature for a record if it is modified or created by the first level user defined in the Assignment rule. Once the user sign’s the record you will see “Signed” against the user and is processed to the next level of user for signature defined… Read More »
In Sage X3, every now and then a requirement requires a defaulting screen/mask field with a value upon initialization or start of processing. To achieve this requirement, Sage X3 offers several ways such as scripting in the Action script under specific events or through screen dictionaries.Below we are demonstrating how to default value through screen… Read More »
While creating any transaction in Sage X3, user has to enter “Gross Price” manually for the products in the detail line. But sometimes we use Price Lists to flow Gross Price automatically on the basis of Product and Supplier/ Customer combination. We have different price lists for Sales and Purchase with the respective Customers and… Read More »
