ENTRY POINTUnder review

F241CBD

ExecBlock("F241CBD", .F., .F.)

FINA241 call and return assignment observed in a community listing.

F241CBDFINA241FA241CANCExecBlock

01 · OVERVIEW

Overview

The Financeiro P12 index associates F241CBD with routine and source FINA241, with specific documentation under construction. The official call list records ExecBlock with three arguments. (TOTVS, n.d., refs. 1–2) Universo do Desenvolvedor places the call in FA241CANC and shows its return assigned to lDelBord. (Universo do Desenvolvedor, n.d., ref. 3) Interpreting the caller name suggests investigating the cancellation flow; the excerpt does not show the condition consuming that return. No useful implementation was located in the GitHub searches performed. Official records were consulted through indexed evidence; the community listing was read directly.

02 · SYNTAX

Syntax

ExecBlock("F241CBD", .F., .F.)

Parameters

Entry point context

UndocumentedContext to confirm

The published call has no fourth argument. This does not establish the absence of implicit context or justify assuming PARAMIXB contents. Formal arguments and available private variables require verification in the target release.

Return value

The community excerpt assigns the return to lDelBord. Its name suggests a logical value related to payment batch deletion, but does not confirm the accepted type or the effect of .T., .F. or NIL. This page recommends no default return.

03 · PRACTICAL EXAMPLE

Documentary caller excerpt

// Excerpt published by Universo do Desenvolvedor; editorial comment.
// Context reported by the listing: FINA241.PRX / FA241CANC().
lDelBord := ExecBlock("F241CBD", .F., .F.)

Expected result

The excerpt shows the return assigned to lDelBord. It does not implement F241CBD and cannot run independently.

BEST PRACTICES

Confirm subsequent use of lDelBord before implementing the entry point; choosing a return without that contract may change cancellation behavior.
The listing is titled P12.2210; it does not establish behavior or compatibility in other releases.
Transaction position, aliases, locks and effects on payables and payment batches remain unconfirmed.
No example was compiled or executed in Protheus. The example is a documentary caller excerpt.