Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from horacio zapettini on Dec 21 at 12:31 PM Bob,
I think this is a definition that should come from your functional analyst.
If I had to solve that, I'd schedule the SP execution in the RDBMS (and I WOULD NOT execute the SP from SAP). That would ensure the Recordset generation once and at a given time and that info would always be available to my programs (without having to wait for the finish of those SP).
If the previous idea is not possible, then I'd go for a change in the SP. I'd save the status (start date and time, end date and time, times launched, ..., caller program, caller server, ...) and I'd evaluate that status from the program before launching each SP execution.
But as said, it's something your functional analyst must define. Not an ABAP issue.
HTH
horacio
| | | ---------------Original Message---------------
From: Bob Sonntag
Sent: Wednesday, December 21, 2011 11:18 AM
Subject: ABAP Detection of Process Chain Execution in Another SAP Environment?
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. __.____._ |   _.____.__ |
