Contents
INS_FSCD_CI_4: Business Function SAP for Insurance Collections/Disbursements 4 ............................... 3
INS_FSCD_CI_4: Payment Plan: Externally Calculated Tax Data (New)..................................................... 5
INS_FSCD_CI_4: Coinsurance (Changed) ................................................................................................... 6
INS_FSCD_CI_4: Wrife-Offs (New) ............................................................................................................. 7
INS_FSCD_CI_4: Extended Withholding Tax Calculation (New) ................................................................ 8
INS_FSCD_CI_4: Tax Posting and Tax Reporting (New) ........................................................................... 10
INS_FSCD_CI_4: Generating BRFplus Functions for Events (New) .......................................................... 11
INS_FSCD_CI_4: Integration with SAP Dispute Management (New) ................................................... 12
INS_FSCD_CI_4: Deferred Revenues (New) ............................................................................................. 13
INS_FSCD_CI_4: Collections Management (New) ................................................................................... 14
INS_FSCD_CI_4: Posting Area Views (New) ............................................................................................. 15
INS_FSCD_CI_4: Archiving in Contract Accounts Receivable and Payable (New) ................................... 16
INS_FSCD_CI_4: Account Balance (New) ................................................................................................. 17
INS_FSCD_CI_4: Integration with SAP Credit Management (New) ......................................................... 18
INS_FSCD_CI_4: Brazil: Boleto (New) ...................................................................................................... 19
INS_FSCD_CI_4: New Events (New) ......................................................................................................... 20
Release Notes as of SAP enhancement package 6 for SAP ERP 6.0, Support Package 3.................... 22
INS_FSCD_CI_4B: Business Function SAP for Insurance: Inkasso/Exkasso 4B ........................................ 22
INS_FSCD_CI_4: Business Function SAP for Insurance Collections/Disbursements
4
Use
As of SAP ECC 6.0, Industry Extension Insurance, Enhancement Package 6 (INSURANCE 606) the
Business Function SAP for Insurance: Collections/Disbursements 4 (INS_FSCD_CI_4) is available.
You can use this business function to:
o Include externally calculated tax data in the payment plan.
o Include the company code from the relevant underlying documents when posting the
coinsurance shares.
o Pass on the general ledger account assignment feature Number for Profitability Segments
(CO-PA) (PAOBJNR) when you are writing off documents
o Make extended withholding tax calculations in the following processes:
- Payment runs
- Manual Postings
- Automatic Clearing
- Manual Clearing
- Posting via Interface
o Fill the tax reporting date (VATDATE) field in the document header of accounting documents
that you create when transferring totals records from the contract accounts receivable and
payable in general ledger accounting (FI-GL)
o Exchange the value-added tax indicator for general ledger items when posting documents in
evento 0067 according to customer-specific or country-specific logic
o Define events that SAP supports for this purpose as BRFplus functions
o Use SAP Dispute Management in Contract Accounts Payable and Receivable as part of
integration to:
- Navigate to a clarification case in the CRM system if the clarification case was created
from a CRM clarification case
- Navigate from to the list of clarification cases to documents, invoicing documents,
invoicing document items, and billable items
o Verify the sums posted in the general ledger due to transfer posting runs for deferred revenues
o Use predefined master data selection when updating collection strategies
o USE BRFplus for dunning by collection strategy
o Use posting area views
o Archive documents in parallel
o Display your own selection view in the account balance
o Use SAP Credit Managment as part of integration to:
- Transfer commitment for billable items and billed but not invoiced items from the
settlement in the contract accounts receivable and payable to SAP Credit Management
- Ensure that you include the commitment, which reports to an external settlement system
as well as to contract accounts receivable and payable, only once
o Enter, change, and display the bar codes of the boletos from your suppliers manually for the
relevant document items when posting payables in contract accounts receivables and payables
For more information, see the following release notes:
o Payment Plan
o Coinsurance
o Write-Offs
o Extended Withholding Tax Calculation
o Tax Posting and Tax Reporting
o Generating BRFplus Functions for Events
o Integration with SAP Dispute Management
o Deferred Revenues
o Collections Management
o Posting Area Views
o Archiving in Contract Accounts Receivable and Payable
o Account Balance
o Integration with SAP Credit Management
o Brazil: Boleto
o New Events
See also
SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp -> SAP ERP Central
Component -> SAP ERP Enhancement Packages -> <Enhancement Package> <Language >
SAP ERP Business Functions (SAP Enhancement Package 6 for SAP ERP 6.0) -> Industry
Business Function Sets -> SAP for Insurance -> Collections/Disbursements -> SAP for
Insurance: Collections/Disbursements 4.
INS_FSCD_CI_4: Payment Plan: Externally Calculated Tax Data (New)
Use
As of SAP ECC 6.0, Industry Extension Insurance, Enhancement Package 6 (INSURANCE 606) the
Business Function SAP for Insurance: Collections/Disbursements 4 (INS_FSCD_CI_4), externally
calculated tax data can be taken into account in the payment plan.
Creating Payment Plan Items
You can now use the payment plan interface to specify externally calculated tax data. This tax data
was already calculated in the feeder system, so no calculation of tax data takes place in FS-CD. You
can specify multiple tax data for each payment plan item.
Debit Position
The debit position takes the externally calculated tax data into account and creates a G/L account item
for each data set in the resulting document.
Correspondence
To publish the tax item in correspondence, the G/L account items are also available in
correspondence for invoices and payment plan posting.
Services
Services for the Insurance Collection Disbursement Request business object were adjusted to
additionally support externally calculated tax data. To do this, the following changed Enterprise SOA
entities, for example, Enterprise Services, are available:
InsuranceCollectionDisbursementRequestERPBulkCreateRequest_In
InsuranceCollectionDisbursementRequestERPByBaseBusinessTransactionDocumentReferenc
eQueryResponse_In
InsuranceCollectionDisbursementRequestERPByIDQueryResponse_In
InsuranceCollectionDisbursementRequestERPCreateCheckQueryResponse_In
INS_FSCD_CI_4: Coinsurance (Changed)
Use
As of SAP ECC 6.0, Industry Extension Insurance, Enhancement Package 6 (INSURANCE 606) the
Business Function SAP for Insurance: Collections/Disbursements 4 (INS_FSCD_CI_4), the following
change is available for coinsurance: To post coinsurance shares, the system takes the company code
from the underlying documents relevant to the coinsurance shares. The system no longer uses the
target company code saved in the coinsurance key. Nevertheless, you still need to maintain the target
company code for a coinsurance key.
Up to now, the system has posted the posted coinsurance shares to the coinsurance key defined in
the company code. From an accounting point of view, the company code needs to be inherited from
the coinsurance-relevant items. This is done so that the entire business process, from the debit entry
up to the transfer of the coinsurance shares, is posted to the same company code.
To do so, you first need to use your own coinsurance key for each company code. You can also do
this with event V110 and the customer include CI_COINS_COLLECT_TRANSFER. If you have used
broker report (Broker Transfers Coinsurance Shares) to post coinsurance shares, this inheritance
was not possible up to now.
Note:
If you do not want this system behavior as of Enhancement Package 6 SAP for Insurance:
Collections/Disbursements 4, you can use transaction VRCN to adjust the posted coinsurance with
event V110 as usual. If the business function is active, the system automatically fills event V110 with
the inherited company code in parameter IS_COLLECT-COMPCODE. If the business function is
inactive, the parameter remains blank.
Effects on Existing Data
The system also passes the company code on to the coinsurance shares to be posted in the case of
documents that were posted before the business function was activated. The BUKRS (company code)
field in the customer include CI_COINS_COLLECT_TRANSFER, as mentioned in SAP Note 1553413,
is no longer necessary. And you no longer need to define a function module for event V110 for the
exchange of company codes.
See also
If you do not activate the business function, see SAP Note 1553413.
INS_FSCD_CI_4: Wrife-Offs (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, you can, when writing off documents, inherit the
G/L account assignment characteristic PAOBJNR (profitability segment number (CO-PA)) from the
document to be written off.
Note
As of SAP enhancement package 2 for SAP ERP 6.0, you can inherit the G/L account assignment
characteristic PAOBJNR (profitability segment number (CO-PA)) using the installation-specific event
5030 (as a modification). This modification remains untouched by the upgrade to SAP enhancement
package 6 for SAP ERP 6.0. That means, that if you have implemented logic in the installation-specific
event 5030, this continues to be processed during write-off.
Effects on Customizing
The prerequisite for inheritance is that you entered the value 1 (Inherit item that is to be written off)
for the derivation of the CO account assignment. You make this entry in Customizing for Contract
Accounts Receivable and Payable under Business Transactions -> Write-Offs in the activities
Define Specifications and Default Values for Write-Off and Define Specs and Default Values for
Mass Write-Offs.
INS_FSCD_CI_4: Extended Withholding Tax Calculation (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, the options for calculating vendor withholding
tax were enhanced for the following processes:
o Payment run
o Manual postings
o Automatic clearing
o Manual clearing
o Posting using interfaces
You activate the extended withholding tax calculation for each company code. In company codes in
which the extended withholding tax calculation is active, the following two events are called in the
processes mentioned:
o 0176 (Adjust tax base amount for withholding tax)
In event 0176, you can adjust the base amount for withholding tax per item. In doing so, all
characteristics of the item are available to be used as a calculation base, so that you can also
calculate the withholding tax base amount independently of the amount of the item.
o 0177 (Add to and adjust withholding tax supplements)
In event 0177, you can add to and correct the determined withholding tax supplements. Here
also all characteristics of the item are available to be used as the calculation base. Changes are
made exclusively using the withholding tax supplements, for which you have already entered
with an appropriate percentage rate in Customizing. You cannot change the tax entered for the
withholding tax indicator itself.
If you enter a percentage rate for a withholding tax supplement in Customizing, this acts as a
default, from which the system departs only in special cases that you provide for in event 0177.
For your installation-specific or industry-specific special cases, you have to provide adjusted
records at event 0177 that contain the tax rate and tax amount valid for the special case. The
system then overwrites the records calculated on the basis of the system settings with the
adjusted records. The system writes the originally determined percentage rate and the tax
amount for documentation purposes in the two new fields PRLQS (provisional withholding tax)
and PRLPZ (provisional percentage rate) in table DFKKQSR. However, the system fills the
fields PRLQS and PRLPZ only if there is an adjustment, and not for new records.
If the extended withholding tax calculation is active, it is not only available in the standard processes
mentioned; you can also use it in your own programs. To do so, you have to include the function
module FKK_WITHH_CONTROL_EVENT_0177 in the given program. This additional step is
necessary, since the system often calls the modules for calculating withholding tax multiple times, for
instance during the selection of open items, then during the document check, and finally during
document posting. This can have undesired effects, for example, if you calculate the withholding tax
with dependence on other items of the same document.
Note
Note that the following restrictions exist for items with extended withholding tax calculation:
o Only complete clearing is allowed, no partial clearing.
o In the case of manual clearing, the group of items to be cleared is only allowed to contain one
item with extended withholding tax.
o In the payment run and in the automatic clearing run, you can only use the parallel processing
object GPART.
Effects on Customizing
To activate the extended withholding tax calculation, set the Extended Withholding Tax Active
indicator for the company codes you want in Customizing for Contract Accounts Receivable and
Payable under Organizational Units -> Set Up Company Codes for Contract Accounts
Receivable and Payable.
You make system settings for withholding tax supplements in Customizing for Contract Accounts
Receivable and Payable under Basic Functions -> Withholding Tax -> Define Withholding Tax
Supplement and Define Allowed Entries for Withholding Tax Supplements.
INS_FSCD_CI_4: Tax Posting and Tax Reporting (New)
Use
Tax Reporting Date in Accounting Document
As of SAP enhancement package 6 for SAP ERP 6.0, you can fill the Tax Reporting Date
(VATDATE) field in the document header of accounting documents that you generate during the
transfer of totals records from Contract Accounts Receivable and Payable (FI-CA) to General Ledger
Accounting (FI-GL). The documents of FI-CA do not themselves contain this field. However, you can
specify in Customizing for Contract Accounts Receivable and Payable that the system fills the field
either with the document date or posting date of the accounting document generated during the
transfer. This ensures that tax reporting also considers the accounting documents from the general
ledger transfer from Contract Accounts Receivable and Payable.
In the transaction for changing accounting documents, you can also change the date later.
Exchange of tax on sales/purchases code for credits
As of SAP enhancement package 6 for SAP ERP 6.0, during posting of documents, you can use event
0067 to replace the tax on sales/purchases code of G/L items according to your own logic or
country-specific logic. In this way, you can, for example, meet the legal requirements for handling tax
on sales/purchases for credits.
Event 0067 is executed when the document to be posted has the following properties:
o The document is not statistical and it is not a down payment.
o The tax on sales/purchases code is filled.
o The document is not cleared.
o The balance of credit memos and receivables is less than zero (credit memo).
The calculation basis of the newly determined tax on sales/purchases code is not allowed to differ
from the calculation basis of the original tax on sales/purchases code. That means that the percentage
rate must be the same.
Effects on Customizing
Tax Reporting Date in Accounting Document
In Customizing for Contract Accounts Receivable and Payable under Organizational Units -> Set Up
Company Codes for Contract Accounts Receivable and Payable in the field Tax Date, specify for
your company code the date that should be used for filling the tax reporting date during the transfer to
the general ledger.
If you make an entry here, you override any Customizing settings made in Customizing for Financial
Accounting (New) under Financial Accounting Global Settings (New) -> Tax on Sales/Purchases
-> Basic Settings -> Define and Check Tax Reporting Date. This means that you therefore have the
option of specifying a different rule for filling the tax reporting date for documents from Contract
Accounts Receivable and Payable.
INS_FSCD_CI_4: Generating BRFplus Functions for Events (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, you can define, in Customizing for management
of events, individual events specified for this by SAP as BRFplus functions. To do so, you select the
event and directly create the BRFplus function there with the appropriate context, along with an
installation-specific function module that calls the BRFplus function with the program context.
This function is released for the following events:
o 0040
o 0060
o 1140
For events 0060 and 1140, SAP provides example implementations.
Effects on Customizing
In order to create a BRFplus function and the related installation-specific function module, in
Customizing for Contract Accounts Receivable and Payable, choose Program Enhancements ->
Define Customer-Specific Function Modules. After you have selected an event by double-clicking
on it, define the necessary objects on the Generate BRFplus Function tab page.
For more information, see the Info (@0S@) button on the Create BRFplus Function tab page.
INS_FSCD_CI_4: Integration with SAP Dispute Management (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, you can use the following functions that
enhance the display of dispute cases:
o From the list of dispute cases, you can now navigate to the following objects in Billing and
Invoicing in Contract Accounts Receivable and Payable (as long as the object types are
contained in the dispute case):
- Documents
- Invoicing documents
- Invoicing document items
- Billable items
The dispute case displays the attributes of the objects. By double-clicking (forward navigation)
you go to the display of the object.
o If a dispute case in Contract Accounts Receivable and Payable was generated from a CRM
dispute case, by choosing the CRM Dispute Case pushbutton, you can navigate to the dispute
case in the CRM system and process the dispute case there.
You can display the internal or external case numbers, as well as the CRM dispute case number by
choosing Additional Data pushbutton in the toolbar.
In the SAP Easy Access menu under Account -> More Information -> Dispute Cases for Account
Balance, you can search for a dispute case using the CRM dispute case number.
INS_FSCD_CI_4: Deferred Revenues (New)
Use
The transfer posting run for time-based deferred revenues (on the SAP Easy Access screen under
Closing Preparation -> Receivable/ Revenue Adjustment -> Transfer Deferred Revenues) and
the transfer posting run for event-based deferred revenues (on the SAP Easy Access screen under
Closing Preparation -> Receivable/Revenue Adjustment -> Event-Based Deferred Revenues ->
Transfer Run) both post cumulated documents in the general ledger.
As of SAP enhancement package 6 for SAP ERP 6.0, you can use the report Display of Transferred
Deferred Revenues to display the data records posted in each of these transfer posting runs. You can
total based on different attributes and thereby make the totals more transparent.
The report can be found:
o From the SAP Easy Access screen under Periodic Processing -> Closing Preparation ->
Receivable/Revenue Adjustment
o From the menu of the transfer posting programs under Environment -> Line Items
INS_FSCD_CI_4: Collections Management (New)
Use
Updating Collection Strategies
As of SAP enhancement package 6 for SAP ERP 6.0, you can use predefined master data selections
when updating collection strategies.
To do so, you first have to create a preselection and execute it. From the SAP Easy Access screen,
choose Periodic Processing -> Technical Preparations.
You can then use this preselection as an additional selection criterion when updating collection
strategies (on the SAP Easy Access screen, choose Periodic Processing -> For Contract Accounts
-> Dunning Notice -> By Collection Strategy -> Update Collection Strategies).
Note
Regardless of the selection type of the preselection, the system determines only business partners if
you use preselections when updating a collection strategy (transaction FPCCU).
Dunning by Collection Strategy with BRFplus
As of SAP enhancement package 6 for SAP ERP 6.0, you can use BRFplus for dunning by collection
strategy. If you assign a BRFplus function to a collection strategy, event 0315 (Determine Next
Collection Step) calls the BRFplus function.
In a similar way as for a BRF trace, the system stores a BRFplus trace that you can display.
Effects on Customizing
Create a BRFplus function in Customizing for Contract Accounts Receivable and Payable under
Business Transactions -> Dunning Notices -> Dunning by Collection Strategy -> Settings for
BRFplus (see the sample application in the activity Example Application for BRFplus).
Assign a BRFplus function to the collection strategy under Business Transactions -> Dunning
Notices -> Dunning by Collection Strategy -> Define Collection Strategy. If you assign both a
BRFplus function and a BRF event to the collection strategy at the same time, then the sample
function module FKK_SAMPLE_0315 executes the BRFplus function.
INS_FSCD_CI_4: Posting Area Views (New)
Use
In Customizing, you can derive multiple function fields from various key fields in a posting area. Even if
not all function fields depend on all key fields, you have to nonetheless enter all possible combinations
when configuring a posting area. To reduce the number of entries to those that are actually needed,
as of SAP enhancement package 6 for SAP ERP 6.0, you can define posting area views for individual
posting areas.
Note
The use of views is optional. That means that even if SAP makes views available for a given posting
area, you do not have to work with views.
In posting areas where SAP provides for views, you can define up to three views.
A view acts like a separate posting area. For example, you can derive the first function field from
exactly the first key field, and for all other function fields provide another key selection, which does not
have to contain the first key field. As a result, you do not have to define as many combinations of key
fields. The number of entries is thereby reduced.
Note
Whenever you activate or deactivate a view, you have to check and adjust the field assignment.
If you already made settings in a posting area, for which SAP now allows views, once you have
activated views for the posting area, you have to change and adjust the existing settings. (This is
similar to the procedure for a changed key selection.) You must assign each function field to exactly
one active view. In each view, you can choose the key fields necessary for the derivation as new and
as appropriate for the view.
The application continues to call the account determination only once (and not for each view).
Internally, the system determines the active views, and combines the results from these views. You
can also, as before, simulate the results of account determination using the Simulation function.
If you have defined views for a posting area, you must select a view on the initial screen for account
determination.
INS_FSCD_CI_4: Archiving in Contract Accounts Receivable and Payable (New)
Use
Parallel Document Archiving (Archiving Object FI_MKKDOC)
As of SAP enhancement package 6 for SAP ERP 6.0, you can use document archiving as a mass
activity in Contract Accounts Receivable and Payable. As a result, you can now process the
documents in parallel in multiple runs.
The system executes the scheduled jobs immediately when the mass activity is started. The same
prerequisites apply for this archiving as for the generation of archive files for FI-CA documents in
archive administration (SARA). You can access the transaction for parallel document archiving from
the SAP Easy Access screen under Periodic Processing -> Archive Data -> Documents (Parallel
Processing).
INS_FSCD_CI_4: Account Balance (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, you can display your own selection screen in
the account balance as follows:
o You can call the additional selection screen with a customer-specific transaction and thereby
place a variant alongside the account balance display (transaction FPL9).
o You can integrate the additional selection screen directly in the account balance display
(transaction FPL9).
Effects on Customizing
Enter the program and application in Customizing for Contract Accounts Receivable and Payable
under Basic Functions -> Postings and Documents -> Document -> Screen Preparations ->
Include Own Fields in Detail Screens.
INS_FSCD_CI_4: Integration with SAP Credit Management (New)
Use
As of SAP enhancement package 6 for SAP ERP 6.0, the following new functions are available for
updating credit exposure in SAP Credit Management.
Update of credit exposure for billable items
Contract Accounts Receivable and Payable now also transfers credit exposure for billable items and
billed but not yet invoiced items from billing in Contract Accounts Receivable and Payable to SAP
Credit Management. Contract Accounts Receivable and Payable transfers the credit exposure for
billable items with status billable (2) with the credit exposure category 220; for billable items with status
billed (4) it uses credit exposure category 210. In SAP Credit Management, the credit exposure
category serves to differentiate the various credit exposures, such as billable items and open items.
At event 4512, you can determine different credit exposure categories for billable and billed items.
Note
The transfer takes place only for items that were created for billing in postpaid scenarios.
Update of credit exposure for external billing systems
By defining an external credit exposure category, you can prevent SAP Credit Management from
considering credit exposures twice that are reported both by an external billing system and Contract
Accounts Receivable and Payable. If an external application reported a credit exposure with this
external credit exposure category to SAP Credit Management, then the mass activity Transfer of
Credit Data (transaction FPCM1) resets this external credit exposure in SAP Credit Management, and
reports the credit exposure in the form of billable items, billing documents, or FI-CA posting
documents, using the credit exposure categories of Contract Accounts Receivable and Payable, to
SAP Credit Management.
Effects on Customizing
Update of credit exposure for billable items
If you want to transfer the credit exposure for billable and billed but not yet invoiced items from Billing
in Contract Accounts Receivable and Payable to SAP Credit Management, then you have to set the
Bill.Active indicator in Customizing for Contract Accounts Receivable and Payable under Integration
-> Financial Supply Chain Management -> Credit Management in the activity Activate Credit
Management.
Update of credit exposure for external billing systems
You enter external credit exposure categories in Customizing for Contract Accounts Receivable and
Payable under Integration -> Financial Supply Chain Management -> Credit Management ->
Define Credit Exposure Category for External Billing Systems.
INS_FSCD_CI_4: Brazil: Boleto (New)
Use
If vendors also present you with boletos along with their invoices, as of SAP enhancement package 6
for SAP ERP 6.0, you can manually enter, change and display the bar codes of the boletos in the
corresponding document items when posting the payables in Contract Accounts Receivable and
Payable. This enables you to create a direct relationship between the document and the invoice
(boleto).
To be able to use the new Bar Code field for payables in Brazilian company codes, you have to make
the field visible in the corresponding transactions. To do so, you implement the enhancement
described in the section "Effects on Customizing". Then you can use the field as follows:
o During document entry (FPE1), you can enter a bar code in the detail view under Dunning
Data/Payment Data.
o The document display (FPE3) displays the bar code on the Payment Data tab page.
o The payment run (FPY1) uses the Bar Code as a separation criterion for creating separate
payments and pays only those items together that have the same bar code.
o When changing a document (FPE2), you can enter the bar code on the Payment Data tab
page.
o During a document change by BAPI, you can transfer the field BARCODE to the BAPI
BAPI_CTRACDOCUMENT_CHANGE in the structure BAPIDFKKOPCH.
Effects on Customizing
To activate the Bar Code field, execute the report in Customizing for Contract Accounts Receivable
and Payable under Program Enhancements -> Prepared Enhancements -> Add Field for Bar
Code to Business Partner Item. The report adds the Bar Code field to the business partner item.
INS_FSCD_CI_4: New Events (New)
Use
As of SAP ERP 6.0, Enhancement Package 6, you can use the following new events:
o 0067: Posting: Exchange Tax on Sales/Purchases Code
o 0176: Taxes: Change Withholding Tax Base Amount
o 0177: Taxes: Add or Correct Withholding Tax Supplements
o 0235: Payment Lot: Limit Search for Similar Keys
o 0550: Provider Contract: Report Changes Further
o 0551: Provider Contract: Enrichment of Industry/Customer Fields
o 0552: Provider Contract: Jump to Contract from Contract Account
o 0965: Prepaid: Derive Prepaid Account from Reference Details
o 0966: Prepaid: Refills and Other Balance Changes
o 0967: Prepaid: Determine Balance of Prepaid Accounts
o 0968: Prepaid: Determine Posting Rule for Reversal
o 0969: Prepaid: Specifications for Payment Authorization
o 0995: Prepaid: Check Table of Messages
o 0996: Prepaid: Process Messages
o 0997: Prepaid: Display Transactions
o 0999: Prepaid Account: Report Changes Further
o 1744: MassAct: Clearing of Prepaid Accounts
o 1745: MassAct: Clearing of Prepaid Accounts, Shift Parameters
o 1785: MassAct: Parallel Document Archiving
o 1876: MassAct: Prepaid Account Closing Operations
o 1877: MassAct: Prepaid Acct Closing Operations, Move Parameters
o 2740: MassAct: Parallel Archiving of Invoicing Documents
o 2742: MassAct: Parallel Archiving of Billing Documents
o 2788: CRM-FCC Enrichment of List of Invoicing Documents
o 2789: CRM-FCC Enrichment of Invoicing Document
o 4512: Determination of Credit Exposure Category for Billable Items
o 4515: Change Amounts for Billable and Billed Items
o 5701: SAP CC: Exclude Business Partner from Distribution
o 5702: SAP CC: Exclude Contract Account from Distribution
o 5703: SAP CC: Additional Data for Business Partner
o 5704: SAP CC: Additional Data for Contract Account
o 5705: SAP CC: Additional Data for Prepaid Account
o 6531: Requests: Account Assignments for Earmarked Funds with Tax
o 8140: BIX: Parallel Archiving of Billed Items
o 8171: CRM-FCC Enrichment of Billable Items
Effects on Customizing
You enter installation-specific function modules in Customizing for Contract Accounts Receivable and
Payable under Program Enhancements -> Define Customer-Specific Function Modules.
Release Notes as of SAP enhancement package 6 for SAP ERP 6.0,
Support Package 3
INS_FSCD_CI_4B: Business Function SAP for Insurance: Inkasso/Exkasso 4B
Use
As of Enhancement Package 6 for SAP ERP 6.0 Support Package 3, Industry Extension Insurance (INSURANCE
606), the Business Function SAP for Insurance: Collections/Disbursements 4B (INS_FSCD_CI_4B) is available.
The functions of this Business Function are described first in an overview chapter, then later in more detail:
Overview: Business Function INS_FSCD_CI_4B
a) Alternative collecting broker in document
This function is delivered as a prepared enhancement. You can use the new fields in the business partner item if
you have activated the Alternative Collecting Broker prepared enhancement in Customizing:
Checkbox: Direct Collections [DIRCOLL]
Alternative collecting broker [ALTBROK]
Broker contract for the alternative collecting broker [ALTBRCO]
After you have activated the Alternative Collecting Broker prepared enhancement, you can define on line item level
which broker is to perform collections and disbursements. You can use the new fields for premiums or claims
category postings. They are independent of broker assignment in master data of the insurance relationship (tab
page Broker Collections for Insurance Object) and are given preferential treatment to it. Furthermore, on document
line item level, you can select the Direct Collections checkbox to define that a claim/liability is to be paid directly,
although the insurance relationship is assigned via master data to a broker for settlement.
To simplify matters, when we mention "new fields" from now on, the fields above are meant. When we use the
expression "assignment of master data to a broker" or "assignment of document line items to a broker",
assignment to an associated broker contract is also implicit.
Activate these new fields in Customizing so that they are available in the corresponding structures. In Customizing
for Insurance, choose: Collections/Disbursements -> Program Enhancements -> Prepared Enhancements ->
Activate Alternative Collecting Broker
Make settings for broker assignments in Customizing under: Contract Accounts Receivable and Payable -> Broker
Collections -> Basic Settings -> Activation of Basic Functions
Note
The Alternative Collecting Broker prepared enhancement cannot be activated together with the Italian agency
collection.
b) Broker Net View
You now have the option in the account balance and outbound correspondence for the broker report to display
premiums and their associated commissions in a net view, that is, premiums less commissions. A premium and its
associated commission are displayed in one line. You can now use this new display to display with ease the
dependencies between premiums and commissions. Furthermore, you can show or hide commissions assigned to
a premium or claim in the account balance in a separate menu option.
c) More functions in broker collections
In broker collections, the following new functions are available:
In the context of the Create Broker Report mass activity, you can perform a simulation run.
If the broker report has not yet been posted, you can reopen a closed broker report and continue to process
it.
In the broker report item on the Payment Data tab page, the new Processing Information field is available so
you can, for example, define information useful for processing clarification cases.
When processing a broker report, you can create notification items. You can freely choose the broker in the
item without there being a relationship between the assigned broker and the customer or insurance
object.
In the dunning proposal run, you can continue to process claims locked in a dunning lock for ependent
contracts for the broker contract in new event V313.
Details: Business Function INS_FSCD_CI_4B
a) Alternative collecting broker in document
Activate Alternative Collecting Broker
The new fields in the business partner item are included in the business partner document and several other
structures via the Activate Alternative Collecting Broker prepared enhancement. To make the fields available in the
relevant structures, they must first be activated. In Customizing, choose: Contract Accounts Receivable and
Payable -> Program Enhancements -> Prepared Enhancements -> Activate Alternative Collecting Broker.
After the prepared enhancement has been activated, the fields are available in the different processes. The new
fields are permissible for postings of the premium or claims category, and, when filled, override the assignment to
a collecting broker defined in the insurance object. You can fill the new fields by using the payment plan interface
or services, or by entering documents manually. Make additional settings for broker assignments in Customizing
under: Contract Accounts Receivable and Payable-> Broker Collections-> Basic Settings -> Activation of Basic
Functions
Payment plan interface
The new fields are only supported for one-time payments (PSNGL='X'). The fields are not supported for recurring
payment plan items. If the new fields are filled in the payment plan item, they are transferred automatically in the
debit position to the document line item created. It is not possible to aggregate payment plan items with different
values in one of the new fierds. This means that if different values are filled and aggregation is active, multiple
document line items or documents (if grouping is active) are created.
If the payment plan items were enhanced with the new fields, the following CI includes are filled:
CI_PP: CI include for table VVSCPOS (payment plan items).
CI_VVSCITEM: CI include for table VVSCITEM. (payment plan subitems)
CI_ISCD: CI include for structure SVVSCPOS_B (direct input template structure)
The new fields can be filled by using the following interfaces for payment plan items:
In dialog mode:
You can use insurance object maintenance to process the payment plan items.
On the Payment Plan Item Document II tab page, in the FS-CD Fields group box, you can process the new fields.
Direct Input and RFC:
The new fields are available via the CI_ISCD CI include.
BAPI:
If you have activated the new fields in Customizing, the corresponding structures are available. In Customizing,
choose: SAP Insurance -> Contract Accounts Receivable and Payable -> Program Enhancements -> Prepared
Enhancements -> Activate Alternative Collecting Broker. Activation ensures that the new fields are added in the CI
Includes (customer-defined extension). For the relevant BAPIs, the new fields are transferred by using the
EXTENSIONIN parameter. For more information, see SAP Note 1636686.
Services
The following services for the Insurance Collection Disbursement Request business object were enhanced with
the new fields:
InsuranceCollectionDisbursementRequestERPBulkCreateRequest_In
InsuranceCollectionDisbursementRequestERPCreateCheckQueryResponse_In
InsuranceCollectionDisbursementRequestERPByIDQueryResponse_In
InsuranceCollectionDisbursementRequestERPByBaseBusinessTransactionDocumentReferenceQueryResp
onse_In
These services now have new elements in the InsuranceCollectionDisbursementRequest-Item structure:
DirectlyCollectedIndicator: Field for the Direct Collections checkbox
ThirdPartyCollection: Structure for specifying the alternative collecting broker and broker contract
CollectionRepresentativeParty: Structure for specifying the alternative collecting broker
BusinessPartnerInternalID: Internal business partner ID for the broker
BusinessPartnerID: External business partner ID for the broker
CollectorContract: Structure for specifying the alternative collecting broker contract
InsuranceCollectionDisbursementAgreementID: Internal insurance object ID for the broker contract
BaseContractBusinessTransactionDocumentReference: Reference to the broker contract in the feeder
system (contract type, contract ID, contract subtype, contract sub-ID, feeder system ID)
If the above fields are filled in the service structure, they are automatically transferred to the new fields in the
payment plan item or items created.
Post/change/display documents (FPE1/FPE2/FPE3) and mass document change (FPE2M)
In the Post Document (FPE1) transaction, you can use line list variants to show the new fields on the list screen of
the business partner items. In the detail screen, the fields are in the FS-CD Fields group box. For document
display and document change, the new fields are shown on the FS-CD Data tab page. The new fields are ready
for input when posting a document, and can also be changed at a later time by using the Change Document
transaction.
If the broker contract for an alternative collecting broker is unique, it is automatically enhanced by the system.
Setting the broker fields in the document and selecting the Direct Collections checkbox at the same time are
mutually exclusive and generate a corresponding error message. When making changes to the new fields in the
context of changing a document, change documents are written and are displayed in the document display. In
mass document change (FPE2M), it is possible to change the values of the fields for individual items or to specify
the changed values in the upper screen area so they can be transferred simultaneously to several selected line
items.
Processing broker reports
Settlement with the broker still takes place via the broker report, which now takes document entries as well as
master data into account. If you have selected the Direct Collections checkbox, the line items affected are
excluded with exception reason 017 from selection. If required, they can be made available again for selection at
event V520. Posting broker reports can result in new on-account items. You can define a derivation rule that
specifies, for example, whether or not the new fields are to be filled for newly created on-account items. To do this,
in Customizing, choose: Contract Accounts Receivable and Payable-> Broker Collections-> Settings for Posting
Broker Reports-> Configure Clarification Code.
Mass activity Create Broker Account (IBR50)
For broker reports created periodically, when manually creating broker reports, documents with an alternative
collecting broker are now also taken into account. The program run in the activity interval (event V482) is changed
so that not only brokers assigned via master data to an insurance contract are taken into account, but also all the
brokers available in the system for whom periodic creation of broker reports is intended.
Web Broker
For Web brokers, not only the insurance master data relationship is taken into account when selecting the items to
be reported by the broker, but also the items in which the Web broker is defined as an alternative collecting
broker are selected.
Account Display (IBR02 / FPL9)
In the Account Display (IBR02) transaction, the Further Selections for Broker group box was enhanced by the Also
Select Using Documents checkbox. If you select the Select Using Documents checkbox, in addition to the
documents found through master data relationships, the system also selects the documents in which the broker is
defined as an alternative collecting broker and the documents selected with the Direct Collections checkbox.
If you also select the Coll. Rel. Only checkbox, only documents for which the broker makes direct collections are
selected. This selection takes into account all documents that are relevant through master data and the alternative
collecting broker in the document.
The Select Using Documents checkbox is not available in transaction FPL9. When selecting the items, all
documents with the Alternative Collecting Broker or the Direct Collections checkbox are taken into account. When
included in line layout variants (Customizing) the new fields can be displayed in the account display (IBR02/FPL9).
By double-clicking the new fields (alternative collecting broker/broker contract) in the line item, you can navigate to
the corresponding master data (business partner/insurance object).
Customers for Broker (IBR06)
You can use this function to display all customers assigned to a broker in list form. Transaction IBR06 was
enhanced with the following fields:
Select Using Master Data
When you select the Select Using Master Data checkbox, all customers that exist for an insurance object with an
assigned broker (Broker tab page) are selected for each broker. If you also select the Coll.-Rel. Only checkbox,
only customers whose items are settled by using a broker are selected.
Select Using Documents
If you select the Select Using Documents checkbox, data from open items in which the broker is defined as the
collecting broker is also taken into account. If you also select the With Cleared Documents checkbox, cleared
items are also taken into account.
Broker for Customer (IBR06)
You can use this new report to display in list form all brokers assigned to an insurance customer. The following
selection options are available:
Select Using Master Data
If you select the Select Using Master Data checkbox, all brokers entered in the insurance object on the Broker tab
page are selected for each customer. If you also select the Coll.-Rel. Onlycheckbox, only the brokers responsible
for settling open items are selected for each customer.
Select Using Documents
If you select the Select Using Documents checkbox, all assigned brokers specified in open items as alternative
collecting broker are selected for each customer. If you also select the With Cleared Documents checkbox, cleared
items are also taken into account.
Dunning Proposal Insurance (VPVA)
In the broker contract, you can set a dunning lock for assigned insurance objects. This dunning lock ensures that
dunnable items of a insurance object relationship are not dunned if they are assigned to a broker contract with a
dunning lock for assigned insurance objects. Previously, the assignment check was exclusively on master data
level. The new enhancement extends the check to the document.
The following applies:
If a collecting broker is assigned in a document due for dunning, the dunning lock check for assigned
insurance objects is performed for the broker contract specified in the document.
If the Direct Collections checkbox is selected in a document due for dunning, the dunning lock for assigned
insurance objects is not checked. The document due for dunning is dunned if a dunning variant has been
defined.
If the Broker Dunning Status function is used, it may happen that the dunning lines for a dunning grouping are
assigned to multiple brokers/broker contracts. Note that in the default characteristic value of event 0301, the
triggering document with the most recent due date decides the broker/broker contract to which the dunning group
is assigned.
Payment Run
Documents with the Direct Collections indicator and a valid payment method are settled by the payment run, even
if a collecting broker is specified in the insurance relationship on master data level.
Installment Plan
Both the installment plan items and installment plan charge inherit the new fields from the original item with the
highest amount (event 3000). When creating an installment plan by using transaction FPR1, the new fields are
available to you in the detail screen and can be modified for each item. You can only make changes to installment
plan items by using transaction FPR2. It is not possible to use the change document (FPE2) transaction to make
changes to an installment plan item or the original document.
Returns
In the New Claims with Explicit Input returns mode, the new fields are visible and ready for input. New claims from
returns posting inherit the new fields from the original items. For return charges passed on to the customer, the
following applies: The new fields (for example, the Direct Collections indicator) are inherited from the item with the
greatest amount of contribution originally cleared with the payment document to be reversed.
Promises to Pay
If charges are posted when creating a promise to pay, they inherit the new fields from the items received in the
promise to pay. Here too, the item with the greatest amount received in the promise to pay inherits the new fields.
You can implement an alternative logic by using event 0186.
Resetting Clearing
The new fields are not inherited in the new on-account items in the resetting clearing document because the
assignment of claims for payment has just been withdrawn and would contain content errors. However, by making
document changes, you can change the new fields in the on-account postings.
Interest
When posting claims for interest, the new fields are inherited from the claims bearing interest.
Item List [FPO4]
In the Item List transaction [FPO4], you can use a predefined selection of brokers, defined earlier in the
Preparations for Evaluations (FPSELP) transaction, in which the system also takes into account those customers
in whose documents the respective broker is selected as the alternative collecting broker. In transaction FPO4, on
the basis of the broker hierarchy, the system also determines the documents in which the broker is selected as the
alternative collecting broker in the line items.
Transfer Items [FP40 ]/Process Credit [FPTCRPO]
When you transfer open items, the new fields are transferred to the new documents.
Processing of Duplicates
You can use processing of duplicates to reassign payment plans not yet posted and open items of the
policyholder, and so reduce the number of duplicated business partners.
If a broker duplicate is involved, the new functionality lets you reassign to the current broker open items for which
the duplicate was defined for the alternative collecting broker. You can make reassignments by using the new
Reassign Open Items with Alternative Collecting Broker (VO2) activity. In Customizing for Insurance, choose:
Collections/Disbursements-> Business Transactions-> Processing of Duplicates.
If Open Payment Plan Items duplicates are involved in which the duplicate is defined for the alternative collecting
broker, the alternative collecting broker is also updated in this case. The update to be executed is preselected in a
table and the current collecting broker is defined in the document at the time of debit entry, when the system
creates a document from the open payment plan item.
Define Activity for Duplicate Processing
In this Customizing activity, you can define the processing level on which the system executes the new
Reassign Open Items with Alternative Collecting Broker(V02) activity for processing of duplicates, and the
function module to control how the activity functions.
Define Order of Activities
In this Customizing activity, you can define the order in which the activities for processing of duplicates are
to be executed.
Policyholder Change (VCPH1)/Transfer Items (FP40)
You can use the Policyholder Change (VCPH1) transaction to reassign payment plans not yet posted and
policyholder open items.
If a broker policyholder change is involved, the new functionality lets you reassign to the current broker open
items for which the previous broker was defined as the alternative collecting broker. You can make reassignments
by using the new Reassign Open Items with Alternative Collecting Broker (VO2) activity.
If Open Payment Plan Items policyholder changes are involved in which the previous broker is defined as the
alternative collecting broker, the alternative collecting broker is also updated in this case. The update to be
executed is preselected in a table and the current collecting broker is defined in the document at the time of debit
entry, when the system creates a document from the open payment plan item.
Example
If, for example, you want to reassign a broker contract from broker A to broker B, then the line items with
alternative collecting broker A are reassigned to alternative collecting broker B. Payment plan items created for a
predecessor business partner are posted to the successor when creating payment plan subitems. New here is
that the field for the collecting broker is also taken into account.
Reassigning open items with adjustment of the alternative collecting broker on line item level takes place
analogously in transaction FP40 (Transfer Items) as well as by using the "Reassign" functionality from credit
processing.
Correspondence
When creating the broker contract statement (IBR40), the new fields are also taken into account in the document.
All line items assigned to the broker and the corresponding broker contract are displayed in list form. If the broker
with the corresponding broker contract is assigned to an insurance relationship through master data, and there are
items for this insurance relationship selected with the Direct Collections checkbox, or
there are items for which an alternative collecting broker was defined
in the document, the items appear for informational purposes in the list.
b) Broker Net View
Grouping in the Account Balance
In account balance transactions (IBR02 and FPL9), in the List Display group box, you can use the new Grouping
field. Here, you can select one of the groupings already used in fast entry for the broker report (IBR01). The
grouping enables premiums and claims to be assigned in fast entry and in account balances. By specifying a
grouping, premiums/claims and their assigned commissions are displayed in one line. Besides the grouping, you
must ensure, for the assignment, that a reference to premiums/claims is defined in the additional reference
(VTRE2) and alternative partner (VGPART2) fields in the commission document.
Assignment of Premiums/Expenses and Commissions in Event 1211
The items are assigned in accordance with the selected grouping on the entry screen in which an FSCD-specific
function module is registered as an application module for event 1211. If you have registered a function module
of your own for this event, you should firstly call the FSCD-specific function module and then process your own
logic. The standard application module supplied for event 1211 groups together one or several commissions for
an item of the premium or claims type at the exact moment the fields of the selected grouping match. If there are
multiple premium-/claims items for a commission, no assignment takes place.
Showing/Hiding Commissions in the Account Balance
You can show or hide commissions assigned to a premium or claim in the account balance in a separate menu
option.
Navigating to Assigned Commissions
You can use the context menu to display commissions assigned to a premium in a separate window. To do this,
select Display Assigned Commissions. You can do this both for single item variants or for totals variants. To
display assigned commissions, you can make settings for your own line layout variant.
Correspondence
A net view is also available for the automatic broker report (V023) and broker invoice (V020) correspondence
types. The ISISCD_BROK_INV form class was enhanced. In the form class, the new form level BSTMP_NV
(structure IBROSTMP_NV) is available. You can incorporate the fields of structure IBROSTMP_NV in
customer-specific forms and hence create a print version with a net view. In structure IBROSTMP_NV, the
XASSIGNEDCOMM field is set when a commission was assigned to a premium or a claim. This lets you decide
for each customer whether assigned commissions are to be printed in a separate line or whether unassigned
items are to be printed separately.
c) More functions in broker collections
Simulation Mode in the Create Broker Report (IBR50) Mass Activity
On the initial screen of the broker report, you now have the option to select the Simulation Mode indicator. In
simulation mode, no reports are created, and there are no entries in the correspondence container.
Broker report transfer program (IBR51) / BAPIs for broker report
In the Broker Report Transfer Program (IBR51) transaction, structure IBROSTMP_EXT was enhanced with the
Processing Information field. The new field is available so you can, for example, specify information for
processing clarification cases. The Processing Info field can also be transferred with the following BAPIs to the
broker report item:
BAPI_BROKERREP_ADDITEM
BAPI_BROKERREP_CHANGEITEM
Mass activity Request Broker Report (IBR60)
The system creates a correspondence for all broker contracts of the periodic broker report request type,
irrespective of whether the broker is assigned to an insurance contract or not. This means a broker report is also
requested even if the broker is not assigned to an insurance contract, and is only entered at document level as
collecting broker.
Restricting the selection to specific business partners, contract accounts, or contracts assigned to a broker or
broker contract is not supported here for performance reasons.
Reopening a Broker Report
Just like a payment lot, you can reopen and continue to process a broker report that has closed status. Before
posting the broker report, it must be closed again. This makes it easier to make changes later to broker reports
that are already closed.
New Processing Info Field in the Broker Report Item
In the broker report item, under the Amount Usage group box on the Payment Data Detailed View tab page, the
new Processing Info field is available. You can fill this field, for example, with information for processing
clarification cases. The Processing Info field is also available as a selection field for selecting clarification cases
from the clarification worklist (transaction IBR04).
Broker in item freely selectable
This allows notification items to be created in a broker report without an existing assignment of the broker to an
insurance relationship. If the checkbox is selected in Customizing, under: Contract Accounts Receivable and
Payable -> Broker Collections -> Basic Settings -> Activation of Basic Functions, then a notification item can be
created and saved even if there is no relationship between the customer/insurance object and the broker/broker
contract. You simply see a warning referring to the missing relationship.
Dunning Proposal Insurance (VPVA)
The dunning proposal processes the new event V313. Here, as for event V311, you can further process claims
that are locked for dunning. The reason for the dunning lock on the claim is a dunning lock for assigned
insurance objects in the broker contract.
Effects on Customizing
In Customizing for Insurance, under: Collections/Disbursements -> Program Enhancements-> Prepared
Enhancements, the Activate Alternative Collecting Broker Customizing activity was added.
To be able to use the functions of the alternative collecting broker prepared enhancement, perform the following
activities:
1. In transaction SFW5, switch on the business function SAP for Insurance: Collections/Disbursements 4B
(INS_FSCD_CI_4B).
2. In Customizing, choose: Contract Accounts Receivable and Payable -> Program Enhancements -> Prepared
Enhancements -> Activate Alternative Collecting Broker. Activation of the prepared enhancement is a
prerequisite for using the fields in various processes. The new fields are permissible for postings of the
premium or claims category, and, when they are filled, override the assignment to a collecting broker
defined in the insurance object. You can fill the new fields, as described above, by using the payment plan
interface or services, or by entering documents manually.
3. Make settings for broker assignments in Customizing under: Contract Accounts Receivable and Payable ->
Broker Collections -> Basic Settings -> Activation of Basic Functions.
Result
After activation, the fields in the line items are available to you, that is, the system automatically creates the fields
and database indexes.
In Customizing, under: Contract Accounts Receivable and Payable -> Broker Collections -> Basic Settings ->
Activation of Basic Settings, the following two group boxes have been added:
Enhanced Broker Assignment for Notification Items
You can use the Include Cleared Document Line Items checkbox to specify whether the system should take
brokers entered in cleared documents into account in searches. You can also enhance the analysis period by
specifying the number of days the system is to take into account in the search in the Number of Days Before the
Analysis Period field Then the system takes this additional analysis period into account when searching for
assigned brokers.
Settings for Notification Creation
If you select the Allow Broker Without Relationships checkbox, you allow the creation of notification items for
brokers or broker contracts for which no relationship to the customer exists.
If you select this checkbox, you can create and save notification items even if no relationship exists between the
customer/insurance object and the broker or broker contract. The system simply issues an error message
referring to the missing relationship.
In Customizing, under: Contract Accounts Receivable and Payable ->Broker Collections -> Settings for Posting
Broker Reports -> Configure Clarification Code, you can define a derivation rule for a clarification code that
specifies, for example, how or whether new fields for newly created on-account items are to be filled.
