on 12-22-2014 8:22 AM
Dear,
After implementing a process, during hyper care or after hyper care (say after go live to 90 days) have you done any alterations to the process, some configuration change and what was the business reason for it.
One example - Return process and functionality - reference mandatory (activated, deactivated and then after initial period again activated)
Thanks!
TW
Hi TW
We have to make changes in processes after Go Live as per company's requirement. Sales return reference mandatory is very common example. When a company implements SAP and they start using it then they realize that they have missed some processes or some processes need to be changed.
I had this experience in my previous role where we used to follow credit note posting through FB75 directly from FI. There were some cases of miss-use of this transaction and business people asked SAP team to implement controls in it. We configured it through SD with document type CR and implemented approvals (Billing block). This is one example. There are many others as well.
From what perspective you are asking this?
Thank$
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
We had a process in CS (Customer Services) that when we receive some defected spare part we scrap that material with a movement type and upload that in scrap material type with some other movement type. User had post two movement types separately.
I searched and found 411 movement type. After some testing and GL assignments I proposed this new process and business agreed to adopt it and it saved time and efforts of users.
Thank$
Moazzam,
From your first post, in the first process, Finance department must have created the documents for the credit process. In the second process, CR (SD module) which department(s) created the documents (cmr, cm)?
In this new process, was it in CS or in SD (with movt type 411)?
TW
Message was edited by: TW Typewriter - all questions in one post
Hi Moazzam,
Thanks!
Many times, after business users (really) work with the newly implemented process, they come up with "short comings". This gives rise to "add ons" (changes, new CRs) in these processes.
It will be better to benefit from past experiences and propose to client, before hand; in order to minimize these kind of "short comings". That is the reason for this thread.
In one of my projects, I proposed cancellation of billing to be included, the key user and team did not want that. So, the process went live without the functionality of cancelling a bill. Then business users came back with a request to incorporate this too. Thus we did add this during hyper care period.
Coming from a non-technical perspective, communication and involvement of the "relevant" stake holders is so important. It is another thing that mostly business users treat this (testing or UAT) as low priority (probably something to do with the management and their "appropriating priority on other tasks).
TW
Moazzam,
Thanks for your post! As always, these are valuable!
(about this ongoing discussion about support consultants ) not sure...not all support consultants can see the impacts (or the impacts which can happen in the future). Not all support consultants get to know the business processes, they tend to get issues at a particular stage of process, thats it!
So, as we know, it depends upon the consultant (or that individual / user - key-users are also sometimes very knowledgeable). The will to grow in a "focused" way or orientation may be the (one of the) keys!
TW
I will keep updating this thread with business scenarios related to "add on" configurations and functionalities, to an implemented (go live) process. This will help the community.
marking this thread as assumed answered, for now.
TW
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.