SAP COM_PROD_OUTBOUND_LGTEXT_READ Function Module for









COM_PROD_OUTBOUND_LGTEXT_READ is a standard com prod outbound lgtext read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 com prod outbound lgtext read FM, simply by entering the name COM_PROD_OUTBOUND_LGTEXT_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_COMM_PR_LGTEXT
Program Name: SAPLCOM_COMM_PR_LGTEXT
Main Program: SAPLCOM_COMM_PR_LGTEXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function COM_PROD_OUTBOUND_LGTEXT_READ 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 'COM_PROD_OUTBOUND_LGTEXT_READ'"
EXPORTING
IS_CHANGED_COMPONENT = "
IV_PRODUCT_GUID = "

CHANGING
CS_PRODUCT_HEADER = "
.



IMPORTING Parameters details for COM_PROD_OUTBOUND_LGTEXT_READ

IS_CHANGED_COMPONENT -

Data type: COMT_CHANGED_PR_COMP
Optional: No
Call by Reference: Yes

IV_PRODUCT_GUID -

Data type: COMT_PRODUCT_GUID
Optional: No
Call by Reference: Yes

CHANGING Parameters details for COM_PROD_OUTBOUND_LGTEXT_READ

CS_PRODUCT_HEADER -

Data type: COMT_PRODUCT_MAINTAIN_API
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_PROD_OUTBOUND_LGTEXT_READ 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_cs_product_header  TYPE COMT_PRODUCT_MAINTAIN_API, "   
lv_is_changed_component  TYPE COMT_CHANGED_PR_COMP, "   
lv_iv_product_guid  TYPE COMT_PRODUCT_GUID. "   

  CALL FUNCTION 'COM_PROD_OUTBOUND_LGTEXT_READ'  "
    EXPORTING
         IS_CHANGED_COMPONENT = lv_is_changed_component
         IV_PRODUCT_GUID = lv_iv_product_guid
    CHANGING
         CS_PRODUCT_HEADER = lv_cs_product_header
. " COM_PROD_OUTBOUND_LGTEXT_READ




ABAP code using 7.40 inline data declarations to call FM COM_PROD_OUTBOUND_LGTEXT_READ

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.

 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!