Robert, thank you for the information. Unfortunately we don’t see the Manual Pegging option on RMB. I have checked everything I can think of in the permission sets related to pegging and given permission to those DB objects related to pegging but still no success. I did find the Pegged Work Order Material Lines screen a couple of weeks ago but there are no options on it to adjust the peggings. Is there any way out could start your debugger and run that manual pegging step then send me the package/procedure that’s ran? That would help me track down which database objects to start targeting for permissions.
Thank you for the information Thilini. I’ll see if we have any of these fixes applied but I don’t believe we do. For the jobs to run in parallel, is that a matter of configuring the background job queue to allow for multiple jobs to execute at the same time? I have setup a separate job queue for these calendar generation jobs to execute but I currently have it set to 1 process, I wasn’t sure if setting that to a higher number would cause any conflicts with multiple PM generations running at the same time.
Thank you for the reply, unfortunately the PO can’t be cancelled due to the peggings. We receive an error when attempting to cancel that there are existing peggings and that it can’t be cancelled. Also, I’m the resident IT guy and sys admin so that option obviously isn’t too great for us. We don’t have any customizations in place to hide the options and I can’t find any permissions issues that would be hiding the pegging options from the users. I may have to open a ticket with IFS, that’s not my favorite path since that’s usually a long and tedious experience but that may be our only option.
Thanks for that suggestion, I had not considered permission issues since it’s working with other LUs (like ActiveSeparate and HistoricalSeparate). However that appears to be the issue because once I logged in as the app owner as you suggested it works as expected. I’ll track down what permissions are missing for the WorkOrder LU and correct that. Thank you for all of you suggestions and assistance!
We are on Apps 10 UPD 9
I agree, I would much rather find the root of why the Object Details is not working for the WorkOrder LU. I performed the steps you suggested and still get the same results….
Using ActiveSeparate seems to work well, my only concern with that is when the work order is finished it will move to HistoricalSeparate and the connection is broken. Can the Object Connection Transormation process be used in this scenario? (I’ve not done anything with the transformations before…...)
My apologies, I should have narrowed that search a bit more. The WorkOrder LU is the target here, which is where I originally placed the IncidentObjectConnection string. I recently added it to the ActiveWorkOrder and HistoricalWorkOrder as well just to do some testing and see if that may have an impact, Here’s a cleaner screenshot of what I’m actually trying to do:
Sure, here it is….
I do see the values in the Object Key column. I had not thought of refreshing the cache, I just did that but get the same results.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.