SAP GET_PRICE_TIME_DATA_IN Function Module for module to fetch CI data
GET_PRICE_TIME_DATA_IN is a standard get price time data in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for module to fetch CI data 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 get price time data in FM, simply by entering the name GET_PRICE_TIME_DATA_IN into the relevant SAP transaction such as SE37 or SE38.
Function Group: OI0_CICRT
Program Name: SAPLOI0_CICRT
Main Program: SAPLOI0_CICRT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_PRICE_TIME_DATA_IN 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 'GET_PRICE_TIME_DATA_IN'"module to fetch CI data.
EXPORTING
IT_OIL_CI_FIELDS = "Time for time-pricing
* IT_OIL_CI_FIELDS_X = "Single-Character Flag
IMPORTING Parameters details for GET_PRICE_TIME_DATA_IN
IT_OIL_CI_FIELDS - Time for time-pricing
Data type: OIC_TIMEOptional: No
Call by Reference: No ( called with pass by value option)
IT_OIL_CI_FIELDS_X - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_PRICE_TIME_DATA_IN 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_it_oil_ci_fields | TYPE OIC_TIME, " | |||
| lv_it_oil_ci_fields_x | TYPE CHAR1. " |
|   CALL FUNCTION 'GET_PRICE_TIME_DATA_IN' "module to fetch CI data |
| EXPORTING | ||
| IT_OIL_CI_FIELDS | = lv_it_oil_ci_fields | |
| IT_OIL_CI_FIELDS_X | = lv_it_oil_ci_fields_x | |
| . " GET_PRICE_TIME_DATA_IN | ||
ABAP code using 7.40 inline data declarations to call FM GET_PRICE_TIME_DATA_IN
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.Search for further information about these or an SAP related objects