PBP - Store Withdrawal Processing

Reference process for decentralised processing of centrally triggered withdrawal instructions in stores.

Meta Process

PBP - Store Withdrawal Processing

graph LR;

%% Nodes
A(PBP<br>Store Withdrawal Processing)
B(PBP-0010<br>Receive scan request)
C(PBP-0020<br>Start scanning)
D(PBP-0030<br>Edit transfer order)
E(PBP-0040<br>Finish scanning)

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E

%% Classes
class A btProcessTitle
class B,C,D,E btProcessActive

The processing of centrally triggered withdrawal instructions takes place decentrally in the stores or on the sales areas. The instructions are transmitted in the form of scan requests. These can be printed in the store and executed manually accordingly. For confirmation, feedback is sent to the system and linked transfer orders are recorded for posting the goods. After the activities have been completed, confirmation is sent to headquarters by scan that the process has been carried out.

PBP-0010 - Receive scan request

By selecting and printing transmitted scan requests, the store confirms that the process is being accepted. The physical removal of the goods can begin and is carried out on the basis of the printed scan request document.

PBP-0020 - Start scanning

The scanning process is started in the system via a function. The store scans the barcode on the scan request in order to link the document to a new transfer process. In the system, a transfer order or a purchase complaint is created in which further processing takes place up to the return shipment of the goods. The relevant header information, from, to, and source document, is taken over.

Outgoing processes:

PBP-0030 - Edit scan request

The items previously removed physically are scanned and added. Once all items have been recorded, the transfer order or purchase complaint is finally posted, the accompanying documents are printed, and the goods are physically shipped to the returns warehouse or to the vendor.

PBP-0040 - Finish scanning

To confirm that the withdrawal for the store has been completed, a function for reporting completion is started and the barcode of the scan request is printed again. The scan request can then be placed or filed with the store documents.

Outgoing processes:

Instances

PBP-WHS - Store Withdrawal Processing to Location

graph LR;

%% Nodes
A(PBP-WHS<br>Store Redistribution Processing)
B(PBP-WHS-0010<br>Receive scan request)
C(PBP-WHS-0020<br>Start scanning)
D(PBP-WHS-0030<br>Edit transfer order)
E(PBP-WHS-0040<br>Finish scanning)

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E

%% Classes
class A btProcessTitle
class B,C,D,E btProcessActive

The processing of centrally triggered withdrawal instructions takes place decentrally in the stores or on the sales areas. The instructions are transmitted in the form of scan requests. These can be printed in the store and executed manually accordingly. For confirmation, feedback is sent to the system and linked transfer orders are recorded for posting the goods. After the activities have been completed, confirmation is sent to headquarters by scan that the process has been carried out.

PBP-WHS-0010 - Receive scan request

See meta process

PBP-WHS-0020 - Start scanning

The scanning process is started in the system via a function. The store scans the barcode on the scan request in order to link the document to a new transfer process. In the system, a transfer order is created in which further processing takes place up to the return shipment of the goods. The relevant header information, from, to, and source document, is taken over.

Outgoing processes:

PBP-WHS-0030 - Edit scan request

The items previously removed physically are scanned and added in the transfer order. Once all items have been recorded, the transfer order is finally posted, the accompanying documents are printed, and the goods are physically shipped to the returns warehouse.

PBP-WHS-0040 - Finish scanning

See meta process

Outgoing processes:

PBP-VEN - Store Withdrawal Processing to Vendor

graph LR;

%% Nodes
A(PBP-VEN<br>Store Redistribution Processing to Vendor)
B(PBP-VEN-0010<br>Receive scan request)
C(PBP-VEN-0020<br>Start scanning)
D(PBP-VEN-0030<br>Edit transfer order)
E(PBP-VEN-0040<br>Finish scanning)

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E

%% Classes
class A btProcessTitle
class B,C,D,E btProcessActive

The processing of centrally triggered withdrawal instructions takes place decentrally in the stores or on the sales areas. The instructions are transmitted in the form of scan requests. These can be printed in the store and executed manually accordingly. For confirmation, feedback is sent to the system and linked transfer orders are recorded for posting the goods. After the activities have been completed, confirmation is sent to headquarters by scan that the process has been carried out.

PBP-VEN-0010 - Receive scan request

See meta process

PBP-VEN-0020 - Start scanning

The scanning process is started in the system via a function. The store scans the barcode on the scan request. In the system, a purchase complaint is created in which further processing takes place up to the return shipment of the goods. The relevant header information, from, to, and source document, is taken over.

Outgoing processes:

PBP-VEN-0030 - Edit scan request

See meta process

PBP-VEN-0040 - Finish scanning

See meta process

Outgoing processes: