Show TOC

Create Point Of Sale Transaction as Bulk Locate this document in the navigation structure

Definition

To create point of sale transactions in bulk.

Technical Data

Software Component Version

RTLPOSDM 1.0

Release State

released

Technical Name

PointOfSaleTransactionERPBulkCreateRequest_In

Namespace

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

Application Component

BW-BCT-ISR-PIP

Related Web Service Definition

POSTrxERPBulkCRTRQ

Category

SAP A2A

Direction

inbound

Mode

asynchronous

Idempotency

not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled

yes

Notes on Release State (Technical Data)

This operation is the successor to operation of the same name under namespace http://sap.com/xi/BICONTENT/Global2.

Business Context

The operation is used to create POS transactions that have been sent from a POS system in the retail sector to SAP POS DM in bulk. This operation supports encryption of credit card data and credit-card-related data.

The corresponding outbound service of this operation resides in third-party component.

Features

The Create Point Of Sale Transaction as Bulk inbound operation is available to create POS transactions that have been sent from a POS system to SAP POS DM. The Create Point Of Sale Transaction as Bulk is a bulk operation that can contain multiple POS transactions within a single message. It is also possible to mix different transaction types within a single message.

The implementation of this inbound operation allows posting of the following transaction types:

  • Retail transactions, for example, sales, return, payment on account

  • Financial transactions, for example, deposit, paid in, tender adjustment

  • Control transactions, for example, cashier sign-on, close register, open store

Per single transaction, credit card data and credit-card-related data can be transferred in a single encrypted data segment.

The implementation of the inbound service is completely embedded in the existing SAP POS DM infrastructure and environment and uses the API /POSDW/CREATE_TRANSACTIONS_INT, which is also called in RFC, BAPI, and IDoc processing. Therefore, the structure of the service operation is mapped to the importing parameter of table type /POSDW/TT_TRANSACTION_INT.

The business object Point Of Sale Transaction is sent as input and describes a business activity as performed in a retail store (including retail transactions, financial movements, and goods movement).

Prerequisites

SAP POS DM must be configured for use according to the business requirements of the customer (the implementation of this inbound service is embedded in the environment of SAP POS DM). The Customizing settings required are the same as for other possible inbound interfaces and techniques such as IDoc, BAPI, or RFC.

Integration

This operation may be optionally referenced within the following software component(s):

  • Store Connectivity

  • ESM BI CONT

  • ESM Integration

There exists a mirrored test operation PointOfSaleTransactionERPBulkCreateRequest_Out under namespace http://sap.com/xi/RTLPOSDM/Global2/Testing.

Error Handling

Forward error handling (FEH) is not available in SAP NetWeaver BW.

As a result, any message that cannot get processed within the service implementation (for example, due to a mapping error) is rejected and a corresponding fault message is raised using cl_proxy_fault=>raise.

Constraints and Integrity Conditions

The operation cannot currently import inventory or summary transactions. This is currently only possible using IDoc, BAPI, and RFC interfaces.

Notes on SAP Implementation

Processing

The Create Point Of Sale Transaction as Bulk operation is an alternative method of transferring POS transactions to SAP POS DM. As a result, the following apply:

  • Depending on the SAP POS DM Customizing settings (transaction /POSDW/IMG) for the store sending the data, you can post the incoming data immediately or to use the SAP POS DM inbound queue (transactions /POSDW/QMON and /POSDW/QDIS) to post the data in a separate processing unit or step.

    If the SAP POS DM inbound queue is used, the XML messages of the service can be identified in the queue monitor in the following fields:

    • Key: Carries the GUID of the message instance

    • Object Type: Displays XML_DOC

  • Successfully processed POS transactions transferred using the Create Point Of Sale Transaction as Bulk operation can be monitored in the POS Workbench (transaction /POSDW/MON0). In the POS Workbench, it is not possible to identify which method was used to import the transactions into SAP POS DM (that is, operation, IDoc, RFC, or BAPI).

Configuration

Values of codelists of GDTs are mapped to corresponding values of SAP POS DM Customizing (criteria values of type 1 and type 2) to determine the PIPE category code. These Customizing settings are found under:   POS Data Management   POS Inbound Processing   Integration with Other SAP Components   SAP POS   Definition of Values for Category Code Criteria  .

Enhancements

The /POSDW/SE_POS_TRANSACT_INBOUND Business Add-In (BAdI) is available for this operation under Enhancement Spot /POSDW/SPOT_SE_POS_TRANSACTION.