M5 - Work with data management in f&o apps Flashcards
In what concepts does the management framework consists of?
- Data entities
- Data project
- Data job
- Job history
- Data package
What is a data entity?
A conceptual abstraction and encapsulation of one or more underlying tables.
What are data entities intended for?
Use them to define import/export packages or for integrations.
What is a data project?
Is automatically created when you select Import or Export from the workspace and should have at least one job.
Contains configurated data entities, which include mapping and default processing that is used for each entity.
What is a data project used for?
Allows users to set up the entities that should be part of the project and defines the format that is used for each entity.
Also, allows to define the mapping that is used from the source file to the staging and to specify the default processing options.
What is a data job?
Performs the actual import or export operation.
Contains an execution instance of the data project, uploaded files, the schedule or recurrence information, and the processing options to use for the job.
What is the job history?
History of the source to staging and staging to target jobs.
Contains the run history for each execution of the data job and the history of the data move.
Where is the job history located?
In the data management workspace.
What does the job history show?
- run job time
- number of records processed
- errors that occurred during processing
What is a data package?
Is a single compressed file that contains a data project manifest and data files.
Where is a data package generated from?
From a data job.
What is a data package used for?
For the importing or exporting of multiple files with the manifest.
What is the manifest of a data package?
Defines the settings of the data project.
What does the downloadable zip file of a data package contain?
The package header and manifest
What is the framework that can quickly help you migrate data?
The data management framework
The data management framework supports using data entities in the following core data management scenarios:
- Data migration – You can migrate reference, master, and document data from legacy or external systems.
- Set up and copy configurations – Use this scenario to copy configurations between companies or environments and set up processes or modules by using the Lifecycle Services environment.
- Integration – Use this scenario when you need real-time, service-based integration or when you need an asynchronous integration. The real-time integration doesn’t have a staging area and is directly processed by the services layer.
What is data migration?
Is an initial or unplanned data load that you can perform manually by using the user interface.
What data strategy is used in the following scenario:
A functional user has some data in a source, such as an Excel workbook that needs to be imported from a legacy system to f&o apps during data migration.
Data migration
What is the primary mechanism for exporting and importing data packages in ALM and demo data scenarios?
Data entities.
Categories of entities:
- Parameters
- Reference
- Master
- Document
- Transactions
Type of entity:
Required to set up a deployment or a module for a specific build or customer.
Parameter
Type of entity:
Simple reference data, of small quantity, that is required to operate a business process.
Reference
Type of entity:
Data assets of the business. Complex reference data, of large quantity.
Master
Type of entity:
Worksheet data that is converted into transactions later.
The operational data of the business.
Document