SAP CI_VB_PLWP_POST Function Module for Update function for maint. package allocations from PLWP doc. table









CI_VB_PLWP_POST is a standard ci vb plwp post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update function for maint. package allocations from PLWP doc. table 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 ci vb plwp post FM, simply by entering the name CI_VB_PLWP_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: CIVB
Program Name: SAPLCIVB
Main Program:
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 3



Function CI_VB_PLWP_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 'CI_VB_PLWP_POST'"Update function for maint. package allocations from PLWP doc. table
EXPORTING
* AEB_KZ = 'X' "Indicator: write change documents
COUNT_MAX = "highest counter of changes of PLPO

TABLES
PLANWP = "Document table maintenance package allocation
PLWP_OLD = "old status of changed PLWP records
.



IMPORTING Parameters details for CI_VB_PLWP_POST

AEB_KZ - Indicator: write change documents

Data type: RIEBT-FLG_VB_WP
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

COUNT_MAX - highest counter of changes of PLPO

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

TABLES Parameters details for CI_VB_PLWP_POST

PLANWP - Document table maintenance package allocation

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

PLWP_OLD - old status of changed PLWP records

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

Copy and paste ABAP code example for CI_VB_PLWP_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_aeb_kz  TYPE RIEBT-FLG_VB_WP, "   'X'
lt_planwp  TYPE STANDARD TABLE OF PLWPB, "   
lt_plwp_old  TYPE STANDARD TABLE OF PPLWP, "   
lv_count_max  TYPE PLWP-ZAEHL. "   

  CALL FUNCTION 'CI_VB_PLWP_POST'  "Update function for maint. package allocations from PLWP doc. table
    EXPORTING
         AEB_KZ = lv_aeb_kz
         COUNT_MAX = lv_count_max
    TABLES
         PLANWP = lt_planwp
         PLWP_OLD = lt_plwp_old
. " CI_VB_PLWP_POST




ABAP code using 7.40 inline data declarations to call FM CI_VB_PLWP_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 FLG_VB_WP FROM RIEBT INTO @DATA(ld_aeb_kz).
DATA(ld_aeb_kz) = 'X'.
 
 
 
"SELECT single ZAEHL FROM PLWP INTO @DATA(ld_count_max).
 


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!