APAR status
Closed as fixed if next.
Error description
If you open up an out-of-box form and go to a locator field in the form, the query that is listed as a part of the field's 'Locator Query' properties may not appear when you click the picker and view the list of queries. An example of where this problem is seen is the [triContract] triLeaseAbstract form's triLocationLookupTX field. The 'Location - Find - Active Property, Building, Structure, and Retail Location or Lease' query is listed as the locator query, but if you click the picker next to that field you can not actually select that query. This has been seen in 3.4.2 as well as 3.5.2
Local fix
Perform these syteps to workaround this problem at an application level: -- Identify the Business Object and Locator Field having the problem -- Use Data Modeler to revise the Business Object in question -- In the 'Field List' window select the Locator Field having the problem -- Go to the 'Field Properties' and find where it says 'Locate Using' -- Click on what is listed above 'Edit Mapping' for the 'Locate Using' property -- In the area below where 'Business Object Name,' 'Assocyated string' and 'Locator Field' is listed, Do the folloiwng in this ssection: -> Note what is listed under 'Locator Field,' as you will need to reset this value -> Change the value of the 'Business Object Name' to be 'All' -> Set the 'Locator Field' value back to what it was set to originally -> Click 'Ok' -- Save the field changes you just made -- Republish the Business Object
Problem summary
If we need to show all the queries based on module then we need to check if theBO is the Base BO, then ignore retrieve all the query based on moduleId.
Problem conclusion
Resolved an issue where locator query against a base BO will now return all the queries in that module. This is targeted to the 1h2017 release.
Temporary fix
Comments
APAR Information
APAR number
IV95403
Reported component name
TRI APP PLTFM R
Reported component ID
5725F26RE
Reported release
342
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-24
Closed date
2017-04-28
Last modified date
2017-04-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
999
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"342","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022