Method GET_INSTANCE_ID_DICTIONARY
Function
Method GET_INSTANCE_ID_DICTIONARY provides an instance of interface IF_UKM_ID_DICTIONARY.
Prerequisites
If a preconfigured context is to be used, it must be entered in Customizing. The dependent database tables must be active and you must have access permission.
Parameters
|
Type |
Name |
Description |
|
Import |
IV_MAIN_CONTEXT_ID |
The interface is instantiated for the specific context. Therefore the correct context must already be defined at instantiation. If the context is left initial during the call, the interface is set up for the standard context. This context uses the database tables that are delivered by default with UKMS. |
|
Import |
IV_DIRECT_DB_INSERT |
By default, changes are only persisted when the update is started. However, if this parameter is set to ABAP_TRUE, the changes are written directly to the database. Only a Commit Work is required. This mode is not recommended. |
|
Import |
IV_RUNTIME_GENERATED_CONTEXT |
The parameter defines if the context specified in IV_MAIN_CONTEXT_ID should be a preconfigured context (customizing context) or a runtime-generated context. An IV_MAIN_CONTEXT_ID can be defined at both times. However, different database tables are used as repository. |
|
Export |
ER_IF_UKM_ID_DICTIONARY |
This export parameter contains the instance for the required interface. |
|
Export |
ES_MESSAGE |
This export parameter can contain a list of messages about processing. |
|
Changing |
CV_BUFFER_LINES_MAX |
The processing logic uses internal tables for buffering in order to accelerate access and to store unsaved data until the update is started. The maximum number of entries to be buffered can be limited with the parameter. If the buffer limit is reached, data can only be read or changed again after explicitly emptying the buffer or updating. |