SAP LOG_CONTENT_ORDER Function Module for NOTRANSL: Anreicherung Kundenauftrag für SAP BW
LOG_CONTENT_ORDER is a standard log content order SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Anreicherung Kundenauftrag für SAP BW processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for log content order FM, simply by entering the name LOG_CONTENT_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCRS
Program Name: SAPLMCRS
Main Program: SAPLMCRS
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOG_CONTENT_ORDER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'LOG_CONTENT_ORDER'"NOTRANSL: Anreicherung Kundenauftrag für SAP BW.
EXPORTING
* XMCVBAK = "
XMCCONTROL = "
BW_APPL = "
CHANGING
XMCVBAP = "
IMPORTING Parameters details for LOG_CONTENT_ORDER
XMCVBAK -
Data type: MCVBAKBOptional: Yes
Call by Reference: Yes
XMCCONTROL -
Data type: MCCONTROLOptional: No
Call by Reference: Yes
BW_APPL -
Data type: MCBW_ZUSA-BWINDUSOptional: No
Call by Reference: Yes
CHANGING Parameters details for LOG_CONTENT_ORDER
XMCVBAP -
Data type: MCVBAPBOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LOG_CONTENT_ORDER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_xmcvbak | TYPE MCVBAKB, " | |||
| lv_xmcvbap | TYPE MCVBAPB, " | |||
| lv_xmccontrol | TYPE MCCONTROL, " | |||
| lv_bw_appl | TYPE MCBW_ZUSA-BWINDUS. " |
|   CALL FUNCTION 'LOG_CONTENT_ORDER' "NOTRANSL: Anreicherung Kundenauftrag für SAP BW |
| EXPORTING | ||
| XMCVBAK | = lv_xmcvbak | |
| XMCCONTROL | = lv_xmccontrol | |
| BW_APPL | = lv_bw_appl | |
| CHANGING | ||
| XMCVBAP | = lv_xmcvbap | |
| . " LOG_CONTENT_ORDER | ||
ABAP code using 7.40 inline data declarations to call FM LOG_CONTENT_ORDER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single BWINDUS FROM MCBW_ZUSA INTO @DATA(ld_bw_appl). | ||||
Search for further information about these or an SAP related objects