Documente Academic
Documente Profesional
Documente Cultură
DOCUMENT_TYPE = DRW
DOCUMENT_PART = 000
DOCUMENT_VERSION = "-"
"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.
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.
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.