This function is used to create and update a setup kit.

A kit is a complete set, identified by a code, containing all the parameters and management rules and all the data used.

A kit is characterized by:

  • a product (for instance Sage X3)
  • a list of activity codes
  • a list of parameters
  • a list of setup elements.

It is necessary to have defined the principal options linked to the kit management:

  • the main management options defined by the activity codes (functionalities, localizations) which correspond to the optional management of some data in the base.

Upon activation of a kit in the folder record and construction of the X3 folder, the kit setup will replace the deliverable setup, according to the priority order defined in the deliverable. The objects from the kit will complete the objects that were potentially filtered by the deliverable. A kit may add recordings for an object, but it does not subtract recordings.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

A kit is defined by an alphanumeric code, to which a set of parameters grouped on different tabs is linked. A kit containing a ~ in its code is archived, and no modification is authorized on this recording in this case.

Tab General

Tab Options

This tab displays the activity codes of Functional and Localization type.

The only possible choice is 'By default'. If a code is subject to licensing in the deliverable but the kit has been bought by the customer, the value defined in the kit will be taken into account when creating the folder. The same applies to the 'not available' value of the deliverable.

Possibility to reload the activity codes of the current folder record: the default value for the activity codes is re-initialized by the value of the activity codes from the folder record (active or inactive).

Possibility to reload the activity codes of a deliverable of the same type: only the default value is replicated identically.

Possibility to reload the activity codes of a kit of the same type: the default value is replicated identically.

If new activity codes with a functional and/or localization type appear for an already defined kit, a message will appear in the kit, at the bottom of the grid. The 'Save' button becomes active in this case.

Tab Dimensions

This tab displays the activity codes of Sizing type.

Possibility to load the sizing activity codes of a deliverable of the same type:

  • If the code does not exist, it is added along with its value.
  • If the code exists, its value is overwritten.

Possibility to load the sizing activity codes of a kit of the same type:

  • If the code does not exist, it is added along with its value.
  • If the code exists, its value is overwritten.

Tab Parameter definition

This tab contains the list of the parameters that can be modified for this kit with respect to the
default value defined in the ledger or in a deliverable.

Possibility to load the parameters of a deliverable of the same type (no test on the legislation is carried out):

  • If the code does not exist, it is added along with its value.
  • If the code exists, its value is overwritten.

 Possibility to load the parameters of a kit of the same type:

  • If the code does not exist, it is added along with its value.
  • If the code exists, its value is overwritten.

 

Tab Setup elements

This tab displays the setup elements filtered for a kit.

They are associated with a data template of patch type, flagged 'Deliverable definition'.

To add lines in the first grid, use the right-click option 'Selection of a new template'.

To add lines in the second grid, use the right-click option 'Selection of the current template'.

The 'Invalid' column is only visible on setup elements that are no longer coherent, for instance in case of a data template that no longer exists. In that case, the 'Selection for the current template' option can not be accessed and the only possible choice is to delete the line concerned. It is also possible to select the option 'Invalid line deletion' in the tool bar. This option will delete, upon confirmation, all the lines with invalid setup elements.

Specific Buttons

Consistency check

This button is used to launch a consistency check on the kit.

This verification concerns the following elements:

  • Control on the existence of Functional or Localization activity codes
  • Control on the existence of new Functional or Localization activity codes
  • Control on the existence of Sizing activity codes
  • Control on the definition of the activity codes
  • Control on the existence of parameters
  • Control on the values entered in the parameters
  • Control on the model in the setup elements
  • Control on the consistency between the template and the table defined in the deliverable
  • Control on the uniqueness of the template-table combination

A log is generated upon launch.

 

Archiving

This button is used to archive the description of an active kit. If the user is not the supervisor of the kit, a message requires a confirmation.

Before the kit definition is archived, a coherence verification is launched. If the kit is correct, it is duplicated with the code = <kit codet>~V<version number>. This recording then becomes non-modifiable. Example: a kit named KITERP will be archived as KITERPV72 for version 1.7.2.

A log is generated upon launch.

 

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation