ENTRY POINTUnder review

F241REC1

ExecBlock("F241REC1", .F., .F., {aContab, "SE2"})

Call in F241IMPOST: receives aContab in the context and assigns the return to the same variable.

F241REC1FINA241F241IMPOSTaContabExecBlock

01 · OVERVIEW

Overview

The official index lists F241Rec1 with source FINA241, an unspecified routine column and documentation under construction. (TOTVS, n.d., ref. 1) The P12.2210 community listing places the call in F241IMPOST, passing {aContab, "SE2"} and assigning the result to aContab. (Universo do Desenvolvedor, 2023, ref. 2) This is caller evidence without an entry point implementation. GitHub searches found no useful implementation.

02 · SYNTAX

Syntax

ExecBlock("F241REC1", .F., .F., {aContab, "SE2"})

Parameters

PARAMIXB[1] / aContab

Type and layout unconfirmedContext to confirm

First element of the outer array: aContab, exposed as PARAMIXB[1] through ExecBlock. (Refs. 2–3) Type, positions and element meanings are unconfirmed. The name does not establish a specific accounting structure.

PARAMIXB[2] / "SE2"

CharacterContext to confirm

Second element: the literal string "SE2", exposed as PARAMIXB[2]. (Refs. 2–3) This does not establish that the alias is open or positioned, or that table writes are safe.

Return value

The call result is assigned back to aContab itself. This demonstrates assignment, not the required layout or subsequent validation. It is not equivalent to modification by reference. Returning aContab unchanged, all of PARAMIXB, NIL or a logical value has not been validated.

03 · PRACTICAL EXAMPLE

Documentary caller excerpt

// P12.2210 listing: FINA241.PRX / F241IMPOST() (ref. 2).
// aContab supplies an input value and receives the call result.
aContab := ExecBlock("F241REC1", .F., .F., {aContab, "SE2"})

Expected result

Shows both context elements and the return assignment to aContab. It does not implement F241REC1 and cannot run independently.

BEST PRACTICES

Inspect aContab preparation and all its uses after the call in the target release and patch. The excerpt does not show those steps.
Distinguish {aContab, "SE2"} from aContab contents: the former is the outer context; the latter occupies only PARAMIXB[1].
Do not infer accounting, payable recording or record reordering behavior from the REC1 and aContab names alone.
Do not transfer the F241AREC or F241ORD contract. They are distinct calls despite appearing in the same F241IMPOST listing.
Editorial test plan: once the contract is established, compare input layout, return and resulting processing. Record types and element counts without exposing customer data.
Under review: not compiled or run in Protheus. Transaction position, aliases and invocation frequency remain unconfirmed. Official index consulted through indexed evidence; community excerpt read directly.