Message type: E = Error
Message class: FINS_FI_MIG - SAP S/4HANA Finance: Data Migration
Message number: 319
Message text: Some particular use of field &1 in &2 not supported by migration
When migrating allocation cycles and field configurations to the new
universal journal entry, some fields become obsolete; for example, the
field RVERS is not present in the respective line item table ACDOCA.
While the basic uses of such obsolete fields can be migrated, other,
more involved uses can't be handled automatically.
The table entries containing the unsupported field use are migrated
nevertheless.
The log states for which table, record, and field name the issue is
encountered. (At least a significant part of the record key is given in
the message.)
Check the respective records for use of that field name.
Change the affected cycles or field configuration by removing or
replacing the field name.
Note that, depending on the type of use, it might be necessary to adapt
further parts of the cycle definition or field configuration.
The following fields become obsolete with the new universal journal
entry table and should be changed in cycle definitions and field
configuration as indicated:
Field name,,Action,,Automated migration
ACTIV,,replace with BTTYPE,,yes
COST_ELEM,,remove,,no
LCURR,,replace with RHCUR,,no
GCURR,,replace with RKCUR,,no
OCURR,,replace with ROCUR,,no
OCLNT,,remove,,no
RPMAX,,remove,,no
RVERS,,possibly remove,,yes, for basic uses
Note that field RVERS is still in use for sender values with rule
"Posted amounts" and "Plan value origin" and for a receiver tracing
factor with rule "Variable portions" and type for plan values; see note
2511303 for details.
After the migration, run check report RGALLOC4 or transaction
<DS:TRAN.GCA9>GCA9</> and proceed according to the results.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message FINS_FI_MIG319 indicates that there is a specific use of a field in a particular context that is not supported during the migration process. This error typically arises during the migration of financial data, especially when using the SAP S/4HANA Migration Cockpit or similar tools.
Cause: The error can occur due to several reasons, including: Incompatible Field Usage: The field in question (denoted as &1) is being used in a way that is not compatible with the migration process. This could be due to the field being populated with data that does not meet the expected format or constraints. Data Structure Changes: The migration process may involve changes in the underlying data structures, and certain fields may have been deprecated or altered in the new system. Custom Fields or Logic: If there are custom fields or logic implemented in the source system that do not have a direct mapping in the target
Get instant SAP help. Sign up for our Free Essentials Plan.
FINS_FI_MIG318 No automatic migration for entries of table &1
What causes this issue? Due to possibly complex dependencies with cycle definitions, entries for the tables describing field groups (T811H, T811J, an...
FINS_FI_MIG317 &2 particular uses of field &1 not supported by migration
What causes this issue? When migrating allocation cycles and field configurations to the new universal journal entry, some fields become obsolete; fo...
FINS_FI_MIG320 Mismatch in data to be deleted for table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_FI_MIG321 Mismatch in data to be inserted for table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.