To make the field for Display only on the Shopping Cart Portal

[Former Member]

Hi All,

We need to make one field on the Shopping cart portal screen as Uneditable.It should be for the display purpose only.

Can you please suggest how it can be done.

Thanks & Rgds,

Sanjeet

[Former Member · Accepted solution]

Hi,

You can use BBP_UI_CONTROL_BADI to control the editability of a field.

Regards,

Prasanna

[Former Member · Accepted solution]

Hi Prasanna,

Thanks 4 ur response.

This BADI is not getting triggered.

Also the field is not getting grayed.

Any idea?

Rgds,

Sanjeet

[Former Member]

In addition to the very useful points made in this thread, I'm looking for a way to restrict the "Invoice Only" option depending on the product category selected. Do you know I would do this?

For example only allow "Invoice Only" to be selected if Product Category X is selected. If product category Y is selected then grey-out "Invoice Only".

Matt

[Former Member]

Hi. This is a bit trickier. If you can not get the BBP_UI_CONTROL_BADI to do what you want then just use the BBP_DOC_CHECK_BADI to check what the user has entered and issue an error message if they choose something you do not want them to.

Regards,

Dave.

[Former Member]

Thanks Dave very helpful!

[Former Member]

Hi. I normally make fields dislpay only in SRM using a transaction variant in SHD0, then set it as the standard for the transaction, so all users get it.

The ITS and portal normally pick it up without you having to change any other settings.

It is a bit messy setting up the variant in the GUI first but it is easier than changing the ITS template or using a BADI.

Regards,

Dave.

[Former Member]

Hi Dave,

Can you please explain how can I make the fields only for display using the Transaction variant in SHD0.

Thanks & Rgds,

Sanjeet

[Former Member]

Hi.

1 - Go to SHD0 in the GUI and make sure you are on the "Transaction Variants" tab.

2 - Enter the transaction code you want to change, probably BBPSC01 or BBPSC02. If you want to do both that is fine, just do 1 for now, then you can very quickly copy it later. You might also want to blank it out in check shopping cart status transaction and so on, you can copy it there quickly too, we'll get to that later.

3 - Enter a name for your variant in the "Transaction Variant" field, ZBBPSC01 for example.

4 - Press enter. SRM 5 seems a bit odd if you do not press enter, you sometimes get an error for no reason, there may be a note for this or something.

5 - Press the "create" button. You will now be taken into the transaction.

6 - This is the tricky part. Go through the transaction as you would do normally. The screen is not nice in the GUI, you will need to work out which section to go to and so on.

Each time you press enter or click on a button a screen will pop up showing you all the data you have entered on the various screens and subscreens.

Look through all the pop up screens. If you do not see the field you want on that pop up then the best thing to do is remove the "copy settings" tick box.

When you get to the field you want to make display only, tick the "output only" option next to it and press "exit and save".

7 - You will be taken to a screen where you can review the settings you have made. Just make sure you have ticked the right field as "display only" and then save.

8 - Select a package and a transport.

9 - You should now be back at the SHD0 main screen. Go to the "Standard Variants" tab.

10 - Make sure your new variant name is entered in the "name" box and press the "Activate" button.

11 - Your variant should now be active. Log on via the portal and make sure it works. If it does not make sure you ticked the right field in step 6. Some of them are a bit tricky to find and several have similar names. You can just press the change button in SHD0 to check what is ticked and so on, you do not have to go all through the transaction again.

12 - You are finished, but if you want to make sure the field is display only everywhere, you might have to copy the variant to other transaction codes. Just press the "copy" button and you can move your variant from one transaction code to another. Most of the screens are shared between all the BBPSC0* transactions, so should work.

Regards,

Dave.

[Former Member]

Hi Dave,

I have created the Transaction variant ZBBPSC02 and one screen variant called ZBBPSC02_0120 for field CUST1 on the screen 120.

What should be the next step ? Where these transaction variant and screen variant have to be used and how?

Thanks & Rgds,

Sanjeet

[Former Member]

Hi. Just follow the instructions from step 9.

Regards,

Dave.

[Former Member]

Hi,

BUS2121 is not included in the documentation but there exists a method for SC i.e. BBP_SC_UI_CTRL (as per SRM 5.0)

There are 2 workarounds;

1.Implement BADI "BBP_DOC_CHECK_BADI" to raise an error whenever the field is edited .

2.Modify the corresponding HTML template in the ITS service BBPSC01 in SE80 for the reqd field.But the ITS chnages will be oevrwritten in case of upgrade.

BR,

Disha.

Do reward points fro useful answers.