ENTRY POINTUnder review

F430PORT

User Function F430PORT()

Defines the bank-data source used in CNAB return settlement.

F430PORTFINA430

01 · OVERVIEW

Overview

The specific page describes one call per process, no parameters: .T. uses the title’s bank bearer; .F. uses the return bank. The FINA430 functional page describes .T. with borderô fields EA_PORTADO, EA_AGEDEP and EA_NUMCON; verify the actual selected account in the release. Mario Antonaccio’s GitHub example asks the operator whether to use the borderô account and returns a logical value. Its Itaú comment describes a local rule, not a universal restriction. (Refs. 1–5)

02 · SYNTAX

Syntax

User Function F430PORT()

Return value

Logical: .T. selects the bearer/borderô source described in the sources; .F. the return bank.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F430PORT()
    // Editorial adaptation of TOTVS and Mario Antonaccio examples.
    // Interactive flow only; do not display a dialog in a job.
    Local lBearer := MsgYesNo("Use the bearer/bordero account?", "CNAB return")
Return lBearer

Expected result

Teaching proposal with behavior described in comments. Verify the context before compiling in a test environment. Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

04 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA430.PRX - FA430GER() -> LALTPORT := EXECBLOCK("F430PORT",.F.,.F.)

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 dialog below is intended for interactive execution. For unattended processing, define an explicit rule without MsgYesNo. Verify bank, branch, account and generated movement in both branches.
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.