SAP Kernel release - Difference between SM51 and System- Status ?

Dear SDN colleagues,
I am a ABAP developer, and have been told by our Basis department that our SAP Kernel is 640.
When I check the following, I get different values:
1) System -> Status : SAP_BASIS is 620
2) Transaction SM51 -> Release Notes: I see SAP R/3 Kernel 640_REL
Can anyone explain why there is a difference in these informations? (and which is the correct one !)
Thanks in advance.
Best regards,
Jodie

Hello Jodie,
First of all there is nothing to be "implemented" as per the note.
Additionally the poor basis guy is saying the correct thing. Check this part:
Solution
The changes are activated with the following patch levels:
4.6D : 1495
6.20 : 764
The paging administration was enhanced.
The error is no longer passed on to other sessions and the trace outputs to determine the error cause have been improved.
The patch levels mentioned are kernel patch levels and have nothing to do with your SAP_BASIS release.Since your kernel is 640 this note is no longer applicable. In my opinion you need to dig for some other note.
Regards.
Ruchit.

Similar Messages

Differences Between Object And System Privileges

Hi,
Whats the difference between object and system privileges in oracle?
Cheers
Paul

System Privileges
A system privilege is the right to perform a particular action, or to perform an action on any schema objects of a particular type. For example, the privileges to create tablespaces and to delete the rows of any table in a database are system privileges.
Schema Object Privileges
A schema object privilege is a privilege or right to perform a particular action on a specific schema object:
For example, the privilege to delete rows from the departments table is an object privilege.
Some schema objects, such as clusters, indexes, triggers, and database links, do not have associated object privileges. Their use is controlled with system privileges. For example, to alter a cluster, a user must own the cluster or have the ALTER ANY CLUSTER system privilege.
A schema object and its synonym are equivalent with respect to privileges. That is, the object privileges granted for a table, view, sequence, procedure, function, or package apply whether referencing the base object by name or using a synonym.
Granting object privileges on a table, view, sequence, procedure, function, or package to a synonym for the object has the same effect as if no synonym were used. When a synonym is dropped, all grants for the underlying schema object remain in effect, even if the privileges were granted by specifying the dropped synonym.

Difference between SYS and SYSTEM user

Hi,
Well, one of my colleagues have asked me the difference between SYS and SYSTEM user .. Normally these are the users which will be under the monitoring of the DBA .. So, how could I know the difference between these two users ..
Please assist me
Regards

SYS is the owner of the database and the owner of the data dictionary.
The objects belonging to SYS cannot be exported. But SYS has the SYSDBA privilege which SYSTEM doesn't.
SYSTEM is a privileged administration user, and typically owns Oracle provided tables other than the dictionary.
SYSDBA is not a role, it is a privilege. You'll find it in system_privilege_map, not in dba_roles.

Difference between Communication and System User

Hello All,
I would like to know the difference between the Communication User and System User.
Definition wise, Yes, I know what they are for?
But My doubt is, why do we need a communication user type for RFC connections when we can use a System user.
Why did SAP designed these two types of users?

It's okay in my books for people to experience the internet as it is and not the way it was individually intended
SU01Solution already solved the problem actually, but there are some very fine peripheral differences still between the user types.
That is why asking a specific question and discussing it's merits / pro's and con's is the best approach and SAP also benefits from it.
Another obvious difference if you do a simple search is that SYSTEM type users cannot issue SAP logon tickets.
There are a few more but as I said these are peripheral and very use-case dependent... so SU01Solution needs to ask a proper and realistic question.
ps: ST01 is not the answer here either...
Cheers,
Julius

Difference Between Physical and System Stock.

Hi Gurus,
I am facing a problem in Executing One Scenario.
Actually we have one Raw Material which contains a "Moisture Contain" Half it own weight.
When we are procuring it, we do it as it is i.e. including the weight of Moisture.
But when we are issuing it for production the scenario is like,
Suppose we require 10 Kg of that Raw Material for 5 Kg of finished product.
Physically we are Isuuing 10 Kg, But in system we are Issuing it as 5 Kg only (i.e "Excluding the Moisture Content of 5 Kg").
But beacuse of this there is a variation in Physical and System Stock.
How to aviod this Variation in Stock?
Please Help.........
Thanks in Advance.

HI
Maintain the moisture content in Component scrap in MRP4 and do all the calculation on dry basis only for FG.
also while procuring the item system will calculate PR qty including the moisture content.
Check with your MM consultant.
Regards
Anupam Sharma

Setting system properties: difference between "-D" and "System.setProperty"

Hi.
I have a program that relies on the jogl library to display graphics. Internally, jogl loads a native library from disk, with a System.loadLibrary() call. In turn, loadLibrary searches the paths in the system property "java.library.path" to find the jogl DLL/SO files. So, it is my responsibility to ensure that the "java.library.path" property is correctly set.
There are two ways that I know of to set system properties: as an argument to the JRE via the "-D" option and from within an application with the System.setProperty method. However, I have noticed that only the former gives the desired behavior. That is, if I do:
java -Djava.library.path=lib MyProgram{code}
the code in jogl.jar is able to successfully find and load the native libraries in lib/, but if I do:
{code:java}System.setProperty("java.library.path", "lib");{code}
at the beginning of main in my program (before the classes requiring jogl are loaded), I end up with an UnsatisfiedLinkError.
Why does this happen? Why do the 2 methods produce different results? Is specifying native library paths on the command line the only way to ensure that they are found?

See the [System Properties Tutorial|http://java.sun.com/docs/books/tutorial/essential/environment/sysprop.html] section on "Writing System Properties" which says:
Warning: Changing system properties is potentially dangerous and should be done with discretion. Many system properties are not reread after start-up and are there for informational purposes. Changing some properties may have unexpected side-effects.
Also see the [setting java.library.path property in java code|http://forums.sun.com/thread.jspa?threadID=627890] thread in the JNI forum.

Activity System status: differences between u0093Openu0094 and u0093In processu0094 status

Dear Experts,
Whats the difference between Open and In process system status? In help.sap.com it: There are four system statuses that represent the life cycle of the business transaction:
Open: has been recently created and not yet processed (for example, contract from the Internet)
In process: administrator is clearing up questions
But, how does the system assumes the In Process status ?? Ive tested business activities creation with different employees assigned and, when editing and saving the business activities with these BPs the system status does not change.
However, in other unknown situations the status system is changed to in Process.
Any ideas about the meaning of the In Process status? And when the business activity switches to that?
Thanks in advance,
Joao

Hi,
These four system statuses that represent the life cycle of the business transaction:
·        Open: has been recently created and not yet processed (for example, contract from the Internet)
·        In process: administrator is clearing up questions
·        Released: contract is complete and legal. Follow-up processes can be started (printing, billing, distribution, releases and so on)
·        Completed: All actions directly linked to contract are completed
·        Closed: all actions indirectly linked to the contract are closed (for example, from R/3: batch run to actual costs)
Each status having its own control at the configuration level. If you observe the following process you may understand the importance of various statuses.
For example in any transaction by default status would be Open. Once the transaction opened by the respective responsible person he will change the status as In Process, Once the assigned task is completed he will change the status as Completed.
Please notice the configuration settings in the following navigation path:
SPRO->IMG->CRM->Transactions->Basic Functions->Status Management-> Change Status Profile for User Status->Select Quotation->Double click on the different status. You can observe the difference.
Hope I convinced.
Best Regards,
Johnny.
Reward if it helps.

Can you tell me some differences between R2 and R3 systems?

Hi,
Can you tell me some differences between R2 and R3 systems?
I guess R2 is used only for mainframe systems some time back. But i dont know why we prefered R3 over R2.
Please clarify this!
Thanks,
Venkatesh.R.

SAP R/3 is
Client server
3 tier
Presentation
Application
Database
Relatively hardware and database independent
ABAP/4 applications runs on application servers.
Dispatcher, shared memory, gateway, work processes are major components of an application server.
SAP R/3 offers
Comprehensive suite of integrated applications meeting the needs of most business
Best practice process design
Ability to configure to
Industry sector
Unique business requirements
In a R/2 System - it is a 2 Tier System based on Mainframe Systems with Intelligent terminals
R/3 is based 3 tier Client Server architechture and supports the R/2 system as well.
R/3 Middleware -
Client server
Uses underlying relational databases
Oracle
SQL server
Ingress
Sybase
Its graphical user interface
Sap GUI
hence R/3 is preffered over R/2 systems because they support Client Server Architecture which is easily configurable,scalable and can integrate with ERP systems and integrate with SOA or Web based Apps.
Thanks,
Saurabh Shukla

What is the difference between ERP2004 and SAP 47 Enterprise?

Currently we have SAP 47 Enterprise with WAS 6.2. I understand ERP2004 is NW and 6.4 sp9. Can any one please let me know the major difference between ERP2004 and SAP 4.7 Enterprise ( more from abap / workflow view)?
Thanks
Swamy

From Abap point of view some of the major add-on in erp2004,netwever :
1) Development of webdynpro studio for java development for portal and iviews.
2) Major abap development uses <b>Abap object oriented</b> methodology, rathet hten old conventional Abap,i.e MVC model (Model,View,Controller) where in it uses concept of classes,interfaces,etc.
3) Advanced BSP tech using MVC model to develop web based modules
4) It is closesly integrated with web-based CRM and BW/APO

What is the difference between mySAP2004 and SAP ERP 2004?

Hi,
Can anybody tell me what is the difference between mySAP2004 and SAP ERP 2004?
If someone has the document, then please mail me at [email protected]
With Regards
tiffny

Hi Tiffny,
actually I don't see a difference as "mySAP2004" is not an official name for anything
There is "mySAP ERP 2004" which is the marketing name for a bunch of functionality provided by several different bits of software components.
Hth,
Michael

What's the difference between WorkflowTask and WorkflowJob in SAP MDM API?

Hi Support,
Could you tell me the differences between WorkflowTask and WorkflowJob in SAP MDM API? And which can represent a workflow in Workflows tab in MDM Date Manager.
Thanks & Regards,
Song

Hi Songxu,
Workflow Task: It is the task(workflow steps like Process, Approver etc) assigned to different user during Workflow. User's use the workflow tabs in Data Manager to view and process workflow tasks. see page 91/654 of Data Manager Guide.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/72b8aaa42301bae10000000a42189b/MDMDataManager71.pdf
Workflow Job: Each workflow is invoked as a job that can consist of multiple records that move through the steps of a workflow (how many records are involved into your Workflow) as a group while simultaneously maintaining record-level granularity. Once the job has been launched, it moves automatically from step-to-step and from user-to-user, showing up in the inbound task queue in each useru2019s Workflows tab for disposition and processing.
Regards,
Mandeep Saini

Time difference between the Identity system and Access System: OAM

I was installing OAM. Performed the below steps.
-installed identity server
-installed webpass
-setup of identity system console
-installed policy manager
-setup of access system console
The above steps were successfull. Then when i was logging into Access system console, i am getting the below error:
Error:there was a problem obtaining the userid. One possible reason for this is a time difference between the Identity system and Access systems (Policy Manager and Access system console).+
The Identity Server, WebPass and Policy Manager are installed on the same machine.
Userdata repository: OVD 10.1.4.3
Policy and Config Data Repository: OID 11.1.1.3
OAM: 10.1.4.3
Windows2008 - 64bit
Found document in metalink similar to this issue. suggested to change ldapmaxofreties. but didn't help.
Any idea on this error. Please Advise.
Thanks in advance.

Try this::
Check Time Difference Between Identity and Access Manager Systems
Check the logfile in the Access Manager install directory. The default location is <$AMinstall_dir>/access/oblix/logs/oblogfile.
If the file exists and it contains following line "skew = slack = " that means the Identity and Access Manager Web Servers are on different machines and have not synchronized time within a minute.
Either synchronize times between the two machines within a minute's accuracy or you can increase the slack by modifying these two files: <$AMinstall_dir>/access/oblix/apps/common/bin/oblixbaseparams.lst: loginslack: <$IMinstall_dir>/identity/oblix/apps/common/bin/oblixbaseparams.xml: loginslack: where numofseconds is more than skew found in the oblogfile.
For example, if you have following line in oblogfile "skew = 121 slack = 60", set numofseconds in the two parameter files to 130. After doing this, Stop the Identity Manager Web Server. Then stop the Identity Server. Start the Identity Server.
Then start the Identity Manager Web Server. Start a new browser session and see if you get the same error.

Difference between Scheduled and released with respect to process chains

HI All,
I am Creating a cube in whcih I want to upload the current status of the process chain.
And the requirement is not to take those process chains whcih are scheduled and not released( only take those process chains whcih have status released)
for the same I dont know what is the difference between Scheduled and Released in respect of process Chains and also from whcih Database table I can get this information.
Please help.
Regards,
Ujjwal

Hi,
Job Status Scheduled means a job has been created and is ready to run but has not yet been triggered.
A release status means the created job has been triggered and is waiting for the opportunity to run. A job can be in released status when it is a periodic Job ( Where once the job is completed it goes to release status), when it is slated for future execution, or when there is a delay due to database overload.
Regards,
Pramod

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Difference between BAPI and IDocs

hello all
what is difference between BAPI and IDocs

Hi,
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
Regards,
Bhaskar

SAP Kernel release - Difference between SM51 and System- Status ?

Similar Messages

Maybe you are looking for