SAP CUSTOMER CHECKOUT BUSINESS ONE

INTEGRATION FRAMEWORK SCENARIO

EXTENSION GUIDE

12-FEB-2016
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
Document History

VERSION DATE CHANGE

1.0 01-SEP-2015 First Version

2.0 12-FEB-2016 New information about extending SAP Business One Integration Framework scenarios
added.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
Contents
Purpose .......................................................................................................................................... 4
Target Audience ......................................................................................................................... 4
Abbreviation used ...................................................................................................................... 4

1. Extending the SAP Business One Integration Framework scenario for SAP
Customer Checkout ................................................................................................................... 5
1.1 Use Case.............................................................................................................................. 5
1.2 Use case – Analysis and how to approach .................................................................. 5
1.2 The extension concept ................................................................................................... 6
1.3 Creating a new scenario step to do data manipulation: ...................................... 6
1.4 Registration of the scenario to the extension point: .......................................... 14
1.5 Verify that the extension works: ............................................................................... 16

2. Basic explanation about available extension points and already provided

sample for using them ............................................................................................................ 18

3. Using Built-In support for field extension in SAP Customer Checkout ......... 20
3.1 Understanding the built-in support concept ............................................................. 20
3.2 Which fields are available and where ...................................................................... 21
3.3 How to view, search these extension fields in SAP Customer Checkout. ... 22

4. Questions/ feedback on this guide ............................................................................ 24

SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
Purpose
The purpose of this “SAP Customer Checkout’s Business One Integration Framework Scenario Extension
Guide” is to explain how to extend the existing SAP Business One Integration Framework scenarios developed
for SAP Customer Checkout integration with SAP Business One.
It is explained with examples:
How to extend and verify the scenarios in SAP Business One Integration Framework

This document does not replace the official documentation of SAP Customer Checkout. This is not a legal
document but is prepared only to assist developers/consultants to extend the SAP Business One Integration
Framework scenarios for SAP Customer Checkout.

Target Audience
 Technology consultant / Application consultant / Developer

Abbreviation used
B1if – SAP BusinessOne Integration Framework.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

1. Extending the SAP Business One Integration Framework

scenario for SAP Customer Checkout

1.1 Use Case

Let us assume a use-case that a customer has added two User Defined Fields (UDF) called “Color” and “Size” in
the material details of SAP BusinessOne. Now he wants that these two fields should also be available in SAP
Customer Checkout. Additionally he wants to modify the description of the item so that the description shown
in SAP Customer Checkout for the item is different from the description shown in SAP Business One. Customer
wants to append the “Color” and “Size” to the description so that in SAP Customer Checkout you see the
“description + color + size” as the description in SAP Customer Checkout.

1.2 Use case – Analysis and how to approach

To achieve the customer’s use-case, the following needs to be done.
1. Modify the SAP Business One Integration Framework service used by SAP Customer Checkout so that
the data about the UDF (Color and Size) and the modified description can be sent back from the SAP
Business One Integration Framework Service.
2. Store this user defined field values (Color and Size) in SAP Customer Checkout.

First, the SAP Business One Integration Framework service used by SAP Customer Checkout by default does
not deliver data about these UDF’s that are added to SAP Business One. Hence the SAP Business One
Integration Framework service has to be enhanced using the extension concept explained below to deliver
data maintained in these UDF’s.

Second, SAP Customer Checkout will by default not store this data in the SAP Customer Checkout system.
From Release 2.0 SP00 there is in-built functionality that supports storing this additional UDF from SAP
Business One Integration Framework Service if delivered in a fixed format, and also viewing and searching in
SAP Customer Checkout based on known extension fields. However this in-built functionality is very powerful
but limited in scope. The partner/customer is responsible to evaluate if this is enough to meet the customer
functional expectation. If a more detailed functionality is required then this has to be achieved using Plug-In
development for SAP Customer Checkout. Plug-In development for SAP Customer Checkout is out of scope for
this document.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
Now that the expectation from this guide is clear, let’s go in more details regarding how to extend the SAP
Business One Integration Framework scenario and use the built-in functionality of SAP Customer Checkout for
storing and viewing this data.

1.2 The extension concept

From SAP Business One for synchronizing articles/materials, SAP Customer Checkout uses the SAP Business
One Integration Framework scenario step “sap.POS.FetchMaterialList” from the scenario package
“sap.CustomerCheckout”. In this SAP Business One Integration Framework scenario step, SAP has provided an
extension point “sap.POS.FetchMaterialList_Output”. This extension point is executed before the output of
the standard step is returned to the caller (SAP Customer Checkout). In this extension point the partner can
manipulate the standard output of the scenario step “sap.POS.FetchMaterialList” and prepare a new output
that is returned to the caller (SAP Customer Checkout).
To do this data manipulation, the partner will create a new scenario step. The newly developed scenario step
by the partner needs to be registered in the extension point “sap.POS.FetchMaterialList_Output”. Once this
registration is done, the output prepared by the new partner scenario step, is returned as the output of the
SAP Business One Integration Framework scenario step “sap.POS.FetchMaterialList” to the caller (SAP
Customer Checkout).
How to build such a new scenario step and how to register this scenario step at the extension point is
explained below.

1.3 Creating a new scenario step to do data manipulation:

You will require basic knowledge of development in SAP Business One Integration Framework to understand
this topic. In our use-case, we would like to read the “color” and “size” UDF’s from SAP Business One and
return it along with all other data for articles/materials in the scenario step sap.POS.FetchMaterialList.
Additionally we would like to append the “color” and “size” to the existing description of material from SAP
Business One so that the description for the item seen in SAP Customer Checkout is “SAP Business One
material description + Color + Size” i.e, different from the description of the item in SAP Business One.

Once the partner step is registered at the extension point, the input data provided to the new partner step is
A) The original input payload sent by SAP Customer Checkout to the step “sap.POS.FetchMaterialList”
More technical in SAP Business One Integration Framework language its
(/vpf:Msg/vpf:Body/vpf:Payload[./@Role='S'])
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
B) The default output payload of the step “sap.POS.FetchMaterialList”, that SAP Business One Integration
Framework would have sent to SAP Customer Checkout
More technical in SAP Business One Integration Framework language its
(/vpf:Msg/vpf:Body/vpf:Payload[./@Role='XS'])

The original input (A) informs the partner step which database to use (based on SystemID etc) and
the default output (B) provides the default output which the partner step can use and manipulate.

For our use case, we now need to do the following in three steps.
Step 1: The default output is a list of materials so we need to loop over all the Materials and prepare the
materials list. And then prepare an SQL call to fire to the database (available as SysId in atom with Role=”S”)
so that Color and Size information about these materials can be fetched.
Step 2: Fire the SQL call and find out the “Color” and “Size” for these articles.
Step 3: Prepare a new output where “Color” and “Size” are added to output and the description is modified to
append the “Color” and “Size” to the description.

The output that is prepared in step 3 has to be returned as output of the new partner scenario step. Once this
partner scenario step is registered in the extension point, then this output is sent as the output of the step
“sap.POS.FetchMaterialList”.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

Real example with sample code and screenshots

The screenshot below shows the input that the partner step will receive once registered at the extension
point. As seen it has original input (A) and the default output (B).
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

A new scenario package and a new scenario step has to be was created. This is shown in the screenshot below.
In this scenario step there are three main atoms “xform”, “sqlcall” and “final” which performs the three steps
mentioned before.

In the xform atom, some xlst transformation is performed to prepare material list and the SQL call is prepared.
This completes step one.
In the sqlCall atom, the actual SQL call is made and this completes step two.
In the final atom, the new output is prepared. In this new output “Color” and “Size” are added to output and
the description is modified. This completes step three.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

Sample code for xform -> Loops over fetched articles from the standard output identified with Role = ‘XS’,
prepares a list of such articles and then prepares an SQL call to fetch the color and Size for these articles.

<xsl:variable name="Localapos">&apos;</xsl:variable>
<xsl:variable name="LocalOpenPara">(</xsl:variable>
<xsl:variable name="LocalClosePara">)</xsl:variable>
<xsl:variable name="Localcomma">,</xsl:variable>

<xsl:variable name="FetchedArticles">
<xsl:if test="count(/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;XS&apos;]/FetchMaterialListResponse/MaterialList/
Material/ItemCode) &gt; 0">
<xsl:value-of select="$LocalOpenPara"/>
<xsl:for-each select="/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;XS&apos;]/
FetchMaterialListResponse/MaterialList/Material">
<xsl:value-of select="$Localapos"></xsl:value-of>
<xsl:value-of select="./ItemCode"></xsl:value-of>
<xsl:value-of select="$Localapos"></xsl:value-of>
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
<xsl:choose>
<xsl:when test="position() = last()">
<xsl:value-of select="$LocalClosePara"></xsl:value-of>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$Localcomma"></xsl:value-of>
</xsl:otherwise>
</xsl:choose>
</xsl:for-each>
</xsl:if>
</xsl:variable>

<sql xmlns="">
<xsl:if test="string-length($FetchedArticles) > 0">
Select ItemCode, U_Size, U_Color from OITM where ItemCode in
<xsl:value-of select="$FetchedArticles"></xsl:value-of>
</xsl:if>
;
</sql>

Sample for sqlCall -> It’s fires the SQL call.

SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

Sample code for final -> The new output is prepared. In this new output “Color” and “Size” are added to
output and the description is modified.
<FetchMaterialListResponse xmlns="">
<MaterialList>
<xsl:for-each select="/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;XS&apos;]/
FetchMaterialListResponse/MaterialList/Material">
<Material>
<!-- Copies all other elements expect ItemName which is the description -->
<xsl:copy-of select="./*[not(name()='ItemName')]"/>
<xsl:variable name="ItemID">
<xsl:value-of select="./ItemCode"/>
</xsl:variable>
<!-- Adds a new element for Size -->
<Size>
<xsl:value-of select="/vpf:Msg/vpf:Body/vpf:Payload[./@id=&apos;atom1&apos;]/
jdbc:ResultSets/jdbc:ResultSet/jdbc:Row[string(./jdbc:ItemCode) =string($ItemID)]/jdbc:U_Size"/>
</Size>
<!-- Adds a new element for Color -->
<Color>
<xsl:value-of select="/vpf:Msg/vpf:Body/vpf:Payload[./@id=&apos;atom1&apos;]/
jdbc:ResultSets/jdbc:ResultSet/jdbc:Row[string(./jdbc:ItemCode)
string($ItemID)]/jdbc:U_Color"/>
</Color>

<!-- Append the Size and Color to the existing description from SAP BusinessOne -->
<ItemName>
<xsl:value-of select="./ItemName"/>
<xsl:value-of select="string(' Size ')"/>
<xsl:value-of
select="/vpf:Msg/vpf:Body/vpf:Payload[./@id=&apos;atom1&apos;]/jdbc:ResultSets/jdbc:ResultSe
t/jdbc:Row[string(./jdbc:ItemCode) = string($ItemID)]/jdbc:U_Size"/>
<xsl:value-of select="string(' Color ')"/>
<xsl:value-of
select="/vpf:Msg/vpf:Body/vpf:Payload[./@id=&apos;atom1&apos;]/jdbc:ResultSets/jdbc:ResultSe
t/jdbc:Row[string(./jdbc:ItemCode) = string($ItemID)]/jdbc:U_Color"/>
</ItemName>
</Material>
</xsl:for-each>
</MaterialList>
<!-- Copies all other elements-->
<LastReturnedObjectId>
<xsl:value-of select="/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;XS&apos;]/
FetchMaterialListResponse/LastReturnedObjectId"></xsl:value-of>
</LastReturnedObjectId>
<ErrorMessage>
<xsl:value-of select="/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;XS&apos;]/
FetchMaterialListResponse/ErrorMessage">
</xsl:value-of>
</ErrorMessage>
</FetchMaterialListResponse>
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

1.4 Registration of the scenario to the extension point:

In SAP Business One Integration Framework, select Scenarios > Setup. Select the scenario package
“sap.CustomerCheckout”. Click on the button “Data Mgt.” and select the entry “Table: vTbl.IncludeList.xml”.
The extension point “sap.POS.FetchMaterialList_Output” is predefined. By clicking on the “…” button, partners
can assign their step to the selected extension point.
This is explained in the screenshot below. The newly created partner step is now registered to be executed at
the extension point ““sap.POS.FetchMaterialList_Output”.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
1.5 Verify that the extension works:
A technical developer’s way to verify that the UDF fields are being sent from SAP Business One Integration
Framework is to check in SAP Business One Integration Framework. You will need basic knowledge of
development in SAP Business One Integration Framework to understand this topic. As in this sample
screenshot below, when we execute the sap.POS.FetchMaterialList step in SAP Business One Integration
Framework, we can see the output of the extension step and the final output of the scenario step.

Marked as in the screenshot below is the point where the output of the extension step can be seen.

Marked as in the screenshot below is the point where the output of the scenario step can be seen.

By looking at these outputs it can be verified that the “color” and “size” elements were added and the
description was modified.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

To store the additional “Color” and “Size” attributes now coming back from the service, you can use the built-
in support in SAP Customer Checkout or do a plugin development. How to use the in-built functionality that
supports storing, viewing and searching based on known extension fields is explained below in this guide.
However the description modification for the materials/articles that was made we can see it immediately in
SAP Customer Checkout.
A very non-technical way to verify that the extension works is that now we can do Article Synchronization in
SAP Customer Checkout, and after the Synchronization is complete, verify that the description is modified and
Size and color are added to the description. As in the screenshot below, for the article A00001, the
description in SAP Business One is “J.B. Multifunktionsdrucker 1420”, however in SAP Customer Checkout the
description is “J.B. Multifunktionsdrucker 1420 Size Medium Color Royal Blue”.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
2. Basic explanation about available extension points and
already provided sample for using them
We have developed a sample SAP Business One Integration Framework scenario package sap.CCO.Extension
which has some scenario steps. These scenario steps are explained below and the expectation is that they can
be registered to the available extension points. The available extension points are also explained below. These
are only sample and they are NOT meant for productive usage.
This scenario package sap.CCO.Extension will be available in the partner edge portal or can be requested from
the [email protected] inbox.
Extension Points available for SAP Customer Checkout extension in the SAP Business One Integration
Framework package sap.CustomerCheckout
1. sap.POS.FetchMaterialList_Output
This extension point is used in the SAP Business One Integration Framework Scenario step
sap.POS.FetchMaterialList
This scenario step is used by the SAP Customer Checkout to synchronize articles and prices from SAP
BusinessOne to SAP Customer Checkout.

In the sample package sap.CCO.Extension, we have provided a scenario step sap.CCO.ExtendMaterial

which can be used as a sample to build extension on the material fetching. In the sample scenario step
it assumes that U_Color, U_Size, U_SP_Instructions (meaning special instructions) as user defined fields
existing in SAP BusinessOne and adds these data to the standard output. It also modifies the material
description to add the color and size to the material description.

2. sap.POS.GetCustomerList_Output
This extension point is used in the SAP Business One Integration Framework Scenario step
sap.POS.GetCustomerList.
This scenario step is used by the SAP Customer Checkout to synchronize customer data from SAP
BusinessOne to SAP Customer Checkout.

In the sample package sap.CCO.Extension, we have provided a scenario step sap.CCO.ExtendCustomer

which can be used as a sample to build extension on the customer fetching. In the sample scenario
step it assumes that U_LoyaltyAccount, U_Rating as user defined fields existing in SAP BusinessOne
and adds these data to the standard output.

3. sap.POS.MaintainBP_PreProcessing
This extension point is used in the SAP Business One Integration Framework Scenario step
sap.POS.MaintainBP.
This scenario step is used by the SAP Customer Checkout to create or update customer from SAP
Customer Checkout to SAP Business One.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
In the sample package sap.CCO.Extension, we have provided a scenario step sap.CCO.MaintainBPPre
which can be used as a sample to modify the payload that is sent to SAP BusinessOne so that the
U_LoyaltyAccount, U_Rating that was fetched into SAP Customer Checkout can be used to modify the
data in SAP BusinessOne as well.

4. sap.POS.POSTInvoice_Documents
This extension point is used in the SAP Business One Integration Framework Scenario step
sap.POS.POSTB1Invoice.
This scenario step is used by the SAP Customer Checkout to create AR Invoice + Incoming/out-going in
SAP BusinessOne from the receipt data sent from SAP Customer Checkout.
This extension point is just before creating an AR Invoice.

In the sample package sap.CCO.Extension, we have provided a scenario step sap.CCO.CreateReceiptPre

which can be used as a sample to modify the payload that is sent to SAP BusinessOne. In the sample
we modify the payload so that the AR Invoice ID created in SAP BusinessOne is the same as the Receipt
ID in SAP Customer Checkout.

Additional scenario steps that are available in the scenario package sap.CCO.Extension
We have provided 2 additional scenario steps in the package sap.CCO.Extension. These are provided as we are
planning to provide a demo plugin as well. In the demo plug code this scenario steps will be called from SAP
Customer Checkout. These are provided as samples so that partners can built their own logic using these as
samples.
1. sap.CCO.Extension -> sap.CCO.ContactPrsnBP
The step is called by the demo plug-in with a BusinessPartner ID, and returns a list of contact details for
the Business Partner.
2. sap.CCO.Extension -> sap.CCO.FetchCntPrsnList
The step is called by the demo plug-in to synchronize contact person details of all Business Partner so that
they can be stored in new tables (created from the plug-in) and use a synchronization job to fetch this data
from SAP BusinessOne and store it in SAP Customer Checkout.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

3. Using Built-In support for field extension in SAP

Customer Checkout

3.1 Understanding the built-in support concept

This functionality is available only from SAP Customer Checkout 2.0 SP00.
By built-in support for field extension, it is meant that for materials and business partner, it is possible to store
additional data in SAP Customer Checkout. Maximum 10 fields mentioned below but the external ERP system
(SAP BusinessOne in this example) must provide the data in the format expected by SAP Customer Checkout.
For materials/articles we have added 10 fixed fields. Similarly for Business Partner we have added 10 fixed
fields. These fixed fields have fixed names like udfString1, udfString2, udfStringXL1 etc.
When we synchronize Articles will SAP BusinessOne, along with regular data like Article ID, Article Description
etc, if the SAP Business One Integration Framework service returns data in the field udfString1, udfString2,
udfStringXL1 etc then this data will be automatically stored in SAP Customer Checkout.
Now let’s assume that we have 2 User Defined fields for Articles in SAP BusinessOne. These are Color and Size.
Using the extension concept for SAP Business One Integration Framework service for SAP Customer Checkout
integration explained in the previous sections of this guide, we can extend the SAP Business One Integration
Framework Scenario step sap.POS.FetchMaterialList so that along with regular data we return data stored in
the UDF color and size as udfString1 and udfString2. By doing this SAP Customer Checkout stores the Size and
Color in the field udfString1 and udfString2. SAP Customer Checkout then provides you the possibility to
display the field udfString1 and udfString2 in the User Interface with any human readable alias that you want
to use. SAP Customer Checkout also provides you the possibility to search based on these fields etc.
The same concept is also used in Business Partner. We can extend the SAP Business One Integration
Framework Scenario step sap.POS.GetCustomerList so that along with regular data UDF data can be returned
as udfString1 and udfString2 etc. It is then possible to see this data in SAP Customer Checkout UI and search
based on it etc.

For Business Partner additionally when a Business Partner is created or updated in SAP Customer Checkout
these fields udfString1, udfString2 etc are sent to the SAP Business One Integration Framework scenario step
sap.POS.MaintainBP responsible to create or update Business partner in SAP Business One. Using the SAP
Business One Integration Framework extension concept and using the extension point
sap.POS.MaintainBP_PreProcessing, partner can modify the data sent to SAP Business One DI API and replace
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
udfString1 with actual UDF fields in SAP BusinessOne. By using this concept it is possible to update these fields
from SAP Customer Checkout and they are updated in SAP BusinessOne.

3.2 Which fields are available and where

10 fields are available in Business Partner and 10 fields are available in Article. The field names and type is
mentioned below.
String "udfString1"; (length 40)
String "udfString2"; (length 40)
String "udfStringXL1"; (length 255)
String "udfStringXL2"; (length 255)
String "udfStringXL3"; (length 255)
String "udfStringXL4"; (length 255)
BigDecimal "udfDouble1";
BigDecimal"udfDouble2";
Boolean "udfBoolean1";
Boolean"udfBoolean2";

SAP Business One Integration Framework Scenario step sap.POS.GetCustomerList is used for Business Partner
synchronization. The scenario step provides the extension point step sap.POS.GetCustomerList_Output for any
modification.

SAP Business One Integration Framework Scenario step sap.POS.FetchMaterialList is used for article
synchronization. The scenario step provides the extension point step sap.POS.FetchMaterialList_Output for
any modification.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

3.3 How to view, search these extension fields in SAP

Customer Checkout.

To a good extend this topic is self-explanatory and a very brief explanation with screenshot is provided below.
For detailed understanding of this topic kindly refer to the official product documentation of SAP Customer
Checkout 2.0. These documents are provided with the product and are also available in
http://help.sap.com/cco20

From Release 2.0 SP00 onwards, in the configuration page a new tab “Dialog settings” is provided. In this
dialog setting for each type Article or Customer, you can decide which fields you want to view, search and also
provide an alias. As a result you can give alias to the udfString1, udfString2 etc and also search based on it.

The below 2 screenshot shows how the “Dialog settings” can be adjusted and based on the changes made in
“Dialog settings“ this is reflected in the search.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

4. Questions/ feedback on this guide

If you have questions or would like to provide feedback on this guide, you can write an email to
[email protected]
We will be happy to hear from you and support you.
SAP CUSTOMER CHECKOUT BUSINESS ONE INTEGRATION
FRAMEWORK SCENARIO EXTENSION GUIDE

© 2016 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.