ENTRY POINTUnder review

F460SAID

User Function F460SAID()

Legacy call in the settlement-selection exit branch.

F460SAIDFINA460

01 · OVERVIEW

Overview

TOTVS lists F460SAID among hooks removed from 12.1.17. In the public copy, it occurs when nOpca is 2 or 0, after FreeUsedCode and before flow exit. No fourth argument or assigned result appears. This does not establish completed writes or an exclusive MVC replacement event. (Refs. 1 and 3)

02 · SYNTAX

Syntax

User Function F460SAID()

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 nOpca == 2 .Or. nOpca == 0
//     FreeUsedCode()
//     If ExistBlock("F460SAID")
//         ExecBlock("F460SAID",.F.,.F.)
//     EndIf
//     // ...
// 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.