ENTRY POINTUnder review

F340TAXA

User Function F340TAXA()

Allows currency-rate handling in payable compensation.

F340TAXAFINA340

01 · OVERVIEW

Overview

The specific page receives the currency array in PARAMIXB[1] and states that return is not applicable. The official example changes private aTxMoedas using the title’s currency as index and column 2 as rate. Its fixed value 2 is illustrative, not a recommended exchange rate. The excerpt does not specify the entire matrix or authorize replacing that mechanism with an array return. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340TAXA()

Parameters

PARAMIXB[1]

ArrayExecution context

Currency array; complete layout not described. (Refs. 1–2)

Return value

Not applicable in the official page; the illustrated change uses private context.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340TAXA()
    // Editorial diagnostic; no exchange rate is changed.
    Local aCurrencies := PARAMIXB[1]
    ConOut("F340TAXA: " + cValToChar(Len(aCurrencies)))
Return Nil

Expected result

Teaching proposal with behavior described in comments. Verify the context before compiling in a test environment. Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

04 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - FA340COMP() -> EXECBLOCK("F340TAXA",.F.,.F.,{ATXMOEDAS})

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

Do not declare Local aTxMoedas and shadow the caller’s private variable. The diagnostic below only counts received currencies; a rate rule requires calculation and conversion validation.
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.