What are Profiles In SAP System

-
  • A profile in the SAP system is an operating system file containing parameters and configuration information of an instance. Since a SAP system might contain from one to several instances, many profiles may also exist. Individual setup parameters can be customized to the requirements of each instance
  • The profiles are an essential part of technical and basis settings of the system, and the values they contain play the most important role when tuning the system.
  •  The profiles are used when starting and stopping the system since they are in charge of allocating or deallocating the necessary resources as specified in the profile parameters

These individual parameters let you customize the following:
  1. The runtime environment of the instance (resources such as main memory size, shared memory, roll size)
  2. Which services are available for the instance (which work processes and how many)
  3. Where other services are located (database host, message server, etc.)
  • The profile files are located under the directory /usr/sap//SYS/profile (logically should point to the directory /sapmnt//profile) which is shared by all application servers belonging to the same SAP system (same SID).
  • An edited profile is not active (its values are not considered by the system) until the corresponding instance is restarted. 
  • If you edit the parameter from RZ11 transaction code the parameters are dynamic changes no need to restart the SAP application server to reflect this changes  but will restore to old value once you restart the SAP application server
  • If you edit the parameters from RZ10 transaction code in the profiles the parameters will be static and to apply this changes you need to restart the SAP application server

Profile Types 

There are several types of profiles available on the SAP R/3 system for correct setup and configuration. These profiles are as follows: 
  1. The start profile, which defines the R/3 services to start. There might be as many start profiles as instances.
  2. The default profile, which acts as a common configuration of profile values for instances taking part of the SAP system. There is only one default profile in a SAP system.
  3. The instance profile, which contains specific instance parameter values. There might be as many as the number of instances.
All the SAP profiles are located under a common directory, /usr/sap//SYS/profile, shared by all instances belonging to the same SID.


Comments

Post a Comment

Popular posts from this blog

SAP Business One Web Client Tiles Not Loading (tiles.svc 500 Internal Server Error)

-
Image
Error: W hile trying to read the field 'bind' of a null object loaded from field com.sap.b1.infra.meta.tile.Tile.action of an object loaded from local variable 'tile" when we are logging into specific company Issue: This issue mainly occurs when adding any web client extension tile to the web client home page and you unassign the extension from the extension manager. Solution: Delete the existing users from the SAP Business One and OUSR table and then recreate the user. Then tiles should load in the Web client.
Read more

SAP Business One Company Initialization Error SAP DBTech JDBC: [259]: invalid table name: Could not find table/view M_TIME_DIMENSION in schema _SYS_BI

-
Image
 Error:  2022-04-29 11:03:39|ERROR|ENABLEMENT|Failed to re-initialize company :module id=Hana Model Deployer; cause:com.sap.businessone.model.renew.exception.ModelException: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259]: invalid table name:   Could not find table/view M_TIME_DIMENSION in schema _SYS_BI: line 4 col 14 (at pos 99)| 2022-04-29 11:03:38|ERROR|MODEL_DEPLOYMENT|Failed to execute sql statement: Create View Next6MonthEndView  as Select Top 6 Year, Month, Max(Date_SQL) as MonthEnd From _SYS_BI.M_TIME_DIMENSION Where Date_SAP <= Last_Day(Add_Months(Add_Days(CURRENT_DATE, 1-DayOfMonth(CURRENT_DATE)), 6)) and Date_Sql >Last_Day(CURRENT_DATE) Group By Year , Month Order By Year Desc, Month Desc, root cause: SAP DBTech JDBC: [259]: invalid table name:   Could not find table/view M_TIME_DIMENSION in schema _SYS_BI: line 4 col 14 (at pos 99)| Solution:   Login to HANA studio  Run the below Query from SYSTEM...
Read more