on 09-10-2010 10:22 AM
Hello Everybody,
I am very new to SRM and am currently having a doubt over a scenario that is existing in our SRM4.0 platform but not in our SRM7.0 platform.
In SRM4.0 - We are creating a Shopping Cart with suppose 2 items. We are forwarding that Shopping Cart to SOCO where we
are creating a Purchase Order for both the line items. From the Purchase Order, we are deleting one line item. That deleted line
item is again reappearing in SOCO for reprocessing. Is this standard in SRM4.0 or should I search for any custom
enhancements done in our SRM4.0 system which is making this deleted line reappear in SOCO? This scenario is not taking place
in our SRM7.0 system. The deleted line from the PO is not appearing again in SOCO.
Please let me know whether this is SRM4.0 standard behavior or not.
<< Please do not offer points.>>
Thanks in advance,
Debanjan
Edited by: Rob Burbank on Sep 10, 2010 4:58 PM
as Lisa said
Deleted shopping cart will venture cockpit again
due to get status job logic.
if deleted PO did not venture cockpit means
two reasons
1. limit PO - item category B or frame work doc type PO
2. PO deleted immediately in backend befor clean job runs.
see bbp_pd
you might see transfer
logical system and etc.
riule:- PO should delete after your clean job run
before run clean job , delete PO this sc never come to cockpit since links are not happened .
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Debanjan,
The behaviour has not changed regarding the deletion of an item in a PO, this should then reappear in SOCO to be resourced. The only reason why this would not be happening is if the item is a Limit item then it will NOT reappear. This is standard behaviour.
If it is a normal item then the following notes should resolve this issue for you:
For the connected R/3 system:
Backend 4.70: 1123548, 1251224, 1305603, 1320044, 1398792
Backend 5.00: 1123548, 1251224, 1305603, 1320044, 1398792
Backend ECC 2005 ( SAP_APPL 600): 1123548, 1141690, 1251224, 1320044,
1322328, 1398792
There are also some notes for the SRM system. Just search for notes for the report 'BBP_GET_STATUS_2'. That reports sets the sourcing indicator and is probably the cause of this issue.
I hope this helps,
Kind Regards
Lisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.