Post a Reply

Weblog: BI Process Chains with Dynamic System Command
Subject: Scenario Elaboration.
Date: 2008-05-15 05:20:14
From: Ryan QuackenbossBusiness Card
Response to: COMMAND IN PROCESS CHAIN

I can try...
Imagine you are building this process chain in the Development environment for transport through the landscape (I know it's tough), and this process chain needs to execute a command file that is located on a development file server. If you hard code the path to the file in system command, once you transport the process chain to your Q/A and Production system you will be forced to change the system command in the subsequent systems to point to their prospective file server.
Example:
Development file server MDSAP00
Q/A file server MQSAP00
Prod file server MPSAP00


If the parameter in system command contains the path to the dev file server...
\\mdsap00\folder1\folder2\filename.xxx and you transport this system command in the process chain, and you run that process chain in Q/A and Production without updating the path, the systems will run the file on the DEVELOPMENT server.
To get the file on the Q/A box to run, you will have to manually update the command parameter to point to the Q/A file server \\mqsap00\ect...


If your organization is like mine and periodically does a "Refresh" of the Q/A system (replace with a copy of production setup and data) then the Q/A box now has system commands that point to the Production file server. NOW you have to touch each and EVERY command to point it back to the Q/A file server.


Talk about pain in the arse.


Fix: replace the sever name with a variable that resolves to the server applicable to each environment.


Hope that clears up the scenario.
Quack

No Previous Message Previous Message Next Message No Next Message

SAP, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product, service names, trademarks and registered trademarks mentioned are the trademarks of their respective owners.