SAP BC_PR_UPDATE Function Module for y
BC_PR_UPDATE is a standard bc pr update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for y 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 bc pr update FM, simply by entering the name BC_PR_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPYP
Program Name: SAPLTPYP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BC_PR_UPDATE 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 'BC_PR_UPDATE'"y.
EXPORTING
PROGRAM_NAME = "
TABLES
SOURCE = "
EXCEPTIONS
NOT_EXISTS = 1 CANCELLED = 2 NAME_NOT_ALLOWED = 3 PERMISSION_ERROR = 4 OBJECT_IS_INACTIVE = 5 WRONG_USER = 6
IMPORTING Parameters details for BC_PR_UPDATE
PROGRAM_NAME -
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BC_PR_UPDATE
SOURCE -
Data type: ABAPSOURCEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAME_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PERMISSION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_IS_INACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_USER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BC_PR_UPDATE 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: | ||||
| lt_source | TYPE STANDARD TABLE OF ABAPSOURCE, " | |||
| lv_not_exists | TYPE ABAPSOURCE, " | |||
| lv_program_name | TYPE SY-REPID, " | |||
| lv_cancelled | TYPE SY, " | |||
| lv_name_not_allowed | TYPE SY, " | |||
| lv_permission_error | TYPE SY, " | |||
| lv_object_is_inactive | TYPE SY, " | |||
| lv_wrong_user | TYPE SY. " |
|   CALL FUNCTION 'BC_PR_UPDATE' "y |
| EXPORTING | ||
| PROGRAM_NAME | = lv_program_name | |
| TABLES | ||
| SOURCE | = lt_source | |
| EXCEPTIONS | ||
| NOT_EXISTS = 1 | ||
| CANCELLED = 2 | ||
| NAME_NOT_ALLOWED = 3 | ||
| PERMISSION_ERROR = 4 | ||
| OBJECT_IS_INACTIVE = 5 | ||
| WRONG_USER = 6 | ||
| . " BC_PR_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM BC_PR_UPDATE
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 REPID FROM SY INTO @DATA(ld_program_name). | ||||
Search for further information about these or an SAP related objects