ISU Master Guide All PDF

4/11/2019
Master Data
Generated on: 2019-04-11
SAP ERP | 6.18.12
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/11/2019
Master Data
Purpose
This component contains data for the Utilities Industry (IS-U) component that remains unchanged over a long period of time.
The graphic below illustrates the master data and shows how the various objects are related to each other.
Master Data in IS-U
There are two different types of master data:
4/11/2019
Business master data and technical master data
Business master data includes:
Business partner
Contract account
Contract (billable service)
Service provider
Non-billable service
Technical master data includes:
Grid
Point of delivery
Connection
Connection object
Technical installation
Premise
Device location
4/11/2019
Installation
Device
SAP Business Partner

De nition
Organization ( rm, branch office), person or a group of persons or organizations in which your company has a business interest.
Use
You can create and manage your business partners centrally for different business transactions.
This is of prime interest if a business partner plays different roles for a company, such as sold-to party and ship-to party.
You can create a business partner in different business partner roles. During the course of the business relationship, the
business partner can assume other business partner roles. You do not need to create the general data, which is independent of
a business partner's function or of application-speci c extensions, again in each case for this business partner. This prevents
data being created and stored redundantly.
Structure
You can use the following basic elements, which form part of the business partner data:
Business Partner Concept
Concept Remark
Business Partner Category The data that is available for your business transactions depends
on the business partner category .
Business Partner Role A business partner can take on different business partner roles ,
which allow different views of the business partner data depending
on the business function.
Business Partner Relationship A relationship connects two business partners and is characterized
by the business partner relationship category .
Business Partner Group Hierarchy You can represent the structure of an organization using the
business partner group hierarchy
Integration
For more information on the functions for a business partner, see Processing Business Partner Data .
BP Role Contract Partner

Use
A contract partner is connected with the company through contract accounts and through the conclusion of contracts. Contract
accounts can therefore only be assigned to a business partner and services billed accordingly if you have created this business
4/11/2019
partner in the role of contract partner in the business role MKK for role categoryMKK.
Note
If you want to use business partner roles on a time-dependent basis, make sure that you do not restrict the business role
MKK for role category MKK with regard to time. It must always have a validity from the current data to 12/31/9999.
As a contract partner receives services from the company and has to be billed for these services, you also have to de ne control
and payment data on the contract partner. In addition to bank details, you can enter general data on the contract partner, such
as the business partner type and creditworthiness. Creditworthiness is determined and updated automatically, but you can
overwrite this.
A company must have the following information on a contract partner:
Address: Name, form of address, academic title, name suffixes and pre xes, personal data, street address, postbox
address, communication methods
Control/Payment Transactions: Bank details and general data (creditworthiness)
Relationships: Relationships to other business partners (see Relationship Categories)
Note
Industry Component Utilities
In the Utilities industry component, you can de ne additional data for the contract partner, for example, the following
general data:
Driving license number
Social insurance number (USA)
Employee classi cation
Account category (as default value for contract account)
Integration
Note for the industry component Utilities Industry
When creating a contract partner in the background, you can create a standard customer in Sales and Distribution (SD). The
system uses a pre-de ned sample customer as a template. You can then change the master data of the customer in the
standard system.
You can meet the speci cations for the creation of an SD customer in parallel with the business partner in Customizing for SAP
Utilities under Master Data Business Partner Settings for Creating Standard Customers .
 Example
Some of your customers utilize service or maintenance industries pay charges or sell goods that are processed by means of
orders in Sales and Distribution.
Activities
Processing the Contract Partner
4/11/2019
Business partners in the role MKK can be processed in the SAP menu under Master Data Business Partner . You can process all
the roles of a business partner in transaction BP in the menu of the SAP Business Partner.
You can delete the role MKK as soon as there are no further contract accounts for a contract partner in the system. When you
delete the role MKK, the corresponding entry in the shadow table for this contract partner is automatically deleted.
Tax numbers for business partners
You can de ne any number of tax numbers. You can de ne any number of tax numbers. You assign these to tax number
categories that control the usage and check of tax numbers.
Checking dependencies of master data changes
If you have set the indicator Business Partner Dependency in Customizing for Contract Accounts Receivable and Payable under
Basic Functions Contract Partner Activate Additional Checks for Master Data Changes to Business Partner , the system
informs you that bank details, payment card details, or the address of a contract partner is still used in a contract account if you
try to delete this information. You can navigate to the maintenance of the contract account to remove this inconsistency.
Check digit for contract partners
When you create a contract partner, you can add a check digit to the contract partner number. The following conditions have to
be met in order to use this procedure:
You add the check digit procedure using event 1051. Sample function module FKK_SAMPLE_1051_2_CHECKDIGITS for
two check digits is supplied by SAP
The contract partner is created with internal number assignment.
The number range is con gured such that it begins with a leading zero (check digit procedure with one check digit) or with two
leading zeros (procedure with two check digits).
Shadow table for business partners
If you have a large dataset of business partners, you can improve the performance of mass runs by using the FI-CA shadow table
that contains the most important business partner data. If the shadow table is active, the system automatically maintains the
shadow table during business partner maintenance. If you want to use the FI-CA shadow table:
1. 1.Activate the function in the Implementation Guide for Contract Accounts Receivable and Payable under Technical
Settings Activate Performance Improvement for Mass Runs by setting the relevant indicator.
2. You can now create the shadow table using mass activity GPSHAD_NEW.
3. If you have used planned changes for SAP Business Partner before a release change and the shadow table has already
been lled, before you run a mass activity for the rst time you have to run report RFKKGPSHUPDATE. This report
invalidates the entries in the shadow table for business partners for whom there are unimplemented planned change
documents. This prevents obsolete data being read from the shadow table.
To revalidate the invalidated entries in the shadow table, you have to run mass activity GPSHAD_UPDATE. This improves
the performance of the read accesses to business partner data since, for invalidated entries in the shadow table, the
system has to read data from diverse database tables of SAP Business Partner.
4. To keep the content of the table up-to-date, schedule report BUPTDTRANSMIT regularly for application MKK. This report
recognizes whether there have been changes to master data due to moves and re ects these in the shadow table.
Data Cleansing
4/11/2019
The functions described in the Data Cleansing section of the documentation for SAP Business Partner are not supported for FI-
CA due to the data structure.
See SAP Note 871094 .
Changes to Payment Data

Use
Changing bank data and payment card details in the master record of a business partner.
Integration
You can change payment data in the master record of the business partner and in dependent objects simultaneously. For
example, you can change the bank details of a customer who changes from a cash payer to a direct debit payer in his business
partner master record and his contract account.
Note for the industry component Insurance
You can also change payment data in the relevant insurance object-partner relationships.
Note for Public Sector Contract Accounting
You can also change payment data in the relevant contract-object-partner relationships.
The maintenance of customer contacts is not supported.
Features
In the transaction Change Payment Data , you can do the following centrally for a business partner:
Create new bank details/payment cards
Change existing bank details/payment card data
Delete bank details/payment cards in the contract account and subsequently in the business partner master record
Create customer contacts
Print con rmation letters
You can control follow-on actions, such as the reversal of dunning notices (or ending dunning runs in industry component
Insurance ) using a exible set of rules. This includes:
Deletion of bank details/payment cards from the master record of the business partner
Deletion of locks from contract accounts, items, and industry objects
Reversal of dunning notices (or ending of dunning runs in the industry component Insurance )
Reset returns activities
The processing takes place in three modes:
Mode Function Call Using Button
4/11/2019
Mode Function Call Using Button
Create Create new bank details/payment card ( Create )
Change Change existing bank details/payment card ( Change )
Delete Delete existing bank details/payment card ( Delete )
Making System Settings

Use
To be able to create and process payment cards and bank details in the transaction Change Payment Data , you have to make
the required system settings in Customizing for Contract Accounts Receivable and Payable under Basic Functions Contract
Partner Changes to Payment Transactions . Also make the following system settings as described.
Procedure
The system saves bank details/payment cards with a unique ID in the master data of the business partner. As standard, in the
transaction Change Payment Data , the rst ID of the bank details/payment card is created with 0001, the second with 0002.
You can change this in event 1053 or 1054. If the system is unable to determine an ID, the user is requested to enter a new ID in
a dialog box (see documentation of function module FKK_EVENT_1053_DIAL).
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, de ne that the eld Posting Control Group changes in the contract account if a customer
changes from being a cash payer to a direct debit payer.
With a function module processed in event 1084, you can limit the objects (contract accounts or contracts) that the system
selects for display.
De ne the event modules in Customizing for Contract Accounts Receivable and Payable under Program
Enhancements De ne Customer-Speci c Function Modules . See the documentation for the sample function modules
FKK_SAMPLE_1053, FKK_SAMPLE_1054, FKK_SAMPLE_1083 and FKK_SAMPLE_1084.
Creation of Con rmation
If you want to send con rmations, de ne the form required for the correspondence types 0036 and 0040. To de ne a standard
form proceed as follows:
1. In Customizing for Contract Accounts Receivable and Payable , choose Basic Functions Correspondence De ne
Standard Form Classes for Correspondence and de ne the form class FI_CA_BANK_MAINTAIN for correspondence type
0036, and form class FI_CA_CCARD_MAINTAIN for correspondence type 0040.
2. Create a copy of the standard form FI_CA_BANK_MAINTAIN_SAMPLE or FI_CA_CCARD_MAINTAIN_SAMPLE and adjust it

accordingly.
3. In Customizing for Contract Accounts Receivable and Payable , choose Basic Functions Correspondence De ne
Application Forms for Correspondence and enter the new forms for the correspondence types 0036 and 0040.
For printing con rmations, you have various options in the IMG activity De ne Processing Variants . For more information, see
the Implementation Guide.
Follow-On Actions
4/11/2019
In the Implementation Guide for Contract Accounts Receivable and Payable , under Basic Functions Contract
Partner Changes to Payment Transactions De ne Set of Rules for Follow-On Actions , de ne rules that the system is to use
to trigger follow-on actions for changes to payment data.
In the IMG activity De ne Processing Variants , you can make further settings for the follow-on actions.
Read the documentation for the IMG activities.
Changing Payment Data

Prerequisites
You have the authorizations to change bank details and payment card data. If the existing authorizations are insufficient, the
system terminates processing.
When you display the contract accounts, only those contract accounts for which you have display authorization appear. You can
only select contract accounts for which you have change authorization. If you do not have the relevant authorizations, the
system issues an error message for every action that it could not carry out.
Procedure
1. On the SAP Easy Access screen, choose Master Data Business Partner Change Payment Data .
2. Enter the business partner required and, in the eld Valid From , the date from which the change to the bank/payment
card data is to be valid.
3. Con rm your entries.
4. Choose a change reason.
5. Make the desired changes and save your entries.
The system selects the object to be changed automatically (bank details/payment card) and starts the transaction accordingly.
You can override this setting during processing by choosing the menu function Goto Change Bank Data , or Goto Change
Payment Card Data .
The system selects the program mode automatically. If there are no bank details for the business partner entered, the system
selects the mode Create . In all other cases, the system selects the mode Change . By selecting the corresponding button in the
toolbar, you can change the mode.
Note
In Customizing for Contract Accounts Receivable and Payable , under Basic Functions Contract Partner Changes to
Payment Transactions De ne Processing Variants , you can suppress this automatic selection of the mode for a processing
variant and de ne the object with which the transaction is to start. For more information, see the Implementation Guide.
By choosing the ( Other Partner ) pushbutton, you can switch to a different business partner to maintain the bank data. If you
choose ( Back ) in the standard toolbar, you can also select a different business partner or change the validity date for the
business partner entered and start the processing again.
To save validity data with effect in the future, see also the section Special Features for Changes with Effect in the Future .
Area: Bank Details/Card Data
4/11/2019
If bank details/payment cards already exist for the business partner, these appear in the eld Old Bank Dets/Prev Pymt Card .
You can select the bank details required from the drop-down list or using the pushbutton ( Find ).
In the New Bank Dets/New Pymt Card eld, you enter the new payment data. Or the system displays the selected bank data or
payment card data there.
Area: Contract Accounts
Using the appropriate radio buttons, you rst specify whether this payment data applies only for incoming payments, only for
outgoing payments, or for both.
The following contract accounts appear here:
Contract accounts where the business partner selected is entered as the contract account holder.
Contract accounts where the business partner selected is entered as the alternative payer.
Contract accounts where the business partner selected is entered as the alternative payee.
Contract accounts where the business partner selected is entered as the payer.
Note
If you enter a different date than the current date in the Valid From eld, the system selects the contract accounts
valid from this date. If, for example, the business partner is not the contract account holder, and only becomes the
alternative payer, alternative payee, or payer for the contract account starting from a date in the future, for technical
reasons, the contract account may not be selected under certain circumstances if you call the transaction before this
future date. The system only selects the contract account when you call the transaction for the date when the change
takes effect and the business partner is, for example, the alternative payer.
The system automatically selects certain contract accounts in the list:
Mode Automatic Selection
Create If the business partner has no bank details/payment card, the

system selects all contract accounts. If the business partner has
bank details/payment card, the system does not select any
contract account.
Change The system selects all contract accounts that contain the bank
details/payment card selected. You cannot change this selection.
Delete The system selects all contract accounts that contain the bank
details/payment card selected. You cannot select any other
contract accounts for changes.
You can also select speci c contract accounts manually.
Caution
When you save, the system only transfers the changes for the contract accounts selected.
If you only want to see which changes would be made to the contract accounts when you save, choose the pushbutton Simulate
Changes . The system highlights the elds that would be changed. To exit the simulation mode, choose the pushbutton End
Simulation .
Note
4/11/2019
When you create and delete payment data, the system determines the payment methods automatically and saves these in
the contract accounts affected. See also the documentation for the IMG activity Basic Functions Contract
Partner Changes to Payment Transactions De ne Default Values for Payment Methods.
In addition to the contract accounts, the insurance objects to which a business partner is assigned are also displayed here. The
processing of the items is as described above for the processing of contract accounts. The contract account holder corresponds
to the contract partner in the industry component Insurance (FS-CD).
In addition to the contract accounts, the system also displays the contract objects to which a business partner is assigned. The
processing of the items is as described above for the processing of contract accounts.
Area: Correspondence/Contact
If you set the indicator Print Con rmation , a con rmation is printed automatically when you save.
Note
In the Implementation Guide for Contract Accounts Receivable and Payable , under Basic Functions Contract
Partner Changes to Payment Transactions De ne Processing Variants, you can make different settings for printing
con rmations for a processing variant. See also the documentation for the activity.
Corresponding to the settings of your processing variant, when you save, the system displays a separate window - Print
Individual Correspondence .
You can create the con rmation manually or have it created in a mass run. For creation in a mass run, use the correspondence
types 0036 and 0040 .
You can also enter further data for the contact.
Note
If you set the Display Contact indicator in the Contact area for a processing variant in Customizing for Contract Accounts
Receivable and Payable under Basic Functions Contract Partner Changes to Payment Transactions De ne Processing
Variants , the system displays the elds for the contact in this area. To create a contact when you save, you also have to set
the indicator Create Contact in Customizing.
The contact is also created when the elds for the contact are not displayed.
Special Features of Changes with Effect in

the Future
When you change payment data so that the change takes effect in the future, the system saves the data in different ways. This
dependent on:
The object being processed (bank details or payment card)
The master data affected (business partner or contract account)
4/11/2019
The program mode (create, change, delete)
When you change bank details, the system saves the data in one of these ways:
Creation in the future
The system saves the bank details in the master data of the business partner, whereby the Valid From date is in the future.
The system saves the planned changes for the contract accounts affected.
Change in the future
The system changes the bank details in the master data of the business partner, if the bank details were not already changed. If
there are already target details for the change and a target date, then the system cannot change the bank details data, except
for the date of the change.
The system does not make any changes for the contract accounts affected.
This procedure only applies if existing bank details are overwritten; if you create new bank details in change mode, the
same procedure applies as for creation in the future.
A business partner has bank details 0001 at ABC Bank. These bank details are valid from 08/05/2005 to 12/31/9999. Bank
details 0001 are assigned to contract account A. The customer calls and informs you that, taking effect on 11/15/2005, his new
bank is XYZ Bank. The bank details at ABC Bank are no longer valid. Using the transaction Change Payment Data , the call
center agent carries out the changes for 11/15/2005.
The system changes the bank details as follows:
For the new bank details at XYZ Bank, the system creates the new ID 0002 with a Valid From date 11/15/2005.
The system changes the old bank details 0001 at ABC Bank and enters the change date 11/15/2005 and the target bank details
0002.
After the change, the bank details are as follows:
ID 0001 ABC Bank, valid from 028/02/2005 to 11/15/2005, target bank details ID 0002, change date 11/15/2005
ID 0002 XYZ Bank, valid from 11/15/2005 to 12/31/2005
After the change, ID 0001 is still assigned to contract account A.
Deletion in the future
For the bank details, the system sets the Valid To date in the future in the master data of the business partner.
When you change payment card data, the system saves the data in one of these ways:
Creation in the future
The system saves the payment card in the master data of the business partner.
4/11/2019
Change in the future
The change function does not apply for payment cards. Therefore, it is not possible to change data of a payment card for a date
in the future.
You can change the use of the payment card in contract accounts (and possibly in contracts). The system saves these changes
as planned changes.
Deletion in the future:
The payment card remains in the master data of the business partner.
Triggering Follow-Up Actions

Use
With the transaction Change Payment Data you can trigger various follow-up actions.
Prerequisites
In Customizing for Contract Accounts Receivable and Payable, under Basic Functions Contract Partner Changes to Payment
Transactions De ne Rules for Follow-Up Actions , you have de ned sets of rules and assigned these to the relevant company
codes.
Features
Based on your Customizing settings, the system determines the set of rules to be used. In this process, the system uses the
standard company code of the contract accounts and contracts that are affected by the change of payment data. Once the set
of rules is determined, then the system determines the follow-up actions when you save the data. This determination is also
dependent on your current operating mode (display, change, delete). The system displays the follow-up actions in a separate
dialog box.
Note
The system displays the follow-up actions as long as you did not suppress the display in your Customizing settings.
You can also display the dialog box during processing by choosing the pushbutton Simulate Follow-On Actions .
Directly below the company code, the system lists all follow-up actions, for which it can determine at least one affected object. If
a follow-up action is assigned to several sets of rules, and these sets of rules are active in the same company code, then the
system displays the follow-up action only once in each company code.
The system lists the objects affected by a follow-up action (such as, locks, dunning notices, or returns) directly under the follow-
up action, and independently of the set of rules.
If you execute a follow-up action, then the system performs the activities for all affected objects (that are displayed in the
dialog).
Note
4/11/2019
The system executes only those follow-up actions that are actually selected.
You can in uence the processing of the follow-up actions through Customizing.
You can specify in Customizing that a set of rules is active. The system considers only active sets of rules when
determining follow-up actions.
For each follow-up action, you can con gure whether it is already selected when you call up the follow-up actions, and
whether the user can change this selection.
For each follow-up action, you can specify the operating modes in which the system considers it. For example, it can
be helpful to allow the follow-up action "Delete Bank Data from Business Partner" only in delete mode.
Depending on your Customizing settings, you can select the following follow-up actions:
Delete Bank Data from Business Partner or Delete Payment Card Data from Business Partner
If you select one of these follow-up actions, the deleted bank details/payment card are also deleted from the master
data of the business partner. The prerequisite is that this payment data is not used in any other object (for example, in a
contract account).
Remove Locks
If you select this follow-up action, the following locks are deleted in accordance with your Customizing settings:
For contract accounts and industry objects:
Payment locks for incoming and outgoing payments
Dunning locks
For items:
Payment locks
Dunning locks
For these follow-up actions, the system only displays the follow-up actions that can be performed
based on your Customizing settings. When you save, the data is then changed in accordance with these
follow-up actions.
Reverse Dunning Notices
For this follow-up action, the system displays the dunning notices that qualify for reversal according to Customizing. If
you select this follow-up action, all dunning notices displayed below it are reversed (including the dunning charges). If the
charges have already been cleared, the system creates a credit memo - provided this is set up in Customizing.
Reverse Returns
For this follow-up action, the system displays the returns that qualify for a reset according to Customizing. If you select
this follow-up action, the system reverses the creditworthiness entries and the charges of all returns that are displayed.
If the charges have already been cleared, the system creates a credit memo - provided this is set up in Customizing.
If a follow-up action that is displayed requires a reconciliation key for execution, the system displays an input eld for it. If
necessary, the system creates the reconciliation keys that you specify in this eld.
Special Cases
4/11/2019
Note
The special cases described below also apply to insurance objects to which the selected business partner is assigned in
Collections/Disbursements (FS-CD) in the industry component Insurance . The contract account holder corresponds to the
contract partner in FS-CD.
The special cases described below also apply to contract objects to which the selected business partner is assigned.
Special Case 1: Alternative Payer/Payee

If the contract account contains an alternative payer/payee, the payment data entered in the contract account belongs to this
alternative payer/payee. If you want to change the payment data of the contract account holder, this is not allowed to have any
in uence on the payment data of the alternative payer/payee. If, for the changes you want to carry out, you selected a transfer
type that would change the payment data for the alternative payer/payee, then contract accounts with alternative
payers/payees appear in the list in the column Alt.Payer/Payee with the icon ( Alt. Payer/Payee ). You can see the business
partner number of the alternative payer or payee in the columns Alternative Payer and Alternative Payee .
 Example
The contract account contains an alternative payer and you have selected the transfer type Incoming Payments . The icon (
Alt. Payer/Payee ) appears.
The contract account contains an alternative payee and you have selected the transfer type Incoming Payments . The icon (
Alt. Payer/Payee ) does not appear.
Which accounts can you select?
Whether you can select a contract account with this icon in the list for changes depends on the transfer type you have selected
and the existing data in the contract account.
Case 1
You have selected the transfer type Incoming and Outgoing Payments . The contract account contains an alternative
payer, but no alternative payee. In this case, you can de ne the payment data of the contract account holder as the
payment data for outgoing payments and therefore select the contract account for the change.
Case 2
You have selected the transfer type Incoming Payments . The contract account contains an alternative payer. In this
case, you cannot initially select the contract account for changes. However, if the contract account holder wants to be
the payer for his contract account, you can click on the icon ( Alt. Payer/Payee ) to switch to processing of the contract
account and delete the alternative payer there. Once you have saved the contract account, you can select it for the
change in the list.
How does the system behave when you save the changed contract account?
There are different cases depending on the option selected:
Case 1
4/11/2019
You have selected the transfer type Incoming and Outgoing Payments . There is an alternative payer, but no alternative
payee.
You save without carrying out any actions.
The bank details/payment cards entered are only stored in the master record of the contract account holder.
You select the contract account and save.
The bank details/payment card are only de ned as the bank details for outgoing payments.
You delete the alternative payer in the contract account, select the contract account, and save.
The bank details/payment card are de ned as the bank details for incoming and outgoing payments.
Case 2
You have selected the transfer type Incoming Payments . There is an alternative payer, but no alternative payee.
You save without carrying out any actions.
The system only saves the bank details/payment card entered in the master record of the contract account
holder.
You delete the alternative payer in the contract account, select the contract account, and save.
The bank details/payment card are only de ned as the bank details for incoming payments.
Special Case 2: Alternative Payment Details

In the following cases, the icon ( Alternative Payment Details Exist ) appears in the column Alternative Payment Details .
Case 1
The contract account contains different payment details than those you have selected.
The contract account contains the bank details ID for incoming payments 001, but in the dropdown list, you have
selected the bank details ID 002. The transfer type Incoming Payments is selected.
Case 2
You have selected the transfer type Incoming and Outgoing Payments . The existing payment details are different.
The contract account contains the bank details ID 001 for incoming payments, and the bank details ID 002 for
outgoing payments.
The system treats a contract account with alternative payment details as follows:
To prevent you changing the contract account in error, the system does not select it. However, you can select the
contract account for changes.
By choosing the icon ( Alternative Payment Details Exist ), you can switch to processing of the contract account
and make any changes required.
Special Case 3: Business Partner Is Payer/Payee

If the business partner entered is not the holder of the contract account, but is entered as alternative payer/payee in the
contract account, the icon ( <Business Partner Number> Is Alternative Payer ) appears in the column BP Is Payer/Payee . The
following is valid for the maintenance:
4/11/2019
If the bank details/payment card selected are used in the contract account, the system selects this contract account.
You cannot change this selection.
If other bank details/payment card are used in the contract account, the system does not select the contract account;
however, you can select it manually.
If the business partner no longer wants to be the alternative payer/payee for this contract account, you can switch to the
full screen maintenance of the contract account via the icon with the quick info text <Business Partner Number> Is
Alternative Payer and remove the business partner from the eld Alternative Payer or Alternative Payee .
Special Case 4: Business Partner Is Payer

If the business partner entered is not the holder of the contract account, but is entered as payer in the contract account, the
icon ( Paid by <Business Partner Number> ) appears in the column BP Is Payer . The contract account is only displayed for
information purposes and you cannot select it.
If the business partner no longer wants to be the payer for this contract account, you can choose the icon ( Paid by <Business
Partner Number> ) to switch to processing for the contract account and remove the business partner from the eld Payer and
remove the contract account from the eld Paid By .
Special Case 5: Several Alternative Payees for Insurance Object (Only in FS-CD)
If several alternative payees are entered for an insurance object-partner relationship in Collections/Disbursements, the icon (
Several Alternative Payees ) appears in the status column. The insurance object is only displayed for information purposes and
you cannot select it. However, you can switch to the maintenance of the insurance object and process the data there.
Replication and Synchronization of Business

Partners
Concept
Note
The replication and synchronization described here is only available to you if you use the industry component Contract
Accounts Receivable and Payable.
SAP Customer Relationship Management (CRM) uses the SAP business partner to represent customer data. SAP ERP (ERP)
uses the SAP business partner, the customer, and the vendor to represent master data in various components in parallel. In a
scenario where you use SAP CRM, CRM is the leading system. You create master data here as business partners and distribute
this master data to SAP ERP using CRM middleware. When you create a business partner, you can have the system
automatically create the corresponding customer or vendor master record. SAP ERP then synchronizes the business partner
with the customer or vendor master record using customer/vendor integration (CVI). SAP ERP also distributes changes to
business partner data in SAP CRM in the same way.
In Contract Accounts Receivable and Payable, you create business partners with customer or vendor master records manually.
On the SAP Easy Access screen, choose Accounting Financial Accounting Contract Accounts Receivable and Payable Master
Data Business Partner Customer/Customer Integration Create Business Partner with Customer and Supplier/Vendor
Integration Create Business Partner with Vendor . There you can also access transactions for changing and displaying master
data. These transactions use role groupings that already contain the necessary roles for synchronous creation of
customers/customers and suppliers/vendors. This ensures that the system creates the business partner in the role MKK, and
4/11/2019
that you can enter information on the company code and sales (or the company code and purchasing) using the roles FLCU00
and FLCU01 or FLVN00 and FLVN01.
Prerequisites
You are familiar with the basic settings of the master data objects business partner, customer, and vendor.
You have experience with con guring the data exchange using CRM middleware assuming that SAP CRM is part of your
scenario.
During the synchronization and replication, both the ERP system and the CRM system are available assuming CRM is
part of your scenario.
Note
For more information, see the following SAP Notes:
SAP Note Description
852870 BP_CVI: Changes in BDT Customizing for ERP 2005
905535 Useful Notes CVI for Master Data Synchronization
928616 BP_CVI: Customizing of Required Entry Fields for

BP/Customer/Vendor
941955 BP_CVI: Integration of Customers/Vendors with SAP BP
954816 BP_CVI: Transactions for Creating/Linking BPs
956054 BP_CVI Customer/Vendor Integration as of ERP 2005 (ECC600)
Activities
If you are using the integration between SAP CRM and SAP ERP, then you have to make the settings described in all of the
following topics. If you are using only SAP ERP, then only make the settings described in the following two topics:
Making Settings for Customer/Vendor Integration
Making Settings for the Postprocessing Office
The synchronization and replication of master data between SAP CRM and SAP ERP requires extensive settings:
For the SAP business partner in the ERP system and CRM system
For the CRM middleware in the ERP system and CRM system
For customer/vendor integration (CVI) in the ERP system
For the Postprocessing Office in the ERP system
In a scenario with SAP CRM, newly created business partner master records and subsequent changes as long as the necessary
settings have been made are distributed automatically from the CRM system to the ERP system.
If you use the appropriate CRM partner roles, then the system creates the customer or vendor master records synchronously,
or updates them, as depicted in the following table.
SAP CRM SAP ERP Synchronized Master Data

4/11/2019
CRM000Sold-to party FLCU00 Customer master record with FI data
FLUC01 Customer master record with Sales

data
MKK
Contract partner
BBP000 Supplier FLVN00 Vendor master record with FI data
FLVN01 Vendor master record with Sales data
MKK Contract Partner
If you are using only ERP, then the system synchronizes and updates the master data as depicted in the following table:
SAP ERP: Role Grouping SAP ERP: Role Synchronized Master Data
FSCR01X VP with customer integration FLCU00 Customer master record with FI data
FLUC01 Customer master record with sales data
FSCR02X VP with vendor integration FLVN00 Vendor master record with FI data
FLVN01 Vendor master record with sales data
Note
If you want to create the business partner with a customer or vendor, then you rst have to compare the required elds of
the customer and vendor master record with those of the business partner. If you create a business partner in SAP ERP of
the type 'person', then you have to make sure that it is possible to enter the correspondence language. Only then is it
possible for the synchronization to take place using CVI. If errors occur during the synchronization, you can get help in the
Business Data Toolset by removing the function module BUA_BUPA_EVENT_FMOD2 for eld group 62. To do so, in the menu
for the Business Data Toolset (transaction BUPT), choose Business Partner Control Screen Layout Field Groups .
Note
During the replication of business partners from SAP CRM to SAP ERP, the standard system sets the Relevant for agency
business indicator for the customers created using CVI.
Note
During the replication of business partners from SAP CRM, the system transfers information about the company code and
sales or the company code and purchasing to the customer or supplier/vendor using the CVI.
Making Settings for Business Partners

Prerequisites
You created a site for the ERP system in your CRM system as described in the topic Making Settings for CRM Middleware under
step 3.
Procedure
4/11/2019
1. In your CRM system in the administration console, create a subscription for all business partners and enter them in the
ERP site de ned in your CRM system. To do so, in the menu, choose Architecture and
Technology Middleware Administration Administration Console . For more details on this procedure, see Making
Settings for CRM Middleware.
2. De ne number ranges for your business partners in your ERP system and CRM system. For more details on this
procedure, see Making Settings for CRM Middleware and Making Settings for Customer/Vendor Integration.
Making Settings for CRM Middleware

Procedure
1. De ne the following RFC destinations:
De ne an RFC connection between the CRM system and the ERP system of the category ABAP connections in
the CRM system. In Customizing for Customer Relationship Management choose CRM Middleware and Related
Components Communication Settings De ne RFC Destinations . Use an appropriate ERP user, such as
CRMOLTP.
In the ERP system, create an RFC connection between the ERP system and the CRM system of the category
ABAP connections. On the SAP Easy Access screen, choose Tools Administration Administration Network RFC
Destinations . Use an appropriate CRM user, such as RFC.
Note
For the view CRMRFCPAR check in the ERP system if the following entry exists for the connection to the CRM system
(in the menu under System Services Table Maintenance Extended Table Maintenance ):
Field Value
User CRM
Object Name *
Destination <
The connection that you created in this
step
>
Load Type *
2. In the CRM system, register the CSA* queues in the RFC monitor. Check if there are queues with the name CSABUPA*
(or CSA*) and R3A*. To do so, in the menu, choose Architecture and
Technology Middleware Administration Register/Deregister Queues .
Note
If CSA* is already active, then you can no longer add CSABUPA*, since it is contained in CSA*. In that case, then you
only need CSA*. Make sure that the queues are registered.
3. In the CRM system, create sites and subscriptions for the middleware data distribution. To do so, in the menu, choose
Architecture and Technology Middleware Administration Administration Console . For the ERP system you create a
subscription there for the following replication objects and publications:
Replication Object Cat. Publications
BUPA_MAIN Simple Bulk All Business Partners (MESG)
4/11/2019
BUPA_REL Simple Bulk All Business Partner
Relationships (MESG)
Caution
Do not create any subscriptions to publications of the replication object VEND_MAIN for the ERP system.
Note
If problems occur during business partner replication in your live system, you can display the status of BDoc
messages for the replication objects BUPA_MAIN andBUPA_REL. On the SAP Easy Access screen, choose
Architecture and Technology Middleware Monitoring Message Flow Display BDoc Message Summary .
4. In both the ERP and CRM systems, create number ranges and assign them to groupings in Customizing for SAP Business
Partner. To do so, choose Business Partner Basic Settings Number Ranges and Groupings
Note
The groupings that you use in the CRM system for business partner distribution to the ERP system have to agree with
those in the ERP system and the other way around. The grouping criteria are used for determining the appropriate
number range in the target system. It is not mandatory for the business partners to have the same numbers in the
CRM and ERP systems. If the numbers are the same, you have to ensure that you create large enough number ranges
in the CRM and ERP systems. In the target system (ERP system) assign a number range with external number
assignment to each grouping criterion that you use for identical numbering. In addition, you can activate function
module COM_BUPA_MWX_MAP_NUMRANGE in the ERP system as explained below.
5. Activate the function modules for CRM outbound data distribution in the CRM system. In the menu choose
System Services Table Maintenance Extended Table Maintenance and call the view V_BUT_CALL_FU.
Activate BDoc generation for the middleware. Activate the following function modules by setting the indicator in the Call
column. The position numbers specify the sequence in which the function modules are executed within a group with the
same event and object. Only the sequence of the numbers is important. That means that the absolute values of the
items can be different.
Event Object Item Function Module Call
CRMOU BUPA 1000000 BUPA_OUTBOUND_BPS_FILL_CENTRAL X
CRMOU BUPA 1200000 CRM_BUPA_OUTB_BPS_FILL_MD X
CRMOU BUPA 1300000 CRM_BUPA_BDOC_BPS_FILL_DATA X
CRMOU BUPA 2000000 ABA_FSBP_OUTBOUND_BPS_FILL X
CRMOU BUPR 1000000 BUPA_OUTBOUND_BPR_FILL_CENTRAL X
CRMOU BUPR 1200000 CRM_BUPA_OUTB_BPR_FILL_MD X
CRMOU BUPR 1300000 CRM_BUPA_BDOC_BPR_FILL_DATA X
BPOUT BUPA 200000 BUPA_MWX_BDOC_CREATE_MAIN X
BPOUT BUPR 100000 BUPA_MWX_BDOC_CREATE_REL X
CLEAR BUPA 1000000 BUPA_OUTBOUND_CLEAR_FLAGS X
CLEAR BUPA 2000000 ABA_FSBP_OUTBOUND_CLEAR_FLAGS x
4/11/2019
Note
You are not allowed to activate the following function modules in the CRM system, that is, you are not allowed to set
the Call indicator for them. However, do not delete any entries from the table, since the function modules can be used
for other purposes.
CRMOU BUPA Any CRM_BUPA_BDOC_BPS_FILL_VENDOR
CRMOU BUPA Any ABA_FSBP_EMP_TO_ROLE_OUTBOUND
BPOUT BUPA Any VEND_MWX_CREATE_MAIN_BDOC
BPOUT BUPA Any BUPA_OUTBOUND_MAIN *)
BPOUT BUPA Any BUPA_OUTBOUND_ALE_MAIN
BPOUT BUPR Any UDM_OUTBOUND_ALE_REL
BPOUT BUPR Any BUPA_OUTBOUND_REL*)
BPOUT BUPR Any BUPA_OUTBOUND_ALE_REL
BPOUT BUPX Any MDS_BUPA_OUTBOUND
R3AOU BUPA Any BUPA_MWX_BDOC_UP_CURRSTATE_SET
XIOUT BUPA Any Any *)
XIOUT BUPR Any Any *)
*) You have to activate this function module if you need a PI distribution of business partner data to other systems
(ERP systems or third-party systems). In that case, you have to ensure that the business partner data is not
distributed using PI to the same ERP system to which it is distributed using middleware.
6. In the ERP system, check the subscriptions for upload and download objects, and make sure that the entries listed in the
following table exist. In the menu choose System Services Table Maintenance Extended Table Maintenance and select
table CRMSUBTAB for maintenance. The Inactive indicator must be set as shown in the table:
User Object Name Up/Download Object Class Function Module Inactive
CRM BUPA_MAIN U BUPA FKK_BUPA_MAIN_INBOUND
CRM BUPA_REL U BUPA COM_BUPA_REL_INBOUND
CRM VEND_MAIN U BUPA COM_VEND_MAIN_INBOUND X
Note
You are not allowed to activate the following function module in the ERP system:
User Object Name Up/Download Object Class Function Module Inactive
CRM BUPA_MAIN U BUPA FSL_BUPA_MAIN_INBOUND
7. In transaction COM_BUPA_CALL_FU, activate the following function modules for the data exchange with the ERP system
by setting the Call indicator.
4/11/2019
R3OBI BUPA 2000110 FKK_BUPA_MAIN_BP_INBOUND X
R3OBI BUPR 2000000 COM_BUPA_REL_BP_INBOUND X
R3IN BUPA 810 FKK_BUPA_INBOUND_FILTER_IDENT X*)
R3IN BUPA 910 FKK_BUPA_INBOUND_MWX_ADD_ROLES X
R3IN BUPA 920 FKK_BUPA_INBOUND_MWX_VND_ROLE X
R3IN BUPA 1000 FSC_BUPA_MWX_FILTER_MAIN X
R3IN BUPA 10000 COM_BUPA_MWX_FILTER_MAIN X
R3IN BUPR 10000 COM_BUPA_MWX_FILTER_REL X
R3IN BUPR 100000 COM_BUPA_MWX_MAP_REL_CENTRAL X
*) Activate this function module only if you do not use the identi cation types CRM002 and CRM004 in the ERP system.
If you want to use the same numbers for business partners in the ERP system as you use in the CRM system, then you
have to activate the following check module. If a business partner does not receive the same number when it is created
in the ERP system, then this function module terminates processing and creates a BDoc error that you can display in the
CRM system.
R3IN BUPA 150000 COM_BUPA_MWX_MAP_NUMRANGE X
Note
You are not allowed to activate the following function modules in the ERP system. That means you are not allowed to
set the Call indicator for them. However, do not delete any entries from the table, since the function modules can be
used for other purposes.
R3OBI BUPA Any FSL_BUPA_MAIN_BP_INBOUND
R3OBI BUPA Any COM_BUPA_MAIN_BP_INBOUND
R3OBI BUPA Any PI_BP_PROXY_BAPI_CUSTOMER
R3OBI BUPR Any PI_BP_PROXY_BAPI_CUSTOMER
R3OBI VEND Any PI_BP_PROXY_BAPI_VENDOR
R3IN BUPA Any COM_BUPA_MWX_MAP_MAIN_CENTRAL
R3IN BUPA Any FSL_BUPA_INBOUND_FILTER_IDENT
R3IN BUPA Any FSL_BUPA_INBOUND_MWX_ADD_ROLES
8. In the ERP system, activate the following function modules in the view V_BUT_CALL_FU by setting the Call indicator for
them. In the menu, choose System Services Table Maintenance Extended Table Maintenance . The position numbers
specify the sequence in which the function modules are executed within a group with the same event and object. Only
the sequence of the numbers is important. That means that the absolute values of the items can be different.
4/11/2019
CRMIN BUPA 1000000 BUPA_INBOUND_MAIN_CENTRAL X
CRMIN BUPA 2000000 ABA_FSBP_INBOUND_MAIN X
CRMIN BUPR 1000000 BUPA_INBOUND_REL_CENTRAL X
CRMOU BUPA 1000000 BUPA_OUTBOUND_BPS_FILL_CENTRAL X
CRMOU BUPR 1000000 BUPA_OUTBOUND_BPR_FILL_CENTRAL X
BPOUT BUPX 10000000 MDS_BUPA_OUTBOUND X
The events CRMOU and BPOUT are relevant for internal synchronization using CVI. In some cases, you might need
additional function modules, such as for the event MERGE.
Making Settings for Customer/Vendor

Integration
Context
To synchronize customer and vendor master data with the CRM system, you use customer/vendor integration (CVI).
Customer/vendor integration synchronizes the related synchronization objects in the ERP system:
SAP business partner (BP)
Customer master record
Vendor master record
You make settings for customer/vendor integration only in the ERP system.
Procedure
1. Check if the following settings were made in SAP Customizing under Cross-Application Components Master Data
Synchronization Synchronization Control Synchronization Control Synchronization Objects .
Syn. Object Sync. Mode *) Extractor Class Description Platform Block size
BP 1 CVI_BP_EXTRACTOR Business X 50
partner
Customer 1 CMD_EI_API_EXTRACT Customer 50
Vendor 1 VMD_EI_API_EXTRACT Vendor 50
*) Synchronization mode:
1 = For synchronous comparison and mass data load
2 = For synchronous comparison only
3 = For mass data load only
2. Enter the following synchronization options. To do so, in SAP Customizing, choose Cross-Application
Components Master Data Synchronization Synchronization Control Preparatory Steps for Synchronization Control
4/11/2019
and follow the link “synchronization processes” in the documentation.
A synchronization option represents a combination of a source synchronization object and a target synchronization
object. The synchnronization option shows which source synchronization object is synchronized with which target
synchronization object.
Source Obj. Target Obj. Strategy Implementation Queue Name
BP Customer CVI_STRATEGY_BP_CUSTOMER MDS_BUPA_CUST
BP Vendor CVI_STRATEGY_BP_VENDOR MDS_BUPA_VEND
Customer BP CVI_STRATEGY_CUSTOMER_BP MDS_CUST_BUPA
Vendor BP CVI_STRATEGY_VENDOR_BP MDS_VEND_BUPA
3. Make sure that the following queues for background processing of synchronization processes are registered and
activated. To do so, in SAP Customizing, choose Cross-Application Components Master Data
Synchronization Synchronization Control Preparatory Steps for Synchronization Control and follow the link “queue
processing” in the documentation.
MDS_BUPA_CUST*
MDS_BUPA_VEND*
MDS_CUST_BUPA*
MDS_VEND_BUPA*
4. Activate the synchronization options in SAP Customizing under Cross-Application Components Master Data
Synchronization Synchronization Control Synchronization Control Activate Synchronization Options as follows:
Source Obj. Target Obj. Act. Ind.
BP Customer X
BP Vendor X
Customer BP X
Vendor BP X
5. Synchronize the business partner (BP) with the customer (CUSTOMER).
Assign the business partner grouping to the account group of the customer. In SAP Customizing choose Cross-
Application Components Master Data Synchronization Customer/Vendor Integration Business Partner
Settings Settings for Customer Integration Field Assignment for Customer Integration Assign Keys De ne
Number Assignment for Direction BP to Customer . If you set the Same Number indicator, then the ERP system
uses identical numbers for the business partner (BP) and the customer (CUSTOMER).
Note
You create and assign number ranges for customer accounts in SAP Customizing under Financial Accounting
(New) Accounts Receivable and Accounts Payable Customer Accounts Master Data Preparations for
Creating Customer Master Data .
Note
You create and assign number ranges for business partners in SAP Customizing under Cross-Application
Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings .
4/11/2019
 Example
The following table shows example entries. In making your own settings, use the business partner groupings
and account groups you need.
Grouping Short name Account Group Meaning Same Numbers
BPIN Internal CUST Customers (int. no. asgmnt)
BPEX External CUNA Customers (ext. no. asgmnt) X
Check if an entry exists for the role category MKK with the name Contract Partner for the synchronization; in
SAP Customizing, choose Cross-Application Components Master Data Synchronization Customer/Vendor
Integration Business Partner Settings Settings for Customer Integration Set BP Role Category for Direction
BP to Customer .
Make sure that the required entry elds and entries for the business partner (BP) and the customer agree with
each other. If they do not, then the system terminates the synchronization.
6. Synchronize customers (CUSTOMER) and business partners (BP).
Note
The following settings are relevant only if you want the system to automatically create a business partner when a
customer is created.
Assign the attributes of a business partner grouping to an account group (customer). In SAP Customizing choose
Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner
Settings Settings for Customer Integration Field Assignment for Customer Integration Assign Keys De ne
Number Assignment for Direction Customer to BP . The following table shows example entries. In making your
own settings, use the attributes of business partner groupings and account groups you need.
 Example
Account Group Short name Grouping Meaning Same No.
CUST General customer BPIN Internal
CUNA Customers (ext. no. asgmnt) BPEX External X
Assign roles, in which the corresponding business partner should be created, to the customer account groups. In
SAP Customizing, choose Cross-Application Components Master Data Synchronization Customer/Vendor
Integration Business Partner Settings Settings for Customer Integration De ne BP Role for Direction
Customer to BP . The following table shows example entries. In making your own settings, use the account groups
and partner roles you need.
 Example
Account Group Description BP Role Description
CUST General customer FLCU00 Customer
CUST General customer FLCU01 Customer
4/11/2019
CUST General customer MKK Contract Partner
CUNA Customers (ext. no. asgmnt) FLCU00 Customer
CUNA Customers (ext. no. asgmnt) FLCU01 Customer
CUNA Customers (ext. no. asgmnt) MKK Contract Partner
7. Perform the activities in SAP Customizing under Cross-Application Components Master Data
Synchronization Customer/Vendor Integration Business Partner Settings Settings for Customer Integration Field
Assignment for Customer Integration Assign Attributes .
8. Synchronize the business partner (BP) with the vendor (VENDOR).
Assign the business partner grouping to the account group of the vendor. In SAP Customizing choose Cross-
Settings Settings for Vendor Integration Field Assignment for Vendor Integration Assign Keys De ne Number
Assignment for Direction BP to Vendor . If you set the Same Number indicator, then the ERP system uses
identical numbers for the business partner (BP) and the vendor (VENDOR).
Note
You create and assign number ranges for vendor accounts in SAP Customizing under Financial Accounting
(New) Accounts Receivable and Accounts Payable Vendor Accounts Master Data Preparations for
Creating Vendor Master Data .
Note
You create and assign number ranges for business partners in SAP Customizing under Cross-Application
Components SAP Business Partner Basic Settings Number Ranges and Groupings .
 Example
The following table shows example entries. In making your own settings, use the business partner groupings
and account groups you need.
Grouping Short Name Account Group Meaning Same Numbers
BPIN Internal VEND Vendors (int. no. asgmnt)
BPEX External SUPP Vendors (ext. no. asgmnt) X
Check if the role category MKK with the name Contract Partner is entered in SAP Customizing under Cross-
Settings Settings for Vendor Integration Set BP Role Category for Direction BP to Vendor . This is needed for
the synchronization of vendors.
Make sure that the required entry elds and entries for the SAP business partner (BP) and the vendor agree with
each other. If they do not, then the system terminates the synchronization.
9. Synchronize vendors (VENDOR) and business partners (BP).
Note
The following settings are relevant only if you want the system to automatically create a business partner when a
vendor is created.
4/11/2019
Assign the attributes of a business partner grouping to an account group (vendor). In SAP Customizing choose
Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner
Settings Settings for Vendor Integration Field Assignment for Vendor Integration Assign Keys De ne Number
Assignment for Direction Vendor to BP . The following table shows example entries. In making your own settings,
use the attributes of the business partner grouping and account group you need.
 Example
Account Group Short name Grouping Meaning Same Numbers
VEND Vendors (int. no. asgmnt) BPIN Internal
SUPP Vendors (ext. no. asgmnt) BPEX External X
Assign roles, in which the corresponding SAP business partner should be created, to the vendor account groups.
In SAP Customizing, choose Cross-Application Components Master Data Synchronization Customer/Vendor
Integration Business Partner Settings Settings for Vendor Integration De ne BP Role for Direction Vendor to
BP . The following table shows example entries. In making your own settings, use the account groups and partner
roles you need.
 Example
Account Group Description BP Role Description
VEND Vendors (int. no. asgmnt) FLVN00 Vendor
VEND Vendors (int. no. asgmnt) FLVN01 Vendor
VEND Vendors (int. no. asgmnt) MKK Contract Partner
SUPP Vendors (ext. no. asgmnt) FLVN00 Vendor
SUPP Vendors (ext. no. asgmnt) FLVN01 Vendor
SUPP Vendors (ext. no. asgmnt) MKK Contract Partner
10. Assign the industries of the business partner to industries of the customer/vendor master record. In SAP Customizing,
choose Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner
Settings Settings for Customer Integration Field Assignment for Customer Integration Assign Attributes Assign
Industries .
11. Synchronize the customer (CUSTOMER) or vendor (VENDOR) with the business partner. This setting is needed for
synchronizing the customer or vendor, or both, with the business partner. Choose Cross-Application
Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings BAdI: Data
Assignment of Form of Address from Customer/Vendor to BP .
Here you deselect the implementation CVI_MAP_TITLE_DIRECT and you select CVI_MAP_BP_CATEGORY. The system
asks you to create a transport request for transporting the change to your quality system and your live system.
These changes apply across the entire system.
Making Settings for the Postprocessing

Office
4/11/2019
Use
During error processing, the Postprocessing Office (PPO) replaces the application log. Using the PPO is optional; therefore, you
have to activate the PPO explicitly.
Caution
If you do not activate the PPO, then errors during synchronization can lead to short dumps.
Procedure
Make the settings described below in your ERP system. PPO Customizing relates to a software component and to speci c
business processes. (The term "business process" has a speci c meaning in the PPO.) To monitor postprocessing requests, on
the SAP Easy Access screen, choose Cross-Application Components Postprocessing Office Postprocessing Order Edit
Postprocessing Order .
1. Set up the internal PPO software component AP-MD (Application Platform master data). To do so, in SAP Customizing,
choose Cross-Application Components General Application Functions Postprocessing Office Display System Settings
for the Postprocessing Office and select Software Components. The PPO needs this internal component in order to be
able to differentiate postprocessing orders that were created by master data synchronization from postprocessing
orders of other projects. In addition, all PPO Customizing settings are component-speci c. Make the following entries:
Software Editing Component Title Display *) Edit *)

Component Transaction Description
AP-MD MDS_PPO2 Application Master Data 2 2

platform Synchronization
master data
*) 0 = Orders that I have to process
1 = Orders in my worklist
2 = All orders
Note
You can use this processing transaction when problems arise during synchronization between business partners and
customers or vendors. The transaction shows the reasons for the errors.
2. For the software component AP-MD, de ne the PPO business processes that you want to use for the initial load. To do so,
in SAP Customizing choose Cross-Application Components General Application Functions Postprocessing
Office Display System Settings for the Postprocessing Office and select Business Processes. Each combination of a
source and target object must be de ned as a business process as follows:
Software Component Business Process Business Process Description
AP-MD CVI_01 Customer -> Business

Partner
AP-MD CVI_02 Vendor -> Business Partner
AP-MD CVI_03 Business Partner ->

Customer
AP-MD CVI_04 Business Partner -> Vendor
4/11/2019
3. Activate the PPO business processes for the component AP-MD. To do so, in SAP Customizing choose Cross-Application
Components General Application Functions Postprocessing Office Business Processes Activate Creation of
Postprocessing Orders . Enter only the business processes you need for your application. Activate each combination of
source and target object that you have de ned as a business process.
Component Business Process Active
AP-MD CVI_01 X
AP-MD CVI_02 X
AP-MD CVI_03 X
AP-MD CVI_04 X
4. Set up a PPO object type for all object types of the master data synchronization for the component AP-MD as shown in
the table. To do so, in SAP Customizing choose Cross-Application Components General Application
Functions Postprocessing Office Display System Settings for the Postprocessing Office and select Object Types. If a
corresponding BOR object already exists, then use the technical key of the BOR object.
Object Type Internal -> External Input Description
BUS1006 MDS_PPO_BP_GET_DESCR MDS_PPO_BP_GET_OBJKEY Business partner
KNA1 MDS_PPO_CUSTOMER_GET_DESCR MDS_PPO_CUSTOMER_GET_OBJKEY Customer
LFA1 MDS_PPO_VENDOR_GET_DESCR MDS_PPO_VENDOR_GET_OBJKEY Vendor
PRODILVND MDS_PPO_PRODILVND_GET_DESCR MDS_PPO_PRODILVND_GET_OBJKEY Interlinkage

Vendor
The entry in the Internal –> External column shows the name of the function module that converts the internal
representation of an object key (such as a GUID) into an external representation for display on the PPO screen.
On the selection screen of the PPO transaction Display Postprocessing Order, you can select postprocessing orders
using the IDs of the objects contained in the orders. If you want to support users with a search help, you can program a
function module for this. You then enter the technical name of this function module in the Input column.
5. As shown in the table, de ne which object types are allowed for which PPO business process. To do so, in SAP
Customizing choose Cross-Application Components General Application Functions Postprocessing Office Display
System Settings for the Postprocessing Office and select Valid Object Types. For the initial load, de ne the source
object type as a main object and the target object as a basis object.
Software Component Business Process Object Role *) Object Category Object Type
AP-MD CVI_01 1 1 (Business KNA1

Object)
AP-MD CVI_01 2 1 (Business BUS1006

Object)
AP-MD CVI_02 1 1 (Business LFA1

Object)

Object)
4/11/2019
Object)
AP-MD CVI_03 2 1 (Business KNA1

Object)

Object)
AP-MD CVI_04 2 1 (Business LFA1

Object)
*) Object Role:
1 = Main object
2 = Basis object
3 = Environment object
4 = Additional environment object
6. As shown in the following table, de ne which processing methods you want to be available for each object type. To do so,
in SAP Customizing choose Cross-Application Components General Application Functions Postprocessing
Office Display System Settings for the Postprocessing Office and select Methods. These processing methods can
either be a method of the related BOR object or a function module you program yourself. If you use your own function
module, enter the technical name of the function module.
Object Type Methods Active Item Function Object BOR Method Description
Module Category *)
BUS1006 DISPLAY X 1 1 DISPLAY Display
BUS1006 EDIT X 2 1 EDIT Change
KNA1 DISPLAY X 1 1 DISPLAY Display
KNA1 EDIT X 2 1 EDIT Change
LFA1 DISPLAY X 1 1 DISPLAY Display
LFA1 EDIT X 2 1 EDIT Change
*) Object category 1 = Business Object
7. De ne the layout for postprocessing orders.
Specify how the tab pages are displayed in the order area. To do so, in SAP Customizing choose Cross-Application
Components General Application Functions Postprocessing Office Display System Settings for the
Postprocessing Office and select Display Order Area.
Reference Sequence PAI PBO Function for Data Refresh
STD1 1 MDS_PPO_ORDER_SCR_ISDAT MDS_PPO_ORDER_SCR_R
STD2 2 MDS_PPO_ORDER_SCR_FCODE MDS_PPO_ORDER_SCR_ISDAT MDS_PPO_ORDER_SCR_R
PAI: Using this function module, you can react to user actions.
PBO: Function modules that are used for reading data before the order data is displayed.
4/11/2019
Refresh: Function modules for updating data.
Specify how the tab pages are displayed in the object area. To do so, in SAP Customizing choose Cross-
Application Components General Application Functions Postprocessing Office Display System Settings for the
Postprocessing Office and select Display Object Area.
Obj.Type Process Obj.Role PAI PBO Refresh

*)
BUS1006 CVI_01 2 MDS_PPO_BP_FCODE MDS_PPO_BP_ISDAT MDS_PPO_BP_REFR
KNA1 CVI_01 1 MDS_PPO_CUSTOMER_FCODE MDS_PPO_CUSTOMER_ISDAT MDS_PPO_CUSTOME
KNA1 CVI_03 2 MDS_PPO_CUSTOMER_FCODE MDS_PPO_CUSTOMER_ISDAT MDS_PPO_CUSTOME
LFA1 CVI_02 1 MDS_PPO_VENDOR_FCODE MDS_PPO_VENDOR_ISDAT MDS_PPO_VENDOR_
LFA1 CVI_04 2 MDS_PPO_VENDOR_FCODE MDS_PPO_VENDOR_ISDAT MDS_PPO_VENDOR_
*) Object Role:
1 = Main object
2 = Basis object
3 = Environment object
4 = Additional environment object
**) Hide Key X = yes
PAI: Function module you can use to react to user actions.
PBO: Function modules for reading additional data for the current object (for example, for displaying on a screen).
Program: Enter the program name here of the function group of the function modules mentioned above.
8. In SAP Customizing choose Cross-Application Components Master Data Synchronization Synchronization

Control Synchronization Control Activate PPO Requests for Platform Objects in the Dialog and for the synchronization
object BP, set the PPO Active indicator. Choose the synchronization objects that you use in your application and that you
designated as platform objects.
Blocking and Deleting Personal Data

Use
The processes and functions of Contract Accounts Receivable and Payable use personal data of the SAP business partner. If,
from the point of view of these processes and functions, there is no longer any reason to store the data (for example, for a
possible tax audit), you can block this data from the perspective of Contract Accounts Receivable and Payable and ultimately
destroy it.
4/11/2019
For destroying personal data, use the functions of Information Lifecycle Management (ILM). Using the ILM functions, you rst
block the personal data of business partners, for whom there is no further business. Then you delete this data as soon as it is no
longer needed.
More Information
SAP Information Lifecycle Management
Integration with SAP NetWeaver Information Lifecycle Management
Business Partner End Of Purpose (EoP)

Check
Use
Contract Accounts Receivable and Payable (FI-CA) checks whether data of business partners with the contract partner role
(MKK) exists and whether it is still relevant for business activities or can be blocked.
Prerequisites
You have activated the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF) and one of the
following industry business functions depending on the industry solution you are using.
Industry Business functions to be activated
Business Function Set Technical Name of Business Function Description of Business Function
FI-CAX FICAX_BUPA_BLOCKING Blocking of Business Partners
UTILITIES ISU_BUPA_BLOCKING Blocking of Business Partners
TELCO TEL_BUPA_BOCKING Blocking of Business Partners
PUBLIC_SERVICES PSCD_BUPA_BLOCKING Blocking of Business Partners
INSURANCE INS_FSCD_BUPA_BLOCKING Blocking of Business Partners
MEDIA MED_BP_BLOCKING Blocking of Business Partners
Technical Details
EoP Check Implementation
To block business partners with the contract partner role (MKK):
1. Check whether business partner data is still relevant for business activities using the mass activity Check Whether
Business Partner Data Can Be Blocked (transaction FPDPR1).
The EoP check for Contract Accounts Receivable and Payable supports the use of application rule variants based on
application-speci c condition elds. You map application-speci c condition elds to application rule variants in
Customizing for Contract Accounts Receivable and Payable under Contract Accounts Receivable and Payable Technical
Settings Data Protection Specify Determination of Rule Variants .
4/11/2019
If the check nds that business partner data is no longer required, the program derives the appropriate rule variant from
Customizing.
The program calculates the end of residence time (representing the EoP) based on the residence periods maintained for
the ILM object CA_BUPA that is active for the audit area BUPA_DP for the application MKK and the existing rule variants.
This information is made available to the blocking program (transaction BUPA_PRE_EOP).
2. Block business partner data no longer required by business activities using transaction BUPA_PRE_EOP.
For more information, see chapter Blocking and Unblocking of Business Partners.
Contract Accounts receivable and Payable uses the following tables:
Tables Used to Store Data Relevant for Blocking
Technical Name of Table Use
DFKKDPR_BP These transparent tables store the start of retention time (SoRT) as
calculated by the check program (transaction FPDPR1).
DFKKDPR_BP_SORT
The information in these tables is processed by the blocking
program.
DFKKDPR_BP_ROLE This database table is an index table for documents with business
partners with more than one role, for example, contract partner and
alternative payer.
DFKKDPR_BP_ASORT This database table stores archiving information so the check

(transaction FPDPR1) does not have to access the archive.
Initial Load Reports
The end of purpose check does not consider business partner data that existed in your system before you implemented the
check, that is, before you activated the appropriate business functions mentioned above. To include this data into the check, you
use the following initial load reports to populate the appropriate tables:
Report Name Use To Be Used When Affected Data
RFKKDPR_BP_INIT Use this report after you have You use this report only once.
activated the appropriate
industry business function to
insert existing business
partners into the transparent
table DFKKDPR_BP.
RFKKDPR_BP_ROLE_FKKOP_INIT Use this report after you have You use this report only once.
populate the database table
DFKKDPR_BP_ROLE with
existing documents.
RFKKDPR_BP_ROLE_ORDERPOS_INIT Use this report after you have You use this report only once.
industry business function to  Note
If you do not use
requests, you do not have
existing requests.
to execute the report.
4/11/2019
Report Name Use To Be Used When Affected Data
RFKKDPR_BP_ROLE_P2P_INIT Use this report after you have You use this report only once.
industry business function to  Note
If you do not use
promises to pay, you do
existing promises to pays.
not have to execute the
report.
RFKKDPR_MIG Use this report after you have For each archive le you use
activated the appropriate this report only once.
populate the database table  Note
DFKKDPR_BP_ASORT with
If you have not archived
data that has been archived
any data yet, you do not
before you activated the
have to execute the
business function.
report.
RFSCDDPR_BP_ROLE_VVSCPOS_INIT Use this report after you have

 Note
industry business function to Use this report only if you
populate the database table are using Contract
DFKKDPR_BP_ROLE for Accounts Receivable and
existing payment plan items. Payable as part of SAP
for Insurance.
You use this report only once.
Handling of Archived Data
Contract Accounts Receivable and Payable collects information related to the start of retention of business partners during
archiving runs in the DFKKDPR_BP_ASORT database table.
The initial load report RFKKDPR_MIG populates the DFKKDPR_BP_ASORT table in the same way as the archiving run would.
To determine whether archived business partner data is still relevant for business activities, the check program (transaction
FPDPR1) only analyzes the DKDDDPR_BP_ASORT database table. The program does not accesses archiving les or the archive
information system.
See Also
See the application help for SAP ERP at http://help.sap.com/erp under SAP ERP Cross-Application Functions Cross-
Application Components :
Data Protection
See the data protection section of the security guide for SAP S/4HANA, On Premise at http://help.sap.com/s4hana.
In the SAP Customizing Implementation Guide under Cross-Application Components, see the Data Protection chapter.
4/11/2019
Blocking and Unblocking of Business

Partners
Use
Transaction BUPA_PRE_EOP (central blocking program of SAP business partner on the SAP Easy Access screen for Cross-
Application Components under Data Protection) checks all registered applications and their function modules for whether the
end of purpose has been reached and whether a business partner can be blocked. You register the applications and function
modules in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking of Data . There the
speci cation for application MKK (software component Contract Accounts Receivable and Payable (FI-CA)) is that a check is to
be made for the end of purpose for business partners with the contract partner role. The related function module is entered as
a standard setting.
Applications that use the SAP business partner determine whether a business partner can be blocked by using application-
speci c functions. The necessary checks can take place at runtime of the blocking program.
Due to the large volume of data in Contract Accounts Receivable and Payable, the checks for blockability are scheduled before
the execution of the blocking program for application MKK. That means:
1. The rst step is for you to determine in Contract Accounts Receivable and Payable which business partners can be
blocked. To do so, you schedule the mass activity Check Whether Business Partner Data Can Be Blocked (FPDPR1) on
the SAP Easy Access screen under Periodic Processing For Data Protection (see Check for End of Purpose in Contract
Accounts Receivable and Payable).
2. Following that, you schedule the program for blocking business partners (transaction BUPA_PRE_EOP).
Transaction BUPA_PRE_EOP blocks a business partner if none of the called applications reports a purpose and the residence
period has been exceeded.
Contract Accounts Receivable and Payable performs the following actions when blocking a business partner:
Synchronizes the central blocking indicator (BUT000-XPCPT) in the shadow table of Contract Accounts Receivable and
Payable (assuming this table is active)
Sets a posting block in all contract account relationships of the business partner
In this way, the posting of new open items is prevented centrally. It is not possible to remove this block.
Sets the deletion ag for all contract account relationships of the business partner
Deletes and updates the trigger for exchanging messages with SAP Credit Management
If there was existing communication with SAP Credit Management, this prevents new communication.
Blocks the user in SAP Tax Payer Online Service (if one exists)
This prevents a taxpayer from logging on.
Note
You can add additional customer-speci c actions (see Customizing for Cross-Application Components under Data
Protection Blocking and Unblocking of Data Business Partner Business Add-Ins (BAdIs) BAdI: Exportation of SORT Details
of Blocked/Unblocked BP to FS Memory ).
4/11/2019
After business partners have been blocked, you can restrict access to their master data and transaction data using
authorization groups. To do so, you enter an authorization group, for which only speci c users have authorization, on the
contract account of the business partner. De ne the authorization group in Customizing for Contract Accounts Receivable and
Payable under Technical Settings Data Protection Enter Authorization Group for Contract Account Relationships . When a
business partner is blocked (transaction BUPA_PRE_EOP), the system enters this authorization group in the contract account
relationships of the business partner.
Note
For insurance object relationships, you enter authorization groups in Customizing for Contract Accounts Receivable and
Payable under Technical Settings Data Protection De ne Authorization Groups for Insurance Object Relationships .
When you unblock a business partner, the shadow table is synchronized, the posting lock is removed, and the deletion ag and
authorization group on the contract account and insurance object (industry component Insurance (FS-CD)) are reset to how
they were before the business partner was blocked. Contract Accounts Receivable and Payable does not perform any other
actions beyond these.
More Information
Blocking and Unblocking Business Partner Data
Block and Unblock Business Partner Data
Request Unblocking
Check for End of Purpose in Contract

Accounts Receivable and Payable
Use
The mass activity Check Whether Business Partner Data Can Be Blocked (transaction FPDPR1) checks in Contract Accounts
Receivable and Payable and its industry components whether the end of purpose has been reached for a business partner and
determines the retention start. The result of the analysis is stored in database tables DFKKDPR_BP and DFKKDPR_BP_SORT
and is analyzed further in transaction BUPA_PRE_EOP.
Prerequisites
In addition to the SAP business partner, you de ned the application rule variants for the application MKK in Customizing for
Cross-Application Components under Data Protection Blocking and Unblocking of Data Business Partner De ne and Store
Application Rule Variants for EoP Check .
In transaction IRMPOL, you de ned residence rules in the ILM policy for the ILM object CA_BUPA in audit area BUPA_DP. In
addition, you de ned retention rules there for the ILM object CA_BUPA in your own de ned audit area. In doing so, you use the
application rule variants that are already de ned.
Features
4/11/2019
Contract Accounts Receivable and Payable performs numerous analyses on the basis of application-speci c object types, such
as the FI-CA document. Some of these analyses determine if open business transactions exist for a business partner. If there
are open business transactions, the business partner is not allowed to be blocked. The system also determines a retention start
date using these speci c application objects. In combination with the residence period de ned in ILM, the date is determined,
starting from which a business partner can be blocked. A business partner has no open business transactions, if the following
conditions (for example) are ful lled:
The business partner has no open items.
There are no open items, in which the business partner is entered in another role, such as an alternative payer.
The business partner is not entered in any contract account as an alternative payer.
There are no open request items for the business partner.
There are no open (non-cash) security deposits for the business partner.
There are no active SEPA mandates for the business partner.
You can see all application objects that Contract Accounts Receivable and Payable includes in the check in Customizing for
Contract Accounts Receivable and Payable under Technical Settings Data Protection Make Speci cations for Customer-
De ned Application Objects . You can also create your own customer-speci c checks in the customer namespace.
Note
You can access information about the individual application objects and the analyses implemented in them by choosing
on the detail screen for the application object.
Activities
On the SAP Easy Access screen, choose Periodic Processing For Data Protection Check Whether Business Partner Data Can
Be Blocked .
As soon as one of the checks nds that there is an open business transaction for business partner, no further checks are
performed. Only if all checks do not nd an open business transaction, then the system determines the retention start, using all
application objects that determine this date.
Note
To improve performance, you should have the system perform those checks rst that frequently nd an open business
transaction. In Customizing for Contract Accounts Receivable and Payable under Technical Settings Data Protection Enter
Priority for Application Objects During Check If Can Be Blocked , de ne the sequence that ts your particular conditions.
 Example
For most business partners, no open items exist because they pay their receivables punctually when due. The system does
not post new open items for recurring monthly receivables until the following month, or for recurring annual receivables until
the next year.
If you can determine while the check is being run that the majority of business partners have an open item, then in that case,
checking for open items with a high priority would be useful.
That means that you execute the run after the items were posted but before payment was made. In this case, a check for
open items should have a high priority.
4/11/2019
If you use a contract object that has the status “Active”or “Inactive”, it can be bene cial to execute checks on the contract
status early. Provider contracts, in which the contract end date has not yet been set, are considered to be open business
transactions. A business partner can only be blocked when all of his or her provider contracts are expired.
Dealing with Blocked Business Partners

To protect personal data, you block business partners for which no more business has taken place, following a certain residence
time in the system. After that, displaying the personal data of a blocked business partner is only possible for users with special
authorization (role SAP_CA_BP_DP_ADMIN). The system prevents the entry of new business for blocked business partners.
You use transaction BUP_REQ_UNBLK to request unblocking; you use transaction BUPA_PRE_EOP to approve the unblocking of
business partners.
Displaying Personal Data

The personal data in Contract Accounts Receivable and Payable needing protection includes:
Name
Address data
Bank data
Payment card data
The technical keys that identify a business partner, a contract account, or an industry-speci c contract within the system are
not protected.
Free text elds, such as the contract account description or the text of a line item, do not require special protection.
Note
Note that industry components that use Contract Accounts Receivable and Payable may apply other, more stringent rules.
Users without special authorization do not have access to the personal data of a blocked business partner (role
SAP_CA_BP_DP_ADMIN). This means, for example, that these users are not able to display the master data of a blocked
business partner. Users without special authorization can continue to display data that is speci c to Contract Accounts
Receivable and Payable (such as the contract account or posting documents) for a blocked business partner, since this data
relates primarily to internal processes in Contract Accounts Receivable and Payable, such as payments and dunning, and less to
the personal data of a business partner. However, within these objects, the system does not display personal data.
 Example
Users without special authorization can continue to display the account balance of a blocked business partner. In the display
of the account balance for the business partner, however, the system suppresses address data, bank data, or payment card
data. The user can navigate, as before, to the display of a posting document. The document display, however, shows neither
address data nor bank data nor payment card data.
Caution
Not all personal data in Contract Accounts Receivable and Payable can be assigned directly to a business partner. For
example, data in payment lot items is personal (bank data), but the payer is not always the person, whose items are being
4/11/2019
cleared by the payment. Make sure that you archive and/or delete data of this kind before the de ned residence period has
expired (see Personal Data Outside of Business Partner Master Data).
If a business partner is blocked, the system still normally allows changes to objects, as long as this does not result in new
business – assuming that the change to the objects would be allowed if the business partner was not blocked.
 Example
In order to avoid adverse effects in customer-speci c follow-on processes, users without special authorization can make
changes to the contract accounts of a business partner even if the business partner is blocked.
For objects that consist mainly of personal data, the system always prevents their display as soon as the business partner is
blocked. This includes:
SEPA mandates
SEPA direct debit pre-noti cations
Correspondence
Preventing New Business

The system prevents new business from arising for blocked business partners as follows:
For a blocked business partner, it is not possible to create new master data, such as contract accounts, prepaid
accounts, or industry-speci c contracts.
You cannot use blocked business partners as alternative payers in other contract accounts or contracts.
You cannot post new documents for blocked business partners.
You cannot post any documents, in which a blocked business partner is entered in another role, such as an alternative
payer.
You cannot reverse any posting documents for a blocked business partner, and resetting clearing is also not possible.
You cannot generate event-controlled or periodic correspondence for a blocked business partner.
Special Cases When Dealing with Blocked

Business Partners
The following table shows special cases that in part differ from the normal situation in Contract Accounts Receivable and
Payable, and where you should therefore take special care.
Function Note
Search Helps If the user does not have authorization for displaying blocked business partners, the
system does not display blocked business partners in the list of results for business
partner search helps. Other seach helps, such as search helps for the contract account,
suppress personal data in the results list.
Revenue Distribution If you use classic or enhanced revenue distribution, be aware that it is not possible to tell
directly from the business partner master record or the contract account of a business
4/11/2019
partner, if the business partner is used as the nal recipient for classic or enhanced
revenue distribution.
Transaction FPDPR1, which checks if business partners can be blocked, therefore does
not check if a business partner is the nal recipient for a revenue distribution and if open
items still exist or distributions are still outstanding that contain this business partner or
one of her contract accounts as the nal recipient. The transaction checks only if open
items still exist for a business partner. If no more business takes place, the business
partner is blocked once the residence period has expired. The results are as follows:
For business partners that are used as the nal recipient in many documents,
new distribution documents are created due to regular clearing of the documents
with the mass activity Revenue Distribution (transaction FP60M) or mass
activity Post Distribution Document or Revenue Distribution: Create and Post
Documents (transaction FP60P). You can prevent unintentional blocking of a nal
recipient by the mass activity Check Bus. Partner Can Be Blocked and the
subsequent program for blocking business partners (transaction
BUPA_PRE_EOP) by choosing a residence period that is long enough and
executing the mass activity for revenue distribution and posting on a regular
basis.
If a business partner is used as a nal recipient in only one or very few

documents (for example, in the case of a government agency requesting
assistance from another government agency) and if the documents were not
cleared over a long period or if clearings were reset, then, despite the revenue
distribution programs being run, no new postings are generated on the account of
the nal recipient. If the de ned residence period is expired, then the mass
activity Check Bus. Partner Can Be Blocked and the subsequent program for
blocking business partners (transaction BUPA_PRE_EOP) can block the nal
recipient unintentionally, although there are still open documents for this nal
recipient. To prevent this, you should choose a residence period that is long
enough, and clear the documents during this period (for example, by writing them
off) if it is to be expected that invoices will not be paid in cases of inter-agency
assistance.
 Recommendation
To be able not to block certain nal recipients at all, or to run special checks
for them, create your own customer-speci c application object for the nal
recipient and implement your own check of the end of purpose for this
application object. Assign a separate application rule variant to this
application object in Customizing.
If a business partner that is used as a nal recipient is blocked, the following activities
are prevented:
You cannot create new documents with the business partner as nal recipient.
Clearing reset is no longer possible for documents with the business partner as
nal recipient.
The mass activity Revenue Distribution (transaction FP60M) does not generate
any new entries in the revenue distribution table DFKKRDI.
The mass activity Post Distribution Documents and program Revenue

Distribution: Create and Post Documents (transaction FP60P) do not generate
any new distribution documents for the blocked business partner.
If you have to perform one of these activities, you have to unblock the business partner.
To do so, you use the transaction for requesting unblocking business partners
(BUP_REQ_UNBLK) and for blocking them (BUPA_PRE_EOP).
Correspondence History The system does not display entries for blocked business partners.
Correspondence Printing You cannot repeat printing for a blocked business partner.
4/11/2019
Financial Customer Care A blocked business partner is no longer found in Financial Customer Care (FCC) in SAP
CRM, and therefore can also not be con rmed. Access to the functions of FCC is
therefore no longer possible.
SEPA Mandates You cannot access SEPA mandates of blocked business partners.
SEPA Direct Debit Pre-Noti cations You cannot access SEPA direct debit pre-noti cations of blocked business partners.
Customer Contacts You cannot access customer contacts of blocked business partners.
SAP Biller Direct A user for a blocked business partner can no longer log on to SAP Biller Direct. Check for
your own company, if these users have to be deleted.
Interest Calculation The mass activity Check Bus. Partner Can Be Blocked does not analyze the calculation
of interest. An interest calculation can take place for items that were already cleared. The
interest calculation itself does not perform any checks for blocked business partners.
Posting an interest document is not possible due to the posting block for a blocked
business partner. Therefore the system issues an error message to that effect in the
application log. Ensure within your organization that the interest runs are performed on a
periodic basis, so that no interest run processes blocked business partners. This can
apply to the following processes:
Item Interest Calculation
Calculation of Interest on Installment Plans
Calculation of Interest on Cash Security Deposits
Balance Interest Calculation
If you have to perform one of these activities, you have to unblock the business partner.
To do so, you use the transaction for requesting unblocking business partners
(BUP_REQ_UNBLK) and for blocking them (BUPA_PRE_EOP).
Migration Workbench Make sure that data from the migration workbench are deleted early.
Submission to Collection Agency You can submit already cleared items to collection agencies.
In order to prevent business partners from being blocked too early, the system takes into
account the communication data with collection agency in database table
DFKKCOLI_LOG.
 Note
Depending on the size of the table, this access can be demanding on performance.
Check if it is necessary to create a suitable index in the customer namespace.
Information Containers Information containers are using for communication between applications and systems. If
a business partner is blocked, the SAP standard processes do not generate any new
entries for information containers.
Check if your own customer-speci c information container categories need to be

adjusted. You have to periodically delete the messages in the XI monitor. A re-send of
already sent messages in an information container is possible, so that the
communication between the systems and applications can be re-established.
The following table shows special cases that in part differ from the normal situation in the industry solution component
Insurance, and where you should therefore take special care.
Function Note
Broker Collections If there is no more business activity, you can also block brokers.
You cannot assign a blocked broker to insurance objects, nor can
you enter him or her in line items as an alternative collecting broker.
4/11/2019
You can also no longer create new broker reports or new broker
report items for blocked brokers.
Coinsurance No special checks take place for coinsurers. The system assumes
that active coinsurers receive new open items periodically by
means of transaction VRCN.
If the business relationship with a coinsurer ends, check if the

related coinsurance key has to be removed or if the entry has to be
limited chronologically (recording active starting from
12/31/9999).
The following table shows special cases that in part differ from the normal situation in the industry component Public Sector
Contract Accounts Receivable and Payable, and where you should therefore take special care.
Function Note
Tax Payer Online Service (TPOS) If a business partner is blocked, then the user assigned to him or
her for the Tax Payer Online Service is also blocked. Check if such
users have to be deleted.
Deleting Business Partners

Use
If all applications that use business partners have reported that a business partner has no purpose and the residence period is
expired, then the system blocks the business partner, preventing access by dialog users and business processes. The write
program of business partner archiving writes these business partners to an archive le and deletes them from the database.
Data destruction destroys personal data for a business partner only if the retention period con gured in ILM Retention
Management has expired.
You can use SAP ILM to delete business partner data from the system after the expiration of a certain, possibly legally speci ed
timeframe.
More Information
Deletion of Business Partner Data
Using ILM Retention Management in the Application System
Dealing with Personal Data Outside the

Business Partner
Not all personal data is assigned directly to a business partner. In these cases, you have to ensure by means within your
organization (not in the system) that all data is archived or deleted in time (see Integration with SAP NetWeaver Information
Lifecycle Management).
 Example
Data from payment lot items (or items from other incoming lots) is personal data, but it is not directly assigned to a
business partner. The payer is also not always the person, whose items are being cleared by the payment. In order to prevent
4/11/2019
data from payment lot items from being displayed while a business partner is blocked, you have to delete the payment lot
data at the right time.
If you block business partners after 2 years, then you also have to archive and delete payment lot data at the latest after 2
years.
 Example
To improve performance, the payment list does not check whether the affected business partners are blocked. Therefore,
you have to delete or archive the payment run early.
For data that you do not have to retain and that you do not archive, separate deletion programs are available on the SAP Easy
Access screen under Periodic Processing Delete Data .
On the SAP Easy Access screen, choose Periodic Processing Delete Data Other Objects (transaction FPDEL_TAB) to delete
data from tables that you do not archive (see Deletion of Other Objects).
 Example
You use the transaction Delete Other Objects to delete data of repayment requests. Repayment requests are also included
in the data that is not directly assigned to a business partner.
If you block business partners after 2 years, then you also have to archive and delete repayment requests at the latest after
2 years.
System Con guration

Use
You are using the rules of SAP Information Lifecycle Management (SAP ILM) to manage the life cycle of business partner
master data. For more information about the general options for con guring SAP ILM, see the documentation for SAP ILM.
You make the system settings that are speci cally for data protection in Contract Accounts Receivable and Payable in
Customizing for Contract Accounts Receivable and Payable under Technical Settings Data Protection . There, in additions to
global settings, you make settings for the application objects, the sequence of checks, the rule variants, and the determination
of the retention start date.
Global Settings
You make general settings in the Make Global Settings for Protection of Personal Data activity. There you enter the following
parameters:
Posting Block
From the start of the retention period until deletion, you can no longer make any postings with reference to business-
partner-related data. To achieve this you set a posting block in the master record of the contract account. The system
transfers the posting block entered there when blocking a business partner.
Days Until Next Check (BP with Open Bus.Trans.) and Days Until Next Check (BP Without Open Bus.Tr.)
By making an entry in these elds, you limit the time period in which the system again checks a business partner
(with/without open business transactions). The time period extends from the time of the last check until the number of
4/11/2019
days is reached that you enter in this eld. The system sets the date for the next check at random within this time
period. If you do not make any entry in this eld, the next check takes place automatically with the next program run.
Account in Archive
If you set this indicator, the system also includes archived contract accounts in the determination of the retention start
date.
Rule Variant
If there is no transaction data in Contract Accounts Receivable and Payable, then the rule variant you enter here acts as
the rule variant for the business partner ILM object (CA_BUPA).
Settings for Application Objects
In the Make Speci cations for Customer-De ned Application Objects activity, you can add your own application objects to the
application objects considered in the SAP standard system De ne the application objects using a freely de nable key and a
description. Enter a class that determines either open business transactions or the start of the retention period.
If the application object should be used for determining open business transactions, then the class must implement the
IF_FKKDPR_BP_ACTIVITY interface and the Open Transactions indicator must be set. If the application object should be
used for determining the retention start, then the class must implement the IF_FKKDPR_BP_SORT interface and the Det. Ret.
Start indicator must be set.
Sequence of Checks
The system processes application objects in a certain sequence. The priority speci es this sequence in the form of a number.
The lower the number, the higher the priority with which the system processes an application object. If no priority is assigned to
an application object, then the system processes this application object at the end, together with the application objects with
the lowest priority.
For the application objects considered in the SAP standard system, SAP provides priorities that you can overwrite in the Enter
Priority for Application Objects During Check If Can Be Blocked activity. The most suitable priority depends on the industry
component you are using and the type of data in your installation.
Recommendation
To improve performance, set the priorities in accordance with the speci c conditions of your installation. Set a high priority
for checks that recognize open business transactions in the majority of cases.
Rule Variants
The application rule variants are available as condition elds for application MKK. They are used both for determining the
residence time and the legal obligation to retain data on the SAP business partner. The application rule variants are determined
dependent on the application objects and the company code. They are stored during a blocking run (transaction
BUPA_PRE_EOP), together with the start of the retention period, in table BUTSORT. During archiving of the SAP business
partner, the rules entered in transaction IRMPOL are evaluated based on the stored application rule variants, and the system
determines the end of the legal obligation to retain data on the SAP business partner.
You con gure the rule variants by following these steps:
1. Enter rule variants in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking
of Data Business Partner De ne and Store Application Rule Variants for EoP Check .
Enter the rule variants there with application name MKK.
4/11/2019
2. De ne the derivation of rule variants. In Customizing for Contract Accounts Receivable and Payable under Technical
Settings Data Protection , assign appropriate rule variants to the legal obligations.
The system, in which Contract Accounts Receivable and Payable is running, determines the rule variant from the
combination of the application object and the company code. In this activity, you de ne the combinations that are used.
The following example provides an overview of the rules to be de ned in SAP ILM.
 Example
You retain business partners, for whom documents exist in company code CCDE, for 10 years and you de ne a rule variant for
this.
You retain business partners, for whom documents exist in company code CCFR, for 8 years and you de ne an additional rule
variant for this.
You assign all other application objects that do not relate to documents to a general rule variant.
Application Object Company Code Rule Variant
0001 (FI-CA Document) CCDE RV_DOC_DE
0001 (FI-CA Document) CCFR RV_DOC_FR
* * RV_GEN
You enter rule variant RV_GEN in Customizing in the Make Global Settings for Data Privacy Functions activity. This rule
variant is then applied when a partner no longer has any transaction data.
If the norm is for partners to be blocked after 2 years, then you de ne the ILM rules without an application and rule variant.
Condition Fields Rule
Residence Duration Unit Time Reference/Time

Offset
2 Years START_RET_DATE
If a business partner is to be deleted according to the rule variants, then select the application and rule variant as condition
elds and de ne the ILM rules.
Condition Fields Rule
Application Name Application Rule Retention Period Unit Time Reference/Time

Variant Offset
MKK RV_DOC_DE 10 Years START_RET_DATE
MKK RV_DOC_FR 8 Years START_RET_DATE
MKK RV_GEN 4 Years START_RET_DATE
Assume that the following two business partners do not have any open business transactions:
Business Partner Company Code CCDE Company Code CCFR Other Data
PARTNER1 Last payment on 10/10/2010 Last payment on 11/11/2011 None
4/11/2019
PARTNER2 No documents Documents exist, last payment Correspondence from
on 01/01/2001 09/09/2010
You start transaction BUPA_PRE_EOP on 01/01/2014. At this point in time, the residence period of two years has been
exceeded by both partners. The program saves the following data (not an exhaustive list) for Contract Accounts Receivable
and Payable (application name MKK) in table BUTSORT. It evaluates this data later during archiving of the SAP business
partner.
Business Partner Application Name Application Rule Variant Start of the Retention Period
PARTNER1 MKK RV_DOC_DE 10/10/2010
PARTNER1 MKK RV_DOC_FR 11/11/2011
PARTNER2 MKK RV_DOC_FR 01/01/2001
PARTNER2 MKK RV_GEN 09/09/2010
The result is that the SAP business partner PARTNER1 is not deleted before 10/10/2020 (10/10/2010 + 10 years >
11/11/2011 + 8 years) and partner PARTNER2 is not deleted before 09/09/2014 (01/01/2001 + 8 years < 09/09/2010 + 4
years).
Note
Check the retention rules for the ILM objects of Contract Accounts Receivable and Payable and for the SAP business partner
(ILM object CA_BUPA) against each other (see also Dealing with Personal Data Outside the Business Partner).
Settings for Integration of Sales and Distribution (SD) with FI-CA
If you have integrated Contract Accounts Receivable and Payable with Sales and Distribution (SD), you have to ensure that you
check not only the business partner for the end of purpose, but also the related customers.
In the standard SAP system, business partners and customers are linked by having the same name. Keep in mind the following
with regard to the two supported integration scenarios:
Sales and Distribution and Contract Accounts Receivable and Payable run in the same system
When you execute transaction BUPA_PRE_EOP for a set of business partners, the system checks if a customer with the
same name exists for the account groups invoiced in Contract Accounts Receivable and Payable for a blockable business
partner. The system determines which account groups in Contract Accounts Receivable and Payable are invoiced by
using the settings in Customizing for Contract Accounts Receivable and Payable under Integration Sales and
Distribution De ne Posting to FI-CA for Customer Account Groups . If a customer of the same name exists for a
business partner, the system checks the end of purpose for that customer. The business partner can only be blocked
when the end of purpose of the customer has been reached.
When you execute transaction CVP_PRE_EOP for a set of customers, the system checks if a business partner with the
same name exists for the account groups invoiced in Contract Accounts Receivable and Payable for a blockable
customer. The system determines which account groups in Contract Accounts Receivable and Payable are invoiced by
using the settings in Customizing for Contract Accounts Receivable and Payable under Integration Sales and
Distribution De ne Posting to FI-CA for Customer Account Groups . If a business partner of the same name exists for a
customer, the system checks the end of purpose for that business partner. The customer can only be blocked when the
end of purpose of the business partner has been reached.
Sales and Distribution and Contract Accounts Receivable and Payable run in separate systems
4/11/2019
Before you can execute transaction BUPA_PRE_EOP in the FI-CA system for a set of business partners, you have to
connect to the integrated SD systems by means of RFC. In Customizing for Cross-Application Components, choose Data
Protection Blocking and Unblocking of Data Business Partner De ne RFC Destinations of Systems Connected to
Master Syst. . The business partner IDs blockable in the FI-CA system are forwarded to the SD systems. In the SD
system, there is a check of whether a customer with the same name exists for the account groups for a business partner
relevant for Contract Accounts Receivable and Payable. The account groups are determined in this process using the
system settings made in Customizing for Sales and Distribution under Basic Functions Integration with Contract A/R
and A/P Specify Posting to Contract A/R and A/P for Customer Groups . If a customer of the same name exists for a
business partner, the system checks the end of purpose for that customer. The business partner can only be blocked
when the end of purpose of the customer has been reached.
Before you can execute transaction CVP_PRE_EOP in an SD system connected to Contract Accounts Receivable and
Payable for a set of customers, you have to connect to the the FI-CA system by means of RFC. In Customizing for Cross-
Application Components, choose Data Protection Blocking and Unblocking of Data Business Partner De ne RFC
Destinations of Systems Connected to Master Syst. . The customer IDs and customer account groups that are blockable
in the SD system are forwarded to the FI-CA system. In the FI-CA system, there is a check of whether a business partner
with the same name exists for the account groups invoiced in Contract Accounts Receivable and Payable. The system
determines which account groups in Contract Accounts Receivable and Payable are invoiced by using the settings in
Customizing for Contract Accounts Receivable and Payable under Integration Sales and Distribution De ne Posting to
FI-CA for Customer Account Groups . If a customer of the same name exists for a business partner, the system checks
the end of purpose for that customer. The business partner can only be blocked when the end of purpose of the customer
has been reached.
The program behavior described here originates from BAdI implementation VFKK_BP_CUSTOMER_MAPPING_EOP.
Caution
In the standard SAP system, for the integation of Sales and Distribution and Contract Accounts Receivable and Payable,
business partners and customers are linked by having the same name. However, you can also use other integration
scenarios in the SAP system that are outside of Contract Accounts Receivable and Payable that are based, for example, on
customer and vendor integration. If you use customer and vendor integration, BAdI implementation
VFKK_BP_CUSTOMER_MAPPING_EOP isnot processed. (See Customizing for Cross-Application Components under Master
Data Synchronization Synchronization Control Synchronization Control Activate Synchronization Options .)
If you use customer and vendor integration, the assignment of business partners and customers is made using the
assignment data of customer and vendor integration.
An incorrect assignment of business partners and customers due to their having the same name can lead to the following
situations:
Business partner master records or customer master records are blocked too early.
This can happen, for example, if the customer master record belonging to a business partner or a business partner
belonging to a customer master record is not found.
Business partner master records or customer master records are not blocked.
This can happen, for example, if, due to the names being the same, a customer master record is found for a business
partner master record, or a business partner master record is found for a customer master record, although they are
not actually assigned to one another.
Note
If you use the scenario with distributed systems, specify a leading system. This is the only way to ensure that all business
partners and customers are checked. We recommend that the system you de ne as the leading system is the system that
4/11/2019
you use to centrally maintain business partner data, and from which you distribute the master data in your system
landscape to the connected systems.
More Information
Make Customizing Settings for ILM Rules
Integration with SAP NetWeaver Information Lifecycle Management
IS-U Business Partner: Special Features

This documentation section contains information about enhancements and variations from the SAP Business Partner described
above, which apply speci cally to SAP Utilities (IS-U).
GP Role Installer (IS-U)

De nition
An installer is a person licensed by a utilities company to carry out installation work.
Structure
You need the role ISUI and the role category ISUI for the BP role Installer (IS-U).
In addition to the address data, you can also enter status management and general data using this role. In the general data you
can de ne data such as license for certain divisions, operating purpose of the company and the identi cation number of the
license. In the status management you can de ne data such as the type of license and the date of the initial license.
BAPIs for Central Business Partner (IS-U)

Use
The Business Object Repository (BOR) contains the following Business Application Programming Interface (BAPIs) for the
business partner:
UtilBusinessPartner.CreateFromData (Creating a Business Partner)
UtilBusinessPartner.Change (Changing a business partner)
UtilBusinessPartner.GetDetail (Displaying a business partner)
UtilBusinessPartner.GetList (Displaying a business partner)
For more information about BAPIs see the following documentation:
See the BAPI user manual and the BAPI Programming Guide
For more detailed information, see the documentation of the individual BAPIs in BOR.
4/11/2019
Merging Business Partners (IS-U)

Purpose
Note
Note that you can only use the functions described in this documentation section (Merging Business Partners (IS-U)), if you
are using the industry solution SAP Utilities .
You can use the business partner merging function in connection with the central business partner (SAP application component
CA-BP Contract Accounting – Business Partner) and Contract Accounts Receivable and Payable (FI-CA Financial Accounting –
Contract Accounting).
Implementation Considerations
The following SAP notes contain more information about business partner merging:
Title of SAP Note SAP Note
FAQs for Transferring Open Items (FP40) 616098
IS-U Transactions and Batch Input 432178
Merging Business Partners 624341
Move-In: No Meter Reading Results Proposed 503243
Integration
Part of the central business partner concept is that every natural or legal person as well as every group is only created once in a
system. There are different reasons why a business partner is created several times in one system. Business partners that have
been created more than once are referred to as duplicates. Duplicates can occur due to the following reasons:
Migration from legacy systems without merging business
Migration from different legacy systems without a duplicate check
New creation of business partners in SAP systems without duplicate checks
Data Cleansing
You can use the data cleansing tool Cleansing Tool (transaction CLEAR_INT) to process duplicates. It has been available since
ABAP Release 5.0A, and is already used by the SAP business partner (as of SAP CRM Release 3.0, for example).
Note
These data cleansing functions are not released for systems with industry add-ons.
Features
The following information about business partner objects and other functions and tools is available for business partner
merging:
4/11/2019
Objects in Contract Accounts Receivable and Payable
Objects and Enhancements in SAP Utilities
Customer Change
Objects and Enhancements in SAP CRM
Automatic Business Partner Merging
In the following, the business partner to be removed from the system is referred to as the source business partner. The
business partner that replaces the source business partner is referred to as the target business partner.
Objects in Contract Accounts Receivable and

Payable
De nition
Business partner-dependent objects from Contract Accounts Receivable and Payable (FI-CA) must be handled separately
during business partner merging in order to ensure that they remain consistent after the business partners have been merged.
These objects include, the contract account, the business partner’s open items, his or her creditworthiness and clari cation
cases.
Use
Master data
Contract account
Each contract account is only allocated to one business partner. You cannot immediately allocate the contract account to
another business partner. First of all, you must close the contract account and create another one before you can do this. Set
the indicator Mark Contract Account for Deletion ( eld LOEVM in table FKKVKP) in the old contract account
However, the source business partner can still be used as a reference in the following contract account elds:
Payer ( eld GPARV in contract account table FKKVKP)
Alternative Payer ( eld ABWRE in contract account table FKKVKP)
Alternative Payee ( eld ABWRA in contract account table FKKVKP)
Alt. Dun. Recipient ( eld ABWMA in contract account table FKKVKP)
Correspondence Recipient ( eld RECEIVER in contract account table FKKVK_CORR)
Alt. Bill Recipient ( eld ABWRH in contract account table FKKVKP)
When business partners are merged, you must determine the corresponding contract accounts and change the elds above to
the target business partner.
Note
When you do this, note the following:
You must also enter a contract account in the Paid By eld (VKONV in table FKKVK) for the payer
4/11/2019
When you change the alternative payer and recipient, you must also change the bank details and payment card data
accordingly.
You must also change any addresses de ned in the contract account for the business partners mentioned above.
Transaction Data
Open Items
In Contract Accounts Receivable and Payable (IS-U-CA), you can use the Transfer Items (FP40) transaction to transfer items to
another contract, contract account or another business partner. During this process, the system creates transfer documents,
which you can also reverse.
This is also possible for open items that have been entered in installment plans and collective bills.
The system can create the corresponding histories (dunning and installment plan histories) for documents created in the target
account.
Caution
Note the following points for open items:
Items that have been submitted to a collection agency cannot be transferred.
The returns history for transferred items is not updated.
The interest history and accompanying interest supplement are not updated.
In SAP Utilities, transferring open items is part of the customer change (see customer change ).
SAP note 616098 contains frequently asked questions (FAQs) about the Transfer Items function.
For further information about transferring items, see the SAP Utilities documentation in the SAP Help Portal under
http://help.sap.com SAP for Industries SAP for Utilities Contract Accounts Receivable and Payable Business
Transactions Transferring Open Business Partner Items .
Clari cation cases
When you process clari cation cases, there is no a function that automatically recognizes merged business partners.
You can enter the source business partner number in the following elds and evaluate the payment lot during processing:
External Business Partner Number ( eld BPEXT in the business partner table BUT000)
Contract Account Number in Legacy System ( eld VKONA in the contract account table FKKVK)
Reference Number of Business Partner in Contract Account ( eld EXVKO in the contract account table FKKVK)
The disadvantage of this procedure is that you can only enter and evaluate one number for each eld.
Business partner creditworthiness
Every business partner has creditworthiness data (de ned in the Utilities Industry Menu under Business Master Data Business
Partner Display/Change Creditworthiness ). If necessary, this data can be transferred from the source to the target business
during business partner merging.
4/11/2019
Creditworthiness data is not transferred with the functions Customer Change (SAP Utilities) or Transfer Items . As a result, you
must manually transfer the source business partner’s creditworthiness to the target business partner.
Automatically transferring data causes problems here because a separate decision has to be made in each case as to whether
the creditworthiness is transferred or not. A company that takes over an insolvent company, for example, does not necessarily
want the insolvent company’s creditworthiness to be transferred.

De nition
In addition to FI-CA objects, SAP Utilities also contains objects and enhancements that are dependent on the business partner
and must, therefore, be taken into consideration when business partners are merged.
Use
Master data
Utility contract
In a utility contract, you cannot change a business partner who was allocated using the contract account. As a result, you must
end the existing utility contracts before you can allocate another business partner to the utility contract.
You can use the customer change function to do this.
Owner allocations
Every premise can be allocated to a business partner, who is then de ned as the owner. All existing owner allocations for the
business partners to be merged must be allocated to a single business partner.
Depending on the Customizing settings made under SAP Utilities Customer Service Process Execution Owner
Allocation De ne Type of Owner Allocation , you must execute the following actions:
Maintenance via Premise
You must enter the owner’s target business partner directly in the premise.
Owner Allocation:
You must change the owner allocation in the Utilities Industry menu under Customer Service Process Execution Owner
Allocation Change Owner Allocation (transaction ES52).
Transaction Data
Budget billing plans
During a customer change, you can deactivate the budget billing plans for the terminated contracts without invoicing them and
transfer them to the new contracts.
Caution
All budget billing plan items must be open. If necessary, you must use a clearing reversal to make the payments on account.
Once you have successfully changed the customer, you must use account maintenance to allocate the payments on account
to the new budget billing plan.
4/11/2019
Security Deposits
During a customer change, you can transfer the security deposits from the terminated contracts to the new contracts.
Other documents from Contract Accounts Receivable and Payable
As with the customer change in SAP Utilities, other documents (that is documents that are not mentioned here) from FI-CA are
not included in this process. This especially applies to cleared documents.
Transaction Data from Sales and Distribution (SD)
The business partner is entered in sales documents from the Sales and Distribution (SD) component.
SD sales documents that have the source business partner entered as the payer are transferred to the target business partner.
This only takes place if the sales documents have not yet been invoiced.
FI-CA documents that originate from SD are transferred together with the open items.
Caution
SD transaction data cannot be transferred to the target business partner automatically.
Business Partner Contacts
Contacts are created with a reference to a business partner.
Caution
Contacts cannot be automatically transferred to the target business partner.
Constraints
When merging business partners in SAP Utilities, you must note the following information for the objects and data below:
Payment plans
Payment plans with the categories AMB and BBP cannot be transferred. If these kinds of payment plans exist, you
cannot execute a customer change.
Open items in deregulation
In SAP Utilities, you cannot use the Transfer Items (FP40) transaction to transfer open items in the deregulated
scenario Bill Processing by Third Party .
Collection item
Documents submitted to a collection agency cannot be transferred using the Transfer Items (FP40) transaction.
Creditworthiness data for business partner
A business partner’s creditworthiness data is not automatically transferred to the target business partner.
Customer Change
Use
4/11/2019
You use the customer change function to transfer the utilities contracts for a contract account, including any resulting
receivables, between business partners.
This can for example be necessary when merging business partners.
The following functions are possible:
Create customer change
Process customer change subsequently
Reverse customer change
Transfer post open items due to customer change
Integration
You can use the function SAP Utilities Customer Service Process Execution Move-In/Out and then the menu option
Other Create / Cancel Customer Change
Use the methods for the BOR object MOVEINOUT to integrate the customer change in the Customer Interaction Center (CIC)
or the front office. Transfer the parameter OK code with the value ".
Prerequisites
Before you can a execute customer change, the contracts to be transferred must have been invoiced at least once.
If you also want to transfer budget billing plans, the budget billing plan items must all be open. If necessary, you must reset all
clearings and set the accrued receivables to payments on account. Therefore, we recommend that you execute the customer
change as close as possible to the last bill in order to avoid this preparatory work.
Customizing
You de ne customer change reasons in Customizing for SAP Utilities under Customer Service Process Execution Move-
In/Out De ne Reasons for Customer Change .
You can also choose whether or not the following objects are also transferred during the customer change:
Security deposits
Open items
Dunning information
Note
See also the Customizing documentation for the individual components and the F1 eld help.
Features
When a customer change is created, the system terminates the transfer contract using a move-out, and creates a new contract
using a move-in. The move-out date is set as the end of the billing period of the most recently invoiced billing document
belonging to the transfer contract
4/11/2019
You can also append an actual move-out date to the move-out, and an actual move-in date to the move-in. This enables you to
document when the move-out customer actually vacated the apartment, and when the move-in customer occupied it. If this
data becomes valid at a future date, the changes to the business partner and contract account data of the move-out customer
are stored as scheduled changes, with the actual move-out date as the validity date. The changes to the business partner and
contract account data are stored as scheduled changes for the move-in customer with the actual move-out date as the validity
date.
When you create a move-out, an adjustment reversal of the most recent billing document takes place for the transfer contract
and a new billing document is created with the value 08 (Customer Change). This billing document contains the billing amount
"0. The most recent billed meter readings are also copied when the move-in is created. Note that constellations in the rate
structure (such as period-end billing for monthly customers, basic monthly price and so on) can result in the billing documents
from the adjustment reversal not having the amount "0.
Depending on the Customizing settings, no new meter reading results are entered. Instead, the last billed meter readings are
copied when the move-in is created (see SAP Note 503243).
When you save the move-in document, the open items in the transfer contract can be posted to the target contract created as
a result of the move-in (this depends on the Customizing settings described above). This is only possible within the same
company code. Items that have already been paid are not reposted. You use the Transfer Items transaction (FP40) to do this.
Depending on the Customizing setting you made previously, security deposits and dunning information can be transferred.
Interest history and supplements are not copied during transfer of the open costs.
Budget billing plans are treated as follows: They are deactivated by the move-out, once you have set the payment on account.
Depending on the Customizing settings, a new budget billing plan is created from the deactivated budget billing plan when you
save the move-in document. You then allocate the credit payments using the account maintenance.
The customer change assigns a posting block to the transfer contracts. You can display this block in the move-out document.
You can change the block using methods ReleaseFicaLock and SetFicaLock of BOR object MOVEOUTDOC.
Constraints
Open items that have been sent to a collection agency cannot be transferred.
The returns history is not transferred to the new target business partner.
The interest history and supplements are not copied when you transfer the open items.
The business partners credit rating data is not transferred.
Alternatives if customer change is not possible
If a contract has not yet been invoiced, proceed as follows:
Reverse the move-in document: Execute move-in with the correct business partner. You can use the move-in document
as a template.
Create an intermediate bill.
Wait for the next bill and then execute the customer change.

De nition
4/11/2019
If you integrate SAP Utilities with SAP CRM, you can use the data cleansing tool in SAP CRM to manage the business partner
merging cases and, in part, process them in SAP CRM.
Use
When objects are replicated between SAP CRM and SAP Utilities, any changes to the target business partner are made in SAP
CRM. The exception to this is the contract in SAP CRM. In this case, the target business partner is changed in SAP Utilities by
the customer change .
For further information about transfer functions for other objects in SAP Utilities, go to Objects and Enhancements in SAP
Utilities for Business Partner Merging .
Business Partner Agreement in SAP CRM
The business partner agreement in SAP CRM (corresponds to the contract account in SAP ERP) is integrated in data cleansing
as of SAP CRM Release 4.0.

Use
You can use BAPIs or BOR methods to automate individual steps of business partner merging. For further information on this,
see the SAP note 624341 (Merging Business Partners).
Features
You can use the following BAPIs for automatic business partner merging:
BAPI Description
BAPI_ISUACCOUNT_GETDETAIL Display contract account
BAPI_ISUACCOUNT_CHANGE Change contract account
BAPI_ISUPARTNER_GETDETAIL Display contract account
BAPI_ISUPARTNER_CHANGE Change contract account
BAPI_ISUPROP_GETDETAIL Detailed information on owner allocation
BAPI_ISUPROP_CREATEFROMDATA Create owner allocation
BAPI_ISUPROP_CHANGE Change owner allocation
BAPI_CTRACDOCUMENT_TRANSFER Transfer open FI-CA items
BAPI_CTRACCONTRACTACCOUNT_GD1 Read detailed FI-CA contract account data
BAPI_CTRACCONTRACTACCOUNT_CH1 Change FI-CA contract account
Note
Use mostly IS-U BAPIs to change master data in SAP utilities since these function modules contain additional elds for
interfaces.
4/11/2019
Caution
SAP does not recommend that you use the batch input procedure to automate steps. For further information on this, see
the SAP note 432178 (IS-U Transactions and Batch Input).
Requirements for automating the business partner merging have been included. If you require any support, contact SAP.
Merging Business Partners (IS-U)

Purpose
Note
Note that you can only use the functions described in this documentation section (Merging Business Partners (IS-U)), if you
are using the industry solution SAP Utilities .
You can use the business partner merging function in connection with the central business partner (SAP application component
CA-BP Contract Accounting – Business Partner) and Contract Accounts Receivable and Payable (FI-CA Financial Accounting –
Contract Accounting).
Implementation Considerations
The following SAP notes contain more information about business partner merging:
Title of SAP Note SAP Note
FAQs for Transferring Open Items (FP40) 616098
IS-U Transactions and Batch Input 432178
Merging Business Partners 624341
Move-In: No Meter Reading Results Proposed 503243
Integration
Part of the central business partner concept is that every natural or legal person as well as every group is only created once in a
system. There are different reasons why a business partner is created several times in one system. Business partners that have
been created more than once are referred to as duplicates. Duplicates can occur due to the following reasons:
Migration from legacy systems without merging business
Migration from different legacy systems without a duplicate check
New creation of business partners in SAP systems without duplicate checks
Data Cleansing
You can use the data cleansing tool Cleansing Tool (transaction CLEAR_INT) to process duplicates. It has been available since
ABAP Release 5.0A, and is already used by the SAP business partner (as of SAP CRM Release 3.0, for example).
Note
These data cleansing functions are not released for systems with industry add-ons.
4/11/2019
Features
The following information about business partner objects and other functions and tools is available for business partner
merging:
Objects in Contract Accounts Receivable and Payable
Customer Change
In the following, the business partner to be removed from the system is referred to as the source business partner. The
business partner that replaces the source business partner is referred to as the target business partner.
Objects in Contract Accounts Receivable and

Payable
De nition
Business partner-dependent objects from Contract Accounts Receivable and Payable (FI-CA) must be handled separately
during business partner merging in order to ensure that they remain consistent after the business partners have been merged.
These objects include, the contract account, the business partner’s open items, his or her creditworthiness and clari cation
cases.
Use
Master data
Contract account
Each contract account is only allocated to one business partner. You cannot immediately allocate the contract account to
another business partner. First of all, you must close the contract account and create another one before you can do this. Set
the indicator Mark Contract Account for Deletion ( eld LOEVM in table FKKVKP) in the old contract account
However, the source business partner can still be used as a reference in the following contract account elds:
Payer ( eld GPARV in contract account table FKKVKP)
Alternative Payer ( eld ABWRE in contract account table FKKVKP)
Alternative Payee ( eld ABWRA in contract account table FKKVKP)
Alt. Dun. Recipient ( eld ABWMA in contract account table FKKVKP)
Correspondence Recipient ( eld RECEIVER in contract account table FKKVK_CORR)
Alt. Bill Recipient ( eld ABWRH in contract account table FKKVKP)
4/11/2019
When business partners are merged, you must determine the corresponding contract accounts and change the elds above to
the target business partner.
Note
When you do this, note the following:
You must also enter a contract account in the Paid By eld (VKONV in table FKKVK) for the payer
When you change the alternative payer and recipient, you must also change the bank details and payment card data
accordingly.
You must also change any addresses de ned in the contract account for the business partners mentioned above.
Transaction Data
Open Items
In Contract Accounts Receivable and Payable (IS-U-CA), you can use the Transfer Items (FP40) transaction to transfer items to
another contract, contract account or another business partner. During this process, the system creates transfer documents,
which you can also reverse.
This is also possible for open items that have been entered in installment plans and collective bills.
The system can create the corresponding histories (dunning and installment plan histories) for documents created in the target
account.
Caution
Note the following points for open items:
Items that have been submitted to a collection agency cannot be transferred.
The returns history for transferred items is not updated.
The interest history and accompanying interest supplement are not updated.
In SAP Utilities, transferring open items is part of the customer change (see customer change ).
SAP note 616098 contains frequently asked questions (FAQs) about the Transfer Items function.
For further information about transferring items, see the SAP Utilities documentation in the SAP Help Portal under
http://help.sap.com SAP for Industries SAP for Utilities Contract Accounts Receivable and Payable Business
Transactions Transferring Open Business Partner Items .
Clari cation cases
When you process clari cation cases, there is no a function that automatically recognizes merged business partners.
You can enter the source business partner number in the following elds and evaluate the payment lot during processing:
External Business Partner Number ( eld BPEXT in the business partner table BUT000)
Contract Account Number in Legacy System ( eld VKONA in the contract account table FKKVK)
Reference Number of Business Partner in Contract Account ( eld EXVKO in the contract account table FKKVK)
4/11/2019
The disadvantage of this procedure is that you can only enter and evaluate one number for each eld.
Business partner creditworthiness
Every business partner has creditworthiness data (de ned in the Utilities Industry Menu under Business Master Data Business
Partner Display/Change Creditworthiness ). If necessary, this data can be transferred from the source to the target business
during business partner merging.
Creditworthiness data is not transferred with the functions Customer Change (SAP Utilities) or Transfer Items . As a result, you
must manually transfer the source business partner’s creditworthiness to the target business partner.
Automatically transferring data causes problems here because a separate decision has to be made in each case as to whether
the creditworthiness is transferred or not. A company that takes over an insolvent company, for example, does not necessarily
want the insolvent company’s creditworthiness to be transferred.

De nition
In addition to FI-CA objects, SAP Utilities also contains objects and enhancements that are dependent on the business partner
and must, therefore, be taken into consideration when business partners are merged.
Use
Master data
Utility contract
In a utility contract, you cannot change a business partner who was allocated using the contract account. As a result, you must
end the existing utility contracts before you can allocate another business partner to the utility contract.
You can use the customer change function to do this.
Owner allocations
Every premise can be allocated to a business partner, who is then de ned as the owner. All existing owner allocations for the
business partners to be merged must be allocated to a single business partner.
Depending on the Customizing settings made under SAP Utilities Customer Service Process Execution Owner
Allocation De ne Type of Owner Allocation , you must execute the following actions:
Maintenance via Premise
You must enter the owner’s target business partner directly in the premise.
Owner Allocation:
You must change the owner allocation in the Utilities Industry menu under Customer Service Process Execution Owner
Allocation Change Owner Allocation (transaction ES52).
Transaction Data
4/11/2019
During a customer change, you can deactivate the budget billing plans for the terminated contracts without invoicing them and
transfer them to the new contracts.
Caution
All budget billing plan items must be open. If necessary, you must use a clearing reversal to make the payments on account.
Once you have successfully changed the customer, you must use account maintenance to allocate the payments on account
to the new budget billing plan.
Security Deposits
During a customer change, you can transfer the security deposits from the terminated contracts to the new contracts.
Other documents from Contract Accounts Receivable and Payable
As with the customer change in SAP Utilities, other documents (that is documents that are not mentioned here) from FI-CA are
not included in this process. This especially applies to cleared documents.
Transaction Data from Sales and Distribution (SD)
The business partner is entered in sales documents from the Sales and Distribution (SD) component.
SD sales documents that have the source business partner entered as the payer are transferred to the target business partner.
This only takes place if the sales documents have not yet been invoiced.
FI-CA documents that originate from SD are transferred together with the open items.
Caution
SD transaction data cannot be transferred to the target business partner automatically.
Business Partner Contacts
Contacts are created with a reference to a business partner.
Caution
Contacts cannot be automatically transferred to the target business partner.
Constraints
When merging business partners in SAP Utilities, you must note the following information for the objects and data below:
Payment plans
Payment plans with the categories AMB and BBP cannot be transferred. If these kinds of payment plans exist, you
cannot execute a customer change.
Open items in deregulation
In SAP Utilities, you cannot use the Transfer Items (FP40) transaction to transfer open items in the deregulated
scenario Bill Processing by Third Party .
Collection item
Documents submitted to a collection agency cannot be transferred using the Transfer Items (FP40) transaction.
4/11/2019
Creditworthiness data for business partner
A business partner’s creditworthiness data is not automatically transferred to the target business partner.
Customer Change
Use
You use the customer change function to transfer the utilities contracts for a contract account, including any resulting
receivables, between business partners.
This can for example be necessary when merging business partners.
The following functions are possible:
Create customer change
Process customer change subsequently
Reverse customer change
Transfer post open items due to customer change
Integration
You can use the function SAP Utilities Customer Service Process Execution Move-In/Out and then the menu option
Other Create / Cancel Customer Change
Use the methods for the BOR object MOVEINOUT to integrate the customer change in the Customer Interaction Center (CIC)
or the front office. Transfer the parameter OK code with the value ".
Prerequisites
Before you can a execute customer change, the contracts to be transferred must have been invoiced at least once.
If you also want to transfer budget billing plans, the budget billing plan items must all be open. If necessary, you must reset all
clearings and set the accrued receivables to payments on account. Therefore, we recommend that you execute the customer
change as close as possible to the last bill in order to avoid this preparatory work.
Customizing
You de ne customer change reasons in Customizing for SAP Utilities under Customer Service Process Execution Move-
In/Out De ne Reasons for Customer Change .
You can also choose whether or not the following objects are also transferred during the customer change:
Security deposits
Open items
Dunning information
Note
4/11/2019
See also the Customizing documentation for the individual components and the F1 eld help.
Features
When a customer change is created, the system terminates the transfer contract using a move-out, and creates a new contract
using a move-in. The move-out date is set as the end of the billing period of the most recently invoiced billing document
belonging to the transfer contract
You can also append an actual move-out date to the move-out, and an actual move-in date to the move-in. This enables you to
document when the move-out customer actually vacated the apartment, and when the move-in customer occupied it. If this
data becomes valid at a future date, the changes to the business partner and contract account data of the move-out customer
are stored as scheduled changes, with the actual move-out date as the validity date. The changes to the business partner and
contract account data are stored as scheduled changes for the move-in customer with the actual move-out date as the validity
date.
When you create a move-out, an adjustment reversal of the most recent billing document takes place for the transfer contract
and a new billing document is created with the value 08 (Customer Change). This billing document contains the billing amount
"0. The most recent billed meter readings are also copied when the move-in is created. Note that constellations in the rate
structure (such as period-end billing for monthly customers, basic monthly price and so on) can result in the billing documents
from the adjustment reversal not having the amount "0.
Depending on the Customizing settings, no new meter reading results are entered. Instead, the last billed meter readings are
copied when the move-in is created (see SAP Note 503243).
When you save the move-in document, the open items in the transfer contract can be posted to the target contract created as
a result of the move-in (this depends on the Customizing settings described above). This is only possible within the same
company code. Items that have already been paid are not reposted. You use the Transfer Items transaction (FP40) to do this.
Depending on the Customizing setting you made previously, security deposits and dunning information can be transferred.
Interest history and supplements are not copied during transfer of the open costs.
Budget billing plans are treated as follows: They are deactivated by the move-out, once you have set the payment on account.
Depending on the Customizing settings, a new budget billing plan is created from the deactivated budget billing plan when you
save the move-in document. You then allocate the credit payments using the account maintenance.
The customer change assigns a posting block to the transfer contracts. You can display this block in the move-out document.
You can change the block using methods ReleaseFicaLock and SetFicaLock of BOR object MOVEOUTDOC.
Constraints
Open items that have been sent to a collection agency cannot be transferred.
The returns history is not transferred to the new target business partner.
The interest history and supplements are not copied when you transfer the open items.
The business partners credit rating data is not transferred.
Alternatives if customer change is not possible
If a contract has not yet been invoiced, proceed as follows:
Reverse the move-in document: Execute move-in with the correct business partner. You can use the move-in document
as a template.
4/11/2019
Create an intermediate bill.
Wait for the next bill and then execute the customer change.

De nition
If you integrate SAP Utilities with SAP CRM, you can use the data cleansing tool in SAP CRM to manage the business partner
merging cases and, in part, process them in SAP CRM.
Use
When objects are replicated between SAP CRM and SAP Utilities, any changes to the target business partner are made in SAP
CRM. The exception to this is the contract in SAP CRM. In this case, the target business partner is changed in SAP Utilities by
the customer change .
For further information about transfer functions for other objects in SAP Utilities, go to Objects and Enhancements in SAP
Utilities for Business Partner Merging .
Business Partner Agreement in SAP CRM
The business partner agreement in SAP CRM (corresponds to the contract account in SAP ERP) is integrated in data cleansing
as of SAP CRM Release 4.0.

Use
You can use BAPIs or BOR methods to automate individual steps of business partner merging. For further information on this,
see the SAP note 624341 (Merging Business Partners).
Features
You can use the following BAPIs for automatic business partner merging:
BAPI Description
BAPI_ISUACCOUNT_GETDETAIL Display contract account
BAPI_ISUACCOUNT_CHANGE Change contract account
BAPI_ISUPARTNER_GETDETAIL Display contract account
BAPI_ISUPARTNER_CHANGE Change contract account
BAPI_ISUPROP_GETDETAIL Detailed information on owner allocation
BAPI_ISUPROP_CREATEFROMDATA Create owner allocation
BAPI_ISUPROP_CHANGE Change owner allocation
BAPI_CTRACDOCUMENT_TRANSFER Transfer open FI-CA items
4/11/2019
BAPI Description
BAPI_CTRACCONTRACTACCOUNT_GD1 Read detailed FI-CA contract account data
BAPI_CTRACCONTRACTACCOUNT_CH1 Change FI-CA contract account
Note
Use mostly IS-U BAPIs to change master data in SAP utilities since these function modules contain additional elds for
interfaces.
Caution
SAP does not recommend that you use the batch input procedure to automate steps. For further information on this, see
the SAP note 432178 (IS-U Transactions and Batch Input).
Requirements for automating the business partner merging have been included. If you require any support, contact SAP.
Contract Accounts
Purpose
This component enables you to create and manage contract account master data. In Contract Accounts Receivable and
Payable , each business partner posting is assigned to one business partner and to one contract account. In the contract
account master record, you can de ne, for each business partner, the procedures that apply when posting and processing the
line items of a given contract account. These include, for example, payment and dunning.
Integration
Master data can be changed automatically by certain business transactions. In this way, for example, a return can result in a
processing lock being set.
Features
You can assign more than one contract account to a given business partner. Similarly, a single contract account can be assigned
to more than one business partner. Note however, that in the industry components listed below, different rules apply. You can
transfer data manually or automatically. Contract accounts tend to be managed on an open item basis. See Open Item
Management . The system logs changes to master data. See Logging Changes .
Telecommunications(IS-T) component
In this component, a contract account can be assigned to one business partner only.
Utilities Industry (IS-U)Component
In Utilities ,one contract account contains all those contracts belonging to one business partner for which the same payment
and dunning terms apply. You assign your business partner contracts to the contract accounts. Although one contract account
can contain more than one contract, each individual contract is assigned to one contract account only. This does not apply to
one-time accounts.
For more information on contracts, see the Utility/Disposal Contracts section in the Utilities Industry component.
4/11/2019
Insurance(FS-CD) Industry Component
You assign contracts to the contract accounts for which there is a business partner. Each contract is only assigned to one
contract account, however one contract account may have several contracts assigned to it.
Contract account master data is usually created and changed from the operational system using an interface.
Industry ComponentPublic Sector Contract Accounts Receivable and Payable(PSCD)
You set up the contract accounts of a business partner for the relevant taxes (property tax, income tax, and so on). You assign
contract objects to a contract account for which relevant taxes are levied. If different taxes are levied for a contract object, you
can make assignments to several contract accounts.
For more information about the contract objects, see the documentation for the industry-speci c component Public Sector
Contract Accounts Receivable and Payable under Contract Object .
Contract Account Category

De nition
A contract account category de nes certain attributes for a contract account.
Use
You have to assign a contract account category to each contract account when you create it. The elds that appear when you
create a contract account are among the things controlled by the contract account category.
Structure
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 collective bill account (industry component Utilities )
Whether it is a one-time account
Whether it is a deposit account and the account contains deposit contracts (industry component Insurance )
The editing screens or data elds that you can use to edit the contract account
Contract Account
De nition
Structure used to bill the posting data for contracts or contract items for which the same collection/disbursement agreements
apply.
4/11/2019
Contract accounts are managed on an open item basis within Contract Accounts Receivable and Payable .
Note
In the industry component Insurance , you can decide whether accounting is to be managed on an account or open item
basis.
Use
Alternative correspondence recipient
You can de ne an alternative correspondence recipient in the contract account (see Recipient and Sender Determination ).
Planned changes to the contract account
You do not have to activate contract account changes to have immediate effect, but rather you can enter a date as from which
the changes should become effective. This data is not written to the database but recorded in change documents. The planned
changes function only applies to changes to the contract account. You cannot schedule the creation of a contract account.
To activate this data, you should run program BUSPCDACT on a daily basis. This writes the scheduling to the database. You can
use the application object FICA to activate planned changes to the contract account.
When you are in display mode for change documents, you can delete inconsistent data, for example, data that arises when
planned changes are cancelled.
Check digits in the contract account
When you create a contract account, you can add a check digit to the contract account number. The prerequisites are as follows:
You add the check digit procedure using event 1051. (Sample function module FKK_SAMPLE_1051_2_CHECKDIGITS for
two check digits is supplied by SAP)
The contract account is created with internal number assignment.
Only procedures with one or two check digits are supported. The number range is con gured such that it begins with a
leading zero (check digit procedure with one check digit) or with two leading zeros (procedure with two check digits).
Contract account enhancements
You can make enhancements using the Business Data Toolset ( BDT) in the menu for transaction CAWM.
Structure
Every contract account master record consists of general data that is the same for all business partners assigned to the
contract account and business partner-speci c data that can be set differently for each business partner in the contract
account.
Note
In the industry component Insurance , you can also de ne this data for the insurance relationship.
The master data is structured according to the processes that depend on the contract account data, such as incoming and
outgoing payments, correspondence, dunning.
4/11/2019
Integration
All transactions relating to contract accounts access data from the contract account master record (such as payments and
dunning). Several transactions change data in the contract account master record (such as payment locks for returns).
Controlling Speci cations in Contract

Accounts
Use
In Contract Accounts Receivable and Payable, you enter data and parameters that control processing processes. Examples of
this data include general data, data for payments and taxes, and data for dunning and correspondence.
Features
The control options available include those mentioned below.
Tab: Group Box You can specify:
General Data Cross-Partner Data The key under which the contract account is managed in the SAP
system and under which it may have been managed in a previous
system
General Data Account Management Data

Whether this business partner is an affiliated company, by
specifying the unique key for the trading partner
That the account is agged for deletion
If there is no dependent data, the account is deleted when

the archiving program is run.
What role a business partner has for the contract account

(account relationship), when multiple business partners are
assigned to the contract account
You can only assign one business partner as the owner of

the account.
Which authorization group that a contract account belongs

to, so that it can only be edited by people with the
corresponding authorization
That postings can no longer be made with reference to

business-partner-related data (posting lock at the level of
the contract account)
In this way, you can specify that no documents can be

entered, cleared, reversed, or reset. You can also choose
between a posting lock and a clearing lock. If you have set a
lock, the open items of a locked contract account are
designated with an icon and cannot be set to active.
That all items posted to the account receive a clearing

restriction
This has the effect that these items can only be cleared by
speci c business transactions (for example, year-end
settlement in a utilities company)
4/11/2019
The tolerance limits that apply to outstanding payments
The underlying clearing category for clearing postings
The planning group that the business partner belongs to

and how many additional days are taken into consideration
before an open item is paid (cash management)
That an interest key applies at contract account level
This is used in interest calculations to determine interest

frequency, amount limits and transfer and tolerance days
as long as no other interest key has been de ned at a more
speci c level.
General Data Invoice Creation

That invoices are sent to an alternative invoice recipient
Which collective invoice account is used by this contract

account together with other contract accounts
The tax jurisdiction valid for calculation of tax

(U.S./Canada)
That no invoice is created as a result of specifying a lock

reason for a master data record
General Data Contract Account: Remarks Remarks about the contract account in various languages
Payments/Taxes: Incoming Payments and Payments/Taxes:

That payments are processed using an alternative payer or
Outgoing Payments
alternative payee
The payment method that is to apply
Which bank details are used for incoming and outgoing

payments
Which card ID is valid for incoming and outgoing payments
Which mandate applies for incoming payments
The reason for locking the contract account for incoming or

outgoing payments
Several limited-time locks are possible.
Payments/Taxes: Taxes
That the withholding tax code is set for incoming and
outgoing payments in the relevant country
That several characteristics are de ned for each tax code,

such as the tax rate
The number and validity period of the certi cate issued for
exemption from withholding tax.
For which country a service was provided
You only have to change the default value here if it differs

from the country key of the business partner's standard
address.
The tax criteria for sorting companies
The regional code for automatic address preparation
4/11/2019
The county code for classifying different locations from a
tax point of view
Dunning/Correspondence: Dunning Control

That the dunning notices are sent to an alternative dunning
recipient but that the actual business partner can also
receive dunning notices
The grouping category to which the contract account's

overdue items are assigned when executing the dunning run
The dunning procedure with which the business partner is

dunned
The dunning lock reason for open items
Several limited-time locks are possible.
Convergent Invoicing: Basic Data

The invoicing category for ner control of billing and
invoicing processes
The selection characteristic in scheduling that is used for

contract-account-dependent derivation of rating, billing and
invoicing dates
That no invoice is created or processing is blocked as a

result of specifying a lock reason for a master data record
The target currency for posting of amounts in invoicing
That a key is entered for determining forms at the contract

account level
This key is used in determining an alternative application

form.
Convergent Invoicing: Periodic Bills When the system generates periodic bills
Convergent Invoicing: Individual Charges/Discounts The individual charges and discounts you calculate for the
business partner
In addition, industry-speci c elds are also available.
Link Between Contract Accounts and

Business Partners
Use
You must assign at least one business partner to each contract account. Depending on the industry, you may also be 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.
4/11/2019
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-speci c. You can set the
business partner-speci c data differently for different business partners.
Logging Changes
Use
The system logs changes to elds in the contract account. You can display the changes when you maintain the account online. In
addition, the system records who created a contract account and when, and who made the last change and when.
Features
Select (in the menu of the transaction): You see:
Extras Creation Data When a contract account was created or last changed and by
whom. There is a difference here between general and business-
partner-speci c data.
Extras Account Changes All the changes to an account. When you choose this function, the
system displays a selection list of all the elds in the account that
have previously been changed. In addition, the system displays
cross-business partner and business partner-speci c details
regarding the account’s creation data and any business partners
that have been created.
By selecting individual elds, you can choose the change data.

After con rming the entries, a list of all the changes appears,
specifying the person who made them and the date of the change.
Extras Field Changes Changes to the eld on which the cursor is positioned. After
choosing this function, a list with the changes made to this eld
appears, specifying the person who made them and the date of the
change.
The system does not create change documents for process locks. There is, however, a history function that you can call up from
the dialog box for locks.
Automatic Master Data Transfer

Use
You use this function to transfer the contract account master data from legacy or operational systems.
Features
Data is generally transferred in two steps:
1. The relevant data is read from the operational system and placed in a sequential le (operational system sender
structure) by the data selection program. This transaction takes place outside of the SAP system and is not supported
by SAP programs. Therefore the data selection program can make changes to data at this point.
4/11/2019
2. The SAP transfer program reads the data from the sender structure, changes the data, and places the data in the
receiver structure. Data can be changed or converted in this last step.
Activities
For more information, and the programs involved, see the Implementation Guide for Contract Accounts Receivable and Payable:
BasicFunctions ContractAccounts DataTransfer .
Creating, Changing, and Displaying Contract

Accounts
Use
You can create or change contract accounts both online and from the operational system (see Transferring Master Data
Automatically ).
Only one business partner’s data is ever displayed. For information on editing or displaying another business partner’s data see
Displaying or Editing Other Business Partners .
Features
If you want to change or display a contract account, you can enter the contract account number or the business partner.
The business partner is determined automatically if only one business partner has been assigned to the contract account.
If more than one business partner has been assigned to the contract account, then a dialog box in which you can choose a
partner to be edited appears.
If several contract accounts were assigned to a business partner, a dialog box appears showing all the contract accounts
assigned to that business partner. You can select a contract account from the dialog box and display it for processing.
Using authorization object F_KK_FCODE, you can issue authorizations for master data dialogs. You can determine, for example,
which user is no longer authorized to assign partners to a contract account. See the authorization documentation for further
information.
You can make changes to a contract account and have them take effect from a time in the future. The changes are not saved
directly to the database, they are entered in change documents. To activate the data, you have to run report BUSPCDACT for
the aplication object FICA(see SAP menu Master Data Contract Account ). For more information, see the report
documentation.
Creating Contract Accounts

Prerequisites
To create a contract account, you must have created a business partner to whom you assign this contract account. You can
assign additional business partners to the contract account depending on the industry and contract account category.
In addition, in the system, a contract account category must have been maintained that you assigned to the contract account
when you created it.
4/11/2019
Procedure
1. Select one of the following paths: Roles Edit contract account master data (SAP_FI_CA_CONTRACT_ACCOUNT)
Create contract account SAP Menu Master data Contract account Create
2. The initial screen appears.
3. Enter the following data:
A business partner who is assigned to the account. At least one partner must be assigned to each account.
A contract account category (see Contract Account Category ),
You can either assign a contract account number yourself or have the system assign the number.
1. Choose Continue .
2. The rst data entry screen appears.
3. Enter the required data. Using the navigation buttons, you can navigate between the various data screens.
4. Save the contract account.
Result
You have created the contract account and made all business partner assignments.
Assigning Additional Business Partners

Prerequisites
The contract account category allows more than one business partner to be assigned to a contract account. You have already
assigned a business partner to the contract account.
Procedure
Change contract account SAP Menu Master data Contract account Change
Enter the required contract account.
2. The rst data entry screen appears.
3. If you choose Goto New partner , a dialog box appears in which you can assign an additional business partner to the
account.
After carrying out the function, all elds that contain business partner-speci c data appear with their default values and the
general data remains unchanged.
Displaying or Editing Other Business

Partners
Prerequisites
4/11/2019
One or more business partners must be assigned to the contract account.
Procedure
Using the Other partner function, you can switch between the data for individual partners for the contract account.
Display contract account SAP Menu Master data Contract account Display
Enter the required contract account.
2. In the menu choose Goto Other partner
3. A dialog box with the business partners who have already been assigned to the contract account appears.
4. Choose a business partner.
The data for this business partner is displayed and can be edited.
Selecting Addresses for Business Partners

Prerequisites
You have maintained several addresses for a business partner and want to use each of these addresses for a speci c purpose
(for example, for dunning notices).
Procedure
1. In the transactions Create Contract Account/Change Contract Account , call up the input help for the eld Name of
Address on the tab pages General Data, Payments/Taxes , or Dunning/Correspondence .
A dialog box appears with the addresses maintained in the master record of the business partner.
2. Select the required address by double-clicking on it.
Result
The selected address is copied into the eld. In the contract account master record, the indicator Fixed next to the address eld
is now selected. It indicates that a speci c address has been selected which is not the business partner's standard address.
Note
You can use this function for each business partner for the contract account, regardless of whether this is the owner of the
contract account to be created/changed or an alternative business partner (for example, dunning recipient).
If you do not select an address, the system automatically uses the standard address of the contract account owner for all
business transactions.
Creating, Changing and Displaying Locks

In the contract account master record, there is one process lock eld for dunning, posting, invoicing, correspondence dunning,
interest calculation, incoming payments, and outgoing payments respectively. You enter a lock reason in this eld if you want to
4/11/2019
lock an account. You can set the lock for a limited period or set multiple locks for each business transaction.
Prerequisites
You have maintained the lock reasons for dunning and payment in Customizing for Contract Accounts Receivable and Payable.
Procedure
1. Call up the contract account you want to change or display.
2. Enter a lock reason in the Lock On eld on the Change Contract Account: Dunning/Correspondence Data screen for
dunning control, incoming or outgoing payments.
3. If you want to set a lock for a limited period or if you want to set or display multiple locks, press the arrow key next to the
Lock eld.
A dialog box appears where you can display or enter the lock interval or the lock itself. You can also display the lock history from
this dialog box. Changes related to the locks are written in the lock history and are not logged with change documents.
You can change and delete locks in this dialog box.
Note the following:
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 appears.
If you have set multiple or limited-time locks, the Lock eld contains a ~ . In this case, choose the arrow key to display the
locks.
Result
The contract account is locked for the business transaction selected either for a limited or unlimited amount of time, depending
on the lock reason.
Correspondence for Master Data Changes

Use
Using correspondence type 0030 (master data change), you can follow immediate and planned changes to the master data of
your business partners (business partner, contract account, contract reference).
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and Payable , under Basic Functions Correspondence De ne
Fields for Creating Master Data Changes , you have entered the tables to be considered for the correspondence (for example,
BUT000 – general business partner data). You can only de ne tables that contain object classes de ned by SAP, since the key
for selecting the change documents is different for each object class and is created in module FKK_SAMPLE_1915. If you want
other tables and therefore object classes to be considered, a program enhancement is necessary. The object classes de ned by
SAP are delivered in system table TFK070QC, which contains the following entries: ADRESSE, ADRESSE2, BUPA_BUP,
FMCA_PSOB, FMCA_PSOBVKK, MKK_VKONT. When you enter a table in Customizing, the system automatically checks whether
4/11/2019
your entry is valid. Use the input help to display the valid entries. Once you have entered the tables, in a second step, you de ne
the elds to be monitored for each table (for example, STREET in table ADRC). If the system writes a change document for a
eld that you have de ned here in Customizing, this eld is displayed in the correspondence. To determine which tables and
elds you have to enter in Customizing, proceed as follows:
In the menu, choose Display Business Partner or Change Business Partner .
Enter a business partner, specify the screen selection, and choose Continue .
In the menu on the detail screen, choose Extras → Partner Changes and select the required elds in the selection dialog box. If
you choose Technical Field Names On/Off , the system displays the table and eld names.
Choose Continue . A list of the change documents previously created appears.
The same procedure applies for the transactions Display Contract Account and Change Contract Account. In the menu of the
detail screen, choose Extras → Account Changes
Features
You have to trigger the creation of the correspondence manually. The program selects all change documents created for the
business partner on the same day and then creates an individual correspondence. Only the change documents for the elds
de ned in Customizing are considered in the correspondence. This means that the user can decide which master data changes
he wants to follow and inform the customer about. Only actual changes to existing data and changes made on the current date
are considered. This means that new master data, such as business partners and addresses, are not taken into account in the
correspondence. You cannot list or individually select the selected changes for the correspondence before the correspondence
is created. For correspondence type 0030 you can use events 1914 (print event) and 1915 (creation event). Read the
documentation for function modules FKK_SAMPLE_1914 and FKK_SAMPLE_1915. You can determine industry-speci c additional
data for the contract reference with a module for event 1916 (FKK_SAMPLE_1916). The module FMCA_SAMPLE_1916 is de ned
for determining data for the contract object for the industry solution Contract Accounts Receivable and Payable for Public
Sector . FI_CA_MASTERDATA is de ned as the standard form class in Customizing. At the top level (document level), the form
class contains a 1:1 level to the business partner. The hierarchy below contains the level for the change documents, whereby the
process logic determines that rst the change documents and then the planned change documents are listed (see application
form example FI_CA_MASTERDATA_SAMPLE). In the application form, you can display the old and the new value for a changed
eld. Note that certain elds only contain IDs (table keys), that is, links to the actual data (for example, bank details ID for
incoming payments). The determination of details for these IDs and other ID elds is not supported in the standard. However,
you can implement this in the customer-speci c application form.
Activities
In the menu of the transactions Change Business Partner, Display Business Partner, Change Contract Account , and Display
Contract Account , choose Extras Additional Extras Correspondence
On the processing screen that appears, make selections for the business partner, contract account, and contract reference and
make speci cations for printing. You must specify a business partner. If you do not make any restrictions for the contract
account and/or contract reference, changes to all contract accounts and contracts (contract references) of this business
partner are considered, instead of only changes to the selected objects.
Con rm your entries.
The correspondence is created.
Example
Example 1
4/11/2019
A customer informs you that she has recently married and informs you of her new last name. She requests written con rmation
that her data has been changed. Once the clerk has entered the new name in the eld Last Name (BUT000-NAME_LAST) in the
transaction Change Business Partner , he creates a correspondence that documents the change made and sends it to the
customer.
Example 2
A tenant informs you that the bank details for the collection authorization that you have will change in two months. The clerk
enters the new bank details in the eld Bank Details ID for incoming payments ( eld FKKVKP-EBVTY) in the transaction
Contract Account and schedules the change for the date speci ed. Using the correspondence for master data changes he
informs the tenant about the change planned in the system.
Contract Account and Contract Special

Features for IS-U
This documentation section contains information about enhancements and variations from the FI-CA contract account and
contract, which apply speci cally to SAP Utilities (IS-U).
Contracts (IS-U)
De nition
Contracts in IS-U.
Use
Contracts represent the entities that are billed. You can bill one or more contracts together using a contract account.
Structure
You can divide the data from contracts into three categories:
General data
Data relevant to billing (business)
Data regarding move-in and move-out.
Integration
Contracts are linked to installations in IS-U; these installations contain technical data with regard to billing. In the case of a
move-out, the installation remains and the contract is ended. In the case of the next move-in, a new contract is created and
linked to the installation. Only one contract can ever be assigned to an installation at any one time.
Controlling Speci cations in Contract

Accounts (IS-U)
Use
There are a number of attributes in the contract account that are speci c to IS-U. These can be divided into various areas:
4/11/2019
General data, such as:
Indicator for additional bill
Transaction currency
Terms of payment
Account class
Settlement category
Account determination ID
Application form
Language
Dunning control:
Indicator for additional dunning notice
Payment control, such as:
Automatic debit procedure
Number of automatic debits performed
Number of returned automatic debits
Indicator for recurring entry request
No payment form indicator
Features
Several business partners can be assigned to the contract account. There is always just one account holder. You cannot post to
the other business partners.
The Business Object Repository (BOR) contains the following Business Application Programming Interface (BAPIs) for contract
accounts:
BAPI_ISUACCOUNT_CREATERFROMDATA (creating a contract account)
BAPI_ISUACCOUNT_GETDETAIL (displaying a contract account)
BAPI_ISUACCOUNT_GETLIST (displaying a list of contract accounts)
For more information about BAPIs, see the following:
BAPIs in general: BAPI user guide and programming guidelines.
BAPIs in detail: Associated documentation in the BOR
Link Between Contract Accounts and

Contracts (IS-U)
4/11/2019
Use
Several contracts are grouped together in a contract account. A selection of these contracts can be invoiced together. You can
make sure that several of them are invoiced together using indicators in the contracts. Otherwise this remains optional, that is,
contracts are only invoiced together if invoicing happens to take place at the same time.
Prerequisites
A contract must always be assigned to a contract account.
Transferring Master Data Automatically (IS-

U)
Use
You use this function to transfer contract account data from a legacy system to IS-U for the rst time. It is available within the
IS-U migration workbench.
Integration
You need the IS-U migration workbench to prepare and carry out the data transfer. To do this, go to the Customizing menu for
SAP Utilities and select Tools Migration Establish settings for IS-U migration .
Prerequisites
You must have transferred business partners in the IS-U migration workbench before transferring the contract accounts.
Migration Customizing for the contract accounts must have been maintained completely.
Features
You create the contract accounts from the legacy system’s data using direct input.
Assigning Contracts to Contract Accounts

(IS-U)
Procedure
Contracts are created in utilities when a move-in is entered (transaction EC50E). Contracts are automatically allocated to a
contract account. You can either select an existing contract account or create a new one.
You can nd more information in the section on move-in .
Result
Once you have saved the move-in, the number of the allocated contract account is stored in the contract.
4/11/2019
Loans (IS-U)
Use
Note that this function does not replace the standard loan management function in Treasury. This functions helps you manage
very simple loans, such as a loan given to a customer if an appliance (a heat pump, for example) has to be bought. It is not
possible to manage premiums or discount. The system only supports xed interest rates for the whole term.
Integration
Before you can use the loan function, the system has to be set up to manage installment plans. The individual interest
calculation function must be set up to enable you to calculate interest.
Features
You can manage both interest-free loans and loans with a xed interest rate. A repayment plan is created for repayment of a
loan. You can select the same due date lists as those for an installment plan. Each installment through to the last installment is
of the same amount. The installment includes an interest and repayment component. As with an annuity loan, interest is
calculated on the basis of the individual due dates of the installment. A small interest amount and a higher repayment amount
are payable at every due date. Note that once you have created the loan, you are no longer able to change either the amount or
the due date of the individual installments.
When you create a loan, you have to specify parameters required for creating an installment plan (such as due date lists) and
other data such as net loan proceeds, interest rate etc. When creating a loan, you have to post a document with the net loan
proceeds as well as a repayment plan for the loan. This document comprises two line items, one of which contains the net loan
proceeds and the other a receivable in the same amount. If you have created a loan with interest, an interest document is also
posted. Depending on the due date of the repayment plan, this interest document contains its own line item with the interest
amount for the due date.
You can group important control parameters as default values in a loan category. You can create several loan categories so that
you avoid having to manually enter xed parameters for the most common loans over and over again. The parameters
proposed by this loan category can be overwritten manually.
You can de ne an alternative recipient for the disbursement. You can also de ne an alternative contract account and if
necessary, an alternative business partner. This would make sense if the disbursement were not being made to the customer
who has been given the loan, but directly to the contract partner supplying the appliance or performing the service. The credit
can also contain an explicit alternative payment method enforcing direct disbursement of the amount.
After you have created and saved the loan, a letter can be sent to the customer. This letter is managed in the same form class
as an installment plan letter.
Settlement type 20D is used when distributing a payment between the source items in a loan plan (interest and repayment) in
settlement control.
Utility Contract
De nition
Utility contracts are utility service agreements between the utility company and its business partners. The following contract
categories exist:
4/11/2019
Delivery contracts, for example for residential contracts, nonresidential contracts, cable television, telecommunications
Purchase contracts for small power producers, solar installations and other forms of energy transmission
Plant consumption contracts for generation and distribution installations of the utility company
Company consumption contracts, for example for the electricity consumption of offices at the utility company
Waste disposal contracts for the waste disposal industry.
For more information, see Waste Disposal Contract in the Waste Disposal Industry (IS-U-WA) component.
Note
Service contracts (such as for maintenance and repair) are not managed in this component; the Customer Service
component (CS) is used instead. Service contracts are billed in the Sales and Distribution (SD) component.
Use
A contract is related to a division. It links one single contract account to one installation (see graphic for the master data (ISU-
BF) component). However, several contracts can be grouped together in one contract account.
A contract contains control data for contract billing and contract accounts receivable and payable. This data includes:
General data (for example, contract account)
Move-in and move-out data
Schedule data (for example, start date and cancellation date)
Data relevant to billing
Account assignment data (for example, account determination ID)
Sales and distribution data
Deregulation data (for example service providers)
Data relevant to budget billing
The Contract Model: What Data Comes From Where
4/11/2019
With the exception of move-in and move-out data, you can change, display and check all data of multiple contracts of a contract
account simultaneously, if none of these contracts have been terminated.
You can change the screen layout by con guring the tabstrips. For more information, see the move-in screen layout .
Relevant Fields in the Contract

Use
Service Provider
The service provider in the contract determines who is the owner of the contract or billable service. During move-in, the
technical master data (installation) is linked with the business master data (contract). The service type in the installation tells
the system that entries are also required for the deregulation elds in the contract. This means that the Service Provider eld
in the contract is a required eld during move-in if theService Type eld in the installation contains an entry.
Caution
It is not possible to change the service provider in the contract at a later stage. If you need to make this type of change, you
must cancel and repeat the move-in.
4/11/2019
Service Provider Invoicing

The service provider you enter here carries out invoicing for a settlement performed for this contract, and therefore acts as
invoicing party for the customer. The invoicing service provider is therefore also responsible for collection for these bills. The
eld is a required eld if the contract is allocated a service provider.
If you enter an invoicing service provider who is not marked as the service provider from your own system (that is to say, for
whom the eld Service provider managed in own system is not agged) in the menu for the Intercompany Data Exchange
under Service Provider, this service provider is usually a billing consolidator In this case, you expect the billing consolidator to
pay the invoiced amount.
Payment Class
The payment class is an important instrument for account-based processing in the deregulated market.
You must always specify a payment class in the contract if the service provider in the contract differs from the invoicing service
provider and the two are managed in different systems.
Note
If both service providers are marked as service providers managed in your own system in the menu for the Intercompany
Data Exchange under Service Provider, you do not need to enter a payment class, since in this case account-based
processing does not take place.
The system determines the payment process and the payment frequency from the combination of payment class and service
provider.
This data maps contractual agreements with another service provider who is not managed in your own system. You can use the
payment class to distinguish between these agreements for each service provider according to criteria of your choice (for
example, to de ne different payment processes and frequencies for different customer groups). The system provides checks
that ensure that the payment class (and therefore the payment process) is used plausibly.
The following payment processes are provided by SAP:
Sole provider
Customer payment
Procedure whereby the billing agent only pays outstanding receivables to the service provider once the customer has paid the
billing agent.
Advance payment
4/11/2019
Procedure whereby the billing agent pays the service provider for the outstanding receivables, even if the customer has not yet
paid the billing agent. The billing agent owns the receivables from the customer once they have been invoiced in IS-U.
Customer payment and advance payment refer to a billing agent scenario.
The payment process has the following functions:
Determines the correct procedure in the supplier's system for inbound bills from the distributor
Indicates whether the supplier is acting as sole provider or billing agent, so that the bill is processed correctly
Differentiates between the customer payment and the advance payment process for the billing agent scenario
Consequently, the payment process provides information about the current scenario.
You allocate the payment process and frequency in the Service Provider transaction, which you can nd in the menu for the
Utilities Industry under Intercompany Data Exchange Service Provider .
The following case scenarios illustrate what information the payment process provides:
1. Invoicing for a different service provider (supplier's perspective)
2.  Example
The supplier receives the bill from the distributor and invoices the bill as billing agent.
The supplier has created a grid usage contract in which distributor DIST01 is entered as the service provider and
supplier SUPP as the invoicing service provider.
4/11/2019
The payment process is determined from the combination of the payment class and service provider DIST01. Subsequent
processing of the incoming bill (when and how payment is made) is determined from the payment process.
3. Invoicing by another service provider (distributor's perspective)
 Example
The distributor sends the bill to the supplier. The supplier invoices the bill as billing agent.
The distributor has created a grid usage contract in which they are entered as the service provider, and the supplier SUPP is
entered as the invoicing service provider.
4/11/2019
The payment process is determined from the combination of the payment class and the invoicing service provider (SUPP).
Note
Unlike in the rst example, the invoicing service provider is relevant in determining the payment process.
In this case, the payment process is used simply to provide the distributor with information about the due date of the bill and on
whether or not it is possible to monitor payments.
Multiple Contract Change

Use
4/11/2019
You use this function to display or process multiple contracts of a contract account at once.
The function is useful because it enables lets you cross-check all of the required contracts of a contract account, so you can
easily enter and change the data that is the same in one step.
Prerequisites
For the contract, you need
A contract account that exists
That a move-in has been completed
Note
You can nd the move-in under Utilities Industry Customer Service Process Execution Move-In .
Features
To access multiple-contract maintenance, enter the contract account. You can determine the contract account key by using the
data nder (Environment Find Conract Account ) or with the F4 search help.
On the detail screen, by positioning the cursor on a speci c contract, you can branch to the full screen of that contract.
In addition to the standard functions, you have the option of switching from the detail screen to display mode or to change
mode, requesting another contract account for processing, or executing the overall check.
You can branch to other IS-U objects (such as the installation or the contract account) by double-clicking the relevant eld.
You can only change entries that can also be changed in the normal contract maintenance screen (Utilities Industry Master
Data Business Contract Change ). You ca change the remaining contract elds using the functions Move-In, Move-Out, and
Move-In/Out (Utilities Industry Customer Service Process Execution ).
Connection Object
De nition
A connection object is usually a building but can also be a piece of property or a facility, such as a fountain or construction site.
Since an address is allocated to a connection object, the connection object links premises, device locations and connections to
the postal regional structure.
Integration
The connection object is a functional location from the Plant Maintenance (PM) application component. Therefore,
maintenance is managed using the functions of the Service Management (PM-SMA) component, for example, if you wish to
organize the repair and maintenance of devices at the connection object level. Maintenance and repairs are billed using the
Sales and Distribution (SD) application component.
Other Information
4/11/2019
For each connection object you can de ne any number of static notes. These can be printed on meter reading orders, for
example, to give eld service employees extra information. Example include "Ring Mr Y’s doorbell," "Beware of the dog," and so
on. You can also sue the dynamic notes prede ned in the system (for example "Installation blocked for meter reading," "Meter
reading already entered.")
Connection
De nition
The connection provides the technical link between the utility grid and the installations.
The connection processing function is optional. You will require it if you wish to manage the technical data for the connections
(for example, length of the line).
Use
The connection is modeled as a piece of equipment with the equipment category A: Connection from the Plant Maintenance
(PM) application component.
Caution
You can change the equipment category A in Customizing for Plant Maintenance and Service Management by choosing
Master Data in Plant Maintenance and Service Management Technical Objects Equipment .
Maintenance and service (such as initial creation of a connection, or malfunction repair) are managed using the functions of the
Customer Service (CS-SO) component. In the Sales and Distribution (SD) application component, quotations are created and
services are billed.
The connection is allocated to the connection object when the device is installed, or when the location of the equipment is
changed in the functional location.
For more information, see:
Plant Maintenance
Equipment
Service Connection (Work ow)
Service Connection with Customer Quotation (Work ow)
Service Connection Order Processing (Work ow)
Premise
De nition
The premise is an enclosed spatial unit that is supplied with energy, for example, an apartment or factory.
Use
4/11/2019
A premise can have several utility installations. Since the premise is division-independent, you can allocate electricity and water
installations to the same premise, for example.
The premise is allocated to a connection object and to the address of that connection object.
For each premise you can maintain the following elds:
Additional street data enables you to manage additional information on the street name of the connection object. You
can also store different street names.
Storage data helps eld service employees to quickly identify premises.
You can enter an owner for a premise. This owner must pay outstanding bills if the premise is empty (see also Owner Allocation
).
Change Connection Object in Premise

Use
Previously, it was not possible to change the connection object in the Change Premise transaction (ES61) once you had created
the premise successfully. This function supports the following business cases:
Case 1: Incorrect allocation of a customer and a device to a connection object within the initial data creation
You have allocated a customer and his/her premise to the wrong connection object (for example, in the initial data
creation). You only notice this error once the customer has already been billed.
There can be various reasons for the incorrect allocation:
The customer was speci ed incorrectly.
Street names and house numbers are only issued once the customer has been maintained.
The owner’s plan was incorrect.
The development plan has been changed.
Case 2: Division of connection object due to change to address
One connection object is divided into two.
For example, a second entrance is built for a building with one entrance, or a corner house has a second entrance from a
different street.
Premise Previous House Number Subsequent House Number
PR1 30 30
PR2 30 30
PR3 30 31
PR4 30 31
4/11/2019
The following functions are required:
Change Allocation of Premise to Connection Object
Change Allocation of Device Location to Connection Object
The Change Allocation of Connection Object to Premise/Device Location/Device function is only possible in the following
cases:
The result of checking the address of the connection objects involved against the regional structure is positive.
When changing the allocation you can only change the House Number, House Number Supplement , and Name elds in
the connection object. The Regional Structure Group, Political Regional Structure , and Maintenance Plant elds must
not be changed.
The regional structure data for the connection objects involved are identical (identical street or street section).
No technical installation is maintained for the premise.
No allocation exists to a device location remaining in the old connection object, and a premise that is reallocated, and
vice versa.
The address of the contract partner to which the address can be passed on during move-in, is not adjusted automatically. It
must be maintained manually later.
If the system automatically generates ship-to parties in SD, you must also adjust the addresses manually.
4/11/2019
In case 1 the device, whose location allocation is being changed, must comply with the following conditions:
It does not belong to a device group.
There are no register relationships to other devices.
It is not a controlling or controlled device.
It is the original device that was installed.
In case 2 the devices installed in the device installations, whose allocations to the higher-level connection object are to be
changed, must meet the following conditions:
There are no register relationships to devices from other device locations.
There is no allocation to a controlling or controlled device from another device location.
They are the original devices that were installed.
Features
Change the Allocation of Premise/Connection Object and Device/Device Location
An installation has been inadvertently installed in the wrong connection object. It is possible to correct this error without
canceling the entire operation, and must be executed again for the correct connection object.
This is made possible by using the Change Allocation of Premise/Connection Object and Device/Device Location transaction.
This allows you to assign authorization to speci c agents and process the operation in one step.
The elds that must be processed – Premise, Connection Object, Connection Object (New), Device Location (Old), Device
Location (New), and Device – are all found on one screen.
The input help for the respective change transactions are used for the premise, connection object, and device location. The
input help for the Device Replacement transaction is used for the device.
Choose the Reassign button to trigger the allocation changes.
If errors occur during the check, the corresponding messages are displayed in the status line.
Change the Allocation of Premise/Connection Object and Device Location/Connection Object
The connection object is divided into two connection objects. The premises and devices with the installed devices are to be
allocated to a new connection object. This is to be executed without it being necessary to cancel the installed devices, create
new premises/device locations, and reinstall the devices.
The elds that must be processed – Connection Object (Old), Connection Object (New), Premise, and Device Location – are all
found on one screen.
Reallocate Point of Delivery/Installation to

New Premise
Use
4/11/2019
You can use the transaction ES64 to reallocate a point of delivery or an installation to a different premise. This transaction
contains the new tab page Change Premise in Installation, which contains the following three elds:
Two elds that identify the installations or points of delivery to be reallocated.
A eld in which you specify the new premise.
Features
You can use the following examples to identify which installation and point of delivery are identi ed and which data is
reallocated.
 Example
You have two installations that are allocated to a premise. Both installations have the same point of delivery:
Reallocate Point of Delivery/Installation to New Premise - Example 1
Identi cation
If you specify installation A and a new premise V_NEU in transaction ES64, the system identi es installation A,
installation B and point of delivery ZP_XXX.
If you specify installation B and a new premise V_NEU in transaction ES64, the system also identi es installation A,
installation B and point of delivery ZP_XXX.
4/11/2019
If you specify point of delivery ZP_XXX and a new premise V_NEU in transaction ES64, the system also identi es
installation A, installation B and point of delivery ZP_XXX.
Reallocation
Following reallocation, the system replaces the premise V_ALT in installation A, installation B and the point of delivery
with the new premise V_NEU.
If move-in or move-out documents exist for the installations, the premise V_ALT is also replaced with the new premise
V_NEU in these documents.
You can change the business partner address using the Business Add-In (BAdI)
ISU_MOVEPODTOPREMISE_UP_BP_ADD in the default implementation.
Checks
The system checks whether a parked document exists for installation A or B as a default setting. If a parked
document exists whose status has not been set to Completed, the system terminates the reallocation.
Three additional checks are performed in the BAdI ISU_MOVEPODTOPREMISE_CHECK in the default implementation.
 Example
You have a point of delivery to which no installation is allocated.
Reallocate Point of Delivery/Installation to New Premise - Example 2
Identi cation
You can specify the point of delivery ZP_YYY and a new premise V_NEU in the transaction ES64.
Reallocation
Following reallocation, the system replaces the premise V_ALT in the point of delivery with the new premise V_NEU.
The following checks and BAdIs apply to the two examples above:
4/11/2019
BAdIs
Three BAdIs are available with the default implementations:
1. BAdI ISU_MOVEPODTOPREMISE_CHECK
You can use this BAdI to decide which checks are to be performed when a point of delivery or an installation is reallocated
to a different premise. The following checks are performed in the default implementation:
Check for Switch Documents
If at least one switch document with the status "Active" exists for the point of delivery or the installation to be
reallocated, the system displays an error message.
Check for Owner
If the owner of the premise for the point of delivery or installation to be reallocated is not the same as the owner
of the new premise, the system displays a selection dialog box on which you must decide if it is really necessary to
make the reallocation.
Check for Regional Structure
If the regional structure group or street or street section of the premise for the point of delivery or installation to
be reallocated is not the same as the location of the new premise, the system displays a selection dialog box on
which you must decide if it is really necessary to make the reallocation.
2. BAdI ISU_MOVEPODTOPREMISE_ADDRESS
You can use this BAdI to decide whether the addresses of the old and new premise are to be displayed on the dialog box.
In the default implementation, when the point of delivery or installation is reallocated to the new premise, the system
displays a dialog box with the addresses of the old and new premise.
3. BAdI ISU_MOVEPODTOPREMISE_UP_BP_ADD
If you use the transaction ES64 to allocate a different premise to a point of delivery or an installation, you can use this
BAdI to change the address for the business partner.
CRM Connection
All applications listed are replicated to CRM.
Technical Installation
De nition
Technical Installation
Use
You can allocate one technical installation to a premise for each division.
A piece of equipment that has already been created can also be allocated to the premise as a technical installation. However, to
do this make sure that the ISU eld (IS-U data) in the Equipment category has not been selected. You nd this eld in IS-U
Customizing under Device Management Technology Device De ne IS-U Equipment Categories.
4/11/2019
At present, you cannot change or delete a technical installation.
Integration
The technical installation is created as a piece of Equipment .
Creating a Technical Installation

Use
You can create a technical installation when you create a new premise or change an already existing premise.
Procedure
1. Choose Utilities industry Technical master data Premise Create or Change .
2. If you are in change mode, enter a premise.
3. Choose Premise Techn. inst. (technical installation ) Create .
4. Enter the division and, if necessary, a description.
5. A temporary equipment number is displayed in the Equipment eld.
6. Save the premise.
7. The technical installation is created in Plant Maintenance and Service Management (PM). as a piece of equipment with
its own number.
8. To maintain the technical installation as a piece of equipment, proceed as follows:
9.
a. Display the technical installation.
b. Double click the equipment to call it.
c. The Display Equipment: General Data screen appears.
d. Choose Equipment Create.
Result
You have created a technical installation and allocated it to a premise.
Utilities Installation
De nition
An installation groups together the devices, registers, and, if applicable, reference values that belong to the same division and
are allocated to the same premise, and that are therefore billed together, such as an on-peak and an off-peak rate meter.
An installation is allocated to one contract only. In exceptional cases (such as an installation under construction or an
installation without an owner) an installation is not allocated to a contract.
4/11/2019
Use
The billing-relevant installation data is managed historically . This enables you to change the rate category within a billing
period, for example, without any problems.
In addition to divisions such as electricity, gas and water, you can also allocate the waste management division to an installation.
For more information, see the Waste Management component.
To calculate charges that are not based on measurements, reference values are used. These charges are made for the
provision of energy or water. The following types of reference values exist:
General reference values (for example, location, value to be billed, indicator for billing relevancy)
Streetlights (for example, address, ownership status, operation modes)
The energy charge is calculated according to the burning hour calendar.
Heating installations (for example, description, charging control, special agreements)
Container
Integration
Integrated Components and Their Functions
To enable you to control meter reading and billing processes, the following components have been integrated:
Component Function
Regional structure (ISU-BFRS) You can store temperature areas and meter reading units for streets
and cities in the regional structure. These can then be copied to
installations.
Portioning and Scheduling (ISU-BFPS) In scheduling you de ne the meter reading dates. These dates are
dependent on the meter reading unit to which the installation is
allocated.
Rate Structure (ISU-BIBDRS) The rate, on which the billing of the installation is based, is
dependent on the general rate category to which the installation is
allocated. You can override the general rate category with the
individual rate category of the installation (if you have made
speci c arrangements with the customer, for example).
Installation Structure (ISU-DMDIIS) The registers and rate data of devices installed in the installation
are maintained in the installation structure.
Pro les
You can allocate a load pro le to an installation. The allocation is related to the identi cation of the corresponding load pro le.
Regional Structure Proposal
You can have the system propose the franchise contract from the regional structure proposals. To do this, select the time slice
you want to processes and choose Edit Regional proposals.
Deregulation Data
The entries you make in the of the installation affect how the deregulation scenario is determined.
4/11/2019
Others
You can change the Valid fr. (valid from) date or the premise of an installation as long as a contract has not yet been allocated
to that installation, and no devices have been installed.
Point of Delivery (PoD)

De nition
Point to which a utility service is supplied, or for which a utility service can be determined.
Use
A point of delivery can be identi ed by a unique key, called the point of delivery ID . This key is used for communication with
external systems. It ensures that, for example, misunderstandings and incorrect data allocations can be avoided, even if a
customer switches utility companies.
Structure
Communication Types
There are two communication types:
Communication in the deregulated energy market
This refers to communication between different utilities in a deregulated energy market. For example a distributor may
exchange consumption information with a supplier.
 Example
A distributor has measured the consumption of a point of delivery (customer’s consumption in a given installation)
and uses the point of delivery ID to send this information to the customer’s supplier. The supplier then bills the
customer based on the consumption data.
Technical Communication
Refers to communication with an automated meter reading system (AMR), for example. This type of communication is
used in the Energy Data Management component (IS-U-EDM) for importing pro le values.
 Example
An AMR sends information on the measured load shape using the point of delivery ID (and the register code of the
register) to IS-U-EDM.
Point of Delivery Roles
When you de ne a point of delivery, you can assign it one of the following roles:
Deregulation point of delivery
When you create an installation, the system automatically creates a deregulation point of delivery, to which you can
allocate a point of delivery ID.
4/11/2019
If you require a point of delivery for communication in a deregulated energy market then you must de ne it as a
deregulation PoD. You can allocate a deregulation point of delivery to one or two installations. If you allocate two
installations (dual contract model), ensure that the same devices (registers and so on) have been installed for billing
purposes in both installations. A deregulation point of delivery can be allocated to one installation only. However, several
technical points of delivery can be allocated to the same installation.
Technical point of delivery
You require a technical point of delivery in the following cases:
You require a point of delivery for technical communication with systems that do not use the point of delivery ID
common to the respective market.
You require a point of delivery for technical communication with systems whose measurement systems do not
conform to market requirements, such as a device that measure several points of delivery.
You can allocate logical registers or installations to a technical point of delivery. If you do this, the allocation
applies to all the registers contained in the installation.
A technical point of delivery distinguishes between the following point of delivery categories :
Normal point of delivery category
Virtual point of delivery category
A virtual point of delivery category is a summary of several normal point of delivery categories. For
example, the virtual point of delivery category can summarize the consumption of the normal point of
delivery categories.
In Customizing, you de ne point of delivery types and allocate these to the SAP prede ned point of
delivery categories.
Integration
The graphic below depicts the integration of the point of delivery in the IS-U data model.
4/11/2019
The data model for the point of delivery is integrated in the following tables:
4/11/2019
The individual tables have the following functions:
Table Function
EUIHEAD De nition of the point of delivery
EUITRANS Link between point of delivery and point of delivery ID
EUIGRID Link between point of delivery and grid
EEDMUISETTLUNIT Link between point of delivery and settlement unit
EUILZW Required for technical points of delivery
Link between point of delivery and register
EUIINSTLN Required for deregulation points of delivery
Link between point of delivery and installation
For more information on the role of the point of delivery in Intercompany Data Exchange (IDE), see point of delivery .
Application Examples
The following examples use selected processes to indicate when you must use a deregulation point of delivery and a technical
point of delivery .
Example 1: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption
4/11/2019
Example 2: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption, as well as Check
Reading for Watt-Hour Consumption
Point of Delivery Transaction
You nd the point of delivery transactions Create/Change/Display in the Easy Access Menu under Technical Master Data Point
of Delivery.
The following information describes the individual elds and tab strips.
Group Box for PoD Description
The individual elds have the following functions:
Field/Symbol Function
History Enables you to display different histories
Header data Enables you to return from times slice display to the normal view
New time slice You cannot enter data in the To eld. To restrict the validity of the
point of delivery ID, insert a new time slice. To do this, choose New
Time Slice . In the From Day eld, enter the date and time at which
you want the new time slice to become valid. The previous time
slice nishes on the start date of the new time slice.
Default value If you use the Metering Code structure category, you can generate
a consecutive number for the point of delivery ID. To do this, choose
the Default Value entry in the Consecutive Number eld.
Valid to Validity period for the PoD ID
Structure category The system automatically proposes the structure category de ned
in Customizing as the default value ( Master Data Point of
Delivery De ne Structure of Point of Delivery ID ).
Fields of the PoD ID Various elds are shown depending on the structure category you
selected
Header Tab Strip
Field Function
PoD Description Text that describes the point of delivery
Point of delivery type Enables you to select one of the point of delivery types de ned in
Customizing.You de ne point of delivery types in the IMG under
SAP Utilities Master Data Point of DeliveryDe ne Point of
Delivery Type.
PoD role See the Point of Delivery Roles unit
Technical PoD
Deregulation PoD
Grid tab strip
4/11/2019
Date From Period for which the grid is allocated to the point of delivery
Date To
Date You can restrict the period for which the grid is allocated to the
point of delivery
Grid Grid that you create beforehand in the Intercompany Data

Exchange menu
Distributor The system automatically displays the distributor allocated to the

grid, provided you have allocated a distributor in the Intercompany
Data Exchange menu under Grid.
Copy Choose Copy to copy your entries to the list
Origin tab strip
The Origin tabstrip is for information purposes only. The entries you make here have no effect on the function.
You can de ne source systems and number ranges for sources systems in Customizing under Tools System Modi cations User-
De ned Functions for Energy Data Management Source Systems.
Allocationtab strip
Valid to Validity period for allocation
Date You can restrict the validity period for the allocation.
Register and Installation tabstrips
To allocate the point delivery to a register, choose Register and enter a device, material, register, or piece of equipment.
You can also allocate the point of delivery to an installation. This allocation applies to all the registers allocated to the
installation. To do this, choose the Installation tabstrip and enter the installation to which you want to allocate the point of
delivery.
Settlementtab strip
On this tab strip, the settlement units are displayed. These automatically originate from the combination of services for the
point of delivery.
However, you can also manually allocate the point of delivery to a settlement unit. To do this, choose Allocate Sett. Unit
Manually. A dialog box appears in which you can use the F4 help to enter the required settlement unit in the Settlement Unit
eld.
In the list on the tab strip you can recognize the settlement units to which the point of delivery was manually allocated by the
Manual eld.
To delete a manual allocation, choose Delete Sett. Unit Manually. .
To change the settlement relevance, choose Sie Change Settlement Relevance. A dialog box appears in which you can
change the date and select or deselect the Settle eld. If the eld is selected, the consumption for the current point of delivery
is taken into account when the settlement unit is settlement for the given period.
4/11/2019
In the list on the tab strip, you can establish the settlement relevance of the point of delivery using the Settlement eld.
PoD Service tab strip
Once a move-in has taken place for the installation, to which this POD is allocated, all the services for this POD are displayed.
You must have de ned the default mechanisms in the IDE menu under Services.
Service on the Basis of the Operational Area or Services on the Basis of Service Provider Relationships.
You de ne the default mechanism to be used in Customizing under SAP Utilities Intercompany Data Exchange Basic
SettingsDe ne Control Parameters.
The service can have various statuses, which can be identi ed using the following icons:
Service exists or is created when you save
Optional service exits Is not created if you remove the data from
the Service provider eld and save
Optional service is proposed Is created if the Service Provider

eld contains an entry If the entry is remove from the eld, no
service is created
Service exists but con icts with the service proposed by the
system Service either no longer exists in Customizing or is not
proposed in the current circumstances because, for example a
contract (billable service) already exists for the same service type
Data Exchangetabstrip
Contains all the data exchange processesrelevant to the current point of delivery. The data exchange processes are only
created at service provider level. If you want to de ne a different due date control for individual points of delivery then you can
rede ne the current de nition for the given PoD.
If you click on a data exchange process the data exchange de nitionappears.
To rede ne a data exchange de nition at point of delivery level, choose Rede ne DATEX De nition . The de nition appears.
In the list on the tabstrip you can recognize the rede nition by the symbol in the Rede nition column. The symbol means
that the data exchange de nitionwas imparted to the point of delivery by the service provider.
To undo a rede nition, choose Undo Rede ne DATEX de nition.
If you do not want a data exchange process to be active for the current point of delivery then you must rst rede ne it. The
de nition appears. Select the Inactive eld and leave the dialog box.
In the list on the tab strip you can see whether a data exchange process is active by the Inactive eld.
To synchronize scheduled data exchange tasks, choose Synchronize . For more information on synchronization see
Synchronization of Scheduled Data Exchange Tasks .
The individual elds have the following functions:
Field Function Symbol
4/11/2019
Import/export Direction of DATEX process Export process
Import process
Data exchange process Data exchange process
Description of data exchange process
Sender/recipient Identi es sender and recipient in DATEX Recipient

process
Sender
Own service type In export processes, the service type

comes from the sender of the messages
In import processes, the service type

comes from the recipient of the messages
Own service provider Own service provider
Name of service provider
Sender/recipient Identi es sender and recipient in DATEX Recipient

process
Sender
External service type In export processes, the service type

comes from the recipient of the messages
In import processes, the service type

comes from the sender of the messages
Technical ServProv Service provider to which a service type Technical service provider
from the technical service category has
been allocated.
This service category described technical

systems, such as automated meter reading
systems.
External ServProv External service provider
Name of service provider
Rede nition Rede nition Rede nition
Impart by service provider
Inactive Data exchange process inactive for PoD
Point of delivery
Valid from Validity period for data exchange de nition
Valid to
No Due Date Control No due date control is allocated to the data

exchange process, meaning you cannot
actively schedule the process. The due date
of process execution cannot be maintained.
Only process execution data
communication are logged.
Text for Due Date Control
Data Exchange Format z.B. MSCONS
4/11/2019
Text for DATEX format Description of data exchange format
Migration of Points of Delivery
For more information, see Migration of points of delivery .
Example 1
Device 4711, containing the registers listed below, is allocated to installation 0815:
Device 4711 Register Code Interval Length
Reg 1 Watt-hour energy 15 mins
Reg 2 Reactive consumption 15 mins
When you created installation 0815, deregulation point of delivery POD 1 was created automatically. Allocate the point of
delivery a POD ID, so that you have the allocation shown below:
Point of Delivery Dereg POD Tech POD Installation Reg 1 Reg 2

(PoD)
POD 1 X X
You can now use the point of delivery ID of POD 1 and the corresponding register code to import the pro le values of the pro les
allocated to the registers.
You therefore do not have to use a technical point of delivery in order to import pro le values.
The Consumption role category is allocated as a default setting. If you do not specify a role category, as is the case in the
following graphic, the pro le values are imported for the pro le that is allocated to the register with the Watt-hours register
code and the Consumption role (colored light gray in the graphic).
4/11/2019
However, if you do want to import the pro le values of the pro le that is allocated to the register with the Watt-hours register
code and the Forecast role (schedule pro le colored light gray in the following graphic), you must specify the Forecast role
category.
4/11/2019
In order to use a deregulation point of delivery in a pro le value import, the system from which you import the data must work
with the same market-standard point of delivery ID as IS-U-EDM.
If this is not the case (if for example the automated meter reading system from which you import the values has its own
numbers), you must use a technical point of delivery for the import.
Point of Delivery Dereg POD Tech POD Installation Reg 1 Reg 2

(PoD)
POD 1 X X
POD 2 X X X
4/11/2019
You still require the deregulation point of delivery to export the data and send it to other market players.
4/11/2019
Communication in the deregulated energy market is still based on the deregulation point of delivery.
Example 2
Device 4712, containing the registers listed below, is allocated to installation 0816:
Device 4712 Register Code Interval Length
Reg 2 Reactive consumption 15 mins
In the installation, register Reg. 3 performs the same meter reading tasks as register Reg. 1. For this reason, the same register
code is used for identi cation purposes.
Registers allocated to a point of delivery must have a unique meter reading task as described by the register code. In the
following graphic, this allocation is not unique.
If you want to import pro le values of the pro le allocated to the register with the Watt-hours register code and the
Consumption role then 2 pro les are possible (colored light gray in the graphic).
4/11/2019
The load shapes for registers Reg.1 and Reg.3 cannot therefore be imported via the same point of delivery, necessitating the
use of technical points of delivery for the pro le import.
Point of Delivery Dereg POD Tech POD Installation Reg 1 Reg 2 Reg 3
(PoD)
POD 1 X X X X
POD 2 X X
4/11/2019
Point of delivery POD 1 us used to import load shapes for registers Reg. 1 and Reg. 2. Point of delivery POD 2 is used for register
Reg. 2.
Point of delivery POD 1 is still used for communication in the deregulated energy market. You must therefore de ne POD 1 as
both a technical and deregulation point of delivery.
The technical point of delivery role has a higher priority has a higher priority than the deregulation point of delivery role . As
soon a technical point of delivery is created, the system uses it for selection purposes.
Note
Note that in this case, you also must allocate data at register level for POD 1 (already allocated at installation level).
Alternatively, you can use technical points of delivery to model the complete pro le value import, as illustrated in example 1.
This would result in the following allocation:
Point of Delivery Dereg POD Tech POD Installation Reg 1 Reg 2 Reg 3
(PoD)
POD 1 X X
POD 2 X X
POD 3 X X X
4/11/2019
Create Deregulation Point of Delivery

Use
When you create an installation, the system automatically creates a deregulation point of delivery. Deregulation points of
delivery are required for communication in the deregulated energy market.
To allocate a point of delivery ID to a deregulation point of delivery, proceed as described below.
Procedure
1. From the SAP Easy Access menu, choose Technical Master Data Installation Create .
Make the entries required in order to create an installation.
2. The Point of Delivery group box is in the lower half of the screen is.
3. Make the entries required for the point of delivery ID and enter the ID of a grid in the Grid eld. Note that you must have
de ned the grids in the Intercompany Data Exchange menu.
4. When you make this entry, the system allocates a grid to the point delivery. The grid is used during the move-in to
determine the default values for service, for example.
Note
If you have not entered a point of delivery ID, you do not have to enter a grid in the installation. However, if you have
already entered a point of delivery ID then you must enter a grid. The grid is a new entity created to IS-U Release
4.63. This means that if you upgrade your system from IS-U 4.62, there are no grids allocated to the points of delivery.
If the system cannot nd a grid allocated to the point of delivery, the functions that require the grid (such as the
default de nition for services) automatically search for a grid in the regional structure. In Energy Data Management
the Settlement settings determine whether you have to specify a grid. If you have made these settings, you must
ensure that all the points of delivery are allocated to grids when you upgrade your system.
5. Save your entries.
Note
You can create an additional installation for the point of delivery by entering the same point of delivery ID in the second
installation. To do this, you must observe the following:
The installations must be allocated to the same premise
The installations must have different service categories
Create Technical Point of Delivery

Use
You create a technical point of delivery if:
You require a point of delivery for technical communication with systems that do not use the point of delivery ID common
to the respective market.
4/11/2019
You require a point of delivery for technical communication with systems whose measurement systems do not conform
to market requirements, such as a device that measure several points of delivery.
Procedure
1. From the SAP Easy Access menu, choose Technical Master Data Point of Delivery Create .
2. Choose one of the prede ned pro le structure categories in the Structure Category eld.
3. The system automatically proposes the structure category de ned in Customizing as the default value Master
Data Point of Delivery De ne Structure of Point of Delivery ID .
4. Enter the required data in the individual point of delivery ID elds.
5. If you use the Metering Code structure category, you can generate a consecutive numberfor the point of delivery ID. To
do this, choose the Default Value entry in the Consecutive Number eld.
If you have de ned default values in Customizing for the selected structure category Technical Master Data Point of
Delivery De ne Structure of Point of Delivery ID under Field Settings, these are displayed in the Point of Delivery ID
elds. Note that if you select the NI eld ( eld is not ready for input), you cannot change the default values. To change
the default values, you must reset the NI eld.
6. In the Valid eld, the current date is displayed as a default value, and the time 00:00:00.
7. To change the validity of the point of delivery ID, enter a different date and/or time in the Valid eld.
8. You cannot enter data in the To eld.
9. To restrict the validity of the point of delivery ID, insert a new time slice. To do this, choose New Time Slice. In the From
Day eld, enter the date and time at which you want the new time slice to become valid. The previous time slice nishes
on the start date of the new time slice.
10. On the tab page header in the PoD Description eld, enter a short text to describe the point of delivery.
11. Choose one of the prede ned options in the Point of Delivery eld.
Select the Technical PoD eld.
Choose Continue.
12. On the Grid tab page, you can allocate a grid to the point of delivery for a speci c period of time.
13. You can also use grids to recreate the distribution grid of a distributor in the system. By allocating a grid to the point of
delivery, you can calculate the results of settlement not only for each settlement unit, but also for each grid.
Enter the period for which you want to allocate the grid to the point of delivery.
The Fran Day eld contains the current date as a default value. However, you can change this date.
In the Grid eld, choose a grid that you have already created in the Intercompany Data Exchange menu.
The system automatically displays the distributor allocated to the grid, provided you have allocated a distributor in the
Intercompany Data Exchange menu under Grid.
Choose the Copy icon to copy the entries to the list.
14. The Origin tab page is for information purposes only. The entries you make here have no effect on the function.
15. You can de ne source systems and number ranges for sources systems in Customizing under Tools System
Modi cations User-De ned Functions for Energy Data Management Source Systems .
16. Choose the Allocationtab.
4/11/2019
17. To allocate the point delivery to a register, choose Register and enter a device, material, register, or piece of equipment.
18. You can also allocate the point of delivery to an installation. This allocation applies to all the registers allocated to the
installation. To do this, choose the Installation tab and enter the installation to which you want to allocate the point of
delivery.
To restrict the allocation data, choose Date.
In the Proration Day eld, enter a new from-date and choose Prorate.
The system inserts a new line with a new time slice.
Place the cursor on the line containing the required time slice and choose Select.
19. Choose the Point of Delivery Servicetab.
Once a move-in has taken place for the installation, to which this POD is allocated, all the services for this POD are
displayed.
You must have de ned the default mechanisms in the Intercompany Data Exchange menu under Services:
Services on the Basis of the Operational Area or Services on the Basis of Provider Relationships.
You de ne the default mechanism to be used in Customizing under Intercompany Data Exchange Basic Settings De ne
Control Parameters .
20. When you have made all the required entries, save the data.
Device location
De nition
These are locations within the connection objects where devices can be installed.
The devices can belong to different divisions.
The address of the connection object is allocated to the device location. In addition, a particular premise can also be allocated,
and a description of the device location can be entered. This means that the exact location of an installed device is determined
using the device location.
Use
The device location is a functional location from the Plant Maintenance (PM) application component. Therefore, maintenance is
managed using the functions of the Service Management (PM-SMA) component, for example, if you wish to organize the repair
and maintenance of devices at the device location level. Maintenance and repairs are then billed using the Sales and
Distribution (SD) application component.
Services
De nition
Used to describe a service supplied to a point of delivery .
Services can be billable or non-billable . All the own or external services that are billed and/or invoiced are modeled as contracts
in SAP IS-U. These contracts are also described as billable services. All other services are non-billable services .
4/11/2019
The most important attributes of services are as follows:
Service type to describe the type of service
Service types can be freely de ned. In Customizing you must allocate them to a prede ned SAP service category.
All the service types that do not correspond to one of the prede ned service categories can be allocated to the Other
service category. If you want to continue using a service type based on the Other service category internally, you must
modify the templates individually.
Service provider as a service agent
For more information on service providers, see service providers .
Validity period of service
In the case of a billable service (contract), the validity period is based on the move-in and move-out dates. The service
type is contained in the corresponding installation.
Integration
The non-billable are modeled as an own entity in the point of delivery. This is why they are referred to as point of delivery
services.

ISU Master Guide All PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ISU Master Guide All PDF

Hochgeladen von

Copyright:

Verfügbare Formate

4/11/2019

SAP ERP | 6.18.12

For more information, please visit the SAP Help Portal.

Master Data in IS-U

There are two diﬀerent types of master data:

Business master data and technical master data

Business master data includes:

Contract (billable service)

Technical master data includes:

SAP Business Partner

Business Partner Concept

BP Role Contract Partner

A company must have the following information on a contract partner:

Control/Payment Transactions: Bank details and general data (creditworthiness)

Relationships: Relationships to other business partners (see Relationship Categories)

Driving license number

Social insurance number (USA)

Employee classi cation

Account category (as default value for contract account)

Tax numbers for business partners

Checking dependencies of master data changes

Check digit for contract partners

The contract partner is created with internal number assignment.

Shadow table for business partners

See SAP Note 871094 .

Changes to Payment Data

Note for the industry component Insurance

Note for Public Sector Contract Accounting

The maintenance of customer contacts is not supported.

Create new bank details/payment cards

Change existing bank details/payment card data

Create customer contacts

Print con rmation letters

Deletion of locks from contract accounts, items, and industry objects

Reset returns activities

The processing takes place in three modes:

Mode Function Call Using Button

Mode Function Call Using Button

Create Create new bank details/payment card ( Create )

Change Change existing bank details/payment card ( Change )

Delete Delete existing bank details/payment card ( Delete )

Making System Settings

Creation of Con rmation

2. Create a copy of the standard form FI_CA_BANK_MAINTAIN_SAMPLE or FI_CA_CCARD_MAINTAIN_SAMPLE and adjust it

Read the documentation for the IMG activities.

Changing Payment Data

3. Con rm your entries.

4. Choose a change reason.

5. Make the desired changes and save your entries.

Area: Bank Details/Card Data

Area: Contract Accounts

The following contract accounts appear here:

The system automatically selects certain contract accounts in the list:

Mode Automatic Selection

Create If the business partner has no bank details/payment card, the

You can also select speci c contract accounts manually.

Note for the industry component Insurance

Note for Public Sector Contract Accounting

You can also enter further data for the contact.

Special Features of Changes with Eﬀect in

The object being processed (bank details or payment card)

The master data aﬀected (business partner or contract account)

Creation in the future