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.
Read more…
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.
Read more…
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.
Read more…
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.
Read more…
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.
Rather than maintaining field selection separately for each screen of a program, you can combine logically associated screens together in a screen group. This reduces the amount of maintenance required. To assign a screen to a screen group, enter the group in the field Screen group on the attributes screen in the Screen Painter.
Read more…
When defining the SAP transaction, there is an option allows you to choose the transaction classification.
Read more…
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.
1. First copy the saplogon.ini file to below folder:
C:WINNT or C:Windows for Windows XP
C:users<user profile>AppDataLocalVirtual StoreWindows for Vista and windows 7. For more information, please check SAP note: 1031740 for detail information.
2. If you open SAP GUI and it pop up above error message immediately, you need to check whether the connection is configured using load-balance way. If yes, please check file named ‘services’ under folder ‘C:WINNTsystem32driversetc’.
You need to maintain the entry like below:
sapmsABC 3600/tcp
The first value is also configured in the saplogon.ini and standards for port used by the message server.
3. It should be working by now. If there are still some errors, it should related to other issues. Please also check file named ‘hosts’ to check whether the IP and the host named are mapped.
Transaction Code:
VFBS – Next screen control.
VOVB – Screen Sequence Group Maintenance.
VOV8 - Document Type Maintenance. You can assign the standard screen sequence group to sales document type in this transaction.
Function Module: SCREEN_SEQUENCE_CONTROL
Function: SCREEN_SEQUENCE_CONTROL
Function group: V00F
Summary
Determination of the next screen from the function code
1. General description
The components contained in the function group V00F serve the determination of the further processing after input of a function code over key or menu. By three tables, those is steered to the definition by functions (T185F) and processing places (T185V), as well as the definition of ways between the places (T185) to be used.
Beyond that the possibility exists of merging the safety dialogues, which are realized in the function group SPO1. The control been made by T185F and T185D, the texts which can be spent are deposit able in T185T, all texts can however also at any time only be handed over at run-time dynamically.
Read more…
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:
process on value-request.
field: viqmel-znp_lob module get_lob.
In the program:
Read more…
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.
But new comer may raise a question: the system field SY-UCOMM also contains the function code that user triggers. Why we still need another field OK_CODE for this purpose.
Read more…