![]() These configs are explained in the configuration section for approval apps in sap help. Step 3: Perform App specific configurations if neededįor Approval Apps, you will need a specific configuration telling Fiori what workflow tasks to use for which app. Having seen a few setups now, I can safely say that its very hard to do these things in isolation. In short, this is a work of close coordination between your architect and your basis team. Keep an eye on what patches/notes are coming up in this area. Also, apart from this you should have a close eye on what notes are available for the apps in your scenario. It will help you prepare the right cutover plan before go-live. Once components are in place you need to activate and register the services on Gateway.įor a basis consultant reading this blog, you have to be careful as to which activities here are transportable and which ones are manual. UI Components can also be common across many apps. In case of Central Hub generally, UI components go on Gateway Hub and OData components go on your backend.įor Example: In case of Leave Creation App, UI Component is UIX01HCM 100 and Backend component is GBHCM002 600. For each app, there is a relevant UI Component and a corresponding OData/Backend components. Now you are ready to put the Fiori Components in. ![]() Then, once right components are in and services have been activated, your architect can help basis team perform Gateway configuration (different Types of RFC Destinations, System Alias for various services and Task Gateway etc.) and do a connectivity check between systems. Once you have done your landscaping its time for basis team to step in and start the install. Step 2: Set up systems and perform the installation and initial configs If your backend is not in place, you are destined to face horrible problems when you put Fiori in. If you don’t know this bit, your partner or architect/functional consultant should be able to help you explaining which app uses what in the backend. If you are interested in purchasing related apps (Like Order from Requisitions, Track Purchase Order or Approve Purchase Order), in the backend system, you should be able to create POs, Create PRs, have a release strategy setup, tested standard workflows and so on. Have you made your leave quotas available for use in ESS (Along with basic quota configuration)?Īre Team Calendar configs available in MSS for Leave Approval Apps? Have you activated ESS Business Function? (Surprise! Yes you need it!) So you need to make sure that you can perform these core functions in your backend sandbox/development system.įor Example, in Leave Management scenario, you may ask yourself following questions:Īre you able to create a leave from transaction PTARQ? Does it trigger the right workflow?Īre basic workflow configs in place for Leave Approval workflow? (Workflow customizing configs, Event Linkages, workflow definitions are active, human tasks are made as General Tasks, Org Structure and Agent Assignment as per Org Structure etc.) ![]() Fiori uses same good old ERP core functionalities. This is probably the most ignored step but the biggest time saver. Step 1: Test core functions well in ERP!! Once you have a plan in place, you are ready to work on the pre-requisites for your implementation. ![]() Get, Set, Go! Starting the Implementation Scenario we are using as a topic of discussion here is Leave Management with some extensions. In this blog we will discuss the actual implementation itself. In part 1 of this blog series (you can read it here – ), I have tried to outline what all things you need to think about when planning your Fiori implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |