ENTRY POINTUnder review

F460JUR

User Function F460JUR()

Supplies the interest-calculation result in the observed caller.

F460JURFINA460

01 · OVERVIEW

Overview

P12.2210 assigns the return to nJuros in FA460REPL. The GitHub copy confirms this use: when lF460JUR is active it uses ExecBlock, otherwise FA070JUROS. This differs from F460EDIT, which validates the field with a logical result. No explicit PARAMIXB context is documented in this call. (Refs. 1–3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F460JUR()

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

Numeric value used as nJuros in the inspected code; no universal formula is documented here.

03 · PRACTICAL EXAMPLE

Observed call and context

// Analysis of a legacy caller published on GitHub (ref. 3); not a hook implementation.
// If lF460JUR
//     nJuros := ExecBlock("F460JUR",.F.,.F.)
// Else
//     nJuros := FA070JUROS(SE1->E1_MOEDA,SE1->E1_SALDO)
// 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.