The source data comes from the metadata describing the source tables and the entire mapping done in Studio. The metadata is imported into Studio and serves as the basis for the Source Map, the Source Engine will assure that the Staging database contains a corresponding table for each structure in the metadata.
Loading data in the Portal Operations is done in 2 steps:
- The data are reformatted from one of the know formats to a common load format.
- The reformatted data are loaded into the corresponding table in the Staging database.
Once these steps have been completed then the Data panel will show a list of all the tables in the Staging Database, as below.
Most tables are marked green, as they have already been loaded as part of earlier iterations of Business Objects Customer and Account.
Apart from the obvious like Alias and Name, the meaning of the columns in the list is:
| Files | The number of files to load. For instance. |
| Reformat | The reformatter to run on the received file to reformat it to the common format used to load data into the Staging database |
| Received file date | The date of the received file. If this file is newer than the Formatted file, it will be marked orange |
| Formatted file date | The date of the formatted file. If this file is newer than the loaded file, it will be marked orange |
| Date of loaded file | The date of the formatted file that was loaded into the Staging database. If this file is newer than the date the file was loaded, it will be marked orange |
| Loaded date | The date of the formatted file was loaded into the Staging database. |
| Baseline | A saved baseline of rows loaded into the Staging table |
| Loaded | The actual number of rows loaded into the Staging table |
Refresh is not automatic
In most of the panels in the Client Area of the Portal Operations, you will see this Refresh button in the upper right corner.
Using Portal Operations, you are really working in a client application sending instructions to the Runtime running on a server. In this simplified training setup, the Runtime is executing on the same machine you are using.
Action Context Menu
Within the Portal Operations you may notice three little dots when hovering above a record/Business Objects.
We refer to this as a Action Context Menu.
The Action Context Menu vary from page to page but it provides an additional way to navigate/validate a Business Object
The details for the context menu for this page are as below.
| Set Reformatter | This gives the option to change the format of the loaded file, the default is set to Reformatter DB2 but for most projects we use Csv |
| Truncate & Load | This enables all values to be deleted leaving the table structure to be loaded |
| Reformat | Enables the source file's format to be changed |
| Duplicates | Duplicate source file |
| Truncate | Delete all values of a table, leaving the table in tact |
| Clear file | Clear the file from the migration |
| Files | Opens the selected file |
We can load data by selecting a Business Object and selecting "File" option in the menu above which gives you the below popup dialog.
Next, in the above dialog you can, among other actions (like Reformat, Clear ..), offload a Business Object to a file.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article