ENTRY POINTUnder review

FA300PA

User Function FA300PA()

Allows extensions after recording PA in legacy SISPAG.

FA300PAFINA300

01 · OVERVIEW

Overview

The official migration table describes this purpose: Allows extensions after recording PA in legacy SISPAG. TOTVS records FINA300 discontinuation on 2022-08-20 and maps it to FA430PA in FINA430. This is a migration mapping, not a guarantee of identical signatures. The P12.2210 listing records the call without establishing current support or its complete contract. No useful GitHub implementation was found. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function FA300PA()

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

Unconfirmed; the excerpt shows no use of the result.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA300.PRX - FA300PROCESSA() -> EXECBLOCK("FA300PA", .F., .F.)

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

For migration, study FA430PA and the FINA430 layout. Do not merely rename the customized hook. Inspect resulting files and prevent repeated processing.
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.