Copy transaction BBPSC01
We want to have some fields available or not depending of a zfield for our SC. Moreover our zfield value must be the same and not changeable for all lines in a SC.
The idea is to determinate the process flow and rules from the fist moment. So a possibility can be to create several transactions as copy BBPSC01 transaction.
So the user decides the transaction and the process flow.
u2022 SC type A will be process by a purchaser. (Transaction ZBBPSC01A)
u2022 SC type B will be processed automatically as PO. So the vendor must be mandatory. (Transaction ZBBPSC01B)
All lines must be A or B, because all lines make reference to the same purchasing process. And not all users are authorized for all transactions.
We created the new transactions (SE93), we created the new service (SICF), we created the internet services (SE80) and we published, and finally we created a new role with our new transaction (PFCG).
Now when we run the new transaction in web access, the system shows us a pop up with the next message :u201D Error in system; shopping cart cannot be processed furtheru201D
Is it a good idea to create new transactions?
Thanks and regards.
Prasanna Rangaraju replied
This problem seems to come from function module BBP_SC_UI_SCENARIO_GET. Here based on SY-TCODE the scenario is exported.
If you see this FM, all standard SY-TCODEs are hard-coded. As yours is a custom Z-tcode it fails to find the scenario.
One way is to do an implicit enhancement to this FM at the end of this function module and send back the scenario. Atleast you can first verify by putting an external break-point in this function and manually change the EV_SC_SCENARIO while debugging to verify this.