SAP ISMAM_RD_DOC_ITEM_STATUS_CHECK Function Module for IS-M: Has ROD Item Been Performed?

Search SAP Function Modules

ISMAM_RD_DOC_ITEM_STATUS_CHECK is a standard ismam rd doc item status check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Has ROD Item Been Performed? 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 ismam rd doc item status check FM, simply by entering the name ISMAM_RD_DOC_ITEM_STATUS_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function ISMAM_RD_DOC_ITEM_STATUS_CHECK 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 'ISMAM_RD_DOC_ITEM_STATUS_CHECK'"IS-M: Has ROD Item Been Performed?
  EXPORTING
   PV_KNUMV =  "Number of Document Condition
   PV_KPOSN =  "Condition Item Number

 IMPORTING
   PV_POPER =  "IS-M: Posting Year and Posting Period Format YYYYMMM)

EXCEPTIONS
   STATUS_DONE = 1 

.

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_SAPLJHEF_001 IS-M/AM: Revenue Object Determination per Pricing: Enhance Comm.Structure
EXIT_SAPLJHEF_002 IS-M: Evaluation of Revenue Distribution Criteria for Account Determin.
EXIT_SAPLJHEF_003 IS-M: Evaluate Revenue Distribution Criteria for Percentage Valuation
EXIT_SAPLJHEF_004 IS-M: Fill CO-PA Interface from Revenue Object Document
EXIT_SAPLJHEF_005 IS-M/AM: Create Revenue Distribution Interface

IMPORTING Parameters details for ISMAM_RD_DOC_ITEM_STATUS_CHECK

PV_KNUMV - Number of Document Condition

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

PV_KPOSN - Condition Item Number

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

EXPORTING Parameters details for ISMAM_RD_DOC_ITEM_STATUS_CHECK

PV_POPER - IS-M: Posting Year and Posting Period Format YYYYMMM)

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

EXCEPTIONS details

STATUS_DONE -

Data type:
Optional: No
Call by Reference: Yes

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

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