EAR 9.2: Direct Journal Payment Accounting Entries Not Displaying Any SpeedType Key Values if User’s Primary Permission List Is Longer Than 8 Characters (Doc ID 2830759.1)

Last updated on DECEMBER 31, 2021

Applies to:

Symptoms

Users are unable to select any SpeedType Key existing values when using the look-up feature, as it returns a no matches found error when trying to select a valid value at the Direct Journal Payment at the Accounting Entries creation page, (Page PAYMENT_MISC_DST). All SpeedType Keys have been configured with the type of Universal, meaning all Users should be able to choose those values.

This seems to take place for those Users whose PeopleTools Profile Primary Permission List is more than 8 characters in length. The delivered codeline from SQL View PS_SPEEDTYP_VW is only taking a substring of first 8 characters from PSOPRDEFN.OPRCLASS, and this filters out all existing SpeedType Keys.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as User ID VP2
    2.- Navigate to: PeopleTools > Security > Permissions and Roles > Copy Permission Lists
    3.- Copy currently delivered ALLPAGES Permission List to a new value of VERYLONGPERMISSIONLIST
    4.- Navigate to: PeopleTools > Security > User Profiles > User Profiles
    5.- Open existing User ID VP2
    6.- At the General tab, change the Primary Permission List from ALLPAGES to VERYLONGPERMISSIONLIST
    7.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Design ChartFields > Define Values > Define Speed Type
    8.- Create a new SpeedType Key OSS-ABC, under Set ID SHARE, making sure that Fields User ID and Primary Permission List are left blank (This makes it Type Universal)
    9.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
    10.- Proceed to create a new Regular Deposit under Deposit Unit US001, and list of Payment transaction, marking it as Direct Journal
    11.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Direct Journal Acctg Entries
    12.- Select the newly created Regular Deposit ID, and its Payment ID that is set up as Direct Journal
    13.- Go to the Accounting Entries tab
    14.- Click on the SpeedType button
    15.- Click on the look-up icon for the SpeedType Key field
    16.- The Look Up SpeedType Key view shows no matches

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ERROR MESSAGE:

    " No matching values were found. "

Functional Team is unable to define the needed Accounting ChartField values for the Distribution Lines of Direct Journal Payments by using already configured SpeedTypes, and as such, these transactions cannot be further processed in the system. Not using already configured SpeedType Keys can lead to Accounting mistakes by choosing wrong values.

When the User clicks on the look-up icon from the SpeedType Key field, the system's view should provide a list of available values to choose from under the defaulted Set ID, allowing proper completion of the needed Accounting Entries.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.