TRTPRICE processing: Load Reason Description

ALIPLK: To modify the contents of the link tables PPRICLINK and SPRICLINK

This entry point, found in the TRTPRICE processing (price search for sales or purchases), generates an "ALIPLK" action.

This action is used to modify the [F] classes in the SPRICLINK or PPRICLINK tables that are used for example to set up the price search criteria.

Context and operating mode

Transaction

There is a transaction in progress only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Log file

There is a log file only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Different call cases

The call is made:

-          in purchases : when managing purchase requests, the buyer plan, orders, delivery requests, and workbenches (reorder plan and global planning)

-          in sales : when managing quotes, orders, deliveries and invoices

Available variables and masks

The following variables are loaded when calling the "ALIPLK" action.

TRAIT

Processing code that launched the price search:

- PSH = purchase requests

- PSM = planning workbenches (automatic management of purchase requests)

- POH = purchase orders

- POI = buyer plan

- POD = purchase delivery requests

- POC = purchase open order contracts

- SQH = quotes

- SOH = sales orders

- SOI = open sales orders

- SDH = deliveries

- SIH = sales invoices

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

AVRECHTAR: Deactivating the price lists before the search

This entry point, found in the TRTPRICE processing (price search for sales or purchases), generates an "AVRECHTAR" action.

The purpose of this action is to give the possibility to deactivate certain price list codes before starting the actual search.

Context and operating mode

Transaction

There is a transaction in progress only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Log file

There is a log file only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Different call cases

The call is made:

-          in purchases : when managing purchase requests, the buyer plan, orders, delivery requests, and workbenches (reorder plan and global planning)

-          in sales : when managing quotes, orders, deliveries and invoices

Available variables and masks

The following variables are loaded when calling the "AVRECHTAR" action.

MODULE

Code for the module concerned (5 = sales module. 6 = purchase module)

PLITYP

Searched for price list type (1 = standard price list,  2 = grouped price list,  3 = prohibited,  4 = component)

TRAIT

Processing code that launched the price search:

- PSH = purchase requests

- PSM = planning workbenches (automatic management of purchase requests)

- POH = purchase orders

- POI = buyer plan

- POD = purchase delivery requests

- SQH = quotes

- SOH = sales orders

- SOI = open sales orders

- SDH = deliveries

- SIH = sales invoices

GPLI(0 .. 99)

Table for the price list codes selected for a price search.

GPIO(0 .. 99)

Price list code priorities table.

GPLINBR

Number of price list codes selected (= number of items in the tables).

The variables given above must not be modified.

The following table is loaded and should be modified in order to deactivate one or more price list codes.

GPLITYP(0 .. 99)

Table for the price list types selected.

It is necessary to enter the value 9 in the index corresponding to the price list code that is to be deactivated.

For example: If the "XXX" price code is present, it must be deactivated.

- If find("XXX",GPLI(0..GPLINBR-1))

- GPLITYP(find("XXX",GPLI(0..GPLINBR-1))-1) = 9

- Endif

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

Miscellaneous remarks

The table for the price list types GPLITYP (0 .. 99) is automatically recovered after the price search.

CPLTARIF: Intervene on the data for each price list code, during a search

This entry point, found in the TRTPRICE processing (price search for sales or purchases), generates an "CPLTARIF" action.

This action is used to complete or modify the data recovered by the search in the price list code records. There is a call to the entry point via the inquired active price list code.  

Context and operating mode

Transaction

There is a transaction in progress only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Log file

There is a log file only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Different call cases

The call is made:

-          in purchases : when managing purchase requests, the buyer plan, orders, delivery requests, and workbenches (reorder plan and global planning)

-          in sales : when managing quotes, orders, deliveries and invoices

Available variables and masks

The following variables are loaded during the call.

MODULE

Code for the module concerned (5 = sales module. 6 = purchase module)

PLITYP

Searched for price list type (1 = standard price list,  2 = grouped price list,  3 = prohibited,  4 = component)

TRAIT

Processing code that launched the price search:

- PSH = purchase requests

- PSM = planning workbenches (automatic management of purchase requests)

- POH = purchase orders

- POI = buyer plan

- POD = purchase delivery requests

- SQH = quotes

- SOH = sales orders

- SOI = open sales orders

- SDH = deliveries

- SIH = sales invoices

I

Iteration variable for the dimensioned variables GPLI  GPIO  GPLITYP  GPLISEA. It is imperative that this variable value is not modified:

GPLI (I)                   Active price list code that has just been processed in the search loop.

GPIO (I)                  Active price list priorities.

GPLITYP (I)           Price list type.

GPLISEA (I)           Search loop code.

The following variables can loaded by the price searches

MONTANT (0..10)  Value (can be a price, an amount, a percentage or a coefficient)

MOTIF (0..10)         Reason for the price list that gave the value

PRIORITE (0..10)   Priority for the price list that gave the value (is used to manage price lists with the same priority)

PLI (0..10)               Price list code that gave the value

PLICRD (0..10)       Price list record

PLILIN (0..10)         Price list record line number

For purchasing, the indexes correspond to: 

0 = gross unit price  

1 to 9 = Charges/discounts 1 to 9  

10 = lead-time in days for the receipt date calculation

For sales, the indexes correspond to: 

0 = gross unit price

1 to 9 = Charges/discounts 1 to 9  

10 = coefficient for the sales representative commission calculation

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

TARIFACH: Intervening on the values found by the search in Purchasing

This entry point, located in the TRTPRICE and TRTACHTAR1 processings (purchase price list in creation of purchase requests, orders, contracts or delivery requests, generates a "TARIFACH" action.

The purpose of this action is to give the possibility to act on the values found via the price search.

Context and operating mode

Transaction

There is a transaction in progress only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Log file

There is a log file only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Different call cases

The call is made:

- in price list simulation upon activation of the "Apply" button.

- when managing purchase requests, the buyer plan, orders, contracts, delivery requests, and workbenches (reorder plan and global planning)

Available variables and masks

The following variables are loaded when calling the "TARIFACH" action.

MODULE

Module code concerned (6 = purchase module)

PLITYP

Price list type (1 = standard price list, 2 = grouped price list)

TRAIT

Processing code that launched the price search:

- PSH = purchase requests

- PSM = planning workbenches (automatic management of purchase requests)

- POH = orders

- POI = buyer plan

- POC = open order contracts for the creation of a price list line

- POV = open order contracts for the valuation of the contract

- POD = delivery requests

[F:BPS]PLISTC

Supplier code structure.

The variables given above must not be modified.

The following variables are loaded by the price search and can be modified.

MONTANT(0)

Gross unit price.

MONTANT (1) to MONTANT(9)

Amounts or percentages for the 9 possible charges or discount

The following global variables indexed from 0 to 8 give the specifications for the charges or discounts (warning the 0 index for the global variable points to index 1 of the MONTANT variable and so on).

- GFMTREM(0..8): "%" indicates that the value is a rate

- GCOLREM(0..8): Short titles for the charges or discounts

- GDISCRGTYP(0..8): 1 indicates an amount,  2 indicates a percentage of an amount and  3 a percentage in series

- GINVDTALIN(0..8): Invoicing element codes

- GNPRNOTFLG-0..8): 1 does not intervene in the line net price and  2 intervenes in the net price

- GCLCRUL(0..8): Calculation bases: 1 by unit,  2 by line and  3 by document

MONTANT(10)

According to the price list setup this field contains the lead-time in number of days used to calculate the expected delivery date from the order date.

MOTIF (0)

Gross unit price reason.

MOTIF (1) to MOTIF(9)

Possible reasons for the 9 charges or discounts.

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

Miscellaneous remarks

The CALNET sub-program is used to calculate the net unit price.

In version 13x, to force a price to zero, the PURPRICE parameter must be deactivated if necessary; This parameter is used to retrieve the standard cost of the product in case the price list does not exist.

This deactivation is performed by setting the GPURPRICE global variable to the value 1.

TARIFVEN: Intervention on the values found during the Sales search

This entry point located in the TRTPRICE processing (price search) generates a "TARIFVEN" action.

The purpose of this action is to give the possibility to act on the values found via the price search.

It is also possible to perform additional controls in this manner: If the amount of the 1st discount is null, a control must be perform to check whether the basis price list is different from XY. Otherwise an error message is displayed.

Context and operating mode

Transaction

There is a transaction in progress only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Log file

There is a log file only if the price search is carried out from the workbenches for a purchase request creation (processing code "PSM").

Different call cases

The call is made:

- in price list simulation upon activation of the "Apply" button.

- when managing purchase requests, the buyer plan, orders, contracts, delivery requests, and workbenches (reorder plan and global planning)

Available variables and masks

The following variables are loaded when calling the "TARIFACH" action.

MODULE

Module code concerned (6 = purchase module)

PLITYP

Price list type (1 = standard price list, 2 = grouped price list)

TRAIT

Processing code that launched the price search:

- PSH = purchase requests

- PSM = planning workbenches (automatic management of purchase requests)

- POH = orders

- POI = buyer plan

- POC = open order contracts for the creation of a price list line

- POV = open order contracts for the valuation of the contract

- POD = delivery requests

[F:BPS]PLISTC

Supplier code structure.

The variables given above must not be modified.

The following variables are loaded by the price search and can be modified.

MONTANT(0)

Gross unit price.

MONTANT (1) to MONTANT(9)

Amounts or percentages for the 9 possible charges or discount

The following global variables indexed from 0 to 8 give the specifications for the charges or discounts (warning the 0 index for the global variable points to index 1 of the MONTANT variable and so on).

- GFMTREM(0..8): "%" indicates that the value is a rate

- GCOLREM(0..8): Short titles for the charges or discounts

- GDISCRGTYP(0..8): 1 indicates an amount,  2 indicates a percentage of an amount and  3 a percentage in series

- GINVDTALIN(0..8): Invoicing element codes

-          GNPRNOTFLG-0..8) : 1 does not intervene in the line net price and  2 intervenes in the net price

- GCLCRUL(0..8): Basis of the calculation: 1 by unit,  2 by line and  3 by document

MONTANT(10)

According to the price list setup this field contains the lead-time in number of days used to calculate the expected delivery date from the order date.

MOTIF (0)

Gross unit price reason.

MOTIF (1) to MOTIF(9)

Possible reasons for the 9 charges or discounts.

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

Miscellaneous remarks

The CALNET sub-program is used to calculate the net unit price.

In version 13x, to force a price to zero, the PURPRICE parameter must be deactivated if necessary; This parameter is used to retrieve the standard cost of the product in case the price list does not exist.

This deactivation is performed by setting the GPURPRICE global variable to the value 1.

NEGPRI: To authorize the entry of a negative price on Purchase order creation

This entry point found in the TRTPRICE processing (net price calculation), which is only called for purchases and only if the product concerned is not managed in stock, generates a "NEGPRI" action.

The purpose of this action is to authorize the entry of a negative price in purchase order creation.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no log file.

Different call cases

The call is performed in the purchase order management function and the buyer plan function.

Available variables and masks

The following variables are loaded when calling the "NEGPRI" action.

PARTNER

Business partner (2 = supplier)

STRUCTURE

Price list structure code

BRUT

Gross unit price

NET

Net unit price

The variables given above must not be modified.

The following variable is loaded if the price is negative and can be modified.

GMESSAGE

Contains the error message if the price is negative.

Deleting this message authorizes the negative price.

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

Miscellaneous remarks

It is not possible to authorize a negative price for a product managed in stock.

FREINV: Modifying the freight calculation

 Use this entry point to act on the freight calculation.

- by modifying the value of the "freight calculation" field: [F :BPC]FREINV

- by modifying the value of the "calculation threshold" field: [F :BPT]TDSFRE(x)

- by allowing the taking into account of the volumetric weight in lieu of the weight.

This entry point is called in the TRTPRICE processing.

- In delivery management: to calculate the freight.

- In carrier management: to simulate the freight calculation.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called:

- in the ‘VERIF_CRE’ and ‘VERIF_MOD’ actions of the delivery management if the ‘FRENUM‘ parameter (freight invoicing element) is not equal to 0. These actions are executed just before the entry or re-entry transaction for a delivery.

- in the carrier management during the execution of the "Simulation" button at the bottom of the screen.

Available variables

The entry point is called in the TRANSPORT sub-program. The following variables are passed as parameters of this sub-program:

BPTNUM: Carrier

BPCNUM: Customer

STOFCY: Shipment site

CRY: Country

POSCTY: City

POSCOD: Postal code

CUR: Currency

WCHGTYP: Exchange rate type

WCHGDATE: Exchange rate date

WAMTNOT: Ex tax amount used for the threshold search

WEU: Weight unit

WGROWEI: Weight

VOU: Volume unit

WVOL1: Volume

To take into account the volumetric weight in lieu of the weight, the WPE_WEIVOL variable has been added.

If this variable is set to 1 in the entry point, and if the volume and the coefficient are different from 0, the volumetric weight will always be taken into account even if it is inferior to the weight. (In the standard case, the volumetric weight is only taken into account if it is superior than the weight).

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 containing the header, but not for the file containing the lines…

CALNET: Act on the intermediate amount during the net price calculation

Use this entry point to act on the net price calculation by intervening in the intermediate amounts for the discounts or charges to apply to the gross price. This also makes it possible to manage net price rounding.

This entry point is called in the TRTPRICE processing.

- In sales: management of quotes, orders, deliveries and invoices.

- In purchasing: management of purchase requests, orders.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

The entry point is called in the net price calculation subprogram, at the end of the calculation.

This sub-program is common:

- to all the sales functions used to create or modify a quote, an order, a delivery or an invoice,

- to all the purchasing functions used to create or modify a purchase request or an order.

Available variables and tables

The local variables loaded before the call:

GCALNETLIN: indicates the no. of the [M] class line in update mode. –1 should be selected to obtain the index.

GCALNETABR: indicates the abbreviation of the class in update mode (ex.: [M] , [M:PSH1] , [F:SDD]

The local variable I takes the values 0 to 8 corresponding to the indexes of the 9 discounts/charges possible.

The record containing the setup of the price list structure (PRICSTRUCT) is on line.

The main fields are:

[F:PRS]NPRNOTFLG(I): indicates whether the discount is taken into account in the net price calculation

[F:PRS]INCDCR(I): indicates whether it is an increase or a decrease

[F:PRS]VALTYP(I): indicates whether it is an amount, a total % or a series %

[F:PRS]CLCRUL(I): indicates if the discount is to be applied to the unit, the line or the document

The important variables supplied as parameters in the sub-program are the following:

- On receipt

BRUT: Gross unit price

MAJREM(0..8): Charges or discounts (as % or amount)

QTE: Quantity

- On issue

NET: Net unit price (calculated)

The local variable WREM indexed by I contains the different discounts arising from the calculation. The values are negative if this is a discount and positive if it is a charge. 

To modify the net price calculation it is necessary to intervene in the different values of WREM.

To obtain the net price, it is then necessary to add the WREM to the gross price:

NET = BRUT + WREM(0) + WREM(1) +  …  + WREM(8) 

If the net price rounding is managed in the entry point, it is necessary to set GPE_RND=1 in order not to carry out the standard rounding.  

The GFONCTION global variable contains the function currently being executed:

SIMTARIF: To modify the price list lines screen during a price search

This entry point is used exclusively when constituting the price list lines in price search after the activation of the "Price list inquiry" button. It is used to modify the content of each line.

This entry point is called in the TRTPRICE processing and is active for purchases and sales.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called for each line to view in the price list line section of the price search function. The loading of the line is carried out in the generated program specific to each price list. The addition of a field in the class [M] grid requires the use of this entry point. 

Available variables and tables

It is necessary to test the active mask to determine the Purchasing or Sales environment:

If clalev ([M:PPM0]) > 0   the environment is purchasing

If clalev ([M:SPM0]) > 0   the environment is sales 

Active price list code:

- in purchasing: [F:PPL]PLI

- in sales: [F:SPL]PLI 

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

MAJFORMAT: Modify the charges and discounts formats in the purchase price list l

This entry point, located in the TRTPRICE processing (loading of price list charges/discounts entry format) generates a "MAJFORMAT" action.

The goal of this action is to be able to assign a specific entry format to each price list line charge or discount, for example to increase the number of decimals.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no log file.

Different call cases

The call is performed in the purchase order management function and the buyer plan function.

Available variables and masks

The following variables are loaded when calling the "MAJFORMAT" action.

WABMSK

Screen mask abbreviation used in the entry of price list charges and discounts.

CUR

Currency in which the amounts are expressed

I

Index used for the loop processing of entry formats (0 to 8)

GFMTREM(I)

Global variable indexed from 0 to 8 containing the charge or discount format type ("M" = amount, "%" = Rate)

GCOLREM(I)

Global variable indexed from 0 to 8 containing the charge or discount title (" " = deactivated column)

The variables given above must not be modified with the exception of I index.

The following variable of a class [M] indexed from 0 to 8 must be loaded with the new format if necessary.

FMTREM(I)

Loading example:

Example 1: Set the charge/discount rates to 3 decimals and the amounts to 4 decimals

For I=0 to 8

   If GFMTREM(I)=”M”

    Assign “[M:”+WABMSK+”]FMTREM(I)” With “NZ:6.4#”

  Else

    Assign “[M:”+WABMSK+”]FMTREM(I)” With “NZ:3.3#[  ]”

  Endif

Next I

Example 2: Identical to the previous example but only for classic orders

If WABMSK=”POH2”

  For I=0 to 8

     If GFMTREM(I)=”M”

      [M:POH2]FMTREM(I)=“NZ:6.4#”

    Else

      [M:POH2]FMTREM(I)=”NZ:3.3#[  ]”

    Endif

  Next I

Endif

The following screen classes are available according to the context:

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.

FREINV1: Intervene on the freight amount at the end of the carrier price list ca

 This entry point is used to intervene in at the end of the freight calculation:

- by modifying the freight value AMTFRE

This entry point is called in the TRTPRICE processing.

- In delivery management: to calculate the freight.

- in carrier management to simulate the freight cost calculation.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called:

- in the ‘VERIF_CRE’ and ‘VERIF_MOD’ actions of the delivery management if the ‘FRENUM‘ parameter (freight invoicing element) is not equal to 0. These actions are executed just before the entry or re-entry transaction for a delivery.

- in the carrier management during the execution of the "Simulation" button at the bottom of the screen.

Upon calling the entry point, the freight calculation is completed. Only the conversion in the requested currency is not carried out.

Available variables

AMTFRE:              contains the freight amount calculated in the carrier currency. The amount modifications must be in the carrier currency.

In the simulation function and according to the rules applied to the calculation, the following descriptive labels for the calculation are already loaded:

LIBCONPV:          If conversion of volume into weight (volumetric weight)

LIBNCAL:             No calculation carried out; either error, or threshold not reached

LIBFIX:                Fixed amount

LIBFIXR:              Fixed amount by region

LIBPRO1:             Proportional amount

LIBPRO2:             Proportional amount (next)

LIBCONVD:          If currency conversion. This line is loaded only if the call currency is different from the carrier price list currency.

LIBUSER:              10 lines of 150 characters available to explain the calculation developed in the entry point. In the simulation screen, the labels for these lines are displayed after the standard labels LIBCONPV, LIBNCAL, LIBFIX, LIBFIXR, LIBPRO1, LIBPRO2, but before LIBCONVD.

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 containing the header, but not for the file containing the lines…

TARIFS: Intervene in different contexts in the price search

This entry point, located in TRTPRICE, manages the calls from different origins. The CODENTPNT code value determines the origin of the call as well as its context. This "derived" call is necessary for the generated processings that cannot be assigned to a standard processing. Thus the entry points arising from purchasing and sales can be processed.

In the specific processing, any development must be linked to a value of CODENTPNT.   

Context and operating mode

Transaction

Log file

Different call cases

COLREM: Modifying the description of charges and discounts columns

This entry point is used upon reading the descriptions of the charges/discounts columns of a price list structure when it is used in entry of a sales or purchase document.

It is used to act on the description of columns to modify them according to the context.

This entry point is located in the TRTPRICE processing.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no log file.

Different call cases

The call is carried out in the management of all purchase documents (purchase requests, RFQs, orders, contract POs, receipts, invoices, returns) and all the sales documents (quotes, orders, open orders, deliveries, invoices).

Available variables and masks

The following variables are loaded when calling the entry point.

TAILLE

L=Title

C=Short title

PARTNER

Structure type

C=Customer (sales)

C=Supplier (purchasing)

STRUCTURE

Price list structure code

To act on the column titles, the following global variable must be modified:

GCOLREM(I)

This global variable indexed from 0 to 8 contains the charges or discounts title. 

The screen classes relating to the different sales/purchasing functions are available and specified according to the context, as well as the tables relating to the corresponding objects.

Open tables

In the table below, the significant content flag indicates that the content matches the context and should not be changed by the entry point.