Page Comparison

USE: 

The Object Definition contains paramaters such as parameters, e.g., the name of the tested service interface and it's its namespace, allowing IFTT to locate the XML message on the middleware platform
in order to store it inside of the IFTT repository for further comparison. Below it is presented how to create a new object definition for for PI inbound interface, PI outbound interface, synchronous interface, IDOC inbound/outbound interfaces, and AIF  AIF interfacesIn

In the General Settings section  section, you will find how to use already existing objects object configuration for a newly created object , or how to configure IFTT in order to test data on remote ERP systems. 

PI INBOUND / OUTBOUND / SYNCHRONOUS INTERFACE: 

Anchor
PIINBIF PIINBIF

1. Enter object definition ID and description. 
2. Enter PI/PO service interface name and namespace. 
   
   
   
   You can copy them from the ICO of the configured interface: 
   
   
   
3.  Define an unlimited number of variables and add a meaningful description for each of them.
   
   
   
   
4. For each of the variables, define actions and define the processing that will be performed. For each action, select one of the variable processors and provide the processing parameter: This way, variables can be used ie.eg.
   
   
   • to identify documents to be compared,
   • for creating new values from a number range for a newly created messages,
   • for passing values to variables in next the following test cases. 
     
     

IDOC INBOUND / OUTBOUND INTERFACE: 

Anchor
IDOCINBIF IDOCINBIF

1. Enter object definition ID and description. 
2. Provide IDOC interface details in the Name field.
   Name The name of the IDOC interface is a combination of IDOC message type, basic type, and an extension separated by a dot ( ".").
   1. In order to provide the correct information open relevant segments of the IDOC:
      
      
      • for message type: /IDOC/EDI_DC40/MESTYP
      • for basic type:       /IDOC/EDI_DC40/IDOCTYP
      • for extension:        /IDOC/EDI_DC40/IDOCTYP
        
        
        
        
   2. The name of the interface is the combination of full Namespace, and  and six first letters of Interface Name separated by a dot: ' ( ". ' ).
      
      Example: 
      For the IDOC with Basic Type ORDERS05, message type: ORDERS and no extension, the interface name will be ORDERS.ORDERS05
      
      
      
      
      
3.  Define an unlimited number of variables and add a meaningful description for each of them.
   
   
4.  For For each of the variables, define actions and define the processing that will be performed. For each action, select one of the variable processors and provide the processing parameter: This way, variables can be used ie.g.e.
   
   
   • to identify documents to be compared,
   • for creating new values from a number range for a newly created messages,
   • for passing values to variables in next the following test cases. 
   
   
   

AIF INTERFACE

Anchor
AIFIF AIFIF

USE: 

The Object Definition contains parameters, such as the generated name of the tested AIF interface allowing IFTT to locate the XML message in the AIF persistance persistence on ECC. Thanks to this, it is possible to store AIF XML message messages inside of the IFTT repository for further comparison. 

• Enter object definition ID and description. 
• Provide AIF interface details in in the Name field.
  Name
  The name of AIF the interface is a combination of an AIF Namespace and the first six letters of an AIF interface.
  
  
  1. In order to To provide correct information, go to transaction /n/AIF/CUST
  2. Open branch: SAP AIF → Interface Development → Define Interface
  3. Open specific namespace and then open interface you want to test in IFTT
     
     
     
     
  4. The name of the interface is the combination of full Namespace, and  and six first letters of Interface Name separated  separated by a dot (".").
     Example: For NOWAKM namespace and SORD_CR interface name - the name of the interface should be NOWAKM.SORD_C  
     
     
     
  5. Define an unlimited number of variables and add a meaningful description for each of them.
     
     
     
      
     
     For each of the variables, define actions and define the processing that will be performed. For each action, select one of the variable processors and provide the processing parameter: This way, variables can be used ie.eg.
     
     
     • to identify documents to be compared,
     • for creating new values from a number range for a newly created messages,
     • for passing values to variables in next the following test cases. 
     
     
     
     
     
     

     GENERAL SETTINGS

     Anchor
     GENSET GENSET

     
     
     

     • (OPTIONAL) Reference Object Definition ID can be entered in order to use configuration of another object definition.
       
       
       
       
       
     • (OPTIONAL) If IFTT is installed on a remote system and it is intended to use documents from another system, Ref. RFC Destination and  and Res. RFC Destination are  are required. 
       
       
       
       
     • In order to To receive additional debugging details select Debug Info as active while configuring a new object. Debugging details will be available at on the results screen 
       during the test case execution. 
       

...