Archive for the ‘Oracle’ Category

Oracle EBS SQL: GL Headers and Lines

Thursday, December 19th, 2013

The following SQL Statement is useful to find information about your GL Journals:

Note, this SQL statement is designed to link attributes 1 and 2 on the GL Journal lines to Projects, as such should be removed for any use elsewhere.

SELECT gjh.je_header_id jnl_hdr_id ,
gjct.user_je_category_name category ,
gjst.user_je_source_name source ,
gjb.status post_status ,
gjb.name batch_name ,
gjh.period_name ,
gjh.name journal_name ,
gjh.external_reference REF ,
gjh.date_created ,
gjh.description ,
gjh.running_total_dr ttl ,
gjh.creation_date ,
fu.description created_by ,
gjl.je_line_num ,
gjl.description line_descr ,
gjl.reference_1 line_ref ,
gjl.reference_5 ap_inv_num ,
gjl.reference_6 line_src ,
gjl.reference_10 line_type ,
GCC.SEGMENT1
|| '-'
|| gcc.segment2
|| '-'
|| gcc.segment3
|| '-'
|| GCC.SEGMENT4
|| '-'
|| gcc.segment5 cgh_acct ,
GJL.ACCOUNTED_DR DR ,
GJL.ACCOUNTED_CR CR ,
GJL.ATTRIBUTE1 PROJECT_ID ,
GJL.ATTRIBUTE2 TASK_ID ,
PPA.SEGMENT1 PROJECTNUMBER,
PT.TASK_NUMBER TASKNUMBER
FROM GL.GL_JE_HEADERS GJH ,
GL.GL_JE_BATCHES GJB ,
GL.GL_JE_LINES GJL ,
GL.GL_JE_SOURCES_TL GJST ,
GL.GL_JE_CATEGORIES_TL GJCT ,
GL.GL_CODE_COMBINATIONS GCC ,
APPLSYS.FND_USER FU ,
PA.PA_PROJECTS_ALL PPA ,
PA.PA_TASKS pt
WHERE GJH.JE_BATCH_ID                                            = GJB.JE_BATCH_ID(+)
AND gjh.je_header_id                                             = gjl.je_header_id
AND GJH.JE_SOURCE                                                = GJST.JE_SOURCE_NAME
AND GJH.JE_CATEGORY                                              = GJCT.JE_CATEGORY_NAME
AND GJH.CREATED_BY                                               = FU.USER_ID
AND GJL.CODE_COMBINATION_ID                                      = GCC.CODE_COMBINATION_ID
-- These allow for duff information from other sources to be excluded.
AND DECODE(GJL.CONTEXT,'Capital Contribution',GJL.ATTRIBUTE1,-1) = PPA.PROJECT_ID(+)
AND DECODE(GJL.CONTEXT,'Capital Contribution',GJL.ATTRIBUTE2,-1) = PT.TASK_ID (+)
AND GJH.JE_CATEGORY                                              = 'Capital Contribution'
ORDER BY GJH.CREATION_DATE DESC ,
GJB.NAME ,
GJH.NAME ,
GJL.JE_LINE_NUM;

* All SQL statements are provided without warranty or support. Use at your own risk!

Modular Designing Documents

Friday, April 6th, 2012

Modular Designing Documents, which are is primafaciely done by the Technical Persons of the Implementation Team like Technical Project Leads / Project Manager. These documents are the Design Documents, which is again based on the BR 120 – Business Requirement Gathering as provided by the business.

These MD’s are of basically discussed any customization needs or any special behaviaour oracle system should work which is not the Standard Oracle Funtionality. These also discussed about the tables and the Interface Tables or forms which are going to be used in the particular modules. Thses also discussed about the High Level Designs like Flows of the Business and all.

These MD’s are basically made after you all Functional Design and if there is no work around Oracle System provides for a particular Test Scenario and there is no other way other than to go for the Customization.

Now I suppose you can understand what is the basic difference between these two.

Now as a Funtional Consultant you need to always go for the BR – 100, that is set up doc. and in your scenario ( as you said that you have created in GL – COA / CAL / CVR etc) you have to document all these into BR 100.

The first version of the BR100 will probably be used to build the TEST environment. Any changes required as a result of problems encountered will be incorporated into the next version of the BR100, which will then be used to build (say) the UAT environment. In parallel with these environments, there will probably be a DEVELOPMENT environment and it may be that there will be changes required to the BR100 because of issues encountered there. The “Final” version of the BR100 will probably then be used to build both the PRODUCTION and TRAINING environments.

Oracle AIM Document Names

Friday, April 6th, 2012

Business Process Architecture (BP)
BP.010 Define Business and Process Strategy
BP.020 Catalogue and Analyze Potential Changes
BP.030 Determine Data Gathering Requirements
BP.040 Develop Current Process Model
BP.050 Review Leading Practices
BP.060 Develop High-Level Process Vision
BP.070 Develop High-Level Process Design
BP.080 Develop Future Process Model
BP.090 Document Business Procedure

Business Requirements Definition (RD)
RD.010 Identify Current Financial and Operating Structure
RD.020 Conduct Current Business Baseline
RD.030 Establish Process and Mapping Summary
RD.040 Gather Business Volumes and Metrics
RD.050 Gather Business Requirements
RD.060 Determine Audit and Control Requirements
RD.070 Identify Business Availability Requirements
RD.080 Identify Reporting and Information Access Requirements

Business Requirements Mapping
BR.010 Analyze High-Level Gaps
BR.020 Prepare mapping environment
BR.030 Map Business requirements
BR.040 Map Business Data
BR.050 Conduct Integration Fit Analysis
BR.060 Create Information Model
BR.070 Create Reporting Fit Analysis
BR.080 Test Business Solutions
BR.090 Confirm Integrated Business Solutions
BR.100 Define Applications Setup
BR.110 Define security Profiles

Application and Technical Architecture (TA)
TA.010 Define Architecture Requirements and Strategy
TA.020 Identify Current Technical Architecture
TA.030 Develop Preliminary Conceptual Architecture
TA.040 Define Application Architecture
TA.050 Define System Availability Strategy
TA.060 Define Reporting and Information Access Strategy
TA.070 Revise Conceptual Architecture
TA.080 Define Application Security Architecture
TA.090 Define Application and Database Server Architecture
TA.100 Define and Propose Architecture Subsystems
TA.110 Define System Capacity Plan
TA.120 Define Platform and Network Architecture
TA.130 Define Application Deployment Plan
TA.140 Assess Performance Risks
TA.150 Define System Management Procedures

Module Design and Build (MD)
MD.010 Define Application Extension Strategy
MD.020 Define and estimate application extensions
MD.030 Define design standards
MD.040 Define Build Standards
MD.050 Create Application extensions functional design
MD.060 Design Database extensions
MD.070 Create Application extensions technical design
MD.080 Review functional and Technical designs
MD.090 Prepare Development environment
MD.100 Create Database extensions
MD.110 Create Application extension modules
MD.120 Create Installation routines

Data Conversion (CV)
CV.010 Define data conversion requirements and strategy
CV.020 Define Conversion standards
CV.030 Prepare conversion environment
CV.040 Perform conversion data mapping
CV.050 Define manual conversion procedures
CV.060 Design conversion programs
CV.070 Prepare conversion test plans
CV.080 Develop conversion programs
CV.090 Perform conversion unit tests
CV.100 Perform conversion business objects
CV.110 Perform conversion validation tests
CV.120 Install conversion programs
CV.130 Convert and verify data

Documentation (DO)
DO.010 Define documentation requirements and strategy
DO.020 Define Documentation standards and procedures
DO.030 Prepare glossary
DO.040 Prepare documentation environment
DO.050 Produce documentation prototypes and templates
DO.060 Publish user reference manual
DO.070 Publish user guide
DO.080 Publish technical reference manual
DO.090 Publish system management guide

Business System Testing (TE)
TE.010 Define testing requirements and strategy
TE.020 Develop unit test script
TE.030 Develop link test script
TE.040 Develop system test script
TE.050 Develop systems integration test script
TE.060 Prepare testing environments
TE.070 Perform unit test
TE.080 Perform link test
TE.090 perform installation test
TE.100 Prepare key users for testing
TE.110 Perform system test
TE.120 Perform systems integration test
TE.130 Perform Acceptance test

PERFORMACE TESTING (PT)
PT.010 – Define Performance Testing Strategy
PT.020 – Identify Performance Test Scenarios
PT.030 – Identify Performance Test Transaction
PT.040 – Create Performance Test Scripts
PT.050 – Design Performance Test Transaction Programs
PT.060 – Design Performance Test Data
PT.070 – Design Test Database Load Programs
PT.080 – Create Performance Test Transaction Programs
PT.090 – Create Test Database Load Programs
PT.100 – Construct Performance Test Database
PT.110 – Prepare Performance Test Environment
PT.120 – Execute Performance Test

Adoption and Learning (AP)
AP.010 – Define Executive Project Strategy
AP.020 – Conduct Initial Project Team Orientation
AP.030 – Develop Project Team Learning Plan
AP.040 – Prepare Project Team Learning Environment
AP.050 – Conduct Project Team Learning Events
AP.060 – Develop Business Unit Managers Readiness Plan
AP.070 – Develop Project Readiness Roadmap
AP.080 – Develop and Execute Communication Campaign
AP.090 – Develop Managers’ Readiness Plan
AP.100 – Identify Business Process Impact on Organization
AP.110 – Align Human Performance Support Systems
AP.120 – Align Information Technology Groups
AP.130 – Conduct User Learning Needs Analysis
AP.140 – Develop User Learning Plan
AP.150 – Develop User Learningware
AP.160 – Prepare User Learning Environment
AP.170 – Conduct User Learning Events
AP.180 – Conduct Effectiveness Assessment

Production Migration (PM)
PM.010 – Define Transition Strategy
PM.020 – Design Production Support Infrastructure
PM.030 – Develop Transition and Contingency Plan
PM.040 – Prepare Production Environment
PM.050 – Set Up Applications
PM.060 – Implement Production Support Infrastructure
PM.070 – Verify Production Readiness
PM.080 – Begin Production
PM.090 – Measure System Performance
PM.100 – Maintain System
PM.110 – Refine Production System
PM.120 – Decommission Former Systems
PM.130 – Propose Future Business Direction
PM.140 – Propose Future Technical Direction