SAP BBP_IV_UNASSIGNED_SET Function Module for Prüft, ob und warum eine Position unassigned ist









BBP_IV_UNASSIGNED_SET is a standard bbp iv unassigned set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prüft, ob und warum eine Position unassigned ist 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 bbp iv unassigned set FM, simply by entering the name BBP_IV_UNASSIGNED_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_IV_UNASSIGNED_SET 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 'BBP_IV_UNASSIGNED_SET'"Prüft, ob und warum eine Position unassigned ist
EXPORTING
* IV_REFOBJ_TYPE = "Objekttyp
* IV_LOG_SYSTEM = "Logisches System des Logistik-Backends
* IS_HEADER = "Schnittstelle Kopf-Daten Beschaffungs-Beleg

TABLES
* IT_DOC_VALUES_DB = "Doc_values_db für BBP CF und BBP IV
* IT_ITEM = "Schnittstelle Positions-Daten Rechnung GetDetail-Fall
* ET_ITEM = "Schnittstelle Positions-Daten Rechnung GetDetail-Fall
.



IMPORTING Parameters details for BBP_IV_UNASSIGNED_SET

IV_REFOBJ_TYPE - Objekttyp

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

IV_LOG_SYSTEM - Logisches System des Logistik-Backends

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

IS_HEADER - Schnittstelle Kopf-Daten Beschaffungs-Beleg

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

TABLES Parameters details for BBP_IV_UNASSIGNED_SET

IT_DOC_VALUES_DB - Doc_values_db für BBP CF und BBP IV

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

IT_ITEM - Schnittstelle Positions-Daten Rechnung GetDetail-Fall

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

ET_ITEM - Schnittstelle Positions-Daten Rechnung GetDetail-Fall

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

Copy and paste ABAP code example for BBP_IV_UNASSIGNED_SET 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_iv_refobj_type  TYPE SWO_OBJTYP, "   
lt_it_doc_values_db  TYPE STANDARD TABLE OF BBPT_CFIV_DOC_VALUES_DB, "   
lt_it_item  TYPE STANDARD TABLE OF TABLE, "   
lv_iv_log_system  TYPE BE_LOG_SYSTEM, "   
lt_et_item  TYPE STANDARD TABLE OF BBP_PDS_INV_ITEM_D, "   
lv_is_header  TYPE ANY. "   

  CALL FUNCTION 'BBP_IV_UNASSIGNED_SET'  "Prüft, ob und warum eine Position unassigned ist
    EXPORTING
         IV_REFOBJ_TYPE = lv_iv_refobj_type
         IV_LOG_SYSTEM = lv_iv_log_system
         IS_HEADER = lv_is_header
    TABLES
         IT_DOC_VALUES_DB = lt_it_doc_values_db
         IT_ITEM = lt_it_item
         ET_ITEM = lt_et_item
. " BBP_IV_UNASSIGNED_SET




ABAP code using 7.40 inline data declarations to call FM BBP_IV_UNASSIGNED_SET

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!