SAP MP_PLAN_TEXTS_POST Function Module for









MP_PLAN_TEXTS_POST is a standard mp plan texts post 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 mp plan texts post FM, simply by entering the name MP_PLAN_TEXTS_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: MP_PLAN
Program Name: SAPLMP_PLAN
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MP_PLAN_TEXTS_POST 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 'MP_PLAN_TEXTS_POST'"
EXPORTING
PLAN_DATA = "
* NEW_TEXT = ' ' "

IMPORTING
TEXT_HEADER = "
POSTING_OK = "

TABLES
TEXT_LINES = "
MESSAGE_RETURN = "
.



IMPORTING Parameters details for MP_PLAN_TEXTS_POST

PLAN_DATA -

Data type: COSPA_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

NEW_TEXT -

Data type: MPO_PLAN_KSTAR_EXT-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MP_PLAN_TEXTS_POST

TEXT_HEADER -

Data type: THEAD
Optional: No
Call by Reference: No ( called with pass by value option)

POSTING_OK -

Data type: MPO_PLAN_KSTAR_EXT-FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MP_PLAN_TEXTS_POST

TEXT_LINES -

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

MESSAGE_RETURN -

Data type: BAPIRETURN1
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MP_PLAN_TEXTS_POST 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_plan_data  TYPE COSPA_KEY, "   
lt_text_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_text_header  TYPE THEAD, "   
lv_new_text  TYPE MPO_PLAN_KSTAR_EXT-FLAG, "   SPACE
lv_posting_ok  TYPE MPO_PLAN_KSTAR_EXT-FLAG, "   
lt_message_return  TYPE STANDARD TABLE OF BAPIRETURN1. "   

  CALL FUNCTION 'MP_PLAN_TEXTS_POST'  "
    EXPORTING
         PLAN_DATA = lv_plan_data
         NEW_TEXT = lv_new_text
    IMPORTING
         TEXT_HEADER = lv_text_header
         POSTING_OK = lv_posting_ok
    TABLES
         TEXT_LINES = lt_text_lines
         MESSAGE_RETURN = lt_message_return
. " MP_PLAN_TEXTS_POST




ABAP code using 7.40 inline data declarations to call FM MP_PLAN_TEXTS_POST

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 FLAG FROM MPO_PLAN_KSTAR_EXT INTO @DATA(ld_new_text).
DATA(ld_new_text) = ' '.
 
"SELECT single FLAG FROM MPO_PLAN_KSTAR_EXT INTO @DATA(ld_posting_ok).
 
 


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!