What is meant by Company sets

The Company Master application, in which you maintain a master list of vendors, stores data in the company set. The vendors that you do business with are unique within the company set. One or more organizations can share the same company set.

Using company sets provides the following benefits:

• You can standardize your list of approved vendors.

• You can create global contracts that can be shared by multiple organizations.

In the Company Master application, you create a catalog of companies and you associate individual companies with specific organizations. In the Companies application, which stores data at the organization level, users can access the vendor information associated with their organization.

When you create a company set in the Sets application, you have the option of automatically adding the companies to the Company Master application. By default, this option is not enabled, which means that users must manually enter new companies in the Company Master application. However, you can enable the options so that the record is automatically added in the Company Master application.

You apply a company set to one or more organizations. If an organization requires its own list of vendors and contracts, you can create a separate company set for it.

The following figure illustrates an example of an enterprise with three organizations and eight sites. Two organizations, and their five sites, share the same company set. The third organization has its own company set.

 

Item sets and company sets are independent of each other. The following figure illustrates such an example. There are four organizations and eight sites. Organizations 1 and 2 share Item Set 1; Organizations 3 and 4 share Item Set 2. Organizations 1 and 2 each have their own company set. Organizations 3 and 4 share Company Set 3.

 

What is meant by Item sets

Item sets group information about assets, materials, spare parts, service items, and tools. Records created in the Item Master application are stored at the set level. 

Assets and inventory items shared between organizations

When you create an item master record, it becomes part of the item set of the organization to which your default site for new records belongs. The items are unique within the set. Because you can assign the same item set to multiple organizations, you can use the same item definitions for all sites within those organizations.

Using item sets provides the following benefits:

• You can transfer items between organizations.
• You can standardize your item definition so that all organizations and their sites share the same item catalog and item assembly structure.
• The Item Master application provides an item catalog from which to set up inventory at multiple sites.

If more than one organization in your enterprise requires its own item definition, you can create multiple item sets. You can assign a separate item set to each organization, or to each group of organizations that you want to share the same item definition.

The following figure illustrates an example of an enterprise with three organizations and eight sites. Two organizations and their six sites share the same item set. The third organization has its own item set.

Service items and tools shared between organizations

Service items and tools records are also stored at the item set level. Service items and tools are unique to the item set. Any organization assigned to the item set can use the service items and tools records in the item set.

Some of the data on a service item record may be specific to a single organization or site. For example, the companies listed in the Vendors window are at the organization level.

Restriction of records using application designer

You can use the Application Designer to define restrictions on what records appear in an application. You can enter a query in the presentation XML of an application to limit what data a user can see in that application. You can also limit the records that an application shows when it uses the same data source that other

applications use, but not all of the data is applicable to all of the applications. The following procedure is presented as an example.

To define restrictions on a power application:

1 In the Application Designer, open the Assets application in the Workspace

tab.

2 Select the List Table control.

3 Click Control Properties to open the Table Properties window.

4 In the Application Restrictions field, type

ASSETNUM!= 'BUS'

the Application Designer interprets the query as

select * from asset where ASSETNUM!= 'BUS'

5 Click Save.

  

When you open the Assets application, you will see all the records that do

not have a ASSETNUM of "BUS".

Similarly you can restrict any record based on attribute .Example restrict workorder based on workorder num 

WONUM !=’10098’

 

Change status using Integration Framework

Change status using Integration Framework ---->>> Integration Framework : Application Import and Export

Integration Framework : Application Import and Export & Change status

This feature supports the import and export of data directly from applications, such as PO orWork Orders. This allows users to perform import and export of data without having to having access to the I-F External System application 

 

      User can just export the application and do the required  modification in the application without approaching  I-f external system

 

      New functionality allows the user to export the data to a formatted file that can be maintained in an Excel spreadsheet. The user can apply changes across one or more rows of data in the spreadsheet and when completed, the data can be imported back into Maximo.

 

      The application-based import and export functionality relies on the object structure component of the integration framework to define the data content and any processing classes (Java) that are needed to facilitate the exporting and importing of data. No other integration framework components (such as publish channels, JMS queues & end points) need to be configured. Administrator will enable the integration for an application using a provided object structure or by creating a new object structure.

 

         

Use the following steps to duplicate the MXPO object structure:

 

 

1 . From the Maximo Admin Console select ‘Go To’ -> ‘Integration’ > Object Structures’

2 . Click on the ‘Object Structure’ tab

3 . Type ‘MXPO’ in the ‘Find’ dialog.

4 . Press Return. The MXPO Object Structure will be displayed.

5 . In the ‘Select Action’ drop down box, choose ‘Duplicate Object Structure’.

6 . Assuming you duplicated MXPO and created NEWMXPO, based on your user’s requirements, you could delete all the objects except PO

 

 

7 . Once that is done your user may also want to limit the number of Po fields that are available. PO , by default has over 80 fields in the object and having a spreadsheet with that many columns can be difficult to maintain.Your user may only want/need to use up to 20 fields.

8 . To support this, the object structure application has a Select Action, Include/Exclude Fields, that allows the administrator to define which persistent and non-persistent fields are to be included in the data that is exported and imported.

9 . If you are exporting in flatfiles file formate the go for Add/Modify Alias of select action , to assign unique field name where there are currently duplicates..

10 . From Select Action, click on Add/Modify Application Export Support, that allows you to enable exporting to an application            

11 . In the dialog (above), select New Row and the application will default to an application that has a main object that is the same as PO . The Default File Type can be set so that your user will not have to select this object structure each time.

 

 

12 . Select Action, Add/Modify Application Import Support, that allows you to enable importing to an application (save the object structure before using this Select Action).

13 . In the dialog (above), select New Row and the application will default to an application that has a main object that is the same as PO . The Default File Type can be set so that your user will not have to select this object structure each time. So if your users will primarily use the data in a spreadsheet you should select Flat File.

 

 

 

Use the following steps to Grant Security access:

1. From the Maximo Admin console select ‘Go To’ -> ‘Security Groups’

2. Select ‘Application’ tag

3. Select ‘Asset’ Application

4. Select ‘Application Import’ and application export

 

5. Check the ‘Grant Access’ box

6. Select the ‘Save’ icon

7. logout and login

8. you can see import and export icons in your applications

 

Steps to follow while exporting :

 

1 . Select new record and fill all the required values

 

 

2 . Save the record

3 . Now click export application icon to export the data and fill the details .such as name of object structure which we have created and configuration format 

  

4 . Save the downloaded xml file 

 

 

 

5 . Open the downloaded xml file in edit++  Let us change the status of record to approve and any other updates  let it be description 

 

 

Steps to follow while importing :

 

6 .Now we need to import the xml modified by us

7 . Open po and click on application import .select the object structure and import configuration

 

 

 

8 . Click ok to start importing

9 . You can see th changes by opening the  po 1009 status as appr and description as purchase order for my organization 

 

 

  ALL the best