E1: 17: R1775 Service Orders Vertex Incorrect Division Code Being Passed To Vertex
Last updated on JULY 08, 2016
Applies to:JD Edwards EnterpriseOne Service Management - Version 9.1 and later
Information in this document applies to any platform.
Currently the R1775 S&WM Work Order Work File Generation when run uses the Service Orders Site Number / ALKY by design. However when using the R1775 Vertex processing options in conjunction with the Vertex Constants and users have a specific business need to setup the Vertex Constants with a Division Code setup to use the Service Orders Branch Plant / MMCU to pull relevant Tax information and not the Site Number / ALKY it’s not possible. The issue is the R1775 pulls the Site Number ALKY by design, Vertex then has no choice and uses the Same Site number passed from the R1775 in conjunction with the Division Code for its output. This Cause the system to use the Site Number in conjunction with the Vertex Constant Division Code setup.
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