ENTRY POINTUnder review

F241NBOR

ExecBlock("F241NBOR", .F., .F.)

Payment batch number: community skeleton and call observed in FA241CANC.

F241NBORFINA241FA241CANCcTmpBord

01 · OVERVIEW

Overview

The official index associates F241NBOR with FINA241; its page is under construction. (TOTVS, n.d., ref. 1) Eurai Rapelli provides a skeleton for changing the payment batch number, returning an empty character cRet. (2023, ref. 2) The P12.2210 community listing places the call in FA241CANC and assigns its result to cTmpBord. (Universo do Desenvolvedor, 2023, ref. 3) The skeleton contains no numbering rule. GitHub searches found no implementation.

02 · SYNTAX

Syntax

ExecBlock("F241NBOR", .F., .F.)

Parameters

PARAMIXB

Undocumented contextContext to confirm

The recorded call supplies no fourth argument. This does not establish a PARAMIXB contract or availability of private variables or aliases. Do not assume PARAMIXB[1] contains the current number.

Return value

In the community skeleton, cRet is declared character and initialized empty. The listing assigns the return to cTmpBord without showing subsequent use or empty-string handling. There is no basis for recommending an empty string as a neutral return or claiming it preserves the current number.

03 · PRACTICAL EXAMPLE

Community skeleton excerpt

// Excerpt from Eurai Rapelli, 2023 (ref. 2); not a complete function.
// The empty string belongs to the skeleton, not a validated rule.
Local cRet := "" as character
Return(cRet)

Expected result

Shows only the declared type and returned initial value. It does not actually change the number and must not be deployed independently.

04 · PRACTICAL EXAMPLE

Documentary caller excerpt

// P12.2210 listing: FINA241.PRX / FA241CANC() (ref. 3).
// Validation and subsequent use of cTmpBord are not shown.
cTmpBord := ExecBlock("F241NBOR", .F., .F.)

Expected result

Shows the return assignment in FA241CANC without an explicit parameter. The function name suggests cancellation context; the excerpt does not establish transaction position.

BEST PRACTICES

Before implementing, inspect how cTmpBord is validated and used in the target release and patch. Do not infer effects from the article title alone.
Do not copy the F240NBOR contract: the F241NBOR listing does not pass the current number as a fourth argument.
Editorial test plan: compare the flow without customization against a return defined after caller analysis. Check selection, number and cancellation outcome.
Do not create fixed numbers or write directly to tables from this skeleton. Length, uniqueness and numbering rules remain unconfirmed.
Preserve attribution: these are community excerpts, not an official TOTVS implementation or a GitHub example.
Under review: not compiled or run in Protheus. Full contract, aliases and transaction position remain unverified.