Planners Not Defined As Current Employees And No Way To Create An Employee In Ascp
(Doc ID 1380069.1)
Last updated on AUGUST 09, 2018
Applies to:Oracle Value Chain Planning Integration Base Pack - Version 3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 23-April-2013***
When collecting from JDE, planner codes are created in ASCP but cannot be linked to employees. Employees are not collected and the employee_id field in msc_planners cannot be set. This causes a warning popup each time a planned order is checked for release back to JDE. The warning states "The planner for this item is not defined as a current employee. Please define this planner as a current employee in the source database and recollect".
The suggested solution is not valid for E1 customers or legacy customers because they will not have access to the HRMS module to define employees. The attached document demonstrates the steps to complete (in the source system) to avoid the warning from happening. For E1 customers and legacy customers, a manual update of the employee_id field in table msc_planners is required.
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
|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.|