BBP_PROCDOC_GETLIMIT SAP Function module

BBP_PROCDOC_GETLIMIT 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 BBP_PROCDOC_GETLIMIT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BBP_PROCDOC_GETLIMIT - BBP PROCDOC GETLIMIT

CALL FUNCTION 'BBP_PROCDOC_GETLIMIT' "
  EXPORTING
*   iv_po_guid =                " crmd_orderadm_h-guid
*   iv_po_number =              " crmd_orderadm_h-object_id
*   iv_po_i_guid =              " crmd_orderadm_i-guid
*   iv_po_item_number =         " crmd_orderadm_i-number_int
    iv_object_type =            " crmd_orderadm_h-object_type
    iv_tol_group =              " bbp_tol_group
    iv_vendor_guid =            " crmt_partner_no
*   iv_ordering_party =         " crmt_partner_no
    is_item =                   " bbp_pds_item
  TABLES
    et_po_limit =               " bbp_pds_limit
*   et_messages =               " bbp_pds_messages
  EXCEPTIONS
    NO_LIMIT_FOUND = 1          "
    WRONG_INPUT = 2             "
    .  "  BBP_PROCDOC_GETLIMIT

ABAP code example for Function Module BBP_PROCDOC_GETLIMIT

The ABAP code below is a full code listing to execute function module BBP_PROCDOC_GETLIMIT 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:
it_et_po_limit  
 
 TYPE STANDARD TABLE OF BBP_PDS_LIMIT,"TABLES PARAM
wa_et_po_limit
 
 LIKE LINE OF it_et_po_limit
,
it_et_messages  
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_et_messages
 
 LIKE LINE OF it_et_messages
.

 

SELECT single GUID 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_iv_po_guid).

 

SELECT single OBJECT_ID 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_iv_po_number).

 

SELECT single GUID 
  FROM CRMD_ORDERADM_I 
  INTO @DATA(ld_iv_po_i_guid).

 

SELECT single NUMBER_INT 
  FROM CRMD_ORDERADM_I 
  INTO @DATA(ld_iv_po_item_number).

 

SELECT single OBJECT_TYPE 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_iv_object_type).


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

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

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

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

"populate fields of struture and append to itab
append wa_et_po_limit to it_et_po_limit.
 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
.

CALL FUNCTION 'BBP_PROCDOC_GETLIMIT'
  EXPORTING
*   iv_po_guid =                 ld_iv_po_guid
*   iv_po_number =               ld_iv_po_number
*   iv_po_i_guid =               ld_iv_po_i_guid
*   iv_po_item_number =          ld_iv_po_item_number
    iv_object_type =             ld_iv_object_type
    iv_tol_group =               ld_iv_tol_group
    iv_vendor_guid =             ld_iv_vendor_guid
*   iv_ordering_party =          ld_iv_ordering_party
    is_item =                    ld_is_item
  TABLES
    et_po_limit =                it_et_po_limit
*   et_messages =                it_et_messages
  EXCEPTIONS
    NO_LIMIT_FOUND =             1
    WRONG_INPUT =                2
    .  "  BBP_PROCDOC_GETLIMIT

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_iv_po_guid
 
 TYPE CRMD_ORDERADM_H-GUID ,
it_et_po_limit
 
 TYPE STANDARD TABLE OF BBP_PDS_LIMIT ,
wa_et_po_limit
 
 LIKE LINE OF it_et_po_limit,
ld_iv_po_number
 
 TYPE CRMD_ORDERADM_H-OBJECT_ID ,
it_et_messages
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_et_messages
 
 LIKE LINE OF it_et_messages,
ld_iv_po_i_guid
 
 TYPE CRMD_ORDERADM_I-GUID ,
ld_iv_po_item_number
 
 TYPE CRMD_ORDERADM_I-NUMBER_INT ,
ld_iv_object_type
 
 TYPE CRMD_ORDERADM_H-OBJECT_TYPE ,
ld_iv_tol_group
 
 TYPE BBP_TOL_GROUP ,
ld_iv_vendor_guid
 
 TYPE CRMT_PARTNER_NO ,
ld_iv_ordering_party
 
 TYPE CRMT_PARTNER_NO ,
ld_is_item
 
 TYPE BBP_PDS_ITEM .



SELECT single GUID 
  FROM CRMD_ORDERADM_H 
  INTO ld_iv_po_guid.
 

"populate fields of struture and append to itab
append wa_et_po_limit to it_et_po_limit.

SELECT single OBJECT_ID 
  FROM CRMD_ORDERADM_H 
  INTO ld_iv_po_number.
 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.

SELECT single GUID 
  FROM CRMD_ORDERADM_I 
  INTO ld_iv_po_i_guid.


SELECT single NUMBER_INT 
  FROM CRMD_ORDERADM_I 
  INTO ld_iv_po_item_number.


SELECT single OBJECT_TYPE 
  FROM CRMD_ORDERADM_H 
  INTO ld_iv_object_type.

ld_iv_tol_group = 'Check type of data required'.
ld_iv_vendor_guid = 'Check type of data required'.
ld_iv_ordering_party = 'Check type of data required'.
ld_is_item = 'Check type of data required'.