Steps to reproduce the issue:

1) Connect to Teradata server.
2) Execute the following scripts on QA:

CREATE TABLE MACRO_SALARY1(
  empid INTEGER NOT NULL,
   NetPay INTEGER
)
GO
CM MACRO_TAB2(empid INTEGER NOT NULL) AS (
SELECT empid,NetPay FROM MACRO_SALARY1 WHERE empid = empid;
)
GO

3) Now, generate CREATE script from ADS UI of the macros  'MACRO_TAB2' object created above.

Actual result: Script is not generated, only statement separator ('GO') is generated. Please refer screenshot.

Expected result: Complete script of macros should be generated as follows:

CM MACRO_TAB2(empid INTEGER NOT NULL) AS (
SELECT empid,NetPay FROM MACRO_SALARY1 WHERE empid = empid;
)
GO

Observations: 
- Same behaviour is observed in V18.

- Also, In Schema Compare it shows an "Error generating DDL".But if you execute SQL fired on SQL Log, you can see that information of that macro is extracted. Please refer attached sql file for query and screenshot.

- Script is not generated when we use 'CM' to create Macros instead of 'CREATE MACRO'. If Macros are created using 'CREATE MACRO' than correct script is generated by ADS. Please refer screenshot.

logging this issue based on the discussions on VA #10097.