Mass Export of Configuration Objects via API

Yes, the generic API function `XXEN_API.EXPORT_FILE_DATA` is designed to handle various object types beyond just reports . To export all templates, you would set the input parameter `p_type` to the value ‘Templates’ . This function returns a CLOB containing the XML definition of all template objects . Other supported non-report types include ‘LOVs’, ‘Assignments’, ‘Profile Option Values’, and ‘All Contents’ .

When exporting a subset of objects, you use the `p_ids` parameter, which is of type `fnd_table_of_number` . You must populate this collection (`l_ids`) with the unique ID numbers of the templates you wish to export . The `p_ids` parameter is applicable when `p_type` is set to ‘Reports’, ‘Templates’, ‘LOVs’, ‘Assignments’, or ‘SQLs’ .

The provided documentation does not explicitly state that the export API restricts data access based on the ‘Blitz Report Template Access’ profile option . The API is intended for administrative or developer use, suggesting it operates at a privileged level. Template access controls (No Access, Private only, Private and shared, Super User) are typically enforced through the user interface when accessing templates via the run window . You should ensure the user running the export script has the necessary privileges to extract all required data.

Yes, you can export previous SQL versions. You would set the `p_type` parameter in `XXEN_API.EXPORT_FILE_DATA` to ‘SQL Versions’ . This functionality is further refined by the optional parameter `p_creation_date`, which can be used to filter SQL versions based on when they were created , .