1. Mapping variable value can be changeable through the session run.
2. Initially, it refers the default value set and its successful completion the integration service saves the value into repository.
3. At the beginning session again the integration service refers the final value from repository.
Today, we are going to discuss about a use case on splitting table record and pass it into target table 1 and 2 respectively.
Mapping Implementation.
1. Mapping #1
1. Define Mapping variable — RecCount default value 0
2. Source - EMP table
3. Aggregator - Output field (o_totalRecCnt) —COUNT(EMPNO)
4. Expression - Variable (setVar) —SETVARIABLE($$RecCount,o_totalRecCnt)
5. Target - STG_RAW table (dummy table to capture the EMP table record count).
2. Mapping #2
1. Define Mapping variable — RecCountNew default value 0
2. Source - EMP table
3. Sequence Generator to get running number
4. Expression - link sequence gen
5. Router — Create two groups Set_1 — first 50% records (NEXTVAL less than equal $$RecCountNew divide 2) / second 50% records (NEXTVAL greater $$RecCountNew divide 2)
6. Target 1 - STG_EMP_REC1 (link Set_1)
7. Target 2 - STG_EMP_REC1 (link Set_2)
3. Mapping Task / Session #1 - Mapping #1
4. Mapping Task / Session #2 - Mapping #2
5. Task Flow (Work flow)
1. Create Data Task 1 - Link Mapping Task #1
2. Create Data Task 2 - Link Mapping Task #2
3. Data Task 2 Properties - goto Input fields and assign RecCount Mapping variable to RecCountNew
4. Publish the Task flow and Run to complete the use case to verify target loaded as expected.
Source/Target files available at below Git link
[ Ссылка ]
