This function is used to define the differentiation keys for each transaction. Upon WIP posting, it is therefore possible to aggregate or not aggregate according to the parameters indicated in this function.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

This function is composed of a single screen.

Entry screen

The entry screen contains two sections:

 The header that indicates the transaction types for which differentiation criteria are defined.

 The differentiation criteria:

The criteria (Key 1 to Key 5 fields) can be expressions that use constants, functions and operators, and fields from the WIPCOST table exclusively.

These differentiation criteria can be very diverse: For example:

By product: [F:MWI]ITMREF

By site: [F:MWI]MFGFCY

By date: format$("D:4Y2M",[F:MWI]TXNDAT)

By transaction type: num$([F:MWI]TXNTYP)

The user must therefore simply enter in Key 1 to Key 5 the criteria differentiating the entries, knowing that:

 Two different sets of criteria always correspond to two different accounting entries

 If all the criteria are equal, a single entry containing as many lines as necessary is created. These lines can be aggregated by same account, nature, tax code, and entry title with the automatic journal mechanism. If for example there is no differentiation by product, but the posting uses an account dependent on the product, there will be as many entry lines in the journal as there are different accounts dependent on the product. If the accounts are identical, but the analytical dimensions are not, an analytical distribution is automatically performed.

Block number 1

Transaction type (field TXNTYP)

WIP type.
Legislation (field LEG)
Company (field CPY)

Aggregation criteria

Key 1 (field KEY1)

Specify the grouping criterion.
Key 2 (field KEY2)
Key 3 (field KEY3)
Key 4 (field KEY4)
Key 5 (field KEY5)

Specific Buttons

Validation,

This button checks that each transaction type has a defined setup.
This control, which concerns all the movement or transaction types, is common to the three definition functions of the differentiation keys:

If the setup is incomplete for a transaction or movement type, regardless of the function, the missing elements are listed in the log file displayed after the control.
No log is produced if the setup is complete.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation