ENTRY POINTUnder review

F340VLEX

User Function F340VLEX()

FINA340 call with aRecno as context argument.

F340VLEXFINA340

01 · OVERVIEW

Overview

The official call catalog lists ExecBlock("F340VLEX",.F.,.F.,{aRecno}) in FINA340. It identifies an outer array containing aRecno but does not describe inner contents, record alias, return or exact operation. No useful GitHub implementation was located in this research. (Ref. 1) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F340VLEX()

Parameters

Entry point context

UnconfirmedContext to confirm

The complete technical contract remains unconfirmed. Do not assume types, PARAMIXB positions or aliases beyond the evidence described.

Return value

Not documented in the available call record.

03 · PRACTICAL EXAMPLE

Observed call and context

// TOTVS call catalog (ref. 1); not a hook implementation.
// FINA340 - ExecBlock("F340VLEX",.F.,.F.,{aRecno})

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 turn the name aRecno into an SE2 record-position contract. Recover the full caller before proposing reversal or deletion validation.
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.