Page Comparison

USE:

int4 Int4 IFTT is integrated with SAP eCATT - a standard tool for recording and replication of manual actions. The eCATT integration is used to allow replicating manual steps in the interface process chains.
The configuration object for eCATT recordings is necessary to bind results and pass them properly correctly to the next step (next test case) of the tested process chain. Additionally, it is used to define the way how eCATT input parameters will be populated.

Please notice that in the configuration object for SAP eCATT, you don't specify the the eCATT script or  or eCATT test configuration name itself itself. The name of the eCATT script is entered is entered during the the test case creation.  This This approach allows to use using the single definition for multiple eCATT scripts referring to the same business document type i.e.outbound delivery, purchase order, etc. 

PREREQUISITES:

See Prerequisites for executing eCATT scripts

PROCEDURE:

1. Create a new object definition

2. Enter object definition name and description. Leave Name and Namespace fields empty as such objects are not associated with the middleware interface.

   
   

   
   Enter the Backend system line for the current doc. and Backend system line for reference doc. By this parameter, the scrips will be called on specific backends based on the execution environment. 
   Please note that the the RFC destination available  available in the the Assign system lines to environment the environment in the landscape configuration must be the same as as the Target system in  in the System data container in the eCATT test script or test configuration. 
   
   Moreover, in Additional Parameters, please set up the the ECATT_RMT parameter. As explained, if the parameter is set as X, then the eCATT script or test configuration will be executed from a remote location. By default, Int4 IFTT assumes that the scrips are local. 
3. In the Object Variables section enter , enter the variables' names and their descriptions.
   
   
   
   
4. Select each variable and proceed to the Variable Processing. Here you can define multiple actions for each of the variables declared.
   
   EXAMPLE: 
   
   In a sample eCATT case where the recording is used for triggering an output for a sales order, we need two variables:
   
   
   • VAR_PO - for purchase order number
   • SO_NUMBER - for sales order number

     Anchor
     INPPAR INPPAR

     
     
     
     

     In VAR_PO variable processing, we set the action

     as:

     as a populate variable before execution.

     Variable processor

     The variable processor is

     being

     set as

     USER

      USER_DEF, which means the variable will be populated

     
     

     with a user-defined value from the cockpit. 

     If the Processing Parameter

     will contain number

     contains numbers from 1 to 4

     then

     , it might be edited directly from the cockpit - entry test case details

     entry

     .

      

     
     

     Anchor
     OUTPAR OUTPAR

     
     
     In SO_NUMBER variable processing we processing, we set the action as: as a populate variable after execution.   Variable processor is  is being set as ECATT_LOG LOG, which means that the value will be read
     from eCATT log, from the node indicated by Xpath declared as the processing parameter. More about it you will find here: Passing values from eCATT recording results.

...