Embed Size (px)
Citation preview
SAP AG 2001
Partner DeterminationOverview
Business Partner
Text DeterminationOrganizational Management
Output DeterminationProduct Master
CRM BillingOpportunity Management
Conclusion & Appendix:CRM Best PracticesActivity Management
Sales Transactions
Business Partner
SAP AG 2001
Explain the SAP Business Partner
Explain partner categories, business partner grouping and business partner roles
Define business partner networks Family trees Group hierarchies
Customize the mapping to the R/3 OLTP
Contents/Objectives
Business partner overview
Business partner modeling elements
Customizing/configuration
Data distribution/data structure mapping
Contents
ObjectivesAt the end of this unit, you will be able to:
SAP AG 2001
Vendor
Patient Business Partner Relationships
Borrower
Plant Neutral Persons, organizations and groups Cross-application approach Open infrastructure Integration through business concepts
Tenant
Customer
Debitor
Creditor
Employee
BusinessPartner
SAP Business Partner as Central Anchor
SAP AG 2001
BP Master Datain CRM Online
BP Master Datain CRM Online
InternetSelf-Registration
InternetSelf-Registration
Interaction CenterInteraction Center
Initial load from legacy system
Initial load from legacy system
Download from R/3
Download from R/3
SAP BW(Leads)
SAP BW(Leads)
CRM Mobile Client
CRM Mobile Client
BP Maintenancein CRM Online
BP Maintenancein CRM Online
BP = Business PartnerBW = Business Information Warehouse
How does BP Master Data get into the System?
SAP AG 2001
Business Partner TypeBusiness Partner Type
Business Partner TypeBusiness Partner Type
Business Partner
FieldsName Visible Hidden
Last NameFirst NameCustomer GroupPriority
GroupingGrouping
OrganizationOrganization
PersonPerson
Business Partner MUST HAVE a Type
Group
Business Partner Type
SAP AG 2001
Business Partner TypeBusiness Partner Type
Business Partner
GroupingGrouping Number RangesFreely defined Group criteriaStandard Defaults
GroupingGrouping
Business Partner Grouping
A business partner must be assigned to a group
The grouping controls the number range
The grouping is defined in Customizing
You can make settings for standard groupings
SAP AG 2001
Ordering PartyOrdering Party
Invoice RecipientInvoice Recipient
PayerPayer
Invoice
Business Partner Roles
A role offers a particular view of the BP master
SAP AG 2001
Contact Person
Address Personal
Goods Recipient
Address Shipping Invoicing
...
...
Address Personal data
SalesSales ShippingShipping InvoicingInvoicing... ......
Data Parts for Business PartnersData Parts for Business Partners
Central set typesCRM-specific set typesCRM-specific set types
Data Sets
Each role offers a different view of the BP master
SAP AG 2001
RMG AG Schmidt & Partner
Business Partner
No. 62031
1st May 1995 – 31st March 2001Assistant to
purchasing managers
1st April – 31st December 9999Purchasing manager
Business Partner
No. 60095 Ms Schulz
Business Partner
No. 60111
For describing relationships between business partners
Attributes describe relationships
Some relationships are time-dependent
SAP Business Partners: Relationships
SAP AG 2001
Is contact person of
Has contact personPerson
Example: Relationship Category
Organization
Function
Department
Communication data
Power ofattorney
Employee responsible
Contact person relationship
SAP AG 2001
Describes the relationship between 2 BPs using attributes.
Additional attributes can be defined
Additional relationship categories can be defined using the BDT (Business Data Toolset)
Relationship direction
Cardinality
Constraints
Dependence of relationship type on business partner types and BP roles
Relationship Categories
SAP AG 2001
A BP relationship is created for each partner function, but a partner function is not created for
each BP relationship
BP 1 BP 2
Partner functions
Ship-to party
Partner functions serve to depict sales area-relevant relationships between two business partners
Example: ship-to party
Example: Bill-to party
Partner Functions
SAP AG 2001
BP50BP50BP40BP40BP30BP30BP20BP20BP10BP10
BP100BP100
BP90BP90BP80BP80BP70BP70BP60BP60
Use groups to build hierarchies
e.g. for chain of retail outlets, buying group, co-operative
Assign BPs to groups (hierarchy nodes) within the hierarchy
Business Partner Group Hierarchy
SAP AG 2001
BP50BP50BP40BP40BP30BP30BP20BP20BP10BP10
BP90BP90BP80BP80BP70BP70BP60BP60
Discount 3%
BP50BP50BP40BP40BP20BP20BP10BP10 BP90BP90BP80BP80BP70BP70BP60BP60
Pricing
Maintain condition and price agreements on an organizational level
Conditions and price agreements are usable for all BP‘s assigned to the lower levels in the hierarchy - depending on the customizing of pricing
Grouping
For statistics and marketing analysis
Business Partner Group Hierarchy - Types
SAP AG 2001
BP30BP30
Discount 3%
From mm/dd/yyyy
to mm/dd/yyyy
From mm/dd/yyyy
to mm/dd/yyyy
From mm/dd/yyyy
to mm/dd/yyyy
Separation of hierarchical structure and business partner master records
No ‚dummy business partner‘ required
Optimized performance
Conditions are assigned to hierarchy nodes
Reassignment across hierarchies
Yes, for BPs
No, for nodes
Time-dependent assignment
Node to node
BP to node
Business Partner Group Hierarchy
SAP AG 2001
CRM
Two Systems - Two Concepts
R/3Account group of the customer master determines
The number range
In which operations a customer can be used (partner functions)
The field control
Grouping
Determines the number range
BP Role
Gives a certain view on BP data in different business processes
Determines the field control
Classification
Determines to which account group a BP is mapped
Existence of data
Determines in which operations a BP can be used
SAP AG 2001
CRMCRM R/3R/3
BP-Roles Classification Account Group Partner Function
Customer 0001
Sold-to Party
Ship-to Party
Bill-to Party
Payer
.....
Customer
GoodsRecipient
Contact Person
.....
Mapping of classifications and Account Groups (1)
SAP AG 2001
Transaction in R/3 OLTP: PIDE.
Each classification is mapped exactly to one account group.
Mapping of Classifications and Account Groups (2)
SAP AG 2001
CRMCRM R/3R/3
CustomerNumber range external5000 - 5999
Sold-to party (entered in R/3)Number range internal5000 - 5999
Customer (entered in CRM)Number range internal1 - 4999
Sold-to partyNumber range external1 - 4999
Consistent Business Partner Distribution
SAP AG 2001
Set field attributes for each BP Role (or Activity, or BP Type)
Hide
Required entry
MUST be mapped to the fields of the Business Partner in R/3 to ensure consistent data synchronization and mapping
Optional entry
Display
Configure Field Attributes for Each BP Role
SAP AG 2001
Configuration via Drag&Drop
Screen layout and screen sequence
Technique
Subscreens
Generation of screen containers
Change Screen Configuration Using VCT (Visual Configuration Tool)
SAP AG 2001
BP Roles & Relationships
Include additional attributes in roles and relationship categories
Create additional roles
Create new relationship categories
Extension of interface is unaffected by SAP release updates
Existing screens can be extended by new fields
Screen sequences can be extended by new screens
Extension by downstream applications
SAP applications
Development partners
Customers
Extensibility with the BDT
SAP AG 2001
Description
Identified duplicates can be merged by reassigning dependent data and objects in dialog
All dependencies are visualized in the form of dependency trees
After merging, duplicates can be archived automatically
Value Proposition / Benefit
Reduce data redundancy
Enable high data quality, consistency and reliability
Business Partner - Data Cleansing
SAP AG 2001
Cleansing DuplicatesIdentifying Duplicates
Duplicate determination
during online transaction BAPI
Duplicate determination
during online transaction BAPI
Full database scan Full database scan
Interface
BAPI
Registration of
cleansing cases
Cleansing stackCleansing stack
Processing of
cleansing cases
Reassign
business partner
information
Business Partner - Data Cleansing: Structure
SAP AG 2001
Description
Records marked for archiving can be written to an archive
After archiving, the data is consistently deleted from the CRM System
Customer enhancements of BP data can be archived without modifications
Check for data dependencies in CRM
Before archiving, the data is checked. If a business partner is used by another application, it can not be archived.
Data dependency check for customer enhancements can be included without modifications
Search, and display of archived data
Value Proposition / Benefit
Enable high data quality, consistency and reliability
Improve performance by reducing data volume
BP - Archiving
SAP AG 2001
Phases of the Archiving Process
Phase 1
Preselect Get approval
(CHECK) System status
to ARCR
Phase 2
WRITE to archive(all records with status ARCR)
Phase 3
Check READ from archive
DELETE in database
SAP AG 2001
You are now able to:
Summary
Explain the SAP Business Partner
Explain partner types, business partner grouping and business partner roles
Define business partner networks
Family trees
Group hierarchies
Customize the mapping to the R/3 OLTP
Understand the concepts of extensibility of BPs
