In order to dynamically create a transaction code for starting a service or a remote service program in a partner application, you have to call KC_CREATE_OBJECT for the object type KC_LTAC.
The local transaction code is assigned either
the name of a transaction code in a specific partner application (with single-step addressing), in which case the local transaction code addresses both the partner application and the transaction code in this application, or
the name of a transaction code in any partner application (with double-step addressing). The partner application in which the service program addressed by the local transaction code is to run must be specified explicitly in the program interface.
If access rights are to be granted by means of an access list, the key set used for this must either already exist or be dynamically created beforehand; the dynamic creation of the key set and the referenced LTAC can also take place within a transaction. If the access rights are to be controlled by means of a lock code, the numeric value for the lock code must not be less than 1 or greater than the maximum value permitted in the application (KDCDEF statement MAX, KEYVALUE operand).
The following rule applies:
Key set (KC_KSET) before LTAC (KC_LTAC) |