
Closed
Posted
Paid on delivery
I need an experienced Informatica PowerCenter developer to dive into one specific folder of mappings in our repository, break down every transformation, and explain exactly how each source field becomes its target value. That means capturing look-ups, filters, joins, default values—the full story, field by field. I will grant read-only access to the repository (or export XML if you prefer) plus any existing spec sheets so you can trace the logic. You may pull additional metadata through the XML export or the Repository Manager as needed; the goal is to translate that technical detail into clear, human-readable documentation and an easy-to-follow visual flow. Deliverables • Source-to-target mapping document for the selected folder, showing field lineage and transformation rules. • Lucidchart data-flow diagrams that mirror the mappings and highlight each major transformation, lookup, and conditional path. The work is considered complete when every target column in the chosen mappings has an accompanying lineage description and appears correctly in the Lucidchart diagram, with no unresolved “unknown” steps. Feel free to use whatever PowerCenter metadata extraction techniques you’re comfortable with, as long as the final outputs are accurate and ready to hand off to business analysts.
Project ID: 40789588
63 proposals
Remote project
Active 4 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
63 freelancers are bidding on average $129 USD for this job

Hi there, I understand you need complete, field-level lineage documentation for a selected Informatica PowerCenter folder, tracing every target column back to its source through lookups, joins, filters, expressions, defaults, and conditional logic. I’m confident I can turn the repository metadata into precise technical documentation and clear visual workflows that business analysts can follow without needing to interpret the mappings themselves. My approach is to first inspect the exported PowerCenter XML, mapping specifications, and repository metadata to inventory the selected mappings and identify all sources and targets. Next, I’ll trace each target field backward through every transformation, documenting source fields, lookup conditions, join keys, filter criteria, expression logic, default values, and data-type conversions. Then, I’ll validate the lineage against the mapping definitions and flag unresolved dependencies rather than making assumptions. Finally, I’ll cross-check every target column against both deliverables to ensure complete, consistent coverage. You’ll receive a maintainable handoff package with auditable field-level logic, traceable dependencies, and diagrams designed for both technical teams and business stakeholders. Could you share the approximate number of mappings in the folder and whether the XML exports include reusable transformations and mapplets? I’m ready to start immediately. Warm Regards, Aneesa.
$100 USD in 1 day
6.8
6.8

Hi there, I went through your project description and understand you need detailed source-to-target lineage documentation for a selected Informatica PowerCenter repository folder, including every transformation, lookup, filter, join, default value, and conditional rule affecting target fields. I will review the exported mapping XML or read-only repository metadata to trace each target column back through its source fields and intermediate transformations. I will document expression logic, lookup conditions, join criteria, filters, parameter dependencies, default values, and relevant branches, making each field’s derivation clear to both technical teams and business analysts. I will also create Lucidchart data-flow diagrams that reflect the actual mapping sequence, identify major transformation points, and connect the visual flow to the written lineage documentation. Where logic depends on external specifications or metadata that is unavailable, I will flag the exact dependency for clarification rather than assume its meaning. I will provide an initial repository review and documentation plan within 24 to 48 hours of project award. To scope your project clearly, approximately how many mappings are in the selected folder, and can you provide an XML export with the relevant source and target definitions? I look forward to helping you produce accurate, traceable documentation ready for handoff. Kind Regards, Imran Ali
$70 USD in 1 day
5.7
5.7

I can thoroughly document the selected Informatica PowerCenter folder, tracing every target column back through its source and transformation logic. I will review the repository or exported XML, analyze expressions, lookups, filters, joins, routers, defaults, and conditional paths, then produce clear source-to-target lineage documentation for business and technical stakeholders. Each target field will receive an explicit explanation, with unknown or ambiguous steps resolved through metadata inspection and cross-checking against available specifications. I will also create Lucidchart data-flow diagrams that accurately mirror the mappings and visually distinguish major transformations, lookup dependencies, and branching logic. The final package will be organized for easy handoff, review, maintenance, and future impact analysis, with completeness checked against every target column in the selected mappings. I’m ready to work from read-only repository access or XML exports, using the most reliable metadata extraction approach available.
$100 USD in 2 days
5.5
5.5

Hello, I am Vishruth from India, data engineer with 8+ years of experience and 132+ clients completed here. I have gone through your requirement. I prefer working from the XML export. I parse it with Python to pull out every connector, expression, lookup condition, filter, joiner and default value automatically, and then review each mapping manually so the logic is explained properly, not just copied. This makes sure no target column is skipped. Please share the parameter files and workflow XML as well, so nothing stays “unknown”.
$140 USD in 2 days
5.3
5.3

HELLO, You need someone who can take a dense Informatica PowerCenter folder and turn it into clean, business-friendly documentation without missing a single lookup, filter, join, default, or transformation rule—and that’s exactly the kind of mapping analysis I do best. I understand the goal here is not just to “document” the mappings, but to trace every target field back to its source with complete lineage, then present it in a way that business analysts and technical teams can both follow easily. I’ll go through the selected folder mapping by mapping, inspect each transformation, and translate the logic into clear source-to-target documentation plus visual flow diagrams in Lucidchart. I can work directly from repository access or XML exports, and I’m comfortable pulling extra metadata when needed to verify expressions, dependencies, and conditional paths. My approach is methodical: validate source fields, trace transformation logic, capture lookup/default/override behavior, and ensure every target column has a complete explanation with no gaps or “unknown” steps. You’ll get someone who communicates clearly, works carefully, and treats documentation as a deliverable that should actually be usable after handoff—not just technically correct. I also stay responsive throughout, so if any mapping logic needs clarification, I can flag it early instead of letting it become a problem later. Website: https://www.freelancer.com/u/Microlent If you’d like, open a chat and I can outline how I’d structure the lineage document and diagram flow for your Informatica folder. SINCERELY, RAJESH
$140 USD in 10 days
5.8
5.8

Hello, As a result of a detailed review of your project requirements, I fully understand your goal of documenting every Informatica PowerCenter mapping in the selected repository folder, including complete field-level lineage and visual data flows. I have experience with XML analysis, ETL workflows, data integration, and technical documentation, and I'm available to start your project right now. In my opinion, the key challenge is accurately tracing each target field through multiple transformations, especially when mappings contain nested lookups, expressions, filters, joins, and conditional logic. I'll analyze the PowerCenter XML exports and existing specifications, trace source-to-target dependencies, and document transformation rules, default values, and lookup conditions for every target column. I'll then create corresponding Lucidchart diagrams showing the major transformations and data paths, cross-checking them against the mapping documentation to identify any missing or ambiguous lineage. I'll preserve the original mapping logic and clearly flag any dependencies requiring additional metadata rather than making assumptions. I have one quick question. • Approximately how many mappings are included in the selected folder? I'd be glad to discuss the details and can start immediately. Best regards, Carlos.
$50 USD in 7 days
4.4
4.4

Hi, The XML export is the most dependable route, so I'd parse the exported mapping XML and trace each target column back through every transformation: source qualifier, expressions, lookups with their conditions and return ports, filters, joiners, routers and default values. That produces a source-to-target document per mapping with field-level lineage and each rule in plain language, with no step left as unknown. The Lucidchart diagrams would be generated from the same parsed metadata, so they match the document one to one, with lookups and conditional paths highlighted. Logic hidden in mapplets, reusable transformations or parameter files gets resolved and noted too. How many mappings are in the folder, and do they use mapplets or session-level overrides (SQL overrides, parameter files) that I should also receive?
$100 USD in 2 days
4.1
4.1

Hey there! We have completed 200+ projects with a 62-member team and 9+ years of experience. I can help turn your PowerCenter mappings into documentation that business analysts can follow, tracing each target column back through its sources and transformation logic. Here's how we can help: - Extract mapping metadata from repository access or exported XML. - Document field-level lineage, lookups, joins, filters, defaults, and expressions. - Explain conditional paths and transformation dependencies. - Build Lucidchart diagrams that mirror the actual mapping flows. - Cross-check every target column and flag unresolved logic before handover. I’d start with a representative mapping to validate the documentation format, then apply it consistently across the selected folder. Approximately how many mappings and target tables are included in the folder?
$140 USD in 7 days
4.1
4.1

Hi, Sara here, from Serbia. What matters most in building your document Informatica mapping logic is numbers people trust and use to make decisions. I'm a senior software developer with 6+ years of experience working with projects like this. For your document Informatica mapping logic, the real challenge is clean data and clear definitions. A common issue: building visuals before agreeing how each number is calculated, so reports disagree. My plan: first, agree each metric, its definition and its data source. Then, clean and model the data, and build the report pages in the BI tool. Finally, check totals against the source and set up scheduled refresh. I'd start with the main dashboard pages as phase one. I've done reporting work before, so I check early for totals that do not match the source. A few questions to better understand the scope: 1. Does the data include personal details? Then I set row-level access, so each viewer sees only their part. 2. Scheduled refresh instead of live queries? I'd recommend scheduled, faster pages and less load on the source. 3. Are the dashboards shown to your own clients? Client-facing reports need their branding and strict access rules. I can start right away. Happy to go over the details here in chat and suggest the best approach. Looking forward to hearing from you, Sara
$177 USD in 2 days
3.4
3.4

I can document every target column in your chosen PowerCenter folder as a field-by-field lineage sheet, with a data-flow diagram for each mapping. The XML shows each mapping, but session overrides and parameter files often decide what a target really receives, so I would read those alongside it. Working order for the folder: 1. Export the folder to XML and pull the session overrides and parameter files that go with those mappings. 2. Trace every lookup, filter and default value first, since that is where a target gets a value nobody expects. 3. Write the lineage sheet, one row per target column, with the rule behind each value. 4. Draw the data-flow diagram for each mapping, with lookups and conditional paths marked, so your analysts can rebuild them in Lucidchart. - 25 USD for the export and the lineage sheet of your first mapping, by the end of the first day - 55 USD for the other mappings and diagrams, once every target column in the folder has a lineage row Check the first mapping's sheet against Repository Manager before you pay the rest. I am available to start this week.
$80 USD in 3 days
3.4
3.4

Hello! I can help document your Informatica PowerCenter mappings by tracing source-to-target lineage, including lookups, joins, filters, defaults, and conditional transformation logic. I’ll organize the findings into a clear field-by-field mapping document and create Lucidchart data-flow diagrams that show each transformation and decision path. My focus will be on accurate, complete documentation, with every target column explained and any unresolved logic clearly investigated before handoff to your business analysts.
$180 USD in 2 days
3.0
3.0

-**High-Quality work, Fast delivery, and results you can TRUST**-- Building your document Informatica mapping logic is doable. I'm a senior software developer with 8+ years of experience working with Data Visualization and Data Analysis. For your document Informatica mapping logic, the real challenge is clean data and clear definitions. My plan: first, define metrics and sources. Then, model data, build pages. Finally, check totals and refresh. I'd start with the main dashboard pages as phase one. I've done reporting work before. A few questions to better understand the scope: 1. Does the data include personal details? Then row-level access limits what each viewer sees. 2. Scheduled refresh instead of live queries? I'd recommend it, faster and lighter on sources. 3. Are the dashboards shown to your own clients? Client reports need branding and strict access rules. Happy to go over the details here in chat and suggest the best approach. Looking forward to hearing from you, VAN HIEU
$300 USD in 7 days
3.0
3.0

Hi , ➡️ I read your project description , you want to document the mapping logic of your Informatica PowerCenter repository by translating technical transformations into clear documentation and visual flows? ⏺️ I specialize in Informatica PowerCenter development and technical documentation. I will meticulously analyze your mappings, look-ups, and joins to create a comprehensive source-to-target mapping document and professional Lucidchart data-flow diagrams. I will ensure every target column has a precise lineage description, providing your business analysts with accurate, human-readable insights. Regards, Muhammad Sabir
$150 USD in 6 days
1.9
1.9

Hi, I can help turn your Informatica PowerCenter mappings into clear, auditable source-to-target documentation that business analysts can follow without having to interpret the mapping logic themselves. I would start by extracting the selected folder's mapping metadata from the repository XML or Repository Manager, then trace every target column backward through its transformations to the original source fields. I would document lookup conditions and return values, joins, filters, expressions, default values, parameter dependencies, and conditional paths, flagging unresolved lineage rather than making assumptions. I would also build Lucidchart diagrams that follow the actual execution flow, with consistent labels linking each transformation to the corresponding lineage documentation. Before handover, I would cross-check every target column against the exported metadata to ensure the document and diagrams agree. Do you have an existing source-to-target documentation template or naming convention you'd like me to follow? Best Muhammad Saad
$140 USD in 7 days
1.8
1.8

Hello, I see the main risk: incomplete lineage from chained transformations and look-ups hidden in Expression and Stored Procedure transformations, which often leaves target columns marked as "unknown." My focus will be to remove every unknown by tracing field-level flow through Source Qualifier, Expression, Lookup, Joiner, Filter, Aggregator, and any custom transformations inside the selected folder. I have 9+ years extracting Informatica PowerCenter metadata and translating repository XML and Repository Manager exports into clear source-to-target documentation for data warehouses. I have produced mapping-level documents and visual flows for analysts and developers that capture look-ups, filter predicates, join keys, default values, and conditional logic so every target column is auditable and testable. I will use direct XML parsing and PowerCenter metadata where needed to ensure accuracy. I will begin by importing the folder XML (or using read-only repository access), enumerate all mappings and transformations, and create a field-by-field lineage table. I will then build Lucidchart data-flow diagrams that reflect each major transformation, lookup, and conditional path so nothing remains unresolved. - Do you prefer I work from a repository read-only account or an exported mapping XML bundle? - Which mapping in the folder should be highest priority if you want an initial sample delivery? Happy to hop on a brief call whenever it suits you. @melopgabriel
$40 USD in 1 day
1.2
1.2

You'll get a field by field source to target document for the chosen mapping folder, plus Lucidchart flows a business analyst can read without opening PowerCenter. Plan: - Work from the XML export of the folder, parsing every mapping, mapplet and transformation instead of reading them by hand - For each target column: source fields, expression logic, lookups with their conditions, filters, joins and default values - Lucidchart diagram per mapping showing the path from source qualifier to target, with each lookup and router branch marked - A final check that every target column has a lineage line, so no step is left as unknown What you get: the mapping document in Excel or Word, the Lucidchart diagrams, and a list of anything in the logic that looks unused or contradictory. Time: 2 days for the folder. Proof: 5.0 rating from 9 reviews, 100% completion. Roughly how many mappings are in the folder? Chaman
$30 USD in 2 days
0.8
0.8

My nearly 20 years in software engineering, technology leadership, and data driven product development give me the analytical depth needed to turn complex repository logic into documentation business analysts can follow. I hold a Bachelor’s degree in Computer Science and a PhD in Artificial Intelligence, with hands-on experience across databases, data extraction, automation, and scalable software systems. I can deliver clear field-level lineage and professional visual flow documentation suitable for business and technical handoff. Choose me to make the selected mappings fully understandable and traceable.
$30 USD in 7 days
0.0
0.0

Mapping documentation at this price covers one mapping as the first checkpoint, with field lineage and a matching Lucidchart flow. I’ll trace each target column through expressions, lookups, joins, filters and defaults, recording dependencies and flagging missing definitions for resolution. XML metadata will anchor the documentation; reusable transformations and mapplets will be traced through their referenced definitions. Within three working days, you’ll receive the first source-to-target document and diagram for review. Diagrams will be produced using AI tools and checked before delivery. The remaining folder requires a next funded milestone after you accept this checkpoint. Please provide the folder’s XML export, including referenced objects, and any existing specifications. Work starts after the milestone is funded. Price: 85 USD fixed · Timeline: 3 working days from access/brief Konrad
$85 USD in 3 days
0.0
0.0

**Free to jump on this right away, I read your post twice and can trace every field in that folder from source to target** I am Anand, a Full-Stack Developer & IT Systems Specialist with strong XML, documentation and data analysis work behind me. I would prefer the XML export plus your existing spec sheets to start. I will trace each mapping through the XML and Repository Manager metadata so nothing is missed. Source-to-target: I will document every target column field by field, covering source fields, lookups, filters, joins, default values and conditional logic, with no unresolved unknown steps by the end. Lucidchart: I will build data-flow diagrams that mirror the mappings and highlight each major transformation, lookup and conditional path so business analysts can follow it easily. Recent work: Built a dashboard app that replaced an ops team's spreadsheets, and a lead intake flow from forms, email and chat into one CRM saving ~15 hrs/week. I have a 4.9/5 rating from 40 reviews with 98% of accepted jobs completed on Freelancer. Can you share the XML export and the folder name so I can confirm the mapping scope and get started?
$80 USD in 7 days
0.0
0.0

Hi there, The key challenge is tracing every Informatica PowerCenter target column through lookups, filters, joins, defaults, and conditional paths, then translating that logic into accurate business-readable lineage and Lucidchart flows. I have strong hands-on experience with data lineage documentation, repository metadata analysis, and Data Visualization, with similar work involving source-to-target tracing and transformation logic analysis. My approach would be to: * Review the selected folder, mapping XML, repository metadata, and existing specification sheets. * Identify the root lineage path for each target field and determine what can be reused versus what needs clarification. * Implement a clean, maintainable source-to-target document using structured lineage tables and Lucidchart data-flow diagrams. * Test edge cases, reliability, transformation completeness, and integration behavior across every mapping. * Deliver and validate the documentation without disrupting the read-only repository or existing implementation. I will use transformation-level tracing to ensure no hidden expression, lookup condition, reject path, or default value remains an unresolved unknown. I prefer documenting the actual root logic rather than making assumptions, and I will keep the final handoff clear, stable, and maintainable for business analysts. I can start by reviewing the repository export, selected folder, mappings, and available specifications, then proceed with the most pract
$220 USD in 5 days
2.3
2.3

Ashburn, United States
Payment method verified
Member since Jul 23, 2023
$250-750 USD
$10-30 USD
$25-50 USD / hour
$15-25 USD / hour
₹600-1500 INR
₹12500-37500 INR
€30-250 EUR
₹37500-75000 INR
$15-25 USD / hour
₹75000-150000 INR
₹100-400 INR / hour
₹750-1250 INR / hour
$25-50 USD / hour
₹100-400 INR / hour
₹600-800 INR
$30-250 USD
₹750-1250 INR / hour
$250-750 USD
$30-250 CAD
₹12500-37500 INR
₹600-1500 INR