Return History Collections Does Not Respect Include RMA Type Filter (Doc ID 1335745.1)

Last updated on DECEMBER 13, 2016

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Demantra Demand Management - Version 7.3.1 to 7.3.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 24-June-2013***

Symptoms


On VCP 12.1.3.1 integrated with Demantra 7.3.1

ACTUAL BEHAVIOR
-------------------------------------------
After running the Returns History concurrent request in Demand Management System Administrator using the Include RMA Types parameter filter, all RMA Types are collected into Demantra table MSD_DEM_RETURN_HISTORY.

EXPECTED BEHAVIOR
---------------------------------------------------
Expect only the RMA Types chosen in the parameter to be collected into Demantra.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Open Returns History concurrent request.
2. Chose at least one value for the Include RMA Type parameter.
3. Submit the request.
4. All RMA Types are collected.
Note: This is occurring whether using Complete or Net Change Collections.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Cannot collect only RMA Types are needed.

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