SAP POSS_INPUTSTRING_GETPAR Function Module for Get field parameters for input string option
POSS_INPUTSTRING_GETPAR is a standard poss inputstring getpar SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get field parameters for input string option 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 poss inputstring getpar FM, simply by entering the name POSS_INPUTSTRING_GETPAR into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPOPOSS
Program Name: SAPLRSPOPOSS
Main Program: SAPLRSPOPOSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function POSS_INPUTSTRING_GETPAR 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 'POSS_INPUTSTRING_GETPAR'"Get field parameters for input string option.
EXPORTING
OPTIONINFO = "Information about printer option
IMPORTING
FIELD_LEN = "Field length in GUI
SHOW_INPUT = "Show input characters?
ALLOWED_CHARS = "Which character groups are allowed?
ALLOW_IN_PRINTTICKET = "Show option in print tickets?
ALLOW_TRUNCATION = "Allow shorter input?
EXCEPTIONS
INVALID_OPTION = 1
IMPORTING Parameters details for POSS_INPUTSTRING_GETPAR
OPTIONINFO - Information about printer option
Data type: POSS_OPTIONINFOOptional: No
Call by Reference: Yes
EXPORTING Parameters details for POSS_INPUTSTRING_GETPAR
FIELD_LEN - Field length in GUI
Data type: NOptional: No
Call by Reference: Yes
SHOW_INPUT - Show input characters?
Data type: COptional: No
Call by Reference: Yes
ALLOWED_CHARS - Which character groups are allowed?
Data type: XOptional: No
Call by Reference: Yes
ALLOW_IN_PRINTTICKET - Show option in print tickets?
Data type: COptional: No
Call by Reference: Yes
ALLOW_TRUNCATION - Allow shorter input?
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_OPTION - illegal option or no INPUTSTRING option
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for POSS_INPUTSTRING_GETPAR 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_field_len | TYPE N, " | |||
| lv_optioninfo | TYPE POSS_OPTIONINFO, " | |||
| lv_invalid_option | TYPE POSS_OPTIONINFO, " | |||
| lv_show_input | TYPE C, " | |||
| lv_allowed_chars | TYPE X, " | |||
| lv_allow_in_printticket | TYPE C, " | |||
| lv_allow_truncation | TYPE C. " |
|   CALL FUNCTION 'POSS_INPUTSTRING_GETPAR' "Get field parameters for input string option |
| EXPORTING | ||
| OPTIONINFO | = lv_optioninfo | |
| IMPORTING | ||
| FIELD_LEN | = lv_field_len | |
| SHOW_INPUT | = lv_show_input | |
| ALLOWED_CHARS | = lv_allowed_chars | |
| ALLOW_IN_PRINTTICKET | = lv_allow_in_printticket | |
| ALLOW_TRUNCATION | = lv_allow_truncation | |
| EXCEPTIONS | ||
| INVALID_OPTION = 1 | ||
| . " POSS_INPUTSTRING_GETPAR | ||
ABAP code using 7.40 inline data declarations to call FM POSS_INPUTSTRING_GETPAR
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