Parameters
Protheus can use standardized or specific configurations called parameters in its routines.
A parameter is a variable that works as a key element in some procedure execution. According to its content, different results are possible.
All variables are started by MV_ prefix and act on several operations in the system as, for example, the MV_ESTADO variable that identifies the State acronym of the system user company for calculating the ICMS.
TOTVS Product Developer uses some parameters that are common to other system environments. If they are changed, the new content is considered for other environments. Some parameters are only generic configurations as the company standard currency.
See the list of the specific parameters of TOTVS Product Developer environment as follows:
Parameter |
Description |
Default Content |
MV_DPRAPFT |
It indicates the budget approval. 0 – Version Approval; 1 – Version Approval. |
|
MV_DPRFICH |
Yes - allows you to enter the technical information of a product, helping in the product identification. |
|
MV_DPRHIST |
Yes - it indicates it is possible to maintain the version history, making impossible to reversion a version already released for engineering. |
|
MV_DPRLIST |
Yes – indicates it is necessary the check-list of the version criteria has been done so it can be approved/released. |
|
MV_DPRESTR |
It indicates the interval that will be suggested for the component code. |
|
MV_DPROPER |
It indicates the interval that will be suggested for the operation code. |
|
MV_DPRPROT |
It indicates the Prototype product code, always suggested in the developed product creation. |
|
MV_DPRQIP |
It indicates that you must have Script for Process Specification. |
|
MV_INTDPR |
It indicates if the existing integration is with Datasul or with Protheus or if there is not integration. 0 – Do not integrate; 1 – Protheus; 2 – Datasul. |
|