Hide a standard field

[Former Member]

Hello all,

I need to know: is there a way to hide a field in SRM web portal? For example, I know, in SAP ECC there is 'Field Status'; in SAP SRM.

Thanks,

Best Regards,

Maria

[Former Member · Accepted solution]

Hi,

There are 2 ways in SRM to hide the std fields:

1.Implement the BADI "BBP_UI_CONTROL_BADI".

2.If the specific fields cannot be hidden using the above BADI,you may sometimes need to do the modifications in the ITS templates through trascn SE80(not recommended as changes are overwritten in case of upgarde).

BR,

Disha.

Do reward points for useful answers.

[Former Member · Accepted solution]

Hi Disha,

thanks very much...I don't know very well SRM System. Can you make me an example in order to hide a field? For example, if I wold hide, in Procurement Catalogue, the "search" field or the "Compare" button:

1) which transactiona must I use? SE19?

2) How can I obtain the result to hide the field? Valuing which fields?

Thanks, BR,

Maria

[Former Member · Accepted solution]

Hi Maria,

Adding to what Disha has suggested, please find the following suggestions which will help in resolving your issue.

You can use SE18 txn to activate the BADI. You can check whether the BADI is implemented or not by clicking on Implementation and overview in the menu bar.

Otherwise you can create the implementation name and can activate that instead of activating the standard BADI.

Define filters under Attributes tab and define the object type for which the BADI needs to be activated.

Hope this makes you more clear.

Award points for hgelpful answers.

Rgds,

Teja

[Former Member · Accepted solution]

Hi,

As I told you the BADI "BBP_UI_CONTROL_BADI" can be used only in some trasnsactions to hide the std fields/links etc.

Pls read the documentation of the BADi:

Field Control in Purchasing Document

Use

Using the Business Add-In BBP_UI_CONTROL_BADI, you can change the visibility and the ready-to-input status of interface objects (for example, fields and pushbuttons) in a document.

You can use the BAdI to override the following documents and applications:

Purchase contract and global outline agreement

(Filter value BUS2000113)

Bid invitation (Filter value BUS2200)

Bid (Filterwert BUS2202)

Auction (Filter value BUS2208)

Purchase order (Filter value BUS2201)

Purchaser's Sourcing application

Confirmation (Filter value BUS2203)

Invoice (Filter value BUS2205)

Vendor list

Note

Changing the ready-to-input status of fields as designated in the standard can lead to errors. You should, therefore, avoid switching the status of a field that is not ready-to-input in the standard to ready-to-input. Do not, for example, set the object ID of an already existing contract to changeable.

Standard settings

Using the following methods of the BAdI, you can control the visibility and ready-to-input status of header and item fields, pushbuttons, and navigation links of the concerned applications and also interface objects of cross-application screens, for example, the partner overview, account assignment, status overview or approval:

BBP_CTR_UI_CTRL

for field control in the contract and in the global outline agreement

BBP_BID_UI_CTRL

for field control in the bid invitation

BBP_QUOT_UI_CTRL

for field control in the bid

BBP_AUC_UI_CTRL

for field control in the auction

BBP_PO_UI_CTRL

for field control in purchase orders, including the screens for purchase order response and price data in the item details.

BBP_AVL_UI_CTRL

for field control in the vendor list.

Using the following methods, you can override the visibility and ready-to-input status of header and item fields, pushbuttons, and navigation links of the relevant application, however not that of interface objects of cross-application screens:

BBP_SOCO_UI_CTRL

for field control in the purchaser's Sourcing application

BBP_CONF_UI_CTRL

for field control in the confirmation

BBP_INV_UI_CTRL

for field control in the invoice

Using the following method, you can set up the mass change transaction in such a way that the previous step need not be completed before the user switches to the next screen.

BBP_CTR_MASS_UI_CTRL

for control of the mass change transaction.

Other then the transactions mentioned above,you need to modify the Std ITS templates(in tcode SE80) to hide the required fields/buttons.For this you first need to find the corresponding ITS service and HTML template for the screen in which you want to remove the button/links from.

E.g.,This is the sample code for Bid invitation screen fields:

*To make the TYPE OF PUBLICATION field under BASIC DATA tab in BI screen as display only

IF iv_fieldname = 'BBPS_BID_UI_HEADER-BID_TYPE'.

cv_input_ready = c_space.

ENDIF.

HTH.

Similarly,You can debug at runtime and see the structures and names for the fields/buttons as per the CATALOGUE screen.

BR,

Disha.

P.S. DO reward points for useful answers.