Usina BRAdvPL Guide
Sign in
← All topics
ENTRY POINTUnder review

F241INC5

ExecBlock("F241INC5", .F., .F.)

Official FINA241 and FINA590 record; community call placed in F241IMPOST.

F241INC5FINA241FINA590ExecBlock
01 · OVERVIEW

Overview

The official index associates F241INC5 with FINA241 and FINA590 and marks its specific documentation under construction. The call list records ExecBlock("F241INC5", .F., .F.) in both routines. (TOTVS, n.d., refs. 1–2) The inspected P12.2210 community listing details the FINA241.PRX call in F241IMPOST(). (Universo do Desenvolvedor, 2023, ref. 3) That excerpt does not document the equivalent FINA590 context. The searches performed located no useful implementation. Official records were consulted through indexed evidence; the community listing was read directly.

02 · SYNTAX

Syntax

ExecBlock("F241INC5", .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

Call located in FINA241

// P12.2210 community excerpt: FINA241.PRX / F241IMPOST().
// Identifies neither the internal FINA590 caller nor an F241INC5 implementation.
ExecBlock("F241INC5", .F., .F.)
Expected result

Documents a call without a fourth argument or return assignment in the FINA241 excerpt. It is not an executable program and does not establish FINA590 behavior.

BEST PRACTICES
  • Confirm context separately in FINA241 and FINA590. Being listed in both does not guarantee identical private variables or execution timing.
  • Do not infer purpose, call sequence or commit timing from the F241INC5 name.
  • F241INC, F241INC2 and F241INC5 are distinct identifiers; their contracts have not been shown to be equivalent.
  • Before implementing, inspect the complete call, aliases, locks and failure handling in the target release.
  • 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