Vor einer Weile musste ich mich recht kurzfristig in das oben genannte Thema einarbeiten. Ich hatte bisher nie konkret damit zu tun und habe daher erstmal die entsprechende SAP Help Seite überflogen. Relativ schnell habe ich zum Glück den für mich relevanten Teil gefunden.
Das relevante Customizing findet man in der SPRO hier:
Die Unternehmen findet man in SF z.B. unter Admin Center → Manage Date → Legal Entity
Report zum Testen: ECPAO_EE_ORG_REPL_QUERY
Collection of useful resources, when working with the Fiori App: My Travel and Expenses for Business Traveler (F6190)
SAP Travel Management for SAP S/4HANA
SAP Help Travel Management (FI-TV)
FI-TV transactions
Reports
Tables
Good to Know: SAP Travel Management for SAP S/4HANA
Related notes:
– 2719018 – S4TWL – SAP Travel Management in SAP S/4HANA Suite 2022
Packet: PTRA_ADDON
My Travel and Expenses for Business Traveler (F6190)
Fiori Reference Library My Travel and Expenses for Business Traveler
SAP Help My Travel and Expenses
App Extensibility: My Travel and Expenses
Related notes:
– 3267811 – Default Travel Expense Start and End Date and Time settings with Travel Management S/4Hana Fiori application
– 3591806 – Fiori Apps Travel Management Version 3: Concurrent Employment not available → Helpful Attachment ExtensionTravelProfileVH.pdf
– 2164524 – Customizing of authorization object P_TRAVL for restricting creating/changing of expense reports
– 2633200 – Expense reports with and without mandatory travel requests
– 3406341 – Attachments in S4Hana Fiori apps MTE V3 and MTR V3
Packet: PAOC_TRV_S4
Workflow
Workflow Scenarios in Travel Management (FI-TV)
Approving a Trip
Standard WF for Approving Trips: WS20000040
Travel Management Workflow FAQ, Common Issues, Known Issues
Related notes:
– 2576990 – Workflow: Status of a trip after reject or send back for correction → Explanation, why the default workflows are a bit “uncomplete”
Recently I had to configure the Travel Fiori Apps on a H4S4 System.
My Travel Requests for Business Traveler (MTR)
My Travel and Expenses for Business Traveler (MTE)
My Inbox – Approve Travel Requests
My Inbox – Approve Travel Expenses
This was pretty easy and after enabling the Apps, I activated the default Workflows WS20000050 (Approve Travel Request) and WS20000040 (Approve Trip) as well. I also checked SWE2 for BU2089 and everything looked good.
But when testing, only the Travel Request Workflow started successfully. When creating a Trip Expense, no Workflow started, instead the Trip Expense directly went to status “Trip Approved” instead of “Trip Completed“. Here you can find an overview of the possible statuses: Trip Status Directory
Initially I thought, this is somehow a Workflow issue or the BUS2089 connection does throw the right event. I also found a note related to this: 2792991.
But it turned out to be a customizing problem and the answer was only one click away from the Trip Status Directory in the chapter Trip Status Assignment. Here the Feature TRVPA is mentioned. And when looking into the system and reading the documentation via PE03 I found the following
Turned out, for Feature TRVPA and Entry WRP the value 4 was set. After changing it to 3, the right trip status got set and the workflow got triggered.
As always, the solution is quite simple once you know it, but it took quite a while to figure it out.
Paket: FPB_PERSONALIZATION
Fuba: FPB_PERS_POST_FOR_DIALOG
Tabelle: FPB_PERSPARM
https://launchpad.support.sap.com/#/notes/0001622954
Beispiel: Reisebeauftragter (RBA) für das Travelmanagement via Dialog CO-CCA-TR
Anlegen:
Tcode FPB_MAINTAIN_PERS_S
Dialog DIA_CO-CCA-TR
Löschen:
Tcode FPB_DELETE_PERS_DATA
Dialog CO-CCA-TR
Anzeigen:
Tcode: FPB_SHOW_PERS_DATA
Siehe weitere Transaktionen im Paket.
" Option 1
TRY.
cl_hrpa_masterdata_factory=>get_read_molga( IMPORTING read_molga = DATA(lr_molga) ).
DATA(molga) = lr_molga->read_molga_by_pernr( pernr ).
CATCH cx_hrpa_violated_assertion.
ENDTRY.
" Option 2
TRY.
DATA(employee_api) = cl_hcmfab_employee_api=>get_instance( ).
DATA(molga) = employee_api->get_molga( pernr ).
CATCH cx_hcmfab_common.
ENDTRY.
DATA infotype_text TYPE TABLE OF hrwpc_s_infotype_text.
CALL FUNCTION 'HRWPC_RFC_IT0XXX_TEXT_GET'
EXPORTING
pskey = CORRESPONDING pskey( p0019 )
TABLES
infotype_text = infotype_text.
DATA(text) = REDUCE #( INIT str = || FOR line IN infotype_text NEXT str = str && | | && line-textline ).
Bisher kenne ich keine “offizielle” Klasse der SAP für die Sachbearbeiterermittlung. Auf jedem System dafür eine neue Helper Klasse/Methode anzulegen finde ich aber auch nervig. Ich nutze daher diese Klasse aus dem Notification Tool Paket P99_NT, nicht optimal, erfüllt aber seinen Zweck.
cl_hrpay00_nt_read_db=>get_admin_data( EXPORTING iv_pernr = pernr-pernr
IMPORTING es_sacha = DATA(es_sacha)
ev_usrid = DATA(ev_usrid)
ev_sbmod = DATA(ev_sbmod)
es_p0001 = DATA(es_p0001) ).
You can use SM30 and View V_T591C to configure whether USRID or USRID_LONG should be used for a subtype of infotype 0105.
DATA(service_manager) = NEW cl_hrpp_ws_service_manager( ).
SELECT * INTO TABLE @DATA(lt_t52el) FROM t52el WHERE molga = '01' AND symko <> @space AND endda >= @pn-begps. " Verknüpfung Lohnart zu symbolischen Konto
SELECT * INTO TABLE @DATA(lt_t52ek) FROM t52ek. " Symbolische Konten
SELECT * INTO TABLE @DATA(lt_t52ep) FROM t52ep. " Kontierungsarten
LOOP AT lt_t52el INTO DATA(ls_t52el). " Ermittle je Lohnart die symbolischen Konten (1:n)
TRY.
DATA(ls_t52ek) = lt_t52ek[ symko = ls_t52el-symko ]. " Ermittele Kontierungsart
DATA(ls_t52ep) = lt_t52ep[ koart = ls_t52ek-koart ]. " Ermittele Typ des symbolischen Kontos
DATA(process) = CONV ktosl( 'HR' && ls_t52ep-kttyp ).
CATCH cx_sy_itab_line_not_found.
CONTINUE.
ENDTRY.
service_manager->hrpp_fi_acct_det_hr( EXPORTING companycode = pernr-bukrs
process = process " Vorgangsschlüssel
symb_acct = ls_t52el-symko
eg_acct_det = CONV #( '1' ) " Überleitung FI/CO: Mitarbeitergruppierung Kontenfindung: alle Mitarbeiter
IMPORTING gl_account_debit = DATA(account_debit)
gl_account_credit = DATA(account_credit)
return_tab = DATA(return_tab) ).
IF line_exists( return_tab[ type = 'E' ] ).
CONTINUE.
ENDIF.
" Lese Sachkonto Text
service_manager->hrpp_gl_acc_getdetail( EXPORTING companycode = pernr-bukrs
glacct = account_debit
language = sy-langu
text_only = abap_true
IMPORTING account_detail = DATA(account_detail) ).
ENDLOOP.
Fiori 2.0 Apps in SAP Human Capital Management
Frontend: CONTENT_HCM_APPS
Backend: ODATA_HCMFAB
Backend: HCMFAB_GLOBALIZATION
Länderspezifische Logik findet man in diesen Paketen, wie z.B. MyForms Implementierungen.
Fiori Apps in SAP Human Capital Management for SAP S/4HANA
Frontend: CONTENT_HCMS4_APPS
Backend: H4S4_APPS
Allerdings sind auf Releasestand H4S4 2022 SP05 die meisten Pakete noch leer.
