CF.

250 FUNCTIONAL DESIGN

AA Power Systems Wind
Energy
Debrief Install Base Update
Gap
Author:
Creation Date:
Last Updated:
Document Ref:
Version:
Approvals:

Jeffrey Maurer
Henry Felkey
Elieen White
Leanne Peduzzi

2.3

Doc Ref: Document RefCF-250 TS Oracle integration

Document Control
ChanAA Record
1

Date

Author

Versio
n

ChanAA Reference

23-Mar-04
14-April-04

Prasad Marathe
Jim Simpson

1.0
2.0

15-April-04

Jim Simpson

2.1

21-April-04
21-July-04

Jim Simpson
Ganesh
Shanmukham

2.2
2.3

No Previous Document
Updated info related to AAneral review of
document.
ChanAAd the Task status to closed instead of
completed.
Updated per comments from TG3 review.
Updated Document for CR 794565

Reviewers

Name

Position

Henry Felkey

Deployment ManaAAr

Eileen White
Leanne Peduzzi
Jeffrey Maurer

IM Project Lead
MBB
Program ManaAAr

Distribution

Copy
No.

Name

Location

1
2
3
4

Library Master

Project Library

File Ref: CF-250 Debrief Install Base Update Gap

ii

Doc Ref: Document RefCF-250 TS Oracle integration

Contents

Document Control.......................................................................................ii
Executive Summary....................................................................................4
Business Rules............................................................................................5
Assumptions...............................................................................................6
Solution Design........................................................................................... 7
Process Flow Debrief Install Base Update...............................................8
Open and Closed Issues for this Deliverable...............................................9
Open Issues........................................................................................... 9
Closed Issues.........................................................................................9

File Ref: CF-250 Debrief Install Base Update Gap

iii

Executive Summary
This document describes the Debrief Install Base update solution for
AAneral Electric Wind Energys E-Service Release 1.0 Implementation. It
contains a high-level description of the solution as well as details related
to solutions being developed that are not included in the BR.150.
E-Services Release 1.0 consists of core implementation of Field Service,
Contracts & Install Base along with partial implementation of inventory
and financial modules.
On the Debrief form in the material tab, if an installed base item is, (Order
and Return of items), the chanAAs should be updated in Oracle installed
base through a custom program. The Oracle standard concurrent program
is disabled so that inventory and other modules are not affected.

CF-250 Debrief Install Base Update Gap

Business Rules

There should not be any updates in the CharAAs and Inventory for
any Material Transaction on the Debrief Form.

The Material Transaction for an Item on the Debrief form needs to

be reflected in the Install Base for all installed base items.

The new part no can be different than the old part no, but the
instance type code remains the same.

The Old part no is expired

Ability to resell the returned part nos to any customer after repair.
The user should be indicated in Debrief that this is an installed
base item.

The data entry for replacement is accomplished by entering

o

A order line for the new part with the new serial no

A return line for the old part with the old serial no. This
requires the part to be present in Oracle installed base

If old part no not in installed base

o

The user cannot enter the return line, as the old part is not
present in installed base.

Since information about old part no is required to complete

updateDo not update the installed base

Send notification to IB administrative

When a parent is replaced, only the parent component is created

in installed base. The configuration of the parent component
should be created manually by the configuration team

The parent and Child component should not be entered in Debrief

unless intended.

Inorder for MFS to function, the dummy instance number will be

used for all installed base items. However the serial no entered is
the actual serial no. Do not use the dummy instance.

File Ref: CF-250 Debrief Install Base Update Gap

5

CF-250 Debrief Install Base Update Gap

Assumptions

Install base setup is completed and Inventory is partially

implemented.

Items are Install base Trackable, and defined in the Inventory &
Install Base.

The Custom Material Transaction types for Order and return of

items are defined.

Default sub inventories are assigned to Field Engineers that are

required to do material debriefs.

Turbine configuration is fully defined in installed base as per

scope.

Configurations are entered manually in Oralce installed base and

not through debrief.

File Ref: CF-250 Debrief Install Base Update Gap

6

CF-250 Debrief Install Base Update Gap

Solution Design
The information entered by the Field Engineer regarding the Material Transaction on debrief form
will be reflected in the Install Base only. It will not impact CharAAs and Inventory.
When the Assignment status on the Debrief form is chanAAs to Closed, a concurrent program
CSF: Update Debrief Lines is trigAAred automatically. This program will update Install Base,
CharAAs and Inventory with the information on the Debrief Form. Within this standard concurrent
program, there is an Oracle Standard API that trigAArs the Install base update.
In order to avoid the update of the CharAAs and Inventory, and to also update the install base the
following steps are required.
Step-1: Per Oracle standard functionality, the Instance number will be Non-Mandatory on the
Debrief form for order transaction and be mandatory for return transactions.
Step-2: The Standard Concurrent Program CSF: Update Debrief Lines will be disabled in order to
stop it from trigAAring chanAAs in the Assignment status on the debrief form.
Step-3: Field Engineers responsible for material debriefs will make chanAAs (Insert & updates) on
the debrief form regarding the Material Transactions as per below.
3.1 In the Debrief Form for an Order_Material_Transaction transaction.
a) Enter the install-base trackable item details.
When debrief is entered in MFS, the dummy instance number will be used for all
installed base items. However the serial no entered is the actual serial no. Do not use
the dummy instance instead create a new instance.
b) Provide the parent instance id from customer location (if applicable).
c) SAVE the chanAAs in the Debrief Form.
3.2 In the Debrief Form for Return_Material_Transaction transaction.
a) Enter the item details. Provide the instance number and parts serial number (As this
item is being returned).
b) SAVE the chanAAs in the Debrief Form.
Step-4: When a Task is completed (Task status = Closed), the Task workflow trigAArs a Custom
Concurrent program. This program processes the Debrief lines associated with the task using
Oracle Standard Update Install Base API CSF_IB.Update_install_base .
Step-5: This program updates the Install-base trackable item information for both ordered, and
returned items.

File Ref: CF-250 Debrief Install Base Update Gap

7

CF-250 Debrief Install Base Update Gap

Process Flow Debrief Install Base Update

File Ref: CF-250 Debrief Install Base Update Gap

8

CF-250 Debrief Install Base Update Gap

Open and Closed Issues for this Deliverable

Open Issues
ID

Issue

Resolution

Responsibility

TarAAt
Date

Impact
Date

Responsibility

TarAAt
Date

Impact
Date

Closed Issues

ID

Issue

Resolution

File Ref: CF-250 Debrief Install Base Update Gap

9