SAP PPTST_PATST_GET Function Module for Read Alternatives
PPTST_PATST_GET is a standard pptst patst 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 Read Alternatives 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 pptst patst get FM, simply by entering the name PPTST_PATST_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: PPTST
Program Name: SAPLPPTST
Main Program: SAPLPPTST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPTST_PATST_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 'PPTST_PATST_GET'"Read Alternatives.
EXPORTING
IM_PALTID_TAB = "
IMPORTING
EX_PATST_TAB = "
EX_AENNR_TAB = "
IMPORTING Parameters details for PPTST_PATST_GET
IM_PALTID_TAB -
Data type: PPET_PALTID_LI_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PPTST_PATST_GET
EX_PATST_TAB -
Data type: PPTST_PATST_LI_TABOptional: No
Call by Reference: Yes
EX_AENNR_TAB -
Data type: PPET_AENNR_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPTST_PATST_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_ex_patst_tab | TYPE PPTST_PATST_LI_TAB, " | |||
| lv_im_paltid_tab | TYPE PPET_PALTID_LI_TAB, " | |||
| lv_ex_aennr_tab | TYPE PPET_AENNR_TAB. " |
|   CALL FUNCTION 'PPTST_PATST_GET' "Read Alternatives |
| EXPORTING | ||
| IM_PALTID_TAB | = lv_im_paltid_tab | |
| IMPORTING | ||
| EX_PATST_TAB | = lv_ex_patst_tab | |
| EX_AENNR_TAB | = lv_ex_aennr_tab | |
| . " PPTST_PATST_GET | ||
ABAP code using 7.40 inline data declarations to call FM PPTST_PATST_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