SAP CJDT_ACT_TO_PLAN_TRANSFER Function Module for NOTRANSL: Stellt Eck- in Prognosetermine ein









CJDT_ACT_TO_PLAN_TRANSFER is a standard cjdt act to plan transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Stellt Eck- in Prognosetermine ein 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 cjdt act to plan transfer FM, simply by entering the name CJDT_ACT_TO_PLAN_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

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



Function CJDT_ACT_TO_PLAN_TRANSFER 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 'CJDT_ACT_TO_PLAN_TRANSFER'"NOTRANSL: Stellt Eck- in  Prognosetermine ein
EXPORTING
AUFNR_IMP = "Order Number
PSPNR_IMP = "WBS Element
.



IMPORTING Parameters details for CJDT_ACT_TO_PLAN_TRANSFER

AUFNR_IMP - Order Number

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

PSPNR_IMP - WBS Element

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

Copy and paste ABAP code example for CJDT_ACT_TO_PLAN_TRANSFER 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_aufnr_imp  TYPE AUFK-AUFNR, "   
lv_pspnr_imp  TYPE PRPS-PSPNR. "   

  CALL FUNCTION 'CJDT_ACT_TO_PLAN_TRANSFER'  "NOTRANSL: Stellt Eck- in Prognosetermine ein
    EXPORTING
         AUFNR_IMP = lv_aufnr_imp
         PSPNR_IMP = lv_pspnr_imp
. " CJDT_ACT_TO_PLAN_TRANSFER




ABAP code using 7.40 inline data declarations to call FM CJDT_ACT_TO_PLAN_TRANSFER

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 AUFNR FROM AUFK INTO @DATA(ld_aufnr_imp).
 
"SELECT single PSPNR FROM PRPS INTO @DATA(ld_pspnr_imp).
 


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!