SUBTPY processing: Payment Types

MGTTPY: Following the validation of a payment transaction

Use this entry point to take over following the payment transaction validation.

For each transaction, the user has the possibility to re-read the window (and therefore the generated screens) in order to possibly carry out modifications on the payment entry screen fields or even the number of tabs on the window.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

According to the context : 

 - Unit validation: there is no open log file 

 - Mass validation: there is an open log file  

Different call cases

This entry point is called after the standard payment transaction validation processing.

The validation of the payment transactions is launched under :

    - the GESTPY "payment entry type" function: validation of a single transaction (unit validation)

    - the GENMSKTRT "transaction validation" function: validation of all the transactions (mass validation)

    - under the SUBTPY processing, the PATCH and GENDOS programs exist: mass validation also upon folder or patch validation or patch.

 Depending on the modifications performed on the entry points, it is necessary to to validate a second time the modified screen(s) and possibly the window if the number of screen(=tabs) has been modified.

  - to re-validate screen 1: Call VALID(MASKDES1,APPLI,[F:ADS]NBRLAN,[F:ADS]LAN,1,OK) From VALMSK

  - to re-validate screen 2  :  Call VALID(MASKDES2,APPLI,[F:ADS]NBRLAN,[F:ADS]LAN,1,OK) From VALMSK

  - to re-validate the window: Call VALID(NOMWIN,APPLI,1,OK) From VALWIN

 Example:

$MGTTYP

Trbegin [AMK2]

Read [F:AMZ2]CODE = MASKDES1;"BPR"  : # Read the field to be modified

If !fstat

  [F:AMZ2]SAIAFF=3 : # Field that became invisible

  Rewrite [F:AMZ2]

 If fstat

GOK=0 : Call FSTA("AMZ2") From GLOCK : Rollback : Return

 Endif

Endif 

Commit

# Revalidation of the modified screen

Call VALID(MASKDES1,APPLI,[F:ADS]NBRLAN,[F:ADS]LAN,1,OK) From VALMSK

Return

 Available variables and masks

The TPYx masks are only open in unit validation.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.