Use the method INIT_LOGGER of class /IWFND/CL_LOGGER to create the logger instance and to initiate the Applications Log protocol.
Note that for the backend system (where software component IW_BEP is deployed) a corresponding class exists called /IWBEP/CL_COS_LOGGER for OData Channel development.
For inbound processes:
This method should be called directly after a request has reached the Connectivity Layer. It will be used only by the framework.
For outbound processes:
Object and/or sub-object:
For application coding you need not specify these parameters when the logger is initiated. The logger will be initialized with the object /IWFND/ and sub-object DESTIM only for design time processes.
Request direction:
Specifies the direction of the request. Possible values are maintained as constants in the class itself and in the domain /IWFND/SUP_REQ_DIR.
Operation:
Specifies the operation executed on the business object type in the current request.
Examples are Create, Update, Delete, and Query.
Parameter Name |
Parameter Type |
Optional |
Data Type |
Def. Value |
---|---|---|---|---|
IV_USERID |
importing |
UNAME |
User Name |
|
IV_REQUESTGUID |
importing |
X |
STRING |
Request GUID |
IV_OBJECT |
importing |
X |
BALOBJ_D |
Object name |
IV_SUBOBJECT |
importing |
X |
BALSUBOBJ |
Subobject |
IV_REQUEST_DIRECTION |
importing |
X |
/IWFND/SUP_REQ_DIR |
Direction of the request |
IV_OPERATION |
importing |
X |
CHAR10 |
Character field length = 10 |
RO_LOGGER |
returning |
/IWFND/CL_LOGGER |
Logger instance |
Use the method GET_LOGGER of class /IWFND/CL_LOGGER to get the logger instance for which you have to create the log messages.
Parameter Name |
Parameter Type |
Optional |
Data Type |
Def. Value |
---|---|---|---|---|
RO_LOGGER |
returning |
/IWFND/CL_LOGGER |
Logger instance |
Use the method INIT_BUSINESS_PROCESS of class /IWFND/CL_LOGGER to initiate the processing scope in which only business messages are created.
Use the method FINISH_BUSINESS_PROCESS of class /IWFND/CL_LOGGER to finalize the processing scope in which only business messages are created. After this method only technical messages are created.
Use the method LOG_STEP_INIT of class /IWFND/CL_LOGGER to create the initiation log message.
The type of an initiation message is always I and so does not need to be specified here.
Parameter Name |
Parameter Type |
Optional |
Data Type |
Def. Value |
---|---|---|---|---|
IV_MSG_ID |
importing |
SYMSGID |
Message class |
|
IV_MSG_NUMBER |
importing |
SYMSGNO |
Message number |
|
IV_MSG_V1 |
importing |
X |
SYMSGV |
Message variable |
IV_MSG_V2 |
importing |
X |
SYMSGV |
Message variable |
IV_MSG_V3 |
importing |
X |
SYMSGV |
Message variable |
IV_MSG_V4 |
importing |
X |
SYMSGV |
Message variable |
IV_SYSTEM_ALIAS |
importing |
X |
/IWFND/DEFI_SYSTEM_ALIAS |
System alias |
IS_OBJECT_KEY |
importing |
X |
/IWFND/S_COR_ID |
ID of the object whose processing caused the errors |
IV_AGENT |
importing |
/IWFND/SUP_IW_AGENT |
IW agent |
|
RV_MSG_HANDLE |
returning |
BALMSGHNDL |
Application Log: Message handle |