PACKDETMAJ: Update of specific/custom files after the update of a packaging line

This entry point is called in the load preparation management to allow the update of specific/custom tables.

It is called in the load preparation management process FUNPKP.

It is called during the creation of a load preparation, on the entry of each parcel line. It is used to insert additional logic before each entry of the parcel line.

Context and operating mode

Transaction

There is a transaction in process (entry or deletion of the load preparation transaction). The GOK variable is used and tested. It is initialized to 1. It can be set to 0 if the transaction should be aborted.

Log file

There is no open log file

Different call cases

This entry point is called from each process allowing to generate/cancel parcels:

.         Load preparation button from the shipment management

.         Load preparation function from the stock management

It is called at two levels:

.         During the creation of packaging detail line:

In the generation loop of the packaging detail. nolign-1. The [F:SPD] buffer is loaded.  One is positioned just before writing the [F:SPD] recording.

The header of the package is not yet created. It will not be until after the creation of all the details.

It should be noted that the delivery header buffer [F :SDH]  or preparation header [F:PRH] is on line. .         During the cancellation of a load preparation. This cancellation is carried out at two levels:

.           When the cancellation button is used.

The delete instruction has just been carried out on the SPACK ([F :SPH]) and SPACKD ([F :SPD]) files for the current shipment. Therefore the complete deletion of the load preparation has been carried out.

.          When using the Save button, just before the generation of the load preparation.

The delete instruction has just been carried out on the SPACK ([F :SPH]) and SPACKD ([F :SPD]) files for the current shipment or preparation. Therefore the complete deletion of the load preparation, if it exists already, has been carried out.

Located just before the detailed packaging generation loop. To differentiate the two call levels (cancellation of the load preparation, saving a parcel line), it is necessary to use the WPOINT_CODTRT variable. It is set to "C" for creation and to "A" for cancellation. 

Global variable GVCRTYP is used to know whether this is a shipment or preparation load preparation.

                GVCRTYP  = 3: Preparation

                GVCRTYP  = 4: Shipment  

CALWCALNBCOL: Verifying if automatic packing is possible

This entry point is called in the load preparation management to allow, if possible, the automatic packing.

It is called in the load preparation management process FUNPKP.

It is called during the packing creation, when loading the table.

Context and operating method

Transaction

There is no transaction in progress.

Log file

There is no open log file

Different call cases

This entry point is called when loading the table.

It is used, for a document line with a outer packing code and capacity entered, a number of detail > 1, to check the possibility to carry out an automatic packing.

This is the WCALNBCOL variable that specifies if an automatic packing can be possible.

                        WCALNBCOL set to 1 means that the automatic packing is not possible.

                        WCALNBCOL set to 0 means that the automatic packing is possible.

In standard mode, the variable WCALNBCOL is equal to 0 if the quantity of all the detail of a document line corresponds to the outer packaging capacity. 

The EP is used to carry out a different verification.

The GPE variable set to 1 is used to omit taking into account the standard verification

Global variable GVCRTYP is used to know whether this is a shipment or preparation load preparation.

                GVCRTYP  = 3: Preparation

                GVCRTYP  = 4: Shipment  

  The PKP1 mask is available

  If GVCRTYP = 4  the tables STOJOU[STJ] , SDELIVERY[SDH] SDELIVERYD[SDD] STOALL[STA )

                             are available

  If GVCRTYP  = 3  the tables STOPREH[PRH] STOPRED[PRE] STOALL[STA )

                             are available

 

BEFWRISPH: Before creation of parcel header SPACK table

This entry point is called in the post-packing management before writing to the SPACK table (parcel shipment).

It is called in the post-packing management process FUNPKP.

It is called during the load preparation recording, at the time the parcel header recording is created (SPACK table)

Context and operating method

Transaction

There is a transaction in process (entry or deletion of the load preparation transaction). The GOK variable is used and tested. It is initialized to 1. It can be set to 0 if the transaction should be aborted.

Log file

There is no open log file

Different call cases

This entry point is called from each process allowing to generate/cancel parcels:

.         Load preparation button from the shipment management

.         Declarative load preparation function from the stock management

We are in the process of parcel headers and lines creation. 

 All the parcel details lines are created.

It should be noted that the delivery header buffer [F :SDH]  or preparation header [F:PRH] is on line. .   

Global variable GVCRTYP is used to know whether this is a shipment or preparation load preparation.

                GVCRTYP  = 3: Preparation

                GVCRTYP  = 4: Shipment  

AFF_PKP1 : Before PKP1 screen's refresh instructions

This entry point is called in the post-packing management, before the PKP1 screen's refresh instructions

It is called in the post-packing management process FUNPKP.

Context and operating method

Transaction

There is no transaction in progress 

 The GPE variable is used and tested. It is initialized to 0. It can be set to 1 if you want to deactivate the PKP1 screen's refresh. It is placed in the label CHARGE_PKP1 of FUNPKP processing

Log file

There is no open log file

Different call cases

This entry point is called every time PKP1 screen is refreshed.

That is to say in the actions: DEBUT, ENR, SUP, ABA, SUI, PRE, LAS, FIR (possibility to test if ACTION header exists and to test its content if the user wants to set conditions for the refresh) 

and right-click "Suppress parcel" starting from a line in the table (in this case, ACTION header does not exist) 

PKP1 screen is loaded.

ENR_COLISAGE: Before the parcels standard validation processing.

 This entry point is called in the post-packing management, before the parcels standard validation processing. It is used to specifically process this validation.

It is called in the post-packing management process FUNPKP.

Context and operating method

Transaction

There is no transaction in progress 

 The GPE variable is used and tested. It is initialized to 0. It can be set to 1 if you want to deactivate the parcels standard validation processing. It is placed in the label ENR_COLISAGE of FUNPKP processing

Log file

There is no open log file

Different call cases

This entry point is called every time the button "Save" is used.

Label ENR_COLISAGE is used for each table line in PKP1 screen with the headers MODFLG set to 2 and PACSEQ <>0:   

                             the loading of PKP2 screen   (label CHARGE_PKP2 processing TRTPKP2)

                              calculation of parcel numbers, SSCC code and writing of parcel details (label                                ECRCOL_PKP2 processing FUNPKP)

                              entering parcel header (label ENTETE_COLIS processing FUNPKP)

When all the lines have been processed, the original document's update is executed (label ENTETE_COLIS of processing FUNPKP

Following ENR-COLISAGE label, the labels printing is executed. Setting the GDOCFLG variable to 0 allows to deactivate it if necessary. (This variable is initiated by the value of the "Automatic printing" header for the transaction.