Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Question from Bob Sonntag on Dec 21 at 11:17 AM All,
I am in a shop that loads lots of non-SAP data into DSOs. We're doing that by running SQL Server stored procedures from ABAP programs to build tables of data and then loading the our DSOs from those tables.
Would like to build that data only once. Since we start in our Dev environment, the process chain gets built with the execution of the ABAP program to build the data. When we transport the process chain to QA, the ABAP program and its execution goes with it. Ditto for Production.
What's the best way to have the ABAP program detect the execution of the chain in another environment (say Prod) and then skip the rebuilding of the data?
IE: If Prod chain exists, then Prod builds the data; QA & Dev skip building the data.
If QA chain exists, then QA builds the data and Dev can skip building the data.
If the process chain is only in Dev, then Dev builds the data.
I think it's cleaner to not add a "DataBuilt" column to the collection process.
Ideas?
Bob
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
