Scripting Variables Based on Business Objects

Show/Hide All

This topic applies only to modules other than Job Cost, Material Requirements Planning, Payroll, TimeCard and Work Order.

In these object-oriented modules, the variables that are passed into and returned from a script are based on the business objects available to the panel.

In External Link Definition, you can view variables that will be passed to the script. You can also access the MS Script Variable Selection window to select the variables. Variables are composed of a business object name ending in _bus and then appended with a column name from the business object main table. Customizer also appends a dollar sign ($) to the end of string variables to distinguish them from numeric variables; however, VBScript and JScript do not use the dollar sign in scripts.

Example of a business object variable

The customer number column from the main Sales Order Entry business class is:

SO_SalesOrder_Bus_CustomerNo$

If you have scripts for a module that has become an object-oriented module, these scripts must now use the business object variables. User-defined fields (UDFs) are also named differently for these modules, so script references to UDFs must be changed.

Example of UDF Names

A UDF that was previously named ML_UDF_SOD_WEIGHT would now be named UDF_WEIGHT using the new object-oriented naming standards.

Example of variable changes within a module

The following table illustrates the differences between variables in the Sales Order Entry Header tab panel before and after the module was redesigned in version 4.0 with an object-oriented architecture. Before version 4.0, the Sales Order module variables were based on control names in the library. After version 4.0, the Sales Order module variables were based on the business objects available to the panel.

Before Version 4.0

After Version 4.0

ML_CUST$

SO_SalesOrder_bus_CustomerNo$

ML_ORDER_DATE$

SO_SalesOrder_bus_OrderDate$

CB_PRNT_PKSHTS$

SO_SalesOrder_bus_PrintPickingSheets$

ML_TERMS$

SO_SalesOrder_bus_TermsCode$

For more information, see:

Scripting Variables

Scripting Variables Based on Control Names

Before Version 4.0	After Version 4.0
ML_CUST$	SO_SalesOrder_bus_CustomerNo$
ML_ORDER_DATE$	SO_SalesOrder_bus_OrderDate$
CB_PRNT_PKSHTS$	SO_SalesOrder_bus_PrintPickingSheets$
ML_TERMS$	SO_SalesOrder_bus_TermsCode$