A data package typically consists of one-to-many data entities. A typical data package consists of a group of entities for a particular task, process, or function. For example, the data entities that are required for general ledger setup may be part of one data package. The format of a data package is a compressed file that contains a package manifest, a package header, and any additional files for the included data entities.

The following screenshot shows the content of a sample data package, which contains sample configuration data for the data validation checklist process:

In a typical implementation scenario, when you start to set up the initial configuration data, you create data packages with entities containing standard business data, sample data, and entities without any data. You can then decompress the package, use data spreadsheets to collect the business data, and compress them to create the final data package. You can import this data package into your environment to complete the initial set of configurations.

Data packages can be directly imported using the data management workspace or uploaded to the LCS asset library and applied to the same or another environment through the data configuration manager. These concepts will be covered in the next subsection.