7 SaPNote 1231815 - Predefined FMDERIVE tables are renamed during transport/CC Component: PSM-FM-UP-AD (Account assignment Determination), Version: 2, Released On: 18.07.2008 | symptom Tcode FMRULES to inport SAP predefined derivation rules into FHDERIVE/FHDERIVER is used in the system, Such a created database tables FMDERIVEQO? are renamed during Transport or Client copy. New table name is created based on name convention: FMFMOASssnmmnnn (sss - system indicator, mmm - client, nnnn - sequence number). | other Terms ABADR, FMOA, Client transport, SCC3, SCC9, SCCL, FMDERIVE, FMRULES, FMDERIVE*, FMDERIVEOO, FMDERIVEOO* | Reason and Prerequisites FMDERIVE derivation tables are transported using Finbasis Transport Tool functionality. This tool creates new derivation rules tables in target logical system based on name convention described above. Protection to avoid renaming of FMDERIVE00? tables is not supported. | solution RECOMMENDED SOLUTION: using hardcoded name of in partner/customer coding to select from FMDERIVE0O? tables is not recommended. Always dynamically read name of derivation rules table from database table TABADRS, i.¢ Tike this: SELECT param_l FROM tabadrs INTO WHERE APPLCLASS = 'FM! SUBCLASS, ‘ou’ ABADRSTRATID = 'FNOA' ABADRENV = = STEP_NO = POSSIBLE WORKAROUND: If suggested solution is not possible, use following workaround. Derivation rules tables are not recreated by Finbasis Transport Tool in case that all checked derivation rule characteristic are exactly the same in source and in target client Follow provided steps to achieve this: 1. Import derivation rules from source logical system and subsequently delete imported predefined derivation rules in target logical system (other types of derivation need to be leaved untouched) . 2. Import your desired predefined rules from TA FMRULES in target logical system. And sort all rules it the exactly same order as in source logical system 3. adjust any derivation rules changes done in source logical system also in target logical system. (i.e. changes such a “overwrite with new value If New Value...", "Initial value Allowed", any changes on Attributes tab, etc.)4. Enter the table TABADRS in target logical system with restriction PARAM_1 = ‘FMOERIVE*' and adjust value of field INTID to the same value as in source logical system for all predefined derivation rules. CANTID is usually structured: ‘sssmmmnnnn', where sss - system indicator, mmm - client,nnnnnn - sequence number. But also different structure could be used especially in long time period operated systems.) 5. Run CC/transport of derivation rules again. Derivation rules tables for FMRULES predefined rules will keep their original names. If tables are getting renamed again, make sure that there are no differences in source and target logical system as described in step 3 If you believe that workaround does not work in your system, create a OSS message for component PSM-FM-UP-AD. | Manual Activities | Attributes Key Value Other Components FIN-FB-IR (Transport-Tool) | Software Components Software Component ‘And subsequent, EADS x | This document is referenced by SAP Note/KBA Tide