Difference between different Technical systems

Please tell
We can define a technical system as :
Web AS ABAP or Web AS JAVA or Standalone JAVA or Third party or
Exchange Infrastructure
What is Web AS ABAP system? What is Web AS JAVA system? What is standalone JAVA?
Thanx in advance
Harsh

Hi Harsh
Web AS ABAP
Web AS ABAP technical systems, ranging from any SAP system to an APO server or CRM server, are based on the same Basis Component (BC), which includes the ABAP interpreter, ABAP Dictionary, ABAP Workbench, and so on. A dedicated database, which stores most of the data of the BC and the application components, is associated with the system.
Web AS Java
Web AS Java systems consist of one or more instances and each instance is installed on a separate host. An instance itself consists of cluster nodes that can communicate with each other.
Standalone Java
Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can also be installed as an operating system service or as a daemon.
Third-Party
Third-party technical systems contain third-party software components and products.
Third-party systems are not automatically registered in the SLD. Therefore, you have to create them manually by creating:
Third-party products
Third-party software components
Third-party technical system
Third-party business system
Exchange Infrastructure (XI)
XI technical systems are the infrastructure systems (such as integration servers and adapter engines) of XI.
Cheers...
VAsu
<b>** REward POints if found useful **</b>

Similar Messages

Difference between the Logical System n Client

Hi Guys,
i need a some information plz help me.
what r the differences between the logical system n the client.
plz give me the detail explanation
appreciated with points
regards
kk

Hi there,
'logical system' is used to identify an individual client in a system, for ALE
communication between SAP systems. That's why you see a field for 'logical
system' in the client master data in SCC4 (table T000).
Client can be defined as commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.
Hope it helps
Cheers
Deepanshu

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 essbase technical and functional consultant

Hi Essbase/Planning gurus, i am new to hyperion essbase/planning, please help me on below questions.
1) Difference between essbase technical consultant and functional consultant (Roles)
2) Difference between Hyperion planning technical consultant and functional consultant (Roles)
Thanks in advance,
Raraju.

Hello Raraju,
I will give it a try.
Essbase and Planning have technically a different concept of roles. I think, this was not your question about.
When looking at the job responsibilities of a technical consultant in Essbase then he/she will be responsible for the server. Take care that it is running performant, has sufficient resources etc.. The person will monitor log files for possible or upcoming problems. Further, the person will set-up connections to other data sources if needed. The person will know about the OS, Networks, Webservers and the technical side of Essbase/Planning.
The functional consultant will know the details of the application(s) and will maintain them for the users. He/she will create changes to the application and helps the users to use the product. The person will know about finance/controlling and the application side of Essbase/Planning.
Regards,
Philip Hulsebosch

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.

Differences between different versions of BW 2.1C,3.0A and 3.5

Can anybody tell me the differences between different versions of BW.
I m new to SAP BW,i directly learned in BI7.0.So please anybody let me know the difference in implementation of features in 2.1C, 3.0A ,3.5 ,if possible BI7.0 also

please read this:
http://help.sap.com/saphelp_nw70/helpdata/en/b2/e50138fede083de10000009b38f8cf/frameset.htm

Differences between different IR versions

Can you please tell me the differences between different IR versions?
Thanks

Here are the 11.1.2 specific IR changes: from the R&A Readme:
Interactive Reporting
Support for SFTP
SFTP protocol is now supported for distribution outputs generated by jobs and schedules. For more information, see the Hyperion Reporting and Analysis Framework Administrator’s Guide.
Interactive Reporting Roles
Two new roles, IR HTML Viewer and IR WebClient Viewer, have been added for Interactive Reporting. For additional information, see the EPM User and Role Security Guide.
Removal of CMC
CMC is no longer a separate web application. All functionality has been merged into the Administer module. For more information, see the Hyperion Reporting and Analysis Framework Administrator’s Guide.
There are also several Workspace changes which would could impact IR users as well, depening on your particular set up , it might be worthwhile reviewing those as well.
Cheers, Iain

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 different Invoices

Hi Frnds,
Can any body let me know the difference between Commercial invoice,
Tax Invoice & Retail Invoice in terms of Bussiness as well as SAP.
Regards
sunil

A commercial invoice is a bill for the goods from the seller to the buyer. Commercial invoices are utilized by customs officials to determine the value of the goods in order to assess customs duties and taxes.
In general there is no standard form for a commercial invoice although they tend to contain many of the following features:
seller's contact information
buyer's contact information
consignee's contact information (if it is different from the buyers)
invoice date
a unique invoice number
sales terms (usually in incoterm format)
payment terms
currency of sale
full quantities and description of merchandise (Generally this includes unit price and total price. Product descriptions should be consistent with the buyer's purchase order. Including the Harmonized System commodity codes can be helpful, especially in countries that are WTO members.)
certification that the invoice is correct (Standard language is "We certify that this invoice is true and correct."
Excise Invoice is charged on the sale of a particular good.
For Combination of creating 2-3 invoices we need to maintain the same
- Payer.
- Shedule Lines.
- Payments Terms .
Excise invoice Original for Buyer copy, whether prices are inclusive or exclusive of excise duty.
The invoice in which the Excise duties are included.
As per Indian tax system, Excise duty (16%) is payable by each manufacturing unit on the value of manufactured goods / on the value added. The manufacturing plant is supposed to submit an excise duty report on fortnightly / monthly basis. Various registers (RG1, RG23A, RG23C, PLA) are maintained for that purpose, which record all the transactions including movement of goods, cenvat credit available and cash balance available.
In SAP, we use transaction j1id for configuration and j1iin, j2i7, j1i5, j2i5, j2i6, j1ip for creating, extracting and printing excise invoice.
Rewards Points if it useful.

Massive copy of BW transformation between different source system

Hi all,
in my BW I have different source systems. I have mapped several objects to one source system.
Now I need to copy all the transformation to other source systems. These source system are different instance of ECCs, there are the same extractor in all the systems.
I can't use the BDLS becouse these move the transformations between the system not copy it.
I try to create a Transport and using the Conversion of Logical System Names but this change only the objects with source sytems dependencies, it don't change the technical name of transformation, and do not create a tranformation to the new system but overwrite the existing one.
Do you know if there are some program or some procedure to copy transformation between sourcesystem in BW?
Thanks in advance
Mario

Hi,
you can do a Retrofit (System copy), Generally, retrofit happens between two different BW systems.
check with your basis team if the retrofit is possible with in the same BW system but for different clients.
Note : System copy will overwrite all the objects.
Regards,
Sudheer

Difference between Existing QM system and Vendor QM system in QI info recor

In Quality info record, under inspection control tab, I find 2 options for certificate monitoring, one is Existing QM system and another one is Vendor's QM system, Please advice the difference between them.

hi dear,
There is no such difference, only he thing is when u developed or upload some new vendor based OM system which is valid from its industry type. Like in manufacuring it is strongly recomended that vendor is certified by some authorized agency like ISO, TUV Nord etc. so when u use this and configure it in ur sap system than u may change the setting and use Vendor QM system in Q-Info, while if is not there than u may use existing QM system of ur own company if u uploaded in SAP or u may keep it blank if not required.
if we use Vendor QM system than it is best practice to maintain QM procurement and related document like Certificate or Delievery assurance from vendor in MM02 ---> QM view.
I hope this short one cleares ur point.
regards
Shailendra Gaur
SAP-QM

In OAWS difference between different stores

HI ALL,
I have worked on tcode OAWS but could not find exact difference between the follwing
-Storing for subsequent entry
-Storing for subsequent assignment
-Store and entry
-Store and assign
-Assign and store
Can nyone make me clear.
Regards,
Tejaswini

Hi
VENDOR_SYS --> System in which POs can be created for this Vendor. In other words system where the Vendor has been created for the purchase organization.
VENDOR_ACS --> System where Accounting for Vendor has to be checked. IN other words, its the FI system which take care of Financial transactions related to the vendor
Regards
Virender Singh

Difference between different RFCs

Hi All,
Could you please provide me with some useful material or brief knowledge where i can find out :
what is an s-RFC, t-RFC and q-RFC ? ?
Where all these are used ? ?
And what is the Difference between them ? ?
Regards,
Arkesh Sharma

Please check this link
http://help.sap.com/saphelp_nw2004s/helpdata/en/62/73241e03337442b1bc1932c2ff8196/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
The qRFC Communication Model
qRFC Properties and Possible Uses
All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC). RFCs can be used to start applications in remote systems, and to execute particular functions.
Whereas the first version of the RFC, the synchronous RFC, (sRFC) required both systems involved to be active in order to produce a synchronous communication, the subsequent generations of RFC had a greater range of features at their disposal (such as serialization, guarantee for one-time-only execution, and that the receiver system does not have to be available). These features were further enhanced through the queued RFC with inbound/outbound queue.
Communication between applications within an SAP system and also with a remote system can basically be achieved using the Remote Function Call (RFC). Here, the following scenarios are possible:
· Communication between two independent SAP systems
· Communication between a calling SAP system and an external receiving system
· Communication between a calling external system and an SAP receiving system
The following communication model shows what these communication scenarios may look like in reality. The actual sending process is still done by the tRFC (transactional Remote Function Call). Inbound and outbound queues are added to the tRFC, leaving us with a qRFC (queued Remote Function Call). The sender system is also called the client system, while the target system corresponds to the server system.
Scenario 1: tRFC
This scenario is appropriate is the data being sent is independent of each other. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, data is transferred by tRFC, meaning that each function module sent to the target system is guaranteed to be executed one time only. You cannot define the sequence in which the function modules are executed, nor the time of execution. If an error occurs during the transfer, a batch job is scheduled, which sends the function module again after 15 minutes.
Scenario 2: qRFC with outbound queue
In this scenario, the sender system uses an outbound queue, to serialize the data that is being sent. This means that function modules which depend on each other (such as update and then change) are put into the outbound queue of the sender system, and are guaranteed to be sent to the target system one after each other and one time only. The called system (server) has no knowledge of the outbound queue in the sender system (client), meaning that in this scenario, every SAP system can also communicate with a non-SAP system. (Note: the programming code of the server system must not be changed. However, it must be tRFC-capable.)
Scenario 3: qRFC with inbound queue (and outbound queue)
In this scenario, as well as an outbound queue in the sender system (client), there is also an inbound queue in the target system (server). If a qRFC with inbound queue exists, this always means that an outbound queue exists in the sender system. This guarantees the sequence and efficiently controls the resources in the client system and server system. The inbound queue only processes as many function modules as the system resources in the target system (server) at that time allow. This prevents a server being blocked by a client. A scenario with inbound queue in the server system is not possible, since the outbound queue is needed in the client system, in order to guarantee the sequence and to prevent individual applications from blocking all work processes in the client system.
Properties of the Three Communication Types
To help you decide which communication type you should use in your system landscape for your requirements, the advantages of the three communication types are listed below:
1. tRFC: for independent function modules only
2. qRFC with outbound queue: guarantees that independent function modules are sent one after each other and one time only (serialization). Suitable for communication with non-SAP servers.
3. qRFC with inbound queue: in addition to the outbound queue in the client system, an inbound queue makes sure that only as many function modules are processed in the target system (server) as the current resources allow. Client and server system must be SAP systems. One work process is used for each inbound queue.
The qRFC Communication Model
Purpose
Communication within an SAP system or with a remote system can take place using Remote Function Call (RFC). This enables the following scenarios:
· Communication between two independent SAP systems
· Communication between a calling SAP system and an external receiving system
· Communication between a calling external SAP system and an SAP system as the receiving system
Implementation Considerations
The following communication model shows how these communication scenarios can occur in practice. tRFC (transactional Remote Function Call) is still responsible for actually sending communications. tRFC is preceded by inbound and outbound queues, which have led to the name qRFC (queued Remote Function Call). The sending system is called the client system, and the target system represents the server system.
There are three data transfer scenarios:
Scenario 1: tRFC
This scenario is suitable if the data being sent is not interrelated. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, the data is transferred using tRFC. This means that each function module sent to the target system is guaranteed to be processed once. The order in which the function modules are executed, and the time they are executed, cannot be determined. If a transfer error occurs, a background job is scheduled that resends the function module after a defined period of time.
Scenario 2: qRFC with Outbound Queue
In this scenario, the sending system uses an outbound queue to serialize the data being sent. This means that mutually dependent function modules are placed in the outbound queue of the sending system and are guaranteed to be sent in the correct sequence, and only once, to the receiving system. The called system (server) has no knowledge of the outbound queue in the sending system (client). Using this scenario, every SAP system can communicate with a non-SAP system (the program code of the server system does not need to be changed, but it must be tRFC-compliant).
Scenario 3: qRFC with Inbound Queue (and Outbound Queue)
In this scenario, in addition to the outbound queue in the sending system (client), there is also an inbound queue in the target system (server). qRFC with an inbound queue always means that an outbound queue exists in the sending system. This guarantees that the sequence of communications is preserved, and at the same time the resources in the client and in the server system are controlled efficiently. The inbound queue is processed using an inbound scheduler, which only processes as many queues in parallel as the current resources in the target system (server) will allow, This prevents a server from being blocked by a client.
Features
Features of the Three Communication Types
To help you decide which communication types you need to implement according to your system landscape and your requirements, the advantages of the three types of communication are explained below:
· tRFC
Suitable only for independent function module calls; the sequence of the calls is not preserved
· qRFC with outbound queue
Function modules in a queue are guaranteed to be processed only once and in sequence (serialization). Also suitable for communication with non-SAP servers.
· qRFC with inbound queue
The function modules created in the outbound queue are transferred from the outbound queue to the inbound queue; the sequence of the function modules is preserved. An inbound scheduler processes the inbound queues in accordance with the specified resources. Both the client and the server system must be SAP systems. One work process is used for each inbound queue.
Queued Remote Function Call (qRFC)
Purpose
All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC). RFCs can be used to start applications in remote systems, and to execute particular functions.
Integration
In contrast the first version of RFC, synchronous RFC (sRFC), which required both participating systems to be active to form synchronous communication, subsequent generations of RFC now provide a considerably extended range of functions (for example, serialization, guarantee that processing occurs once, and the receiving system does not have to be available). These features were further enhanced through the queued RFC with inbound/outbound queue.
Contents:
The information about qRFC is organized into the following main sections, with more detailed subsections:
The qRFC Communication Model
· qRFC with Outbound Queues
· qRFC with Inbound Queues
qRFC Administration
· qRFC Administration: Introductory Example
· Outbound Queue Administration
· Inbound Queue Administration
qRFC Programming
· qRFC Programming: Introductory Example
· Outbound Queue Programming
· Inbound Queue Programming
· qRFC API
For an introduction to the new bgRFC (Background RFC), use the following links:
bgRFC (Background RFC)
· bgRFC Administration
· bgRFC Programming
Using Asynchronous Remote Function Calls
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
· When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
· Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
· The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functionu2019s result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
To start a remote function call asynchronously, use the following syntax:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION ...
EXPORTING...
TABLES ...
EXCEPTIONS...
The following calling parameters are available:
§ TABLES
passes references to internal tables. All table parameters of the function module must contain values.
§ EXPORTING
passes values of fields and field strings from the calling program to the function module. In the function module, the corresponding formal parameters are defined as import parameters.
§ EXCEPTIONS
See Using Predefined Exceptions for RFCs
RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
§ IMPORTING
§ TABLES
§ EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Transactional RFC (tRFC)
Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
· are executed in the order in which they are called
· are executed in the same program context in the target system
· run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.
Disadvantages of tRFC
· tRFC processes all LUWs independently of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
· In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later

Client copy between different operating systems.

Hi Experts,
Our production system is running on HP-UX OS. We are installing a standby quality system and planning to do a client copy to this system from production by taking this into transport domain. But this new system is in windows. So, is it possible to perform a client copy where the source system is HP -UX and target system is windows??
Regards,
Amit.

Hi Amit,
Follow SAP Note 552711 for client copy. Refer to qns no 4 & 5, which is relevant for your question.
Can I create client copies in a heterogeneous system landscape?
Remote copies or client transports can also be carried out between different database and operating systems.
Regards,
Debasis.

Difference between different attributes in Org Structres?

Dear Experts,
Could you please help me to understand the difference between system alias for vendor (Vendor_Sys) and Accounting system for vendor (Vendor_ACS)?
What is the relevance of each attribute in business scenario?
Thanks and regards,
Ranjan

Hi
VENDOR_SYS --> System in which POs can be created for this Vendor. In other words system where the Vendor has been created for the purchase organization.
VENDOR_ACS --> System where Accounting for Vendor has to be checked. IN other words, its the FI system which take care of Financial transactions related to the vendor
Regards
Virender Singh

Difference between different Technical systems

Similar Messages

Maybe you are looking for