You can add a Sales Order and link it to a contract when the parameter MV_CNPEDVE is set to .T. (True); thus, it is possible to perform the entire measurement process automatically using the data added to the Order. But the system requires that a Sales Contract without authorization control is already registered and effective.

Place the cursor in the Customer field and click F9, then follow the procedures described:

1. Select the branch and click OK to continue. Press F12 and view the parameter configuration screen. When needed, use the field help instructions.
2. To continue adding, click Add. This registration has a self-explainable filling-in. But, when necessary, follow the guidance provided in Main Fields.
3. Then, click Confirm to save the inclusion made.
4. The system will perform consistency verification before saving.
5. After this verification, the system allows you to perform releases of order, credit, and stock, up to the outgoing document generation.

When you access the routine, you can see the Sales Orders already registered and identify them quickly using the Caption.

See also the general features available in Other Actions.

To add a Sales Order with Product Grid, set the parameters as follows:

MV_GRADE set to .T. (True);

MV_MASCGRD set to the grid mask;

MV_GRDMULT set to the program that uses the multi-field grid, allowing the use of different values to the grid products, with price list;

1. It is possible to add a Sales Order when a Price List is already registered.
2. Note that, when entering the quantities in the grid, in the items registered on it, start Unit Price according to the list price.
3. Enter the other information and, after saving the information, note that field List (C6_PRUNIT) stores the list price of each item according to the field concept.
4. If the price of one of the items with a price list changes, the total value difference is displayed at the footer of the Order with a discount or increase, following the concept already found in the Sales Order.

1. This type of Sales Order inclusion with a discount at the header requires a Discount Rule, a Price List, and Payment Terms already registered.
2. Add a Sales Order by entering the Price List, and enter the discount(s) at the header of the Then, distribute the quantities on the grid.
3. Check the application of the discount according to the routine rule.
4. After saving, note that field List (C6_PRUNIT) stores the price list of each item according to the field concept and values calculated with the discount.

1. Adding a Sales Order with a discount on the item requires that the parameter MV_ARREFAT be set to round decimal places.
2. When adding the order, enter the grid quantities and apply the discount to the Sales Order item.
3. The discount percentage must be applied to each grid item.
4. The System does not allow unit price changes to any grid item because the discount percentage applies to all. No changes are allowed.
5. In this situation, the system displays an explanatory help.

1. For the correct functioning, previously register a group of optional items with the sale price.
2. Also, add a structure for one of the Product Grid items and correlate the structure items to the group of optional items.
3. Then, add a Sales Order and, when you enter the quantity for the item with the structure registered with optional items, the selection of the desired optional item is requested.
4. Observe that, after selecting it, the selling price defined in the record of the selected optional item is automatically added to the unit price.
5. If the unit price is changed, the system notifies the sum of the value of the selected optional item.

When you use this option, the shaded fields cannot be edited.

Adjust the information according to the instructions described in Main Fields.

See also the general features available in Other Actions.

Other Actions / Delete / Delete

After a Sales Order is created, its deletion is already possible as long as it has not been billed or released.

Check the status of the orders using the caption's indicative colors.

To use the option, follow these guidelines:

1. To delete a sales order, select the desired order and click Other Actions / Delete.
2. Check the data and confirm the deletion.

Other Actions / Delete / Residue

To use the option, follow these guidelines:

After you select the Sales Order and activate this option, the system deletes the existing residue, and, to the system, this Sales Order is now displayed as closed. 

Other Actions/Barcode

With this option, various products can be added in sequence without entering information for each item. After adding the items, enter the other mandatory data for each item to confirm the order.

To use the option, follow these guidelines:

1. Fill in the sales order header as instructed in the topic "add a sales order".
2. To start adding items, activate the reader and place it on the barcode.
3. The system shows a screen with the product code and offers two operation keys:

• • [F5] - To enter product quantity.
  • [F6] - To delete an item.

Other Actions/Barcode/Add

To use the option, follow these guidelines:

1. Fill in the Sales Order header as instructed in the topic "add a sales order".
2. To start adding items, activate the reader and place it on the barcode.
   1. [F5] - To enter product quantity.
3. Complete the missing fields such as TIO Code, among others.
4. Check the information and confirm.

Other Actions/Barcode/Edit

To use the option, follow these guidelines:

1. Select the Sales Order.
2. Click Other Actions/Edit.
3. Perform the desired adjustment and click OK to continue.

Other Actions / Copy

This allows you to add a new Sales Order based on the content of a registered order, either pending or not.

Check the completion of parameters MV_TIPCPDT  and MV_PEDFREZ, for the best results in this option.

To use the option, follow these guidelines:

1. In the Sales Order maintenance window, select the order to be copied and click Copy.
2. The System shows a sales order inclusion screen, bringing data from the original order.
3. All fields are copied except for the ones related to transaction table binding, status, and balance tracking. The order will always be copied as Not serviced.
4. Make any necessary changes and confirm.

Other Actions/Return

The purpose of this option is to accelerate the inclusion of a Purchase or Processing Return based on the existing incoming documents. Thus, when you select this option, a list containing incoming documents is displayed.

It returns purchases or shipment/return held by third parties for incoming invoices of types N or B.

When updating the sales order return, the System selects the TIO relative to the field Return TIO of the TIO entered in the Incoming Invoice.

To use the option, follow these guidelines:

1. In the Sales Order maintenance, click Other Actions/Return.
2. The System displays a screen with the Inbound Invoices.
3. Select the invoice and click Return.
4. The System displays the sales order return update screen, with the original data filled out.
5. Check the information and fill in the field TIO.

Check the data and confirm it.

Other Actions / Prep.outg.doc.

This option makes the outgoing document generation process easier so that documents can be prepared automatically from the Sales Order, from release to Billing, and up to the generation of Invoices.

For this process to work as expected, restrictions must not exist for the customer and/or stock for the items ordered.

This process automatically updates the data tables related to the following processes:

• Sales Order;
• Order Release;
• Outgoing Documents;
• Stock Balances.

It is possible to Account for the Sales Order. For this, you must set the question parameters Online Booking and Show Entry to Yes and create the Standard Entries.

To use the option, follow these guidelines:

1. In the Sales Order maintenance, place the cursor on the desired order and click Outg. doc.
2. A wizard is displayed to help you configure the preparation of the outgoing document related to the order selected. Click Next.
3. The System checks the order release status.
4. If the Sales Order has no items released for invoicing, the wizard displays a message to warn you and allows the automatic release if a balance exists in stock.
5. When the release is performed, click Next.
6. The wizard displays a new message notifying that the Sales Order is released and uses the items ready for invoicing to prepare the outgoing document.
7. If the order is not fully released, the items not released are ignored. To invoice it, click Next.
8. At this moment, a verification checks if any credit/stock restriction related to the order exists.
9. If so, the Sales Order Release window is displayed with the blocked items and the reason for blocking them.
10. To finish, click Next to view the message for successful completion.
11. If any items remain to be invoiced, a screen with the Series/Invoice data is displayed.

13. Select the series/invoice to be invoiced and click Ok.

14. At the next screen, set the parameters to generate the Outgoing Document.

The question Group Equal Orders? set to Yes allows you to group similar Sales Orders into the same outgoing document.

The question Conversion Ref. Dt. allows you to choose the reference date for conversion of the currency used in the Sales Order, Outgoing Document, and Telesales assistance according to DECREE No. 25 OF November 27, 2008, FOREIGN TRADE OFFICE - SECEX PUBLISHED IN THE DOU AT PAGE 00236 ON NOVEMBER 28, 2008.

15. Configure them and confirm. The Outgoing Document is generated, and the Sales Order is closed.

Other Actions/Accounting Tracker

This query is available only when viewing the Sales Order. This allows you to track this document and its items, displaying the main entities related to the Sales Order.

To use the option, follow these guidelines:

1. Select the document and view the screen with the data.
2. Select Other Actions/Accounting Tracker;
3. A screen is displayed with information on the accounting entries.

Other Actions / Caption

The generated orders follow a classification that identifies the current status of the order in the System, which can be:

 Pending Sales Order

Order ready to be released.

Closed Sales Order

This status appears after the preparation of the outbound document, indicating the order is closed.

Sales Order Released

This order is ready to be evaluated for credit and stock, prior to the preparation of the outbound document.

Sales Order with Rule Blocking

The order is blocked by a business rule. This happens when the sales order items and header do not agree with the definition in the Business Rules file.

Order with Funds Blocking

The order is blocked by a sales fund. This happens when, in the analysis of funds, the System checks whether the discount granted in the order items is greater than that allowed by the company. The difference between the one allowed by the rule and the one granted in the sales order is deducted from the sales fund balance if any. If the balance is insufficient, the order is blocked by the fund.

Other Actions/Related Actions

This option links to the Sales Order files such as figures, texts, spreadsheets, or any type that has information relevant to the system. 

To use the option, follow these guidelines:

1. In the routine maintenance, select the desired item;
2. Click Other Actions/Related;
3. Select the item you wish to add or enter.
4. To finish the process, click

Other Actions/Customer (Customer Status)

Show important information on the relationship with clients, such as:

• registration and financial information (returned checks, protested bills, average delay, greatest purchase, last purchase, etc.).

To use the option, follow these guidelines:

1. When accessing this option, view the parameter configuration screen.
2. Configure them according to the need. To continue, click
3. The system displays the screen to query the Customer Status.

The system also provides resources for a quick query of bills outstanding, bills received, references, and billing history. Plus, it also provides buttons for a quick query of pending bills, received bills, orders, billing, references, and collection history.

Other Actions/Methods (Payment Methods)

This option allows you to define specific payment methods for the order and enter the percentage apportionments between them.

The payment method is different from the condition, because it is only an informative record indicating means, for example, cash or check, and the condition indicates the distribution of values in installments according to the business rules and, therefore, the due date of bills in Financials, in the case of integration. 

Other Actions/Spreadsheet (Financial Spreadsheet)

This option shows a forecast of tax calculations that must levy the outgoing document and bills receivable that must be generated (amounts and due dates). 

Other Actions/Advances (Anticipated Receipts)

Available to Brazil

To use the option, follow these guidelines:

1. When you select this option, the system displays the advance selection screen.
2. After entering the amount, confirm the order.

This option allows you to list advances (RA-type bills) to the Sales Order to be used in payment order deductions of the order to be generated.

Other Actions/Simulation

This option is enabled when the integration of the module SIGAOMS into TOTVS GFE is used.

Check Integrations.

Other Actions/Formation

To use the option, follow these guidelines:

1. Access this option and check the worksheet presentation;
2. Select the Standard option and click OK to continue.
3. Then, set the parameters on the screen and confirm.
4. The system displays the screen of the worksheet Standard - Actual Average Cost, such as selected.

Other Actions / NFS Binding

To use the option, follow these guidelines:

1. For it to work correctly, the field Work Code (C5_OBRA) in the Sales Order must be filled in.
2. Access this option and view the parameter configuration screen.
3. Select the invoice and the other fields according to your needs and, to continue, click Confirm.
4. Then, confirm the order.

N = Regular

The type of invoice that fits the default sale situation.

Example:

D = Return

1. Used when it is necessary to return goods.
2. Use the Add option and, in the Order Type field, select D - Purchase Return.
3. Find the Product When you position the cursor, the system opens the edit screen.
4. Find the field Original Invoice (C6_NFORI), position the cursor, and type F4 to view the Incoming Invoices.
5. Select the Invoice you wish to return.
6. After you confirm, the system loads the Sales Order with the source invoice data.
7. Complete the information and confirm to continue.
8. The system makes the order available for release and preparation of the Outgoing Document.

When needed, enter the Sales Orders referring to the Purchase or Goods return item by item (the Grid Transaction is not implemented for this type of order).

The tax code does not necessarily have to be related to returns. In this case, the Sales Order is not generated for the customer but for the supplier, since it is an incoming invoice.

Return of value only, without quantity.

1. Use a return TIO compatible with the Sales Order that has the Qty Set to Zero (F4_QTDZERO) field set to Yes;
2. Adjust the quantity to 0;

The value fields Unit and Total must contain, respectively, the difference of the Value to return.

C = Quantity/Price Complement

1. When it is necessary to complement an Invoice, add a new Sales Order and set the Order Type field to C-Quantity/Price Compl.
2. At the Compl Type field, set the type of operation: 1-Price or 2-Quantity;
3. Enter a TIO (Type of Inflow and Outflow) taxing as in the original invoice;
4. Enter a Product, Quantity, Unit Price, and the Total Value.
5. Find the Original Invoice using the C6_NFORIG field and make the binding
6. Then, confirm the inclusion.

P = IPI Complement

This type of invoice is required when the rate of value of invoice IPI is registered lower than the due value.

The IPI value will always be the order total.

1. In Tax Records, the IPI value is displayed in the column Taxed, regardless of whether the TIO (Types of Inflow and Outflow) is set to Yes.
2. The ICMS is calculated when the question Levy IPI in the TIO file is filled in.
3. The completion procedure must be:

• • Type = P;
  • Product Code = original product code;
  • Quantity = 0 (zero).

I = ICMS Complement

This type of invoice is required when the rate of value of invoice ICMS is registered lower than the due value.

The ICMS amount will always be the invoice total, irrespective of the definition of the question Calculate ICM (S/N) of the TIO file. In this situation, the IPI amount is not calculated.

In Tax Records, the ICMS value is shown in column Taxed, regardless of what is set in the question ICM Tax Record from TIO File. The invoice is not generated.

The completion procedure must be:

• Type = I;
• Product Code = original product code;
• Quantity = 0 (zero).

B - Processing - Use supplier and Processing Operation

Return or Remittance in Third-Party possession (according to TIO used).

• When sending a product for processing, you must perform the following tasks:
• Register in the structure a processing code.
• Issue a raw material invoice referring to remittance to processing. This invoice is saved in the file for balance held by third parties, to track each invoice.
• Open a PO (Production Order) referring to the product resulting from the processing.
• When receiving the material through the incoming invoice, enter the code of the product for processing, as well as the previous PO Thus, the request for the same product is generated for the reference PO.

Remittance at Inflow is the remittance to the client, use:

• Invoice type (B), and
• TIO with (R) in the Third-Party Poss. field (F4_PODER3).

Remittance at Outflow is a remittance to your supplier, use:

• Invoice type (B), and
• TIO with (R) in the Third-Party Poss. field (F4_PODER3).

Return at inflow is the return of a remittance already run to the supplier. Use:

• Invoice type (N), and
• TIO with (D) in the field Third-Party Poss. (F4_PODER3).

Return in outflow is the return of the remittance already run by the customer. Use:

• Invoice Type (N=Regular), and
• TIO with (D=Return) in the field Third-Party Poss. (F4_PODER3).

Processing operation

When sending a specific product to custody/fixing/processing in third parties, the System provides tracking on these quantities.

To track third-party possession, the Billing, Purchases, and Stock/Costs environments must be implemented.

The system controls the quantity of the company's products in third-party possession and vice-versa.

In third-party possession, there are two basic cases:

1 - With stock transactions: For third parties with stock transactions, the system makes a cost transaction depending on the operation, i.e.:

a) For third-party operations, the cost will be equal to the entry cost.

b) For operations at third parties' facilities, the cost will be the weighted average cost.

2 - Without stock transactions: For the third parties without stock transactions, the system stores the net balance of the product in third-party possession, but that still belongs to the company's stock.

Completion procedure must be: a TIO in Third-Party Possession = (R=Remittance) or (D=Remittance Return) exists according to processing needs.

When the option is "D" (Return), if the source invoice is not typed or selected through the [F4] key on the field "Quantity" (C6_QTDVEN) of the Sales Orders routine, the system will display the remittance invoices with the balance to be returned, where the invoice must be selected and [Enter] pressed.

When a Sales Order involving the rendering of a service is issued, check whether the product (service) has a service code registered in its file.

If not, the registration can be done in the Sales Order itself using the field ISS Serv. Code of the Products File.

The Service Code is important because the ISS Registration books perform the calculations based on this code (D2_CODISS), in accordance with the legislation in effect.

When generating invoices, the amount of the CSSR Rural Social Security Contribution Tax) will be calculated and saved in the Sale Invoices Header File - SF2, field F2_CONTSOC).

To issue a Sale Invoice for a Rural Producer, the following configuration must be followed:

1. In the Customers File, the field Type (A1_TIPO) = L - Rural Area Producer.
2. In the Products File, the field Sec. Cont. (B1 ContSoc) = Yes. This field indicates whether the Social Security Payment is levied on the product.
3. In the Parameters File, Configurator environment, note the content of the parameters:
   1. MV_CONTSOC. This parameter indicates the CSSR (Rural Social Security Payment) percentage to be calculated. Which are: Natural Person (2,2); Special Insured (2,3); Legal Entity (2,7).
   2. MV_DIAFUN It indicates the day when the Social Security Payment bill is generated (FUNRURAL).
4. In the Companies File, Configurator environment, option Company Creation, set the Rural Producer field (M0_PRODRUR) in Registration Data, folder Complement:

F: Natural Person

J: Legal Entity

L: Special Insured (works with the family group according to IOB Bul. Occupational Social Security Legislation 48/94).

This field is automatically configured by the system as a blank field, i.e. the company is not subject to payment of FUNRURAL. When filled in, it is directly related to the parameter MV_CONTSOC.

Important:

The Product must contain information on the Levy of the Rural Social Security Payment (FUNRURAL) in its record.

After configuring the above-mentioned information, the amount of the Social Security Contribution will be calculated, and the TX-type bill will be generated in the Accounts Payable of the Financials environment.

In the outgoing operations to which the payment of the Rural Social Security Fund (FUNRURAL) must be applied, when the company is a Legal Entity or a Natural Person (M0_PRODRUR = J or F) and the customer is a Natural Person (A1_TIPO = F), a bill payable to the Federal Government will be generated because the responsibility for the payment lies on the company. When the customer is a Legal Entity (A1_TIPO=R), a deduction bill will be generated for the customer, as the responsibility for its payment lies on the customer.

To maintain the integrity between the service order and the Sales Order records, some adjustments were made to block the editing of points from a service order when a sales order is pending.
For that, the parameter MV_LIBVINC was created. It is verified when the sales order items are edited.

When set to False (.F.), it blocks editing and adding new items, and, when set to True (.T.), it allows the edition and inclusion of new items.

This option is available after an Outgoing Document of the Return type is added.

This situation happens when goods are received via an Incoming Document, but they have to be returned using a return invoice with a TIO that generates a stock transaction. Thus, the Purchase Order becomes available to be reused with the quantity returned.

Among the fields that must be filled in in the Adm/Fin/Cost folder of the Types of Inflow and Outflow file, it is important to consider the following criteria:

• Inflow TIO: field TIO File filled in with the Inflow option and field Stock set to Yes.
• Output TIO: field TIO Type filled in with the Outflow option and field Stock set to Yes.

The generation of the Outgoing Document is made using the Sales Order. When the Purchase Order is partially or fully released, the field Expected Incoming Qty. is updated.

After the Outgoing Document of the return type is added, the Purchase Order may change its status to:

• Pending Order (green caption ): the total order quantity is returned.

Example

Order Partially Served (yellow caption ): only part of the goods is returned.

Example 

After each transaction, it is necessary to observe the product balance, i.e., the content of the fields Current Balance and Expected Incoming Qty. 

The process described here follows the following order:

1. Purchase Order;
2. Incoming Document;
3. Sales Order - Return;
4. Outgoing Document - Return;
5. Released Order - Partial or Total;

This procedure enables you to establish the Calculation Basis for the Public Spending Processing Fee (TPDP) for:

• Sales Orders; 
• Outgoing Documents, and 
• Deletion of Outgoing Documents.

After you make the necessary registrations in the Customer and Product with YES and enter the Tax Rate, the System performs the Invoice transactions normally.

1. To generate, register the parameter MV_ALITPDP according to the procedures.
2. Register a new Customer with the field TPD = YES. 
3. Register a Product with the field TPDP = YES.
4. In the Billing module, access Sales Order and add a new order.
5. The system makes the Outgoing Invoice transactions normally, calculating the Public Spending Processing Fee (TPDP) and generating financial bills. 

The parameter MV_ICMPAUT sets the withheld ICMS base composition method when an ICMS basis is entered into the operation.

If the parameter is set to .T. (True): The ICMS calculation withheld base will be started by the base value, even if the sales price is greater or lower than the Base value.

When the parameter is set to .F. (False): If the sales price is lower than the base value, the calculation base withheld ICMS will be the base value, but if the sales price is greater than the base value, the calculation base withheld ICMS is obtained by the sales price value.

Example:

The composition of the calculation base withheld ICMS according to parameter configuration and several different sales prices.

Adding a Sales Order using a product with a solidarity margin of 30% and a tax exception with an internal rate of 12% and ICMS BASE of BRL 9.60.

Parameter MV_ICMPAUT = .F. and sales price LOWER (BRL 8.00) than the Base value;
ICMS Basis = 8.00 * ICMS Rate 12% = ICMS Value = 0.96
Withheld ICMS Rate = 12.48 Composition (9.60 + 30% margin)

Parameter MV_ICMPAUT = .F. and sale value GREATER (BRL 10.00) than the base value;
ICMS Basis = 10.00 * ICMS Rate = 12% = ICMS Value = 1.20
Withheld ICMS Basis = 13.00 Composition (10.00 + 30% margin)

Parameter MV_ICMPAUT = .F. and sales price LOWER (BRL 8.00) than the Base value;
ICMS Basis = 8.00 * ICMS Rate 12% = ICMS Value = 0.96
Withheld ICMS Rate = 12.48 Composition (9.60 + 30% margin)

Parameter MV_ICMPAUT = .T. and sale value GREATER (BRL 10.00) than the base value;
ICMS Basis = 10.00 * ICMS Rate = 12% = ICMS Value = 1.20
Withheld ICMS Basis = 12.48 Composition (9.60 + 30% margin)

Use this routine to generate, in Sales Orders and Outgoing Document, the National Tax Payment Form (GNRE) of Local ICMS, as well as generate bills payable in the Financials module for each outgoing invoice issued to another State.

1. In Billing (SIGAFAT), access Outgoing Document Doc. Prep. and select YES for the following questions:
   1. Generate Local ICMS Bill?
   2. Generate Local ICMS Form?
2. Use a TIO configured for Local ICMS calculation with the Customer, Nature (SA1), and Product (SB1) files:
   1. F4_ICM = Yes;
   2. F4_LFICN = T;
3. Confirm saving of Outgoing Invoice.
4. The generation of the GNRE national tax payment form is displayed, and a bill of ICM prefix is generated in Financials (SIGAFIN).

The system contemplates the calculation of several contributions, check some of them below and click the corresponding link to get more information.

The State Fund for Transport and Housing (FETHAB) is the contribution targeted at financing planning, execution, follow-up, and evaluation of transport and housing works and services in the state of Mato Grosso.

The Support fund to soybean cultivation (FACS) is the contribution aimed at financing actions targeted at the support and development of soybean cultivation, and the organization of the respective Production System through entities represented by this segment.

The Support fund to cattle development (FABOV) is the contribution aimed at financing actions targeted at cattle support and development, and the organization of the respective Production System through entities represented by this segment.

Tax calculation in outgoing Invoices to consider the calculation basis of taxes and payments regarding used vehicle operations.

Services companies with Taxpayer Register for Service Providers (CCM), and the Invoice is the NFS.

In the Configurator module, use Table 60 (ISS Service Code) and the codes of the services provided by the company.

Configure the fields of the processes:

Products File: 

ISS Serv. Code (B1_CODISS) - code referring to the service rendered, used to detail the operation before the levying city administration.

ISS Rate (B1_ISS) - enter the ISS calculation rate. When this field is blank, the system uses the information in the parameter MV_ALIQISS.

TIO File:

ISS Tax Record (F4_LFISS) - you must enter how the Service Invoice will be classified in the ISS Tax Records: Taxed, Exempt, Other, or Not Classified column.

Calculate ISS (F4_ISS) - enter Yes in this field when the company is not responsible for collecting the tax.

Customers File:

        Collect ISS (A1_RECISS) set to Yes (relates the financial nature to the service provision). The invoice issued has ISS calculation and a bill generated in Accounts Payable (Financials).

Some specifications exist for invoices generated in the Free Economic Zone of Manaus. The sale is identified when the customer has the SUFRAMA code (Superintendência Zona Franca de Manaus) and, when generating the invoice, the System grants a 7% discount on the unit price.

The discount value is kept in its own field in the Outgoing Invoice Items file and can be highlighted in the invoice depending on the invoice printing script.

To issue an Invoice with a discount in cases of sales to the Free Economic Zone of Manaus, the following configuration is necessary:

• In the Customers File, the fields:

Suframa (A1_SUFRAMA): Customer's Code in Suframa.

State Reg. (A1_INSCR): Customer's State Registration.

State (A1_EST): Customer's state (Must be a part of the content of parameter MV_NORTE).

Disc. to Sufr. (A1_CALCSUF): This field determines whether to calculate the discount to the Free Economic Zone of Manaus or not (ICMS calculation = 7% for customers with Suframa);

ZFM City Code: according to the definition of table S1 - Table of Cities for Free Economic Zone of Manaus and Free Trade, topic Tables, in the Configurator environment.

• In the Products File, the field:

Free Econ. Z. Tax = No or blank (allowing the discount).

• In the TIO File (Type of Inflow and Outflow), set it to calculate ICMS.

Practical example:

Notice the example of the Sales Invoice to the Free Economic Zone of Manaus in which the supplier is located in the state of Sao Paulo, and the customer is located in Ceara.

1. In the A Product file, the field Free Econ. Z. Tax is set to
2. In the File of Customer RO Indústria e Comércio Ltda, the following fields have been entered:

• • State = CE.
  • State Registration entered.
  • Suframa with Customer's code at Suframa.
  • Discount for Suframa set to S.
  • ZFM City Code set to 00105.

3. An order with the following information was saved in the Sales Orders File:

• • Customer RO Trade and Industry Ltd.
  • Customer Type: Reseller.
  • Product A.
  • Quantity = 10.
  • Unit Value = $ 100.00.
  • Total Value = $ 1,000.00.
  • TIO of Outflow for sale.

4. Order released for billing.

5. Credit released.

6. Stock released.

7. Invoice issued by the Outgoing Document routine.

8. After issuing the Invoice, you can query it and check its calculation:

• • Value of Goods 10 * 100.00 = 1,000.00
  • Calculation Basis of ICMS appropriate to operation = 1,000.00
  • ICMS appropriate to operation 1,000.00 * 7 % = 70.00 (Free Economic Zone of Manaus Discount).

To access these parameter settings, you need to access the routine and press the <F12> key for viewing and configuration.

To serve the demand of Incremental Releases processes, the source MATA410 (Sales Orders) was fragmented according to the naming sequence as follows:

The sources are now fragmented by processes and types of actions, and, to make identification easier, they are separated by acronyms.

Examples:

MATA410 (default existing source) = BASE - contains the operations that can be performed by the application, e.g.: adding, editing, operation, viewing, deleting, setting views and charts, browsing routine, and interfaces.

B = Business: Contains processes for saving records and business rules in general.

V = Validation: Contains pre and post-validation of forms, rows, and others.

I = Integration: Contains processes for integration between systems.

In some cases, acronyms of sources are used for better organization of processes.

See:

Therefore, the division of Sales Orders (MATA410) sources goes as follows:

MATA410 - Base (EXISTING)

MATA410B - Single Message (EXISTING)

MATV410 - Validation (Header, Header Folders, Menu Options, and Processes from Other Modules) (NEW)

MATV410A - Items Validation (NEW)

MATN410 - Business Rules involving the Billing module. (NEW)

MATN410A - Business Rules involving Supply Management. (NEW)

MATN410B - Business Rules involving Tracking of Stores, Tax Management, Logistics, Third-Party Software, and Other Modules. (NEW)

MATN410C - Business Rules to add orders via barcode. (NEW)