...
Afterward, all needed Objects have to be marked and moved to the box on the right using drag and drop or the add-button. Where appropriate, name changes can be altered here.
...
In case objects are not valid for import, the tool-tip of each line indicates why an Object is not valid.
...
| Anchor | ||||
|---|---|---|---|---|
|
In this case, all Technical Names exceed the permitted length. One possibility could be to replace the first character of the Technical Name with “ZM_” (see below).
...
Finally, the New Technical Name is shortened to the correct length of 9 characters.
Easier: Use the "Cut Technical Names"-button, which cuts off the exceeded length of the New Technical Name from all Objects in the list.
...
By cutting off the names, Objects might become yellow which means that a duplicate with the same Technical Name was created (see below).
...
Only InfoObjects will be imported, which are verified by the system. Those are indicated using the checkbox in the first column. After a change is made, Objects are automatically checked for duplication. Nevertheless, it is not possible to enter a Technical Name that is too long. The “Start Import”-button is activated as soon as no more discrepancies exist.
Maximum Depth Level
| Anchor | ||||
|---|---|---|---|---|
|
A highly important function is the setting of "Level of Dependencies" for all Objects to import (see figure below).
...
In the beginning, the Maximum Depth Level is set to 0, which means that Objects will be imported with any depth. Changing the setting to 1 would result that only dependent and directly assigned attributes, as well as parentheses, are included in the import (if they are not part of the Modeling Project already).E.g. the Object InfoObject 0COMP_CODE is supposed to be imported with a “Maximum Depth Level” of 2. It does not refer to another Object or has any parentheses.
...
The import of InfoProvider is structured the same way as 3091905030Import Objects from SAP.
“Import as” – Functionalities
The drop-down menu for importing InfoProvider includes three options:
Keep Object Type
DataStore (applies to Cubes and MultiProvider)
BW/4HANA object types
If the first and also initial setting is chosen, each InfoProvider with the same InfoProvider Type from the same SAP Source System is imported.
...
The final option does the following:
Source Entity Type | Target Entity Type |
|---|---|
MultiProvider (MPRO) | HANA CompositeProvider (HCPR) |
InfoCube (CUBE) | Advanced Data Store Object (ADSO) |
Data Store Object (ODSO) | Advanced Data Store Object (ADSO) |
In doing so, provider-specific configurations are set automatically. For example, the setting “All Characteristics are Keys” for ADSOs is generated from InfoCubes.
...
In order to rename all contained entities use the “Rename included InfoObjects”-button (see screenshot below).
...
Maximum Depth Level
Again, a prefix can be used to replace a certain number of leading characters. This process follows the structure described 3091905030 Import Objects from SAP. “Level determines the depth to which Objects are renamed (see “3091905030Import Objects from SAP#Maximum Depth Level”). Changing the Level setting leads directly to an updated list of elements in the table below.SAP Core-Objects, like 0FISCPER, are not allowed to be renamed and therefore can’t be selected by the checkbox in the first column. Whereas entities aren’t preselected but can be chosen or renamed.
As soon as all inconsistencies are eliminated from the table the saving option becomes active. Renamed elements are now elements in the Modeling tool, including their updated name in the InfoProviders definition.
...