Professional Documents
Culture Documents
Currently this document can only be produced as part of the shipping document set following WIP Job completion and picking
--------------------------------------------------------------*****************--------------------------------------------------------------
Dinesh Garg
Creation Date
24-FEB-2015
Last Updated
24-FEB-2015
Document Ref
NONE
Version
1.0
CF.250 Instructions
Objective
The purpose of this document is to describe the functionality of confirmed custom
solutions that solve gaps documented in the BR.150 that have no other solution
possibility. This document will:
Describe the need for a custom solution and its reference in the appropriate
BR.150. No orphan CF.250s will be accepted.
Describe the business environment in which the solution will operate.
Include a high-level description of all the appropriate solution features; form,
report, integration, etc.
Include a flow-diagram to describe the interactions between all features of
the solution.
Include proposed test data and business use cases or a clear reference to
them via TE.050s.
Defect
Rating
High
High
High
High
Medium
L, M, H
Note:
Note:
Note: To add additional approval lines, press [Tab] from the last cell in the
table above.
You can delete any elements of this cover page that you do not need for your
document. For example, Copy Number is only required if this is a
controlled document and you need to track each copy that you
distribute.
Document Control
Change Record
5
Date
Author
Version
24-FEB-2015
Change Reference
Initial Document
Reviewers
Name
Position
Distribution
Copy No.
Name
Location
The copy numbers referenced above should be written into the Copy
Number space on the cover of each distributed copy. If the document
is not controlled, you can delete this table, the Note To Holders, and
the Copy Number label from the cover page.
Contents
Document
Control......................................................................................
........ 3
Executive
Summary..................................................................................
.......... 6
References................................................................................
.......................... 6
Scope and
Impact......................................................................................
......... 6
Abbreviation and
Terminology..................................................................... 6
Scope..................................................................................
.......................... 7
Oracle EBS
Gap......................................................................................
...... 7
Impact to Existing
Systems........................................................................... 7
Impacts to
Processes.............................................................................
........ 7
Business
Requirements...........................................................................
............ 8
Business
Rules....................................................................................
.......... 8
Upstream/Downstream
Dependencies.......................................................... 9
Assumptions and
Prerequisites..................................................................... 9
Solution
Design......................................................................................
.......... 10
Report
Parameters..........................................................................
............. 10
Report
Layout.................................................................................
............ 11
Report Data
Elements.............................................................................
.... 12
Report Selection
Criteria............................................................................. 2
0
User
Interface..............................................................................
............... 20
Interface...................................................................................
........................ 20
Performance
Requirements...........................................................................
.... 21
Expected
Output......................................................................................
......... 21
Oracle
Program....................................................................................
............. 22
Workflows.................................................................................
....................... 22
Forms
Personalization.........................................................................
.............. 22
Other
Objects.....................................................................................
............... 22
Use
Cases........................................................................................
................. 22
Appendix
A...............................................................................................
.... 24
Appendix
B...............................................................................................
.... 26
Appendix
C...............................................................................................
.... 27
Appendix
D...............................................................................................
.... 28
Appendix
E...............................................................................................
.... 30
Open and Closed
Issues.................................................................................... 3
1
Executive Summary
There is a business requirement to inspect the parts at the operation 50 during the
quality inspection and testing of end unit repaired. Sometimes, customer also,
expects to see an inspection document along with the part repaired from the repair
shop.
Hence, in order to serve the business, there is a document named as Maintenance
Source Inspection Document required to be produced in operation 50 i.e. inspection
step of the repaired part.
Oracle EBS standard doesnt generate any such document. Hence need for the
custom report arises. The solution includes the design of Maintenance Source
Inspection Approval Document along with logic to generate the same.
References
Req/Def
ect Id
Folder URL
Document Name
Not Applicable.
Not Applicable.
2523
MSCA
Description
Oracle E-Business Suite Oracle System
which is intended to capture all the
transactional information of GE Aviation
system
Stands for Mobile Supply Chain Application.
This is oracle provided application used in
Oracle warehouse to do the transaction in
system.
OM
Order Management
PO
Purchasing
INV
Inventory
Scope
Maintenance Source Inspection Approval report will need to be printed for repair
work orders, which are repaired and ready for shipping to the customer based on
customer requirement.
Oracle BI publisher shall be used to generate the desired output template.
The scope of this CF250 is as follows:
a) The design of the Maintenance Source Inspection Approval Report;
b) The expected output document structure;
c) The Maintenance Source Inspection Approval Report Field Mapping.
d) The Unit Test Scenarios.
Any other document requirement other than Maintenance Source Inspection
Approval Report is considered as out of scope of this CF250.
Impacts to Processes
The following standard business processes are impacted:
Repair Process: This report will be printed as soon as any part is repaired and
ready for shipping from a repair warehouse against a repair sales order. The report
can be invoked at the following events:1. Any time after delivery is picked manually as well as part of document set
similar to OE.
2. Any time after delivery is shipped manually as well as part of document set
similar to OE.
The report shall be printed for all sales order line where any of the source inspection
field value (as specified in Appendix A) is set to Yes.
Business Requirements
Report Name
Description
Report Type
Reports Used Today
Business Purpose
Data Source
Target Location
Security Requirement
Business Rules
Following business rules shall apply:
a) The source inspection report will be generated for all repair work orders
associated with end items where related sales order does have any of source
inspection field as specified in Appendix A is Yes.
b) The document will be triggered from Custom Form Maintenance Release
Documents Form for a specific work order as soon as user presses the Print
Documents button.
c) The source inspection document should display one part per page.
d) All dates should be in DD-MON-YYYY format.
e) Each Repair sales order will have only one part number associated
with it with quantity = 1.
f) All parts including container part will be displayed on this part, if any
of source inspection field as specified in Appendix A is Yes at Header
or Line Level.
CTQs
a) The quality should be able to inspect the part without any hassle.
b) No user intervention is required.
c) The transaction must not take longer than 30 sec per report.
Upstream/Downstream Dependencies
a) Oracle OM, INV, WMS, Service Request and Depot Repair Modules are
properly setup.
b) Printers are setup.
Solution Design
There will be a new concurrent program and report developed which will be
triggered based on Source Inspection Attribute Flag set to Yes as defined on the
sales order. This report shall be fired from Print Documents button on the
Maintenance Release Documents Form and should only be fired when any source
inspection flag is set to Yes. Refer Appendix A.
Report Parameters
This should be fired from existing Program GEAS Repairs Generate Release
Documents.
Parameter
Name
Description
Organizatio
n
Should be defaulted to
Profile
MFG_ORGANIZATION_ID.
Should
have
a
List
containing all organization
available in profile MO:
Operating Unit
Work Order
Number
Work
Order
Number
selected by user manually
from LOV on the custom
form.
Mandat
ory
(Y/N)
Y
Displaye
d
List Of Values
Should be defaulted to
Profile
MFG_ORGANIZATION_ID.
Should have a List
containing all
organization available in
profile MO: Operating
Unit
Should be a LOV which
should display all valid
Work Orders.
Report Layout
Special Note: The Form Number for this document is Form: ERP-J-013, Rev.
1.0 and should be positioned in the same place as on the manufacturing source
inspection document.
Logo
Logo
Addre
ss
Description
Values
Cal
cul
ati
on
s
(if
an
y)
NO
NE
NO
NE.
Fiel
d/
Colu
mn
Nam
e
Description
Values
Cal
cul
ati
on
s
(if
an
y)
Tax
Num
ber
NO
NE
Custo
mer
Order
No
NO
NE
Refer
ence
Num
ber
NO
NE
Sales
Order
No
NO
NE
Date
NO
NE
Bill to
Addre
ss
NO
NE
Fiel
d/
Colu
mn
Nam
e
Description
Values
item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.
item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.
inventory_item_id NOT IN
inventory_item_id NOT IN
Cal
cul
ati
on
s
(if
an
y)
Ship
to
Addre
ss
and item_type =
'GEAS_SHIPPING_CONT';
item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.
item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.
NO
NE
Fiel
d/
Colu
mn
Nam
e
Description
Values
inventory_item_id NOT IN
inventory_item_id NOT IN
Cal
cul
ati
on
s
(if
an
y)
and item_type =
'GEAS_SHIPPING_CONT';
In case of no sales order,
default from Service
Request.
Following logic should be
used for pulling the contract
Number based on Project and
from contract number, prime
contract number should be
picked..
1. One project should be
associated to one contract.
Incase one project is
associated to multiple
contracts, then report should
error out with the text
message 'Project Number
<Project Number> is assigned
to multiple contracts i.e.
<Contract Number 1> ,
<Contract Number 2>,
<Contract Number 3>.
2. Project association at
delivery Level
- Check if project from SO line
is associated at DTS (Delivery
level) of any contract number,
and then use the same
contract number for pulling
NO
NE
Fiel
d/
Colu
mn
Nam
e
Description
Values
Cal
cul
ati
on
s
(if
an
y)
NO
NE
Order
Head
er/Ap
plicat
ion
NO
NE
where ppc.class_category =
'Platform'
where ppc.class_category =
'Platform'
Incot
erms
NO
NE
Line
Item
NO
NE
Fiel
d/
Colu
mn
Nam
e
Produ
ct
Num
ber/C
usto
mer
Part
Num
ber/D
escri
ption/
HTN/
ECCN
Description
Values
Sche
dule
Ship
Date
QTY/
UOM
Cal
cul
ati
on
s
(if
an
y)
NO
NE.
NO
NE
NO
NE.
Fiel
d/
Colu
mn
Nam
e
SERIA
L/LOT
Description
Values
Cal
cul
ati
on
s
(if
an
y)
RELE
ASE
NO
NE.
GE
Deleg
ated
Pick from
Pick from
NO
NE.
Gove
Pick from
Pick from
NO
Fiel
d/
Colu
mn
Nam
e
Description
Values
Cal
cul
ati
on
s
(if
an
y)
rnme
nt
NE,
Pick from
Pick from
Pick from
Pick from
Regul
atory
Custo
mer
NO
NE.
NO
NE.
Fiel
d/
Colu
mn
Nam
e
Sourc
e
Inspe
ction
Rema
rks
Foote
r
Addre
ss
Description
Values
NO
NE.
NO
NE.
Cal
cul
ati
on
s
(if
an
y)
User Interface
Custom Form: - A new custom form/OA Framework Page has to be
developed with the sample layout as shown below:-
Interface
Not Applicable. As there are no integrations involved.
Performance Requirements
It should not take more than 30 seconds to print a packing slip report pertaining to a
delivery name.
Expected Output
Oracle Program
Concurrent Program:A new concurrent program GEAS Maintenance Source Inspection Approval
Report needs to be developed with following input parameters. Program should be
attached to generalize Quality Responsibilities based on the matrix provided by
business:Parameter
Name
Description
Organizatio
n
Should be defaulted to
Profile
MFG_ORGANIZATION_ID.
Should
have
a
List
containing all organization
available in profile MO:
Operating Unit
Work Order
Number
Work
Order
Number
selected by user manually
from LOV on the custom
form.
Mandat
ory
(Y/N)
Y
Displaye
d
List Of Values
Should be defaulted to
Profile
MFG_ORGANIZATION_ID.
Should have a List
containing all
organization available in
profile MO: Operating
Unit
Should be a LOV which
should display all valid
Work Orders.
Workflows
Not Applicable. As there are no workflow design requirements.
Forms Personalization
Not Applicable as there are no form personalization design requirements.
Other Objects
Not Applicable as there are no other objects impacted.
Use Cases
S.
N.
SCENARIO
EXPECTED RESULT
1.
2.
3.
4.
5.
6.
7,
8.
9.
10.
11.
12.
13.
Appendix A
Source Inspection Filter Mechanism:This report should be printed for lines for which at least any one of below
highlighted fields is Yes. Fields Names are:1. Delegated to GE
2. Government = Y/N
3. Regulatory (FAA/CAA)
4. Customer
In case any of these fields is blank, check the relevant field in sales order header
DFF, as shown below:-
Appendix B
Logo Requirement:
There is a business requirement to have different logo for different sites. Hence in
order to achieve the same, all logo information needs to be stored in apps server
folders. As of now, following logo information is identified from business sides:
LOGO
OPERATING UNIT
GEAS MRAS OU
GEAS US OU
GEAS UK OU
GEAE OU
Appendix C
HTN Code HTN Code is a flex field at the item category level. Following is the
sample screen shot for one Sample data:
Category Set Name TCT Tagging
Field Name HTN (HS Code)
Appendix D
Solution Design for Postal Address for a operating unit:
1) New Fnd Message:
A new FND message will be created as per below screen shot. This message shall
contain the Postal Address for each legal entity with the following addresses:
MRAS Address:
MRA Systems, Inc. Registered Office, 103 Chesapeake Park Plaza, Baltimore, MD
21220, United States.
US Avionics Address:
GE Aviation Systems, LLC. Registered Office, 3290 Patterson Avenue, Grand Rapids,
MI, 49512-1991, United States.
UK Address:
GE Aviation Systems Ltd. Registered Office, Bishop Cleeve, Cheltenham.
Gloucestershire GL52 8SF. Incorporated in England. No. 745917 VAT Registration No.
GB 647 894 477.
2) New Lookup:
A new lookup will be created which will store the Sales order legal entity and
corresponding message code from FND Messages.
Code Legal Entity Id
Meaning Legal Entity Name
Description Message code for Address.
Below is the screen shot of the lookup:
Appendix E
EIN stored at legal entity level as shown in screen shot below.
Comments
Resolution
Owner