AIM

MD.050 APPLICATION EXTENSIONS FUNCTIONAL DESIGN NMC

Creation Date: Last Updated: Document Ref: Version: 1.0 June 21, 2012 June 21, 2012

Approvals:

Mr. Godly Sam Mr. Vijay Todkar

MD.050 Application Extensions Functional Design

Doc Ref: 1

Document Control
Change Record
3

Date

Author

Versio n 1.0

Change Reference

No Previous Document

Reviewers

Name

Position

Distribution

Copy No. 1 2 3 4

Name Library Master

Location Project Library Project Manager

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.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Table of Contents

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Topical Essay
For Sales order Invoices Where We get the invoices from one operating unit and They are transferring these invoices to another operating unit. One Report is required same as NMC Sales Invoice Trading (Discount) which has to print changed Address Where we are entering this new address in form based on the invoice number.

Basic Business Needs

The Business wishes to track the following: Need one Form to capture the new address for a particular invoice number Reports for these invoices.

Reports: Based on templates shared by business, reports will be developed to track business transactions and events. Report output would be based on system configuration, transaction data stored in system over period of time and the parameters entered for executing the report.

Custom Forms: These are screens built based on user inputs, which the user uses for entering and reviewing business transaction details which are not supported directly in standard Oracle applications.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Solution Design

Sales Invoices User Input

Contain s Original Address

Alternat e Address

Custom table Keeps track of both original Address and Alternate Address

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Detailed Design
Custom table information Table Name is XXNMC_INSTITUTIONAL_DETAILS COLUMN NAMES ORIGINAL_TRX_NUMBER ORIGINAL_CUST_PO_NUMBER ORIGINAL_TRX_DATE ORGINAL_ORDER_NUMBER ORIGINAL _PARTY_TYPE ORIGINAL _PARTY_NAME ORIGINAL _PERSON_FIRST_NAME ORIGINAL _PERSON_MIDDLE_NAME ORIGINAL _PERSON_LAST_NAME ORIGINAL_ADDRESS1 ORIGINAL_ADDRESS2 ORIGINAL_ADDRESS3 ORIGINAL_ADDRESS4 ORIGINAL_CITY ALTERNATE_ADDRESS1 ALTERNATE_ADDRESS2 ALTERNATE_ADDRESS3 ALTERNATE_ADDRESS4 ALTERNATE_CITY CREATED_BY CREATION_DATE LAST_UPDATED_BY LAST_UPDATE_DATE LAST_UPDATE_LOGIN DESCRIPTION Invoice number Purchase Order Number Creation Date From Wsh_Delivery_Details Table ORDER NUMBER FROM OE_ORDER_HEADERS_ALL Organization or person From HZ_PARTIES Table Party Name From HZ_PARTIES Table First Name From HZ_PARTIES Table Middle Name From HZ_PARTIES Table Last Name From HZ_PARTIES Table Adress1 From HZ_LOCATIONS Table Adress2 From HZ_LOCATIONS Table Adress3 From HZ_LOCATIONS Table Adress4 From HZ_LOCATIONS Table City From HZ_LOCATIONS Table User Will Enter User Will Enter User Will Enter User Will Enter User Will Enter WHO Column WHO Column WHO Column WHO Column WHO Column

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Assumptions
The following will be assumed in conjunction with this document: The master information like Bank, facility details and respective limit will be updated by user manually in the Bank master and in custom forms. Transaction Data will be populated based on information entered in AP Invoices and AP Payments, Miscellaneous Receipts. Utilization of limit, availability and notification will work based on the transactional data entered as mentioned in the previous step.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Business Rules
This design assumes that the following statements are true: Bank Master is populated in Oracle Accounts Payable Facility-wise master information are updated by user in custom forms Prepayment Invoices would be used for recording the LC details. Trust Receipt / Term Loans will be created as payment methods in Oracle Accounts Payable Receivable activity will be defined for Term Loans and used in Miscellaneous Receipt for Term Loan which is not availed for paying off LC.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Business Process Master Creation

Bank:
All Bank accounts will be created in Oracle Payables. The banks created in Accounts Payable will be available as an LOV, in Custom form to define different facilities extended by respective bank.

Facility:
For each bank, user can define multiple facilities. The facility names viz. Letter of Credit, Trust Receipt, Term Loan, Over Draft, Bank Guarantee will be defined in Lookup window so that the same can be used in multiple windows of Oracle Payables and custom forms. Four level Facilities structure will be defined for each bank to track limit, calculate utilization and availability. The Facility structure will be as follows: Level 1: Bank Limit (Sum of all facility Limits extended by the Bank) Level 2: Facility Limit Level 3: Sub Limit for the facility Level 4: Limit within Sub Limit Example for facility structure: Level 1: Bank Limit NBD Level 2: Facility Limit - Letter of Credit Level 2: Facility Limit Trust Receipt Level 3: Sub Limit for the facility LC limit for Local Purchase Level 4: Limit within Sub Limit Local Purchase from Jumbo = 500 = 300 = 200 = 100 = 50

Utilization will be updated at the lowest level as defined in the facility Master based on business transactions Availability will be calculated in descending order from the lowest level (Level 4) with cross validation at each level, up to the highest level (Level 1). Note: Utilization and Availability will be recalculated at each level on creation of new transaction, deletion of a transaction. Payment of the transaction and expiry of the transaction Following Alerts / Notifications will be triggered:

Facility-wise Limits reaching respective threshold at each level Expiry / Due of transaction Availability of other facilities on expiry of a transaction Example, 5 Days before acceptance due
date of an LC issued earlier the balance available against Trust receipt and term Loan for a Bank
File Ref: 101111008.doc Form Design Topical Essay 6

Company Confidential - For internal use only

MD.050 Application Extensions Functional Design

Doc Ref: 1

Reports:
Reports based on templates shared by business. NOTE: The effective Bank-wise / Facility-wise master information will be updated by business on a regular basis when bank revises the limits extended to NMC for each facility. The Following information will be entered by user in the Facility Master and update as and when required, all amounts at the master level will be entered and maintained in functional currency (AED): Only utilized amount fields at the master level will be based on the exchange rate applied for the transactions, all other amount fields will be based on the exchange rate applicable on the from date of the period range mentioned at the bank level.

Bank
Overall Limit extended by the bank will be entered Facilities availed from the bank will be entered Effective Periods Utilization of Overall Limit will be a calculated value based on the system data at each facility level Balance will be a calculated as a difference between limit and utilization.

Letter of Credit
Limit extended by bank for LC Sub-limits fixed by bank - user will enter sub-limit category (E.g. Supplier), Name (E.g. Supplier Name) of sub-limit and amount Limit within sub-limit if any, user will enter Name of sub-limit and amount Effective Periods will be entered by user. Facility utilization at each level will be calculated based on the system data. Balance at each level will be a calculated as a difference between limit and utilization.

Trust Receipt
Limit extended by bank for Trust Receipt Sub-limits fixed by bank - user will enter sub-limit category (E.g. Supplier), Name (E.g. Supplier Name) of sub-limit and amount Limit within sub-limit if any, user will enter Name of sub-limit and amount Effective Periods will be entered by user. Facility utilization at each level will be calculated based on the system data. Balance at each level will be a calculated as a difference between limit and utilization. Rate of interest charged by bank for Trust Receipt for the effective period

Term Loan
File Ref: 101111008.doc Form Design Topical Essay 6

Company Confidential - For internal use only

MD.050 Application Extensions Functional Design

Doc Ref: 1

Limit extended by bank for Term Loan Name) of sub-limit and amount Limit within sub-limit if any, user will enter Name of sub-limit and amount Effective Periods will be entered by user. Facility utilization at each level will be calculated based on the system data. Balance at each level will be a calculated as a difference between limit and utilization. Rate of interest charged by bank for Term Loan for the effective period

Sub-limits fixed by bank - user will enter sub-limit category (E.g. Supplier), Name (E.g. Supplier

Over Draft

Limit extended by bank for Over Draft. Sub-limit if any, user will enter Name of sub-limit and amount Effective Periods will be entered by user. Rate of interest charged by bank for Over Draft for the effective period Neither Utilization nor other transactional information will be tracked in the custom application.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

Business Process Transaction Data

Letter of credit
All process pertaining to opening of LC will be done outside oracle applications and on opening the LC Against a supplier, user will enter the following information in Oracle Accounts Payable Prepayment Invoice: 1. LC No# 2. Amendment / Revision # 3. LC Currency 4. LC Open Date 5. LC Expiry Date 6. LC Amount 7. Payment Terms 8. Acceptance Date 9. Acceptance Due Date 10. Acceptance Amount 11. Beneficiary / Supplier 12. Negotiating Bank 13. Supplier Invoice Number 14. PO Number The prepayment invoice will be created and saved. On acceptance due date the Prepayment invoice will be accounted in accounts payable. Based on the Payment mode the LC will be paid off and accounted in accounts payable. The prepayment invoice will be applied against invoice created based on Goods received. Letter of Credit with multiple shipments Single Letter of credit opened against supplier for multiple shipments the details will be entered as follows: Prepayment Invoice will be created initially for the LC amount and other details entered as explained above except the acceptance details. On first shipment and acceptance the prepayment invoice created in the previous step will be revised to the acceptance amount and acceptance details will be entered. For subsequent shipments additional prepayment invoices will be created and acceptance details will be entered in reference to the original LC. All other process would be the same as explained in Letter of Credit process.

Trust Receipt
The process of availing the trust receipt facility from the bank will be done outside Oracle Applications. On availing the facility the details of the same will be entered in Oracle Payables as follows: When the LC is paid off through a trust receipt, the payment mode will be selected as Trust Receipt in the prepayment invoice which was used to enter the LC details. In payment workbench Trust Receipt would be used as the payment method to enter and account the Trust Receipt details. The following Trust Receipt details will be entered while creating the payment voucher: 1. Trust Receipt No# 2. Extension / Revision # 3. Payment Terms 4. Trust Receipt Date 5. Trust Receipt Due Date 6. Trust Receipt Amount 7. Rate of Interest for Trust Receipt
File Ref: 101111008.doc Form Design Company Confidential - For internal use only Topical Essay 6

MD.050 Application Extensions Functional Design

Doc Ref: 1

8. Bank Charges
Following information will be picked from the LC Prepayment Invoice created and accounted earlier: 9. LC Reference 10. Beneficiary / Supplier 11. Supplier Invoice Number 12. PO Number Paying off Trust Receipt: On the due date of Trust Receipt the same will be settled by creating an invoice and payment in Accounts Payables.

Term Loan
The process of availing Term Loan facility from the bank will be done outside Oracle Applications. When a Term Loan is availed for paying off LC then a Payment would be created in Payment workbench with Term Loan as Payment Method to account the liability. If the Term Loan is availed for not paying off other Bank Facilities then the same would be entered and accounted by creating as a Miscellaneous Receipt in Accounts Receivable. The following information will be entered in both the Term Loan scenarios by the user: 1. Term Loan No# 2. Extension / Revision # 3. Term Loan Revised Expiry Date 4. First EMI Due Date 5. Last EMI Due Date 6. Rate of Interest for Term Loan 7. Bank Charges 8. EMI 9. Monthly EMI payment due date 10. Number of Installments Following information will be picked from the LC Prepayment Invoice created and accounted earlier: 11. LC Reference 12. Beneficiary / Supplier 13. Supplier Invoice Number 14. PO Number Repayment The payment of monthly installments will be entered as Accounts Payable invoices with following details: 15. Term Loan Number # 16. Principal amount repaid in EMI 17. Interest Portion paid in EMI 18. EMI Number# The invoice created for repayment will be paid off by creating a payment in Accounts Payable workbench.

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay

MD.050 Application Extensions Functional Design

Doc Ref: 1

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

File Ref: 101111008.doc Form Design

Company Confidential - For internal use only

Topical Essay