Developper CASE en API
Developper CASE en API
Developper CASE en API
Case Management
Case Management
Developer Documentation
January 15, 2004
Contents
1 Einleitung ........................................................................................................................ 4
2 Case Management API................................................................................................... 4
=?> @
Update.......................................................................................................................................................... 4
=?>A=
!" #$
%&'()#$*+%-,. /%-012435'6879
:;*.)
<
2.3.37
2.3.38
2.3.39
SAVE .............................................................................................................................................. 22
SET_CLIENT_FRAMWORK_ID ..................................................................................................... 23
SET_ROOT_OBJECT .................................................................................................................... 23
!" #$
%&'()#$*+%-,. /%-012435'6879
:;*.)
1 Einleitung
Case Management has been designed as a reuse component. Applications are provided with a range of
options for integrating and customizing Case Management. Most of the activities require d to customize Case
Management are incorporated as Customizing settings in the Implementation Guide (IMG). Each of the
activities is documented online.
The following documentation refers to those topics that require you to perform implementation tasks:
System-driven execution of case-related activities; for this, you use Case Management API.
DFE&G
Update
The update must be activated centrally using the methods Create or OPEN_CASE (with a parameter). All
other methods evaluate the settings made here.
DFEHD
To implement the API, you need to connect it to the framework. The methods can be called from an active
framework. To make this connection, call the set_root_object method. This makes sure that the active
framework is also used for the API methods.
If the program is independent, and is not provided with a framework, then each of the methods is checked
implicitly to see whether the framework is activated. The framework is activated if it is inactive.
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE
SRMBOOLEAN (optional)
DEFAULT
IF_SRM=>FALSE
EX_SKIPPED
TYPE
EX_VALUES
TYPE
TY_NAMEVALUEASSTRING
IM_RESELECT_DB
EXPORTING:
Exceptions:
FAILED
!" #$
%&'()#$*+%-,. /%-012435'6879
:;*.)
Example:
2.3.2 ATTRIBUTE_CHANGE
Description: Change a case attribute
Call sequence: OPEN_CASE -> ATTRIBUTE_GET -> ATTRIBUTE_CHANGE -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_VALUE
TYPE
STRING
IM_FIELDNAME
TYPE
STRING
IM_CHECK_AUTHORITY
TYPE
XFELD (optional)
DEFAULT
SPACE
Exceptions:
FAILED
NO_AUTHORITY
Example:
2.3.3 ATTRIBUTE_GET
Description: Get a case attribute
Call sequence: OPEN_CASE -> ATTRIBUT_GET ->CLOSE_CASE
Parameters:
IMPORTING:
IM_FIELDNAME
TYPE
STRING
IM_CHECK_AUTHORITY
TYPE
XFELD
DEFAULT
SPACE
TYPE
SRMBOOLEAN (optional)
DEFAULT
IF_SRM=>FALSE
IM_RESELECT_DB
!" #$
%&'()#$*+%-,. /%-012435'6879
:;*.)
RETURNING:
RE_VALUE
TYPE
STRING
Exceptions:
FAILED
NO_AUTHORITY
Example:
2.3.4 AUTHORITY_CHECK
Description: Check the authorization for an activity
Call sequence: OPEN_CASE -> AUTHORITY_CHECK ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ACTIVITY
TYPE
SCMG_AUT_ACTIVITY
TYPE
SY-SUBRC
RETURNING:
RE_RESULT
Exceptions:
FAILED
Example:
8M 4
UMP
8PPPPPPPP PPPP
MM2
PPPPPPPP
PPMU
2.3.5 AUTHORITY_CHECK_FIELD
Description: Check authorization for accessing a field
Call sequence: OPEN_CASE ->AUTHORITY_CHECK_FIELD ->CLOSE_CASE
Parameters:
IMPORTING:
IM_FIELDNAME
TYPE
FIELDNAME
IM_ACTIVITY_FIELD
TYPE
ACTIV_AUTH
TYPE
SY-SUBRC
RETURNING:
RE_RESULT
"$
&()$+-./-245689
;.)
Exceptions:
FAILED
Example:
MM2
PPPPPPPP
PPMU
2.3.6 BOR_OBJECTS_GET
Description: Get all BOR objects (for a specific anchor). The anchor must be defined in the record model.
Call sequence: OPEN_CASE -> BOR_OBJECTS_GET ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING (optional)
IM_BOR_TYPE
TYPE
OJ_NAME (optional)
IM_BOR_KEY
TYPE
SWO_TYPEID (optional)
TYPE
SCMG_TT_BOR_IN_RECORD
RETURNING:
RE_BOR_OBJECTS
Exceptions:
FAILED
Example:
2.3.7 BOR_OBJECT_DELETE
Description: Delete a BOR object in the case record. You have two options: Either you specify the BOR
object using the parameters IM_ANCHOR, IM_BOR_KEY, IM_BOR_TYPE, and IM_SPS_ID (in this case, all
these parameters are mandatory), or you specify the BOR object using the node ID. You then need only to
specify the IM_ID parameter. In the second variant, all objects below the record node are deleted.
Call sequence: OPEN_CASE -> BOR_OBJECT_DELETE -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ID
TYPE
"$
&()$+-./-245689
STRING (optional)
;.)
IM_ANCHOR
TYPE
STRING (optional)
IM_BOR_KEY
TYPE
SWO_TYPEID (optional)
IM_BOR_TYPE
TYPE
OJ_NAME (optional)
IM_SPS_ID
TYPE
STRING (optional)
Exceptions:
FAILED
INVALID_PARAMETERS
Example:
MPP8PP 4
Or alternatively:
2.3.8 BOR_OBJECT_INSERT
Description: Insert a BOR object in the case record
Explanation: The anchor must be defined in the record model; BOR_KEY is the key of the fixed BOR object;
BOR_TYPE is the BOR type; and SPS_ID is the element type for the BOR type in Case Management.
Call sequence: OPEN_CASE -> BOR_OBJECT_INSERT -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING
IM_BOR_KEY
TYPE
SWO_TYPEID
IM_BOR_TYPE
TYPE
OJ_NAME
IM_DESCRIPTION
TYPE
STRING (optional)
IM_SPS_ID
TYPE
STRING
IM_RELATIONS
TYPE
SRM_XML_RELA_TAB (optional)
IM_PROPERTIES
TYPE
TY_NAMEVALUEASSTRING (optional)
Exceptions:
FAILED
NOT_ENQUEUED
Example:
"$
&()$+-./-245689
;.)
MPP8PP 4
2.3.9 CLOSE_CASE
Description: Close the case after it has been processed
Explanation: The case is unlocked and the connection to the back end is closed.
Example:
2.3.10 CREATE
Description: Create a case
Explanation: After an OPEN_CASE, a decision is made about whether the case is updated or not
(IM_UPDATE_TASK = IF_SRM=>FALSE). By default, there is no update.
The IM_WITH_PATH parameter is obsolete and is no longer evaluated. The process route is now created in
accordance with the configuration in the case type.
The IM_PATH_TEMPLATE parameter can be used to load a process route model into the current process
route directly after the case is created.
IM_CASE_TYPE
TYPE
SCMGCASE_TYPE
IM_CHECK_AUTHORITY
TYPE
XFELD (optional)
DEFAULT
SPACE
IM_CASE_GUID
TYPE
SCMG_CASE_GUID (optional)
IM_WITH_PATH
TYPE
XFELD (optional)
DEFAULT
SPACE ) (obsolete)
IM_PATH_TEMPLATE
TYPE
SRMWFPTHID (optional)
IM_UPDATE_TASK
TYPE
SRMBOOLEAN (optional)
DEFAULT IF_SRM=>FALSE
RETURNING:
RE_CASE
TYPE REF TO
IF_SCMG_CASE_API
Exceptions:
"$
&()$+-./-245689
;.)
FAILED
NO_AUTHORITY
Example:
MPP8PP 4
2.3.11 DELETE
Description: Delete the case
Explanation: An internal flag is set that prevents the API functions from being used to process this case any
further. The case also cannot be saved.
Call sequence: OPEN_CASE -> DELETE
Parameters:
IMPORTING:
IM_CHECK_AUTHORITY
TYPE
XFELD (optional)
DEFAULT
SPACE
IM_DELETE_FROM_CONTAINER TYPE
DEFAULT
SRMBOOLEAN (optional)
IF_SRM=>FALSE
Exceptions:
FAILED
NO_AUTHORITY
CONTAINER_ENQUEUED
Example:
UMP8MUMPPMP4P
x
xP
2.3.12 DEQUEUE
Description: Unlock a case
Call sequence: OPEN_CASE -> -> DEQUEUE ->CLOSE_CASE
Parameters:
RETURNING:
RE_OKAY
TYPE
XFELD
Exceptions:
"$
&()$+-./-245689
;.)
"
FAILED
Example:
UMPP4&PPPPP4 4
2.3.13 ELEMENT_DELETE
Description: Delete an object in the case record. You have two options: Either you specify the object using
the parameters IM_ANCHOR, IM_SP_POID, and IM_SPS_ID (in this case, all these parameters are
mandatory), or you specify the object using the node ID. You then need only to specify the IM_ID parameter.
In the second variant, all objects below the specified record node in t he hierarchy are deleted.
Call sequence: OPEN_CASE -> ELEMENT_DELETE -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING (optional)
IM_SPS_ID
TYPE
STRING (optional)
IM_SP_POID
TYPE
SRM_LIST_POID (optional)
IM_ID
TYPE
STRING (optional)
Exceptions:
FAILED
INVALID_PARAMETERS
Example:
MPP8PP 4
Or alternatively:
2.3.14 ELEMENT_INSERT
Description: Insert an object in the case record
Explanation: There are two options for inserting elements, either using the model ID (the node ID in the
record model) or using the anchor. The anchor must then be defined in the record model. One of these two
parameters must be specified. If you specify both parameters, then the object is inserted in the specified
anchor. In both cases, you must specify the element type (SPS ID) and the corresponding parameters for
finding the POID of the object.
Call sequence: OPEN_CASE -> ELEMENT_ADD -> SAVE ->CLOSE_CASE
"$
&()$+-./-245689
;.)
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING (optional)
IM_SP_POID
TYPE
SRM_LIST_POID
IM_SPS_ID
TYPE
STRING
IM_MODEL_ID
TYPE
STRING (optional)
IM_DESCRIPTION
TYPE
STRING (optional)
IM_RELATIONS
TYPE
SRM_XML_RELA_TAB (optional)
IM_PROPERTIES
TYPE
TY_NAMEVALUEASSTRING (optional)
Exceptions:
FAILED
NOT_ENQUEUED
Example:
MPP8PP 4
Or alternatively:
2.3.15 ENQUEUE
Description: Lock a case
Explanation: If OPEN_CASE is not called with the lock parameter, then you can use ENQUEUE to lock the
case.
Call sequence: OPEN_CASE -> -> ENQUEUE -> ... -> DEQUEUE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_SCOPE
TYPE
STRING (optional)
DEFAULT IF_SRM_SP_ENQUEUE=>SCOPE_DIALOG
IM_MODE
TYPE
STRING (optional)
DEFAULT IF_SRM_SP_ENQUEUE=>MODE_EXCLUSIVE
RETURNING:
"$
&()$+-./-245689
;.)
"
RE_OKAY
TYPE
XFELD
Exceptions:
FAILED
ENQUEUED
Example:
2.3.16 FIND_CASES_BY_ATTRIBUTE
Description: Find cases with the given attributes
Call sequence: FIND_CASES_BY_ATTRIBUTE
Parameters:
IMPORTING:
IM_SEARCH_FIELDS
TYPE
TY_NAMEVALUEASSTRING
TYPE
SCMG_TT_CASE_GUID (optional)
CHANGING:
CH_CASE_GUIDS
Exceptions:
FAILED
NOTHING_FOUND
Example:
2.3.17 FIND_CASES_BY_ATTR_RANGES
Description: Find cases with the specified search parameters
Explanation: You can use the following in the search criteria: groups (within a group: OR relationship;
between different groups: AND relationship), ranges (upper and lower value of an attribute), and operators
(EQ (equal), NE (not equal), BT (between), NB (not between), GE (greater than or equal), GT (greater than),
LE (less than or equal), LT (less than), CP (contains pattern), NP (not pattern)). The search is conducted in
the standard table and in the customer table (if specified).
"$
&()$+-./-245689
;.)
"
TYPE
SDM_QUERY_DESC_TAB
IM_CUST_TABLE
TYPE
TABLENAME (optional)
IM_MAX_NUM_OF_CASES
TYPE
I (optional)
TYPE
SCMG_TT_CASE_GUID
EXPORTING:
EX_CASE_GUIDS
Exceptions:
NOTHING_FOUND
WRONG_MAX_NUM
WRONG_PROPERTIE
WRONG_OP
Example:
2.3.18 FIND_CASES_BY_BOR_OBJECT
Description: Find cases with the BOR object
Call sequence: FIND_CASES_BY_BOR_OBJECT
Parameters:
IMPORTING:
IM_BOR_TYPE
TYPE
OJ_NAME
IM_BOR_KEY
TYPE
SWO_TYPEID
IM_SPS_ID
TYPE
STRING
IM_RMS_ID
TYPE
STRING
IM_RELATION
TYPE
STRING (optional)
DEFAULT
CT
TYPE
SCMG_TT_CASE_GUID
EXPORTING:
EX_T_CASE_GUIDS
Exceptions:
FAILED
"$
&()$+-./-245689
;.)
"
Example:
2.3.19 GET_ALL_OBJECTS
Description: Get objects from the case record
Call sequence: OPEN_CASE -> GET_ALL_OBJECTS ->CLOSE_CASE
Parameters:
RETURNING:
RE_ELEMENTS
TYPE
SRM_REC_ELEM_TAB
Exceptions:
FAILED
Example:
2.3.20 GET_ALL_SUBCOMPONENTS
Description: Gets all subcomponents of the case and fills G_SUB_INTERFACE
Call sequence: OPEN_CASE -> GET_ALL_SUBCOMPONENTS ->CLOSE_CASE
Parameters:
IMPORTING:
IM_CASE_TYPE
TYPE
STRING
Exceptions:
CX_SRM_SPCL_UNEXPECTED
Example:
2.3.21 GET_BACKEND_CASE
Description: Get the case back end
Parameters:
RETURNING:
RE_CASE_BACKEND
TYPE REF TO
"$
&()$+-./-245689
IF_SCMG_CASE
;.)
"
Exceptions:
FAILED
Example:
2.3.22 GET_BACKEND_NOTES
Description: Get the notes back end
Parameters:
RETURNING:
RE_NOTES_BACKEND
TYPE REF TO
IF_SCMG_SP_CASE_NOTES_BACKEND
Exceptions:
FAILED
Example:
2.3.23 GET_BACKEND_RECORD
Description: Get the records back end
Parameters:
RETURNING:
RE_RECORD_BACKEND
TYPE REF TO
IF_SRM_SP_RECORD
Exceptions:
FAILED
Example:
2.3.24 GET_BACKEND_WF_PATH
Description: Get the process route API
Parameters:
IMPORTING:
IM_CREATE_IF_NONE
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE REF TO
CL_SRM_WF_PATH
RETURNING:
RE_WF_PATH_API
"$
&()$+-./-245689
;.)
"
Exceptions:
FAILED
NOT_ENQUEUED
Example:
2.3.25 GET_BACKEND_WF_STATE
Description: Get the process route status
Parameters:
RETURNING:
RE_WF_STATE
TYPE
SRMWFPTHST
Example:
TYPE
SCMG_CASE_GUID
IM_ENQUEUE
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE
STRING (optional)
IM_MODE
DEFAULT IF_SRM_SP_ENQUEUE=>MODE_EXCLUSIVE
IM_SCOPE
TYPE
STRING (optional)
DEFAULT IF_SRM_SP_ENQUEUE=>SCOPE_DIALOG
IM_UPDATE_TASK
TYPE
SRMBOOLEAN (optional)
DEFAULT IF_SRM=>FALSE
RETURNING:
RE_CASE
TYPE REF TO
"$
&()$+-./-245689
IF_SCMG_CASE_API
;.)
"
Exceptions:
FAILED
ENQUEUE_FAILED
INVALID_GUID
Example:
2.3.27 GET_CASE_TEXT
Description: Get the terminology that is set in Customizing; by default, the text is "Case".
Call sequence: OPEN_CASE -> GET_CASE_TEXT ->CLOSE_CASE
Parameters:
IMPORTING:
IM_TERMID
TYPE
SCMGTERMID (optional)
DEFAULT
CASE
TYPE
SCMGTERM
RETURNING:
RE_TERMID
Exceptions:
Example:
2.3.28 GET_INSTANCES_FOR_REC_ANCHOR
Description: Get all elements in the case record. If the anchor is specified as a parameter, then only this
anchors elements are found.
Call sequence: OPEN_CASE -> GET_INSTANCES_FOR_REC_ANCHOR ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING (optional)
TYPE
SCMG_TT_INST_IN_RECORD
RETURNING:
RE_ELEMENT_TABLE
Exceptions:
FAILED
Example:
"$
&()$+-./-245689
;.)
"
2.3.29 GET_LINKED_OBJECTS
Description: Get objects from the case record
Not yet implemented.
Parameters:
IMPORTING:
IM_BOR_OBJECT_TYPE
TYPE
SWO_OBJTYP (optional)
TYPE
TY_NAMEVALUEASSTRING
RETURNING:
RE_OBJECTS
Exceptions:
FAILED
2.3.30 GET_RECORD_OPEN
TYPE
SRMBOOLEAN
Exceptions:
Example:
l_record_open = l_case->get_record_open( ).
2.3.31 GET_VICINITY
Description: Get the supercases and subcases for a case
Parameters:
IMPORTING:
IM_ANCHOR
TYPE
STRING (optional)
DEFAULT
CZ
EXPORTING:
EX_SUPERCASES_GUID_TAB TYPE
SCMG_TT_CASE_GUID
EX_SUBCASES_GUID_TAB
SCMG_TT_CASE_GUID
TYPE
Exceptions:
Example:
"$
&()$+-./-245689
;.)
"
2.3.32 LOG_READ
Description: Get the log
Call sequence: OPEN_CASE -> LOG_READ ->CLOSE_CASE
Parameters:
IMPORTING:
IM_START_DATE
TYPE
D (optional)
IM_END_DATE
TYPE
D (optional)
IM_MAX_ROWS
TYPE
I (optional)
TYPE
SRMPT_PROTO_ENTRY_TAB
EXPORTING:
EX_ENTRIES
Exceptions:
Example:
2.3.33 LOG_WRITE
Description: Write the log
Call sequence: OPEN_CASE -> LOG_WRITE -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ACTIVITY
TYPE
STRING
IM_ARG1
TYPE
STRING
IM_ARG2
TYPE
STRING
IM_ARG_STRING
TYPE
STRING
Exceptions:
FAILED
Example:
MPP8PP 4
2.3.34 NOTES_GET
Description: Get notes
Call sequence: OPEN_CASE -> NOTES_GET ->CLOSE_CASE
"$
&()$+-./-245689
;.)
Parameters:
IMPORTING:
IM_TEXT_TYPE
TYPE
TDID (optional)
IM_DATE_FROM
TYPE
D (optional)
IM_DATA_TO
TYPE
D (optional)
IM_CREATED_BY
TYPE
SYUNAME (optional)
IM_KEYWORD
TYPE
STRING (optional)
IM_DB_UPDATE
TYPE
XFELD (optional)
TYPE
TEXT_LH
RETURNING:
RE_TEXTS
Exceptions:
FAILED
Example:
2.3.35 NOTE_INSERT
Description: Insert a note for a case
Call sequence: OPEN_CASE -> NOTE_INSERT -> SAVE ->CLOSE_CASE
Parameters:
IMPORTING:
IM_ID
TYPE
TDID
IM_TEXT
TYPE
TLINETAB
IM_LANG
TYPE
TDSPRAS (optional)
DEFAULT
SY-LANGU
Exceptions:
FAILED
Example:
MPP8PP 4
"$
&()$+-./-245689
;.)
2.3.36 OPEN_CASE
Description: Open a case to be processed
Explanation: For the subsequent modifying operations, call the method with the log flag (IM_ENQUEUE =
X); otherwise other case actions will fail.
However, also avoid locking objects unnecessarily, since this generates unnecessary lock objects.
After a OPEN_CASE, a decision is made about whether the case is updated or not. IM_UPDATE_TASK =
IF_SRM=>FALSE
No update
IM_UPDATE_TASK = IF_SRM=>TRUE
Update
To close the transaction, use CLOSE_CASE.
Call sequence: OPEN_CASE -> -> CLOSE_CASE
Parameters:
IMPORTING:
IM_CASE_GUID
TYPE
SCMG_CASE_GUID
IM_ENQUEUE
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE
STRING (optional)
IM_MODE
DEFAULT IF_SRM_SP_ENQUEUE=>MODE_EXCLUSIVE
IM_SCOPE
TYPE
STRING (optional)
DEFAULT IF_SRM_SP_ENQUEUE=>SCOPE_DIALOG
IM_UPDATE_TASK
TYPE
SRMBOOLEAN (optional)
DEFAULT IF_SRM=>FALSE
RETURNING:
RE_CASE
TYPE REF TO
IF_SCMG_CASE_API
Exceptions:
FAILED
ENQUEUE_FAILED
INVALID_GUID
CX_SRM_GSP_BACK
Example:
2.3.37 SAVE
Description: Save a case
Explanation: If notes (Notes_Insert) are inserted in the actions (betwe en OPEN_CASE and Save), or if
events are triggered when attributes (such as the status) are changed, then a COMMIT_WORK must be
performed after Save( ); otherwise the changes or events might be lost.
Call sequence: OPEN_CASE -> -> SAVE ->CLOSE_CASE
"$
&()$+-./-245689
;.)
Parameters:
IMPORTING:
IM_DEQUEUE
IM_NEW_VERSION
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE
XFELD (optional)
DEFAULT
SPACE
TYPE
SCMG_T_ATTR_RETURN_VALUE
EXPORTING:
EX_MESSAGES
Exceptions:
FAILED
Example:
...
UMPP
->save(
UMP8PaP
MPP4&PPPP8PP4 a
).
2.3.38 SET_CLIENT_FRAMWORK_ID
Description: Set the client framework ID (if it is not the default framework)
Parameters:
IMPORTING:
IM_CLIENT_FW_ID
TYPE
STRING
EXPORTING:
CHANGING:
RETURNING:
Exceptions:
INSTANCE_EXISTS
FAILED
Example:
UMPPPPUMMP MPP8PPMPPPPPUMPPPPUMPP8PP8P4 4
2.3.39 SET_ROOT_OBJECT
Description: Set the root object (before the first GET, or similar action)
Explanation: You can use this method if you already have a framework, and you want to use this framework
for the API methods as well. This method must be called before all other API methods; otherwise an error is
triggered.
"$
&()$+-./-245689
;.)
Parameters:
IMPORTING:
IM_ROOT_OBJECT
TYPE REF TO
IF_SRM_ROOT
Exceptions:
DIFFERENT_NEW_ROOT_OBJECT
Example:
UMPPMPPP PUMPPMPPUMPPPPP8PPMPPP4 4
2.4.2 C_ACTIVITY_FIELD_MODIFY
Description: Constant Activity; field value Display (authorization check); initial value 03
Type: ACTIV_AUTH
2.4.3 G_CASE_GUID
Description: Technical key of the case
Type: SCMG_CASE_GUID
2.4.4 G_CASE_POID
Description: POID of the case
Type: IF_SRM_POID
2.4.5 G_CLIENT_FW_ID
Description: Framework ID default
Type: STRING
2.4.6 G_DELETED
Description: Case deleted, yes or no (X/space)
Type: XFELD
2.4.7 G_IS_ENQUEUED
Description: Lock set, yes or no (X/space)
Type: XFELD
"$
&()$+-./-245689
;.)
2.4.8 G_LAST_EXCEPTION
Description: Last exception raised (after FAILED)
Type: CX_ROOT
2.4.9 G_ROOT_OBJECT
Description: Root object
Type: IF_SRM_ROOT
2.4.10 G_SUB_INTERFACE
Description: Table with the interfaces of the subcomponents
Type: SCMG_TT_CASE_SUBCOMPONENTS_API
"$
&()$+-./-245689
;.)
IS_CHANGED( ): This method is called to determine whether any changes made to the subcomponent need
to be saved. In a dialog, the user then decides whether to save the case.
FINISH( ): This method is called when the user exits the case (by switching scre ens, for example). You might
need to release resources. There is no dialog.
ANSWER_ON_REQUEST( ): This method is relevant only for subcomponents that use service providers in
the passive in-place visualization. You do not normally need to implement this me thod.
Note: If you want to access the subcomponent using the case API as well, you must also implement the
IF_SCMG_SUBCOMPONENT_API interface. This is documented online in the system.
"$
&()$+-./-245689
;.)