TRTVENCDE processing: Int Mod Result on Detail

ALISQHSOH: Loading the order header in order quote conversion

Use this entry point, during the transformation of a quote into an order, in order to take over after the fields in the order header screens are populated.

This allows you to populate fields that are specific to the header screens for order management and to the SORDER table.

It is called in the order management during the creation of an order upon picking a quote.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log.

Call context

This entry point is called during the creation of an order, if no line has been entered for the order and a quote or quote line has been picked. It is called after the order header screens are populated from the quote header.

Available variables and masks

The quote header file [F :SQH] is on line with the quote header that has been picked.

The quote detail file [F :SQD] is on line with the quote line that has been picked (if a complete quote has been picked, the 1^st line of this quote is on line.

The masks of the OBJect in the order management are on line. The header screens SOH0, SOH1, SOH2, SOH3 are loaded, as well as the address screens [M :ADB1] and [M :ADB2].

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…

The open tables are the tables opened by the order OBJect.

ALISQDSOH: Loading the order detail in order quote conversion

Use this entry point, during the transformation of a quote into an order, in order to take over after the fields in the detail screen are populated.

It is therefore possible, using this entry point, to load specific/custom fields in the detail screen for order management and in the SORDERP and SORDERQ tables.

It is called in the order management during the creation/modification of an order upon picking a quote.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log.

Call context

This entry point is called when creating or modifying an order and a quote or quote line is picked. It is called after the order detail screen is loaded from the quote detail line.

Available variables and masks

The quote header file [F :SQH] is on line with the quote header that has been picked.

The quote detail file [F :SQD] is on line with the quote line that has been picked.

The masks of the OBJect in the order management are on line. The header screens SOH0, SOH1, SOH2, SOH3 are loaded. SOH4 screen is loaded with the quote detail line.

[M :SOH4]NBLIG has been incremented. Nolign is loaded with the line index that has been inserted.

The NOL variable is loaded: NOL=nolign-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…

The open tables are the tables opened by the order OBJect.

ALIFMI: Loading the FMI field (Delivery method) on a order line

Use this entry point in order to take over after the initialization of the FMI field (Delivery method) of a sales order line.

This entry point makes it possible to modify the value of this field after its initialization.

It is called in the order management during a line entry. It is also called during the automatic generation of a sales order (within an inter-company context).

Context and operating mode

Transaction

There is no transaction in progress when the entry point is called from an order line entry.

There is a transaction in progress when the entry point is called during the automatic generation of a sales order from an inter-site/inter-company purchase order.

Log file

There is no log file open when the entry point is called from an order line entry.

There is an open log file when the entry point is called during the automatic generation of a sales order from an inter-site/inter-company purchase order.

Call context

This entry point called when creating or modifying an order, or when generating an order automatically from a purchase order within an inter-site or inter-company context. It is called after the standard initialization of the field.

It is called in the ALIFMI subprogram.

This subprogram is called during the entry of an order line:

. After entering the product reference.

. After modifying the shipment site of the line.

. After modifying the shipment site of the header, if the user has requested a transfer to the lines.

. When replacing an article with the Alternate product action.

. When generating an order line via the configurator.

. When generating a component order line.

This subprogram is called when generating a sales order from a purchase order, when the SOH4 screen is loaded from the POH2 screen.

Available variables and masks

The parameter of the ALIFMI subprogram are the following:

WITMREF: Product reference

WSTOFCY: Shipment site.

WFMI: Delivery method.

The ITMMASTER ITMSALES ITMFACILIT files are open and loaded with the product being ordered.

The masks of the object in the order management are on line. The header screens SOH0, SOH1, SOH2, SOH3 are loaded. The SOH4 screen is loaded with the lines of the order.

The WFMI variable is initialized in a standard way.  This variable needs to be modified in the EP in order to modify the value of the FMI field.

Open tables

In the table below, the significant content flag indicates that the content matches 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…

The open tables are the tables opened by the order object.

BEFREWSOH: Before writing sales order header

This entry point is called before the "Rewrite" instruction for each sales order header.

The SORDER [SOH] table buffer is loaded and can be modified with the usual care.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There can be an open log file (GTRACE test)

Call context

Call before writing a record in the SORDER table.

Available variables and masks

The SORDER file is open and loaded.

Table	Significant content	Table title
SORDER	Yes	Order headers

 

BEFREWSOP: Before writing sales order price detail line

This entry point is called before the "Rewrite" instruction for each sales order price detail line.

The SORDERP [SOP] table buffer is loaded and can be modified with the usual care.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There can be an open log file (GTRACE test)

Call context

Call before writing a record in the SORDERP table.

Available variables and masks

The SORDERP file is open and loaded.

Table	Significant content	Table title
SORDERP	Yes	Order line prices

 

BEFREWSOQ: Before writing sales order quantity detail line

This entry point is called before the "Rewrite" instruction for each sales order quantity detail line.

The SORDERQ [SOQ] table buffer is loaded and can be modified with the usual care.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There can be an open log file (GTRACE test)

Call context

Call before writing a record in the SORDERQ table.

Available variables and masks

The SORDERQ file is open and loaded.

Table	Significant content	Table title
SORDERQ	Yes	Quantity line orders

 

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There can be an open log file (GTRACE test)

Call context

Call before writing a record in the SORDERQ table.

Available variables and masks

The SORDERQ file is open and loaded.

Table	Significant content	Table title
SORDERQ	Yes	Quantity line orders