Usina BRAdvPL Guide
Sign in
← All topics
HISTORICAL SOURCEPublished

Protheus 7.10 entry points

User Function <nome-do-ponto>() · PARAMIXB · Return <valor-esperado>

Historical catalog of 1,041 unique entry points across 21 Protheus 7.10 modules.

Entry pointsProtheus 7.10ExecBlockPARAMIXBHistoryCustomization
01 · OVERVIEW

Overview

Dated January 20, 2003, this 243-page document records the routine, ExecBlock identifier, execution moment, parameters, notes and expected return for Protheus 7.10 entry points. It contains 1,133 occurrences, 1,041 unique identifiers and 221 program sections. Treat it as a historical map and verify each item against the current TDN and the source of the release in use.

02 · SYNTAX

Syntax

User Function <nome-do-ponto>() · PARAMIXB · Return <valor-esperado>

Parameters

SIGAFAT, SIGACOM e SIGAFIS
MódulosOptional

Billing, Purchasing and Tax.

SIGAPMS, SIGAGPE e SIGAPON
MódulosOptional

Project management, Human Resources and Time Attendance.

SIGATRM, SIGARSP e SIGATMK
MódulosOptional

Training, Recruitment and Telemarketing.

SIGAEST, SIGAPCP e SIGAQNC
MódulosOptional

Inventory/Costs, Production Planning and Nonconformity Control.

SIGAQDO, SIGAQIP, SIGAQIE e SIGAQMT
MódulosOptional

Quality-related modules.

SIGAFIN, SIGACON e SIGAATF
MódulosOptional

Finance, Accounting and Fixed Assets.

SIGATEC e SIGALOJA
MódulosOptional

Field Service and Store Control.

03 · PRACTICAL EXAMPLE

MT410BRW — historically listed and confirmed in TDN

#Include "TOTVS.ch"

User Function MT410BRW()
    Local aArea := GetArea()
    ConOut("Before displaying the sales-order browse")
    RestArea(aArea)
Return
Expected result

The 2003 document and current TDN place this entry point before the MATA410 browse.

04 · PRACTICAL EXAMPLE

Entry point returning logical

#Include "TOTVS.ch"

User Function M410ALOK()
    Local lPermite := .T.

    // Validação específica, testada e documentada.
    // .F. impede a alteração do pedido no contexto histórico.
Return lPermite
Expected result

The exact contract must be confirmed for the release in use.

05 · PRACTICAL EXAMPLE

Safe PARAMIXB reading

User Function ExPonto()
    Local xValor := NIL

    If ValType(PARAMIXB) == "A" .And. Len(PARAMIXB) >= 1
        xValor := PARAMIXB[1]
    EndIf

Return xValor
Expected result

Validation avoids assuming that PARAMIXB is always a populated array.

BEST PRACTICES
  • Use the document to discover historical names, not as proof of current availability.
  • Confirm source routine, execution moment, PARAMIXB and return type in the current TDN.
  • Search the supported release source and test in a controlled environment when current documentation is unavailable.
  • Preserve work areas when navigating aliases.
  • Return exactly the documented type.
  • Record release, purpose and expected behavior for each customization.
COMMON PITFALLS
  • The source dates from 2003; routines and entry points may have changed or disappeared.
  • The original contains duplicates and typographical inconsistencies.
  • PARAMIXB has no universal structure.
  • An incorrect customization may block critical processing.
  • Review includes, transactions, filters and security before adapting historical examples.

Related content

REFERENCES
  1. Entry Points — AP 7 7.10. Database dated January 20, 2003. Supplied 243-page document; no author identified.
  2. TOTVS. Billing entry points — Protheus 12. TDN.
  3. TOTVS. MT410BRW. TDN.
  4. TOTVS. TLPP support in Protheus — entry points with ExistBlock and ExecBlock. TDN.
  5. MICROSIGA. Programming Manual. Collaborative document, file dated July 11, 2001. Historical reference.
Status
Published
Page created on
Last reviewed on
Original language
Portuguese
Reviewed by
Usina.BR