Why is it possible to delete SC that have a PO as Follow on Document?
in SRM 7.0 CS, i am trying to understand the system behaviour w.r.t. to the deletion of shopping cart items, that already have R/3 follow on documents against itself.
We start with a free text item in the shopping cart. After its approval in SRM, the request becomes a Purchase Requisition in the R/3 system. As long as it is only the purchase requisition, that is the follow on document, the shopping cart can be deleted (the purchase requisition in R/3 is updated with a deletion flag in that case).
But as soon as a Purchase Order has been created in the R/3 system for that requirement, the deletion of the SRM shopping cart is no longer possible. In the shopping cart a message is there saying that the shopping cart item can not be deleted because a Purchase Order already exists.
I can understand and agree to this system behaviour.
We order a catalogue item via the EBP shopping cart. After its approval in SRM, the request become a Purchase Order in the R/3 system.
But it is still possible to delete the shopping cart item and thus also the PO as the follow on document in the R/3 system.
Why doesn´t the SRM system behave in the same way for shopping carts, whos follow on Purchase Orders has been created manually by the Buyer (scenario 1) or has been created automatically by the R/3 system (scenario 2)?
Thank you very much.
Ricardo Cavedini replied
As per standard design, it is possible to delete a shopping cart if only
one follow-on document exists. For example, a purchase order or a
When you delete the shopping cart in EBP, the deletion indicator will
be set in the purchase order.
You cannot delete the shopping cart if the follow-on document has other
follow-on documents, like confirmation or invoice.
The following is the standard behaviour for SC/limit SC deletion:
SC -> PO : deletion possible
SC -> PReq: deletion possible
SC -> PReq + PO: deletion NOT possible
SC -> PO + CF: deletion NOT possible
SC -> PReq + PO + CF: deletion NOT possible
SC -> PO + CF + INV: deletion NOT possible
SC -> PReq + PO + CF + INV: deletion NOT possible
Standard logic: in general SC does not prevent the deletion of SC items
just because of existence of follow-on documents.
The SC item itself does not know if the deletion is possible.
It just tries to delete the corresponding item of follow-on document.
If this deletion has been successful, then also the SC item can
and will be deleted. If the deletion of follow-on document item has
failed, the SC item deletion is not possible.
So it is a task of follow-on document to know if its items can be
deleted or not.