SAP PLM_AUDIT_PLAN_PREFETCH_M_DB Function Module for

Search SAP Function Modules

PLM_AUDIT_PLAN_PREFETCH_M_DB is a standard plm audit plan prefetch m db 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 plm audit plan prefetch m db FM, simply by entering the name PLM_AUDIT_PLAN_PREFETCH_M_DB into the relevant SAP transaction such as SE37 or SE38.

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

Function PLM_AUDIT_PLAN_PREFETCH_M_DB 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 'PLM_AUDIT_PLAN_PREFETCH_M_DB'"
  EXPORTING
*  I_AUD_OBJECTTYPE = 'AUP' "
*  I_EXTERNAL_ID_RANGE =  "
*  I_PROC_STATUS_RANGE =  "
*  IT_PROJECT_GUID =  "
*  IT_PLANFINISH_RANGE =  "
*  IT_ACTUALFINISH_RANGE =  "
*  IT_AUTH_GROUP_RANGE =  "
*  I_PLANSTART_RANGE =  "
*  I_ACTUALSTART_RANGE =  "
*  I_CHANGED_ON_RANGE =  "
*  I_CREATED_ON_RANGE =  "
*  I_CHANGED_BY_RANGE =  "
*  I_CREATED_BY_RANGE =  "
*  I_SEARCH_FIELD_RANGE =  "
*  I_GROUPING_RANGE =  "

TABLES
   E_GUID_TAB =  "

EXCEPTIONS
   WRONG_INPUT = 1    NOTHING_FOUND = 2 

.

IMPORTING Parameters details for PLM_AUDIT_PLAN_PREFETCH_M_DB

I_AUD_OBJECTTYPE -

Data type: CGPL_OBJECT_TYPE
Default: 'AUP'
Optional: No
Call by Reference: Yes

I_EXTERNAL_ID_RANGE -

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

I_PROC_STATUS_RANGE -

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

IT_PROJECT_GUID -

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

IT_PLANFINISH_RANGE -

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

IT_ACTUALFINISH_RANGE -

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

IT_AUTH_GROUP_RANGE -

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

I_PLANSTART_RANGE -

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

I_ACTUALSTART_RANGE -

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

I_CHANGED_ON_RANGE -

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

I_CREATED_ON_RANGE -

Data type: PLMT_AUDIT_RANGES_FOR_DATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHANGED_BY_RANGE -

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

I_CREATED_BY_RANGE -

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

I_SEARCH_FIELD_RANGE -

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

I_GROUPING_RANGE -

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

TABLES Parameters details for PLM_AUDIT_PLAN_PREFETCH_M_DB

E_GUID_TAB -

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

EXCEPTIONS details

WRONG_INPUT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOTHING_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PLM_AUDIT_PLAN_PREFETCH_M_DB 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.

ABAP code using 7.40 inline data declarations to call FM PLM_AUDIT_PLAN_PREFETCH_M_DB

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