Use this entry point to take over in the processing for stock line extraction. Setting the GPE global variable to 0 is used to exclude a stock line being read.
There is no transaction in progress.
There is no open log file.
The ALLSCALSTO mask is open. It is not yet open.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
FACILITY | Yes | Site |
STOCK | Yes | Stock lines |
STOALL | No | Allocations |
STOLOT | Yes | Lots |
ITMMASTER | Yes | Product |
Use this entry point to take over after the printing of a weigh label in order to launch a specific processing, for example the printing of additional labels.
There is no transaction in progress.
There is no open log file.
The WEIGHING ([F:WGG]) file is open.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
FACILITY | Yes | Site |
WEIGHING | Yes | Weight |
Use this entry point to take over during the creation of recordings in the WEIGHING table (it is used, for example, to initialize specific fields). It is located just before the write instruction [WGG].
There is a transaction in progress.
If a problem arises, set the GOK variable to 0.
If there is a complete or partial weighing of a component, there is an open log file.
In other call contexts, there is no open log file.
The WEIGHING ([F:WGG]) file is open.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
WEIGHING | Yes | Weight |
This entry point is used to modify the value of the code managing exchanges between the weighing station and X3 if there is a weighing that generates a material tracking in order to replace this material tracking by a location change.
There is no transaction in progress.
There is no open log file.
The LCODE variable has a value between 27 and 31.
A value between 90 and 95 must be assigned to this code in order to perform an action (a location change, for instance) other than the update of the tracking along with the 'TRT_LCODE' entry point.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
WEIGHING | No | Weight |
This entry point is used to replace the material tracking by another action (change of location, for instance) by testing the LCODE variable in the MAJ_LCODE entry point.
There is one transaction in progress.
If a problem arises, set the GOK variable to 0.
If there is a complete or partial weighing of a component, there is an open log file.
In other call contexts, there is no open log file.
This entry point is called if the LCODE variable is different than 27, 28, 29, 30 or 31.
In that case, the LCODE value set in the MAJ_LCODE entry point must be tested in order to carry out the desired action.
Example for a change of location:
# Example of a sequence to write in the EP in order to
# change a location after a weighing
Local Decimal LQTY, LSHT
Local Integer LNBR, LNBJ, LRET
Raz [M:STW]
[M:STW]STOFCY = GSCA1MFGFCY
[M:STW]TRSTYP = 7 :# Change of location
[M:STW]ITMREF = F_ITMREF
[M:STW]LOCENT = Target location (must be known at this level)
[M:STW]CUR = GLOCALDEV
[M:STW]IPTDAT = date$
[M:STW]PRIORDH = 0
[M:STW]PIOQTY = 3
[M:STW]VCRTYP = 10 : # WO
[M:STW]VCRNUM = F_MFGNUM
[M:STW]VCRLIN = F_MFGLIN
[M:STW]SEQ = F_SEQ
[M:STW]STOCOU(0) = F_STOCOU
LQTY = F_WEIWEI_US
Call ALISTOWORK(11,0,LQTY,LSHT,LNBR,LNBJ,LRET) From STKINT
# Stock update
If LRET=0 Call MAJ_STOCK From STKMAJ Endif
If LRET<>0 | GOK<1 GOK=0 Endif
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
WEIGHING | Yes | Weight |
Use this entry point to take over during the creation of recordings in the MFGHEADTRK table (it is used, for example, to initialize specific fields). It is located just before the write [MTK] instruction.
There is one transaction in progress.
There is an open log file.
The MFGHEADTRK ([F:MTK]) file is open.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
WEIGHING | Yes | Weight |
MFGMATTRK | Yes | Production tracking - Material |
Use this entry point to take over when retrieving WO components. It is used to set additional filters in order to select components.
There is no transaction in progress.
There is no open log file.
The MFGMAT ([F:MFM]) file is open and loaded. The GSCA1ITMREF global variable is valued with the component to weigh if a component has been specified in the weighing home page.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGITM | Yes | Work orders - header |
MFGMAT | Yes | Work orders - components |
Use this entry point to take over after the WO components have been filtered. It is used to replace for each component the operation number by a phase number added in specific.
There is no transaction in progress.
There is no open log file.
The MFGMAT ([F:MFM]) file is open and loaded. The WNUMOPE local variable is valuated by default with the [F:MFM]BOMOPE routing operation number. The user can then assign the desired specific value.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGITM | Yes | Work orders - header |
MFGMAT | Yes | Work orders - components |
Use this entry point to take over just before retrieving the content of the material allocation table when constituting the list of lots eligible for a component weighing. In order to avoid the retrieving of an allocation, for example because the location of the allocation has already been changed (specific case), this entry point is used to take over just before taking it into acocunt in the ALLSCALSTO fields.
There is no transaction in progress.
There is no open log file.
The ALLSCALSTO [M:ASSW] mask is loaded with the content of the STOCK table.
The quantity presented in [M:ASSW] have been decreased of the allocated quantity.
Therefore,
[M:ASSW]DISPONIBLE (nolign-1) = [F:STO]QTYSTU - [F:STO]CUMALLQTY
[M:ASSW]ALLOUE (nolign-1) = 0
The [F:STA] table is loaded when calling the entry point. The allocations are added to the fields mentioned in standard during the read of the table.
This entry point has been designed to take over inside the allocation read loop. It is used to short-circuit the update of the ALLSCALSTO mask with the content of STOALL. To that purpose, set the GPE global variable to 0.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
FACILITY | Yes | Site |
STOCK | Yes | Stock lines |
STOALL | Yes | Allocations |
STOLOT | Yes | Lots |
ITMMASTER | Yes | Product |
Use this entry point to take over after the WO components have been filtered. It is used to replace for each component the remaining quantity (WQTYRESTAN) with a specific quantity. This data is then sent to the weigh station in order to perform the material weighing.
There is no transaction in progress.
There is no open log file.
The MFGMAT ([F:MFM]) file is open and loaded. The WQTYRESTAN local variable is valuated by default with the requirement quantity – consumed quantity.
To that purpose, the CAL_POIDS() sub-program is used:
Call CAL_POIDS ([F:ITM]ITMREF,[F:MFM]RETQTY-[F:MFM]USEQTY,WQTYRESTAN) from SCALEXCHAN
The [F:MFM]RETQTY and [F:MFM]USEQTY quantities are expressed in STK. The STK quantity is converted in weight unit of the [F:ITM]ITMWEI product and rounded according to the decimal number of the weight unit of the [F:ITM]WEU product before being assigned to the WQTYRESTAN local variable. WQTYRESTAN is then sent to the weigh station.
The specific value desired must just be assined to this variable.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGITM | Yes | Work orders - header |
MFGMAT | Yes | Work orders - components |
Use this entry point to take over after the WO components have been filtered. It is used to replace for each component the standard tolerance percentages with specific tolerance percentages.
There is no transaction in progress.
There is no open log file.
The ITMFACILIT ([F:ITF]) file is open and loaded. The WTOLPOS and WTOLNEG local variables are valued by default with the tolerance percentage of the [F:BOD]ITMTOLPOS /[F:BOD]ITMTOLNEG BOM. The user can then assign the specific value desired.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGITM | Yes | Work orders - header |
MFGMAT | Yes | Work orders - components |
Use this entry point to take over before retrieving the standard containers linked to the SHI record of the current component. It is used to replace the SHI record of the component with a specific SHI record.
There is no transaction in progress.
There is no open log file.
The WISM local variable is loaded by default with the SHI record of the component to weigh. The user can then assign the desired specific value.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
MFGMAT | Yes | Work orders - components |