Hierarchy
⤷ CRM-LOC-BR (Application Component) Brazil
⤷ J1BA (Package) Localization Brazil
Basic Data
Data Element | J_1BSHIPFROM |
Short Description | Sending Tax Jurisdiction |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | J_1BSHIPFROM | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Send. Jur. |
Medium | 15 | Sending Jr. |
Long | 20 | Sending Jurisdiction |
Heading | 2 | SJ |
Documentation
Definition
Indicates the ship-from address from which the system takes the tax jurisdiction code to determine tax rates.
Procedure
When you define a nota fiscal type and enter a nota fiscal partner function, the system uses the tax jurisdiction code of this NF partner function for determining tax rates. However, if you want the system to use a different partner's tax jurisdiction code, you select an entry from the value help for this field. When the value that you select also includes a main business partner, the system puts this partner in the header of notas fiscais with this NF type.
Dependencies
In order to preserve the original nota fiscal types, we recommend that you make copies of the nota fiscal types and make the changes there.
Examples
You define a nota fiscal type and, in this field, you select '2 - Supplying vendor is main partner, shipfrom is from PO vendor.' When a nota fiscal of this NF type is generated, the system lists the supplying vendor in the header of the nota fiscal. However, the system uses the tax jurisdiction code from the purchase order vendor for determining tax rates.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 46C |