1 / 26

June 2005

Monthly Product Update. June 2005. Presented By. Diane Fryer. Diane Fryer Knowledge Transfer Manager – SYSPRO S.A. Agenda. Known Issues SYSPRO Technical Overview of Enhancements Distribution Manufacturing General Business Objects Assets Register – conversion problems.

roz
Download Presentation

June 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Monthly Product Update June 2005

  2. Presented By Diane Fryer Diane Fryer Knowledge Transfer Manager – SYSPRO S.A

  3. Agenda • Known Issues • SYSPRO • Technical • Overview of Enhancements • Distribution • Manufacturing • General • Business Objects • Assets Register – conversion problems

  4. Issue 009 Known Issues Ports 25 – 28

  5. SYSPRO Email Print Preview causing MAPI Error and not functioning The following issue was introduced in SYSPRO 6.0 Issue 009 Port 25 and affects sites using Office Automation only. When attempting to email documents or reports from the Print Preview screen, you will get a MAPI Error - 000000012. The email will not be sent. This error will occur in every program where the program attempts to attach a document or report. The file and version affected is: IMPEML 6.0.011. This program has been fixed in port 26 of SYSPRO 6.0 Issue 009 and is available for download.

  6. Technical – SYSPRO printing It has come to our attention that some customers are having problems with certain Epson printers. After upgrading to Issue 9, the printer would be taken offline after printing to it, and the user has to manually place the printer online in order to print again. After some investigation, this problem was resolved. In order to resolve this, the hex codes that were being used had to be altered to include the initialise printer code for both the start and end codes. Once this was done, the users were able to print normally without any intervention being required

  7. Issue 009 Enhancements Distribution Ports 25 - 28

  8. Inventory – new options cater separately for ledger codes in P/O Receipts • What has been done • The Inventory Setup program • has new options for requesting • ledger codes during P/O Receipts. • These are: • Debits (Non-stocked) • Credits • Non merchandise • The Business Process for G/L postings • now includes these new areas: • PRD = P/O receipt debit posting • PRI = P/O receipt credit posting • PRN = non-merchandise posting • Why this was done • To provide better control of G/L codes • when processing P/O receipts The P/O Receipts Business Object has also been changed to cater for this option Port 25

  9. P/Orders - Ability to change address on any type of p/order for direct delivery • What has been done • You can change the P/O • Delivery Address • You can access the shipping • Address from the originating • S/O • P/O format allows the printing • of the following fields: • Warehouse • Warehouse description Why this was done To allow you to change the P/O delivery address so that your supplier can deliver directly to your customer Port 25

  10. S/Orders - Sales Order Review allows creation of SCT for non transfer-supplied warehouses What was done There is a new option “Allow SCT for non-transfer Supplied warehouses” in the Back Order Review program. Why this was done To bring the Back Order Review program in line with Sales Order Entry so that an SCT can be created for non transferred supplied warehouses Port 26

  11. Issue 009 Enhancements Manufacturing Ports 25 – 28

  12. Projects & Contracts - Release of B/O Qty program now displays details in a listview What was done Information in the Release of Backorder Qty program is now displayed in a list view Why this was done To improve the visual appearance of the Projects and Contracts information Port 26

  13. Issue 009 Enhancements General Ports 25 – 28

  14. Facility to list role conflicts and operators who are allowed to run a specific program Why this was done To enable companies to list which operators are allowed to run specific SYSPRO Programs and establish what role conflicts exist for a program. This is in accordance with requirements for the Sarbanes-Oxley Act. What was done A new program lists which operators are allowed to run a specific program and, optionally, what role conflicts exist for the program. Before you can report on role conflicts, you must create a role conflict file. This text file (CONFLICT.TXT) can be created using an editor such as Notepad, and must be saved in your working directory. In a Client/Server environment this file must reside on the server. Port 26

  15. Facility to list role conflicts and operators who are allowed to run a specific program Please see the Enhancement notice on the Support Zone for the file layout for the CONFLICT.TXT file. Port 26

  16. Standard Message Box Utility enhanced Why this was done Developers may want to have a 'Do not show this message again' checkbox associated with a message box. This enables developers to provide a more user-friendly interface where the operator can suppress subsequent invocations of the message box, if required. What was done The standard SYSPRO function: 'INVOKE-MESSAGE-BOX' now allows developers to set a flag indicating that a checkbox (labeled: 'Do not show this message again') must be shown. This function is explained in the SYSPRO Software Development Kit documentation. Port 28

  17. Issue 009 Business Objects Ports 25 – 28

  18. Sales Orders - New Sales Order Contract Price Query Business Object What was done A new Business Object has been created to select contract types • The following filters can be applied to • restrict the amount of data returned: • Buying group (All, Range, List) • Customer (All, Range, List) • Stock code (All, Range, List) • Supplier (All, Range, List) • Salesperson (All, Range, List) • Product class (All, Range, List) • Area (All, Range, List) • Branch (All, Range, List) • Customer class (All, Range, List) • Start or Expiry date (All, Range, • Single) • A warehouse must be supplied • for contract types that rely on a • markup. Why this was done To enable the development of applications that can retrieve Contract price information for customer or buying group Port 25

  19. Inventory - New List of Stock Codes Available Query Business Object What has been done • The list of stock codes available to an operator takes into account the list of warehouses in SYSPRO to which the operator has access. A stock code is returned only if it is stocked in a valid warehouse. • In addition, an operator has access to specific customers, who have access to specific product classes. If a valid customer is supplied, then the list of stock codes reflects the valid product classes against that customer. Why this was done The operator security restrictions need to be taken into account before supplying the developer with a list of stock codes available to the operator Port 28

  20. Assets Register Conversion problems

  21. Assets Register - Preparation for conversion to SYSPRO 6.0 Issue 009 • Check the General Ledger period dates are valid for the current and previous years. • blank dates in the current year are deemed to be invalid so update them to be valid dates.

  22. Assets Register - Preparation for conversion to SYSPRO 6.0 Issue 009 Points to note about entering period end dates • When selecting a 12 period financial year in Assets Register, a period is deemed to run from the first to the last day of a calendar month, even if for example, the physical run date of the period-end was the 25th of the month. • Therefore you should not choose a period-end date of the 1st of the month if the period-end should be the 31st. For example, for the period of 01 May 2004 to 01 June 2004, the system will calculate 2 periods. If only 1 period is required, you should select 31 May as the next date.

  23. Assets Register - Preparation for conversion to SYSPRO 6.0 Issue 9 • Run the Movement Schedule in issue 8 and check that all assets have the following: • A valid group code • A valid Book value code • A valid Tax Depreciation code • Run the Period end function – make sure it is run successfully • Print the G/L Distribution report • Print the Amendment Journals • Print the Movement Schedule

  24. Assets Register – Procedures after conversion to SYSPRO 6.0 Issue 9 • Run the Movement Schedule and compare to the issue 8 Movement Schedule • Check the G/L ledger integration setup and ensure all the fields have the correct G/L codes. • Enter G/L codes for the new fields: • Asset Control • Profit & Loss • Revaluation Reserve • Asset Clearing

  25. Assets Register – Procedures after conversion to SYSPRO 6.0 Issue 9 • There are 5 new fields on the Asset Master: • Branch • this is a mandatory field and after the conversion will contain a branch code _UND. Enter a valid branch code for each asset. • Cost Center • Location • Owner • Asset type

  26. Questions

More Related