Beruflich Dokumente
Kultur Dokumente
Version:
Status:
Date:
18 Oct, 2015
Prepared by:
www.oraclehrmsoverview.com
Contributors:
Responsible Authorities
Project Sponsor:
Project Manager:
Senior User:
Service Owner:
System Owner:
Document purpose
This document is used to capture the detailed functional features, use, and behaviour of the customised
Oracle application extensions.
Table of contents
1
1.2
Definitions .................................................................................................................................3
1.3
1.4
1.5
<Form Description>...................................................................................................................4
2.2
2.3
Prerequisites .............................................................................................................................4
2.4
2.5
Considerations ..........................................................................................................................5
4.2
Page 2 of 8
1.1
Currently HR department is keeping passport information in excel files. Now HR department has raised
the requirement to store passport information in oracle.
1.2
Definitions
N/A
1.3
User Procedures
This option should be available only to AE HRMS Manager responsibility. Through this responsibility, they
should be able to enter the passport information.
Following field should be available on the passport entry screen
Passport Number
Passport Issue Date
Passport Expiry Date
1.4
Business Rules
Solution should have capability to store multiple records of passports for an employee.
1.5
Page 3 of 8
The following defines the form and report elements of <Subject> customization:
2.1
<Form Description>
2.2
<Form Title>
2.3
Prerequisites
2.4
Field 1
HELP
(Display only)
HELP
Enter...
Field 2
<Custom Application Name> displays
2.5
(Required, Default)
First Option
Second Option
Page 4 of 8
Technical Overview
3.1
Considerations
If any Oracle Manufacturing tables change in future versions of Oracle Manufacturing, components of this
customization may also require changes to work correctly. Evaluating the impact of such changes on
custom programming is the responsibility of the company, although additional consulting services can be
contracted to assist prior to upgrading.
Page 5 of 8
4.1
Open issues
ID
4.2
ID
Issue
Resolution
Responsibility
Target date
Impact Date
Responsibility
Target date
Impact Date
Closed issues
Issue
Resolution
Page 6 of 8
Document control
Approvals
Version No.
Approval Date
Name
Title
Name
Title
Signature/Email ref
Review history
Version No.
Review Date
Version history
Version No.
Version Date
Summary of Changes
Prepared by:
Page 7 of 8
Template control
Template Name
Location
Template approvals
Review Date
Name
Title
Version Date
Summary of Changes
Prepared by
Page 8 of 8