MD.070 A E T D: USG PO Report

AIM
MD.070 APPLICATION
EXTENSION TECHNICAL DESIGN
USG
PO Report
Author: Bhavani
Creation Date: June 10, 2005
Last Updated: Junely 104, 2005
Document Ref: MD270_SCM_01
Version: DRAFT1.0
Approvals:
<Approver 1>
<Approver 2>
MD.070 Application Extension Technical Design Doc Ref: MD270_SCM_01
Junely 104, 2005
Document Control
Change Record
4
Date Author Version Change Reference
10-June-2005 Bhavani Draft 1a No Previous Document

14-July-2005 Bhavani 1.0 Item valuation to be done at company
level(Previously item valuation is done at warehouse
level)
Reviewers
Name Position
Srinivas Krishna(BK)
Pauline Vogl
Atul Solanki
Distribution
Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4
Note To Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.
PO Report <Form Title> - Form Logic 4 of 7

File Ref: 52149989.doc (v. DRAFT1. )
Company Confidential - For internal use only
Junely 104, 2005
Contents
Document Control...................................................................................................................ii
Technical Overview.................................................................................................................1
Approach............................................................................................................................1
Module List........................................................................................................................3
<Form Title> - Form Logic.....................................................................................................4
Navigation Logic..............................................................................................................4
Block Relationship Diagram...........................................................................................4
Table and View Usage.....................................................................................................4
Zone and Field Summary................................................................................................4
Special Logic......................................................................................................................5
Telik Inventory Valuation Report - Concurrent Program Logic......................................5
Calling Arguments...........................................................................................................5
Log Output....................................................................Error! Bookmark not defined.
Table and View Usage.................................................Error! Bookmark not defined.
Program Logic (pseudo code)....................................Error! Bookmark not defined.
SQL Statements.............................................................Error! Bookmark not defined.
Default Data Sources ........................................................................................................5
Validation Logic................................................................................................................5
Incompatibility..................................................................................................................5
Performance Considerations...........................................................................................5
Other Considerations.......................................................................................................6
Integration Issues.....................................................................................................................7
Changes Required.............................................................................................................7
Shared Components.........................................................................................................7
Alert conditions................................................................................................................7
Incompatibilities................................................................................................................7
Performance Issues...........................................................................................................7
Database Design.......................................................................................................................8
Desired Table Changes....................................................................................................8
New/Updated Seed Data................................................................................................8
Descriptive Flexfields .......................................................................................................8
Value Sets...........................................................................................................................8
Grants/Synonyms............................................................................................................9
Archiving...........................................................................................................................9
Database Diagram............................................................................................................9
Tables, Indexes, Sequences.............................................................................................9
Installation Requirements..................................................Error! Bookmark not defined.

Junely 104, 2005
Implementation Notes........................................................Error! Bookmark not defined.
Design Summary..........................................................Error! Bookmark not defined.
Coding Summary.........................................................Error! Bookmark not defined.
Testing Summary.........................................................Error! Bookmark not defined.
Installation.....................................................................Error! Bookmark not defined.
Open and Closed Issues for this Deliverable..................Error! Bookmark not defined.
Open Issues...................................................................Error! Bookmark not defined.
Closed Issues.................................................................Error! Bookmark not defined.
Metrics Information.....................................................Error! Bookmark not defined.

Junely 104, 2005
Technical Overview
This document defines the technical components required to implement
customization <BRM Number>, PO Report. This Application Extension Technical
Design document complements the Application Extension Functional Design
document for PO Report and you should consider the set to be the complete
detailed design.
Approach
Standard
Oracle
Applications
User Will submit the PO Report from SRS window
POReport should be Executed internally.
Output should be generated in HTML Format

Junely 104, 2005
Step 1: A Custom Oracle Report ‘USG_PO.rdf’ and Concurrent Program

‘PO Report’ have to be created in the
Development instance.
This concurrent program should be taken from the scratch there is no base
report for this.
As USG is going to expense out the PURCHASING till the commercial production,
a Descriptive Flexfield will be enabled at PO Line line Level it should contains the
Item cost details form where TELIK users responsible for costing these inventory
item will manually enter the calculated cost outside Oracle System for FG Items.
RDF Should Contains the following Columns
Set Of Books Name: Default Value should be from the Profile Option
Responsibility : Default Value should be from the Profile Option
Inventory Organization: Default Value should be from the Profile Option
Report will take Two Parameters
From Purchase Order No:
To Purchase Order No:
The PO Report’ Report Lay out is given below:

Report Parameters
Organization:
From PO
To PO:
USG PO Report Report Date:
PONO Supplie SupplierSite Contact Buyer PO total Bill TO ShipTO Currency

r Person

Junely 104, 2005
Step 2: The developed Custom report “USG_PO.rdf” and Concurrent Programs

“PO Report’” have to be moved from development instance to Test/Production instance
(Details are provided in the MD120 Document)
Module List
Reports
PO Report’ includes the following reports:
Concurrent Progtam Name : USG Purchase Order Report
Executable Name :USGPO.rdf
Custom Path :USG_TOP\PO\11.5.0\Reports\US\
Request Group : All PO Reports
Responsibility :PO Users Responsibility

Junely 104, 2005
<Form Title> - Form Logic

N/A
Navigation Logic
Entry Mode
START
1. User enters Parameters in the First Concurrent Program SRS Window..

2. It will shows the PO details and the same Parameters will be passed to the
Invoice report Internally
END
Block Relationship Diagram
The diagram below represents the base tables of each block or zone of the form
(vertical) and tables referenced for validation or lookups (horizontal).
Table and View Usage
Table Name Select Insert Update Delete Base Table

X
MTL_SYSTEM_ITEMSN/A
PO_HEADERS_ALL Y Y
PO_LINE_ALL Y Y
PO_VENDORS Y Y
PO_VENDOR_SITES_All Y Y
PO_VENDOR_CONTACTS Y Y
HR_LOCATIONS Y Y
Zone and Field Summary
Zone 1
Base Table:
Where/Order By:
Field/Column Type Rqd? Default Validation QuickPick
N/AField 1 Char Yes Validated against Display MEANING

COLUMN_NAME <column> from <Application Short
from <table> Name>_LOOKUPS

Junely 104, 2005
Field/Column Type Rqd? Default Validation QuickPick
where <column> = where LOOKUP_TYPE =

<value> '<lookup type>
Zone 2
Base Table:
Where/Order By:
Field Type Rqd? Default Validation QuickPick

(
Field 1 Char No (QuickPick
COLUMN_NAME validation) D
i
s
p
l
a
y
M
E
A
N
I
N
G
from <Application Short

Name>_LOOKUPS
where LOOKUP_TYPE =
'<lookup type>
Special Logic
Zone 1
<Description of special zone-level logic (if any)>
Field Name
<Description of special field logic>
N/A
Calling Arguments
Default Data Sources

Table Column Source Value
N/A<table name> <column name <table>.<column>

column 2> 'Literal string'
<column 3> (Description of derived value)

Junely 104, 2005
Validation Logic
First Report:
Same as the Standard Oracle Report “PO Report.rdf”
Second Report:
None
Incompatibility
None
Performance Considerations
N/A
Other Considerations
Restart Strategy
N/A
Crash Recovery
N/A


MD.070 A E T D: USG PO Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MD.070 A E T D: USG PO Report

Uploaded by

Copyright:

Available Formats

AIM

Date Author Version Change Reference

10-June-2005 Bhavani Draft 1a No Previous Document

Copy No. Name Location

PO Report <Form Title> - Form Logic 4 of 7

PO Report <Form Title> - Form Logic 4 of 7

PO Report <Form Title> - Form Logic 4 of 7

User Will submit the PO Report from SRS window

POReport should be Executed internally.

Output should be generated in HTML Format

PO Report <Form Title> - Form Logic 4 of 7

Step 1: A Custom Oracle Report ‘USG_PO.rdf’ and Concurrent Program

RDF Should Contains the following Columns

Responsibility : Default Value should be from the Profile Option

Inventory Organization: Default Value should be from the Profile Option

Report will take Two Parameters

From Purchase Order No:

To Purchase Order No:

The PO Report’ Report Lay out is given below:

USG PO Report Report Date:

PONO Supplie SupplierSite Contact Buyer PO total Bill TO ShipTO Currency

PO Report <Form Title> - Form Logic 4 of 7

Step 2: The developed Custom report “USG_PO.rdf” and Concurrent Programs

PO Report’ includes the following reports:

Concurrent Progtam Name : USG Purchase Order Report

Executable Name :USGPO.rdf

Custom Path :USG_TOP\PO\11.5.0\Reports\US\

Request Group : All PO Reports

Responsibility :PO Users Responsibility

PO Report <Form Title> - Form Logic 4 of 7

<Form Title> - Form Logic

1. User enters Parameters in the First Concurrent Program SRS Window..

Block Relationship Diagram

Table and View Usage

Table Name Select Insert Update Delete Base Table

Zone and Field Summary

Field/Column Type Rqd? Default Validation QuickPick

N/AField 1 Char Yes Validated against Display MEANING

PO Report <Form Title> - Form Logic 4 of 7

Field/Column Type Rqd? Default Validation QuickPick

where <column> = where LOOKUP_TYPE =

Field Type Rqd? Default Validation QuickPick

from <Application Short

<Description of special zone-level logic (if any)>

<Description of special field logic>

Default Data Sources

N/A<table name> <column name <table>.<column>

PO Report <Form Title> - Form Logic 4 of 7

Same as the Standard Oracle Report “PO Report.rdf”

PO Report <Form Title> - Form Logic 4 of 7

You might also like