Export Order Progress - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

On the J.20.11 Export Order Progress screen, you can export information about an order into a csv file. This file has a comma separated value file format that can be interpreted by a calculation program; for example, Microsoft Excel can read this file. In addition, a log file contains a list of any errors that occurred and why the output of a particular order could not be carried out to the csv file.

The following data is written to the csv file:

  • Order Type

  • Number/name of the agreement

  • Suppl (agreement supplement number)

  • Pos (agreement line item number)

  • Sub Pos (agreement sub line item number)

  • Quantity

  • Quantity unit

  • Cost

  • Progress

  • Account Code

For calculating the costs of a line item, the other costs on the line item level and on the agreement level are taken into account. For the line item level, this calculation is only possible if all other costs have the same account code assigned as the line item itself.

The other costs on the agreement level are partitioned among the line items with the same account code, depending on the weight this line item has in comparison with all line items with the same account code. On the other hand, this means that for every account code found here there must be at least one line item with the same account code.

All cost values, those on the line items, those of the other costs on the agreement level or the line item level can have different currencies. To add them up, it is necessary that the conversion factors are defined in the software, either on P.30.21, or on A.10.13.

For calculating the progress, you can use the milestones, but there are other possibilities. Therefore, a customer (CIP) function is used:

M_PCK_ACCOUNT_CUSTOM.Fetch_Progress ( p_poh_id IN m_po_headers.poh_id%TYPE, p_progress OUT NUMBER ) RETURN VARCHAR2

The function has the agreement ID as the input parameter, and the result is the return value, with the type of the return value as NUMBER. All return values > 0 are considered as normal values (no error), and values < 0 are considered as errors. If the function returns a value < 0 (error), this value is written to the log file, and the order is not written to the csv file.

If the function returns no error, the return value is NULL (empty). If the return value is not NULL, the procedure itself interprets this as an error.

ZJ_USE_AC is set to Y:

As the line item and the agreement itself have no account codes, the other costs on the agreement level (if there are any) cannot be partitioned among the different line items.

The values specified on J.20.02 Other Accounts and J.20.03 Other Cost Accounts are used for calculation. For every account code found on J.20.03 at least one record for the same line item with this account code must exist on J.20.02.

The procedure considers that there can be different records for one line item on J.20.02 (with different account codes). For each line item, the procedure sums up all found values of J.20.03. For each line item and each account code, one record is written into the csv file.

If the cost values have different currencies than the line item, the values are converted into the currency of the line item.

ZJ_USE_AC is set to N:

The procedure takes the values of P.50.07. The other costs on the agreement level are partitioned among the different line items, depending on the account codes and the weight of the line item.

All costs are converted into the currency of the line item.

For each order, the procedure works in two steps:

1) The order is checked:

  • Are all needed conversion factors available?

  • Is the correlation between the account codes of the different levels correct?

If, for example, a conversion factor is missing, an account code cannot be assigned correctly. In this case, a message is written to the log file. If any error occurs for an agreement, this agreement is not exported to the csv file.

If ZJ_USE_AC is set to Y, the software checks that the sum of quantities of J.20.02 Order Accounts is with the same as the quantity given for the line item. Because different quantity units are allowed, the values must be converted to the unit of the line item. This conversion happens before the available conversion factors are checked. The summation for this check does not depend on the account code.

If ZJ_USE_AC is set to Y, the software also checks that no other costs on the agreement level exist.

2) If no errors occur, the csv file is written.

The name of the created files is 'EXP_PROG_' concatenated with a sequence number and the extension .csv for the data file and .log for the log file.

At the end of the procedure, the csv file automatically opens, and an alert appears, asking you whether you want to open the log file. In both cases, the web browser on your computer is used to open the file (or the program the file extension is associated with). The csv file is stored on the application server, and you now can save a copy of the file(s) to your computer by means of the 'Save as...' function.

When you start the procedure again or when you close the screen, the export and log files of the last run are deleted.

Click the Run query button to display the available agreements. The agreements are displayed with the number/name in the Order Number field, the supplement number in the Suppl field, the order type in the Type field, and the descriptions in the Short Desc and Description fields.

Select the Sel check box for the agreements you want to export. You can use the Select All button to select all displayed agreements. The Deselect All button cancels the current selection. Finally, click the Export button to start the export of the selected agreements into a csv file.