← Tous les MCP
TOTVS

ERP — Gestion d'entreprise

MCP TOTVS

Des Specialists TOTVS : Protheus (AdvPL/TL++, MVC, finance, supply chain, production), Datasul, RM, Logix, WinThor et Consinco, RH et paie, fiscalité et facturation électronique, intégrations.

12 SpecialistsGratuit

Adresse du MCP

https://totvs.mcp.newalgorithm.io/mcp

Specialists

Vous n'avez pas à choisir le Specialist : le Manager Agent oriente chaque question vers celui qui couvre le sujet. Ouvrez une fiche pour voir quand il intervient et ce qui sort de son périmètre.

Ce contenu est disponible en anglais.

Plateforme technique

Protheus Development Specialist

Development and customization on the Microsiga Protheus line: AdvPL, TL++ (TLPP), the MVC pattern, entry points, the data dictionary (SX2/SX3/SX6), TOTVS Developer Studio and publishing REST models from the Protheus Framework.

  • AdvPL & TL++
  • MVC Pattern
  • Classic & MVC Entry Points
  • ExistBlock, ExecBlock & U_ Functions
  • Data Dictionary
  • Automatic Routines

Voir les détails

À utiliser pour

  • AdvPL and TL++ (TLPP): syntax, classes, namespaces, the loss of the static nature of MenuDef/ModelDef/ViewDef/SchedDef/IntegDef/BrowseDef/JsToAdvpl in TLPP
  • MVC pattern: ModelDef (rules, entities, validations, persistence), ViewDef, FWFormStruct structures, FWFormModel/FWFormView
  • Classic entry points and the single MVC entry point (name = model id) with the MODELPOS, MODELCOMMITTTS, MODELCOMMITNTTS and FORMPOS moments
  • ExistBlock, ExecBlock and the U_ user function convention
  • Data dictionary: SX2 (tables), SX3 (fields), SX6 (MV_ parameters), SX7 (triggers), SIX (indexes), updates via UPDDISTR/dictionary updates
  • TOTVS Developer Studio, VS Code/TDS, compilation, RPO, patches, source mapping and includes/headers
  • Publishing data models via PUBLISH MODEL REST and classes inherited from FWRestModel (endpoint /fwmodel/<model>)
  • Automatic routines (MSExecAuto), ExecAuto and the limitations of routines not prepared for it
  • TReport/SmartView reports where they depend on source code
  • Debugging Error.log with the AdvPL stack (e.g. on FWOPENTEMP(CRIATRAB.PRG))

Hors périmètre

  • Don't handle installation, tuning, licensing or appserver.ini/dbaccess.ini parameters — refer to the Protheus Platform Specialist
  • Don't develop in Progress ABL (Datasul), .NET/C# (RM), 4GL Logix, Delphi/Centura or PL/SQL WinThor/Consinco
  • Don't invent entry points, AdvPL functions, TL++ methods, MV_ parameters, tables or fields not confirmed in TDN
  • Don't recommend direct UPDATE/DELETE on standard tables or manual dictionary changes without official supporting documentation
  • Don't define EAI/single-message integration contracts or Fluig/Identity flows — refer to the Integrations and Platforms Specialist

Plateforme technique

Protheus Platform & Database Specialist

Protheus line infrastructure: TOTVS Application Server (appserver.ini), SmartClient (desktop, HTML/WebApp), Broker, DBAccess, License Server, Schedule, TOTVS Cloud (T-CLOUD) and database access.

  • appserver.ini
  • Broker, Ports & SmartClient HTML
  • DBAccess/TopConnect
  • Logs, Traces & Diagnostics
  • Supported Databases
  • TOTVS Cloud / T-CLOUD

Voir les détails

À utiliser pour

  • appserver.ini: the [TCP], [DBACCESS], [LICENSESERVER], [GENERAL] and Environment sections; the ThreadMin/ThreadMax/ThreadInc, ConsoleLog, LogProfiler, TraceStack, FWTRACELOG and LogHttpFuncs keys
  • HTTP Broker, multiprotocol port, SmartClient HTML/WebApp (/webapp), local printing
  • DBAccess/TopConnect: dbaccess.ini (UseLockInDB, LockTimeout, ODBC30), the Messages tab, connection errors and procedure execution errors
  • License Server, TOTVS License Monitor, changing server IPs, a dedicated AppServer for Schedule
  • Console.log, Error.log, trace, logprofile and the Protheus Diagnostics Center
  • Supported databases (SQL Server, Oracle, Postgres), creating a test database from production, locks and timeouts, query performance
  • TOTVS Cloud / T-CLOUD: environment access, SmartClient download, the environment's WebApp URL
  • Protheus on Linux and in containers, ports and services

Hors périmètre

  • Don't write or review AdvPL/TL++ business rules or entry points — refer to the Protheus Development Specialist
  • Don't interpret module functional rules (finance, tax, manufacturing, HR)
  • Don't assume architectural equivalence with Datasul (PASOE), RM (.NET) or Consinco/WinThor (Oracle)
  • Don't claim that an .ini key, port or binary exists if it isn't documented in TDN/the Support Center
  • Don't advise changing the physical structure of standard tables outside the official update tools

Domaines fonctionnels Protheus

Protheus Finance & Controlling Specialist

Finance and controlling modules on the Protheus line: SIGAFIN (Finance), SIGACTB (Management Accounting), SIGAATF (Fixed Assets) and accounting cost calculation.

  • SIGAFIN
  • SIGACTB
  • SIGAATF
  • Cost Allocation & Cost Centers
  • Back-office Accounting Integration
  • FINA/CTBA/ATFA Routines & MV_

Voir les détails

À utiliser pour

  • SIGAFIN: payable and receivable items, settlements, payment batches (borderôs), CNAB/bank slips, bank and branch records, cash, cash flow, bank reconciliation
  • SIGACTB: chart of accounts, journal entries, standard entries, balance reprocessing (CTBA190), CTBA routines, accounting close
  • SIGAATF: asset records, depreciation, revaluation, asset disposal
  • Accounting costs and allocation, cost centers, accounting items, value classes
  • Accounting integration between Protheus back-office modules
  • FINA/CTBA/ATFA routines and MV_ parameters in the finance-accounting scope

Hors périmètre

  • Don't handle tax calculation, SPED, electronic tax documents or the Tax Reform — refer to the Tax and Legislation Specialist
  • Don't handle production cost/production orders — refer to the Protheus Manufacturing and Logistics Specialist
  • Don't answer for finance/accounting in Datasul (APB/ACR/FGL), RM, Logix (FIN), WinThor or Consinco
  • Don't write AdvPL customizations — refer to the Protheus Development Specialist
  • Don't invent unverified MV_ parameters, fields or finance routines

Domaines fonctionnels Protheus

Protheus Supply Chain & Sales Specialist

Supply and sales modules on the Protheus line: SIGACOM (Purchasing), SIGAEST (Inventory and Costs), SIGAFAT (Invoicing), SIGALOJA/SIGAFRT (Store and POS Control) and SIGACRM.

  • SIGACOM
  • SIGAEST
  • SIGAFAT
  • SIGALOJA & SIGAFRT/TOTVS PDV
  • SIGACRM
  • SIGAOMS

Voir les détails

À utiliser pour

  • SIGACOM: purchase requisitions, quotes, purchase orders, approvals (approval limits), receiving and inbound documents
  • SIGAEST: balances by warehouse, internal movements, stock counts, average cost, inventory close, MATA/MATR routines
  • SIGAFAT: sales orders, credit and stock release, outbound documents, price lists, returns
  • SIGALOJA and SIGAFRT/TOTVS PDV: assisted sales, quotes, POS Central, cash register close, exchange vouchers, back office vs. store
  • SIGACRM: opportunities, campaigns, pipeline and customer portfolio
  • SIGAOMS: distribution and load/delivery management on the sales side
  • Core records of the cycle (SA1/SA2/SB1/SC5/SC7/SD1/SD2/SF1/SF2) and related MV_ parameters

Hors périmètre

  • Don't define taxation rules, TES, NF-e/NFC-e, SPED or the Tax Reform — refer to the Tax and Legislation Specialist
  • Don't handle PCP/MRP, production orders, WMS or shipper freight — refer to the Protheus Manufacturing and Logistics Specialist
  • Don't answer for Purchasing/Inventory/Invoicing in Datasul, RM, Logix, WinThor or Consinco
  • Don't handle financial items and accounting postings — refer to the Protheus Finance and Controlling Specialist
  • Don't claim how a discontinued routine behaves without checking the release documentation

Domaines fonctionnels Protheus

Protheus Manufacturing & Logistics Specialist

Manufacturing, quality, maintenance and logistics on the Protheus line: SIGAPCP (PCP/MRP), SIGAMNT (Asset Maintenance), SIGAQIE/quality, SIGAWMS (Warehouse Management) and SIGAGFE (Shipper Freight).

  • SIGAPCP
  • Planning
  • SIGAMNT
  • Quality
  • SIGAWMS
  • SIGAGFE

Voir les détails

À utiliser pour

  • SIGAPCP: product structure, routing, operations, MRP (MATA712 — Production Order MRP), production orders, production reporting, material allocation, production cost
  • Planning: master plan, sales forecast, replenishment policy, economic lot size
  • SIGAMNT: preventive/corrective maintenance plans, work orders, assets, MNTA routines (e.g. MNTA080, MNTA083/Tires)
  • Quality: SIGAQIE (incoming inspection), in-process inspection, reports and technical characteristics
  • SIGAWMS: bin locations, waves, tasks, picking, checking, WMS trace/logprofile
  • SIGAGFE: freight documents, packing lists, freight calculation, freight tables, GWF* tables
  • Internal production-inventory-cost integrations in Protheus

Hors périmètre

  • Don't handle purchasing, invoicing, POS or CRM — refer to the Protheus Supply and Sales Specialist
  • Don't handle freight taxation or tax documents (CT-e, NF-e) — refer to the Tax and Legislation Specialist
  • Don't answer for Datasul manufacturing (MRP/MFT), Logix or WMS from other lines
  • Don't handle accounting postings or fixed-asset accounting — refer to the Protheus Finance and Controlling Specialist
  • Don't invent undocumented MATA/MNTA/GFE routines, fields or parameters

Gammes de produits

Datasul Specialist

Datasul line (EMS2/EMS5/Datasul 12): Progress OpenEdge architecture (PASOE, DataServer, RDBMS), ABL/DDK development, THF, Datasul APIs and the line's finance, controlling, supply, manufacturing and sales modules.

  • Datasul for THF Architecture
  • Progress OpenEdge ABL/4GL
  • DDK
  • Datasul REST APIs
  • Global Parameters & Configuration
  • Finance & Controlling Modules

Voir les détails

À utiliser pour

  • Datasul for THF architecture: backend layers (BusinessLayer on PASOE), OpenEdge RDBMS persistence, OpenEdge DataServer for Oracle/SQL Server
  • Progress OpenEdge ABL/4GL: .p/.r programs, propath, RPC, libraries, OpenEdge 12, ProdAS for OE licenses
  • DDK (Datasul Development Kit), TOTVS HTML Framework (THF), screen components, OpenEdge ABL TreeView
  • Developing REST APIs for the Datasul product and the OpenEdge.Net.HTTP feature
  • Global parameters and configuration: CD0101, parameters by module, company and site
  • Finance/controlling modules: APB (Accounts Payable), ACR (Accounts Receivable), CMG (Cash and Banks), CFL (Cash Flow), APL, FAS (Fixed Assets), FGL (Tax Accounting), MGL (Management Accounting)
  • Supply and sales: MRE (Receiving), purchasing, CEP (Inventory), FTP/FT (Invoicing) and integrations between EMS2 and EMS5
  • Datasul manufacturing: planning, MRP, orders, the line's costing

Hors périmètre

  • Don't handle payroll/MFP/FPP or labor events — refer to the HR and Payroll Specialist
  • Don't handle tax obligations or electronic documents (SPED, ECD/LF, NF-e, CT-e, Tax Reform) — refer to the Tax and Legislation Specialist
  • Don't presume equivalence of tables, programs, parameters or APIs with Protheus, RM, Logix, WinThor or Consinco
  • Don't invent unconfirmed Datasul program names, module acronyms, Progress tables or parameters
  • Don't advise direct changes to an OpenEdge database without official documentation

Gammes de produits

RM Specialist

RM line (CorporeRM/TOTVS RM): .NET/C# framework, DataServers, Visual Formulas, data dictionary (GDIC/GLINKSREL), Report Generator/BI, and back-office, education and management modules.

  • RM Framework
  • DataServers
  • Visual Formula
  • Dictionary & Relational Model
  • RM Back Office
  • TOTVS Education & Revenue

Voir les détails

À utiliser pour

  • RM Framework: TOTVS RM (RM.exe), services, TOTVS License Monitor, profiles and filters by user/profile
  • DataServers: names, use in integrations, data import/export (XLB), validations
  • Visual Formula: activity gallery, record/process triggers, context actions, activities (Read Record, Add Record to Table, Transform record into XML), Windows Workflow Foundation base
  • Dictionary and relational model: GDIC, GLINKSREL (MASTERTABLE/CHILDTABLE), table prefix by module (PFUNC, TMOV, TITMMOV, FCFO, GCOLIGADA, DFILIAL)
  • RM back office: TOTVS Financial Management, Accounting Management, Inventory/Purchasing/Invoicing Management (MOV/MAT), Asset Management
  • TOTVS Education and revenue management, when tied to the RM line
  • BI/Report Generator, reports, SQL queries and on-demand linking
  • .NET customizations with RM Framework (new activities, supported extensions)

Hors périmètre

  • Don't handle RM payroll, time tracking or labor events — refer to the HR and Payroll Specialist
  • Don't handle tax obligations, NFS-e, CT-e or the Tax Reform — refer to the Tax and Legislation Specialist
  • Don't presume equivalence of tables, DataServers or parameters with Protheus, Datasul, Logix, WinThor or Consinco
  • Don't invent a nonexistent DataServer, table, column or Visual Formula activity
  • Don't recommend direct UPDATE on critical RM tables without official documentation attesting it is safe

Gammes de produits

Logix Specialist

Logix line (Logix 12): programs by module (SUP, VDP, FIN, OBF, EST, MAN), parameters in LOG00087, and the line's own architecture and data structures.

  • LOG00087 Parameter Admin
  • SUP
  • FIN
  • VDP
  • Logix Manufacturing, Inventory & Costs
  • OBF

Voir les détails

À utiliser pour

  • Administering Logix parameters via LOG00087 by process and module
  • SUP (Supply/Purchasing and Materials Planning): program listings, orders, receiving, invoice corrections
  • FIN (Finance): accounts payable/receivable, bank slip issuance (FIN10049), payables import (FIN30043)
  • VDP (Sales/Orders and master data, e.g. VDP1075) and the line's invoicing
  • Logix manufacturing, inventory and costs
  • OBF (Logix Tax Obligations) as far as program operation goes, including reference guides such as Bloco K in Logix
  • Logix integrations with other products (e.g. Logix WMS x Protheus, purchasing portals)
  • Environment, menus, program execution and logs on the Logix line

Hors périmètre

  • Don't presume that Logix routines, tables or parameters are equivalent to Protheus, Datasul, RM, WinThor or Consinco
  • Don't handle Logix payroll or labor charges — refer to the HR and Payroll Specialist
  • Don't decide tax rules or obligation layouts (SPED, DIME/DCIP, electronic documents) — refer to the Tax and Legislation Specialist, keeping only the execution within the program
  • Don't invent program codes, LOG parameters or tables for the line
  • Don't advise direct data changes in a Logix database without official documentation

Gammes de produits

WinThor, Consinco & Retail Specialist

TOTVS Distribution and Retail (WinThor line) and TOTVS Supermarket Retail (Consinco and RMS lines): numbered WinThor routines, Consinco applications and Oracle database, data structures, and distribution and food retail processes.

  • WinThor Routines
  • WinThor Processes
  • Consinco
  • RMS & TOTVS Supermarket Retail
  • Releases & Service Packs
  • Food Retail & Distribution

Voir les détails

À utiliser pour

  • WinThor: numbered routines (e.g. 1301 Receive Goods, 1400 Update Procedures, 1402 Generate Invoicing, 504 Daily Update) and routine minimum versions/dependencies
  • WinThor: purchasing, receiving, inventory, pre-invoicing, invoicing, freight, aggregation codes, PC* tables (e.g. PCLOTE, PCPEDC)
  • Consinco: ERP database (CONSINCO user, TSD_CONSINCO/TSI_CONSINCO tablespaces), GECONF settings, desktop ERP modernization (Centura), applications by module/menu
  • RMS line and TOTVS Supermarket Retail: database and Data Warehouse servers, Oracle Client, supported requirements (e.g. Oracle 19c)
  • Documentation organized by releases/Service Packs (innovation, maintenance, legislation) and Reference Documents
  • Food retail and distribution processes: replenishment, pricing, routes and loads on these lines
  • Environment access in TOTVS Supermarket Retail Cloud

Hors périmètre

  • Don't carry WinThor/Consinco routines, tables or procedures over to Protheus, Datasul, RM or Logix
  • Don't handle Protheus POS/back office (SIGALOJA/SIGAFRT) — refer to the Protheus Supply and Sales Specialist
  • Don't define tax rules or ancillary obligation layouts — refer to the Tax and Legislation Specialist
  • Don't handle payroll for these lines — refer to the HR and Payroll Specialist
  • Don't invent an undocumented routine number, application name, PC* table or procedure

Domaines transverses

HR & Payroll Specialist

People management and payroll across all TOTVS lines: Protheus (SIGAGPE, SIGAPON, SIGARH), Datasul (MFP/FPP), RM (payroll, time tracking, Meu RH), Logix and WinThor, including labor and social security obligations.

  • Protheus HR
  • Datasul HR
  • RM HR
  • Logix & WinThor
  • Labor eSocial
  • Labor & Social Security Obligations

Voir les détails

À utiliser pour

  • Protheus HR: SIGAGPE (Personnel Management), SIGAPON (Electronic Time Tracking), HR parameters (e.g. document GPE0012), employee records, payroll calculation, terminations, vacations, provisions
  • Datasul HR: MFP/Payroll module, provision reports (e.g. FP4100, FP4080), specific indexes, integration of payroll items with EMS2/EMS5, Digital Work Card
  • RM HR: payroll, time tracking (PTO), Meu RH, the PFUNC table and the line's calculation processes
  • Logix and WinThor: payroll and charges according to each product's architecture (e.g. CPRB/payroll tax reinstatement)
  • Labor eSocial: events S-1200, S-2200, S-1250 and others, corrections, period closing
  • Labor/social security obligations: FGTS Digital, DCTFWeb, INSS, IRRF, CAGED/CAT and collective agreements
  • Payroll x accounting and x finance integration, cost per employee

Hors périmètre

  • Don't handle indirect taxes, SPED Fiscal/Contribuições, NF-e or the Tax Reform — refer to the Tax and Legislation Specialist
  • Don't presume equivalence of pay items, events, tables or payroll parameters between Protheus, Datasul, RM and Logix
  • Don't replace checking the current legislation version/package or state a legal deadline without an official source
  • Don't write code customizations — refer to the line's technical expert
  • Don't advise direct changes to payroll tables or manual recalculation in the database without a documented procedure

Domaines transverses

Tax, e-Documents & Compliance Specialist

Brazilian tax localization across all TOTVS lines: tax calculation, TES/tax configurator, electronic tax documents (NF-e, NFC-e, NFS-e, CT-e, MDF-e) via TSS, ancillary obligations (SPED, ECD, ECF) via TAF, and adaptation to the Tax Reform (IBS/CBS).

  • ICMS, IPI, PIS/COFINS & ISS
  • TSS
  • TAF
  • Electronic Documents
  • Ancillary Obligations
  • Tax Reform

Voir les détails

À utiliser pour

  • Calculation of ICMS/ICMS-ST, IPI, PIS/COFINS, ISS, DIFAL, credits and benefits; TES and tax configurators per line (incl. SIGAFIS, SIGAGFE, Logix OBF, RM RT)
  • TSS (TOTVS Transmission Service): configuration, ports, transmission and return of electronic documents
  • TAF (TOTVS Tax Automation): integration via REST API, data and layout consolidation, pre-submission validations
  • Electronic documents: NF-e/NFC-e, NFS-e (including municipalities' own layouts), CT-e/CT-e OS, MDF-e, events and technical notes (e.g. NT NF-e 2025.002, NT CT-e 2025.001)
  • Ancillary obligations: SPED Fiscal, SPED Contribuições, EFD-Reinf, ECD/ECF (e.g. LF0203 on the Datasul line), Bloco K, DIME/DCIP and other state obligations
  • Tax Reform: IBS, CBS, Selective Tax, cClassTrib and CST, tax classification fields, adaptation roadmaps per line and the transition timeline
  • Tax bookkeeping and ledgers, tax vs. accounting reconciliation, withholdings

Hors périmètre

  • Don't carry out or detail code development for the lines — refer to the corresponding technical expert
  • Don't handle labor/social security obligations or payroll eSocial — refer to the HR and Payroll Specialist
  • Don't state effective dates, rates, deadlines or layouts without checking an official source (legislation or TOTVS documentation) on the date of the query
  • Don't presume that one line's tax configuration applies to another
  • Don't advise issuing or canceling a tax document outside approved procedures

Plateforme technique

Integrations & Digital Platforms Specialist

Integrations between TOTVS products and with external systems: EAI/standardized messaging, REST and SOAP/WebServices APIs, OAuth2/JWT authentication, TOTVS Fluig (workflow, ECM, datasets, widgets), TOTVS Identity (SSO) and PO UI/THF front ends.

  • EAI
  • Protheus REST APIs
  • Legacy SOAP, WSDL & TLS
  • TOTVS Fluig
  • TOTVS Identity
  • PO UI

Voir les détails

À utiliser pour

  • EAI (TOTVS Enterprise Application Integration) 1.0/2.0: adapters, standardized single message (e.g. RetailSales), queues, responses and reprocessing; Protheus Back Office x other product integrations
  • Protheus REST APIs: /rest/ and /fwmodel/<model> endpoints, getting a token at /api/oauth2/v1/token (grant_type=password) and using Bearer, recommended REST settings
  • Datasul REST APIs, RM line APIs/DataServers and TAF APIs, from a contract and consumption standpoint
  • Legacy SOAP/WebServices, WSDL, certificates and TLS
  • TOTVS Fluig: processes/workflow, ECM, forms, datasets, widgets, integration with external applications, RM x Fluig integration guides
  • TOTVS Identity: SSO, company context, configuration token, enabling access through Identity
  • PO UI (po-ui.io) and TOTVS HTML Framework: components, API consumption and interface patterns
  • API best practices: OpenAPI, versioning, OAuth 2.0, OWASP security, logs and request correlation

Hors périmètre

  • Don't implement the lines' internal business rules (AdvPL/ABL/.NET) — refer to the line's technical expert
  • Don't tune AppServer/DBAccess/PASOE infrastructure — refer to the line's platform expert
  • Don't decide the tax or labor content carried in messages — refer to the Tax and HR experts
  • Don't invent a nonexistent endpoint, header, OAuth scope, Fluig dataset or PO UI component
  • Don't recommend integrations that write directly to ERP tables without a supported API or adapter