SAP B470_REQUISITION_CHANGE Function Module for
B470_REQUISITION_CHANGE is a standard b470 requisition change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 b470 requisition change FM, simply by entering the name B470_REQUISITION_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_DRIVER_470
Program Name: SAPLBBP_BD_DRIVER_470
Main Program: SAPLBBP_BD_DRIVER_470
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function B470_REQUISITION_CHANGE 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 'B470_REQUISITION_CHANGE'".
EXPORTING
NUMBER = "
TABLES
REQUISITION_ITEMS_OLD = "
REQUISITION_ITEMS_NEW = "
* REQUISITION_ACCOUNT_OLD = "
* REQUISITION_ACCOUNT_NEW = "
* REQUISITION_TEXT_OLD = "
* REQUISITION_TEXT_NEW = "
* RETURN = "
* CONTROL_RECORD = "
IMPORTING Parameters details for B470_REQUISITION_CHANGE
NUMBER -
Data type: BAPIEBAN-PREQ_NOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for B470_REQUISITION_CHANGE
REQUISITION_ITEMS_OLD -
Data type: BBPS_BAPIEBANVOptional: No
Call by Reference: Yes
REQUISITION_ITEMS_NEW -
Data type: BBPS_BAPIEBANVOptional: No
Call by Reference: Yes
REQUISITION_ACCOUNT_OLD -
Data type: BBP_BAPIEBKNVOptional: Yes
Call by Reference: No ( called with pass by value option)
REQUISITION_ACCOUNT_NEW -
Data type: BBP_BAPIEBKNVOptional: Yes
Call by Reference: No ( called with pass by value option)
REQUISITION_TEXT_OLD -
Data type: BBPS_BAPIEBANTXOptional: Yes
Call by Reference: Yes
REQUISITION_TEXT_NEW -
Data type: BBPS_BAPIEBANTXOptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRETURNOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTROL_RECORD -
Data type: BBP_CONTROL_RECORDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for B470_REQUISITION_CHANGE 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_number | TYPE BAPIEBAN-PREQ_NO, " | |||
lt_requisition_items_old | TYPE STANDARD TABLE OF BBPS_BAPIEBANV, " | |||
lt_requisition_items_new | TYPE STANDARD TABLE OF BBPS_BAPIEBANV, " | |||
lt_requisition_account_old | TYPE STANDARD TABLE OF BBP_BAPIEBKNV, " | |||
lt_requisition_account_new | TYPE STANDARD TABLE OF BBP_BAPIEBKNV, " | |||
lt_requisition_text_old | TYPE STANDARD TABLE OF BBPS_BAPIEBANTX, " | |||
lt_requisition_text_new | TYPE STANDARD TABLE OF BBPS_BAPIEBANTX, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRETURN, " | |||
lt_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD. " |
  CALL FUNCTION 'B470_REQUISITION_CHANGE' " |
EXPORTING | ||
NUMBER | = lv_number | |
TABLES | ||
REQUISITION_ITEMS_OLD | = lt_requisition_items_old | |
REQUISITION_ITEMS_NEW | = lt_requisition_items_new | |
REQUISITION_ACCOUNT_OLD | = lt_requisition_account_old | |
REQUISITION_ACCOUNT_NEW | = lt_requisition_account_new | |
REQUISITION_TEXT_OLD | = lt_requisition_text_old | |
REQUISITION_TEXT_NEW | = lt_requisition_text_new | |
RETURN | = lt_return | |
CONTROL_RECORD | = lt_control_record | |
. " B470_REQUISITION_CHANGE |
ABAP code using 7.40 inline data declarations to call FM B470_REQUISITION_CHANGE
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 PREQ_NO FROM BAPIEBAN INTO @DATA(ld_number). | ||||
Search for further information about these or an SAP related objects