LTIPRICE: Calculation of the planned reception date with the price list deadline

This entry point located in the TRTACHCDE1 process, purchase order creation, generates an "ECLBESOINS" action.

The purpose of this action is to give the possibility to force the integration of the price list deadline in order to recalculate the planned reception date further to a price list search.

Context and operating method

Transaction

There is no transaction in process.

Log file

There is no open log file.

Different call cases

The call is made:

-          in the traditional order management during the creation of an order line

-          in the buyer's plan management during the creation of a line

Available variables and masks

The following variables are loaded at the time of the call to the "LTIPRICE" action.

TRAIT

Process code that launched the price list search:

-          POH = orders

- POI = buyer plan

MONTANT (10)

Deadline given by the price list

[M :POH2]RETRCPDAT(NOL)  or  [M :POI1]RETRCPDAT(NOL)

Planned due date.

[M :POH0]ORDDAT  or   [M :POI1]ORDDAT

Order date

The following variable can be modified and is used to force or not the calculation of the planned reception date with the price list deadline.

LTIFLG

0 = No calculation of the planned reception date

1 = Calculation of the planned reception date depending on the price list deadline (Order date + Price list deadline)

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context and must not be altered by the entry point.

Table

Significant content

Table Title

BPARTNER

Yes

Business partner (BPs)

BPSUPPLIER

Yes

Supplier

BPSUPPMVT

Yes

Supplier movements

ITMMASTER

Yes

Product

ITMBPS

Yes

Product-Supplier

PPRICLINK

Yes

Search purchase prices (Link)
Miscellaneous remarks

This entry point is only called if there is a deadline on the price list and the order line is being created.

 

TARIFACH: Intervention on the values found during the price list search

This entry point is located in the TRTPRICE and TRTACHTAR1 processes search the purchase price lists in the creation of purchase requests, orders or delivery requests, generating a "TARIFACH" action.

The purpose of this action is to give the possibility to intervene in the values found during a price list search.

Context and operating method

Transaction

There is a transaction in process only if the price list search is carried out from the work benches for a purchase request creation (process code "PSM").

Log file

There is a log file only if the price list search is carried out from the work benches for a purchase request creation (process code "PSM").

Different call cases

The call is made:

- in price list simulation on activation of the "Apply" button

- in purchase request management, from the buyer plan, the orders, contracts, shipment requests, and work benches (reorder planning and global planning)

Available variables and masks

The following variables are loaded at the time of the call to the "TARIFACH" action.

MODULE

Module code concerned (6 = purchase module)

PLITYP

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

TRAIT

Process code that launched the price list search:

- PSH = purchase requests

-          PSM = work benches (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 = shipment requests

[F:BPS]PLISTC

Supplier code structure.

The variables given above must not be modified.

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

MONTANT (0)

Gross unitary 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 as a number of days used to calculate the expected shipment date from the order date.

MOTIF (0)

Gross unitary price reason.

MOTIF (1) to MOTIF(9)

Possible reasons for the 9 charges or discounts.

The following screen classes are available as a function of the context:

Contexts

TRAIT

Line grid screens

Other screens

Purchase requests

PSH

PSH1

 

Order

POH

POH2

POH0, POH1, POH3

Buyer plan

POI

POI1

 

Contracts

POC, POV

POC2

POC0, POC1, POC3

Shipment requests

POD

POD1

 

Work benches

PSM

PURMGT

 

Price list simulation

POH

POH2

POH0, POH1, POH3, PPSIMUL0, PPSIMUL1

 

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context and must not be altered by the entry point.

Table

Significant content

Table Title

BPARTNER

Yes

Business partner (BPs)

BPSUPPLIER

Yes

Supplier

BPSUPPMVT

Yes

Supplier movements

ITMMASTER

Yes

Product

ITMBPS

Yes

Product-Supplier

PPRICLINK

Yes

Search purchase prices (Link)
Miscellaneous remarks

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

In version 13x if the price needed to be forced to zero, the PURPRICE setup would be de-activated if necessary, the setup is used to take the standard cost of the product in the case where the price list did not exist.

This deactivation would be made by setting the GPURPRICE global variable to the value 1.