Informatica Tranformation Example For Peoplesoft ERP HR data.
1. Informatica Expression (Source to Target)
2. Source Qualifier transformation
3. Expression Transformation
4. Informatica Language example use of IFF syntax.
5. performance optimisation using Oracle DECODE function inside Expression transformation
6. Hexadecimal to Decimal Conversion Logic
READ part 1:
This debate of SAP Vs Oracle or last 2 yrs buzz SAP HANA vs Oracle Exalytics
Every year in Enterprise Software space Competition of SAP Vs Oracle Hots up with new announcements and New technology comparisons of SAP new Tech Vs Oracle New Tech.
The Enterprise Software stack built up by No.1 and No.2 world’s top most valued companies in Enterprise Technology Space.
So SAP Vs Oracle comparison will never go out of picture only every year it will up the ante.
In Memory Technology: SAP Vs Oracle (New tech now 2 yrs old).
Now a day In-Memory Technology is the Hottest area especially in Business Intelligence (BI). But its not limited to BI it goes into ERP, Application development of any Kind.
The processing infrastructure in form of in Memory Systems is much faster than any other form. As Cost of RAM is coming down and capacity of server is expanding So most data to be processed can be pulled inside memory at once instead of using Locality of reference to pull and process from secondary memory.
Also Server can hold lot more data to processed in memory at once.
SAP HANA Vs Oracle Exadata
So SAP Came with SAP HANA and Oracle has its own in memory systems. At same time Oracle released high performance machine Exadata which brook many performance records. So There was running comparisons of SAP Vs Oracle in Enterprise Technology space.
innovation at SAP : ABAP, BSP and BAPI
SAP customized by using Advanced Business Application Programming (ABAP) Language.
Using which reports are customized, forms are modified, business processes are written to reflect business Logic. ILE, BAPI, IDOC can be used to interface with external software or integration or developing Adaptor. Custom Exits and User Exits are written to customize forms and reports.
For SAP datawarehouse technology SAP BIW or SAP BI datawarehouse is created using
Extraction Legacy System Migration Workbench (LSMW) or Cost and profitability Analysis (COPA) Extrations then transformation can be applied using ABAP user exits.
Problem with ABAP is compared to mordern langauges it has not evolved much over time.
Most of ABAP constructs are similar to COBOL constructs. There is Object oriented ABAP also like JSP or ASP it came up with BSP (Business Server Pages) to Expose ABAP code directly to Web like JSP does for Java or ASP does for Microsoft Technology.
SAP Netweaver Vs SAP ABAP BSP
SAP began adopting Java in 2003 and came up with Netweaver product which was J2EE server for ABAP code. Now you can code using either java or ABAP in netweaver. For Application requiring functionality to exposed to Web Java was natural choice.
But Oracle having acquired Java in year 2010 Since then there was continuous Effort on part of SAP to move away from its dependence of Java. So BSP came into picture as first step.
Benefits of In-memory in SAP HANA
next was paradigm shift using Columar database instead of Row oriented databases which consumed less storage (on account of reduction in repetitions of similar column values as well compression of data).
Also it integrates:
BI and datawarehousing system or OLAP with
Operational systems or OLTP Systems as one.
Even Analytic requiring lowest level of granularity can be queried on same server.
Effect of which was Whole data can be pulled and kept in In-memory system offering faster response time to multiple user connected at same time rather than
Regular database Query processing logic
parsing request , making parse tree,
comparing with already fetched query parse tree in cache
if not available
fetching data from secondary memory
when depending on the request into
Improvement in data processing in SAP HANA and column oriented database
Now since whole data can be kept in-memory So Every query can directly fetch data quicker.
Future Technology Like SAP HANA
Enhancement over this Technology are Probabilistic databases and Graph databases.
Graph databases are available commercially since long time.
Index free storage. Every element has direct pointer to adjacent element, hence no lookup needed.
Here is list:
Probabilistic databases : Are active area of research as discussed above as well.
Depending on ERP there can be many modules inside..
Major modules of peoplesoft ERP are :
1. Human Resource Management Systems HRMS
Submodules: (payroll, Core HR, benefits, recruitment, performance management)
(Account payable AP, Account Receivable AR, General Ledger GL etc..)
3. Supply chain Management SCM
4. Customer Relationship Management CRM
Functional consultant major work is during GAP Analysis To find As-IS state and identify work required to achieve TO-BE state.
Find all those forms which needs to be modified, and all those reports which needs to be modified And Exactly what field to change, What button to remove, What functionality to be disabled, What pre-delivered business logic behind components to be modified and What formulae to be used during modification.
There is Another Module which is consider Techno-functional Peopesoft EPM. EPM is datawarehouse part which has four major components for Each of four above there is a data mart for each area of finance, HR, SCM, CRM.
Each contains data from its own module transferred using ETL tools and reporting using BI Tools and analytics can be applied over formulae in BI systems.
-Also functional consultant decide based on feedback from local management to modify field like in HRMS a rejoining of employee should get ID as previous from old record or new ID based of policy in management.
if Payroll of local market like irish payroll or indian payroll does not exits then it should existing global payroll should be modified to achieve local labour laws and saving rules , income tax based customisation.
There are 5 major streams for Peoplesoft technical consultant
1. Reporting Tool: Hyperion SQR, nvision, Crystal,
2. Server Tool: peopesoft internet Architecture, Tuxedo, JOLT, Webserver, Appserver
3. Application development: peoplecode, application designer, App Engine, PS integration Broker,
4. Installation and Upgrade : Upgrade Assistant,
5. Peoplesoft DBA: all issues related to Database on top of which peoplesoft ERP is sitting.
Depending of Each of these streams The a day in life of Peoplesoft technical consultant will differ.
Life cycle of Peoplesoft implementation from :
4 major areas:
1. GAP Analysis,
3. stabilization phase of ERP ,
4. and support for already developed
Each phase has its own daily routine Like during support phase
3 major type of request which can come from user is ICE:
Incident, Customization, and Enhancement request.
During gap analysis: The As-IS state is studied and its difference made out from TO-BE state. The Gap between AS-IS and TO-BE state is implementation which needs to done.
As you know peoplesoft is ERP package comes with its pre-delivered tables, forms and reports Which needs customisation depending on company, country , laws of land, company processes.
During implementations phase according to gap analysed forms , reports are customized using peoplecode language and application designer, 9 steps process is applied to each component being developed, which include security settings.
SQR banned reports are being customized with header footer for display and for business logic of processing data fetched from database and displaying in format required using option like BREAK options.
Support Phase ICE request for each change is being accepted for Incident, enhancement and Customisation for Each Change Request raised and Accepted or any errors in existing code.
Read Previous part
Normal Schedule for development role :
9:00-9:30 Check all mail communications of late night loads Etc.
9:30-10:30 Attend Scrum meeting to discuss update status of completed task mappings and mapping for New user stories requirements, understand big picture of work completed by other staff status.
10:30 am -1:30 pm Look at LLD, HLD to create source to target transformations after understanding business logic and coding that in transformations available with tool.
1:30-2:00 Lunch break
2:00-3:00 Unit test data set to validate as required between source and target.
3:00-3:30 Documentation requirements of completed work.
3:30-4:30 Attend defect Call To look into new defects in code and convey back if defects not acceptable as out of scope or not according to specifications.
4:30-5:00 Status update daily work to Team Lead.
5:00-5:30 sit with Team lead, architect code walk through and update with team.
5:30-6:30 Take up any defects raised in Defect meting and Code walk through.