SAP POS DM 1.

0 (New)

Use
As of SAP NetWeaver BI Content 7.07, POS Data Management functionality is no longer included in the BI
Content Add-On. Customers installing or upgrading to SAP NetWeaver BI Content 7.07 or higher must install
SAP POS Data Management 1.0 (SAP POS DM 1.0) as a separate software component.

SAP POS DM 1.0 is available for both traditional databases and the SAP HANA™ database. Using SAP POS
DM 1.0 powered by SAP HANA allows you take advantage of SAP in-memory computing to accelerate
decision making in your business.

Effects on Customizing
The Define Profile for Over/Short Balancing Customizing activity has been renamed to Define Profile for
Short/Over Balancing. All underlying functionality has remained unchanged.

See also
SAP POS DM 1.0, Decoupling from SAP BI Content (New)

SAP POS DM 1.0, Powered by SAP HANA™ (New)

SAP POS DM 1.0, Deprecated Enterprise Services (Changed)

SAP POS DM 1.0, Decoupling from SAP BI Content (New)

Use
As of SAP NetWeaver BI Content 7.07, POS Data Management functionality is no longer included in the BI
Content Add-On. Customers installing or upgrading to SAP NetWeaver BI Content 7.07 or higher must install
SAP POS Data Management 1.0 (SAP POS DM 1.0) as a separate software component.

The SAP POS DM application help, previously located on the SAP Help Portal under SAP NetWeaver --> BI
Content --> Application Help --> Industry Solutions --> Trading Industries --> Retail Trade --> Store Analytics -
-> POS Data Management, can now be accessed from http://help.sap.com/posdm.

Furthermore, release notes related to POS Data Management functionality shipped with previous releases of BI
Content, can be accessed on the SAP Service Marketplace under http://service.sap.com/releasenotes --> SAP
NetWeaver -->BI Content.

Effects on System Administration

If you are using Service Oriented Architecture (SOA) to transfer transactional data from POS systems to SAP
POS DM 1.0, you must update the Web Service names as described in SAP POS DM 1.0, Deprecated
Enterprise Services.

Effects on Customizing
Customers who use SAP Loss Prevention Analytics (LPA) and SAP Retail Method of Accounting (RMA) and
who install SAP POS DM 1.0 can optionally specify RFC destinations using the following Customizing
activities:

 LPA General Settings, under POS Data Management --> POS Inbound Processing --> Integration
with Other SAP Components --> Loss Prevention Analytics

You use this activity to specify the RFC destination of the system that contains the SAP NetWeaver BI
Content referenced by SAP LPA.

 Determine RFC Destinations for Method Calls, under SAP Customizing Implementation Guide -->
SAP NetWeaver --> Application Server --> IDoc Interface ALE --> Communication

You use this activity to specify the logical system name of the system that contains SAP POS DM 1.0,
which is called as an external application by SAP RMA.

The option to specify the above mentioned RFC destinations is provided for future use. For the SAP POS DM
1.0 release, not specifying an RFC destination results in a local call (that is, a call to the current system).
Existing customers upgrading to SAP POS DM 1.0 do not need to make changes to their current Customizing
settings.
SAP POS DM 1.0, Powered by SAP HANA™ (New)

Use
As of SAP POS DM 1.0, the application is available for both traditional databases and the SAP HANA™
database. Using SAP POS DM 1.0, powered by SAP HANA allows you take advantage of SAP in-memory
computing to accelerate decision making in your business.

SAP POS DM 1.0, powered by SAP HANA includes SAP POS DM In-Memory Analytics, which allows you to
query uncompressed, real-time POS transaction data stored in the SAP HANA database. The SAP POS DM
In-Memory Analytics is comprised of:

 Internal BI Content, included in the SAP POS DM installation

 SAP HANA Business Content (HANA analytic views), the installation and deployment of which are
described in SAP Note 1720277

The internal BI Content included with SAP POS DM can:

 be used as is, if you have evaluated it and it fits your business needs

 be adapted so that you can work with it to any degree of detail

 serve as a template or as an example for customer-defined BI Content

Effects on Existing Data

If you are implementing SAP POS DM 1.0 on a traditional database, there is no effect on existing data; POS
transaction data is compressed and persisted in TLOGS and TLOGL tables as in previous releases.

If you are implementing SAP POS DM 1.0 on an SAP HANA Database, POS transaction data is stored
uncompressed and is persisted in the TLOGF table.

Note that if you are migrating to SAP POS DM 1.0, powered by HANA from a previous release, an additional
effort is required to convert existing POS data to the new uncompressed format required by the SAP HANA
database. Refer to the SAP NetWeaver BW 7.3, powered by SAP HANA End-to-End Implementation
Roadmap guide, available at
https://help.sap.com/nw73bwhana/ under Installation and Upgrade Information. Prior to migrating existing POS
transaction data, it is recommended that you save or archive your existing POS transaction data.

Furthermore, if you are migrating to SAP POS DM 1.0, powered by HANA from a previous release and you
have previously replaced the standard implementation of the /POSDW/CL_DATA_SOURCE class with a
custom implementation using the Assignment of Customer-Specific Classes for POS DW Customizing
activity, you must update the following methods:

Prior Methods New Methods (SAP POS DM 1. 0, powered by HANA)

FETCH_NEXT_TLOG FETCH_NEXT_TLOG_DS
READ_TLOG READ_TLOG_DS
SEARCH_TLOG SEARCH_TLOG_DS
WRITE_TLOGL WRITE_TLOGL_DS
WRITE_TLOGS WRITE_TLOGS_DS
Effects on System Administration
To archive POS transactions on an SAP HANA database, you must select the appropriate archiving object in
SAP POS DM 1.0. Start transaction SARA and use the following archiving object:

 /POSDW/TLF for archiving POS transactions on the SAP HANA database

Effects on TREX

To enable TREX features for SAP POS DM implemented on the SAP HANA database, apply SAP Note
1714365. You must also ensure that your version of SAP NetWeaver is at least:

• SAP NetWeaver 7.3 SPS 08, or

• SPS 04 of enhancement package 1 for SAP NetWeaver 7.3

Effects on Customizing
The SAP POS DM 1.0 application automatically detects the presence of an SAP HANA database in your
landscape and there are no specific Customizing activities that need to be executed.

In the SAP POS DM 1.0 release, the following BAdIs have been provided under Customer-Specific
Enhancements and BAdI Implementations --> Enhancement for In-Memory Analytics to accelerate
performance of in-memory analytics:

 BAdI: POS Transaction Inbound Data Status Processing Enablement

 BAdI: POS Transaction Aggregation on Header Level

 BAdI: POS Transaction Aggregation on Item Level

 BAdI: POS Transaction Aggregation on Tender Level

 BAdI: POS Transaction Data Distribution to Item Level

The Define Tasks Customizing activity has been enhanced to include the following new indicators:

 Data Status Relevant - this new option allows you to specify whether a task modifies the transactional
data stored in the TLOGF table.

 Task Cancelation Tracking - this new option allows you specify whether the cancellation of a task
should be tracked in the POS transaction record.

The Define Profiles Customizing activity has been enhanced to include the Master Data Checks for Data
Status Determination option. This new option allows you to specify a check profile that will be used by the
application during data status processing. Also, the previously existing option Master Data Checks in Dialog
has been renamed to Master Data Checks for Inbound Processing and POS Workbench without affecting the
underlying functionality.
Furthermore, the following tasks have been added to the standard SAP Profile:

 8001 Aggregate Transaction Data for Analytics

 8002 Supply Analytics Content with Distributed Transaction Data

 8003 Determine Transaction Data Status

See also
For more information on the new tasks added to the standard profile, see SAP Help Portal at
http://help.sap.com/posdm --> Application Help --> POS Inbound Processing Engine --> Task Processing --
> Task Processing for In-Memory Analytics.
SAP POS DM 1.0, Deprecated Enterprise Services (Changed)

Use
As of the SAP NetWeaver 7.XX BI Content 7.X7 release, SAP POS Data Management is no longer included in
the BI Content software component (as it previously was in SAP NW 7.XX BI CONT ADDON 7.X5 and SAP
NW 7.XX BI CONT ADDON 7.X6). SAP POS DM 1.0 is available in its own, RTLPOSDM 100_7XX software
component. Therefore, if you were using one of the following enterprise services:

 Namespace: http://sap.com/xi/BICONTENT/Global2

o PointOfSaleTransactionERPBulkCreateRequest_In

o LoyaltyMembershipActivityJournalCRMBulkRequest_Out

 Namespace: http://sap.com/xi/BICONTENT/Global2/Testing

o PointOfSaleTransactionERPBulkCreateRequest_Out

you should be aware that these enterprise services have been set to lifecycle status "Deprecated" in the
Enterprise Service Repository (ESR) for Process Component Point Of Sale Transaction Processing.

If you are implementing SAP NetWeaver 7.XX BI Content 7.X7 with SAP POS DM 1.0, use the following
enterprise services:

 Namespace: http://sap.com/xi/RTLPOSDM/Global2

o PointOfSaleTransactionERPBulkCreateRequest_In

o LoyaltyMembershipActivityJournalCRMBulkRequest_Out_V1

 Namespace: http://sap.com/xi/RTLPOSDM/Global2/Testing

o PointOfSaleTransactionERPBulkCreateRequest_Out

See also
For more information, see SAP Help Portal at http://help.sap.com/posdm --> Application Help --> Enterprise
Services.