Logistics on Product Documentation

MDA-LOC - Warehouse Master Data Management

Mon, 01 Jan 0001 00:00:00 +0000

The master data management process cannot be viewed separately; instead, the individual instances belong to the respective subprojects. Therefore, this instance is handled here and is linked to the meta process MDA - Master Data Management.

MDA-LOC - Warehouse Master Data Management

The process includes the management of warehouse locations for mapping and managing inventory for merchandise management and accounting. Within warehouse locations, a distinction is made between owned goods and depot or consignment goods.

PPA - Goods Receipt Package Preregistration

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(PPA<br>Goods Receipt Package Preregistration)
B(PPA-0010<br>Create package preregistration)
C(PPA-0020<br>Capture package)
D(PPA-0030<br>Check and complete capture)
E(PPA-0040<br>Print goods receipt label)

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

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

Package preregistration for goods receipt is carried out by the vendor. It gives the vendor the opportunity to capture the packages (or packaging units) of the goods ordered from them in the system exactly as they are actually provided. This supports the work of the customer’s import department (wholesaler), because they no longer have to interpret the contents of the shipment from complicated delivery notes. It can also simplify the receipt of goods at the central warehouse.

WFL - Goods Receipt Freight List

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WFL<br>Goods Receipt Freight List)
B(WFL-0010<br>Create GR freight list)
C(WFL-0020<br>Capture GR packages)
D(WFL-0030<br>Check and complete GR freight list)
E(WFL-0040<br>Print GR freight list)

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

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

The goods receipt freight list (GR freight list) is a document in which the vendor can add all packages that belong to one shipment.

WRB - Goods Receipt Journal

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WRB<br>Goods Receipt Journal)
B(WRB-0010<br>Physical goods receipt)
C(WRB-0020<br>Perform capture)
D(WRB-0030<br>Complete capture)

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

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

The goods receipt journal process describes the activities for the physical receipt of goods on the inbound area by logistics. It provides information about the goods shipments accepted in the warehouse and starts the logistics processes around goods receipt and quality assurance. In addition to goods shipments from vendors, returns and other shipments in the form of documents and samples can also be accepted.

WRT - Goods Receipt

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WRT<br>Goods Receipt)
B(WRT-0010<br>Create goods receipt document)
C(WRT-0020<br>Get source document)
D(WRT-0030<br>Capture line data)
E(WRT-0040<br>Perform total check)
F(WRT-0050<br>Post goods receipt)

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

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

The process describes the receipt of goods shipments in the system. The source documents for creating a goods receipt can differ. As a rule, however, these are inbound document types such as purchase order, advice, transfer order (receipt), and sales complaint. In the system, goods receipt is used for documented receipt and completeness control of goods shipments by logistics. Goods receipt increases warehouse inventory in the respective warehouse. Goods receipt offers the possibility of entering a put-away process for bin-managed logistics systems.

WPA - Put-away

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WPA<br>Put-away)
B(WPA-0010<br>Create put-away)
C(WPA-0020<br>Add lines)
D(WPA-0030<br>Edit document)
E(WPA-0040<br>Register put-away)

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

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

The delivered goods from vendor orders, from transfers, or from registered sales or purchase complaints are matched with a storage bin in the warehouse. The document header contains the warehouse location, posting date, and document number. The lines are transferred from the source document.

WST - Goods Issue

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WST<br>Goods Issue)
B(WST-0010<br>Open header data)
C(WST-0020<br>Add lines)
D(WST-0030<br>Release goods issue)
E(WST-0040<br>Start picking)
F(WST-0050<br>Capture line data)
G(WST-0060<br>Create package)
H(WST-0070<br>Check package)
I(WST-0080<br>Create shipping label)
J(WST-0090<br>Post goods issue)
K(WST-0100<br>Prepare goods for shipment)

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E
E ==> F
F ==> G
G ==> H
H ==> I
I ==> J
J ==> K

%% Classes
class A btProcessTitle
class B,C,D,E,F,G,H,I,J btProcessActive
class K btProcessExternal

The basis for goods issues is formed by the source documents sales order, transfer order, picking proposal, and purchase complaint. The goods can be assigned to a picking process and sorted by transaction. In wholesale, packages are generally used into which the items are scanned, whereas in retail goods are handled without packages.

WPI - Picking

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WPI<br>Picking)
B(WPI-0010<br>Create picking)
C(WPI-0020<br>Select picking)
D(WPI-0030<br>Physical goods movement)
E(WPI-0040<br>Capture line data)
F(WPI-0050<br>Register picking)

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

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

The picking of goods issues can be carried out on the basis of printed picking slips or supported by mobile devices. The picking transaction is performed manually and is realized in the system by manually increasing quantities or scanning via mobile data capture devices. Picking is carried out on the basis of shelves (non-inventory-managed bins) or bins in logistics.

FRD - Loading List Processing

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(FRD<br>Loading List Processing)
B(FRD-0010<br>Create document)
C(FRD-0020<br>Get source documents)
D(FRD-0030<br>Release document)
E(FRD-0040<br>Register document)
F(FRD-0050<br>Hand over document)

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

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

Based on different posted and unposted logistics documents (packages and goods issues), collection takes place for the purpose of handing them over to a carrier. The resulting list serves as proof for the carrier of which goods (quantity/weight) were handed over to them. With the help of the loading list, delayed posting of the unposted logistics documents (packages, goods issues) is made possible.

RET - Return Processing

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(RET<br>Return Processing)
B(RET-0010<br>Check package)
C(RET-0020<br>Check goods + return slip)
D(RET-0030<br>Open complaint)
E(RET-0040<br>Scan complaint)
F(RET-0050<br>Capture item)
G(RET-0060<br>Edit complaint)
H(RET-0070<br>Complete complaint)

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

%% Classes
class A btProcessTitle
class B,C btProcessExternal
class D,E,F,G,H btProcessActive

This process describes how returned goods pass through the returns department and inspection. The goods were previously announced through sales by recording a sales complaint. Based on return processing, the goods are received and evaluated in the central system. The complaint supports the response to any defects by triggering complaint-related documents. These can lead to a return delivery to the vendor and a new order, as well as replacement orders for the customer in exchange.

WTM - Bin Transfer

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WTM<br>Bin Transfer)
B(WTM-0010<br>Pick up goods)
C(WTM-0020<br>Capture item)
D(WTM-0030<br>Edit bins)
E(WTM-0040<br>Perform posting)
F(WTM-0050<br>Physically move goods)

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

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

The process describes the transfer within a warehouse location from one bin to another.

WTM-0010 - Pick up goods

The source bin is selected and the goods are picked up.

LPT - Label Printing

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(LPT<br>Label Printing)
B(LPT-0010<br>Create print job)
C(LPT-0020<br>Adjust print job header)
D(LPT-0030<br>Capture print job lines)
E(LPT-0040<br>Print labels)

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

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

The label printing process describes the procedure for generating labels from various source processes in procurement, sales, and merchandise management. Labels are forwarded to physical printing by means of so-called print jobs. The print jobs are prepared according to the respective source documents. Print jobs can be triggered by the respective functions from the purchase order, goods receipt, sales order, goods issue, and correction document, as well as when completing price management.

LOC - Warehouse Adjustment

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(LOC<br>Warehouse Adjustment)
B(LOC-0010<br>Create document header)
C(LOC-0020<br>Capture document lines)
D(LOC-0030<br>Edit warehouse adjustment document)
E(LOC-0040<br>Post warehouse adjustment document)

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

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

Warehouse adjustment is used to capture inventory-changing adjustment postings. It is used for removing, adding, or reclassifying goods through decreases and increases. Negative postings are generally carried out due to withdrawals, shrinkage, or theft. Reclassifications can be used, for example, to reclassify standard goods to collective items.

INV - Inventory

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(INV<br>Inventory)
B(INV-0010<br>Define inventory date)
C(INV-0020<br>Create inventory)
D(INV-0030<br>Determine target quantities)
E(INV-0040<br>Capture counted quantities)
F(INV-0050<br>Check and release inventory)
G(INV-0060<br>Post inventory result)

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

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

The process describes inventory by means of an inventory order or the inventory journal. It includes inventory date management, determination of inventory target quantities, handling of differences, and inventory-affecting posting.

ICO - Inventory Count

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(ICO<br>Inventory Count)
B(ICO-0010<br>Select source document)
C(ICO-0020<br>Capture items)
D(ICO-0030<br>Determine inventory quantity)
E(ICO-0040<br>Complete inventory)

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

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

The process describes the capture of inventory quantities. Capture can be performed manually by document or by MDE.

ICO-0010 - Select source document

The created source document is selected and a new inventory capture document is created. The source document originated from inventory date planning or EDI import.

IVA - Partial Value Write-downs

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(IVA<br>Partial Value Write-downs)
B(IVA-0010<br>Prepare inventory valuation)
C(IVA-0020<br>Determine inventory value)
D(IVA-0030<br>Calculate write-down)
E(IVA-0040<br>Check write-down)
F(IVA-0050<br>Complete inventory valuation)
G(IVA-0060<br>Create revaluation)
H(IVA-0070<br>Post revaluation)

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

%% Classes
class A btProcessTitle
class B,C,D,E,F,G,H btProcessActive

This process describes the valuation of merchandise inventory and the determination of so-called partial value write-downs. The write-down can be made on the basis of different criteria such as the age of the goods, season, or market observation. On the basis of inventory valuation levels, write-downs can be defined in BE-Fashion as percentages. When an inventory valuation level is reached, a proposed write-down percentage results. Depending on the chosen age determination, the inventory valuation level results either from the difference between two seasons or from the difference between the first/last goods receipt date and the currently considered cutoff date. The valuation is carried out on the corresponding level of cost price management (item or item-variant-warehouse location). When determining the write-down, acquisition costs represent the upper limit. The valuation of the goods is carried out according to the lower-of-cost-or-market principle.

QAG - Goods Quality Assurance

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(QAG<br>Goods Quality Assurance)
B(QAG-0010<br>Create QA header)
C(QAG-0020<br>Create QA lines)
D(QAG-0030<br>Edit QA document)
E(QAG-0040<br>Perform QA inspection)
F(QAG-0050<br>Release QA inspection)

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

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

The process includes preparing the quality inspection, carrying it out, and initiating the resulting actions. Materials (ingredient or finished products) are usually subjected to an inspection when goods or sample shipments are received. The result is transmitted to the vendors in the form of a report. The quantities received with the shipment of goods are buffered in a blocked warehouse as long as the quality control has not been completed and released accordingly.

WRC - Goods Receipt Defect List

Mon, 01 Jan 0001 00:00:00 +0000

Meta process

graph LR;

%% Nodes
A(WRC<br>Goods Receipt Defect List)
B(WRC-0010<br>Create defect list)
C(WRC-0020<br>Edit defect list)
D(WRC-0030<br>Release defect list)
E(WRC-0040<br>Post defect list)

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

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

This process describes the evaluation of goods shipments on the basis of the physical receipt. This means that the shipment as such is evaluated here, not the goods specifically. A special form of the defect list can be stored as a template for each vendor and activated for the inspection process. The background is differences in quality in the area of packaging, labeling, and documents. In addition to quality control, which primarily takes care of the qualitative assurance of the produced goods, the defect list evaluates the shipment itself (without reference to goods). The defect list contains a number of criteria that are checked for compliance by the warehouse personnel. Based on negatively evaluated criteria, charge notes can be created in the form of penalties, rework charges, and processing fees. The process ties in directly with the goods receipt journal.