ENTRY POINTUnder review

F040FMP

User Function F040FMP()

Complements recording of the FUMIPEQ receivable. Documented purpose and a plan to validate the entry point in the target environment.

F040FMPFINXFINFUMIPEQ

01 · OVERVIEW

Overview

The official Financeiro P12 index associates F040FMP with MATXATU/FINXFIN and complementary recording of the FUMIPEQ receivable; its specific documentation is under construction. (TOTVS, n.d., ref. 1) The settlement entry point list states the same purpose. (TOTVS, n.d., ref. 2) We did not locate sufficient public documentation to confirm the call, arguments or return value. The syntax below is only the function declaration used by the editorial example; it is not a transcription of the standard call. This page is under review. Full source access was restricted and the example has not been compiled or run in Protheus.

02 · SYNTAX

Syntax

User Function F040FMP()

Parameters

Entry point context

UndocumentedContext to confirm

The index does not specify arguments, PARAMIXB, array positions or available aliases. Missing documentation does not establish that execution context is absent.

Return value

The required return value and its effect are unconfirmed. The bare Return only ends the observation example; it must not be adopted as a production contract.

03 · PRACTICAL EXAMPLE

Observe entry point execution in a test environment

#Include "Protheus.ch"

User Function F040FMP()
    // Only observes execution: it neither writes receivables nor changes context.
    // Transaction placement and return requirements still need confirmation.
    ConOut("F040FMP: execution observed in test environment")
Return

Expected result

If the scenario and release invoke F040FMP, the console will record execution. The message does not confirm correct receivable generation, commit placement or return compatibility. If it is absent, investigate the scenario, RPO and entry point availability before concluding that the entry point does not exist.

BEST PRACTICES

Before implementing a rule, confirm the F040FMP call, received context and caller handling of the return value in the target release.
Editorial test plan: reproduce an operation generating a FUMIPEQ receivable in a test database; record standard results before activating diagnostics.
Compare receivables, amounts and invocation counts for the same scenario with and without customization. Use test data and avoid logging identifiable financial data.
If the environment supports change, deletion or reprocessing scenarios, test them separately and record observed behavior without assuming that they all invoke this entry point.
Once the contract is confirmed, replace diagnostics with the required rule, preserve any work areas used and document release and patch.

COMMON PITFALLS

Do not copy nSavRec, PARAMIXB or return behavior from F040FET, F040FAC or F040FAB: similar names do not establish identical contracts.
Do not treat this entry point as a FUMIPEQ calculation, cancellation or authorization mechanism without caller evidence.
Do not assume that recording has been committed, SE1 is selected or a record is locked.
The console message is an editorial diagnostic, not a functional implementation or proof of validation.