SAP BBP_IV_COMPLETING_STATUS_SET Function Module for Zahlungsstatus der Rechnung
BBP_IV_COMPLETING_STATUS_SET is a standard bbp iv completing status set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Zahlungsstatus der Rechnung 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 bbp iv completing status set FM, simply by entering the name BBP_IV_COMPLETING_STATUS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_IV2
Program Name: SAPLBBP_IV2
Main Program: SAPLBBP_IV2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_IV_COMPLETING_STATUS_SET 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 'BBP_IV_COMPLETING_STATUS_SET'"Zahlungsstatus der Rechnung.
EXPORTING
* IV_GUID = "GUID der Rechnung
* IV_OBJECT_ID = "Nummer der Rechnung
* IV_STATUS = C_S_PAID "Einzelstatus
* IV_CHECK_CLEARING = ' ' "
IMPORTING
EV_STATUS_SET = "Importierter Status wurde im Backend gesetzt
EV_REFERENCE_NUMBER = "Nummer des Referenzbelegs
EV_PAYMENT_DATE = "Zahldatum
EXCEPTIONS
NOT_FOUND = 1 FAILED = 2
IMPORTING Parameters details for BBP_IV_COMPLETING_STATUS_SET
IV_GUID - GUID der Rechnung
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_ID - Nummer der Rechnung
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_STATUS - Einzelstatus
Data type: J_ISTATDefault: C_S_PAID
Optional: No
Call by Reference: No ( called with pass by value option)
IV_CHECK_CLEARING -
Data type: BOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_IV_COMPLETING_STATUS_SET
EV_STATUS_SET - Importierter Status wurde im Backend gesetzt
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
EV_REFERENCE_NUMBER - Nummer des Referenzbelegs
Data type: CHAR20Optional: No
Call by Reference: No ( called with pass by value option)
EV_PAYMENT_DATE - Zahldatum
Data type: DATUMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Die Rechnung wurde im Backend nicht gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FAILED - Ein Fehler ist aufgetreten
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_IV_COMPLETING_STATUS_SET 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_iv_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_not_found | TYPE CRMT_OBJECT_GUID, " | |||
| lv_ev_status_set | TYPE XFELD, " | |||
| lv_failed | TYPE XFELD, " | |||
| lv_iv_object_id | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lv_ev_reference_number | TYPE CHAR20, " | |||
| lv_iv_status | TYPE J_ISTAT, " C_S_PAID | |||
| lv_ev_payment_date | TYPE DATUM, " | |||
| lv_iv_check_clearing | TYPE BOOLEAN. " ' ' |
|   CALL FUNCTION 'BBP_IV_COMPLETING_STATUS_SET' "Zahlungsstatus der Rechnung |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_STATUS | = lv_iv_status | |
| IV_CHECK_CLEARING | = lv_iv_check_clearing | |
| IMPORTING | ||
| EV_STATUS_SET | = lv_ev_status_set | |
| EV_REFERENCE_NUMBER | = lv_ev_reference_number | |
| EV_PAYMENT_DATE | = lv_ev_payment_date | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| FAILED = 2 | ||
| . " BBP_IV_COMPLETING_STATUS_SET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_IV_COMPLETING_STATUS_SET
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 OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_id). | ||||
| DATA(ld_iv_status) | = C_S_PAID. | |||
| DATA(ld_iv_check_clearing) | = ' '. | |||
Search for further information about these or an SAP related objects