ENTRY POINTUnder review

F340LIBT

User Function F340LIBT()

Controls the title-release check during compensation.

F340LIBTFINA340

01 · OVERVIEW

Overview

The specific documentation defines logical lVerLibTit. Its example normally returns .T. and .F. for an illustrative prefix: .T. retains the release check; .F. skips it in the described flow. Caller names differ between the page and P12.2210, requiring version verification. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340LIBT()

Return value

Logical: .T. checks release; .F. skips that check in the documented context.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340LIBT()
    // Retains the documented release check; no exceptions.
Return .T.

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() -> LVERLIBTIT :=EXECBLOCK("F340LIBT",.F.,.F.)
// FINA340.PRX - FA340QRYTI() -> LF340LIBT  := IF(EXISTBLOCK("F340LIBT"), EXECBLOCK("F340LIBT",.F.,.F.), LF340LIBT)

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

The baseline below preserves the check. Any exception needs an explicit business rule and tests with released and unreleased titles.
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.