BARC_ADD_TIME_OBJECT SAP Function module - Create a time object

BARC_ADD_TIME_OBJECT 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 BARC_ADD_TIME_OBJECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BARC
Released Date: 16.04.1997
Processing type: Normal fucntion module

Pattern for FM BARC_ADD_TIME_OBJECT - BARC ADD TIME OBJECT

CALL FUNCTION 'BARC_ADD_TIME_OBJECT' "Create a time object
* EXPORTING
*   timeobject_type = 'U'       " bctimeobj-type  Time object type
*   fl = SPACE                  " bctimeobj-fl  Attribute type
*   d_val = SPACE               " sy-uzeit      Time
*   r_val = SPACE               " bctimeobj-r_val  Attribute value
*   u_val = SPACE               " bctimeobj-u_val  Attribute value
*   winid = SPACE               " net_graph-winid  Window ID
  IMPORTING
    id =                        " bctimeobj-id  Identification
  EXCEPTIONS
    INV_WINID = 1               "               Incorrect window ID
    INV_VAL = 2                 "               Missing entry for R_VAL or U_VAL
    INV_TYPE = 3                "               Incorrect time object type
    .  "  BARC_ADD_TIME_OBJECT

ABAP code example for Function Module BARC_ADD_TIME_OBJECT

The ABAP code below is a full code listing to execute function module BARC_ADD_TIME_OBJECT 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_id  
 
 TYPE BCTIMEOBJ-ID
.



DATA(ld_timeobject_type) = some text here


DATA(ld_fl) = some text here

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


DATA(ld_r_val) = some text here


DATA(ld_u_val) = some text here


DATA(ld_winid) = some text here
.

CALL FUNCTION 'BARC_ADD_TIME_OBJECT'
* EXPORTING
*   timeobject_type =            ld_timeobject_type
*   fl =                         ld_fl
*   d_val =                      ld_d_val
*   r_val =                      ld_r_val
*   u_val =                      ld_u_val
*   winid =                      ld_winid
  IMPORTING
    id =                         ld_id
  EXCEPTIONS
    INV_WINID =                  1
    INV_VAL =                    2
    INV_TYPE =                   3
    .  "  BARC_ADD_TIME_OBJECT

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
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_id
 
 TYPE BCTIMEOBJ-ID ,
ld_timeobject_type
 
 TYPE BCTIMEOBJ-TYPE ,
ld_fl
 
 TYPE BCTIMEOBJ-FL ,
ld_d_val
 
 TYPE SY-UZEIT ,
ld_r_val
 
 TYPE BCTIMEOBJ-R_VAL ,
ld_u_val
 
 TYPE BCTIMEOBJ-U_VAL ,
ld_winid
 
 TYPE NET_GRAPH-WINID .



ld_timeobject_type = some text here

ld_fl = some text here
ld_d_val = 'Check type of data required'.

ld_r_val = some text here

ld_u_val = some text here

ld_winid = some text here