The DIMS system from Daimler supplies different types of files. These file types are:
RT00-File types
Big Volume and 70-Parts Return - non moving parts which return to the LC
Scrapping - Scrapping parts
Orders - Parts that will be delivered from NDL (instead of LC) to a sub-branch
Relocation - Parts that are slow- or non-moving parts in one sub-branch and fast-movers in other sub-branches will be relocated to the fast-mover sub branches.
SPM BuyBack order file (BBO-File) types (XML format)
Return from DIMS - Worshop order import type.
Return from CORE parts - Purchase order import type.
PSL return - Worshop order import type.
Add-Hoc return - Worshop order import type.
Individual parts return - Worshop order import type.
Local scrapping - Worshop order import type.
The program Import parts return files imports these files and depending on the file type.
The program could be invoked manually via the menu or automatically via Timed Operations. Log Files on a monthly basis will be created.
After selecting the Purchase Control company and before the program is opened several checks are done, for example, does the Logisticbus parameter exists for this company and is it activated, does the new file MB.MS.logoc exist and is the Purchase Control company set up properly.
Depending on the following matrix the program determines the file type.
| SA00 Format | Digit 60 | Digit 63 | Digit 64 |
|---|---|---|---|
| Return Big Volume | Blank | All, except A/G | 1 |
| Return /70 Parts | Blank | A/G | 1 |
| Orders | L/D | Blank | Blank |
| Scrapping | Blank | Blank | 2 |
| Relocation | Digit 50-51 = 60 | — | — |
The record layout is displayed below:
| 1 Lfd | 2 | 3 Description | 4 Digit | 5 Length | 6 Remarks |
|---|---|---|---|---|---|
| 01 | — | Record type | 1 | 2 | — |
| 02 | — | Niederlassung Number | 3 | 3 | — |
| 03 | — | Branch number | 6 | 2 | — |
| 04 | — | Customer number in SPICS | 8 | 5 | — |
| 05 | — | Order number | 13 | 4 | — |
| 06 | — | Positionsnr. | 17 | 4 | — |
| 08 | — | Internal | 21 | 4 | — |
| 09 | — | Part number | 25 | 19 | — |
| 10 | — | Quantity | 44 | 6 (5,1) | — |
| 11 | — | Lieferwerk | 50 | 2 | — |
| 12 | — | Internal | 52 | 8 | — |
| 13 | — | Code for Order file | 60 | 1 | “L” or “D” |
| 13 | — | Blank | 61 | 1 | — |
| 13 | — | Blank | 62 | 1 | — |
| 13 | — | Code for Return file | 63 | 1 | A, G, R, S, T |
| 14 | — | Code scrapping | 64 | 1 | 2 = Scrapping |
A setup is required to use this function:
The Parts return file name and Spooler log file in EOD fields on the Import Parts return tab of the Logisticbus parameters.
The required import location of the files is retrieved from the field Transfer directory or Local directory on the Import Order File tab of the Logisticbus parameters.
Note: If the file names for the different companies are the same it is vital that the Transfer directory is different for each company, otherwise it could happen, that files would be imported in the wrong company.
For Scrapping, a wip will be created with the Account obsolete partsfield on the Logisticbus tab of the Logisticbus parameters.
Parts that are not available in the stock file are ignored. Non-existing stock records will be logged. The file type is recognised via byte 64, which contains 2.
For Order and Relocation the customer number from the file has to match with the Dealernumber field on the Logisticbus tab of the Logisticbus parameters.
For Big Volume and 70-parts return the Spics II Dealernr field of the Part ordering parameters has to match with the given customer number in SPICS form the file. (location 8,5 in the file)
If the function should run in EOD the company number must be set to MS_MB_LIC_IMPCOMP.html. The spooler is taken from the Logisticbus parameters, so no spooler must be setup here.
The Default operator field on the Header tab of the POS parameters > Flag-Priorities is used as WIP user when creating a WIP.
This function needs for each parts line in a WIP a Department code (P) with Department type of 2 (Parts).
ICT and Bulk Transfer are explained in the appropriate sections.
Depending on the file types the function acts in a different way.
Big Volume and Return 70 Parts
The program creates a negative Purchase order. The necessary supplier account is derived from the field Customer Number in Spics from the read record. The program reads the records form the Parts ordering parameter of the selected PC -company until the number matches to the field Spics II Dealernnr. The supplier is taken from the field Supplier stock file. If no supplier could be determined the file will be not imported and a log and error entry is created. Should a part not exist in the stock file, it is ignored and a log entry is written in the monthly and current log file.
Scrapping
The program creates a WIP with the Account obsolete parts from the Logisticbus parameter. None existing parts in the stock file are ignored and will be logged in the log files.
Orders
The program creates a WIP in the selected Point of Sale company, where each part line get the status I (=ICT). The account code for the WIP is determined from the parameter Depot & Branches. If the parameter does not exist a corresponding record is written in the error log file and the file is not imported. Through the parts daemon an ICT-WIP is automatically created in the supplying company. The supplying company is determined by reading the Logisticbus parameter record until the field Dealernr matches to the Customer Number in Spics field in the file record. If no match was found the file is not be imported and a record is written in the error log file. Parts that are not available in the stock file of the supplying company are ignored and logged, where non existing parts in the requesting company are created, if the part record exists in the MB price file, otherwise the part is ignored and logged.
Relocation
The program uses Pull bulk transfer of parts functionality to move parts from one company to another. A WIP will be created in the supplying company. The supplying company is determined in the same way as in Chapter Orders described. In the selected Purchase Control company a purchase order is created. The supplier account number in the file is read from the Depot & Branches record.
The record layout is displayed below:
Menu Bar and Action:
| Field | Type | Description | Values |
|---|---|---|---|
| OrderType | String(4) | Buyback order type | DIMS - Return from DIMS CORE - Return from CORE parts PSL - PSL return AH - Add-Hoc return PO - Individual parts return SCRP - Local scrapping |
| DIMS_Code | String(4) | DIMS booking code | R36A - Return from DIMS R03A - Return from CORE parts R36A - PSL return R03A - Add-Hoc return R37A - Individual parts return R35A - Local scrapping |
| OrderNo | Number(10) | Daimler order number | Blank for local scrapping |
| OrderDate | Number(8) | Date of order creation | |
| CustomerNo | String(8) | Retail customer number | 2 digits country + 6 digit customer code |
| CustVendorNo | Number(10) | Vendor number of retail customer | Blank for local scrapping |
| CustRefNo | String(10) | Customer reference on header | |
| Currency | String(3) | ISO 3 currency code | |
| TotalNetValue | Number(6,2) | Total net value of tde buyback order | |
| FacingLoc | Number(5) | Daimler location (LC.ELC)no. (Parts receiver) |
|
| DeliveryDate | Number(8) | Planned delivery date to LC/ELC | |
| PosNo | Number(8) | Daimler order line number | |
| PartNr_I | String(19) | Part number in SORT format Packed part number |
|
| Qty | Number(6,2) | Quantity | |
| QtyUnit | Number(1) | Measure unit | 1 - Piece 2 - kg 3 - meter 4 - cbm 5 - square meter 6 - liter 7 - pair 8 - gros |
| NetValue | Number(6,2) | Net value of unit | |
| NetValuePos | Number(6,2) | Total net value of line | |
| RMA | Number(20) | Daimler return number | 10 digits with inbound number + 10 digits with position number |
| CustRefPos | String(10) | Customer reference on line level |
Depending on the file types the function acts in a different way.
Return from DIMS:
For type DIMS - Return from DIMS a WIP is created in Point of Sale. The Sales ledger account mapped to the PSL/DIMS return account in the Logisticbus parameters is used as the Sales ledger account on the header of the WIP that is created. The Daimler order number is stored in the Order no field on the WIP as reference, which can be used to find the workshop order, based on the Daimler order number. The department on the WIP header is set according to the first department set in the parameter Parts departments in Logisticbus parameters. If the parameter is not set the default department P will be used. The flag SO.headr.RETAIN on the WIP header is set ot P to avoid deletion of the WIP based on retention days. The price on the WIP line will be taken from the field NetValueP os and the fixed price flag on the WIP line will be set to prevent the price being updated.
PSL return:
For type PSL - PSL return a WIP is created in Point of Sale. The Sales ledger account mapped to the PSL/DIMS return account in the Logisticbus parameters is used as the Sales ledger account on the header of the WIP that is created. The Daimler order number is stored in the Order no field on the WIP as reference, which can be used to find the workshop order, based on the Daimler order number. The department on the WIP header is set according to the first department set in the parameter Parts departments in Logisticbus parameters. If the parameter is not set the default department P will be used. The flag SO.headr.RETAIN on the WIP header is set ot P to avoid deletion of the WIP based on retention days. The price on the WIP line will be taken from the field NetValuePos and the fixed price flag on the WIP line will be set to prevent the price being updated.
Add-Hoc return:
For type AH - Add-Hoc return a WIP is created in Point of Sale. The Sales ledger account mapped to the Add-Hoc parts return account in the Logisticbus parameters is used as the Sales ledger account on the header of the WIP that is created. The Daimler order number is stored in the Order no field on the WIP as reference, which can be used to find the workshop order, based on the Daimler order number. The department on the WIP header is set according to the first department set in the parameter Parts departments in Logisticbus parameters. If the parameter is not set the default department P will be used. The flag SO.headr.RETAIN on the WIP header is set ot P to avoid deletion of the WIP based on retention days. The price on the WIP line will be taken from the field NetValueP os and the fixed price flag on the WIP line will be set to prevent the price being updated.
Individual parts return:
For type PO - Individual parts return a WIP is created in Point of Sale. The Sales ledger account mapped to the Individual parts return account in the Logisticbus parameters is used as the Sales ledger account on the header of the WIP that is created. The Daimler order number is stored in the Order no field on the WIP as reference, which can be used to find the workshop order, based on the Daimler order number. The department on the WIP header is set according to the first department set in the parameter Parts departments in Logisticbus parameters. If the parameter is not set the default department P will be used. The flag SO.headr.RETAIN on the WIP header is set ot P to avoid deletion of the WIP based on retention days. The price on the WIP line will be taken from the field
Local scrapping:
For type SCRP - Local scrapping a WIP is created in Point of Sale. The Sales ledger account mapped to the Obsolete parts accounts in the Logisticbus parameters is used as the Sales ledger account on the header of the WIP that is created. The Daimler order number is stored in the Order no field on the WIP as reference, which can be used to find the workshop order, based on the Daimler order number. The department on the WIP header is set according to the first department set in the parameter Parts departments in Logisticbus parameters. If the parameter is not set the default department P will be used. The flag SO.headr.RETAIN on the WIP header is set ot P to avoid deletion of the WIP based on retention days. The price on the WIP line will be taken from the field NetValuePos and the fixed price flag on the WIP line will be set to prevent the price being updated.
Note: The return parts can only be added to a WIP if there is free stock available, return parts with a quantity which exceeds the number of free stock available will only be added to the WIP with the quantity available, the remainaing quantity is not processed and parts that are unknown in the stock file will not be processed. For each of these, an entry will be added to the log file indicating the reason why the part has not been added.
Return from CORE parts:
A purchase order in created for type CORE - Return from CORE parts for each DIMS order number received in the file. The Daimler order number field is stored in the Internal memo field of the Purchase header record. The Supplier account on the Purchase header is determined based on the Parts Ordering parameters. The Daimler order number is stored in the Remarks field of the Purchase order line.
Note: The return parts can only be added to a Purchase order if there is free stock available, return parts with a quantity which exceeds the number of free stock available will only be added to the Purchase order with the quantity available, the remainaing quantity is not processed and parts that are unknown in the stock file will not be processed. For each of these, an entry will be added to the log file indicating the reason why the part has not been added.
This form is displayed if you click on Manufacturer systems (Module) and MB. Mercedes-Benz (Company) > Menu-Parts > Menu-Logisticbus > Import Parts return RT00-files.
Menu Bar and Toolbar:
| Menu Bar | Action |
|---|---|
| File > Open | Opens the Select parts return import file form to select a file for import. |
| File > Import | Imports the selected file(s). |
| File > Exit | Returns you to the previous menu. |
| Tools > Parameters | Opens the Logisticbus parameters and gives the possibility to change/check the parameters. |
| Tools > View log file | Opens the Log file information form. |
| Tools > View errors | Opens the Error file information form. |
| Tools > Matching numbers | Opens the Matching Order Numbers form which list the Autoline numbers together with their matching order number and import date. |
| Tools > Refresh | Refresh the list of files available for import. |
| Help > Help F1 | Displays this help file in a Web Browser. |
| Help > Info | Displays information about program version and Product-ID. |
Fields:
Upload file from client: If this field is active, it is possible to select and import an import file from the local PC. If this field is not active, the import file can be selected from the server.
Note: The standard import directory must be defined in the Logisticbus parameters.
The file below will be uploaded in Autoline
File location: Displays the import directory as defined in the Logisticbus parameters or from the files selected on the local PC if Upload file from client is selected.
File name(s): Displays selected file and files that are available for import.
Click on File > Open in the menu.
The “Select parts return import file” form is displayed.
Note: Depending on the parts return file name and the transfer directory from the Logisticbus parameters the program is searching for possible import files. Only if import files are found, it is possible to select the Import-Button.
Select the import file and click on “Open”
The filename is displayed together with the import directory
Click on File > Import in the menu.
The selected file is imported.
A log record is created.
Note: An inquiry is displayed additionally during manual import if you want to print the log file or not. During automatic import the log file is printed on a printer that is defined in the parameters per company.