ENTRY POINTUnder review

F430CHK

User Function F430CHK()

Participates in duplicate-processing control for payable CNAB returns.

F430CHKFINA430

01 · OVERVIEW

Overview

TOTVS associates F430CHK with resubmission prevention. Its log documentation distinguishes FI0/FI1 for receivables from a .VRF file for payables. P12.2210 records CHK430FILE directly returning ExecBlock without explicit context. That excerpt does not detail return type or polarity. (Refs. 1–3)

02 · SYNTAX

Syntax

User Function F430CHK()

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

Result propagated by CHK430FILE; complete reprocessing policy unconfirmed.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA430.PRX - CHK430FILE() -> RETURN EXECBLOCK("F430CHK",.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

Process the same file twice in a test environment and inspect control records. Do not remove .VRF files or return a constant to bypass duplicate prevention.
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.