Parts request (Gozintograph)
Technical description
Starting from parts planning, the production-specific parts lists selected there - sorted by production stage - are summarised in so-called Gozintographs. The parts request module(business pattern) described here is used to maintain such automatically generated gozintographs.
The task of this module is to be able to carry out purely logistical material planning in a first stage. This is done in six steps:
- Determination of the disposition type of the parts
- Determination of the standard procurement time according to the MRP type
- Scheduling the necessary provision of parts
- Checking the availability of materials
- Triggering production orders, purchase requisitions and warehouse reservations
- Release of the parts request
Steps 1, 2 and 3 can be called up and carried out directly and automatically as a process from parts planning. The "standard details" for the procurement type and time from the master information of the parts master are used as the basis. Steps 3 and 4 (planning) may have to be carried out iteratively several times after the disposition type and/or procurement time of individual parts have been changed manually so that the planned deadlines can be met. This planning can also be carried out with graphical support using a Gantt chart.
Post-calculation
In order to determine which costs have actually been incurred for a cost object (e.g. sales order), all costs ? its subsequent documents must be totalled. These are, for example, goods withdrawal slips, PDC cancellations, incoming invoices, etc. Some parts that are required but not planned do not have follow-on documents, but must of course still be charged to the sales order. This is done for these parts using the standard quantity specified in the parts list.
Only if the parts request is released (traffic light on green), all costs of the parts that are not planned are allocated to the cost units via the final costing.
All other costs are automatically incurred when the follow-up document is posted.
The following MRP types are available for MRP from the parts request:
| Disposition type | Description | Dispo account | Stock withdrawal | Provision | Loaded | Recalculation | Indicator | |
|---|---|---|---|---|---|---|---|---|
| No disposition | Parts are required but do not need to be planned because, for example, they have been found somewhere or because the standard planning type on the parts warehouse account is set to "manual warehouse". | 0 | 0 | 0 | 0 | Parts list | 0 | |
| Material removal | Parts are withdrawn from the warehouse via the staging list. Planned material withdrawals appear in the MRP account of the relevant part | 1 | 1 | 1 | Order | Material removal | 1 | |
| Purchase requisition | Parts are ordered as required and provided via a goods receipt | 1 | 0 | 1 | Order | Incoming invoice | 2 | |
| Production order | Parts are manufactured. | 1 | 0 | 1 | Order | Production order | 3 | |
| Material removal in advance | Before creating the part request, a part has already been reserved via an advance requirement, which is now used for this part request item | 1 | 1 | 1 | Order | Material removal | 4 | |
| Preliminary order request | Before creating the part request, a part has already been ordered via an advance requirement, which is now used for this part request item | 1 | 0 | 1 | Order | Incoming invoice | 5 | |
| Advance production order | A part has already been produced via a preliminary requirement before the part request was created, which is now used for this part request item | 1 | 0 | 1 | Order | Production order | 6 | |
| Special material withdrawal | Parts are provided via the staging list, but a material withdrawal is not created for this. The part request item that has not yet been staged does not appear in the MRP account of the part | 0 | 0 | 1 | Order | parts list | 7 | |
| Remaining quantity | When creating a part request for a remaining quantity part, the system checks whether the stock level is still positive, regardless of the amount.
| 1 | 1 | 1 | Order | Material removal | 8 | |
| Disposition type | Description | Dispo account | Stock withdrawal | Provision | Loaded | Recalculation | Indicator | |
| JIT part | Is regularly supplied by the supplier without having to be ordered | 0 | 0 | 0 | Order | parts list | 9 | |
| Kanban part | The part request item appears in the MRP account and is posted to the stock reservation status. A material withdrawal is not necessary. However, the required material appears on the production documents and the parts list. Level 0 and BOM items are staged via the staging list. The corresponding BOM items are selected here and the menu item "Create goods withdrawal document" is selected. This marks the items as staged, even if no document is generated (mock posting). The replenishment of the storage bin is carried out automatically by the employees bypassing the system. | 1 | 0 | 1 | Cost centre | parts list | 10 | |
| Hand bearing part | The part request item does not appear in the MRP account and is not posted to the stock reservation status. Staging and material withdrawal is not necessary. However, this material withdrawal appears on the production documents and the parts list. | 0 | 0 | 0 | Cost centre (stock transfer to non-disp. warehouse) | parts list | 11 | |
| Material overhang | A sufficient stock quantity is available for the part request, which was originally set to "purchase requisition" or "production order". The MRP type has been automatically or manually changed to material surplus. This item therefore does not need to be planned but can be withdrawn from the warehouse. The expected quantity can also be taken into account using the setting "Consider scheduled stock orders". | 1 | 1 | 1 | Order | Material removal | 12 | |
| Disposition type | Description | Dispo account | Stock withdrawal | Provision | Loaded | Recalculation | Indicator | |
| Own provision: Production order | Material is provided to the customer. Typically, such parts are subsequently found in the part request below an ordered part. A production order is created for this item. All parts required for this production order are visible in the part request and must be planned. | 1 | 0 | 1 | Order | Production order | 13 | |
| Own provision: purchase requisition | Material is provided to the customer. Typically, such parts are located below an order part in the part request. Material is ordered and then sent to the customer. | 1 | 0 | 1 | Order | Incoming invoice | 14 | |
| Own provision: Material withdrawal | Material is provided to the customer. Typically, such parts are located below an order part in the parts request. The material is removed from the staging list as in a standard material withdrawal and then sent to the customer. | 1 | 1 | 1 | Order | Material removal | 15 | |
| Customer provision | The customer will supply the material. The part request item behaves like a purchase order. It expects a goods receipt and is planned according to its provision | 1 | 0 | 1 | click="javascript:toggle_dynamic_var(" | ");" title="Click to edit dynamic variable: | ">No value assigned | 16 |
| Kanban semi-finished product | Kanban semi-finished parts are parts that are manufactured from larger raw materials. For example, a holder plate that is punched from a large sheet of raw material. | 0 | 0 | 0 | Order | parts list | 17 | |
| Disposition type | Description | Dispo account | Stock withdrawal | Provision | Loaded | Recalculation | Indicator |
Explanation of the general term "Kanban"
Kanban is Japanese and means "card". It is a practical system of warehouse management in which a card is placed under all parts at the bottom of each box in which parts are stored in the warehouse. When the box is empty, the card becomes visible. Now the employee who took the last part from the crate must take the card and give it to the buyer indicated on the card. Depending on the replenishment time of the part, there must then be 2 or more crates of this part.
Every time a crate is empty, a new one is ordered. During the time in which the crate has been ordered but has not yet arrived or is being manufactured, the remaining crates are used.
1. determination of the disposition type of the parts
Based on the logistics labelling assigned to a part by default (in-house production, purchased or external production part) and its staging labelling (MRP part, stock part, etc.), the MRP type is automatically determined for each part in the Gozintograph. For example, non-stock in-house production parts are set to the "production order" MRP type, non-stock purchased parts to the "requirement request" MRP type and stock parts to the "material withdrawal" MRP type.
Staging indicators such as manual storage part are parts that actually have the MRP type "Material withdrawal". However, since such parts are not withdrawn from the warehouse on an order-related basis via material withdrawal slips and are therefore not "processed", such parts are set to the MRP type "No MRP".
Another irregularity is the "Special material withdrawal". If a part request item is set to special material withdrawal, this requirement does not appear in the MRP account, but the item is still in the stock reservation status - and can therefore be found via the staging list. These items must also be staged here, but no goods withdrawal documents are created. These parts also appear in the production documents as to be withdrawn from the warehouse.
The determination of the MRP type can either be influenced automatically by separate control systems or changed manually. If, for example, a purchased part that is not normally kept in stock has stock (e.g. due to a return delivery from a previous order), the system automatically changes the MRP type from "requirement request" to"material surplus ". The same applies to a production part in stock that may have been "left over" from a previous order. The parts can then be taken directly from the warehouse. The part requests labelled with this MRP type appear in the staging list under "Stock reservation".
The MRP type defined in a Gozintograph - automatically or manually - can therefore differ from the "standard" procurement type. The "standard" procurement type defines the generally applicable case and is not (should not be) changed for specific orders.
In a gozintograph, the fully exploded parts lists of all parts are recorded in full. If a part is located below or within an assembly whose MRP type is "requirement request" or "material withdrawal", then this part or its quantity share - together with all parts of its BOM - does not need to be taken into account for MRP, as it is already contained in its higher-level assembly. For such parts, the MRP type is set to "not required". Conversely, if the MRP type of the superordinate assembly is changed to "production order" (if it is also an in-house production part), the subordinate parts are automatically included in the MRP again - the quantities (proportions) become visible again.
The MRP type"No MRP" therefore refers to parts that are required or must be used, but should not be planned. The MRP type"not required", on the other hand, refers to parts that appear in the summarised bill of materials, but whose parent part is not to be produced (the parent part does not have the MRP type "production order").
The determined or manually defined MRP type is displayed in the "MRP" column. In the next column, information is displayed - if required - as to whether the MRP type could cause problems in the subsequent processing stages. If the check fails, a red warning dot is displayed:
| Disposition type | Check |
|---|---|
| Production order | Valid routing, master routing |
2. determination of the standard procurement time according to the MRP type
The standard procurement or replenishment lead time is taken from the production role for the "production order" MRP type and from the order item role for the part for the "requirement request" MRP type. For production parts, this is purely the procurement time of the corresponding level (total lead time of the routing for this production part only, not its assemblies). It is therefore not the total "delivery time" of the part. For parts kept in stock (material withdrawals), a duration of 1 day is entered as standard.
In addition to the standard procurement time, there is also the option of having the procurement time determined dynamically. This dynamic determination only affects parts that have been assigned the "Production order" MRP type. The system now checks whether a routing has already been cancelled on the production order that may already be attached. If so, the total time of the cancelled routing is saved as the lead time for the part request item.
If there is no routing for the production order yet, or if no production order has been created yet, the total of the master routing is saved as the lead time for the part request item.
3. scheduling of the necessary provision of the parts
Due to the sequence of the production stages and the procurement times of the individual parts, there is a scheduling network of the parts among each other (order network), which is best represented in the form of a Gantt chart.
In forward scheduling, this collective order starts on a predefined date (the default value is the day of planning itself); in backward scheduling, the delivery date (or, if available, the provision date) is used as the starting point. It is not possible to schedule into the past, i.e. even with backward scheduling, the delivery or provision date can be postponed to a later date than desired. (A corresponding warning message is automatically issued by the system, the system then automatically schedules forwards).
The delivery or provision date can be influenced by changing (shortening or extending) the procurement time: this results in an extension or shortening of the entire order network.
The starting point of scheduling - e.g. the delivery or provision date in the case of backward scheduling - is initially transferred to the collective order as the"latest finish date". If the procurement time is subtracted from such a "latest finish date", a"latest start date" is obtained. Different lengths of procurement times within a production stage result in"earliest start dates" for individual parts, which can be earlier than the latest start date. Adding the procurement time to the earliest start date then results in an"earliest finish date".
In the case of automatic scheduling over a period of time (e.g. "3rd calendar week 2014"), the last working day of the period is used as the latest end date for backward scheduling. This results in the latest start. The earliest start is then determined from the latest start by subtracting the duration of the period, and the earliest finish is determined from this.
Excursus: The production orders are transferred to capacity planning with their respective earliest and latest finish dates.
Automatic (non-graphical) forward scheduling:
See the Automatic schedulingsection
See also operating calendar and buffer times
In the case of requirements from part requests (issue date), the planned date is made up of the earliest and latest start, which also results in a time span.
With the "Strict" evaluation type, the earliest date of this time period is always used for the evaluation, with the "Medium" setting exactly the middle and with "Soft" the end of the time period, i.e. there is the least buffer for the actual requirement.
If replenishment (e.g. stock replenishment) is always to take place with a little breathing space, we recommend the "Medium" setting, which is always set in the standard system.
However, if there is little space in the warehouse or if the warehouse budget should always be kept as low as possible, the "Soft" setting is recommended, which means that stock is only planned on the actual requirement date.
Strict therefore means that the goods are always procured at the earliest possible date and may also remain in the warehouse for some time until they are needed, depending on how long the buffer times of the requirements were.
4. checking the availability of materials
Checking material availability on the basis of the earliest or latest date in the parts request. This can be shifted forwards (with -) or backwards by days or weeks. This postponement is not calculated in calendar days but in working days, i.e. public holidays and weekends are not taken into account.
During the check, the subsequent part requests are normally also taken into account, i.e. parts are also displayed that are available for the order but are in the red due to other orders. By selecting the "Ignore later requirements" checkbox, these subsequent part requests are no longer taken into account!
On the one hand, the availability of material on the desired date can be checked here for stock-managed material - by checking in the respective MRP account. The entries with the unavailable material are displayed selected in the list.
On the other hand, material overhangs can be checked: If a part is a purchased or production part by default, but remaining stock (material overhangs) is still available from previous orders, these entries in the list are also displayed selected for further checking. In response, the MRP type can be changed from requirement request to material withdrawal, for example, which means that this part is no longer procured via purchasing but is withdrawn from the existing (surplus) stock.
These checks can also be carried out with graphical support using a Gantt chart.
5. triggering of production orders, purchase requisitions and stock reservations
Once the MRP types and dates for all parts within the Gozintograph have been created, further documents such as production orders, purchase requisitions and stock reservations can be created automatically.
6. release of the parts request
The release of the part request blocks it from subsequent changes.
A. Linking with advance requirements
If a sales order item is planned and advance requirements have been created for it, the following query appears, for example:

If you press "YES", this means that the remaining quantity still reserved via advance requirements is withdrawn from this special sales order, transferred to the warehouse and thus released for general availability.
If you press "NO", it means that you still want a remaining reserved quantity to remain available for this sales order and its further future dispositions.
If in doubt, you should answer "NO" here, i.e. leave the reserved quantities for this sales order.
Double-click on the part request item to open the individual MRP. Among other things, the quantity of the part request item can be changed there. To do this, the edit field must be enabled using the button next to the quantity. The quantity change is also carried out in the exploded parts list (predecessor of the parts request item) when the individual MRP is saved. If the part request item has several predecessors, the system attempts to allocate the quantity to all predecessors. This can result in the quantity of a parts list item being set to 0 or being greatly increased. If it is not possible to split the new quantity, a corresponding error message is issued and the quantity change is not saved.
C.Deletion of direct follow-up documents (production order, requirement request, warehouse reservation)
When deleting direct follow-up documents, the respective identifiers within the part request must be deleted, otherwise direct follow-up documents can no longer be created for the items concerned.
To remove the identifier, there is the menu item Delete in the part request under Edit. The various identifiers can be removed using the submenu items below.
Functionality
- Main window
- Single disposition
- Disposition structure
- List window
- Selection window
- Automatic scheduling
- Required capacity
Main window
This window is used to process a parts request (Gozintograph) that has been created as part of parts planning from the production parts lists summarised by production stage. The type of display and further processing of the parts request can be controlled via the options.
In the main menu, the activities relating to the entire parts request are summarised; functionality relating to individual selected lines of the parts request can be accessed using the buttons or the context menu (right mouse button on a line).
Double-clicking on a list entry takes you to the maintenance window of an individual list entry, an individual MRP.
The "Work plan" column provides a quick overview of whether there is anything to note with regard to the work plans for production parts:
- Red dot: There is no master routing for the production part, so a routing cannot be exploded during further processing.
- Green tick: A routing has already been exploded on the created production order (perhaps it has already been changed)
If neither of the two cases applies to the part request item, the column remains empty.
| Menu item | Menu description |
|---|---|
| Edit | - |
| Disposition | - |
| : : Determine disposition type | Transfer of the standard procurement type from the parts master. This process must always be carried out first. Manual specification is possible by double-clicking on the list entry. |
| : : Determine procurement time | If default values are selected, the procurement time is determined from the production or order part role - according to the previously defined MRP or procurement type. With Dynamic, the procurement time for production parts is taken from the sum of the lead times of the master routing. If a routing has already been exploded for the production order, the total sum of the individual work sequences is determined as the lead time for the production part. For ordered parts, the procurement time is also taken from the ordered part role. |
| Scheduling | - |
| : : Graphical | Backward or forward scheduling is carried out using a graphical tool for editing the Gantt chart (a separate licence is required). In the event of rescheduling, the Gantt chart is only called up for part request items that are not completely finished/ready. The earliest start date and the latest finish date are transferred to the Gantt chart as fixed points for parts request items that are already in further processing. These are (can no longer be) changed. The "Show current scheduling" mode only opens the graphical view of the current scheduling, i.e. it no longer changes the existing dates! |
| : : Automatic | The backward or forward scheduling is determined internally and written to the gozintograph. With "fixed scheduling", the same start/end date is entered in all lines of the part request (e.g. purely based on the end date). You can choose whether you only want to reschedule the previously undermined part request items (e.g. also those items whose dates were previously deleted with the "Delete" menu item below) or also those items that have already been processed further. More about automatic scheduling in the automatic scheduling window. |
| : : Delete | The start and end dates are deleted. |
| Check | - |
| : : Material availability | see |
| : : Material surpluses | For all parts of the MRP type not equal to material withdrawal, a possible availability in the warehouse on the desired date is checked. If stock is actually available on the desired date, these parts are displayed in a separate list. Such parts could then be manually switched to the "Remaining quantity" MRP type, for example. |
| : : Capacity requirement (CTP) | All required work centres are checked for capacity in the required week and displayed in a "Required capacity" window. For production parts, the system checks whether the work can be carried out on time at the defined work centres on the exploded routing items (capacity check - CTP). If no routing has yet been cancelled for the part request item, this is carried out simulatively. The deadline for the entire production is postponed by one week into the future until all work sequences can be executed in direct succession. The end date can therefore be postponed. This is only possible with forward scheduling. |
| : : Changed dates | Display of all part requests that no longer match the dates of the follow-on documents due to rescheduling |
| : : Open advance requirements | Listing of all open advance requirements for orders processed in this gozintograph |
| Set assembly type | - |
| : : Constructive assembly | A part labelled with the MRP type production order is completely removed from the part request. This part is treated as a constructive assembly, whereby the production level of all parts included in this assembly is reduced by one level.(Business Pattern) |
| Further processing | - |
| : : Process part request in one | All necessary steps for further processing of the part request are carried out in one run: Create production order, purchase requisition, stock reservation, release. |
| : : Create first production order | The production orders are created as items within a common production order for all parts of the production order MRP type. The options can be used to control whether and how the production order is to be further processed. |
| : : Create first purchase requisition | The purchase requisitions are created as items within a common purchase requisition for all parts of the MRP type purchase requisition. |
| : : Make stock reservation | A stock reservation is made for all parts of the MRP type material withdrawal, remaining quantity, special material withdrawal. |
| : : Release part request | Once all the necessary steps have been carried out, the parts request should be marked as released - and therefore fully processed. |
| : : Stragglers | - |
| : : : Create another production order | If a first production order has already been created, but a further production order is required due to the rescheduling of another part, this can be created using this selection. |
| : : : Create another purchase requisition | If an initial purchase requisition has already been created, but a further purchase requisition is required due to the replanning of another part, this can be created using this selection. |
| : : : Create another stock reservation | If a stock reservation has already been made, but a further stock reservation becomes necessary due to the reallocation of another part, this can be created subsequently using this selection. |
| : : Subsequent calculation of the parts request | Post all parts of the part requests for the preliminary costing and "non-scheduled" parts (e.g. JIT) also for the costing. |
| Delete | - |
| : : Cancel part request release | The release of the part request is cancelled. This is always necessary first if changes need to be made to the part request or if the entire part request needs to be cancelled. |
| : : Cancel production order | After the production orders that have already been created have been deleted, the internal identifier must also be deleted here within the part request. |
| : : Cancel purchase requisition | After the purchase requisitions that have already been created have been deleted, the internal identifier must also be deleted here within the part requisition. |
| : : Cancel stock reservation | The stock reservation of parts awaiting material withdrawal is cancelled. |
| : : Cancel the warehouse reserve documents | Each item of the parts request is checked to see whether a stock return document exists as a successor; if so, it is cancelled and deleted if necessary. |
| : : Cancel calculation of the parts request | All parts of the part requests from the preliminary costing and "non-scheduled" parts (e.g. JIT) are also cancelled from the costing. |
| : : Delete entire part request | The parts request is deleted completely, the parts planning can be carried out again - possibly in a different combination of primary orders. |
| : End position | - |
| : : Cancel remaining quantity | The quantity of the selected part request items not yet provided is cancelled |
| Close | The window with the part request is closed. If the part request has not yet been released, a warning message appears. |
| Navigate | - |
| Generated production order(s) | The production orders generated from the part request are displayed. |
| Generated purchase requisition(s) | The purchase requisitions generated from the part request are displayed. |
| : Triggering part dispositions | The primary triggers of the parts lists summarised in the part request are listed. |
| Completion of change management | All open reversals (stop sign next to the quantity) due to changes are then displayed in the "Change management completion" processing window. The quantities that are no longer required can be reversed from here (return documents, goods putaway...) |
| Options | A special window for selecting list display and/or filtering options is opened. If this option window is closed, the list is rebuilt according to the selected options. |
| Search | The list window is opened. |
Context menu
| Menu item | Menu description |
|---|---|
| Navigate | - |
| : Parts requirement trigger | The primary triggers (customer, stock order or advance requirement items) are displayed for the selected lines of the parts request. |
| : Parent part(s) | For a single, selected part of the part request, all the parts in which this part is used are also marked in the list. |
| Allocated part(s) | - |
| : : List view | For a single, selected part of the part request, you can choose either a) have the parts additionally marked in the list view that are required for the selected part (allocated from the selected part) or |
| : : tree view | b) display the entire MRP structure in the tree view. These views are only activated after the MRP has been run, as only then is it determined which parts are required and which are not. |
| Capacity requirements of the selected items | Determines the capacity requirement per calendar week and work centre for the selected items |
| Check Change main MRP | What would change if an order item is to be produced in-house? A results window opens in which the changes that would result are displayed |
| Change main MRP | - |
| No disposition | The MRP type can be specified manually for the selected lines of the part request. A part should always be manually set to "No MRP" if it is not to be processed for MRP purposes, i.e. it should neither be managed in the MRP account nor taken into account in the scheduling of the remaining parts: It is still required. Such a part is therefore still included in the costs of the final costing. If a part is no longer required at all, its quantity should be set to zero (individual MRP). |
| Material withdrawal | The part is reserved in the warehouse and withdrawn from there using a material withdrawal slip. |
| : Purchase requisition | The system generates a purchase requisition for the part and forwards it to the purchasing department. |
| : Production order | The system generates a production order for the part. |
| : Advance material withdrawal | The part is confirmed as stocked, but the material withdrawal has already been carried out - with a material withdrawal slip related to this order (post-calculation!). |
| Preliminary purchase requisition | The part is confirmed as an MRP purchased part, but has already been procured. This MRP type is automatically assigned by the system if a preliminary requirement was created for this part and order. If this MRP type is assigned manually, care should be taken to ensure that the purchase costs are posted to this order for the purposes of post-calculation. |
| Advance production order | The part is confirmed as an MRP production part, but has already been manufactured. This MRP type is automatically assigned by the system if a preliminary requirement was created for this part and order. If this MRP type is assigned manually, care should be taken to ensure that the production costs are posted to this order for post-calculation purposes. |
| Remaining quantity | like "Material withdrawal", different identifier as notification to warehouse staff. |
| : Manual storage part | The part is confirmed as stocked, but should not be processed for MRP purposes (corresponds to the MRP type "No MRP"). |
| Special material withdrawal | like "Material withdrawal", different identifier as notification to warehouse staff. |
| JIT part | In ClassiX® standard processing such as "purchase requisition", customer-specific adaptations as agreed. |
| : Kanban part | In ClassiX® Standard processing such as "Material withdrawal", customer-specific adaptations by agreement. |
| Create secondary disposition | In addition to the main planning of a part, a partial quantity can also be planned in another way. For example, if production is very busy and therefore cannot produce 100 units of a product on time, a partial quantity can be ordered from a supplier. After posting the auxiliary disposition, all quantities no longer required for production are cancelled and a request is made to put them back into stock via the "Evaluation - Logistics - Change management completion" list. |
| Purchase requisition | A purchase requ isition is created for the selected part and linked to the part requisition item. The quantity that is planned via a purchase requisition is cancelled from all subordinate parts lists and production orders |
| Production order | Not possible. Production order must always be the main MRP. Solution to the problem: Set the logistics indicator in the part to "Production part". "Production order" is then used as the main MRP when the part request is created. You can then create a "stock reserve" secondary MRP for existing stock quantities. This is generated automatically if you have selected "Use surplus quantities automatically" in the options. |
| Stock reserve | A warehouse reserve document is generated that exclusively binds a surplus quantity from the warehouse to the part request item. This quantity is then no longer available for other orders |
| Own provision | An in-house provision is created for the selected part. However, it does not fulfil the requirements of the item, which must be received in full and planned via the main MRP. |
| Customer provision | A customer provision document is generated: The customer has this part himself and would like to have his own part built into the component. |
| Perform (partial) cancellation | Cancellation of the entire part request or partial quantities with a cancellation document |
| (Partial) provision correction | Completion of an open part request with a correction document (no cancellation) ! |
| Icon | Toolbar description |
|---|---|
| Edit part | |
| Show production part | |
| Show stock movements | |
| Show stock | |
| Show dispo movements | |
| Show logistics account | |
| Show parts usage | |
| Show document history | |
| Display parts list | |
| Edit work plan | |
| Print list | |
| Copy to clipboard | |
| List all advance requirements for part requests | |
| Graphical view of the current scheduling, so the part request must already be scheduled beforehand! | |
| Number | Select part request directly |
| Release part request or reset release |
Options window
Each time the part request window is opened, the options described here are reset to the default settings.
| Menu item | Menu description |
|---|---|
| Edit | - |
| : Set default settings | all changed settings are reset to default |
| Field | Field description |
|---|---|
| Display | |
| : Display | - |
| : : Do not show parts without disposition | Only the parts of the part request that are planned according to the agreed MRP rules are shown. |
| : : Show parts without MRP | Parts of the part request are also shown that are to be used according to the parts list but are not planned (e.g. manual bearing parts). |
| : : Show all parts ("without disposition" AND "not used") | All parts of the parts request are shown, i.e. all parts of the parts lists summarised in the gozintograph, regardless of their disposition. |
| Disposition | |
| Surplus quantities | - |
| : : Automatically consume surplus quantities | Surplus quantities are consumed. |
| : : Consider scheduled stock orders | Normally, a part in the logistics account is set as staging MRP or stock management. This option allows the linking of both staging types for production parts. An MRP part is produced when there is a requirement (e.g. sales order). This setting enables quantities to be produced in advance as a stock order; if a sales order is now scheduled in the parts request and the end date of the stock order is before that of the sales order, a stock reserve document is automatically created and the part is not produced additionally. This setting can be used to achieve optimised capacity utilisation for special machines or test equipment for certain products, e.g: |
| : : Until minimum stock | Can only be selected if the "Consume automatically" checkbox is activated. Surplus quantity is used up to minimum stock. |
| Release | |
| : : Release with capacity test | If this option is set, the system automatically checks whether sufficient capacity is available for the part request when a part request is released (see also menu item for checking capacity requirements (CTP)). |
| Requirement requests | |
| : Booking | |
| : : Automatically post created purchase requisition | If this option is set, the purchase requisitions created from a part request are posted automatically. |
| Scheduling | |
| End date | - |
| : : Delivery date | The delivery date specified on the order item is used as the end date for scheduling and dispatching. |
| : : Provision date | The delivery date specified on the order item is used as the end date for scheduling and dispatching. |
| : : Production date | The production date specified on the order item is used as the end date for scheduling and dispatching. |
| : Daily date determination | - |
| : : First working day in period | As the Gantt chart plans on the basis of daily data, the dates specified as a period (e.g. a delivery date specified as a calendar week) must be converted to a daily date. This option is used to select the appropriate conversion method. Starting from the start of the period (calendar week = Monday, month = 1st of the month, etc.), the first working day found is used as the planned day, going forwards into the future. |
| : : Middle working day in period | Starting from the centre of the period (calendar week = Wednesday, month = 15th of the month, etc.), the working day found first is used as the planned day going forwards into the future. |
| : : Last working day in period | Starting from the end of the period (calendar week = Sunday, month = last day of the month, etc.), the first working day found in the past is used as the planned day. |
| Start date | |
| : : Equate earliest with latest start date for stock parts | As the preset procurement time for stock parts is 1 day, this option equates the earliest - and therefore also the latest - start date 1 day before the earliest=latest end date when scheduling stock parts. |
| Production order | |
| : Explode routing | - |
| : : automatically with capacity check | |
| : : automatic | If the production order is created for the parts to be produced, the routings should be exploded automatically. If this option is selected, you can also specify whether the production order should then also be posted in terms of capacity. |
| : : manual | If the production order is created for the parts to be produced, the routings should not be exploded. This is the case, for example, if no routings have yet been created. |
| : Post capacity requirements | - |
| : : automatic | If the "Explode routing automatically" option has been selected, you can also specify here whether the production order should be posted to capacity after explosion. |
| : : manual | Although the "Explode routing automatically" option has been selected, the production order is not posted directly to capacity. |
| : Advance requirement | - |
| : : Do not consider advance requirements | Any advance requirements created are not offset. |
| : : Status check (at least the technical release must have been issued) | Activates the check of the status of the advance requirement items that are to be taken into account for production parts. At least the technical release for the advance requirement must have taken place. Otherwise an error message appears. |
| Presettings | |
| Global presettings | Default options |
| : User preferences | The user default settings can be saved via the context menu. |
| Button | Button description |
|---|---|
| OK BUTTON | The settings are saved and the window is closed. |
Single disposition
In this window, a single entry of the entire part request is processed.
| Menu item | Menu description |
|---|---|
| Edit | - |
| Dates | - |
| : : Set | |
| : : Delete |
| Field | Field description |
|---|---|
| Order | Output of the number of the FIRST primary order (for information). |
| Part | Output of the part number. |
| Designation | Output of the part designation. |
| Quantity | Output of the quantity. The button behind it is used to activate the quantity for editing. |
| Disposition | Disposition type of the part. Can be changed here for the individual part. If a part is not required at all, the quantity must be set to zero here. The MRP type Not required is only assigned automatically for parts that are not required. |
| Procurement time | Procurement time of the part. Can be adjusted manually here after the automatic run of the procurement time determination. |
| Earliest start | Manual maintenance of the scheduling |
| Latest end | Manual maintenance of scheduling |
| Button | Button description |
|---|---|
| OK BUTTON | The changed entries are saved. |
| Close | The window is closed. |
Disposition structure
| Menu item | Menu description |
|---|---|
| Options | - |
| : Parts without disposition | - |
| : : Do not display | Parts without disposition are not displayed |
| : : Display | Parts without disposition are displayed |
In this view, the entire MRP structure of the (sub)parts actually required for a part selected in the list view of the part request is displayed. As it is only known which parts are actually required after MRP, this MRP structure can only be called up after MRP. Optionally, you can only select whether you also want to display the parts "without MRP".
The part number, the description, the required quantity, the MRP type and - in the case of multiple use - the number of parts in which the corresponding part is included are displayed. Double-clicking on an entry within the tree takes you directly to the corresponding entry in the list view, where you can also display any multiple use (in the higher-level parts). (If parts are not displayed in the list view, please check the display options)
Cancellation of part requests
By cancelling a requirement trigger document (stock order, sales order, advance requirement), the part request must also be cancelled so that the requirement no longer appears in the MRP account.
When a part request is cancelled, all successors in the part request are also cancelled, e.g. in the case of production orders, all items that belong to it are cancelled.
The following rules apply to cancellations, which are shown schematically here:
| Procurement type | ..is stopped and can be found in loggicid | ...is cancelled |
|---|---|---|
| Warehouse reservation | Goods removal document already created | No stock removal document created yet |
| Production order | has started AFO or already has a staged quantity. Successors are only cancelled if the cancelled quantity is greater than the staged quantity of the production order. These are cancelled in proportion to the difference. | has no started work sequences |
| Purchase requisition | an order has already been created | No order has been created yet |
Calculation of the remaining quantity for shortages in completed stock orders
If a stock order item is marked as completed before the complete quantity has been put away, the remaining quantities are written to the cancelled.quantity slot and the status of the stock order item changes to "put away".
To cancel a warehouse order item early, a partial quantity must be created via a posted goods receipt. On the one hand, there is the option of reporting the warehouse order as complete with a minimum quantity by ticking "Cancel remaining quantity"; on the other hand, there is the option of doing the same in the warehouse order item itself using the traffic light.
If a partial quantity for a warehouse order item is put away and the traffic light is then switched from green to red, the warehouse order item is not stopped or cancelled, but marked as complete.
In both cases, the system branches to a cancellation document. Only after this cancellation document has been posted is the remaining quantity cancelled and the order status changed to completed or cancelled.
All Gozinto items are also adjusted and the remaining quantity is written to the cancelled.quantity slot.
If several parts lists have been combined when creating the Gozintograph and only one parts list item is to be stopped, cancelled or reported complete, then the quantity of the item to be cancelled must be determined proportionally. The following graphic is helpful for this:

Subsequent change of the disposition type
If, for example, a part originally planned as an order part is to be converted to a production order after the part request has been released, existing production orders, material withdrawals and purchase requisitions may change.
For this reason, it is not easy to change over a planned part request item.
The first thing to check is whether existing part request items will be changed/added as a result of the changeover.
This is done via the context menu of the list.
- The entry to be converted is marked in the part request and the context menu is opened with the right mouse button.
- Here, the entry"Change check MRP type" is expanded and the sub-item "Production order" is selected.
- A results window appears, which contains all newly added or existing changing part request items. It shows the original and the newly determined quantity, as well as the statuses before and after the simulated changeover. This makes it possible to check in advance what further changes are to be expected:

The tested item previously selected in the list appears at the top as the initial object. If a previously "dormant" part request item (old status "Not required") is now required,"New part request item" appears in the first column on the left. If the part request item already existed,"Changed part request item" appears here.
If no existing part request items with an MRP type material withdrawal, purchase requisition or production order have been changed, the item can be changed without hesitation.
In the example above, no critical changes can be seen, the only changed parts requirement items were and are set to "No MRP".
The"Hide not required" checkbox is used to control whether the "sleeping" parts request items that are not required even after the simulated changeover are also displayed or not.
However, if parts request items that have already been processed are changed, further quantity changes are necessary. The MRP controllers of the existing purchase requisitions may need to be contacted in order to adjust the quantity to be ordered and coordinate the quantities and dates with the supplier. In the case of production orders, existing production documents must be collected and reprinted. These scenarios are not yet implemented in ClassiX®, the changeover is cancelled via an error message. - More on this later...
If the disposition type is now changed, exactly the same part requirements are created that were previously visible in the preview window. At present, only a subsequent changeover from purchase requisition to production order is supported.
The new part request items are not yet scheduled, which must be done manually via the graphical scheduling.
The lead times of the new part request items should be reset beforehand. This is currently done automatically when switching the MRP type.
If the end dates are correct again after the adjustment, the project is updated via the "Edit"-"Update project" menu and the dates are written back.
Surplus quantities and splitting
If a quantity of a standard MRP part is still available in a warehouse, e.g. because the requirement of an original requirement trigger has been reduced or cancelled completely, this stock quantity (the so-called surplus quantity, see also " Check material surpluses" in the Gantt chart for part requirements) should be used up as quickly as possible. Surplus quantities can also arise if a part that was initially stocked is switched to "MRP": any quantities still in stock at this time are then also treated as surplus quantities by the system.
ClassiX® offers the functionality to take surplus quantities into account when creating the Gozintograph. For this purpose, an option "Automatically consume surplus quantities" is available in all option windows for creating a Gozintograph. If this option is set, an additional - initially unposted - warehouse reserve document is immediately created for each recognised surplus quantity when the MRP type is determined. This document serves as an identifier for the reservation of the surplus quantity for the order(s) processed in the Gozintograph.
The stock quantity is only actually reserved for the processed order(s) when the stock reserve document is posted. This posting is triggered either manually by the user or by the further processing of the Gozintograph (e.g. by executing "Create first purchase requisition" in the case of surplus quantities of purchase requisitions). The posting fails if another user has already used these surplus quantities while the Gozintograph is being processed.
If a surplus quantity is recognised and posted for a production order, all secondary parts requirements subordinate to this production order are automatically reduced by the corresponding quantity. If, for example, 1000 screws are required for a production order of 100 pieces, but 20 pieces are withdrawn from the warehouse as a surplus quantity, the quantity of screws withdrawn is automatically reduced to 800 pieces. The quantity of screws no longer required (200 pieces) is marked as a cancelled quantity in the parts request item for the screws (for final posting, see above).
If surplus quantities are taken into account in parts request items (production order or purchase requisition), this has no effect on the scheduling (e.g. in the Gantt chart) of the corresponding parts request items: it is assumed that the respective surplus quantity is available "immediately", the lead time of the parts request item is only based on the "main MRP", i.e. the lead time of the production or order part.
This splitting (of part dispositions) can not only take place automatically in the event of surplus quantities, but can also be triggered manually in the Gozintograph via the "Secondary disposition" menu selection. For example, a partial quantity can be ordered in the event of bottlenecks in production or, conversely, a partial quantity can be produced by a supplier in the event of delivery bottlenecks. In the latter case, however, the main MRP must be the production order - due to the secondary MRP - with the purchase requisition as a secondary MRP.
Which secondary MRP can I create for which main MRP?
The following table illustrates this:
| Main disposition\Additional disposition | Production order | Purchase requisition | Material withdrawal |
|---|---|---|---|
| Production order | - | ||
| order request | - | - | |
| Material removal | - | - |
This table shows all secondary disposition types. Here are a few examples and an explanation:
The left-hand column shows which main MRP type is on the part request item. In the columns to the right of this, the respective line shows which secondary MRP type can be created. It is clear that a secondary MRP "production order" cannot be created for any main MRP; only a purchase requisition and/or a warehouse return document can be created as a secondary MRP.
Since - as already explained above - the scheduling of a restocking document is irrelevant, only the additional MRP items that are purchase requisitions (replenishment lead times) need to be taken into account when scheduling a collective order. As can be seen from the table above, this only applies to the main MRP "production order" and "material withdrawal":
- If the main MRP is a "material withdrawal", only the auxiliary MRP (= purchase requisition) is taken into account during scheduling
- If the main MRP is a "production order", an additional date bar is displayed in the Gantt chart: one - as usual - for the original part request item of the production order and an additional date bar for the secondary MRP "purchase requisition". This means that the scheduling can be set independently of each other.
Rescheduling
See also operating calendar
A parts request that has already been started can be rescheduled in the same way as a parts request that has not yet been started.
Please note that the release of the part request must be cancelled before each change (set traffic light to red)!
To do this, select "Edit - Scheduling - Graphical - Rescheduling" or "Edit - Scheduling - Graphical - Backward/forward scheduling" from the menu and reschedule the part request.
After rescheduling, all follow-up documents that may exist for the individual part request items must be checked to ensure that the dates still match, as the dates of the follow-up documents (production order / requirement request) are not automatically adjusted during rescheduling.
To find out which parts request items have changed after rescheduling, a list showing all changed parts request items is opened after "Update project" in the graphical scheduling.
This window can be opened again at any time after closing via the menu item"Edit - Check - Changed dates".
If the appointments are now to be transferred to the follow-up documents, select the respective entry from the list and open the context menu with the right mouse button. Here you will find the entry "Transfer dates to follow-on documents". The latest end of the part request item is adopted as the date for the follow-on documents.
Please note that the work sequences are only adjusted to the end date (the work sequences are shifted by exactly as many working days as the end date of the part request has shifted)!
If the duration of a production order has been changed via graphical scheduling, the routing is not automatically extended! This must be done manually afterwards! (The system cannot know which work sequence now takes longer or which work sequence has been added!)
- For production orders, the cancelled routing is booked out, changed and booked in again. If the production order item has already been printed, it is given a "repeat print" indicator and can be found again via the worklist. If the production order item is printed again, this indicator disappears again.
- For requirement requests that have already been ordered, the date on the order item (delivery schedule) must first be adjusted. If this is not done before the transfer, a cancellation message appears stating that the order must first be changed to the date xx.xx.xxxx. If the order date has been adjusted, the date can be transferred to the purchase requisition.
Material withdrawals whose dates have changed are ignored when the list of changed dates is reopened. Material withdrawals do not have a follow-up document and therefore do not need to be handled separately. When this list is opened automatically for the first time, directly after rescheduling from the graphical view, these material withdrawals also appear in the list, as all changed part request dates are generally displayed here at this time.
Changing the lead time
With this dialogue it is possible to increase the total throughput time for the Gozintograph and to distribute this as a percentage of the throughput times of the parts on the individual positions of the Gozintograph.
However, the throughput times of individual work sequences of the production orders do not change, only the earliest start date and end date are changed. This gives the individual cost centres/work centres more time to process the order and can therefore avoid peaks.
| Field | Field description |
|---|---|
| Data | |
| : : Current | Current data (this is only displayed and cannot be changed). |
| : : New | Depending on the "Base" selected, either a different start or end date (as a starting point) can be entered (from which a new lead time is calculated) or a new lead time is entered, from which a new start or end date is calculated (depending on the "Base" selected). |
| : : Diff. (days) | Difference in working days between the respective date in the "Current" column and the date in the "New" column |
| : : Base | The selected line is the calculation basis for the changes, i.e. either the start date is the basis - in which case a new end date can be entered - or the end date is the basis, in which case a new start date can be entered. The entry in one of the fields requires the recalculation of one of the other fields, e.g. if you change the lead time with a fixed start date, the end date is recalculated and output. |
| : : Is | After the calculation, the possible result appears here. |
| : : Start | Start date - the earliest start date of the gonzitograph. |
| : : End | End date - the latest end date of the Gozintograph. |
| : : Lead time days | The respective lead time in days. |
| Work centres | If a work centre is selected in the list, the work steps within this work centre are displayed in the lower list. |
| : : Number | Unique identification of the work centre / resource. |
| : : Description | Description of the work centre / resource. |
| : : Start | Start date as calendar week. |
| : : - New | New start date as calendar week. |
| : : End | End date as calendar week. |
| : : - New | New end date as calendar week. |
| : Work sequences | |
| : : | Work sequence number |
| : : Start date - old | previous start date. |
| : : Lead time - old | Previous lead time |
| : : Start date - new | New start date |
| : : Work plan | Identification of the work plan. |
| : : Description | Description of the task list. |
| Button | Button description |
|---|---|
| Calculate | The new start and end dates for all entries in the part request are recalculated using the new data entered. In addition, the newly calculated start and end dates for the work centres of the production parts are displayed in the list of work centres. |
| Accept | The newly calculated start and end dates are transferred to the part request. |
| Menu item | Description |
|---|---|
| Edit resource | |
| Worklist | |
| Capacity overview | |
| Capacity utilisation | |
| Display current scheduling | Display of the gonzitograph |
Own provision
If, for example, a "brick lining" service is ordered from a supplier, in which this supplier is to install something in a finished assembly (brick lining), the construction of the assembly must take place before the brick lining is ordered.
The parts list must therefore look like this:
Order part "brick lining" has the following parts list entries in its production role:
- Assembly A
- Assembly B
Assembly A must be provided to the supplier so that the supplier can perform the ordered service. Assembly B is provided by the supplier.
The parts requisition therefore contains the brickwork with the procurement type "purchase requisition".
However, a production order must now be created below this purchase requisition so that the assembly is completed on schedule before the brick lining is ordered:
There are two options for this:
- Assembly A is generally a part that must always be manufactured and provided. In this case, simply set the procurement type in the logistics account of the part to"Own provision: MRP". In the case of "Own provision: warehouse", it is assumed that this part is in stock and the resulting part request item is automatically set to "Material withdrawal".
- Assembly A is only an in-house provision in this case: The option "Show all parts (without MRP AND unused)" must be set in the parts request (options window via menu item "Options" in parts request). The list is then sorted by part number and assembly A is selected.
All parts that are not required or not planned are then also displayed. The system now searches for the part to be provided and switches its main MRP type to the corresponding in-house provision (production order, purchase requisition or material withdrawal). An in-house provision document with all the required data is created immediately. The items in the parts request that are not required can now be hidden again using the options. Depending on the standard procurement type, a production order, a purchase requisition or a stock reservation is now created for this item and its required sub-items when the parts request is processed further.
For information on the further course of in-house provision , see here.
List window
Used to list or search for part requests (gozintographs).
All transaction types that exist in the ClassiX® system can be dragged into the list with the mouse.
If there is a follow-up part request for the item dragged into the list, or for one of its sub-items, these are displayed in the list.
| Menu item | Menu description |
|---|---|
| Edit | - |
| Successor | - |
| : : Generated production order | If a production order has already been created for the selected part request, it is opened |
| : : Generated purchase requisition | If a requirement request has already been created for the selected part request, this is opened |
| : Predecessor | - |
| : : Triggering part disposition | The sales order items for which the selected part request was created are displayed in the part MRP list. |
| Tests | Obsolete functions, no longer use! |
| : : Predecessor parts | |
| : : Full part number | |
| : : Quantity | |
| : : Disposition status | |
| : Service | - |
| : : Body/order numbers | |
| : : Index | - |
| : : : Form | |
| : : : Delete | |
| : : Repair release |
| Icon | Toolbar description |
|---|---|
| Edit part request | |
| Print part request | |
| Copy all part requests to the clipboard |
| field | Field description |
|---|---|
| Number | Search by number. If no number is entered, the last 100 part requests are listed |
| 1st order | Search for part requests that are follow-up documents to the order entered. If no order number is entered, the last 100 part requests are listed |
| Not released | The "Display" button can be used to display all the part requests that have not been released |
| Date (created) | Search for part requests by creation date |
| Date (released) | Search for part requests by release date |
| Processor | Search for part requests by processor. The two radio buttons next to the "Processor" button can be used to select whether to search for the creation or release processor. |
| Button | Button description |
|---|---|
| Edit | The current part request is displayed in the main window. |
| Close | The window is closed. |
Selection window
This window is used to select part requests (gozintographs).
| field | Field description |
|---|---|
| Number | Search by number |
| 1. order | Search for order |
| Button | Button description |
|---|---|
| OK BUTTON | The selected part request is accepted. |
| Close | The selection is cancelled. |
Automatic termination
Automatic scheduling offers the option of scheduling the entire part request either forwards from a start date or backwards from an end date.
This type of scheduling simulates the resulting work sequences, if they have not already been resolved, and plans these into the actual utilisation of the resources in order to find bottlenecks.
In addition, the automatic scheduling window can be used to check whether parts are/will be available on the specified date. Bottlenecks (material or capacity) are pointed out or automatically avoided by rescheduling. It is also possible to clear the remaining bottlenecks later in the manual graphical scheduling.
There are two options for bypassing bottlenecks, i.e. workplace-specific public holidays or insufficient capacity:
| : Seamless scheduling in the event of bottlenecks | Ticked: If a bottleneck occurs for a work sequence, not only is the deadline for this work sequence postponed, but the entire planning is postponed by one week until all the necessary work can be completed in one go. Tick not set: If a bottleneck occurs for a work sequence, only the deadline for this work sequence is postponed, so that the total lead time for the production order is extended by a certain waiting time. Ticking this box may result in an earlier finish date if there are bottlenecks for some resources. This scheduling is particularly suitable for stockpiling orders, whereby the scheduling only fills the open "gaps" in capacity utilisation. |
The scheduling options set are saved on the part request item (seamless scheduling and avoid bottlenecks).
If a further work sequence is subsequently added to a production order, it is scheduled with the same settings as the entire parts request before it.
Note: The operating calendars of the individual work centres or production areas are taken into account during scheduling. For example, it is possible to fully schedule the welding shop in the first calendar week of the year, whereby all other production areas are free at this time.
After automatic scheduling, a message appears indicating whether the planned delivery date could be met, and information on capacity and material bottlenecks will also appear in the list in the scheduling window.
More about rescheduling and the general scheduling of the necessary provision of parts.
| Icon | Toolbar description |
|---|---|
| Print window | |
| Display stock movements | |
| Show stock | |
| Show dispo movements | |
| Show logistics account | |
| Edit workplace | |
| Worklist | |
| Graphical representation of the utilisation of the selected resource / calendar week | |
| Capacity overview | |
| Capacity utilisation of the selected resource | |
| Copy all list entries to the clipboard |
| Field | Field description |
|---|---|
| Direction | |
| : Backwards | Scheduling starts with the date entered as the latest end date and subtracts the individual lead times until start dates are reached for the individual production stages. |
| Forward | Scheduling starts with the date entered as the start date of the lowest stages and adds the lead times until a finish date for stage 0 is reached. |
| Start or end date | This date is used for scheduling. Either as the start date for forward scheduling or as the end date for backward scheduling |
| General | |
| : Seamless scheduling in case of bottlenecks | Ticked: If a capacity bottleneck or a production site-specific public holiday occurs for a work sequence so that the work sequence cannot be processed in the planned calendar week, not only is the deadline for this work sequence postponed, but the entire planning is postponed by another week until all the necessary work can be processed in one go. Tick not set: If a capacity bottleneck or a production site-specific public holiday occurs for a work sequence so that the work sequence cannot be processed in the planned calendar week, only the date for this work sequence is postponed, so that the total lead time for the production order is extended by a certain waiting time. By ticking this box, the end date can be brought closer if there are bottlenecks for some resources. |
| Material (ATP) | |
| : Check material bottlenecks | During scheduling, the system checks for material bottlenecks. Any bottlenecks found are then displayed in the results list of the scheduling window. The checked, uncorrected bottlenecks are marked with a red stop sign in the list. |
| Capacity (CTP) | |
| : Check capacity bottlenecks | For production parts, the system checks whether all work at the production centres can be carried out on time at the defined workstations (capacity check - CTP). If no routing has yet been cancelled for the part request item, this is simulated. The bottlenecks found are then displayed in the results list of the scheduling window. The checked, uncorrected bottlenecks are marked with a red stop sign in the list. |
| : Automatically avoid capacity bottlenecks | Any capacity bottlenecks found are bypassed by postponing them by one week until sufficient capacity is available (see also option "Seamless scheduling in the event of bottlenecks" here in the table. Public holidays at specific work centres / production sites are always bypassed regardless of this option. |
| : Automatically adjust exploded production routings | The determined dates are transferred directly to the exploded routing items, eliminating the need for subsequent adjustment. This option is only active if there is already an exploded production routing! |
| Results list | The bottlenecks that have not been resolved are displayed here with a red stop sign and those that could be bypassed with a green tick. |
| Button | Button description |
|---|---|
| OK BUTTON | Starts the termination with all set parameters |
| Close | Closes the window. |
Required capacity
This window provides an overview of all required workstation resources in the respective calendar weeks.
The system simulates the requirements and adds them to the actual current requirements, even for work schedules or production orders that have not yet been cancelled.
| Icon | Toolbar description |
|---|---|
| Print window | |
| Edit workplace | |
| Worklist | |
| Graphical representation of the utilisation of the selected resource / calendar week | |
| Capacity overview | |
| Capacity utilisation of the selected resource | |
| Copy all list entries to the clipboard |
| Field | Field description |
|---|---|
| List | All resources required for the part request are displayed with the calendar week in the list. The planned, required and already booked capacity is displayed, as well as a green box if there is sufficient capacity for the planned work sequence, or a red bitmap if the capacity for the planned work sequence is no longer sufficient |
| Button | Button description |
|---|---|
| Close | The window is closed |
Related topics
- index
- Change management in general
- Change management: Change quantity of part request item
- Gantt chart
- Operating calendar
- Parts disposition
- Technical release
Technical documentation
- preConstraints-postConstraints Connections of the part request items to each other
- Overview
- Implementation
- Quality Assurance
preConstraints-postConstraints Connections of the part request items to each other
The connection in a part request between the items below (to be planned before me) and above (to be produced with me after me) is made by the connection preConstraints (before me) and postConstraints (after me).
This connection makes it very easy to determine for which part request item another part request item is required.
It is no longer necessary to go through the complicated parts list predecessor item.
If a part request item is to be cancelled, all part request items that are to be planned before this item must also be adjusted in the correct quantity ratio (or cancelled if the cancelled item is the only predecessor) - these can now be determined very easily.
If a part is required at several points in the parts list across several production levels, it always appears at the lowest level in the parts request, as these are planned first (it is double-wired via postConstraints!).
Example:
A fan to be manufactured in-house is to be installed in a control cabinet.
M6 screws are required for both the switch cabinet and the fan (they are available in both parts lists).
The parts lists look like this:
Switch cabinet:
- 4 support strips
- Metal cabinet
- 50 M6 screws
- blower
Blower:
- motor
- Regulator
- Fan wheel
- Housing
- 20 M6 screws
A total of 70 M6 screws are therefore required. The same parts are grouped together in the part request (e.g. so that the same production order is not created 3 times for the same part). It is therefore necessary to procure the screws in their entire quantity at the earliest possible date, i.e. at the time the blower is manufactured. The part request item appears with the highest required level and is also scheduled this early.
Technically, the part request item of the M6 screw is now linked to 2 post constraints, namely that of the blower and that of the control cabinet.
If the fan is now cancelled via the parts list, the parts request item of the screws is reduced in quantity and moved directly below the level of the control cabinet.
Overview

Parts request basic module
Module name
cxItemDemand.mod
classes
security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | security |
|---|---|---|---|
| ITEM_DEMAND_CHANGED | Part request object | Part request has been changed | |
| ITEM_DEMAND_CREATED | Part request object | Part request was created | |
| ITEM_DEMAND_DELETED | Part request object | Part request was deleted |
| Message | Parameters | Function | Receive module |
|---|---|---|---|
| EDIT_ITEM_DEMAND | NULL or part request object | Call up input window for part request | Part request editing module |
Part request editing module
Module name
itemDemandEdit.app
classes
security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | security |
|---|---|---|---|
| DELETE_ITEM_DEMAND | |||
| EDIT_ITEM_DEMAND | NULL or part request object | Call up input window for part request | |
| ITEM_DEMAND_CHANGED | Part request object | Part request has been changed | |
| ITEM_DEMAND_CREATED | Part request object | Part request was created | |
| ITEM_DEMAND_DELETED | Part request object | Part request was deleted | |
| LIST_ITEM_DEMAND | Collection part request objects or NULL | Call up list window for part request | |
| LOAD_ITEM_DEMAND | Import part request | ||
| PRODUCTION_ORDER_CREATED | |||
| PRODUCTION_ORDER_DELETED | |||
| TMP_DISPOSITION_WIN |
| Message | Parameters | Function | Receive module |
|---|---|---|---|
| APPEND_PURCHASE_REQUISITION | |||
| CREATE_PRODUCTION_ORDER | |||
| DELETE_ITEM_DEMAND | |||
| EDIT_BILL_OF_MATERIAL | |||
| EDIT_ITEM | |||
| EDIT_ITEM_DEMAND | NULL or part request object | Call up input window for part request | Part request editing module |
| EDIT_JOB_SCHEDULE | |||
| EDIT_PRODUCTION_ORDER | |||
| EDIT_PURCHASE_REQUISITION | |||
| EDIT_STOCK_ACCOUNT | |||
| ITEM_DEMAND_CHANGED | Part request object | Part request was changed | |
| ITEM_DEMAND_CREATED | Part request object | Part request was created | |
| ITEM_DEMAND_DELETED | Part request object | Part request was deleted | |
| ITEM_DEMAND_RELEASED | |||
| ITEM_DEMAND_UNRELEASED | |||
| LIST_ALLOCATOR | |||
| LIST_ITEM_DEMAND | Call up list window for parts request | Part request editing module | |
| LIST_ITEM_DISPOSITION | |||
| LIST_ITEM_STOCK_SUB_MONITORS | |||
| SELECT_DISPO_ACCOUNT_LOGGINGS | |||
| SELECT_STOCK_LOGGINGS | |||
| SHOW_PREVIEW | widget | Print preview | Print preview |
| TMP_DISPOSITION_WIN |
Part request selection module
module name
itemDemandSelect.app
classes
security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | security |
|---|---|---|---|
| ITEM_DEMAND_CHANGED | Part request object | Part request has been changed | |
| ITEM_DEMAND_CREATED | Part request object | Part request was created | |
| ITEM_DEMAND_DELETED | Part request object | Part request was deleted | |
| SELECT_ITEM_DEMAND | Collection part request objects or NULL, recipient of the response | Call up selection window for part request |
| Message | Parameters | Function | Receive module |
|---|---|---|---|
| EDIT_ITEM_DEMAND | NULL or part request object | Call up input window for part request | Part request editing module |
| ITEM_DEMAND_SELECTED | Part request object, recipient | Part request was selected |