PI_BP_FEEDBACK_REL_COLLECT SAP Function module

PI_BP_FEEDBACK_REL_COLLECT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PI_BP_FEEDBACK_REL_COLLECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CCCI
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PI_BP_FEEDBACK_REL_COLLECT - PI BP FEEDBACK REL COLLECT

CALL FUNCTION 'PI_BP_FEEDBACK_REL_COLLECT' "
  EXPORTING
    iv_status =                 " r3a_rel-status
*   is_partner1 =               " busei_com_instance
*   is_partner2 =               " busei_com_instance2
*   iv_contact =                " knvk-parnr
    iv_relation_category =      " r3a_rel-rel_catego
    .  "  PI_BP_FEEDBACK_REL_COLLECT

ABAP code example for Function Module PI_BP_FEEDBACK_REL_COLLECT

The ABAP code below is a full code listing to execute function module PI_BP_FEEDBACK_REL_COLLECT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_iv_status) = some text here

DATA(ld_is_partner1) = 'Check type of data required'.

DATA(ld_is_partner2) = 'Check type of data required'.
 

SELECT single PARNR 
  FROM KNVK 
  INTO @DATA(ld_iv_contact).



DATA(ld_iv_relation_category) = some text here
.

CALL FUNCTION 'PI_BP_FEEDBACK_REL_COLLECT'
  EXPORTING
    iv_status =                  ld_iv_status
*   is_partner1 =                ld_is_partner1
*   is_partner2 =                ld_is_partner2
*   iv_contact =                 ld_iv_contact
    iv_relation_category =       ld_iv_relation_category
    .  "  PI_BP_FEEDBACK_REL_COLLECT

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_iv_status
 
 TYPE R3A_REL-STATUS ,
ld_is_partner1
 
 TYPE BUSEI_COM_INSTANCE ,
ld_is_partner2
 
 TYPE BUSEI_COM_INSTANCE2 ,
ld_iv_contact
 
 TYPE KNVK-PARNR ,
ld_iv_relation_category
 
 TYPE R3A_REL-REL_CATEGO .



ld_iv_status = some text here
ld_is_partner1 = 'Check type of data required'.
ld_is_partner2 = 'Check type of data required'.

SELECT single PARNR 
  FROM KNVK 
  INTO ld_iv_contact.


ld_iv_relation_category = some text here