BIZC_COMMIT_AND_EXPORT_USAGE SAP Function module

BIZC_COMMIT_AND_EXPORT_USAGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BIZC_COMMIT_AND_EXPORT_USAGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SBIZC_FW_REMOTE
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM BIZC_COMMIT_AND_EXPORT_USAGE - BIZC COMMIT AND EXPORT USAGE

CALL FUNCTION 'BIZC_COMMIT_AND_EXPORT_USAGE' "
  EXPORTING
    ip_usage =                  " bizc_usage
*   ip_calling_application = SPACE  " bizc_client
*   ip_replace_username = 'SAP'  " syuname
  IMPORTING
    ep_data =                   " xstring
    ep_bizc_guid =              " bizc_serv_guid
  EXCEPTIONS
    COMMUNICATION_PROBLEM = 1   "
    UNKNOWN_ERROR = 2           "
    BIZC_FRAMEWORK_ERROR = 3    "
    READ_ERROR = 4              "
    NO_REGISTRATION = 5         "
    NOT_AVAILABLE_FOR_BIZCONTENT = 6  "
    .  "  BIZC_COMMIT_AND_EXPORT_USAGE

ABAP code example for Function Module BIZC_COMMIT_AND_EXPORT_USAGE

The ABAP code below is a full code listing to execute function module BIZC_COMMIT_AND_EXPORT_USAGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ep_data  
 
 TYPE XSTRING
,
ld_ep_bizc_guid  
 
 TYPE BIZC_SERV_GUID
.


DATA(ld_ip_usage) = 'Check type of data required'.

DATA(ld_ip_calling_application) = 'Check type of data required'.

DATA(ld_ip_replace_username) = 'some text here'.
.

CALL FUNCTION 'BIZC_COMMIT_AND_EXPORT_USAGE'
  EXPORTING
    ip_usage =                   ld_ip_usage
*   ip_calling_application =     ld_ip_calling_application
*   ip_replace_username =        ld_ip_replace_username
  IMPORTING
    ep_data =                    ld_ep_data
    ep_bizc_guid =               ld_ep_bizc_guid
  EXCEPTIONS
    COMMUNICATION_PROBLEM =      1
    UNKNOWN_ERROR =              2
    BIZC_FRAMEWORK_ERROR =       3
    READ_ERROR =                 4
    NO_REGISTRATION =            5
    NOT_AVAILABLE_FOR_BIZCONTENT =    6
    .  "  BIZC_COMMIT_AND_EXPORT_USAGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ep_data
 
 TYPE XSTRING ,
ld_ip_usage
 
 TYPE BIZC_USAGE ,
ld_ep_bizc_guid
 
 TYPE BIZC_SERV_GUID ,
ld_ip_calling_application
 
 TYPE BIZC_CLIENT ,
ld_ip_replace_username
 
 TYPE SYUNAME .


ld_ip_usage = 'some text here'.
ld_ip_calling_application = 'some text here'.
ld_ip_replace_username = 'some text here'.