Skip to Content
  • We often come across scenarios wherein the customer expects to route the local url to a public domain while displaying the links in the “Related Objects” section of FIORI My Inbox.
  • We are acqainted with the fact that FIORI my inbox becomes a replica of R3 My inbox(SBWP) and this a part of standard customization. Now after we expose the Decison Task to NW Gateway we are able to perform the actions (Approve,Reject,User Comments, Opening links in the Related Objects Section) from FIORI My Inbox.The Standard service for Task Processing /IWPGW/TASKPROCESSING has to be activated to allow processing of task operations like (opening attachments, fetching related objects URL links…).
  • Similarly standard service /IWWRK/WFSERVICE/ is activated to take show the workitems created under the exposed task, handling of approve/reject scenario, user comments.
  • Screenshot to show the Related Object Link Section.

When the user opens a workitem from FIORI Inbox, there is a Related Objects Section that contains URL links(BO like PO,PR SES….).The link should directly take the user to the corrsponding BO in a new Webgui session.

 

  • On clicking the URL link from the related objects section the user is prompted to enter the ECC login credentials in the new WEBGUI Session. This should be rather redirected directly to the link resource without the login page.
  • When the hostname of FIORI and ECC WebGUI are on the same hostname ie (SERVER.DOMAIN.LOCALĀ ) the link is routed correctly to the resource however it prompts for the login page when they are different. FIORI user uses a public domain (SERVER.NEWDOMAIN.COM) i.e an alias of the previous one
  • When the user clicks on the Link it hits the ECC server to fetch the Link URL.
  • It reaches the following method where it fetches the URL link for displaying the ECC resource(BO in the given example). Please follow the sceenshot below.

  • If we drill down further we reach to the exact place where we see how the URL and port number are generated.It is a ‘C’ call in function module ‘TH_GET_VIRT_HOST_DATA’ that eventually fetches the hostname and port number.

  • A Sample screenshot from the NW Gateway as well to showcase what all Task attributes are fetched. Object Link URL is encircled in red.

  • Now the fetched URL would show up against the Related Objects as shown in the screenshot below.

  • Now on clicking the Disbursement Request it would open a new WEBGUI Session separately.

  • At this place we can modify the URL according to the user requirement. In the aforesaid example I would redirect it to the Yahoo Home Page.In any client scenario as I have explained earlier a different URL whose host name is an alias of the local can be replaced with the existing one.
  • In order to strenghten this scenario, while creating the enhancement we get the instance id i.e the workitem ID. With this we get the desired workflow for which the enhancement can be triggered.
  • Please follow the screenshots below.
  • A Sample screenshot from the NW Gateway as well to showcase what all Task attributes are fetched. The Modified Object Link URL is encircled in red.

  • This URL shall be returned to My Inbox and when we hover the cursor on the Related Objects Link it will show the changed URL in place of the earlier one.
  • Please follow the screenshot below.

  • A Sample screenshot from the NW Gateway as well to showcase what all Task attributes are fetched. The Modified Object Link URL is encircled in red.

  • Now on clicking the Disbursement Request it would redirect us to Yahoo Home Page as shown in the screenshot below

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply