Material requirements forecast (disposition account)
Description
The documents posted in the MRP account and certain data from the logistics account are displayed. Only open documents that represent planned receipts or issues should be posted to the MRP account (for example: open planned receipt: purchase order item not yet (completely) ordered, production order item not yet reported as completed, etc.; open planned issue: order item not yet (completely) delivered, parts request item not yet (completely) withdrawn, etc.).
Based on the current stock level, the documents in the MRP account represent the future (planned) stock development in the date sequence. The stock level can fall below the minimum stock level for the respective part at any one time or even become negative. Such situations (minimum stock shortage, reorder point) are analysed in the requirements and stock list (see also date control).
Attention - Irregularity with exceeded deadlines via the SCM module:
When checking dates in SCM (missing parts list), note that planned receipt documents that are scheduled earlier than today and have not yet arrived are automatically scheduled as a "tomorrow" date!
If an order was scheduled for 6.2.2012 and has a purchase order with the same date, but today is 7.2.2012 and the purchase order has not yet arrived, then the order is classified as a missing part and receives the shortage indicator in the MRP account. This item also appears in SCM as a missing part!
(Technical note: If the variables checkInPastActivated and checkInPastGenerallyActivated are set to TRUE in SetOptions, this control is also active in the normal MRP account and the B&B list with schedule control).
The disposition account can also be called up for individual company codes.
Requirement triggers in the MRP account (requirement triggers reduce the stock):
- Project reservations with the status "started
- Order items
- Advance requirements
- Part requirements (dispositions)
- Stock Reserves
Coverage of requirements in the dispo account (coverage of requirements increases the stock)
Although documents such as goods receipts increase stock, they will never be seen in the MRP account because they do not represent a future movement but already reduce stock when the document is posted.
Parts consumption and parts sales
The dispatch account also shows how often the part has been used in the last year. For consumption, quantities are added up on transaction data in a certain period. The movement data includes goods withdrawals, goods receipts and direct deliveries not put into storage and production orders not put into storage.
For Kanban parts, other evidence for the evaluation of consumption is included, namely the confirmed order items and the further processed part request items of the part. For Kanban parts it is not possible to use the two arrows 
to switch to the parts consumption overview in addition to the parts consumption, as the parts consumption for Kanban parts does not appear in this overview.
Consumption from order items can be viewed via the sales item turnover display.
The other consumptions via processed parts request items can only be viewed via the operation folder of the part.
Functionality
Sorting the documents
The shortfall analysis depends on the assumption of when and "how certain" the deadlines are. For example, if the dates are given as a time span, the "true" date can be determined by making the appropriate selection. Three sorting modes are provided to allow different views of the inventory development:
| strict | Receipt date: end date counts, dispatch date: start date counts | |
| medium | Date of arrival and date of departure are compared "naturally" (e.g. whole calendar week comes after Tuesday but before Thursday of the week) | |
| soft | Receipt date: Start date counts, Departure date: End date counts |
If required from part requests (departure date), the planned date is composed of the earliest and latest start, which also results in a time span.
With the evaluation type "Strict", the earliest date of this time span is always used for the evaluation, with the setting "Medium" exactly the middle and with "Soft" the end of the time span, i.e. there is the least buffer for the real demand.
If planning (e.g. stock replenishment) is always to be carried out with a little air, the setting "Medium" is recommended, which is always set in the standard system.
However, if there is little space in the warehouse or if the warehouse budget is always to be kept as low as possible, the setting "Soft" is recommended, whereby planning is always carried out on the actual demand date.
Strictly means, therefore, that the goods are always already procured at the earliest possible date and may also lie in the warehouse for some time until they are needed, depending on how large the buffer times of the requirements were.
Example (opening stock = 0 pieces):
(Week 13, 2002: Mon=25.03., Tue=26.03., Wed=27.03., Thu=28.03., Fri=29.03., Sat=30.03., Sun=31.03.)
Strict: Ordered goods are always late:
| Type | Open | Access | Disposal | Balance | Date | per date |
|---|---|---|---|---|---|---|
| Disposition | 1 piece | 1 piece | -1 piece | 25.03.2002 | 25.03.2002 | |
| Disposition | 1 piece | 1 piece | -2 pieces | 29.03.2002 | 29.03.2002 | |
| Order | 1 piece | 1 piece | -1 piece | 13. WEEinkauf 2002 | 31.03.2002 | |
| Order | 1 piece | 1 piece | 0 pieces | 13. WEEinkauf 2002 | 31.03.2002 |
Medium: first order comes too late:
| Type | Open | Access | Disposal | Balance | Date | per date |
|---|---|---|---|---|---|---|
| Disposition | 1 piece | 1 piece | -1 piece | 25.03.2002 | 25.03.2002 | |
| Order | 1 piece | 1 piece | 0 pieces | 13. WEEinkauf 2002 | 31.03.2002 | |
| Order | 1 piece | 1 piece | +1 piece | 13. WEEinkauf 2002 | 31.03.2002 | |
| Disposition | 1 piece | 1 piece | 0 pieces | 29.03.2002 | 29.03.2002 |
Soft: everything is fine:
| Type | Open | Access | Disposal | Balance | Date | per date |
|---|---|---|---|---|---|---|
| Order | 1 piece | 1 piece | +1 piece | 13. WEEinkauf 2002 | 31.03.2002 | |
| Order | 1 piece | 1 piece | +2 pieces | 13. WEEinkauf 2002 | 31.03.2002 | |
| Disposition | 1 piece | 1 piece | +1 piece | 25.03.2002 | 25.03.2002 | |
| Disposition | 1 piece | 1 piece | 0 pieces | 29.03.2002 | 29.03.2002 |
The document list cannot be sorted manually.
Display of the current balance; balance check
The balance is carried forward into the future from the quantity available today (available stock + quantity received). The balance is increased with each planned receipt and decreased with each planned issue.
Each time the MRP account window is activated, a balance control procedure is automatically performed for the part. During the check the result of the master calculation formula "AVAILABLE_QUANTITY" (the formula is defined to calculate the "ideal" available quantity of a part, based on data from the stock and MRP account; e.g: Warehouse stock + stock order + In production + Requested + Ordered + GR quantity + QA quantity - In order - Reserved) compared to the calculated final balance (the last balance in the document list). If the results are different, an error message about the difference is displayed; the difference is also shown in red below the list.
It is important to note that the last column on the far right displays the MRP type with which a sales order or gozo item was posted to the MRP account, whether, for example, as a warehouse reservation or as a production order or requisition. This is particularly important if you have stock reservations listed in the B&B list for parts that currently no longer have the staging type, e.g. stock management. Then you can simply find out the document in the corresponding MRP account that was reserved in stock!
If the option "Split variants" is set (see option window), and the part is a variant part, no balance is displayed, but the currently used variation of the variant part. See also variant filter.
Display of the last parts sales
There is another group above the list. It displays the parts turnover of the last 12, 6, 3 and the current month. The button on the right-hand side takes you directly to the parts turnover statistics. The part is automatically selected there and the sales of the last 12 months are displayed in detail.
Variant filter
If the displayed part is a variant part and the option "Split variants" is activated, the corresponding quantities are split in the interim/stock and dispatch quantity lists according to the variation that has occurred. Above these lists there is a small button with a magnifying glass, which opens these lists enlarged. This also allows sorting by variation or individual characteristics. If you double click on one of the lists, a filter is set on the document list, which corresponds to the clicked variation. Only documents with the same variation are displayed in the document list. The documents responsible for the clicked quantity are also marked.
This filter can be changed via the Refresh 
toolbar button again.
If the parts consumption list is opened with a filter set in this way, the filter is transferred and now also applies in the parts consumption list.
Bitmaps in the list
| Bitmap | Meaning |
|---|---|
 | Article is available |
 | Reorder level has fallen below |
 | Minimum stock level has been fallen below |
 | Negative stock |
 | Maximum stock has been exceeded |
| Menu item | Description |
|---|---|
| Edit | - |
| : Update list | Reload data for the dispo account. |
| Part | Opens the part master mask of the corresponding part |
| : Logistics account | Displays the logistics account |
| : Stock movements | Shows the positional movements of the part |
| Navigate | - |
| : -> Document | Opens the currently selected document, corresponds to double-clicking in the list |
| : : -> Reference | Opens the reference document (if any) that appears in the list in the Reference column |
| : : : Disposition for... | Displays the production order items for which the current part must be provided during a disposition |
Show list in new window | Displays the document list of the material requirements forecast in a new window. There you can sort, select and export the list. |
| Perform (partial) cancellation | Cancellation of the entire document or partial quantities with a cancellation document |
| (Partial) supply correction | Concluding a still open part request with a correction document (no cancellation) ! |
Correct the cash on hand | Recalculate the current stock and update the list. All MRP accounts can also be checked and corrected in one inspection run. |
| Close | Close window |
| Menu item | Description |
|---|---|
| Navigate | - |
| -> Document | Opens the currently selected document, corresponds to double-clicking in the list |
| : -> Reference | Opens the reference document (if any) that appears in the list in the Reference column |
| : Disposition for... | Displays the production order items for which the current part must be provided during a disposition |
| Show/hide documents with stored project quantity | Specify whether putaways or goods receipts that were put away directly into a blocked project warehouse (goods belong to project) should be displayed or hidden. |
Show list in new window | Displays the document list of the material requirements forecast in a new window. There you can sort, select and export the list. |
| Perform (partial) cancellation | Cancellation of the entire document or partial quantities with a cancellation document |
| (Partial) supply correction | Concluding a still open part request with a correction document (no cancellation) ! |
| End stopped part requests | Part requests with the status "stopped" can be finalised here without going through change management. |
| Symbol | Description |
|---|---|
 | Display document history |
| Update list |
 | Print transactions |
 | Copy objects to the clipboard |
 | Edit part |
 | The variant overview is opened. This is a list with the variant part and all its sub parts, which creates an overview of all stock levels and MRP movements of this variant. |
 | Display operations |
 | Show logistics account |
 | Display stock movements |
 | Show stock level |
 | Create new purchase requisition for purchased parts with stock management. If a production part has a purchased part role, a purchase requisition can also be created for it. |
 | Extend purchase requisition, see "New purchase requisition...". |
 | Create new stock order for production parts with stock management. If a purchased part has a production part role, a stock order can also be created for it. |
 | Extend stock order, see "New stock order...". |
 | Show purchase items |
 | Show production articles |
 | Show parts usage |
 | Display parts list |
 | Edit work plan |
| Company code | Possible restriction of the data in relation to a selected company code. If this field remains empty, all entries are without restriction to a company code. |
| Field | Description |
|---|---|
| Logistics account | Procurement details of the part |
| Demand Forecast | See Sorting the documents |
| Parts consumption of the | Shows the total consumption of the part in different time periods (variant filter has no influence here!) |
| Interim stocks | Shows the current stock quantities of the part. If the variant filter is active, this filter can also be activated for the document list by double-clicking on a filtered result. Above the list there is a magnifying glass button with which the list can be enlarged. |
| Dispo quantities | Shows the planned quantities received and issued. If the variant filter is active, this filter can also be activated for the document list by double-clicking on a filtered result. Above the list there is a magnifying glass button with which the list can be enlarged. |
| Receipt list | All open receipts and issues of the part. If the variant filter is activated, it is possible that only a subset of the documents is displayed here, depending on the variant. Click on the button "Refresh display to delete the filter again. The filter never sets itself, it is only set by double-clicking on the stock or MRP quantity list. |
Option window
Menu Menu item Description Edit - : Reset default settings Sets and displays the default settings defined via the module
| Field | Description |
|---|---|
| Basic data | |
| zero stocks | Zero stocks of the stock or disposition list can be displayed or hidden. By default these are hidden, except for the actual stock level, which is also displayed if it is zero and all other zero quantities are hidden. |
| : Autom. refresh | Each time the window gets the focus, all the displayed data is determined again. This may take a long time and is therefore deactivated by default. |
| : Split variants | If the displayed part is a variant part, it does not simply show the quantity of this variant part that has been or will be processed in any orders with different characteristics, but an individual sum depending on the variation. See Variant filter |
| Double-click on the quantity list to display the total. | Only required for technical troubleshooting. The displayed quantity is compared via info box with the total quantity of all marked documents. |
Overview of variants
In the dispo account of a variant part, or one of its subparts, there is the possibility to display all subparts of the variant part and itself in a clear list with all its stock and dispo quantities one below the other. By double-clicking on an entry, the MRP account for the selected part is called up, but the list remains in the foreground so that it is easier to click through all the MRP accounts one after the other.
By right-clicking on the list, the minimum, reporting and maximum stocks of the subparts can be changed directly in the list
| Symbol | Description |
|---|---|
| Print list - or copy to clipboard |
| Field | Description |
|---|---|
| Dispatch quantities | This list shows the variant part and all its subparts with their MRP and stock quantities. Double-clicking on an entry calls up the dispo account for the selected part, but the list remains in the foreground so that it is easier to navigate through all dispo accounts one after the other. |
| button | Description |
|---|---|
| Close | The window is closed. |
Related topics
Technical Documentation
FindCritical Date (FindCriticalMoment )
Call:
SendMsg(FIND_CRITICAL_MOMENT)
| here the time period is specified in which the critical moment is sought. 0 - all events are searched, 1 - only events within the replenishment time of the item are searched, 2 + 3 - only events in 2 or 3 times the replenishment time are searched | ||
| or or NULL | When a document is sent, the system only checks what the MRP account would look like without this document. or... when on that day... (control date) | |
| or NULL | ...as much would be withdrawn (control quantity). If a document was passed as parameter, NULL must be passed here! | |
| sorting mode: 0 - strict, 1 - medium, 2 - soft | ||
| Dispatch account | ||
| Widget that expects the response message CRITICAL_MOMENT_FOUND |
The method FindCriticalMoment can be used for two purposes, whereby the way it behaves is determined according to the transfer parameter.
On the one hand, you can check whether a planned retirement is possible on a certain date and what effects this retirement has on the subsequent planning movements. The parameters checkQuantity and checkDate are absolutely necessary. The sorting parameter only evaluates the hard, medium or soft data(see above). Further specifications such as checkToDateLevel have no influence on this method.
What makes the functions? First of all, the test output is sorted into the dispositive movements. This is done on the basis of the date. Then all operations are run through (simulated) once and the effect of the stock change through the test dispatch is analysed. The result of this test is the return code.
What evidence has an influence on the outcome?
Document (stock) | Impact | ||
|---|---|---|---|
| Any one document (stock) before the test | none | ||
| Exactly the stock before the test | Based on the quantity before the test withdrawal, it is analysed whether the sign of the stock changes. (+ -> -
| ||
| The document after the test run | It is analysed whether the test exit has an impact on the stock development after the test date. | ||
| Any document after the test |
| Bit | Statement |
|---|---|
| 0 | Removal O.K. Neither the test withdrawal nor the subsequent documents result in a stock shortfall. |
| 1 | Removal O.K., but at least one of the follow-on documents, which would be pos. without the test issue, causes the stock to fall short. |
| 2 | Removal O.K., but one of the subsequent documents, which has already led to a stock shortfall, causes the stock to run further into negative territory. |
| 3 | Removal NOT possible, because the stock is already negative before the test retirement and therefore continues to run into the negative. |
| 4 | Removal NOT possible, because the stock is positive but runs into negative territory due to the test retirement. |
| 5 | An error has occurred during the calculation! |
Examples: 
| Date | Quantity | returnCode | Declaration |
|---|---|---|---|
| 24.07.2003 | 1 piece | 16 | Withdrawal would result in a negative stock. (withdrawal not possible!) |
| 25.07.2003 | 1 piece | 8 | The test withdrawal is always classified as the last operation of a day if several movements are planned on the same "per date". This means that the stock is already in the negative due to the issue of 1 piece. |
| 01.08.2003 | 1 piece | 7 | - the test withdrawal is possible -> 1.bit set - the stock becomes negative on 25.8. although it would be positive without the test withdrawal -> 2.bit - the stock continues to run negative on 8.3.04 (would otherwise also be negative) -> 3.bit |
| 26.08.2003 | 1 piece | 16 | Removal not possible! (stock was previously positive) |
| 9.3.2004 | 1 piece | 8 | Removal not possible! (stock was already negative) |
Furthermore, this method can be used to check whether and when a minimum stock shortage occurs for a part. This information is also taken from the MRP account. This method makes sense when creating the requirements and stock list.
As return parameters you also get a returnCode and a returnContainer. The returnCode determines the type of underrun. Except in the case that the returnCode is 0 (all o.k.) or 16 (ERROR) the returnContainer contains the following information:
| date | Undercutting date | |
| current.quantity | Balance at the moment of underrun | |
| default.transaction | the document which caused the shortfall | |
| in.quantity | Incoming quantity | |
| out.quantity | Outgoing quantity | |
| purchase.transaction | The document which is to cover the shortfall. |
| 0 | no shortfall (returnContainer is NULL in this case!) | |
| 1 | shortfall before the control date (if no control date: shortfall at the very beginning) | |
| 2 | underrun on the control date (if no control date: underrun sometime in the middle) | |
| 3 | shortfall after the control date (if no control date: shortfall at the very end) | |
| 4 | Unit error |
Flow chart
Quality assurance
Test balance difference
The message CHECK_DISPO_BALANCE_DEVIATION can be used to check whether a dispo account shows a balance difference.
Call:
SendMsg(CHECK_DISPO_BALANCE_DEVIATION)
| Dispatch account | ||
| Widget that expects the response message DISPO_BALANCE_DEVIATION_CHECKED |
DISPO_BALANCE_DEVIATION_CHECKED is sent back to with the following parameters:
| FALSE | no difference | |
| TRUE | there is a difference |
Test FindCriticelMoment
By calling "SendMsg(TEST_CRITICAL_MOMENT)" the functionality of the macro and the interface can be tested via a test window that opens.
To do this, simply enter the corresponding values in the test value group and press Send. The return code is displayed as the result. In addition, the variable "returnContainer" is set so that you also have access to it via the monitor window.
Disposition account Transactions Selection module
Module name
loggidac.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 |
|---|---|---|---|
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
;){kind=link}
;){kind=link}
;){kind=link}