ENTRY POINTUnder review

FA070BLQ

User Function FA070BLQ()

Controls monetary-adjustment editing in receivable settlement.

FA070BLQFINA070

01 · OVERVIEW

Overview

The official historical Protheus 10/11 page shows lLibCm receiving the return. Its example asks whether to edit monetary adjustment: .T. accepts and .F. rejects. This is neither adjustment-amount calculation nor a general title lock. The call passes no explicit context and the tables do not detail parameters. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function FA070BLQ()

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

Logical used in lLibCm; the official example uses .T. to accept editing and .F. to reject it.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function FA070BLQ()
    // Adapted TOTVS example: interactive choice, no amount calculation.
    Local lEdit := MsgYesNo("Change monetary adjustment?", "Monetary adjustment")
Return lEdit

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.
// FINA070.PRX - FA070TIT*/() -> LLIBCM := EXECBLOCK("FA070BLQ",.F.,.F.)

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 dialog below adapts the official example for attended operation. Do not use MsgYesNo in unattended jobs. Verify its effect on the adjustment field in the target release.
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.