ConfigPanel - Technical Settings
The Technical Settings screen in the ConfigPanel is used to change the framework technical settings for application logs viewable in SAP. These application logs are logging levels and conversion exit logs.

-
Application Logging Level: Defines the logging level for all framework components. Logging entries are recorded in the SAP application log database under the object </syclo/>.
The logging levels are:
-
No logging
-
Abort
-
Error
-
Warning
-
Info
-
Debug
-
Trace
-
-
Enqueue Wait Time (Sec): If an SAP object is locked and inaccessible during an update by a mobile device, this parameter controls the number of seconds the underlying component continues to attempt to access the locked object in intervals of one second. If accessing the locked object is still unsuccessful after the wait time, the update process aborts.
-
Internal Conversion Exit Active: When checked, the framework runtime data manager performs standard SAP external-to-internal format conversion exit for all inbound BAPI parameters. The option is enabled by default. Only an application developer should change the Internal Conversion Exit Active setting, as changing it directly impacts the mobile application.
-
External Conversion Exit Active: When enabled, the framework runtime data manager performs standard SAP internal-to-external format conversion exit for all outbound BAPI parameters. The option is enabled by default. Only an application developer should change the External Conversion Exit Active setting, as changing it directly impacts the mobile application.
-
Range Parameter Check Active: When enabled, the framework runtime data manager performs checks on all SAP range parameters of inbound BAPI parameters. The SAP range parameter has the structure of SIGN, OPTION, LOW and HIGH. The check routine sets the SIGN value to I and the OPTION value to EQ if not specified. The option is enabled by default. Only an application developer should change the Range Parameter Check Active setting, as changing it directly impacts the mobile application.
-
Collection Mode: Determines how system statistic records are written to the database. Two modes are supported currently: Synchronously and Asynchronously. When Synchronously is selected, the statistics record is written to the database in real-time during BAPI calls. However, selecting Synchronously incurs a performance penalty. Selecting Asynchronously means that statistics are collected in-memory and written asynchronously to the database at the end of the BAPI call.
-
Statistic Collection Active: When enabled, the framework records all runtime statistics associated with the BAPI calls between the middleware server and SAP. The statistic collection provides data for the KPI statistics collections found in the Administration Portal. Only an application developer should change the Statistic Collection Active setting, as changing it directly impacts the mobile application.
-
Created By, Creation Time Stamp, Last Changed By, Changed Time Stamp: The user ID and time stamps are automatically logged when a record is created or changed.