Tuesday, August 11, 2015

Oracle Fixed Asset Mass Addition Process - Oracle Fixed Asset

Oracle ebusiness  suite>Oracle Financial> Oracle Fixed Asset (FA)


Fixed Asset Mass Addition Process:


In this article I will explain the mass assets process of Oracle Fixed Asset Module.

This process start from the payables module to Fixed Asset Module.

I assume in payables  Assets Invoices are recorded and Track as Fixed Asset checked.


Oracle Payables Part:



Navigation: Payables > View>Request>New Request


Select Report Mass Additions Create
Enter the Parameter for report






Enter GL Date
Select Asset Book
Press OK 
Then Press Submit to Submit the report.

Run Mass Additions Create Report 


Then Select Asset Book
And Press OK
Then Submit Report.



Oracle Fixed Assets Part:


Navigation: Fixed Asset > Mass Additions> Prepare Mass Additions






Select the Queue as New
Press OK
Then Press Find

All the invoices will come



Change the Queue to POST
Select the Correct Category ( Asset Category)
Select the Expense Account 
Select the Location
Optionally select the Employee Name & Number 
You can change the Date in Service 
Can change the Cost  

Then Press Asset Details TAB


Enter Asset Number 
Enter Tag Number 
Select Asset Key
Select  In Use
Check In Physical Inventory

Then Press Depreciation TAB



Depreciation method will automatically selected
Enter Salvage Value

Then Press Done

Run Post Mass addition report to post the mass addition into asset registry.

Navigation: Fixed Asset > Mass Additions> Post Mass Additions


Select the parameter for Mass Addition Post 
Select the parameter for Mass Addition Posting Report 

Then Press OK
Press Submit 


For more details please visit http://www.oracle.com/
                                                 http://docs.oracle.com/



QUERY TO FIND OUT PR AND PO LINKED Oracle Purchasing - SQL


QUERY TO FIND OUT PR AND PO LINKED Oracle Purchasing - SQL


Below is the query for find our PR and PO






select req.segment1,req.DESCRIPTION req_,req.APPROVED_DATE,po.segment1,po.CREATION_DATE,po.APPROVED_FLAG
from po_headers_all po,
po_distributions_all dst,
po_req_distributions_all rd,
po_requisition_lines_all rl,
po_requisition_headers_all req
where po.po_header_id = dst.po_header_id
and dst.req_distribution_id = rd.distribution_id
and rd.requisition_line_id = rl.requisition_line_id
and rl.requisition_header_id = req.requisition_header_id

Monday, August 10, 2015

AP Forward and Backward Tracking Query (SQL)-( Tech R12)

AP Forward and Backward Tracking


Transaction Modes





Validate

TABLE: XLA_EVENTS
EVENT_STATUS_CODE=’I’
PROCESS_STATUS_CODE=’U’



Draft:

Draft will create journal entries, which are not final, which means they are not ready to be transferred to GL.

TABLE: XLA_AE_HEADERS
ACCOUNTING_ENTRY_STATUS_CODE =’D’

TABLE: XLA_EVENTS
PROCESS_STATUS_CODE=’D’
EVENT_STATUS_CODE=’U’     

Final:

Final will create journal entries, which can be transferred to GL.

TABLE: XLA_AE_HEADERS
ACCOUNTING_ENTRY_STATUS_CODE =’F’

TABLE: XLA_EVENTS
PROCESS_STATUS_CODE=’F’
EVENT_STATUS_CODE=’F’     

Final Post:

    Final Post will create journal entries in final mode, transfer them to GL and post them.


TABLE: XLA_AE_HEADERS
ACCOUNTING_ENTRY_STATUS_CODE=’F’
GL_TANSFER_STATUS_CODE=’Y’

TABLE: XLA_EVENTS
PROCESS_STATUS_CODE=’P’
EVENT_STATUS_CODE=’P’     




GL Back Tracking:
                                                               
      S#

1.         
We query the GL_JE_BATCHES table and see BATCH_ID against our batch name

2.         
We see the JE_HEADER_ID from JL_JE_HEADERS against Our Batch ID
3.         
We see the REFERENCE_5 Column from GL_IMPORT_REFERENCES that have the entity id
Note(Reference_6 have the value of Event_id)
4.         
In final step we query the XLA_TRANSACTION_ENTITIES_UPG table and find INVOICE_ID from its SOURCE_ID_INT_1.In this way we reach to the AP_INVOICES_ALL table.


RECOMMENDED WAY FOR R12

      S#

1.         
We query the GL_JE_BATCHES table and see BATCH_ID against our batch name

2.         
We see the JE_HEADER_ID from GL_JE_HEADERS against Our Batch ID
3.         
We query GL_JE_LINES and select JE_LINE_ID against our JE_HEADER_ID for further process.
4.         
In GL_IMPORT_REFERENCES we will find our JE_LINE_ID and see GL_SL_LINK_ID against this line.
5.         
In XLA_AE_LINES we find above GL_SL_LINK_ID and see it’s AE_HEADER_ID.
6.         
In XLA_AE_HEADERS we will find above AE_HEADER_ID and see it’s Event_ID
7.         
In XLA_EVENTS we will find above EVENT_ID and see IT’s ENTITY_ID
8.         
In XLA_TRANSACTION_ENTITIES we will find above ENTITY_ID and see it’s SOURCE_ID_INT_1 that is basically Inoice_ID
9.         
In AP_INVOICE_ALL we will find this particular invoice.





Query for Back Tracking:


                                                    We will pass JE_BATCH_ID to this query and it show us all the invoices against this batch from AP_INVOICES_ALL.

SELECT * FORM AP_INVOICES_ALL WHERE INVOICE_ID IN
(
SELECT SOURCE_ID_INT_1 FROM XLA_TRANSACTION_ENTITIES_UPG
 WHERE ENTITY_ID IN
(
SELECT ENTITY_ID FORM XLA_EVENTS
WHERE EVENT_ID IN
(
SELECT REFERENCE_6 FROM GL_IMPORT_REFERENCES
WHERE JE_HEADER_ID IN
(
SELECT JE_HEADER_ID FORM GL_JE_HEADERS WHERE  JE_BATCH_ID=&JE_BATCH_ID
)
)
)
)


Tracking of Records that are Un Transferred to GL:


                                                                              We will pass Period name to this query and it gives us output of Un transferred Entries to GL   

SELECT * FROM AP_INVOICES_ALL
WHERE INVOICE_ID IN
(
SELECT SOURCE_ID_INT_1 INVOICE_ID FROM XLA_TRANSACTION_ENTITIES_UPG
WHERE ENTITY_ID IN
(
SELECT ENTITY_ID FROM XLA_AE_HEADERS
WHERE GL_TRANSFER_STATUS_CODE=’N’
AND PERIOD_NAME=&PERIOD_NAME
)
)


Note: we also can see un posted entries from XLA_EVENTS table through EVENT_STATUS_CODE=’N’

Monday, August 3, 2015

Oracle AP Month End Closing Process - Oracle Payables

Oracle ebusiness suite>Oracle Financial> Oracle Payables

Oracle AP Month End Closing Process:


In this article I will explain the period end- month end closing process for Oracle Payables. What are the steps for closing process and what reports are required for this process to ensure the closing process without any issue.

1- Complete Transactions:

 Complete all the transactions in Oracle Payables and approve the invoices if invoice approval is required in Oracle Payables.

  • Complete Invoicing and Credits
  • Complete Prepayments
  • Complete Expense Reports
  • Complete Invoice Import
Validate the invoices then approve if invoice approval is enable.

 2- Complete Payments:


 Complete the payments for all invoices that is required to process. 

Approve all the payments in the same way if payment approval is enable in Payables.


3- Run Create Accounting & Transfer to GL:

  After completing invoices and payments the next step is create accounting.

3.1 - Create Accounting:

 Run the create accounting ( You can run the create accounting in draft or final mode)

  • Journal import programe will automatically run when you run the create accounting.

  • Review the Create Accounting output file it will give to overall picture of create accounting summary. How many entries are process and how many entries are not processed. 

3.2-Transfer to GL:


When you run create accounting  Transfer to GL option select YES. It will transfer all the entries into GL.

You can also run the Transfer to GL Programe to transfer the transaction to GL.

 4-Month End Closing Reports:


When you complete the create accounting and transfer to GL process. The next step is to check whether all the transactions are successfully transferred to GL and there is no transactions stuck in the interface.Then you need to run the following reports.


4.1 - Unaccounted Transaction Report : 


This report shows the transactions that are not accounted for the period that report is run.

You can run this report to verify that accounting have been successfully created for all the transactions.


4.2 - Sub ledger period close Exception Report : 


This Reports shows the exception if there is for the period for that report is run. You can run this report and resolved the exceptions.


5- Close Payables Period.


After doing all the activities, you need to close the Oracle Payables Period.


Period will not close if there is any exception for that period. then you need to Sweep that exceptions to the next period and close the current period.








Sunday, August 2, 2015

How to create Employee in Oracle HRMS


Oracle E-Business Suite  >Oracle HRMS


How to create Employee in Oracle HRMS



In this article I will explain how to create employee in Oracle applications (HRMS)

Navigation: HRMS>People>Enter and Maintain




Click on New 
 Click on New to enter the employee.




Select Title
Enter First name
Enter Family name
Enter Birth Date
Select Marital Status
Then click on "Addition information" Tab


 Select Action
Select Person Type for Action
Select Religion
Education and other information




Select Nationality
Click on Assignment


Select Organization
Select Job 
Select Grade
Select Location
Select Position
Select Status

then Click on Supervisor  


Select Name of Supervisor
Select Worker Number 
Select Assignment number 

Then Click on Entries to enter elements


Select the Payroll elements. (Optional for payroll only)






For more details please visit http://www.oracle.com/
                                                 http://docs.oracle.com/