on 03-20-2008 3:52 PM
This the all the code it takes to send the bid invitation for all the bidders as XML. You can build a custom program / create a new implementation of the BADI imp we discussed in the earlier thread. Hope this solves your problem.
*&---------------------------------------------------------------------*
*& Report ZKB_SEND_BID_AS_XML
*&---------------------------------------------------------------------*
REPORT zkb_send_bid_as_xml.
* Selection Screen - Bid Invi Number
PARAMETERS: p_obj_id TYPE crmt_object_id_db OBLIGATORY.
* Local Declarations - Internal Tables
DATA: lt_e_partner TYPE TABLE OF bbp_pds_partner.
DATA: lt_e_messages TYPE TABLE OF bbp_pds_messages.
* Local Declarations - Work Areas
DATA: ls_e_header TYPE bbp_pds_bid_header_d.
DATA: ls_e_partner TYPE bbp_pds_partner.
DATA: ls_e_messages TYPE bbp_pds_messages.
* Get the Bid Invi details
CALL FUNCTION 'BBP_PD_BID_GETDETAIL'
EXPORTING
i_object_id = p_obj_id
IMPORTING
e_header = ls_e_header
TABLES
e_partner = lt_e_partner.
* Delete other partners other than bidders
DELETE lt_e_partner WHERE partner_fct <> '00000018'.
* Send Bid Invi for all bidders
LOOP AT lt_e_partner INTO ls_e_partner.
CLEAR: lt_e_messages.
CALL FUNCTION 'BBP_RFQ_SEND'
EXPORTING
iv_guid = ls_e_header-guid
iv_action_code = '01'
is_partner = ls_e_partner
iv_object_type = 'BUS2200'
IMPORTING
et_messages = lt_e_messages.
READ TABLE lt_e_messages INTO ls_e_messages
WITH KEY msgty = 'E'.
IF sy-subrc NE 0.
COMMIT WORK AND WAIT.
ENDIF.
ENDLOOP.
Regards
Kathirvel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kathirvel,
Thanks for your help.
We have created our own implementation for BADI: EXEC_METHODCALL_PPF and called it ZSEND_BID_AS_XML. The Method Filter was called: ZPPPFDFLTVAL.....which we have selected as the method in the configuration.
Now when we publish a new Bid Invitation, the BADI is not getting triggered. Is there something we may have missed in configuring? (We do not see any errors in SM21 or SLG1 or SXMB_MONI)
Current Configuration:
IMG --> SRM Server --> Cross Appl. Basic Settings --> Set Output Actions and Output Format --> Define Actions for PO Output --> (Select Bid Invitation BBP_PD_BID)
Action Definition -->
ActionProfile BBP_PD_BID
Description Bid Invitation
Action Definition STANDARD_BID
Description Bid Invitation
Processing Time : Processing when saving document
Processing Times Not Permitted : No Restrictions
Sort Order For Display 0
Action Determination and Action Merging:
Determination Technology: SRM: Output Generation: Bid Invitation Offer
Action Merging : Set Highest Number of Processed Actions
Processing Types:
Method set as Default
Method : ZPPFDFLTVAL
Description: Send Bid Invitation as XML to XI
Thanks,
Ashwani
Hi Ashwani,
The config you have maintained is perfect. Please note that the BADI would be called in a background task and hence debugging the code in the BADI while publishing the BID is not possible.
Please check the following:
1. Make sure your custom implementation is active and the standard implementation is inactive
2. Just to make sure whether the BADI is called, please do the below:
Change the value of Processing Time as below:
Processing Time : Processing using selection report and publish a new bid invitation. Then goto transaction SPPFP and search the entires created. You must find entries for the Bid Invitation (refer the field KEY) you have published (If you are not able to find any entries here, then please raise an OSS message with SAP, because this is a standard functionality and the system should create these entries). Now put a break point in the BADI and start processing entries in the transaction SPPFP. This would stop at the break point (provided point 1 is correct).
For more info please check this note: Note 564826 - EBP: Customizing for the output of EBP documents
Best Regards
Kathirvel
Hi Kathirvel,
After 3 weeks of back and forth with SAP, SAP has finally replied that they do not support the configuration that we did for passing XML docs. Please review below answer from SAP and would appreciate any thoughts/suggestions.
FYI - We are on SRM 4 with Classic Scenario.
*Dear Customer,
I am Meghalaya Lolla, from SRM-EBP-CA-PRT development support currently processing this message as Sapna Patil is not available today. We have discussed this issue with our PPF frame expert and XML expert and as per our experts information, As per the standard system design, to send an xml from a bid invitation when you click PUBLISH button is not possible because of the following reasons:
1. There is no proxy interface for bid invitation available to send a xml.
2. In SRM 4.0, Post Processing Framework(PPF) is not called and there is no output determination through PPF while publishing the bid invitation. Therefore, PPFTTRIGG table will not any entries when a bid invitation is published via mail, Due to this reason, you won't find any entries for this output using the PSPPFPROCESs report aswell3. The MAIL output is created and SEND using the SAPCONNECT interface of class cl_document_bcs from the FM BBP_OUTPUT_BIDINV_BID.
Due to this reasons, the standard implementation BBP_RFQ_SEND_XML is never be called when you publish a bid invitation.
In summary, xml output from bid invitation while you are publishing is not possible as per the current system design.
If you still want to use the xml medium, you have to do your own modifications. But SAP is not at responsible and will not support on issues due to your modifications. In that case, we can provide you only remote consulting services.
Just for your information, briefly here I am providing a rough idea how xml "could" work with your modifications. This is just to give you an idea. But we can not provide any more support on this consulting issue.
If you want SAP support on this modifications, the message will be forwarded to remote consulting department.
To use an xml medium, you have to do the following:
===================================================
- Use the badi BBP_CHANGE_SF_BID for changing the medium outside the FM BBP_OUTPUT_BIDINV_BID
- Change the document type from 'RAW' to 'XML', the default document type is 'RAW' for sending texts via mail.
- Pass the xml contents aswell to the FM BBP_OUTPUT_BIDINV_BID by writing your own modification. for passing the contents you can use your report ZSEND_BID_AS_XML)
- Remove imeplementation ZPPFDFLTVAL for process type method call from customizing and leave as it is before that is the standard implementation.*
Regards,
Ashwani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.