My Oracle Support Banner

Location To Zone Transit Time Setups Are Not Used by ATP, Get Zero Days Transit Time (Doc ID 1491690.1)

Last updated on OCTOBER 01, 2018

Applies to:

Oracle Global Order Promising - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On :  12.1.3 version, ATP based on planning data

ACTUAL BEHAVIOR  
---------------
Upgrade from 11.5.9
Arrival type order expecting offset of request date to reflect transit time to customer site.

Using ZONE level setups for transit time
- Internal location - ORG TO ZONE type setup in transit times form
have about 100 types of transit methods - NONE are checked as default method
transit method passed to ATP by OM for each order

ATP does not use the transit time passed.

ATP session file session-17683166
in ZIP file - ses_log.rar
 shows

Records Retrieved := 2
*****  number of records := 2
Begin Initialize_Set_Processing
Call_ATP_No_Commit: j : 1
Call_ATP_No_Commit: requested_ship_date :
Call_ATP_No_Commit: requested_arrival_date : 21-SEP-12
.....

GET_ITEM_ATTRIBUTES: l_source_org_id =
GET_ITEM_ATTRIBUTES: get_item_attr ATP flag is Y
GET_ITEM_ATTRIBUTES: get_item_attr ATP components flag is N
Schedule: ship_method: 000001_UPS SCS_A_D2D
Schedule: internal_org_id:
Schedule: Inside customer_site_id code
PROCEDURE get_delivery_lead_time
   org from: 191   to:
   loc from:    to:
   instance from: 21   to: 21
   customer id: 47854   site_id: 156398
   supplier id:    site_id:
   session_id: 17683166
   partner_site: 156398
   ship method: 000001_UPS SCS_A_D2D
   p_partner_type:
   p_party_site_id:
   p_order_line_id:
location to:
location from: 111
********** get_transit_time **********
loc from: 111 to:
instance from: 21 to: 21
session_id: 17683166
partner_site: 156398
ship method: 000001_UPS SCS_A_D2D
Using region level transit times
Using default transit times
********** get_transit_time **********
loc from: 111 to:
instance from: 21 to: 21
session_id: 17683166
partner_site: 156398
ship method:
Using region level transit times
transit_time:
ship_method:
transit_time:
ship_method:
   ship method =
   delivery_lead_time = 0
END get_delivery_lead_time
Schedule: G_PARTNER_ID = 65899
Schedule: G_PARTNER_SITE_ID = 152920


EXPECTED BEHAVIOR
-----------------------
Sales Order schedule ship date should follow the transit times defined for the Ship Method
Ship method for zone1 indicates schedule should be offset 3 days. Ship Method for US Zone indicates 2 days. Order ships late

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Order Management Responsibility
2. Create a Sales Order
3. Notice the transit time for the ship method is not being followed - no offset of Requested date to Requested ship date or requested arrival date.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Shipping schedule date is incorrect - effects customer receipts

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.