Product Development

Get Involved. Join the Conversation.

Topic

    Minna Muikku
    19 A: New 'Public check box' in Edit Item Class: how...
    Topic posted February 5, 2019 by Minna MuikkuSilver Medal: 2,000+ Points, last edited February 5, 2019, tagged Product Development, Product Hub 
    151 Views, 1 Comment
    Title:
    19 A: New 'Public check box' in Edit Item Class: how this chek box can be ticket?
    Summary:
    There is a new check box in Item class atributes, but we don't know how to tick that box
    Content:

    Since uodating in 19A we noticed that there is a new 'Public' check box on "Edit Item Class" page. We believe this needs to be selected in (now it is deselected by default and it thus we cannot create new items).

    in https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/faipr/defining-items.html#FAIPR161716 iit s said:

    Item classes have a Public check box, which when selected indicates that all items in the item class are public. All new item classes, including its child items and child item classes, are public by default, and do not require data security to be set. To make a child item private, you must deselect the Public check box in the Data Security dialog box.

    How this check box can be selected? Screenshot attached

     

    Br,

     

    Minna

    Image:

    Comment

     

    • Kumar

      The new functionality for public item classes applies only to new customers that are installing 19A for the first time. Existing customer will have their current data security state migrated during the 19A upgrade process which will mean the Root Item Class Public flag will be un-checked and disabled. For existing customer, since the Root Item Class is always in the private state, they will not be able to use item classes in the public state.

    • Kumar


      https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/pm/releases/19A/19A-scm-pm-wn.htm#F5952

      Item data security management has been enhanced to provide a new set of capabilities that extend existing data security modeling. You can now secure items by entering data security grants only for the item or set of items that require security. The remaining items will be accessible to all users.

      Prior to this update, item data security had only a single state in which data security must be entered to access items. With this update, item data security is enhanced to provide a second state where no item data security must be entered for the items and all users have access to the items.

      For new installations, the Root Item Class is always public, where you can create items without entering data security. In this update, you have the option of modeling the item data security by deciding on which items will be accessible to all users and which items require restricted access. You can model the items that are available to all users by creating item classes under the Root Item Class that are public. In public item classes, all items will be public. You need to enter data security grants to control access to user-defined attribute groups for the items.

      You can model the items that require restricted access by defining item classes under the Root Item Class and making these item classes private.  In private item classes, all items are private. You need to enter data security grants for both the item content and the user-defined attribute groups.

      Prior to this update, you could model data access requirements by creating a duplicate item class and provide different data security grants for the items created within these item classes. With this update, you can use a single item class for the product classification, but apply data security to only the items that require data access control. For example, you are introducing a new tablet product into an existing line of tablets and this new item require limited access for a brief period. Previously, you had to create a new item class and duplicate the existing set up for the existing tablet item class. In this update, not only you can use a single, public item class for tablets, but also restrict the access to the new tablet item by making only the tablet item as private.