For example, you maintain an item's primary unit of measure at the Master level.Īttributes maintained at the Organization level may have different attribute values in different organizations. This attribute control type determines whether you have centralized ( Master level) or decentralized ( Organization level) control of item attributes.Īttributes maintained at the Master level have the same attribute values in each organization in which an item is assigned. One of the prerequisites for defining items (and assigning values to item attributes) is setting attribute controls. Item attributes are information about an item, such as order cost, lead time, and revision control. Implementing the Item Master Organization Item Attribute Controls You do not have to change any other information about the item in fact, because information such as unit of measure, description, and so on is maintained at the Master level, you know it is consistent in each organization. Finally, you change the planning and build attributes in each organization to describe the different behavior of the items in those organizations. Next, you assign the item to both the warehouse and the factory. Using an Item Master with a warehouse and a factory as the other organizations, you define the item just once-in the Item Master. In the factory, the item is MRP planned and built. In the warehouse, the item has independent demand and is min-max planned. Suppose you have a distribution warehouse and a manufacturing factory. The item master organization uses itself as the Item Master. This is also where you assign child organizations to the Item Master. Use the Organization Parameters window to specify that organization as the Item Master. See: Creating an Organization,, Oracle Human Resource Management System User's Guide. Use the Organization window to create the organization you want to use as the Item Master. You cannot copy items across item master organizations. You cannot associate items in one item master organization with another item master organization. In addition, multiple item masters are distinct entities, with no relationship to each other. This can make item definition and maintenance confusing. Oracle also recommends that you do not define multiple item masters. However, for simplicity, Oracle recommends that you limit the Item Master to just an item definition organization. There is no functional or technical difference between the Item Master organization and other organizations. After you define an item in the Item Master, you can assign it to any number of other organizations. Other organizations (child organizations) refer to the Item Master for item definition. To distinguish it from others, we call it the Item Master organization. Implementing the Item Master Organization Once you have defined items, you can set up other parameters, such as item cross references, to control the use of items. These enable you to maintain, group, reference, query, and delete your items. You must set certain controls and reference options before defining items. Copying Items with Category Assignments.Defining Customer Item Cross References.Status Attributes and Item Status Control.Implementing the Item Master Organization.This chapter covers the following topics:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |