SAP /CCEE/BAPI_FISC_SEND_BS Function Module for Fiscalization Croatia: Send Business Space Data









/CCEE/BAPI_FISC_SEND_BS is a standard /ccee/bapi fisc send bs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fiscalization Croatia: Send Business Space Data 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 /ccee/bapi fisc send bs FM, simply by entering the name /CCEE/BAPI_FISC_SEND_BS into the relevant SAP transaction such as SE37 or SE38.

Function Group: /CCEE/FISC_SD
Program Name: /CCEE/SAPLFISC_SD
Main Program: /CCEE/SAPLFISC_SD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function /CCEE/BAPI_FISC_SEND_BS 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 '/CCEE/BAPI_FISC_SEND_BS'"Fiscalization Croatia: Send Business Space Data
  EXPORTING
   I_BUS_' ' =  "Fiscalization Croatia: Business Space Master Data
   I_COMP_OIB =  "OIB of the Company
   I_UUID =  "UUID in character form
   I_KEY_VIEW =  "Certificate Key Store View
   I_KEY_ENTRY =  "Certificate Key Store Entry

 IMPORTING
   E_PROCDAT =  "Processing date
   E_PROCTIM =  "Processing time
   E_ERROR =  "Error Code
   E_ERRORTEXT =  "Error text
   E_XMLREQUEST =  "XML request message
   E_XMLRESPONSE =  "XML response message

TABLES
   RETURN =  "Return Parameter

EXCEPTIONS
   SYSTEM_FAILURE = 1    COMMUNICATION_FAILURE = 2
.



IMPORTING Parameters details for /CCEE/BAPI_FISC_SEND_BS

I_BUS_SPACE - Fiscalization Croatia: Business Space Master Data

Data type: /CCEE/FISC_BS
Optional: No
Call by Reference: No ( called with pass by value option)

I_COMP_OIB - OIB of the Company

Data type: /CCEE/FISC_COMPANY_OIB
Optional: No
Call by Reference: No ( called with pass by value option)

I_UUID - UUID in character form

Data type: /CCEE/FISC_UUID
Optional: No
Call by Reference: No ( called with pass by value option)

I_KEY_VIEW - Certificate Key Store View

Data type: CHAR20
Optional: No
Call by Reference: No ( called with pass by value option)

I_KEY_ENTRY - Certificate Key Store Entry

Data type: CHAR20
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for /CCEE/BAPI_FISC_SEND_BS

E_PROCDAT - Processing date

Data type: DATS
Optional: No
Call by Reference: No ( called with pass by value option)

E_PROCTIM - Processing time

Data type: TIMS
Optional: No
Call by Reference: No ( called with pass by value option)

E_ERROR - Error Code

Data type: /CCEE/FISC_ERR_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

E_ERRORTEXT - Error text

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

E_XMLREQUEST - XML request message

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

E_XMLRESPONSE - XML response message

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for /CCEE/BAPI_FISC_SEND_BS

RETURN - Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

EXCEPTIONS details

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /CCEE/BAPI_FISC_SEND_BS 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_e_procdat  TYPE DATS, "   
lv_i_bus_space  TYPE /CCEE/FISC_BS, "   
lv_system_failure  TYPE /CCEE/FISC_BS, "   
lv_e_proctim  TYPE TIMS, "   
lv_i_comp_oib  TYPE /CCEE/FISC_COMPANY_OIB, "   
lv_communication_failure  TYPE /CCEE/FISC_COMPANY_OIB, "   
lv_i_uuid  TYPE /CCEE/FISC_UUID, "   
lv_e_error  TYPE /CCEE/FISC_ERR_CODE, "   
lv_i_key_view  TYPE CHAR20, "   
lv_e_errortext  TYPE STRING, "   
lv_i_key_entry  TYPE CHAR20, "   
lv_e_xmlrequest  TYPE STRING, "   
lv_e_xmlresponse  TYPE STRING. "   

  CALL FUNCTION '/CCEE/BAPI_FISC_SEND_BS'  "Fiscalization Croatia: Send Business Space Data
    EXPORTING
         I_BUS_SPACE = lv_i_bus_space
         I_COMP_OIB = lv_i_comp_oib
         I_UUID = lv_i_uuid
         I_KEY_VIEW = lv_i_key_view
         I_KEY_ENTRY = lv_i_key_entry
    IMPORTING
         E_PROCDAT = lv_e_procdat
         E_PROCTIM = lv_e_proctim
         E_ERROR = lv_e_error
         E_ERRORTEXT = lv_e_errortext
         E_XMLREQUEST = lv_e_xmlrequest
         E_XMLRESPONSE = lv_e_xmlresponse
    TABLES
         RETURN = lt_return
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        COMMUNICATION_FAILURE = 2
. " /CCEE/BAPI_FISC_SEND_BS




ABAP code using 7.40 inline data declarations to call FM /CCEE/BAPI_FISC_SEND_BS

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!