SAP ISSC_FPU5_CHANGE_BDT_OBJECTS Function Module for FPU5 by DI: Change Objects when Transfer Posting









ISSC_FPU5_CHANGE_BDT_OBJECTS is a standard issc fpu5 change bdt objects SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FPU5 by DI: Change Objects when Transfer Posting 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 issc fpu5 change bdt objects FM, simply by entering the name ISSC_FPU5_CHANGE_BDT_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

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



Function ISSC_FPU5_CHANGE_BDT_OBJECTS 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 'ISSC_FPU5_CHANGE_BDT_OBJECTS'"FPU5 by DI: Change Objects when Transfer Posting
EXPORTING
IT_VVSCPOS = "Bill Scheduling: Scheduling Item
IT_VVSCITEM = "Bill Scheduling: Scheduling Document
IT_DIMAPARSCPOS = "
GPART1 = "Business Partner Number
GPART2 = "Business Partner Number
I_VTREF = "Reference Specifications from Contract
.



IMPORTING Parameters details for ISSC_FPU5_CHANGE_BDT_OBJECTS

IT_VVSCPOS - Bill Scheduling: Scheduling Item

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

IT_VVSCITEM - Bill Scheduling: Scheduling Document

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

IT_DIMAPARSCPOS -

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

GPART1 - Business Partner Number

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

GPART2 - Business Partner Number

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

I_VTREF - Reference Specifications from Contract

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

Copy and paste ABAP code example for ISSC_FPU5_CHANGE_BDT_OBJECTS 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_vvscpos  TYPE TAB_VVSCPOS_S1_SC, "   
lv_it_vvscitem  TYPE TAB_VVSCITEM_S1_SC, "   
lv_it_dimaparscpos  TYPE TAB_DIMAPARSCPOS_S1_SC, "   
lv_gpart1  TYPE GPART_KK, "   
lv_gpart2  TYPE GPART_KK, "   
lv_i_vtref  TYPE VTREF_KK. "   

  CALL FUNCTION 'ISSC_FPU5_CHANGE_BDT_OBJECTS'  "FPU5 by DI: Change Objects when Transfer Posting
    EXPORTING
         IT_VVSCPOS = lv_it_vvscpos
         IT_VVSCITEM = lv_it_vvscitem
         IT_DIMAPARSCPOS = lv_it_dimaparscpos
         GPART1 = lv_gpart1
         GPART2 = lv_gpart2
         I_VTREF = lv_i_vtref
. " ISSC_FPU5_CHANGE_BDT_OBJECTS




ABAP code using 7.40 inline data declarations to call FM ISSC_FPU5_CHANGE_BDT_OBJECTS

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!