SAP FTR_CORR_CREATE_PLAN_REC_EXT Function Module for External Creation of Planned Corresp. Record (Outside Trans. Processing)









FTR_CORR_CREATE_PLAN_REC_EXT is a standard ftr corr create plan rec ext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for External Creation of Planned Corresp. Record (Outside Trans. Processing) 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 ftr corr create plan rec ext FM, simply by entering the name FTR_CORR_CREATE_PLAN_REC_EXT into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_CORR_CREATE_PLAN_REC_EXT 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 'FTR_CORR_CREATE_PLAN_REC_EXT'"External Creation of Planned Corresp. Record (Outside Trans. Processing)
EXPORTING
I_VTBKORES_NEW = "Rohdaten für neuen Korrespondenzplansatz
* X_COMMIT_WORK = ' ' "

EXCEPTIONS
INVALID = 1 NOT_ALLOWED = 2 AUTHORITY = 3
.



IMPORTING Parameters details for FTR_CORR_CREATE_PLAN_REC_EXT

I_VTBKORES_NEW - Rohdaten für neuen Korrespondenzplansatz

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

X_COMMIT_WORK -

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

EXCEPTIONS details

INVALID - Access Incorrect

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

NOT_ALLOWED - Error

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

AUTHORITY - Authorization

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTR_CORR_CREATE_PLAN_REC_EXT 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_invalid  TYPE STRING, "   
lv_i_vtbkores_new  TYPE VTBKORES, "   
lv_not_allowed  TYPE VTBKORES, "   
lv_x_commit_work  TYPE BOOLE-BOOLE, "   SPACE
lv_authority  TYPE BOOLE. "   

  CALL FUNCTION 'FTR_CORR_CREATE_PLAN_REC_EXT'  "External Creation of Planned Corresp. Record (Outside Trans. Processing)
    EXPORTING
         I_VTBKORES_NEW = lv_i_vtbkores_new
         X_COMMIT_WORK = lv_x_commit_work
    EXCEPTIONS
        INVALID = 1
        NOT_ALLOWED = 2
        AUTHORITY = 3
. " FTR_CORR_CREATE_PLAN_REC_EXT




ABAP code using 7.40 inline data declarations to call FM FTR_CORR_CREATE_PLAN_REC_EXT

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 BOOLE FROM BOOLE INTO @DATA(ld_x_commit_work).
DATA(ld_x_commit_work) = ' '.
 
 


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!