What is the logic behind PONUM autonumber for both Site and Organization levels?
RobertoG.Palma 270000BQR0 Visits (7059)
The autonumber PONUM exists at both the system level and organization level in Maximo system.
Do you believe there is some explanation of why it exists at both?
The Autonumbering is controlled by the Autonumber Setup within the Organizations application. Autonumbering can be setup at system, org, and/or site levels in any combination desired.
A PO is a SITE Level record and when you create a new PO, Maximo takes in consideration the User Default Insert Site to fill the PO SiteID and OrgID.
This way if a PO Header is specified in the ORG1 and SITE1 , all the POLINEs will be created to the Same ORG1 and SITE1.
Additionaly, MIF (Maximo Integration Framework) uses the same Business Rules that Maximo UI does. The Maximo code identifies which to use for a given record like this:
If there's an autokey record for this ORG and SITE, then use it
For a multisite implementation, you can have different autonumbering sequences for different organizations and sites.
For example, Preventive Maintenance is a site-level application and preventive maintenance IDs are unique at the site level.
However, you can implement an organization-level sequence. You can choose to have the autonumbering work in the following ways:
1 >> All sites are part of the same sequence. You set the autonumbering for preventive maintenance records and the autonumbering works the same
2 >> You have three sites and you want one to have independent preventive maintenance autonumbering. You want sites 1 and 2 to be on the same autonumber sequence, but you want site 3 to be independent. You set preventive maintenance autonumbering to 1000. You then specify an independent autonumber sequence for site 3.
3 >> You want all sites to have independent preventive maintenance autonumbering. You specify autonumbering for all sites, or you specify autonumbering for all sites except one. The exception is defined by whatever you specify in the Organization Level window.
Standard Maximo does not offer a functionality that you can use to delete an Organization Level autonumber. Also, if you check the Database Configuration app, and search for PO object and PONUM attribute (in Attributes tab) you will see that there is a 'Can Autonumber?' field which is check as default and cannot be disabled or unchecked, as this is read-only. (When checked, Maximo indicates that this attribute is able to support autokey)
Good Luck, thanks...