Amit,

This is what I came across.  Hope it helps you troubleshoot.  (source is https://blogs.oracle.com/PLM/entry/update_on_document_publishing_sample)

Running the Single Object Sample for the First Time

Do the following on a test or QA server.  Do not run any new program for the first time on your production server.  It will help if you have some experience with Agile PLM events and SDK programming, but that experience is not required.  Heed the instructions from Douglas Adams and Don’t Panic!  If you think it worthwhile, keep your towel handy.  

Download the 9.3.1.2 Document Publishing Sample and extract DocumentPublishingSingleObject.groovy (in the DocumentGenerationJava folder within OAS or WLS folders).  Open the script in a text editor.  At the top of the script there are many variables to control document publishing.  There are 3 you must update to match your system:

1. TEMP_PATH – this must be a real folder on your server.  Talk to your System Administrator.  For Windows, a path like c:/temp/ is typical.  Note that the forward slashes work fine.  For Linux, the path is likely /tmp/.  Your System Administrator may want to give you a specific subdirectory.  The script will place temporary files into this directory in order to create documents.
2. TEMPLATEHOLDER – this must be a real Object in your Agile PLM system that will have the Template attached.  In the unmodified script, this is a Document called BIPUB-000002-TMP. 
3. FILTER – this must be a real ACS filter in your Agile PLM system.  We recommend keeping this filter at a minimum (just Page 1, 2, 3) for your first try.  In the unmodified script this is “Default Quality Change Request Filter”.  The comment in the script mentions this is an API Name, but the full name works.

Install Word and BI Publisher Desktop.  If you are running 9.3.1.x or 9.3.2, use BIP Desktop 10g.  For 9.3.3, use BIP Desktop 11g.  This installation will add some menus into Word ADD-INS.  Don’t worry about those for now.  Create a new file in Word, add some simple text (HELLO WORLD!), and save as the file as RTF (template.rtf).  Attach template.rtf to your TEMPLATEHOLDER in Agile PLM.

The next steps require administrator privileges to setup a new event to trigger the script by creating an Event Handler (the code), an Event (the trigger), and an Event Subscriber (telling Agile PLM which code to run against the trigger).  Open Java Client, select the Admin tab, open System Settings > Event Management and perform the next steps.  

• Open Event Handlers node, create a new Handler of type Script PX with a name (Test Doc Publishing).  In the script box, replace the contents with the script.  Note: one easy method is to return to the text editor with the script open, select all the contents (Ctrl A), Copy (Ctrl C), then return to Java Client in the Script box, select all and paste (Ctrl V).  Select Ok to complete creating the Event Handler.  

• Open Events node.  Create a new Event of Type Extend Actions Menu with a name like “Create Document.”  Choose the class where you wish to trigger the Document Publish, for example all Quality Change Requests.  Select Ok.  

• Open the Event Subscribers node.  Create a new subscriber, skip down to Event and choose the new one “Create Document”, then choose the new Event Handler “Test Doc Publishing”, now select the generate button (123) next to Name, change Execution Mode to Synchronous, and select Ok.  You should now have an Event Subscriber called “Create Document Test Doc Publishing”.

The Event system is setup, so now we need to trigger this process for the first time.

Return to Web Client and open an object of the class you selected when creating the Event, in this example a CAPA.  Make sure there is content in the CAPA Cover Page fields; the exported XML will only contain fields with values.  In order to see the results of the script, select the Attachments tab. 

Now trigger the event by selecting Actions Menu – “Create Document”.  Within a minute, you should see 2 attachments, a PDF and XML, with the Object Number as the filename.  The PDF will contain the simple text (HELLO WORLD!), while the XML file will contain the dynamic contents of the object.

Congratulations!  You have completed the first step to creating a real document.  If the documents never showed up, proceed to the Troubleshooting section.  If the documents appeared, move on to the next section.

I like Adrian already.

Yes Anand, the recommendation is to NOT have users on any DEV instance and only access to PROD and any system you may use for user acceptance testing activities.

When we post the links we also mention the color of the GUI so users can keep them straight.

Another tact is to only post the PROD link and send the UAT link out only when necessary.  I keep a internal page for the PLM Team with all the links so at the very least we have a library of links to draw upon.

Just a quick note Anand that you are not alone.  I also find that node balancing is tough and am constantly bouncing to regulate data consistency on 9.3.2.  We also do not have a solid solution other than to keep a vigilant eye on this.

If I recall correctly, for PPM in 9.3.4 there is an option to set the work week to 5 days and different calendars.  Before that it is pretty much what you are seeing.  Others chime in if my recollection is missing some gaps.

Anand, if you are considering upgrading to 9.3.4 check it out.  I believe this issue may be resolved as they bring in calendar options.

Anandh, I have not yet seen this issue.  Can you identify a pattern to these that are not reporting correctly?  Is the user simply going in and marking the task complete rather than updating the percentage?  Do some of these automatically roll up to 100%?  I am looking for a pattern to the issue so any additional information would be helpful.

Of course you do.  The event is the % update.  The PX could look at all the sub items to determine the parent %.

Are you using single sign on through your LDAP?  Have you checked that setup if applicable?

Did SolidWorks integration work previously?  Or are you attempting to set this up from scratch?

This is indeed a very interesting issue.  I would recommend limiting any variables and see if you can redirect to port 8080 on the new server.  I know this seems comical but I have seen some very comical solutions when it comes to Agile in the past.