SUBSDHB processing: Shipment management

SDHGENLIG: Generation of delivery lines in v130

This entry point is now deactivated in version 140.

 This entry point has been replaced by the SDHGENLIN entry point in the same processing.     

Warning, even if the purpose of the new entry point remains the same in v140 as in v130, its usage context as well as its functioning are completely different (the screens must be loaded in lieu of the delivery tables).      

This entry point is called during the delivery of an order via the "Delivery" button in order management.

It is used to take over just before the processing of each delivery detail line in order to remove this processing and to replace it or not with a specific processing.

It is also called during the execution of the 'Delivery' button in order management.

Context and operating mode

Transaction

There is one transaction in progress. This is the delivery creation transaction.

To cancel the transaction if a problem occurs, the GOK variable must be set to 0.

Log file

There is no open log file.

Call context

The entry point is located in the delivery creation transaction. The delivery header has been processed. The context is at the level of the detail line processing.

This entry point is called for each delivery line to create, just before the call to the DET_LIV label that carries out the delivery detail line processing.

It is used to prevent the execution of the DET_LIV label and to execute or not another label.

Available variables and masks

The record of the order header to deliver is loaded in [F:SOH].

The record of the delivery header to create is loaded in [F:SDH] but it is not yet created.

The WSOHNUM, WSOPLIN, WSOQSEQ variables contain the key to the order line to deliver.

The DET_LIV label to be substituted manages:

.        Read with lock the [F:SOQ] and [F:SOP] records for the order line to deliver.

.        Read the records corresponding to the product [F :SOQ]ITMREF ([F :ITM], [F :ITS] and [F :ITU])

.        Load the [F :SDD] class for the record of the delivery detail to create.

.        Create the record [F :SDD]

.        Update the delivered order line ([F:SOQ], [F :SOP]) and the associated files (the allocations, the WIP)

These are all the processings that will not be executed if the entry point is activated.

To activate the entry point, the WPOINT_DET_LIV variable has been created.

The GPE variable is initialized to 1 before calling the entry point and is tested when resuming the processing. The DET_LIV label is only executed if WPOINT_DET_LIV is set to 1.

To prevent the execution of the DET_LIV label, it is necessary to set the WPOINT_DET_LIV variable to 0.

If the DET_LIV label must be replaced, it is necessary to use its contents as template and integrate it in the entry point.

 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…). It is usually the case for the file that contains the header but not for the file that contain the lines…

SDHGENLIN: Generation of delivery lines in v140

In version 140, this entry point replaces ‘SDHGENLIG’ that was active in v130.

Warning, even if the purpose of this entry point remains the same in v140 as in v130, its usage context as well as its functioning are completely different (the screens must be loaded in lieu of the delivery tables).      

This entry point is called during the delivery of an order via the "Delivery" button in order management.

It is used to take over just before the processing of each delivery detail line in order to remove this processing and to replace it or not with a specific processing.

It is also called during the execution of the 'Delivery' button in order management.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

The delivery header has been processed. The context is at the level of the detail line processing.

This entry point is called for each delivery line to create, just before the call to the DET_LIV label that carries out the delivery detail line processing.

It is used to prevent the execution of the TRT_LIGCDE From SUBSDHC label and to execute or not another label.

Available variables and masks

The record of the order header to deliver is loaded in [F:SOH].

The two order detail records are in [F :SOQ] and [F :SOP].

The record for the header of the delivery to create is loaded in the [M:SDH0], [M :SDH1 and [M :SDH2] screen classes.

These are all the processings that will not be executed if the entry point is activated.

To activate the entry point, the WPOINT_DET_LIV variable has been created.

The GPE variable is initialized to 1 before calling the entry point and is tested when resuming the processing. The TRT_LIGCDE label is only executed if WPOINT_DET_LIV is set to 1.

To prevent the execution of the TRT_LIGCDE label, it is necessary to set the WPOINT_DET_LIV variable to 0.

The TRT_LIGCDE label to substitute loads the delivery line to create in the [M:SDH1] screen class.

As a consequence if this label must be replaced, it will be necessary to use its content as a template and to integrate it in the entry point.

 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…). It is usually the case for the file that contains the header but not for the file that contain the lines…

SDHFROMPRH: Sales site on delivery created by the button from pick tickets

When creating a delivery via the button in pick tickets, the site used to determine the company is the shipment site of the pick ticket.

This entry point is used to act on this functioning, and choose another site, therefore another company possibly.

This is not the standard case.

The specific will need to potentially support the linked impacts.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called when creating a delivery via the button in pick tickets.

At first, the GFCY global variable is initialized from the shipment site of the pick ticket ([F:PRH]STOFCY).

GFCY is then used to initialize other global variables such as GSOCIETE.

Available variables and masks

The ISDHFROMPRH whole local variable is declared and initialized to zero (zero).

If its value remains 0, the standard behavior is kept and GFCY is loaded with [F:PRH]STOFCY.

For any other value given to ISDHFROMPRH, it is considered that the value of GFCY was given in the entry point. This value will thus be kept.

The record of the pick ticket header is loaded in [F:PRH].

Example of modification of the GFCY value by the entry point:
       GFCY = <Site to use>
       ISDHFROMPRH = 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…). It is usually the case for the file that contains the header but not for the file that contain the lines…