01 · OVERVIEWOverview
The official index associates F040FAC with supplementary recording of the FACS title in accounts receivable. Its row lists MATXATU and FINXFIN; the specific entry remains marked “Em construção” (under construction). (TOTVS, s.d., ref. 1) The MTFUNDOS manual, updated on August 8, 2022, identifies FACS as Fundo de Apoio a Cultura da Soja. This historical context explains the acronym without establishing its current fiscal applicability. (TOTVS, s.d., ref. 4) FINA040 documentation includes the “Vlr. FACS” and “Parc. FACS” fields. They help identify the topic in the functional process but do not prove which fields or aliases will be available inside this entry point. (TOTVS, s.d., ref. 5) The public listing shows FINXFIN calling ExecBlock("F040FAC", .F., .F., nSavRec). (TOTVS, s.d., ref. 2) The generic ExecBlock mechanism exposes its fourth argument through PARAMIXB rather than passing it directly through the User Function signature. (TOTVS, s.d., ref. 3)
03 · PRACTICAL EXAMPLEDiagnostic example
#Include "Protheus.ch"
User Function F040FAC()
Local uContext := Nil
// The variable may reflect a scalar value; do not assume an array.
If Type("PARAMIXB") <> "U"
uContext := PARAMIXB
EndIf
// In a test environment, log only the type, without title data.
ConOut("F040FAC: context type = " + ValType(uContext))
Return
Expected resultWhen the routine actually invokes the entry point, the console should show the received type without exposing the context value. If nothing appears, first check compilation, RPO, environment, and scenario. No message does not prove that the entry point was discontinued.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.