Archiving POS Application Objects (SAP Library - Distributed Data Processing)

Archiving POS Application Objects

Use

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

Integration

The general notes should be used to archive the objects listed here, for example, for dependencies that are named in the documentation for the individual objects.

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 it does not write the billing documents to the database. In this case, the system only generates follow-on documents, for example, from Financial Accounting.
If you have not configured your system to do this, you have to archive the billing documents.

Note

You should archive all billing documents that are more than one week old.

You can use the following IDocs to generate billing documents:

WPUBON01	POS Interface: Upload sales documents (receipts) non-summarized
WPUTAB01	POS Interface: Upload POS for day-end closing
WPUUMS01	POS Interface: Upload aggregated sales data

Object name: SD_VBRK

Inventory Management

POS inbound processing records changes to stock in article documents.

Note

You should archive all article documents that are more than one week old.

You can use the following IDocs to generate article documents:

WPUBON01	POS Interface: Upload sales documents (receipts) non-summarized
WPUWBW01	POS Interface: Upload goods movements
WPUUMS01	POS Interface: Upload aggregated sales data

Object name: MM_MATBEL

Financial Accounting

POS inbound processing records changes to accounts in accounting documents.

Note

You should archive all accounting documents that are more than one week old.

You can use the following IDocs to generate accounting documents:

WPUBON01	POS Interface: Upload sales documents (receipts) non-summarized
WPUWBW01	POS Interface: Upload goods movements
WPUUMS01	POS Interface: Upload aggregated sales data
WPUTAB01	POS Interface: Upload POS for day-end closing
WPUFIB01	POS Interface: Upload Financial Accounting Interface FWWS/POS

Object name: FI_DOCUMNT

Purchase orders

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

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

You can use the following IDocs to generate purchase orders:

WGSREQ	Incoming orders/order confirmation
ORDERS	Purchase orders/orders

Object name: MM_EKKO

Purchase requisitions

The system can generate purchase requisitions (PR) during POS inbound processing.

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

You can use the following IDocs to generate purchase requisitions:

WGSREQ	Incoming orders/order confirmation
ORDERS	Purchase orders/orders

Object name: MM_EBAN

Deliveries

The system can generate deliveries during POS inbound processing.

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

You can use the following IDocs to generate deliveries:

WGSREQ	Incoming orders/order confirmation
ORDERS	Purchase orders/orders

Object name: RV_LIKP