How to Maintain Transaction Launcher for Access to Shared Network Files

  • by Judy Hildebrandt, Senior Business Process Specialist, Suncor Energy
  • March 2, 2012
Walk through the steps a company took to set up the transaction launcher in its SAP CRM system so users can access other systems via their desktops.

My company keeps master files on a shared network drive file location. Employees can access these files via transaction launcher links from the SAP CRM system. Some examples of shared files are credit application forms and SAP CRM quick reference guides in Microsoft Word format.

SAP CRM users have read access to the files, while administrators are given read and write access so that they can periodically update the files. Users can link to these files from the SAP CRM WebClient UI or the SAP CRM Interaction Center (IC) WebClient UI, save them as another name, and then change them, but they cannot change the master in the SCPFILES location.

Below are the steps I follow to set up the launch to a shared file. I’m using our Inside Sales Training Guide for CRM as an example. While the transaction launcher functionality has been available from SAP CRM 4.0 onwards, this article assumes an SAP CRM 7.0 system.

Judy Hildebrandt

Judy Hildebrandt has worked at Suncor Energy (previously called Petro-Canada) for the past 24 years. She supports the SAP CRM Sales design and configuration at Suncor, with a sales force of 500+ users.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.