ENTRY POINTUnder review

F460CAN

User Function F460CAN()

Hook in legacy settlement operation cancellation.

F460CANFINA460

01 · OVERVIEW

Overview

TOTVS classifies F460CAN as legacy removed from 12.1.17. In the GitHub copy, nOpca different from 1 enters a block where F460CAN takes precedence over F460CON through ElseIf. No explicit context or assigned result appears. The migration article supplies no exclusive replacement event for F460CAN. (Refs. 1 and 3)

02 · SYNTAX

Syntax

User Function F460CAN()

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 != 1
//     If lF460Can
//         ExecBlock("F460CAN",.F.,.F.)
//     ElseIf lF460CON
//         ExecBlock("F460CON",.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.