INV_BPEM_LOG_MERGE SAP Method Merge Logs
Below is documentation, parameters and attributes of ABAP Method INV_BPEM_LOG_MERGE within SAP class CL_ISU_BPEM_ANALYSE_INVMON. There is also a number of example ABAP code snipts to help you use the functionality of this method.
This method is available within SAP systems depending on your version and release level, you can view further information by entering the class name CL_ISU_BPEM_ANALYSE_INVMON into the relevant SAP transactions such as SE24 or SE80, and then selecting the method you are interested in.
Method Type - Static
This is a Static Method so you can call it directlyThe following technical details of method INV_BPEM_LOG_MERGE can also be found below:
- Importing parameters
- Exporting parameters
- Changing parameters
- Returning parameters
- Exceptions
- Coding Examples
Parameters of Method INV_BPEM_LOG_MERGE
.| Name | Type | Data Type | Description | Default Value |
| IM_END_TIME | Importing | TYPE BALTIMSTMP | Application Log: Message Time Stamp | |
| IM_OBJECTKEY | Importing | TYPE EMMA_OBJKEY | Object Key | |
| IM_OVERALL_STATUS | Importing | TYPE CHAR1 | Single-Character Indicator | |
| IM_RUNID | Importing | TYPE EMMA_RUNID | Internal Job Number | |
| IM_START_TIME | Importing | TYPE BALTIMSTMP | Application Log: Message Time Stamp | |
| IM_T_INV_LOG_DATA | Importing | TYPE INV_LOG_DATA | Log Data Inbound Bill/Payment Advice Note Processing | |
| IM_T_MESSAGES | Importing | TYPE EMMA_MESSAGE_TAB | Table Type BALM | |
| IM_T_MESSAGE_CONTEXT | Importing | TYPE BALC_T | Application Log: Context data table | |
| IM_T_MESSAGE_PARA | Importing | TYPE EMMA_MESSAGE_PAR_TAB | Table Type for BALMP | |
| EX_T_RETURN | Exporting | TYPE BAPIRETTAB | Table with BAPI Return Information | |
| CH_CTBUSOBJ | Changing | TYPE EMMA_CTBUSOBJ | Status Counter of Business Objects Processed | |
| CH_MESSAGE_COUNT | Changing | TYPE I | Number of All Messages | |
| CH_T_MSGEO | Changing | TYPE EMMA_OBJ_MSG_TAB | Table of Objects with Messages for Case Determination | |
| CH_T_MSGSO | Changing | TYPE EMMA_OBJ_MSG_TAB | Table of Objects with Messages for Case Determination | |
| CH_T_MSGWO | Changing | TYPE EMMA_OBJ_MSG_TAB | Table of Objects with Messages for Case Determination |
Exceptions of Method INV_BPEM_LOG_MERGE
This method does not have any exceptionsExample ABAP coding
DATA: lv_CH_CTBUSOBJ TYPE EMMA_CTBUSOBJ,
lv_CH_MESSAGE_COUNT TYPE I,
lv_CH_T_MSGEO TYPE EMMA_OBJ_MSG_TAB,
lv_CH_T_MSGSO TYPE EMMA_OBJ_MSG_TAB,
lv_CH_T_MSGWO TYPE EMMA_OBJ_MSG_TAB,
lv_EX_T_RETURN TYPE BAPIRETTAB,
lv_IM_END_TIME TYPE BALTIMSTMP,
lv_IM_OBJECTKEY TYPE EMMA_OBJKEY,
lv_IM_OVERALL_STATUS TYPE CHAR1,
lv_IM_RUNID TYPE EMMA_RUNID,
lv_IM_START_TIME TYPE BALTIMSTMP,
lv_IM_T_INV_LOG_DATA TYPE INV_LOG_DATA,
lv_IM_T_MESSAGES TYPE EMMA_MESSAGE_TAB,
lv_IM_T_MESSAGE_CONTEXT TYPE BALC_T,
lv_IM_T_MESSAGE_PARA TYPE EMMA_MESSAGE_PAR_TAB,
lv_other TYPE c.
CALL METHOD CL_ISU_BPEM_ANALYSE_INVMON=>INV_BPEM_LOG_MERGE(
EXPORTING
IM_END_TIME = lv_IM_END_TIME
IM_OBJECTKEY = lv_IM_OBJECTKEY
IM_OVERALL_STATUS = lv_IM_OVERALL_STATUS
IM_RUNID = lv_IM_RUNID
IM_START_TIME = lv_IM_START_TIME
IM_T_INV_LOG_DATA = lv_IM_T_INV_LOG_DATA
IM_T_MESSAGES = lv_IM_T_MESSAGES
IM_T_MESSAGE_CONTEXT = lv_IM_T_MESSAGE_CONTEXT
IM_T_MESSAGE_PARA = lv_IM_T_MESSAGE_PARA
IMPORTING
EX_T_RETURN = lv_EX_T_RETURN
CHANGING
CH_CTBUSOBJ = lv_CH_CTBUSOBJ
CH_MESSAGE_COUNT = lv_CH_MESSAGE_COUNT
CH_T_MSGEO = lv_CH_T_MSGEO
CH_T_MSGSO = lv_CH_T_MSGSO
CH_T_MSGWO = lv_CH_T_MSGWO ).
Links to Related Class(s)
CL_ISU_B...Full list of available SAP object classes
Search for further information about these or an SAP related objects