F300FLT
User Function F300FLT()Filters the record being processed in the former FINA300 SISPAG return flow.
Overview
The official notice describes F300FLT as a filter for the record being processed and lists no equivalent entry point in its migration table. SISPAG was discontinued on 2022-08-20; its replacement suite uses FINA430. (TOTVS, ref. 1) The community listing records IF !ExecBlock("F300FLT") in FA300PROCESSA. It demonstrates a negated condition but omits the IF body: it does not alone establish whether .T. or .F. discards, accepts or aborts the entire file. (Ref. 2)
Syntax
User Function F300FLT()Return value
The excerpt consumes the result through logical negation in IF. Each value’s consequence depends on the omitted conditional body; a complete acceptance/rejection contract was not established. (Ref. 2)
Read the legacy caller without inventing an implementation
// Caller excerpt, not a User Function: EURAI, P12.2210 (ref. 2).
// Observed context: FINA300.PRX / FA300PROCESSA().
If !ExecBlock("F300FLT")
// The consulted excerpt does not include the IF body.
// Do not infer the record effect of .T. or .F. from this alone.
EndIfShows how the community reference consumes the result. This commented analysis excerpt is not a ready entry point implementation. Example not compiled or run in Protheus.
- Do not invent Return .T. or Return .F. to fill the example: the operational consequence remains unconfirmed.
- The observed call has no fourth argument. Do not assume a positioned alias or a PARAMIXB layout.
- The official table lists no equivalent. This does not establish that the rule cannot be redesigned in FINA430.
- For legacy maintenance, inspect the complete FA300PROCESSA conditional body and test accepted records, excluded records and multiple-record files.
- Editorial test plan: compare standard and customized behavior in the described operations, inspect resulting records and record release and patch.
- Under review: sources and example checked against documentation; code not compiled or run in Protheus. Exact transaction position and target release behavior remain unconfirmed.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.