BEFORE_STW: Before the use of the data at the origin of the creation of STOWORK

This entry point is used to intervene in the setups, before the call to the process for the loading of the screen for the interface used to update the stocks (STOWORK) from the stock data in a document line.

It is thus possible in certain cases to authorize the issue of stock that does not exist even though the product does not permit negative stocks

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located at the start of the STKINT process.

It is called just before the switch, according to the data origin, to the call to the loading processing of the STOWORK interface screen.

The significant variables are:

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

[L]WNEGSTO           = Negative stock authorized

For instance     :

To authorize negative stock when normally it is prohibited for the product being processed, it is necessary to set [L]WNEGSTO = 2, and to prohibit WNEGSTO = 1.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

ENTW_STW: Transfer of data from STOENTW or STOENTM to STOWORK

This entry point is used to transfer the data from the receipt data storage screen (STOENTW or STOENTM) to the interface screen used to update stock (STOWORK).

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located in the CHARGE_ENT_STW label of the STKINT processing.

It is called at the end of the loading of the STOWORK interface screen from the storage screen of the input data (STOENTW or STOENTM)

It is used to load the interface screen with the information entered in the input screens in order to use them on stock update (input flows).

In this way it is possible to manage new fields in the stock movements (STOJOU table) or stock lines (STOCK table) created from this incoming flow.

The significant variables are:

LORI                           = Origin of the data (2 or 9 : STOENTW [M :ENTW]  /  4 : STOENTM [M :ENM])

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

The indexes to be used in the screen grids are :

NOL    = Index in STOWORK  [M :STW]

I           = Index for the receipt detail in STOENTW [M :ENTW] and STOENTM [M :ENM]

IL        = Index for the receipt detail in STOENTW [M :ENTW] and STOENTM [M :ENM]

Warning:

This entry point is only designed to manage new fields.

At no time should the standard contents of the STOWORK, STOENTW or STOENTM screens be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

SOW_STW: Transfer of data from STOSORW or STOSORM to STOWORK

This entry point is used to transfer the data from the issue data storage screen (STOSORW or STOSORM) to the interface screen used to update stock (STOWORK).

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located in the CHARGE_SOR_STW label of the STKINT process.

It is called at the end of the loading of the STOWORK interface screen from the issue data storage screen (STOSORW or STOSORM).

It is used to load the interface screen with the information entered in the issue screens in order to use them on stock update (issue cycle).

In this way it is possible to manage the new fields in the stock movements (STOJOU table) created from this issue cycle.

The significant variables are:

LORI                          = Origin of the data (3 : STOSORW [M :SOW]  /  5 : STOSORM [M :SOM])

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

The indexes to be used in the screen grids are :

NOL    = Index in STOWORK  [M :STW]

I           = Index in STOSORW [M :SOW] and STOSORM [M :SOM]

Warning:

This entry point is only designed to manage new fields.

At no time should the standard contents of the STOWORK, STOSORW or STOSORM screens be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

SGW_STW: Transfer of data from STOSRGW to STOWORK

This entry point is used to transfer data from the stock change data storage screen (STOCHGW) to the interface screen used to update stock (STOWORK).

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located in the ORI_STOCHGW label of the STKINT process.

It is called at the end of loading of the STOWORK interface screen from the stock change data storage screen (STOCHGW).

It is used to load the interface screen with the information entered in the issue stock change screens in order to use them on stock update.

In this way it is possible to manage the new fields in the stock movements (STOJOU table) created from this stock change cycle.

The significant variables are:

LORI                          = Origin of the data (7 : STOCHGW [M :SGW])

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

The indexes to be used in the screen grids are :

NOL    = Index in STOWORK  [M :STW]

I           = Index in STOCHGW [M :SGW]

Warning:

This entry point is only designed to manage new fields.

At no time should the standard contents of the STOWORK or  STOCHGW screens be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

CUD_STW : Transfer of data from CUNLISDET to STOWORK

This entry point is used to transfer data from the stock count detail record (CUNLISDET) to the interface screen used to update stock (STOWORK).

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located in the ORI_CUNLISDET label of the STKINT process.

It is called at the end of the loading of the STOWORK interface screen from the stock count detail record (CUNLISDET).

It is used to load the interface screen with the information entered and stored in the stock count detail in order to use it on stock update.

In this way it is possible to manage new fields in the stock movements (STOJOU table) created from this stock count cycle.

The significant variables are:

LORI                          = Origin of the data (8 : CUNLISDET [F :CUD])

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

The indexes to be used in the screen grids are :

NOL    = Index in STOWORK  [M :STW]

Warning:

This entry point is only designed to manage new fields.

The standard contents of the STOWORK screen should in no way be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

Screen	Significant content	Screen title
STOWORK	Yes	Stock interface

Table	Significant content	Table Title
CUNLISDET	Yes	Stock count detail
ITMMASTER	Yes	Products
ITMFACILIT	Yes	Products - Sites
STOJOU	No	Stock movements
STOCK	No	Stock
STOLOT	No	Lot
STOLOC	No	Location
TABLOCTYP	No	Location type

CHGPRIORD: Access to the order price coming from the original movement

This entry point is used to modify the order price of the stock movements to be generated when this price comes from the order price of an original movement.

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located at the end of the RECH_STJ_PRI label of the STKINT process.

It is called after the recovery of the order price of an original movement.

The order price is recovered in this way (when there is an original document), in the following update processes:

- Inter-site supplier receipt (and intra-company)

- Customer return

- Loan return

- Stock re-integration

- Supplier return

- Miscellaneous issue corresponding to the disassembly of an assembly

The significant variables are:

[M :STW]STOFCY    = Site

[M :STW]TRFFCY                 = Original site for the transfer (if inter-site supplier receipt)

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]VCRTYPORI    = Original document type (local menu 701)

[M :STW]VCRNUMORI       = Original document number

[M :STW]VCRLINORI          = Original document line

[M :STW]ITMREF     = Product

[M :STW]PRIORD(NOL)      = Order price coming from the original movement

[M :STW]PRIVAL(NOL)      = Valued price coming from the original movement

For instance     :

To add transport expenses (€ 25) to the order price of an inter-site receipt:

If  [M :STW]TRSTYP=3 [M:STW]PRIORD(NOL)+=25 Endif

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

Table	Significant content	Table Title
ITMMASTER	Yes	Products
ITMFACILIT	Yes	Products - Sites
STOJOU	No	Stock movements
STOCK	No	Stock
STOLOT	No	Lot
STOLOC	No	Location
TABLOCTYP	No	Location type

VALCUD: Before stock count line validation

Entry point before validation of a stock count line detail, CUNLISDET table.

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is no open log file.

Different call cases

After the reading of each valid record in the detail table: the [F :CUD] buffer is loaded, the master product, product-site and stock product are loaded.

Available variables and masks

Open tables

Tables of INV object

ALLVALCUD: Before rewrite of a stock count line on validation

Entry point before rewrite of a stock count detail line, CUNLISDET table, on validation.

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is no open log file.

Different call cases

Before rewrite of each record that can be validated in the detail table (with or without stock count variance). Buffer [F :CUD] is loaded as well as the master product and product-site.

In the event of a stock count variance on an existing stock count line, the STO buffer is loaded.

Available variables and masks

Open tables

Tables of INV object

STA_STW: Transfer of data from a STOALL record to the STOWORK record

This entry point is used to transfer data from a stock count detail record (STOALL) to the interface screen used to update stock (STOWORK).

Context and operating method

Transaction

There is one transaction in progress.

Log file                        

There is an open log file if GTRACE <> ‘’ .

Different call cases - Significant variables

This entry point is located in the CHARGE_STA_STW label for the STKINT process.

It is called at the end of loading of a STOALL allocation record into the STOWORK interface screen.

It is used to feed the interface screen with the information stored in the allocation records in order to use it on stock update.

The significant variables are:

LORI                          = Origin of the data (1 : STOALL [M :STA])

[M :STW]STOFCY    = Site

[M :STW]TRSTYP     = Movement type (local menu 704)

[M :STW]VCRTYP    = Document type (local menu 701) ( 34th for the reorder plan)

[M :STW]VCRNUM  = Document number

[M :STW]VCRLIN     = Document line

[M :STW]ITMREF     = Product

The indexes to be used in the screen grids are :

NOL    = Index in STOWORK  [M :STW]

Warning:

This entry point is only designed to manage new fields.

The standard contents of the STOWORK screen should in no way be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...).

QCR1_STW : Transfert de données d'un enregistrement QCR1 vers STOWORK

Contexte et mode de fonctionnement