My Oracle Support Banner

Error "Fetching array element 0: index is not in range 1 to 0. (180,252)" or "Fetching array element 2: index is not in range 1 to 1. (180,252)" when Creating a Price Rule or Upgrading from a Release < 8.9 to a Release >= 8.9 (Doc ID 1235774.1)

Last updated on JULY 05, 2023

Applies to:

PeopleSoft Enterprise SCM Order Management - Version 8.9 to 9.1 [Release 8.9 to 9]
Information in this document applies to any platform.

Symptoms

1) The below error is issued when attempting to create a new Price Rule (navigation: Pricing Configuration, Create Pricing Information, Price Rules Maintenance):

Fetching array element 0: index is not in range 1 to 0. (180,252) EOEP_PRICER.SaveLogic.FormulaTree.Tree.OnExecute Name:PopUntil PCPC:8705 Statement: 171
Called from: EOEP_PRICER.SaveLogic.FormulaTree.Tree.OnExecute Name:Push Statement: 185
Called from: EOEP_PRICER.SaveLogic.FormulaTree.Tree.OnExecute Name:BuildTreeFromString Statement: 43
Called from: EOEP_PRICER.SaveLogic.FormulaTree.Tree.OnExecute Name:SearchTables Statement: 10
Called from: EOEP_PRICER_FOUNDATION.EOP_RULE.ProcessLogic.OnExecute Name
While fetching the value of an array element, the index was not withing the length of the array.

 

2) The below error is issued when upgrading from a Release < 8.9 to a Release >= 8.9:

Fetching array element 2: index is not in range 1 to 1. (180,252) EOEP_PRICER.SaveLogic.Combination.FindCombinations.OnExecute Name:GenWhereClause PCPC:4949 Statement:95

Called from:EOEP_PRICER.SaveLogic.Combination.FindCombinations.OnExecute Name:FindLessUsedKeys Statement:24
Called from:EOEP_PRICER.SaveLogic.SearchTables.OnExecute Name:FindLessUsedKeys Statement:63
Called from:EOEP_PRICER.SaveLogic.SearchTables.OnExecute Name:Insert Statement:40
Called from:EOEP_PRICER.SaveLogic.SearchTables.

Message Set Number: 180
Message Number: 252
Message Reason: Fetching array element %1: index is not in range 1 to %2. (180,252)

Process 1 ABENDED at Step UPG_EOEP.KeyValue.UpdKyVal (PeopleCode) -- RC = 24 (108,524)
Message Set Number: 108
Message Number: 524
Message Reason: Process 1 ABENDED at Step UPG_EOEP.KeyValue.UpdKyVal (PeopleCode) -- RC = 24 (108,524)

Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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