AIM

ID	Task	Work Product	Template
Objectives
RD.001	Detail Business and System Objectives	Business and System  Objectives	Business and System  Objectives
Document Requirements
RD.005	Create System Context Diagram	System Context Diagram	System Context Diagram
RD.011	Develop Future Process Model	Future Process Model	Future Process Model
RD.030	Develop Current Business Process Model	Current Process Model	Current Process Model
RD.045	Prioritize Requirements (MoSCoW)	MoSCoW List	MoSCoW List-Excel, MoSCoW List-Word, Generic Workshop Notes, Generic Workshop Schedule, and Workshop Preparation Notes
RD.065	Develop Domain Model (Business Entities)	Domain Model	Domain Model
RA.023	Develop Use Case Model	Use Case Model	Use Case Model, Visio Template and Stencil
RA.024	Develop Use Case Details	Use Case Specification	Use Case Specification
Map Requirements
AN.010	Map Business Requirements	Mapped Business Requirements	Validated Functional Prototype
AN.020	Define and Estimate Application Extensions	Application Extension Definition and Estimates	Refer to the Task Overview for  guidance.
AN.030	Define Gap Resolutions	Gap Resolutions	Refer to the Task Overview for guidance.
IM.010	Develop Functional Prototype	Functional Prototype	Refer to the Task Overview for guidance.
RA.085	Validate Functional Prototype	Validated Functional Prototype	Validated Functional Prototype
Configure
DS.010	Define Business Data Structure Setups	Business Data Structure Setups	Business Data Structure Setups
RA.040	Define Business Data Structures	Business Data Structures	Refer to the Task Overview for guidance.
DS.030	Define Application Setups	Application Setup Documents	Application Setup Documents
Analyze and Design Components
AN.050	Analyze Data	Data Analysis	Analysis Model
AN.060	Analyze Behavior	Behavior Analysis	Refer to the Task Overview for guidance.
AN.090	Analyze User Interface	User Interface Analysis	Refer to the Task Overview for guidance.
DS.080	Design Software Components	Software Component Design	Refer to the Task Overview for guidance.
DS.090	Design Data	Component Data Design	Refer to the Task Overview for guidance.
DS.100	Design Behavior Component	Behavior Design	Refer to the Task Overview for guidance.
DS.130	Design User Interface	User Interface Design	Refer to the Task Overview for guidance.
DS.150	Develop Database Design	Logical Database Design	Logical Database Design
Implement Components
IM.005	Develop Conceptual Prototype	Conceptual Prototype	Refer to the Task Overview for guidance.
IM.040	Implement Database	Implemented Database	Physical Database Design
IM.050	Implement Components	Implemented Components	Refer to the Task Overview for guidance.
IM.070	Assemble Components	Assembled Components	Refer to the Task Overview for guidance.
Integrate
IM.080	Integrate Services	Integrated Services	Refer to the Task Overview for guidance.
Test
TE.030	Perform Unit Test	Unit-Tested Components	Refer to the Task Overview for guidance.
TE.040	Perform Integration	Test Integration-Tested Components	Integration Test Results
TE.070	Perform System Test	System-Tested Applications	System Test Results
TE.100	Perform Systems Integration Test	Integration-Tested System	Systems Integration Test Results

AR Invoice showing completed in front end application, however sub ledger period close exception report showing status as invalid

Issue: AR Invoice showing completed in front end application, however sub ledger period close exception report showing status as invalid

Cause: Mostly this issue happens when you copy recurring invoices

Solution:

------------------

1. Pull Invoice diagnostics and take event id

2. If the invoice is invalid the EVENT_STATUS_CODE= 'I'

3. Run the below query to check the same.

select * from xla.XLA_EVENTS where EVENT_ID=1234567;

It will show the EVENT_STATUS_CODE= 'I'

4. Run the below update script to change the flag to 'U'

UPDATE XLA.XLA_EVENTS SET EVENT_STATUS_CODE = 'U' WHERE EVENT_ID = 1234567 AND APPLICATION_ID = 222 AND EVENT_STATUS_CODE= 'I' AND PROCESS_STATUS_CODE='U';

COMMIT;

5. Run the create accounting and transfer to General ledger 'Yes’.

6. Now the status will change to  EVENT_STATUS_CODE = 'P'

Run the subledger period close exception report ,it won’t show this Invoice .

Realease 12 Invoice validation issue

Error Message: Unexpected error occured during Tax Calculation'.
Exception: A Mandatory constraint to generate unique summary tax line is voilated with the error ORA-00001'.

Action plan
------------------------
Apply the Generic Data Fix patch 12961200:R12.ZX.B as per the readme instructions.

Please note that this script needs to executed manually in the db instance.

Following are the instructions to execute this script:
1. To run the Data-Fix for a specific invoice pass the value of variable TRX_ID
  (where TRX_ID is the INVOICE_ID of the invoice).

Parameter variable TRX_ID =  Invoice Id  = 'XXXXX'

Unable to query Invoices from Invoice work bench and getting the error "FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-01403"

Unable to query Invoices from Invoice work bench and getting the below errors

1."FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-01403"

2. FRM-40350:Query caused no records to be retrieved.

Data fix need apply to resolve the above errors.

Please apply the GDF Patch 13857555:R12.IBY.B

Steps to follow:(Run the scripts with "Apps" User)

1) Run $IBY_TOP/patch/115/sql/iby_dup_payee_sel.sql

2) Verify the log file to find out if duplicate payees exist.

3) Log File will be created in the following directory:

              SELECT decode(instr(value,','),0,value,

                   SUBSTR (value,1,instr(value,',') - 1))

               FROM   v$parameter

                WHERE  name = 'utl_file_dir';

4)Customer will review and update the RFC to run the next step

5) Follow the action plan provided in the log file to fix the corrupted data.

Oracle History and ERP Versions their Release Dates

Oracle History and ERP Versions their Release Dates

Ellison co-founded Oracle Corporation in 1977 with Bob Miner and Ed Oates under the name Software Development Laboratories (SDL). In 1979 SDL changed its name to Relational Software, Inc. (RSI). In 1982, RSI renamed itself Oracle Systems Corporation to align itself more closely with its flagship product Oracle Database. At this stage Bob Miner served as the company's senior programmer. In 1995, Oracle Systems Corporation changed its name to Oracle Corporation. On March 12, 1986: Oracle gone public with revenues of $55 million USD.

·         Oracle E-Business Suite started life as Oracle Financials in 1987. 

·          August 1987: Oracle founds its Applications division, building business-management software closely integrated with its database software. Oracle Corporation acquires TCI for its project management software.

·          October 1987: Oracle Applications Release 1

·          Sometime in August 1988 they released their first ERP application called accounting system that has only general Ledger functionality enabled. This is one of the reason of having General ledger application_id is 101.

·          November 1988: Release 3

·          January 1989: Release 4

·           May 1989: Release 5

·           October 1989: Release 6

·           May 1990: Release 7

·           November 1990: Release 8

·           June 1992: Release 9

·           1995: Release 10

·           Release 10 Sub versions are 10.7NCA, 10.7.16.1, 10.7

·           April 1998: Release 11

·           Release 11 sub versions are 11.0, 11.0.1, 11.0.2, 11.0.3, 11.0.28

·           July 16, 1998: First combined production installation of Oracle Applications Release 10.7 NCA at Leeson Electric Corporation.

·           May 2000: Release 11i

·           11i Sub Versions are 11.5, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10.0, 11.5.10.1, 11.5.10.2.

·          Feb 2006: 11.5.10.2

·          31 Jan 2007: R12

·          R12 Sub Versions are 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 12.0.5, 12.0.6, 12.0.7, 12.1, 12.1.1, 12.1.2, 12.1.3 and upcoming version is 12.2.