Application Customisation Technical Design...mtl_material_transactions) b1043627d1a648ae889a.doc...

Application Customisation Technical Design

AIM

Author: TCS

Creation Date: 20-Sep-2007

Last Updated: 13-Oct-2007

Document Ref: FDD_MD055 Pick Slip-Report_V1.4

Version: 1.0

Approvals

b1043627d1a648ae889a.doc

Name Position Signature DateApproved by:Approved by:

Page 1 of 28

Parkway Hospitals Singapore Pte Ltd.

Document Control

Change Record

Date Change Originator

Version Description of change

13-Oct-2007 TCS 1.0 Initial Version

Reviewed by

Date Name PositionReviewed by:Reviewed by:

Distribution

Copy No. Name Location

Related Documents

Document Reference Related Document Names

b1043627d1a648ae889a.doc Page 2 of 28


Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date

Impact Date

Closed Issues


ID Issue Resolution Responsibility Target Date

Impact Date


Contents

Application Customisation Technical Design............................................................................................1Document Control......................................................................................................................................2Issues for this Deliverable..........................................................................................................................3Contents..................................................................................................................................................... 4

Topical Essay..................................................................................................................................... 6

Basic Business Needs ................................................................................................................6Major Features............................................................................................................................ 6User Procedures.......................................................................................................................... 6Business Process......................................................................................................................... 6General........................................................................................................................................ 6Proposed Solution....................................................................................................................... 6Pre-Requisites and Dependencies............................................................................................... 6Assumptions ...............................................................................................................................6

Technical Overview........................................................................................................................... 7

Approach.....................................................................................................................................7Module List................................................................................................................................. 8

Module Logic .................................................................................................................................... 9

PH Delivery Slip Report (PHINVMTXR002)............................................................................9Concurrent ‘PH Delivery Slip Report’......................................................................................14Value Sets................................................................................................................................. 15Package .................................................................................................................................... 21Validation Logic....................................................................................................................... 21Table and View Usage.............................................................................................................. 21Incompatibility.......................................................................................................................... 22Performance Considerations..................................................................................................... 22Other Considerations.................................................................................................................22Shared Components.................................................................................................................. 22Alert conditions.........................................................................................................................22

Integration Issues..............................................................................................................................23

Changes Required..................................................................................................................... 23

Database Design...............................................................................................................................24

Desired Table Changes............................................................................................................. 24 NA..................................................................................................................................24Descriptive Flex fields.............................................................................................................. 24Grants/Synonyms...................................................................................................................... 24Data file.....................................................................................................................................24

Implementation Notes...................................................................................................................... 25

Design Summary.......................................................................................................................25Coding Summary...................................................................................................................... 25Testing Summary...................................................................................................................... 26Installation.................................................................................................................................26

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

Open Issues............................................................................................................................... 27



Closed Issues.............................................................................................................................27



Topical EssayThis custom report is to view all the transfer of items / material transactions of items between various subinventories of Inter Organization and within the organizations based on Parkway’s own format.

Basic Business Needs A Customized Delivery Slip report to view all the transactions of various subinventories of organization/organizations

Major Features• XML Publisher is used for generating the report details.

User Procedures NA

Business ProcessParkway will be able to view the customized Delivery Slip report details for all the material Transactions of InterOrganization and within Organization of various subinventories.

General

Proposed SolutionFor viewing the report details as per the requirement, XML report template is used.

Pre-Requisites and Dependencies• Needs to enable DFF in the “Transaction Types” Form. • This “PH Delivery (Pick) Slip report” is used in the “Automatic Material Top-Up”

Interface.

Assumptions The ‘PH Pick Slip Report’ concurrent program name was later changed as ‘PH Delivery Slip Report’.



Technical OverviewThis deliverable is to document the technical specifications for customization of Delivery Slip report in Parkway format to view all the transfer of items / material transactions between various subinventories with an organization and also for Inter Organization subinventory transfers. The header level information consists of E-Form Request number, Requester Name/ ID, Transaction number, transaction name, transaction date, Posted by/ID, Issue and receiving organization and Issue and receiving subinventory. For every header level information multiple line level information with requested quantity and issue quantity and variance in the quantity will be printed.

ApproachAs per Parkway requirement the ‘PH Delivery Slip Report’ will print the following details.

• Transaction Name

• Transaction Number

• Transaction Date

• E-Form Request ID

• Requestor Name, ID

• Posted By, ID

• Date and Time

• Issue Organization

• Issue SubInventory

• Receiving Organization

• Receiving SubInventory

• S No

• Item Code

• Description

• UOI

• Issue Qty

• Requested Qty

• Variance

While running the report, Parkway has provision to choose which fields to be viewed in the PH Delivery Slip Report.

For the report, XML Publisher report template is used.



Module List

Forms & PLL

None

Reports

PH Delivery Slip Report (PHINVMTXR002)

Concurrent Programs

PH Delivery Slip Report

Packages

NA



Module Logic

PH Delivery Slip Report (PHINVMTXR002)

The PH Delivery Slip Report is developed using XML Publisher template.

Report Parameters List of Input Parameters:

• P_TRANSACT_DATEFROM

• P_TRANSACT_DATETO

• P_TRANSACTION_NAME

• P_EFORM_REQUEST_ID

• P_SHIPMENT_NUMBER

• P_TRX_SETID

• P_SOURCE_ORGN_ID

• P_SOURCE_SUBINV_CODE

• P_TRNSF_ORGN_ID

• P_TRNSF_SUBINV

• P_ITEMFROM

• P_ITEMTO

• P_CONC_REQUEST_ID

Report Group and QueriesQ_transaction_date: This query is for retrieving the material transaction details to be printed in the report.

Groups: G_transaction_date G_TRX_QTY

Select StatementsQ_transaction_date:

SELECT rownum, a.* b1043627d1a648ae889a.doc Page 9 of 28


from (select distinct mmt.transaction_date,

mtt.transaction_type_name,

mmt.transaction_set_ID, mmt.transaction_ID,

nvl(mmt.shipment_number, mmt.transaction_set_ID) "transaction_number",

-- mp1.organization_code "src_org_code",

mmt.organization_id "src_org_id",

mmt.subinventory_code "src_subinv_code",

mmt.transfer_organization_id "dest_org_id",

mmt.transfer_subinventory "dest_subinv_code",

mmt.inventory_item_id,

msi.segment1 "Item",

msi.description "ITEM_DESC",

msi.attribute9 "BIN_NO",

abs(mmt.transaction_quantity) "TRX_QTY",

mmt.transaction_uom,

round( mmt.actual_cost, 4) "ACTUAL_COST",

round( round(mmt.actual_cost,4)*abs(mmt.transaction_quantity),4) "total_value",

to_char(sysdate, 'DD-MON-YYYY - HH:MM:SS:AM') "DATE",

mmd.request_number "e-form_id",

mmt.attribute6 "requested_qty" ,

nvl(mmt.attribute6-abs(mmt.transaction_quantity),0) "variance",

mmt.attribute7 "REQUESTED_BY" ,

mmt.created_by "POSTED_BY_ID"

FROM

mtl_material_transactions mmt,

mtl_transaction_types mtt,

mtl_parameters mp1,

mtl_system_items_b msi,

-- mtl_secondary_inventories msiin1,

mtl_parameters mp2,

mtl_material_transactions_dfv mmd

WHERE

mtt.transaction_type_id = mmt.transaction_type_id



-- and mmt.transaction_set_ID = nvl(to_number(:P_TRANSACTION_NUM), mmt.transaction_set_ID)

and trunc(mmt.transaction_date) between nvl(trunc(to_date(:P_TRANSACT_DATEFROM)),trunc(mmt.transaction_date))

and nvl(trunc(to_date(:P_TRANSACT_DATETO)),trunc(mmt.transaction_date))

and mtt.transaction_type_name= nvl(:P_TRANSACTION_NAME, mtt.transaction_type_name)

and mmt.organization_id = mp1.organization_id (+)

and nvl(to_number(:p_source_orgn_id), mp1.organization_id) = mmt.organization_id--(+)

and mmt.subinventory_code = nvl(:p_source_subinv_code, mmt.subinventory_code)

and msi.organization_id = mmt.organization_id

and msi.organization_id = mp1.organization_id

and msi.inventory_item_id = mmt.inventory_item_id

and msi.segment1

between nvl(:P_ITEMFROM, msi.segment1)

AND nvl(:P_ITEMTO,msi.segment1)

--and mca.category_set_id = mic.category_set_id

-- and nvl(:p_trnsf_orgn_id, mp2.organization_id) = mmt.transfer_organization_id(+)

and nvl(mmt.transfer_organization_id,-1) = nvl(nvl(:p_trnsf_orgn_id,mmt.transfer_organization_id),-1)

and nvl(mmt.transfer_subinventory,-1) = nvl(nvl(:p_trnsf_subinv,mmt.transfer_subinventory),-1)

-- and msiin1.secondary_inventory_name(+)= nvl(:p_trnsf_subinv,mmt.transfer_subinventory)

and mmd.rowid= mmt.rowid

-- and mmd.request_number = nvl('&p_eformreq_id',mmt.attribute2(+) )

and nvl(mmt.attribute2,-1) = nvl(nvl(:P_EFORM_REQUEST_ID,mmt.attribute2),-1)

--and nvl(mmt.request_id ,-1) = nvl(nvl(:P_CONC_REQUESTID,mmt.request_id),-1)

and nvl(mmt.transaction_set_ID ,-1) = nvl(nvl(:P_TRX_SETID,mmt.transaction_set_ID),-1)

and nvl(mmt.shipment_number ,-1) = nvl(nvl(:P_SHIPMENT_NUMBER,mmt.SHIPMENT_NUMBER),-1)

order by 3,4,1,2) a



Report FramesNA.

Display Fields

Totals/Sub Totals NA

ValidationsThese validations are included in this report

• Formula columns –

o CF_DEST_ORG_CODE


Data Model Field Name Display Column Name

TRANSACTION_TYPE_NAME TRANSACTION_TYPE_NAME

TRANSACTION_NUMBER TRANSACTION_NUMBER

TRANSACTION_DATE TRANSACTION_DATE

DATE DATE

ORGANIZATION_ID CF_SRC_ORG_CODE

SUBINVENTORY_CODE SRC_SUBINV_CODE

TRANSFER_ORGANIZATION_ID CF_DEST_ORG_CODE

TRANSFER_SUBINVENTORY_CODE

DEST_SUBINV_CODE

ATTRIBUTE2 REQUEST NO

CS_SUMSNO SNO

SEGMENT1 ITEM_CODE

ITEM_DESCRIPTION ITEM_DESC

TRANSACTION_UOM UOI

TRANSACTION_QUANTITY TRX_QTY

ATTRIBUTE6 REQUESTED_QTY

VARIANCE VARIANCE

ATTRIBUTE7 POSTED BY, ID

CREATED_BY REQUEDTED BY, ID


o CF_SRC_ORG_CODE

o CF_SNO

• Summary columns –

o CS_SUMSNO

TriggersTriggers used in the report

• BEFORE REPORT

function BeforeReport return Boolean is

BEGIN

SRW.USER_EXIT('FND SRWINIT');

return (TRUE);

END;

• AFTER REPORT

function AfterReport return boolean is

BEGIN

SRW.USER_EXIT('FND SRWEXIT');

return (TRUE);

END;

Header and Footer Specs• Data to be displayed on the Header

‘Delivery Slip’

• Data to be displayed on the footer.

Resetting of Page number for each delivery slip.



order by prh.segment1

Concurrent ‘PH Delivery Slip Report’For viewing the PH Delivery Slip Report in Oracle, in the PHSPL PCS Inventory User responsibility, Parkway has to run the concurrent ‘PH Delivery Slip Report’. The Concurrent input parameters are:

• Transaction Date

• Transaction Date To

• Transaction

• E-Form Request ID

• Shipment Number

• Transaction Number

• Issue Organization

• Issue SubInventory

• Receiving Organization

• Receiving Subinventory

• Items From

• Items To

Based on the input parameters the selected fields are to be displayed. The concurrent request generates the ‘PH Delivery Slip Report’.

The Concurrent Layout is as shown below.



Value Sets

Value Set Size Type Rqd Validation/Values

PH_INVR_TRANS_DATE_FROM

20 Char No Select v.transaction_date from (select distinct trunc(transaction_date) transaction_date from MTL_MATERIAL_TRANSACTIONS) vorder by 1

PHINVR_TRANSACTION 80 Char NO Select mtt.TRANSACTION_TYPE_NAME , mtt.DESCRIPTION , mtt.TRANSACTION_TYPE_NAME from mtl_transaction_types mtt,mtl_transaction_types_dfv mttd Where mtt.rowid=mttd.rowid and (mttd.pick_slip_show_flag in ('Y') )order by 1

PH_EFORM_REQUEST_ID 30 Char No Select mmt.attribute2 from (select distinct attribute2 from mtl_material_transactions) mmt where mmt.attribute2 in (select distinct mmt.attribute2 from mtl_material_transactions mmt , mtl_transaction_types mtt wheremmt.transaction_type_id=mtt.transaction_type_idand mtt.transaction_type_name=nvl(:$FLEX$.PHINVR_TRANSACTION:NULL,mtt.transaction_type_name)and mmt.attribute2 is not null)order by 1




PHINVR_SHIPMENT_NUMBER

30 Char NO Select mmt.shipment_number, mmt.shipment_numberFrom (select distinct shipment_number from mtl_material_transactions) mmt WHEREmmt.shipment_number in (select distinct mmt.shipment_number from mtl_material_transactions mmt , mtl_transaction_types mtt wheremmt.transaction_type_id=mtt.transaction_type_idand mtt.transaction_type_name=nvl(:$FLEX$.PHINVR_TRANSACTION:NULL,mtt.transaction_type_name)and mmt.attribute2 = nvl(:$FLEX$.PH_EFORM_REQUEST_ID:NULL,mmt.attribute2)and mmt.shipment_number is not null)order by 1




PHINVR_TRANS_ID 22 Number

No Select t.transaction_set_id, t.transaction_set_id from (select distinct transaction_set_id , transaction_type_id from MTL_MATERIAL_TRANSACTIONS) t WHERE where t.transaction_type_id in (select distinct transaction_type_id from mtl_transaction_types where transaction_type_name = nvl(:$FLEX$.PHINVR_TRANSACTION:NULL, transaction_type_name))AND (:$FLEX$.PHINVR_SHIPMENT_NUMBER:NULL is null AND :$FLEX$.PH_EFORM_REQUEST_ID:NULL is NULL)order by t.transaction_set_id

PHINVR_SRC_ORGN 20 Char No SELECT organization_code, organization_id FROM mtl_parameters WHERE organization_id in(select distinct organization_id from mtl_material_transactions)




PHINVR_SRC_SUBINV 10 Char No SELECT secondary_inventory_name, secondary_inventory_name FROM mtl_secondary_inventories WHERE organization_id in(select organization_id from mtl_material_transactions where organization_id in (nvl(:$FLEX$.PHINVR_SRC_ORGN:NULL, organization_id)))and secondary_inventory_name in (select distinct subinventory_code from mtl_material_transactions where organization_id in(nvl(:$FLEX$.PHINVR_SRC_ORGN:NULL, organization_id)))and nvl(disable_date, sysdate+1) > sysdate

PHINVR_DEST_ORGN 20 Char No SELECT organization_code, organization_id FROM mtl_parameters WHERE organization_id in(select distinct transfer_organization_id from mtl_material_transactions)




PHINVR_DEST_SUBINV 10 Char No SELECT secondary_inventory_name, secondary_inventory_name FROM mtl_secondary_inventories WHERE organization_id in(select organization_id from mtl_material_transactions where organization_id in (nvl(:$FLEX$.PHINVR_SRC_ORGN:NULL, organization_id)))and secondary_inventory_name in (select distinct subinventory_code from mtl_material_transactions where organization_id in(nvl(:$FLEX$.PHINVR_SRC_ORGN:NULL, organization_id)))and nvl(disable_date, sysdate+1) > sysdate

PH_INVR_ITEM_FROM 40 Char No (select distinct segment1 from MTL_SYSTEM_ITEMS_B) V where v.segment1 in (select distinct segment1 from mtl_system_items_b where stock_enabled_flag='Y' and mtl_transactions_enabled_flag='Y' and upper(inventory_item_status_code)='ACTIVE')order by v.segment1



Concurrent Executables

Executable Short Name Application Description Execution Method

Execution File Name

PHINVMPHINVMTXR002

PHINVMTXR002

Parkway Customization

Custom Delivery Slip Report for Parkway

Oracle Reports PHINVMTXR002

Concurrent Programs

Program Short Name

Application Description Executable Name Executable Method

PH Delivery Slip Report

PHINVMTXR002

Parkway Customization

Custom Report for all Material Transactions

PHINVMTXR002 Oracle Reports

Seq Parameter Description Value Set Default Type Default Value

Required

Prompt

20 p_transaction_date

Transaction date From


No Transaction Date From

30 p_transaction_date_to

Transaction date To


No To

40 p_transaction_name

Transaction Type name

PHINVR_TRANSACTION

No Transaction

50 p_e-form_request_id

E-form Request ID

PH_EFORM_REQUEST_ID

No E-Form Request Id

55 p_shipment_number

Shipment Number

PHINVR_SHIPMENT_NUMBER

No Shipment Number

60 p_transaction_id

Transaction number

PHINVR_TRANS_ID

No Transaction Number

70 p_source_organization

Source Organization Code

PHINVR_SRC_ORGN

No Receiving Organization



Program Short Name

Application Description Executable Name Executable Method

80 p_source_subinventory

Source Subinventory

PHINVR_SRC_SUBINV

No Receiving Subinventory

90 p_dest_organization

Destination Organization

PHINVR_DEST_ORGN

No Issue Organization

100 p_source_organization

Destination Subinventory

PHINVR_DEST_SUBINV

No Issue Subinventory

Seq Parameter Description Value Set Default Type Default Value

Required

Prompt

110 p_item_from

Items From PH_INVR_ITEM_FROM

No Items From

120 p_item_to Items To PH_INVR_ITEM_FROM

No To

170 p_conc_request_id

Concurrent Request ID

15 Digit Number

No Concurrent request Id

Concurrent MessagesNA

Package NA

Validation Logic

Error Conditions:

Specify the types of errors that may occur while running the program

Error Number Error Description

Table and View UsageNone



IncompatibilityNone

Performance Considerations

Other Considerations

Restart Strategy

NA

Crash Recovery

NA

Shared ComponentsNA

Alert conditionsNA



Integration Issues

Changes Required

Within Product

NA

Other Products

NA



Database DesignNA

Desired Table Changes NA

Descriptive Flex fieldsApplication: Inventory

DFF Title: Transaction types

Grants/Synonyms NA

Data fileNA



Implementation NotesThis document describes exactly how the application is developed and implemented

Design Summary

Functional Design

FDD_MD055 Delivery Slip-Report_V1.4

Functional Design Approval

Technical Design

TDD_INV_PH Delivery(Pick) Slip Report V.1.0

Design Review

Final Acceptance

Coding SummarySpecify the summary of program files

Program Files

The files required for this customization are as follows:


File Description Coded By

PHINVMTXR002.rtf Report Template TCSPHINVMTXR002.rdf Report file TCSSet_up Document for Delivery(Pick)Slip Report.doc

Set up document for server side component details.

TCS


Testing SummaryThe customizations were tested in CRP test environment before being moved to production.

InstallationFollowing files needed for the PH Delivery Slip Report Customization:

• Concurrent_Details.doc

• PHINVMTXR002.rtf

• PHINVMTXR002.rdf



Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date




Date post:	24-Jan-2021
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times