Content Comparison

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 apprehends data 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

Types of Schema Activities
Adeptia Suite provides the following type of schema activities:

• Advance Database Schema
• Advance Positional Schema
• Advance Text Schema
• Database Schema
• Excel Schema
• Positional Schema
• Text Schema
• /wiki/spaces/AS/pages/5312787
• XML Schema
• XML Validator
• EDI Schema

Adeptia Suite allows you to create schemas schema in two ways:

• Using Definition File
• Entering the 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:

...

Anchor
definitionfile_advpositionalschema definitionfile_advpositionalschema

Field File format for Advance Positional Schema
The Field file format for Advance Positional Schema can be of two types:

• Based on Start Position and End Position
• Based on Field Length

Field File format for Advance Positional Schema based on Start and End Position
<Record Identifier1>:<Value>,<Record Identifier2>:<Value>
<RecordIdentifier Value>,<FieldName>,<Description>,<DataType>,[DateFormat],[TimeFormat],<Start
Position>,<EndPosition>,<Alignment>,<Skip>
In case of Advance Positional Schema, Record Identifier, and Value should be specified at the beginning of the CSV file as displayed below:

...

Entering Fields Sequentially
This is a manual way of creating a schema. If you select this option, you will then have to manually enter the field's name and their data type in the correct sequence.
When creating a schema (except XML schema), the schema automatically creates a Record Number attribute at the record level. It is available for each record. If you use a schema at the source level, then the schema will populate this attribute in the intermediate XML file at the record level. The Record Number attribute always starts at 1. If the schema detects an error, then it will generate this attribute in the Error File. For example, if an error is found at record number 5 in the source file, then the Error File will display Record Number 5.

Error Records
On execution of a process flow, there is a possibility that some of the records in the source file are not according to the schema definition. The schema treats them as error records when the schema parses the source data. Consider an excel schema whose field format is as shown in the figure (see Figure 209):

...

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: