Validity
- Description
- Functionality
- Rules/exceptions
- Validity of parts and parts lists
- Display Access options in list windows
- Related topics
- Technical documentation
Description
With this module the temporal validity of an object can be set. This time validity window is compared with the validity date specified in the system during each processing with this object. If an object is therefore "invalid", it is not displayed in lists by default, for example, or access to data of this object is no longer possible.
In the business environment, data in the manner described above are very often limited in time (e.g. customer no longer exists, product is no longer to be sold), but as a rule one piece of information is only replaced by another piece of information that is "newer" in time: the value added tax rate is increased from 1.1., a price table changes from a certain date, etc. In these cases it is possible to make a temporal concatenation of information or objects. This is made possible by the "Exchange objects" box. This box contains all the objects that are in a logical chronological order; depending on their validity, one object automatically replaces the other. It does not matter which object you are currently standing at, you will always receive the correct information at the right time.
Functionality
A validity period can be specified in three different ways:
- "Valid from": is indicated e.g. as"1.1.2015 -" with a "-" at the end to represent the open end of the period.
- "Valid until": is indicated e.g. as"- 31.12.2015" with a "-" at the beginning to represent the open start of the period.
- "Valid from-to": is indicated e.g. as"1.1.2015-31.1.2015" with a "-" between the start and end of the period. On the input mask this entry is made by clicking both boxes "Valid from" and "Valid to". If an object is valid on only one day (e.g. for currency tables), the date in the "Valid from" field is identical to the date in the "Valid to" field, e.g. "4.7.2015-4.7.2015".
In order to carry out a temporal concatenation of objects, the objects in question must be dragged and dropped into the "Exchange objects" box. Then press the OK button.
Rules/exceptions
The following list specifies a number of rules or exceptions for which the validity cannot be set, or what happens if the validity of an object is restricted:
| Object type | Validity cannot be set if... |
|---|---|
| Partner (company, person) | any partner function is still valid, unless the partner is replaced by a valid partner (exchange object) |
| Partner function (customer, vendor, employee, etc.) | open items are still available. If a partner no longer has any valid partner functions due to the invalid setting of partner functions, the system queries whether the partner should also be set invalid. If the answer to this question is "yes", the corresponding partner object is displayed in the validity mask for further processing after setting the invalidity for the last partner function |
| Part | any part roll is still valid, unless the part is replaced by a valid part (replacement object) Further information: see under Validity of parts and parts lists |
Validity of parts and parts lists
For different scenarios that lead to the invalidity of a part, it may be useful to define different procedures for each:
| Scenario | possible approach |
|---|---|
| part may generally no longer be used (e.g. due to a safety risk), a replacement for this part is available | The part is invalidated. The part is completely replaced with a replacement object, which leads to automatic changes in its parts rolls and in all parts lists. Production parts lists and postings remain unchanged. Possibly the part rolls are also set invalid and the "new" part rolls (of the "new" part) are stored there as their replacement objects If the "old" part is to remain available as long as it is in stock, the Parts KPI-Auditor can be used to automatically report this point in time and the part can then be manually invalidated. A description of the available options and how they can be implemented can be found under Parts Life Cycle. |
| Part runs out completely | The part and all its parts rolls are invalidated. If a part without an exchange object is invalidated, the existing valid BOM items in which the part is used are displayed. From this window, you can set the items to invalid or adjust the parts lists. See If the "old" part is to remain available as long as it is in stock, the Parts KPI-Auditor can be used to automatically report this point in time and the part can then be manually invalidated. A description of the available options and how they can be implemented can be found under Parts Life Cycle. |
| Part to be replaced by another part in certain parts lists | The respective parts list items are invalidated and a "new" parts list item - with the new part - is added. It is not possible to use the new bill of material item as an exchange object for the invalid item. |
| One parts list is to be replaced by another | The parts list is invalidated and the new parts list is specified as the replacement object. When exploding parts lists, the new parts list of the exchange object is now used. Already exploded production parts lists and postings remain unchanged. |
Input window
| Field | Description |
|---|---|
| Object | Object to which the validity data refer |
| Period | Time period in which the object is valid |
| Valid from | Date from which the object should be valid. Tomorrow's date (in relation to the session date) is offered by the system |
| Valid until | Date up to which the object should be valid. Yesterday's date (in relation to the session date) is offered by the system |
| Validity last changed | |
| date | Date of the last change of validity of the selected object |
| User | User who last changed the validity of the selected object. When saving via the OK button, this data is determined and saved on the object. |
| Exchange objects | Defines the objects to replace the original object in the invalid period. |
| button | Description |
|---|---|
| Insert | Insert exchange object |
| Remove | Remove replacement object |
| OK | Changes to the validity are saved. If no changes have been made, the button is locked. |
Display - access options in list windows
The following options are available to specify the validity of an object as a search criterion.
The radio buttons result in 4 possible combinations, which are described below. Only 1 radio button from each group can be selected at any one time, as they are conditional.
With exchange object & valid objects: (default setting)
All valid objects are displayed. If an object is invalid and has a valid exchange object, the exchange object is displayed. Invalid objects are not accessible here.
| Display in the list | Object 1 (original object) | Object 2 (exchange object) |
|---|---|---|
| Object 1 | valid | no |
| - | invalid | no |
| Object 2 | invalid | valid |
| - | invalid | invalid |
With exchange object & all objects:
Display of all valid objects and all invalid objects that do not have a valid exchange object. It is not possible to access the original object if it has a valid exchange object at the time of the search. In this case the exchange object is always found. For invalid objects with invalid exchange objects, the original object is displayed. If this setting is selected, a column is added to the list which shows the validity of the objects.
| Display in the list | Object 1 (original object) | Object 2 (exchange object) |
|---|---|---|
| Object 1 | valid | no |
| Object 1 | invalid | no |
| Object 2 | invalid | valid |
| Object 1 | invalid | invalid |
Without exchange object & valid objects:
The searched object must be valid at the time of the search to be found. If it is invalid and has a valid exchange object, the exchange object is ignored.
| Display in the list | Object 1 (original object) | Object 2 (exchange object) |
|---|---|---|
| Object 1 | valid | no |
| - | invalid | no |
| - | invalid | valid |
| - | invalid | invalid |
Without exchange object & all objects:
The searched object must be valid at the time of the search to be found. If it is invalid and has a valid exchange object, it will be ignored. If you are looking for an invalid object with a valid exchange object, the original invalid object will be displayed. If this setting is selected, 2 columns are added to the list. The column "validity" shows the validity of the objects, the other "exchange object" shows if invalid objects have valid exchange objects and shows their number. If no valid or no exchange object exists the column remains empty.
| Display in the list | Object 1(original object) | Object 2(exchange object) |
|---|---|---|
| Object 1 | valid | no |
| Object 1 | invalid | no |
| Object 1 | invalid | valid |
| Object 1 | invalid | invalid |
Examples:
Part 1 is valid and has no replacement object
| Option | Search result |
|---|---|
| With exchange object & valid parts | Part 1 |
| With exchange object & all parts | Part 1 |
| Without exchange object & valid parts | Part 1 |
| Without exchange object & all parts | Part 1 |
Part 1 is invalid and has no exchange object
| Option | Search result |
|---|---|
| With exchange object & valid parts | - |
| With exchange object & all parts | Part 1 |
| Without exchange object & valid parts | - |
| Without exchange object & all parts | Part 1 |
Part 1 is invalid and has valid exchange object Part 2
| Option | Search result |
|---|---|
| With exchange object & valid parts | Part 2 |
| With exchange object & all parts | Part 2 |
| Without exchange object & valid parts | - |
| Without exchange object & all parts | Part 1 |
Part1 is invalid and has invalid exchange object Part2
| Option | Search result |
|---|---|
| With exchange object & valid parts | - |
| With exchange object & all parts | Part 1 |
| Without exchange object & valid parts | - |
| Without exchange object & all parts | Part 1 |
Related topics
Technical documentation
Validity by date Editing module
Module name
validity.mod
Classes
-
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| EDIT_VALIDITY_BY_DATE | Object whose validity is to be edited | The validity of an object can be edited | |
| SHOW_VALIDITY_BY_DATE | Object whose validity is to be edited | The validity of an object can be viewed | |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
LIST_INVALID
Normally, only valid objects are added to an Object User Box. However, when this flag is set, invalid objects are also included and displayed.
LIST_ORIGIN
If an invalid object is inserted into a ListView and there is a valid exchange object, the valid exchange object is normally included. This flag prevents this so that only the valid original object is included. The interaction with LIST_INVALID is explained in more detail below.
Interaction LIST_INVALID with LIST_ORIGIN
Without flags only valid objects are included, in case of invalid objects the valid exchange object. LIST_INVALID allows to include invalid objects, LIST_ORIGIN includes only the original object, not the exchange object.
| Presentation | Flag |
|---|---|
| U U with A | no flag |
| U U with A U | LIST_INVALID |
| U | LIST_ORIGIN |
| U U U with A | LIST_ORIGIN & LIST_INVALID |
U / U ... original object valid / invalid
_ ... the underlined object is displayed
A ... valid exchange object
| Option | LIST_INVALID | LIST_ORIGIN |
|---|---|---|
| With exchange object & valid parts | no | no |
| With exchange object & all parts | yes | no |
| Without exchange object & valid parts | no | yes |
| Without exchange object & all parts | yes | yes |
;){kind=link}
;){kind=link}
;){kind=link}