---
title: "Full Generation"
canonical: "https://docs.vaultspeed.com/space/VPD/3013378064/Full%20Generation"
format: markdown
---
Navigate to the **DDL/ETL Generation **menu and** **click on **Generation.**
> 📝 Make sure you have defined your ODI/Talend Settings(when needed) before generating any ETL/ELT Code!
In the **Full Generation** submenu, you can generate **All** DDL and/or ELT code.
Select the desired settings from the drop-down Lists:
- **Project**
- **Data Vault**
- **Data Vault Release **(latest one is selected by default)
- **Business Vault Release **(latest one is selected by default)
If you want to filter for which objects in a specific source, data vault, or object you want the generation to run, you can use the following elements on this interface:
- **Layer**: Select a layer; this determines on which layer the objects can be selected in the object dropdown.
- When selecting Source, the object contains the source object names
- When selecting Data Vault, the object list contains the raw data vault object names
- When selecting Business Vault, the object list contains the Business Vault objects
- **Source**: Use the source selection to limit visible objects in the object list. Select ALL to include objects from all sources.
You can select a specific source only if the "source" or "Data Vault" layer is chosen.
- **Object**:** **Select a specific object to limit code generation to that object. The dropdown content depends on the choices in “Layer” and “Source.” Use multi-select to choose objects filtered by these settings. Use the “All” indicator to select or deselect the entire list, and the toggle box next to each object to select it.
- If a source object is selected, then all the code to load the resulting Data Vault objects will be generated.
- If a Data Vault object is selected, all the code to load it will be generated. This can be further limited by specifying a source as well (see example below).
- If a Business object is selected, then only the code for that object will be generated.
> 📝 Be aware that, when you start using the multi-select of entities, this principle doesn’t take into account dependencies that exist between entities.
> 📝
> 📝 Using the multi-select to mimic delta generations is strongly discouraged.
> 📝
> 📝 You can use this functionality only when you are 100% sure about the dependencies of objects and the content of the code base you are creating.
Specific settings for the code base that will be generated
- **ETL Generation Type**: Depending on the Database Type, different ETL Generation Types can be available. For e.g. choose one of the following for an Oracle DataBase: Oracle ODI Groovy, Oracle SQL, or Talend JobScript Oracle.
- **Load Type**: Choose either INCR (Incremental), INIT (Initial Load), VIEWS (only the views: BV, and firewall/delta), DDL (only for Spark and ODI), or ALL (both) to generate a specific type of Code.
After all of the above Selections have been made, a number of Buttons will appear:
To start the generation of DDL and/or ETL Code, click on the appropriate Button(s):
If a specific layer or object is selected, then some of these might not be available.
Generate DDL
- **ALL**: All DDL Code is generated.
- **Remote SRC: **DDL Code for the remote loading window table.
- **INI**: DDL Code for the Initial load tables is generated (if needed by parameter setting)
- **CDC**: DDL Code for the Change Data Capture tables is generated (if needed by parameter setting)
- **SRC**: DDL Code for metadata tables and delta/firewall tables (if needed) is generated.
- **EXT**: DDL Code for Extraction Layer is generated.
- **STG**: DDL Code for Staging Layer is generated.
- **DV**: DDL Code for Data Vault Layer is generated.
- **BV**: DDL Code for Business Vault Layer is generated.
Generate ETL
- **ALL**: All ETL Code is generated.
- **Remote SRC:** ETL Code for the remote loading window table.
- **SRC**: ETL Code for Source Layer is generated (delta & firewall views/mappings).
- **EXT**: ETL Code for Extraction Layer is generated.
- **STG**: ETL Code for Staging Layer is generated.
- **STG DL**: ETL Code for Staging Layer (Many-to-Many Links) is generated.
- **HUB**: ETL Code for Hubs is generated.
- **SAT**: ETL Code for Hub Satellites is generated.
- **REF: **ETL Code for Reference objects is generated
- **LNK**: ETL Code for Links is generated.
- **LKS**: ETL Code for Link Satellites is generated.
- **LND**: ETL Code for Many-to-Many Links is generated.
- **NHL: **ETL Code for Non-Historized Links is generated.
- **LDS**: ETL Code for Many-to-Many Link Satellites is generated.
- **RTS: **ETL Code for Record Tracking Satellites is generated.
- **BV**: ETL Code for Business Vault Layer is generated (PITs, BRIDGES, and Business views).
- **LNA**: ETL Code for Links across sources is generated.
- **LAS**: ETL Code for satellites on Links across sources is generated.
Clicking on one of the buttons will launch a set of tasks. These tasks will generate the requested code, and the VaultSpeed Agent will then download it to your designated location.
By default, the generated code will be downloaded to the "generated_files" folder of your agent.
If you changed the folder in the variable ‘path.in’ in the ‘client.properties’ file on the agent, the files can be found in the specified path instead.
You will find a Zip file named ‘_DDL.zip’ (contains only DDL Code), ‘_GENERATE_ETL.zip’ (contains only ETL Code) where ‘’ is the Identifier (Sequence) for a certain code generation ( the most recent generation will have the largest Id).
To deploy the generated Code, see [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011248154](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011248154).