ABAP, NetWeaver, ERP Tutorial » UI

How to hide SAP standard button in standard transaction

Andy — Thu, 02 Feb 2012 06:30:52 +0000

Business user might need to hide some buttons in SAP standard transaction code because they don’t want there functions to be abused. We assume there function couldn’t be controlled by authorization objects. SAP provides transaction variant to change SAP standard UI.

Transaction variants can simplify transaction runs as they allow you to:

Preassign values to fields

Hide and change the 'ready for input' status of fields

Hide and change table control column attributes

Hide menu functions

Hide entire screens

In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.

Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.

For example, if we need to hide button ‘Reject document’ in tcode VA02. Below are the detail steps.

SAP ALV Overview

Andy — Wed, 09 Nov 2011 13:38:04 +0000

ALV is the abbreviation of SAP List View which is an UI element for displaying tabular data. ALV provides a rich set of functionalities like sorting, filtering, aggregation, exporting, persistence of custom settings. History of SAP ALV ALV is formerly known as ABAP List Viewer. From basis 4.0, ALV is available for SAP internal usage based on ABAP list processor technology.

SAP NWBC – ECC CRM Integration

Andy — Mon, 15 Aug 2011 06:27:10 +0000

In some cases, the client wants to integrate some individual WebClient UI components with ECC transactions into NWBC. This integration is for the users who mainly use ECC transactions and only needs a few WebClient UI applications. For example, You use Financial Accounting in SAP ERP and, in addition, you wish to use account details of SAP Customer Relationship Management (SAP CRM). SAP still recommends the users who work primarily with WebClient UI applications to use standalone WebClient UI. Below are the steps to set up this scenario for NWBC. System Landscape There is a CRM system and a ECC system. The NWBC will logon the ECC system to access all the required transaction, Web Dynpro applications, WebClient UI components and other applications.

Web Dynpro ABAP – Portal Navigation

Andy — Mon, 07 Feb 2011 07:17:07 +0000

In some SAP portal implementation projects, SAP standard transactions are integrated into portal using ITS – a first generation of web technology developed by SAP. Because the main UI technology used in ECC is Dynpro, ITS plays an important part in presenting these transactions in the internet environment. Below diagram shows the SAP current UI strategy in ABAP and Java.

Define Field Selection for WBS

Andy — Fri, 21 Jan 2011 09:21:37 +0000

When implementing the project system, the WBS detail screen always need to be adapted to fulfill customer’s special requirements. SAP provides a special function named Field Selection to support in changing the screen field attributes.

Overview

The function Field selection allows you to change the attributes of screen fields dynamically at runtime.Field selection distinguishes between influencing fields and modified fields. At runtime, a function module analyzes the field contents of the influencing fields and then sets the attributes of the modified fields accordingly.

SAP Transaction Classification

Andy — Wed, 29 Dec 2010 05:36:21 +0000

When defining the SAP transaction, there is an option allows you to choose the transaction classification.

SAPGUI Error – ERROR:Service ‘?’ unknown

Andy — Tue, 02 Feb 2010 07:30:07 +0000

Sometimes when I try to login to the SAP system, the GUI pop up the error message “Error: Service ‘?’ unknown”. I confused by this error message but don’t know how to fix this. I got some time today and fortunately found the route of the problem.

SAP Screen Sequence Control

Andy — Tue, 26 Jan 2010 07:43:16 +0000

Transaction Code: VFBS. Function Module: SCREEN_SEQUENCE_CONTROL Function: SCREEN_SEQUENCE_CONTROL Function group: V00F Summary Determination of the next screen from the function code

Dynpro programming – seach help

Andy — Thu, 21 Jan 2010 15:36:46 +0000

If you develop the custom screen, you always need to deal with the search help. Some search help comes from the DDIC definition. In some case the search help value comes from program dynamically. Below code example shows how you can populate search help. In the screen flow logic:

Reason of using OK_CODE

Andy — Mon, 18 Jan 2010 16:12:47 +0000

In the ABAP dynpro programming, we always deals with OK_CODE which contains the function code user triggers. For each screen, there is a default UI element with type OK. The element is used to pass function code to the program for further processing.