Entries in BBP_DOCUMENT_TAB, doc_type = IM

Hello,
I have a shopping cart that generated a purchase order.
Now, the user is trying to do "Confirm Goods Receipt". But when he clicks on the order, he receives the message BBP_CF044 "Error blocking purchase order in backend. Inform system administration".
In the table BBP_DOCUMENT_TAB I could see three entries (one for each item in the PO). And the DOC_TYPE = IM. What does it mean?
The report CLEAN_REQREQ_UP runs every 20 minutes.
What can I do?
Thanks!!!!!!!

Hi
Please go through this ->
Note 623457 Incorrect entries in BBP_DOCUMENT_TAB
Note 549846 FAQ: Goods receipt confirmation EBP
Note 457505 Check the lock for backend purchase orders
Note 388601 Follow-up processing for GR/SE confirmation is not possible
Re: SC not to be seen in check status after MIGO in R/3
Do update me.
Regards
- Atul

Similar Messages

BBP_DOCUMENT_TAB- Entries with special charaters afetr unicode upgrade

Hi,
We are on SRM 5.0 (SRM_SERVER 550) Sp07. SAp 4.7 backend.
We are upgrading the system to unicode.
What we have observed is after PO creation the BBP_DOCUMENT_TAB has some special characters in the field 'Key'
For example:
BUS2121001##䟅㳤탇ᾣᾣઃ????#?? ######## 01############################
In the non unicode system the entry reads like below
BUS2121001GAEp#?g8Ia#####o# ################ 01###########
This does not cause problems in most of the SRM systems, but in one of the systems, the Clean_reqreq_up job is failing with a message 'Buffer table not up to date'. We are not sure if this is due to the entries in BBP_DOCUMENT_TAB which have special characters or not.
Can someone please explain the impact/risk of such entries in BBP_DOCUMENT_TAB. Is this a known issue. is there any solution for this?
Thanks & regards,
Srivatsan
Edited by: Srivatsan on Feb 29, 2008 1:14 PM

Hi,
The special characters may be due unicode/langauage issue.
See the foll notes:
Note 548016 - Conversion to Unicode
Related Notes
986907 - SQL Server settings for R3load based system copy
971646 - 6.40 Patch Collection Hom./Het.System Copy ABAP
956921 - IDES ERP 2005 ECC 6.0
952514 - Using the table splitting feature
938374 - Additional tools for MDMP --> Unicode conversion preparation
936441 - Oracle settings for R3load based system copy
932779 - Unicode conversion - analysis of nametab problems
928729 - Combined Upgrade & Unicode Conversion (CU&UC) FAQ
920831 - RFC with inactive text language
896144 - mySAP ERP 2005 Upgrade for R/3 or ERP MDMP Customers
895560 - Support for languages only available in Unicode system
871541 - Frequently used text patterns
857081 - Unicode conversion: downtime estimate
855772 - Distribution Monitor
852235 - Release Restrictions for SAP ERP 6.0
814707 - Troubleshooting for RFC connections Unicode/non-Unicode
812821 - Cascading Font settings
806554 - FAQ: I/O-intensive database operations
795267 - System Copy for 'SAP Web AS Java' based systems
793113 - FAQ: Oracle I/O configuration
791199 - Default editor changed to MSWord in SAPscript and SmartForms
750219 - Unicode UTF-8 printing with HP printers
747036 - mySAP ERP 2004 Upgrade for R/3 MDMP Customers
745030 - MDMP - Unicode Interfaces: Solution Overview
742662 - MS Word as Editor in SAPscript and Smart Forms
741821 - Release limitations concerning SAP ERP 2004
693168 - Minimized Downtime Service and Incremental Migration (IMIG)
673244 - SAPGUI: Recent corrections for Unicode support.
647495 - RFC for Unicode ./. non-Unicode Connections
638357 - Transport between Unicode and non-Unicode systems
585116 - Translation after installation of WebAS SP25
573044 - Unicode conversion for HR application
552464 - What is Big Endian / Little Endian? What Endian do I have?
551344 - Unicode Conversion
547444 - RFC Enhancement for Unicode ./. non-Unicode Connections
543715 - BW Migrations and System Copies for BW 2.0B / 2.1 Content
540911 - Unicode restrictions for R/3 Enterprise, ECC 5.0, ECC 6.0
508854 - SAPGUI: How to use Unicode
379940 - Unicode based mySAP availability
355771 - Oracle: Explanation of the new tablespace layout
330267 - Transports between Basis Releases 4.6* and 6.*
316903 - SAPGUI: How to use I18N mode
215015 - Unicode UTF-8 printing with a Lexmark printer
80727 - Transporting non-LATIN-1 texts
79991 - Multi-Language and Unicode support of mySAP solutions
73606 - Supported Languages and Code Pages
BR,
Disha.
Do reward points for useful answers.

Data in BBP_DOCUMENT_TAB are not getting deleted

Hi All,
We are in SRM 4.0.
Since today morning whenever a user trying to create / change shopping cart, PO, GR it got updated in the BBP_DOCUMENT_TAB. But it is not getting deleted automatically. Earlier it used to get deleted automatically once the documents have been ordered.
But I could see the POs and GRs have been transfered to the back end system.
Job CLEAN_REQREQ_UP is running every 2 mts.
Please advise.

Hi Arun,
note 338985 describes in detail how the the status of the document(s), CLEAN_REQREQ_UP and the IDOCs interact.
If the documents are posted without any error i.e. there´s everything perfect but the 'obsolete' entries in BBP_DOCUMENT_TAB, then this sounds like a malfunction.
Maybe you should debug the the cleaner with one document and see whats happening starting at the following spot:
CLEAN_REQREQ_UP
process selected entries: check existence of follow on documents,
update if necessary local documents etc. (depends on entry type)
        LOOP AT selarea.
          IF still_to_proc = c_proc_block_size.
            SET UPDATE TASK LOCAL.
          ENDIF.
lateron the entries are deleted in function module BBP_DELETE_FROM_DOCUMENT_TAB
Note 535765 describes how to delete entries via a Z* report but I would NOT RECOMMEND to do that without having checked the situation by SAP before.
see note 535765:
Please note!:
Deleting relevant entries from the BBP_DOCUMENT_TAB may cause severe
problems, as the system needs the entries to set the right status to
shopping carts, invoices and confirmations. So please be careful with
the deletion of entries.
Kind Regards
Michael

SRM - Delete confirmation (service entry sheet)

Hi,
we have the 5.00SRM.
The user tried to post twice the same confirmation (service entry sheet) so the system replicated the first one in R3 and the second is in error for the Purchase order lock (message class SAP-T100 message-id BBP_ADMIN 010).
It's right that the second is in error (Luckly!!!), but now we don't know how delete it (the second wrong confirmation), because in the confirmation transaction the delete button is inactive. Now the user need to create a new confirmation for the same purchase order, but since now all the confirmations for that purchase order go in error.
Please, help me ... I looked all SAP notes and forum messages but I didn't find the solution.
Thanks
Lara

Hi
Which SRM scenarion and version are you using ?
Seems to be some bug in the system (Either due to wrong implmentation of some OSS note or some other reasons).
Anyways, better to raise an OSS message with SAP as well.
Refer to following OSS notes.
535765 Too many entries in BBP_DOCUMENT_TAB
1028584 You cannot delete confirmations that are in approval process
863198 Confirmation screen is locked on click on delete button
668829 Error when deleting held goods receipt confirmations
852327 Disable Deletion of Confirmed PO Items
994529 Conf can be deleted despite error in DOC_CHECK_BADI
778489 Partial confirmations for back-end service purchase orders
602973 Duplicate error messages during confirmation
499917 EBP: deleted return delivery: BBPERS creates no invoice
786051 Deleted service lines are checked
515754 Deletion of held confirmation documents in back-end case
355138 Cancellation of goods receipt/service confirmation
430660 Deletion, change, return delivery possible after return
Hope this will help.
Regards
- Atul

Good receipt not deleted in table BBP_DOCUMENt_TAB

Hello,
In SRM 5.5, we have a problem when posting confirmation.
The programm CLEAN_REQREQ_UP doesn't delete all entries 'IM' in table BBP_DOCUMENT_TAB.
In R/3 backend, when we remove the note 384660, it works but it's not so good.
To remove this note, means to increaze Idocs in R/3 backend.
In EBP 3.0, this problem doesn't exist.
Please, if somebody can help me to solve this issue?
Thanks in advance four your help.
Claudine

Hi Claudine,
We are facing the same problem where in the IM ( Conformation) entries are
not being cleaned by the CLEAN_REQREQ_UP batch job.
I went though the OSS available and there are some old notes which talks of this issue. OSS 171113, 187802..but no soution recommended.
I also came across this note 644963 which talks of a report to delete the IM entries in BBP_DOCUMENT_TAB (Report :ZZ_CLEAN_BBP_DOCUMENT_TAB).
But this report has not be provided by SAP in patch level SRM_SERVER 550 -SAPKIBKT05.
Please let us know if you got a solution to this issue.
Best Regards
Prashanth

Hi pls respond my code its urgent

hi,
my prblm is in this program i used bapi function module for upload excel data.
bapi_incominginvoice_park.
in my output park number showing increasing for each item.
so i need parknumber it should be same for all items.
i am sending my code pls check this.
*& Report ZBAPI_MIRO
&& Developed By : ESWAR
*& Created Date : 29.10.2007
*& Requested By : GANESH(MM)
*& SAP Area : MM
*& Output : Excel format,Using BDC for Tcode MIRO
REPORT ZBAPI_MIRO.
DATA: BEGIN OF INTERN OCCURS 0.
 INCLUDE STRUCTURE ALSMEX_TABLINE.
DATA: END OF INTERN.
DATA : IT_INTERN LIKE INTERN OCCURS 0 WITH HEADER LINE.
No of columns
DATA: BEGIN OF DATA_TAB OCCURS 0,
 VALUE_0001(10), "DOC.TYPE
 VALUE_0002(10), "DOC DATE
 VALUE_0003(10), " PSTNG.DATE
 VALUE_0003(10), " GROSS_AMNT
 VALUE_0004(10), " REF_DOC_NO
 VALUE_0005(10), "BLINE_DATE
 VALUE_0006(10), "HEADER_TXT
 VALUE_0007(10), "INVOICE_DOC_ITEM
 VALUE_0008(10), "PO_NUMBER
 VALUE_0009(10), " PO_ITEM
 VALUE_0010(10), "TAX_CODE
 VALUE_0011(11), "ITEM_AMOUNT
 VALUE_0012(10), "SHEET_NO
 VALUE_0013(10), "ITEM_TEXT
 VALUE_0014(10), "SHEET_ITEM
 END OF DATA_TAB.
DATA : BEGIN OF IT_DATA OCCURS 0,
 invoice_ind like BAPI_INCINV_CREATE_HEADER-invoice_ind,
 doc_type like BAPI_INCINV_CREATE_HEADER-doc_type,
 doc_date like BAPI_INCINV_CREATE_HEADER-doc_date,
 pstng_date like BAPI_INCINV_CREATE_HEADER-pstng_date,
 comp_code like BAPI_INCINV_CREATE_HEADER-comp_code,
 currency like BAPI_INCINV_CREATE_HEADER-currency,
 gross_amount like BAPI_INCINV_CREATE_HEADER-gross_amount,
 calc_tax_ind like BAPI_INCINV_CREATE_HEADER-calc_tax_ind,
 REF_DOC_NO LIKE BAPI_INCINV_CREATE_HEADER-REF_DOC_NO,
 bline_date like BAPI_INCINV_CREATE_HEADER-bline_date,
 header_txt like BAPI_INCINV_CREATE_HEADER-header_txt,
 invoice_doc_item like BAPI_INCINV_CREATE_ITEM-invoice_doc_item,
 po_number like BAPI_INCINV_CREATE_ITEM-po_number,
 po_item like BAPI_INCINV_CREATE_ITEM-po_item,
 tax_code like BAPI_INCINV_CREATE_ITEM-tax_code,
 item_amount like BAPI_INCINV_CREATE_ITEM-ITEM_AMOUNT,
 sheet_no like BAPI_INCINV_CREATE_ITEM-sheet_no,
 item_text like BAPI_INCINV_CREATE_ITEM-item_text,
 sheet_item like BAPI_INCINV_CREATE_ITEM-sheet_item,
 END OF IT_DATA.
 DATA : BEGIN OF IT_CHAR OCCURS 0,
 IND(6) TYPE N, ""Index for comparison
 CHARN LIKE RCTMS-MNAME, "CHAR NAME
 CHARV LIKE RCTMS-MWERT, "CHAR VALUE
 END OF IT_CHAR.
 DATA: BEGIN OF it_msg OCCURS 0,
 po_number LIKE BAPI_INCINV_CREATE_ITEM-po_number,
 po_item like BAPI_INCINV_CREATE_ITEM-po_item,
 message(20),
 message1(90),
 mblnr TYPE mkpf-mblnr,
 END OF it_msg.
DATA : W_DATA LIKE LINE OF IT_DATA.
DATA : W_CHAR LIKE LINE OF IT_CHAR.
DATA: T_EXCELFILE TYPE ALSMEX_TABLINE OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS : <L_FS> .
DATA : W_INTERN LIKE LINE OF INTERN,
 W_INTERN1 LIKE LINE OF IT_INTERN,
 W_DATA_TAB LIKE LINE OF DATA_TAB.
DATA: TIND(4) TYPE N.
DATA: ZWFELD(19),ZWFELD1(19).
FIELD-SYMBOLS: <FS1>,<FS2>.
DATA : G_MODE(1),G_UPDATE(1).
DATA : G_FLG(1).
DATA : TOT_REC(6) TYPE N,
 DUP_REC(6) TYPE N,
 UPL_REC(6) TYPE N.
 DATA: WA_DATA LIKE LINE OF IT_DATA,
 WA_DATA1 LIKE WA_DATA.
 DATA:WA_HEADER LIKE BAPI_INCINV_CREATE_HEADER,
 WA_INVOICEDOCNUMBER TYPE BAPI_INCINV_FLD-INV_DOC_NO,
 IT_ITEM LIKE BAPI_INCINV_CREATE_ITEM OCCURS 0 WITH HEADER LINE,
 IT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA:BEGIN OF IT_MBLNR OCCURS 0,
 MBLNR LIKE MKPF-MBLNR,
 MJAHR LIKE MKPF-MJAHR,
 END OF IT_MBLNR.
*& Selection screen
SELECTION-SCREEN BEGIN OF BLOCK BLK WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN END OF BLOCK BLK.
*& AT SELECTION-SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
PERFORM GET_FILE.
*& Start of selection
START-OF-SELECTION.
PERFORM GET_BDC_DATA.
PERFORM PROCESS_BDC_DATA.
PERFORM BDC_UPLOAD.
PERFORM display_log.
*& Form GET_FILE
FORM GET_FILE .
*F4-HELP FILE
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
FIELD_NAME = ' '
 IMPORTING
 FILE_NAME = P_FILE.
ENDFORM. " GET_FILE
FORM GET_BDC_DATA .
DATA : WRK_FLG(1).
DATA : GIDX LIKE SY-TABIX.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = '1'
 I_BEGIN_ROW = '1'
 I_END_COL = '250'
 I_END_ROW = '50000'
 TABLES
 INTERN = INTERN
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 WRITE:/ 'Upload Error ', SY-SUBRC.
ELSE.
 SORT INTERN BY ROW COL.
 LOOP AT INTERN.
 TIND = INTERN-COL.
 CONCATENATE 'DATA_TAB-VALUE_' TIND INTO ZWFELD.
 ASSIGN (ZWFELD) TO <FS1>.
 <FS1> = INTERN-VALUE.
 AT END OF ROW.
 APPEND DATA_TAB.
 CLEAR:IT_CHAR,DATA_TAB.
 ENDAT.
 ENDLOOP.
ENDIF.
ENDFORM. " GET_BDC_DATA
*& Form PROCESS_BDC_DATA
FORM PROCESS_BDC_DATA .
DATA : WRK_IND(6) TYPE N.
DATA : WRK_ROW TYPE I,
 GIDX LIKE SY-TABIX.
IF NOT DATA_TAB[] IS INITIAL.
 LOOP AT DATA_TAB INTO W_DATA_TAB.
 WRK_ROW = SY-TABIX.
 IT_DATA-DOC_TYPE = W_DATA_TAB-VALUE_0001.
 IT_DATA-DOC_DATE = W_DATA_TAB-VALUE_0002.
 IT_DATA-PSTNG_DATE = W_DATA_TAB-VALUE_0003.
 it_data-ref_doc_no = w_data_tab-value_0004.
 IT_DATA-GROSS_AMOUNT = W_DATA_TAB-VALUE_0004.
 IT_DATA-BLINE_DATE = W_DATA_TAB-VALUE_0005.
 IT_DATA-HEADER_TXT = W_DATA_TAB-VALUE_0006.
 IT_DATA-INVOICE_DOC_ITEM = W_DATA_TAB-VALUE_0007.
 IT_DATA-PO_NUMBER = W_DATA_TAB-VALUE_0008.
 IT_DATA-PO_ITEM = W_DATA_TAB-VALUE_0009.
 IT_DATA-TAX_CODE = W_DATA_TAB-VALUE_0010.
 IT_DATA-ITEM_AMOUNT = W_DATA_TAB-VALUE_0011.
 IT_DATA-SHEET_NO = W_DATA_TAB-VALUE_0012.
 IT_DATA-ITEM_TEXT = W_DATA_TAB-VALUE_0013.
 IT_DATA-SHEET_ITEM = W_DATA_TAB-VALUE_0014.
 APPEND IT_DATA.
 ENDLOOP.
ENDIF.
ENDFORM.
FORM BDC_UPLOAD.
DATA:LW_DATE(10).
DELETE ADJACENT DUPLICATES FROM it_data.
LOOP AT IT_DATA INTO WA_DATA1.
WA_DATA = WA_DATA1.
While program finds the header record, post the previous entries
if WA_data-DOC_TYPE NE ' '
 AND wa_data-doc_date NE ' '
 AND wa_data-pstng_date NE ' '
 AND WA_data-REF_DOC_NO NE ' '
 AND WA_data-BLINE_DATE NE ' '
 AND WA_data-HEADER_TXT NE ' ' .
 WA_HEADER-INVOICE_IND = 'X'.
 WA_HEADER-COMP_CODE = 'TSKY'.
 WA_HEADER-CURRENCY = 'INR'.
 WA_HEADER-CALC_TAX_IND = 'X'.
 IF sy-tabix NE 1.
update
 PERFORM f0301_exe_bapi TABLES it_item USING wa_header.
 REFRESH it_item.
 CLEAR: it_item, wa_header.
 ENDIF.
*CONCATENATE WA_DATA-PSTNG_DATE+4(4)
 WA_DATA-PSTNG_DATE+2(2)
 WA_DATA-PSTNG_DATE+0(2) INTO LW_DATE.
 WA_HEADER-DOC_DATE = LW_DATE.
 WA_HEADER-PSTNG_DATE = LW_DATE.
 wa_header-doc_type = wa_data-doc_type.
 wa_header-doc_date = WA_DATA-DOC_DATE.
 wa_header-pstng_date = WA_DATA-PSTNG_DATE.
 WA_HEADER-REF_DOC_NO = WA_DATA-REF_DOC_NO.
 WA_HEADER-BLINE_DATE = WA_DATA-BLINE_DATE.
 WA_HEADER-HEADER_TXT = WA_DATA-HEADER_TXT.
 ENDIF.
 IT_item-INVOICE_DOC_ITEM = WA_DATA-INVOICE_DOC_ITEM.
 IT_item-PO_NUMBER = WA_DATA-PO_NUMBER.
 IT_item-PO_ITEM = WA_DATA-PO_ITEM.
 IT_item-TAX_CODE = WA_DATA-TAX_CODE.
 IT_item-ITEM_AMOUNT = WA_DATA-ITEM_AMOUNT.
 IT_item-SHEET_NO = WA_DATA-SHEET_NO.
 IT_item-ITEM_TEXT = WA_DATA-ITEM_TEXT.
 IT_item-SHEET_ITEM = WA_DATA-SHEET_ITEM.
 APPEND it_item.
 CLEAR it_item.
ENDLOOP.
PERFORM f0301_exe_bapi TABLES it_item USING wa_header.
ENDFORM. " f0200_UPDATE
 FORM f0301_exe_bapi TABLES p_it_item STRUCTURE it_item
 USING p_wa_header.
 CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
 EXPORTING
 headerdata = wa_header
 ADDRESSDATA =
 IMPORTING
 INVOICEDOCNUMBER = WA_INVOICEDOCNUMBER
 FISCALYEAR = lc_gjahr
 tables
 itemdata = it_item
 ACCOUNTINGDATA =
 GLACCOUNTDATA =
 MATERIALDATA =
 TAXDATA =
 WITHTAXDATA =
 VENDORITEMSPLITDATA =
 return = it_return.
 READ TABLE it_return INDEX 1.
READ TABLE it_item INDEX 1.
IF it_return-type EQ 'E'.
 MOVE it_item-po_number TO it_msg-po_number.
 move it_item-po_item to it_msg-po_itm.
 MOVE 'Discrepancy in PO' TO it_msg-message.
 MOVE it_return-message to it_msg-message1.
 APPEND it_msg.
 CLEAR it_msg.
 clear it_return.
ELSE.
 MOVE it_item-po_number TO it_msg-po_number.
 move it_item-po_item to it_msg-po_item.
 MOVE 'Successfully parked' TO it_msg-message.
 MOVE WA_INVOICEDOCNUMBER TO it_msg-mblnr.
 APPEND it_msg.
 CLEAR: it_msg, WA_INVOICEDOCNUMBER.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
ENDFORM. "f0301_exe_bapi
FORM display_log .
Display the log
WRITE : '10 Po_number', 25 'Message', 55 'Error message' ,135 'ParkedDocumentNumber'.
ULINE.
LOOP AT it_msg.
 WRITE : /10 it_msg-po_number,
 25 it_msg-message,
 55 it_msg-message1,
 135 it_msg-mblnr.
 ULINE.
ENDLOOP.
ENDFORM. " display_log

hi,
my prblm is in this program i used bapi function module for upload excel data.
bapi_incominginvoice_park.
in my output park number showing increasing for each item.
so i need parknumber it should be same for all items.
i am sending my code pls check this.
*& Report ZBAPI_MIRO
&& Developed By : ESWAR
*& Created Date : 29.10.2007
*& Requested By : GANESH(MM)
*& SAP Area : MM
*& Output : Excel format,Using BDC for Tcode MIRO
REPORT ZBAPI_MIRO.
DATA: BEGIN OF INTERN OCCURS 0.
 INCLUDE STRUCTURE ALSMEX_TABLINE.
DATA: END OF INTERN.
DATA : IT_INTERN LIKE INTERN OCCURS 0 WITH HEADER LINE.
No of columns
DATA: BEGIN OF DATA_TAB OCCURS 0,
 VALUE_0001(10), "DOC.TYPE
 VALUE_0002(10), "DOC DATE
 VALUE_0003(10), " PSTNG.DATE
 VALUE_0003(10), " GROSS_AMNT
 VALUE_0004(10), " REF_DOC_NO
 VALUE_0005(10), "BLINE_DATE
 VALUE_0006(10), "HEADER_TXT
 VALUE_0007(10), "INVOICE_DOC_ITEM
 VALUE_0008(10), "PO_NUMBER
 VALUE_0009(10), " PO_ITEM
 VALUE_0010(10), "TAX_CODE
 VALUE_0011(11), "ITEM_AMOUNT
 VALUE_0012(10), "SHEET_NO
 VALUE_0013(10), "ITEM_TEXT
 VALUE_0014(10), "SHEET_ITEM
 END OF DATA_TAB.
DATA : BEGIN OF IT_DATA OCCURS 0,
 invoice_ind like BAPI_INCINV_CREATE_HEADER-invoice_ind,
 doc_type like BAPI_INCINV_CREATE_HEADER-doc_type,
 doc_date like BAPI_INCINV_CREATE_HEADER-doc_date,
 pstng_date like BAPI_INCINV_CREATE_HEADER-pstng_date,
 comp_code like BAPI_INCINV_CREATE_HEADER-comp_code,
 currency like BAPI_INCINV_CREATE_HEADER-currency,
 gross_amount like BAPI_INCINV_CREATE_HEADER-gross_amount,
 calc_tax_ind like BAPI_INCINV_CREATE_HEADER-calc_tax_ind,
 REF_DOC_NO LIKE BAPI_INCINV_CREATE_HEADER-REF_DOC_NO,
 bline_date like BAPI_INCINV_CREATE_HEADER-bline_date,
 header_txt like BAPI_INCINV_CREATE_HEADER-header_txt,
 invoice_doc_item like BAPI_INCINV_CREATE_ITEM-invoice_doc_item,
 po_number like BAPI_INCINV_CREATE_ITEM-po_number,
 po_item like BAPI_INCINV_CREATE_ITEM-po_item,
 tax_code like BAPI_INCINV_CREATE_ITEM-tax_code,
 item_amount like BAPI_INCINV_CREATE_ITEM-ITEM_AMOUNT,
 sheet_no like BAPI_INCINV_CREATE_ITEM-sheet_no,
 item_text like BAPI_INCINV_CREATE_ITEM-item_text,
 sheet_item like BAPI_INCINV_CREATE_ITEM-sheet_item,
 END OF IT_DATA.
 DATA : BEGIN OF IT_CHAR OCCURS 0,
 IND(6) TYPE N, ""Index for comparison
 CHARN LIKE RCTMS-MNAME, "CHAR NAME
 CHARV LIKE RCTMS-MWERT, "CHAR VALUE
 END OF IT_CHAR.
 DATA: BEGIN OF it_msg OCCURS 0,
 po_number LIKE BAPI_INCINV_CREATE_ITEM-po_number,
 po_item like BAPI_INCINV_CREATE_ITEM-po_item,
 message(20),
 message1(90),
 mblnr TYPE mkpf-mblnr,
 END OF it_msg.
DATA : W_DATA LIKE LINE OF IT_DATA.
DATA : W_CHAR LIKE LINE OF IT_CHAR.
DATA: T_EXCELFILE TYPE ALSMEX_TABLINE OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS : <L_FS> .
DATA : W_INTERN LIKE LINE OF INTERN,
 W_INTERN1 LIKE LINE OF IT_INTERN,
 W_DATA_TAB LIKE LINE OF DATA_TAB.
DATA: TIND(4) TYPE N.
DATA: ZWFELD(19),ZWFELD1(19).
FIELD-SYMBOLS: <FS1>,<FS2>.
DATA : G_MODE(1),G_UPDATE(1).
DATA : G_FLG(1).
DATA : TOT_REC(6) TYPE N,
 DUP_REC(6) TYPE N,
 UPL_REC(6) TYPE N.
 DATA: WA_DATA LIKE LINE OF IT_DATA,
 WA_DATA1 LIKE WA_DATA.
 DATA:WA_HEADER LIKE BAPI_INCINV_CREATE_HEADER,
 WA_INVOICEDOCNUMBER TYPE BAPI_INCINV_FLD-INV_DOC_NO,
 IT_ITEM LIKE BAPI_INCINV_CREATE_ITEM OCCURS 0 WITH HEADER LINE,
 IT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA:BEGIN OF IT_MBLNR OCCURS 0,
 MBLNR LIKE MKPF-MBLNR,
 MJAHR LIKE MKPF-MJAHR,
 END OF IT_MBLNR.
*& Selection screen
SELECTION-SCREEN BEGIN OF BLOCK BLK WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN END OF BLOCK BLK.
*& AT SELECTION-SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
PERFORM GET_FILE.
*& Start of selection
START-OF-SELECTION.
PERFORM GET_BDC_DATA.
PERFORM PROCESS_BDC_DATA.
PERFORM BDC_UPLOAD.
PERFORM display_log.
*& Form GET_FILE
FORM GET_FILE .
*F4-HELP FILE
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
FIELD_NAME = ' '
 IMPORTING
 FILE_NAME = P_FILE.
ENDFORM. " GET_FILE
FORM GET_BDC_DATA .
DATA : WRK_FLG(1).
DATA : GIDX LIKE SY-TABIX.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = '1'
 I_BEGIN_ROW = '1'
 I_END_COL = '250'
 I_END_ROW = '50000'
 TABLES
 INTERN = INTERN
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 WRITE:/ 'Upload Error ', SY-SUBRC.
ELSE.
 SORT INTERN BY ROW COL.
 LOOP AT INTERN.
 TIND = INTERN-COL.
 CONCATENATE 'DATA_TAB-VALUE_' TIND INTO ZWFELD.
 ASSIGN (ZWFELD) TO <FS1>.
 <FS1> = INTERN-VALUE.
 AT END OF ROW.
 APPEND DATA_TAB.
 CLEAR:IT_CHAR,DATA_TAB.
 ENDAT.
 ENDLOOP.
ENDIF.
ENDFORM. " GET_BDC_DATA
*& Form PROCESS_BDC_DATA
FORM PROCESS_BDC_DATA .
DATA : WRK_IND(6) TYPE N.
DATA : WRK_ROW TYPE I,
 GIDX LIKE SY-TABIX.
IF NOT DATA_TAB[] IS INITIAL.
 LOOP AT DATA_TAB INTO W_DATA_TAB.
 WRK_ROW = SY-TABIX.
 IT_DATA-DOC_TYPE = W_DATA_TAB-VALUE_0001.
 IT_DATA-DOC_DATE = W_DATA_TAB-VALUE_0002.
 IT_DATA-PSTNG_DATE = W_DATA_TAB-VALUE_0003.
 it_data-ref_doc_no = w_data_tab-value_0004.
 IT_DATA-GROSS_AMOUNT = W_DATA_TAB-VALUE_0004.
 IT_DATA-BLINE_DATE = W_DATA_TAB-VALUE_0005.
 IT_DATA-HEADER_TXT = W_DATA_TAB-VALUE_0006.
 IT_DATA-INVOICE_DOC_ITEM = W_DATA_TAB-VALUE_0007.
 IT_DATA-PO_NUMBER = W_DATA_TAB-VALUE_0008.
 IT_DATA-PO_ITEM = W_DATA_TAB-VALUE_0009.
 IT_DATA-TAX_CODE = W_DATA_TAB-VALUE_0010.
 IT_DATA-ITEM_AMOUNT = W_DATA_TAB-VALUE_0011.
 IT_DATA-SHEET_NO = W_DATA_TAB-VALUE_0012.
 IT_DATA-ITEM_TEXT = W_DATA_TAB-VALUE_0013.
 IT_DATA-SHEET_ITEM = W_DATA_TAB-VALUE_0014.
 APPEND IT_DATA.
 ENDLOOP.
ENDIF.
ENDFORM.
FORM BDC_UPLOAD.
DATA:LW_DATE(10).
DELETE ADJACENT DUPLICATES FROM it_data.
LOOP AT IT_DATA INTO WA_DATA1.
WA_DATA = WA_DATA1.
While program finds the header record, post the previous entries
if WA_data-DOC_TYPE NE ' '
 AND wa_data-doc_date NE ' '
 AND wa_data-pstng_date NE ' '
 AND WA_data-REF_DOC_NO NE ' '
 AND WA_data-BLINE_DATE NE ' '
 AND WA_data-HEADER_TXT NE ' ' .
 WA_HEADER-INVOICE_IND = 'X'.
 WA_HEADER-COMP_CODE = 'TSKY'.
 WA_HEADER-CURRENCY = 'INR'.
 WA_HEADER-CALC_TAX_IND = 'X'.
 IF sy-tabix NE 1.
update
 PERFORM f0301_exe_bapi TABLES it_item USING wa_header.
 REFRESH it_item.
 CLEAR: it_item, wa_header.
 ENDIF.
*CONCATENATE WA_DATA-PSTNG_DATE+4(4)
 WA_DATA-PSTNG_DATE+2(2)
 WA_DATA-PSTNG_DATE+0(2) INTO LW_DATE.
 WA_HEADER-DOC_DATE = LW_DATE.
 WA_HEADER-PSTNG_DATE = LW_DATE.
 wa_header-doc_type = wa_data-doc_type.
 wa_header-doc_date = WA_DATA-DOC_DATE.
 wa_header-pstng_date = WA_DATA-PSTNG_DATE.
 WA_HEADER-REF_DOC_NO = WA_DATA-REF_DOC_NO.
 WA_HEADER-BLINE_DATE = WA_DATA-BLINE_DATE.
 WA_HEADER-HEADER_TXT = WA_DATA-HEADER_TXT.
 ENDIF.
 IT_item-INVOICE_DOC_ITEM = WA_DATA-INVOICE_DOC_ITEM.
 IT_item-PO_NUMBER = WA_DATA-PO_NUMBER.
 IT_item-PO_ITEM = WA_DATA-PO_ITEM.
 IT_item-TAX_CODE = WA_DATA-TAX_CODE.
 IT_item-ITEM_AMOUNT = WA_DATA-ITEM_AMOUNT.
 IT_item-SHEET_NO = WA_DATA-SHEET_NO.
 IT_item-ITEM_TEXT = WA_DATA-ITEM_TEXT.
 IT_item-SHEET_ITEM = WA_DATA-SHEET_ITEM.
 APPEND it_item.
 CLEAR it_item.
ENDLOOP.
PERFORM f0301_exe_bapi TABLES it_item USING wa_header.
ENDFORM. " f0200_UPDATE
 FORM f0301_exe_bapi TABLES p_it_item STRUCTURE it_item
 USING p_wa_header.
 CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
 EXPORTING
 headerdata = wa_header
 ADDRESSDATA =
 IMPORTING
 INVOICEDOCNUMBER = WA_INVOICEDOCNUMBER
 FISCALYEAR = lc_gjahr
 tables
 itemdata = it_item
 ACCOUNTINGDATA =
 GLACCOUNTDATA =
 MATERIALDATA =
 TAXDATA =
 WITHTAXDATA =
 VENDORITEMSPLITDATA =
 return = it_return.
 READ TABLE it_return INDEX 1.
READ TABLE it_item INDEX 1.
IF it_return-type EQ 'E'.
 MOVE it_item-po_number TO it_msg-po_number.
 move it_item-po_item to it_msg-po_itm.
 MOVE 'Discrepancy in PO' TO it_msg-message.
 MOVE it_return-message to it_msg-message1.
 APPEND it_msg.
 CLEAR it_msg.
 clear it_return.
ELSE.
 MOVE it_item-po_number TO it_msg-po_number.
 move it_item-po_item to it_msg-po_item.
 MOVE 'Successfully parked' TO it_msg-message.
 MOVE WA_INVOICEDOCNUMBER TO it_msg-mblnr.
 APPEND it_msg.
 CLEAR: it_msg, WA_INVOICEDOCNUMBER.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
ENDFORM. "f0301_exe_bapi
FORM display_log .
Display the log
WRITE : '10 Po_number', 25 'Message', 55 'Error message' ,135 'ParkedDocumentNumber'.
ULINE.
LOOP AT it_msg.
 WRITE : /10 it_msg-po_number,
 25 it_msg-message,
 55 it_msg-message1,
 135 it_msg-mblnr.
 ULINE.
ENDLOOP.
ENDFORM. " display_log

Confirmation Creation not possible - Document is in Transfer for PO.

Hi Gurus,
Scenario :Extended classic
Server :SRM_SERVER 550 -SAPKIBKT05
We are not able to create subsiquent Confirmations for a PO, as the entries in table BBP_DOCUMENT_TAB, is not being cleaned by CLEAN_REQREQ_UP, even after the IDOC has been posted successfully in the back end.
the IM ( Conformation) entries are
not being cleaned by the CLEAN_REQREQ_UP batch job which is running succesfully.
I went though the OSS available and there are some old notes which talks of this issue. OSS 171113, 187802..but no soution recommended.
I also came across this note 644963 which talks of a report to delete the IM entries in BBP_DOCUMENT_TAB (Report :ZZ_CLEAN_BBP_DOCUMENT_TAB).
But this report has not be provided by SAP in patch level SRM_SERVER 550 -SAPKIBKT05
Has any one resolved this issue..please help us out.
Please note that deleting the (IM) entry related to this PO from table BBP
DOCUMENTTAB, solves the problem.
Best Regards
Prashanth

Hi Ramakrishna,
Thanks for the responce.
Running CLEAN_REQREQ_UP manually and resetting the job solved the problem.
The report that I mentioned is in a related note of 644963
Best Regards
Prashanth

Item in Transfer - classic scenario!!

Hi experts,
I am in SRM server 5.0 using the classic scenario. In a particular case a Shopping cart has been approved but not transferred to the backend system. There were no alerts in RZ20,ST22 & SM21 when checked at that time.
I have also analyzed and found that there is a table entry in the table BBP_DOCUMENT_TAB for the corresponding Shopping Cart and a PO number has been generated.In the details of that entry I find that the object GUID is 00000.
The checkbox is marked as X while the X flag field is blank.
So, under normal circumstance I understand that if entry exist in this table chk whether PO number exits in REF Object no.Then in SE38 run clean REQREQ up and input the logical system name and SC No. and execute. I had run the same but still the status of the Shopping Cart remains Item in Transfer Process.
I even tried to resubmit the SC by using function module BP_PD_SC_RESUBMIT and in the field OBJECTKEY, I put the backend object ID I got from table BBP_PDBEI (PO ID) which should retry to create the backend doc, and then create an entry in BBP_DOCUMENT_TAB, ready for CLEAN_REQREQ_UP.
But even after that the status remained same.
Now atlast I have got an alert in BBP_PD for the SC which states that the
" Shopping Cart ( value of PO ID ) does not exist "
Can anyone guide me as to why this occured and how can I transfer the PO to the backend system ?
Looking forward for your expert Comments and solution..
Thanks in Advance,
Rajesh Rajendran

Hi Marcin,
Sorry for the delay!!! Thanks for the info but i checked up and found that the number range interval has been maintained in the SRM server when i checked through - transaction SPRO -> SRM -> Cross-Application Basic Settings -> Number Ranges - Define Number Rang. per backend System for Follow-on Docs.
But for the backsystem when i went into transaction SPRO->Cross Application Components - > General Application Functions ->Cross Application Document Numbering -> Maintain Number ranges.. when i executed the same I got an error pop up stating " For the object J_1AOFFDOC no sub-object was defined ".
What does this mean ? This should not be the case else all the Classic PO's would not go to backend ..
Can you clarify ?
Thanks & Regards,
Rajesh Rajendran

Diff between programme BBP_GET_STATUS_2 & CLEAN_REQREQ_UP in SRM7.0

Hi Experts ,
We have ECC6.04 with SRM 7.0 with Classic Scenarion
I am confused over exactly what BBP_GET_STATUS_2 do in SRM ?
I believe CLEAN_REQREQ_UP update the SC with follow on document i..e Classic PO....
and BBP_GET_STATUS_2 update the entries in BBP_DOCUMENT_TAB..but not getting exactly what is does..since if we change qty in Classic Po ..it automatically updates automatically in SC follow on document...if we Craete GR in ECC it updates automatically in SC follow on document...
Can anyone please suggest me exactly what BBP_GET_STATUS_2 do in SRM ( what is exact diff between both )?
Thanks
NAP

Hello,
Report : BBP_GET_STATUS_2
Function : This reports updates the requirement coverage requests (Shopping carts) to ensure that information on the status of backedn purchase requisitions, purchase orders, and reservations is up-to-date.
You should schedule this report to run daily in the SRM server system.
Report : CLEAN_REQREQ_UP
Function : Interval for update check.
Updating of documents (purchase requisitions, purchase orders, reservations) is executed asynchronously in the backend system. You can only process the requirement coverage request in the SRM server system further after the update has been carried out. At the interval defined by you in Customizing, the system checks whether the documents have been updated and thus if you can further process the requirement coverage request.You should schedule this report periodically.
Hope this helps.
Best Regards,
Rahul

Purchase Order from EBP was not created

Hi people,
I have a problem with an approved shopping cart that must generate a Purchase Order in R3.
But:
- The order was not generated in R3
- I have an entry in bbp_document_tab table in EBP system
- When I check the status of the Shopping Cart in transaction BBP_PD I can see the item in "Item in Transfer Process" status.
- When I check the Application Monitor in EBP system, there is no messages related to this Shopping Cart.
- The report CLEAN_REQREQ_UP is schedule to run every 25 minutes and after it runs, the entry in bbp_document_tab remains there.
- I checked the dumps in R3 system using transaction ST22 but I could not find entries (I have searched using the RFC user).
What else I can check? If I have an error when BAPI_PO_CREATE1 is called, where it is logged?
Thank you!

Hi
You need to take help of ABAP resource here.
Using the same data what you are passing in the shopping cart, directly create a purchase order both
1) using ME21N transaction directly and
2) then using 'BAPI_PO_CREATE1' bapi using a custom program in this case.
3) Incase you are using ECS, then implement BBP_CREATE_PO_BACK BADI and put a break-point there and then you can easily figure out, what's the problem happening as soon as BAPI - 'BAPI_PO_CREATE1' is called from SRM system using RFC call there.
Do let me know your findings.
Regards
- Atul

Document in transfer for purchase order - creation not possible

Hi Experts,
we get this error when we do confirmation"'document in transfer for purchase order - creation not possible'"
any inputs are appreciated
Rg
sam

Hi All,
We have resolved the above problem.
When user does confirmation ,if it sucessfully created then there will be no entry in BBP_Document_tab table.If it's in error in process and next time when user tries to do GR then he will encounter a pop up message "Document in transfer for PO, creation not possible".
So we need to delete the entries from table BBP_DOCUMENT_TAB using FM BBP_DELETE_FROM_DOCUMENT_TAB.
Then check again in BBP_DOCUMENT_TAB now there will be noentry there...so now user can do the confirmation from SRM,he will not encounter this error now.
Thanks to all the ppl who has replied
sameer

How to clear status "Error in process"?

Hi All,
I need help to clear the status of my invoice in SRM. The invoice status is "error in process". We checked in backend and reprocessed the IDOC through WE19 instead of BD87 and the invoices are posted now in backend. But the status of the invoices still shows "error in process" in SRM. I do understand that we should not use WE19 and should have processed it through BD87.
I checked in SRM and the enteries exists in BBP_DOCUMENT_TAB table for these invoices, just tried to run CLEAN_REQREQ_UP and BBP_GET_STATUS_2 but no help.
Please help
Thanks, Sachin

please read all below
An IDoc BBPIV is sent if an invoice is released in the BBP system.In the invoice the statuses I1022 "Release granted" and I1017 "In transfer" are set.In addition, for the background job (see below) an entry is written to table BBP_DOCUMENT_TAB.
Unless I1017 is not set again to inactive, all previous operations are not allowed (in particular all changes to the invoice), that is, they are stopped by the program. The sending of the IDOC is checked by the background job CLEAN_REQREQ_UP. The report reads the BBP_DOCUMENT_TAB and makes a RFC (remote function call) per META_GOODSMVT_UPDATECHECK to check the posting of inbound IDocs.If the IDoc is posted successfully (status 53), the BBP invoice receives status I1018 "Transferred to backend".In addition, the entry is deleted in BBP_DOCUMENT_TAB.
If the IDoc is posted incorrectly (status 51, no follow-on document), the status of the invoice is set to I1019 "Transfer failed".The entry in BBP_DOCUMENT_TAB remains as is, that is, the status of the IDOCs in the backend system is still checked by the background job.The sending of the IDOC is checked by the background job CLEAN_REQREQ_UP.If the IDoc has not (yet) arrived in the backend system, the entry also remains as is.
Status I1018 allows to reverse the invoice in the future. In case of status I1019, a deletion is (again) possible.
The following must be considered when processing an incorrect IDoc in the backend system:
a) Further process the same IDoc (BD87), instead of copying and correct the IDoc with Transaction WE19 since in the latter case, the background job cannot find the (copied) IDoc and the invoice posted from that. In this case the BBP invoice would remain endlessly in status "incorrect", the entry in BBP_DOCUMENT_TAB would never be deleted and the background job would always make the RFC at every run.In addition the BBP invoice would never receive the status "paid" (see below).
b) If the IDoc cannot be corrected or the error in the backend system cannot be solved, the IDoc remains in status "incorrect".In this case the BBP invoice should be deleted and the entry in BBP_DOCUMENT_TAB should be deleted manually or with a self-written report.
Additional information: As of EBP Release 4.0 or after the implementation of Note 601470 or the import of the relevant Support Package, the entry in BBP_DOCUMENT_TAB is deleted by the program (during the deletion of the invoice). Then the manual deletion is no longer required.
The following section does not correspondingly apply to the confirmation, but only applies to the invoice.
Status I1020 "paid" is set in the invoice by using the second background job BBP_IV_UPDATE_PAYMENT_STATUS to check the payment status of the follow-on invoice in the FI backend system for all invoices from the selection area.This only occurs for BBP invoices with status I1018 "Transfer to backend". To read the FI documents, META_FI_DOCUMENT_READ_40B is used.

Distribution of GOA to the backend system

Dear Experts,
I am working in Extended classic scenario (SRM 5.0). We are planing to configure GOA.
Can any one give me the steps required to configure GOA and distribute the contracts to the back end system.
When I create the GOA as of now GOA is getting created but not distributed.
Regards,
B.N.Karthikeyan

Hi,
Here are the main configuration steps needed:
1: Make sure you have done the following in customizing:
   When you go to define transaction type and you
   choose the entry with BUS2000113, then you click Transaction type
   go to DETAIL screen of GCTR and choose Global Outline
   agreement as a specification.
2: You can follow these steps.
   1. Go to the transaction WEDI
   2. Goto IDoc menu and select Partner Profile (or F6)
   3. In Partner Profile, Goto PartnerType LS
   4. Click on the client eg. ABCCLNT300
   5. In "Inbound parmtrs" make an entry for BLAORD.Enter the client as
   Partner number. BLAO as Process Code.
3: In the R3 backend system,
   maintain BLAORD as inbound message type, and maintain
   BLAREL as outbound message type
4: One of the requirements for setting up GOA is:
   Mapping of the appropriate products,product categories, condition
   types, document IDs, transaction types and text iDs in the BAdis:
   *IN EBP > BBP_CTR_BE_CREATE
IN the backend system: BBP_CTR
Any GOA contract in EBP has to be mapped in R/3 with the corresponding
entry for conditions i.e 01CT to synchronise the two systems.
If the conditions are not mapped, the idocs will not be created.
Hence, please map the conditions and check for the distribution.
It is also an option to try:
Please run the function module 'BBP_PD_CTR_TRANSFER', this FM posts the
IDOC in R/3 and add an entry in BBP_DOCUMENT_TAB,
afterwards call report 'CLEAN_REQREQ_UP' which updates the status.
Kindly ensure all customizing and settings are correct in both SRM and
R/3 backend in order for the GOA to pass from systems without issues.
I hope this helps,
Kind Regards,
Lisa

Urgent ! Purchase Requisition not created in Backend Classic Scenario

Hello All,
I am implementing the classic scenario SRM 5.5. We have replicated the material form the backend to SRM system. Also we have made the necessary config such as maintain backend system, Define Backend System for Product Category, Define Number Ranges for Shopping Carts and Follow-on Document, Define Number Ranges per Backend System for Follow-on Document. Now the problem i am facing is that in the dev system SC with line item with desc and the product (material replicated from backend) as line items are created and their PR is created in the backend. However the same is not happening in the QA system. Only those SC with line item as Desc/text only are created in the backend and those having have product id dont transfer to create PR in the backend. There is no message in the RZ20, SM13, ST22, SM21 etc. Alsowhen i try to tranfer it using the FM BBP_PD_SC_TRANSFER it is created successfully and there is entry in BBP_DOCUMENT_TAB which is cleared afetr clean_reqreq_up is run. I am not sure whats is going wrong. Please help me out guys.
Thanks
Karthik

Hi Andy,
Thanks for the quick responses. I dont see any PR doc no and neither the BUS object type in BBP_PD item details. Please see the o/p below
BE_LOG_SYSTEM                R3QAS400
BE_OBJ_ITEM
BE_OBJECT_TYPE
BE_OBJECT_ID
BE_REFOBJ_TYPE
BE_REFOBJ
BE_REFOBJ_ITEM
BE_REFOBJ_SBITM
BE_REFOBJ_TYPE2
BE_REFOBJ2
BE_REFOBJ_ITEM2
BE_REFOBJ_FYEAR2             0000
BE_STGE_LOC
BE_PLANT                     IE01
BE_BATCH
BE_VAL_TYPE
BE_MOVE_REAS                 0000
BE_EXPERYDATE                000000
BE_PUR_GROUP                 440
BE_PUR_ORG                   IE01
BE_CO_CODE                   IE01
BE_DOC_TYPE                  EC
BE_ACCREQUIRED
BE_SP_STK_IND
BE_INFO_REC
BE_MOVE_TYPE                 101, so i am not sure what could be going wrong.
Is there any way i can debug it and find out what the cause is,
though the calls to the bapis are asynchronous. Also just for the reference sake my backend is 46C. I have been grazing through the notes but haven't found a substantial one.

SRM Shopping Cart Error

Hi All,
Can any one explain about the error "Please buy (PR Number) to exist" which is not allowing to create follow-on documents although PR and PO are created in backend. We are following the Classic scenario.
Edited by: praveen sridhar on Jul 18, 2008 7:15 AM

Hello Praveen,
Please proceed by this way
With transaction BBP_PD in SRM(GUI) enter the SC no. as the object id, navigate to each SC item detail in backend item data, table BBP_PDBEI, you will find the reference to the object type & ID that SRM tried to create in R/3: tell me what's there
check if the corresponding document exists in R/3
if yes, then you have to re-create manually the corresponding entry in BBP_DOCUMENT_TAB, to let the job CLEAN_REQREQ_UP finalize the process (look how other entries are populated, or look at note 532213)
If not, then you must retransfer the SC: use BBP_PD_SC_RESUBMIT, but in the field OBJECTKEY, you will put the backend object ID you got from table BBP_PDBEI (PO or PR ID). This will retry to create the backend doc, and then create an entry in BBP_DOCUMENT_TAB, ready for CLEAN_REQREQ_UP.
Rgrds,
Raj
Please do reward points if the information is helpful

Entries in BBP_DOCUMENT_TAB, doc_type = IM

Similar Messages

Maybe you are looking for