SAP BAM4_READ_DETAIL_ANALYSIS_RFC Function Module for









BAM4_READ_DETAIL_ANALYSIS_RFC is a standard bam4 read detail analysis rfc 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 bam4 read detail analysis rfc FM, simply by entering the name BAM4_READ_DETAIL_ANALYSIS_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: BAM4
Program Name: SAPLBAM4
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAM4_READ_DETAIL_ANALYSIS_RFC 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 'BAM4_READ_DETAIL_ANALYSIS_RFC'"
  EXPORTING
*  OBJECT_TYPE =  "
   APPL =  "
   GROUP =  "
   SEQNO =  "
   OBJECT_ID =  "
   DATE =  "

 IMPORTING
   ENVIRONMENT =  "
   OBJECT_Z =  "
   OBJECT_R2 =  "
   OBJECT_FP_CTRLFLAG =  "
   VIEWSTR =  "

TABLES
*  OBJECT_G2 =  "
*  OBJECT_S3 =  "
*  OBJECT_S4 =  "
*  OBJECT_S5 =  "
*  OBJECT_TP =  "
*  OBJECT_FP_PROTTYPES =  "
*  OBJECT_FP_PROTOCOL =  "
*  OBJECT_MOD_OBJ =  "
*  OBJECT_RESULTS =  "
*  OBJECT_COMP_ASSOC =  "
*  MULTDOCS =  "
*  OBJECT_G1 =  "
*  OBJECT_B =  "
*  OBJECT_H =  "
*  OBJECT_R =  "
*  OBJECT_S =  "
*  OBJECT_G3 =  "
*  OBJECT_L6 =  "
*  OBJECT_L7 =  "

EXCEPTIONS
   NO_DATA_FOUND = 1    SYSTEM_FAILURE = 2    COMMUNICATION_FAILURE = 3
.



IMPORTING Parameters details for BAM4_READ_DETAIL_ANALYSIS_RFC

OBJECT_TYPE -

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

APPL -

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

GROUP -

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

SEQNO -

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

OBJECT_ID -

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

DATE -

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

EXPORTING Parameters details for BAM4_READ_DETAIL_ANALYSIS_RFC

ENVIRONMENT -

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

OBJECT_Z -

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

OBJECT_R2 -

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

OBJECT_FP_CTRLFLAG -

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

VIEWSTR -

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

TABLES Parameters details for BAM4_READ_DETAIL_ANALYSIS_RFC

OBJECT_G2 -

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

OBJECT_S3 -

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

OBJECT_S4 -

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

OBJECT_S5 -

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

OBJECT_TP -

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

OBJECT_FP_PROTTYPES -

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

OBJECT_FP_PROTOCOL -

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

OBJECT_MOD_OBJ -

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

OBJECT_RESULTS -

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

OBJECT_COMP_ASSOC -

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

MULTDOCS -

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

OBJECT_G1 -

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

OBJECT_B -

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

OBJECT_H -

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

OBJECT_R -

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

OBJECT_S -

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

OBJECT_G3 -

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

OBJECT_L6 -

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

OBJECT_L7 -

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

EXCEPTIONS details

NO_DATA_FOUND -

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

SYSTEM_FAILURE -

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

COMMUNICATION_FAILURE -

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

Copy and paste ABAP code example for BAM4_READ_DETAIL_ANALYSIS_RFC 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:
lt_object_g2  TYPE STANDARD TABLE OF BAMRTTYPE1, "   
lv_environment  TYPE BAMANENV, "   
lv_object_type  TYPE BAMUI-OBJTYPE, "   
lv_no_data_found  TYPE BAMUI, "   
lt_object_s3  TYPE STANDARD TABLE OF BAMRTTYPE8, "   
lt_object_s4  TYPE STANDARD TABLE OF BAMRTTYPE9, "   
lt_object_s5  TYPE STANDARD TABLE OF BAMTABI_30, "   
lt_object_tp  TYPE STANDARD TABLE OF THEADPROT, "   
lt_object_fp_prottypes  TYPE STANDARD TABLE OF SDPROTTYP, "   
lt_object_fp_protocol  TYPE STANDARD TABLE OF SDPROTOCOL, "   
lt_object_mod_obj  TYPE STANDARD TABLE OF BAMSSMODOB, "   
lt_object_results  TYPE STANDARD TABLE OF SNODETEXT, "   
lt_object_comp_assoc  TYPE STANDARD TABLE OF TFRC3, "   
lt_multdocs  TYPE STANDARD TABLE OF BAMMULTDOC, "   
lv_appl  TYPE BAMANDIR-APPL, "   
lv_object_z  TYPE BAMRTTYPE0, "   
lt_object_g1  TYPE STANDARD TABLE OF BAMRTTYPE2, "   
lv_system_failure  TYPE BAMRTTYPE2, "   
lv_group  TYPE BAMANDIR-GRPID, "   
lt_object_b  TYPE STANDARD TABLE OF BAMRTTYPE3, "   
lv_object_r2  TYPE BAMRTTYPE5, "   
lv_communication_failure  TYPE BAMRTTYPE5, "   
lv_seqno  TYPE BAMANDIR-SEQNO, "   
lt_object_h  TYPE STANDARD TABLE OF BAMRTTYPE2, "   
lv_object_fp_ctrlflag  TYPE SDCTRLFLAG, "   
lv_viewstr  TYPE BAMVIEWSTR, "   
lt_object_r  TYPE STANDARD TABLE OF BAMRTTYPE4, "   
lv_object_id  TYPE BAMANDIR-OBJID, "   
lv_date  TYPE SY-DATUM, "   
lt_object_s  TYPE STANDARD TABLE OF BAMRTTYPE4, "   
lt_object_g3  TYPE STANDARD TABLE OF BAMRTTYPEA, "   
lt_object_l6  TYPE STANDARD TABLE OF BAMRTTYPE6, "   
lt_object_l7  TYPE STANDARD TABLE OF BAMRTTYPE7. "   

  CALL FUNCTION 'BAM4_READ_DETAIL_ANALYSIS_RFC'  "
    EXPORTING
         OBJECT_TYPE = lv_object_type
         APPL = lv_appl
         GROUP = lv_group
         SEQNO = lv_seqno
         OBJECT_ID = lv_object_id
         DATE = lv_date
    IMPORTING
         ENVIRONMENT = lv_environment
         OBJECT_Z = lv_object_z
         OBJECT_R2 = lv_object_r2
         OBJECT_FP_CTRLFLAG = lv_object_fp_ctrlflag
         VIEWSTR = lv_viewstr
    TABLES
         OBJECT_G2 = lt_object_g2
         OBJECT_S3 = lt_object_s3
         OBJECT_S4 = lt_object_s4
         OBJECT_S5 = lt_object_s5
         OBJECT_TP = lt_object_tp
         OBJECT_FP_PROTTYPES = lt_object_fp_prottypes
         OBJECT_FP_PROTOCOL = lt_object_fp_protocol
         OBJECT_MOD_OBJ = lt_object_mod_obj
         OBJECT_RESULTS = lt_object_results
         OBJECT_COMP_ASSOC = lt_object_comp_assoc
         MULTDOCS = lt_multdocs
         OBJECT_G1 = lt_object_g1
         OBJECT_B = lt_object_b
         OBJECT_H = lt_object_h
         OBJECT_R = lt_object_r
         OBJECT_S = lt_object_s
         OBJECT_G3 = lt_object_g3
         OBJECT_L6 = lt_object_l6
         OBJECT_L7 = lt_object_l7
    EXCEPTIONS
        NO_DATA_FOUND = 1
        SYSTEM_FAILURE = 2
        COMMUNICATION_FAILURE = 3
. " BAM4_READ_DETAIL_ANALYSIS_RFC




ABAP code using 7.40 inline data declarations to call FM BAM4_READ_DETAIL_ANALYSIS_RFC

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 OBJTYPE FROM BAMUI INTO @DATA(ld_object_type).
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single APPL FROM BAMANDIR INTO @DATA(ld_appl).
 
 
 
 
"SELECT single GRPID FROM BAMANDIR INTO @DATA(ld_group).
 
 
 
 
"SELECT single SEQNO FROM BAMANDIR INTO @DATA(ld_seqno).
 
 
 
 
 
"SELECT single OBJID FROM BAMANDIR INTO @DATA(ld_object_id).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date).
 
 
 
 
 


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!