TARIF - difference between Feature and Indirect Evaluation Module

Greetings,
What is the difference between feature Tarif that is used to default payscale area /ps type and Indirect eval module used for wagetypes ?
How is this used, applied ?
Thanks
AP

Ms Datar,
Well described, Thanks. Understood that Valuation module for wage type has nothing to do with Feature Tarif.
However, I also found Indirect Valuation Module called TARIF with variants -A,B,C, D.
TARIF
Valuation according to the "collective agreement group and level" specifications you enter in the IMG step:
Module variant 'A'
Country grouping derived from the employee's personnel area
Pay scale type from infotype 0008/0052
Pay scale area from infotype 0008/0052
Pay scale indicator derived from the employee subgroup
Pay scale group from infotype 0008/0052
Pay scale level from infotype 0008/0052
Wage type = SPACE
Therefore, now i understand as : Feature Tarif defaults Payscale values in IT8 .
and Ind Val Module Tarif ( A) reads the payscale values in IT8 and leaves the wagetype blank with no amount ?
Is this correct ?

Similar Messages

Differences between R12 and 11i by module wise.

Hi All,
Could any one please give me the knowledge stack on "differences between R12 and 11i by module wise".
Thanks,
RED.

Please refer to:
Note: 404152.1 - E-Business Suite Release 12: Release Content Documents
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=404152.1
Oracle Applications Concepts
http://download.oracle.com/docs/cd/B40089_09/current/acrobat/120oacg.pdf
Note: 433111.1 - Release 12 File System Changes : R12 Vs 11i
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=433111.1
Edited by: hsawwan on Feb 6, 2009 7:12 PM -- Added couple of helpful links/notes

Difference between poh and pov in module pool programming

hi all,
                   pls tell me difference between poh and pov and how i check validation in screen

Hi,
POV gives you F4 help.
like:
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD f MODULE mod.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field f, the system calls the module mod belonging to the FIELD statement. If there is more than one FIELD statement for the same field f, only the first is executed. The module mod is defined in the ABAP program like a normal PAI module. However, the contents of the screen field f are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These alll have the prefix F4IF_. The most important are:
·        F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
·        F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The self-programmed value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT demo_dynpro_f4_help_module.
TYPES: BEGIN OF values,
         carrid TYPE spfli-carrid,
         connid TYPE spfli-connid,
       END OF values.
DATA: carrier(3) TYPE c,
      connection(4) TYPE c.
DATA: progname TYPE sy-repid,
      dynnum   TYPE sy-dynnr,
      dynpro_values TYPE TABLE OF dynpread,
      field_value LIKE LINE OF dynpro_values,
      values_tab TYPE TABLE OF values.
CALL SCREEN 100.
MODULE init OUTPUT.
progname = sy-repid.
dynnum   = sy-dynnr.
CLEAR: field_value, dynpro_values.
field_value-fieldname = 'CARRIER'.
APPEND field_value TO dynpro_values.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE value_carrier INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
       EXPORTING
            tabname     = 'DEMOF4HELP'
            fieldname   = 'CARRIER1'
            dynpprog    = progname
            dynpnr      = dynnum
            dynprofield = 'CARRIER'.
ENDMODULE.
MODULE value_connection INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
       EXPORTING
            dyname             = progname
            dynumb             = dynnum
            translate_to_upper = 'X'
       TABLES
            dynpfields         = dynpro_values.
READ TABLE dynpro_values INDEX 1 INTO field_value.
SELECT carrid connid
    FROM spfli
    INTO CORRESPONDING FIELDS OF TABLE values_tab
    WHERE carrid = field_value-fieldvalue.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
            retfield    = 'CONNID'
            dynpprog    = progname
            dynpnr      = dynnum
            dynprofield = 'CONNECTION'
            value_org   = 'S'
       TABLES
            value_tab   = values_tab.
ENDMODULE.
*POH gives you F1 documentation:*
like:
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
       VAR(4),
       INT TYPE I,
       LINKS TYPE TABLE OF TLINE,
       FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
    WHEN 1.
    VAR = '0100'.
    WHEN 2.
    VAR = '0200'.
    INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
       EXPORTING
            DOKLANGU                      = SY-LANGU
            DOKTITLE                      = TEXT-002
            CALLED_FOR_TAB                = 'DEMOF1HELP'
            CALLED_FOR_FIELD              = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
       EXPORTING
            DOKCLASS                      = 'TX'
            DOKLANGU                      = SY-LANGU
            DOKNAME                       = 'DEMO_FOR_F1_HELP'
            DOKTITLE                      = TEXT-003
       TABLES
            LINKS                         = LINKS.
ENDMODULE.
Regards,
Renjith Michael

What is the difference between LH and LX modules?

I would like to know the difference between LX and LH SFP modules. Long Haul ( LH ) denotes longer distances while Long Wavelength ( LX ) denotes less energy which is obviously shorter distance. Why does Cisco use both LX and LH for certain SFP modules?
Do they denote the capability of the module to work both for MM ( which will be Long wavelength ) and SM ( Long Haul ) fiber? Do correct me if i am wrong.
What does it infer if a modules says like "Cisco 1000BASE-LX/LH SFP" ?

What does it infer if a modules says like "Cisco 1000BASE-LX/LH SFP
Generally a module is either made for single mode (More distance) / multimode (short distance). But this module can be used for both Single mode and Multimode.
If used with SM fiber it can go upto 10Km
It used with MM it can go upto 550meters (depend on what kind os MM fiber you have) You need a mode conditioning patch chord too with legacy MM i think OM1 and 2.
Long Haul ( LH ) denotes longer distances while Long Wavelength ( LX ) denotes less energy which is obviously shorter distance. Why does Cisco use both LX and LH for certain SFP modules
Read this link and dont worry about LX/LH (You will ge tthe distance mentiond above depending on the type of fibe ryou are using)
http://en.wikipedia.org/wiki/Gigabit_Ethernet
Before it was standardized 1000BASE-LX10 was essentially already in widespread use by many vendors as a proprietary extension called either 1000BASE-LX/LH or 1000BASE-LH

Difference between ME_READ_PO_FOR_PRINTING and ME_PRINT_PO

I just saw these 2 function modules in standard PO printing program SAPFM06P. Can someone please let me know whatz the difference between ME_READ_PO_FOR_PRINTING and ME_PRINT_PO function modules...

Hi friend......
The function module ME_READ_PO_FOR_PRINTING is used to read the PO
The function module ME_PRINT_PO is used to print the PO
if u want let u know some more information
How can i get PO partner functions using FM ME_READ_PO_FOR_PRINTING
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/tcode-me9f-user-exit-exit_saplmedruck_001-617362

Difference between RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_ITEM_BUFFER FMs

Hi Experts,
I want to know the difference between RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_ITEM_BUFFER function modules.
Both FMs are meant to fetch all pricing condtions for document.
Thanks in advance,
Sagar

In the calculation schema you can customize your conditions. E.G: if they shall be printed or not.
So the FM gets you back two tables of conditions.
TKOMV (ALL of em)
TKOMVD (Just the ones that are marked as to be printed)
Those ones from TKOMVD are the ones you need for invoice printing.
But for calculation issues or whatever you may need to have a look at some conditions which are not marked as to be printed and so you get TKOMV back to be able to do so.

What is the difference between subroutine and function module?

What is the difference between subroutine and function module?

Hi,
they can both return values.
FMs are mainly used when a routine is to be performed by many programs.
Subroutines (forms) are generally only executed within one program.
You can perform routines from other programs, but it's not often done.
both forms and FMs are reusable modularization units.
To distinguish we generally say that forms are used for internal modularization and
FMs are used for external modularization.
To decide on which to implement, consider whether you need the content to be used just for a limited program
or wheteher it can be called from many independent programs.
For the first purpose it is better to implement a form whereas for the second we implement an FM.
However, ABAP does not isolate the usage context.
That is; you can call a form from another program within whose code the form is not actually implemented.
However, this requires attention since the form may utilize global variables.
The same issue holds for FMs.
FMs are encapsulated in function groups and function groups may have global variables that can be globally
used by all FMs inside it.
Thanks,
Reward If Helpful.

Could any one tell me what is the difference between swfloader and module loader?

Hi All,
                      Could any one tell me what is the difference between SWFLoader and Module Loader in Flex3 in detail?

Hi,
ModuleLoader is a kind of strange API that is really just intended to look like SwfLoader for modules that contain a single visual component, and hides most of the module loading infrastructure, which is all about class factories.
What I mean by "only loaded once" is that if you have several places in the code that call the ModuleManager.getModule("url").load() call, it will only ever get loaded over the wire and interpreted once, subsequent "loads" will just re-dispatch pseudo-load events to the new client. In other words, the class factory is a singleton for a given url. Unloading is a totally different story. As you note, not everything is truly unloadable, because there may be lots of references to stuff in
the module that will keep it alive and un-GC'ed.
I suggest playing with the low-level API so that you understand the backing implementation, and this should help you understand the limits of ModuleLoader.
The main difference between modules and applications is that modules have lower overhead, and they only ever get loaded once, no matter how many times you load them. If you're using the ModuleLoader API, keep in mind that you're losing about half the functionality of the module system. I will assume that you are, because otherwise it would be obvious where to expose methods. You might want to play around with the lower level ModuleManager API just to get a hang of what's going on - ModuleLoader is a pretty thin veneer over the lower API.
                Basically, what you want to do is to have your module implement an interface, say IModuleWhatever.
Also try and refer to this link which was previously discussed in this forum..
http://forums.adobe.com/message/74404
Thanks,
Bhasker

Differences between R12 and 11.5.9 in Oracle Learning Management Module

Hi,
I am into One Upgrade Project.
I would like to know what are the differences between R12 and 11.5.9 in Oracle Learning Management and need to know any new Tables, Views, Forms and Reports got upgraded?.
Thanks & Regards,
Srinivasulu Vakati

Hi Anders,
Could you please explain me what is this SWAN Interface ?
Kind Regards,
Naga Suresh. Challapalli (Naga)

US PY - Indirect Evaluation Module

Hi Expert,
Could you explain me about Indirect Evaluation Module in WT.
There are some features assigned to it and also some variant.
Can you help me to understand the core concept and use of Feature and Variant and why and how are they used?
Thank you in advance.
Regards,
Sejal

Hi Sejal,
Indirect evaluation module:
Name of a module that valuates wage types according to certain criteria. The following descriptions of the diverse options can be used for wage types in the following infotypes:
Basic Pay (0008)
Standard Wage Maintenance (0052)
Recurring Payments/Deductions (0014)
Additional Payments (0015)
For some modules, the type of valuation depends on the specification of the module variant.
The following indirect valuation modules are available in the standard system:
TARIF
PRZNT
SUMME
UNITS
CONST
ARBPL
ANSAL
CHSTD
EXPAT (only for Management of Global Employees)
Define valuation of base wage types
You may have already defined indirect valuation for certain wage types in the step " Check wage type characteristics".
Depending on which module you use for indirect valuation (see documentation on the Module name field), you need to define additional procedures to ensure that indirect valuation functions correctly.
Example
In the Basic Pay infotype (0008), an employee has the wage types 'standard pay' and 'standard bonus'. You also want to assign to your employee the wage type 'percentage bonus' which should be x% of the sum of the first two wage types.
You have defined the module PRZNT for the 'percentage bonus' wage type.
In this step, you must define the wage types to be used as the basis for calculating the percentage bonus.
Requirements
The wage type catalog and wage type characteristics must be defined.
Standard settings
The standard system contains some models for valuating basic
wage types.
Recommendation
Read the documentation on the Module name and
Module variant fields in the section entitled "Check wage type characteristics".
Activities
1. Delete any entries that you do not need.
2. Create new entries based on your requirements and the definitions in the step "Check wage type characteristics"
a) Name the module that you want to use.
b) Enter the wage type you defined in the 'Check wage type characteristics' step.
c) Number the wage types which are to be used as the basis for indirect valuation.
d) Define the validity period.
e) Define base wage type(s) for indirect valuation.
f) Specify the percentage rate for weighting the base wage type.
I hope it helps you!!!!!!!!
Thanks
Cheera

Difference between validation and susbstittution with tcodes

hi all can any body tell me about difference between validation and susbstittution with tcodes
regars
sravya

Hi,
Settting up the FI Validations
You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.
For e.g. to allow postings from company code 0001 to business area AA only.
GGB0 - To maintain the validations
Validation - Enter a validation name e.g. VBUS
Applicaion Area - SAP module e.g. FI
Calling Point - Dependent upon the application area that is selected.
0001 - Document Header - validate enteries at document header, e.g BKPF table
0002 - Line Items - check line item entris within a document, e.g. BSEG table
0003 - Complete Document - check settings for the whole documents.
e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.
Prerequisite
<BSEG> $BUKRS = '0001' AND
<BKPF> $GLVOR = 'FI00'
Check
<BSEG> $GSBER = 'AA'
Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4
OB28 - Define Validations for Posting
CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1
Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input
GGB4 - Manage the activation of all validations in the SAP system.
Validations, Substitutions, and Rules
Purpose
With the validations and substitutions software, you can validate and/or substitute data at the time of entry in the FI-SL System and other SAP Systems.
Implementation Considerations
You do not need to change the standard system to customize your validations and substitutions. For each installation, you can define exactly which validations and substitutions are necessary to ensure the integrity of your data.
Features
Validation
In the SAP System, almost all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use FI-SL's validations program to create validations for your system.
With validations, you can check values and combinations of values as they are being entered in the SAP environment. Validation rules are stored in the Rule Manager; as data is entered, the Integration Manager validates the data against the validation rules stored in the Rule Manager. Because data is validated before it is posted, only valid information enters the FI-SL System.
You define validation rules using Boolean logic. When you define a validation rule, the system checks the validation rule to ensure that it is syntactically correct.
You can also define the result of breaking the validation rule. For instance, you can specify that a message is issued but the user can continue processing. You can also force the user to correct the error before processing can continue.
For more information, see Validation or What Are Validations?. For more information on using validations, see Creating a Validation. For more information on Boolean Logic, see Introduction to Boolean Logic.
Substitution
Substitution rules are stored in the Rule Manager. When data is entered in the system, it is substituted by the Integration Manager. The Integration Manager calls the Rule Manager. Substitution occurs before the data is posted to the FI-SL databases.
You define substitution rules using Boolean logic. When you define a substitution rule, the system checks the substitution rule to ensure that it is syntactically correct.
For more information, see Substitution or What Are Substitutions?. For more information on using substitutions, see Creating a Substitution. For more information on Boolean Logic, see Introduction to Boolean Logic.
Rules
A rule is a Boolean expression that you can use as a condition, as a check, or in another rule. Rules enable you to refer to frequently used Boolean statements simply by specifying the rule name.
The FI-SL Integration Manager uses Boolean logic. When you use Boolean logic and syntax, you can:
Validate data
Substitute data
Select ledgers for posting
Transfer substitution data to a rollup ledger
Select report data
The Rule Manager stores the Boolean rules used to analyze data. The Integration Manager calls the Rule Manager and determines whether entered data should be used. If a Boolean statement is true, an action is taken; if a statement is false, no action is taken.
Boolean logic is used in the following FI-SL modules:
Validation
Substitution
Ledger selection
Report Writer
Rollups
To use Boolean Logic in one of the functions listed, you create statements that are used as formulas in the FI-SL System. For more information on using Boolean Logic, see Introduction to Boolean Logic or Boolean Logic Statements and Rules.

Difference between sapscripts and BDCs

what is the difference between sapscripts and BDCs

BDC for data communication between sap to non sap(vice-versa)
where scripts is a business layout(we create)
<b>bdc help</b>
They are the only 3 methods mostly we use in BDC.
Call _Dialog is outdated. it is there in the intial stages of SAP.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
These are the Function modules used for the Session Method.
BDC_OPEN_GROUP
BDC_INSERT
BDC_CLOSE_GROUP
BDC_DELETE_SESSION to create a session
You can schedule the execution of BDC session using the program RSBDCSUB.
another one call transaction
open dataset
close dataset
reward if it helps u
vijay pawar

Can anybody give me the difference between Catt and Ecatt

Hi gurus,
Can any body give me the difference between catt and ecatt.

Hi,
I think this is new technology in sap.
I know little bit of this can u go through this.
eCATT (extended Computer Aided Test Tool)
What is eCATT?
eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
Features of eCATT:
Following functions can be performed using eCATT:
Test transactions, reports and scenarios.
Call BAPIs and function modules.
Test remote systems.
Check authorizations (user profiles).
Test updates (database, applications, GUI).
Set up customizing tables.
Test the effect of changes to customizing settings.
Perform load testing.
Check system messages.
Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
Supports CATT migration to eCATT.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
There can be several versions of Test Scripts, which allows different implementations with different releases.
The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
Why eCATT?
CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
Due to automation, testing time is reduced to a large extent.
Due to automation, less manpower is required for testing. This helps financially.
Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
Proved to be extremely useful in implementation projects.
In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
Differences between CATT and eCATT?
Till date, CATT could only be used with the R/3 system. eCATT (which is available with SAP Web Application Server 6.20) covers the automatic testing in SAPGUI for Windows and SAP GUI for Java. For other GUIs and Applications, eCATT provides an interface for external tools. This allows companies to perform automated tests from an SAP system in a complete IT solution landscape across system boundaries. These new options enable complete automation of solution landscapes under standard Windows and Web-based user interfaces- resulting in low-cost operation of an IT Solution.
eCATT (extended Computer Aided Test Tool)
eCATT requisites
Web Application Server (WAS) 6.20 or more.
SAPGUI 6.20 or more.
R/3 4.6C or more. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.7).
Before creating Test Scripts using eCATT, some system settings need to be done:
Maintain table T000.
1.      Go to transaction SM31
2.      Enter T000 and chose MAINTAIN.
3.      In the Change View Clients: Overview screen, select the relevant client and choose Details
4.      In the CATT and eCATT Restrictions field, select CATT and eCATT allowed.
5.      Click on SAVE.
Enabling scripting at the Front-end
1.      On any SAP GUI screen, choose Customizing of Local Layout.
2.      Choose Options
3.      Choose Scripting Tab
4.      Select Enable Scripting
5.      Click Apply and then OK.
Enabling Scripting on the Application Server
1.      Go to transaction RZ11.
2.      On the Maintain Profile Parameters screen, enter sapgui/user_scripting.
3.       Choose Display.
4.      If the Current Value is not set to TRUE, then click on Change Value:
5.      Enter TRUE in the New Value.
6.      Click on SAVE.
eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
Features of eCATT:
Following functions can be performed using eCATT:
Test transactions, reports and scenarios.
Call BAPIs and function modules.
Test remote systems.
Check authorizations (user profiles).
Test updates (database, applications, GUI).
Set up customizing tables.
Test the effect of changes to customizing settings.
Perform load testing.
Check system messages.
Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
Supports CATT migration to eCATT.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
There can be several versions of Test Scripts, which allows different implementations with different releases.
The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
Why eCATT?
CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
Due to automation, testing time is reduced to a large extent.
Due to automation, less manpower is required for testing. This helps financially.
Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
Proved to be extremely useful in implementation projects.
In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
Reward points if it is helpful.
Rgds,
P.Nag

Difference between IntegrationServer and Integration Engine

Hi,
Could you please provide me difference between IntegrationServer and Integration Engine.
functionality of both and what are the runtime environments exits in XI Server.
Could you please show me digaram how message flow from
XI server i.e., through which engines.. what is the input and output of each engine.
Thanks,
RamuV

Hello Ramu,
Go through this link..
http://help.sap.com/saphelp_nw04/helpdata/en/e1/0c733cb7d61952e10000000a11405a/frameset.htm
Use
Two SAP XI 3.0 Integration Servers are used to exchange messages between the system landscapes of two business partners.
Description
An SAP XI Integration Server of a business partner is connected to the SAP XI Integration Server of another business partner. Both use SAP XI message protocol to send or receive messages.
When an SAP XI Integration Server receives a message from another Integration Server it understands the message format and so processes the message.
Example
A business partner that uses SAP XI wants to send a message to another business partner who also uses SAP XI .
·        The message is sent between the Integration Servers in SAP XI message format
·        The Integration Server of the second business partner then sends the message to the relevant business system
Integration Engine
Purpose
The Integration Engine enables you to process XML messages exchanged between applications in heterogeneous system landscapes. Both applications of SAP components and external applications can communicate with the Integration Engine.
Using adapters, the Integration Engine can also process IDocs (Intermediate Documents) and RFCs (Remote Function Calls). This option is available for applications that have already defined IDocs or RFCs, as well as for applications of SAP components that do not yet have access to the proxy generation functions.
Integration
The Integration Engine is the runtime environment of the SAP Exchange Infrastructure. The following are examples of other important parts of this infrastructure:
·        Proxy Generation
·        Integration Repository
·        Integration Directory
The integration processes involved can take place between heterogeneous system components within a company, as well as between business partners outside company boundaries.
Features
The Integration Engine, as a runtime component of SAP Exchange Infrastructure, has the task of receiving, processing, and forwarding XML messages. During message processing, collaboration agreements are evaluated, the receivers are determined, and mapping activities are executed.
The individual processing steps are called pipeline services and are defined in pipelines. It is the task of the Integration Engine to process these pipelines correctly and consistently. To guarantee this, you must configure the Integration Engine accordingly and monitor the message processing. Both event-driven message processing and prioritized message processing are possible.
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Apr 22, 2008 3:34 PM

Difference between GUI_UPLOAD and WS_UPLOAD

Hi,
Please make me clear about the difference between GUI_UPLOAD and WS_UPLOAD. In which cases we need to use these modules...??
Thanks,
Satish

I would suggest to always use the GUI_UPLOAD. I say this because this is the function module which is used in the GUI_UPLOAD method of the class CL_GUI_FRONTEND_SERVICES.   Really, you should probably use the class/method instead of the function module.
data: filename type string.
filename = p_file.
call method cl_gui_frontend_services=>gui_upload
         exporting
              filename                = filename
              filetype                = 'ASC'
         changing
              data_tab                = iflatf
         exceptions
              file_open_error         = 1
              file_read_error         = 2
              no_batch                = 3
              gui_refuse_filetransfer = 4
              no_authority            = 6
              unknown_error           = 7
              bad_data_format         = 8
              unknown_dp_error        = 12
              access_denied           = 13
              others                  = 17.
Regards,
Rich Heilman

TARIF - difference between Feature and Indirect Evaluation Module

Similar Messages

Maybe you are looking for