SAP SCHED_CATALOGUE_BUILD Function Module for NOTRANSL: Erweitern des Feldkataloges um terminierungsrelevante Merkmale
SCHED_CATALOGUE_BUILD is a standard sched catalogue build 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: Erweitern des Feldkataloges um terminierungsrelevante Merkmale 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 sched catalogue build FM, simply by entering the name SCHED_CATALOGUE_BUILD into the relevant SAP transaction such as SE37 or SE38.
Function Group: V03C_APOINT
Program Name: SAPLV03C_APOINT
Main Program: SAPLV03C_APOINT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCHED_CATALOGUE_BUILD 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 'SCHED_CATALOGUE_BUILD'"NOTRANSL: Erweitern des Feldkataloges um terminierungsrelevante Merkmale.
EXPORTING
IF_VBELN = "Sales and Distribution Document Number
IF_POSNR = "Item Number of the SD Document
IS_ATTRIBUTES = "Attributes for Shipment Scheduling
* IF_SCHEDULE_SHIPPING = 'X' "Activate delivery scheduling
* IF_SCHEDULE_TRANSPORT = 'X' "Activate transportation scheduling
* IF_ACCEPT_PAST_DATES = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
TABLES
CT_SCHED_FIELDTAB = "DE-EN-LANG-SWITCH-NO-TRANSLATION
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLV03C_APOINT_001 Scheduling: Populate User Exit with Additional R/3 Attributes
IMPORTING Parameters details for SCHED_CATALOGUE_BUILD
IF_VBELN - Sales and Distribution Document Number
Data type: LIKP-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
IF_POSNR - Item Number of the SD Document
Data type: LIPS-POSNROptional: No
Call by Reference: No ( called with pass by value option)
IS_ATTRIBUTES - Attributes for Shipment Scheduling
Data type: SCHEDULE_ATTRIBUTESOptional: No
Call by Reference: No ( called with pass by value option)
IF_SCHEDULE_SHIPPING - Activate delivery scheduling
Data type: TVAK-VSTRMDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IF_SCHEDULE_TRANSPORT - Activate transportation scheduling
Data type: TVAK-TRTRMDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IF_ACCEPT_PAST_DATES - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: TVAK-TENURDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCHED_CATALOGUE_BUILD
CT_SCHED_FIELDTAB - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ATPFIELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCHED_CATALOGUE_BUILD 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_if_vbeln | TYPE LIKP-VBELN, " | |||
| lt_ct_sched_fieldtab | TYPE STANDARD TABLE OF ATPFIELD, " | |||
| lv_if_posnr | TYPE LIPS-POSNR, " | |||
| lv_is_attributes | TYPE SCHEDULE_ATTRIBUTES, " | |||
| lv_if_schedule_shipping | TYPE TVAK-VSTRM, " 'X' | |||
| lv_if_schedule_transport | TYPE TVAK-TRTRM, " 'X' | |||
| lv_if_accept_past_dates | TYPE TVAK-TENUR. " SPACE |
|   CALL FUNCTION 'SCHED_CATALOGUE_BUILD' "NOTRANSL: Erweitern des Feldkataloges um terminierungsrelevante Merkmale |
| EXPORTING | ||
| IF_VBELN | = lv_if_vbeln | |
| IF_POSNR | = lv_if_posnr | |
| IS_ATTRIBUTES | = lv_is_attributes | |
| IF_SCHEDULE_SHIPPING | = lv_if_schedule_shipping | |
| IF_SCHEDULE_TRANSPORT | = lv_if_schedule_transport | |
| IF_ACCEPT_PAST_DATES | = lv_if_accept_past_dates | |
| TABLES | ||
| CT_SCHED_FIELDTAB | = lt_ct_sched_fieldtab | |
| . " SCHED_CATALOGUE_BUILD | ||
ABAP code using 7.40 inline data declarations to call FM SCHED_CATALOGUE_BUILD
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 VBELN FROM LIKP INTO @DATA(ld_if_vbeln). | ||||
| "SELECT single POSNR FROM LIPS INTO @DATA(ld_if_posnr). | ||||
| "SELECT single VSTRM FROM TVAK INTO @DATA(ld_if_schedule_shipping). | ||||
| DATA(ld_if_schedule_shipping) | = 'X'. | |||
| "SELECT single TRTRM FROM TVAK INTO @DATA(ld_if_schedule_transport). | ||||
| DATA(ld_if_schedule_transport) | = 'X'. | |||
| "SELECT single TENUR FROM TVAK INTO @DATA(ld_if_accept_past_dates). | ||||
| DATA(ld_if_accept_past_dates) | = ' '. | |||
Search for further information about these or an SAP related objects