--------------------------------------------------------------*****************-------------------------------------------------------------The Customer Source Inspection (CSI) document should be producible for signing by the customer source inspector at operation 50

Currently this document can only be produced as part of the shipping document set following WIP Job completion and picking
--------------------------------------------------------------*****************--------------------------------------------------------------

CF.250 CUSTOM SOLUTION

DESIGN - FUNCTIONAL
GE AVIATION SYSTEMS
Maintenance Source Inspection
Document
Author

Dinesh Garg

Creation Date

24-FEB-2015

Last Updated

24-FEB-2015

Document Ref

NONE

Version

1.0

Note: Title, Subject, Last Updated Date, Reference

Number, and Version are marked by a Word Bookmark so that they can be
easily reproduced in the header and footer of documents. When you change
any of these values, be careful not to accidentally delete the bookmark. You
can make bookmarks visible by selecting Tools->OptionsView and
checking the Bookmarks option in the Show region.
Approvals:
David Bergin
Vinny Joshi
Michael Rimmer

WMS IT Process Lead

Quality Integration IT Process
Lead
Quality Enterprise Lead

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.

File Naming Convention

GE Energy does not mandate a document naming convention, but if one has not
been decided upon for the project, please consider the following suggestion:
AAA_BBB_CCC_desc.doc
Where: AAA = Instance or business name e.g., CENTERPIECE, WIND_US
BBB = Document type = CF250
CCC = Track Name: MFG, FIN, SRC
desc = Description such as OpenPO_Report, COGS_Reclass_Process.
Whatever document naming convention is adopted by the project should be
rigorously adhered to and should apply to ALL documents.
Document Control
Changes and updates to the document should be clearly indicated in this section by
providing the date of updates, person who updated the document, change
references indicating at a high level what was updated or reasons for update and
versioning the document with an incremental version number.
Abbreviations and Terminology
This section should list the meaning of business-specific terms and abbreviations
used through out the document that have a unique connotation in this context.
Important Sections of the document
Any section designated as MANDATORY must contain actual content!
Review Matrix
The following criteria will be used by the reviewer of this document.
Review comment classification
GEM template not used for brand new document

Defect
Rating
High

Existing CF.250 not updated when it was appropriate to do so

Any mandatory document section is missing or incomplete
(note data mapping for interfaces)
Document does not reference gap in appropriate BR.150
Document versions, document control not updated
Comments directly related to document content (evaluated
on case-by-case basis)

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

Dinesh Garg 1.0

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

Scope and Impact

Abbreviation and Terminology
Abbreviated Form
Oracle EBS

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.

Oracle EBS Gap

Oracle standard EBS doesnt generate the Aviation Business specific report formats.
Hence the need for a custom solution arises.

Impact to Existing Systems

Since this is a new Oracle Report, hence there is no impact to any existing systems.
Oracle BI Publisher shared services will be used.

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

GEAS Maintenance Source Inspection Approval Report

As per the GE Aviation business requirement, for all sales
order line where any of source inspection field specified in
Appendix A is Yes, then for those lines, source inspection
document should be printed. This document will be used
for inspection of goods prior to shipping. Also, customer
can visualize this document to know the inspection status
of the part.
PDF
Manual.
This report will be used as a reference for inspecting the
goods physically prior to shipping and note down the
inspection results. Also, will be sent to customer along
with goods as a result of inspection.
Oracle-OM,INV, Depot, Service Request, Work in Process
Should print on Oracle Printers.
Fired from Maintenance Release Documents Form.

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.

Assumptions and Prerequisites

The proposed alternative and estimated work effort is based on the following
assumptions:
a) Oracle Application Release 12.1.3 is being used.
b) Oracle WMS, Inventory, OM and Shipping Transactions are setup.
c) The printers are registered and Install at Oracle Applications.

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.

Report Data Elements

Fiel
d/
Colu
mn
Nam
e

Logo

Logo
Addre
ss

Description

Values

Cal
cul
ati
on
s
(if
an
y)

Logo needs to be derived

based on Legal Entity of the
sales order. Please see
appendix B for details.

Logo needs to be derived

based on legal entity of the
sales order. Please see
appendix B for details.

NO
NE

Address beside Logo should be

coming from Lookup GE
RELEASE AGENCY ADDRESS
based on concurrent program
short name concatenated by

Address beside Logo should

be coming from Lookup GE
RELEASE AGENCY ADDRESS
based on concurrent program
short name concatenated by

NO
NE.

Fiel
d/
Colu
mn
Nam
e

Description

organization code. The lookup

will store address message in
DFF, which can be de-coded
further.

Values

Cal
cul
ati
on
s
(if
an
y)

organization code. The lookup

will store address message in
DFF, which can be de-coded
further.

Tax
Num
ber

EIN Number based on

Appendix G.

EIN Number based on

Appendix G.

NO
NE

Custo
mer
Order
No

Repair Order Default PO

Number.

Repair Order Default PO

Number

NO
NE

Refer
ence
Num
ber

Work Order Number Plus

Service Request Number.

Work Order Number Plus

Service Request Number.

NO
NE

Sales
Order
No

Sales Order Number

Associated to Repair Order. In
case of no Sales Order found,
it should be blank.

Sales Order Number

Associated to Repair Order. In
case of no Sales Order found,
it should be blank.

NO
NE

Date

Date on which report is

generated. This should be in
DD-MON-YYYY format.

Date on which report is

generated i.e. sysdate. This
should be in DD-MON-YYYY
format.

NO
NE

Bill to
Addre
ss

Repair Ship Sales Order Line

Bill to Address with
Customer Name on first
line. There can be two ship
lines, hence exclude the
ship line which does have

Repair Ship Sales Order Line

Bill to Address with
Customer Name on first
line. There can be two ship
lines, hence exclude the
ship line which does have

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.

Following query can be

leverage to exclude the
container ship line:-

Following query can be

leverage to exclude the
container ship line:-

inventory_item_id NOT IN

inventory_item_id NOT IN

select inventory_item_id fro

m apps.mtl_system_items_b

select inventory_item_id fro

m apps.mtl_system_items_b

Cal
cul
ati
on
s
(if
an
y)

where organization_id = 112 where organization_id =

112
and item_type =
'GEAS_SHIPPING_CONT';
In case of no sales order,
default from Service
Request.

Ship
to
Addre
ss

and item_type =
'GEAS_SHIPPING_CONT';

In case of no sales order,

default from Service
Request.

Repair Ship Sales Order Line

Ship to Address with
Customer Name on first
line. There can be two ship
lines, hence exclude the
ship line which does have

Repair Ship Sales Order Line

Ship to Address with
Customer Name on first
line. There can be two ship
lines, hence exclude the
ship line which does have

item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.

item_type =
'GEAS_SHIPPING_CONT' at
the item organization level.

Following query can be

leverage to exclude the
container ship line:-

Following query can be

leverage to exclude the
container ship line:-

NO
NE

Fiel
d/
Colu
mn
Nam
e

Description

Values

inventory_item_id NOT IN

inventory_item_id NOT IN

select inventory_item_id fro

m apps.mtl_system_items_b

select inventory_item_id fro

m apps.mtl_system_items_b

Cal
cul
ati
on
s
(if
an
y)

where organization_id = 112 where organization_id =

112
and item_type =
'GEAS_SHIPPING_CONT';
In case of no sales order,
default from Service
Request.
Gove
rnme
nt
Contr
act
Num
ber

Contract Number to which

work order project number is
associated.

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)

the text based on the note

type.
- If none of the deliverable
lines matches to SO line level
Project, then check Project
match at the Contract header
level for pulling text.
Proje
ct

Work Order Project

Description

Work Order Project

Description

NO
NE

Order
Head
er/Ap
plicat
ion

Project Class Code for

category Platform of the
Projects defined at the work
order. Below sample query
can be used to fetch one data:

Project Class Code of the

Projects defined at the work
order. Below sample query
can be used to fetch one
data:

NO
NE

SELECT ppc.class_code from a

pps.PA_PROJECT_CLASSES ppc
,
apps.pa_projects_all
ppa

SELECT ppc.class_code from a

pps.PA_PROJECT_CLASSES pp
c,
apps.pa_projects_al
l ppa

where ppc.class_category =
'Platform'

where ppc.class_category =
'Platform'

and ppa.project_id = ppc.proj

ect_id

and ppa.project_id = ppc.proj

ect_id

and ppa.segment1 = <Project

Number>;

and ppa.segment1 = <Project

Number>;

Incot
erms

Picked from Sales Order Line

associated on. If blank,
default from Sales Order
Header FOB/Incoterms.
Ignore the container line. In
case of no sales order, will be
blank.

Picked from Sales Order Line

associated on. If blank,
default from Sales Order
Header FOB/Incoterms.
Ignore the container line. In
case of no sales order, will be
blank.

NO
NE

Line
Item

Should be default to 1.0

Should be default to 1.0

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

Part Number - Work Order

Assembly Part Number.

Part Number - Work Order

Assembly Part Number.

Customer Part No Repair

Sales Order Ship Line
related to work order DFF
Attribute named Customer
Part Number. Customer Part
Number should have CPN:
static word appended in the
front.

Customer Part No Repair

Sales Order Ship Line
related to work order DFF
Attribute named Customer
Part Number. Customer Part
Number should have CPN:
static word appended in the
front.

Description is Part Description

from item master. It should
appear on next line.

Description is Part Description

from item master. It should
appear on next line.

HTN is a flex field in category

set named TCT Tagging
assigned at the ship from
warehouse of sales order line.
For details, please see
appendix C

HTN is a flex field in category

set named TCT Tagging
assigned at the ship from
warehouse of sales order line.
For details, please see
appendix C

ECCN is a flex field in category

set named TCT Tagging

ECCN is a flex field in category

set named TCT Tagging

HTN and ECCN should come in

next line after description after
Labels HTN and ECCN:

HTN and ECCN should come in

next line after description after
Labels HTN and ECCN:

Sche
dule
Ship
Date

Work Order Expected

Completion Date. This should
be DD-MON-YYY format.

Work Order Expected

Completion Date. This should
be DD-MON-YYY format.

Ignore container line.

Ignore container line.

QTY/
UOM

Work Order Assembly

Part Qty plus Primary UOM.

Work Order Assembly

Part Qty plus Primary 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

Should be picked from Field

Outbound Serial Number
from collection plan derived
based on Plan Type = RTS
FRACAS as per Appendix
A.

Should be picked from Field

Outbound Serial Number
from collection plan derived
based on Plan Type = RTS
FRACAS as per Appendix
A.

If above value is blank, then

default it from Latest WIP
Issue transaction for the
item tagged as Repair Item
in technician portal and
issued at operation 10.

If above value is blank, then

default it from Latest WIP
Issue transaction for the
item tagged as Repair Item
in technician portal and
issued at operation 10.

Cal
cul
ati
on
s
(if
an
y)

RELE
ASE

Quality Release Code based

on collection plan based on
Plan Type = CAPABILITY
PLAN

Quality Release Code

based on collection plan
based on Plan Type
= CAPABILITY PLAN

NO
NE.

GE
Deleg
ated

Pick from

Pick from

Sales Order Line

ATTRIBUTE1 First DFF GE
Delegated. Picked from
table oe_order_lines_all ATTRI
BUTE1 first field before first ~.

Sales Order Line

ATTRIBUTE1 First DFF GE
Delegated. Picked from
table oe_order_lines_all ATTRI
BUTE1 first field before first
~.

NO
NE.

In case, line field is blank,

display it from
Sales Order Header
ATTRIBUTE1 GE Delegated.
Picked from
table oe_order_headers_all AT
TRIBUTE1 first field before
first ~.

Gove

Pick from

In case, line field is blank,

display it from
Sales Order Header
ATTRIBUTE1 GE
Delegated. Picked from
table oe_order_headers_all AT
TRIBUTE1 first field before
first ~.

Pick from

NO

Fiel
d/
Colu
mn
Nam
e

Description

Values

Cal
cul
ati
on
s
(if
an
y)

rnme
nt

Sales Order Line

ATTRIBUTE1 Second DFF
Government = Y/N. Picked
from
table oe_order_lines_all ATTRI
BUTE1 first field before
second ~ and after first ~.

Sales Order Line

ATTRIBUTE1 Second DFF
Government = Y/N. Picked
from
table oe_order_lines_all ATTRI
BUTE1 first field before
second ~ and after first ~.

NE,

In case, line field is blank,

display it from

In case, line field is blank,

display it from

Sales Order Header

ATTRIBUTE1 Government =
Y/N. Picked from
table oe_order_headers_all AT
TRIBUTE1 field before second
~ and after first ~.

Sales Order Header

ATTRIBUTE1 Government =
Y/N. Picked from
table oe_order_headers_all AT
TRIBUTE1 field before second
~ and after first ~.

Pick from

Pick from

Sales Order Line

ATTRIBUTE1 Third DFF
Regulatory (FAA/CAA). Picked
from
table oe_order_lines_all ATTRI
BUTE1 first field before third
~ and after second ~.

Sales Order Line

ATTRIBUTE1 Third DFF
Regulatory (FAA/CAA). Picked
from
table oe_order_lines_all ATTRI
BUTE1 first field before
third ~ and after second ~.

In case, line field is blank,

display it from

In case, line field is blank,

display it from

Sales Order Header

ATTRIBUTE1 Regulatory
(FAA/CAA). Picked from
table oe_order_headers_all AT
TRIBUTE1 field before third ~
and after second ~.

Sales Order Header

ATTRIBUTE1 Regulatory
(FAA/CAA). Picked from
table oe_order_headers_all AT
TRIBUTE1 field before third ~
and after second ~.

Pick from

Pick from

Sales Order Line

Sales Order Line

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

ATTRIBUTE1 Fourth DFF

Customer. Picked from
table oe_order_lines_all ATTRI
BUTE1 first field before fourth
~ and after third ~.

ATTRIBUTE1 Fourth DFF

Customer. Picked from
table oe_order_lines_all ATTRI
BUTE1 first field before fourth
~ and after third ~.

In case, line field is blank,

display it from

In case, line field is blank,

display it from

Sales Order Header

ATTRIBUTE1 Customer.
Picked from
table oe_order_headers_all AT
TRIBUTE1 field before fourth
~ and after third ~.

Sales Order Header

ATTRIBUTE1 Customer.
Picked from
table oe_order_headers_all AT
TRIBUTE1 field before fourth
~ and after third ~.

Note text from Contracts

related to Work Order Project
where note type - GE QASource Inspection. Ideally,
there should be one note type
with name as GE QA-Source
Inspection for each contract.
In case of multiple notes with
same name as stated above,
concatenated all together and
display.

Note text from Contracts

related to Work Order Project
where note type - GE QASource Inspection. Ideally,
there should be one note type
with name as GE QA-Source
Inspection for each contract.
In case of multiple notes with
same name as stated above,
concatenated all together and
display.

NO
NE.

Please see Appendix D for

details

NO
NE.

Static Address per operating

unit. To be stored in a lookup.
Please see Appendix D

Cal
cul
ati
on
s
(if
an
y)

Report Selection Criteria

Data will be fetched based on the mandatory parameters and other optional
parameters (if provided) passed through the report and based on criteria specified
in Appendix A.

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.

Create a work order with at least one line

having Delegate to GE inspection flag set
to Yes on sales order line DFF and all other
inspection flag set to No.

A Source Inspection Approval Sheet

should be generated with Delegate to
GE to Y and all other source
inspections set to N for that particular
work order.

2.

Create a work order with at least one line

having Government inspection flag set to
Yes on sales order line DFF and all other
inspection flag set to No.

A Source Inspection Approval Sheet

should be generated with Government
Source set to Y and all other source
inspections set to N for that particular
work order.

3.

Create a work order with at least one line

having Regulatory (FAA/CAA) inspection
flag set to Yes on sales order line DFF and
all other inspection flag set to No.

A Source Inspection Approval Sheet

should be generated with Regulatory
(FAA/CAA) set to Y and all other source
inspections set to N for that particular
work order.

4.

Create a work order with at least one line

having Customer inspection flag set to Yes
on sales order line DFF and all other
inspection flag set to No.

A Source Inspection Approval Sheet

should be generated with customer
inspection set to Y and all other source
inspections set to N for that particular
work order.

5.

Create a work order with at least one line

having two inspection flag set to Yes at
sales order line.

A source inspection approval sheet

should be generated with two inspection
flag set to Yes and other set to No.

6.

Create a work order with at least one line

having inspection flag set as blank and
header having same inspection flag set to
Yes.

A source inspection approval sheet

should be generated with one inspection
flag set to Yes as specified on sales
order header.

7,

Ship a delivery with sales order line having

all inspection flag set to No.

No source inspection should be

generated for that sales order line.

8.

Create a work order with sales order line

having all inspection flag set to blank/No.
For lines, where any of the source
inspection flag is blank and corresponding
header inspection flag is also No.

No source inspection should be

generated for that work order.

9.

Repeat all scenarios for 1 to 8 for a work

order having one line having serial
controlled item.

Source Inspection should be printed

when any of inspection flag is set to Yes
at the sales order line level, if any one of
the inspection flag is blank, check the

10.

11.

12.

13.

Repeat cases from 1 to 11 for a project

associates to multiple contracts.

Repeat cases from 1 to 11 for a project

associates to a contact at DTS level.
Repeat cases from 1 to 11 for a project
associates to a contract at contract header
level, but not associated at DTS Level of
any contract.

sales order header is set at Yes and lot

number is populated. In case of multiple
serial numbers, then put all serial
numbers segregated by spaces.
Source Inspection should error out with
the message stating that Project
Number <Project Number> is assigned
to multiple contracts i.e. <Contract
Number 1> , <Contract Number 2>,
<Contract Number 3>.
Source Inspection should be printed with
Prime Contract Number based on
contract where project is associated to
contract at DTS level.
Source Inspection should be printed with
Prime Contract Number based on
contract where project is associated to
contract at header level.

Customer Part Number value should be

Repeat all cases from 1 to 11 and check
printed as per logic in appendix F
for Customer Part No printed for each OE
sales order.

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.

Open and Closed Issues

Issue

Comments

Resolution

Owner