Click here to Download
Tuesday, 19 June 2012
Monday, 18 June 2012
Saturday, 9 June 2012
CHTMLB & THTMLB
CHTMLB---Configurable HTMLB Tags
They are used on the view, in case the view can be changed in the configuration.
i.e they are used to introduce the possibility of configuring UI's in terms of existence and place the UI Elements and fields.
They are based on basic tags but are more complex
THTMLB---Thin HTMLB Tags
They are basic tags and can be used directly
Used for Basic UI Elements like inputs,texts,tables and tress
UI Framework makes use of THTMLB & CHTMLB Tags
These tags ensures a consistent look and feel throughout the application
Note
The WEBCUIF software component includes essentially 3 tag libraries.
THTMLB
CHTMLB
TAJAX(Used for delta Handling Purpose)
They are used on the view, in case the view can be changed in the configuration.
i.e they are used to introduce the possibility of configuring UI's in terms of existence and place the UI Elements and fields.
They are based on basic tags but are more complex
THTMLB---Thin HTMLB Tags
They are basic tags and can be used directly
Used for Basic UI Elements like inputs,texts,tables and tress
UI Framework makes use of THTMLB & CHTMLB Tags
These tags ensures a consistent look and feel throughout the application
Note
The WEBCUIF software component includes essentially 3 tag libraries.
THTMLB
CHTMLB
TAJAX(Used for delta Handling Purpose)
Sunday, 13 May 2012
Value Node & Model Node
Value Nodes are used for display purpose. For example if you have an internal table and want to display that data on UI, you can do it using a Value Node. A Value does not need any BOL reference, just a Data Dictionary Structure. It can be created in run time.
Modal Nodes have an underlying GENIL reference, database tables and have many features like relations etc., A BOL entity is a must for a Modal Node Creation. They can be bound to custom controllers or component controllers for data exchange. They are arranged in a hierarchy which can be viewed using TCODE GENIL_MODEL_BROWSER.
BOL Entity
Data we enter on the webui get saved in the database via BOL Entities
To find which component is driving the WebUI Page just press F2 on the view element
from the technical settings you can have the UI component and its corresponding view
To find which component is driving the WebUI Page just press F2 on the view element
from the technical settings you can have the UI component and its corresponding view
- Execute the transaction "BSP_WD_CMPWB" (BSP WEBDYNPRO COMPONENT WORKBENCH)
- Enter the name of the component
- click on display
- Identify the view which you have found out by clicking F2 on the UI Element by expanding the views folder
- double click on the View
- Expand the Context in the right pane
- expand the context nodes
- Double Click the context node which u have found by clicking F2 on the UI Element
- you will find the context node class with the extension "CNXX
Note
Controller Class will have an "IMPL " Extension.
Context class will have an "CTXT" Extension.
Context Node Class will have an " CNXX" Extension.
The same thing is applicable for controller, window and the view. Just double click on the selected element in the left pane be it either a controller, window or a view the class extensions are same.
The Context Node class contain a collection wrapper class
A collection wrapper class is a container that hold the BOL Entities
A BOL entity is a class instance with underlying structures mapped to the database tables.
These BOL Entities will be of type CL_CRM_BOL_ENTITY
For example consider the Form View which contains the data that is being held by 1 BOL entity which in turn is held by a Collection wrapper
Note
For Table view the data is 1:N, i.e there can be N BOL entities (all with the same structures) corresponding to the each row of the table view and held by the collection wrapper.
To access BOL Entity underlying the view
If you are in the method of an IMPL Class
Controller( or ME)-->Context-->Context Node-->Collection Wrapper-->Get_current ( ).
If you are in the method of a Context Node class
context node-->Collection Wrapper-->Get_Current ( ).
Get_current ( ) gives the BOL Entity underlying the view.
You can also use get_first ( ) (in the case of a form view) as there is only 1 BOL Entity.
In case of a table view where each and every row of the table view corresponds to 1 BOL Entity you can loop around the collection wrapper and get the BOL Entity of the corresponding row using the index.
Get_next ( ) also gives the next BOL Entity underlying the table view.
Saturday, 12 May 2012
Enhancement set
SAP provides a concept to enhance standard UI Components without modifying the standard SAP UI components. all the modifications that are carried by the customer will be stored in the container called Enhancement set
- Execute the Transaction SM34.
- Open the view cluster BSPWDVC_CMP_EXT.
- Go to change mode.
- click on " New Entries " Button.
- Furnish the details such as Enhancement set (for eg: say ZESET) and maintain the description for the same.
- click on "SAVE".
Note:
You can create multiple enhancement sets but only one enhancement set is used by the Webclient UI Framework at runtime.
After Creation of Enhancement set you have to assign your enhancement set to the current client where you are working on enhancing the UI Component.
Assigning the enhancement set to the client
- Execute the transaction SM30
- Enter BSPWDV_EHSET_ASG
- click on "Maintain"
- enter assignment no sat for example 221
- enter your enhancement set i.e ZESET
- SAVE
Note
BSPWDV_EHSET_ASG is a maintainance View to maintain the data of table BSPWD_EHSET_ASGN
Subscribe to:
Posts (Atom)
