EBS R12 MRP Back Scheduling

Question

Business has not been able to set up MRP for back scheduling logic. Business question - was If the fix LT is 5 days then my DJ will go back or forward 5 days.
So, why are my DJ’s not going back 5 days?
Advice given that is not always working was -
The issue is caused by the an incorrect routing setup. The assemblies routing resources are not scheduled and/or there was no "time" in the routing steps.
Change the routing resources to scheduled and ensure the correct rates are in place for all routing steps.
1. Navigation path: Bill of Materials > Standard Operations, using an existing operation for a job that exhibits the bad behavior with start & completion dates.
2. Select the appropriate operation and click on the Operation Resources button.
3. Click on the Scheduling tab and check the value for the Schedule field. If it is not already Yes, make it so.
Question to forum thread is if there is another MRP based configuration that must be set to automate back scheduling of planned orders.

Answer 1

Thanks Rod and thanks for your great integration to EBS document btw, it had help me allot getting my own SSO solution working.
I ended up doing this for the LOGOUT routine and it works:
l_url := fnd_profile.VALUE('APPS_JSP_AGENT') ||
'/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE';
owa_util.mime_header('text/html', FALSE);
owa_util.redirect_url(l_url);
owa_util.http_header_close;
apex_application.g_unrecoverable_error := TRUE;
For some reason I had to change it a bit, the OA_HTML worked, the servlet URL did not.
Could be that I am still testing in my R11 env, still have to move it back to R12.
I also found that this worked too, though I liked the OAHOMEPAGE more as its simpler. But included this for anyone else that may be interested.
l_url := apps.icx_portlet.createexeclink(p_application_id => 809
,p_responsibility_id => 56616
,p_security_group_id => 0
,p_function_id => 16524
,p_url_only => 'Y');
owa_util.mime_header('text/html', FALSE);
owa_util.redirect_url(l_url);
owa_util.http_header_close;
apex_application.g_unrecoverable_error := TRUE;
In this example I hard-coded the IDs (as I was testing) but you can get them out of the session easily enough.
Edited by: attis on Nov 3, 2011 6:35 AM
Edited by: attis on Nov 3, 2011 6:36 AM
Edited by: attis on Nov 3, 2011 6:36 AM
Edited by: attis on Nov 3, 2011 6:37 AM