SAP BBP_LA_AUCAPI_GET_AUCTION Function Module for Retrieves the auction header, line items, invitees, and chat
BBP_LA_AUCAPI_GET_AUCTION is a standard bbp la aucapi get auction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieves the auction header, line items, invitees, and chat 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 la aucapi get auction FM, simply by entering the name BBP_LA_AUCAPI_GET_AUCTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_LA_AUCAPI
Program Name: SAPLBBP_LA_AUCAPI
Main Program: SAPLBBP_LA_AUCAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_LA_AUCAPI_GET_AUCTION 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_LA_AUCAPI_GET_AUCTION'"Retrieves the auction header, line items, invitees, and chat.
EXPORTING
I_AUCTION_GUID = "Globally Unique identifier
* I_LANGUAGE = "R/3 System, current language
* I_CLIENT_TYPE = "Client type
* I_PARTNER_GUID = "Globally Unique identifier
* IV_LOGON_CURRENCY = "Logon Currency Key
IMPORTING
ES_AUC_HEADER = "Auction header
TABLES
* ET_AUC_ITEM = "Auction line item
* ET_PARTICIPANT = "Auction participant
* ET_CHAT = "Chat
* ET_LONGTEXT = "Long Texts for Procurement Document
* ET_MESSAGES = "Error Messages
IMPORTING Parameters details for BBP_LA_AUCAPI_GET_AUCTION
I_AUCTION_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - R/3 System, current language
Data type: SYLANGUOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CLIENT_TYPE - Client type
Data type: BBP_LA_CLIENT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNER_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGON_CURRENCY - Logon Currency Key
Data type: WAERSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_LA_AUCAPI_GET_AUCTION
ES_AUC_HEADER - Auction header
Data type: BBPS_LA_BIZAPI_AUC_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_LA_AUCAPI_GET_AUCTION
ET_AUC_ITEM - Auction line item
Data type: BBPS_LA_BIZAPI_AUC_ITEMOptional: Yes
Call by Reference: Yes
ET_PARTICIPANT - Auction participant
Data type: BBPS_LA_BIZAPI_PARTICIPANTOptional: Yes
Call by Reference: Yes
ET_CHAT - Chat
Data type: BBPS_LA_BIZAPI_CHATOptional: Yes
Call by Reference: Yes
ET_LONGTEXT - Long Texts for Procurement Document
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: Yes
ET_MESSAGES - Error Messages
Data type: BBP_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_LA_AUCAPI_GET_AUCTION 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: | ||||
| lt_et_auc_item | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_AUC_ITEM, " | |||
| lv_es_auc_header | TYPE BBPS_LA_BIZAPI_AUC_HEADER, " | |||
| lv_i_auction_guid | TYPE BBP_GUID, " | |||
| lv_i_language | TYPE SYLANGU, " | |||
| lt_et_participant | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_PARTICIPANT, " | |||
| lt_et_chat | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_CHAT, " | |||
| lv_i_client_type | TYPE BBP_LA_CLIENT_TYPE, " | |||
| lt_et_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lv_i_partner_guid | TYPE BBP_GUID, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_MESSAGES, " | |||
| lv_iv_logon_currency | TYPE WAERS. " |
|   CALL FUNCTION 'BBP_LA_AUCAPI_GET_AUCTION' "Retrieves the auction header, line items, invitees, and chat |
| EXPORTING | ||
| I_AUCTION_GUID | = lv_i_auction_guid | |
| I_LANGUAGE | = lv_i_language | |
| I_CLIENT_TYPE | = lv_i_client_type | |
| I_PARTNER_GUID | = lv_i_partner_guid | |
| IV_LOGON_CURRENCY | = lv_iv_logon_currency | |
| IMPORTING | ||
| ES_AUC_HEADER | = lv_es_auc_header | |
| TABLES | ||
| ET_AUC_ITEM | = lt_et_auc_item | |
| ET_PARTICIPANT | = lt_et_participant | |
| ET_CHAT | = lt_et_chat | |
| ET_LONGTEXT | = lt_et_longtext | |
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_LA_AUCAPI_GET_AUCTION | ||
ABAP code using 7.40 inline data declarations to call FM BBP_LA_AUCAPI_GET_AUCTION
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