Archiving POS Application Objects 

Use

The inbound POS interface uses the objects created here in POS inbound processing.

Integration

For archiving of the objects mentioned here, the general remarks (such as about dependencies) that are described in the documentation for the individual objects apply.

Features

Billing

The system uses billing in POS inbound processing to calculate values for other functions and to process payment transactions. Billing documents are generated in the processes and they are used to document the billing procedure.

You can configure your system in Customizing for POS so that POS inbound processing calls the billing function but does not write the billing documents to the database. In this case, the system only generates follow-on documents, for example in Accounting.
If you have not configured your system to do this, you have to archive the billing documents.

You should archive all billing documents that are older than a week.

Billing documents are generated by the following IDocs:

WPUBON01

POS Interface: Upload Sales Documents (Individual Receipts)

WPUTAB01

POS Interface: POS Upload for Day-End Closing

WPUUMS01

POS Interface: Upload Aggregated Sales Data

Object name: SD_VBRK

See also: Archiving Billing Documents (SD-BIL)

Inventory Management

POS inbound processing records changes to stock in article documents.

You should archive all article documents that are older than a week.

Article documents are generated by the following IDocs:

WPUBON01

POS Interface: Upload Sales Documents (Individual Receipts)

WPUWBW01

POS Interface: Goods Movement Upload

WPUUMS01

POS Interface: Upload Aggregated Sales Data

Object name: MM_MATBEL

See also: Archiving Material Documents (MM-IM)

Financial Accounting

POS inbound processing records changes to accounts in accounting documents.

You should archive all accounting documents that are older than a week.

Accounting documents are generated by the following IDocs:

WPUBON01

POS Interface: Upload Sales Documents (Individual Receipts)

WPUWBW01

POS Interface: Goods Movement Upload

WPUUMS01

POS Interface: Upload Aggregated Sales Data

WPUTAB01

POS Interface: POS Upload for Day-End Closing

WPUFIB01

POS Interface: Upload Financial Accounting Interface instore system/POS

Object name: FI_DOCUMNT

See also: Archiving FI Documents (FI-GL, FI-AR, FI-AP)

Purchase Orders

The system can generate purchase orders (PO) during POS inbound processing.

If a purchase order cannot be generated successfully, the system generates the workflow task TS00900073.

Purchase orders are generated by the following IDocs:

WGSREQ

Distributed retailing system: order receipt/order confirmation

ORDERS

purchase orders/sales order

Object name: MM_EKKO

See also: Archiving Purchasing Documents (MM-PUR)

Purchase Requisitions

The system can generate purchase requisitions during POS inbound processing.

If a purchase requisition cannot be generated successfully, the system generates workflow task TS00900075.

Purchase requisitions are generated by the following IDocs:

WGSREQ

Distributed retailing system: order receipt/order confirmation

ORDERS

purchase order/sales order

Object name: MM_EBAN

See also: Archiving Purchase Requisitions (MM-PUR)

Deliveries

The system can generate deliveries during POS inbound processing.

If a delivery cannot be generated successfully, the system generates workflow task TS00900075.

Deliveries are generated by the following IDocs:

WGSREQ

Distributed retailing system: order receipt/order confirmation

ORDERS

purchase orders/sales order

Object name: RV_LIKP

See also: Archiving Deliveries (LE-SHP)

Sales Orders

The system can generate sales orders during POS inbound processing.

If a sales order cannot be generated successfully, the system generates workflow task TS00900075.

Sales orders are generated by the following IDocs:

WGSREQ

Distributed retailing system: order receipt/order confirmation

ORDERS

purchase orders/sales order

Object name: SD_VBAK

See also: Archiving Sales Documents (SD-SLS)