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 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 of schemas 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.

Image Modified
Figure 196: Process For Data Conversion Using Schema

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 SchemaWord Schema
• /wiki/spaces/AS/pages/5312787
• XML Schema
• XML Validator
• EDI Schema

...

These methods may vary across different schemas. Their compatibility with the schemas are outlined in the table below.

Anchor
_Toc208651148 _Toc208651148

Anchor
_Toc315880721 _Toc315880721

Table 1: Definition File Methods Used for Creating Schemas

Anchor
usingdatafile usingdatafile

Anchor
_Hlt185500653 _Hlt185500653

Using Data File
A data file contains the actual data which we use as source or target during the execution of a process flow. It can be the same file that is used in the process flow or another sample file of same format.

Anchor
usingfieldfile usingfieldfile

Anchor
_Hlt185500657 _Hlt185500657

Using Field File
A field file is a Comma Separated Values (CSV) file that contains the name of the fields and their definitions which are separated by comma. This option is helpful in case the number of fields in the source or target data file is very large. All the field names are picked up from this CSV file. If the data type is Date then, format of the date must be specified after the data type, separated by comma.

...

Info
In case a field is defined as Date or Time type and their format is not defined then, the default date format will be MM/dd/yy and time format will be blank. When copying a field file, you need to verify that the field format is correct and there are no extra lines in that document. Else, the schema will generate an error while converting it to HTML.

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:

...

Anchor
defintionfile_EDIschema defintionfile_EDIschema

where: L means left alignment
R means right alignment
T means True
F means False

Anchor
fieldlength fieldlength

Field File format for Advance Positional Schema based on Field Length
<RecordIdentifier Value>,<FieldName>,<Description>,<DataType>,[DateFormat],[TimeFormat],<Length>,<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:

...

where: L means left alignment
R means right alignment
T means True
F means False

Anchor
usingXSDfile usingXSDfile

Using XSD File
The XML Schema Definition (XSD) file describes the elements in an XML document. The XSD file that you will use to create a schema must be compliant to the Adeptia-Suite's format. To get an Adeptia-Suite compliant XSD file, you can edit any existing schema and download its XSD file. You can also edit the fields in that XSD file and use it to create the schema. For example, you have created a schema of 100 fields and you want to create another schema of only 90 fields by using the existing 100 field schema. You can download the XSD file of the existing schema, delete 10 additional field by editing the XSD file, and use that XSD file to create another schema of just 90 fields.

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):

Image Modified

...

Figure 209: Excel Schema Example

The corresponding data file of the excel schema is shown in the figure (see Figure 210):

Image Modified

...

...

Figure 210: Data File Example

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, how to handle these error records, refer to the Handling Error Records section.