The Performer Suite works with entities from the SAP BW system. To provide a fast selection on of entities of all types the entities are stored in the application's database itself.
After installing the software the your database is empty, so it has to be synchronized with the your target SAP system(s)systems. This implies that the entities and some of their properties (timestamp, description, InfoArea, etc.) are captured into the database of the Performer Suite's database (only little properties are stored).
As soon as any a documentation is createdexported, the details will directly be directly be read from SAP using BAPIs or RFC Function Modules. This means it is not possible to create technical documentation without being connected to the your SAP system.
The synchronization Your SAP Synchronization is necessary in the following cases:
- After your first installation, when the your database is still empty
- When If in the meantime new entities have been created in your SAPWhen
- If meanwhile descriptions in your SAP have been changed in SAP
- When a selection of entities by date of change is done (to update the dates of change that are saved in the your database)
A Synchronization is relevant for the selection of entities because during selections the entities are read from the your database. But
On the other side, every documentation-related information is read directly from the your SAP system, so no worries that an outdated documentation will be created when no this way your documentations will always be up-to-date, even when no SAP synchronization has been done performed before. The only exception is that descriptions
Exception: Descriptions of entities and some InfoObject details (Type, Length, Reference Characteristic) are still read from the your database.
Those properties are usually not changed in your SAP and it improves the performance of the document generation a lot when those details are read from the Performer Suite database instead of from your SAP.
| Info |
|---|
| Implementing the application with a central database will eliminate the need for each user to carry out the synchronization individually. |
...
The synchronization of SAP tables requires to add adding either development class or single tables manually.
...
Because the table documentation uses SAP standard Function Module RFC_READ_TABLE there are the following restrictions regarding the possibility to create table documentations:
...