SAP RH_PM_AUSART_FOR_OBJECT_GET Function Module for
RH_PM_AUSART_FOR_OBJECT_GET is a standard rh pm ausart for object get 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 rh pm ausart for object get FM, simply by entering the name RH_PM_AUSART_FOR_OBJECT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHB7_5
Program Name: SAPLRHB7_5
Main Program:
Appliation area:
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_PM_AUSART_FOR_OBJECT_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 'RH_PM_AUSART_FOR_OBJECT_GET'".
EXPORTING
PLVAR = "
* PAY_MODE = ' ' "
OTYPE = "
OBJID = "
BEGDA = "
ENDDA = "
ISTAT = "
* ONLY_NOT_INTEGRATED = ' ' "
* ONLY_INTEGRATED = ' ' "
* NO_MESSAGE = "
TABLES
AUSART_TAB = "
EXCEPTIONS
NOTHING_REQUIRED = 1 AUSART_ERROR = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLRHB7_5_001 Customer Enhancement Financing Assistant
IMPORTING Parameters details for RH_PM_AUSART_FOR_OBJECT_GET
PLVAR -
Data type: P1000-PLVAROptional: No
Call by Reference: Yes
PAY_MODE -
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
OTYPE -
Data type: P1000-OTYPEOptional: No
Call by Reference: Yes
OBJID -
Data type: P1000-OBJIDOptional: No
Call by Reference: Yes
BEGDA -
Data type: P1000-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
ENDDA -
Data type: P1000-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
ISTAT -
Data type: P1000-ISTATOptional: No
Call by Reference: Yes
ONLY_NOT_INTEGRATED -
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
ONLY_INTEGRATED -
Data type: FLAGDefault: SPACE
Optional: No
Call by Reference: Yes
NO_MESSAGE -
Data type: FLAGOptional: Yes
Call by Reference: Yes
TABLES Parameters details for RH_PM_AUSART_FOR_OBJECT_GET
AUSART_TAB -
Data type: PMAUSARTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_REQUIRED -
Data type:Optional: No
Call by Reference: Yes
AUSART_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RH_PM_AUSART_FOR_OBJECT_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_plvar | TYPE P1000-PLVAR, " | |||
| lt_ausart_tab | TYPE STANDARD TABLE OF PMAUSART, " | |||
| lv_nothing_required | TYPE PMAUSART, " | |||
| lv_pay_mode | TYPE FLAG, " SPACE | |||
| lv_otype | TYPE P1000-OTYPE, " | |||
| lv_ausart_error | TYPE P1000, " | |||
| lv_objid | TYPE P1000-OBJID, " | |||
| lv_begda | TYPE P1000-BEGDA, " | |||
| lv_endda | TYPE P1000-ENDDA, " | |||
| lv_istat | TYPE P1000-ISTAT, " | |||
| lv_only_not_integrated | TYPE FLAG, " SPACE | |||
| lv_only_integrated | TYPE FLAG, " SPACE | |||
| lv_no_message | TYPE FLAG. " |
|   CALL FUNCTION 'RH_PM_AUSART_FOR_OBJECT_GET' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| PAY_MODE | = lv_pay_mode | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| ISTAT | = lv_istat | |
| ONLY_NOT_INTEGRATED | = lv_only_not_integrated | |
| ONLY_INTEGRATED | = lv_only_integrated | |
| NO_MESSAGE | = lv_no_message | |
| TABLES | ||
| AUSART_TAB | = lt_ausart_tab | |
| EXCEPTIONS | ||
| NOTHING_REQUIRED = 1 | ||
| AUSART_ERROR = 2 | ||
| . " RH_PM_AUSART_FOR_OBJECT_GET | ||
ABAP code using 7.40 inline data declarations to call FM RH_PM_AUSART_FOR_OBJECT_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.| "SELECT single PLVAR FROM P1000 INTO @DATA(ld_plvar). | ||||
| DATA(ld_pay_mode) | = ' '. | |||
| "SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype). | ||||
| "SELECT single OBJID FROM P1000 INTO @DATA(ld_objid). | ||||
| "SELECT single BEGDA FROM P1000 INTO @DATA(ld_begda). | ||||
| "SELECT single ENDDA FROM P1000 INTO @DATA(ld_endda). | ||||
| "SELECT single ISTAT FROM P1000 INTO @DATA(ld_istat). | ||||
| DATA(ld_only_not_integrated) | = ' '. | |||
| DATA(ld_only_integrated) | = ' '. | |||
Search for further information about these or an SAP related objects