![]() In the third step which is Define Custom Handler Classes For Business Transaction Model Nodes. Over here I have user 1 to many as 1 particular opportunity could have multiple dealers:-ģ. This particualr section deals with the kind of realtionship/cardinality which we are looking out for the dealer table with respect to the BT order transctions. We need to come back on the User area menu screen click on the button Extend Model for Business transaction with new relations. Now in step 1 after defining the new node. When we enter the screen after clicking on the button we need to click on the new entries button:-Īnd we need to make the following entries:-Ģ. When we click on extend model for business transactions with new nodes we’ll be defining the new ZBOL model with respect to the Dealer table which we had created above. As a first step type transaction SPRO click on SAP Reference IMG and got user area MENU Customer Relationship Management->CRM Cross-Application Components->Generic Interaction layer/Object Layer->Component specific settings->business transactions->Extend Model for business transactions with new nodes:. This mean after we incorporate the handler class enhancement and when we open the opportunity on webui screen we’ll have this data for Dealer shown as per the entry made in the dealer database table.ġ. The GUID DE17AD967C89D5F19C570019B9F5A712 is for the quotation number 100:-Īlso define the structure for the table which we’ll be using in our later steps:. To make it more simple we have already made an entry in this table as :. The GUID will be the key which will link this table to the BT objects(in our case its opportunity). So we have a Z table ZZBT_DEALERS created as per below screenshot:. You can use your Customize table and then accordingly use it. We’ll be using a simple scenario wherein we are planning to have some dealers associated with the opportunity id. Steps to use handler classes in BSP workbench.Testing the handler class in GENIL_BOL_BROWSER.He worked in SAP CRM Web UI areas like BSP enhancements, transaction launchers, BOL Programming, BRFPlus. Prior to working with Atos he had worked with SAP India(SAP Global Delivery), Capgemini, Accenture and Infosys. He is also a SAP CRM EHP2 Certified associate consultant. He has got experience of more than 9 years in SAP ABAP and SAP CRM web UI. Rajwin Singh Sood is currently working as Team lead/Solution Architect at Atos. The other purpose is it gives good insight to the user especially to the technical people as to how the CRM BOL architecture works. The second answer it gives more flexibility as well as the power to each technical developer to design the custom functionality. ![]() Due to this inconsistency many times the whole Web UI dumps. First one AET is not always reliable many instances are there where we have added the custom fields/table to the existing standard field and when we try to activate it suddenly takes more time and meantime AET dumps out. ![]() Well there are two answers to this which I have experienced while working in umpteen implementation projects. But then the question is why we should use handler classes in first hand when we have powerful tool like AET with us. To be more precise by using handler classes we are trying to achieve what we do in AET or EEWB. Handler classes methodology is very helpful in SAP CRM WEBUI framework where we have a scenario to enhance standard BOL object in order to include customize functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |