Lot modification
This function is used to manage the parameterization of the screen and functional personalization for the Changes to lot characteristics, Mass changes to lot characteristics and Renumbering / Mixing of lots.
At least one standard transaction for each of these three functions is provided with the installation of the software. They can either be modified or deleted with this function, which is also used to create new ones.
It is possible to parameterize several different transactions for each of the functionalities to cover. Each transaction, identified by a code and a text description, appears in a selection window when calling the functions concerned.
Prerequisite
Refer to documentation Implementation
Screen management
Header
The parameterization of the Lot modification transactions contains a header for the transaction code, potentially an access code for the transaction and a status (active/inactive) and two tabs.
Access code: Transactions can be filtered according to the operators, thanks to the introduction of this access code: if the field is entered, only the users who have this access code in their profiles will be able to access the transaction.
If several transactions are parameterized for a function, and the user only has access to one of them because of the access codes, the selection window is no longer proposed: the access is by direct entry.
Active: This field is used to activate or deactivate a transaction. The inactive transactions are not presented in the transaction selection window.
Lot modification transaction
Transaction (field SRTNUM) |
Transaction code. |
Description (field DESAXX) |
Transaction description. |
Active (field ENAFLG) |
Use this field to activate or deactivate a transaction. |
Access code (field ACSCOD) |
This access code is used to restrict access to data by user or group of users. |
Group (field GFY) |
Tab General
Use section:It is necessary in the first instance to specify if the transaction currently being parameterized will be a Modification of lot characteristics or of Renumbering/Lot mixing function. A single transaction cannot cover both roles at the same time.
Modification of Lot characteristics: this function is used for a lot and if necessary a given sub-lot to modify the lot title (if the management of titles is foreseen for the product), the expiry lead-time and the expiry date (if expiry management is planned for the product) and the supplementary lot information (if this information is managed for product). A "Modification of lot characteristics " transaction can be used for both the "change of characteristics " that makes it possible to intervene in a single lot/sub-lot at a time, and for the "mass change" function that makes it possible to modify a selection of lots/sub-lots.
Renumbering and Mixing : this function is used either to allocate a new lot or sub-lot code to all or part of an existing lot (this is renumbering) or the mixing of all or part of the lot/sub-lot with an existing lot/sub-lot (this is mixing).
Function section: in the case where the role chosen is Renumbering/Mixing, it is possible to specify whether the transaction can only be used for renumbering, for mixing or for both at the same time. This section is inactive if the transaction is planned for "lot characteristic modification".
"Authorisations" block: It is possible to specify at the level of a transaction planned to be used for mixing or renumbering which stock statuses it is possible to manipulate for the original lot as well as the target lot (when this exists: it is mixing).
Management block:this section is used to plan the entry on a lot characteristics change or renumbering/mixing note of a project code, a movement description (that will be carried by all the movements arising from these notes) and a group code.
Movement group: This is statistical information that will be recorded in the stock journal at the moment of saving the movements for the lot modification. This movement group comes from the miscellaneous table N°9. The value given in the transaction parameterization corresponds to a default value that can/cannot be visualized and/or modified according to the transaction parameterization (entry field, display, hidden).
Entry mode section: (only active for a Renumber/Mixing type transaction) within the framework of a transaction planned to be used for lot renumbering, it is possible to plan whether the entry uses a new lot code or not. If it is an unplanned entry, the new lot code will be automatically allocated via the sequence number counter for lot defined for the product. The target lot must be entered if lot mixing is planned in the transaction since it is necessary to choose from amongst the existing lots the lot resulting from the mixing.
Use
field CHANGECOD |
Lot modification transaction type. |
Functions
Renumbering a lot (field RENUMCOD) |
This flag is used to activate/de-activate the partial or complete renumbering of an existing lot. |
Lot mixing (field MIXCOD) |
This flag is used to activate/de-activate the partial or thorough mixing of 2 existing lots. (lot A is partially or completely integrated into lot B) |
Lot characteristics (field LOTCOD1) |
Lot versions (field ECCCOD) |
Authorization
Authorized statuses (field AUZSTA) |
Indicate which statuses are authorized in this stock movement type. |
Authorized substatuses (field AUZSST) |
Specify here which sub-statuses are authorized for this stock movement type. To do so, click on Authorized statuses from the Actions icon. Entry is possible in grid mode by selecting the grids from the stock status table or by entering a sub-status template with generic characters (*,?,#,!). On validating this grid, a control is carried out to keep only those corresponding to the chosen authorized statuses. If this field is left empty, it will be automatically populated with the sub-status templates corresponding to the authorized statuses. |
Management
Project (field PJTCOD) |
This parameter is used to define, for this entry transaction, whether the project field must be:
|
Stock movement group (field TRSFAMCOD) |
The Movement group is a statistical piece of information recorded in the stock journal when saving the receipt movements. This movement group is contained in the miscellaneous table no. 9. Use this parameter to define if the movement group code must be:
|
Default value (field TRSFAMDEF) |
This parameter is used to define, for this transaction, a default transaction group code. |
Movement description (field MVTDESCOD) |
Setup used to define, for this entry transaction, if the movement description that will be written in the stock journal must be:
|
Entry
Lot (field LOTCOD) |
Parameter used to define, for this entry transaction, if the destination lot number field must be: hidden displayed entered. |
Sublot (field SLOCOD) |
Parameter used to define, for this entry transaction, whether the product Sub-lot number must be:
|
Tab Detail
Entry mode section: (only active for a transaction of the type Lot characteristics change) used to choose which stock information can be modified (title, expiry, user sections) for a given transaction
Entry
Supplier lot (field BPSLOTCOD) |
Potency (field POTCOD) |
Parameter used to define, for this entry transaction, if the title must be: hidden displayed entered. |
Expiration (field PERCOD) |
Parameter used to define, for this entry transaction, if the expiry date must be: hidden displayed entered. |
field SRUB1FLG |
This setup is used to specify for each of the user free fields 1-2-3-4 of the Lot addition entry window whether these fields must be entered. These fields are used to associate additional information to a lot. |
field SRUB2FLG |
This setup is used to specify for each of the user free fields 1-2-3-4 of the Lot addition entry window whether these fields must be entered. These fields are used to associate additional information to a lot. |
field SRUB3FLG |
This setup is used to specify for each of the user free fields 1-2-3-4 of the Lot addition entry window whether these fields must be entered. These fields are used to associate additional information to a lot. |
field SRUB4FLG |
This setup is used to specify for each of the user free fields 1-2-3-4 of the Lot addition entry window whether these fields must be entered. These fields are used to associate additional information to a lot. |
Printing
Printing (field PRNCOD1) |
Parameter used to define, for this entry transaction, whether the print of the document is planned or not. Note: In the lot characteristics modification function, the printing of labels is available only if a lot title is modified. |
field PRNSCR1 |
Specify, for this entry transaction, if the field must be present in:
|
No. prints (field PRNNBFLG1) |
Parameter used to define, for this entry transaction, if the number of documents to be printed can be entered or not. |
field PRNNBSCR1 |
Specify, for this entry transaction, if the field must be present in:
|
Display
Serial number (field SERCOD) |
Parameter used to define, for this entry transaction, whether the first product serial number for receipt to stock must be:
|
field SERSCR |
Specify, for this entry transaction, if the field must be present in:
|
Identifier 1 (field IDECOD1) |
The identifiers correspond to pieces of free information each used to identify a stock line. This parameter used to define, for this entry transaction, whether the analytical dimension must be:
|
field IDESCR1 |
Specify, for this entry transaction, if the field must be present in:
|
Identifier 2 (field IDECOD2) |
This parameter is used to define, for this entry transaction, whether the identifier 2 in the screen must be:
|
field IDESCR2 |
Reports
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.