Use Case Overview
This Use Case would help you jumpstart solution development for a Adeptia Solution developer with basic knowledge of ETL.
ETL is the most common integration pattern where the key requirement is to pull or receive data from a source system or a file and perform the necessary transformation and deliver to a target system or file.
This document will outline the key steps to very quickly setup an ETL based transformation
Scope of Use Case
Applicable Scenarios
- This use case is applicable for any simple ETL use case for source and target systems supported by the product..
- Uses out of the box pre-built Data Integration Flow.
- Transactions using this template is meant to be used bu internal Business users.
Excluded Scenarios
- Not recommended for partner self-service.
- Post processing and complex mapping requirements.
Pre-requisites
Following are the pre-requisites to implementing the B2B use case:
- Input schema and type of source data (file in this case ). The most common types are XML, Excel, CSV, JSON, Text, Database
- Source Type – File or LAN location in this example
- Target schema and type. The most common types are XML, Excel, CSV, JSON, Text, Database.
- Target Type - File or LAN location in this example.