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 organizationsService 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 otherapplications 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 Workspacetab.
2 Select the List Table control.
3 Click Control Properties to open the Table Properties window.
4 In the Application Restrictions field, typeASSETNUM!= 'BUS'the Application Designer interprets the query asselect * from asset where ASSETNUM!= 'BUS'
5 Click Save.
When you open the Assets application, you will see all the records that donot have a ASSETNUM of "BUS".
Similarly you can restrict any record based on attribute .Example restrict workorder based on workorder num
WONUM !=’10098’
Subscribe to:
Posts (Atom)