SAP BBP_SUS_IV_ASSIGNMENT Function Module for Rechnungserzeugung aus Vorgängerbelegen
BBP_SUS_IV_ASSIGNMENT is a standard bbp sus iv assignment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Rechnungserzeugung aus Vorgängerbelegen 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 sus iv assignment FM, simply by entering the name BBP_SUS_IV_ASSIGNMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_SUS_ASSIGNMENT
Program Name: SAPLBBP_SUS_ASSIGNMENT
Main Program: SAPLBBP_SUS_ASSIGNMENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_SUS_IV_ASSIGNMENT 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_SUS_IV_ASSIGNMENT'"Rechnungserzeugung aus Vorgängerbelegen.
EXPORTING
IV_OBJECT_TYPE = "Geschäftsvorgangstyp
* IV_SUBTYPE = "Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)
* IS_USER_INFO = "Übergabe der User-Information an den Search-Screen
* IV_NO_QUANCHECK = "Feld zum Ankreuzen
* IV_SIMULATE = '-' "boolsche Variable (X=true, -=false, space=unknown)
* IT_SELECTED_ITEMS = "Schlüsselfelder für Lean- oder Backend-Dokument
* IS_FOLLOW_UP_DOC_SETTINGS = "SUS Deviation und Folgebelegserzeugungs-Einstellungen
IMPORTING
ES_HEADER = "Schnittstelle Kopf-Daten Rückmeldung GetDetail-Fall
ET_ATTACH = "KW-Anlagen inkl. Dokument
ET_LIMITPO = "Liste der GUIDs
TABLES
IT_SELECTION = "Schlüsselfelder für Lean- oder Backend-Dokument
* ET_TAX = "Steuern
* ET_ACTUAL_VALUES = "Ist-Werte und Mengen
* ET_MESSAGES = "Fehlermeldungen zu einer PD-Methode
* ET_HCF = "Tabellenartige Kunden- und Solutionfelder am SUS Bestellkopf
* ET_ICF = "Tab. Kunden- und Solutionfelder an der SUS Bestellposition
* IT_DOC_VALUES_DB = "Struktur zum Merken der Dokumentwerte auf der Datenbank
* IT_ITEM_PO = "SRM-SUS: Table type for PO items
* ET_ITEM = "Schnittstelle Positions-Daten Rückmeldung GetDetail-Fall
* ET_PARTNER = "Geschäftspartner
* ET_LONGTEXT = "Langtexte zum Procurement Document
* ET_LIMIT = "Wertlimit
* ET_STATUS = "Status
* ET_FREIGHT = "Frachtkosten
IMPORTING Parameters details for BBP_SUS_IV_ASSIGNMENT
IV_OBJECT_TYPE - Geschäftsvorgangstyp
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: No
Call by Reference: Yes
IV_SUBTYPE - Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)
Data type: BBP_PDS_HEADER-SUBTYPEOptional: Yes
Call by Reference: Yes
IS_USER_INFO - Übergabe der User-Information an den Search-Screen
Data type: BBPS_SEL_USER_INFOOptional: Yes
Call by Reference: Yes
IV_NO_QUANCHECK - Feld zum Ankreuzen
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_SIMULATE - boolsche Variable (X=true, -=false, space=unknown)
Data type: BOOLEANDefault: '-'
Optional: Yes
Call by Reference: Yes
IT_SELECTED_ITEMS - Schlüsselfelder für Lean- oder Backend-Dokument
Data type: BBPT_OBJECT_KEYOptional: Yes
Call by Reference: Yes
IS_FOLLOW_UP_DOC_SETTINGS - SUS Deviation und Folgebelegserzeugungs-Einstellungen
Data type: BBPS_SUS_DEVOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_SUS_IV_ASSIGNMENT
ES_HEADER - Schnittstelle Kopf-Daten Rückmeldung GetDetail-Fall
Data type: BBP_PDS_SUSINV_HEADER_DOptional: No
Call by Reference: Yes
ET_ATTACH - KW-Anlagen inkl. Dokument
Data type: BBPT_PDS_ATT_TOptional: No
Call by Reference: Yes
ET_LIMITPO - Liste der GUIDs
Data type: BBP_T_SUS_GUIDSOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_SUS_IV_ASSIGNMENT
IT_SELECTION - Schlüsselfelder für Lean- oder Backend-Dokument
Data type: BBPS_OBJECT_KEYOptional: No
Call by Reference: Yes
ET_TAX - Steuern
Data type: BBP_PDS_TAXOptional: Yes
Call by Reference: Yes
ET_ACTUAL_VALUES - Ist-Werte und Mengen
Data type: BBP_PDS_ACTVALOptional: Yes
Call by Reference: Yes
ET_MESSAGES - Fehlermeldungen zu einer PD-Methode
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: Yes
ET_HCF - Tabellenartige Kunden- und Solutionfelder am SUS Bestellkopf
Data type: BBP_PDS_HCF_SUSPOOptional: Yes
Call by Reference: Yes
ET_ICF - Tab. Kunden- und Solutionfelder an der SUS Bestellposition
Data type: BBP_PDS_ICF_SUSPOOptional: Yes
Call by Reference: Yes
IT_DOC_VALUES_DB - Struktur zum Merken der Dokumentwerte auf der Datenbank
Data type: BBP_CFIV_DOC_VALUES_DBOptional: Yes
Call by Reference: Yes
IT_ITEM_PO - SRM-SUS: Table type for PO items
Data type: BBPT_PD_SUSPO_UI_ITEM_DOptional: Yes
Call by Reference: Yes
ET_ITEM - Schnittstelle Positions-Daten Rückmeldung GetDetail-Fall
Data type: BBP_PDS_SUSINV_ITEM_DOptional: Yes
Call by Reference: Yes
ET_PARTNER - Geschäftspartner
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: Yes
ET_LONGTEXT - Langtexte zum Procurement Document
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: Yes
ET_LIMIT - Wertlimit
Data type: BBP_PDS_LIMITOptional: Yes
Call by Reference: Yes
ET_STATUS - Status
Data type: BBP_PDS_STATUS_SUSOptional: Yes
Call by Reference: Yes
ET_FREIGHT - Frachtkosten
Data type: BBP_PDS_FREIGHTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_SUS_IV_ASSIGNMENT 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_es_header | TYPE BBP_PDS_SUSINV_HEADER_D, " | |||
| lt_it_selection | TYPE STANDARD TABLE OF BBPS_OBJECT_KEY, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lt_et_tax | TYPE STANDARD TABLE OF BBP_PDS_TAX, " | |||
| lt_et_actual_values | TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lt_et_hcf | TYPE STANDARD TABLE OF BBP_PDS_HCF_SUSPO, " | |||
| lt_et_icf | TYPE STANDARD TABLE OF BBP_PDS_ICF_SUSPO, " | |||
| lv_et_attach | TYPE BBPT_PDS_ATT_T, " | |||
| lv_iv_subtype | TYPE BBP_PDS_HEADER-SUBTYPE, " | |||
| lt_it_doc_values_db | TYPE STANDARD TABLE OF BBP_CFIV_DOC_VALUES_DB, " | |||
| lv_et_limitpo | TYPE BBP_T_SUS_GUIDS, " | |||
| lt_it_item_po | TYPE STANDARD TABLE OF BBPT_PD_SUSPO_UI_ITEM_D, " | |||
| lv_is_user_info | TYPE BBPS_SEL_USER_INFO, " | |||
| lt_et_item | TYPE STANDARD TABLE OF BBP_PDS_SUSINV_ITEM_D, " | |||
| lv_iv_no_quancheck | TYPE XFELD, " | |||
| lt_et_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lv_iv_simulate | TYPE BOOLEAN, " '-' | |||
| lt_et_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lv_it_selected_items | TYPE BBPT_OBJECT_KEY, " | |||
| lt_et_limit | TYPE STANDARD TABLE OF BBP_PDS_LIMIT, " | |||
| lv_is_follow_up_doc_settings | TYPE BBPS_SUS_DEV, " | |||
| lt_et_status | TYPE STANDARD TABLE OF BBP_PDS_STATUS_SUS, " | |||
| lt_et_freight | TYPE STANDARD TABLE OF BBP_PDS_FREIGHT. " |
|   CALL FUNCTION 'BBP_SUS_IV_ASSIGNMENT' "Rechnungserzeugung aus Vorgängerbelegen |
| EXPORTING | ||
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_SUBTYPE | = lv_iv_subtype | |
| IS_USER_INFO | = lv_is_user_info | |
| IV_NO_QUANCHECK | = lv_iv_no_quancheck | |
| IV_SIMULATE | = lv_iv_simulate | |
| IT_SELECTED_ITEMS | = lv_it_selected_items | |
| IS_FOLLOW_UP_DOC_SETTINGS | = lv_is_follow_up_doc_settings | |
| IMPORTING | ||
| ES_HEADER | = lv_es_header | |
| ET_ATTACH | = lv_et_attach | |
| ET_LIMITPO | = lv_et_limitpo | |
| TABLES | ||
| IT_SELECTION | = lt_it_selection | |
| ET_TAX | = lt_et_tax | |
| ET_ACTUAL_VALUES | = lt_et_actual_values | |
| ET_MESSAGES | = lt_et_messages | |
| ET_HCF | = lt_et_hcf | |
| ET_ICF | = lt_et_icf | |
| IT_DOC_VALUES_DB | = lt_it_doc_values_db | |
| IT_ITEM_PO | = lt_it_item_po | |
| ET_ITEM | = lt_et_item | |
| ET_PARTNER | = lt_et_partner | |
| ET_LONGTEXT | = lt_et_longtext | |
| ET_LIMIT | = lt_et_limit | |
| ET_STATUS | = lt_et_status | |
| ET_FREIGHT | = lt_et_freight | |
| . " BBP_SUS_IV_ASSIGNMENT | ||
ABAP code using 7.40 inline data declarations to call FM BBP_SUS_IV_ASSIGNMENT
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 OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_type). | ||||
| "SELECT single SUBTYPE FROM BBP_PDS_HEADER INTO @DATA(ld_iv_subtype). | ||||
| DATA(ld_iv_simulate) | = '-'. | |||
Search for further information about these or an SAP related objects