BAdI: DMS Configuration for Supplem.

Data in Product Lookup

Use
This Business Add-In (BAdI) is used for the SAP Retail Store Ops Associate application. In this application, you can
activate settings that allow you to download supplemental product information, such as warranty or other detailed
information, and images to the mobile device from various back-end systems. You can use this BAdI to gather
information required to configure the download of product information or images from the data provider to the mobile
device.
Standard settings
This BAdI is called by the BAdI: Supplemental Data Query for Product Lookup
/SRSMOB/STOP_SUPP_DATA_QUERY when SAP DMS is configured as the storage mechanism for images and
supplemental data, and it has been configured in the SAP back-end system.
The fallback class /SRSMOB/CL_STOP_SUPP_DMS_CFG uses SAP Document Management Services (DMS) to
store persisted images and other data. To retrieve the images and data, it uses information captured by this BAdI to
locate the requested data in SAP DMS. For example, this BAdI provides information about the document type, part,
version, format and document file name throught the following parameters:

DOCUMENT_TYPE = DRW

DOCUMENT_PART = 000

DOCUMENT_VERSION = "-"

Detail image file name

"PRODUCT_IMG"

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element
Definitions tab in the BAdI Builder (transaction SE18).
Activities
To create a document in SAP DSM, you must use the same configuration settings and upload the document files to
DMS using the same file name, for example "PRODUCT_IMG". Alternately, you can create a BAdI implementation
specifying your own configuration settings for storing images and supplemental data.
More Information
For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application
Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View > Application Server > Application
Server ABAP > Application Development on AS ABAP > ABAP Customer Development > Enhancement Framework.

BAdI: OData Supplem. Data Parameter Parser for Product Lookup

Use
This Business Add-In (BAdI) is used for the SAP Retail Store Ops Associate application. In this application, you can
activate settings that allow you to download supplemental product information, such as warranty or other detailed
information, and images to the mobile device from various back-end systems.
The request for supplemental data originates in the Search feature in the mobile application and is carried out by an
OData Service to the back-end system. Because the OData Service protocol does not support requests that contain a
list or an array of multiple product numbers, if a request for multiple products is needed it must be created in the form
of one long string-type parameter with separators for each product. This BAdI parses the OData input parameters for
multiple products and breaks them down into individual product requests.
This BAdI definition is called by the SRSMOB/CL_MGW_AL_FACADE class when a
GetImageForMultiArticles OData Service request is received.
Requirements
You must configure the connectivity between the SAP back-end system and the SAP OData service through SAP
NetWeaver Gateway server, and integrate with the relevant image and supplemental data provider service such as
SAP Document Management Service (DMS), or any other Product Information Management (PIM) service.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element
Definitions tab in the BAdI Builder (transaction SE18).
Activities
The fallback class uses "|" as the separator between multiple product numbers. For example, "R100000|R100001"
represents two product numbers: R100000 and R100001. You can create a BAdI implementation to recognize a
different separator, however if you do so you must also create new client-side code, or change existing code to
incorporate the new separator in the send request.
More Information
For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application
Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View > Application Server > Application
Server ABAP > Application Development on AS ABAP > ABAP Customer Development > Enhancement Framework.

BAdI: Supplemental Data Query for Product Lookup

Use
This Business Add-In (BAdI) is used for the SAP Retail Store Ops Associate application. In this application, you can
activate settings that allow you to download supplemental product information, such as warranty or other detailed
information, and images to the mobile device from various back-end systems. The default BAdI implementation uses
SAP Document Management Services (DMS) to retrieve product images. Warranty information and product long
descriptions are partially hard-coded in the dummy implementation. You can create a different BAdI implementation
to integrate with another supplemental information, or image-providing back-end system.
Requirements
You must configure the connectivity between the SAP back-end system and the SAP NetWeaver Gateway server,
and integrate with the relevant image and supplemental data provider system, for example SAP Document
Management service, or any other Product Information Management (PIM) service.
Standard settings
The fallback class /SRSMOB/CL_STOP_SUPP_DATA_DMS integrates with DMS.
This BAdI provides the following methods:

GET_IMAGE_FOR_MULTI_ARTICLES
This method retrieves one image per article, but supports multiple articles. The image_usage parameter
is used to determine which image file is retrieved. In the SAP Mobile Retail Store Ops Associate application,
a THU value is sent by the client application to retrieve the thumbnail image file for the list screen.

GET_ALL_IMAGES_FOR_ARTICLE
This method retrieves all image files for one article. You customize the file name in the
/SRSMOB/STOP_SUPP_DATA_DMSCFG BAdI.

GET_ALL_SUPP_DATA_FOR_ARTICLE
This method retrieves all supplemental data for one article. The return structure is generic because it uses
name and value pairing.

GET_SUPP_DATA_WITH_IMAGE
This method retrieves images, warranty and long description text for one article.
It is specific to the Product Detail screen in the SAP Mobile Retail Store Ops Associate application since
only that data, and no other, is required there. This method is defined to return information in one request,
which provides a work around for the OData service that does not support returning two lists. This allows it
to avoid two OData calls; one to handle the get_all_images_for_article method, and the other to handle
get_all_supp_data_for_article. The SAP Mobile Retail Store Ops Associate application client sends a LIM
value to retrieve large image files for the detail screen.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element
Definitions tab in the BAdI Builder (transaction SE18).
More Information

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application
Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View > Application Server > Application
Server ABAP > Application Development on AS ABAP > ABAP Customer Development > Enhancement Framework.

BAdI: Customization of Goods Movement Type in Product Lookup

Use
This Business Add-In (BAdI) is used for the SAP Retail Store Ops Associate application. You use this BAdI to retrieve
the following SAP ERP for Retail component customizations:

Business transaction list for Other Goods Movement

Business transaction list for Stock Transfer

Reason list for Other Goods Movement

Requirements
You must make standard Customization settings for Goods Movement under Logistics - General > SAP Retail Store
> Goods Movement.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element
Definitions tab in the BAdI Builder (transaction SE18).
Activities
The default implementation BAdI /SRSMOB/CL_STOP_GM_CUSTOM_RET retrieves the customizaton of standard
Web Dynpro applications in SAP ERP for Retail. You must implement a new BAdI to retrieve the customization of
other applications, such as the ITS Mobile applications and the Web Dynpro applications.
In the default implementation BAdI, only one business transaction (0001 - Stock transfer from site to site) is retrieved
from the customization. This business transaction (0001) is set for use by the front end application for stock transfers
from site to site.