Area | Activity | Details |
FIORI Activation App ID: F3473 | Migrate Your Data | fioriappslibrary. link Odata service : /LTB/MIG_MC_ODATA_SRV BSP Node: /sap/bc/ui5_ui5/sap/LT_MC_PE_S1/ Role : SAP_BR_CONFIG_EXPERT_DATA_MIG |
FIORI Activation App ID: DMC_WDA (DMC_WDA_APP) | Migrate Your Data – Migration Cockpit (old) | fioriappslibrary. link BSP Node: /sap/bc/webdynpro/sap/DMC_WDA |
App ID: F1047A,F1686A, F2399,F2442, F3251,F3455 | Other MDG applications in case MDG-F/MDG-F into scope | fioriappslibrary. link |
Area | Details |
Asset Migration | “Legacy Data Transfer status” has to change from “In Preparation” SPRO : Financial Accounting – Asset accounting – Asset Data Transfer – Define Transfer date and additional parameter |
Asset Migration | Apply additional filter in LTMOM -> select project -> Source structure -> ANLA->Technical selection Filter to select only valid asset for migration . Remapping of depreciation area from source to target to change assignments . |
Asset Migration | Separate Screen layout/Field group rules for Asset to be redefine considering migration scenario would require input enable fields which are read only otherwise example Orign. Useful life |
Controlling area currency | Mapping area currency issues refer to SAP note 2934306 |
Business partner / Vendor | CVI configuration need to completely defined Industry system Vendor->BP->Vendor number range need to be in syc as external or internal number range. |
Business partner / Vendor + Customer | Title of business partner mapping require to be in sync with source and target system. Migration of direct transfer to be excluded from 4eye check vendor confirmations. For integrated business partner scenario customer to be migrated first and extend same business partner as vendor role Attachment migration is not part of application transfer.It requires Separate handling. |
Troubleshooting | Additional filter criteria for migration object selection 1. Transaction CNV_PE_PROJ - CNV_PE_PROJ_MAINTAIN/LTMOM Select project created via FIORI 2. Select Data Model / Source structure form project 3. Add selection criteria into source structure. 4. Ensure data integrity is maintained as filtered data from project will not be considered for migrations. Debugging 1. Transaction LTMOM Select project created via FIORI 2. Target processing provides BAPI mapped for migration 3. Execute / Simulation 4. Select filter criteria for debugging using free selection 5. Tick appropriate Build/Simulation option for debugging 6. Bapi test variant can be set for further debugging in SE37. Retention:Project has not been deleted after the retention period, contact your system administrator to check that the retention job (job /LTB/RETENTION) is running. For more information, see SAP Note 2997667 . Template upload and download. (Client 000):Report CNV_PE_DOWNUP: TEMPLATES UPLOAD AND DOWNLOAD 2953439 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |