Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Depot Repair - Version 11.5.6 to 11.5.10 [Release 11.5]
Oracle Teleservice - Version 11.5.8 to 11.5.10 [Release 11.5]
Information in this document applies to any platform.
***Checked for relevance on 14-APR-2016**
FORM:CSDREPLN.FMB - Repairs
Background of the customer/account/party concepts being used in CRM/Apps modules.
Party - an entity that can enter into business relationships. A party is a real person, organization, branch, subsidiary, legal entity, holding company, etc. Any real thing that one might want to put a name to is a party. The attributes of a party are universal. In other words, they are independent of any selling (or ultimately buying) relationship with the party.
Relationship - A binary relationship between two parties such as a contact, employee, etc. Party relationship types can be seeded or user-defined. A party relationship is optionally a party itself, meaning certain party relationships can engage in various transactions across the E-Business Suite.
Party Site - the link between a party and a location that indicates the location is valid for that party. Party sites should not be used to model the hierarchy or organizational structure of a company. The organizational hierarchy should be modeled using party relationships. Party sites are simply meant to represent the valid set of locations for a party
Account - the attributes of the selling relationship between the company deploying Oracle Applications and a party. Account attributes do not describe a party; they only exist when a selling relationship is present between the deploying company and the party.
Account Site - a party site that is used within the context of an account; e.g., for billing or shipping purposes. An account is simply the attributes that describe your financial relationship with a party.
The applications were designed so it would be possible to create a SR without providing any account information, but still capturing the Bill-To/Ship-To addresses. As such, Service Request/Depot Repair forms default the addresses at the party level (and not at account level).
This note will address common questions regarding the Bill To/Ship To defaulting addresses in the Repair Order form:
1. Is the Depot Repair form displaying the information at party or account level?
2. In order to default the Bill To/Ship To address in the Repair Order form, should the primary be set at Account level or Party level?
3. How should the 'customer master' and 'customer online' be maintained in order that the correct information would be populated automatically in the Repair Order form?
4. What is the impact of creating new contacts (and addresses) from Repair Order versus creating them from the Customers Standard form (AR)?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms