SAP BBP_LA_BIZAPI_SUBMIT_CHAT Function Module for SRM-LAC BizAPI submit chat
BBP_LA_BIZAPI_SUBMIT_CHAT is a standard bbp la bizapi submit chat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SRM-LAC BizAPI submit 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 bizapi submit chat FM, simply by entering the name BBP_LA_BIZAPI_SUBMIT_CHAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_LA_BIZAPI
Program Name: SAPLBBP_LA_BIZAPI
Main Program: SAPLBBP_LA_BIZAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_LA_BIZAPI_SUBMIT_CHAT 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_BIZAPI_SUBMIT_CHAT'"SRM-LAC BizAPI submit chat.
EXPORTING
I_CLIENT_GUID = "Globally Unique identifier
I_CLIENT_SEQ_NO = "SRM Live Auction Sequence No.
I_LANGUAGE = "R/3 System, current language
I_SERVER_SEQ_NO = "SRM Live Auction Sequence No.
I_USER_ID = "SAP System, User Logon Name
IMPORTING
E_SERVER_SEQ_NO = "SRM Live Auction Sequence No.
E_AUC_HEADER = "SRM Live Auction BizApi Auction Header
ES_AUC_RTIME_PARMS = "Auction Runtime Parameters
E_SUBRC = "Return Value, Return Value After ABAP Statements
TABLES
* IT_CHAT = "SRM Live Auction BizApi Chat
* ET_AUC_ITEM = "Auction line item
* ET_ACKN = "SRM Live Auction BizApi Acknowledgment
* ET_PARTICIPANT = "SRM Live Auction BizApi Participant
* ET_CHAT = "SRM Live Auction BizApi Chat
* ET_BID = "SRM Live Auction BizApi Bid
* ET_LONGTEXT = "Long Texts for Procurement Document
* ET_DUMMY = "Table With Sequence Numbers for filtered entries
* ET_MESSAGES = "Error Messages
EXCEPTIONS
USER_NOT_VALID = 1
IMPORTING Parameters details for BBP_LA_BIZAPI_SUBMIT_CHAT
I_CLIENT_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
I_CLIENT_SEQ_NO - SRM Live Auction Sequence No.
Data type: BBP_LA_SEQ_NOOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - R/3 System, current language
Data type: SYLANGUOptional: No
Call by Reference: No ( called with pass by value option)
I_SERVER_SEQ_NO - SRM Live Auction Sequence No.
Data type: BBP_LA_SEQ_NOOptional: No
Call by Reference: No ( called with pass by value option)
I_USER_ID - SAP System, User Logon Name
Data type: SYUNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_LA_BIZAPI_SUBMIT_CHAT
E_SERVER_SEQ_NO - SRM Live Auction Sequence No.
Data type: BBP_LA_SEQ_NOOptional: No
Call by Reference: No ( called with pass by value option)
E_AUC_HEADER - SRM Live Auction BizApi Auction Header
Data type: BBPS_LA_BIZAPI_AUC_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
ES_AUC_RTIME_PARMS - Auction Runtime Parameters
Data type: BBPS_LA_BIZAPI_RTIME_PARMSOptional: No
Call by Reference: No ( called with pass by value option)
E_SUBRC - Return Value, Return Value After ABAP Statements
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_LA_BIZAPI_SUBMIT_CHAT
IT_CHAT - SRM Live Auction BizApi Chat
Data type: BBPS_LA_CHATOptional: Yes
Call by Reference: Yes
ET_AUC_ITEM - Auction line item
Data type: BBPS_LA_BIZAPI_AUC_ITEMOptional: Yes
Call by Reference: Yes
ET_ACKN - SRM Live Auction BizApi Acknowledgment
Data type: BBPS_LA_BIZAPI_ACKNOWLEDGMENTOptional: Yes
Call by Reference: Yes
ET_PARTICIPANT - SRM Live Auction BizApi Participant
Data type: BBPS_LA_BIZAPI_PARTICIPANTOptional: Yes
Call by Reference: Yes
ET_CHAT - SRM Live Auction BizApi Chat
Data type: BBPS_LA_BIZAPI_CHATOptional: Yes
Call by Reference: Yes
ET_BID - SRM Live Auction BizApi Bid
Data type: BBPS_LA_BIZAPI_BIDOptional: Yes
Call by Reference: Yes
ET_LONGTEXT - Long Texts for Procurement Document
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: Yes
ET_DUMMY - Table With Sequence Numbers for filtered entries
Data type: BBPS_LA_BIZAPI_DUMMYOptional: Yes
Call by Reference: Yes
ET_MESSAGES - Error Messages
Data type: BBP_MESSAGESOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
USER_NOT_VALID - user is not valid
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_LA_BIZAPI_SUBMIT_CHAT 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_it_chat | TYPE STANDARD TABLE OF BBPS_LA_CHAT, " | |||
| lv_i_client_guid | TYPE BBP_GUID, " | |||
| lv_user_not_valid | TYPE BBP_GUID, " | |||
| lv_e_server_seq_no | TYPE BBP_LA_SEQ_NO, " | |||
| lt_et_auc_item | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_AUC_ITEM, " | |||
| lv_e_auc_header | TYPE BBPS_LA_BIZAPI_AUC_HEADER, " | |||
| lv_i_client_seq_no | TYPE BBP_LA_SEQ_NO, " | |||
| lt_et_ackn | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_ACKNOWLEDGMENT, " | |||
| lv_i_language | TYPE SYLANGU, " | |||
| lv_es_auc_rtime_parms | TYPE BBPS_LA_BIZAPI_RTIME_PARMS, " | |||
| lv_e_subrc | TYPE SYSUBRC, " | |||
| lt_et_participant | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_PARTICIPANT, " | |||
| lv_i_server_seq_no | TYPE BBP_LA_SEQ_NO, " | |||
| lt_et_chat | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_CHAT, " | |||
| lv_i_user_id | TYPE SYUNAME, " | |||
| lt_et_bid | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_BID, " | |||
| lt_et_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lt_et_dummy | TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_DUMMY, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_MESSAGES. " |
|   CALL FUNCTION 'BBP_LA_BIZAPI_SUBMIT_CHAT' "SRM-LAC BizAPI submit chat |
| EXPORTING | ||
| I_CLIENT_GUID | = lv_i_client_guid | |
| I_CLIENT_SEQ_NO | = lv_i_client_seq_no | |
| I_LANGUAGE | = lv_i_language | |
| I_SERVER_SEQ_NO | = lv_i_server_seq_no | |
| I_USER_ID | = lv_i_user_id | |
| IMPORTING | ||
| E_SERVER_SEQ_NO | = lv_e_server_seq_no | |
| E_AUC_HEADER | = lv_e_auc_header | |
| ES_AUC_RTIME_PARMS | = lv_es_auc_rtime_parms | |
| E_SUBRC | = lv_e_subrc | |
| TABLES | ||
| IT_CHAT | = lt_it_chat | |
| ET_AUC_ITEM | = lt_et_auc_item | |
| ET_ACKN | = lt_et_ackn | |
| ET_PARTICIPANT | = lt_et_participant | |
| ET_CHAT | = lt_et_chat | |
| ET_BID | = lt_et_bid | |
| ET_LONGTEXT | = lt_et_longtext | |
| ET_DUMMY | = lt_et_dummy | |
| ET_MESSAGES | = lt_et_messages | |
| EXCEPTIONS | ||
| USER_NOT_VALID = 1 | ||
| . " BBP_LA_BIZAPI_SUBMIT_CHAT | ||
ABAP code using 7.40 inline data declarations to call FM BBP_LA_BIZAPI_SUBMIT_CHAT
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