Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-LOC-BR (Application Component) Brazil⤷
J1BA (Package) Localization Brazil
IMG Activity
| ID | J_1BNFTXCONDV | Map SD Tax Values to Nota Fiscal Fields |
| Transaction Code | S_PL0_09000318 | (empty) |
| Created on | 20020423 | |
| Customizing Attributes | J_1BNFTXCONDV | Condition-Based Tax Calculation - SD |
| Customizing Activity | J_1BNFTXCONDV | Map SD Tax Values to Nota Fiscal Fields |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | J_1BNFTXCONDV |
Use
In this IMG activity, you map SD tax values to nota fiscal fields.
Requirements
Standard settings
Activities
When you customize the tax code of an item, you specify which tax types are to appear in the nota fiscal. The tax types are identical to the condition types in the tax calculation procedure. (See the IMG documentation for Define FI/MM Tax Codes for further information.)
In this activity, for each nota-fiscal-relevant tax type, you define from which lines of the pricing-procedure results table the system is to take the nota-fiscal values. You can map the following nota-fiscal fields to table fields:
- Base amount
- Tax rate
- Tax value
- Excluded base
- Other base
For each of these nota-fiscal fields, you specify:
- The condition type that indicates the line of the pricing-procedure results table (in the Tax (Tax Type) field)
- The field in this table line that stores the value to be transferred. It can be the condition base (KAWRT), the condition rate (KBETR), or the condition value (KWERT).
Example
Suppose an item in a document (such as a purchase order, material document, or invoice) has the tax code I1 (Inp. Industrialization: ICMS only). This tax code is delivered with three active tax types: ICM1, ICMX, and IPIN.
According to the Brazilian law, the nota fiscal must contain two tax lines in this case:
- ICMS tax line, which contains the actual tax rate, amount, and base values
- IPI tax line, which has the IPI calculation base (net value + ICMS) stored in the Other base field because no IPI tax is due.
The system takes the values of the ICMS line from the line of the pricing-procedure results table that has the condition type ICM1. It takes the values of the IPI line from the line that has the condition type IPIN. (The tax type ICMX is not to be considered in the nota fiscal; it is used only for calculation purposes in the tax calculation procedure.) The assignment of tax group ICMS to the tax type ICM1 and tax group IPI to the tax type IPIN is defined in the Customizing activity Define Tax Types.
During tax calculation, the system processes the calculation procedure and stores the results internally in the pricing-procedure results table. Which fields of that table contain the nota-fiscal values? This information is stored in this mapping table. Suppose it has the following entries:
Tax Type ICM1
Tax Rate: BIC0 Mapping: Condition Rate
Tax Amount: ICM1 Mapping: Condition Value
Tax Base: BIC9 Mapping: Condition Value
Ex. Base: BIC7 Mapping: Condition Value
Other Base: BIC2 Mapping: Condition Value
Tax Type IPIN
Tax Rate: <left blank>
Tax Amount: <left blank>
Tax Base: <left blank>
Ex. Base: <left blank>
Other Base: IPIN Mapping: Condition Value
For the ICMS line of the nota fiscal, the system takes the tax value from the field KBETR (condition rate) of the line of the pricing-procedure results table that has the condition BIC0; the tax amount will be taken from the field KWERT (condition value) of the line of the pricing-procedure results table that has the condition ICM1; the normal tax base will be taken from the field KWERT of the line of the pricing-procedure results table that has the condition BIC9; the excluded base will be taken from the field KWERT of the line of the pricing-procedure results table that has the condition BIC7; and the other base will be taken from the field KWERT of the line of the pricing-procedure results table that has the condition BIC2.
For the IPI line of the nota fiscal, the tax rate, tax amount, normal tax base, and excluded base will be zero since no mapping field is specified. The other base will be taken from the field KWERT of the line of the pricing-procedure results table that has the condition IPIN.
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| J_1BNFTXCONDV | BR | Brazil |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | J_1BNFTXCONDV | 0 | HLA0009600 | Sales and Distribution |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| J_1BNFTXCONDV | V - View | SM30 |
History
| Last changed by/on | SAP | 20020509 |
| SAP Release Created in | 470 |
