Integrating SAP Hybris Commerce, financial

services accelerator with Policy Management in

SAP S/4HANA
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

TABLE OF CONTENTS
1 TERMINOLOGY ................................................................................................................................ 4
2 TECHNICAL PREREQUISITES ........................................................................................................ 6
2.1 System Landscape ............................................................................................................................. 6
2.2 Supported and required releases ..................................................................................................... 8
3 CONFIGURATION ............................................................................................................................ 9
3.1 Configuring Policy Management in SAP S/4HANA ......................................................................... 9
3.1.1 Monitoring / Restarting the CPI Service Call ........................................................................................ 9
3.2 Configuring Business Partner in SAP S/4HANA ............................................................................. 9
3.3 Configuring SAP Cloud Connector ................................................................................................. 10
3.3.1 Defining a Back-End System in SAP Cloud Connector (Mapping Virtual System to Internal System)
11
3.3.2 Defining the Mapping Virtual to Internal Systems............................................................................... 11
3.3.3 Configuring SAP Cloud Platform Destinations ................................................................................... 12
3.3.4 RFM Destinations – Default Destination Configuration ...................................................................... 13
3.4 Configuring SAP Cloud Platform Integration and Integration Content ...................................... 13
3.4.1 Deploying Integration Content SAP Cloud Platform Integration ......................................................... 14
3.4.2 Configuring the integration package and its artifacts ......................................................................... 14
3.4.2.1 Prerequisite ......................................................................................................................................... 14
3.4.2.2 Artifact Integration Flow ...................................................................................................................... 15
3.4.2.3 Artifact Value Mapping ........................................................................................................................ 18
3.4.3 Manage Authorizations in the SAP Cloud Platform Account .............................................................. 20

2
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

Your insurance company runs SAP Hybris Commerce, financial services accelerator as a customer
portal, where customers register to see the current data of their insurance contracts (policy or contract
inquiries). The data for the inquiry is loaded from a local data store to avoid frequent access to Policy
Management (FS-PM).

The inquiry displays the current policy/contract data. If there are multiple versions for a specified date,
only the latest version for the current date is displayed. The currently valid version, in other words
effective policy and all future versions of the policies/contracts in FS-PM are transferred to the local data
store.

When you release an application in FS-PM, the system triggers publishing of all contract versions that
are relevant for the user in SAP Hybris Commerce.

The connection from Policy Management in SAP S/4HANA to SAP Hybris Commerce, financial services
accelerator is enabled by an integration flow (iFlow) that is in the integration package SAP Hybris
Commerce, financial services accelerator integration with Policy Management in SAP
S/4HANA in SAP Cloud Platform Integration (CPI), available in SAP API Business Hub
(https://api.sap.com ).

3
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

1 TERMINOLOGY

Term Definition

Artifact A service (OData, Soap, and so on) that

enables you to integrate solutions or mapping
information.

Integration Content Processes and concepts related to the design

and maintenance of Integration Content.

Integrating business processes using cloud

integration implies the exchange of data
(messages) between the participants involved.

The way in which messages are exchanged is

defined by Integration Content, which is
designed on the basis of the requirements of
the business process.

Integration flow A central element of Integration Content that

describes how a message sent by one
participant is processed by SAP Cloud
Platform Integration.

SAP Cloud Platform Integration (CPI) Supports end-to-end process integration

across cloud-based and on-premise
applications (cloud-cloud and cloud-on-
premise integration).

Tenant Resources of the platform allocated to a

customer, which must be securely connected
to the associated component in the customer
landscape.

4
CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

Term Definition

For each customer system connected to the

integration platform, separate resources in
terms of memory and the central processing
unit (CPU) are allocated in SAP Cloud.

5
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

2 TECHNICAL PREREQUISITES

2.1 System Landscape

The integration involves the following components. The following chapters for each of the components
describe the necessary configuration steps (from bottom to top).

SAP S/4HANA

 Policy Management (FS-PM)

Policy Management in SAP S/4HANA manages the whole life cycle of insurance contracts, starting
from the creation of an application, through policy issuance and ongoing contract maintenance, right
up to the termination of the contract.

6
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

For information about how to configure FS-PM, see Configuring Policy Management in SAP
S/4HANA.

 Business Partner (BP)

The Business Partner component in SAP S/4HANA manages natural or legal persons with whom
business relationships are maintained. Insurance policies and contracts can relate to business
partners in their role as policy holder, insured persons, and premium payers.

For information about how to configure BP, see Configuring Business Partner in SAP S/4HANA.

 SAP Cloud Connector

SAP Cloud Connector links on-demand applications in SAP Cloud Platform and existing on-premise
systems. It combines an easy setup with a clear configuration of the systems that are exposed to
SAP Cloud Platform. In addition, you can control the resources available for the cloud applications in
these systems. Thus, you can benefit from your existing assets without exposing the whole internal
landscape.

For more general information, search for Cloud Connector in the documentation of SAP Cloud
Platform.

For information about how to configure the SAP Cloud Connector in this integration scenario, see
Configuring SAP Cloud Connector.

SAP Cloud Platform Integration (CPI)

SAP Cloud Platform Integration facilitates the integration of business processes and data across on-
premise, back-end systems and SAP Cloud Platform Mobile Services for Development and Operations.

For more general information, see SAP Cloud Platform Integration.

For information about how to configure and deploy CPI, see Configuring SAP Cloud Platform Integration
and Integration Content.

7
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

For information about operating and monitoring CPI, see

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-
US/c401afc97d954e298a3b3473257e1cf3.html

SAP Hybris Commerce, financial services accelerator

For general information, see SAP Hybris Commerce, financial services accelerator.

There are no specific steps to perform in SAP Hybris Commerce, financial services accelerator to enable
the import of policies from FS-PM.

For more information about the import of policies into SAP Hybris Commerce, financial services
accelerator, see Integration with Policy Management in S/4 HANA.

2.2 Supported and required releases

The following releases, or higher, are required for setting up the integration:

 SAP Hybris Commerce, financial services accelerator, 6.7

 SAP S/4HANA 1809

 Integration package SAP Hybris Commerce Financial Services Accelerator integration with
Policy Management in SAP S/4HANA, 1.0

 SAP Cloud Connector 2.8.0.1

8
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

3 CONFIGURATION

3.1 Configuring Policy Management in SAP S/4HANA

Note:
The Integration Content is available in integration package SAP Hybris Commerce Financial Services
Accelerator integration with Policy Management in SAP S/4HANA in SAP Cloud Platform Integration (CPI)
which is available in SAP API Business Hub (https://api.sap.com ).

In Policy Management you must do the following:

- The webservice configuration in SOA-Management (see next chapter)
- Specify the information about which changes shall be potentially transferred to SAP Hybris
Commerce
- Implement a Business Add-In to choose the versions that shall be replicated and trigger the
replication

For more information, see

https://help.sap.com/viewer/DRAFT/5bec6e0df6b549258e7ae381fedd4066/1809.000/en-
US/c0b8290e737e4179a08a8b89335aaee3.html

In the integration flow, a remote function module (RFM) is called from Policy Management. The technical
users who execute these calls need to have the required authorization.

Technical Name Description INPUT TYPE Target

(Service path or RFM name) System
/PM0/ABT_SVC_POL_REA Reads detailed Policy RFC Policy
D information for a certain number, Management
policy version contract in S/4HANA
number,
effective
date

3.1.1 Monitoring / Restarting the CPI Service Call

The web service message monitor can be used to monitor or restart service calls to CPI (transaction
SRT_MONI). For information, see Monitoring the Web Service Runtime.

3.2 Configuring Business Partner in SAP S/4HANA

In the integration flow, RFMs are called from Business Partner. The technical users who execute these calls
need to have the required authorization.

Technical Name Description INPUT TYPE Target

(Service path or RFM name) System
BAPI_BUPA_BANKDETAIL_ Reads business partner Business RFC Business
GETDETAIL bank details partner Partner in
ID, S/4HANA
bank
account
ID,
effective
date of
the
version

9
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

BAPI_BUPA_CENTRAL_GE Reads first name, last Business RFC Business

TDETAIL name and date of birth partner Partner in
for a certain business ID, S/4HANA
partner effective
date of
the
version

3.3 Configuring SAP Cloud Connector

To connect SAP Cloud Connector to the SAP Cloud Platform Integration tenant (and the corresponding SAP
Cloud Platform account), proceed as follows:
1. Get the access data (URL, user/password) from your SAP Cloud Appliance Library administrator.
2. Enter the URL.
3. Enter the user name and password, and choose Login.
Note: If you a have a valid URL from a trusted source, you can ignore the security warning in the
browser.
4. On the SAP HANA Cloud Connector Administration screen, choose Account Dashboard then
choose Add.

5. Enter the account details for SAP Cloud Platform.

Note:

 The subaccount name is available in the Subaccount Information section in SAP Cloud
Platform Cockpit.
 Keep the proxy settings at hand.

10
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

 You can import additional access control data from any other account available at this SAP
Cloud Connector instance. To do so, mark the Import Access Control From
Account checkbox and choose the available account from the dropdown list.
6. Save your data.

7. Check the status of the new account in the Status column. The connection status must
be Operational.

For more information, see Outbound: SAP Cloud Connector.

3.3.1 Defining a Back-End System in SAP Cloud Connector (Mapping Virtual System to Internal
System)

You must define a back-end system in SAP Cloud Connector by mapping the virtual system to the internal
system.

Note: A prerequisite is that you have connected SAP Cloud Connector to the SAP Cloud Platform account.

3.3.2 Defining the Mapping Virtual to Internal Systems

1. On the SAP HANA Cloud Connector Administration screen, select your account from the dropdown list
and then choose Access Control.

11
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

2. Choose Add and enter the data as described in the Access Control for SAP Cloud Connector section
below.

3. Define the accessible resources, which means you must define the path (and optionally the sub-path)
that leads to the resource of the host.

 S/4HANA Remote Functions

 FSA Services

Defining the Path to the Resource of the Host

3.3.3 Configuring SAP Cloud Platform Destinations

This section describes how the SAP Cloud Platform destinations must be defined for RFM-based
communication between the integration package and the back-end system S/4HANA:

1. Open the SAP Cloud Platform Cockpit of your tenant account.

2. Choose Connectivity Destinations.

12
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

3. Choose New Destination and enter the destination configuration data as described in in the RFM
Destinations – Default Destination Configuration section, using the virtual hosts defined in the
previous chapter.

4. Save the destination.

3.3.4 RFM Destinations – Default Destination Configuration

The following table shows the required destination entries.

Destination Name Type Description Additional

Properties

S4HANA_RFC RFM RFM destination for reading policy versions jco.client.client

and business partner data.
jco.client.mshost

jco.client.r3name

3.4 Configuring SAP Cloud Platform Integration and Integration Content

The connection from Policy Management in S/4HANA to SAP Hybris Commerce is enabled by an integration
flow (iFlow) provided in the integration package SAP Hybris Commerce Financial Services Accelerator
integration with Policy Management in SAP S/4HANA in SAP Cloud Platform Integration (CPI), available in
SAP API Business Hub (https://api.sap.com ).

13
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

This integration package enables you to:

 Connect Policy Management (FS-PM) and the Business Partner (BP) to SAP Hybris
Commerce, financial services accelerator.

 Map the information stored in the backend systems to the format of SAP Hybris Commerce.

3.4.1 Deploying Integration Content SAP Cloud Platform Integration

1. Open the SAP Cloud Platform Integration tenant WEB UI

(for example, https://<your SAP Cloud Platform Integration tenant URL/itspaces).

2. Select All to see all published integration packages.

3. Search for the SAP Hybris Commerce Financial Services Accelerator integration with Policy
Management in SAP S/4HANA - Integration package.

4. To copy the integration package from the catalog to your customer workspace, mouse-over the
integration package tile and click Copy to workspace.

3.4.2 Configuring the integration package and its artifacts

This section briefly describes the content of the integration package and the necessary configurations.

3.4.2.1 Prerequisite

14
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

You need to know the connection details (URL/Credentials) for the SAP Hybris Commerce system to do the
following:
 Retrieve the OAuth token needed by the relevance check
 Call the WebService for the contract/policy relevance check
 Call the OData Service for the import policy service

Besides this, you need the name of the destinations within your SAP Cloud Platform Tenant pointing to the
following:
 S/4HANA FS Policy Management system
 S/4HANA Business Partner system.

3.4.2.2 Artifact Integration Flow

This artifact is responsible for replicating policy data from FS-PM to FSA. The execution of this iFlow is
initiated by FS-PM whenever a policy change requires a notification in SAP Hybris Commerce. The iFlow first
checks if the changed policy is relevant for SAP Hybris Commerce by calling the appropriate Webservice. If
this is the case, it gathers all required information from FS-PM and BP to send a complete, updated version of
the policy to SAP Hybris Commerce by using the import policy OData service.

Therefore, multiple services and RFMs are called. Some calls depend on the results of previous calls. The
following table gives an overview of the services involved:

Name in iFlow Technical Name Description INPUT TYPE Target

(Service path or RFM name) System
FSA_Hybris_Get_Tok /authorizationserver/oauth/to Gets the access token - HTTP SAP Hybris
en ken needed for checking the Commerce
relevance FSA
FSA_Hybris_Check_ /financialwebservices/v1/site Checks whether a policy Policy HTTP SAP Hybris
Relevance s/insurance/catalogs/financia is relevant for SAP holder ID, Commerce
lProdctCatalog/versions/&On Hybris Commerce; policy FSA
line/policies/relevance currently only the policy number,
holder is considered Product
Model ID
of Sales
Product
and
Product
FSA_Hybris_Policy_I /odata2webservices/Inbound Provides data for Whole oDATA SAP Hybris
mport InsuancePolicy several contracts and contract Commerce
policies and their versions FSA
versions to SAP Hybris
Commerce
FS- /PM0/ABT_SVC_POL_REA Reads detailed Policy RFC Policy
PM_Read_Policy_Ver D information for a policy number, Management
sion version contract in SAP
number, S/4HANA
effective
date
BP_Get_Bank_Detail BAPI_BUPA_BANKDETAIL_ Reads bank details of Business RFC Business
s GETDETAIL business partner partner Partner in
ID, SAP
bank S/4HANA
account
ID,
effective
date of
the
version
BP_Get_Details BAPI_BUPA_CENTRAL_GE Reads first name, last Business RFC Business
TDETAIL name and date of birth partner Partner in
of a business partner ID,

15
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

effective SAP
date of S/4HANA
the
version

Before you configure the iFlow, deploy the user credentials within the security material of the SAP Cloud
Platform Integration. Click the Manage Security Material tile and add new user credentials, which are needed
for the OData Service call to import policies. You can use the name FSA_UPDATE_VERSION or any other
name. Enter the user and password:

The iFlow deployment requires a configuration with your individual network and product settings.
For general information about the configuration/externalization, see:
https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-
US/462a4782db7b485b94ffce5b6fe22c31.html
The configuration can be done by choosing the configuration menu item in your iFlow artifact:

3.4.2.2.1 Configuration of the Receiver

3.4.2.2.1.1 BP_Get_Bank_Details

Adapter for the BP system to retrieve bank details.

16
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

Parameter name Value

Destination <Tenant Destination to On-Premise S/4 HANA BP
system>

3.4.2.2.1.2 FSA_Hybris_Check_Releance

Adapter for the SAP Hybris system Webservice for checking the relevance of a policy.

Parameter name Value

FSA_HostPort <Host and Port of the SAP Hybris Commerce
system (or virtual port in Cloud connector pointing to
SAP Hybris Commerce system>
FSA_RelevanceCheck <Webservice Path pointing to the Relevance Check
in the SAP Hybris Commerce system>

3.4.2.2.1.3 BP_Get_Details

Adapter for the BP system to retrieve details.

Parameter name Value

Destination <Tenant Destination to On-Premise S/4 HANA BP
system>

3.4.2.2.1.4 FS-PM_Read_Policy_Version

Adapter for the FS-PM system to read policy data.

Parameter name Value

Destination <Tenant Destination to On-Premise S/4 HANA FS-
PM system>

3.4.2.2.1.5 FSA_Hybris_Get_Token

Adapter for the Hybris system for OAuth token retrieval.

Parameter name Value

FSA_HostPort <Host and Port of the SAP Hybris Commerce
system (or virtual port in Cloud connector pointing to
SAP Hybris Commerce system>
FSA_OAuthServicePath <Webservice Path pointing to the service for the
OAuth Token retrieval>

3.4.2.2.1.6 FSA_Hybris_Policy_Import

Adapter for the SAP Hybris system for the import policy service.

Parameter name Value

FSA_HostPort <Host and Port of the SAP Hybris Commerce
system (or virtual port in Cloud connector pointing to
SAP Hybris Commerce system>
FSA_PolicyImportServicePath <Webservice Path pointing to the service for the
OAuth Token retrieval>
Authentication <Authentication method>

17
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

Credential Name <Name of the deployed User Credential within CPI.

Required for the Authentication Method BASIC>

3.4.2.2.2 More Parameters

Parameter name Value

FSA_Version <Version number of the connected SAP Hybris
Commerce system. This Version must correspond to
the version used in the Value Mapping Artifact>
FSPM_Version <Version number of the connected FS-PM system.
This Version must correspond to the version used in
the Value Mapping Artifact>

3.4.2.2.3 Rules and Credentials for remote users

The RFC-user that executes the calls (see: RFM Destinations – Default Destination Configuration) needs full
authorization to access the required data in the S/4HANA system.

The user who passes the information to SAP Hybris Commerce (FSA_Hybris_Policy_Import), financial
services accelerator needs authorization to execute the oData-call.

3.4.2.3 Artifact Value Mapping

This artifact defines the mapping of product definitions as defined in Policy Management in S/4HANA to the
product definition of SAP Hybris Commerce, financial services accelerator.

For example, product module IDs are mapped from FS-PM to FSA, but also values for payment frequencies.

In the example below, the contract status 002 in FS-PM is mapped to the value REVERSED in FSA:

18
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

If authorized values in FS-PM depend on the templates in which they are used, you need to add the template
ID as a prefix to the field for which you define the mapping.

The screenshot above shows that for PAYFRQ_CD there is also specialized mapping defined for template
PU80000S0000. This relates to the template PU80000S0000 defined in FS-PM’s In-Force Business
Configurator: Premium Category Recurring

During runtime, the iFlow checks whether specialized mapping information is available. If not, the general
mapping definition is used.

As the integration flow can be used to connect different FS-PM-releases with different FSA-releases, it is
possible to define the combination of versions and releases for which the mapping is valid. Therefore, the
AGENCY needs to be set accordingly:

The versions currently connected are defined as configurable properties in the iFlow:
 FSPM_Version
 FSA_Version

Therefore, the mapping defined in the screenshot is applied when the following applies:
 FSPM_Version is set to 1809 (The system concatenates it to FSPM_<FSPM_Version>)
 FSA_Version is set to 67 (The system concatenates it to FSA_<FSA_Version>)

For detailed information about the configuration of value mapping and a description of how to upload mapping
defined in CSV-files, see: https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-
US/6c8847fe8dcc459580a63194fc55d5b3.html

19
 CONFIGURING THE INTEGRATION OF SAP HYBRIS COMMERCE, FINANCIAL SERVICES ACCELERATOR
WITH POLICY MANAGEMENT IN SAP S/4HANA

3.4.3 Manage Authorizations in the SAP Cloud Platform Account

To authorize a user to call the CPI tenant (using HTTPS/basic authentication), assign the role
ESBmessaging.send as follows:

20
www.sap.com

© 2014 SAP SE 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 SE or an SAP
affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices. Some software products
marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform
directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned
not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making
purchasing decisions.