SAP ISU_DISCDOC_GET_BP_FR_DEV Function Module for IS-U internal: Get billing period from device









ISU_DISCDOC_GET_BP_FR_DEV is a standard isu discdoc get bp fr dev 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-U internal: Get billing period from device 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 isu discdoc get bp fr dev FM, simply by entering the name ISU_DISCDOC_GET_BP_FR_DEV into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DISCDOC_GET_BP_FR_DEV 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 'ISU_DISCDOC_GET_BP_FR_DEV'"IS-U internal: Get billing period from device
  EXPORTING
*  X_EQUNR =  "Equipment Number
*  X_LOGIKNR =  "Logical Device Number
*  X_ANLAGE =  "Installation

 IMPORTING
   Y_BP_TYPE =  "

EXCEPTIONS
   NOT_FOUND = 1    INPUT_ERROR = 2    GENERAL_FAULT = 3
.



IMPORTING Parameters details for ISU_DISCDOC_GET_BP_FR_DEV

X_EQUNR - Equipment Number

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

X_LOGIKNR - Logical Device Number

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

X_ANLAGE - Installation

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

EXPORTING Parameters details for ISU_DISCDOC_GET_BP_FR_DEV

Y_BP_TYPE -

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

EXCEPTIONS details

NOT_FOUND - No assignment found

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR - Input error

Data type:
Optional: No
Call by Reference: Yes

GENERAL_FAULT - General Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_DISCDOC_GET_BP_FR_DEV 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_x_equnr  TYPE EQUNR, "   
lv_not_found  TYPE EQUNR, "   
lv_y_bp_type  TYPE BP, "   
lv_x_logiknr  TYPE LOGIKNR, "   
lv_input_error  TYPE LOGIKNR, "   
lv_x_anlage  TYPE ANLAGE, "   
lv_general_fault  TYPE ANLAGE. "   

  CALL FUNCTION 'ISU_DISCDOC_GET_BP_FR_DEV'  "IS-U internal: Get billing period from device
    EXPORTING
         X_EQUNR = lv_x_equnr
         X_LOGIKNR = lv_x_logiknr
         X_ANLAGE = lv_x_anlage
    IMPORTING
         Y_BP_TYPE = lv_y_bp_type
    EXCEPTIONS
        NOT_FOUND = 1
        INPUT_ERROR = 2
        GENERAL_FAULT = 3
. " ISU_DISCDOC_GET_BP_FR_DEV




ABAP code using 7.40 inline data declarations to call FM ISU_DISCDOC_GET_BP_FR_DEV

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!