OCD - Correction Document

Reference process for mass changes to sales orders using correction documents in BE-terna Fashion.

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.

OCD-0020 - Retrieve variants

The items to be corrected and their variants are entered in the correction document lines. Using the function “Retrieve all variants”, the system automatically records all variants of a specified item. Depending on the processing type, additional information may need to be entered, for example replacement item, new delivery dates, and texts.

OCD-0030 - Edit correction document

After the items to be corrected have been specified in the item lines, all orders or customers matching the restrictions from the correction document header are determined by means of the function “Affected customers/orders”. The data records identified in the previous step are checked against the restrictions in the correction document header and modified if necessary. Individual customers and items can be removed manually or excluded from the correction document.

OCD-0040 - Post correction document

The checked and final correction document is posted in the system. Posting can either be carried out manually in the system or started automatically overnight through a job.

Outgoing processes:

Instances

OCD-IEX - Correction Document with Item Replacement

The process describes the batch run of a correction document when an item is replaced.

graph LR;

%% Nodes
A(OCD-IEX<br>Correction Document<br>with Item Replacement)
B(OCD-IEX-0010<br>Create correction document header)
C(OCD-IEX-0020<br>Retrieve variants)
D(OCD-IEX-0030<br>Edit correction document)
E(OCD-IEX-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-IEX-0010 - Create correction document header

The correction document header is filled with the necessary restrictions or filters. The type is “Replace”. A cancellation reason must be specified which is used to cancel the items to be replaced.

OCD-IEX-0020 - Retrieve variants

The items to be corrected and their variants are entered in the correction document lines. Using the function “Retrieve all variants”, the system automatically records all variants of a specified item. The corresponding replacement item variant must be entered for each item variant.

OCD-IEX-0030 - Edit correction document

After the items to be corrected have been specified in the item lines, all orders or customers matching the restrictions from the correction document header are determined by means of the function “Affected customers/orders”. The data records identified in the previous step are checked against the restrictions in the correction document header and modified if necessary. Individual customers and items can be removed manually or excluded from the correction document.

OCD-IEX-0040 - Post correction document

The checked and final correction document is posted in the system. Posting can either be carried out manually in the system or started automatically overnight through a job. The affected items are cancelled in the affected order lines and new item lines with the replacement items are appended to the orders.

Outgoing processes:

OCD-CAN - Correction Document due to Cancellation

The process describes the batch run of a correction document when an item has to be cancelled completely because, for example, it was not purchased or is not deliverable.

graph LR;

%% Nodes
A(OCD-CAN<br>Correction Document<br>due to Cancellation)
B(OCD-CAN-0010<br>Create correction document header)
C(OCD-CAN-0020<br>Retrieve variants)
D(OCD-CAN-0030<br>Edit correction document)
E(OCD-CAN-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-CAN-0010 - Create correction document header

The correction document header is filled with the necessary restrictions or filters. The type is “Cancel”. A cancellation reason must be specified for the cancellation.

OCD-CAN-0020 - Retrieve variants

The items to be corrected and their variants are entered in the correction document lines. Using the function “Retrieve all variants”, the system automatically records all variants of a specified item.

OCD-CAN-0030 - Edit correction document

After the items to be corrected have been specified in the item lines, all orders or customers matching the restrictions from the correction document header are determined by means of the function “Affected customers/orders”. The data records identified in the previous step are checked against the restrictions in the correction document header and modified if necessary. Individual customers and items can be removed manually or excluded from the correction document.

OCD-CAN-0040 - Post correction document

The checked and final correction document is posted in the system. Posting can either be carried out manually in the system or started automatically overnight through a job. The affected items are cancelled in the affected order lines.

Outgoing processes:

OCD-ETD - Correction Document Delivery Date

The process describes the batch run of a correction document due to a change of delivery date.

graph LR;

%% Nodes
A(OCD-ETD<br>Correction Document<br>Delivery Date)
B(OCD-ETD-0010<br>Create correction document header)
C(OCD-ETD-0020<br>Retrieve variants)
D(OCD-ETD-0030<br>Edit correction document)
E(OCD-ETD-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-ETD-0010 - Create correction document header

The correction document header is filled with the necessary restrictions or filters. The type is “Delivery date postponement”.

OCD-ETD-0020 - Retrieve variants

The items to be corrected and their variants are entered in the correction document lines. Using the function “Retrieve all variants”, the system automatically records all variants of a specified item. The new delivery date must be entered in the field New shipment date.

OCD-ETD-0030 - Edit correction document

After the items to be corrected have been specified in the item lines, all orders or customers matching the restrictions from the correction document header are determined by means of the function “Affected customers/orders”. The data records identified in the previous step are checked against the restrictions in the correction document header and modified if necessary. Individual customers and items can be removed manually or excluded from the correction document.

OCD-ETD-0040 - Post correction document

The checked and final correction document is posted in the system. Posting can either be carried out manually in the system or started automatically overnight through a job. The affected items are cancelled in the affected order lines.

Outgoing processes:

OCD-AOT - Correction Document Insert Order Text

The process describes the batch run of a correction document due to an addition of order text.

graph LR;

%% Nodes
A(OCD-AOT<br>Correction Document<br>Insert Order Text)
B(OCD-AOT-0010<br>Create correction document header)
C(OCD-AOT-0020<br>Retrieve variants)
D(OCD-AOT-0030<br>Edit correction document)
E(OCD-AOT-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-AOT-0010 - Create correction document header

The correction document header is filled with the necessary restrictions or filters. The type is “Insert order text”.

OCD-AOT-0020 - Retrieve variants

The items to be corrected and their variants are entered in the correction document lines. Using the function “Retrieve all variants”, the system automatically records all variants of a specified item. The order text to be added is entered using the function Capture item text.

OCD-AOT-0030 - Edit correction document

After the items to be corrected have been specified in the item lines, all orders or customers matching the restrictions from the correction document header are determined by means of the function “Affected customers/orders”. The data records identified in the previous step are checked against the restrictions in the correction document header and modified if necessary. Individual customers and items can be removed manually or excluded from the correction document.

OCD-AOT-0040 - Post correction document

The checked and final correction document is posted in the system. Posting can either be carried out manually in the system or started automatically overnight through a job. The order text is added to the affected order lines.

Outgoing processes:

Links

Further Information

Links

Links