You’ve created some AET extension tables to a specific object. Now you want to display them along with the SAP standard views in the CRM WEB UI. This brief article will tell you how to do this, but does not give you the detail of the configuration steps, short of mentioning briefly what configuration is needed.
I’ll use the BP_HEAD component of the CRM Web UI as my example. This component is the component that displays the business partner or Account.
Find the view created for the extension. This can be viewed in spro: Customer Relationship Management->UI Framework->UI Framework Definition->Application Enhancements->Define System Settings (transaction axtsys). Select the package that was used to create the AET fields. The components created when the AET extension was done will be listed. You need to find the component, check that component in transactioon bsp_wd_cmpwb to find your view.
In the component that you want to enhance (BP_HEAD in our example) add that view into the component usages in the Runtime Repository Editor. Give the usage a meaningful name. In my example I have used ZZ_BP_INCOME. This name will be used later for the context node binding.
Then Add the view to the relevant viewset in the Runtime Repository Editor. In our example we add our view to the BPHEAD/BPHEADOverview Viewset.
You need to find out the name of the context node from your AET view that you will bind to the context node of the SAP standard view. Ours is called ‘PARENT’. It seems AET always creates a node called PARENT.
If not already done enhance the Component Controller of the SAP standard component that you are working with. BP_HEAD in our case. Once enhanced, redefine the WD_USAGE_INITIALIZE method to bind the view context node (PARENT) to the relevant component controller context node (PARTNER (BuilHeader)). Note the name of the usage comes from the name provided when the usage was created in Step 2 above. Sample code:
METHOD WD_USAGE_INITIALIZE. CALL METHOD SUPER->WD_USAGE_INITIALIZE EXPORTING IV_USAGE = iv_usage.
CASE iv_usage->usage_name. WHEN 'ZZ_BP_INCOME'. TRY. CALL METHOD iv_usage->bind_context_node EXPORTING iv_controller_type = cl_bsp_wd_controller=>co_type_component iv_name = iv_usage->usage_name iv_target_node_name = 'PARTNER' " Node of the MAIN component iv_node_2_bind = 'PARENT'. " Node of the embedded component CATCH cx_bsp_wd_incorrect_implement. "#EC NO_HANDLER * Go on with next binding ENDTRY.
Now you can go to the Component Structure Browser, select the relevant view. BP_HEAD/BPHEADOverview in our case. Now select the Configuration tab. The selected view should be an overview page. This means that it will have configurable Assignment Blocks in it.
If you have done the above steps correctly your new view should be in the list of available Assignment Blocks. You should have created a Business Role and Role Configuration Key for your new configuration. You can now copy one of the existing configurations that is suitable, add the new view to your new configuration by selecting it from the left column and moving it to the right column. Save this configuration.
When you login with the correct business role, you will now see your new AET extension table as an assignment block. It should have an Edit List button that allows you to maintain entries.
Go for it and good luck!