If you create a project with multiple input entities, only one of the entities will be mapped to the output schema in the Schema Editor. For example, if you have two input entities, Usinput(34) and Upinput2(182), only the attributes of the first input, Usinput (34), are initially mapped to the output.
Therefore all other input entities must be mapped to this output schema. There are two ways to do this. Both methods can be used for single or multiple input entities.
Guidelines:
- If you use an output entity from a Quality process as input to your project, do not insert the system-defined attributes Source ID and Sequence Number into your output schema. These attributes are automatically generated in the output schema and should not be duplicated.
- Be careful of the order of mapping for the following scenario: Input 1 has attributes A and B, Input 2 has attribute A and you want to create an output attribute C that contains B from Input 1 and A from Input 2. The results will be the same in both batch and the Control Center, as long as you map A before B (and give them both the length of the longer attribute), so that A from Input 1 is overwritten by B from Input 1. If you map B before A then, in the batch output, B from Input 1 will be overwritten by A from Input 1. The problem does not occur in the Control Center because the attribute names include the entity number but in batch the entity numbers are removed.
Method 1: Insert input attributes into output
One way of mapping is to insert the attributes in the output schema.
Method 2: Redefine input attributes to output as sub-attributes
The other way of mapping is to redefine the attributes as sub-attributes (synonyms)