Usina BRAdvPL Guide
Sign in
← All topics
ENTRY POINTUnder review

FA070BCO

User Function FA070BCO()

Validates bank choice in the observed receivable settlement flow.

FA070BCOFINA070
01 · OVERVIEW

Overview

P12.2210 uses the return in logical expressions in FA070LOT and FA070TIT without explicit context. DanielPitthan’s GitHub example reads __cUserID, cBanco and custom MV_UUSUHV/MV_UCXHV settings; it rejects a different bank for covered users and restores the workarea. That rule belongs to the example, not every environment’s standard contract. (Refs. 1–3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function FA070BCO()

Parameters

Entry point context
UnconfirmedContext to confirm

The complete technical contract remains unconfirmed. Do not assume types, PARAMIXB positions or aliases beyond the evidence described.

Return value

Logical result in the observed use. The community example returns .F. to reject its bank rule and .T. to accept it.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA070.PRX - FA070LOT() -> .AND. IIF(__LFA70BCO,EXECBLOCK("FA070BCO",.F.,.F.),.T.) .AND. IIF(LJFILBCO, JURVLDSA6("1", {CESCRIT, CBANCOLT, CAGENCIALT, CCONTALT}), .T.))
// FINA070.PRX - FA070TIT*/() -> (IIF(__LFA70BCO,EXECBLOCK("FA070BCO",.F.,.F.),.T.) .AND.;
Expected result

The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.

BEST PRACTICES
  • The example’s $ expression searches a text substring rather than exact membership in a permissions register. Verify user lists, lengths, bank and local settings; do not copy custom parameters as standard configuration.
  • A call without a fourth argument does not document a PARAMIXB layout. Preserve caller identifiers and do not invent fields or positions.
  • Test plan: compare standard and customized flows, exercise success, rejection and repetition, and inspect balances, movements and accounting as applicable.
  • Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

Related content

REFERENCES
  1. TOTVS. Pontos de Entrada - Financeiro - P12. TDN. Accessed on 2026-10-24.
  2. EURAI. Pontos de Entrada P12.2210 - Parte 2. Universo do Desenvolvedor, 2023. Accessed on 2026-10-24.
  3. DanielPitthan/Exemplos-Protheus-para-IA. Protheus/Fontes/uni_repo/HV/FA070BCO.prw. GitHub, commit 2e916160c23d301a60c3ed1ab5b31de2e0d07dc2. Arquivo completo analisado; regra particular.
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