SAP PPC1PR_MAT_TRANSFER_EXE Function Module for DE-EN-LANG-SWITCH-NO-TRANSLATION









PPC1PR_MAT_TRANSFER_EXE is a standard ppc1pr mat transfer exe SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DE-EN-LANG-SWITCH-NO-TRANSLATION 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 ppc1pr mat transfer exe FM, simply by entering the name PPC1PR_MAT_TRANSFER_EXE into the relevant SAP transaction such as SE37 or SE38.

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



Function PPC1PR_MAT_TRANSFER_EXE 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 'PPC1PR_MAT_TRANSFER_EXE'"DE-EN-LANG-SWITCH-NO-TRANSLATION
EXPORTING
IT_COMP = "Component Structure for Aggregated Material Posting
IT_HEADID = "Table of Confirmations (GUIDs) (Generic ITab)
IF_POSTDATE = "Posting Date in the Document
IF_PLANT = "Plant
IF_FLG_INFO_DEST = "Target system for subsequent processing
IF_CONFLOGSYS = "System for entering the confirmation
* IF_LOG_HANDLE = "Application Log: Log Handle

IMPORTING
EF_MAT_LINES_TR_OK = "
EF_MAT_LINES_TR_FAIL = "

EXCEPTIONS
HEAD_ERROR = 1 WIP_ERROR = 2 PROTOCOL_ERROR = 3 INSERT_STEP2_ERROR = 4 LOCK_ERROR = 5
.



IMPORTING Parameters details for PPC1PR_MAT_TRANSFER_EXE

IT_COMP - Component Structure for Aggregated Material Posting

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

IT_HEADID - Table of Confirmations (GUIDs) (Generic ITab)

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

IF_POSTDATE - Posting Date in the Document

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

IF_PLANT - Plant

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

IF_FLG_INFO_DEST - Target system for subsequent processing

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

IF_CONFLOGSYS - System for entering the confirmation

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

IF_LOG_HANDLE - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PPC1PR_MAT_TRANSFER_EXE

EF_MAT_LINES_TR_OK -

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

EF_MAT_LINES_TR_FAIL -

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

EXCEPTIONS details

HEAD_ERROR -

Data type:
Optional: No
Call by Reference: Yes

WIP_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PROTOCOL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INSERT_STEP2_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LOCK_ERROR - Lock Errors

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPC1PR_MAT_TRANSFER_EXE 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_it_comp  TYPE PPC_COMP_TAB, "   
lv_head_error  TYPE PPC_COMP_TAB, "   
lv_ef_mat_lines_tr_ok  TYPE I, "   
lv_it_headid  TYPE PPC_T_HEADID_INTERN, "   
lv_wip_error  TYPE PPC_T_HEADID_INTERN, "   
lv_ef_mat_lines_tr_fail  TYPE I, "   
lv_if_postdate  TYPE BUDAT, "   
lv_protocol_error  TYPE BUDAT, "   
lv_if_plant  TYPE WERKS_D, "   
lv_insert_step2_error  TYPE WERKS_D, "   
lv_lock_error  TYPE WERKS_D, "   
lv_if_flg_info_dest  TYPE PPC_FLG_INFO_DEST, "   
lv_if_conflogsys  TYPE PPC_CONFLOGSYS, "   
lv_if_log_handle  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'PPC1PR_MAT_TRANSFER_EXE'  "DE-EN-LANG-SWITCH-NO-TRANSLATION
    EXPORTING
         IT_COMP = lv_it_comp
         IT_HEADID = lv_it_headid
         IF_POSTDATE = lv_if_postdate
         IF_PLANT = lv_if_plant
         IF_FLG_INFO_DEST = lv_if_flg_info_dest
         IF_CONFLOGSYS = lv_if_conflogsys
         IF_LOG_HANDLE = lv_if_log_handle
    IMPORTING
         EF_MAT_LINES_TR_OK = lv_ef_mat_lines_tr_ok
         EF_MAT_LINES_TR_FAIL = lv_ef_mat_lines_tr_fail
    EXCEPTIONS
        HEAD_ERROR = 1
        WIP_ERROR = 2
        PROTOCOL_ERROR = 3
        INSERT_STEP2_ERROR = 4
        LOCK_ERROR = 5
. " PPC1PR_MAT_TRANSFER_EXE




ABAP code using 7.40 inline data declarations to call FM PPC1PR_MAT_TRANSFER_EXE

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!