Monthly To Weekly Conversion When Start Date And End Date Are 5 Weeks (Doc ID 1614546.1)

Last updated on JULY 03, 2017

Applies to:

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

Symptoms

On : 12.1.3 version, Demand Processor Related Issue

RLM Monthly to Weekly Conversion when start date and end date are 5 weeks.
When User sends monthly demand of 5 week
Start Date - End Date > Oracle converted to 4 weeks of weekly, instead of 5 weeks. 

Does Oracle use the start date and end date parameters when it changes to weekly,
or does it just assume 4 weeks and leave the last week with 0 demand? 

The document says this can be controlled in the Ship Delivery Patterns, but since this 
appears to be weekly, users cannot understand how that would work. Sometimes the 
user sends 4 monthly as 4 weeks and some times as 5.

What are the Options?

ERROR
 Entering DETERMINE_SDP_CODE (10/03/2013 13:25)
  ShipDeliveryRuleName
  use_edi_sdp_code_flag ==> Y
  DefaultSDP ==> N
  Entering GET_CUSTOMER_NAME (10/03/2013 13:25)
  Exiting GET_CUSTOMER_NAME (0 seconds)
  Entering GET_ERR_MESSAGE (10/03/2013 13:25)
  Index ==> 1
  x_ErrorMessage ==> The Use EDI SDP code flag for Ship From Org EUD, <Customer Name> and address <XXXXX> is set to Yes.
  Please ensure that a valid Ship Delivery pattern code is passed in the schedule. Using Default Ship Delivery Pattern Code N.
  Exiting GET_ERR_MESSAGE (0 seconds)
  null input sdp, defaults applied
  x_ReturnStatus ==> 1
  x_SdpCode ==> N
  Exiting DETERMINE_SDP_CODE (0 seconds)

ProcessOrderAPI Error ==> Error: Import order line has failed as order lines were not found.
  interface line ==> 77023
  l_source_document_id ==> 59001
  schedule_header_id ==> 59001
  l_header_id ==> 38002
  order_header_id ==> 38002
  x_msg_level ==> W
  x_msg_name ==> RLM_PROCESS_ORDER_WARN
  l_msg_level ==> W
  Entering GET_ITEM_NUMBER (10/03/2013 13:25)
  Exiting GET_ITEM_NUMBER (0 seconds)
  x_msg ==> Error: Import order line has failed as order lines were not found.
  Message at index ==> 10
  Message Found ==> Workflow activity Ship has failed. Please fix the errors and retry the activity from the Order Form or the Workflow Monitor.
  get message context
  schedule line ==> 59001
  ProcessOrderAPI Error ==> Workflow activity Ship has failed. Please fix the errors and retry the activity from the Order Form or the Workflow Monitor.
  interface line ==> 77023

STEPS
1. Responsibility: Release Management
2. Run DSP
3. ErrorMessage ==> The Use EDI SDP code flag for Ship From Org EUD, <Customer Name> 
    and address <XXXXX> is set to Yes. Please ensure that a valid Ship Delivery pattern code is passed in the schedule. Using
    Default Ship Delivery Pattern Code N.
4. ProcessOrderAPI Error ==> Error: Import order line has failed as order lines were not found.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms