ENTRY POINTUnder review

F340GRV

User Function F340GRV()

Runs a customization after compensation with a confirmation indicator.

F340GRVFINA340

01 · OVERVIEW

Overview

The specific page documents numeric PARAMIXB[1]: 1 for confirmed compensation and 0 for cancellation. Tables remain positioned for consultation; the official example names SE2, SE5, FK2 and FK7 in the confirmed branch. This specific description takes precedence over the historical inclusion-validation summary. Execution after commit is not established. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340GRV()

Parameters

PARAMIXB[1]

NumericExecution context

1: confirmed; 0: canceled. (Refs. 1–2)

Return value

Not applicable according to the specific page. The received indicator is not the function return.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340GRV()
    Local nStatus := PARAMIXB[1]
    If nStatus == 1
        ConOut("F340GRV: compensation confirmed")
    ElseIf nStatus == 0
        ConOut("F340GRV: compensation canceled")
    EndIf
Return Nil

Expected result

Teaching proposal with behavior described in comments. Verify the context before compiling in a test environment. Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

04 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - FA340COMP() -> EXECBLOCK("F340GRV",.F.,.F.,{NOPCA})

Expected result

The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.

BEST PRACTICES

Do not interpret cancellation as a persisted compensation. For external integrations, establish the transaction boundary and retry policy before emitting events.
A call without a fourth argument does not document a PARAMIXB layout. Preserve caller identifiers and do not invent fields or positions.
Test plan: compare standard and customized flows, exercise success, rejection and repetition, and inspect balances, movements and accounting as applicable.
Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.