This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
We are currently on 6.2.3, Oracle 10g, and WebSphere. We bill for work done and charged against work orders for other departments each month until the work order is closed. We added an Invoice Date field that gets populated when our SQL is run each month to generate XML files that are sent to our billing system. The SQL looks to see if a date is in the invoice date field on the transaction and if so it does not put that transaction in the file. We added a Customer ID field on the Work Order Tracking application/screen to gather data by customer.
We wrote a billing summary report for the business managers of our department to run at the first of the month that shows them what is about to be billed so they can review it, okay it, or make corrections, before the code is run.
We pass labor hours, materials, and tool charges to the billing system in the XML files. Tools are large equipment like bucket trucks.
I hope this helps some.
Dwight Morgan
University of North Carolina at Chapel Hill
Dwight.Morgan@energy.unc.edu
We are currently on 6.2.3, SQL Server 2005, and WebSphere. We bill all work orders on our Transportation Module using a status called 'RELS BILLING' (release for billing) which is a synonym for 'COMP' through a cron task. We use this customized cron task that runs once a month to take all work orders in this status and calculate the charges for labor, materials, services, tools, and fuel (which we store in the matusetrans table) and then store them in a custom billing table. From this table we generate a interface file (flat file) which we feed to our billing system and then update a field on work order named Bill Date and 'CLOSE' the work order.
The user reviews all of the charges through a series of reports and once they approve the charges we place the interface file on our file server for our financial system to consume.
Using this process we do not allow the users to 'CLOSE' the work order, only the billing process can close a work order. This way we can be sure that all work orders that have been closed have been billed for. This process works well for work orders that are only billed once all of the work on that work order is completed.
This is another approach, I hope this helps as well.
Gerard N. Mayers
Senior Maximo Developer
Information Technology Department
214 Hogan Street 9th Floor
Jacksonville, FL 32202
904-255-8034 - Phone
904-232-6932 - Fax
________________________________
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Morgan, Dwight (Energy Services)
Sent: Wednesday, June 22, 2011 9:16 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Billing for workorders
We are currently on 6.2.3, Oracle 10g, and WebSphere. We bill for work done and charged against work orders for other departments each month until the work order is closed. We added an Invoice Date field that gets populated when our SQL is run each month to generate XML files that are sent to our billing system. The SQL looks to see if a date is in the invoice date field on the transaction and if so it does not put that transaction in the file. We added a Customer ID field on the Work Order Tracking application/screen to gather data by customer.
We wrote a billing summary report for the business managers of our department to run at the first of the month that shows them what is about to be billed so they can review it, okay it, or make corrections, before the code is run.
We pass labor hours, materials, and tool charges to the billing system in the XML files. Tools are large equipment like bucket trucks.
I hope this helps some.
Dwight Morgan
University of North Carolina at Chapel Hill
Dwight.Morgan@energy.unc.edu<mailto:Dwight.Morgan%40energy.unc.edu>