SAP Business Navigator

SAP has streamlined business processes to take full advantage of the most efficient business and technological processes. SAP provides the Business Navigator tool to provide a graphical representation of the SAP process flows and integration across modules. The Business Navigator lists the business objects associated with processes as well as the SAP programs that respond. In addition, the Business Navigator displays the related SAP documentation for selected objects. The Business Navigator can be displayed in either the Component view or Process Flow view. The Component view shows each process and business object in relation to its functional module. The Process Flow view displays each process in relation to overall business function, regardless of system functional module ownership. This allows you to see the big picture of your business plan.

 
 

The Business Navigator can be displayed by following the SAP application menu path

Tools>Business Engineering>Business Navigator.

Transaction code SB10 takes you to the Component view

Transaction code SB09 takes you to the process Flow view

Many companies use the implementation of SAP as an opportunity to reengineer their entire business and develop the most efficient processes available. SAP has invested a great deal of time and money into delivering the most efficient business-friendly processes in the system's your company doesn't have the time or resources to undertake a full reengineering effort at the very least, you should use the implementation to change and Streamline problem processes in your business. A system implementation is the best opportunity you will ever have for change.

 
 

There are many small companies that have neither the time nor the resources to undertake a full business process reengineering project, but they are still implementing SAP. The ASAP (Accelerated SAP) methodology developed by SAP provides an excellent tool for small companies to rapidly implement SAP and take advantage of its integrated business processes. Key incentives for adopting ASAP are that you don't need any modifications to standard SAP source code and you can still take advantage of standard SAP best business processes. This type of quick implementation is proving very successful in many different industries and business segments.

 
 

Try this link for more information

 
 

 
 

 
 

  

Terms in SAP

Term	Definition
ABAP	Advanced Business Application Programming. The programming language of SAP’s ERP software.
Basis	The underlying technology base that allows SAP's functional applications and modules to interoperate.
Blueprinting	Phase 2 of the implementation process. During this period, the project team will identify the state’s organizational structures, design new business processes, install the SAP software and begin training for the team.
Business Warehouse	SAP’s term for a data warehouse, where state data is stored.
CATS	Cross Application Time Sheet. An electronic time sheet for recording employee working times.
Configuration	The process of establishing the SAP settings to support specific business rules, validations, and default values for North Carolina.
Go Live & Support	The fifth and final phase of the implementation. This is when the system will move into actual production.
EE	Employees. This abbreviation is used for employees in the SAP software.
ERP	Enterprise Resource Planning. A collection of software applications that use a common database to integrate an organization’s business processes.
ESS	Employee Self Service.
Infoset	A SAP Query element, Infosets determine to which tables, or fields within a table, a query can refer. Infosets are usually based on table joins or logical databases.
Infotype	A set of data that is grouped together according to subject matter. From the user perspective, infotypes are entry screens that support the maintenance of infotype records.
Integration	Allows data to flow freely from one business area to another without having to pass through time-consuming and trouble-prone interfaces. Integration also enables the maintenance of data from various sites.
Landscape	All the R/3 systems, which share a common transport directory.
Legacy Applications	The numerous and dated computer programs currently being used by the client. The mySAP ERP software will eventually replace those involving human resources, payroll, budget management, accounting, and tax/revenue.
MSS	Manager Self Service.
MySAP.com	The specific type of ERP software being implemented by North Carolina.
Module	The SAP software is comprised of several functions (e.g., time management, payroll, personnel administration), which together form an integrated system.
Portal	The Web interface that will be used by employees and managers to access the HR/payroll system.
Project Preparation	Phase 1 of integration, which included the organization of the project team, various team-building activities, the project kick-off, and initial planning.
Realization	Phase 3 of the implementation. During this time, the project team will configure the HR and payroll modules, and implement processes defined in the “blueprint” that was developed in Phase II.
SAP Query	Tool that allows users without knowledge of the ABAP programming language to define and execute their own reports.
SMEs	Subject Matter Experts. Client's representatives who are considered to be specialists in certain business areas (modules).
Stakeholder	A person, department or organization that has an interest in the success of a project.
Statement of Work	A document that sets forth services to be performed.
System Test	An implementation activity that tests the interfaces between sets of applications or functional areas in a new system. It verifies the ability of the system to handle data and operating requirements.
Time Recording	Time recording captures and evaluates all employee time information required for running payroll in payroll accounting. Time information includes attendance, absence, or availability data for employees.
UAT	User Acceptance Testing. The final stage of functional testing before the Go Live phase.
User Group	Every user can be assigned to specific groups based on their role in the organization.

LSMW - Step by Step

Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method. 

1. TCode : LSMW. 
2. Enter Project name, sub project name and object name. 
Execute. 
3. Maintain object attributes. 
Execute 
select Batch Input recording 
goto->Recording overview 
create 
recording name. 
enter transaction code. 
start recording 
do recording as per ur choice. 
save + back. 
enter recording name in lsmw screen. 
save + back 

Now there will be 14 steps. 
2. MAINTAIN SOURCE STRUCTURES. 
Here you have to enter the name of internal table. 
display change 
create 
save + back 

3. MAINTAIN SOURCE FIELDS. 
display change 
select structure 
source_fields->copy fields. 
a dialogue window will come . 
select -> from data file 
apply source fields 
enter No. of fields 
length of fields 
attach file 
save + back 

4. MAINTAIN STRUCTURE RELATIONS 
display change 
save + back 

5. MAINTAN FIELD MAPPING & CONVERSION RULE 
display change 
click on source field, select exact field from structue and enter 
repeat these steps for all fields. 
save+back 

6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED 
execute 
save + back 

7. SPECIFY FILES. 
display change 
click on legacy data 
attah flat file 
give description 
select tabulatore 
enter 
save + back 

8. ASSIGN FILE 
execute 
display change 
save + back 

9. IMPORT DATA. 
execute 
display change 
save + back 

10. DISPLAY IMPORTED DATA 
enter ok, it willl show records only. 
back 

11. CONVERT DATA 
execute 
display change 
save + back 

12. DISPLAY CONVERTED DATA 
execute 
display change 
save + back 

13. CREATE BATCH INPUT SESSION 
tick keep batch input folder 
F8 
back 

14. RUN BATCH INPUT SESSION. 
sm35 will come 
Object name will be shown here 
select object & process 

How to Start 'AS IS' Statement?

How to start doing the project in 'AS IS' ?

Are you working as a functional person?

This work is of a functional consultant.It involves understanding the complete functionality of the system.

Like suppose you are implementing SAP HR module for them then in the AS-IS and TO-BE phase, you need to prepare all the documents of the process flow (you can prepare them in word). Like suppose you are implementing for PA then you need to identify how many personnel areas you need to make, how many subareas you will make, employee groups, subgroups, based on what you are classifying them? This all will come in the master data document which has to be approved from the client whoever he is. It involves detailed understanding of how the HR department is functioning because based on that only you would provide a solution to them. 

Like if the current system is on mainframe or for some specific applications like for recruitment the system is on mainframes and the client wants to keep that system as well then interfaces need to be identified which will be there because you will have to upload the data to sap system using bdc.

Like this for every process there will be a document.Even for actions like:

- Hiring
- Newly Hire
- Termination
- Transfer
- Layoff etc

You will have to see what all actions your client wants, like if there is an action transfer which is run for employee what all will be the reasons you will be configuring for that action. This will be told by the client which can come out after a series of meetings and after discussions you will have to come out with the document that these will be action types. These will be the action reasons, these will be the action codes for that. This will be in the TO BE process document.

After this phase is over complete configuration can be done.

Actually AS-IS process in summary involves a :

1) Series of meeting with the client.

2) Gathering complete information about the existing system.

3) Preparation of the blue print documents describing the complete AS-IS process ,i mean the existing system.

4) Flow charts should be included in the as-is blue print process flow document describing the complete process.

5) After this is finished u have to give the TO-BE process structure that will be implemented in SAP.

6) After that there will be some things which cannot be implemented in SAP so the gaps are to be identfied.

7) These gaps are to be documented in white paper for the client.

It is a lenghty process but not so difficult only the thing is that the functionality is to be understood properly.