July The minimum software pre-requisite to install an e.app solution is SYSPRO Version 6.1 SP1 Port 008 or higher.

Transcription

1 e.ap P S P O R TFOLIO July 2014 EOH APPLICATIONS AND e.apps EOH Applications has been a Value Added Reseller for SYSPRO since the early 1990 s. Services are currently provided on-site and remotely to SYSPRO clients in the commercial and industrial markets, located across Southern Africa. As part of its technology offering, EOH Applications also provides add-on technologies and applications including bar coding, work flow, Advanced Planning and Scheduling, portals, shop floor collection and Business Intelligence (BI). The add-on technologies that EOH Applications provide include e.apps, which is a brand name created by EOH Applications. e.apps products are utilities that have been developed in-house, by EOH Applications own SYSPRO developers. OVERVIEW OF e.apps e.apps includes more than 70 solutions that have been developed, tested and implemented successfully for numerous clients over the years. All solutions have the objective of increasing the performance of existing SYSPRO modules. These solutions have been developed in such a way that other companies requiring the same add-ons are able to implement them, provided that they meet the minimum software requirements. There may be specific SYSPRO Modules required as pre-requisites, depending on the e.app selected. The minimum software pre-requisite to install an e.app solution is SYSPRO Version 6.1 SP1 Port 008 or higher. THE e.apps PRODUCT PACKAGE The purchaser will receive the following, when purchasing an e.apps product: 1. End-user Licence Agreement This agreement has been compiled together with EOH Legal Describes the rights of EOH and the rights of the user 2. Read-Me document Contains the minimum software requirements Contains the criteria for the user, to ensure the successful implementation of the e.apps product Page 1 of 8

2 3. Technical Files - The type of technical files is dependent on the specific e.apps product, e.g. SYSPRO VB scripting,.net,.net Windows, Excel imports 4. Installation Guide 5. User Manual OVERVIEW OF THE e.apps PRODUCT RANGE e.bus The e.bus range contains business tools to enhance the existing SYSPRO functionality with regards to Global Price Updates, Purchase Order Imports, Managed Stock Allocation, and more e.form The e.form range contains Stationery or templates useful for business outputs utilising the SRS module. Formats available include Invoices, Order Acknowledgements, Statements, and more. e.reps The e.reps range contains developed reports catering for various management information needs. Report types include Accounts Payable Aged Creditors, Cash Flow Statements, Inventory Schedules, Comparative Sales, and more. The range contains automated processes or workflows, which enhance the existing SYSPRO modules. Examples of the workflows are Purchase Order Requisition, General Ledger Journal, Landed Cost Tracking, Create and Update Debtors, and more. Page 2 of 8

3 DETAILS OF PRODUCTS AVAILABLE The products listed below are the solutions that have been previously developed for different clients. e.bus NAME e.bus Foreign Exchange Cover e.bus Stock take with auto serial number allocation e.bus Customer supply allocation e.bus Inventory cost change update e.bus Inventory price update e.bus WIP Job Closure e.bus Invoice copy e.bus Requisition approval e.bus Kronos e.bus Fraxion e.bus Shopware e.bus Back Order Release e.bus Cost and price update e.bus Supplier release e.bus Job stock reservation DEV PROJECT FEC Capture Screen Stock Take (Cycle Count Selection Notification) Managed Stock Allocation (Pre- Allocation of Stock Before PO Receipt) Bulk Inventory Cost Update Bulk Inventory Price Code Update Bulk Job Closure Invoice Copy Purchase Requisitions SYSPRO / Kronos SYSPRO / Fraxion SYSPRO / Shopware Back Order Release application Global Price Update Supplier Release System Stock reservation for jobs DESCRIPTION The business case for the e.bus Foreign Exchange Cover is to manage forward exchange cover bought by the organisation as it is allocated to incoming shipments. Organisations will buy forward exchange cover and allocate the forward cover to the incoming shipments, the budget rate specified on the shipment is often different from the forward cover rate or rates applied to the shipment and this difference will be posted to a variance account. This e.bus application allows the organisation to store the forward cover purchased and the shipments to which it has been allocated. The business case for the e.bus stock take with auto serial number allocation is to speed up the stock take capture with serial numbers. When the operator performs a standard stock take capture for a serialised stock code this is done without needing to capture the serial numbers as well. The program allocates the available serial numbers on the system; if the count differs to the available serial numbers on the system then the system prompts the user to perform a full serial number stock take capture. The business case for the e.bus customer supply allocation is to allow for limited stock to be easily allocated to customers. In the case where an organisation is in a short supply situation and needs to share available stock between customers in an equitable fashion the operator is able to review the available stock then allocate stock on hand as well as incoming stock to customers. The system will provide a view at a master account level of what stock has been allocated. PRICE Imports inventory cost changes via a business object from a.csv file Imports inventory price code changes via a business object from a.csv file This application shows a list of Jobs ready to be closed with the WIP value. The user is able to select multiple Jobs to be closed in a batch process. The business case for the e.bus Invoice copy is to recreate an AR invoice from one SYSPRO company to another. The application posts AR invoices generated in company 1 into another SYSPRO company on the same server, with additional transactions to balance the transaction in the target company. Routes and approves requisitions through a set of approval levels determined by a custom SQL matrix. Requisitions are captured via SYSPRO screens and then routed / approved via script. ADP had the additional requirement that Requisitions need to be captured via a web based system. All capturing, routing and approval is handled by the web application. A generic system would probably work better using SYSPRO's workflow. R R Imports WIP Labour transaction via a business object from a.csv file extracted from Kronos Exports master data (Suppliers, GL Codes, Currencies) from SYSPRO into Fraxion Import database. Imports AP Invoices from Fraxion Export database into SYSPRO. Export and import transactioned via business objects. Imports inventory transactions from Shopware SQL tables into SYSPRO using business objects. Releases in batches instead of one-by-one This programme allows the automatic update of existing SYSPRO prices. Produces a schedule of planned demand for the suppliers of components, based on the MRP plan for the manufacturer Sees which jobs in SYSPRO can be released; then prints out report of Jobs that can be released. No SYSPRO Updates done. The LMC is a system that reserves stock to jobs before the stock is issued to a job. This is done so that stock reserved for jobs are not stolen for other jobs or sold. Page 3 of 8

4 e.bus continued NAME DEV PROJECT DESCRIPTION PRICE e.bus Technical Database Technical Database This is a technical database system using the BOM as the starting point. It is used to load technical information of products far beyond what you can input into SYSPRO. The key aspect of the system is that there is that there is a change control process in place to manage the versions of the technical documentation and producing documentation. The documentation cannot be altered other than through the document change control process. The application specifically for an environment where tight controls must be in place around documentation such as pharmaceutical, medical or cosmetic production R e.bus Retailer order EDI XML Transformation Transforms XML files received from the retailer into XML format required by SYSPRO Business Objects. 2 types of transaction files can be transformed: MRP Forecast Maintenance and Sales Order Entry. The application reads the XML files, transforms it into the correct format and writes it to the DFM input folder. DFM handles the import into SYSPRO. e.bus Tender Management System TMS System Tender Management System - from tender document, through bids and awarding process, to SYSPRO contract creation. Designed for government clinics; uses Word and Excel templates to generate documentation through tag replacement. This is a tender management system using workflow. The tenders are outgoing tender management for suppliers to respond too. In this case it was written for a government organisation that MUST make sure that all purchases are driven through a tender process. There are links to SYSPRO. R e.bus Load planning Delivery Payments Load Planning Procedure Mechanism to import payments into AR based on deliveries scheduled in the load planning module. e.bus IRS system IRS - Incentive & Rebate System Written for the Motor Industry. It interfaces with SYSPRO but can be used as an independent system with users data capturing information and also be interfaced to any system that has ODBC capabilities or File Extract capabilities. (We have interfaced it already to SYSPRO, ACS Embrace, SAP, Protean, Fourth Shift, QAD, Microsoft Excel, Microsoft Access on customer sites) IRS has been in existence for 10 years and is installed at approx. 30 customer sites country wide POA Page 4 of 8

5 e.form SYSPRO STATIONERY STANDARD # FORMATS PRICE All formats as a complete package R e.form Purchase Order Purchase Order Local 4 R Purchase Order Foreign 1 R e.form Invoice Invoice Portrait 2 R Invoice Landscape 2 R Invoice Multi Copies Landscape 1 R e.form Statement Statement Invoice Balances 1 R Statement All Detail 2 R e.form Order Acknowledgement Order Acknowledgement Portrait 2 R Page 5 of 8

6 e.reps BUSINESS AREA REPORT NAME DESCRIPTION PRICE DATA MART SQL VIEWS MICROSOFT REPORTING SERVICES EXCEL SYSPRO REPORTING SERVICES Data Mart Data Mart Foundation Data Mart database and scripts R Accounts Payable AP Aged Creditors Accounts Receivable AR Aged Debtors Finance Creditors ageing report by branch. Debtors ageing report by branch. R Y N Y Y N R Y N Y Y N Balance Sheet Balance Sheet with drill down R Y N Y Y N Income Statement R Y N Y Y N Income Statement Income Statement - Detailed Income statement - IFRS Income statement with drill down Detailed Income statement IFRS Income statement Cash & Equivalent Schedule to financial statements R Y N Y Y N Cash Flow Cash Flow statement R Y N Y Y N Direct Manufacturing Cost Schedule to financial statements R Y N Y Y N Employees Schedule to financial statements R Y N Y Y N Exception Report Schedule to financial statements R Y N Y Y N Fixed Assets Schedule to financial statements R Y N Y Y N Inter Company Schedule to financial statements R Y N Y Y N Interest Schedule to financial statements R Y N Y Y N Inventory Schedule Schedule to financial statements R Y N Y Y N Prepayments Schedule to financial statements R Y N Y Y N Provisions Schedule to financial statements R Y N Y Y N Sales & Marketing Expenses Schedule to financial statements R Y N Y Y N Trade Creditors Schedule to financial statements R Y N Y Y N Trade Debtors Schedule to financial statements R Y N Y Y N Inventory Aged Inventory Detail aged inventory R Y N Y Y N Stock Valuation Inventory valuation R Y N Y Y N Sales Daily Sales Daily sales detail R Y N Y Y N Order Intake Order intake R Y N Y Y N Region Summary Sales by region R Y N Y Y N Retailer by Category Sales by retailer R Y N Y Y N Sales by Customer Sales by customer R Y N Y Y N Sales Margin Sales margin analysis R Y N Y Y N Period Comparison Sales Comparative sales R Y N Y Y N Top Customers Top customer report R Y N Y Y N Page 6 of 8

7 NAME WORKFLOWS DESCRIPTION PRICE GL Workflow GL Journal GL Journal The business case for the GL Journal approval is to manage manual general ledger journals; this allows an organisation to satisfy audit requirements. On the capture of a new GL journal an is sent to the an approver who is authorised to approved the value of the journal. The approval or decline of the journal is through an via a hyperlink imbedded in the . Unreconciled Cash Journal Unreconciled Cash GL Journal Entry The business case for the Unreconciled Cash Journal is to reflect in separate control accounts the value of unreconciled cash book entries not in bank and therefore still a creditor s control liability. Therefore the balance sheet reflects the bank account correctly. This is specifically relevant where payments are processed but are not processed through the EFT before the financial period is closed. On posting the creditors and debtors payments to the cash book a GL Journal is posted to an Unreconciled Bank GL account and an Unreconciled Debtors or Creditors control account. When the cask book entry is reconciled these GL entries are reversed. Debtors Workflow Create Debtor Create Customer Account The business case for the Create Debtor is to authorise the creation of a new debtor account. When a new debtor account is created an is sent to an approver for authorisation. Authorisation can run in two streams where one is to authorise the credit limit and another other key details, such as delivery address or tax number. Update Debtor Update Customer Account The business case for the update Debtor is to authorise the changes to an existing debtor account. When a debtor account changed an is sent to an approver for authorisation. Authorisation can run in two streams where one is to authorise the credit limit and another other key details, such as delivery address or tax number. Debtors Adjustment Debtors Adjustment Transaction The business case for the Debtors adjustment approval is to ensure that adjustments posted in the Debtors payment program are approved before they are allowed. In the Debtors payments and adjustment program, when an adjustment is processed an is sent to an approver before the adjustment is posted in SYSPRO. Creditors Workflow Creditors Creditors Payment Sales Workflow Sales Suspense Release Price Discount Creditors Invoice Creditors Payment Sales Order Suspense Release Discount And Price Changes On Sales Orders The business case for the Creditors approval is to manage creditor invoices received before being processed for payment. On the capture of the suppliers invoice the requisition originator will receive an to approve the supplier's invoice. The originator has the ability to reject the supplier invoice for correction. Once the supplier invoices are approved they can then be added to a payment run. The approval or decline of the invoice is through an via a hyperlink imbedded in the . The business case for the Creditors payment approval is to manage creditor payment before the payment is transferred to the EFT process. On capture of the payment run the authoriser will receive an to approve the payment. On a new payment run being loaded this is sent to an authoriser before the payment run can be released. The approval or decline of the payment is through an via a hyperlink imbedded in the . The business case for the Sales suspense release approval is to manage the order suspense process. When a sales order moves into suspense an is sent to notify an accounts authoriser that a Sales order has gone into suspense and then notify the originator when the order is taken out of suspense. The business case for the price discount approval is to manage discounting of sales where the discount differs from the standard price or discount. When a sales order is updated with a price or discount override the new values are captured into new price or discount custom form fields and a workflow is triggered which sends an to an authoriser. The approval or decline of the new price or discount is through an via a hyperlink imbedded in the . On approval of the new price or discount the sales order is updated and the originator informed that the order can be dispatched and invoiced. R R Page 7 of 8

8 continued NAME WORKFLOWS DESCRIPTION PRICE Purchasing Workflow Requisition P/O requisition approval The business case for the Requisition approval is to authorise requisitions in accordance with authority levels. On initiating a new requisition in SYSPRO the requisition is routed in accordance with the rules imbedded in the workflow. The approval or decline of the requisition is through an via a hyperlink imbedded in the . LCT Pre-Receipt LCT Pre-Receipt with FEC Variance Supplier Contract Price Notification Inventory Workflow Stock Hold Status EDI Collection Supply Chain Transfer Notification Asset Workflow Stock to Asset Pre-LCT stock receipt for shipments Pre-LCT stock receipt for shipments including e.bus Foreign Exchange Cover Notification process when supplier contract prices are changed process for putting stock on hold and managing outstanding purchase orders and sales orders Collect Sell- out Data Notification of the receiving warehouse of an incoming supply chain transfer Converting SYSPRO Inventory stock into Assets The business case for the LCT pre-receipt is to match forward cover consumed with the incoming shipments, and then count the incoming stock before the LCT shipment receipt is processed. Organisations will buy forward exchange cover and allocate the forward cover to the incoming shipments, the budget rate specified on the shipment is often different from the forward cover rate or rates applied to the shipment and this difference will be posted to a variance account. When the physical shipment is receipted the stock is counted and recorded by the system, this includes serialised stock, the actual count is compared to the expected shipment electronically and an is sent to a authoriser to either accept the actual count or request a recount. In addition an will be sent to the shipping clerk if the shipment needs to be adjusted where the actual quantity received differs from the shipment packing list. In this case a voucher of correction would be obtained therefore the shipment should be corrected to reflect the actual shipment. When the stock is receipted the landed cost will therefore be apportioned correctly to the actual stock received. The business case for the LCT pre-receipt with FEC variance is to match forward cover consumed with the incoming shipments, and then count the incoming stock before the LCT shipment receipt is processed. When the physical shipment is receipted the stock is counted and recorded by the system, this includes serialised stock, the actual count is compared to the expected shipment electronically and an is sent to a authoriser to either accept the actual count or request a recount. In addition an will be sent to the shipping clerk if the shipment needs to be adjusted where the actual quantity received differs from the shipment packing list. In this case a voucher of correction would be obtained therefore the shipment should be corrected to reflect the actual shipment. When the stock is receipted the landed cost will therefore be apportioned correctly to the actual stock received. The business case for the Supplier contract price notification is to notify necessary staff of changes to supplier contract prices. R R The business case for the Stock hold status is to manage stock which goes on hold. R The business case for the EDI collection is a mechanism to automatically upload sellout data into SYSPRO through workflow. The sell-out data supplied by retailers must be supplied or converted into a specific format and place into a designated folder before it is uploaded into SYSPRO. The business case for the Supply Chain transfer notification is to notify the receiving destination of an incoming supply chain transfer. When a supply chain transfer is created for a receiving warehouse the responsible person in the receiving warehouse is notified of the incoming shipment. The business case for the Stock to Asset approval is to allow the controlled allocation of stock to an individual, contract or client which is then converted and managed as an asset. R R For more information, please contact Pequita Sampson: tel: +27 (21) cell: +27 (72) pequita.sampson@eoh.co.za Page 8 of 8