SAP Function Modules

ALE_CATIMESHEETMGR_DELETE SAP Function module







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

Associated Function Group: BAPICATS
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ALE_CATIMESHEETMGR_DELETE - ALE CATIMESHEETMGR DELETE





CALL FUNCTION 'ALE_CATIMESHEETMGR_DELETE' "
* EXPORTING
*   profile =                   " bapicats6-profile
*   testrun =                   " bapicats6-testrun
*   releasedata =               " bapicats6-release_data
*   agent =                     " swhactor
*   obj_type = 'BUS7024'        " serial-obj_type
*   serial_id = '0'             " serial-chnum
  TABLES
    catsrecords =               " bapicats4
*   workflowtext =              " solisti1
    receivers =                 " bdi_logsys
*   communication_documents =   " swotobjid
*   application_objects =       " swotobjid
  EXCEPTIONS
    ERROR_CREATING_IDOCS = 1    "
    .  "  ALE_CATIMESHEETMGR_DELETE

ABAP code example for Function Module ALE_CATIMESHEETMGR_DELETE





The ABAP code below is a full code listing to execute function module ALE_CATIMESHEETMGR_DELETE 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:
it_catsrecords  TYPE STANDARD TABLE OF BAPICATS4,"TABLES PARAM
wa_catsrecords  LIKE LINE OF it_catsrecords ,
it_workflowtext  TYPE STANDARD TABLE OF SOLISTI1,"TABLES PARAM
wa_workflowtext  LIKE LINE OF it_workflowtext ,
it_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS,"TABLES PARAM
wa_receivers  LIKE LINE OF it_receivers ,
it_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_communication_documents  LIKE LINE OF it_communication_documents ,
it_application_objects  TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_application_objects  LIKE LINE OF it_application_objects .


DATA(ld_profile) = some text here

DATA(ld_testrun) = some text here

DATA(ld_releasedata) = some text here
DATA(ld_agent) = 'Check type of data required'.

DATA(ld_obj_type) = some text here

DATA(ld_serial_id) = Check type of data required

"populate fields of struture and append to itab
append wa_catsrecords to it_catsrecords.

"populate fields of struture and append to itab
append wa_workflowtext to it_workflowtext.

"populate fields of struture and append to itab
append wa_receivers to it_receivers.

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects. . CALL FUNCTION 'ALE_CATIMESHEETMGR_DELETE' * EXPORTING * profile = ld_profile * testrun = ld_testrun * releasedata = ld_releasedata * agent = ld_agent * obj_type = ld_obj_type * serial_id = ld_serial_id TABLES catsrecords = it_catsrecords * workflowtext = it_workflowtext receivers = it_receivers * communication_documents = it_communication_documents * application_objects = it_application_objects EXCEPTIONS ERROR_CREATING_IDOCS = 1 . " ALE_CATIMESHEETMGR_DELETE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_profile  TYPE BAPICATS6-PROFILE ,
it_catsrecords  TYPE STANDARD TABLE OF BAPICATS4 ,
wa_catsrecords  LIKE LINE OF it_catsrecords,
ld_testrun  TYPE BAPICATS6-TESTRUN ,
it_workflowtext  TYPE STANDARD TABLE OF SOLISTI1 ,
wa_workflowtext  LIKE LINE OF it_workflowtext,
ld_releasedata  TYPE BAPICATS6-RELEASE_DATA ,
it_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS ,
wa_receivers  LIKE LINE OF it_receivers,
ld_agent  TYPE SWHACTOR ,
it_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_communication_documents  LIKE LINE OF it_communication_documents,
ld_obj_type  TYPE SERIAL-OBJ_TYPE ,
it_application_objects  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_application_objects  LIKE LINE OF it_application_objects,
ld_serial_id  TYPE SERIAL-CHNUM .


ld_profile = some text here

"populate fields of struture and append to itab
append wa_catsrecords to it_catsrecords.

ld_testrun = some text here

"populate fields of struture and append to itab
append wa_workflowtext to it_workflowtext.

ld_releasedata = some text here

"populate fields of struture and append to itab
append wa_receivers to it_receivers.
ld_agent = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.

ld_obj_type = some text here

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.

ld_serial_id = Check type of data required

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ALE_CATIMESHEETMGR_DELETE or its description.