• A Confluence está sendo executada atualmente com todos os plugins que não são do sistema desabilitados. Pode haver perda de algumas funcionalidades
Páginas filhas
  • Sales Orders - MATA410 - Billing - P12

Index

Purpose

Formalizing the sale of products or services between the parties involved (supplier and customer), and in this way establish the products or services sold associated with the commercial conditions in which the sale is made, involving prices, discounts, and payment terms, among others.

It is also based on the Sales Order that the commissioning rules for salespeople are established, and the information that allows the correct calculation of taxes that are attributed to the sale itself is obtained.

Adding the Sales Order is a mandatory step when it involves Outgoing Documents and corporate sales (billing). Also, this document allows other outgoing documents to be generated, such as Purchase Returns, Tax Complements, and others.

Mental Map

This diagram contains information on the routine resources.

Also, check the preconditions required by the routine and the parameter settings.

Sales Orders

When a sales order is added to the system, it is still not ready to be billed or to generate the outgoing document. For this to happen, the Sales Order must be released, and this is done using the Order Release routine.

Operations for Sales Orders

The following is a description of operations related to Sales Orders: 

Sales Orders - Types

The information that sets the Sales Order function is its type, which is treated individually as follows: 

Specific conditions involving Sales Orders 

Invoices - Examples for issuance/configuration

Main Fields 

Source Fragmentation

Related Content

Other Information


Statute no. 13,709 - General Personal Data Protection Law of Brazil (LGPD)

In order to adapt the Protheus® system to the General Personal Data Protection Law, we needed to adapt the presentation of routine data in order to carry out the treatment of sensitive and/or personal data using the processes of Access Control and Audit Log.


  • Access Control

Define if the user or a group of users has permission to access/view the sensitive personal data available on the screen of the routines and/or reports when applicable.

The System Admin is the responsible party for establishing whether the information control rules will be applicable to a single user or a group of users. The configuration of the access to sensitive and personal data for users and/or user groups is available in the Configurator (SIGACFG) module through accesses 192 and 193 (Accesses x Routine Relationship).

For further details on the Security Policy, click here.


  • Audit Log

Use this feature to audit updates to the Data Dictionary, to the Users File, and to access authentications to routines with sensitive and/or personal fields, as well as the possible access rejections to such data.

For further details, refer to the Audit Rules chapter in the Security Policy.

Protheus® System makes some routines available for the generation of the Audit Logs. You can get the procedures for configuring and generating these reports using the Log and Audit Routines.