Main differences between Forms and Selfservices

If anyone know plz list out the advantages and disadvantages of Form Services and Selfservice application vise versa

Have a look at the following thread:
self service and Forms
Re: self service and Forms

Similar Messages

What is the main difference between ws_upload and gui_upload?

Hi All,
What is the main difference between ws_upload and gui_upload?
In what contexts should we use these two function modules??
Thanks,
Creasy

search the forum before posting.
You can find lot of posts related.

What is the main difference between eewb and aet tool ?

Dear all,
What is the main difference between eewb and aet? Both ways we can create fields and coming to aet is in crm 7.0 and eewb is in 6.0.when we are creating fields through eewb we should have technical knowledge but aet tool is a simple tool as a function people also can easily add the fields. I want to know is there any main difference between both these tools.
Regards,
Jemmi.

EEWB works from SAP GUI whereas AET works from WEB UI. AET is developed on top of the EEWB. Most the Objects are supported barring a few through AET. It's a very usefull tool for SAP CRM.
Since in CRM SAP GUI will be phased out soon, AET will be prominent. One will see lot more features in upcoming relase in AET tool.
Regards,
Harshit

What is the main difference between Enhancements and BADI.?

What is the main difference between Enhancements and BADI.?plzz tell
Edited by: Alvaro Tejada Galindo on Feb 13, 2008 3:48 PM

CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.
Difference Between BADI and User Exits
BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
BADI's are oops based.
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

What is the main difference between menu_exits and user_exits

what is the main difference between menu_exits and user_exits

Hi,
User Exits:
A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Menu Exits:
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Regards,
Priyanka.

What is the main difference between view and materialize view and advantage of Mview ??

What is the main difference between view and materialize view and advantage of Mview ??

1.A view uses a query to pull data from its associated tables.
2.Views do not have data's physically stored in the Database.
3.Views Get the Data from 2 or more tables and displays as a single block.
4.But a materialized view is a table on disk is a result set of a query done.
5.A Materialized view can have data's in the database.
6.Materialized view are used for Boosting the Performance.
7.And the important one is Materialized views are updated based on the parameters defined when they are created.
8.By using triggers we can update the data in a materialized view.
9.When you call a materialized view it will show the data when it was last updated.
Hope it helps.

What is the main difference between BPEL and ESB

Hi all,
I am making use ESB in my application .Where the my client application calls ESB and inturn the ESB calls the BPEL process .
I want to know the differences between BPEL and ESB,I came to know that ESB can do messaging and routing ,where my BPEL process can also do the same thing .
I came to know form a vendor that ESB is used for connecting to multiple end points ,where as my BPEL process can also do this.
SO what is main purpose of using ESB ?
Cheers,
Kalyan.
Message was edited by:
patti

Hi,
Look for the blog entry dated 1st october 2007.
URL:
http://abhishek-soablog.blogspot.com
Cheers,
Abhi...

Difference between form and shop paper

Hi Guys,
I want to know the difference between Form, smart form and shop paper.
Our problem is one form is there, so user want to modify the form with some changes, they have provided the form name.
i have checked in the customization and able to find only shop paper related data.
Could you please suggest me how to find the forms.
Is there any customization available to link the forms with shop papers?
Thanks for reply.
Joshita

Hi,
A shop paper is a combination of print program and form.
Look at customizing transaction OIDA, Use this to adjust what form is used by a particular shop paper. Transaction SE71 can be used to adjust the form.
Do not adjust standard forms (PM_COMMON, etc), make a copy and adjust your own version.
-Paul

MAIN DIFFERENCES BETWEEN PARALLEL AND SEQUENTAIL PRCESSING???

HI PALS,
I WANT THE COMPLETE DIFFERENCES BETWEEN PARALLEL AND SEQUENTIAL PROCESSING!
IN THE CONTEXT OF RFC.

Hi
Parallel Processing
To achieve a balanced distribution of the system load, you can use destination additions to execute function modules in parallel tasks in any application server or in a predefined application server group of an SAP system.
Parallel-processing is implemented with a special variant of asynchonous RFC. Itu2019s important that you use only the correct variant for your own parallel processing applications: the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword. Using other variants of asynchronous RFC circumvents the built-in safeguards in the correct keyword, and can bring your system to its knees
Details are discussed in the following subsections:
·        Prerequisites for Parallel Processing
·        Function Modules and ABAP Keywords for Parallel Processing
·        Managing Resources in Parallel Processing
Prerequisites for Parallel Processing
Before you implement parallel processing, make sure that your application and your SAP system meet these requirements:
·        Logically-independent units of work:
The data processing task that is to be carried out in parallel must be logically independent of other instances of the task. That is, the task can be carried out without reference to other records from the same data set that are also being processed in parallel, and the task is not dependent upon the results of others of the parallel operations. For example, parallel processing is not suitable for data that must be sequentially processed or in which the processing of one data item is dependent upon the processing of another item of the data.
By definition, there is no guarantee that data will be processed in a particular order in parallel processing or that a particular result will be available at a given point in processing.
·        ABAP requirements:
¡        The function module that you call must be marked as externally callable. This attribute is specified in the Remote function call supported field in the function module definition (transaction SE37).
¡        The called function module may not include a function call to the destination u201CBACK.u201D
¡        The calling program should not change to a new internal session after making an asynchronous RFC call. That is, you should not use SUBMIT or CALL TRANSACTION in such a report after using CALL FUNCTION STARTING NEW TASK.
¡        You cannot use the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword to start external programs.
·        System resources:
In order to process tasks from parallel jobs, a server in your SAP system must have at least 3 dialog work processes. It must also meet the workload criteria of the parallel processing system: Dispatcher queue less than 10% full, at least one dialog work process free for processing tasks from the parallel job.
Function Modules and ABAP Keywords for Parallel Processing
You can implement parallel processing in your applications by using the following function modules and ABAP keywords:
·        SPBT_INITIALIZE: Optional function module.
Use to determine the availability of resources for parallel processing.
You can do the following:
¡        check that the parallel processing group that you have specified is correct.
¡        find out how many work processes are available so that you can more efficiently size the packets of data that are to be processed in your data.
·        CALL FUNCTION Remotefunction STARTING NEW TASK Taskname DESTINATION IN GROUP:
With this ABAP statement, you are telling the SAP system to process function module calls in parallel. Typically, youu2019ll place this keyword in a loop in which you divide up the data that is to be processed into work packets. You can pass the data that is to be processed in the form of an internal table (EXPORT, TABLE arguments). The keyword implements parallel processing by dispatching asynchronous RFC calls to the servers that are available in the RFC server group specified for the processing.
Note that your RFC calls with CALL FUNCTION are processed in work processes of type DIALOG. The DIALOG limit on processing of one dialog step (by default 300 seconds, system profile parameter rdisp/max_wprun_time) applies to these RFC calls. Keep this limit in mind when you divide up data for parallel processing calls.
·        SPBT_GET_PP_DESTINATION: Optional function module.
Call immediately after the CALL FUNCTION keyword to get the name of the server on which the parallel processing task will be run.
·        SPBT_DO_NOT_USE_SERVER: Optional function module.
Excludes a particular server from further use for processing parallel processing tasks. Use in conjunction with SPBT_GET_PP_DESTINATION if you determine that a particular server is not available for parallel processing (for example, COMMUNICATION FAILURE exception if a server becomes unavailable).
·        WAIT: ABAP keyword
WAIT UNTIL
Required if you wish to wait for all of the asynchronous parallel tasks created with CALL FUNCTION to return. This is normally a requirement for orderly background processing. May be used only if the CALL FUNCTION includes the PERFORMING ON RETURN addition.
·        RECEIVE: ABAP keyword
RECEIVE RESULTS FROM FUNCTION Remotefunction
Required if you wish to receive the results of the processing of an asynchronous RFC. RECEIVE retrieves IMPORT and TABLE parameters as well as messages and return codes.
Managing Resources in Parallel Processing
You use the following destination additions to perform parallel execution of function modules (asynchronous calls) in the SAP system:
In a predefined group of application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP Groupname
In all currently available and active application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP DEFAULT
Sequential Processing
In the following cases, the system chooses sequential (non-parallel) processing:
●      In table RSADMIN, entry QUERY_MAX_WP_DIAG has value (column value) 1.
●      The entire query consists of one sub-access only.
●      The query is running in a batch process.
●      The query was started from the query monitor (transaction RSRT) using various debug options (for example, SQL query display, execution plan display). See, Dividing a MultiProvider Query into Sub-Queries.
●      The query requests non-cumulative key figures.
●      Insufficient dialog processes are available when the query is executed. These are required for parallel processing.
●      The query is configured for non-parallel processing.
●      You want to save the result of the query in a file or a table.
In Release SAP NetWeaver 7.0, the system can efficiently manage the large intermediate results produced by parallel processing. In previous releases, the system terminated when it reached a particular intermediate result size and proceeded to read data sequentially. This is no longer the case. Therefore, the RSADMIN parameter that was used in previous releases for reading a MultiProvider sequentially is no longer used.
Reward If Helpfull,
Naresh

Difference between Forms and forms in OC4J_BI_FORMS

Hi
When I logged in OAS in console. I see a row for Forms and one for reports Server.
In oc4j_BI_Forms also I see forms and reports.
What is the difference between these two forms or reports processes.Whihc one is used when we deploy forms and reports in OAS.
Thanks in Advance.

OC4J_BI_Forms holds a part of the Forms and Reports Application, but the engines run in the Forms and Reports as a different product or application, if you make any modification in OC4J_BI_Forms container it wont affect the forms and reports engines, it's necesary, but the hole work is made by the individual products, and all are necesary.
Hope this helps.
Greetings.

Whats the main difference between wifi and wifi Cellular for iPad mini?

Can someone explain to me in simple terms the main difference/benefit of buying a wifi or a wifi + cellular iPad? I thought the cellular meant you would have a sim card in it and you can then connect to the internet when you are not near a wifi, but now looking at the specs again it mentions a sim card for the wifi one, so what are you getting extra for the cellular technology?

Aloha Karl. You're welcome. I'm still new to all this technology myself. I only had my iPad for a year and a half. Up until a few years ago I had no plans to to ever have anything to do with computers. Fortunately a few friends showed me what was available on the internet and another friend suggested I should give the iPad a look at. The rest is history. At 63 I'm still like a kid with a new toy, trying to learn, trying to help. Bob.

Main Difference Between EDI and IDOC Based On RFC

In IDOC ,RFC is Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
What About EDI ?

Hi Saurabh,
Check this..Hope it helps you.
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
IDOC:
IDOC is a container that can be used to exchange data between any two process.
Each iDoc is assigned a unique number for tracking and future reference.
iDoc Consist of several segments,and segments contain several fields.
iDoc contains the following three type of records...
1.One Control Record.
2.One or many Data Record
3.One or many Status record.
PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.
RFC Destination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
Partner Profile:
Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.
Message Control
Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.
Process:
Setup RFC destinations SM59
Port Destinations WE21
Partner Profile WE20
Message control NACE
Purchase Order ME21
Check IDOCs WE02,WE05
Explain to me about Idoc?
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.
Re,Manas

What's the main difference between XLR and 1/4" inputs.

Of course I know that they look different and that they are bother forms of audio inputs an outputs, but I was wondering if there was a difference in quality as well.

ahicox wrote:
LOL ... uuh, no they don't.
Of anything XLR has less contact surface area than 1/4 inch (though truthfully when you boil it all down it's probably more or less the same).
LOL, no you're wrong. The three pins and sockets of an XLR plug and jack both have large surface contact areas. The 1/4" barrel (ground) does have substantially more surface area but that's solely for a ground connection.
The surface electrical-contact-area of the tip and ring of a 1/4" plug and jack are very small when compared to the high and low sides an XLR connection. The XLR provides a much more stable electro-mechanical connection.

Main difference between these 2 methods

HI
what is the main difference between updateOrder and repriceOrder methods in any form handler
please give me exact difference

Both are totally different operations. repriceOrder method invokes the pricing engines and calculators to calculate the order prices whereas, updateOrder method saves the changed order properties to the database.
Thanks,
Tejas

Difference between Smartforms and Sapscrits.

Hi Experts,
I have a interview coming up next week and I was just wondering: difference between Smartforms and SAPscripts..
So experts, can anyone please let me know what are the main differences between Smartforms and SAPScripts??
I will really appreciate your answers.. guys..
Regards,
-Ashok Patel.

Hi,
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated.
f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.
In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
Check the link,
http://www.sap-img.com/smartforms/sap-smart-forms.htm
Conversion of SAPSCRIPT to SMARTFORMS
SAP provides a conversion for SAPscript documents to SMARTforms.
This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
You can also do this one-by-one in transaction SMARTFORMS, under
Utilities -> Migrate SAPscript form.
You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
Hope it helps u.
Thanks&Regards,
Ruthra.R

Main differences between Forms and Selfservices

Similar Messages

Maybe you are looking for