SOP - Sales Order

Reference process for creating, editing, releasing, and monitoring sales orders in BE-terna Fashion.

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.

graph LR;

%% Nodes
A(SOP<br>Sales Order)
B(SOP-0010<br>Create order header)
C(SOP-0020<br>Add order lines)
D(SOP-0030<br>Define sizes and colours)
E(SOP-0040<br>Edit sales order)
F(SOP-0050<br>Release sales order)
G(SOP-0060<br>Monitor status)

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

SOP-0010 - Create order header

When a new sales order is created, the framework parameters of the process are set in the order header. In addition to the customer information (sell-to customer, bill-to customer), the order is assigned to an order season. Likewise, a time frame (shipment date) is defined for the order, which can deviate and be specified more precisely at line level. Conditions in the form of discounts, payment terms, and delivery terms are inherited into the document from the customer master data. The payment terms can contain value days that lead to the calculation of a value date. When specifying the order type, flexible order types can be selected. As a rule, a distinction is made between pre-order, immediate order (repeat order), and sample order for the customer. Among other things, the order type determines whether quantities may only be entered against availability. The sales representative is taken over from the customer master data and determines the responsible unit. To create a reference to the customer order, an external document number is entered in the header. In most cases, the location is prefilled with the central warehouse. In individual cases, a special location can be specified (showroom, sample warehouse, etc.). Since a sales order can be entered across several locations, the location at line level is decisive.

Incoming processes:

SOP-0020 - Add order lines

The order lines are created using the stored master data. For creating order lines, the line type (item, general ledger account, resource, fixed asset, item charge) is the starting point. In sales, the standard case is lines of type “Item”. This is how the goods are sold. Different line types are used to map additional calculations such as freight costs, services, or general surcharges. The fixed asset line type offers a special case for the sale of assets from the company’s own fixed asset master. Depending on the line type, a number can be specified that defines the master record of the object to be sold (item, general ledger account, resource, item charge code, fixed asset). In Fashion, items are often differentiated by colour and size variants. See step “SOP-0030 Define sizes and colours”. Price and discount calculation is performed. Depending on the combination of item, customer or customer price group, price date, quantity, and currency, this defines the valid price and discount. Depending on a central setup, the price date is either the shipment date or the document date.

SOP-0030 - Define sizes and colours

One order line is entered for each item variant (colour/size variant). The item variants can be entered manually using the fields variant code or colour, size scale, size, and EAN code, or alternatively via an entry matrix or item scan. Entering items via the entry matrix is the most commonly used option. After opening the matrix, the size-colour combinations are entered by specifying the quantities. Delivery dates can be changed in the matrix. Depending on availability, which depends on the order type, further delivery dates may result. The delivery date distribution is used for this.

SOP-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

Incoming processes:

SOP-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

Instances

SOP-MAN - Manual Sales Order

The sales order is entered manually in the system by internal sales or field sales.

graph LR;

%% Nodes
A(SOP-MAN<br>Manual Sales Order)
B(SOP-MAN-0010<br>Create order header)
C(SOP-MAN-0020<br>Add order lines)
D(SOP-MAN-0030<br>Define sizes and colours)
E(SOP-MAN-0040<br>Edit sales order)
F(SOP-MAN-0050<br>Release sales order)
G(SOP-MAN-0060<br>Monitor status)

%% 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
SOP-MAN-0010 - Create order header

When a new sales order is created, the framework parameters of the process are set in the order header. In addition to the customer information (sell-to customer, bill-to customer), the order is assigned to an order season. Likewise, a time frame (shipment date) is defined for the order, which can deviate and be specified more precisely at line level. Conditions in the form of discounts, payment terms, and delivery terms are inherited into the document from the customer master data. The payment terms can contain value days that lead to the calculation of a value date. When specifying the order type, flexible order types can be selected. As a rule, a distinction is made between pre-order, immediate order (repeat order), and sample order for the customer. Among other things, the order type determines whether quantities may only be entered against availability. The sales representative is taken over from the customer master data and determines the responsible unit. To create a reference to the customer order, an external document number is entered in the header. In most cases, the location is prefilled with the central warehouse. In individual cases, a special location can be specified (showroom, sample warehouse, etc.). Since a sales order can be entered across several locations, the location at line level is decisive.

SOP-MAN-0020 - Add order lines

The order lines are created using the stored master data. For creating order lines, the line type (item, general ledger account, resource, fixed asset, item charge) is the starting point. In sales, the standard case is lines of type “Item”. This is how the goods are sold. Different line types are used to map additional calculations such as freight costs, services, or general surcharges. The fixed asset line type offers a special case for the sale of assets from the company’s own fixed asset master. Depending on the line type, a number can be specified that defines the master record of the object to be sold (item, general ledger account, resource, item charge code, fixed asset). In Fashion, items are often differentiated by colour and size variants. See step “SOP-0030 Define sizes and colours”. Price and discount calculation is performed. Depending on the combination of item, customer or customer price group, price date, quantity, and currency, this defines the valid price and discount. Depending on a central setup, the price date is either the shipment date or the document date.

SOP-MAN-0030 - Define sizes and colours

One order line is entered for each item variant (colour/size variant). The item variants can be entered manually using the fields variant code or colour, size scale, size, and EAN code, or alternatively via an entry matrix or item scan. Entering items via the entry matrix is the most commonly used option. After opening the matrix, the size-colour combinations are entered by specifying the quantities. Delivery dates can be changed in the matrix. Depending on availability, which depends on the order type, further delivery dates may result. The delivery date distribution is used for this.

SOP-MAN-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

Incoming processes:

SOP-MAN-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-MAN-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-SQU - Sales Order from Sales Quote

The process describes the handling of a sales order based on an accepted sales quote.

graph LR;

%% Nodes
A(SOP-SQU<br>Sales Order from Sales Quote)
B(SOP-SQU-0010<br>Create order header)
C(SOP-SQU-0020<br>Add order lines)
D(SOP-SQU-0030<br>Define sizes and colours)
E(SOP-SQU-0040<br>Edit sales order)
F(SOP-SQU-0050<br>Release sales order)
G(SOP-SQU-0060<br>Monitor status)

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

%% Classes
class A btProcessTitle
class B,C,E,F,G btProcessActive
class D btProcessInactive
SOP-SQU-0010 - Create order header

The header data for the sales order is automatically taken over from the accepted sales quote. Further detail regarding goods recipients and delivery addresses can be added.

Incoming processes:

SOP-SQU-0020 - Add order lines

The sales lines for the sales order are automatically taken over from the accepted sales quote.

SOP-SQU-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-SQU-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-SQU-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-EDI - Sales Order via EDI

IN ORDERS are imported and the sales order is created from the EDI document. The steps, including release, run automatically. Cancellations are also carried out automatically if availability is insufficient.

graph LR;

%% Nodes
A(SOP-EDI<br>Sales Order via EDI)
B(SOP-EDI-0010<br>Create order header)
C(SOP-EDI-0020<br>Add order lines)
D(SOP-EDI-0030<br>Define sizes and colours)
E(SOP-EDI-0040<br>Edit sales order)
F(SOP-EDI-0050<br>Release sales order)
G(SOP-EDI-0060<br>Monitor status)

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

%% Classes
class A btProcessTitle
class B,C,E,F,G btProcessActive
class D btProcessInactive
SOP-EDI-0010 - Create order header

The sales order is created from IN ORDERS processing and the order header data is taken over from the EDI IN ORDERS message and the assigned customer.

Incoming processes:

SOP-EDI-0020 - Add order lines

The order lines are also transferred from the EDI message into the lines.

SOP-EDI-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-EDI-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-EDI-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-BOR - Sales Order Blanket Order

A blanket order represents a contractual construct with an agreed total quantity. Multiple releases can be created from the blanket order. The blanket order is entered for the head office without specifying the branches. The prerequisite for distributor entry is the maintenance of the branches on the head office and the assignment of the head office to itself so that collective orders with several releases to the head office/customer are possible directly.

graph LR;

%% Nodes
A(SOP-BOR<br>Sales Order Blanket Order)
B(SOP-BOR-0010<br>Create order header)
C(SOP-BOR-0020<br>Add order lines)
D(SOP-BOR-0030<br>Define sizes and colours)
E(SOP-BOR-0040<br>Edit sales order)
F(SOP-BOR-0050<br>Release sales order)
G(SOP-BOR-0060<br>Monitor status)

%% 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
SOP-BOR-0010 - Create order header

When a new sales order is created, the framework parameters of the process are set in the order header. In addition to the customer information (sell-to customer, bill-to customer), the order is assigned to an order season. Likewise, a time frame (shipment date) is defined for the order, which can deviate and be specified more precisely at line level. Conditions in the form of discounts, payment terms, and delivery terms are inherited into the document from the customer master data. The payment terms can contain value days that lead to the calculation of a value date. When specifying the order type, flexible order types can be selected. As a rule, a distinction is made between pre-order, immediate order (repeat order), and sample order for the customer. Among other things, the order type determines whether quantities may only be entered against availability. The sales representative is taken over from the customer master data and determines the responsible unit. To create a reference to the customer order, an external document number is entered in the header. In most cases, the location is prefilled with the central warehouse. In individual cases, a special location can be specified (showroom, sample warehouse, etc.). Since a sales order can be entered across several locations, the location at line level is decisive.

The blanket order indicator is taken over from the customer master data and can also be set manually. When a sales order is identified as a blanket order, it is active for the follow-up process Sales Order Distributor, but it cannot be delivered directly. A release order is always required for the delivery of the goods recorded in this order (see release from blanket order).

SOP-BOR-0020 - Add order lines

The order lines are created using the stored master data. For creating order lines, the line type (item, general ledger account, resource, fixed asset, item charge) is the starting point. In sales, the standard case is lines of type “Item”. This is how the goods are sold. Different line types are used to map additional calculations such as freight costs, services, or general surcharges. The fixed asset line type offers a special case for the sale of assets from the company’s own fixed asset master. Depending on the line type, a number can be specified that defines the master record of the object to be sold (item, general ledger account, resource, item charge code, fixed asset). In Fashion, items are often differentiated by colour and size variants. See step “SOP-0030 Define sizes and colours”. Price and discount calculation is performed. Depending on the combination of item, customer or customer price group, price date, quantity, and currency, this defines the valid price and discount. Depending on a central setup, the price date is either the shipment date or the document date.

SOP-BOR-0030 - Define sizes and colours

One order line is entered for each item variant (colour/size variant). The item variants can be entered manually using the fields variant code or colour, size scale, size, and EAN code, or alternatively via an entry matrix or item scan. Entering items via the entry matrix is the most commonly used option. After opening the matrix, the size-colour combinations are entered by specifying the quantities. Delivery dates can be changed in the matrix. Depending on availability, which depends on the order type, further delivery dates may result. The delivery date distribution is used for this.

SOP-BOR-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-BOR-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-BOR-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-CBO - Sales Order Release from Blanket Order

Further orders can be created from a distributor for a blanket order. These release orders reduce the quantities of the blanket orders and are separated by goods recipients or delivery addresses.

graph LR;

%% Nodes
A(SOP-CBO<br>Sales Order Release from Blanket Order)
B(SOP-CBO-0010<br>Create order header)
C(SOP-CBO-0020<br>Add order lines)
D(SOP-CBO-0030<br>Define sizes and colours)
E(SOP-CBO-0040<br>Edit sales order)
F(SOP-CBO-0050<br>Release sales order)
G(SOP-CBO-0060<br>Monitor status)

%% 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
SOP-CBO-0010 - Create order header

From the blanket order, a release order can be created via the sales order distributor. The header data is taken over automatically from the blanket order. The branch selected in the sales order distributor is used as the sell-to customer. Release orders are appended to existing orders separately by goods recipient. The assignment between blanket order and release orders is always maintained.

Incoming processes:

SOP-CBO-0020 - Add order lines

The order lines are automatically taken over from the underlying blanket order, according to the items and quantities selected in the sales order distributor.

SOP-CBO-0030 - Define sizes and colours

The sizes and colours are automatically taken over from the underlying blanket order, according to the items and quantities selected in the sales order distributor.

SOP-CBO-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-CBO-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-CBO-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-REO - Sales Order from Replacement Order

If a complaint has been recorded and a corresponding decision has been made, a replacement order is created from the complaint document.

graph LR;

%% Nodes
A(SOP-REO<br>Sales Order from Replacement Order)
B(SOP-REO-0010<br>Create order header)
C(SOP-REO-0020<br>Add order lines)
D(SOP-REO-0030<br>Define sizes and colours)
E(SOP-REO-0040<br>Edit sales order)
F(SOP-REO-0050<br>Release sales order)
G(SOP-REO-0060<br>Monitor status)

%% 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
SOP-REO-0010 - Create order header

The header data is taken over from the complaint.

Incoming processes:

SOP-REO-0020 - Add order lines

The replacement item is transferred from the complaint and a reference to the original item is established.

SOP-REO-0030 - Define sizes and colours

The colour-size level is taken over from the variant in the complaint. The quantity corresponds to the quantity of the returned items.

SOP-REO-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer such as clearance lots or special conditions. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-REO-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-REO-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-ICO - Intercompany Sales Order

Sales orders can be linked to purchase orders from another company using intercompany functions. The orders are then either created automatically based on a purchase order from another company, or they generate this purchase order after release, depending on the side on which the intercompany process is started.

graph LR;

%% Nodes
A(SOP-ICO<br>Intercompany Sales Order)
B(SOP-ICO-0010<br>Create order header)
C(SOP-ICO-0020<br>Add order lines)
D(SOP-ICO-0030<br>Define sizes and colours)
E(SOP-ICO-0040<br>Edit sales order)
F(SOP-ICO-0050<br>Release sales order)
G(SOP-ICO-0060<br>Monitor status)

%% 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 btProcessInactive
class E,F,G btProcessActive
SOP-ICO-0040 - Edit sales order

Prices and discounts can be changed manually and via special functions. Reasons include individual agreements with the customer and clearance lots. Prices are taken from the valid price list; these can be overridden using special prices. If conditions for discounts, among other things, have been stored on the customer, these can be selected in the order.

Remarks and texts can be stored at line level. In the remarks, it can be specified, for example, whether a print should appear on the order confirmation, picking, delivery note, or invoice.

Additional functions include cancellation, determination of sales prices, and transfer of invoice discounts. For cancellation, the corresponding line is marked and cancellation is activated. The reason for cancellation is specified and the remaining quantity of the line is set to 0.

Among other things, delivery dates can be changed at line level (special cases if further logistical processes such as preparation still need to be considered).

SOP-ICO-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. Releasing makes the sales order visible for subsequent processes. Releasing the sales order triggers the intercompany function, which keeps the item lines, quantities, and conditions of the purchase order linked to this document in sync.

Outgoing processes:

SOP-ICO-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.

SOP-ECO - Webshop Sales Order

This process describes the order handling of the B2B and B2C webshop. For this purpose, sales orders are transferred from the eCommerce interface.

The header data of the sales order is taken over from the webshop, such as billing address and, if applicable, a different delivery address as well as payment terms. In addition, the webshop order number is transferred. An assignment to the webshop order is created and the specified reference is taken over.

The order lines are also taken over from the webshop order.

graph LR;

%% Nodes
A(SOP-ECO<br>Webshop Sales Order)
B(SOP-ECO-0010<br>Create order header)
C(SOP-ECO-0020<br>Add order lines)
D(SOP-ECO-0030<br>Define sizes and colours)
E(SOP-ECO-0040<br>Edit sales order)
F(SOP-ECO-0050<br>Release sales order)
G(SOP-ECO-0060<br>Monitor status)

%% 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 btProcessInactive
class E,F,G btProcessActive
SOP-ECO-0040 - Edit sales order

The sales order can now be checked and edited. Lines with missing availability can be cancelled.

SOP-ECO-0050 - Release sales order

Once order entry is complete, the order must be released. It must be checked that each order line has a price, sales representative, and shipment date. If prepayment rates are stored, a prepayment invoice must first be created. After the open item has been settled, the sales order can be released. Releasing makes the sales order visible for subsequent processes. If the sales order is complete and checked, it is released and the follow-up processes are started. An order confirmation can be issued as a printed document or electronically (EDI ORDRSP).

Outgoing processes:

SOP-ECO-0060 - Monitor status

Organisational process step in internal sales. Further processing of the order is monitored using the corresponding inquiries. Customer and item search are used to support this.