ENTRY POINTUnder review

F340FCAN

User Function F340FCAN()

Allows complementary writes during payable compensation reversal.

F340FCANFINA340

01 · OVERVIEW

Overview

The specific page states that SE2 is positioned and execution occurs within Begin Transaction. Parameters and return do not apply. Its example writes E2_DTCSTMZ, a custom field that must not be assumed standard in every environment. The community call appears in FA340CAN. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340FCAN()

Return value

Not applicable. The official example ends with NIL; this entry point is not a logical reversal validation.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340FCAN()
    // Editorial diagnostic in the documented transaction context (ref. 1).
    // Avoids depending on the official example custom field E2_DTCSTMZ.
    ConOut("F340FCAN: reversal processing; transaction still active")
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 - FA340CAN() -> EXECBLOCK("F340FCAN",.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 published diagnostic does not write records. Before adapting the custom-field example, verify SX3, title identity and RecLock; preserve the standard transaction and test rollback. Do not assume commit before external integrations.
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.