ENTRY POINTUnder review

F340FCPTOP

User Function F340FCPTOP()

Replaces the title selection query in payable compensation.

F340FCPTOPFINA340

01 · OVERVIEW

Overview

The official overview describes a selection filter in TOPconnect. The P12.2210 call receives {cQry} and assigns its return to cQry in FA340QRYTI: this replaces text, unlike F340FLCP concatenation. The official NDF/INS article shows PARAMIXB[1] receiving the query. A tax-type inclusion rule requires its own analysis; do not remove SQL literals indiscriminately. (Refs. 1–3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F340FCPTOP()

Parameters

PARAMIXB[1] / cQry

CharacterExecution context

Received query, according to support example and community call. (Refs. 1–2)

Return value

Query text returned to the caller. The editorial example preserves the received query.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340FCPTOP()
    // Editorial example based on the observed argument and replacement.
    Local cQuery := PARAMIXB[1]
    // Keeps all filters; does not change tax title types.
Return cQuery

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 - FA340QRYTI() -> CQRY := EXECBLOCK("F340FCPTOP",.F.,.F.,{CQRY})

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 globally replace INS or uppercase the complete query as a generic solution: this can change literals and unrelated criteria. Compare final titles, branches and balances.
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.