FINS_CFIN_COPA_MSG - Central Finance Profitability Analysis Message Class

The following messages are stored in message class FINS_CFIN_COPA_MSG: Central Finance Profitability Analysis Message Class.
 It is part of development package FINS_CFIN_COPA in software component FI-CF-CO. This development package consists of objects that can be grouped under "Central Finance - Controlling Profitability Analysis".
Message Nr ▲
Message Text
000*** 000 - 100 reserved for COPA Posting ***************************
001Operating Concern &1 is invalid
002PA document posting failed
003PA ledger is not '01'
004Cannot retrieve PA ledger information
005Preceding document &1 is not available
006Business transaction &1 is not allowed
007PA configuration for source logical system &1 &2 failed to load
008There is an import parameter conflict. Stop processing
009Operation concern &1 is not active
010Controlling area &1 does not exist
011Company code &1 does not match controlling area &2
012Plant &1 does not match company code &2
013Record type &1 business transaction type &2 is not supported
014Column &1 in the source system is mapped to column &2
015Column &1 in source system does not have column mapping information
016Operation &1 has not enhanced, missing necessary technical column
017PA document &1 position number &2 already posted
018Cannot find source operating concern &1 related mapping information
019Cannot find source operating concern &1 information
020Source COPA document &2 posted successfully with central COPA document &1
200*** 200 - 300 reserved for COPA Mapping ***************************
201Operating Concern &1 is already maintained
202Operating Concern &1 does not exist
203Operating Concern &1 does not exist in system &2
204Enter a valid table for characteristic/value field mapping
205CE4 table does not exist in the Central Finance system
206CE1 table does not exist in the Central Finance system
207Data type is different between source and Central Finance system
208Field length in Central system is shorter than that in source system
209Field &1 does not exist in the source system
210Field &1 is key, assign a field from source system
211Field &1 does not exist in the Central Finance system
212&2 from source system &1 mapped to multiple central operating concerns
213Field &1 of table &2 in the Central Finance system isn't mapped correctly
214Settings for table &1 missing in Central system
215Settings for table &1 missing in source system
216Field &1 is missing in META source repository for operating concern &2
217Field &1 is missing in META central repository for operating concern &2
218Data type of field &1 is different from field &2, mapping not possible
219Field &1 does not exist in the source system
220Table &1 does not exist in the Central Finance system
221Structural info for &1 from system &2 not found, sync table structure
222Mapping not found for operating concern &1 from system &2
223Structure for table &1 in system &2 has changed, update mapping?
224Structure for table in both source/Central system changed,update mapping?
225No change in table structure detected
226Update the current mapping to adjust for updated structure, continue?
227Updating table structure repository failed
228Field &1 in table &2 from system &3 cannot be dynamically created
229Maintain at least one field mapping
230Displayed central fields differ from database table structures, update?
231RFC destination not found for logical system &1
232Unable to get data from source system
233RFC destination for system &1 is not configured
234No value fields maintained in customizing, mapping not needed
235Maintain chara. mapping for oper. concern &1 and &2 &3
250COPA data type &1 is not supported for operating concern &2
251Mapping not found between &1 in system &2 and &3 in Central system
252Operating concern &1 in the source system &2 is not mapped
253Mapping not allowed between &1 in sender system and &2 in Central system
Privacy Policy