SAP ME_ITEM_CATEGORY_INPUT Function Module for NOTRANSL: Konvertierung Positionstyp in internes Format
ME_ITEM_CATEGORY_INPUT is a standard me item category input 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: Konvertierung Positionstyp in internes Format 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 me item category input FM, simply by entering the name ME_ITEM_CATEGORY_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINH
Program Name: SAPLEINH
Main Program: SAPLEINH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_ITEM_CATEGORY_INPUT 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 'ME_ITEM_CATEGORY_INPUT'"NOTRANSL: Konvertierung Positionstyp in internes Format.
EXPORTING
EPSTP = "Item category in external format
IMPORTING
PSTYP = "Item category in internal format
PTEXT = "Text for the external item categor
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ME_ITEM_CATEGORY_INPUT
EPSTP - Item category in external format
Data type: T163Y-EPSTPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_ITEM_CATEGORY_INPUT
PSTYP - Item category in internal format
Data type: T163-PSTYPOptional: No
Call by Reference: No ( called with pass by value option)
PTEXT - Text for the external item categor
Data type: T163Y-PTEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Item category not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_ITEM_CATEGORY_INPUT 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_epstp | TYPE T163Y-EPSTP, " | |||
| lv_pstyp | TYPE T163-PSTYP, " | |||
| lv_not_found | TYPE T163, " | |||
| lv_ptext | TYPE T163Y-PTEXT. " |
|   CALL FUNCTION 'ME_ITEM_CATEGORY_INPUT' "NOTRANSL: Konvertierung Positionstyp in internes Format |
| EXPORTING | ||
| EPSTP | = lv_epstp | |
| IMPORTING | ||
| PSTYP | = lv_pstyp | |
| PTEXT | = lv_ptext | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " ME_ITEM_CATEGORY_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM ME_ITEM_CATEGORY_INPUT
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 EPSTP FROM T163Y INTO @DATA(ld_epstp). | ||||
| "SELECT single PSTYP FROM T163 INTO @DATA(ld_pstyp). | ||||
| "SELECT single PTEXT FROM T163Y INTO @DATA(ld_ptext). | ||||
Search for further information about these or an SAP related objects