Automated Creation of Operation Wise – Product Code

In Sage X3 Bills of Materials (BOM) play a significant role for companies involved in manufacturing finished products. They enable the manufacturing unit to plan inventories, design, and estimate the final cost of the entire manufacturing process.

One of our clients required the automated creation of Operation-wise Product codes from the routing screen of the Production BOM screen in such a way that the user could create the Engineering BOM FG01 with the code as 10 and update the routing for the same product as 10.

New Stuff: Crystal report with oracle query in sage X3

Fig 1: Production BOM Screen

Fig2 : Routing Screen

By taking this as a reference, the system was supposed to create the operation-wise Product Code.

1)In the BOM and Routing screens, all data should be entered manually. While creating the Routing, the product code (formed by combining the Routing product and Operation number, separated by ‘_’) must be generated and added to the Product master. This newly created product code should then flow into the Product Outcome field (a custom field in the Routing tab).

2)The 1st Operation is Bar-Cutting. By referencing the routing and routing operation sequence from the routing screen, the system should generate the new product code as FG01_10 in the Product master and display the Product Outcome as FG01_10.

3)The 2nd Operation is Pre-Machining. By referencing the header and routing operation sequence from the routing screen, the system should generate the new product code as FG01_20 in the Product master and display the Product Outcome as FG01_20.

4)The 3rd Operation is Final Inspection. Here, by referencing the Main FG Code, the system should display the Product Outcome as FG01.

5)The system will generate operation-wise product codes for all operations except the last one. For the final operation, the product code will be designated as FG01_BC in Product master.

For the above requirement, there were some conditions like :
Product Category of Parent Product could be any type but Product Category of the automated product code that we’re creating using the code must be OPER type.
 BOM code of Parent Product must be 10.
 Routing code must be 10.

To accomplish the aforementioned requirement, we executed the following steps:
Step 1:
A new display field was added in Routing Operations labeled as Product Outcome.

Step 2:
For streamlining the process, a custom Import/Export template named ZITM was generated. This template mirrored the standard ITM template, encompassing only the essential fields.

Step 3:
The ZITM template was imported using a 4GL script in the SPEROU script. The Product Category was configured as OPER, and other details were retained identical to the Parent Product during the import.

Step 4:
A fresh folder titled ROU was established within the server’s directory to store the imported files.

Step 5:
Additionally, a ZTEMP sequence number was established, incorporating a constant and a sequence to generate unique files in the ROU folder.
Sequence Number path : All -> Setup -> General parameters -> Sequence number definition

Fig 3: Sequence Number Definition

Ultimately, the products newly generated (formed by combining the Routing product with ‘_’ and the Operation Number) are showcased in the Product Outcome field through the implementation of a 4GL script within the SPEROU script.

Fig 4 : Routing with Product Outcome