Usina BRAdvPL Guide
Sign in
← All topics
ENTRY POINTPublished

M110EXIT

M110EXIT() --> Logical

M110EXIT runs in the Save and completion area of MATA110, in A110Exit.

Entry pointsMATA110SIGACOMPurchase RequestExecBlockSave and completion
01 · OVERVIEW

Overview

M110EXIT is an Entry Point identified in the analyzed MATA110 technical documentation. The call occurs in A110Exit, in the Save and completion area. Confirm its contract against the release and patch used by the environment before implementing a customization.

02 · SYNTAX

Syntax

M110EXIT() --> Logical

Parameters

PARAMIXB
ContextualOptional

Its structure depends on the call site. Confirm the arguments sent by the target release before reading array positions.

Return value

Logical.

03 · PRACTICAL EXAMPLE

Initial validation structure

#Include "TOTVS.ch"

User Function M110EXIT()
    Local uRet := Nil

    // Confirm PARAMIXB and the return value in the target release documentation.

Return uRet
Expected result

Minimum structure: adjust parameters and return value only after confirming the call site in the environment.

BEST PRACTICES
  • Validate PARAMIXB and the return value in the target environment.
  • Preserve work areas used by the customization.
  • Test creation, edit, deletion, approval, and automatic execution separately when applicable.
COMMON PITFALLS
  • Do not assume a point called by several operations always receives the same state.
  • Do not return a type different from the one consumed by the caller.
  • Do not rely on private variables without validating the context.

Related content

REFERENCES
  1. MATA110 — Purchase Request technical documentation. Reference dated Aug. 15, 2019; call identified in A110Exit.
  2. TOTVS. Purchase Request (MATA110 — SIGACOM).
Status
Published
Page created on
Last reviewed on
Original language
Portuguese
Reviewed by
Usina.BR
0 approved comment(s)

Comments

There are no approved comments yet.

Sign in with Google or Microsoft to comment.

Powered by Usina Docs · Alpha