Ansicht
Dokumentation
J_1BCFOP_XREGV - Assign Validity Date to CFOP Versions
General Material Data ABAP Short ReferenceThis documentation is copyright by SAP AG.
Use
In this IMG activity, you assign a valid-from date to CFOP versions, and assign a version to a region (state) if required.
Requirements
You have already defined CFOP versions.
Standard settings
Activities
To assign a version and validity date to all of Brazil, leave the region blank; otherwise, assign the relevant version to the relevant region.
The system determines the version in the following sequence:
- Most recent valid-from date
- Most specific entry, such as the region
This means that if a general CFOP change occurs (as on 1/1/2003), you only need to maintain one entry for country BR with the valid-from date. If, however, a state has a different version for the new date, you must enter that explicitly as an exception.
Example
Country | Region | Valid-from | Version |
---|---|---|---|
BR | - | 1/1/1900 | 1 |
BR | SP | 1/1/2001 | 2 |
BR | SC | 1/1/2001 | 3 |
BR | - | 1/1/2003 | 4 |
BR | SC | 1/1/2003 | 3 (same version for SC, just a different validity date; otherwise the system would take the most recent entry, version 4) |
With the above settings, the system would select the CFOP version as follows:
Region | Billing date | Version |
---|---|---|
SP | 1/1/1999 | 1 |
RJ | 1/1/2002 | 1 |
SP | 1/1/2002 | 2 |
SP | 1/1/2003 | 4 (the system takes the most recent entry; if the SP exception still applies, you have to maintain it explicitly as of the same valid-from date as the general entry, which in this case is 4) |
SC | 1/1/2003 | 3 |