02 0 TRM PSCD Master Data

Agenda
Introduction Interests
Master Data Installment Plans / Promise to Pay
Transactions Security Deposits
Documents Correspondence
Specific Posting Processes Integration Accounting
Payments and Clarification Invoicing
Payment Run and Transfers Overview Business Rule Framew.
Clearing Control / Ac. Maint. Financial Customer Care

Returns
Dunning
SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 1
1
Master Data
Contents:
Business Partner Background
Business Partners, Contract Accounts, Contract Objects,
Relationships
Control Parameters Within Master Data
Business Data Toolset for Enhancing Screens
WebDynpro Application for Taxpayer Registration
2
Master Data: Unit Objectives
After completing this unit, you will be able

to:
Create business partners, contract accounts, and contract
objects in the system.
Explain central address management.
List possible master data relationship scenarios.
Apply master data control parameters at desired levels.
Create Taxpayers with the WebDynpro Application
3
Master Data
Business Partner
Contract Account
Contract Object
Revenue Type Overview
WebDynpro for Taxpayer Registration
Business Data Toolset
Additional Information
4
Business Partner: Requirements
One view on business partner Central Master Data
One person – many processes Business Partner role concept
Connection to other persons / entities Business Partner relationships
Additional information for specific Extensibility

tasks
Adaptable Screens Configurable
Cooperation with all existing Well-defined Interfaces

applications
Business Requirements TRM Solution
Business Partners are in the focus of business interest. All relevant information must
therefore be available quickly.
The required information on the business partner depends on the situation. The system
differentiates the output from the database according to the role of the business partner.
A business partner may have relationships with other business partners (a marriage, contact
person, company relationship, etc). This can be recorded in the system.
Standard software is unable to provide highly specific information. Downstream
developments (ERP applications, development partners and customers) can add new
attributes to SAP Business Partners. Such extensions are release-independent.
Using the VCT (Visual Configuration Tool), users can configure Business Partner screens
using "drag and drop". Again, no modifications are required in the event of a release update.
To have problem-free cooperation with applications in existing system landscapes, interfaces
must guarantee the integration of Business Partners. SAP offers corresponding BAPIs
(Business Application Programming Interface) for communication with existing applications.
5
Business Partner and Roles: Examples
Employee
Audit
Business
Taxpayer
Partner
Citizen
Constituent
Services
Vendor
Collections
Roles
…………
Debtor
Application-neutral data, such as name, address, bank details and payment cards, is
contained on the business partner master record. Special requirements involved in setting up
business partners that are organizations, groups, and individuals are also fulfilled.
In addition, SAP’s Business Partner offers an open infrastructure for linking application-
specific attributes for business partners. From a business point of view, this link is made by
way of the role concept.
On the technical side, SAP Business Partner offers predefined interfaces via which business
partner attributes from different applications can be linked.
This means that existing business partner mapping within SAP can gradually be integrated
into SAP Business Partner.
6
Business Partner Role Definition
Role
Contact Person
Taxpayer
Business
A business partner role corresponds to a business context in which a business partner can
appear. A business partner can have several business partner roles.. Possible roles are
citizen, contact person (used in PSCD), individual taxpayer or business.
The above example shows that a business partner can assume several roles (contact
person, taxpayer, business) depending on the business process in which he/she is involved.
BP roles consist of blocks (attributes) known as data sets. These are shown as little black
boxes in the graphic above.
SAP’s Business Partner offers an open infrastructure. This means that other components
(core R/3, IBU components, components of development partners, and a customer’s-own
components) can easily include their own application-specific business partner data.
As of release ERP2005, business partners must now exist in the business role MKK for role
category MKK. If you use business partner roles on a time basis, note the following : you
must not restrict the business role MKK for role category MKK on a time basis. It must
always have a validity from the current data to 31.12.9999. Restrictions on the validity of this
role are not permitted.
7
Master Data Structure: Structure Elements
Business
Natural person(s) or legal entity
Partner
Contract
Holds accounting information
Account
Contract Person, thing or intangible

Object the business process refers to
SAP Business Partner: Does exist in the real world, is a natural person or a legal entity.
Contract Account: Does NOT exist in the real world, holds accounting information.
Contract Object: Does (or does not) exist in the real world, is either not a natural person nor
legal entity or a natural person / legal entity, but with this aspect being not relevant (Tangible
contract objects may include children, properties, physical locations and cars etc).
The component central business partner enables you to create and manage business partners
centrally.
By using business partners it is possible to merge partner data already held by a company in
more than one system in such a way that the potential for new contracts within the same
customer contact can be identified.
Seamless integration of customer-specific data is possible without modification, ensuring full
future maintenance, as defined interfaces exist for this purpose.
Business Partner is a component embedded in the SAP Business Framework. This is a decisive
advantage, because the link to SAP’s Business Framework guarantees the integration of BP in
an existing system landscape, as well as cooperation with other external applications.
As data is distributed by BAPIs, SAP BP can function as the server for non-SAP systems. The
BAPIs (Business Application Programming Interface) are called by different basis technologies
(COM/DCOM, CORBA, JAVA, RFC, etc.) by external systems. In the future, it will be possible to
distribute business partner data over several systems.
8
Master Data: Minimum Structure
Minimum Structure for Master Data in PSCD
Business
Partner
Person A
Corporate Value
Contract
Income Added Services
Account Tax Tax
Contract
Object
In principle, business transactions in PSCD can also be mapped out without contract objects
by means of contract accounts.
You must assign at least one business partner to each contract account. Depending on
customizing, you are also allowed to assign several business partners to a contract account.
Prerequisites: You can only assign additional business partners to a contract account if the
respective contract account category allows you to do this.
Features: The master data in a contract account can be divided into one part that is the
same for all business partners in the contract account (in other words, cross-business
partner) and into another part that is business partner-specific. You can set the business
partner-specific data differently for different business partners.
9
Master Data: Contract Object (Scenario 1)
Using contract objects as PAYMENT REFERENCE for revenues / payments
Business Owner
Partner
Company A Person B
Personal
Corporate Value Income
Contract
Contract Income Added Services
Account Tax
Account Tax Tax
Alternative
payer
CIT
Contract Location A VAT Licenses Job A Job B
Location A
Object
CIT
Location B
by means of contract accounts. However, using contract objects offers the advantage of a
functionally different method of managing the various business transactions. When using
contract objects, the following functions are available:
A contract object can be assigned to one or more business partner.
You can override data defined in the contract account for:
Invoice recipient correspondence control
Control of incoming and outgoing payments
Control data for generating correspondence requests (inbound correspondence)
Focus on account view (account balance) for a business partner is available for selected
contract objects.
10
Using contract objects as an OBJECT for revenues and payments
Business Owner
Partner
Company A Person B
Corporate Value Personal

Contract
Contract Income Added Services Income
Account
Account Tax Tax Tax
Contract Licenses Job A Job B

Location B Location A
Object
contract objects.
11
Aggregation of Contract Accounts
Business Owner
Partner
Company A Person B
Taxes
Contract
Contract and Additional Taxes
Account
Account Fees Revenues and Fes
Contract CIT VAT PIT PIT

License
Object Location A Location B Job A Job B
VAT
Location A
contract objects.
12
Control Parameters within Master Data
( ) = if indicator activated
Address(es) Which address?
Bank data Bank details ID (Bank details ID)
Payment
Payment card Payment card ID (Payment card ID)

Payment method (Payment method)
Alternative payer/payee (Alternative payer/payee)
Business Partner
Contract Account
Contract Object
Payment Lock (Payment Lock)
Corr. control (Corr. Control)

Open Item Management
Corr. variant (Corr. Variant)

Alt./add. Recipients (Alt./add. Recipients)
Posting rules/ lock Inbound Corr. Dunning/
Dunning control/ lock Lock
Invoice Type Dunning Lock
Interest Calculation/ lock Invoicing separately/
Lock
Clearing Control
Control Parameters
Most processing control data can be set on the contract account as well as on the contract
object.
Many of the control parameters above can be overridden or extended by data contained in
posting documents. For example, the payment / dunning methods can be determined in the
line item.
Note: By setting the appropriate field indicator in the contract object you control whether the
payment parameters defined in the contract object or in the contract account are used.
Payment parameters in a document still have priority.
13
Business Partner: Business Partner Category
BP Category
Business
Partner Person Group Organization
e.g.
BP Type
Resident
Business
Non-Profit
A business partner in PSCD usually represents the person or legal entity that you need to
process incoming and outgoing payments against. It is primarily the constituent or taxpayer
from the collections point of view and the beneficiary from the disbursements point of view.
Business partner category is the term used to classify a business partner as a natural person
(e.g. private individual), group or organization (legal entity or part of a legal entity, such as
department).
The business partner category determines which fields are available for data entry. For
example, when you want to create a business partner as an organization, one of the fields
requires you to enter the legal form, whereas with a person, you have to enter first name,
name components and gender, etc.
When a business partner is created, the business partner category must be selected
(required entry).
Assignment of the business partner category is static and cannot be changed once the
business partner has been created.
It is not possible to create other business partner categories.
14
Business Partner: Business Partner Type
Business
BP Category
e.g.
BP Type
Resident
Business
Non-Profit
The business partner type controls the field status definition (which fields on the business
partner master record are mandatory, hidden, displayed, optional) when creating a business
partner in PSCD.
You can use business partner types to group business partners according to your own
criteria
You can find the BP Type in the control data of the business partner.
15
Business Partner: Business Partner Group
Business
BP Category
e.g.
BP Type
Resident
Business Grouping for

Internal/external numbering
Non-Profit
A business partner group is a classification of business partners according to criteria that the
user can freely define. The procedure in customizing is as follows:
Definition of number ranges for the business partners
Definition of groupings for the business partner and assignment of number ranges
Number range intervals and a type of number assignment are defined for each number
range:
Type of number assignment: external or internal number assignment
Number range intervals determine which numbers are permitted.
Business partner number ranges apply to all clients. The standard ERP system contains
number ranges for the groups provided, and these can be changed if necessary.
16
Business Partner: Address management
Address
Address Valid from…to
1:n
Postal Address
Postal Address
Postal Address
1:n
Telephone
Telephone
Telephone
1:n
E-mail, Fax, others
E-mail, Fax, others
E-mail, Fax, others
=Standard address
Central address management allows different addresses to be assigned to a business

partner for different functions (see customizing of business partner address types). These
addresses can be classified according to address types (e.g. delivery address,
correspondence address, etc.).
You can maintain any number of addresses for each business partner. One address per
business partner is flagged as being the standard address.
Postal data and information on different communication types is assigned to the address.
You can maintain different communication types for each address (telephone, fax, internet
mail address, pager services, printers, remote mail, Secure Store & Forward, telex, teletex,
URI/URL/FTP, X.400).
The address can be used independently of the business partner.
The address is an object in itself and offers interfaces. The business partner is based on
these, and offers corresponding business partner interfaces.
The standard address is always maintained in the "Address" screen.
As of release ERP2005, the standard address of a business partner is no longer portrayed
using the indicator XDFADR in table BUT020. This indicator is obsolete and you can no
longer specify it on manual entry. With effect from Release 6.40, the standard address is
portrayed with the address use XXDEFAULT. If you want to use addresses on a time basis,
you can create different standard addresses for different periods. For each time, you can
specify one address as standard address for the business partner.
17
Address Management: Additional Functions
Standard address
Street / House number Main Street 138
Postal code / City 15317 McMurray
Country US Region PA
.
.
. Valid
Valid combination?
combination?
Postal check (postal code, city, street)

Tested against regional structure in ERP
Use of external software by way of BADIs (Business Add Ins)
Check for duplicates (error-tolerant)

Search (error-tolerant)
To date, SAP uses software provided by the company UNISERV to carry out the above
checks. Interfaces provided by the company Paricon make the link to Central Address
Management. Integration with other software providers is also planned.
Integration is guaranteed by BADIs (Business Add Ins). BADIs are open interfaces that can
be created at every level of a multi-level system landscape (ERP, country versions, IS
solutions, partner, customer and so on).
Examples of checks:
Postal check: Postal codes, cities and streets, and combinations of the same, are checked for
consistency. To activate the central address management please review the Notes 098050 and
132948 via OSS.
During the check, missing elements are added. For example, if only the city has been entered,
the postal code will then be added
When you create and change a business partner, you are offered a number of phonetically
similar, existing partners for comparison purposes. In this way you avoid creating the same
partner more than once.
Error tolerant search means, that you can search for duplicate business partner entries using
the PF4 ‘search’ function.
18
Duplicate Check Business Partner
Duplicate Check:
First name/ Name 69115

Hans Miller
Miller
Street / Number Main street 138
Zip Code / City SW1
SW1 N8
N8 London
Similar
SimilarBusiness
Businesspartner
partner
Franz/ Miller/Main Street/138/SW1 N8/ London

Hans/Millar/Main Street/138/SW1 N8/ London
From Release ERP 2005 you can check the existence of duplicate business partners during
creation with transaction FMCABP.
In the customizing you can define rules (name, address, bank details), which are used by the
system to identify relevant duplicates.
19
Master Data
Business Partner
Contract Account
Contract Object
20
Contract Account: Structure and Function
Contr. Acc. Category
Contract = Grouping for:

Account
1. General Data
• CA name
• Account Management Data (Interest,
Clearing)
2. Payments
• Payer
• Incoming/Outgoing: Bank, Card,
Payer, Lock
3. Dunning/Correspondence
• Invoicing
• Dunning
• Correspondence control/dunning/lock
• Add./alt. recipients
For posting a document, a contract account must be assigned to a business partner.

A contract account within PSCD represents a sub-ledger account and is necessary for open-
item accounting within PSCD. It is also a unit to group postings for the business partner.
The contract account category determines the following contract account attributes:
Whether you are allowed to assign only one business partner or more than one to a contract
account.
Whether you are allowed to assign only one contract or more than one.
Whether you are allowed to maintain a contract account online.
The number range that is allowed for external or internal number assignment.
Whether it is a one-time account.
The editing screens or data fields that you can use to edit the contract account.
Cross-partner data: The key under which the contract account is managed in the R/3 system
and under which it may have been managed in an operational system.
You can use the method “BAPI_CTRACCOUNT_EASYCREATE” to create a contract
account with sample values for external creating of contract account.
21
Contract Account: Company Code Group
Contract Account: Property Tax
General data Payment / Taxes Dunning/Correspondence
Payment data / General
Company Code Group : BS01

Standard Company Code : BS02 Mandatory
Payer :
Paid by :
Owner bank details :
N:1
BS01: Group Company Code BS04: Paying Company Code
N:1
BS01: Company Code

BS02: Company Code
BS03: Company Code
The company code group includes all company codes that are permitted for posting to a
contract account. One company code group is assigned to each contract account. Company
code groups can overlap. This means, for example, you can have a group G1 that consists of
company codes 0001, 0002, and 0003, and group G2 that consists of 0001 and 0003.
Using the new event 1010, you can check whether a company code group is permitted in a
contract account. This enables you to prevent, for example, that cross-country groups (in
certain contract accounts) are used.
22
Contract Account: Company Codes
Company Code Group:
Includes all company codes that are permitted for posting to a contract
account.
The event 1010 allows you to check, if the company code group is
permitted or not in the contract account.
Paying Company Code:
Is responsible for payment transactions. House banks and payment

methods have to be defined per paying company code.
Standard Company Code:
Used for all postings for which no company code can be determined by
other means.
Paying company code

Exactly one paying company code is always assigned to each company code group. A
paying company code is responsible for payment transactions. You have to define house
banks and payment methods for paying company codes. Several company code groups can
have the same paying company code. The paying company code does not have to be in the
company code group itself.
You can also specify the paying company code in a business partner item. In this case, this
specification overrides the paying company code determined via the company code group of
the contract account. If a paying company code specified in the line item is in a different
country to the paying company code determined via the contract account, you also have to
specify a payment method in the line item. In this case you cannot use the payment methods
from the contract accounts since they refer to a different country.
Standard company code
One standard company code is assigned to every contract account. You use the standard
company code for all postings for which no company code can be determined by other
means (for example, for payments on account).
23
Master Data
Business Partner
Contract Account
Contract Object
24
Contract Object: Configuration
Contract Object Category

Contract Object Type
Contract Object
= Grouping for:
• Number Range
• Internal/external Number
Assignment
• Field Modifications
• Enabling (Yes/No) specific rules for
AP/AR Data (Correspondence)
You specify the name of the contract object and contract object type to which it is assigned
in the basic data. A contract object type determines a contract object’s grouping
characteristics. You determine the attributes of a contract object type in the PSCD
Customizing.
Contract objects can be differentiated using contract object types.
Contract Object Category: See next slide.
25
Contract Object: Master Data Structure
Business Partner/Contract Account
A/P and A/R Data
Contract Object 1. Relationship Data

2. Payment Data
3. Correspondence
4. Inbound Correspon-
dence
1. Administration Data
Object Number
Object Type
Short Text
Contract Object
2. Basic Data
Category BDT
Business Partner independent
In the Business Data Toolset you define the data structure of a contract object type. This is
called the contract object category. In the context of the BDT application object "contract
object", the term "category" is used as a synonym for "business partner role" (BP role).
SAP delivers three contract object categories ( „PAAC with access to business partner and
contract account“ , „PSOB without access to business partner and contract account “, „PSDD
only by Campus with access to business partner, contract account and due date schedule“).
Accounts Receivable and Payable Data are not compulsory. But NOTE: As soon as postings
have made these data cannot be changed anymore. The use of Contract Objects without
employing the use of a Business Partner and a Contract Object for TRM scenario’s is not
typical.
26
Contract Object: Configuration
Basic Data Contract Object Type
Contract
ContractObject
Object
Business
Business Partner
Partner 11
Business Partner 2
Contract
Account
10 Contract
Account
20
You can create a contract object directly or use an existing template or a sample which is defined
in customizing. This takes you to the Contract Object screen:
Enter the name of the contract object in the basic data and choose A/R and A/P Data with or without
sample. This will take you to the accounts receivable and payable processing screen for the contract
object. To use the A/R, A/P data is only possible by using a contract object type with the category
“PAAC or PSDD” , which is defined in customizing.
On the Basic Data tab ride, specify a partner relationship by assigning a business partner and a
contract account category. There you can create a new business partner and contract account if
necessary .
If you want to have a different control logic for the contract object from the one assigned in the
contract account, proceed as follows:
To define an alternative correspondence control, set the “Activate Correspondence Parameters for
Contract Object” indicator on the Correspondence tab ride and specify the correspondence data you
require.
To define alternative invoicing, you must set the “Activate Correspondence Parameters for Contract
Object” indicator and the “Separate Invoicing” indicator on the Correspondence tab ride and specify
an invoice type.
To define an alternative payer or payment recipient, set the “Activate Correspondence Parameters”
for Contract Object indicator on the Payment Data tab ride and enter the relevant business partner.
You can flag individual records on contract account data assigned to a contract object as Obsolete,
thereby excluding them from further contract object processing (for example, in transaction
PSOBWORK).
Before you set this indicator, make sure that there are no open items or open inbound
correspondence on the specified record for contract account data (in other words, for the specified
business partner, contract account category and contract account). You set the indicator “Obsolete”
on the tab page Basic Data on screen area “Administration Data”. The data records on contract
accounts flagged as obsolete are hidden from all F4 help and overview lists for contract objects. It is
the responsibility of administrators to process such entries in transaction PSOBWORK who have
special authorization with F_KK_SOND for activity '24'. Administrators can process obsolete contract
account data, under Extras Administration Show Obsolete Data or Hide Obsolete Data.
In Customizing you can define whether more than one business partner may be assigned to a
contract object for each contract object type. As each business partner assigned corresponds to a
record on tax data for PSCD, at the same time you will be able to limit the number of assigned
contract accounts as soon as this option is active.
27
Facts: General Introduction
Contract
Contract Object
Object Types
Types
Plant:
Plant: Location:
Location: Vehicle:
Vehicle:
-Category
-Category -Street
-Street -cylinder
-cylinder
-Size
-Size -Town
-Town -capacity
-capacity
-Employers
-Employers -Employers
-Employers -Number
-Number ofof axles
axles
-Emission
-Emission -Emission
-Emission -Emission
-Emission Class
Class
-….
-…. -….
-…. -….
-….
Facts
Facts offers a framework that allows customers to customize business repository

objects time-dependently.
This is done by setting up attributes in Customizing and linking them to the business
repository object during master data maintenance.
In Public Sector Collection and Disbursement facts are used to make calculations
and reporting on contract object level. Using facts enables evaluation of tax
assessment cases with different tax assessment objects.
28
Facts Structure
Plant:
Category Category
Size Size Plant Plant
Plant
Employers Employers
….
Location Location
Location
Location:
Street
Town Address
Employers Employers
….
Fact Fact Fact

Categories Types Sets
Fact Categories
are the smallest entity of meaningful information to describe a piece of data such as a simple type
in the SAP data dictionary.
Once categories are grouped in a Fact Type they will be contextualized in a business
environment.
The qualifier represents a piece of data that completes the meaning of the data, for example the
unit of measure or the currency or maybe the type of business partner.
All tables are client dependant.
Fact Type
It is a collection of Fact Categories encapsulating data in a meaningful business context.
Example: dates on which amounts were paid by a customer.
Fact Set
It is a collection of Fact Types that are based for a framework on which a Business Repository
Object will utilize them.
Example: Fact Category of dimensions, plus the dates the owner has paid an amount (as above).
One fact set is assigned to a Contract Object Type.
29
Facts: Additional Information
Facts offer additional functions:

Facts can be time-dependent
Facts can be used in the PSCD Billing
Business Rules Framework can select facts
Facts can be used for Calculations and Validations
30
Master Data
Business Partner
Contract Account
Contract Object
31
Overview Revenue Type
Different Tax Types have different Forms, Rules, Calculations

and Posting rules, etc… these tax type identifying factors are
assigned to the Revenue Type.
Personal Income Tax Corporate Income Tax Value Added Tax
Form A Form B Form C

Rules Set A Rules Set B Rules Set C
Calculation A Calculation B Calculation C
Posting Rules A Posting Rules B Posting Rules C
Revenue Type
The revenue type represents the tax type.

From the revenue type the tax forms and rules are derived.
32
Overview Period Key
1/2007 6/2007 12/2008

annually
half year
quarterly
monthly
The Period Key is independently from the posting periods

of FI or PSCD and describes the begin and end of a tax
period for which the taxpayer has to pay taxes.
01.01.2007 31.12.2007 03/2008

Tax Period: 2007 Open Posting Period in FI
33
Revenue Type and Period Key
Revenue Type
Contract Object Type

Form
Rules Set
Calculation
Posting Rules
….
Contract Object
Period Keys
More detailed information about the Revenue Type is given in the next chapter.
The Periods Keys for which the Revenue Type is used, where assigned to the
Revenue Type
The Revenue Type is assigned to the Contract Object Type.
Several Revenue Types may be assigned to a Contract Object Type.
The assignment is time-dependent based on the Period Key.
34
Master Data
Business Partner
Contract Account
Contract Object
35
What Is WebDynpro?
WebDynpro
Is SAP‘s development environment for creating professional
UIs for business applications
Includes sophisticated runtime services
Minimizes manual coding because of its model-driven
approach
Uses visual tools to design and reuse UI components
Is based on a powerful and flexible Model View Controller
architecture that ensures a clear separation between UIs and
backend services
Gives developers full control of the generated code at all
stages of the development process
Value Proposition Of WebDynpro

Separation of frontend / backend
Decoupling the UI from the backend allows multiple user interfaces for the same backend
business objects and process logic
Greater reuse of most valuable asset (business logic)
Team development thanks to integration into the SAP Development Infrastructure
Protection of investment
No longer need device-specific programming models (one fits all)
Supports browsers, smart clients, mobile devices
Configuration of user interfaces from very few powerful, pre-built user interface
components
“Template”-based, consistency-enforcing, highly efficient UI creation environment
36
Positioning
SAP NetWeaver ’04

First synchronized release that comprises Web AS, WebDynpro and
SAP Enterprise Portal in one seamless platform
Proves that NetWeaver is much more than the sum of its components
SAP Enterprise Portal

SAP's strategic platform to access any kind of application, information
and service using a Web browser
WebDynpro
SAP's strategic approach to building professional user interfaces for
Web applications running in SAP Enterprise Portal
SAP WebApplication Server

SAP‘s strategic runtime environment for both ABAP and Java
applications
Positioning WebDynpro and Enterprise Portal 6.0

SAP Enterprise Portal is SAP's strategic platform to access all SAP applications via a Web
browser
WebDynpro is SAP's strategic approach to build professional UIs for applications running in the
browser
WebDynpro is SAP's strategic approach to build content for SAP Enterprise Portal
Seamless Integration with NetWeaver ‘04
Portal eventing
Wizard for WebDynpro applications
Same look and feel for controls (unified rendering)
Unified branding (by portal theme)
Support for session management
Unified User Management
Enhanced navigation possibilities (Object Based Navigation, Dynamic Navigation, Navigation by
URL, ...)
37
WebDynpro Architecture
SAP NetWeaver
WebDynpro
Developer Studio Tools
ESS
ERP
Application
MSS Data
Internet Application
ESS
Browser Application
BAPI
WebDynpro WebDynpro ESS
/ RFC
ESS
BAPI
Client Runtime ESS
BAPI
BAPI
SAP J2EE Server
R/3
SAP Web Application Server Enterprise
38
Pattern-Based UI Design
Three levels of UI patterns

Controls Controls
Atomic elements in the layout,
constitute the look & feel
Components
Reusable, task-oriented building
blocks Components
Floor plans
Screen layout, interaction, and
semantics for a generic application
Consistent user interfaces
Faster learning process;
Less knowledge required Floor plans
Less development, less
maintenance
Developing a user interface =
Parameterize a business process
39
Guided Procedure to create the Master Data
Steps to register a Taxpayer
1 2 3 4 5
Enter data Select Revenue Types Create Registrations Review and Save Completed
Designed as
Person
WebDynpro Application
Organization
Group
The Taxpayer Registration is designed as WebDynpro Application. WebDynpro is

SAP's strategic approach to building professional user interfaces for Web
applications.
WebDynpro:
Is SAP‘s development environment for creating professional UIs for business applications
Includes sophisticated runtime services
Minimizes manual coding because of its model-driven approach
Uses visual tools to design and reuse UI components
Is based on a powerful and flexible Model View Controller architecture that ensures a clear
separation between UIs and backend services
WebDynpro offers a consistent and user-friendly frontend through UI elements
based on Unified Rendering
UIs in different applications are consistent thanks to the use of patterns. Therefore
minimal end user training is required and the improved usability increases
productivity. It follows accessibility standards (especially screenreader support)
40
Step 1: Enter data
General Data
Title Business Partner
First name Last Name
Street House Number
Postal Code City
Country Region
Telephone
E-Mail
Identification Numbers
ID Type ID Number Description
Bank Data
Country Bank Key Bank Account ID
Payment Cards
Card ID CardType Card Number Card Holder Issuing Bank Valid from
Check
Check for
for Duplicates
Duplicates Reset
Reset Next
Next Step
Step
Prerequisites:
Sample Values for CA and CO defined
Fact Type RG01 has to be assigned to the relevant Fact Set
41
Step 2: Select Revenue Types
Revenue Type Tax Period No. of Registrations From Tax Period To Tax Period
PIT 2007 1 2006 2008

VAT 0701 1 0701 0812
Previous
Previous Step
Step Next
Next Step
Step
42
Step 3: Create Registration
Revenue Type Tax Period No. of Registrations From Tax Period To Tax Period
PIT 2007 1 2006 2008

VAT 0701 1 0701 0812
Taxable Object Create

Name
Card ID Incoming Incoming Payment Method
Previous
Previous Step
Step Next
Next Step
Step
43
Step 4: Review and Save
Overview of
all entries
Previous
Previous Step
Step Check
Check Next
Next Step
Step
44
Step 5: Completed
Register Taxpayers
1 2 3 4 5
Enter data Select Revenue Types Create Registrations Review and Save Completed
Taxpayers: 5200000052
Contract Account: 120000000012
Contract Object: 00000003000000000012
45
Master Data
Business Partner
Contract Account
Contract Object
46
Contents:
Positioning BDT
BDT Development
47
What exactly is the Business Data Toolset (BDT)?
In General Advantages
official tool for screen design different screens can be associated

and business process flow to different user groups
management standard objects can be copied
enables customers to extend runs in batch and dialog mode
SAP standard applications
easy BRF integration through
without modification
function module call
„ICL_RAISE_EVENT“
Possibilities unified „Look and Feel“
multi instance compatible
Design of new customer screens
„slim“ BDT in batch mode
Extensions or standard process
additions with customer coding
The BDT (Business Data Toolset) is a toolset for implementing master data and
transaction data maintenance.
Beside the dialog the BDT also provides generic services for consistently recurring
requirements such as occur in change document lists, field groupings and
archiving/deletion programs.
The BDT offers generic parts of the functionality and calls the applications using
predefined interfaces (events in control tables). The applications themselves
introduce application-specific enhancements, such as function modules for writing
and reading application tables.
Note: Beside the SAP Business Partner the BDT is used for maintaining several
application objects. You can find a list of these objects in SAPNET, Alias BUPA.
48
BDT – Configuration of individual business processes
With
With customizing
customizing you
you can:
can:
Move
Move screens
screens Fields (smallest unit)
Hide,
Hide, reorder
reorder sections
sections Field groups
Hide,
Hide, view
view fields
fields Views – „ABAP sub screens“
…
… Sections
Screens
Screen sequences (largest unit)
49
BDT – Positioning
Application Objects
SAP Contract
Bank Account SAP BP Further
BP Relations Account
(BKKA) (BUPA) Objects
(BUPR) (PSCD)
BDT
SAP Basis (DDIC, development environment, ABAP...)

The BDT is based on the SAP-Basis, this means the Development Workbench and
the Data Dictionary. BDT it’s self is developed in ABAP.
The BDT is a layer between SAP-Basis and the applications. The development
system inside SAP is the application basis. BDT has been shipped with all SAP
systems since release 4.6A.
50
BDT – Development Areas
Applications
SAP BP SAP BP SAP BP
Central
Data
CRM
Data
Customer
Data SAP BP
(BUPA)
Development
Data Dictionary Development

BDT Control Tables
(DDIC) Workbench
The development of a new application in BDT is divided into three steps:

Data dictionary
Creation of a new table or extension of an existing table
Development workbench
Developing of program logic and screens in the Development Workbench corresponding to the
BDT-Events.
BDT control tables
Adding new entries for the application specific enhancements
51
BDT Development – Data Dictionary
Applications
SAP BP SAP BP SAP BP
Central Data CRM Data Customer Data
Table: BUT000 Table: ZZ_...

... ...
... ...
... ...
Append ...
ZZ_... ...
ZZ_... ...
The first step of developing an application for the SAP BP is enhancing the Data
Dictionary.
If you want to add new fields for the Business Partner, you can extend the table
BUT000 by an append structure. But this possibility is only allowed for customers.
SAP applications and development partners should create their own table with the
same key fields like BUT000.
If you want to add new tables for maintaining several values per business partner (for
example maintaining the hobbies of a BP in a table control), you have to create a
new table in the Data Dictionary.
52
BDT Development – Development Workbench
Function
Group
Function Modules
ISSTA
ISDAT Events for each

application
ISDST
Program logic
...
GET Events for

Screens PBO-Module Collect tables
• PBO ...
• 0010 First Contact
• ...
..._PBC_.
. Events for each
PAI-Module ...PBO_..
view
• PAI ..._PAI_..
• ...
...
The second step has to be done in the development workbench. Each application
develops in its own function group.
The fields of an application can be divided into different screens. Normally you should
combine attributes on one screen, which belong together in the dialog and which are
checked together.
Note: Every application screen must have the category subscreen.
You also have to develop PBO- and PAI-Modules for the screens. But the logic
inside is very restricted, especially the field checks have to be implemented in PAI-
function modules.
Depending on the kind of extension you have to write some function modules for
BDT events. The BDT has different kind of events
Events for each application
For example for reading and writing the database tables of an application.
Events for each table
The responsible application writes these function modules for exchanging the actual field values
with other applications.
Events for each view (screen)
For example the field checks have to be implemented in the PAI function module.
53
BDT Development – Control Tables
The BDT uses control tables for
Applications
Screen layout and screen sequence
Program logic (events)
Function codes
The BDT control tables are the connection between the BDT and the applications.
Every application notify itself by adding an entry to the BDT application table.
The BDT has different control tables for
Screen layout and screen sequence
Program logic
Function codes.
Every application should add its own entries to these tables to notify the BDT about
the application specific enhancements.
If you assign the single role SAP_CA_BP_DEVELOPER_AG to your user, you can
access the BDT settings for the Business Partner via the SAP Easy Access menu.
54
BDT – Screen Layout Concept
Change Partner: Address A screen contains one or

more sections
View 1 A section contains one or
Section 1 more views
View 2
A view is presented by a
subscreen
View 3
View 4 Section 2 Screen 1
View 5
View 6
View 7 Section 3
View 8
In the Business partner maintenance every BDT screen is represented by a tab

page. The title of the tab page can be determined by the application.
Every screen can contain one or more sections. Around every section you will see a
frame with a title. Also the title of the section can be maintained.
Every section itself can contain one or more views. A view is technically represented
by a subscreen.
All these entities and the allocations between these can be maintained in BDT control
tables.
With this technique it is very easy to
Combine subscreens of different applications on one screen
Change the screen layout
55
Configurability: Customizing Screen Layout
Configuration via
Drag&Drop
(Visual Basic)
Screen layout and

screen sequence
Technique
Subscreens
Generation of
screen containers
Because mid-sized customers in particular tend to suppress most of the standard

SAP data fields, dialog maintenance becomes tedious when you still have to go
through screen after screen on which only one or two fields are relevant. Switching
screens often slows down data entry considerably.
As a result, it was decided to make screens configurable in order for customers to
both tailor entry screens to their individual needs and keep the number of screens to
a minimum.
Screen layout and sequence can be configured by application developers and/or
customers. While developers use BDT control tables to modify screens, customers
can take advantage of a configuration tool developed using Visual Basic for changing
standard SAP screen layout and sequence with the drag&drop method.
56
Master Data
Business Partner
Contract Account
Contract Object
57
Check digits
Check digits
allow for the validation of

Business Partner numbers
Contract Account numbers
Contract Object numbers.
Prerequisite: Internal numbering!
Check digits allow for the validation of contract account and / or business partner numbers
and may be used in conjunction with incoming payments, for example. In order to use check
digits, numbering of contract accounts and business partners, respectively, must be of type
internal.
For example, if a customer sends in a payment for his account and he has entered his
contract account number in the note to payee field incorrectly, the check digit algorithm has
the ability to automatically correct the error (assuming the error does not involve several
numbers). SAP does not provide the algorithm but does provide the necessary events.
Business Partner: You add the check digit procedure by way of event 1051. Sample function
module FKK_SAMPLE_1051_2_CHECKDIGITS for two check digits is supplied by SAP.
Contract Account: Leading check digits can be utilized when creating contract accounts and
may be of one or two digits in length. Event 1019 and function module
FKK_SAMPLE_1019_2_CHECKDIGITS (delivered sample function module that uses two
check digits) is used for contract account check digit processing.
Contract Objects: With a customer enhancement you can implement a check digit procedure
for the contract object numbers. See for more information in the example function module
FMCA_SAMPLE_P500.
SAP offers an interpretation rule for contract objects based on the Modulo 11 method
(FMCA_MODULO11_DIGIT_P500). Additionally this method can be used for the
interpretation of the note to payee on the electronic bank statement.
58
Locks
Processing Locks can be entered on the level of a

Contract Account
Contract Object
Line Item
Processing Locks can be set for an unlimited or for a

limited period.
Mass locks can be…

Set (transaction FKLOCK2)
Deleted (transaction FPLKDEL)
Locks on the contract account: For dunning, posting, invoicing, correspondence dunning, interest
calculation, incoming payments and outgoing payments respectively.
Locks on the contract object: Incoming and outgoing payments, inbound correspondence dunning
You can set the lock for a limited period or set multiple locks for each business transaction.
NOTE:
If you only specify one lock reason, the lock will be for an unlimited period of time.
If you only enter one lock reason, you can change or delete this. If multiple or limited-time locks have been
set, press the arrow key to make changes. You can then make changes in the dialog box that follows.
If you have set multiple or limited-time locks, only a ~ will be shown in the Lock field. In this case, choose the
arrow key to display the locks.
To analyse which locks are activated on the different levels you can use the transaction FPLKA under
Periodic Processing For Contract Accounts Evaluation of Business Blocks
You can create processing locks with transaction FKLOCK2 (Menu : Periodic Processing For
Contract Accounts). From the selection criteria Business Partner, Contract Account, Contract,
Company Code, you can set mass locks for a combination of Lock Category, Process and Lock
Reason. To delete mass locks, you can use transaction FPLKDEL.
59
Maintenance of Bank & Credit Card Data
Requirement: Creation of a new bank detail that should be used for

outgoing payments only…
Business
Business partner
partner 400000131
400000131
All steps in one
Bank
Bank details:
details:
-- 0001
0001 Deutsche
Deutsche Bank
Bank FPP4
-- 0002
0002 UBS
UBS
- 0003 Credit Suisse
Credit
Credit card
card details
details ::
-- 0001
0001 Visa
Visa
Contract
Contract account:
account: Property
Property Tax
Tax Contract
Contract account:
account: Corporate
Corporate Income
Income Tax
Tax
Bank
Bank details
details incoming:
incoming: 0001
0001 Bank
Bank details
details incoming:
incoming: 0002
0002
Bank details outgoing: 0003 Bank details outgoing: 0003
Credit
Credit card
card details
details incoming:
incoming: 0001
0001 Credit
Credit card
card details
details incoming:
incoming: 0001
0001
Credit
Credit card details outgoing: 0001
card details outgoing: 0001 Credit
Credit card details outgoing: 0001
card details outgoing: 0001
60
Maintenance of Bank & Credit Card Data
The transaction FPP4 allows you to:

Create new bank details
(Determination of new bank detail ID in event 1053)
Change / delete existing bank details
Create new payment card details

(Determination of new card detail ID in event 1054)
Change / delete existing payment card details
Create customer contacts
Print confirmation letters
Control follow-up actions (i.e. reverse dunning notice, remove lock,

…)
Make further changes to the contract account (event 1083)
FPP4 makes changing business partner-related bank data much easier. In the
transaction Maintain Payment Data, you can, for example, change the bank details of
a customer who changes from being a cash payer to a direct debit payer
simultaneously in the business partner master record and in dependent objects, such
as the contract account.
You can also control follow-up actions, such as reversing dunning notices, by means
of flexible rules.
If you set the indicator Create Bank ID in the client-specific settings in Customizing,
in event 1053 you can determine new bank details ID for the business partner
concerned.
If you set the indicator Create Credit Card ID in the client-specific settings in
Customizing, in event 1054 you can determine a new payment card ID for the
business partner concerned.
With a function module processed in event 1083 you can make further changes to
the contract account when you save the data. In this event, you can, for example,
change the field Planning Group in the contract account if a customer changes from
being a cash payer to a direct debit payer.
61
Maintenance of Bank Data
Create, Change, Delete
New Bank
Details
Payment
Method
Selection of
Contract Acc.
Selection of
Actions
62
Business Partner Overview
The Business Partner Overview is a flexibly configurable transaction for displaying business
partner data.
You can assign a configuration to individual users in user maintenance or define it as
standard.
The contract accounts and contract objects of a business partner are displayed in hierarchies
in a tree structure. The contract objects are subordinate to contract accounts. The user can
navigate through the tree by double clicking and using environment menus. Some data of the
master data object selected is displayed in the upper screen area. The master data
information can be changed by using a customer-defined program and subscreen.
Additional business partner data is displayed in a tab . You can define the sequence and
display of the tab pages.
Data procurement is carried out using events. You can replace the standard function
modules with user-defined function modules.
The user interface contains a range of links to other transactions. Additional functions which
can be set in Customizing are displayed as push buttons or menu entries for calling up
maintenance functions.
You define the settings for the business partner overview in Customizing under:
Configure Business Partner Overview
Maintain Additional Functions for Business Partner Overview
63
Archiving: Reasons
Data Archiving
removes mass data from the database that the R/3 System no longer needs
online, but which must still be accessible at a later date if required.
There are both technical and legal reasons for archiving application data:
• Resolve memory space and performance problems caused by large
volumes of transaction data
• Make master data easier to handle and to keep up-to-date
• Ensure statutory data retention rules are observed
• Ensure that data can be reused at a later date, for example, in new product
development
64
Archiving: Process
Archiving session
Database
1
Archive Files
Documents Archiving Object
2
3
Archiving is carried out in three steps:

Step 1: Create Archive File(s)
Depending on the data volume you have to create one or more archive files.
Step 2: Store Archive Files
Step 3: Execute Delete Program
After closing the first archive file, the archive management system creates a new archive file and
continues with the archiving process. While this happens, another program reads the archived
data from the completed archive file and deletes it from the database. This procedure guarantees
that only data that has been correctly saved in the archive file is deleted from the database.
The documentation/application helps gives a detailed description of the customizing prerequisites
for each archiving object.
65
Archiving: Use
You can archive the following objects:

Business partner
Contract account
Contract object
Documents
Payment lots
Returns lots
Returns history
Dunning history (TA: dunning notices)
Correspondence
Invoice history
Check management
Customer contact
Documents are archived per document type according to customizing settings.

Archiving and/or deletion of certain object is triggered via the transaction SARA or via the
menu path Periodic Processing Archive Data. There are the following archive-objects in
PSCD:
Business Partner: CA_BUPA
Contract Account: FI_FICA
Contract Object: FMCA_PSOB
Documents:FI_MKKDOC
Payment lots: FI_MKKPAYL
Returns lots: FI_MKKRET
Returns history: FI_MKKREHI
Correspondence: FI_MKKCORR
Dunning history: FI_MKKDUNN
Invoice History: FMCA_INVH
66
Exercise
Unit 02: Master Data
Topic: Master Data
67

02 0 TRM PSCD Master Data

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

02 0 TRM PSCD Master Data

Загружено:

Авторское право:

Доступные форматы

Agenda

Master Data Installment Plans / Promise to Pay

Transactions Security Deposits

Payment Run and Transfers Overview Business Rule Framew.

Clearing Control / Ac. Maint. Financial Customer Care

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 2

After completing this unit, you will be able

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 3

Revenue Type Overview

WebDynpro for Taxpayer Registration

Business Data Toolset

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 4

One view on business partner Central Master Data

One person – many processes Business Partner role concept

Connection to other persons / entities Business Partner relationships

Additional information for specific Extensibility

Cooperation with all existing Well-defined Interfaces

Business Requirements TRM Solution

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 5

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 6

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 7

Contract Person, thing or intangible

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 8

Minimum Structure for Master Data in PSCD

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 9

Using contract objects as PAYMENT REFERENCE for revenues / payments

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 10

Using contract objects as an OBJECT for revenues and payments

Corporate Value Personal

Contract Licenses Job A Job B

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 11

Aggregation of Contract Accounts

Contract CIT VAT PIT PIT

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 12

Payment card Payment card ID (Payment card ID)

Corr. control (Corr. Control)

Corr. variant (Corr. Variant)

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 14

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 15

Business Grouping for

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 16

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 17

Central address management allows different addresses to be assigned to a business

Postal check (postal code, city, street)

Check for duplicates (error-tolerant)

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 18

First name/ Name 69115

Franz/ Miller/Main Street/138/SW1 N8/ London

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 19

Revenue Type Overview

WebDynpro for Taxpayer Registration

Business Data Toolset

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 20

Contr. Acc. Category

Contract = Grouping for:

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 21

For posting a document, a contract account must be assigned to a business partner.

Contract Account: Property Tax

General data Payment / Taxes Dunning/Correspondence

Payment data / General

Company Code Group : BS01

BS01: Company Code

SAP AG 2008, Public Sector Collections and Disbursements / Master Data / 22