Ii) Create Function module enhancement for ‘ PTRA_UTIL_EXPENSE_REPORT_SAVE’. L_te_key-pdvrs = wd_assist->gs_common_rfc_input-period_version.ĮXPORT user FROM lt_user TO DATABASE pcl1(te) ID l_te_key. TRIPS TOWEB CODEIn the pre-exit of the ON_NAVIGATE method in the component controller, make the below code changes.Lo_el_user_data = lo_nd_user_data->get_element( ).ĬASE 2: When creating the new request, save these new fields in the Travel cluster. Lo_nd_user_data = wd_context->get_child_node( name = wd_this->wdctx_user_data ). L_te_key-perio = wd_assist->gs_common_rfc_input-period_number.ĭATA lo_nd_user_data TYPE REF TO if_wd_context_node.ĭATA lo_el_user_data TYPE REF TO if_wd_context_element.ĭATA ls_user_data TYPE wd_this->element_user_data. L_te_key-reinr = wd_assist->gs_common_rfc_input-trip_number. L_te_key-pernr = wd_assist->gs_common_rfc_input-employee_number. IF wd_assist->gs_common_rfc_input-trip_action EQ ‘MOD’. In the post exit of the WDDOMODIFYVIEW method, make the following code changes, When modifying the travel request, retrieve the stored data in cluster and display it in the Webdynpro screen. Pass these customer fields (USER_DATA) to the USER EXIT maintained for earlier version of travel management.When creating the new request, save these new fields in the Travel cluster.When modifying the travel request, retrieve the stored data in cluster and display it in the Webdynpro screen.Now map the fields of structure user_data to the UI elements.Įnhancements are made under the following scenarios Screen enhancement in TRIP/PR05 Transactionįollowing are the screen fields enhanced using the structure PTK99 in the screen exit SAPMP56T (screen number 9999 ).Ĭreate a node(USER_DATA) in the component controller of the Webdynpro Component FITE_VC_GENERAL_DATA.Ĭreate the UI elements in the view and map the newly created node in the component controller node to the view node. Moreover SAP has clearly mentioned that “ This user exit cannot be used with the SAP EP interface”, that made me try some solution that helps all the travel management consultants to easily make use of the existing travel data without creating new structure/table/cluster in the new version. In the travel management (EHP3) solution, there is no provision to neither enable those customer fields nor save the information in the cluster. After enabling the user data option using the transaction FITVFELD, all the custom fields are enhanced in the standard screen exit SAPMP56T (screen number 9999) using the structure PTK99 and stored in the cluster using the same structure. In the earlier version of Travel Management, TRIP and PR05 transactions are used to create travel request/expense. This blog clearly explains in displaying/saving the customers enhanced fields for the screen exit SAPMP56T using PTK99 structure and reuse it in Webdynpro ABAP without creating a new structure/table/cluster. This blog applies to SAP Netweaver 7.0, SAP HR EHP3(EA-HR 603).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |