Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-LOC-BR (Application Component) Brazil⤷
J1BA (Package) Localization Brazil
Basic Data
| Data Element | J_1BCFOP_REDET |
| Short Description | Automatic CFOP Redetermination Following Version Change |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Redeterm. |
| Medium | 15 | Redetermine |
| Long | 30 | Automatic CFOP Redetermination |
| Heading | 30 | Automatic CFOP Redetermination |
Documentation
Definition
Means that if a different CFOP version comes into effect between the current process and the preceding document, the system automatically redetermines the CFOP code for pending documents. For example, you have aleady entered a sales order or delivery, a new CFOP version becomes valid, and you later process billing; you need the new CFOP version in the billing document.
Procedure
Examples
Dependencies
If this indicator is not set, you need to verify the CFOP code manually. Note, however, that you cannot change the CFOP code manually in the billing document. This means that if automatic CFOP redetermination is triggered in billing, you have no way of changing it - except to cancel the billing document and then manually change the delivery or sales order.
You should, therefore, set this indicator with caution, and only for a transition period during which a version change for pending documents is likely.
History
| Last changed by/on | SAP | 20030130 |
| SAP Release Created in | 470 |
