Anchor |
---|
| _Toc240804619 |
---|
| _Toc240804619 |
---|
|
Anchor |
---|
| _Toc293928957 |
---|
| _Toc293928957 |
---|
|
Anchor |
---|
| _Viewing_EDI_Logs |
---|
| _Viewing_EDI_Logs |
---|
|
You can use
a schema to parse data from all the supported data type formats and transform it into any of the supported data types. What
a schema actually does is that, it reads the data from the source, transforms it into XML, and then commits it to the source in the requested format. If you want data transformation then you need to use different
types type of
schemas schema both at the source and target end of your Process
flow. Please see the figure (see Figure 196) to get more information on how a schema works....
Flow.
The working of schema is depicted in the below diagram.
Image Added
Business Example
Your organization has asked you to compile all the information, that is saved on a common server, about their inactive users and convert it into database entries which they will use for archiving. Your job is to fetch all the relevant data from this stack of information and convert it into acceptable database entries. For this reason you need the following knowledge:
- An understanding of fetching data from different file types
- An understanding of converting that fetched data into target file format
...
Adeptia Suite allows you to create schemas schema in two ways:
- Using Definition File
- Entering Fields Sequentially
Anchor |
---|
| usingdefinitionfile |
---|
| usingdefinitionfile |
---|
|
Anchor |
---|
| _Hlt185610484 |
---|
| _Hlt185610484 |
---|
|
Anchor |
---|
| _Hlt239858252 |
---|
| _Hlt239858252 |
---|
|
Using Definition File You can create a schema using a Definition File in three ways:
...
As you can note that in the schema definition, the data type of the Account_Number field is Number. However, in the source data file, there are two records where the Account_Number field contains a string data type. Now, when the schema will parse this file, the data for these two records will not match as per the schema definition and hence these two records will be treated as error records.
Similarly when you use a schema at the target side then also the schema can generate error records.
In this scenario, you may want to handle these error records as per your requirement. You can do this while creating the Process Flow, where you will be actually using this schema.
Info |
---|
To know, For information on how to handle these error records, refer to the Handling Error Records sectionHandling Error Records. |
Following are the major subsections:
Section Name | Description |
---|
Advance Database Schema | Introduces Advance Database Schema concept. Instructions to create Advance Database Schema and to enable RollBackOn Error attribute are also provided. |
Advance Positional Schema | Introduces Advance Positional Schema concept. Instructions to create Advance Positional Schema, use hierarchy at root level, use record at child level, define field positions non-sequentially, and view print page are also provided. |
Advance Text Schema | Introduces Advance Text Schema concept. Instructions to create Advance Text Schema and use record at child level are also provided. |
Database Schema | Introduces Database Schema concept. Instructions to create Database Schema are also provided. |
Excel Schema | Introduces Excel Schema concept. |
Positional Schema | Introduces Positional Schema concept. Instructions to create Positional Schema are also provided. |
Text Schema | Introduces Text Schema concept. Instructions to create Text Schema are also provided. |
XML Schema | Introduces XML Schema concept. Instructions to create XML Schema and to use Easy Schema Parser for Existing XML Schema Activity are also provided. |
JSON Schema | Introduces JSON Schema concept. Instructions to create JSON Schema are also provided. |
XML Validator | Introduces XML Validator concept. Instructions to create XML Validator are also provided. |
EDI Schema | Introduces EDI Schema concept. Instructions to create EDI Schema are also provided. |
Testing Schema | Learn how to test the schema. |