Comments

  • 1-10 of 10
  • Sudarshan Srivatsan

    Hello Vivian,

    I have not received an answer to this so far. There is no SR as such for this.

    I came across the workaround in the aforesaid note id and found that perhaps it's not actually working as intended. Therefore I had a generic query on whether there is any additional condition required in the product transformation rule recommended in the note id or if there are any related pricing setups to be done for the above case to be achieved properly.

    Please advise.

    Thanks,

    Sudarshan 

  • Sudarshan Srivatsan

    Thanks all for your respective replies. 

    Does anyone know if and when the functionality to assign SO lines to a single shipment set irrespective of DOO is expected? 

    Regards,

    Sudarshan 

  • Sudarshan Srivatsan

    Hi Ramadoss,

    Thanks for your reply.

    We have cases where field service engineers require several items to be shipped for repair.

    Some of these lines may have a different DOO based on business process specific to that item. However, the objective is to ensure that all the line items are shipped together to make the field service more efficient instead of shipping some partially. 

    Therefore, we are looking to see if this can be controlled on the OM UI via shipment set. 

    Regards,
    Sudarshan 

  • Sudarshan Srivatsan

    Hi Megan,

    Thanks for your response, appreciate it. 

    So if I understand this correctly, the Enrichment Rules Setup does not automatically interface a Transfer Order to WIP (the way it does to OM when
    the 'Ship Through Order Management' option is selected). 

    The work order relate Enrichment Rule is independent of a Transfer Order and can also be used for work orders in general i.e. standalone, back-to-back related work orders etc. 

    Would you therefore have any generic examples or guidelines to follow for a work order related Enrichment Rule, for example WO related to specific INV Orgs only. 

    Regards,
    Sudarshan  

  • Sudarshan Srivatsan

    Hi Sunil,

    Thanks for your inputs. Yes we understand the Reservations route is one such option that can be used at present, especially given the fact that Pick Confirm is auto in our process hence selecting a different lot number at this stage is not an option we have at present.

    However, to cut down on the overall effort required to do this from a user point of view, I was looking for a similar functionality in Manage Shipment Lines (like Record Serial Numbers) 

    Thanks,

    Sudarshan  

  • Sudarshan Srivatsan

    Hello Sunil,

    Yes if the item has a secondary UOM setup, the same shows up in the 'Manage Shipment Lines' screen. However, since our Business as such does not maintain a secondary UOM, the expectation is for the UOM on the OM screen to seamlessly flow into Shipping so both OM and Shipping are in synch from this perspective.

    We are working with Oracle support to see if an Enhancement is likely in the future. 

    Thanks,

    Sudarshan 

  • Sudarshan Srivatsan

    Thanks Sunil. 

    Yes we thought as much. As such there does'nt seem to be a standard design of doing so, at least not in the current scheme of things. 

    We will probably look forward to any such enhanced functionality in the upcoming releases.

    Thanks,

    Sudarshan 

  • Sudarshan Srivatsan

    Hi Sunil / Prasad,

    Really appreciate all the inputs and suggestions, thank you.

    Yes while the aforesaid functionality in the latest release (on creating RMA without having to refer the original order) may be a workable option, we are still trying to figure out a way to negate the line type defaulting (since we don't have a Business need as such to create separate order type for RMAs and doing so may result in additional overhead, which is something we will avoid since the volume of RMAs vis-a-vis outbound sales order is lesser).

    Therefore, if we are to use the above functionality, the User will still have to be alert to change the line type for RMA during RMA creation, which is something we can deal with consider the low volume of RMA vis-a-vis sales orders. 

    Thanks,

    Sudarshan 

  • Sudarshan Srivatsan

    Hi Prasad,

    Thanks for your inputs.

    We did think of using a new order type for RMAs, however the Business process requires that we use the same order types for Sales Order/RMA Orders and drive the differentiation based on line types. Hence this approach may not work for us :) 

    Also, if RMA orders have CATEGORY = Order, do you know which cases/orders would fall in the bucket of CATEGORY = Return Goods. Shouldn’t RMA ideally be CATEGORY = Return Goods.

    Thanks,

    Sudarshan 

  • Sudarshan Srivatsan

    Hi Sunil,

    Yes in general it is the BUY line type that defaults. However for our Business, we have defined custom line types and have mapped them to respective Orchestration Processes. We then defined a pre-transformation rule as below to default this line type based on a few IF conditions as below - 
    -----------------------------------------------------------------------------------------------
    If Business Unit(Header) = *** and If Order Type(Header) = ABC and If Category(Header) = Order

    Then Line Type = XYZ
    -----------------------------------------------------------------------------------------------
    The requirement therefore is to default the line type based on order type and to this extent the above rule works fine. 

    However, the flip side is we see the aforesaid defaulting rule applies for RMA orders as well, even though one of the IF conditions is where CATEGORY = ORDER.

    My question is, is there a way to default the Pre-Transformation Rule such that it does not apply to RMA orders.(i.e. it should only apply to orders where CATEGORY = ORDER) 
    Thanks,
    Sudarshan