https://experience.sap.com/fiori-design-web/formatting-numbers/#usage
https://sapui5.netweaver.ondemand.com/sdk/#/topic/91f3145e6f4d1014b6dd926db0e91070
a few examples: https://github.com/brooklynb7/HTML5/blob/master/sapui5-dist-static/test-resources/sap/ca/ui/demokit/explored/views/type/number.view.xml
<ObjectListItem
title="{income>Month}"
number="{ model : 'income', path : 'Cost', type: 'sap.ui.model.type.Integer', formatOptions: {groupingEnabled: true} }"
numberUnit="EUR" />
I’m deploying the openui5-sample-app to a Linux Container running Debian Buster. First update the packages and install Node.js.
apt update && apt upgrade -y
apt install curl -y
curl -sL https://deb.nodesource.com/setup_12.x | bash -
apt install nodejs -y
nodejs --version
Install PM2 (process manager to manage Node.js applications) and the UI5 Tooling
npm install pm2 -g
npm install --global @ui5/cli
Now clone the openui5-sample-app and build it
apt install git
git clone https://github.com/SAP/openui5-sample-app.git
cd openui5-sample-app/
ui5 build -a
cd ..
Run your project on port 8000. With “startup” it will automatically create a systemd script.
pm2 serve openui5-sample-app/dist/ 8000
pm2 startup
pm2 save
systemctl start pm2-root
systemctl status pm2-root
1. Install node.js
2. Install UI5 Tooling
npm install --global @ui5/cli
3. Install Easy UI5 Generator, create a project and run it on your localhost
npm install -g yo generator-easy-ui5
yo easy-ui5
cd <your project name>
npm start
4. Set up a Github project and do your initial push
git add .
git commit -m "Initial commit"
git remote add origin https://github.com/user/myUI5App.git
git push origin master
5. Install your favorite Editor, e.g. Visual Studio Code or Atom, and open your project to edit it
SAPUI5 follows Semantic Versioning.
MAJOR.MINOR.PATCH (e.g. 1.71.9)
Version overviews:
https://sapui5.hana.ondemand.com/versionoverview.html
https://openui5.hana.ondemand.com/versionoverview.html
Find detailed patchinfos here:
https://sapui5.hana.ondemand.com/X.XX.X/patchinfo.html (where X.XX.X is the SAPUI5 version number)
https://openui5.hana.ondemand.com/X.XX.X/patchinfo.html (where X.XX.X is the OpenUI5 version number)
Note: “sap.ui.core and sap.m are special, because they are OpenUI5 libraries. Currently, OpenUI5 libraries are always released as a whole. This means that whenever there is a change to be released for any of the OpenUI5 libraries, the new patch includes them all.”
If you forward a workitem manually from the MyInbox or via function module SAP_WAPI_FORWARD_WORKITEM, the function module SWW_WI_FORWARD will be called. There the SAP implemented a BAdI call of the BAdI WF_WI_FORWARD.
The BAdI provides a method to add additional checks, when forwarding a workitem. I will use it, to send notification mails.
Create your own BAdI implementation and add a task id as filter. In my case it’s the task TS21500003 of the leave request approval workflow.
Now your implementation will only be called, if this specific workitem is forwarded. Now we implement the method CHECK_BEFORE_FORWARD. The method has enough parameters to get all necessary information to enrich the mail text.
First the workitem container is read out of the context. There we get the _WI_OBJECT_ID element, which contains the request object reference. With this information we are able to get the current request object out of the workflow. I pass this into antother class where I already have a mail sending implementation.
METHOD if_ex_wf_wi_workitem~check_before_forward.
*---------------------------------------------------------------------------------*
* This BAdI implementation is used to send an info mail when a workitem is forwarded.
*---------------------------------------------------------------------------------*
TRY.
"Get workitem container and requestId
DATA(container) = im_workitem_context->get_wi_container( ).
container->get_value_ref( EXPORTING name = |_WI_OBJECT_ID|
IMPORTING value_ref = DATA(lr_req_id) ).
ASSIGN lr_req_id->* TO FIELD-SYMBOL(<lpor>).
"Get current request object
DATA(lo_req) = NEW cl_pt_req_wf_attribs( )->bi_persistent~find_by_lpor( lpor = <lpor> ).
"Send an info mail to each new agent (should be only one)
LOOP AT im_table_new_agents INTO DATA(new_agent).
zcl_hcm_leave_request_assist=>send_mail( io_req = CAST cl_pt_req_wf_attribs( lo_req )
iv_tdname = mc_mailtext
iv_pernr = cl_hcmfab_employee_api=>get_instance( )->get_employeenumber_from_user( iv_user = new_agent-objid ) ).
ENDLOOP.
CATCH cx_hcmfab_common.
CATCH cx_swf_cnt_elem_not_found.
CATCH cx_swf_cnt_container.
"In error case, do nothing. The workitem should still be forwarded.
RETURN.
ENDTRY.
"Write Info to WF Log
MESSAGE s001(00) WITH |Forward: Mail { mc_mailtext }| INTO DATA(lv_message).
im_workitem_context->set_message_to_log( im_function = CONV #( lv_message ) "max char30
im_message = VALUE #( msgid = sy-msgid
msgty = sy-msgty
msgno = sy-msgno
msgv1 = sy-msgv1 ) ).
COMMIT WORK.
ENDMETHOD.
At the end I’m writing a little notification in the workflow log. The workitem context provides the method set_message_to_log for this. The log will look like this.
cl_pt_req_badi=>get_request( EXPORTING im_req_id = request_id
IMPORTING ex_request = DATA(request) ).
request->get_all_attribs( IMPORTING ex_attribs_struc = DATA(req_attribs) ).
DATA(req_begda) = req_attribs-version-item_tab[ 10 ]-value.
Take a look in the item_tab to see the specific request values.
If you want to copy the standard workflow of the leave request approval process (WS12300111) and are adding another approval step (or you just want to add an escalation where you set the approve workitem to obsolete and create a new approval step for the next approver) you have to implement the following BAdI. In detail you only have to add the new step ID in the filter, else the approver will not see any approval or reject buttons in his inbox. See details here.
BAdI: /IWWRK/BADI_WF_BEFORE_UPD_IB
As second step you have to add the Workflow in the customizing. You’ll find further information here.
Paket: SWL = Business Workflow: Worklist Client
Paket: SWW = Business Workflow: Workitems
Also usefull:
Transactions:
| PTARQ | Testumgebung Abwesenheitsmitteilung |
| PTCOR | Testumgebung Zeitbuchungskorrektur |
HCM Fiori OData Services:
Request database :
BAdI’s:
Leave Request Functionsmodules:
SE38:
SICF:
/sap/bc/ui5_ui5/sap//sap/opu/odata/sap/ und /sap/bc/bsp/sap/Tcodes:
| sicf | Pflege des HTTP-Service-Baums (SAP Internet Communication Framework) | |
| segw | SAP Gateway Service Builder | |
| /n/iwbep/view_log | SAP Gateway Protokoll-Viewer | |
| /n/iwfnd/gw_client | SAP Gateway Client | |
| /n/iwfnd/apps_log | SAP Gateway Anwendungsprotokoll-Viewer | |
| /n/iwfnd/error_log | SAP Gateway Fehlerprotokoll | |
| /n/iwbep/error_log | SAP-Gateway-Backend-Fehlerprotokoll | |
| /n/iwfnd/maint_service | Services aktivieren und verwalten | |
| /n/iwfnd/cache_cleanup | Bereinigung des Gateway-Modellcache (Frontend) | |
| /n/ui2/cust | Customizing für UI-Technologien | |
| /n/ui2/flp | SAP Fiori Launchpad | |
| /n/ui2/flc | SAP Fiori Launchpad – Prüfungen | |
| /n/ui2/flia | Fiori Launchpad: Absichtsanalyse | |
| /n/ui2/flpd_cust | Fiori Launchpad: Designer (mandantenüber.) | /n/ui2/flpcm_cust (3170196) GUI -> /ui2/flpcm_cust WEB |
| /n/ui2/flpd_conf | Fiori Launchpad: Designer (mandantenabh.) | /n/ui2/flpcm_conf (3170196) GUI |
| /n/ui2/flpcm/cust | FLP-Content-Manager | |
| /n/ui2/flpcm/conf | FLP-Content-Manager | |
| /n/ui2/semobj | Semantisches Objekt definieren – Kunde | |
| /n/ui2/semobj_sap | Semantisches Objekt definieren – SAP | |
| /n/ui2/theme_designer | UI Theme Designer | |
| swfvisu | Workflow Visualisierungs-Metadaten | |
| swfvmd1 | Workflow Visualisierungs-Metadaten | |
| sui_support | for getting information tied to a Fiori, UI, Gateway, and Basis logs (3432533) |