SAP FACILITY_CAT_GET Function Module for Determine Facility Category for Product Type
FACILITY_CAT_GET is a standard facility cat 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 Determine Facility Category for Product Type 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 facility cat get FM, simply by entering the name FACILITY_CAT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: TB17
Program Name: SAPLTB17
Main Program: SAPLTB17
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FACILITY_CAT_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 'FACILITY_CAT_GET'"Determine Facility Category for Product Type.
EXPORTING
IM_PRODUCT_TYPE = "Product Type
IMPORTING
EX_FACILITY_CAT = "Facility Category
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FACILITY_CAT_GET
IM_PRODUCT_TYPE - Product Type
Data type: VVSARTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FACILITY_CAT_GET
EX_FACILITY_CAT - Facility Category
Data type: TB_FACILITY_CATOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED - Error Occurred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FACILITY_CAT_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_failed | TYPE STRING, " | |||
| lv_ex_facility_cat | TYPE TB_FACILITY_CAT, " | |||
| lv_im_product_type | TYPE VVSART. " |
|   CALL FUNCTION 'FACILITY_CAT_GET' "Determine Facility Category for Product Type |
| EXPORTING | ||
| IM_PRODUCT_TYPE | = lv_im_product_type | |
| IMPORTING | ||
| EX_FACILITY_CAT | = lv_ex_facility_cat | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FACILITY_CAT_GET | ||
ABAP code using 7.40 inline data declarations to call FM FACILITY_CAT_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.Search for further information about these or an SAP related objects