Technical Proposal Group6
Technical Proposal Group6
Group 6
Meet Nalin Mehta Mithun Nambiar Moloy Sundar Ghosh P. Sujit Parantap Sharma
Project Controlling
Requirements 1) Review, Approve or Reject timesheets 2) Perform Period Closeout 3) Baselines
Finance module
Requirements 1) Fixed Asset Accounting :Able to define fixed assets at different levels such as group asset 2) Fixed Asset Master Data : Able to maintain the information like asset number etc in the fixed asset master 3) Addition of Fixed Assets : Able to allocate a unique asset number upon creating master record 4) Depreciation and revaluation of fixed assets 5) Corporate Budgeting/ Analysis a) Revenue/ Operating Expenditure budget b) Capital Expenditure Budget c) Budget Control d) Reporting
General ledger
Requirements 1) Global settings 2) Accounting Period 3) Chart of Accounts 4) GL Master Data 5) GL Transaction Posting
Payroll
Requirements 1) Payroll - (Salary) 2) Allowance (Salary) 3) Deduction - (Salary) 4) Tax and Provident Fund (Salary) 5) Benefits and Claims (Salary)
Training Comprehensive Documentation on the software Step by step user manual Continuous updates Audio / Visual user guides User guide for small scale maintenance Co- documentation Source code Full user license training ESS training
Documentation
Training Schedule
The team would be helped to document data conversion requirements as part of the current state review and the development of the future state process We would develop a conversion strategy for the following types of data : 1. Static files master data such as customer 2. Dynamic files transaction data such as open Purchase orders 3. History transaction history Implementation of your IT staff in the following ways: Project management Data conversion planning Data mapping: current system to the new system Data migration: exporting and importing Managing data cleansing activities Quality assurance
We will define the new data that needs to be collected Our team would help you create spreadsheets to collect and segment the data into logical tables Data collection will include collecting whole data entities relating to areas that are being automated for the first time in the organisation or Specific attributes relating to existing data entities e.g. new parameters relating to existing items that will drive new supply chain planning functionality
Testing is a critical activity in an ERP data migration project and can be manual or programmatic. Typically a combination of both will be employed Manual testing may involve manual checking of a defined sample size of records or of specific fields Programmatic testing may include checking data formats or searching for specific errors A set of test cycles would be defined and followed. This may include unit testing of individual data conversions, end-to-end test cycles of all conversions in sequence and in tandem with any related manual steps, and transact ability testing
Review and weeding out of unneeded information such as customers who havent purchased in a while or are no longer in business Data cleansing is the manipulation of extracted and collected data into the formats required by the new system as well as removal or correction of out of date or incorrect data before it is loaded This can be carried out in a number of stages. The first is to cleanse the data in the legacy system before extraction A second stage of cleansing is to manipulate the data subsequent to extraction
Different records referring to the same product, customer or supplier may exist in different systems and these will need to be harmonised into a single record
Comprehensive integration of business functions Integration of functional modules across the enterprise. Seamless connectivity across departments
Online collaboration community for product manufacturers and their supply chains to efficiently collect and manage product sustainability data. Connect directly with suppliers and customers to streamline and better manage your relationships Request, manage, and update component declarations Create and manage product decalarations as well as declaration requests Manage application content, legal information, and community knowledge Stay informed about features by sharing and discussing best practices
secures the data communication paths between the various SAP system client and server components. There are wellknown cryptographic algorithms that have been implemented by security products supported and with SNC, you can apply these algorithms to your data for increased protection. receive application-level, end-to-end security. All communication that takes place between two SNC-protected components is secured (for example, between the SAP GUI for Windows and the application server). use additional security features that SAP does not directly provide (for example, the use of smart cards). change the security product at any time without affecting the SAP business applications.
robust
implementation faster rollouts de-risked upgrades dependable production support best quality development enable our clients to control and predict costs optimizing your investment