User talk:NaguPandian

--NaguPandian 10:54, 27 December 2005 (UTC)--NaguPandian 10:54, 27 December 2005 (UTC)--NaguPandian 10:54, 27 December 2005 (UTC)I have more than 5 Years of experience of Java and ERP Solutions. Here I am posting the SAP Integration with Java and Technical scenario as shown below

SAP integration with Java For :

Problem Specification

This integration will involve creating SAP integrate data into the Java using JConnector. This system will utilize an Desktop Applications, on-line, web-enabled interface and a back-end database for ERP packaging structure with ordering, inventory, Purchase Order, Sales Order and customer management. The system will be developed on behalf of BAPI functions using JConnector interface caller into the Java Application Currently operates a small number material list from the SAP using the remote access from any geographical location with Single authorized user. The site, in its initial design, will essentially replicate many of the functions normally performed at one of the “BAPI-FUNCTIONS”, with requiring the BAPI Functions and Table name to drive to java develop. System must be informative, robust, responsive, user-friendly, and secure. System should be designed to allow possible future expansion (i.e. more transaction, more product lines, more warehouses, etc.), and for potential porting to other businesses.

The Specification Document I. Input/Output Specifications A. Input Specifications (SAP User’s View) System site will be designed that allows the user to input the following Information from any computer with Internet access:  Authorized SAP profile information: (applicable. properties file)

o Client (string format, 8 characters max.) o User name (string format, 20 characters max.) o Password (string format, 20 characters max.) o Hostname (SAP Server name or IP address.) o Language (Which language authorized to the user, 2 digits required) o System Number (numeric format, 2 digits required)

Material List Information:

o Material-to name search (string format, 40 characters max.)

B. Output Specification (Materials View) The system will output information to the user’s welcome screen, with the search of the Material functions.

A main “login” screen, so that the user’s profile can be created and/or recalled from the server. A Material review screen, where various Materials and description can be viewed. The complete materials shown into the Text Area boxes into the Desktop Application A sales order details of the information are retrieving to the console level. Meta Data retrieve from SAP to java console

C. Exception Handling Example exception situations that the program is anticipated to encounter are: User logon and/or password is incorrect. o User ID must be between 6 and 12 characters, include letters and/or digits, but no special punctuation marks. o Password must be between 6 and 12 characters, include letters and/or digits, but no special punctuation marks. User profile information is incorrect or incomplete. o User must enter authorized name. Materials give specific material name or choose for all put *. o Material no limited of any

II. Performance Specifications Operating environment: System will be JSP for web, Swing for Desktop, JSP meaning it will be able to run in any mainstream web browser available to the home computer user. The client PC will not need any special software to support this application. Response time: Response time from any given screen to another screen should be limited to a maximum of 7 seconds, except in cases where response time is affected by activities out of the control of the program (such as slow response from external sources). Memory requirements: Any user system that is capable of supporting a web browser will be able to access the system. III. Delivery Schedule Proposal: Planning: Design: Coding: Final Product Delivery with Documentation: