For the purchasing piece you probably only need the COTAR as an approver. Adding/modifying a project should fall under the Change Management process, with the purchasing portion being a task(s) under the CR. The CR would then have the multiple approvals if needed.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Roger Justice Sent: Wednesday, February 29, 2012 8:25 AM To: [email protected] Subject: Re: Asset Invoicing ** This is included with ITBM. -----Original Message----- From: Tommy Morris < <mailto:[email protected]> [email protected]> To: arslist < <mailto:[email protected]> [email protected]> Sent: Wed, Feb 29, 2012 8:22 am Subject: Re: Asset Invoicing ** The OOB Purchasing module is not very robust. There is only one approval allowed so chain approvals are out of the question. If you have a current homegrown process then you need to really go through the OOB purchase process to see where all the gaps are. I’ll bet that you are going to have to customize like crazy to get it to work the way your business partners need it. From: Action Request System discussion list(ARSList) [ <mailto:[email protected]?> mailto:[email protected]] On Behalf Of Brian Pancia Sent: Wednesday, February 29, 2012 6:53 AM To: <mailto:[email protected]> [email protected] Subject: Re: Asset Invoicing ** Lars, The Asset Management piece has a purchasing and receiving piece that might solve the bulk of your requirements. You may also be able to setup the projects as CIs and relate all the items purchased to the project CI. Add your additional attributes that you need to the project CI. If there are a lot of things outside the OOB functionality that you need you can always setup a backend staging form to setup your invoicing, but I think with little effort you can probably use the straight OOB functionality to handle most of what you're looking for. You can setup the paying units as cost centers and you have the ability to relate multiple cost centers. The only part that may require some customization is your pricing model for initial cost versus monthly costs, but it doesn't sound like this would be major. Brian From: Action Request System discussion list(ARSList) [ <mailto:[email protected]?> mailto:[email protected]] On Behalf Of <mailto:[email protected]> [email protected] Sent: Wednesday, February 29, 2012 5:16 AM To: <mailto:[email protected]> [email protected] Subject: Asset Invoicing ** Hi, has anyone been able to create an invoicing module of assets in the ITSM-system (7.6) with very few changes within the itsm-code. Something besides itsm handling the invoicing of assets. Assets are supposed to be connected to a paying unit, have a price which can easily modified, logic for initial cost and after that a monthly cost, file has to be created for R3, and excelfiles has to be created as specifications to the different customers. Each asset has to be connected to a project number, and a lot of other economy attributes, like order number. We have run this for many years in our home built system, but now it has to be done in itsm. Any feedback will be appreciated. L ars _attend WWRUG12 <http://www.wwrug.com/> www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 <http://www.wwrug.com/> www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 <http://www.wwrug.com/> www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
