Professional Documents
Culture Documents
CT-e: Legal Change: Configuration Guide
CT-e: Legal Change: Configuration Guide
Configuration Guide
Date
Modified Chapters
Details
30.04.2014
3.1.3 Configuring
Conhecimento Determination
22-04-2014
All
General editing
Version
2.2
2
Document Items
15-10-2013
3.1.2 Purchasing Tax Code
Determination
08-02-2012
Table of Content
INTRODUCTION ............................................................................................................................... 3
2
2.1
2.2
ACTIVATION ..................................................................................................................................... 3
Activation of the solution ................................................................................................................ 3
Document Items ............................................................................................................................... 3
3
3.1
3.1.1
3.1.2
3.1.3
3.1.3.1
3.1.3.2
3.2
3.3
3.4
3.5
3.6
3.7
4
4.1
4.1.1
4.2
4.3
4.4
5
5.1
5.2
8
8.1
8.2
8.3
BAPI ................................................................................................................................................ 12
10
10.1
10.1.1
SCREEN CONTROLS..................................................................................................................... 12
Screen Control for Group Assignment ........................................................................................ 12
Screen Control for Group Assignment ............................................................................................. 12
INTRODUCTION
This guide provides a general overview of Conhecimento Eletrnico (CT-e) implementation and usage.
Section 2 describes how to activate the CT-e solution in the system.
The remaining chapters give examples of usage of the solution.
The execution of the steps of the chapter 2 is mandatory. The execution of the steps of the examples in the
remaining chapters is not mandatory, since there might be variations of the customizing in order to cover
different scenarios.
2
ACTIVATION
2.1
2.2
Document Items
In SAP ERP system, CT-e documents must contain only one item. Processes with more than one item in the
CT-e are not supported.
In Incoming Scenarios, any Purchase Order or Service Entry Sheet created must contain only one
item.
In Outgoing Scenarios, Sales Order documents and Billing documents created for CT-e documents
must contain only one item.
3
In the system, freight is considered a service and does not require a goods receipt. Therefore, the incoming
CT-e process is based on External Service Management (SRV-MM-BR). For more information see SAP Note
947670, Service Management - Localization for Brazil (overview).
3.1
3.1.1
Basic Configuration
Configuring Tax Code MM
Condition types are available to calculate ICMS on CT-e. They are different from ICMS on freight in nota
fiscal and from ICMS on goods. This also applies to ICMS ST.
Two other conditions have been created to calculate the Complementary ICMS tax (ICMS DIFAL). For more
information, see SAP Note 1792935, CT-e: Incoming Complementary ICMS. As ICMS DIFAL is only relevant
for consumption/asset material transportation, then it is necessary to set the usage of the tax code as
Consumption.
To use these new condition types, it is necessary to create a new Tax Code MM (or customize an existing
one) activating the related condition types, as follows:
Tax
Conditions
ICMS
PIS
COFINS
Note: For ICMS, it is not necessary to activate all conditions. Activate only the conditions related to your tax
classification.
3.1.2
For PO tax code determination, you can use the NAVS condition technique. For more information, see SAP
Note 501054, FAQ: Taxes in purchasing.
Note: The NAVS condition technique does not work if your pricing procedure has requirement 60 in the
NAVS condition. In this case, you can either remove it or create another pricing procedure depending on
your business needs.
3.1.3
Conhecimento determination is used to differentiate a normal service purchase order from a purchase order
intended to be used as a base document for the creation of a CT-e.
In addition to the new condition types, the purchase order for CT-e is also different in other aspects:
For CT-e, the taxes are calculated at Purchase Order item level. For ISS, the taxes can be calculated
at service item level.
The ICMS and ICMS ST rates are different in goods documents than in CT-e. For CT-e, the rate is
indicated in the column ICMS on Freight, if it exists in the Tax Rate Tables. This column is
maintained in the Tax Managers Workplace Brazil (transaction J1BTAX), in Maintain ICMS Values
(table J_1BTXIC1). For others Tax Rate Tables, ICMS Base and ICMS Rate are used.
In a standard nota fiscal (for example, 1A) the freight value is just a part of the Net Amount. For CT-e,
however, the Net Amount represents the freight value itself.
The system determines that a document is a CT-e when the condition type CONH (or another condition type
assigned to the internal code CONHECIMENTO) is found in the purchasing calculation schema.
The condition CONH can be activated in the pricing procedure either manually or via a correspondent
condition record retrieved by an access sequence. An access sequence is not provided to determine CONH
as different customers will have different requirements to determine if a process corresponds to freight.
3.1.3.1
The following steps are example. You can adapt them to an existing condition type and purchasing
calculation schema accordingly.
4
The calculation schema configuration is available in the IMG under Materials Management ->
Purchasing -> Conditions -> Define Pricing Determination Process.
1. Create Purchasing condition CONH (in the IMG under Materials Management -> Purchasing ->
Conditions -> Define Pricing Determination Process -> Define Condition Types).
2. Enter Purchasing Calculation Schema definition menu (in the IMG under Materials Management ->
Purchasing -> Conditions -> Define Pricing Determination Process -> Define Calculation Schema).
3. Select schema RM0000 and choose Control Data.
4. Choose the New Entries pushbutton.
5. Enter the information as follows:
Step
Counter
30*
Condition Type
Requirement
CONH
10
* step 30 is an example
ATTENTION: When creating the condition CONH (step 1) is advised to include an access sequence in it.
Otherwise, whenever the associated pricing procedure (i.e. RM0000) is called the Purchase Order is going
to activate CT-e Determination and CT-e taxes calculation.
3.1.3.2
Application
CONHECIMENTO
3.2
Condition Type
CONH
conditions (CIC1, CIC2, CST1, and so on) and choose the Taxes pushbutton to verify the calculated
taxes.
9. Save the purchase order.
3.3
Service Entry Sheet creation does not require any specific procedures other than the standard process.
However, it is necessary to perform invoice verification.
1. Start the Service Entry Sheet creation process. (In the SAP menu, choose Logistics Sales &
Distribution Bill of Services Service Entry Sheet Create.)
2. Enter the required information and save the document.
3.4
Creating an Invoice
3.6
The tax group 6 (available in SAP Note 1714749, CT-e LC: Extension of Tax Calculation Features) was
created especially for CT-e. This tax group makes use of dynamic exception tax table (J_1BTXIC3) and uses
Service Item Level as the key for retrieving tax data (for example, rate and base).
For tax calculation purposes, if there is more than one service item in the purchase order, the item with the
higher net value is used for retrieving tax data.
That is, the selected service determines the condition records to be retrieved.
In the example above, the second service is used for this purpose.
This selection can be overridden using the BAdI J_1BCTE_SELECT_SRVPOS. For more information, see
section 8.2, Service Item Selection (MM).
3.7
When carrying out a consumption/asset material transportation, if the intrastate ICMS Tax is greater than the
interstate Tax, it is necessary to collect the difference between them, that is, the ICMS complement.
For example, if a transport from state RS to state SP has 5% of ICMS and the intrastate tax for SP is 12%, it
is necessary to evaluate the difference between the taxes.
In the standard pricing procedure, the DIFAL base amount is stored in condition type BX30 and the tax
amount is stored in condition type BX31.
In the CT-e document, tax type CCOP highlights the calculated DIFAL tax value. The CCOX condition type
(in the pricing procedure) stores the offset (minus CCOP) so that this value is not added in the total taxes of
the nota fiscal.
8
In general, the outgoing CT-e process follows the steps of a normal sales process, that is, the creation of a
Sales Order, the creation of a Billing Document and the correspondent CT-e document.
4.1
Basic Configuration
1. Create a material for freight service with Material Type DIEN Service.
2. Create a new sales order type (or use an existing one) and assign it to a nota fiscal type with model
57.
4.1.1
4.3
The determination of the ship-from location for outgoing CT-e was extended.
To determine the ship-from it is necessary to customize the Map CT-e Partner to NF Partner Function
(J_1BCTE_PAR_MAPV) view.
The Partner Function assigned to the 0 Goods Sender CT-e Partner will determine the ship-from. For
example, when the RE Bill-to Party is mapped, the Bill-to Party business partner address of the Sales
Order is the ship-from.
Item
Description
Ship-From
Ship-To
This ship-from location affects tax rates, CFOP determination and the determination of new fields for
Jurisdiction Code in CT-e.
ICMS EXEMPT
In some Brazilian processes the ICMS is exempt, and therefore it should not be charged.
Usually it is the source and end locations of the service and the product being transported that determines
the ICMS exemption, for example:
- PLS 274/04 for law 87/96 - Exemption of ICMS for transportation of paper for book or newspapers in
all states in Brazil.
- ICMS Law at RS 38/2012 - Exemption of ICMS for transportation of vehicles for disabled people - law
specific for Rio Grande do Sul.
Even without the calculation of ICMS, the ICMS base value should be visible in the CT-e and the ICMS
should be reported in legal reports. The ICMS base for ICMS Exempt must be calculated and displayed as
excluded base. The law that makes the ICMS exempt must be printed in the CT-e.
5.1
MM ICMS EXEMPT
In the system, MM scenarios with the ICMS exempt are done by the use of a proper tax code. There are
other customizations that also have to be carried out to report the ICMS exempt correctly.
Create a new Tax Code (or use an existent one) making sure that the option ICMS-ex. is marked.
A tax type for exempt must be active. In order to move the base values to the CT-e document, the tax
type for exempt must have Ex. Base Cond. and Other Base Con. filled with the proper conditions.
With this customizing the condition record that identifies the ICMS exempt is generated. In SAP default
customizing this condition is BICX, related to the internal code ICMSNULLEXEMPT - application TX.
5.2
SD ICMS EXEMPT
For SD, the tax code should have Industrialization as Customer usage and ICM-exempt must be checked.
The Tax Type use must have its Ex. Base Cond correctly filled.
With this customizing the condition record that identifies the ICMS exempt is generated. In SAP default
customizing this condition is BICX, related to the internal code ICMSNULLEXEMPT - application V.
6
News fields for Origin Jurisdiction Code (J_1BNFDOC-CTE_STRT_LCT) and Final Jurisdiction Code
(J_1BNFDOC-CTE_END_LCT) were created to support the CT-e.
These new fields are automatically filled according to the ship-from and to the ship-to defined in the
Purchase Order or in the Sales Order.
In the CT-e tab of the CT-e/NF-e Writer whenever a Jurisdiction Code is informed the name of the city is
presented beside the field.
7
The access sequence BRCC was created especially for ICMS Conhecimento (released via Note 1714749)
taxes.
As standard, the related internal codes for ICMS Base and Rate are customized using this access sequence.
10
Please, notice that no tax group (tax group assigned to internal code of tax conditions) should be customized
for Conhecimento ICMS base and rate internal codes.
Because of this, customer tax groups (Tax Group for Dynamic Tax Exceptions, between 10 and 89) will
never be inserted in BRCC when executing a migration.
If needed, instead of using migration tool, the customer tax groups should be customized manually in access
sequence BRCC via view VV_T682_TX.
ATTENTION: If a tax group (tax group assigned to internal code of tax conditions) is customized for
Conhecimento ICMS Base and Rate internal codes, you could then use the migration tool. Then all access
sequences assigned to conditions (and those assigned to internal codes CONH_ICMS_BASE and
CONH_ICMS_RATE) will be updated. However this may work for migration, SAP standard functionality does
not support collateral effects of this procedure (e.g. fiscal books, several entries for unwanted conditions
migrated).
8
8.1
The BAdI (J_1BCTE_IV) was created to fill data regarding incoming CT-e. It is called during invoice
verification when the CT-e document is generated.
This BAdI imports the data from the Purchase Order and exports the new CT-e data to be stored in the
database.
This BAdI is available in the IMG under Cross-Application Components -> General Application Functions ->
Nota fiscal -> Electronic Fiscal Documents -> CT-e Specifics -> Incoming CTe -> Business Add-Ins -> BAdI:
Fill CT-e Data During Invoice Verification.
8.2
The BAdI J_1BCTE_SELECT_SRVPOS was created (available via SAP Note 1714749, CT-e LC: Extension
of Tax Calculation Features) to be used for overwrite the selection of the default service to be used as key to
search the exception in Tax Group 6 (Dynamic Exceptions table) when executing a purchasing process.
This BAdI is available in the IMG under Cross-Application Components -> General Application Functions ->
Nota fiscal -> Electronic Fiscal Documents -> CT-e Specifics -> Incoming CTe -> Business Add-Ins -> BAdI:
Select Service Master Used in Dynamic Exceptions.
11
8.3
The BAdI J_1BCTE_SD (available via SAP Note 1761307, BAdI for import Outgoing CT-e Data) was created
to fill data regarding outgoing CT-e and is called during the billing when the CT-e document is generated.
The BAdI imports the data from the Billing and exports the new CT-e data to be stored in the database.
This BAdI is available in the IMG under Cross-Application Components -> General Application Functions ->
Nota fiscal -> Electronic Fiscal Documents -> CT-e Specifics -> Outgoing CTe -> Business Add-Ins -> BAdI:
Import Outgoing CT-e Data.
9
BAPI
SCREEN CONTROLS
It is necessary to assign NF Types to the screen controls for handling CT-e incoming and outgoing
documents.
Attention: The NF Types <CO> and <C1> mentioned below are not delivered. You should use your own NF
Types for incoming and outgoing as described in the following section.
10.1 Screen Control for Group Assignment
The following steps are examples. You should adapt them to your existing NF Types accordingly.
1. Execute transaction SM30.
2. Enter J_1BALV in the Table/View field.
3. Choose the Maintain pushbutton.
4. Choose the New Entries pushbutton.
5. Enter the information as follows:
Mode
Scr.cnt.rf
Conhecimento outgoing
Change
28
<CO>
Conhecimento outgoing
Create
24
<CO>
Conhecimento outgoing
Display
21
<CO>
Conhecimento outgoing
Change
29
<CO>
Conhecimento outgoing
Create
24
<CO>
Conhecimento outgoing
Display
22
NF Type
Description
<CO>
Manual
Mode
Scr.cnt.rf
<C1>
Conhecimento Incoming
Change
28
<C1>
Conhecimento Incoming
Create
23
<C1>
Conhecimento Incoming
Display
21
<C1>
Conhecimento Incoming
Change
29
<C1>
Conhecimento Incoming
Create
25
<C1>
Conhecimento Incoming
Display
22
13
14