Product Master Data Management

Get Involved. Join the Conversation.

Comments

  • Steven Cascio

    PDH rules only let you assign items to existing categories based on the time you wrote the rule, not to a catalog that is dynamically created within the rule.

  • Vinesh Phale

    Need help....

    I need to migrate Item master from existing oracle  Instance to a new instance. Since both the instance with the same oracle fusion platform. Can have a quick method to prepare Item upload FBDI template. 

     

  • Sureshwar Oka

    Thanks Shyam and Steve for the useful documents

  • Shivam Upadhyay

    DFF can be used for this and then you can have standard or custom reports(if any business logic required)  to print / share the data.

  • Sandip Roy

    Hello,

    Can you please elaborate your question? What do you mean by 'Harmonized Tariff'?

    Regards

    Sandip

  • Junaid Ahmed

    Many many thanks for the quick response. I just raised the SR and got the same response. 

    Cheers

  • Ramkumar Oduru

    If you got the error when you are trying to change the status of the NIR from Open to Definition then check the NIR type setup. 

    ====================================================
    There is an auto promote set for the Open status to Definition, which is
    causing an issue here, because internally the system is also trying to
    promote it to Definition and service is also trying to do the same.
    Disable the auto promote status for the New item Request type from Open to
    Definition and retry the flow.
    ====================================================

  • Ramkumar Oduru

    Hi Junaid,

    Yes, It worked for me. If you got the error when you are trying to change the status of the NIR from Draft to Open then check the 'Header' information in the Postman ( or which ever the RESTful tool you are using to call the REST API) . Headers tab should have the below values.

     

  • Junaid Ahmed

    Hi Ramkumar,

    Were you able to update the status via api? I am also getting the same error. Here is the payload, I am using:

    {
            "name" : "changeStatus",
            "parameters" :   [
            { "nirNumber" : "MEL_NIR_1037" },
            { "orgCode" : "IM"},
            { "toStatusName" : "Open" }
            ]
    }
    
  • Anand Dhinakaran

    Hi Steven,

    Thanks for the heads up. Can you please let us know what would be location which would hold these publication files? It would be great if you can throw some light on the reasoning behind this move? It will have high impacts to the integrations which are already built and might involve re-development in some cases. Can Oracle leave these processes to remain as-is to avoid possible discomforts to clients who are already using such functionalities? 

    There is no contradictions on enhancements as that is very much necessary but a change in the existing design will have impacts.

    Thanks,

    Anand 

  • kaleem khan

    Reclassification is typically used to redefine an item in inventory. Assume part is damaged or refurbishment in some way.

    For example, we have two different items, Item A and B, Item A has 10 Qty and Item B has 5 qty. Now we need to merge the quantities of Item A and B in Item C with new Cost.

     

    This scenario usually required in manufacturing companies in order to reevaluate the item cost.

     

     

  • Ravi Nadiga

    Could you rephrase "Item Reclassification"?

    We allow Item Class of an item to be changed from one to another, subject to certain constraints.
    Items can be assigned to multiple Catalog Categories.

  • Ravi Nadiga

    Attributes that are classified as Variant attributes must be associated to an item class. Once you associated these variants to an IC, the option of creating a 'style' item is available to the user. After a style item is created, you can then go and create SKUs associated with this style item. 
    In your case, I suspect the attributes are not 'classified' as Variants. You need to mark the attributes as variants in the attribute group definition task.

    a. Pls follow below steps

    1. Remove the Attribute Group from the Pages of the Item Class. (Query the item class and Edit)
    2. Remove the AGs from the Item Class
    3. Once this happens, the items belonging to this item class will NOT have the page, Attribute groups and attributes
    4. Deploy flexfields so that any previously existing artifacts gets updated.
    5. Query the child item class - Edit.
    6. Associate the AGs to the Item Class and then add these AGs to the Page. Redeploy EFF.

    b. Style Items can be created IF the item class has atleast one variant attribute group. When you define Attribute Group, you have the option of making it as a variant. Create variant attributes under this attribute group. Associate this variant attribute group to the required item class. In the create item flow, you will get an option of creating a style item. Once you create  a style item, you can further create SKUs associated with this style item.

    Pls refer SCM – Managing Product Variants in Product Hub Cloud  that has a recording of a session where we explain this in more detail.

  • Steven Cascio

    Sorry for the confusion, we seed only on DFF for categories, but you have multiple segments, each segment can have its own value set.

  • Steve Orford

    So can I add multiple DFF's under manage category descriptive flexfields? It doesn't seem to allow me to do that.