Índice |
---|
The Smart TIO registration is available with the goal of facilitating and speeding up the filling of the TIO code (Type of Inflow and Outflow) in the tax documents considering rules previously registered. The advantage of using this routine is that we can configure which TIO codes will be used in certain tax documents.
...
The registration of TIO code completion rules is linked to a transaction type code (FM_TYPE), for example: 01 - Sale of goods,02 - Simple shipment of material, 03 - Sale for final consumer etc.
Transaction type codes are registered in the DJ table of SX5, in generic tables. Each rule defined may have an outflow TIO code (FM_TS) and/or an inflow TIO code (FM_TE).
Once the type of transaction and TIO to be used is set in the rule, you will need to fill in the other fields listed below:
Field | Description |
---|---|
FM_CLIENTE | Customer Code |
FM_LOJACLI | Customer Store |
FM_FORNECE | Supplier Code |
FM_LOJAFOR | Supplier Store |
FM_EST | State |
FM_GRTRIB | Taxation Group |
FM_PRODUTO | Product Code |
FM_GRPROD | Product Taxation Group |
FM_POSIPI | Product NCM |
FM_REFGRD | Grid Reference Code |
FM_TIPOMOV | Sales Order Type |
FM_GRPTI | Smart TIO Group |
FM_TIPOCLI | Customer Type |
FM_GRPCST | IPI Framing Code |
FM_CFO_O | Tax transaction outflow code |
FM_CFO_I | Tax transaction inflow code |
FM_TPCTO | Contract Type |
FM_ID | Identification of the rule |
FM_ORIGEM | Product Source |
Informações | ||||
---|---|---|---|---|
| ||||
|
...
To exemplify the filling in, let's assume the creation of a rule to suggest the TIO code 500 in sale of goods to Final Consumer in the State of Sao Paulo. We must fill in the Smart TIO rule as follows:
Rule number 1:
Type of Transaction | Outflow TIO | State | Customer Type |
01 | 500 | SP | F-Final Cons. |
When there is a tax document bookkeeping with type of transaction 1 for the State of Sao Paulousing customer classified as Final Consumer, TIO 500 will be suggested in the bookkeeping of the tax document.
...
Let's look at another example,Sale of Goods of the "AAAA" product, suggesting the TIO code 501.
Rule number 2:
Type of Transaction | Outflow TIO | Product Code |
01 | 501 | AAAA |
With this rule, when a Sale of Goods of Product"AAAA" is booked, TIO 501 will be suggested when entering the invoice.
...
There may also be conflict of different rules registered with different fields, but with the same amount of information framed with the tax document. Below is an example of this situation:
Rule number 3
Type of Transaction | TIO | Product |
02 | 502 | BBBB |
Rule number 4
Type of Transaction | TIO | Customer |
02 | 503 | CCCC |
In a simple operation of material shipping to the Customer "CCCC" moving product "BBBB", rules 3 and 4 fall within the tax document, rule 3 framed the Product Code, and Rule 4 framed the Customer Code. Both have the same amount of information, both TIO 502 and 503 could be suggested. To solve this conflict, the system adopts the criterion of the order of more relevant/priority fields of the Smart TIO record. If the Product Code has greater relevance, then TIO 502 will be suggested; or, if the Customer Code has greater relevance, then TIO 503 will be suggested. The system has a default order of priorities, which can be changed by the customer if necessary.
...
SFM Field Identifiers - Operations with Customer
Field | Description | Identification code |
FM_PRODUTO | Product Code | 1 |
FM_GRPROD | Product Taxation Group | 2 |
FM_POSIPI | NCM | 3 |
FM_CLIENTE+FM_LOJACLI | Customer+Customer Store | 4 |
FM_GRTRIB | Taxation Group | 5 |
FM_EST | State | 6 |
FM_REFGRD | Grid Reference Code | 7 |
FM_GRPTI | Smart TIO Group | 8 |
FM_TIPOCLI | Customer Type | 9 |
FM_GRPCST | IPI Framing Code | 10 |
FM_TIPOMOV | Type of transaction of the sales order | 11 |
FM_ORIGEM | Product Source | 12 |
For Client-bound operations, the default system order is 1,2,3,4,5,6,7,8,9,10,11,12, where each number represents a field in the SFM table, i.e. the order of priority fields is:
...
SFM Field Identifiers - Operations with Supplier
Field | Description | Identification code |
FM_PRODUTO | Product Code | 1 |
FM_GRPROD | Product Taxation Group | 2 |
FM_POSIPI | NCM | 3 |
FM_FORNECE+FM_LOJAFOR | Supplier+Supplier Store | 4 |
FM_GRTRIB | Taxation Group | 5 |
FM_EST | State | 6 |
FM_REFGRD | Grid Reference Code | 7 |
FM_GRPTI | Smart TIO Group | 8 |
FM_GRPCST | IPI Framing Code | 9 |
FM_ORIGEM | Product Source | 10 |
For operations linked with Supplier, the default system order is 1,2,3,4,5,6,7,8,9,10, where each number represents a field in the SFM table, i.e. the order of priority fields is:
...
The TIO will be returned after filling in a given field depending on the operation being performed, such as issue of sale order, issue of purchase order, incoming invoice, etc. These fields can be viewed in the list below, as well as the fields that are used as parameters for defining the Smart TIO rule:
Table | Table Title | Trigger Field | Parameters |
SC6 | Sales Order Items | C6_OPER | C5_CLIENT, C5_LOJAENT, C6_PRODUTO, C6_TES |
SC7 | Purchase Req. / Delivery Aut. | C7_OPER | C7_OPER, C7_FORNECE, C7_LOJA, C7_PRODUTO, C7_TES |
SCK | Quotation Items | CK_OPER | CK_OPER, CJ_CLIENTE, CJ_LOJA, CK_PRODUTO, CK_TES, CJ_TIPOCLI |
SCY | Purchase Order History | CY_OPER | CY_OPER, C7_FORNECE, C7_LOJA, CY_PRODUTO, CY_TES |
SD1 | Incoming Invoice Items | D1_OPER | D1_OPER, C7_FORNECE, C7_LOJA, D1_COD, D1_TES, F1_EST |
SUB | Telesales Budget Items | UB_OPER | UA_CLIENTE, UA_LOJA, UB_PRODUTO, UB_TES, UA_TIPOCLI |
VVA | Vehicle Departure Items | VVA_OPER | VVA_OPER, VV0_CODCLI, VV0_LOJA, (VVA_CHAINT or VV1_CHAINT) |
VVG | Vehicle Arrival Items | VVG_OPER | VVG_OPER, VVF_CODFOR, VVF_LOJA, (VVG_CHAINT or VV1_CHASSI) |
DBJ | Purchase Center Parameters | DBJ_TPOPER | DBJ_TPOPER |
Aviso | ||
---|---|---|
| ||
All fields that participate in the desired rule (fields that are in the "Parameters" column in the table above) must be filled in before the field that triggers the rule (Field found in the "Trigger Field " column of the table above), so that the rule is loaded correctly. If it is necessary to change any field that is a parameter with the intention that another rule is selected, it is also necessary to delete and populate the Trigger field again so that the rule is loaded correctly. |
...