...
The advance payable of a contract must be directly made in Microsiga Protheus® environment via the routine Payment Order or Payment Order 2. Thus, it can be apportioned by projects, however, it is not automatically appropriated in TOP (TOTVS Works and Projects), since TOP (TOTVS Works and Projects) lists the apportionments by project of available advances and appropriates the relevant apportionments for contracts through a request via WebService when needed. Such advances become locked in Microsiga Protheus® and they can be unlocked again by TOP (TOTVS Works and Projects).
...
The advance receivable of a contract must be directly made in Microsiga Protheus® environment via the routine Miscellaneous Collections or Miscellaneous Collections 2. It can have its revenue apportioned, however, it is not automatically appropriated in TOP (TOTVS Works and Projects), since TOP (TOTVS Works and Projects) lists the apportionments by project of available advances and appropriates the relevant apportionments for contracts through a request via WebService when needed. Such advances become locked in Microsiga Protheus® and they can be unlocked again by TOP (TOTVS Works and Projects).
...
An advance with an apportionment locked by TOP (TOTVS Works and Projects) cannot be changed in Microsiga Protheus®.
The parameter MV_RMCCUST defines a standard Cost Center for integration because this information is mandatory in RM, but not in Microsiga Protheus®.
...
Procedures