Professional Documents
Culture Documents
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure.
Subtopics from other structures are not included.
2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior
notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 1 of 8
TABLE OF CONTENT
1 Information Container
1.1 Information Type
1.1.1 Adjust Information Types
1.2 Confirmation
1.3 Storing Confirmations in the Info Container
1.4 Forwarding and Reading of Confirmations
1.5 Display the Information Container
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 2 of 8
1 Information Container
Purpose
The information container (IC) is flexible temporary storage, which contains information about business transactions and processes, in
the form of confirmations , which trigger downstream processes in other systems.
You can use the information container to store information from Collections/Disbursements processes centrally, and to transfer it to
upstream or downstream SAP or external systems. When specific business transactions occur (reaching a specific dunning level or
receipt of bank returns, for example), confirmations are updated in the information container and predefined communication methods
are forwarded to the relevant recipient systems.
The definition of information types and their attributes determines which data is transferred to the information, and which processes this
is for. The standard delivery contains various standard information types, including the function modules used by the triggering
processes to write the confirmations to the information container.
Implementation Considerations
You can find more information about setting up and adjusting the information types, with their associated communication types, in the
Implementation Guide under Collections/Disbursements Integration Information Container.
You control the authorizations for the information container (such as displaying the container and forwarding confirmations) with the
authorization object I_VV_IC.
Integration
You use automated formatting of information from the information container to support Collections/Disbursements in cross-system
processing of business processes - between Collections/Disbursements and other SAP components such as Financial Services Policy
Management (FS-PM) and your customer-specific (external) systems. The information container can therefore be used to standardize
outgoing FS-CD interfaces.
Scope of Functions
The information container provides you with the following options:
Predefined Standard Information Types
Mass activity for efficient forwarding of confirmations
Generic services for storage and forwarding of confirmations
You can find more information under Storage
Restrictions
The information container is not intended for the processing of mass data, such as general clearing information and daily master data
changes. The storage of such large amounts of data could lead to negative effects on system performance in the triggering processes.
The
Forwarding Clearing Information function is available for forwarding information of this type.
Use
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 3 of 8
The information types are defined in Customizing. You can find the settings under Collections/Disbursements Integration
Information Container Define Information Types.
Standard Information Types
The standard delivery contains the following standard information types, including the function modules used by the triggering processes
to write the confirmations to the information container.
V001 (special dunning level) creates confirmations from the dunning activity run for a current dunning procedure (for example, if a certain dunning level has
been reached).
V002 (returns) creates confirmations if a return has been received from the bank.
V003 (insufficient deposit coverage) creates confirmation if insufficient credit is available in a deposit to clear the affected open items.
V004 quotation acceptance) creates confirmations if a contract quotation has been implicitly accepted by a payment.
V005 (premium adjustment) creates confirmations if a dynamic premium adjustment has been refused.
If no suitable payment has been received before a specific deadline (meaning that the adjustment has been implicitly rejected), the data is forwarded.
V006 (customer-initiated payment) creates confirmations on payment receipt for insurance contracts, for which a customer-initiated payment method has
been agreed.
This information is relevant for contracts with non-periodic payment form.
V007 (benefit case) creates confirmations if a contract is benefit-free (predefined dunning level reached) or has benefits again (dunning procedure ended).
To enable the system to create confirmations, you must make additional settings for most standard information types in the system.
For more information, see the documentation for the IMG activity Define Information Types.
for
Procedure
Depending on how you want to map your own fields, you have the following options:
Change contents of standard info fields
1. Change the contents of the info fields for the information type in Customizing, under Collections/Disbursements Integration
Information Container Define Information Types.
The fields available are dependent on the triggering process. Take note of the documentation for the function module
VINFO_SAMPLE_V253.
In the Info Field field, enter the object from which the values are now to be read.
2. Copy the sample module defined for event V253 for the assignment of fields, and adjust the assignment for the new info fields.
Include Own Fields in Customer Include
1. Full the CI_DVIINFO customer include in the DVIINFO table with the fields that you also want to transfer to the information container.
2. Copy the sample module defined for event V253 for the assignment of fields, and assign the appropriate values to the customer
fields there.
The fields available are dependent on the triggering process. Take note of the documentation for the function module
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 4 of 8
VINFO_SAMPLE_V253.
Store additional fields in the data container
1. For the desired information type, define in Customizing that information is to be stored in the data container
(Collections/Disbursements Integration Information Container Define Information Types).
2. Copy the function module defined for event V251 and define which of the fields offered the system is to store in the data container.
Result
When storing the confirmations in the information container or the data container, the fields and values you have defined are transferred.
However, the additional fields in the customer include and the data container are not taken into account for the display for the
information container .
Example
You want to adjust the transferred information for the standard information type V002 (Returns) so that the information for the returns lot
is not taken from the RLKEY field (standard setting) and the item number from the returns lot (POSRA field in the DFKKRH table) is
transferred.
This is possible, as the fields for the DFKKOP and DFKKRH tables can be used for information type V002:
1. In the Define Information Types IMG activity, replace the field that is defined for information type V002 in Info Field 4 with the field
name POSRA.
2. In your module for event V253, assign the value is_dviinfotype-v002icbankreturn-fkkrh-posra to the I_DVIINFO_DATA4 field in the
case instruction WHEN V002.
1.2 Confirmation
Definition
Message that is generated by a Collections/Disbursements process and stored in the information container.
The system generates and updates confirmations when business transactions occur. You can use predefined communication types to
transfer them to other components/systems and then trigger a subsequent process in the recipient system.
Use
A confirmation contains all information about a process that is required to identify the business transaction and trigger any necessary
follow-up actions. This includes general information such as business partner and insurance object, as well as process-specific data that
is determined by the underlying information type.
If you have activated an information type in Customizing, the system generates a confirmation in the information container when
predefined business transactions occur.
During communication with the SAP Exchange Infrastructure (SAP XI), the confirmation corresponds to a message
Structure
A confirmation in the information container consists of the following elements:
General information for identifying the confirmation (information type, system data, data for triggering mass activity)
General master data information (business partner, contract account, insurance object)
Process information (dependent on triggering process, such as the dunning level reached in the dunning process).
Confirmations have a predefined structure, which you can extend on an individual basis (see Adjust Information Types). The structure
corresponds to the table DVIINFO.
Structure of a Standard Information Type
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 5 of 8
Field
Description
INFOHKF
CD
INFOTYP
INFOTYP_VI
V002
INFOKEY
INFOKEY_VI
427B206FA8A64DEOE10000
UNAME
User name
C5055065
CDATE
11.03.2005
CTIME
09:15:00
XTRIAL
XTRIAL_VI
GPART
BU_PARTNER_VI
ZLATAN0711
VKONT
VKONT_VI
USERK0711
VTREF
INSOBJECT_MD_VI
VOBJ05147888
ENTID<number>
ENTID_VI
OPBEL
BETRW
RLBEL
RLKEY
DATA<number>
CDATA_VI
000001000782
100.00
11000000465
11052005_GOS
XCODT_CLUST
XCODT_CLUST_VI
LAUFD
CREATE_LAUFD_VI
<empty>
(Confirmation for V002 are not
generated by a mass activity)
LAUFI
<empty>
(Confirmation for V002 are not
generated by a mass activity)
INFO_LAUFD
20050816
INFO_LAUFI
INFO_LAUFD_VI
ZL01
The data container enables you to store and read data with complex structures. The structure of the stored data is dependent on the
information type.
Prerequisites
You have made the necessary Customizing settings for the information types, for which the system is to store confirmations in the information container.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 6 of 8
You can find more information in the IMG documentation for the information container, under Collections/Disbursements Integration Information
Container. Pay particular attention to the notes about the additional settings required for the individual information types.
You have adjusted the information types to meet your requirements, where necessary.
For more information, see Adjust Information Types.
Process Flow
1. The triggering process responsible for an information type (such as a dunning activity) transfers the data to a process-specific
function module (such as VINFO_WRITE_DUNNING for information type V001), using the predefined interface.
2. The process-specific module generates an instance of the class VCL_INFO_00 and transfers the data to this instance for further
processing.
3. Generic services for the instance check the settings for the information type and process the data. The following events run, for
which you can control storage:
Event V253 assigns concrete values from the triggering process to the fields defined in Customizing, for each defined information
type.
You can find more information in the documentation for the event (sample module VINFO_SAMPLE_V253).
Event V251 writes additional information to the data container, if update is activated for this information type.
You can find more information in the documentation for the event (sample module VINFO_SAMPLE_V251).
Result
The system has stored the data from the process as a confirmation in the information container, plus any additional data. This
information is now available for recipient systems, or you can forward it using a mass activity.
Prerequisites
In the Implementation Guide, you have activated the communication types to be used to transfer the data (Activate Communication Types IMG activity), and
you have defined the communication type you want for the activated information type (Define Information Types IMG activity).
You can find the activities, and further information, in the Implementation Guide for Collections/Disbursements, under Integration Information Container.
The confirmations are stored in the information container and the data container, if required, and have not yet been archived.
You can find more information about archiving in the information container under
Archiving Confirmations.
Process Flow
Various processes take place, dependent on whether the system forwards the information directly to the recipient systems or simply
formats it.
Forwarding with the Forward Information Function (Push Scenario)
1. You start forwarding for confirmations.
You can find the function in the Collections/Disbursements menu, under Periodic Processing Transfer Data Information Container Forward
Information.
2. For event V222, the system selects the data from the information container that corresponds to the selection criteria.
3. Dependent on the communication type defined in Customizing for the information type, the system transfers the data to one of the
following events:
Event V225 for forwarding with SAP XI
Event V226 for forwarding with RFC
Event V227 for forwarding with a file
If the system is also to forward additional information from the data container, event V250 (for reading data from the data container) must be called up in these
events.
For more information, refer to the documentation for the individual events.
If you start the program in the simulation run, the system does not forward the information to the events. The confirmations do not
receive the status Forwarded and can be sent again.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 7 of 8
In this case, the confirmations are not marked as Forwarded. This affects the archiving of confirmations (see
Confirmations).
Archiving
Prerequisites
The system has already updated confirmations in the information container. The confirmations have not yet been
archived.
Scope of Functions
Display provides you with the following options:
Display according to business partner, insurance object, information type, or for all selection criteria
Display the status of the confirmations (send/unsent)
Detailed display for master data (business partner and insurance object)
Adjustment of layouts, dependent on the information required
Symbol with Quick Info Not forwarded the confirmation has not yet been forwarded.
However, it is possible that the information has already been taken by the recipient system, using the VINFO_PULL_RFC module.
Symbol with Quick Info Forwarded the confirmation has been forwarded
Data Container specifies whether additional information is/has been stored for this information type, in the data container.
Info Field contains the name of the object from which the value in the Data field comes.
Data contains the actual information (values from the info fields).
Test specifies whether the confirmation was created from a test run.
This is only relevant for information types for which the confirmations have been generated by mass activities (by a mass activity run, for example).
Confirmations for which the flag is set are not taken into account when forwarding.
You can find more information about the structure of a confirmation under Confirmation.
Activities
To call up display for the information container, choose Insurance Collections/Disbursements Periodic Processing Transfer
Data Information Container Display Information Container from the SAP Easy Access screen.
If you do not make any entries in the Information Container Selection area, the system displays all the contents of the information
container.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 8 of 8