Webui Classes and interface

CLASSES

CL_CRM_BOL_CORE

            This class creates an instance of business object layer (Component Set). This class follows singleton design pattern. The BOL Core is the central service provider for API classes and it communicates with underlying business object implementation.

·         START_UP: It takes the name of component set that to be started and starts the BOL. It takes one more parameter IV_DISPLAY_MODE_SELECT which is optional and set to ABAP_FALSE by default. This means BOL follows optimistic lock which makes all objects changeable in user interface even without a lock. The lock is automatically requested on first attempt of change.

·         GET_ENTITY_FACTORY: Get factory handler for business object.

CL_CRM_BOL_QUERY_SERVICE

            Used to select bol entity.

·         GET_INSTANCE: Get the instance.

·         SET_PROPERTY: Set a search criterion.

·         GET_QUERY_RESULT: This method is used to execute the query and returns the result of type if_bol_entity_col.

CL_CRM_BOL_DQUERY_SERVICE

            This class is used for advanced query search using greater than, lesser than, multiple search patterns, saved searches (save and retrieve).

·         SET_QUERY_PARAMETERS: Setting the query parameter for maximum hits.

·         ADD_SELECTION_PARM: Adding selection criteria. It takes 4 parameters.

·         GET_QUERY_RESULT: This method is used to execute the query and returns the result of type if_bol_entity_col.

·         SAVE_QUERY_AS_TEMPLATE: Save query as template using query id.

·         LOAD_QUERY_AS_TEMPLATE: Load the query from template using query id.

CL_CRM_BOL_ENTITY

            This class is used to access the entities which implements business objects.

·         GET_RELATED_ENTITIES: Gets a list of 1:N related entities for particular attributes.

·         CREATE_RELATED_ENTITIES: For creating child objects.

CL_CRM_BOL_COL

            This class is used to hold all the instances implementing the standard property access interface IF_BOL_BO_PROPERTY_ACCESS.

CL_CRM_BOL_ENTITY_COL

            This holds regular BOL entities only.

CL_CRM_BOL_ENTITY_FACTORY

·         CREATE: For creating root entity.

CL_BSP_DLC_VIEW_DESCRIPTOR

            This class is used to describe the property of attributes such as changing to dropdown list, checkbox, link, radio, oca, etc.

INTERFACES

IF_BOL_TRANSACTION_CONTEXT

            This interface Controls transactional behavior such as modify, create, delete entities. It has three types of transaction, one is global transaction context which holds all modified root entities, next is fine granular transaction context exists for each root object instance and last is custom transaction context.

·         SAVE: Save the changes.

·         COMMIT: Commit the changes.

IF_BOL_BO_COL

            Provides collection to hold business objects (BO).

IF_BOL_ENTITY_COL_ITERATOR

·         GET_FIRST: Gets the first entity from collection wrapper.

·         GET_NEXT: Gets the next entity from collection wrapper.

IF_BOL_BO_PROPERTY_ACCESS

            This interface is used to access the properties of BOL entities and query services. The classes CL_CRM_BOL_ENTITY and CL_CRM_BOL_QUERY_SERVICE inherits this interface.

·         GET_PROPERTY_AS_STRING

·         SET_PROPERTY

SAP CRM Business Partner and Set type data tables

SAP CRM Business Partner and Set type data tables

Following are the tables that will come in handy, when you have to find out where is the relationship stored between BP Guid and Set Types Guid (Example, Shipping, Billing, Sales Tab's).
Here are the tables

CRMD_ORGMAN – Organization unit set
BUT000 - Business Partner
CRMM_BUT_LNK0011 - Business Partner - Sales Rule
CRMM_BUT_SET0010 - Business Partner: Sales Data
CRMM_BUT_LNK0021 - Business Partner - Shipping Rule
CRMM_BUT_SET0020 - Business Partner: Shipping Data
CRMM_BUT_LNK0031 - Business Partner - Billing Rule
CRMM_BUT_SET0030 - Business Partner: Billing Data
CRMM_BUT_LNK0141 - Business Partner Organization Rule
CRMM_BUT_SET0140 - Business Partner Organization Rule Period

Difference Between Append Structure and Include Structure

Difference Between Append Structure and Include Structure

1. Append Structure is a mechanism of adding extra fields to the Standard Table. Where as, Include Structure is a mechanism of adding extra fields to the Custom Table.


2. Append Structure adds fields at the last of the Standard Table. Where as, Include Structure adds fields at any position.


3. Append Structure can only be used once.(i.e. If we add an append structure to a Standard Table, the same Structure can't be appended to the another Standard table). Where as, Include Structure can for Multiple Tables. (i.e. If we include structure to the custom table using include structure, the same structure can be included in any other Custom Tables).


Append Structure & Include Structure can also be used to add new fields or extra fields to the structures. (i.e. Using Append Structure, we can add a structure to a standard structure, which will add the fields at the end of the structure. Include Structure can be included in any custom structure at any position).

Note :
1. It is not possible to add or to append or to include a table to a structure.
2. We can't append a structure to a sap table which has the fields with data type VARC, LCHR RAW & LRAW.(i.e. all the fields with the above specified data types should be always be as the last fields in the data base table. if we add an append structure to such table their comes the conflict b/w append structure and the long data types in sap table.

HYBRIS

How to Delete an already released transport request or task

     

          How to Delete an already released transport request or task .

        Is it possible to delete a task/transport request once it is set to release ? 

        Of course, we can But we  have to change status of the request to do so.

       1. Goto  transaction SA38 ( or SE38 )and run program: RDDIT076 . 

         

     

   

 2.  Set your request number and run the program, A list with Transport request and tasks will appear 

 3 . Double click on the TR or task you want to unlock. A popup will appear for change and display (Expert mode).

      

   PS : in case the expert mode is not enable go down to see the Alternative approach. 

  

 4.   On the popup window click on display/change button or press F9. 

5. Change the Status from R to D (Or N to D in case only task is released ).

6.  Click on ok button. A confirmation popup will appear click on yes. 

7. The TR is set to modifiable state,Now you can delete Transport request.    

-------------------------------------------------------------------------------------------------------------------------

PS : Sometime user didn't have the proper authorisation for the expert mode(i.e only display access is given  ) as the auth. object   S_CTS_ADMI  is missing, You can  ask you Basic consultant for the this access or to unlock the TR.

Alternate solution :( surpass the authority check in debugging mode.)  

Goto tcode SE37 , Open function module TR_AUTHORITY_CHECK_ADMIN. place a session  debugger at line 23. 

 Execute  report RDDIT076 as mentioned in the step 1 and 2 above, 

Debugger will hit as soon as you click on the TR  , in the debug mode forcefully go inside the If condition ( place the cursor on line 24 and press F12). execute the return condition. 

The debugger will get hit couples of time so repeat the same steps. After the execution is completed you can see the popup with Expert mode is enable. 

Follow the step 4 and rest afterwards  :-) 

      

   

CRM Webui Keyboard Shortcuts

List of shortcut keys:

1) F2 – Technical data

2) F6 – HTML Print preview

3) CTRL + SHIFT + F7 – Performance Information

to close  the window  we need  to press ‘CTRL + SHIFT + F7’ keys again.

Also ‘Create Memory Snapshot’ has the same functionality as a memory snapshot in S_MEMORY_INSPECTOR. ‘Start Backend Runtime Analysis’ creates a runtime trace that can be read via transaction SAT.

4) CTRL + ALT + F2 – System Information 

5 ) SHIFT+ALT+F2 for "view hierarchy

6) conditional break point using ALT+F2

 7) SHIFT+ALT+CTRL+F2 all short cut keys

How to find view name and component from transport request

SAP CRM webui provides this excellent feature to change layout of  view based on our requirement.

When a new screen layout is created a Guid is generated by system (context id), the Screen layout customisation is stored as an XML file,Based on the context system at run time knows which screen layout need to be loaded.

As a developer we are are aware of the change done on screen by us ,while sometime it is difficult to know the views/component name as their might be a lot of views changed or maybe other developers are also working on the same component.      

In Transport request we can only see the guids and and some others node, like in the below picture:

this is not what we are looking for right ?

The solution of our question is BSPC_DL_XMLSTRX2.


"BSPC_DL_XMLSTRX2 is a standard SAP Table which is used to store Storagetable for XML layout descriptions information."

1. Goto Se16/SE11 give the table name as BSPC_DL_XMLSTRX2.

2. In the Context id field paste the guid(or list of guid ) copied from the transport request.

3. Execute. you will get View and component name with  role key and other fields .

If it was useful, you are welcome to leave a comment :-) . 

How to create data loss popup in CRM WebUI

When navigating from one custom component to other components or documents using Quick links or Navigation bar links we need to restrain user from accidentally deleting the  unsaved data, to achieve this we prompt data loss popup, which requires user input to proceed further. 

Below are the steps to create a data loss popup: 

STEP 1: Create a method with the name ON_BEFORE_WA_CONTENT_CHANGE in window                    implementation class with following properties:

                                      Level : Instance Method
                                     Visibility: Protected

STEP 2: Click on the method and click on Detail View button which is near parameters and set the                   following settings by clicking on Event handler for checkbox:

                                     Class/Interface: CL_BSP_WD_VIEW_MANAGER
                                      Event: BEFORE_WORKAREA_CONTENT_CHANGE
           and save the settings.

STEP 3:  Set the following settings for parameters:
                                     Parameter: DATA_LOSS_HANDLER
                                     Type: Importing
                                     Typing Method: Type Ref To
                                     Associated Type: IF_BSP_WD_DATA_LOSS_HANDLER

STEP 4: Write the following code into the above method:

data_loss_handler->set_save_handler( me ).   data_loss_handler->set_revert_handler( me ).   data_loss_handler->set_cancel_handler( me ).   data_loss_handler->trigger_data_loss_handling( ).

STEP 5: Redefine the method DO_VIEW_INIT_ON_ACTIVATION and write the following line: 

        

            SET HANDLER on_before_wa_content_change ACTIVATION abap_true.

STEP 6: Add interface IF_BSP_WD_EVENT_HANDLER in main your window. Implement the method IF_BSP_WD_EVENT_HANDLER~HANDLE_EVENT

	CASE iv_event_name.     WHEN if_bsp_wd_data_loss_handler=>save_event.     rv_success = abap_true.     WHEN if_bsp_wd_data_loss_handler=>revert_event.      rv_success = abap_true.     WHEN if_bsp_wd_data_loss_handler=>cancel_event.      ...  ENDCASE.

 

And write the logic in these cases and when yes or no button is pressed leaves current component.

How to Modify, Create and Delete table entries from SE11 tcode.

We all come across some situation when a table entry need to be modify or removed, Generally it can be done through tcode SM30 or Maintenance view, However sometimes as table is not maintained through transaction SM30 or no Data maintenance view is not present, its all most impossible to proceed further.

In such case to achieve this we can modify the table entry through se11

1. Goto Tcode SE11, enter the Table name

2. click on the Content(Ctrl+Shift+F10)

3. Then click on execute button.

4.  Click on the record you want to Delete or modify .

5. The entries is displayed now, go to debug mode by typing /H in the command screen , press enter        to switch on Debugging.

6. Again press Enter key or click on Continue to go into Debug Mode.



7. change the value of code to 'DELE' /EDIT, In this example as i want to edit the record,so i change       the value to EDIT.

8. After changing the value press F8. now you will be able to Edit/Delete  the entry  that entry.

9. Now made the change and save.

Apart from this procedure ,depending on the SAP release you can also use transaction SE16N or SE16. Enter the name of the table and then in the command field &sap_edit. Then your maintenance functions will be available.

SAP CRM interview Question

These are some Interview Questions i was asked during my interviews . I will keep posting  the new question and answer.


1) CRM BOL Programming 

31. What is business role ?

32. How to create Business Role and what is Business role customizing ?

33. What is Navigation bar customizing ?

34 Have you ever created TBUI ?

35 What is logical link and how to create logical link ?

36 How to create a custom component ?

37 What is the difference between BOL and GENIL ?

38 What is context ?

39 How to handle event ?

40 What is the difference AET and EEWB ?

41 What is the difference between MACRO and SUB-ROUTINE ?

42 Can we debug a MACRO ?

43 What is abstract method ? What is its use ?

43 What is abstract class ?

Inline ABAP declarations

Inline Declaration with release 7.4 

Inline ABAP DATA declarations are a new concept introduced in release 7.4 which allows you to declare your internal table variables or work areas within the code that uses them. This is done simply by adding the DATA(wa_data) or @DATA(it_data) statements.
The easiest way to describe this is to show you a very simple before after ABAP code example.
Pre 7.40 you would declare a work area and read data into it something like this

DATA: it_ekko TYPE STANDARD TABLE OF EKKO,
wa_ekko TYPE EKKO.
READ IT_EKKO INTO WA_EKKO.

Using the new method you would simply just using the following code:

READ TABLE it_ekko INDEX 1 INTO DATA(wa_ekko_new).

Hopefully the above example gives you an idea of how this new functionality can streamline your ABAP code and make it more readable. Also gives you the basics so you can have a play yourself. Now onto the @DATA statement....




The @DATA statement- Service Pack 08

The @DATA statement takes this a step further, allowing you to automatically inline declare an internal table to hold values you are selecting from a database table, using the SELECT statement. The only problem with this functionality is that it doesn't come in until Service Pack 08 or SP09. I have tried SP07 and it is definitely not in that and is there by SP09.
If you had a coding example where you declare an internal table to select values into it you would have some code that looked something like this.

TYPES: BEGIN OF t_ekko,

ebeln TYPE ekpo-ebeln,

ebelp TYPE ekpo-ebelp,

statu TYPE ekpo-statu,

aedat TYPE ekpo-aedat,

matnr TYPE ekpo-matnr,  menge TYPE ekpo-menge,

  meins TYPE ekpo-meins,

  netpr TYPE ekpo-netpr,

  peinh TYPE ekpo-peinh,

  CELLCOLOR TYPE LVC_T_SCOL,

 END OF t_ekko.

DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,

      wa_ekko TYPE t_ekko.

select ebeln ebelp statu aedat matnr menge meins netpr peinh

   up to 10 rows

  from ekpo

  into CORRESPONDING FIELDS OF TABLE it_ekko.

Using the new @DATA statement you could essentially replace all this with the following ABAP code, which automatically create an internal table with the correct field structure and drops the selected values into it. AS well as the @DATA note the ,'s after each field in the SELECT.

select ebeln, ebelp, statu, aedat, matnr, menge, meins, netpr, peinh
    up to 10 rows
    from ekpo    into TABLE @DATA(it_ekko_new).

This is more like it and if you combine the two examples together you get quite a neat and efficient looking section of code. It essentially removes all the ABAP declaration lines of code without adding much at all to SELECT and READ statements.

select ebeln, ebelp, statu, aedat, matnr, menge, meins, netpr, peinh    up to 10 rows
    from ekpo    into TABLE @DATA(it_ekko_new).
READ TABLE it_ekko_new INDEX 1 INTO DATA(wa_ekko_new2).
 WRITE:/ wa_ekko_new2.

ABAP Code Snippet

1)  Convert String/char  into Amount/quantity field based on Decimal notation set in the user profile.