ENTRY POINTUnder review

F460CTB

User Function F460CTB()

Complementary call after accounting in the inspected code.

F460CTBFINA460

01 · OVERVIEW

Overview

The GitHub copy comments this call as after accounting, without a fourth argument or result assignment. P12.2210 also records it in FINA460A/F460ACOMMIT. The function name does not establish that commit has completed. F460CTB is not explicitly named among removed hooks in the migration list consulted. (Refs. 1–4) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F460CTB()

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

The excerpt does not assign the result; complete contract unconfirmed.

03 · PRACTICAL EXAMPLE

Observed call and context

// Analysis of a legacy caller published on GitHub (ref. 3); not a hook implementation.
// If ExistBlock("F460CTB")
//     ExecBlock("F460CTB",.F.,.F.)
// EndIf

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 GitHub copy does not identify a validated release and is not an official distribution. Check the caller in the target environment; this example analyzes legacy flow rather than providing a deployable function.
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.