You are viewing this site as a guest. You can still ask questions and help others! Join our Dev2Dev IT Community to receive your own blog, share your knowledge, and much more.

Where are the SQL Objects kept in Maintenance Pack?

2 replies [Last post]
Guest's picture

A new Record View is delivered by PeopleSoft.
Where can you find the SQL object that is associated to that new view and how is it applied?

Applying MP6 to 8.9 (from file - not project migration) and we get an error in the SQL Build Process that reads as follows

Error: ASSIGNMENT_SRCH - SQL view has not been defined for this record. Record skipped. (76,32)

At that point the record existed in the environment and the radio button defined it as SQL View but when we opened up the SQL Editor no SQL existed. Once we pasted it in from Demo we were able to get passed this error.


CompShack's picture
User offline. Last seen 6 years 23 weeks ago. Offline
Joined: 12/09/2007
Posts: 167
Re: Where are the SQL Objects kept in Maintenance Pack?

I'm the wrong person to answer such a question, sounds like a PS Admin question to me. I will try to contact a friend of mine to help out on this one. I can tell you where the SQL is stored in the database but not in the maintenance pack. I will get back to you as soon as I get an answer!

Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog

Guest's picture
Guest (not verified)
Re: Where are the SQL Objects kept in Maintenance Pack?

Our issue begins with - We are applying Mulitple Maintenance Packs (6 thru 9). Did this in one environment loading files. Then created a project for Retrofits.

We attempted to do the same in another environment (as a pre test to production) using the same method (files - not by project). It appears that there is an XML file which sets the upgrade flags that I suppose changes as you go through the Change Assistant. So when we went to do this a second time using the same files the upgrade flags were not set correctly since the XML had changed from the original version.

We are attemping this again but this time we will go back to use the original XML version to see if this corrects our issues we had on the second attempt.

In short
1. Refreshed environment from Production. We applied MPs (one at a time) using Files to first environment. Some errors as normal but got to a clean SYS and DDD audit. After all MPs were applied we then did retrofits (saving these to a project. Went through a complete test and all was good.
2. Went to the next environment. Refreshed it from production. Applied MP6 from files but received different erros and some objects did not appear to come over correctly. Realized two things the upgrade flags were different and the XML file which sets the upgrade flags was much smaller then the original.

Hope this makes some sense ...
I'll let you know if this turns out better.