SAP AKB_CHECK_TRANSPORTED_OBJECTS Function Module for









AKB_CHECK_TRANSPORTED_OBJECTS is a standard akb check transported objects SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 akb check transported objects FM, simply by entering the name AKB_CHECK_TRANSPORTED_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: PA_AKB_COMPCHECK
Program Name: SAPLPA_AKB_COMPCHECK
Main Program: SAPLPA_AKB_COMPCHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function AKB_CHECK_TRANSPORTED_OBJECTS 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 'AKB_CHECK_TRANSPORTED_OBJECTS'"
  EXPORTING
   TRKORR =  "Request/Task
*  OBJ_TYPE =  "
*  IN_BATCH = ' ' "Background Processing
*  LOCK_TABLE = ' ' "Lock Management
*  START_DATE =  "Start Date
*  END_DATE =  "End Date
*  FROM_SCRATCH =  "
*  PROJECT = '0' "ID of a Backwards-Compatibility Check
*  RFCDEST =  "Logical Destination (Specified in Function Call)
*  PERFORM_COMP_CHECK = ' ' "
*  ONLY_FROZEN_OBJECTS = 'X' "
*  CHECK_FROM_SCRATCH = ' ' "

EXCEPTIONS
   JOB_NOT_CREATED = 1    PROJECT_LOCKED = 2
.



IMPORTING Parameters details for AKB_CHECK_TRANSPORTED_OBJECTS

TRKORR - Request/Task

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

OBJ_TYPE -

Data type: TROBJTYPE
Optional: Yes
Call by Reference: Yes

IN_BATCH - Background Processing

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

LOCK_TABLE - Lock Management

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

START_DATE - Start Date

Data type: AS4DATE
Optional: Yes
Call by Reference: Yes

END_DATE - End Date

Data type: AS4DATE
Optional: Yes
Call by Reference: Yes

FROM_SCRATCH -

Data type: FLAG
Optional: Yes
Call by Reference: Yes

PROJECT - ID of a Backwards-Compatibility Check

Data type: AKB_PROJECT_ID
Default: '0'
Optional: Yes
Call by Reference: Yes

RFCDEST - Logical Destination (Specified in Function Call)

Data type: RFCDEST
Optional: Yes
Call by Reference: Yes

PERFORM_COMP_CHECK -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

ONLY_FROZEN_OBJECTS -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHECK_FROM_SCRATCH -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

JOB_NOT_CREATED -

Data type:
Optional: No
Call by Reference: Yes

PROJECT_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AKB_CHECK_TRANSPORTED_OBJECTS 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_trkorr  TYPE TRKORR, "   
lv_job_not_created  TYPE TRKORR, "   
lv_obj_type  TYPE TROBJTYPE, "   
lv_in_batch  TYPE FLAG, "   ' '
lv_lock_table  TYPE FLAG, "   ' '
lv_start_date  TYPE AS4DATE, "   
lv_project_locked  TYPE AS4DATE, "   
lv_end_date  TYPE AS4DATE, "   
lv_from_scratch  TYPE FLAG, "   
lv_project  TYPE AKB_PROJECT_ID, "   '0'
lv_rfcdest  TYPE RFCDEST, "   
lv_perform_comp_check  TYPE FLAG, "   ' '
lv_only_frozen_objects  TYPE FLAG, "   'X'
lv_check_from_scratch  TYPE FLAG. "   ' '

  CALL FUNCTION 'AKB_CHECK_TRANSPORTED_OBJECTS'  "
    EXPORTING
         TRKORR = lv_trkorr
         OBJ_TYPE = lv_obj_type
         IN_BATCH = lv_in_batch
         LOCK_TABLE = lv_lock_table
         START_DATE = lv_start_date
         END_DATE = lv_end_date
         FROM_SCRATCH = lv_from_scratch
         PROJECT = lv_project
         RFCDEST = lv_rfcdest
         PERFORM_COMP_CHECK = lv_perform_comp_check
         ONLY_FROZEN_OBJECTS = lv_only_frozen_objects
         CHECK_FROM_SCRATCH = lv_check_from_scratch
    EXCEPTIONS
        JOB_NOT_CREATED = 1
        PROJECT_LOCKED = 2
. " AKB_CHECK_TRANSPORTED_OBJECTS




ABAP code using 7.40 inline data declarations to call FM AKB_CHECK_TRANSPORTED_OBJECTS

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.

 
 
 
DATA(ld_in_batch) = ' '.
 
DATA(ld_lock_table) = ' '.
 
 
 
 
 
DATA(ld_project) = '0'.
 
 
DATA(ld_perform_comp_check) = ' '.
 
DATA(ld_only_frozen_objects) = 'X'.
 
DATA(ld_check_from_scratch) = ' '.
 


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!