MD50 - Sales Order Invoice for Another OU

AIM

MD.050 APPLICATION EXTENSIONS FUNCTIONAL DESIGN NMC Creat reatio ion n Date:

Jun June 21 21, 2 20 012

Last Updated:

June 21, 2012

Document Ref: Version:

1.0

Approvals:

Mr. Godly Sam Mr. Vijay Todkar

Titles you can't find anywhere else

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.







Doc Ref:

MD.050 Application Extensions Functional Design

1

Document Control Change Record 3

Date

Author

Versio n

Change Reference

1.0

No Previous Document

Reviewers

Name

Position

Distribution

Copy No.

Name

Location

1 2 3 4

Library Master

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.








Doc Ref: 1

Table of Contents








Doc Ref: 1

Topical Essay For Sales order Invoices Where We get the invoices from one operating unit and They are transferring transferring these invoices invoices to another another operating 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 Business wishes to track track the followin following: g: 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.







Doc Ref:


1

Solution Design

Sales Invoices

Contain s Original

User Input

Alternat e Address

Address

Custom table Keeps track of both original Address Address and Alternate Address







Doc Ref:


1

Detailed Design ∙ Custom table information Table Name is

“XXNMC_INSTITUTIONAL_DETAILS ”

COLUMN NAME’S

DESCRIPTION

ORIGINAL_TRX_NUMBER ORIGINAL_TRX_NUMBER ORIGINAL_CUST_PO_NUMBER ORIGINAL_CUST_PO_NUMBER ORIGINAL_TRX_DATE ORIGINAL_TRX_DATE ORGINAL_ORDER_NUMBER ORIGINAL _PARTY_TYPE _PARTY_TYPE ORIGINAL _PARTY_NAME _PARTY_NAME ORIGINAL _PERSON_FIRST_NAME _PERSON_FIRST_NAME ORIGIN ORIGINAL AL _PERSO _PERSON_M N_MIDD IDDLE_ LE_NAM NAME E ORIGINAL _PERSON_LAST_NAME _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_ DATE LAST_UPDATE_LOGIN LAST_UPDATE_ LOGIN

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 Middle Name Name From From “HZ_PA “HZ_PART RTIES IES”” Tabl Tablee Last Name From “HZ_PARTIES” Table Adress1 From “ HZ_LOCATIONS ” Ta Table Adress2 From “ HZ_LOCATIONS ” Ta T able Adress3 From “ HZ_LOCATIONS ” Ta T able Adress4 From “ HZ_LOCATIONS ” Ta T able 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










Doc Ref: 1

Assumptions The followin following g will be be assumed assumed in conjunction conjunction with with this document: document: The master master informat information ion like like Bank, facility details and respective respective limit will will be updated by user manually in the Bank master and in custom forms. Transaction Transaction Data will be populated populated based based on information information entered 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.







Doc Ref:


1

Business Rules This design design assumes assumes that the the following following stateme statements nts are 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 payment methods 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.







Doc Ref:


1

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

Facility: For each bank, user can define multiple facilities. The facility facility names names viz. Letter Letter of Credit, Trust Receipt, Receipt, Term Loan, Loan, Over Over Draft, Draft, Bank Guarantee Guarantee will 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 Facility structu structure re will be be as follows 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

= 50’0 = 30’0 = 20’0

Level 3: Sub Limit for the facility –LC limit for Local Purchase

= 10’0

Level 4: Limit within Sub Limit – Local Purchase from Jumbo

= 5’0

Utilization will be updated at the lowest level as defined in the facility Master based on business transactions








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 Followin Following g information information will be entered by user in the Facility Facility Master Master and update update as and when 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.

• •








Doc Ref: 1

•

•

• • • • •

Limit extended by bank for Term Loan 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 Term Loan for the effective period

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.










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. Amen Amendme dment nt / Revi Revisi sion on # 3. LC Curr Curre ency 4. LC Open Date 5. LC Expi Expiry ry Date Date 6. LC Amount 7. Paym Paymen entt Ter Term ms 8. Acce Accept ptan ance ce Date Date 9. Acce Accept ptan ance ce Due Due Dat Date e 10. Acceptance Acceptance Amount Amount 11. Beneficiary Beneficiary / Supplier Supplier 12. Negotiating Negotiating Bank 13. Supplier Invoice Invoice Number Number 14. PO Number Number

The prepaymen prepaymentt invoice invoice will will be created created and saved. 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 prepaymen prepaymentt invoice invoice will will be applied applied against against invoice created based on Goods Goods received. received.

Letter of Credit with multiple shipments Single Letter of credit opened against supplier for multiple shipments the details will be entered as follows: •








Doc Ref: 1

8. Bank Charges Following information will be picked from the LC Prepayment Invoice created and accounted earlier: 9. LC Refer efere ence 10. Beneficiary Beneficiary / Supplier Supplier 11. Supplier Invoice Invoice Number Number 12. PO Number 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 process of availing availing Term Term Loan Loan facility facility from from the bank will will be done done outside outside Oracle Oracle Applicati Applications. ons. 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 followin following g information information will be entered in both the Term Term Loan Loan scenarios scenarios by the user: user: 1. Term Term Loan Loan No# No# 2. Extens Extensio ion n / Revis Revisio ion n# 3. Term Loan Revise Revised d Expiry Expiry Date Date 4. First EMI Due Date 5. Last Last EMI EMI Due Due Date Date 6. Rate of Interest for Term Loan 7. Bank ank Ch Charges ges 8. EMI 9. Monthly EMI payment due date 10. Number of of Installm







Doc Ref:


1

Open and Closed Issues for this Deliverable Open Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Responsibility

Target Date

Impact Date

Closed Issues

ID

Issue

Resolution

MD50 - Sales Order Invoice for Another OU

Recommend Documents