F340DTFIN
User Function F340DTFIN()Controls MV_DATAFIN validation in payable compensation.
Overview
TDN documents .T. to validate the MV_DATAFIN date and .F. to ignore that validation. It does not change the parameter value. The P12.2210 listing shows calls in FA340CAN and FA340COMP; verify both flows. (Refs. 1–2)
Syntax
User Function F340DTFIN()Return value
Logical: .T. checks MV_DATAFIN; .F. skips that check.
Editorial example based on documentation
#Include "Protheus.ch"
User Function F340DTFIN()
// TOTVS contract: .T. validates the date; .F. skips validation (ref. 1).
// Keeps the check without changing MV_DATAFIN.
Return .T.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.
Observed call and context
// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - FA340CAN() -> LVLDDTFIN := EXECBLOCK("F340DTFIN", .F., .F.)
// FINA340.PRX - FA340COMP() -> LVLDDTFIN := EXECBLOCK("F340DTFIN",.F.,.F.)The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.
- The example keeps .T. to retain documented validation. Bypassing requires an explicit rule; compare dates before, equal to and after the financial limit.
- 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.

Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.