Usina BRAdvPL Guide
Sign in
← All topics
ENTRY POINTPublished

MT110COR

MT110COR() --> Array

MT110COR runs in the Entry, browse, and menu area of MATA110, in Mata110.

Entry pointsMATA110SIGACOMPurchase RequestExecBlockEntry, browse, and menu
01 · OVERVIEW

Overview

MT110COR is an Entry Point identified in the analyzed MATA110 technical documentation. The call occurs in Mata110, in the Entry, browse, and menu area. Confirm its contract against the release and patch used by the environment before implementing a customization.

02 · SYNTAX

Syntax

MT110COR() --> Array

Parameters

PARAMIXB
ContextualOptional

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

Return value

Array.

03 · PRACTICAL EXAMPLE

Initial validation structure

#Include "TOTVS.ch"

User Function MT110COR()
    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 Mata110.
  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