This content has been marked as final. Show 4 replies
Dear Mr. Govind,
we have followed all the Project Implementation Setup for the new operating unit except for the Implementation options which we have to fill up for each operating unit.
In the implementation Options form in the first tab 'System' there are many fields to be filled up.
For 'Summarization period Type' we choose 'G L Period' and based on this the fields 'Calendar Name' and 'P A Period Type' automatically gets populated.
But in our case the 'P A Period Type' is not getting populated.
Can you let me know where we can link the 'P A Period Type' to the chosen 'Calendar name'?
Also there is a check box - 'Maintain common PA and GL Periods'. If we tick this check box, a message says: 'The Period Type and Calendar of the PA Period does not match the Period type and Calendar of the corresponding GL Period.'
Can you please let me know where to create the PA Period based on the corresponding GL periods?
Thanks everyone for your updates.
Found out that it's a bug in Oracle EBS.
We should not create a project template using a responsibility through which you can see all the operating units at the header level.
We should create a responsibility and assign only one particular Operating unit profile to it and then proceed to create the project template.
This problem would not come.