Comments

  • 1-3 of 3
  • William Brand

    Hi Pramod,

    My team owns the schedule objects. I'm not familiar with the specifics of that error, but I can say that we do not presently support the use of the Flexible sub-type of Time shifts for Maintenance.  Because work definitions are planned out in detail to the minute, the decision a few years back was to restrict the use of only Punch and regular Time Shifts.  The idea of a flexible start or end time for a resource wasn't contemplated by the manufacturing team - who own the work definition.  We also do not support the use of Elapsed or Duration types.

    So if it's possible to model your shifts without using the Flexible sub-type, please do.  I believe you should not encounter any further errors.  If the flexible sub-type is something you believe you need, then I would recommend making this as an Idea in the ALM (Maintenance) lab and alerting me here.  Our team does not have a dedicated lab, and we'd need to coordinate with ALM and Manufacturing to consider the feasibility.

    Hope this helps explain matters,

    Bill

  • William Brand

    Hi Travis,

    While there is not yet the capability to copy or duplicate an inventory organization such that the items are copied as you describe, the PIM suite does have a feature for item grouping.  The basic concept is that  you can collect localized sets of orgs, with one serving as a local parent and all of the child orgs inheriting the item definitions.  An organization may be deemed a definition organization, and will be responsible for the item definitions. It serves as the parent.  Any other organization may be set up as a reference organization, pointing to a definition org.  All of the items for the reference organizations are inherited from the definition organization.  The functions for assigning these two states are controlled as actions in the inventory organization parameters parent/manage page. You can find more documentation on the capabilities here:

    https://docs.oracle.com/en/cloud/saas/supply-chain-management/19b/faipr/defining-item-organizations.html#FAIPR3174373

    Hope this helps!

    Bill

  • William Brand

    Hi Alberto,

    The flex field behavior is centrally owned by the Applcore team. Unfortunately our product team doesn't have any control over the behavior that you're seeing.

    I've spoken to them, and was given a quick answer that it is possible. You have to use table validated value sets, and use bind variables in the where clause to reference prior segments.  If you have additional questions about this suggested approach, I'd recommend using Support to assist in getting more specifics from the Applcore team.

    Regards,

    Bill