Jaiswal, We are first going to that "a lot of dogs are called Max, but not every dog is called Max". It is important at every step to know at what environment SAS-metadata or Windows-server (where your appservers are running) something is happening. SAS-folders  Windows-folders   SAS-explorer Windows-explorer all is confusing like Max.          step 2 This is the SAS environment. Your SAS platform admin could have defined different namings for you as "shared" is shared with ... and must be managed. step  4 The source-code-repository that is in reality become a pointer to a Windows-folder. If this pointer does not exist yet than you have to create one.    That creating is missing in your references. It is needed once for every Windows-folder you are putting the code in. There is also an "Add" button when you have the options of the source-code-repository use that.. SAS(R) 9.4 Stored Processes: Developer's Guide (example step 3) it is behind the manage button (here a C:\ Windows folder) http://support.sas.com/resources/papers/proceedings11/050-2011.pdf   you see an example where the installation path of SAS (Unix) is used, confusing as SAS is having the same naming conventions. Remember that you must select a location on the Windows-server that is accessible to the SAS app-servers (you?). When you have remote access to the Windows-Server you could use the Windows explorer for that. Change your question of cannot find "Shared Data" to "at wich location on the Windows Server my source may be placed". I assume the contentserver of the midtier with (9.3 9.4 is used for storing files in the metadata with 9.3 and up. Metadata source code storage in 9.3 stored processes - Real BI for Real Users the refreshing is another attention point.  51735 - A large SAS® Stored Process source-code file might be truncated when it is executed if it is stored in metadata   ... View more