Follow on document details not updating in shopping cart

Hi Experts,
I created a shopping cart and created PO as a follow on document from sourcing cockpit after assigning vendor.
but Shopping cart is not updating with follow on document (PO)details even after running BBP_GET_STATUS_2 report also.
Is there any other settings required to do for updating shopping cart with follow on document details.
Thanks,
Bhaskar.

Hi ,
Please check the repots ( jobs ) CLEAN_REQREQ_UP And BBP_GET_STATUS _2 are running..
Check in RZ20 is there any error message for the follow on document.
Thanks
prasad.s

Similar Messages

SC Item in Transfer process active - follow on document status not updated

Hi Gurus,
    Follow on document is not updated in SRM after PO creation. Ours is classic scenario (SRM 5.5, ECC6.0) and passed thru the following steps - SC (FFT) created, document approved, sent to SoCo, purchaser assigned vendor and created PO, PO created in ECC.
In SRM SoCo screen displays message 'PO created 45xxxxxxxxxx' successfully. Checked the BE PO 45xxxxxxx that was created successfully.
Ran BBP_GET_STATUS_2 and CLEAN_REQREQ_UP jobs. jobs finished successfully. But status is not updated in SRM. RZ20/SLG1 does not have any errors.
BBP_PD shows following statuses:
     I105   Awaiting Approval         X
     I1021 Created
     I1038 Complete
     I1106 SC ordered
     I1129 Approved
     I1111 Item in Transfer process
                    The last status I1111 is still active.
Any advise are welcome. Not sure if I am missing any OSS Notes.
Regards
Viktor Paul

Hi,
1. Check in table BBP_DOCUMENT_TAB if the entry exists use CLEAN_REQREQ_UP program.
2. If entry in the table not exists then check in transaction BBP_PD if the follow on document ( PO ) Number reserved for
the SC .. then use FM BBP_PD_SC_RESUBMIT.
3. none of these use normal process execute BBP_REQREQ_TRANSFER And then use CLEAN_REQREQ_UP
Thanks,
prasad.s

Follow on Document details not correct

Hello Experts,
We are in SRM 4.0 Classic
One Shopping Cart has been created with 1Goods and 7 Service line items....
PR has been created in backend...... (we see generally SC line item 1,2,3.... follow sequece 10,20,30 in PR, But here this order is shuffled.... though all the SC and PR line item details are correct)
Now for SC line item 2, 'follow on document' tab shows details of PR line item 40 and vice versa.... which is incorrect....
Except these two SC line items, all other SC items shows correct PR line item details in follow on document
Can anyone advise on such system behaviour? Is thr any way to fix this?
Thanks,
Dhananjay

Hi,
Did you delete some line items and again added them in your SC? Are you using cost distribution in your SC?
Regards,
Nikhil

Item in Transfer Process - Follow on documents status not displayed

Hello experts,
User created a shopping cart of 12 line items (out of that no 3rd is deleted) and PO is created in backend r/3 system.
Now when i see the status of my last item ie 12th line item is "Item in Transfer Process". and for 3rd item which is deleted for that also Status shown PO NO (I1113) i can see that PO no is there when i check follow on document.Problem is i want to change the status of 12th line item with its respective PO no .
Activity done by me to solve
If i manually update the status in the table CRM_JEST then the status will get changed but the follow on document is not displayed evenafter run reports like CLEAN_REQREQ_UP and Get status2. i am trying to run a report BBP_ALERT_SB_NOTTRANSFERED but it got cancelled. even i tried to run a function module BBP_PD_SC_RESUBMIT but short dump will come. i have implemeted a suggested SAP note 729967 but still problem persist.
In BBP_PD and in table BBP_PDBEI field ( BE_OBJECT_ID ) in this field Ponumber is there against that line item.
Thanks
Sunny Sharma

Hi Sunny,
the manual action taken on the transfer is dangerous and can cause even more inconsistency.
Hence you may have changed some tables of the SC manually, I would suggest rather to delete SC items, and create a new SC for them.
Regards,
Peter

Follow-on documents are not visible in MIRO in TEST server, awsys = PRD300.

Dear Experts ,
The Test Server was refreshed around mid-June 2011 with data of
Production Server. The follow-on documents are not visible for the
invoice documents in MIRO in TEST server due to value in tables
BKPF,RBKP : field : AWSYS = PRD300 .
The newly created Purchase Orders after the refresh, the accounting
documents can be seen for the Goods Receipt (MIGO_GR-display) and
Invoice documents (MIRO).
we had already raised this issue in March & got the feedback from SAP
as shown below.
accordingly we have developed & run the program "zzlogsys2" which
updates the Logsys/Awsys field from PRD300 ( of production server ) to
that of the current server i.e. TST300 as required.
after which the FI documents for the material documents are visible in
MIGO,but follow-on documents are not visible for the invoice documents
in MIRO.
we have Checked notes 781498 and 28958 to see if the logical system is
correctly assigned , where we found that in table RBKP after entering document number, Fiscal Year , the
Field AWSYS is "PRD300" & not "TST300" as it should be. We will take up the activity of updating table RBKP
also as we are currently doing for tables MKPF & BKPF.
But to have clear picture as to what we are doing is correct , pl
advise about the following :
1) Is it a correct process done by our SAP-Basis team , that every time
any Server ( e.g. Test or Quality ) is refreshed with Production server
data, the Field AWSYS in various transaction tables gets value as
"PRD300" which then is required to replaced by running program such as
ZZlogsys.
REPORT ZZLOGSYS.
TABLES: T000, MKPF.
DATA: NEW_SYS LIKE MKPF-AWSYS.
PARAMETER: OLD_SYS LIKE MKPF-AWSYS.
SELECT SINGLE * FROM T000 WHERE MANDT EQ SY-MANDT.
NEW_SYS = T000-LOGSYS.
CHECK NOT NEW_SYS IS INITIAL.
UPDATE MKPF SET AWSYS = NEW_SYS
WHERE AWSYS = OLD_SYS.
WRITE:/ 'Number of updates: ', SY-DBCNT.
2) if the above process is correct & normal , then which are the other
tables in a particular server ,apart from tables MKPF,BKPF,RBKP , which
needs to be updated the value of field "AWSYS" in the same way
replacing value "PRD300".
3) if the process in point no. 1 is not correct , then what is the
correct process that the Basis team can do while refreshing any target
server with production data so that target server retains its value in
Field AWSYS & not showing "PRD300".
With 3 servers TEST,DEV & Quality , recently refreshed with production
server to bring all servers in Sync for a HR patch application, we have
this situation now in all 3 servers .
Thanks in advance ,
Anil Shanbhag

It is appropriate to move this thread from ERP-MM to [Enterprise Resource Planning (ERP)|Enterprise Resource Planning (SAP ERP);
Edited by: Jeyakanthan A on Jul 7, 2011 4:56 PM

Cannot update delivery attributes: the following field(s) are not updatable

Hi. I create in EBS simple Order
Now , my goal is to create a delivery , pick , change shipping quantity and ship confirm. Here is my code
DECLARE
p_sales_order NUMBER := 10014445;
p_line_number NUMBER := 1.1;
p_org_id NUMBER := 308;
l_shipped_quantity NUMBER := 5;
p_api_version_number NUMBER := 1.0;
init_msg_list VARCHAR2(200);
l_commit VARCHAR2(30);
x_msg_details VARCHAR2(3000);
x_msg_summary VARCHAR2(3000);
x_return_status VARCHAR2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(3000);
p_validation_level NUMBER;
v_errbuf VARCHAR2(2000);
v_retcode VARCHAR2(20);
v_released_status wsh_delivery_details.released_status%TYPE;
v_inv_interfaced_flag wsh_delivery_details.inv_interfaced_flag%TYPE;
v_oe_interfaced_flag wsh_delivery_details.oe_interfaced_flag%TYPE;
v_source_code wsh_delivery_details.source_code%TYPE;
v_pending_interface_flag wsh_trip_stops.pending_interface_flag%TYPE;
l_changed_attributes wsh_delivery_details_pub.changedattributetabtype;
l_source_code VARCHAR2(30) := 'OE';
-- Parameters for WSH_DELIVERIES_PUB
p_delivery_name VARCHAR2(30);
p_action_code VARCHAR2(15);
p_asg_trip_id NUMBER;
p_asg_trip_name VARCHAR2(30);
p_asg_pickup_stop_id NUMBER;
p_asg_pickup_loc_id NUMBER;
p_asg_pickup_loc_code VARCHAR2(30);
p_asg_pickup_arr_date DATE;
p_asg_pickup_dep_date DATE;
p_asg_dropoff_stop_id NUMBER;
p_asg_dropoff_loc_id NUMBER;
p_asg_dropoff_loc_code VARCHAR2(30);
p_asg_dropoff_arr_date DATE;
p_asg_dropoff_dep_date DATE;
p_sc_action_flag VARCHAR2(10);
p_sc_intransit_flag VARCHAR2(10);
p_sc_close_trip_flag VARCHAR2(10);
p_sc_create_bol_flag VARCHAR2(10);
p_sc_stage_del_flag VARCHAR2(10);
p_sc_trip_ship_method VARCHAR2(30);
p_sc_actual_dep_date VARCHAR2(30);
p_sc_report_set_id NUMBER;
p_sc_report_set_name VARCHAR2(60);
p_sc_defer_interface_flag VARCHAR2(60);
p_sc_send_945_flag VARCHAR2(60);
p_sc_rule_id NUMBER;
p_sc_rule_name VARCHAR2(60);
p_wv_override_flag VARCHAR2(10);
p_asg_pickup_stop_seq NUMBER;
p_asg_dropoff_stop_seq NUMBER;
x_trip_id VARCHAR2(30);
x_trip_name VARCHAR2(30);
fail_api EXCEPTION;
x_debug_file VARCHAR2(100);
l_ship_method_code VARCHAR2(100);
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
CURSOR c_ord_details IS
SELECT DISTINCT det.source_header_number sales_order,
det.org_id,
det.source_line_number,
det.source_header_id,
det.source_line_id,
det.source_header_type_name,
det.inventory_item_id,
det.requested_quantity,
det.delivery_detail_id,
(SELECT concatenated_segments
FROM mtl_system_items_kfv
WHERE inventory_item_id = det.inventory_item_id
AND organization_id = det.organization_id) ordered_item,
det.organization_id,
det.src_requested_quantity,
det.shipped_quantity,
del.delivery_id,
del.status_code delivery_status_code,
det.released_status pick_release_status,
det.oe_interfaced_flag,
det.inv_interfaced_flag
FROM wsh_delivery_details det,
wsh_delivery_assignments asn,
wsh_new_deliveries del
WHERE 1 = 1
AND det.delivery_detail_id = asn.delivery_detail_id
AND asn.delivery_id = del.delivery_id(+)
AND det.source_header_number = 1199656
AND det.source_line_number = '1.1'
AND det.org_id = 10102
AND shipped_quantity IS NULL
AND NVL(del.status_code, 'OP') <> 'CL'
and det.delivery_detail_id =21439836
/* AND det.released_status = 'Y'*/;
BEGIN
-- Initializing the Applications
SELECT user_id INTO l_user_id FROM fnd_user WHERE user_name = 'MSHAPIRA';
SELECT responsibility_id, application_id
INTO l_resp_id, l_appl_id
FROM fnd_responsibility_vl
WHERE responsibility_name = 'OM Super User - UDS UK';
fnd_global.apps_initialize(l_user_id, l_resp_id, l_appl_id);
FOR i IN c_ord_details LOOP
DBMS_OUTPUT.put_line('Initializing the Application for Shipping Transactions');
-- Mandatory initialization for R12
mo_global.set_policy_context('S', i.org_id);
mo_global.init;
-- Ship Confirming
p_delivery_name := TO_CHAR(i.delivery_id);
DBMS_OUTPUT.put_line('Before Shipping, Calling WSH_DELIVERY_DETAILS_PUB API to Update Shipping Attributes');
DBMS_OUTPUT.put_line('=============================================');
l_changed_attributes(1).delivery_detail_id := i.delivery_detail_id;
l_changed_attributes(1).shipped_quantity := 5;
wsh_delivery_details_pub.update_shipping_attributes(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
p_commit => l_commit,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_changed_attributes => l_changed_attributes,
p_source_code => l_source_code);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
RAISE fail_api;
DBMS_OUTPUT.put_line('Failed to Update the Shipping Attributes');
ELSE
DBMS_OUTPUT.put_line('Successfully Updated the Shipping Attributes');
END IF;
BEGIN
SELECT shipping_method_code
INTO l_ship_method_code
FROM oe_order_headers_all
WHERE order_number = i.sales_order
AND org_id = i.org_id;
EXCEPTION
WHEN OTHERS THEN
l_ship_method_code := NULL;
END;
p_action_code := 'CONFIRM'; -- The action code for ship confirm
p_sc_action_flag := 'S'; -- Ship entered quantity.
p_sc_intransit_flag := 'Y';
--In transit flag is set to 'Y' closes the pickup stop and sets the delivery in transit.
p_sc_close_trip_flag := 'Y'; -- Close the trip after ship confirm
p_sc_trip_ship_method := l_ship_method_code; -- The ship method code
p_sc_defer_interface_flag := 'Y';
p_sc_stage_del_flag := 'Y';
p_sc_create_bol_flag := 'N';
p_wv_override_flag := 'N';
-- API Call for Ship Confirmation
DBMS_OUTPUT.put_line('Calling WSH_DELIVERIES_PUB to Perform Ship Confirmation');
DBMS_OUTPUT.put_line('=============================================');
wsh_deliveries_pub.delivery_action(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_action_code => p_action_code,
p_delivery_id => i.delivery_id,
p_delivery_name => p_delivery_name,
p_asg_trip_id => p_asg_trip_id,
p_asg_trip_name => p_asg_trip_name,
p_asg_pickup_stop_id => p_asg_pickup_stop_id,
p_asg_pickup_loc_id => p_asg_pickup_loc_id,
p_asg_pickup_stop_seq => p_asg_pickup_stop_seq,
p_asg_pickup_loc_code => p_asg_pickup_loc_code,
p_asg_pickup_arr_date => p_asg_pickup_arr_date,
p_asg_pickup_dep_date => p_asg_pickup_dep_date,
p_asg_dropoff_stop_id => p_asg_dropoff_stop_id,
p_asg_dropoff_loc_id => p_asg_dropoff_loc_id,
p_asg_dropoff_stop_seq => p_asg_dropoff_stop_seq,
p_asg_dropoff_loc_code => p_asg_dropoff_loc_code,
p_asg_dropoff_arr_date => p_asg_dropoff_arr_date,
p_asg_dropoff_dep_date => p_asg_dropoff_dep_date,
p_sc_action_flag => p_sc_action_flag,
p_sc_intransit_flag => p_sc_intransit_flag,
p_sc_close_trip_flag => p_sc_close_trip_flag,
p_sc_create_bol_flag => p_sc_create_bol_flag,
p_sc_stage_del_flag => p_sc_stage_del_flag,
p_sc_trip_ship_method => p_sc_trip_ship_method,
p_sc_actual_dep_date => p_sc_actual_dep_date,
p_sc_report_set_id => p_sc_report_set_id,
p_sc_report_set_name => p_sc_report_set_name,
p_sc_defer_interface_flag => p_sc_defer_interface_flag,
p_sc_send_945_flag => p_sc_send_945_flag,
p_sc_rule_id => p_sc_rule_id,
p_sc_rule_name => p_sc_rule_name,
p_wv_override_flag => p_wv_override_flag,
x_trip_id => x_trip_id,
x_trip_name => x_trip_name);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
DBMS_OUTPUT.put_line('Ship confirm has not been Completed For SO => ');
ROLLBACK;
RAISE fail_api;
ELSE
DBMS_OUTPUT.put_line('Ship confirm Successfully Completed For SO => ');
COMMIT;
DBMS_OUTPUT.put_line('Checking the Delivery Status after delivery action API Call');
DBMS_OUTPUT.put_line('==========================================');
SELECT wdd.source_code,
wdd.released_status,
wdd.inv_interfaced_flag,
wdd.oe_interfaced_flag,
wts.pending_interface_flag
INTO v_source_code,
v_released_status,
v_inv_interfaced_flag,
v_oe_interfaced_flag,
v_pending_interface_flag
FROM wsh_trips wtr,
wsh_trip_stops wts,
wsh_delivery_legs wlg,
wsh_new_deliveries wnd,
wsh_delivery_assignments wda,
wsh_delivery_details wdd
WHERE wtr.trip_id = wts.trip_id
AND wts.stop_id = wlg.pick_up_stop_id
AND wts.pending_interface_flag = 'Y'
AND wdd.inv_interfaced_flag <> 'Y'
AND wlg.delivery_id = wnd.delivery_id
AND wnd.delivery_id = wda.delivery_id
AND wda.delivery_detail_id = wdd.delivery_detail_id
AND wnd.delivery_id = p_delivery_name
AND wdd.source_line_id = i.source_line_id;
IF (v_source_code = 'OE' AND v_released_status = 'C' AND
v_inv_interfaced_flag <> 'Y' AND v_oe_interfaced_flag <> 'Y' AND
v_pending_interface_flag = 'Y') THEN
DBMS_OUTPUT.put_line('The Delivery has been Shipped & the Next Step is - Run Interface');
DBMS_OUTPUT.put_line('===========================================');
-- API Call for Submitting Interface Trip Stop
wsh_ship_confirm_actions.interface_all_wrp(errbuf => v_errbuf,
retcode => v_retcode,
p_mode => 'ALL',
p_stop_id => NULL,
p_delivery_id => p_delivery_name,
p_log_level => 0,
p_batch_id => NULL,
p_trip_type => NULL,
p_organization_id => i.organization_id,
p_num_requests => 1,
p_stops_per_batch => 1);
ELSE
DBMS_OUTPUT.put_line('The Delivery has not Shipped Properly');
END IF;
END IF;
END LOOP;
EXCEPTION
WHEN fail_api THEN
DBMS_OUTPUT.put_line('==============');
DBMS_OUTPUT.put_line('Error Details If Any');
DBMS_OUTPUT.put_line('==============');
wsh_util_core.get_messages(p_init_msg_list => 'Y',
x_summary => x_msg_summary,
x_details => x_msg_details,
x_count => x_msg_count);
IF x_msg_count > 1 THEN
x_msg_data := x_msg_summary ||' '||x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
ELSE
x_msg_data := x_msg_summary||' '|| x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
END IF;
END;
But at the stage of updating delivery attributes I get the following error message
Warning: For Delivery Detail 21439836, the following field(s) are not updatable: SHIPPED_QUANTITY.
Why?

Hi Paul
Looks like the authorisation is failing due to a bad registration for some reason.
Would you be kind enough to clear out the registration to ensure we are dealing with a fresh start and no information is being used which may have become corrupt. You may do this by following this procedure;
Remove existing reg details
# usr/lib/cc-ccr/bin/eraseCCRRepository
List /tmp/RegistrationProfile.properties file
# cat /tmp/RegistrationProfile.properties
Attempt re-registration
# sconadm register -a -r /tmp/RegistrationProfile.properties
Send us the full output of the commands above if you would please.

Measuring point/document is not updating

Dear all,
I am new in PM. I have one issue over here.Measuring point/document is not updating automatically after production order confirmation via co11n . I tried with following steps
1) Created the equipment as (P)Production resources/tools -->created measuring point as a counter ---> maintain the usage value formula SAPF02 in the PRT tab . Unit of measurement for the characteristics and base unit of measure of material are same
2) Then i have assigned this equipment as a PRT in the routing of material .
3) Production order confirmation via co11n Each unit
Which steps i am missing. if u give me steps by steps procedure to me for counter based maintenance, its helpful for me.
STILL not answered and no reply.
I am waiting for reply.
Thanks
tarun
Edited by: tarun on Oct 5, 2010 5:06 PM

Hello,
Have look this thread [Re: Auto Update of measuring point/document;
Regards,
Rakesh

Unable to proceed in change document are not updating in CDHD, CDPOS tables

Hi all,
This is a question related to Change document.
I created one custom Change document object ZBUDGETS.
As I am trying to place a trigger on FMIT (Total Funds Management) table I created a Change document object ZBUDGETS.
I included some of the authorized fields from FMIT table on which we placed the trigger.
And of course all those fields are change document enabled in the data element level. I generation of the update program was completed. And I got the function module zbudgets_write_document along with some include programs and structure.
Everything is fine, But i am unable to get this change document generated information to these tables are CDHDR and CDPOS.
the problem is when I make any expenditure like PO Posting, it will be logging in the FMIT table and the respective fields also updating. With this the Change document object should trigger and it should send the record in CDHDR and CDPOS tables. This is not happening. If the records are getting updated in the CDHDR and CDPOS tables I can use those include programs and function modules in my program to retrieve the changes in FMIT table.
Since I am unable to proceed further since the documents are not updating in CDHDR and CDPOS tables.
Prabhakar

CDHDR and CDPOS will not be populated with entries only by creating the change document object.Change documents will be written to CDHDR and CDPOS tables only if the function zbudgets_write_document is called in the transaction which updates FMIT.
You need to find an use exit in the transaction updating FMIT and call the function zbudgets_write_document in that exit.
Refer the below link http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa01b6493111d182b70000e829fbfe/content.htm
-Kiran
*Please reward useful answers

Revenue recongnized documents are not updated with trading partners

Hi SAP Gurus
Revenue recongnized documents are not updated with trading partners
Can any body help on this as it is priority issue
Regards,
suchithra

You might try looking/posting here.
Microsoft Support – Office for Mac
Microsoft Support – Office for Mac (2)

When restoring and updating my iPhone I am getting the following message " iTunes could not update to the carrier settings for your iPhone.an unknown error occurred (1630)

When restoring and updating my iPhone I am getting the following message " iTunes could not update to the carrier settings for your iPhone.an unknown error occurred (1630).can anyone please with a knowledge tell me what I should do please. Thank you

The search bar can be very valuable...........
In using it, I found out other's have had this issue and it likely means you have a 3G iPad? If you do, go into settings and turn off cellular data, then try to update again and you should be OK........

Document year not updated at the time of part I Posting

Dear Guys.,
At the time of part I posting the document yaer not updated properly. this is not upodated in some times or some cases only . but it is updating correctly other times...
but i dont know the reason why this document year was not updated.
the field name and table tane is J_1iexchdr- DOCYR.
Excise Transaction type is GRPO.
because of this problem we can not able to do the invoice verification..
REgards
P.Anandhakumar.
Edited by: Anandhakumar Palanisamy on Sep 3, 2009 8:47 AM

Timing
I am not sure what is going on behind the scenes with this web site in the past few days. One day I could not post in your thread at all. Another day
I was receiving Inbox email notifications that were never posted in the Adobe Premiere Elements Forum or were posted several hours after I saw them
in my Inbox email notifications. I was waiting for the problem to disappear on its own. If not, we can post in the Adobe Comments Forum to find out what
might be going on.
https://forums.adobe.com/community/general/forum_comments
Yours has not been the only thread where I have had these problems.
ATR

Approval Preview not displayed in Shopping cart

Hi,
On creating shopping carts through Plan Driven procurement, we are changing the cart status from the default "Ordered/Approved" to "Awaiting approval". The approvers are displayed in BBP_PD for this Shopping Cart, however the same is not visible in SRM portal.
We have also refreshed all the templates, but the Approval tab and Overview link, is not displayed in shopping cart.
We are on SRM 5.0, 5.5 server, Extended Classic scenario with SP 17 and have implemented N-step approval work flow BADI to determine approvers based on the cost center entered in shopping cart.
Kindly provide inputs to have approvers displayed in SRM portal.
Thanks,
KB

Hi,
SAP does not provide the standard solution for triggering the WF from external system ( ECC )... any document create outside the SRM, system will automatically put the status to approved... even 0-Level wont trigger... you can activate the nstep workflow by following step by step help...
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770
Saravanan

Order not allowed before shopping cart take over

Dear All,
After System update, to SAPKIBKV10, when creating a shopping cart, the error message "Order not allowed before shopping cart take over" appears.
THis functionality was never in use and is not activated. How to resolve the issue
Regards

Hi,
Check SAP Note 1499352 - SRM Transfer: Redesign, bug fixes and all relevant side effect notes.
This issue seems to be related to SRM design bug so raise it with SAP on high priority.
Thanks,
Ravi

Cost Centre drop down not working in Shopping Cart

Hi Experts,
Cost Centre drop down is not working in Shopping Cart.
Version: SRM 7.0 SP05
Message - no input help due to errors when checking the display authoriz.
I have checked there are some SAP Notes available for this issue, but it is for SRM 5.0 version
725247 - Search help and BAdI BBP_F4_READ_ON_ENTRY in accnt assgn scr
839534 - Problems with dropdown list in Acc. ***. overview
925890 - Cost centre drop down not working
I have raised OSS Message, Please gothrough the reply from SAP below
Note
656633
815849 top 5
Customizing Recommendations
- Note 656633 desribes pre-requisites for ERP RFC-user using F4-help.
- Assign SRM standard role /SAPSRM/EMPLOYEE during F4-help testing.
- Check RFC-dialog for F4-help destination using SM59.
- ERP F4-help destination must be maintained in IMG table bbp_backend_dest.
- Using PPOMA_BBP dropdown disable BE_F4_HELP authority activity as of note 815849. Multiple values must be maintained in attribute CNT cost center.
- Hint: Mix of ERP F4-help and PPOMA_BBP dropdown is not possible.
Return
a.SRM system ID, client, remote access, logon data buyer who face the problem incl. sap_all
b.ERP RFC-dialog access via SRM, RFC-user incl. display or sap_all
I have followed both the notes, but still problem presists
Please advice.
BR,
Siva

Hi,
This issue has been resloved.
Solution:
Step:1
Assign SRM standard or custom role like /SAPSRM/EMPLOYEE to user; Please make sure multiple values been maintained in attribute CNT cost center in PPOMA_BBP for the user
Step: 2
Disable BE_F4_HELP authority activity for role /SAPSRM/EMPLOYEE in BBP Component > SRM: General Access Authorizations in EBP
Step: 3
Apply SAP Note 668746 - COIN - Switching off OKB9 in EBP scenario in SAP R/3 as per note 815849 Solution 1
System will check during the processing of account assignment objects in an EBP scenario, the backend system reads the default account assignment (Transaction OKB9) as usual if EBP does not provide any account assignment. This note will Switch off OKB9 in EBP scenario and it will list the CNT values from PPOMA in the shopping cart account assignment F4 help.
BR,
Siva

Bugseye catalog does not return a shopping cart occasionally

Dear Experts,
We have a problem where Bugseye catalog items sometimes randomly do not return a shopping cart into the SRM portal side. This happens randomly for any Bugseye items after restarting the browser (IE8 and Firefox 3.6.13). Otherwise the Bugseye catalogs are running fine with an https connection.
After the browser restart, about 1/3 attempts to create a shopping cart from Bugseye catalogs return nothing. Instead the user is brought back to 'Shop in 4 steps' screen without a shopping cart. After the failed attempt a user lock is created (tcode SM12) and the shopping session left open. Once a shopping cart is successfully returned, it does not fail again unless the browser is restarted. The error happens randomly and we haven't been able to figure out any logic behind it. We have verified that the source codes in the Bugseye side, just before continuing to order items, are identical for a successful and non-successful tries. We have also placed breakpoints in function module BBP_WS_IMPORT_SC_DATA, to ensure no errors are issued for the items
Does anyone have any idea what could cause the problem?
We are running SRM7.0 Extended Classic Scenario ( SRM 7.00 SP11). Requisite Bugseye version 4.0.0.25.
Here is an example Standard Call Structure for the catalog:
10                              https://orsrdd01.orion.fi:8001/requisite/BugsEye     0 URL
10     username     xxxx     2 Fixed Value
20     password     xxxx     2 Fixed Value
30     catalog     Catalog2     2 Fixed Value
40     sap-locale     SY-LANGU     1 SAP Field
50     datalanguage     EN     2 Fixed Value
60     BYPASS_OUTB_HANDLER   2 Fixed Value
70     BYPASS_INB_HANDLER                                                                                2 Fixed Value
100     HOOK_URL                                                                                4 Return URL
Looking forward to your expert insights,
Matti Hokkanen

Hi,
Please also append this in the call structure,
5     ~OkCode     ADDI     2 Fixed Value
6     ~target     _top     2 Fixed Value
7     ~caller     CTLG     2 Fixed Value
sometimes the browser cookie and session information will be conflicting with the punchout window. It is better to clear the cookie information and then try once on http.
Thanks,
Prashanth

Follow on document details not updating in shopping cart

Similar Messages

Maybe you are looking for