Announcement

Collapse
No announcement yet.

Day duration vs lookup issues in service type

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Day duration vs lookup issues in service type

    Hi all,

    Urgent inputs are required. In our production environment we had lanes in service time tables wherein sometimes same lane with 2 different names were there and the service type was lookup. so for example lane x and lane y both going from A to B were there. lane x had 2 days service time and lane y 3 days.OTM in the RIQ used to pick up the least time.So OTM picked 2 days.

    Now since we wanted to use calendars we changed to day duration service type. But OTM now in the RIQ is using the higher service time.MEans in the earlier example it is picking up 3 days.

    Does changing to dayduration leads OTM to pick up the higher service time?? Please enlighten.

    Regards
    Mithun

  • #2
    Re: Day duration vs lookup issues in service type

    To answer your question: changing to DAYDURATION does not result in a longer service time.

    However, there is quite some other stuff to consider to be able to give you more helpful advise. What is the setup of your Rate Service Calendar for example?

    If you look in the logfile you will be able to see what dates OTM calculates so you can deduce where things go wrong.

    Comment


    • #3
      Re: Day duration vs lookup issues in service type

      Lourens.

      Thanks for the response. Yes I agree that day duration has no role to play here. Tested the same several times in dev box and results were similar to production but strangely OTM RIQ even for look up service type for the same 2 lanes in service time picks sometimes the higher transit time and sometimes the lower.

      So my question here for all is the following:

      1. Does OTM caluclates picks up service time for any service type which gives the least time for 2 lanes with similar lanes but different x_lane_gid in service_time table?
      2. Or does OTM pick up the longest time for the above?
      3.Or OTM picks up randomly a service time from the same set of lanes present in the service time table?
      4.Or OTM picks up the service time for the lane which it encounters first while going through the data base?

      The log files for service time and service time details do not mention which lanes it is going thorgh. It only mentiones the rate service and the service days for that lane. Does not evaluate the similar lanes in that rate service?

      In our production system in Oracle EBS due to this incorrect service time sent by OTM the invoicing to customers is hampered since the drop date at ship to location is not always correct which triggers invoicing in Oracle??

      Kindly clear this confusion.

      Regards
      Mithun

      Comment


      • #4
        Re: Day duration vs lookup issues in service type

        If this is a production issue, than by all means, get Oracle Support involved: they should know the rules about service time calculation

        Comment

        Working...
        X