Sales on Product Documentation

MDA-SAL - Sales Master Data Management

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

Meta Process

The master data management process cannot be viewed separately; rather, the individual instances belong to the corresponding subprojects. These instances are therefore handled here and are functionally assigned to the master data area.

graph LR;

%% Nodes
A(MDA-SAL<br>Sales Master Data<br>Management)

%% Flow

%% Classes
class A btProcessTitle

Instances

MDA-CON - Contact Master Data Management

Contacts are created by sales or field sales. They are used to record people and companies with whom no business relationship yet exists. After further classification, contacts can be processed further into customers and vendors.

SQU - Sales Quote

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

Meta Process

This process describes the creation of quotes as the basis for a sales order. Sales quotes support the sales process by creating a still non-binding document that can become a binding order through further processing. The sales quote also forms the basis for the EDI item master data export by means of PRICAT.

graph LR;

%% Nodes
A(SQU<br>Sales Quote)
B(SQU-0010<br>Create quote header)
C(SQU-0020<br>Add quote lines)
D(SQU-0030<br>Edit quote)
E(SQU-0040<br>Check availability)
F(SQU-0050<br>Create order)

%% 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

SQU-0010 - Create quote header

The sales quote is created and the header data is entered. The quote header is filled, analogously to the sales order, with the customer and further framework parameters such as order season and delivery period. Specifying the customer results in further conditions such as payment and delivery terms, price group, as well as language and currency. By assigning it to a campaign, the quote can be linked to a marketing activity. To support entry, a document can be copied from an existing sales document.

SOP - Sales Order

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

Meta Process

The process describes the creation of sales orders in wholesale. Sales orders are created through different entry methods by internal sales, field sales, and electronic messages. They can be entered as an individual order or as a blanket order. The header information defines the framework conditions for the order through the customer and corresponding period assignments. Individual lines are entered and added to the order with the stored conditions. For handover to subsequent processes, the order is released, which serves to check the order. Depending on the order type, these can be organised differently. The process ends after the order has been released. Follow-up processes are generally located in logistics (repeat order) or procurement (pre-order). In individual cases, the sales order can be delivered and invoiced directly.

SOD - Sales Order Distribution

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

Meta Process

Additional orders can be created from a distribution based on a blanket order. These call-off orders reduce the quantities of the blanket orders and are separated by goods recipients or delivery addresses. The assignment between blanket order and call-off orders is available at all times.

graph LR;

%% Nodes
A(SOD<br>Sales Order Distribution)
B(SOD-0010<br>Create document header)
C(SOD-0020<br>Create distribution)
D(SOD-0030<br>Edit distribution)
E(SOD-0040<br>Create order)

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

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

SOD-0010 - Create document header

A distribution for call-off orders can be stored on an existing blanket sales order. The header data and item lines are automatically transferred from the blanket order. The function “Distribution delivery dates” opens an item distribution overview in which the size-branch combination is shown as individual lines for each item on the basis of the colour code. Several distributions with different shipment dates can be created for each item colour code. Sizes and colours are inherited from the blanket order and from the quantities assigned in the order distribution to the call-off order. The quantities of the call-off order reduce the quantities of the blanket order.

PPP - Picking Proposal

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

Meta Process

The process describes the allocation of available warehouse stock to customer orders due for delivery according to internal criteria and the preparation of goods issue. The picking proposal is used for central control of which order lines are to be transferred to the goods issue process. The process is usually carried out in wholesale. Stock allocation is generally performed according to a defined allocation sequence. Because of its scalability, the picking proposal can be created and processed for targeted items or for a selection of items and orders.

CIN - Customer Invoice Processing

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

Meta Process

In this process, the invoice or credit memo is created based on a shipment or return, or as a manual process. The corresponding invoicing transaction completes the sales process started earlier and transfers the resulting data to Financial Accounting or Accounts Receivable.

Where invoice is mentioned in the individual process steps, this also includes the credit memo. The process instances are described separately according to document type, invoice and credit memo.

CIL - Sales Invoice List

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

Meta Process

In this process, various posted invoices and credit memos are collected in the form of a list in order to forward them or print them afterwards.

graph LR;

%% Nodes
A(CIL<br>Sales Invoice List)
B(CIL-0010<br>Create document header)
C(CIL-0020<br>Prepare lines)
D(CIL-0030<br>Release document)
E(CIL-0040<br>Transmit document)

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

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

CIL-0010 - Create document header

The system assigns a unique document number taken from a number series. After entering the document date, various filters can be defined, for example date filter, association number, and customer filter, in order to include the relevant invoices and credit memos.

ACC - Sales Representative Commission Settlement

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

Meta Process

This process describes the commission settlement procedure. Employed representatives or independent commercial agents often receive a commission when they handle the sale of goods. Their typical activities include customer acquisition, presentation of the goods to the customer or in a showroom, customer consulting up to order placement, order entry, and customer care or customer support. Representatives play an especially important role in the wholesale business.

Representatives are assigned to the orders for which they are responsible. As a rule, the representative is already stored in the customer master record and inherited from there to the sales order. Commission rates can be stored in the system for the representative, which generate commission lines after the sales order is released. When the order is invoiced, meaning the corresponding sales invoice is posted, commission entries are written from it.

ROP - Customer Return Notification

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

Meta Process

The return process in Sales is carried out through several steps. The process of the return notification is described below. It usually takes place in the Sales department and describes the recording of sales complaints on the basis of which further processes such as goods receipt, credit memo, and replacement order can take place.

graph LR;

%% Nodes
A(ROP<br>Customer Return Notification)
B(ROP-0010<br>Create sales complaint)
C(ROP-0020<br>Insert complaint lines)
D(ROP-0030<br>Edit complaint)
E(ROP-0040<br>Register complaint)
F(ROP-0050<br>Post sales complaint)

%% 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

ROP-0010 - Create sales complaint

The return of goods by the customer is registered. For this purpose, the complaint document is recorded in the system. To support entry, a complaint can be copied from, for example, a sales shipment or invoice. In manual entry, the complaint type return or complaint is selected in the complaint header, the relevant customer and the receiving warehouse are recorded. The negotiated conditions result from the customer. In addition, indicators in the header can be used to select whether acceptance of the returned goods has been rejected or collection of the returned goods has been initiated.

OCD - Correction Document

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

Meta Process

The process describes the batch run of a correction document with predefined restrictions. The document can be used to perform and log mass changes to orders. A simulation is also possible.

graph LR;

%% Nodes
A(OCD<br>Correction Document)
B(OCD-0010<br>Create correction document header)
C(OCD-0020<br>Retrieve variants)
D(OCD-0030<br>Edit correction document)
E(OCD-0040<br>Post correction document)

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

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

OCD-0010 - Create correction document header

The correction document header is created. A processing type is selected: replace, cancel, postpone delivery date, insert order text. In addition, the required restrictions or filters are filled, for example delivery date, order number from/to, customer, warehouse location, representative, or item.