PI_BP_GET_NEW_CONTACT_NUMBER SAP Function module

PI_BP_GET_NEW_CONTACT_NUMBER 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_GET_NEW_CONTACT_NUMBER 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_GET_NEW_CONTACT_NUMBER - PI BP GET NEW CONTACT NUMBER

CALL FUNCTION 'PI_BP_GET_NEW_CONTACT_NUMBER' "
* EXPORTING
*   is_partner =                " bsc_maini
*   is_partner1_and_2 =         " busei_rcom_instance
  IMPORTING
    ev_contact =                " knvk-parnr
  EXCEPTIONS
    NUMBERRANGE_ERROR = 1       "
    INTERNAL_ERROR = 2          "
    .  "  PI_BP_GET_NEW_CONTACT_NUMBER

ABAP code example for Function Module PI_BP_GET_NEW_CONTACT_NUMBER

The ABAP code below is a full code listing to execute function module PI_BP_GET_NEW_CONTACT_NUMBER 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_ev_contact  
 
 TYPE KNVK-PARNR
.


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

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

CALL FUNCTION 'PI_BP_GET_NEW_CONTACT_NUMBER'
* EXPORTING
*   is_partner =                 ld_is_partner
*   is_partner1_and_2 =          ld_is_partner1_and_2
  IMPORTING
    ev_contact =                 ld_ev_contact
  EXCEPTIONS
    NUMBERRANGE_ERROR =          1
    INTERNAL_ERROR =             2
    .  "  PI_BP_GET_NEW_CONTACT_NUMBER

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_ev_contact
 
 TYPE KNVK-PARNR ,
ld_is_partner
 
 TYPE BSC_MAINI ,
ld_is_partner1_and_2
 
 TYPE BUSEI_RCOM_INSTANCE .


ld_is_partner = 'Check type of data required'.
ld_is_partner1_and_2 = 'Check type of data required'.