RS_B4HPREP - B4H Transfer Preparation Messages
The following messages are stored in message class RS_B4HPREP: B4H Transfer Preparation Messages.
It is part of development package RS_B4HANA_PREPARE in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "Preparation Tasks for BW/4 Transfer".
It is part of development package RS_B4HANA_PREPARE in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "Preparation Tasks for BW/4 Transfer".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Object &1 &2 added &3 new objects (it has &4 children) |
002 | Non-Existing Object &1 &2 will be purged from RSOOBJXREF |
003 | &1 of &2 Entries Deleted from RSOOBJXREF |
004 | Deletion of &1 Entries (out of &2) from RSOOBJXREF failed |
005 | Object &1 &2 cannot be maintained |
006 | BW/4HANA Conversion Cockpit not installed. Remote transfer not possible. |
007 | There is no active DLM run with maintained target system |
008 | Requests for &1 &2 successfully prepared |
009 | Some objects cannot be transferred. See details by using HotSpot. |
010 | Test mode activated. Click again to deactivate. |
011 | Test mode deactivated |
012 | System is not a BW system. No action required. |
013 | Maintain name of new BW/4 system before execution |
014 | Logical name of new BW/4 must be different to current BW |
015 | No relevant DataSources in current scope. No action required. |
016 | Function &1 does not exist in system &2 |
017 | Implement Note &1 in &2 or perform init simu. during source downtime |
018 | &1 &2: Last delta is old (&3). Ensure delta can be loaded, or delete init |
019 | DataSource &2(&3): Delta queue contains large data quantity (&1 blocks) |
020 | Delta for DataSource &1 (&2) must be reinitialized in &3 |
021 | DataSource &1 &2 will be cloned from BW &3 to &4 with new processes: |
022 | DataSource &1 &2 successfully cloned from BW &3 to &4 |
023 | Check not possible before clone task has been run |
024 | Request &1 not completed. Monitor this request (Tx RSRQ). |
025 | Request delta for &1 (&2) before synchronization of delta queues |
026 | Cloned DataSource &1 &2 successfully synchronised |
027 | At least one new DTP for the DataSource &1 must be selected |
028 | ODP process &1 successfully renamed to &2 |
029 | No authorization for this action |
030 | DataStore object &1 must have all data activated |
031 | Object &1 &2 has no transportable package. Execute task in dialog. |
032 | InfoCube &1 must be switched to loading mode before transfer |
033 | Target source system &1 is not of type ODP, context &2 |
034 | Target object &1 &2 already exists. Choose another name or delete it. |
035 | Setup & Generation phase is not complete. Task list cannot be continued. |
036 | Program preprocessing is not complete yet. Task list cannot be continued. |
037 | Read tasks are not complete yet. Task list cannot continue. |
038 | Transfer InfoObjects and OpenHub only at "Ready For Conversion" |
039 | Only transfer InfoObjects and OpenHub at "Ready For Conversion" |
040 | Functionality is only available if BW/4HANA starter add-on is installed |
041 | Source system &1 cannot have more than 10 characters |
042 | Target name &1 cannot be used twice |
043 | Objects written successfully to transport request &1 |
044 | Objects successfully stored on database |
045 | Objects successfully stored in remote system |
046 | No Task List Runs found |
047 | Run &1 contains objects of current scope; Continue run. |
048 | Object &1 &2 was already transferred before; First reset old transfer |
049 | InfoObject &1 must have all data activated |
050 | Process variant &1: Zero elimination is not supported |
051 | Process variant &1: Deletion before date is not supported anymore |
052 | Process variant &1: Function &2 with value '&3' is not supported |
053 | Process variant &1: DTP &2 is not a full DTP |
054 | Process variant &1 will be deleted |
055 | Process variant &1: InfoPackage not supported |
056 | InfoSet &1: No transfer possible for InfoSets with only one PartProvider |
057 | InfoSet &1: Anti-Join is not supported in CompositeProvider |
058 | InfoSet &1: "Most Recent Reporting for InfoObjs" not supported |
059 | InfoSet &1: "LeftOuter: Filter on ON-Condition" is not supported |
060 | InfoSet &1: "Local Grouping before Join" is mandatory |
061 | InfoSet &1: Referencing key figure &1 not supported during transfer |
062 | Process variant &1 is obsolete |
063 | &1 not found or not released for ODP (see SAP Notes 2232584 and 1560241) |
064 | Source system type &1 is not supported (system &2) |
065 | No authorization for debugging |
066 | Object &1 &2 is inactive; Activate it before using the Transfer Tool |
067 | Object &1 &2 cannot be transported |
068 | Object &1 (&2) cannot be transferred |
069 | Transfer not possible for &1. It is part of the SPO/HybridProvider. |
070 | Aggregation level &1 on InfoCube/DataStore needs to be remodeled |
071 | SAP HANA analysis process &1 needs to be remodeled |
072 | Transfer for InfoCube &1 not possible. Auditing is switched on. |
073 | Transfer for &1 not possible because DAP exists |
074 | Transfer of SAP HANA-optimized DataStore object &1 is not possible |
075 | InfoCube &1 needs to be converted to HANA-optimized |
076 | Write-optimized DataStore &1 has no key and is used for reporting |
077 | MultiProvider &1: "Accept Inconsistency During Compounding" not supported |
078 | MultiProvider &1: Mapping from &2 not possible (InfoObject on HANA model) |
079 | InfoCube &1: Execute report RSDD_SWITCH_NCUM_HANDLING before transfer |
080 | Main partition InfoObject is not maintained for &1. |
081 | Main partition InfoObject &1 is not possible for &2. |
082 | Target object ADSO for multi-segment DataSource (&1 (&2)) not supported |
083 | InfoCubes with inventory handling and DAP cannot be converted |
084 | Write-optimized DataStore Object &1 has DAP and is used for reporting |
085 | InfoProvider with ADK archive only cannot be converted |
086 | Implement note & before using this function |
087 | Object &1 &2 not part of current scope; Navigation not possible |
088 | Maintain target system in scope collection task |
089 | Select at least one line |
090 | Inconsistencies in request tables |
091 | Transfer at least one delta InfoPackage (like &1) for DataSource &2 |
092 | Create a delta InfoPackage for DataSource &1 and transfer it |
093 | Task &1 not allowed in check task list |
094 | Task is not executed in check task list |
095 | 3.x object &1 &2 will be skipped. Consider 3.x migration instead. |
099 | Target name &1 is already used for old object &2 |
100 | Unchecked usages exist |
101 | Usage of &2 for object &1 was manually set to solved |
102 | All findings solved |
103 | Finding &1 &2 still exists |
104 | Finding &1 &2 is resolved |
105 | New finding exists for &1 &2 |
106 | No findings solved |
107 | Check is not possible |
108 | Finding &1 &2 (line &3) still exists |
109 | New finding exists for &1 &2 (line &3) |
110 | Data could not be uploaded (same data already exists) |
111 | Move of statistic data successful |
112 | Move of statistic data failed |
113 | No data available for move |
114 | Field-based DataStore &1 is a not released feature (see Note 1922533) |
115 | NO2 aggregation is not supported for key figure &1 in &2 |
116 | Delete requests in Transport Organizer only |
117 | InfoProvider &1 has &2 requests; delete or reduce them |
118 | Run &1 contains objects of current scope; Finalize or continue this run. |
119 | Object &1 &2 is used by SEM BCS. Transfer only during Ready4Conversion. |
120 | InfoProvider &1 has &2 requests; a reduction is not possible |
125 | Consider an ADSO as transfer object for data source &1 (see long text) |
126 | &1 requests have not been propagated yet by delta DTP &2 |
127 | There are &1 records in the error stack of DTP &2 |
128 | There is still data in the PSA of DataSource &1 which must be processed |
200 | In receiver &4 there is no active sender system for remote transfer |
201 | Source systen &1 in receiver &4 has the wrong type (&2 instead of &3) |
202 | Source system &1 in receiver &4 has wrong client (&2 instead of &3) |
203 | Source system &1 in receiver &4 has wrong physical system (&2 inst. &3) |
224 | Some objects in &1 already transferred from another sender &2 &3 |