SAP PRC_CUST_PURPOSE_SEL Function Module for









PRC_CUST_PURPOSE_SEL is a standard prc cust purpose sel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 prc cust purpose sel FM, simply by entering the name PRC_CUST_PURPOSE_SEL into the relevant SAP transaction such as SE37 or SE38.

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



Function PRC_CUST_PURPOSE_SEL 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 'PRC_CUST_PURPOSE_SEL'"
EXPORTING
IV_APPLICATION = "Application
* IV_PURPOSE = "Condition Function
* IV_LANGUAGE = "Language Key

IMPORTING
ET_PURPOSES = "Table for Target Fields for Condition Purposes
ET_PURPOSE_TEXTS = "Table: Texts for Condition Purposes

EXCEPTIONS
PURPOSE_NOT_FOUND = 1 PURPOSE_TEXT_NOT_FOUND = 2
.



IMPORTING Parameters details for PRC_CUST_PURPOSE_SEL

IV_APPLICATION - Application

Data type: PRCT_APPLICATION
Optional: No
Call by Reference: Yes

IV_PURPOSE - Condition Function

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

IV_LANGUAGE - Language Key

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

EXPORTING Parameters details for PRC_CUST_PURPOSE_SEL

ET_PURPOSES - Table for Target Fields for Condition Purposes

Data type: PRCT_COND_DEST_DU_TAB
Optional: No
Call by Reference: Yes

ET_PURPOSE_TEXTS - Table: Texts for Condition Purposes

Data type: PRCT_COND_DEST_T_DU_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PURPOSE_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

PURPOSE_TEXT_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PRC_CUST_PURPOSE_SEL 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_et_purposes  TYPE PRCT_COND_DEST_DU_TAB, "   
lv_iv_application  TYPE PRCT_APPLICATION, "   
lv_purpose_not_found  TYPE PRCT_APPLICATION, "   
lv_iv_purpose  TYPE PRCT_COND_PURPOSE, "   
lv_et_purpose_texts  TYPE PRCT_COND_DEST_T_DU_TAB, "   
lv_purpose_text_not_found  TYPE PRCT_COND_DEST_T_DU_TAB, "   
lv_iv_language  TYPE SYLANGU. "   

  CALL FUNCTION 'PRC_CUST_PURPOSE_SEL'  "
    EXPORTING
         IV_APPLICATION = lv_iv_application
         IV_PURPOSE = lv_iv_purpose
         IV_LANGUAGE = lv_iv_language
    IMPORTING
         ET_PURPOSES = lv_et_purposes
         ET_PURPOSE_TEXTS = lv_et_purpose_texts
    EXCEPTIONS
        PURPOSE_NOT_FOUND = 1
        PURPOSE_TEXT_NOT_FOUND = 2
. " PRC_CUST_PURPOSE_SEL




ABAP code using 7.40 inline data declarations to call FM PRC_CUST_PURPOSE_SEL

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



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!