Chapter 5: Validation of Sage X3 Webservices objects and Data Dictionary

After all the Sage X3 patches are installed, we need to verify if all the web services objects and sub-programs are validated and published properly or not.

For Sage X3 v6.5, v7.0 and v8 - Once all the Sage X3 patches are installed, we can verify the same using the Web service tester (Adonix) provided by Sage X3 by following the below steps:

  • In IE browser type http://localhost:28880/root/

  • Enter username and password.

  • Navigate to Webservice tester -> Context section

  • Enter your Webservice Pool name, username, and Password.

  • Select the language as English.

  • Click on the Save Context button.

  • Navigate to the Subprogram tab.

  • In public, Identifier enter “XX3KARINQR”.

  • In the parameters, section enters the below value.

    <PARAM> </PARAM>

  • Click on Execute button.

For Sage X3 v9 and above - The user can use Webservices tester which is inbuilt in Sage X3 itself from Sage X3 v9 onwards.

  • Navigate to Administration --> Web services --> Classic SOAP web services

  • As we are going to check XX3KARINQR subprogram. Select the run option from the list.

  • Enter the language, Webservice Pool name in pool alias, and pool id.

  • In the Public name enter “XX3KARINQR”.

  • In the Input XML/JSON section enters the below value.

    <PARAM> </PARAM>

  • Click on Invoke button.

  • You will get a valid XML in the Reply section if executed successfully. Otherwise, you may receive an error Message.

  • Below is the error message user may receive if web service objects are not published/appropriately validated. BLOK, X3 subprogram (AWEB: RECUPHDAT) that reads web services [Unknown web service (0)] timestamp returned the status [] and timestamp [XX3KARINQR].

  • If you get the above error, you will have to publish it manually.

  • To publish it manually, please, follow the below steps:

a) Login to Sage ERP X3. b) Navigate to Development -> Script Dictionary -> Scripts -> Webservices c) Select the Webservice object XX3KARINQR from the list. d) Click on the publication button. e) The user will have to publish all the web service objects in this way which begins with the name XX3K….

  • Below is another error message that a user may receive if web service objects are not published/appropriately validated.

    BLOK, ErrNum=[20] ErrLine=[136] ErrPgm=[@NATRAINV6.TRT/WJXX3KALLCUST$adx] ErrTyp=[1] ErrMess= [C:\Sage\SAGEX3V6\X3V65\Folders\NATRAINV6\TRT\XX3KARINQR.adx : File Non-existent]

If you get the above error then you may need to copy ADX files at the below location manually C:\Sage\SAGEX3V6\X3V65\Folders\<your folder name>\TRT (assuming Sage X3 is installed in C:\ drive) and then publish web services manually. (To publish it, please follow the above publish it manually section).

You can find the ADX files in the ADX folder of the GUMU installation directory folder.

  1. Also, check for the XX3KPRDVW web service object if it is successfully installed and published. If the Sage X3 CRM side patch is not installed properly, the user may need to create this view/object manually. This view is used to display Sage X3 product lookup while creating orders/quotes in Sage CRM. If this view is not there, the user won’t be able to view the Sage ERP X3 product lookup.

  2. To create a view manually please follow the below steps:

    • Navigate to Development -> Data and Parameters -> Development setup->View

    • Enter the below values in the field

      i. View code: XX3KPRDVW ii. Enter the below query in SQL Server Query:

      SELECT ITMFACILIT.ITMREF_0, ITMMASTER.ITMDES1_0, ITMFACILIT.STOFCY_0,ITMMASTER.TCLCOD_0,ITMMVT.PHYSTO_0

      FROM ITMFACILIT

      JOIN ITMMASTER ON ITMMASTER.ITMREF_0= ITMFACILIT.ITMREF_0

      LEFT JOIN ITMMVT ON ITMMASTER.ITMREF_0=ITMMVT.ITMREF_0 AND ITMFACILIT.STOFCY_0 = ITMMVT.STOFCY_0

      LEFT JOIN ITMCATEG ON ITMMASTER.TCLCOD_0 = ITMCATEG.TCLCOD_0

      WHERE ITMCATEG.SALFLG_0 = 2 and ITMCATEG.DLVFLG_0 = 2

  • Navigate to the Fields tab and enter values as mentioned below screenshot:

  • Click on “Create” and then validate.

2. Dictionary Validation: Next step is to change the “Number of Sales order lines” to 300 -> Dictionary validation. Without doing this user won’t be able to promote orders and view order details.

Note: - This step is applicable only for the Sage X3 version V7 and above. If your Sage X3 version is v6.5 then you can skip this step.

There are 2 ways to achieve the same.

a. Dictionary Validation (Preferred One) b. Folder Validation

Below we have explained both methods but it is preferable to use the first one since it takes less time.

  1. Dictionary Validation: (Prefer this one)

Also, you need to validate the Dictionary for the SOH activity Code and the steps are as follows…

**Before dictionary validation navigate to Development -> Data and Parameters ->Development setup-> Activity Code. Select the Activity code “SOH” and change the screen size from 1002 to 300.

Step 1: Go to Dictionary Menu (Development > Utilities > Dictionary -> Validations -> Dictionary)

Step 2: It will open a Dictionary validation window and select a folder (E.g. SEED) and scroll down to enter the Activity Code.

Step 3: Add activity code “SOH” and select all the checkboxes as shown below.

Step 4: Hit “OK” to proceed with validation. It might take a few minutes to complete the process.

2. Folder Validation:

Please follow the below steps for the same:

  • Navigate to Setup -> General Parameters -> Folders

  • Click on the screens tab.

  • Search for “SOH” and change its screen size to 300.

  • Save the record.

  • Change the endpoint to EM and click on the validation.

  • The folder will be validated

Note: It can take 3 to 4 hours or max to complete the folder validation depending on your system configuration and usage

Last updated