Change supplier number in invoice receipts with receive all lines

When using option receive all lines, it was not possible to use another supplier number than was specified on the order. This has is now possible so that the rule can be specified in application dependent data. The rule now corresponds to the rule when receiving line by line.

OIO Embedded PDF

A functionality has now been developed, that enables in connection with invoicing (appl. 6235) an XML file to be created that is created according to the OIOUBL standard with the invoice PDF document as embedded data in the XML file.

Validation of Contact Person

Previously it was not possible to validate Contact Person on for example Order Headers via normal Field Definitions(STFE) validation. The program ZKONTPERS used so far returns the name of the contact person but not an error if the contact person is not created as a contact.

A new program ZCONTPERS has now been made that can be used on field definitions(STFE) instead of ZKONTPERS if the validation is desired.

So if there is a requirement to ensure that all contact persons selected on orders are infact created as contact persons, it is now possible to change the validation by using the programm ZCONTPERS on the field definition (STFE).

The alternative is the default setting of ZKONTPERS as validation. This does not validate if selected contact person is created as a contact and it is possible to add contact information without any validation.
 

Display field

At field level in application files (9165), a new column has been added. It is now possible for each key-field to see if it is sorted ascending or descending.

Goods receipt app

A new app for Goods receipts has been created. The app is called 7M65 is available in the ASPECT4 Crosspad for user who have user rights for 7M65.

Unlike in the Client based applications for goods receipts, the app will instantly update transactions. A number of configuration settings are available for 7M65 in Application parameter (128).

More lines for a row in List with columns in Crosspad

It is now possible to have more than 1 field in a column for each row in a Crosspad Column list. On the Field definition(STFE) the line number for a field can be stated.

New call program for field control id's to execute commands.

A new standard utility program ZCPCMD has been added to Aspect4. This is a general-purpose call program that allows you to execute any IBM i command directly from within the Aspect4 application — for example, running a Query Manager query from a screen button in an app — without needing a custom CL program to be developed each time.

ZCPCMD is called using the standard Aspect4 CALLPGM function with one parameter — the command string you want to execute:
CALLPGM('ZCPCMD', <CommandString>)

Example — Running a Query Manager query with an order number:
CALLPGM('ZCPCMD', 'RUNAS4QRY QRY(MYLIB/ORDERQUERY) PARM1(''000012345'')')

Output Management

Today ASPECT4 Manufacturing exports XML-data for the documents the printed using DocManager. Some customers use other Output Management Systems like Interform or LaserNet. With this change it is now possible to output XML to other Output Management System than DocManager. This includes Document Property data like Document name, printer, number of copies, email recipient adress. These data will be sent in a separate DocManager band called PRINTVAL

Made for these document:

• Appl. 6230 Proforma Invoice
• Appl. 6231 Quotation
• Appl. 6232 Order Confirmation
• Appl. 6233 Delivery Note
• Appl. 6235 Invoice
• Appl. 6236 Collective Invoice
• Appl. 6254 Packing List
• Appl. 7232 Purchase Order
• Appl. 7233 Purchase Order Reminder
• Appl. 8254 Job Ticket

It is possible to setup that DocManager is used for some documents and other Output Management Systems for other document. For each document it is configured on the matching System parameter if XML-output for other systems should be created.

Hidden and thousand separator settings now handled in list with columns in Crosspad

List with columns in Crosspad now respect the Field definition(STFE) settings regarding hidden and thousand separator.

Automatic conversion to alternative units independant of field type

Until now only fields defined as 13,5N could be automatic converted to alternative units. Now it is possible for all numeric fields. 

Application Job Definitions(9176) - validation of sorting.
It is now validated if the specified sorting id valid.

Currencycode wrong on finance postings

The currencycode is wrong on finance postings concerning sales and purchase orders. On the account types where postings besides the value in the systemcurrency (used for bookkeeping) also contains information in currency from the orders in question the currencycode may be wrong. Previously the currencycode from the system defined currency was reported on all financial postings. This has now been changed so that the currencycode transferred is now found via the currencycode from the debtor/credtor posting and transferred to the financial system on relevants postings. On other postings the systemdefined currency code is transferred.

Delivery note

Delivery note number is now correct on print of copies of Delivery notes for Intercompany CS- orders. 

Simulate Field Screen failed for views

When using the function to Simulate Field Screen i Field Definitions(9169) for a file of type VIEW, a program error was reported. This has been corrected.

Retrieving FIK number from Finance

This feature would not work in a setup where country numbers would be different in Manufacturing and Finance. System parameter LAND is now extended with a new field for Finance Country-code. It is used for looking up Payment Information about the structure of the FIK-number from general register 2269.

When upgrading the new field is converted based on information in general register 2140. However it should be manually verified afterwards that the value in the new field is correct for all countries.

Dates did not show up correct in list with columns in Crosspad

When using list with columns in Crosspad apps, date field did only show the day part of the date. Besides that support for texts from text entries on Field definitions(STFE) in lists with columns are added. 

Replace acted as Open for buttons in Crosspad apps

On a button in a Crosspad app it is set up on the Field definition(STFE) whether the next page should be made as Open or Replace. The difference is what happens upon return. With Open it returns to the page with the button. With Replace it should return the prior page but by mistake it acted the same way as Open.

Allocation on a sales order should not be deleted if it is attached on a despatch journal.
Changes are done to restrict deleting allocations in orders, for example Firm Orders (6104) for order lines which are on a despatch journal. In this situation the allocation must be deleted from Picking Journals (6152) .

Validate the Active date, creating Invoice service sales orders(SF) 

We currently validate active dates for "SF" orders (invoice service sales) when creating sales orders transactions, which is unnecessary. Therefore, we have modified the program to bypass date validation for SF order types.

Abending program with F4
When the logistics part of a customer or supplier is maintained via call from Aspect4 Finance, the program ZSQGSQL may occasionally be abending. This could happen if F4 was used in one of the open fields in the field picture in the Aspect4 Logistics part of the customer or supplier. This has now been resolved.

Record status icon not visible

In some cases where the key fields were removed from the list, the icon for locked or withhold record were not shown. This could for example be missing order type in Firm Orders (6104)

Shortcut to Equipment (9151)

When application Equipment (9151) is called via an application dependent shortcut, the application shows the list instead of executing the option that it is called with. The reason was that the key was not transferred from the calling application correct. This has now been resolved.

VAT-handling for direct deliveries

Changes have been implemented to address VAT handling. If the supplier's country of origin is the same as the customer's country in a direct delivery, no EU VAT will apply.

Missing field help for settings
In applications 9120, 9121, 9122, 9123, and 9153, the 'All Lines -> Settings' option lacked field help, making it difficult for users to understand the purpose of the field. To address this, generic field help has been added to these applications.

Line level for production order transactions cannot be called with application dependent shortcut

If the line level for production order transactions (8101) was called via an application dependent shortcut to execute an option, this call ended in error. The reason was that the key supplied was destroyed. This has now been resolved.

Correct customer data for service orders
In batch applications for service orders (6202, 6205, 8203) where customer data were read based on service agreements, only the first customer was read. This has now been changed so that when there is a change in the customer number on the service agreement, the customer is now read properly.

Filtering on local company texts for system parameters gave wrong result

A system parameter can be defined as having description locally in each company. In this case and when a list is set up to show this text, filtering on the text gave wrong result in some cases. 

Missing translation of application layout cost prices (9131)

In application edit application parameters (0128), the layout for cost prices (9131) was not correct in English. This has now been corrected.

Creating orders and invoices.

When creating a quotation sales order (6105), it was possible to enter a manual delivery address without filling out a valid country code. The result was that lines were not printed on the document. This kind of data is illegal, as the solution requires an existing country code. A validation has therefore been added to ensure hat the country code is validated against the systemparameter Countries (LAND).

The validation code has been added in sales order applications (6102, 6103, 6104, 6105, 6106, 6108). The validation code has been put on the field ORDH-LAND.

Please note that if the installation contains copy applications of these standard applications, it will be relevant to make the same change for these applications. If so, the change that must be made manually is related to the validation code for the field ORDH-LAND. If it's 'Mod tekstindgang + blank', it should be changed to 'Mod tekstindgang'.

Filtering via warehouse does not work

Filtering for warehouse in the picking app via the settings field has stopped working. This has happened after the two new fields for which journaltypes that should be included have been added. The fields overlap which would result in inconsistent settings data.

The reason was that the bufferposition for the XXXX-FIELD for the warehouse in the fielddefinition *REQUEST RUTH01 was wrong. This has now been corrected.

Document Product Structure Item(9224) dump due to not numeric value

Fixed a dump which was caused by the movement of Non numeric field to a numeric field 

Missing danish description
For application Document Product Structure Item(9224), the Danish description was incorrectly populated with English text. This issue has now been resolved, and the correct Danish description is visible

Column text updated as lead text

If a column text is entered in Language in application Label Texts and Column Heading(9061), it is updated as lead text if there is no lead text in the actual language. This has now been changed so that the column text in this case is now updated in the correct field.

In Document Product Structure Item(9224), the field "Calculate all variants" exists on the Field Definition but is not shown on the field image.

Application Document Product Structure Item(9224)  Field Definition has a 'Variant' field, but it is not displayed on the screen due to the program's logic at customers that do not use variants for items. The field name VARIANT has therefore been changed to a new name so that it is now visible.

Filename not updated with new viewname.

For the window application Invoice Vouchers (706H) which is used in cockpit application Invoice match (7769), the filename was changed from TIEB03REG to A706HZVIW in an earlier release. This was, however not changed due a deployment error. This has now been resolved.

This record below for application 706H in application Application Control Identities (9060) had been created with status 0. The result was that it was not possible to select a voucher in the cockpit. This  has also been resolved now. A new record is deployed with status 30.

Appl    Funktion    Perform    Line    ID    St    Description    CalcSpec
706H    *READ    After    10        30    Opdaterer env. variable til journal og bilag    *EXITPGM := 'A706HZ'

Time based material profile
A time based material profile did not include quantities received from production orders with status >20. A time based material profile gives priority to quantities issued to orders with status > 20. Unfortunately this has meant that quantities received from orders with status > 20 was excluded. This has now been corrected.

Fixed - Cannot Update Delivery Date on Journal Lines in Application purchase order transactions (7101):

Sometimes an error message is thrown when trying to change a field at line level in the application. The system returned error message 18317: "Order No cannot be 0. It occurs if order number is part of the location number in a location-controlled warehouse number. But this error message makes no sense here as the order number does not exist if the transaction type is a creation. In this case the validation/create of location number is skipped until later in the creation process where the order number is created.

Calculate ABC Grouping of Items(9211) Application dumps.

The application was unable to process ABC analysis for companies with a large number of warehouses (more than 99). This caused the program to fail when running the analysis. Application Calculate ABC Grouping of Items(9211) can now handle up to 1,000 warehouses.

Handling of ping's in text not handled correct in Application controls(9060)

The result of concanating texts which includes a ping did not give the correct result. It now works as it does in Field controls. The general issue is that the text should be arounded by a ping. If the text itself contains a ping you must write 2 ping's to indicate that. It is a general conversion that is used elsewhere. 

Sales Order Transactions (6101) application was abending when customer group 9 was selected.

The application was unable to process transactions when customer group 9 was selected in the selection settings. This caused the program to abend with an out-of-range error when attempting to filter transactions by customer group. The issue was due to an overflow in an internal variable that could only handle single-digit values (0-9), preventing it from correctly calculating the array index for customer group 9.

Sales Order Transactions (6101) application can now correctly handle customer groups 0-9 and supports up to customer group 29.

Collective Invoice(6236)
Now Lot numbers is specified correct for all lines on the invoice.

Relative fields made on Field Override(9160) did not appear correct

If a field was made as an Field Override(9160) and it has a Relative to Field set, the buffer was not calculated and the result was random.

Finance period between 79 and 29.

In the Company calendar application (9175), an error occurred when attempting to edit a line in a calendar for a year beyond 2029. This issue was caused by a validation rule that restricted the maximum allowable year to 2029. The validation has now been changed so that editing is now allowed for calendars up to the year 2049.

Missing lead- and column texts for cost price specifications

Some lead- and column texts were not deployed previously for cost price specifications. These are now included as part of the current release.