SAP FKJO_CNTR_JOB_PLANEN Function Module for









FKJO_CNTR_JOB_PLANEN is a standard fkjo cntr job planen 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 fkjo cntr job planen FM, simply by entering the name FKJO_CNTR_JOB_PLANEN into the relevant SAP transaction such as SE37 or SE38.

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



Function FKJO_CNTR_JOB_PLANEN 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 'FKJO_CNTR_JOB_PLANEN'"
  EXPORTING
*  I_AKTYP =  "
   I_JTYPE =  "
*  I_START_DATE = SY-DATUM "
   I_START_TIME =  "
   I_LAUFD =  "
   I_LAUFI =  "
*  I_COPYD =  "
*  I_COPYI =  "
*  I_JOBNAME =  "

EXCEPTIONS
   UNSPEC_ERR = 1    OPEN_ERR = 2    SUBMIT_ERR = 3    CLOSE_ERR = 4
.



IMPORTING Parameters details for FKJO_CNTR_JOB_PLANEN

I_AKTYP -

Data type: DFK_JC_CNTR_PROD-AKTYP
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_JTYPE -

Data type: TFKDO_TYP-JTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_START_DATE -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_START_TIME -

Data type: SY-UZEIT
Optional: No
Call by Reference: No ( called with pass by value option)

I_LAUFD -

Data type: DFK_JC_CNTR_PROD-LAUFD
Optional: No
Call by Reference: No ( called with pass by value option)

I_LAUFI -

Data type: DFK_JC_CNTR_PROD-LAUFI
Optional: No
Call by Reference: No ( called with pass by value option)

I_COPYD -

Data type: DFK_JC_CNTR_PROD-LAUFD
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_COPYI -

Data type: DFK_JC_CNTR_PROD-LAUFI
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_JOBNAME -

Data type: DFK_JC_CNTR_PROD-JOBNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

UNSPEC_ERR -

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

OPEN_ERR -

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

SUBMIT_ERR -

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

CLOSE_ERR -

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

Copy and paste ABAP code example for FKJO_CNTR_JOB_PLANEN 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_i_aktyp  TYPE DFK_JC_CNTR_PROD-AKTYP, "   
lv_unspec_err  TYPE DFK_JC_CNTR_PROD, "   
lv_i_jtype  TYPE TFKDO_TYP-JTYPE, "   
lv_open_err  TYPE TFKDO_TYP, "   
lv_submit_err  TYPE TFKDO_TYP, "   
lv_i_start_date  TYPE SY-DATUM, "   SY-DATUM
lv_close_err  TYPE SY, "   
lv_i_start_time  TYPE SY-UZEIT, "   
lv_i_laufd  TYPE DFK_JC_CNTR_PROD-LAUFD, "   
lv_i_laufi  TYPE DFK_JC_CNTR_PROD-LAUFI, "   
lv_i_copyd  TYPE DFK_JC_CNTR_PROD-LAUFD, "   
lv_i_copyi  TYPE DFK_JC_CNTR_PROD-LAUFI, "   
lv_i_jobname  TYPE DFK_JC_CNTR_PROD-JOBNAME. "   

  CALL FUNCTION 'FKJO_CNTR_JOB_PLANEN'  "
    EXPORTING
         I_AKTYP = lv_i_aktyp
         I_JTYPE = lv_i_jtype
         I_START_DATE = lv_i_start_date
         I_START_TIME = lv_i_start_time
         I_LAUFD = lv_i_laufd
         I_LAUFI = lv_i_laufi
         I_COPYD = lv_i_copyd
         I_COPYI = lv_i_copyi
         I_JOBNAME = lv_i_jobname
    EXCEPTIONS
        UNSPEC_ERR = 1
        OPEN_ERR = 2
        SUBMIT_ERR = 3
        CLOSE_ERR = 4
. " FKJO_CNTR_JOB_PLANEN




ABAP code using 7.40 inline data declarations to call FM FKJO_CNTR_JOB_PLANEN

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.

"SELECT single AKTYP FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_aktyp).
 
 
"SELECT single JTYPE FROM TFKDO_TYP INTO @DATA(ld_i_jtype).
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_start_date).
DATA(ld_i_start_date) = SY-DATUM.
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_i_start_time).
 
"SELECT single LAUFD FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_laufd).
 
"SELECT single LAUFI FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_laufi).
 
"SELECT single LAUFD FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_copyd).
 
"SELECT single LAUFI FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_copyi).
 
"SELECT single JOBNAME FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_jobname).
 


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!