Tuesday, January 3, 2012

SAP Application Modules


SAP has several layers. The Basis System is the heart of the data operations and should be not evident to higher level or managerial users. Other customizing and implementation tools exist also. The heart of the system from a manager’s viewpoint are the application modules. These modules may not all be implemented in a typical company but they are all related and are listed below:
  • FI Financial Accounting–designed for automated management and external reporting of general ledger, accounts receivable, accounts payable and other sub-ledger accounts with a user defined chart of accounts. As entries are made relating to sales production and payments journal entries are automatically posted. This connection means that the “books” are designed to reflect the real situation.

  • CO Controlling–represents the company’s flow of cost and revenue. It is a management instrument for organizational decisions. It too is automatically updated as events occur.
  • AM Asset Management–designed to manage and supervise individual aspects of fixed assets including purchase and sale of assets, depreciation and investment management.
  • PS Project System–is designed to support the planning, control and monitoring of long-term, highly complex projects with defined goals.
  • WF Workflow–links the integrated SAP application modules with cross-application technologies, tools and services
  • IS Industry Solutions–combine the SAP application modules and additional industry-specific functionality. Special techniques have been developed for industries such as banking, oil and gas, pharmaceuticals, etc.
  • HR Human Resources–is a complete integrated system for supporting the planning and control of personnel activities.
  • PM Plant Maintenance–In a complex manufacturing process maintenance means more than sweeping the floors. Equipment must be services and rebuilt. These tasks affect the production plans.
  • MM Materials Management–supports the procurement and inventory functions occurring in day-to-day business operations such as purchasing, inventory management, reorder point processing, etc.
  • QM Quality Management–is a quality control and information system supporting quality planning, inspection, and control for manufacturing and procurement.
  • PP Production Planning–is used to plan and control the manufacturing activities of a company. This module includes; bills of material, routings, work centers, sales and operations planning, master production scheduling, material requirements planning, shop floor control, production orders, product costing, etc.
  • SD Sales and Distribution–helps to optimize all the tasks and activities carried out in sales, delivery and billing. Key elements are; pre-sales support, inquiry processing, quotation processing, sales order processing, delivery processing, billing and sales information system
Each of these Modules may have sub-modules designed for specific tasks as detailed below.

Monday, January 2, 2012

SAP Support Packages


What is Support Packs in SAP:
SAP releases Support packs, which are a collection of advanced corrections.
Types of Support Packages are listed below:
HR Support Package
ABAP Support Package
APPL Support Package
Basis Support Package
Add-on Support Packages
These are available for download directly from the SAP Service marketplace at below link
SPAM package download: service.sap.com/patches
On demand the Support packs available are sent in form of CDs to SAP’s customers. The system should be update by the designated personnel as early as possible. The support packages have certain dependencies and the same is to be checked on. Basis and ABAP support packages can be loaded independently whereas special care is to be taken while loading application support packages to include the CRTs of addon packages otherwise some conflict can arise and system can go to an unstable state.
_
_
_
How to apply Support Packs (SPAM package) to SAP :
After collecting the required information on CRTs and the like, the Support packs can either be downloaded from the SAPNET or uploaded from (Support packages) CD into the usr/sap/trans/EPS/in directory. The CAR files will also have to be extracted to the same directory.
Login to the system on client 000 – With any user-id other than SAP* or DDIC. The login-id should have SAP-ALL and SAP-NEW authorizations.
Run transaction code SPAM to invoke the SAP Patch manager. You can choose the upload button to upload data directly from /usr/sap/trans/EPS/in directory on the server or from a path on your local Front end.
Execute the “SPAM” transaction again. You will now be able to see the support packs window. Use the drop down box menu to verify the queue. The support packs will be in the queue followed by their corresponding CRT’s for the different add-on. Press the consistency check button to verify the queue is okay.
Go to the Menu Option settings on the SPAM screen and change the settings from ”S” to “T” (Standard to Test mode) The queue may be applied in test mode to check if it has conflict with any object that is already modified in the system. If there are any modifications to the program that the hot pack is also affecting, then the hot pack will create versions for the same. It will make the program delivered by it to be the current request the active version. Transaction “SPAU” (SAP Adjustments) will need to be run to make the required adjustments. If CIN programs are also affected, please check with SAP India.
_
_
_
Please Note:
Make sure that you have applied the latest SPAM update before you apply any other patches.
Always apply patches to your test system before you start to apply them to your production system!
Only the system administrator should be able to download, apply, confirm, or reset the status of patches. To use all the SPAM functions, you require the authorizations.S_CTS_TR_ALL and S_CTS_ADMIN. You can find both of them in the authorization profile S_A.SYSTEM
Ensure that you are logged into client 000 with the proper authorizations. If you log into another client, or do not have the correct authorizations, you can only use the display functions.
Make all the users log off before you apply patches in scenario ‘S’. During the patch application steps, the R/3 system must not be in use, i.e. only the system administrator is allowed to be logged on. Otherwise you risk program terminations.
Shut down all application servers except the central one for the duration of the import. Otherwise, buffer synchronization problems with program terminations, and possibly data inconsistency, may result.
You cannot have any incompletely applied patches in your system. To check this, under Directory choose Aborted patches and then choose Display. No patches should be displayed. Under the section Patch, the status should display a green traffic light.
Check the logs before confirming the patch application.
Never apply patches directly with tp. You will lose all of your modifications and overwrite your Add-On, if you have installed one. If you have made a modification adjustment for the Patch Queue in your test system, ensure that you do not import the resulting modification adjustment transport into further systems until you have applied the same patches to these systems.
While a patch is being applied the session is blocked. Open a second session before you apply the patch to avoid logging on again.

Sunday, January 1, 2012

How to install Language using SMLT


Language Installation in SAP with SMLT
Steps to install extra languages in to a SAP system.
1. Download Language DVD from SAP Service Market Place suitable to your SAP ECC version(e.g SAP 4.7, ECC 6.0 etc)
2.Place .PAT files to EPS/in folder.
3.Login to SAP in client 000 with Admin user.
4. Execute SE38
5. Execute program RSCPINST
6.Add an entry for the language you are willing to install.
7. Execute transaction SMLT
8. Create a new entry in SMLT for the required language. Give Supplementation language as English.
9.Click on the Import Language/Package symbol next to newly created entry for your language.
10.Default path is set to EPS/in folder, where it will search for the .PAT file required.
11.Found language should show either Green or Yellow button. If it is showing Red button it means you have downloaded the wrong source. Double check on SAP Service Market Place and download the right source files.
12. Press Execute to install the selected Language.
13.Monitor the import process in SM37 and Import transport logs.
14.Once installation get finished go to SE38, execute RSCPINST.
15. Click on Simulate button and copy new value for parameter zcsa/installed_languages.
16.Go back and activate the settings.
17. Go to RZ10 and change instance profile.Add new parameter zcsa/installed_languages and set its value as suggested in point 15 above.
18.Restart the SAP instance and try login with new Language.
19. Go to SE38
Execute RSTLAN_IMPORT_OCS
Select the newly installed language and press OK
It will show you the support packages whose language parts you want to import.
20. GO to Next screen.
Copy the PAR or CAR files to EPS/in folder for all support packages showing in RED.
This will import the language specific parts of those support packages.
Press Import Language Data and Overwrite.
It will show you the message “The Support Package Language Data was imported correctly.All system languages are up to date.
21. Next step is to copy the client specific data to required client.
Login to yr non default client or product client.
Go to SE38 and execute RSREFILL.
22. Refference Language EN
Language to be updated Newly installed one
Update Mode I
Log Directory sapmnttrans*.snd
23. Go to SE38
Execute RSTLAN_SUPPLEMENT_UNI
Select your language from drop down
Press Client Maintenance with Customizing Translations