AIM

BR.100 APPLICATION SETUP

MANHEIM
TRADING COMMUNITY
ARCHITECTURE

Author: Dominic Mazzotta

Creation Date: October 1, 2014
Last Updated: October 7, 2014
Document Ref: BR100.TCA
Version: 1.1
Print Date: June 18, 2018

Approvals:

Document1

6/18/2018 10:59 PM i
Document Control

Change Record
3

Date Author Version Change Reference

01-Oct-2014 Dominic Mazzotta Draft 1.0 No Previous Document

11-Sep-2015 Sunil Pandey Draft1.0 Modified document to include TRND setups
25-Sep-2015 Sunil Pandey Draft1.0 Modified document for
MAN_TCA_AUCTION_CODES value set
07-Oct-2015 Sunil Pandey 1.1 Modified document to make Group Code DFF as
free form text (40 Chars) instead of based on VS:
MAN_TCA_GROUPCODE

Reviewers

Name Position

Distribution

Copy No. Name Location

1 Library Master Project Library

2 Project Manager
3
4

6/18/2018 10:59 PM ii
 Contents

Document Control ..................................................................................................................ii

Setup Control Sheet - Oracle Trading Community Architecture ..................................... 1
TCA: Create Custom Responsibilities .................................................................................. 2
TCA: Define Descriptive Flexfields (Optional) ................................................................... 4
DFF Summary .................................................................................................................. 4
DFF Configuration ........................................................................................................... 8
TCA: DQM Profile Options ................................................................................................. 11
TCA: Set Up Data Quality Management – Run Requests ............................................... 12
DQM Staging Program ................................................................................................. 12
DQM Synchronization Method ................................................................................... 13
DQM Synchronization Program .................................................................................. 13
TCA: Receivables Systems Options .................................................................................... 14
TCA: Update Customer Profile Classes ............................................................................. 15
DEFAULT ....................................................................................................................... 15
TCA: Define Lookups ........................................................................................................... 18
Credit Classification ...................................................................................................... 18
Customer Classification ................................................................................................ 19
TCA: Define Customer Classifications............................................................................... 20
Open and Closed Issues for this Deliverable ...................................................................... 1
Open Issues....................................................................................................................... 1
Closed Issues .................................................................................................................... 1
Appendix: Patches .................................................................................................................. 2
Appendix: Assign a Single Contact to Multiple Customers ............................................. 3
Appendix: Create Refunds for Customer Contacts (DO NOT SETUP)........................... 5
Customer Contacts .......................................................................................................... 5
Receivables Activity ........................................................................................................ 6
Receipt ............................................................................................................................... 7
Credit Memo .................................................................................................................... 8
Payables ............................................................................................................................ 8

6/18/2018 10:59 PM iii

Setup Control Sheet - Oracle Trading Community Architecture

Environment Name: Machine: Type (definition, execution, or both):

Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Date Signature Approval
SubWorkflow Name

Setup Trading Community

Architecture

6/18/2018 10:59 PM 1
TCA: Create Custom Responsibilities

System Administrator>Security>Responsibility>Define
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description:

Update Menus:
Navigation: System Administrator>Application>Menu

System Administrator: Application: Menu

Menu

User Menu Name

Menu Type

Description

Seq
Prompt Submenu Function Description Grant







6/18/2018 10:59 PM 2
Create Responsibilities:
Navigation: System Administrator>Security>Responsibility>Define

Responsibility

6/18/2018 10:59 PM 3
TCA: Define Descriptive Flexfields (Optional)

Receivables Manager>Setup>Financials>Flexfields>Descriptive>Segments
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description:

DFF Summary
Application Title Context DFF Name Attribute # Value Set Value Set: Required Comments
Max Size

Receivables Site Use Global Pref Default ATTRIBUTE1 MAN_TCA_PREF_ 50 [OM] DELETE – Diego doesn’t need it for any custom
Information Payment Type DEF_PAYTYPE objects
Receivables Site Use Global Pref Netting ATTRIBUTE2 MAN_TCA_PREF_ 50 [OM] DELETE – Diego doesn’t need it for any custom
Information Option NETTING objects
Receivables Site Use Global Pref Title Ship ATTRIBUTE3 MAN_TCA_PREF_ 50 [OM] DELETE – Diego doesn’t need it for any custom
Information Method TITLE_SHIPMETH objects
OD
Receivables Site Use Global Pref Check ATTRIBUTE4 MAN_TCA_PREF_ 59 [OM] DELETE – Diego doesn’t need it for any custom
Information Printing Option CHECK_PRINTIN objects
G_OPTION
Receivables Site Use Global Netting: Opt In ATTRIBUTE5 Yes_No 3 [Netting] VALUES: Yes/No
Information
Receivables Site Use Global Netting: Day ATTRIBUTE6 Netting_Day 2 [Netting] VALUES: 1, 2, 3, 4
Information
Receivables Site Use Global Netting: Protected ATTRIBUTE7 Yes_No 3 [Netting] VALUES: Yes/No
Information
Receivables Site Use Global Netting: Title ATTRIBUTE10 Yes_No 3 [Netting] VALUES: Yes/No
Information Absent Exempt

6/18/2018 10:59 PM 4
 Application Title Context DFF Name Attribute # Value Set Value Set: Required Comments
Max Size

Receivables Site Use Global Customer Payable ATTRIBUTE8 MAN_IBY_PAYME 50 [AR] Table Type Value Set
Information NT_METHOD

where payment_method_code in (select curr.payment_method_code

FROM fnd_application_vl a,
iby_applicable_pmt_mthds le,
iby_applicable_pmt_mthds org,
iby_applicable_pmt_mthds txntype,
iby_applicable_pmt_mthds loc,
iby_applicable_pmt_mthds curr,
fnd_lookups lk
WHERE a.application_id IN (200, 206, 260, 222, 8405)
AND curr.payment_flow(+) = 'DISBURSEMENTS'
AND curr.applicable_type_code(+) =
'FOREIGN_CURRENCY_FLAG'
AND curr.application_id(+) = a.application_id
AND loc.payment_method_code(+) = curr.payment_method_code
AND loc.application_id(+) = curr.application_id
AND loc.applicable_type_code(+) = 'CROSS_BORDER_FLAG'
AND loc.payment_flow(+) = 'DISBURSEMENTS'
AND le.payment_method_code(+) = curr.payment_method_code
AND le.application_id(+) = curr.application_id
AND le.applicable_type_code(+) = 'PAYER_LE'
AND le.applicable_value_to(+) IS NULL
AND le.payment_flow(+) = 'DISBURSEMENTS'
AND org.payment_method_code(+) = curr.payment_method_code
AND org.application_id(+) = curr.application_id
AND org.applicable_type_code(+) = 'PAYER_ORG'
AND org.applicable_value_to(+) IS NULL
AND org.payment_flow(+) = 'DISBURSEMENTS'
AND txntype.payment_method_code(+) =
curr.payment_method_code
AND txntype.application_id(+) = curr.application_id
AND txntype.applicable_type_code(+) = 'PAY_PROC_TRXN_TYPE'
AND txntype.applicable_value_to(+) IS NULL
AND txntype.payment_flow(+) = 'DISBURSEMENTS'
AND lk.lookup_type = 'IBY_PMT_MTHD_USAGES'
AND lk.lookup_code = 'ALL'
and a.application_name = 'Receivables'
AND Language = 'US')

6/18/2018 10:59 PM 5
 Application Title Context DFF Name Attribute # Value Set Value Set: Required Comments
Max Size

Receivables Site Use Global Pay Group ATTRIBUTE9 MAN_AP_PAY_GR 50 [AR] Table Type Value Set
Information P

where lookup_type = 'PAY GROUP'

AND VIEW_APPLICATION_ID = 201
AND END_DATE_ACTIVE IS NULL
Receivables Site Use Global Acceptance ATTRIBUTE11
Information Indicator
Receivables Site Use Global T&C Version ATTRIBUTE12
Information Number
Receivables Site Use Global User ID ATTRIBUTE13
Information
Receivables Site Use Global Date / Time ATTRIBUTE14
Information Stamp
Receivables Site Use Global Aging Exception ATTRIBUTE18 Yes_No 5
Information
Receivables Site Use Global Existing AS400 ATTRIBUTE15 Yes_No 5
Information
Z
Aging

6/18/2018 10:59 PM 6
 Application Title Context DFF Name Attribute # Value Set Value Set: Required Comments
Max Size

Receivables Address Global Manheim Auction ATTRIBUTE1 MAN_TCA_AUCTI [OM] The Value Set and values for the value set will be
Information Code ON_CODES defined in OM BR100. We just need to assign the
value set for this TCA setup.

Please see attached for values to be setup for this

independent value set

MAN_TCA_AUCTION
_CODES_VS_Values.xlsx

Receivables Customer Global Customer Type ATTRIBUTE10 MAN_TCA_CUST_ 50 [OM] VALUES: Get from Nickie?
Information TYPE **Please refer OVC Phase-2 document for setting up
this value set values and DFF details.

Install Plan for OVC

Phase 2.docx
Receivables Customer Global Customer ATTRIBUTE13 MAN_TCA_CUST_S 50 [OM] VALUES: Get from Nickie?
Information SubType UBTYPE **Please refer OVC Phase-2 document (above
document) for setting up this value set values and DFF
details.

Also, need to first define Receivable lookup code

“CUSTOMER CLASS”, mentioned later in this
document
Receivables Customer Global Dealer ATTRIBUTE14 MAN_TCA_DLR_S 50 [OM] DELETE – Diego doesn’t need it for any custom
Information Segmentation EGMENTATION objects
Receivables Customer Global Group Code ATTRIBUTE15 MAN_TCA_GROUP 40 [OM] For Sales Orders:
Information CODE  COXF
40 Chars  EMPL
 MANH
 MYRD
For Consigner Netting:
INF, INFS, LSE, NCAN, NIS, NISD, NISM, NISS,
NITO, NMAC, NMBD, NMCH, NMRS, NOL, NRD,
FMC, FOR, ARS, PRIM
Receivables Customer Global Dealer License ATTRIBUTE16 [OM]
Information Number
Receivables Customer Global Buy Fee Rebate ATTRIBUTE17 OM: Yes or No 50 [OM] Yes/No
Information Program Seller

6/18/2018 10:59 PM 7
 Application Title Context DFF Name Attribute # Value Set Value Set: Required Comments
Max Size

Receivables Customer Global Buy Fee Rebate ATTRIBUTE20 OM: Rebate % 3 [OM] % (0-100)
Information Program Percent

Receivables Customer Global Customer OVC ID ATTRIBUTE18 [CONV]

Information
Receivables Customer Global Account OVC ID ATTRIBUTE19 [CONV]
Information
Receivables Customer Floorplan Agency ATTRIBUTE1 MAN_AR_AGENC 50 [FP] VALUES: BASIC, BASIC PLUS, ADVANTAGE,
Information Agency Classification Y_CLASS ADVANTAGE X
Preferences
Receivables Customer Floorplan FP Agency ID ATTRIBUTE4 [FP]
Information Agency
Preferences
Receivables Party Global Customer OVC ID ATTRIBUTE18 [OM] Converted OVC number for 100M
Information
Receivables Party Global OVC 100 Million ATTRIBUTE20 [OM] Converted 100M number
Information Number

DFF Configuration
Query the following Application and Title:
Application Title Freeze flexfield Segment Separator

Context Field
Prompt Value Set Default Value Reference Field Required Displayed

Context Value Checked

Uncheck Freeze Flexfield Definition and create the following Context Field Values:

6/18/2018 10:59 PM 8
Context Field Values
Code Name Description Enabled

Navigation: Segments button on Descriptive Flexfield form

Segment Summary
Number Name Widow prompt Column Value set Displayed Enabled

10
20
30

Navigation: Value Set button on Segment Summary form

Value Sets
Value Set Name Description List Type Security Type

Format Validation
Format Type Maximum Size Precision Numbers Only (0-9) Uppercase Only (A- Right-Justify and Min Value Max Value
Z) Zero-Fill Numbers
(0001)

Value Validation
Validation Type

Navigation: Open button on Segment Summary form

6/18/2018 10:59 PM 9
Segments
Name Description Column Number Enabled Displayed

Validation
Value Set Description Default Type Default Value Required Security enabled Range

Sizes
Display Size Description Size Concatenated
Description Size

Prompts
List of Values Window

Completion Steps
Save your work.
Check Freeze Flexfield Definition.
Click the Compile Button.

6/18/2018 10:59 PM 10
TCA: DQM Profile Options

System Administrator>Profile>System
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: Oracle employs the Data Quality Management (DQM) match rules to identify how search results should be displayed in the application's search
screens.

Query the following profile options:

Note: Some of these values are seeded

Profile Option Name Site Applicatio Responsibility User

n

HZ: Enable DQM Party Search Yes

HZ: Match Rule for Organization Simple Search HZ_ORG_SIMPLE_SEARCH_RULE

HZ: Match Rule for Organization Advanced Search HZ_ORG_ADV_SEARCH_RULE

DQM Match Rule for Search SAMPLE:ADVANCED SEARCH RULE

HZ: Match Rule for Person Simple Search HZ_PERSON_SIMPLE_SEARCH_RULE

HZ_PERSON_ADVANCED_SEARCH_MA
HZ: Match Rule for Person Advanced Search
TCH_RULE

HZ: Match Rule for Organization Duplicate Prevention SAMPLE: SEARCH

HZ: Match Rule for Person Duplicate Prevention SAMPLE: SEARCH

HZ: Duplicate Allowed No

HZ: Do not use contact addresses and contact points for DQM
No
Duplicate identification.

6/18/2018 10:59 PM 11
TCA: Set Up Data Quality Management – Run Requests

Trading Community Manager>Control>Requests>Run

Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: Run the DQM Staging program from a Trading Community Manager responsibility. The DQM Staging program uses the match rules that you
selected to create the indexes used in Oracle search screens.

DQM Staging Program

Navigation: Trading Community Manager>Control>Requests>Run
Click OK to select Single Request.
In the Name field, enter “DQM Staging Program”
Enter the following parameters:

Number of Parallel Staging

3
Workers

Staging Command STAGE_ALL_DATA

Continue Previous Execution

Index Creation Tablespace

Index Creation

Click the OK button.

Click the Submit button.

*Once this completes successfully, go back and set the DQM Synchronization Method to Automatic (see next step). Then you do NOT have to run the DQM
Staging program anymore unless you are bringing in data from other sources

6/18/2018 10:59 PM 12
DQM Synchronization Method
Navigation: Oracle Customer Data Librarian Super User -> Administration Tab > DQM tab > Setup > Synchronization Method

Set Method to Automatic, click Apply

Note: In Release 12, the DQM Synchronization can be set to:

 Automatic
 Batch
 Disabled

If DQM automatic sync is enabled a concurrent program is submitted whenever a party is created/updated.
This concurrent program is called DQM Serial Sync Index Program (ARHDQMSS).

Once a new party/account is added or updated, the DQM Serial Sync Index Program is kicked off and once the concurrent process is complete you can search
and find the party/account that was updated or added.

You might not be able to search for the newly created party/account immediately after creation. After a few minutes you can search for them, this depends on
the completion of the concurrent request.

DQM Synchronization Program

Navigation: Trading Community Manager -> Control > Requests > Run

Note: It is not required to run this program at this time. However, it may be necessary to run after updating DQM profile options that affect indexes.
Use this program to troubleshoot any search related/indexing issues.

This program synchronizes an existing staged schema and interMedia indexes with the TCA registry. This program ensures that any new or updated data in
the TCA registry is reflected in the staged schema. You can schedule the DQM Synchronization Program to be run on a periodic basis. Running this program
frequently ensures that the data in the staged schema and inetrMedia indexes reflect new data for your search.

6/18/2018 10:59 PM 13
TCA: Receivables Systems Options

Receivables Manager>Setup>System>System Options {Already Exists in Production}

Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: Ensure that Automatic Customer Numbering and Automatic Site Numbering is configured as required.

Requirement: Customer Number (Account Number) and Customer Account Site (Site Number) are Auto Generated
UPDATE: These will be generated by the OVC interface. Leave as auto generate for testing in the interim.

6/18/2018 10:59 PM 14
TCA: Update Customer Profile Classes

Receivables>Customers>Profile Classes
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: In the Oracle Receivables Customer Profile Classes window, assign customer attributes to your customer profile classes.

Note: This configuration is owned by the AR BR100.

DEFAULT

Name DEFAULT Active Checked

tab
Profile Class
Balance Forward Billing Enabled

Bill Level Tax Printing

Type Grouping Rule

Payment Terms IMMEDIATE Send Statements

Allow Discounts Checked Send Credit Balance

Override Terms Send Dunning Letters

Discount Grace Days Cycle

Collectors Name Default Collector Match Receipts By

Classification Moderate Risk Autocash Rule Set

Periodic Review Cycle Annually Remainder Rule Set

6/18/2018 10:59 PM 15
 Analyst Mazzotta, Dominic AutoReceipts Include Disputed Items

Tolerance 0 []

Credit Check

tab
Late Charge Profile
Enable Late Charges Checked Credit Items

Charge Calculation Overdue Transactions Only Disputed Transactions

Late Charge Type Adjustment

Payment Term

Message Text

Interest Calculation Formula

Interest Calculation Period Daily

Days in Period 30

Receipt Grace Days

Hold Charged Invoices No

Charge Beginning Date

Use Multiple Interest Rates

tab
Profile Class Amounts

USD
Credit Limit Min Receipt Amount

6/18/2018 10:59 PM 16
 Order Credit Limit Min Statement Amount

Exchange Rate Type Corporate

Minimum Customer Balance Value

Minimum Invoice Balance Value

Minimum Charge Per Invoice Maximum Charge Per Invoice

Interest Charge: Type Penalty Charge: Type

Interest Charge: Value Penalty Charge: Value

Interest Charge: Charge Schedule Penalty Charge: Charge Schedule

6/18/2018 10:59 PM 17
TCA: Define Lookups

Receivables>Setup>System>QuickCodes>Receivables
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: The following table lists lookup types used for Customers

Add records in Green and disable records in Red:

Credit Classification

Type AR_CMGT_CREDIT_CLASSIFICATION

Meaning Classification

Application Receivables

Description Credit Classification

Code Lookup Code Meaning Lookup Code Description Tag From To Enabled

45 SPECIAL 45 Special 45 Special 19-Nov-09 NO

BIG TRUCK Big Truck Big Truck 19-Nov-09 NO
GOLD CARD Gold Card Gold Card 19-Nov-09 NO
GUARANTOR Guarantor 30-Jan-06 Yes
HIGH High Risk 23-Sep-02 Yes
LOW Low Risk 23-Sep-02 Yes
MODERATE Medium Risk 23-Sep-02 Yes
RECEIVABLE Receivables Receivables 19-Nov-09 NO
RENTAL Rental Rental 19-Nov-09 NO
RV RV RV 19-Nov-09 NO
UCL Universal Credit Limit Universal Credit Limit 19-Nov-09 NO
MEDIUM LOW Medium Low Risk 08-APR-2015 Yes

6/18/2018 10:59 PM 18
 Code Lookup Code Meaning Lookup Code Description Tag From To Enabled

MEDIUM HIGH Medium High Risk 08-APR-2015 Yes

EXPORT TRADER Export Trader Export Trader 09-JUL-2015 Yes

Customer Classification

Type CUSTOMER CLASS

Meaning Customer Class

Application Receivables

Description Customer Class

Code Lookup Code Meaning Lookup Code Description Tag From To Enabled

Federal Federal Federal Yes

Floorplan Agency Floorplan Agency Floorplan Agency Yes
Mega Dealer B2B Mega Dealer B2B Mega Dealer B2B Yes
Public Sector Companies Public Sector Companies Public Sector Companies Yes
N/A-MS N/A-MS N/A-MS Yes
F/L F/L F/L Yes
FACTORY FACTORY FACTORY Yes
INS-COM INS-COM INS-COM Yes
RETAIL RETAIL RETAIL Yes
AUCTION AUCTION AUCTION Yes
GOVT GOVT GOVT Yes
INS-TRL INS-TRL INS-TRL Yes
RENTAL RENTAL RENTAL Yes
DEALER DEALER DEALER Yes
BANK BANK BANK Yes
OTHER OTHER OTHER Yes
TITLE LOAN TITLE LOAN TITLE LOAN Yes
WHOLESALE WHOLESALE WHOLESALE Yes

6/18/2018 10:59 PM 19
TCA: Define Customer Classifications

Receivables>Setup>System>QuickCodes
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: The following table lists lookup types used for Customers

6/18/2018 10:59 PM 20
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

6/18/2018 10:59 PM 1
Appendix: Patches

NAVIGATION:
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: Below are patches that have been identified and tested to resolve the specified issues.

Date Issue SR/Support Note Patch Details

30-Sep-2014 When accessing the Customer form through the Receivables Doc ID: 1253394.1 Patch:
Manager responsibility, user receives following error: R12.AR.A: Patch 10036698
R12.AR.B: Patch 10036698
KeyFlexfieldDefinitionFactory.getStructureNumber could not find the
structure definition for the flexfield specified by Updating Files:
Application = SQLGL, Code = GL# and Structure number = R12.AR.A:
ArBusPurDetAMImpl.java 120.8.12000000.6
FND, Message Name: FND_GENERIC_MESSAGE, Tokens: ArActSiteBusPurCO.java 120.11.12000000.12
MESSAGE = java.sql.SQLException: ORA-20001:
Operating Unit -1 does not exist in the target database. ORA-06512: at R12.AR.B:
"APPS.APP_EXCEPTION", line 72 ORA-06512: at ArBusPurDetAMImpl.java 120.10.12010000.5
"APPS.GL_GLOBAL", line 65 ORA-06512: at line 1; ArActSiteBusPurCO.java 120.16.12010000.5

*Error is not received when accessing the Customer form from

OM or Credit Management

6/18/2018 10:59 PM 2
Appendix: Assign a Single Contact to Multiple Customers

NAVIGATION:
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: The details below explain how to resolve the issue: Unable to attach a contact to multiple customers.

Customer Form, Contact Issue: How to Assign Existing Contacts to a Customer (Doc ID 1141014.1)

Goal
In the Communications tab, you would like to use an existing contact record and assign it to a customer record rather than creating a new contact record.
When you open the Communication tab, you can see a Create Contact button, but no option to use a pre-existing contact.

How can I assign an existing contact to a customer in Release 12?

Solution
When assigning contact persons to a customer, there is no direct way of picking an already existing contact person record.

Instead, you would click on the Create Contact button and proceed to enter contact information. You can enter minimal information such as First and Last
name and then click on Apply. The form will then validate the data you entered to check if a potential duplicate exists. If similar data is found, you will be
presented with a Warning: Possible Duplicate Persons page:

6/18/2018 10:59 PM 3
You then have the option to Create New Person, or Use Existing Person.

To ensure the form behaves as described above, please review the following setup requirements:
1. Enable DQM (Data Quality Management)
Please review Note 553671.1, Customer Form, search Issue: How to Setup Data Quality Management (DQM) Enabled Searching in the Customer Form
2. Verify the DQM Automatic synchronization is set up. See Note 465993.1, How does the DQM Real Time (Automatic) Synchronization work for R12?
3. Define Match Rules. For more information, please review Note 565905.1, FAQ on the setup/usage of DQM Profile Options for OCO and Receivables,
Release 11i
(This note was written for 11i but still applies to Release 12.)
4. To prevent creation of duplicate contact, following are sample settings for relevant profile options.

6/18/2018 10:59 PM 4
Appendix: Create Refunds for Customer Contacts (DO NOT SETUP)

NAVIGATION:
Process: Business Area: Date:

Control Number: Priority (H, M, L): Process Owner:

Description: The details below explain how to resolve the issue: Can you create refunds for Customer Contacts?

Oracle Receivables can process Customer Refunds as payments through Oracle Payables. This can also be accomplished for Customer Contacts by following
the steps below:

Customer Contacts
Assign an Account and Site to the Contact, if it does not currently have one. This is required to apply a Refund to the Party (Person) in Receivables
1. In the Customer Form, query the Customer Contact by changing the Customer Type to Person, entering the Name, and click Go.
2. Click on the Party Name.
3. Click the Create Account button.
4. Enter the Account Number and Click Create Address.
5. Enter the Address and Site Purpose, then click Finish.

6/18/2018 10:59 PM 5
Receivables Activity
Create a Receivables Activity for Refunds.
1. Navigate to: Receivables Manager -> Setup -> Receipts -> Receivable Activities
2. Create Receivables Activity with Type: Refund

6/18/2018 10:59 PM 6
Receipt
Apply the Receivables Activity to the Unapplied/On Account Receipt in Receivables.
1. In Receipts form, query the Receipt requiring Refund and click the Apply button.
2. Select Refund from the LOV in the Apply To field and click the Refund Attributes button.
3. Populate the Refund Payment Method (check) and click Apply. Save the Transaction.

6/18/2018 10:59 PM 7
Credit Memo
Apply the Receivables Activity to the Credit Memo in Receivables.
1. In the Transaction form, query the Credit Memo that requires Refund. Complete if necessary.
2. Select Actions -> Applications, select Refund from the LOV in the Apply To field, and click the Refund Attributes button.
3. Populate the Refund Payment Method (check) and click Apply. Save the Transaction.

Payables
Query the Invoice in Payables to see the Refund in process.

6/18/2018 10:59 PM 8
6/18/2018 10:59 PM 9