Informatica naming Conventions best practice.
This page will show you the recommended best practice of Informatica naming Conventions option, please note, it does not obligate you to use it in your organisation.
Designer Objects Naming
The following tables illustrate some naming conventions for mapping objects (e.g., sources, targets, joiners, lookups, etc.) and workflow-related tasks. You may choose to make the prefixes all lower case:| Designer Objects | Suggested Naming Conventions |
|---|---|
| Mapping | m_{TARGET_NAME} or suffix with _{descriptor} if there are multiple mappings for that single target table |
| Mapplet | mplt_{DESCRIPTION} |
| Target | {logic_update_type}_{physical_update_type}_{TARGET_NAME} This naming convention should only occur within a mapping as the actual target name object affects the actual table that PowerCenter will access. E.g. if the target name is Account and we are inserting records then the target name should be ACCOUNT_Ins. Abreviations should be Ins, Del, Upd. |
| Aggregator Transformation | agg_{FUNCTION} that leverages the expression and/or a name that describes the processing being done. |
| Application Source Qualifier Transformation | asq_{TRANSFORMATION} _{SOURCE_TABLE1}_{SOURCE_TABLE2} represents data from application source. |
| Custom Transformation | ct_{TRANSFORMATION} name that describes the processing being done. |
| Data Quality Transform | idq_{descriptor}_{plan} with the descriptor describing what this plan is doing with the optional plan name included if desired. |
| Expression Transformation | exp_{FUNCTION} that leverages the expression and/or a name that describes the processing being done. |
| External Procedure Transformation | ext_{PROCEDURE_NAME} |
| Filter Transformation | fil_{FUNCTION} that leverages the expression or a name that describes the processing being done. |
| Flexible Target Key | fkey{descriptor} |
| HTTP | http_{descriptor} |
| Idoc Interpreter | idoci_{Descriptor}_{IDOC Type} defining what the idoc does and possibly the idoc message. |
| Idoc Prepare | idocp_{Descriptor}_{IDOC Type} defining what the idoc does and possibly the idoc message. |
| Java Transformation | jv_{FUNCTION} that leverages the expression or a name that describes the processing being done. |
| Joiner Transformation | jnr_{DESCRIPTION} |
| Lookup Transformation | lkp_{TABLE_NAME} or suffix with _{descriptor} if there are multiple look-ups on a single table. For unconnected look-ups, use ULKP in place of LKP. |
| Mapplet Input Transformation | mplti_{DESCRIPTOR} indicating the data going into the mapplet. |
| Mapplet Output Transformation | mplto_{DESCRIPTOR} indicating the data coming out of the mapplet. |
| MQ Source Qualifier Transformation | mqsq_{DESCRIPTOR} defines the messaging being selected. |
| Normalizer Transformation | nrm_{FUNCTION} that leverages the expression or a name that describes the processing being done. |
| Rank Transformation | rnk_{FUNCTION} that leverages the expression or a name that describes the processing being done. |
| Router Transformation | rtr_{DESCRIPTOR} |
| SAP DMI Prepare | dmi_{Entity Descriptor}_{Secondary Descriptor} defining what entity is being loaded and a secondary description if multiple DMI objects are being leveraged in a mapping. |
| Sequence Generator Transformation | seq_{DESCRIPTOR} if using keys for a target table entity, then refer to that |
| Sorter Transformation | srt_{DESCRIPTOR} |
| Source Qualifier Transformation | sq_{Schema Name}_{SOURCE_TABLE1}_{SOURCE_TABLE2}. Using all source tables can be impractical if there are a lot of tables in a source qualifier, so refer to the type of information being obtained, for example a certain type of product SQ_SALES_INSURANCE_PRODUCTS. |
| Source Definition Object | {sc}_{SchemaName}_{TableName} e.g. sc_Clarity_CLARITY_BED |
| Stored Procedure Transformation | sp_{STORED_PROCEDURE_NAME} |
| Transaction Control Transformation | tct_{DESCRIPTOR} indicating the function of the transaction control. |
| Union Transformation | un_{DESCRIPTOR} |
| Unstructured Data Transform | udo_{descriptor} with the descriptor identifying the kind of data being parsed by the UDO transform. |
| Update Strategy Transformation | upd_{UPDATE_TYPE(S)} or UPD_{UPDATE_TYPE(S)}_{TARGET_NAME} if there are multiple targets in the mapping. E.g., UPD_UPDATE_EXISTING_EMPLOYEES |
| Web Service Consumer | wsc_{descriptor} |
| XML Generator Transformation | xmg_{DESCRIPTOR}defines the target message. |
| XML Parser Transformation | xmp_{DESCRIPTOR}defines the messaging being selected. |
| XML Source Qualifier Transformation | xmsq_{DESCRIPTOR}defines the data being selected. |