SAP ISU_DB_SET_PRINTED_TO_COLLBILL Function Module for Collective Bill: Set Print Indicator
ISU_DB_SET_PRINTED_TO_COLLBILL is a standard isu db set printed to collbill SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Collective Bill: Set Print Indicator 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 isu db set printed to collbill FM, simply by entering the name ISU_DB_SET_PRINTED_TO_COLLBILL into the relevant SAP transaction such as SE37 or SE38.
Function Group: E31D
Program Name: SAPLE31D
Main Program: SAPLE31D
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_SET_PRINTED_TO_COLLBILL 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 'ISU_DB_SET_PRINTED_TO_COLLBILL'"Collective Bill: Set Print Indicator.
EXPORTING
X_OPBEL = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ISU_DB_SET_PRINTED_TO_COLLBILL
X_OPBEL -
Data type: FKKOP-OPBELOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Object does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_SET_PRINTED_TO_COLLBILL 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_x_opbel | TYPE FKKOP-OPBEL, " | |||
| lv_not_found | TYPE FKKOP. " |
|   CALL FUNCTION 'ISU_DB_SET_PRINTED_TO_COLLBILL' "Collective Bill: Set Print Indicator |
| EXPORTING | ||
| X_OPBEL | = lv_x_opbel | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " ISU_DB_SET_PRINTED_TO_COLLBILL | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_SET_PRINTED_TO_COLLBILL
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 OPBEL FROM FKKOP INTO @DATA(ld_x_opbel). | ||||
Search for further information about these or an SAP related objects