FLS BOISE MD070 Order Acknowledgement 1.1

8/2/2019 FLS BOISE MD070 Order Acknowledgement 1.1

1/27

AIM

MD.070 APPLICATION EXTENSIONTECHNICAL DESIGN

FLSmidth

Order AcknowledgementReport

Author: Satish Kumar Singh

Creation Date: Febuary 27, 2012

Last Updated: Febuary 27, 2012

Document Ref: FLS_BOISE_MD070_Order_Acknowledgement_1.0

Version: 1.0

Approvals:


2/27

MD.070 Application Extension Technical Design

Document Control

Change Record

5

Date Author Versio

n

Change Reference

27-Feb-2012

Satish KumarSingh

1.0 No Previous Document

Reviewers

Name Position

Micheal Fisher ManagerVenu Gopal

Distribution

CopyNo.

Name Location

1234

Note To Holders:

If you receive an electronic copy of this document and print it out, pleasewrite your name on the equivalent of the cover page, for documentcontrol purposes.

If you receive a hard copy of this document, please write your name onthe front cover, for document control purposes.

File Ref: 89091877.doc (v. 1.0)CompanyConfidential - For internal use only

XXFLS - Order Acknowledgement Report Boise - Concurrent Program Logic13 of 24


3/27


Contents

Document Control.......................................................................................ii

Technical Overview.....................................................................................v

Approach...............................................................................................vModule List............................................................................................v

- Form Logic.........................................................................vi

Navigation Logic...................................................................................vi

Block Relationship Diagram.................................................................viTable and View Usage.........................................................................viiZone and Field Summary...................................................................viii

XXFLS - Order Acknowledgement Report Boise - Concurrent Program Logic...................................................................................................................ix

Calling Arguments................................................................................ixTable and View Usage........................................................................xiiiProgram Logic (pseudo code)..............................................................xvSQL Statements...................................................................................xvDefault Data Sources..........................................................................xixValidation Logic..................................................................................xixIncompatibility.....................................................................................xxPerformance Considerations...............................................................xxOther Considerations...........................................................................xx

Integration Issues.....................................................................................xxi

Changes Required..............................................................................xxiShared Components...........................................................................xxiAlert conditions...................................................................................xxiIncompatibilities.................................................................................xxiPerformance Issues............................................................................xxi

Database Design.....................................................................................xxii

Desired Table Changes......................................................................xxii

New/Updated Seed Data....................................................................xxiiDescriptive Flexfields.........................................................................xxiiValue Sets..........................................................................................xxiiGrants/Synonyms.............................................................................xxiiiArchiving...........................................................................................xxiiiDatabase Diagram...........................................................................xxiii Tables, Indexes, Sequences..............................................................xxiii

Installation Requirements......................................................................xxiv

Implementation Notes.............................................................................xxv

Design Summary...............................................................................xxv




4/27


Coding Summary...............................................................................xxvTesting Summary..............................................................................xxvInstallation........................................................................................xxvi

Open and Closed Issues for this Deliverable..........................................xxvii

Open Issues......................................................................................xxviiClosed Issues...................................................................................xxvii




5/27


Technical Overview

This document defines the technical components required to implementcustomization Order Acknowledgement Report. This ApplicationExtension Technical Design document complements the ApplicationExtension Functional Design document for Order AcknowledgementReport and you should consider the set to be the complete detaileddesign.

Approach

Module List

Forms

includes the following forms:

Reports

Order Acknowledgement Report includes the following reports:

XXFLS_ONT_OEXORDERACK_BOISE.rdf

Concurrent Programs

Order Acknowledgement Report includes the following concurrent

programs:

XXFLS Order Acknowledgement - Boise

Database Triggers

includes the following database triggers:




6/27


- Form Logic

Navigation Logic

Entry Mode

START

1. User enters data into form.

2. User commits transaction.

3. Form calls concurrent program X with selected parameters.

4. Form displays "Request xxxx has been sent to the concurrentmanager".

5. User presses any key to acknowledge message.

6. Form clears.

7. Cursor moves to field 1.

END

Block Relationship Diagram

The diagram below represents the base tables of each block or zone ofthe form (vertical) and tables referenced for validation or lookups(horizontal).

B a s e T a b l e

L o o k u p T a b l e

C h i l d T a b l e

P a r e n t

o f

C h i l d

o f




7/27


Table and View Usage

Table Name Select Insert Update Delete Base Table

X

hr_all_organization_units

hr_locations_all

hr_operating_units

xle_entity_profilesper_all_people_f

fnd_attachment_functions

fnd_doc_category_usages

fnd_documents_vl

fnd_attached_documents

fnd_documents_short_text

oe_order_headers_all

oe_order_lines_all

oe_order_types_v

oe_transaction_types_tl

oe_arguments_v

oe_lookups

oe_charge_lines_v

ar_lookups

ra_terms

ra_contacts

hz_parties

hz_party_sites

hz_loc_assignments

hz_locations

hz_cust_acct_sites_allhz_cust_accounts_all

hz_cust_accounts

hz_relationships

ra_salesreps

fnd_user

mtl_system_items

mtl_system_items_tl

mtl_units_of_measure

wsh_carriers_v

wsh_carrier_ship_methods

fnd_territories_vl




8/27


Zone and Field Summary

Zone 1

Base Table:

Where/Order By:

Field/Column Type Rqd?

Default

Validation QuickPick

Field 1COLUMN_NAME

Char Yes Validatedagainstfrom

where =

Display MEANINGfrom _LOOKUPS where

LOOKUP_TYPE ='

Oranization_name

Yes

Sales PersonCustomer RFQTermsShip ViaOrder DateItemQuantityPart #

Item DescriptionUnit WeightUnit PriceExtended Price

Zone 2

Base Table:

Where/Order By:

Field Type Rqd?

Default Validation QuickPick

Field 1COLUMN_NAME

Char No (QuickPickvalidation)

Display MEANINGfrom _LOOKUPSwhere LOOKUP_TYPE= '




9/27


XXFLS - Order Acknowledgement Report Boise - ConcurrentProgram Logic

Calling Arguments

XXFLS- Order Acknowledgement Report Boise is called from theStandard Report Submission form with the following arguments:

Argument Prompt Value Set Default Value

Set of BooksId

Set of Books Id OE: Number ZeroPrecision

selectto_number(FND_PROFILE.VALUE('GL_SET_OF_BKS_ID')) fromdual

OrganizationId

Organization Id OE: Number ZeroPrecision

selectfnd_profile.value('ORG_ID') from DUAL

Item FlexCode

Item Flex Code OE: Text OE_ID_FLEX_CODE

Item Display Item Display ONT_SRS_ITEM_DISPLAY_CODE

select meaning fromoe_lookups wherelookup_type ='ITEM_DISPLAY_CODE' and lookup_code ='D'

BookedStatus

Booked Status OM: Yes or No

Order Type Order Type ONT_SRS_ORDER_TYPE

OrderNumber(From)

Order Number (From) FND_NUMBER

OrderNumber (To)

Order Number ( To) FND_NUMBER select :$FLEX$.FND_NUMBERfrom sys.dual

Order Date(From)

Order Date ( From) FND_STANDARD_DATE

Order Date(To)

Order Date (To) FND_STANDARD_DATE

selectfnd_date.date_to_cha

rdate(fnd_date.canonical_to_date(:$FLEX$.FND_STANDARD_DATE)) fromsys.dual

Bill ToCustomerName(From)

Invoice To CustomerName ( From)

XXFLS_ONT_SRS_CUSTOMER_NAME




10/27



Bill ToCustomerName (To)

Invoice To CustomerName (To)


select :$FLEX$.XXFLS_ONT_SRS_CUSTOMER_NAMEfrom sys.dual

Ship ToCustomerName(From)

Ship To CustomerName ( From)


Ship ToCustomerName (To)

Ship To CustomerName (To)



ScheduleDate (From)

Schedule Date (From) FND_STANDARD_DATE

ScheduleDate (To)

Schedule Date (To) FND_STANDARD_DATE

selectfnd_date.date_to_chardate(fnd_date.canonical_to_date(:$FLEX$.FND_STANDA

RD_DATE)) fromsys.dual

RequestDate (From)

Request Date (From) FND_STANDARD_DATE

RequestDate (To)

Request Date (To) FND_STANDARD_DATE

selectfnd_date.date_to_chardate(fnd_date.canonical_to_date(:$FLEX$.FND_STANDARD_DATE)) fromsys.dual

PromiseDate (From)

Promise Date (From) FND_STANDARD_DATE

PromiseDate (To)

Promise Date (To) FND_STANDARD_DATE

selectfnd_date.date_to_chardate(fnd_date.canonical_to_date(:$FLEX$.FND_STANDARD_DATE)) fromsys.dual

OrderCategory

Order Category ONT_SRS_ORDER_CATEGORY

select meaning fromoe_lookups wherelookup_type='REPORT_ORDER_CATEGORY' and

lookup_code='SALES'LineCategory

Line Category ONT_SRS_LINE_CATEGORY

select meaning fromoe_lookups wherelookup_type='REPORT_LINE_DISPLAY' andlookup_code='ALL'

Salesperson Salesperson ONT_SRS_SALESREPS

Created By Created By ONT_SRS_AOL_USER




11/27



Open OrdersOnly

Open Orders Only OM: Yes or No select meaning fromfnd_lookups wherelookup_type='YES_NO' andlookup_code='Y'

Deliver ToCustomer(From)

Deliver To CustomerName(From)


Deliver ToCustomer(To)

Deliver To CustomerName (To)



ShowHeaderAttachments

Show HeaderAttachments

OM: Yes or No select meaning fromfnd_lookups wherelookup_type ='YES_NO' andlookup_code = 'N'

Show BodyAttachments

Show BodyAttachments

OM: Yes or No select meaning fromfnd_lookups where

lookup_type ='YES_NO' andlookup_code = 'N'

Show FooterAttachments

Show FooterAttachments

OM: Yes or No select meaning fromfnd_lookups wherelookup_type ='YES_NO' andlookup_code = 'N'

Organization_id

Organization_id WIP_SRS_NUMERIC_ OPT

MFG_ORGANIZATION_ID

Print Weight Print Weight OM: Yes or No select meaning fromfnd_lookups wherelookup_type='YES_NO' andlookup_code='N'

Print asProformaInvoice

Print as ProformaInvoice

OM: Yes or No select meaning fromfnd_lookups wherelookup_type='YES_NO' andlookup_code='N'

Main Template:-

XXFLS_ONT_OEXOEACK_BOISE.rtf




12/27


Log Output:-

Responsibility FLSUS978 OM Super User (Boise) Template




13/27


Table and View Usage

Table Name Select Insert Update Delete

X

hr_all_organization_units




14/27


Table Name Select Insert Update Delete

X

hr_locations_all

hr_operating_units

xle_entity_profiles

per_all_people_f

fnd_attachment_functions

fnd_doc_category_usages

fnd_documents_vl

fnd_attached_documents

fnd_documents_short_text

oe_order_headers_all

oe_order_lines_all

oe_order_types_v

oe_transaction_types_tl

oe_arguments_v

oe_lookups

oe_charge_lines_v

ar_lookups

ra_terms

ra_contacts

hz_parties

hz_party_sites

hz_loc_assignments

hz_locations

hz_cust_acct_sites_all

hz_cust_accounts_all

hz_cust_accounts

hz_relationshipsra_salesreps

fnd_user

mtl_system_items




15/27


Program Logic (pseudo code)

BEGIN1. Selected Column OPERATING_UNIT to show Operating unit (See Query 1)

2. Selected Columns, Order_Number, Order_Date,

Purchase_Order, Order_Type, Sales_Person, Payment_Terms

To Show Header Information (See Query 2)

4. Selected Columns line_number, ordered_quantity, ordered_item,

Request_Date, Promise_Date, Selling_Price to show Lines

Information (See Query 3)

5. For Discount (See Query 4).

6. For Header Attachment (See query 5,5.1,5.2).

7. For Line Attachment (See query 6).

8. For Sum of Products Cost group by FOB (See query 7).

9. For Header Charges (See query 8).

10. For Line Charges (See query 9).

11. For Line Service Reference (See query 10).

END

SQL Statements

1 - Data Selection

Query 1 for Ligal Entity

---------------------------

SELECT haou.organization_id,

haou.name org_name,

RTRIM(xle.name,'(LE)') legal_entity_name,

hl.derived_locale,

hl.location_code,

hl.address_line_1,

hl.address_line_2,

hl.address_line_3,

hl.town_or_city,hl.country,

hl.postal_code,

hl.region_1,

hl.region_2,

hl.telephone_number_1 tel,

hl.telephone_number_2 fax

FROM hr_all_organization_units haou,

hr_locations_all hl,

hr_operating_units hou,

xle_entity_profiles xle

WHERE haou.location_id = hl.location_id

AND hou.organization_id = haou.organization_id

AND hou.default_legal_context_id = legal_entity_id

Query 2 for Headers

----------------------

Order Akw_headercode.sql

Query 3 for Lines

--------------------




16/27


Order Akw_linesCode.sql

Query 4 for Discount

----------------------

SELECT P.HEADER_ID,

P.LINE_ID, SUM(DECODE(

P.LINE_ID,

NULL,

DECODE(P.CREDIT_OR_CHARGE_FLAG,

'C',(-1) * P.OPERAND,

P.OPERAND),

DECODE(

P.CREDIT_OR_CHARGE_FLAG,

'C',

DECODE(

P.ARITHMETIC_OPERATOR,

'LUMPSUM',

DECODE(l.ordered_quantity,0,0,(-1) * (P.OPERAND)), (-1) * (L.ORDERED_QUANTITY * P.ADJUSTED_AMOUNT)

),

DECODE(P.ARITHMETIC_OPERATOR,

'LUMPSUM',

DECODE(l.ordered_quantity,0,0,P.OPERAND),

(L.ORDERED_QUANTITY * P.ADJUSTED_AMOUNT))

)

))

DISCOUNT

FROM OE_PRICE_ADJUSTMENTS P, --OE_PRICE_ADJUSTMENTS P,

OE_ORDER_LINES_ALL L

WHERE P.LINE_ID = L.LINE_ID(+)

ANDP.LIST_LINE_TYPE_CODE ='DIS' ANDP.APPLIED_FLAG ='Y'

--AND P.ADJUSTMENT_NAME not in('Price Override')

ANDP.LIST_HEADER_ID IN(SELECT LIST_HEADER_ID

FROM QP_LIST_HEADERS_TL

WHERE NAME'Price Override')--7014

--AND P.HEADER_ID=1789

GROUPBY P.HEADER_ID,P.LINE_ID

Query 5 Header Attachments

-----------------------------

SELECT DECODE(fndcatusg.format,

'H', st.short_text, NULL, st.short_text,

NULL)

hdr_short_text,

DECODE(fndcatusg.format,'B', st.short_text,NULL) body_short_text,

DECODE(fndcatusg.format,'F', st.short_text,NULL) ftr_short_text,

DECODE(fndcatusg.format,'H', description,NULL) hdr_attach_desc,

DECODE(fndcatusg.format,'B', description,NULL) body_attach_desc,

DECODE(fndcatusg.format,'F', description,NULL) ftr_attach_desc,

ld.LONG_TEXT,

fnddoc.CATEGORY_DESCRIPTION,

pk1_value hdr_attach_pk,

fnddoc.datatype_name hdr_attach_dtype




17/27


FROM fnd_attachment_functions fndattfn,

fnd_doc_category_usages fndcatusg,

fnd_documents_vl fnddoc,

fnd_attached_documents fndattdoc,

fnd_documents_short_text st,

fnd_documents_long_text ld

WHERE fndattfn.attachment_function_id = fndcatusg.attachment_function_id

AND fndcatusg.category_id = fnddoc.category_id

AND fnddoc.document_id = fndattdoc.document_id

AND fndattfn.function_name ='OEXOEACK'

AND fndattdoc.entity_name ='OE_ORDER_HEADERS'

AND fnddoc.media_id = st.media_id

AND fnddoc.media_id = ld.media_id

--and pk1_value=1750

ORDERBY fndattdoc.seq_num

Query 5.1 Header Attachments

-----------------------------

SELECT fndattdoc.pk1_value,

log_att.LONG_TEXT ATTH_SALUTATION,

fnddoc.CATEGORY_DESCRIPTION

FROM fnd_documents_long_text log_att,



fnd_attachment_functions fndattfn

WHERE fnddoc.media_id = log_att.media_id




--and fndattdoc.pk1_value=1750

--and fnddoc.category_id=1000653

AND fnddoc.CATEGORY_DESCRIPTION IN('FLS SPARES SALUTATION')

Query 5.2 Header Attachments

-----------------------------

SELECT fndattdoc.pk1_value,

log_att.LONG_TEXT ATTH_FOOTER,

fnddoc.CATEGORY_DESCRIPTION

FROM fnd_documents_long_text log_att,



fnd_attachment_functions fndattfn

WHERE fnddoc.media_id = log_att.media_id




--and fndattdoc.pk1_value=1750

--and fnddoc.category_id=1000653

AND fnddoc.CATEGORY_DESCRIPTION ='FLS SPARES FOOTER'

Query 6 line Attachments

--------------------------

SELECT st.short_text,

description line_attach_desc,

pk1_value line_attach_pk,

datatype_name line_attach_dtype,

fndcatusg.format line_attach_format

FROM fnd_attachment_functions fndattfn,

fnd_doc_category_usages fndcatusg,



fnd_documents_short_text st

WHERE fndattfn.attachment_function_id = fndcatusg.attachment_function_id

AND fndcatusg.category_id = fnddoc.category_id




18/27




AND fndattdoc.entity_name ='OE_ORDER_LINES'

AND fnddoc.media_id = st.media_id

ORDERBY fndattdoc.seq_num

Query 7 Sum of Products Cost group by FOB

--------------------------------------------

SELECT l.header_id,

--l.pricing_quantity,

--uom.UOM_CODE,

--l.unit_selling_price Selling_Price,

SUM((l.unit_selling_price) * (l.ordered_quantity)) SUM_total_price,

lk2.meaning Line_FOB,

lk2.description Line_fob_des

FROM oe_order_lines_all l,

oe_line_types_v ol,

mtl_units_of_measure uom,

mtl_system_items si,

wsh_carriers_v f,

WSH_CARRIER_SHIP_METHODS_V CSM, /* Added for bug#2373742 */

--oe_agreements_v a,

oe_lookups lk1,

ar_lookups lk2,

ra_salesreps sr,

ra_terms terms

WHERE l.line_type_id = ol.line_type_id(+)

-- and l.org_id=:p_organization_id

-- and l.line_category_code = 'ORDER'

-- and l.service_reference_line_id is null /* Changed for bug#2597093 */

AND(l.service_reference_line_id ISNULL

OR l.service_reference_type_code 'ORDER'

OR(l.service_reference_type_code ='ORDER'

ANDNOTEXISTS

(SELECT header_id

FROM oe_order_lines_all

WHERE line_id = l.service_reference_line_id

AND header_id = l.header_id)))

AND l.order_quantity_uom = uom.uom_code(+)

AND l.inventory_item_id = si.inventory_item_id

ANDNVL(si.organization_id,0)=:c_master_org

AND terms.term_id(+)= l.payment_term_id

AND sr.salesrep_id(+)= l.salesrep_id

--and a.agreement_id(+) = l.agreement_id

AND lk1.lookup_code(+)= l.freight_terms_code

AND lk1.lookup_type(+)='FREIGHT_TERMS'

AND lk2.lookup_code(+)= l.fob_point_code

AND lk2.lookup_type(+)='FOB'

AND CSM.ship_method_code(+)= l.shipping_method_code

ANDNVL(CSM.organization_id(+),0)=:c_master_org

AND f.freight_code(+)= CSM.freight_code

GROUPBY lk2.meaning,

l.header_id,

lk2.meaning,

lk2.description

ORDERBY l.header_id;

Query 8 Header Charges

------------------------




19/27


SELECTsum(charge_amount) header_charge,CHARGE_NAME header_charge_name,

header_id

FROM oe_charge_lines_v

GROUPBY header_id, CHARGE_NAME

Query 9 Line Charges

----------------------

SELECTSUM(charge_amount) Line_Charge, CHARGE_NAME line_charge_name,

header_id,line_id

FROM oe_charge_lines_v

WHERE line_id isnotnull

GROUPBY header_id, line_id,CHARGE_NAME;

Query 10 Line Service Reference

---------------------------------

SELECT NVL(svc_lin.unit_selling_price,0) svc_selling_price,

svc_lin.service_duration,

(NVL(svc_lin.pricing_quantity,0))

* NVL(svc_lin.unit_selling_price,0)

svc_extended_price,

svc_lin.service_end_date,

svc_lin.order_quantity_uom svc_unit_code,

svc_lin.service_reference_line_id,

svc_lin.tax_value tax_on_svc_line,

mtl.description svc_item_description

FROM mtl_system_items_tl mtl, oe_order_lines_all svc_lin

WHERE svc_lin.item_type_code ='SERVICE'

AND mtl.language=:p_user_lang

ANDNVL(svc_lin.org_id,0)=NVL(:p_org_id,0)

AND svc_lin.inventory_item_id = mtl.inventory_item_id

ANDNVL(mtl.organization_id,0)=:c_master_org

Default Data Sources

Table Column Source Value


20/27


Warning Conditions:

Incompatibility

Performance Considerations

Other Considerations

Restart Strategy

Crash Recovery




21/27


Integration Issues

Changes Required

Within ProductCustom menus

Other Products

No changes required

Shared Components

INV

None

BOM

None

ENG

None

MPS/MRP

None

WIP

None

Alert conditions

None.

Incompatibilities

None.

Performance Issues

None.




22/27


Database Design

This section summarized new and changed database objects and datarequired supporting XXFLS - Order Acknowledgement Report Boise. However, the complete database design is documented in theDatabase Extensions Design document.

Desired Table Changes

None

New/Updated Seed Data

Rows added to _LOOKUPS:

Lookup TypeCode Meaning

Descriptive Flexfields

Application:Form Name:Base Table:

Segment Name Prompt Size Value Set Default Value

Application:Form Name:Base Table:

Segment Name Prompt Size Value Set Default Value

Value Sets

Value Set Size

Type Rqd

Validation/Values

OE: Number Zero Precision 38 SQLStatement

Yes

OE: Text 30 Profile YesONT_SRS_ITEM_DISPLAY_CODE 50 SQL

Statement

Yes




23/27


Value Set Size

Type Rqd

Validation/Values

OM: Yes or No 50 SQLStatement

Yes

ONT_SRS_ORDER_TYPE 50 SQLStatement

No

FND_NUMBER 15 SQLStatemen

t

No

FND_STANDARD_DATE 11 SQLStatement

No


50 SQLStatement

No

ONT_SRS_ORDER_CATEGORY 50 SQLStatement

No

ONT_SRS_LINE_CATEGORY 50 SQLStatement

No

ONT_SRS_SALESREPS 30 NoONT_SRS_AOL_USER 50 NoWIP_SRS_NUMERIC_OPT 30 Profile Yes

Grants/Synonyms

Owner Object Grantees

Archiving

No need to archive.

Database Diagram

No new tables

Tables, Indexes, Sequences

No new table




24/27


Installation Requirements

Installation scripts must be prepared to perform the following actions inan automated way:

1. Create new tables.

2. Insert seed data into _SYNONYM as describedabove.

3. Run grant/synonym script.

4. Define Value Sets and Validation Tables.

5. Define Descriptive Flexfields.

6. Define Help text.

7. Define Message text.

8. Register Forms.

9. Register Concurrent Programs.

10. Register Standard Report Submission parameters.

11. Create Menus.




25/27


Implementation Notes

This document describes exactly how XXFLS - OrderAcknowledgement Report Boise was developed and implemented atFLSmidth.

Design Summary

Functional Design

Functional Design Approval

Technical Design

Design Review

Final Acceptance

Coding Summary

Development was done on , to work withRelease of Oracle Applications. All coding follows the standards defined inthe Build Standards document for XXFS - Order AcknowledgementReport Boise

Program Files

The files required for this customization are as follows:

File Description Coded By

Testing Summary

The customizations were tested in FLSmidth's test environment beforebeing moved to production. See the Link Test scripts for moreinformation.




26/27


Installation

All modules are installed as if part of a separate product. A UNIXdirectory structure is created under $APPL_TOP as shown in the followingexample:

$APPL_TOP|

XXFLS|1.0.0

___________________________|___________________________________| | | | | | | | |

forms bin src sql log out srw install sql

The directories contain the components of the enhancement as shownbelow (directories not listed are empty). All future customizations willalso be stored in these directories.

forms/

bin/src/sql/srw/install/sql/

The forms and concurrent programs are registered in Application ObjectLibrary under the FLS Common application.

A new set of menus (owned by XXFLS) is created to call the new forms asfollows:

The basic specifications are as follow

Report Name : XXFLS Order Acknowledgement -Boise

Application : FLS Common

RDF :XXFLS_ONT_OEXORDERACK_BOISE.rdf

RTF :XXFLS_ONT_OEXOORDER_BOISE.rtf

Request Group: OM Concurrent Programs

Responsibulity : FLSUS978 OM Super User

Navigation:

FLSUS978 OM Super User--> Reports

--> Run Reports

Name: XXFLS Order Acknowledgement- Boise




27/27


Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date ImpactDate

Closed Issues

ID Issue Resolution Responsibility Target Date ImpactDate

Documents

FLS BOISE MD070 Order Acknowledgement 1.1