Hi Daniel,
The mapper only lists tables and views so there is no way to configure a BO to match the output of the GetX proc.
Right now that is the case, though before 1.4.1 becomes a complete version, we should be able to map a business object to a stored procedure.
There are properties of the BO like InsertStoredProcedureName, UpdateStoredProcedureName and DeleteStoreProcedureName but no documentation on how to use them. There is no property like SelectStoredProcedureName.
The Insert-, Update-, and DeleteStoredProcedureName properties are used to map the business object to the stored procedures generated by the DDT for INSERTs, UPDATEs, and DELETEs. If you want to fill a business off of a stored procedure, then you'll need to call the FillByStoredProcedure method. If we added a SelectStoredProcedure, it would be unnecessary with the FillByStoredProcedure() method, and would be limited because you often use more than one stored procedure to fill a business object.
The DDT says it will "auto generate" some stored procs but the details of what will be generated are not documented, and this generation presumably does not happen until you deploy, so it's difficult to see how one could develop towards it.
It has been slated to allow you to "view" the code generated by a DDT stored procedure within the DDT itself. That should also happen before 1.4.1 goes official.
There are probably other questions that I should ask but I don't have enough info to even do that.
Well, when you come up with those questions, let me know