SAP PPESTATUSCUST_PSTYPE_FIND Function Module for NOTRANSL: Suchen des 'obersten' Statusobjektes









PPESTATUSCUST_PSTYPE_FIND is a standard ppestatuscust pstype find 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: Suchen des 'obersten' Statusobjektes 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 ppestatuscust pstype find FM, simply by entering the name PPESTATUSCUST_PSTYPE_FIND into the relevant SAP transaction such as SE37 or SE38.

Function Group: PPESTATUSCUST
Program Name: SAPLPPESTATUSCUST
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PPESTATUSCUST_PSTYPE_FIND 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 'PPESTATUSCUST_PSTYPE_FIND'"NOTRANSL: Suchen des 'obersten' Statusobjektes
EXPORTING
IM_OTYPE = "Object Type of Status (Node, Variant, Alternative, ...)
IM_PXTYPE = "Object Customizing Type

IMPORTING
EX_CSID = "Status Type

TABLES
* TAB_CPSGRAPH = "Status Graph

EXCEPTIONS
ILLEGAL_OTYPE = 1 ILLEGAL_PXTYPE = 2 NOT_FOUND = 3 NOT_UNIQUE = 4
.



IMPORTING Parameters details for PPESTATUSCUST_PSTYPE_FIND

IM_OTYPE - Object Type of Status (Node, Variant, Alternative, ...)

Data type: PPEST_CPSASSIGN-OTYPE
Optional: No
Call by Reference: Yes

IM_PXTYPE - Object Customizing Type

Data type: PPEST_CPSASSIGN-PXTYPE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for PPESTATUSCUST_PSTYPE_FIND

EX_CSID - Status Type

Data type: PPEST_PPESSTATUS-CSID
Optional: No
Call by Reference: Yes

TABLES Parameters details for PPESTATUSCUST_PSTYPE_FIND

TAB_CPSGRAPH - Status Graph

Data type: PPEST_CPSREL_TAB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ILLEGAL_OTYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_PXTYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND - No Status Found

Data type:
Optional: No
Call by Reference: Yes

NOT_UNIQUE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPESTATUSCUST_PSTYPE_FIND 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_csid  TYPE PPEST_PPESSTATUS-CSID, "   
lv_im_otype  TYPE PPEST_CPSASSIGN-OTYPE, "   
lt_tab_cpsgraph  TYPE STANDARD TABLE OF PPEST_CPSREL_TAB, "   
lv_illegal_otype  TYPE PPEST_CPSREL_TAB, "   
lv_im_pxtype  TYPE PPEST_CPSASSIGN-PXTYPE, "   
lv_illegal_pxtype  TYPE PPEST_CPSASSIGN, "   
lv_not_found  TYPE PPEST_CPSASSIGN, "   
lv_not_unique  TYPE PPEST_CPSASSIGN. "   

  CALL FUNCTION 'PPESTATUSCUST_PSTYPE_FIND'  "NOTRANSL: Suchen des 'obersten' Statusobjektes
    EXPORTING
         IM_OTYPE = lv_im_otype
         IM_PXTYPE = lv_im_pxtype
    IMPORTING
         EX_CSID = lv_ex_csid
    TABLES
         TAB_CPSGRAPH = lt_tab_cpsgraph
    EXCEPTIONS
        ILLEGAL_OTYPE = 1
        ILLEGAL_PXTYPE = 2
        NOT_FOUND = 3
        NOT_UNIQUE = 4
. " PPESTATUSCUST_PSTYPE_FIND




ABAP code using 7.40 inline data declarations to call FM PPESTATUSCUST_PSTYPE_FIND

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 CSID FROM PPEST_PPESSTATUS INTO @DATA(ld_ex_csid).
 
"SELECT single OTYPE FROM PPEST_CPSASSIGN INTO @DATA(ld_im_otype).
 
 
 
"SELECT single PXTYPE FROM PPEST_CPSASSIGN INTO @DATA(ld_im_pxtype).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!