Hi Munawar

Please see my inline comments

Thanks & Regards

Saravanakumar K
From: Hussain, Munawar
Sent: Tuesday, February 17, 2015 11:49 AM
To: Kothandapani, Saravanakumar
Cc: Ramakrishnan ,Venkateswaran; Shariff, Abdul R.; Singh, Mukesh
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Saravana
As discussed, the justification provided for Period Close Variance as per the attached email was
incorrect, it really took us a hard way and long time to find out the actual reason
Observation:
1. System is automatically creating Period Close Variance transaction while closing
Inventory Period
[Saravana K] Yes. Period Close Variance This gets generated at the time of closing the period
when there is net activity for a Non-standard expense job(EAM Work Orders). EAM
jobs are period costed. Only a monthly account (specific period) of what has been
spent is needed. WIP Value does not carry over to next period
2. There is no variance taken into GL. All the variances are showing in Work Order Costing
only[Saravana K]
[Saravana K]
There will be no impact in GL. All Variances can be viewed in Work Order Form.
3. System takes all the actual transactions happened in that month related to Work Orders
[Saravana K]
Yes. Refer my explanation above
4. Create DR/CR entries using the same GL Account Code against the actual transactions
happened in that month (no impact in GL)
[Saravana K] We are maintaining same account for WIP Valuation & Variance Account In WIP
Accounting Class since we are following Average Costing.
5. Actual Transactions contains (WIP Issue, WIP Return, Labor Receipt etc.)
[Saravana K]
Yes . Also Purchases Happened for the related Work Order
Kindly confirm if above observation is correct and if we missed out any other element?
Moreover, there is no TCP and test script provided for this Fix. Appreciate if you do that at
earliest.
[Saravana K] Venkat will be sending the TCP /Test Script

Regards,
Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Ramanujam, Sunderraj

Sent: Thursday, January 29, 2015 11:20 AM
To: Hussain, Munawar
Cc: Dulba, Keni G.; Ramakrishnan ,Venkateswaran; Shariff, Abdul R.; Mansoor, Yasar;
Singh, Mukesh; Kothandapani, Saravanakumar
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Munawar
Please find attached Help file to check Period Close Variance with an example of one transaction
278901 taken from Period Close Exception report. You may check additional cases using the
helpfile.
As explained, Period Close Variance is calculated and accounted by system for Open Work
Orders for which there is a difference between Estimate and Actual.
Thanks
Sunder
From: Hussain, Munawar
Sent: Tuesday, January 27, 2015 5:27 PM
To: Ramanujam, Sunderraj
Cc: Dulba, Keni G.; Ramakrishnan ,Venkateswaran; Shariff, Abdul R.; Mansoor, Yasar;
Singh, Mukesh; Kothandapani, Saravanakumar
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Hi Sunder,
We have gone through your email and verified few transactions through WIP Transaction
Distribution
Can you please take few examples from the existing stuck transactions and show us why system
generated these transactions while closing Inventory Period?
We want to understand the system mechanism of generating these variances
Regards,
Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Ramanujam, Sunderraj

Sent: Tuesday, January 27, 2015 10:47 AM
To: Hussain, Munawar
Cc: Dulba, Keni G.; Ramakrishnan ,Venkateswaran; Shariff, Abdul R.; Mansoor, Yasar;

Singh, Mukesh; Kothandapani, Saravanakumar

Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Munawar:
Please find below further explanation for the Period Close Variance event.
INTRODUCTION
In operations / processes where EAM is in use and Work Orders are created to track jobs,
following accounting happens, where system Debits WIP Valuation and Credits WIP Variance and
vice versa, depending upon the difference. Oracle suggested to input same GL Code for both
WIP Valuation & WIP Variance, so that it does not create any financial impact in accounts, as it is
only for information purpose.
JOB CLOSE VARIANCE
This is the difference between Work Order Estimate and Actuals. This is calculated when Work
Order is Closed & accounted in the same period.
PERIOD CLOSE VARIANCE
This is also difference between Work Order Estimate and Actuals. However, this is calculated
when Inventory Period is Closed for Open Work Orders.
The accounting for the same happens as below:a) If the INV & GL Period are both Open, accounting for the same goes to GL, without getting
stuck in Interim Accounting Tables.
b) If the INV period is Open, but GL period is Closed, accounting lines get stuck in Interim
Accounting tables, because GL Period is closed.
In our case, PERIOD CLOSE VARIANCE was created by system when past INV periods were
closed together on 31-Dec-2014. And the accounting Date happened to be in respective INV
periods, for which GL was already closed, hence they got stuck in Interim Accounting tables.
Therefore, it is a standard behavior, which can be averted, if INV period is closed before GL
Period, in which case accounting would be created as under:
JOB CLOSE VARIANCE: In the event of closing Work Order/s
PERIOD CLOSE VARIANCE: In the event of closing INV period for the work orders that are
not closed.
Hope this clarifies. Please let us know in case you require further clarification.
Thanks
Sunder
From: Hussain, Munawar
Sent: Wednesday, January 21, 2015 9:36 AM
To: Ramanujam, Sunderraj; Singh, Mukesh
Cc: Dulba, Keni G.; Ramakrishnan ,Venkateswaran; Shariff, Abdul R.; Mansoor, Yasar
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Importance: High
Sunder / Mukesh,

We have fixed following Activities together in Dec-14 closing:

Phase 1 Cleared all Period Close Exception stuck due to Standard Rate issue
Outcome: Verified by Finance that all the data have been successfully interfaced to GL
Phase 2 Cleared all Period Close Exception stuck due to clearing Pending Resource
Transaction
Outcome: Verified by Finance that all the data have been successfully interfaced to GL
Observation We ran the Period Close Exception today as per your suggestion and found:
Jun-14 : 1833 Transactions
Jul-14 : 2148 Transactions
Aug-14 : 867 Transactions
Sep-14 : 3579 Transactions
Oct-14 : 1628 Transactions
Nov-14 : 2328 Transactions
Dec-14 : No Records Found
We are not at all convinced with sunders below response:
1. Why these unaccounted transactions not highlighted in our previous extensive activities
while clearing Period Close Exception and Inventory Period Closing?
Answer: These transactions arose after Inventory periods were closed and hence did not
exist in period close exception earlier. Oracle generated these entries with the old
respective period GL Dates(INV period were open), since respective GL periods are
closed, these transactions got stuck in Interim Accounting table.
While closing Inventory Periods; there were no errors found nor did system stop us from
closing the periods
Please provide us complete detail from where these unaccounted transaction appeared
again in Period Close Exception and WHY despite of all the past efforts ???
Appreciate your prompt reply
Regards,
Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Ramanujam, Sunderraj

Sent: Tuesday, January 20, 2015 9:47 AM
To: Hussain, Munawar

Cc: Mansoor, Yasar; Dulba, Keni G.; Ramakrishnan ,Venkateswaran; Singh, Mukesh
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Munawar
Please find below our clarifications for your questions;
Q Why these transactions are still not appearing in Period Close Exception?
Answer: DPE Period Close Exception report might have run for period name as Dec-14. Please
note that, since Dec-14 GL period was Open when Dec-14 Inventory period was closed, Dec-14
transactions went into GL. Hence, nothing appeared in the Period close exception report.
Transactions, which are stuck in the Interim Accounting Table, belongs to Jun-14 to Nov-14 period
and the respective GL periods were closed. Period close exception report should be run for
respective periods, i.e. Jun-14, Jul-14, Aug-14, Sep-14, Oct-14 and Nov-14, and it will show
exceptions relating to respective periods.
Q Is there a way to check these transactions from front end?
Answer: There is no way we can see all stuck transactions on the Screen.
Following are the ways to check the stuck transactions
1) Run DPE Period close exceptions report
2) Output of the Create Accounting program
Take the Transaction ID(from Period close Exception Report) and review the data from front-end
using the below navigation to check the transaction and accounting in front end

Input the Transaction ID (Source_ID_Int_1 that is seen in period close exception report sent by
us). Ensure to remove the date range. We have given Transaction ID 278901. Period close
variance exceptions dump was provided in previous mail.

Below form shows the accounting

Thanks
Sunder
From: Hussain, Munawar
Sent: Monday, January 19, 2015 3:26 PM
To: Singh, Mukesh
Cc: Mansoor, Yasar; Dulba, Keni G.; Ramanujam, Sunderraj; Ramakrishnan
,Venkateswaran
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Hi Mukesh,
Thanks for the clarification
We need to share all these justifications with Finance because it will hit the Journals. Please
clarify following points:
Q Why these transactions are still not appearing in Period Close Exception?
Q Is there a way to check these transactions from front end?
Regards,

Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Singh, Mukesh

Sent: Monday, January 19, 2015 3:15 PM
To: Hussain, Munawar
Cc: Mansoor, Yasar; Dulba, Keni G.; Ramanujam, Sunderraj; Ramakrishnan
,Venkateswaran
Subject: RE: Request 39525 FIN - Create Accounting - from daily log
Hi Munawar
Please check the clarification and let us know for any further clarification
1. Why these unaccounted transactions not highlighted in our previous extensive
activities while clearing Period Close Exception and Inventory Period Closing?
Answer: These transactions arose after Inventory periods were closed and
hence did not exist in period close exception earlier. Oracle generated these
entries with the old respective period GL Dates(INV period were open), since
respective GL periods are closed, these transactions got stuck in Interim
Accounting table.
2. What is the impact in GL after running Transfer to GL program for clearing
these transactions?
Answer: Please find attached the dump. Net impact is zero. Please review.
3. What is the root cause of these transactions? Will it appear again after
clearing?
Answer: Please find attached mail sent by Saravana explaining root cause of
these transactions.
Since INV period will be closing now onwards before GL period, this
problem will not appear.
Thanks
Mukesh Singh
CSC DPE Project - Support Manager
INDIA: +91.9873170033/9811303945
mukesh.singh@dubaipetroleum.ae

msingh28@csc.com

From: Hussain, Munawar

Sent: Monday, January 19, 2015 1:32 PM
To: Singh, Mukesh
Cc: Mansoor, Yasar; Dulba, Keni G.
Subject: Request 39525 FIN - Create Accounting - from daily log
Importance: High

Mukesh,
We have fixed every transactions appearing either in Period Close Exception Report, Inventory
Open Period and Pending Resource Transactions during year end closing
All the Inventory Periods have been successfully Closed till Dec-2014
CONCERN
1. Why these unaccounted transactions not highlighted in our previous extensive activities
while clearing Period Close Exception and Inventory Period Closing?
2. What is the impact in GL after running Transfer to GL program for clearing these
transactions?
3. What is the root cause of these transactions? Will it appear again after clearing?
Appreciate your further clarification
Regards,
Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Singh, Mukesh

Sent: Monday, January 19, 2015 1:14 PM
To: Hussain, Munawar
Cc: Mansoor, Yasar
Subject: RE: Request 39525 Assigned to you
Hi Munawar
Create Accounting program is completing in Warning. This means, there are some
unaccountable transactions exists in Interim Accounting Tables.
When we checked the program output, we found only the WIP Period Close Variance
transactions that are stuck in Interim Accounting Tables, due to which, the program
ends with Warning.
Once these exceptions are cleared using the Interim Accounting Table update script,
the program may complete with Normal status(If there are no-more un-accounted
transaction, new transactions keep on creating. ).
Steps(Please perform the following steps in PRE-PRODUCTION instance)

Execute the attached script

o P_ACCOUNTING_DATE => 01-Jan-2015
o P_PERIOD_NAME=>Jan-15

Run transfer to GL program Transfer Journal Entries to GL - Cost

Management from DPE Cost Management SLA responsibility
o Choose Batch Name as 39525- WIP Period Close Variance
transactions or any meaningful batch name to identify these
transactions in GL
After that run create accounting program and share the output for verification.

Hope it clarify. Please let me know for more information.

Thanks
Mukesh Singh
CSC DPE Project - Support Manager
INDIA: +91.9873170033/9811303945
mukesh.singh@dubaipetroleum.ae

msingh28@csc.com

From: Hussain, Munawar

Sent: Wednesday, January 14, 2015 3:12 PM
To: Singh, Mukesh
Cc: Mansoor, Yasar
Subject: FW: Request 39525 Assigned to you
Mukesh,
Can you please explain the attached email context in simple words?
Regards,
Munawwar
Ext : 2114
Core Behaviours: 1) Take Ownership of Issues 2) Do Simple Things Well with a Sense of Urgency 3) Follow
Up 4) Talk Face to Face 5) Respect your Colleagues
Please use the IT Service Catalogue as the primary tool to request Information Technology (IT) related
services

From: Ramanujam, Sunderraj

Sent: Wednesday, January 14, 2015 1:24 PM
To: Mansoor, Yasar
Cc: Singh, Mukesh; Ramakrishnan ,Venkateswaran; Kothandapani, Saravanakumar
Subject: RE: Request 39525 Assigned to you
Yasar
I received the Create Accounting output file from Mukesh. Thanks for arranging the same.
We analyzed and found that, period close exceptions that are stuck in Interim Accounting table
are the reason for the program to complete in Warning.
Just to give you brief, when Inventory periods were closed, system generated Period Close
Variance events, for WIP Variance, for each period that was closed. Since those periods are
closed in GL, they are stuck in Interim Accounting table. Munawar is aware of it. If these are
transferred to GL, the Create Accounting program may not end in warning.

You have already been using Update script to clear exceptions in Interim Accounting table. Same
script to be used, but ensure the following;
xe.event_type_code = 'PERIOD_CLOSE_VARIANCE' (it would have been either OSP or
RESOURCE_ABSORPTION for earlier needs)
Once done, please run Transfer Journal Entries to GL Cost Management program
After the above program is completed we shall check the performance of Create Accounting
program.
Please execute the suggested process in PRE-PROD.
Our version of the update script is attached for your reference, however, you may please use the
one you are already using with the suggested change.
Thanks
Sunder
From: Mansoor, Yasar
Sent: Wednesday, January 14, 2015 1:03 PM
To: Ramanujam, Sunderraj
Cc: Singh, Mukesh; Ramakrishnan ,Venkateswaran
Subject: RE: Request 39525 Assigned to you
Please check with Mukesh.

Yasar Mansoor
Solution Analyst
Information Technology
Dubai Petroleum
Mobile: +971 50 242 6422
Office: +971 4 301 2374
Fax: +971 4 301 2200
e-Mail: yasar.mansoor@dubaipetroleum.ae

From: Ramanujam, Sunderraj

Sent: Wednesday, January 14, 2015 11:29 AM
To: Mansoor, Yasar
Cc: Singh, Mukesh; Ramakrishnan ,Venkateswaran
Subject: RE: Request 39525 Assigned to you
Yasar
Please save the below file in a share drive accessible to us.
Request ID 1781536
Create_Accounting_130115.rtf size 232 MB
This output will list all transactions with accounting details that are stuck in accounting table.
Thanks
Sunder

From: Mansoor, Yasar

Sent: Wednesday, January 14, 2015 11:03 AM
To: Ramanujam, Sunderraj
Cc: Singh, Mukesh; Ramakrishnan ,Venkateswaran
Subject: RE: Request 39525 Assigned to you
Hi,
Please refer to the attached information and confirm if sufficient.
Request ID 1786876
Create_Accounting_130115.rtf
Create_Accounting_130115.txt
Request ID 1781536
Create_Accounting_130115.rtf size 232 MB cannot be attached.
Create_Accounting_130115 - 1781536.txt

Request ID 1787494

Accounting_Program_130115.txt

Yasar Mansoor
Solution Analyst
Information Technology
Dubai Petroleum
Mobile: +971 50 242 6422
Office: +971 4 301 2374
Fax: +971 4 301 2200
e-Mail: yasar.mansoor@dubaipetroleum.ae

From: Ramanujam, Sunderraj

Sent: Wednesday, January 14, 2015 8:54 AM
To: Mansoor, Yasar
Cc: Singh, Mukesh; Ramakrishnan ,Venkateswaran
Subject: RE: Request 39525 Assigned to you
Yasar
Please provide the latest output file and log files for below programs relating to the ticket.

When Create Accounting program is triggered, it triggers some child programs, below are two of
them.
Create Accounting
Accounting Program
You can fetch the output file, only if you login as the User Id which scheduled the program. Please
let me know if you need any clarification.
Thanks
Sunder