Skip to Content
avatar image
Former Member

"Deletion Indic. not set in BE"


Does anybody came accross 'Deletion Indic. not set in BE' seletion criterion on BBP_GET_STATUS_2.

Surprsingly, their exists no code in the program which is using this parameter 'be_del' and their are no OSS message for the same.

Any ideas on this one.


Piyush Garg

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Apr 13, 2007 at 09:26 PM

    Hi Piyush,

    It is really surprsing to see that you have a field on selection screen and not used in the program.So far there is no OSS note released by SAP on this object for this field.There are very good number of notes available from SAP on this program but no note is catering this field in selection screen.

    Even there is no F1 Help available on this field.

    If you want explanation from SAP on this,you can raise OSS to them.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Nishant,

      It seems finally I have to raise an OSS message only. But, let's see if anybody else on this forum has something different. Someone might have copied it to 'Z' and would have modified the same to incorporate the logic which SAP forgot to code.



  • avatar image
    Former Member
    Apr 16, 2007 at 01:57 PM


    Which SRM version are you using ?

    We are using SRM 5.5 version. No problems, there is not any code for the field "be_del" as such. We have not faced this problem yet.

    Please provide the detailed process to show how to replicate the steps.

    <u>Meanwhile, Have a look at the following relevant SAP OSS Notes</u>.

    Note 1040917 - BBP_STATUS_READ: Error messages are not deleted
    691569 - Error messages in BBP_GET_STATUS_2
    Note 890319 ActualValues in SC from back-end documents are not deleted
    989891 BBP_GET_STATUS_2: Incorr quantity determination in back end  
    1040847 Requirement is removed from sourcing after BBP_GET_STATUS_2 
    1012124 SHP not reappear in SOCO after backend PO delete 
    1032713 BBP_GET_STATUS_2: incorrect sourcing indicator   
    757625 Incorrect Status I1112->analysis report
    755769 Status I1113, no item or header relations->analysis report 
    994314 PO appears twice in applet preview in limit SHP  
    949162 Follow-on documents exist, status I1111 and I1113 active 
    947198 IMS monitor: Web Dynpro with hierarchies
    922575 BE_REFOBJ and BE_REFOBJ_ITEM filled during Confirmation(SUS) 
    844209 BE_REFOBJ is filled at confirmation
    798044 Correction for object links missing between SC and BE docs 
    776921 Display of deleted purchase orders on history screen 
    723680 Corrections in the mapping of SAP XML messages 
    723594 SRM 4.0 XML confirmation mapping error    
    662411 BBP_GET_STATUS_2: Too many database updates
    651040 No update of shopping cart after reversing goods receipt
    638505 Delete shopping cart item: Status stil active 
    604420 Composite SAP note SRM 3.0 SP1 group 
    626109 Enhancement BBP_PD_SC_REF_GETLIST for local bid invitations 
    619897 EBP 3.0: local SC reporting and SC status
    576555 Perf: BBP_GET_STATUS_2/Confirmatn for only Classic Scenario 
    578033 Item from the shopping cart are deleted in backend 
    573202 'Buffer table not up to date' for APPEND at tables 
    570440 Problems with Delete/Restore of back end documents
    551276 Too many database updates in BBP_GET_STATUS_2 
    498899 Correction instructions for EBP 3.0 in Note 436151 incorrect 
    422697 Change of structure 'BBPS_SC_REFUPDATE' 
    459422 EBP SC Status: Backend PO delete indicator set at random 
    501052 Deleted purchase orders not displayed in the history 
    513034 History for an extended limit purchase order in test status 
    417334 EBP/BBP: Deletion of requisition not displ. when UOM wrong
    426444 BBP_GET_STATUS_2: Dump

    Do let me know.


    - Atul

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      On execution, parameter "BE_DEL" is 'CHECKED', what happens if my requirement is to execute it as "UNCHECKED".

      It's of no use...since there is no code for 'BE_DEL' in the SAP standard problem.