SAP BBP_ICC_SAVE_CUF_BR Function Module for Saves Brazil-specific fields
BBP_ICC_SAVE_CUF_BR is a standard bbp icc save cuf br SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Saves Brazil-specific fields 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 icc save cuf br FM, simply by entering the name BBP_ICC_SAVE_CUF_BR into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_COUNTRY_BR
Program Name: SAPLBBP_COUNTRY_BR
Main Program: SAPLBBP_COUNTRY_BR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_ICC_SAVE_CUF_BR 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_ICC_SAVE_CUF_BR'"Saves Brazil-specific fields.
EXPORTING
IV_FIELD_NAME = "Field Name
IV_VALUE = "
EXCEPTIONS
NOT_SUCH_COMPONENT = 1
IMPORTING Parameters details for BBP_ICC_SAVE_CUF_BR
IV_FIELD_NAME - Field Name
Data type: DD03L-FIELDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_VALUE -
Data type: ANYOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_SUCH_COMPONENT - Field does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_ICC_SAVE_CUF_BR 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_field_name | TYPE DD03L-FIELDNAME, " | |||
| lv_not_such_component | TYPE DD03L, " | |||
| lv_iv_value | TYPE ANY. " |
|   CALL FUNCTION 'BBP_ICC_SAVE_CUF_BR' "Saves Brazil-specific fields |
| EXPORTING | ||
| IV_FIELD_NAME | = lv_iv_field_name | |
| IV_VALUE | = lv_iv_value | |
| EXCEPTIONS | ||
| NOT_SUCH_COMPONENT = 1 | ||
| . " BBP_ICC_SAVE_CUF_BR | ||
ABAP code using 7.40 inline data declarations to call FM BBP_ICC_SAVE_CUF_BR
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 FIELDNAME FROM DD03L INTO @DATA(ld_iv_field_name). | ||||
Search for further information about these or an SAP related objects