SAP BI Deployment Checklist
Hum, today we have some job in SAP BI. We are going in huge massive development in production this weekend. So QA sign-off will be in this Friday. I don’t know how the things move. I really have nothing to post at blog. Just some scrap. The big deal is creating deployment check list and then follow up sign-off. Let see what deployments check list is. Deployment Check list is step by step jobs/steps, responsible person who initiate it and estimated time process will take to complete. As well as how jobs inter dependent with each and which follow what. That’s it. It gives clear idea to team and to netweaver guys. This give clear pictures, how to transport and what is coming in production.
Here are more details of Development Checklist:
√ Change Review Number, if you have any number
√ Project Name
√ Deployment coordinator
√ Target Environment, e.g. Production
√ Task number: This is a Column having Task number. Start with Init
√ Task Description; Column
√ Person Responsible ; Column
√ Dependent Tasks; Column
√ Start Time ; Column
√ End Time; Column
This is typical one. We can add more stuff like the following tables:
√ Dependencies (Developers note: All object dependencies should be included in your project. Please check with others who might be using the objects to ensure they can be moved within your project and on your date requested)
√ Special Instructions(Developers note: Please include any special instructions or manual processes that also need to be completed for this deployment)
√ Special Test Requirements (QA note: Are there any special needs required in the testing environment (ie. Simulating tests on different run dates))
√ Data Requirements (QA note: Are there any special data requirements (ie. Specific test cases, golden data refreshes, etc)
√ Attachments
√ Contacts: like Contact Name and Phone number
√ Back out: If the programs that we are running are failed then we can clear the data in the tables and reload once again
√ Escalation Plan: In the event of any failure with data loads, the team member will immediately phone the deployment coordinator. The deployment coordinator will communicate to the team through a group email the status and if necessary contact the dependent resource and advice of new times.
Monday, March 23, 2009
Thursday, March 19, 2009
My personal thoughts, about how to behave with your co-worker.
My personal thoughts, about how to behave with your co-worker.
That’s the thing I don’t like about IT job. Today I’m doing nothing. Today is very boring day. I have nothing to do. It’s always like that after big sign-off. You work like a dog till sign-off and after it done, it’s so quite. You look for any job to do to kill the quietness. I’m doing the same. I am trying to find some job so that kills silence. Put in this way, show other team member that I have job to do. In IT if you don’t have any thing to do, then you have act as that you are dam busy. IT job make you actor. If you are good actor, you are best employee. Nobody care if you are doing your job very effectively and quickly. They care how good you act to showing other that you are the only person, who is running the show.
Second, your co-worker will never ever be your friend. How much they talk to you. How much you share with them. How much they share with you. It doesn’t matter how many time you hangout together. Co-worker is co-worker. Never try to be friends with them. Always keep a very good distance with them. If you are keeping some distance. You will be happy. If not your office life as well as your personal life will be mess. Really mess.
Third, never ask favour from co-worker at your personal level. It doesn’t matter if you are open with them or not. If you need any favour from co-worker, always follow the company’s rules. Today, I’m little bit burnt. Burn by heart! I ask a return favour from my 2 co-workers. Guess what, they denied. They denied because I asked favour at my personal level. That’s a blunder mistake I did. This is a blunder mistake. This makes you very weak in front of your co-worker. So never ever ask favour from co-worker.
That’s the thing I don’t like about IT job. Today I’m doing nothing. Today is very boring day. I have nothing to do. It’s always like that after big sign-off. You work like a dog till sign-off and after it done, it’s so quite. You look for any job to do to kill the quietness. I’m doing the same. I am trying to find some job so that kills silence. Put in this way, show other team member that I have job to do. In IT if you don’t have any thing to do, then you have act as that you are dam busy. IT job make you actor. If you are good actor, you are best employee. Nobody care if you are doing your job very effectively and quickly. They care how good you act to showing other that you are the only person, who is running the show.
Second, your co-worker will never ever be your friend. How much they talk to you. How much you share with them. How much they share with you. It doesn’t matter how many time you hangout together. Co-worker is co-worker. Never try to be friends with them. Always keep a very good distance with them. If you are keeping some distance. You will be happy. If not your office life as well as your personal life will be mess. Really mess.
Third, never ask favour from co-worker at your personal level. It doesn’t matter if you are open with them or not. If you need any favour from co-worker, always follow the company’s rules. Today, I’m little bit burnt. Burn by heart! I ask a return favour from my 2 co-workers. Guess what, they denied. They denied because I asked favour at my personal level. That’s a blunder mistake I did. This is a blunder mistake. This makes you very weak in front of your co-worker. So never ever ask favour from co-worker.
Wednesday, March 18, 2009
SAP CML Batch/Periodic Process Testing-Part 2
March 18, 2009: 2:50 PM
QA sign-off form is on desk of our PM. PM is in meeting. So I drop on desk and left a sticky note, when done. Mean while I’m doing blog. At last we did with Periodic process sign off today. This is second sign off with in 3 week. This sign- off is like part 2 of our periodic process. As I mention in my last post, our daily periodic processes are in Prod.
This sign off is about our monthly processes. We tested again in T3 and Then TX. We are going with one defect with this sign off in prod. Actually this is not defect, hum kind of.
Let me explain it little bit. We have one process which updates those loans that do not have IOA frequency into 1 on condition in SAP CML. If we run this process first time or if we added few loans. That loans need to change, frequency of IOA, then this process work very well, without any hiccup. But thing is when we run this process with any change or run it twice, it cancelled it self. It cancelled itself after showing error message. The error message is no IOA found on loans to change.
So we have 2 problems with one process. One is why the heck it showing error message. We are expecting warning message. Second which is my major concern, and that is why it cancelled itself. Let me mention this is a daily process. The expected results we are expecting are:
A. When we run this process daily, if it get some loan to change, it show the loans number. It works well, when we add new loans?
B. When it rerun again, as this is daily process, if it not found any loans to change, its display warning message that “no loans found to change”. Not error message
C. After rerun or after not getting any loan to change, we expect it should not cancel itself. Why? Right now its independent process. No processes are dependent on it.
When we investigate this issue, we found this. Our old developer has hard coded, in this way, it always show error message instead of warning message. So guys lesson learn old things always haunt.....
QA sign-off form is on desk of our PM. PM is in meeting. So I drop on desk and left a sticky note, when done. Mean while I’m doing blog. At last we did with Periodic process sign off today. This is second sign off with in 3 week. This sign- off is like part 2 of our periodic process. As I mention in my last post, our daily periodic processes are in Prod.
This sign off is about our monthly processes. We tested again in T3 and Then TX. We are going with one defect with this sign off in prod. Actually this is not defect, hum kind of.
Let me explain it little bit. We have one process which updates those loans that do not have IOA frequency into 1 on condition in SAP CML. If we run this process first time or if we added few loans. That loans need to change, frequency of IOA, then this process work very well, without any hiccup. But thing is when we run this process with any change or run it twice, it cancelled it self. It cancelled itself after showing error message. The error message is no IOA found on loans to change.
So we have 2 problems with one process. One is why the heck it showing error message. We are expecting warning message. Second which is my major concern, and that is why it cancelled itself. Let me mention this is a daily process. The expected results we are expecting are:
A. When we run this process daily, if it get some loan to change, it show the loans number. It works well, when we add new loans?
B. When it rerun again, as this is daily process, if it not found any loans to change, its display warning message that “no loans found to change”. Not error message
C. After rerun or after not getting any loan to change, we expect it should not cancel itself. Why? Right now its independent process. No processes are dependent on it.
When we investigate this issue, we found this. Our old developer has hard coded, in this way, it always show error message instead of warning message. So guys lesson learn old things always haunt.....
Saturday, March 14, 2009
SAP CML Batch/Periodic Process Testing
SAP CML Batch/Periodic Process Testing.
What is Batch/Periodic Process Testing?
Answer is mess, yes don't be surprise.Batch Process or Periodic process or Batch process in SAP CML is a pure shit/mess. However testing it is more shitty. It's not a very easy job.
First lets understand,what the hell is Periodic process or Batch Process. I want to call it a Batch Process. Batch processes are jobs which triggers itself periodically. They complete the process and trigger other process. They are scheduled according to need.Take example,a big banks or finical company, getting payments on loan or mortgage every day from different customers. They have different type of payment methods, like Cheque,Cash,Pre Auth.Payment or electronic payments or wire. So banks or finance company run process everyday to maintain customer account,cash flow,account statement, ledgers to update accounts. So batch process can be daily,weekly,biweekly,monthly,quarterly,semi annually and annually.
It's all depend on business rules or what is running in current system. Here in my company we have categorized the batch process in 4 periodicity. Daily, Monthly, quarterly and annually.We have sliced and diced our all finical business process and then come up these 4 periodicity. But shit don't stop here. We have some processes which run twice a day. These are payments and disbursements processes. Posting of payments and disbursement on loan and etc.
Some processes run monthly, like Accrual/Deffer, IOA cal, and lots of corresponding generated processes.
The worst part is testing all these processes. These all processes are interdependent or interwoven to each other. I created our test plan in iterative approach. Plan is this- First test the daily job, then monthly and then quarterly and annually. So for till today we already tested daily processes in Testing, and Then in UAT and then in TX environments. Last weekend we sign off and it goes in Prod. Next week will be sign-off for Monthly and quarterly processes. I already tested these process in T3. I think our netweaver guys has transported all transport into TX.So Monday we have to create data in TX. Most probably our sing-off will be on Wed/Thur.
Yes we are testing directly in UAT region. Why, first we don't have time. Second our QA region is fully of garbage data. So we think that may break our region. Third everyone so dry, why, the CML project so long, and so many new faces are in. we are just 3 people in whole team are old faces. Me(QA) and 2 BAs are left.Our Developers are new, our PM is new.
That's it from my side. That was very long time from my last posting on this blog. We were deadly busy in to bring multi-applications-integration into Prod. woooww. We work's some 100 hrs/week last 2 months. I don't believe myself, that i really work so long hours.
Atul
What is Batch/Periodic Process Testing?
Answer is mess, yes don't be surprise.Batch Process or Periodic process or Batch process in SAP CML is a pure shit/mess. However testing it is more shitty. It's not a very easy job.
First lets understand,what the hell is Periodic process or Batch Process. I want to call it a Batch Process. Batch processes are jobs which triggers itself periodically. They complete the process and trigger other process. They are scheduled according to need.Take example,a big banks or finical company, getting payments on loan or mortgage every day from different customers. They have different type of payment methods, like Cheque,Cash,Pre Auth.Payment or electronic payments or wire. So banks or finance company run process everyday to maintain customer account,cash flow,account statement, ledgers to update accounts. So batch process can be daily,weekly,biweekly,monthly,quarterly,semi annually and annually.
It's all depend on business rules or what is running in current system. Here in my company we have categorized the batch process in 4 periodicity. Daily, Monthly, quarterly and annually.We have sliced and diced our all finical business process and then come up these 4 periodicity. But shit don't stop here. We have some processes which run twice a day. These are payments and disbursements processes. Posting of payments and disbursement on loan and etc.
Some processes run monthly, like Accrual/Deffer, IOA cal, and lots of corresponding generated processes.
The worst part is testing all these processes. These all processes are interdependent or interwoven to each other. I created our test plan in iterative approach. Plan is this- First test the daily job, then monthly and then quarterly and annually. So for till today we already tested daily processes in Testing, and Then in UAT and then in TX environments. Last weekend we sign off and it goes in Prod. Next week will be sign-off for Monthly and quarterly processes. I already tested these process in T3. I think our netweaver guys has transported all transport into TX.So Monday we have to create data in TX. Most probably our sing-off will be on Wed/Thur.
Yes we are testing directly in UAT region. Why, first we don't have time. Second our QA region is fully of garbage data. So we think that may break our region. Third everyone so dry, why, the CML project so long, and so many new faces are in. we are just 3 people in whole team are old faces. Me(QA) and 2 BAs are left.Our Developers are new, our PM is new.
That's it from my side. That was very long time from my last posting on this blog. We were deadly busy in to bring multi-applications-integration into Prod. woooww. We work's some 100 hrs/week last 2 months. I don't believe myself, that i really work so long hours.
Atul
Subscribe to:
Posts (Atom)