I want to call an existing procedure and store its table-typed `OUT` parameters to new physical tables, without having to repeat the definitions of the output types when creating the new tables. For example, if the procedure were

```
CREATE PROCEDURE MYPROC
     (IN X INTEGER, OUT Y TABLE(A INTEGER, B DOUBLE, C NVARCHAR(25)))
LANGUAGE SQLSCRIPT AS BEGIN
...
END;

```

I would want to create a physical table for the output without repeating the `(A INTEGER, B DOUBLE, C NVARCHAR(25))` part.

If I already had a table with the structure I want my result to have, I could `CREATE TABLE MY_OUTPUT LIKE EXISTING_TABLE`, but I don't.

If I already had a named type defined for the procedure's output type, I could create my table based on that type, but I don't.

If it were a subquery instead of a procedure output parameter, I could `CREATE TABLE MY_OUTPUT AS (<subquery>)`, but it's not a subquery, and I don't know how to express it as a subquery. Also, there could be multiple output parameters, and I don't know how you'd make this work with multiple output parameters.

In my specific case, the functions come from the [SAP HANA Predictive Analysis Library](https://help.sap.com/viewer/2cfbc5cf2bc14f028cfbe2a2bba60a50/2.0.02/en-US/c9eeed704f3f4ec39441434db8a874ad.html), so I don't have the option of changing how the functions are defined. Additionally, I suspect that PAL's unusually flexible handling of parameter types might prevent me from using solutions that would work for ordinary SQLScript procedures, but I'm still interested in solutions that would work for regular procedures, even if they fail on PAL.

Is there a way to do this?