TRTACHAPP1 process: TRTACHAPP1

VALMAXSIGN: Amount for choice of signatures

This entry point located in the TRTACHAPP1 process, purchase signature management, generates a "PAMAPPFLG" action.

The purpose of this action is to give the possibility to specify whether the modification of a heading must lead to the resumption of the signature cycle.

Context and operating mode

Transaction

There is no transaction in process.

Log file

There is no open log file.

Different call cases

The call occurs on the After-modification actions for the fields in the purchase order or purchase request screens.

Available variables and masks

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

WABMSK  Abbreviation of the current mask. It is entered for the purchase order (POH2) and purchase request (PSH1) lines.

NOLIG      Index of the line

NOMZON   Name of the modified field

FLAG        Major heading flag (1=no, 2=yes)

This is the flag that needs to be modified to define a field as being a major field which will cause the signature cycle to resume.

Remarks

This entry point is called as a standard only for fields which have an after-modification PAMAPPFLG action.

To add this mechanism to specific fields, it will be necessary to add this after-modification action.

To add this mechanism to standard fields that are not considered, it will be necessary to add a SPE after-modification action. This action calls the PAMAPPFLG subprogram of the TRTACHAPP1 process.

SIGNATAIRE: Modification of the delegates and substitutes

This entry point, located in the TRTACHAPP1 processing (purchase signature management), generates a "SIGNATAIRE" action.

This action is used to change the signatories and the delegates before the creation of the signatures to be performed.

Context and operating method

Transaction

An entry transaction is active.

Log file

There is an open log file if the value of the GTRACE global variable is entered.

Call context

The entry point is called during the creation and modification of the following elements:

• Purchase requests
• Orders
• Contracts

The entry point can also be called in signature management.

Available screens and variables

The [F :PAD] class is available.
[F :PAD]APPUSR
User code of the signatory (can be modified)
[F :PAD]SBSAPPUSR
User code of the delegate (can be modified)
[F :PAD] APPRUL
Signature rule (1=Purchase request line, 2=Order, 3=Contract)
[F :PAD]NUM
Number of the purchase request, order or contract
[F :PAD]LIN
Number of the purchase request line or 0 for the orders
GFONCTION
Contains the current function and helps determine the context.
The following values are possible:
- GESPSH = Purchase request management
The [F :PSH] and [F :PSD] classes are significant and must not be modified.
- GESPOH = Order management
The [F :POC] class is significant and must not be modified.
- GESPOC = Contract management
The [F :POC] class is significant and must not be modified.
- FUNPAD = Signature rule management
If it proves necessary for the entry point, the (F:PSH], [F:PSD] or F:POH] classes must be open. Then it is necessary to use [F:PAD] ]NUM and [F:PAD]LIN.
- ?????? = Various values, that is to say that they correspond to the generation of purchase requests and orders from the workbenches.
Classes [F :PSH] and  [F :PSD] are significant if [F :PAD]APPRUL = 1
The [F :POH] class is significant if [F :PAD]APPRUL = 2 or 3

Open grids

In the grid below, the "significant content" flag indicates that the content is on a par with the context.

Other comments

To find out the user codes that need to be modified, pseudo users should be created with an easily identified code (for example, starting with "XXX") and rules should be created with them.
Then, using the entry point, the appropriate code (buyer's code, etc. ) should be used as replacement.