Usina BRAdvPL Guide
Sign in
← All topics
ENTRY POINTUnder review

F241INC

ExecBlock("F241INC", .F., .F.)

Call listed in FINA241 and placed in F241IMPOST by the community; technical contract unconfirmed.

F241INCFINA241F241IMPOSTExecBlock
01 · OVERVIEW

Overview

The Financeiro P12 index lists F241INC under routine and source FINA241, with specific documentation under construction. The official list records ExecBlock("F241INC", .F., .F.). (TOTVS, n.d., refs. 1–2) The P12.2210 community listing places the call in F241IMPOST(), without return assignment in the excerpt. (Universo do Desenvolvedor, 2023, ref. 3) This identifies the caller but does not establish the specific purpose, insertion event or recording stage. GitHub and web searches located no useful implementation. Official indexes were consulted through indexed evidence; the community listing was read directly.

02 · SYNTAX

Syntax

ExecBlock("F241INC", .F., .F.)

Parameters

Entry point context
UndocumentedContext to confirm

The located call has no fourth argument. This does not establish the absence of private context or justify assuming PARAMIXB structure or contents. Formal parameters, aliases and accessible variables remain unconfirmed.

Return value

Type and meaning are unconfirmed. The excerpt shows no return assignment or test; this neither establishes that any value is safe nor confirms handling by every caller.

03 · PRACTICAL EXAMPLE

Documentary call excerpt

// P12.2210 community listing: FINA241.PRX / F241IMPOST().
// Caller excerpt; not an F241INC implementation.
ExecBlock("F241INC", .F., .F.)
Expected result

Shows the call without a fourth argument or return assignment in this excerpt. It cannot run independently and demonstrates no business rule.

BEST PRACTICES
  • Do not infer execution after insertion, recording or commit from the INC suffix alone.
  • F241INC, F241INC2 and F241INC5 are distinct identifiers; similar names do not establish equivalent contracts or execution stages.
  • Before implementing, confirm the complete call on the target release and patch, including tables, available context and failure handling.
  • Avoid choosing .T., .F. or NIL returns without confirming how the standard routine handles that value.
  • This page provides no implementation; no Protheus compilation or execution occurred.

Related content

REFERENCES
  1. TOTVS. Pontos de Entrada - Financeiro - P12. TDN. Indexed evidence accessed on 2026-10-23.
  2. TOTVS. Pontos de Entrada. TDN. Indexed evidence accessed on 2026-10-23.
  3. EURAI. Pontos de Entrada P12.2210 - Parte 2. Universo do Desenvolvedor, 2023. Accessed on 2026-10-23.
Status
Under review
Page created on
Last reviewed on
Original language
Portuguese
Reviewed by
Usina.BR
0 approved comment(s)

Comments

There are no approved comments yet.

Sign in with Google or Microsoft to comment.

Powered by Usina Docs · Alpha