SAP PLTC_CREATE_TIME_AXIS Function Module for Generated time axis for Gantt chart from time profile
PLTC_CREATE_TIME_AXIS is a standard pltc create time axis SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generated time axis for Gantt chart from time profile 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 pltc create time axis FM, simply by entering the name PLTC_CREATE_TIME_AXIS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PLTC
Program Name: SAPLPLTC
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLTC_CREATE_TIME_AXIS 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 'PLTC_CREATE_TIME_AXIS'"Generated time axis for Gantt chart from time profile.
EXPORTING
* TIME_AXIS_PROFILE_ID = ' ' "Scale - time axis
* WINID = ' ' "Gantt chart window ID
* TIME_PROFILE_ID = ' ' "Key of a time profile
* TIME_PROFILE = ' ' "Time profile (generated by user)
* GLOBAL_HORIZON_FLAG = ' ' "Create global time horizon
* CAPA_PLAN_FLG = ' ' "
IMPORTING
AV_ID = "Pre-evaluation period ID
PH_ID = "Planning period ID
AN_ID = "Post-evaluation period ID
START_DATE = "
END_DATE = "
EXCEPTIONS
WRONG_PARAMETERS = 1 DATE_CONVERSION_ERROR = 2
IMPORTING Parameters details for PLTC_CREATE_TIME_AXIS
TIME_AXIS_PROFILE_ID - Scale - time axis
Data type: TCY54D-SEC_PROFIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINID - Gantt chart window ID
Data type: NET_GRAPH-WINIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TIME_PROFILE_ID - Key of a time profile
Data type: TCY33-TIPRO_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TIME_PROFILE - Time profile (generated by user)
Data type: CYCRPTIPRODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
GLOBAL_HORIZON_FLAG - Create global time horizon
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CAPA_PLAN_FLG -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PLTC_CREATE_TIME_AXIS
AV_ID - Pre-evaluation period ID
Data type: BCSECTION-IDOptional: No
Call by Reference: No ( called with pass by value option)
PH_ID - Planning period ID
Data type: BCSECTION-IDOptional: No
Call by Reference: No ( called with pass by value option)
AN_ID - Post-evaluation period ID
Data type: BCSECTION-IDOptional: No
Call by Reference: No ( called with pass by value option)
START_DATE -
Data type: CYCRPDATES-LIDAVOptional: No
Call by Reference: No ( called with pass by value option)
END_DATE -
Data type: CYCRPDATES-LIDABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_PARAMETERS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATE_CONVERSION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PLTC_CREATE_TIME_AXIS 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_av_id | TYPE BCSECTION-ID, " | |||
| lv_wrong_parameters | TYPE BCSECTION, " | |||
| lv_time_axis_profile_id | TYPE TCY54D-SEC_PROFID, " SPACE | |||
| lv_ph_id | TYPE BCSECTION-ID, " | |||
| lv_winid | TYPE NET_GRAPH-WINID, " SPACE | |||
| lv_date_conversion_error | TYPE NET_GRAPH, " | |||
| lv_an_id | TYPE BCSECTION-ID, " | |||
| lv_time_profile_id | TYPE TCY33-TIPRO_ID, " SPACE | |||
| lv_start_date | TYPE CYCRPDATES-LIDAV, " | |||
| lv_time_profile | TYPE CYCRPTIPRO, " SPACE | |||
| lv_end_date | TYPE CYCRPDATES-LIDAB, " | |||
| lv_global_horizon_flag | TYPE CYCRPDATES, " SPACE | |||
| lv_capa_plan_flg | TYPE CYCRPDATES. " SPACE |
|   CALL FUNCTION 'PLTC_CREATE_TIME_AXIS' "Generated time axis for Gantt chart from time profile |
| EXPORTING | ||
| TIME_AXIS_PROFILE_ID | = lv_time_axis_profile_id | |
| WINID | = lv_winid | |
| TIME_PROFILE_ID | = lv_time_profile_id | |
| TIME_PROFILE | = lv_time_profile | |
| GLOBAL_HORIZON_FLAG | = lv_global_horizon_flag | |
| CAPA_PLAN_FLG | = lv_capa_plan_flg | |
| IMPORTING | ||
| AV_ID | = lv_av_id | |
| PH_ID | = lv_ph_id | |
| AN_ID | = lv_an_id | |
| START_DATE | = lv_start_date | |
| END_DATE | = lv_end_date | |
| EXCEPTIONS | ||
| WRONG_PARAMETERS = 1 | ||
| DATE_CONVERSION_ERROR = 2 | ||
| . " PLTC_CREATE_TIME_AXIS | ||
ABAP code using 7.40 inline data declarations to call FM PLTC_CREATE_TIME_AXIS
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 ID FROM BCSECTION INTO @DATA(ld_av_id). | ||||
| "SELECT single SEC_PROFID FROM TCY54D INTO @DATA(ld_time_axis_profile_id). | ||||
| DATA(ld_time_axis_profile_id) | = ' '. | |||
| "SELECT single ID FROM BCSECTION INTO @DATA(ld_ph_id). | ||||
| "SELECT single WINID FROM NET_GRAPH INTO @DATA(ld_winid). | ||||
| DATA(ld_winid) | = ' '. | |||
| "SELECT single ID FROM BCSECTION INTO @DATA(ld_an_id). | ||||
| "SELECT single TIPRO_ID FROM TCY33 INTO @DATA(ld_time_profile_id). | ||||
| DATA(ld_time_profile_id) | = ' '. | |||
| "SELECT single LIDAV FROM CYCRPDATES INTO @DATA(ld_start_date). | ||||
| DATA(ld_time_profile) | = ' '. | |||
| "SELECT single LIDAB FROM CYCRPDATES INTO @DATA(ld_end_date). | ||||
| DATA(ld_global_horizon_flag) | = ' '. | |||
| DATA(ld_capa_plan_flg) | = ' '. | |||
Search for further information about these or an SAP related objects