3.5. AUTORIDADES ESTATALES COMPETENTES EN MATERIA AMBIENTAL
3.5.1. Protectora de Bosques del Estado de México (PROBOSQUE)
Allows for maintaining older versions of rows when a change occurs by generating new rows in a target. The operation converts rows flagged as UPDATE to UPDATE plus INSERT, so that the original values are preserved in the target. You will specify the columns that might have updated data. Additionally, the settings of the operation can also result in DELETE rows being converted to UPDATE rows.
This operation requires that a Table Comparison operation also be present upstream in the processing flow.
Note
The input to the History Preserving node cannot contain any LOBs, text, or shorttext attributes, even if they are not in the list of attributes being compared.
Note
The History Preserving node is available for real-time processing.
Table 69: Parameters
Parameter Description
Name The name for the output target for the history preserving operation.
Display Name The name shown in the Palette pane.
Note
This option can only be changed when creating a template. It cannot be changed when us ing the node outside of a template.
Description (Optional.) Provides a comment about the operation. For example, "Preserving previous cus tomer sales."
Date Attributes Sets the parameters for the duration the date is valid.
Current Flag Sets the current flag for the attribute, set value, and reset value. A column from the source schema that identifies the current valid row from a set of rows with the same primary key. You can indicate whether a row is the most current data in the warehouse for a given primary key when using this flag.
The Current Flag column cannot be the same value as the Valid From or Valid To date columns.
Update Attributes on Deletion
Parameter Description
Compare Attributes Provides the compare attributes and the primary key of the compare attributes. You can Add or Remove attributes, or move an attribute Up or Down in the list.
Mappings
The mappings tab shows how the input column names are mapped to output column names. If you have a large table, you can use Filter pattern to search for specific columns. See "Using the Mapping Editor" topic in the SAP HANA Developer Guide.
Input data
Select the input data General tab by clicking Input_<n>.
Table 70: General
Option Description
Name The name of the input source. You can rename this source.
Kind Identifies the type of input source, For example, table, column, scalar. Table 71: Signature
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be blank.
Use the Add, Remove, Up and Down buttons to edit the input fields accordingly.
Table 72: Fixed Content
Option Description
Fixed Content Enable to have the input table of the node saved with the flowgraph file. Otherwise, it is placed in a separate table connected to the node. For more information, see the SAP HANA Developer
Output data
Only one data target is allowed.
Select the output data General tab by clicking Output_<n>.
Table 73: General
Option Description
Name The name of the output source. You can rename this source.
Kind Identifies the type of output source. Table 74: Signature
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be null.
Use the Add, Remove, Up and Down buttons to edit the input fields accordingly.
Annotations
Create comments for users. For example, you might want to make a note of some particular settings in this flowgraph so that the administrator can schedule or understand certain customizations. The annotations are written to a table. See the "Application Function Modeler" section of the SAP HANA Developer Guide.
All
Shows all of the options in one screen. It includes, General, Mappings, and Annotations.
5.14 Input Type
Input Type is used to set parameters for use in the data source tables when the flowgraph is activated.
Before using the Input Type node, you must have an existing table or table type created. You can create an input table type in application function modeler within SAP HANA Studio.
Use Input Type node to specify the physical table at run time and make it more flexible by setting parameters. The schema of the input tables must match the schema of Input Type.
General Properties
Option Description
Kind Table: Cannot be changed.
Real-time behavior Choose to run as real-time or batch processing. When selecting to run as a real time process, then you must select a Reference Virtual Table.
Note
When choosing real-time processing, you must use the Output Type node. When using batch processing, you can use the Output Type node, the Data Sink node, or the Template Table node.
Reference Virtual Table Browse to the schema and select the table name. Only used when Real-time behavior is selected.
When executing the flowgraph, you are prompted with the Table Type Parameters window to specify the physical table name. The schema of the input table type and the physical table must match.
Example
Let's say that you have many employee tables. The tables are listed by department and all of the schemas are the same with the same columns for employee names, addresses, ID numbers, and so on. You want to replicate the tables from one system and place them into another, and also to cleanse the data in the process. You can use Input Type to pull the tables into one flowgraph by calling the individual tables at run time, whereas if you used the Data Source node, you would have to run a separate flowgraph for each department.
Related Information
5.15 Join
A Join node represents a relational multi-way join operation.
Prerequisites
You have added a Join node to the flowgraph.
Note
The Join node is not available for real-time processing.
Context
The Join node can perform multiple step joins on two or more inputs.
Procedure
1. Select the Join node.
2. (Optional) Add additional input anchors.
3. (Optional) Remove any output columns by clicking the pencil icon or the trash icon, respectively. You can multi-select the columns that you do not want output by using the CTRL or Shift key, and then Delete.
4. In the Properties view, select the General tab to configure the type of the join (inner join, left outer join, or right outer join).
5. In the table defined in the General tab, use the Table Editor to define the Left join partner, the Join Type, the Right join partner and the Join Condition of each join step. In this, only the first entry in the join condition consists of a Left join partner and a Right join partner. Every subsequent join condition has the previous join tree as Left join partner.
The Expression Editor opens and lets you specify the Join Condition.
5.15.1 Join Options
Description of options for the Join node.Option Description
Name The name for the node.
Display Name
Note
AFM only.
The name shown in the Palette pane.
Note
This option can only be changed when creating a template. It cannot be changed when using the node outside of a template.
Description
Note
AFM only.
(Optional.) Provides a comment about the node. For example, "Employee_v8 and Employee_v12."
Left The left source of a join.
Join Type Choose from one of these options:
Inner: use when each record in the two tables has matching records.
Left_Outer: output all records in the left table, even when the join condition does not match any records in the right table.
Right_Outer: output all records in the right table, even when the join condition does not match any records in the left table.
Right The right source of a join.
Join Condition The expression that specifies the criteria of the join condition.
Note
In AFM, you can use the Expression Editor to assist in creating the expression.
Add A join condition is created.
5.16 Lookup
Retrieves a column value or values from a Lookup table that match a lookup condition you define. In addition to returning the values from the Lookup table, you can also do the following:
● Specify lookup table column and sort value pairs to invoke a sort which selects a single lookup table row when multiple rows are returned.
● Configure default values in the form of constants to be output when no Lookup table rows are returned.
Note
The Lookup node is available for real-time processing.
General properties
Table 75: General options
Option Description
Name The name for the output target. This can be named the same as the input source.
Display name The name shown in the Palette pane.
Note
This option can only be changed when creating a template. It cannot be changed when us ing the node outside of a template.
Description (Optional.) Provides a comment about the operation. For example, "Lookup ISO9001 codes."
Lookup Table The table or file that contains the result or value that you are looking up.
Lookup Condition The expression value that the function searches for in the column to be compared.
Lookup Attributes Provides the Name, Type, Mapped Value, and Default Value for the attributes. If the lookup doesn't return any results, you can specify a default value. The Name attribute is the name of the lookup table column for which the default is specified in the output. The Mapped Name at tribute is the default value for the respective attribute name. You can Add or Remove attrib utes, or move an attribute Up or Down in the list.
Sort Attributes Provides the Name and Sort Order of the sort attributes. When more than one row is returned as the result of Lookup, one or more Lookup table input attributes and sort direction pairs can be specified to sort the rows. The first row evaluated as a result of the sort will be the row whose column values are returned for the lookup. Specify the direction with either descending or ascending. You can Add or Remove attributes, or move an attribute Up or Down in the list.
Mappings
The mappings tab shows how the input column names are mapped to output column names. If you have a large table, you can use Filter pattern to search for specific columns. See "Using the Mapping Editor" topic in the SAP HANA Developer Guide.
Input Data
Only one data source is allowed and this element is required.
Table 76: Required parameters
Parameter Description
Name The name of the input source. You can rename this source.
Kind Identifies the type of input source, For example, table, column, scalar. Table 77: Signature
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be null.
Use the Add, Remove, Up and Down buttons to edit the input fields accordingly.
Table 78: Fixed Content
Option Description
Fixed Content Enable to have the input table of the node saved with the flowgraph file. Otherwise, it is placed in a separate table connected to the node. For more information, see the SAP HANA Developer
Guide topic "Flowgraphs".
Output data
The operation creates a single output table.
Table 79: Required parameters
Parameter Description
Parameter Description
Kind Identifies the type of output target. Table 80: Required parameters
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be null.
Annotations
Create comments for users. For example, you might want to make a note of some particular settings in this flowgraph so that the administrator can schedule or understand certain customizations. The annotations are written to a table. See the "Application Function Modeler" section of the SAP HANA Developer Guide.
All
Shows all of the options in one screen. It includes General, Mappings, and Annotations.
5.17 Map Operation
Sorts input data and maps output data for UPDATE rows.
Typically, you'll use the Map Operation node as the last object before the target in the flowgraph. You should include a Table Comparison node prior to the Map Operation, or use this node in real time data provisioning.
Note
The Map Operation node is available for real-time processing.
General Properties
Table 81: General options
Option Description
Name The name for the output target. This can be named the same as the input source.
Display Name The name shown in the Palette pane.
Note
This option can only be changed when creating a template. It cannot be changed when us ing the node outside of a template.
Description (Optional.) Provides a comment about the operation. For example, "Map the UPDATE opera tion to an INSERT."
Mapping tab
Option Description
For Select the column that you want to use for the map operation.
Insert/Normal Mapping
Use the Expression Editor to create a SQL statement to perform the insert operation.
Update Mapping Use the Expression Editor to create a SQL statement to perform the update operation.
Delete Mapping Use the Expression Editor to create a SQL statement to perform the delete operation.
Map Operation tab
Specify the mapping for each input row type. For example, if you want to preserve the data that would be updated in a previous node, then you can change the UPDATE Input Row Type to INSERT. To accomplish this you would choose INSERT in the Output Row Type column.
Mappings
The mappings tab shows how the input column names are mapped to output column names. If you have a large table, you can use Filter pattern to search for specific columns. See "Using the Mapping Editor" topic in the SAP HANA Developer Guide.
Input data
Select the input data General tab by clicking Input_<n>.
Table 82: General
Option Description
Name The name of the input source. You can rename this source.
Table 83: Signature
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be null.
Use the Add, Remove, Up and Down buttons to edit the input fields accordingly.
Table 84: Fixed Content
Option Description
Fixed Content Enable to have the input table of the node saved with the flowgraph file. Otherwise, it is placed in a separate table connected to the node. For more information, see the SAP HANA Developer
Guide topic "Flowgraphs".
Output data
Only one data target is allowed.
Select the output data General tab by clicking Output_<n>.
Table 85: General
Option Description
Name The name of the output target. You can rename this target.
Kind Identifies the type of output target. Table 86: Signature
Option Description
Name The column name in the input source. This can be named the same as the output from the previous node.
Type The type of data contained in the column, for example, Nvarchar, Decimal, Date, and so on.
Length The number of characters allowed in the column.
Scale The number of digits to the right of the decimal point. This is used when the data type is a deci mal.
Nullable Indicates whether the column can be blank.
Annotations
Create comments for users. For example, you might want to make a note of some particular settings in this flowgraph so that the administrator can schedule or understand certain customizations. The annotations are written to a table. See the "Application Function Modeler" section of the SAP HANA Developer Guide.
All
Shows all of the options in one screen. It includes, General, Mappings, and Annotations.
5.18 Match
Identifies potentially duplicate (matching) records.
Note
This topic applies to the SAP HANA Web-based Development Workbench only.
Matching is the process of identifying potentially duplicate (matching) records. To prepare for matching, the software analyzes your data, identifies content types and match components, and then recommends match policies for your specific data. You can accept these recommended match policies or choose different match policies. You can also adjust match settings, which control special scenarios, such as matching on alternative forms of a name (John vs. Jonathan, for example).
You can perform matching on a single source or up to 10 sources at a time.