I think what Rob is saying is that your actual SQL will be kept as a string in the list, along with the name of the service that you will use with that select to transform the selected data and the SQL string for inserting this transformed data into the target table. For example you can create an XML file that looks smth like this:
SELECT X, Y, Z FROM TAB WHERE C='VAL'
INSERT INTO TAR(R,T,Y) VALUES('VAL1','VAL2','VAL3')
SELECT X, Y, Z FROM TAB-A WHERE C='VAL'
INSERT INTO TAR-A(R,T,Y) VALUES('VAL1','VAL2','VAL3')
Now have your generic service read this xml into a documentList, loop over the document list and in each iteration,
- Use the stmtSelect string in a Dynamic Q template to select the data,
- Use the servTransform string to invoke the service that does the transformation and
- Use the stmtInsert string in another Dynamic Q Template to insert the data into the target table.
PS: Remember, the transform service can be blank (in cases where you don’t need the transformation at all) - in such cases you should skip the invoking transformation service.