SAP ISM_BUFFER_CALENDARID_GET Function Module for IS-M: Buffer Planning Calendar
ISM_BUFFER_CALENDARID_GET is a standard ism buffer calendarid get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Buffer Planning Calendar 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 ism buffer calendarid get FM, simply by entering the name ISM_BUFFER_CALENDARID_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGSDCAL01
Program Name: SAPLJGSDCAL01
Main Program: SAPLJGSDCAL01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_BUFFER_CALENDARID_GET 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 'ISM_BUFFER_CALENDARID_GET'"IS-M: Buffer Planning Calendar.
EXPORTING
IN_BP = "
IMPORTING
EX_CALENDARID = "Factory Calendar
IMPORTING Parameters details for ISM_BUFFER_CALENDARID_GET
IN_BP -
Data type: KUNNROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_BUFFER_CALENDARID_GET
EX_CALENDARID - Factory Calendar
Data type: SCAL-FCALIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_BUFFER_CALENDARID_GET 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_in_bp | TYPE KUNNR, " | |||
| lv_ex_calendarid | TYPE SCAL-FCALID. " |
|   CALL FUNCTION 'ISM_BUFFER_CALENDARID_GET' "IS-M: Buffer Planning Calendar |
| EXPORTING | ||
| IN_BP | = lv_in_bp | |
| IMPORTING | ||
| EX_CALENDARID | = lv_ex_calendarid | |
| . " ISM_BUFFER_CALENDARID_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_BUFFER_CALENDARID_GET
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 FCALID FROM SCAL INTO @DATA(ld_ex_calendarid). | ||||
Search for further information about these or an SAP related objects