Loading...
 

Inspection - Materials Management

Inspection - Materials management

Description of

This app is used to check data relating to materials management in general. For this purpose, there are inspection runs that are intended to help maintain or achieve a clean and consistent database. Various inspection runs from the entire system are compiled in this app. There is a brief description of the inspection run next to the execute button on the screen.

There are local inspection runs that are executed in the inspection results window and inspection runs that call up other apps and are started or analysed there.

To provide a better overview, the inspection window is divided into various sub-windows. The subwindows are then also divided into subgroups with a more detailed specification of the topic.

Functionality

Selection window

The various inspection runs can be called up from this window.

Some test runs offer the option of limiting the search results to "bearing parts only". The following description can be used as a definition for "bearing part":

  • Part is per staging type
    • stocked
    • Remaining quantity
    • Hand bearing part
  • or the part has a stock
menu
menu itemMenu description
Edit-
: Set default settings
Open result windowCall up result window

Implemented inspection runs (fields and buttons)
FieldField description
Part master
Number of parts-
: : Display number of partsSelection shows number of parts
: Parts registration-
: : Part registration

This test searches for variant parts that cannot be found in the parts master. This condition may have arisen due to technical changes in the system. These parts are then made findable in the parts master and displayed in the results list.

Units-
: : Tables of unitsAll parts with a unit table are listed.
: : Inconsistent tables

Parts are searched for that have an inconsistent unit table. A detailed description of what inconsistent unit tables are can be found here.

: : Booked quantitiesTest searches for parts for which quantities are posted in MRP or warehouse accounts that do not match the part's own unit table or cannot be converted to the standard unit.
Parts organisation-
: : Parts environmentPart environment test
: : No provisioning type

Test searches for parts for which it has not yet been determined whether the part should always be in stock or should be ordered when required. The possible setting options can be found here.

: : No logistics KZTest searches for parts for which it has not yet been determined whether they are to be purchased or manufactured in-house. The result is displayed in the window.
: : No use of parts

All parts are searched depending on whether they are either not used in any master parts lists or have never been used in an exploded production parts list. The result is displayed in the window.

: : Duplicate lower partsTest searches for subparts that exist several times in the variant part in the attribute specification.
Part validity-
: : Invalid partsSearch for invalid parts (window)
: : Invalid parts in parts listsSearch for invalid parts in master parts lists (window)
: : Valid storage binsInvalid parts with valid storage bins (window)
Parts master II
Attributes-
: : Incomplete attributesCheck all subparts/sales reels/assembly set items of variant parts for complete attributes
: : Incomplete sales set attributesTest for sales set items with missing attributes compared to the sales role
: : Attributes with default valuesTest searches for variant parts that have attributes with value specifications
: : Parts without weightTest searches for parts without weight. The first step is to check whether the units table of a part contains a weight conversion; if this is not the case, the part is searched for an attribute with the name "weight". If both fail, the part is output as a part without weight.

With the specification "Only parts with sales roles", only those parts are checked that have any sales role (sales item, spare part, special sales part, etc.). This can be used, for example, to ensure that sales items in a delivery note always have a weight.

Service items (CX_SERVICE) are excluded from this test

: : Deviation attributesTest searches for lower parts with deviations of attribute values between lower part and roll
: Product numbers-
: : Commodity codes usedTest collects all specified commodity codes from the parts master. Each commodity code is only output once. If the identifier "per part class" is set, each combination of part class and commodity code is output - also only once in each case
: : Missing commodity codesTest checks all commodity codes specified in the part master against the commodity code register of the Combined Nomenclature. Parts without commodity codes ("Skip parts without commodity codes" switch off) and all parts individually ("Output missing commodity code only once" switch off) can also be output.

If no commodity codes have yet been entered in the Combined Nomenclature register, you can use this run to output all commodity codes used in the parts master - and therefore missing in the register - as an Excel file. This file can then be read in again in the Combined Nomenclature module under the Maintenance menu item and supplemented there with the data from the SOVA master file.
Part rolls
Production parts-
: : No production rollThe system searches for production parts defined by logistics indicator for which no production role (production data) has yet been created. All required data such as manufacturer costs, material costs, replenishment times and so on are saved in the production role.
: : Multiple production rolesThe system searches for production parts defined by logistics indicator for which more than one production role has been created.
: : No parts listTest searches for production parts that do not have a parts list or routing
: : No preliminary costingTest searches for production parts that have not had a preliminary cost estimate since the specified date
: : Long lead timeTest searches for production parts that have a longer lead time than the value from the input field or an invalid value.
: Order parts-
: : No order part rollThe system searches for order parts defined by logistics indicator for which no order items (purchasing data) have yet been created. Each order part should have an order item role in which the procurement data such as replenishment time (delivery periods), prices, supplier agreements (special prices for some suppliers...) are defined.
: : Several order item rolesThe system searches for order parts defined by logistics indicator for which more than one order item role has been created.
: : No A-supplier

The system searches for order item roles for which one or more supplier agreements have been defined, but for which no supplier has been selected as the main supplier.

: : No purchasing areaTest searches for order parts that are not assigned to a purchasing area.
: : Search for order itemsTest searches for order parts for which the lot size differs between the standard procurement data and the A-supplier.
: Sales article-
: : Sales article testsOpen sales article window with further test options. (window)
Spare parts-
: : Spare parts testsOpen spare parts tester with further test options. (window)
: Validity-
: : Valid rolesTest searches for valid roles from invalid parts.
Part cost
: Roll prices-
: : No standard priceTest searches for parts whose main role, defined according to the logistics indicator, does not contain a standard price or this is zero.
: : Incorrect price table

Test searches for order item roles whose price table does not provide a price for the standard order quantity. This is an organisational error that should be avoided. For standard calculations where no current quantity is available, the price is determined using the standard order quantity. If this price is then zero because there is no table entry for this quantity, this calculation can only be included in the valuation with the value 0EUR.
The output takes place in an extra window.

: : Incorrect price unitTest searches for order parts and sales parts for which the price units do not match the standard order quantity.
: : Incorrect cost tableTest searches for production parts for which the cost tables do not match the lot size.
: : Incorrect overheadsTest searches for production parts for which the overheads are missing or have been overwritten by a different price.
: : Standard quantity is zeroTest searches for order item and production roles that contain a price table but whose standard quantity is zero. In this case, the most expensive price would always be determined when determining the standard price, although this part is always ordered 2000 pieces at a time and would therefore result in a much lower price. For parts without a price table, this does not matter because the price is always the same for each quantity.
: : Bottom part without priceCockpit run for subparts that share the order item role of the variant part and for whose characteristics there is no price or a price that is incompatible with the standard unit of the part. The test run can be called up from the part master for all selected parts or from the cockpit for all subparts of all valid variant parts
Update standard price order item-
: : Update standard price- Updating the standard price in the order item with the current A-supplier or just checking how the standard price would change or whether one is available at all.
- The search can be limited to parts that have a stock location.
- A distinction is made between the following cases :
CaseMessage textMessage description
01No supplier dataThere is no A or B supplier in the part's order role or no supplier can be found via the movement monitor.
02No price on supplier dataThere is no price in the supplier data
03Part has no standard order quantityOrder item has no order quantity
04Old price conditional table, new price simplePrice is transferred to standard price
05Old price simple, new price conditional tableTable is transferred to standard price
06Old price table, new price table - different columnsTable is transferred to standard price
07Old price table, new price table - same columnsTable is transferred to standard price
08Old price single, new price singlePrice is transferred to standard price
09No old price
10New price would be zero!No price is transferred to the standard price
11Old price simple, new price table, no price for batch sizeNo price is transferred to the standard price
12Old price simple, new price table, price for batch size found!Price for the batch size is transferred to the standard price
13Old price simple, new price table, no quantity-dependent price table!No price is transferred to the standard price
14Old price table, new price table, old table is not a quantity-dependent price table!No price is transferred to the standard price
15Old price table, new price table, quantity-dependent price table, entry for batch size available, transfer as entry to existing price table!Price for the solution size is entered in the existing table.
16Old price table, new price table, quantity-dependent price table, NO entry for lot size available, NO price transfer!No price is transferred to the standard price
17No new price availableA CX_PRICE_DISCOUNT object was found, but no price could be determined.

Options:

  • Only parts without invalidating prices
    If a new price has already been defined for a part (current price becomes invalid), then these parts are not to be considered by this run.
Stock
Bearing-
: : Negative stockTest searches for warehouses that currently have negative stock.
: : Invalid stock. StockTest searches for invalid warehouses that still have positive or negative stock.
: : Warehouse without inventoryTest searches for storage locations for which no inventory has been taken since the date to be entered. As an option, all invalid warehouses can be ignored during the test. (Info: Only storage bins without stock can be set to invalid).
Storage bins-
: : Storage bin numbers controlSearch checks all storage bins for multiple allocation of the number within a warehouse or whether the storage bin has no number. The storage bins found are displayed in the results window.
: : Empty storage bin numberThis reorg sets empty storage bin numbers to the number of the warehouse if the number of the warehouse has not yet been assigned to another storage bin in the warehouse and the warehouse does not have several storage bins without names. After completion, the processed objects are displayed in the results window. It is recommended to start the "Storage bin number check" run before reorganising. If the "Also correct afterwards" checkbox is not ticked, only objects found are displayed. The tick is set when the window is opened.
: : Empty storage bin accounts without movement in the lastThe system checks the stock levels of the storage bins. If the stock = 0 and the last movement was longer than the specified period, the direct link to the storage account of the part is removed. This speeds up the search and display in the stock lists. No movement data is lost in the process.
: : Empty project storage bin accounts without movement in the lastThe system checks the stocks of the project storage bins. If the stock = 0 and the last movement was longer than the specified period, the direct link to the project storage account is removed. This speeds up the search and display in the stock lists. No movement data is lost in the process.
Specifications
: : Specifications ControlSpecifications of variant parts can and should only be stored in project stock, as no value and cost determination can be carried out for these. You can use this test to search for normal stocks of specifications. The result is displayed in the stock list and can be checked there.
Stock account
Stock account registration-
: : Warehouse account registrationTest searches for parts whose stock accounts (CX_STOCK_ACCOUNT objects) are not registered in the REP collection and registers them there.
: Main storage bin-
: : No occupancy in main storage binTest searches for parts whose main storage bin has never been moved. Either the part actually has a different main storage bin or it has never actually been moved.
: : No movement at all.Test searches for bearing parts that have never been moved.
: : Invalid main storage binTest searches for parts that have an invalid main storage bin. This inevitably occurs when a warehouse is invalidated but its storage bins are still entered as the main storage bin in various parts.
Average price on warehouse account-
: : Check average priceStocked parts are searched for that do not have an average price in the stock account or this is zero. In addition, you can check for average prices that have a greater deviation from the standard roll price plus or minus the recorded percentage.

This option can be used to add the price from the standard procurement reel as the average price for all parts found. If the standard reel price is zero, it is not adopted and the parts are marked in the list.

Stock level-
: : Stock of ung. PartsTest searches for invalid parts that are still in stock.
: : Stock of invalid parts Stock pl.Test searches for parts that have an invalid storage bin with stock.
: Staging type-
: : Converted storage partsTest searches for MRP parts that still have part request items in material withdrawal status.
: : Missing min./max. quantities

Test searches for stocked parts without min./max. quantities

: : Defined min./max. quantities

Test searches for non-stocked parts with defined min./max. quantities

Stock statistics
: Stock statistics for current statistics periodThe following applies to all tests described here:
The tests are only executed if the"Redetermine results" option has been selected.
If the"Show last results" option has been selected, as is the default setting, only the results of the last test are displayed!
In addition, the check is only performed for the current statistics period. If a different statistics period is to be tested, it is recommended that you only display the current result for the current month, then close the results window, set the desired month in the warehouse statistics and select the test to be carried out via the "Test" menu. Please bear in mind that these tests can take some time depending on the amount of data. For this reason, it is possible to display the last results again within one second at the touch of a button.
: : No priceTest searches for vouchers that were posted within the current statistics period and have no price or the price is zero.
: : Negative closing stockTest searches for statistics of the current statistics period (part/warehouse) that have negative closing stock.
: : Value without quantityTest searches for statistics of the current statistics period that have a closing stock of zero but a closing value greater or less than zero. These cases are automatically corrected at the end of the month. The test is therefore used to analyse statistical periods that were completed before 2003, when these cases were not yet automatically corrected.
: : Outgoing zero quantitySince it is expressly desired and intended to post a stock issue from a zero stock in a warehouse (e.g. the goods receipt has not yet been posted because the employee in question is ill), it is possible to put these "twisted" goods receipts and issues back in the correct order, if you can find out where this is the case. This is exactly what this check is for. A new date for the goods receipt can then be entered in the results list so that it is again before the goods withdrawal. This is also important to ensure that the moving average price is calculated correctly in the statistics and warehouse accounts.
: : Average price

Test searches for parts for which the average price in the logistics account is not equal to the average unit value of the last warehouse statistics.

: Stock statistics in general-
: : Broken chainIf the monthly closing for a part is not carried out within a current year, for example because the checks have failed, but the next month has been properly closed again, it can happen that incorrect initial values are used in the last month. For these parts, all month-end closings since the "gap" up to the last closed month must be repeated. This check run has been written to detect these parts.
Correct differences storage bin accounts-
(Further information)
: : Broken chain

Stock statistics are searched for parts that have either not been finalised or have been changed after finalisation.
All monthly closings displayed in this test must be repeated, then continue with steps 2 to 4.

: : Storage bin account differencesIn all storage bins for all parts, the system goes back to the last physical inventory, takes the counted quantity as the starting quantity and adds or deducts all document quantities incurred since the physical inventory posting. The final total from this calculation is then compared with the final stock actually stored in the storage bin account.
If there are differences, it is possible to correct individual entries or all entries.
: : Warehouse account differencesFor each storage account, a total is calculated from all storage bin accounts and compared with the total quantity currently in the storage account
: : Differences warehouse statistics

The most recently posted warehouse statistics are determined for all parts and their current quantity is compared with the total of all storage bin accounts in this warehouse. If there are differences, these parts are listed.

The correction option is disabled for this function as it is carried out without a document or traceability. The "Set initial values with inventory"function should be used to correct warehouse statistics
This function can be activated by a trained AppswareHouse consultant. It should be borne in mind that the correction is realised with virtual receipt or issue quantities, which can then no longer be traced due to the posted documents. This correction should therefore only be used as a last resort if all other possible causes of error have been ruled out.

: : Execute last 2The last 2 runs are executed one after the other.
Dispatch account
: Dispo account registration-
: : Dispatch account registrationTest searches for parts whose MRP accounts (CX_DISPO_ACCOUNT objects) are not registered in the REP collection and registers them there.
Dispatch account entries-
: : Total overdraft entriesThe number of all documents posted in parts MRP accounts is determined. This test is used to get a feeling for whether work is being done properly. If a large number of provisions remain uncompleted, the number of entries slowly increases. The same applies to unfulfilled orders that are never sent to the supplier or have been sent, orders that were simply forgotten to be cancelled, etc.
: : Search for partsYou are asked to enter a number. The system then searches for parts for which the same number - or more - of disposition entries have been entered.
: : Search for receipts

You are prompted to enter a date. All parts MRP accounts are then searched for vouchers that are at least as old as the date entered. This makes it possible to find old entries that are still registered in the MRP account by mistake. This is the case, for example, if a goods withdrawal has not yet been posted for a production order. This goods withdrawal then remains in the MRP account.
In addition, an option is offered that simply removes incorrectly stuck vouchers from the MRP account. An obviously incorrect voucher is, for example, a goods withdrawal that is older than the date entered and whose order item predecessor has long since been delivered. These documents are NOT cancelled, they are simply removed from the MRP account WITHOUT changing the total stock quantities. The posted quantities that this document has increased therefore remain at the high value. This is necessary because sometimes an inventory or stock correction has already taken place, which has already corrected the stock quantity!

: : : Clearing obviously incorrect vouchers
: Dispatch account quantities-
: : Negative quantity of goods received

This finds MRP accounts on which a negative goods receipt quantity has been posted. This can happen if the goods receipt is processed incorrectly (e.g. staged and then deliberately put away). The individual cases that cause this have already been rectified.

: Labour supply-
: : Finished, registered AFOChecking the worklist based on the work sequences in the MRP account of the work centres. Work sequences that have already been reported as completed via a PDC booking or where the upstream customer (production or internal order) has already been cancelled or reported as completed are listed in an extra window.

If the "Correct" checkbox is selected, the items are deleted directly from the MRP accounts of the work centres.

Transaction data
Order management-
: : Parts differentTest searches for order items that have an order for a different part as a successor, but this is not labelled as an additional order, works contract or alternative part. Due to such an incorrect order, the order item cannot be provided and remains registered in the MRP account with its open quantity.
: : Check billing valuesTest searches for orders whose invoiced value differs greatly from the actual order value (too much or too little invoiced, although the order has the status "fully invoiced")
: : Missing dispo statusTest for order items that have a bill of materials but no MRP status.
: Warehouse-
: : Negative goods receiptsTest searches for goods receipts that contain a negative quantity. Such goods receipts should only be used if an incorrect goods receipt quantity has been incorrectly saved on an old document that can no longer be changed. To avoid having to post a withdrawal, which is then also evaluated in the warehouse statistics, you can post a negative goods receipt in these cases, which only reduces the goods receipt value by the value entered, i.e. does not increase the goods issue value (otherwise it would count as turnover).
Unfortunately, the option of negative goods receipts can be misused to achieve a better result during a stocktake. The difference quantity is then simply booked out via a negative goods receipt and the official deviation in the inventory is 0. This test run was created to detect these cases of cheating.
: : No cost originatorTest searches for warehouse documents that have neither a predecessor document nor a cost centre as the cost originator. These documents cannot be assigned to a cost centre or cost object.
: : Unposted warehouse vouchersTest searches for stock receipt, stock removal and stock transfer documents that were created in a statistical period and not posted until the statistical period was closed. These errors also result in an inaccurate final statistics result.
Production-
: : How often manufactured?The "Period" text field is used to specify a period in which the system checks how often all production parts occur in a production order. This test produces a list of results in which the number of times each part was produced is displayed in a column. This figure does not represent the quantity produced, but the actual number of production orders. This list can then be used to analyse for which production parts it would be worth switching to "stock management". By switching to stock management, much larger stock order quantities could be produced in one go, which would then only need to be removed for the respective orders. This also saves time later for the overall order.
Parts utilisation
: : Parts utilisationCurrently no longer supported: see parts consumption module

Parts utilisation or parts usage in the last e.g. 12 and 36 months (2 entries can be made). All stock movements (without stock transfers, inventories), direct dispatch, production orders, goods receipts and incoming invoices are taken into account

: : Not used since/used in periodTest searches for parts that have not been used for a period of time. If the number of parts found reaches the limit, the search process is cancelled! The complementary search finds parts that were used in the specified time period.

All parts are used for this evaluation, but JIT parts, Kanban parts and manual storage parts without stock management are not evaluated. The use of the part in a warehouse transfer posting, in a production parts list, a customer order, an internal order (no stock orders!), a parts planning with level > 0, an advance requirement or a goods receipt is considered "use".

Related to this are the modules parts utilisation (intended for use by engineering), parts usage (intended for use by service/sales) and parts consumption (intended for use by logistics).

Provision
Open stock reservations-
: : Open production sub-itemTest searches for open stock reservations that should be withdrawn for production order items that have already been staged and have probably been withdrawn, but not booked out in the system by a goods withdrawal document.
: : Open completed advance ordersTest searches for open stock reservations that should be withdrawn for already completed advance requirements and have probably been withdrawn, but not booked out in the system by a goods withdrawal document.
: : Open stock in. Warehouse open.Test searches for open stock reservations that should be withdrawn for stock order items that have already been put away and have probably been withdrawn, but have not been booked out in the system by a goods withdrawal document.
: : Open stock order items Customer orderTest searches for open stock reservations that should be withdrawn for sales order items that have already been delivered and have probably been withdrawn, but have not been booked out in the system by a goods withdrawal document.
Open provisions-
: : Open stagingTest searches for all open, unprovided part request items for provided production order items (purchase requisition, stock reservation, production order, ...)
Staging - goods receipts-
: : Stored and ready. WETest searches for goods receipts that were incorrectly staged and still put away.
Staging - superfluous data-
: : Superfluous parts listTest searches for order items that have been completely withdrawn from the warehouse and have an unfinished parts list.
: Open staging - exchange part-
: : Multiple withdrawalsTest searches for order items that have been withdrawn multiple times by their exchange part.
Production
Parts lists-
: : Display number of parts listsIn this inspection run, the number of valid and the number of invalid parts lists are displayed. It also determines how many parts lists have variant items or refer to variant parts.

The box "with count of production stages" is used to additionally determine and output the maximum production stage of the parts lists.
: : Same parts listsIdentical parts lists are searched for in this inspection run
: : Parts lists without parts allocationThis inspection run outputs parts lists that are not assigned to a production part
: : Part statuses in parts listsParts can be assigned to any number of order terms. Among other things, such organisation terms can also describe the status of parts, e.g. "In process", "Released", "Blocked", etc.

With this inspection run, it is possible to check in parts lists of parts, e.g. in the status "Released", whether all parts - which occur within the parts lists - also have the status "Released". It is therefore checked to what extent a status (part status) of a part matches the status (part status) of all parts in its parts list.

Work plans-
: : Display number of routingsIn this inspection run, the number of valid and invalid parts lists is displayed. It also determines how many parts lists have variant items or refer to variant parts.

The "With multiple use count" box is used to count the routings that are assigned to several production parts at the same time, i.e. are used multiple times
: : Same/similar routingsThe same or similar routings are searched for in this inspection run. Task lists are identical if all work sequences and their times are identical.

Similar routings can also be determined by specifying setup and piece time grids. A time grid of e.g. 5min means that all times within the grids 0-5min, 5.01-10min are always considered to be the same
Constructive assembly
: : Deactivated assemblies

Test searches for BOM item where constructive assemblies are not used as such.

: : Activated assemblies

Test searches for BOM item that is not a constructive assembly but is used as such.

: :

Exploded assemblies

Test searches for exploded BOM items with constructive assemblies and displays the successor.

: :

Deactivated part identifier

Test searches for exploded parts list item where constructive assemblies are not labelled as such, although the part holds the identifier.

Technical administration
Dispatch account-
: : Stopped or cancelled entries entries

Test searches for MRP accounts in which stopped or cancelled entries are posted. Stopped entries are normal, but cancelled entries should no longer appear.

: : No open quantity

Test searches for entries in MRP accounts that have an open quantity of zero. Except for goods receipts that are still posted due to insufficient QA, this means that the documents have been left in due to an error.

: : Deleted entriesTest searches for MRP accounts that contain entries that have been deleted and are only displayed with a red X in the MRP account without quantities and voucher details.
: : Check dispo stockTest compares the MRP stock with the quantities in MRP warehouses.
: Balance differences-
: : Search for balance differences

Test checks whether the quantities posted to the MRP account, such as "Sales order quantity" or "Production order quantity", match the total of all visible documents in the MRP account. If there is a difference, the difference is described in red at the bottom when the MRP account is opened. All MRP accounts that show such a difference are collected and displayed in this check run, but not yet corrected!

: : Balance diff. + comparison

All balance differences are collated as described above. The result is compared with the last compilation of the balance differences and only the parts that have been added since then are displayed.

: : Only compare last result.

The balance differences are not recalculated, only the last two results are compared with each other and the results that have occurred since the penultimate calculation for the last calculation are displayed.

: : Correct balance diff.The last balance differences determined are corrected. The same text file is used for this as is used when comparing the last results.
: Order parts-
: : Incorrect "tradeAgreement"Test searches for order parts for which the "tradeAgreement" slot is not the main supplier.
Attributes-
:: Search attributesTest searches for all attributes that have slots that correspond to other attributes.

Buttons
ButtonButton description
CloseThe window is closed.

Result window

The results window shows the results of a test that was started from the inspection screen. From here, you can double-click to jump directly to the editing screen of the displayed object. In addition, the usual toolbar buttons such as document history, dispo account etc. are available. Any vouchers can be dropped into this window. This is interesting for cancellation or repair runs that are in the cockpit.

Toolbar
IconToolbar description
tree.pngShow document history
CX_DISPO_ACCOUNT.pngDisplay dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
ListListing of the result entries

Buttons
ButtonButton description
CloseThe window is closed.

Part environment test window

The part environment test window offers further restriction options for the execution of the test run.

Toolbar
IconToolbar description
CX_AMOUNT_calculation.pngRecalculate
tree.pngShow document history
CX_DISPO_ACCOUNT.pngDisplay dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
Preselection-
: Parts selection-
: : Stock parts onlyOnly bearing parts are considered in the test run
: : Part type-
: : : All partsAll part types are taken into account
: : : Only variant partsOnly variant parts are considered
: : : Only sub/individual partsOnly sub/individual parts are taken into account
: : ProcessorSelected employee
: : Cost centreSelected cost centre
Period-
: : Investment date part (from-to)Either only a date such as "today", a period open to the future or past (-01.01.2005 or 01.01.2005-) or a fixed period (1.1.2005-1.7.2005) can be entered.
: : No preliminary costing since (date)Only a current date is expected in the results analysis date for the preliminary costing of production parts (01.01.2005). If a production part has not received a preliminary cost estimate since the specified date, it appears in the list. If no date has been entered in this field, the system generally only checks whether a preliminary cost estimate has ever been created for this part.
Test mode-
: : Execute test conditions(see below under "Integrated tests in the parts environment test")
: : Parts without operationsOnly the "Parts without operations" test is performed
: : Unconditional
List

Buttons
ButtonButton description
ProcessorSelect employee
Cost centreSelect cost centre
CloseThe window is closed.

Integrated tests in the parts environment test::

The test lists all parts...

  • without logistics indicator
  • without order or production role depending on the logistics indicator
  • without staging type
  • without SVP (if not variant part)
  • with order reel but without A-suppliers
  • with A-suppliers but unsuitable lot size
  • with production role but without preliminary costing (can be delimited by date field on selection mask! For more information see here below)
  • with production role but without lot size
  • with production role but with unsuitable lot size in material and labour cost tables
  • with production role but without parts list (but parts list not mandatory if "dispos. assembly" = DB)
  • with production roll but without routing (but routing not mandatory if "constr. assembly" = KB)
  • Parts without operations
    • No sales role
    • Simple part has no parts list or operations
    • For subparts -> the subpart and variant part have no parts list or operations
    • For variant part -> the variant part and all subparts have no BOM or operations

... on. The list can be sorted and analysed according to the desired data field (e.g. batch size error A supplier or BOM number).

Check for parts lists and routings

Constructive assembly:
No work plan is required for constructive assemblies. The design assembly is not created as a Gozino item. It contains sub-parts that must already be included in the higher-level routing, as this is where the gozino items are moved to. However, they must contain a parts list.

Purely disposable assembly:
In the case of purely MRP assemblies, the system only checks for an existing routing if the logistics indicator of the part is set to "production part". A parts list must not exist (otherwise it would not be a purely MRP assembly!).

Preliminary costing in the parts environment test

  • Date entered as the cut-off date in the "No preliminary costing since (date)" field
    • A one appears in the column "VKK missing (=preliminary costing missing)" if...
      • no preliminary costing has been found for a production part since the date entered
      • and the part has been released
      • and the part is a stock part or an MRP part with stock on hand
    • In the column "le.VKK-Überberg. (=last preliminary costing transfer by production role)" column, the date of the last transfer of a part preliminary costing appears.
      This date is shown below the part preliminary costing pointer in the "Costs" tab on the production parts screen.
      This date is only displayed in the list if a part preliminary costing pointer exists.
  • No date entered as an accrual date::
    • A one appears in the column "VKK missing (= precalculation missing)" if...
      • no preliminary cost estimate has ever been created for a production part
      • and the part has been released
      • and the part is a stock part or an MRP part with stock on hand
    • In the column "le.VKK-Überberg. (=last preliminary costing transfer by production role)" column, the date of the last transfer of a part preliminary costing appears.
      This date is shown below the part preliminary costing pointer in the "Costs" tab on the production parts screen.
      This date is only displayed in the list if a part preliminary costing pointer exists.

Number of parts

Fields
FieldField description
Number of all partsNumber of all parts
...variant partsNumber of variant parts
...lower partsNumber of lower parts
...individual partsNumber of individual parts
Purchased parts/manufactured parts-
dispositiveNumber of disposable parts
: not dispositiveNumber of non-disposable parts
listList of part roles and their number

Buttons
ButtonButton description
CloseThe window is closed.

No logistics indicator

Toolbar
symbolToolbar description
CX_AMOUNT_calculation.pngStart search
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
Preselection-
: Parts selection-
: : Valid parts onlyOnly valid parts are considered
: : Only released partsOnly released parts are considered
: : Part type-
: : : All partsAll part types are considered
: : : Only variant partsOnly variant parts are considered
: : : Only sub/individual partsOnly sub/individual parts are taken into account
: Period-
: : Investment date part (from-to)Either only a date such as "today", a period open to the future or past (-01.01.2005 or 01.01.2005-) or a fixed period (1.1.2005-1.7.2005) can be entered.
List

Buttons
ButtonButton description
CloseThe window is closed.

No use of parts

Parts that have a sales role are not taken into account in this test because the level 0 order items are not posted to the part utilisation. In addition, it may be normal that a level 0 production part does not appear in any other master BOM because it is sold directly.
When testing for existing movement data, movements of the sub-parts are also checked for variant parts, as it can happen that the variant part itself has never remained in a BOM, but has always been broken down into one of its sub-parts.
When testing for occurrences in other master parts lists, the system also checks whether the variant part occurs in a master parts list. Subparts are usually never in master BOMs, but always the variant part.
It would not necessarily be wrong for a variant part to have no part usages of its own - or for a sub-part to have no other master BOM occurrences of its own.

Toolbar
SymbolToolbar description
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Invalid parts

toolbar
IconToolbar description
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Invalid parts in master parts lists

If parts are invalid and these are used in parts lists, these parts lists cannot be exploded when the parts request is created. With this search run, all valid items of parts lists are checked to see whether an invalid part is used; if so, it is displayed.

You now have the option of editing the parts list items individually by hand - double-click - or simply accepting the validity from the part.

Toolbar
SymbolToolbar description
CX_AMOUNT_calculation.pngStart search
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list
CX_VALIDITY.pngThe validity from the part is transferred to the item, i.e. if the part was valid until 31 December 2013, the item is then only valid until 31 December 2013. The validity of the items can also be carried out when setting the part validity. See

Invalid parts with valid storage bins

Toolbar
SymbolToolbar description
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list
CX_STOCK_ACCOUNT.pngShow logistics account
CX_VALIDITY.pngValidity

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Incorrect price table

Toolbar
IconToolbar description
CX_AMOUNT_calculation.pngRecalculate
tree.pngShow document history
CX_DISPO_ACCOUNT.pngDisplay dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
Preselection-
: Prices to be checked-
: : Order roll price
: : A-supplier price
: : B supplier price
: : C supplier price
: Parts selection-
: : Stock parts onlyOnly stock parts are considered
: : Part type-
: : : All partsAll part types are taken into account
: : : Only variant partsOnly variant parts are considered
: : : Only sub/individual partsOnly sub/individual parts are taken into account
: Period (creation date part)
List

Buttons
ButtonButton description
CloseThe window is closed.

Incorrectly registered work sequences

Toolbar
IconToolbar description
CX_STOCK_ACCOUNT.pngDisplay worklist
tree.pngShow document history
copytoclipboard.pngCopy analysis to the clipboard
delete.pngRemove selected entries from the dispo account of the workstations

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Not registered vouchers

Toolbar
IconToolbar description
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Differences warehouse statistics - storage bin accounts - warehouse account

There may be differences between warehouse statistics and warehouse accounts due to incomplete months of parts. Various test runs have been implemented to eliminate these differences.

Four steps are required to restore a completely synchronised picture:

The first step is to check whether the month-end closing was not carried out for parts in certain months or whether the final value is no longer correct due to postings that were only made after the month-end closing.

Instructions for correcting differences in warehouse statistics - storage bin accounts

First of all, a test run must be started to find interrupted closing chains or closed months for which a posting was made after the closing.

To do this, open the new cockpit and start this run Interrupted chain:

Inspection Mm01 En

A result window appears:

Result window - interrupted chain

Toolbar
IconToolbar description
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list
check_green.pngCorrect data for selected entries

fields
FieldField description
Missing terminations
: ListView of all months that have been changed after completion.
New parts to be finalised
ListEntry per part with the indication from when the monthly closings have to be redone until today

Buttons
ButtonButton description
CloseThe window is closed.

In this results window, you can now see all the months that were changed after completion.

In the second notebook tab, there is only one entry per part with the information from when the monthly closings must be redone until today.

This list should now be sorted by month.

Then open the stock statistics and set the date as it is displayed in the column for the part and up to the last completed period.

Now select all parts in the results list that need to be newly completed in January and simply drag and drop them into the stock statistics.

All months in this period are displayed (for all warehouses where this part was moved in this period).

Now in the warehouse statistics via the menu

"Closing->Repeat monthly closing" menu to repeat the monthly closings.

The list is empty after closing. It can be rebuilt using the "Execute statistics" button (not necessary, only if the result is to be checked)

Proceed in the same way with all parts in the list. The three other runs can then be started one after the other and corrected if necessary.

Storage bin account differences

toolbar
symbolToolbar description
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
delete.pngRemove selected entries from list
check_green.pngCorrect data for selected entries
copytoclipboard.pngCopy analysis to the clipboard

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Differences stock account

toolbar
IconToolbar description
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard

Fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Differences in warehouse statistics

Compares the warehouse statistics with the warehouse accounts. It checks the "closing.quantity" of the last warehouse statistics with the stock level; if this is not available, the system calculates it. It does not have to be the last closed statistic, a new statistic is already opened when a part is booked in or out. It can only be changed in this statistic.

If differences have arisen in the warehouse statistics that were found here in this run, they can be corrected directly in this window. For this purpose, the individual data is displayed in the list with the month to be corrected, as well as the current and newly calculated quantities and values. This gives you an overview of the totals that make up the changes.

Buttons are provided in the toolbar for correcting or simply removing from the results list.

After the correction, the corresponding month does not need to be finalised again, as the values of the finalisation are adjusted at the same time.

Toolbar
IconToolbar description
CX_DISPO_ACCOUNT.pngShow dispo movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list
check_green.pngCorrect data for selected entries

fields
FieldField description
List

Buttons
ButtonButton description
CloseThe window is closed.

Storage bin accounts without inventory

Search window in which a date can be entered and warehouses selected. The system then searches either for all selected warehouses or, if none have been selected, for all storage bin part accounts for which no inventory has been posted since the date entered. The evaluation can also be carried out over the financial year. In this case, a check is made for all parts of the selected warehouses to see whether an inventory was posted in the selected financial year. Parts that did not have any stock movements in the selected financial year are ignored. The entries found are displayed in the list below. From this list, the entries found can be dragged and dropped directly into an inventory.

The "Invalid storage bins/parts also" checkbox can be used to control whether the currently invalid parts or storage bins/storage bins should be included or not.

Toolbar
IconToolbar description
CX_AMOUNT_calculation.pngRecalculate - Either according to the date entered or the selected financial year
CX_STOCK_on.pngDisplay stock level
CX_STOCK_log.pngShow stock movements
CX_DISPO_ACCOUNT.pngShow disposition movements
CX_STOCK_ACCOUNT.pngShow logistics account
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list

Fields
FieldField description
DateDate from which it is to be checked whether an inventory has been posted
Financial yearFiscal year in which to check whether an inventory has been posted for the parts of the selected warehouse or all warehouses
Also invalid storage bins/partsIf this box is ticked, all invalid warehouses are also displayed for selection. The subsequent search then no longer excludes invalid storage bin accounts.
Warehouse listWarehouses to be included in the search. If no warehouse is selected, all warehouses are searched.
Result listAll storage bin part accounts found

Buttons
ButtonButton description
OK BUTTONThe search is executed and the results are returned to the calling window

Number of parts lists

Various numbers of parts lists are displayed. The button can be used to list the group of parts lists found there.

Buttons
ButtonButton description
CloseThe window is closed.

Number of routings

Various numbers of routings are displayed. The button can be used to list the group of routings found there.

Buttons
ButtonButton description
CloseThe window is closed.

Spare parts test window

toolbar
IconToolbar description
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list

Implemented tests (fields and buttons)
ButtonsTest description
Without offer+orderSpare parts without quotation and order
Without identifier in SLSpare parts that are in master parts lists without a "spare part" identifier
SL without spare partBOM item with "spare part" identifier and without spare parts that are in master BOMs without "spare part" identifier
Part classesPart classes that contain spare parts
SpecificationSpare parts that contain duplicates in the specification table
Price historySpare parts, price history for prices as value of quantity exported to file.

Sales article tests

Search for parts with different properties in relation to its sales part.

The following search functions are available :

Menu itemDescription
Parts (variant or individual parts) without sales itemsSearch for variant and individual parts that do not have a sales role.
Parts with sales parts and without manufacturerSearch for variant and individual parts that have a sales, spare parts or special sales role, but no manufacturer is stored in the parts master.
Parts with multiple sales rolesSearch for parts that have several sales-related roles, i.e. that have e.g. spare part and sales part roles.

Menu
Menu itemMenu description
Edit-
: Change part settings with WizzardYou can change certain settings/values of the selected parts in one run. See

Toolbar
symbolToolbar description
copytoclipboard.pngCopy analysis to clipboard
delete.pngRemove selected entries from list

Related topics


Technical documentation

The SaveCollectionToDisk and ReadCollectionFromDisk macros are used to export objects from a collection or vector to a text file.
The SaveCollectionToDisk macro saves all database addresses of each object contained in the vector to a text file.

The call is made as follows::

Vector file name SaveCollectionToDisk

The ReadCollectionFrom Disk macro returns the objects determined from the database addresses of the transferred file name in a vector as a return parameter:

File name ReadCollectionFromDisk -> Vector

Part master Testutlities module

Module name

utilitem.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.

Messages received
MessageParametersFunctionsecurity

Messages sent
MessageParametersFunctionReceive module

Operational business