REGSTJAUTO: Used to adjust pending movements with a lot that has not been entere

This entry point is used to automatically adjust pending movements for which the lot has not been entered.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Different call cases - Significant variables

This entry point is called during the adjustment of a pending movement, just before the filters are loaded on the stocks that will adjust this movement.

To make the lot value optional in the movement to be adjusted, it is necessary to set the WLOTOPT local variable as follows:   WLOTOPT = 1.

A pending movement involving a product managed by lot can thus be adjusted even if the lot has not been entered.

The significant masks are :

STKSHTSEL [SHTS](with the PNOL index): Pending movements to be adjusted

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

STOCK

No

Stock

ITMMASTER

Yes

Product

ITMFACILIT

Yes

Product-site

 

MODTRACE: Used to replace the standard log file with another

This entry point is used to replace the standard log file on adjustment of the shortages.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Different call cases - Significant variables

This entry point is called on adjustment of a shortage, right after each adjustment attempt.

To replace the standard log file with another (that should be written in the entry point), the GPE variable needs to be set as follows:   GPE = 1

The local variable WACT is used to identify the context that matches the log file written in standard. The possible values are:

WACT = "A": Allocation of the shortage

WACT = "D": Deletion of the shortage

WACT = "M": Decrease of the shortage

WACT = "S": Result of the allocation attempt when there is still some shortage. 

WACT = "F": End of a line adjustment ('The adjustment has ended correctly')

For example, if you do not want to trace the adjustment attempts that did not end correctly, you need to test [M:ALP]ALLQTY.

If [M:ALP]ALLQTY=0: GPE = 1: Endif

The significant masks are:

ALLPAR [ALP]: Parameters of the allocation ([M:ALP]ALLQTY contains the quantity that has been allocated) 

 STKSHTSEL [SHTS] (with the PNOL index): Pending movements to be adjusted

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

STOCK

No

Stock

STOALL 

No

Allocation

ITMMASTER

Yes

Product

ITMFACILIT

Yes

Product-site

 

NO_REAJUST: Used to prevent the readjustment of the allocated quantity in whole

This entry point is used to avoid readjusting the allocated quantity in whole sales unit.

Context and operating method

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Different call cases - Significant variables

This entry point is called during the automatic adjustment of an allocation

for the types: [M:ALP]VCRTYP,2,3,4,5: orders, preparations, deliveries, invoices.

To avoid the adjustment, you need to set the GPE variable as follows:   GPE = 1

 The significant masks are :

ALLPAR [ALP]: Parameters of the allocation ([M:ALP]ALLQTY contains the quantity that has been allocated) 

CRITSTASPE: Used to add filters during the adjustment

This entry point is used to add filters on the STOALL table when adjusting stock shortages. 

Context and operating method

Transaction

There is no transaction in process.

Log file

There is an open log file.

Different call cases - Significant variables

This entry point is called when adjusting stock shortages. 

The entry point is set just before the reading of the STOALL table.

The filter can be applied with the elements of the STKSHTSEL mask or STOALL table.

A heading of 250 alphanumeric characters is available: CRITSTA to define the filter