Service options
Less than to read
Standard activity codes do not require any setup to be generated in Sage X3 Services.
Standard activity codes are generated automatically in the SYSTEM package if they are used in an API.
However, specific activity codes (starting with an X, Y or Z) must be linked to a package to be generated.
It is possible to link specific activity codes with the Activity code specific tab in the Package function (GESAPACK):
Note: Specific activity codes can’t be linked to a package whose owner is Sage. They must be linked to packages belonging to the partner who owns the respective activity code. As partners may have to manage a lot of activity codes, creating a dedicated Shared package is recommended to declare all the activity codes not directly related with its applicative packages.
Activity codes defined in X3, and assigned to a package for the specific ones, generate a service options in Sage X3 Services.
Once the node bindings validation is done and the package generation is executed, a file is created for each activity code in the lib/service-options directory of the package where the activity code has been defined. For example:
PJM is a standard activity code. Consequently, the service option is generated in the directory x3-system/lib/service-options.
On the nodes with an activity code configured, this line is generated to assign the activity to the node:
If you want to know how to add an activity code to a node or a package, please check the Node and Package documentation.