You are on page 1of 12

MD.

050 APPLICATION
EXTENSIONS FUNCTIONAL
DESIGN
Oracle ERP ACE GROUP
Author

Hussainaiah Bodisetty

Creation Date

Sep 23rd , 2013

Last Updated

Sep 23rd , 2013

Document Ref

MD050 ACE_ERP-Integration_Ver 1.2

Version

3.0

Submitted to
By

Document Control
Distribution
Copy
No.

Name

Location

1
2

Mr. Srinivasa Raghavan


Mr. Aamir Nassim

Project manager-Wipro
Project manager-ACE

Change Record3
Date

Author

Version

Change Reference

24-SEP-13

Hussainaiah Bodisetty

Initial
Draft

Date

Name

Position

24-SEP13
24-SEP13

Mr. Srinivasa Raghavan

Project Manager-Wipro

Mr. Aamir Nassim

Project Manager-ACE

Reviewers
Signature

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.

Contents

Document Control.......................................................................................ii
Topical Essay.............................................................................................. 4
Basic Business Needs............................................................................4
Customer Transactions...............................................................................8
Supplier Transactions...............................................................................10
Open and Closed Issues for this Deliverable.............................................12
Open Issues......................................................................................... 12
Closed Issues.......................................................................................12

Topical Essay
This document describes the modifications of existing integration
between Siebel and Oracle Applications (Accounts Payables & Accounts
Receivables).

The Integration between oracle and Siebel designed by using integrated


WSDL methods. After providing the required data based on Business
Validations in Siebel system, Siebel will invoke the Oracle Customized web
services. During this process data will be differentiated and populates in
respective modules staging tables and in same flow related customized
Work Flow packages will be called and transactions will be created
accordingly .

Basic Business Needs


The Insurance policies and Claims will be created in Oracle Siebel for all
Insurance Customers and Suppliers. Same information will be flow to
Oracle Finance system that is Oracle receivables and Oracle payables
Modules through Web services.
Current Scenario for the Claim Transactions for Customer and Insurance
Supplier :
During Customer Account creation Oracle will create Customer and
Supplier under same party by storing the Siebel Customer number as a
reference in the KNOWN_AS column of HZ_PARTIES table.
Whenever customer claim transactions are flowing from Siebel Oracle is
creating Customer Claim transactions in the Payables and Insurance
Supplier transactions are creating in Receivables respectively.
With current Functionality ACE Finance team is facing difficulties while
making Receipts and Payments using with Std. Functionality of AP/AR
netting .
Current scenario example :

Custome
r
Desc
Policy amount( Invoice
Customer)
Commission
Invoice to Insurer
Claim (CreditNote Customer)
Debit Note for Insurer

ABC

Broking
ACE
Riyadh

Insurance
Supplier/
Under writer

Transaction
Type

SAICO

AP/AR

1000
-100
900
100
100
4

AR
AP
AP
AP
AR

Refer below touch points for current flow of Siebel to Oracle Transactions:

LOOKUP_CO
DE
MEANING
1 Invoice Insurer
2 Invoice Customer
Invoice Broker
3 Details
4 CreditNote Insurer
CreditNote
5 Customer
6 CreditNote Broker
7 Account Receipts
Claim Receipts
8 Details
Credit Note for
9 Insurer
Credit Note for
10 Claimant
Debit Note for
11 Insurer
Debit Note for
12 Claimant
13 Account Details

DESCRIPTION
Invoice Insurer
Invoice Customer
Invoice Broker
Details
CreditNote Insurer
CreditNote
Customer
CreditNote Broker
Account Receipts
Claim Receipts
Details
Credit Note for
Insurer
Credit Note for
Claimant
Debit Note for
Insurer
Debit Note for
Claimant
Account Details

AR
Y
Y

AP

Y
Y

N/A

Y
Y
N/A

N/A

N/A
Y
Y

Y
Y
Y

N/A

Expected Scenario for the Claim Transactions for Customer and Insurance
Supplier :
To overcome few of the difficulties Integration design need be changed
accordingly as follows.
All Customer Claim transactions related transactions should flow to
Account Receivable module as a Credit Memos and All Insurer claim
related transactions should flow to Account Payables as a Credit Memos

Expected Scenario with example.

Custome
r
Desc
Policy amount( Invoice
Customer)
Commission
Invoice to Insurer
Claim (CreditNote

ABC

Brokin
g
ACE
Riyadh

Insurance
Supplier/
Under writer

Transaction
Type

SAICO

AP/AR

1000
-100
900
-100

AR
AP
AP
AR Credit

Customer)
Debit Note for Insurer

-100

Expected touch points of Siebel to Oracle Transactions:

LOOKUP_CO
DE
MEANING
1 Invoice Insurer
2 Invoice Customer
Invoice Broker
3 Details
4 CreditNote Insurer
CreditNote
5 Customer
6 CreditNote Broker
7 Account Receipts
Claim Receipts
8 Details
Credit Note for
9 Insurer
Credit Note for
10 Claimant
Debit Note for
11 Insurer
Debit Note for
12 Claimant
13 Account Details

DESCRIPTION
Invoice Insurer
Invoice Customer
Invoice Broker
Details
CreditNote Insurer
CreditNote
Customer
CreditNote Broker
Account Receipts
Claim Receipts
Details
Credit Note for
Insurer
Credit Note for
Claimant
Debit Note for
Insurer
Debit Note for
Claimant
Account Details

AR
Y
Y

AP

Y
Y
Y
N/A

N
Y
N/A

N/A

N/A
Y
Y

Y
Y

N/A

Memo
AP Credit
Memo

Customer Transactions

Invoice for Policy created in Siebel comes from Siebel to Oracle AR. Refund and cancellation of Invoice
as Credit Note in AR.
Balance payable or receivable from a party will be settled either by payment through AP or receipt in
AR. For example, if there is a liability that needs to be paid to a party after netting the transactions,
then AR invoices needs to be closed by passing a Credit Memo in AR. When user creates a credit
memo in AR system should automatically create same invoice in AP to reduce the liability amount and
vice versa. This process needs to be automated.

Debit note for excess/depreciation are created in Siebel comes from Siebel to Oracle AR. Credit Note
for Customer Claims and reversal of claims.

Invoice / debit notes generated at Siebel and moved to Financials should not be editable / deleted by
any user.

Customer Debit transactions will be created in AR as Invoice/Debit note and Credit transactions will
be created in AR as Credit note.

Customer payments will be handled by manually creating credit notes in AP and payments made from
AP One specific AP invoice type should be available when that specific types of AP Invoice is created
the same amount of Debit Memo for this type of Invoice to be created automatically in AR. Customer
debit memo should also be created for same account to offset. Control account for both AR/AP should
be same.

Above screenshot is AR Transaction window. There will be separate transaction class that will be
created and user has to perform transaction using this transaction class. Based on this transaction
class corresponding invoice will be generated in AP. Remaining process will be same as normal
transaction.

Supplier Transactions

System should allow the user to generate the payment to Supplier in Oracle AP.

System should allow the user to generate the credit note to Supplier in Oracle AP.

Supplier Credit transactions will be created as standard invoice and debit transactions will be created
as Credit note/Debit note in AP.

Parties receipts will be handled by creating debit note in AR manually and receipts made from AR.
There will be special Receipt type to be available. When this type of receipt is created, automatically
debit memo in AR and Credit memo of same account with the same amount in AP to be created to
balance out. Be sure same control is used for balance out.

Suppliers will be credited for the in AP from Seibel Similarly, the suppliers will be debited for the
refund and cancellation.

Suppliers will be debited for the settlement of net claims from Seibel in AP. Similarly the suppliers will
be credited for the net claim amount in case of cancellation of settled claim in AP.

Above screenshot is AP Invoice work bench window. There will be separate Invoice type that will be
created and user has to perform Invoice using this Invoice type. Based on this Invoice type
corresponding invoice will be generated in AR. Remaining process will be same as normal Invoice.

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

You might also like