PI Unit - self-creation of automation objects

USE:
The PI Unit Test type requires a minimal level of parameters to start test automation. This test type will validate the processing in the SAP PI/PO platform only.

Suppose the automation object doesn’t exist for an interface in both Int4 IFTT Test Case Cockpit and PI/PO Robot. In that case, there is an option to automatically create it for a new SAP PI Unit Test Interface. The new object will be made based on the source message.

PREREQUISITES:
You have completed the steps described in the General rules for a test case creation.

Example for Int4 IFTT Test Case Cockpit (tcode /INT4/IFTT_COCKPIT):

Choose Interface Type - PI Unit Test. Enter a message number GUID from PI (you can use Message Selector for this) and hit save:
Int4 IFTT will try to find an existing automation object based on Service Interface Name and Service Interface Namespace from the SAP PI/PO message header. If no automation object is found, IFTT will display a pop-up with relevant information and propose Object ID and Description. You can change it according to your needs.
Suppose an automation object with the same Service Interface Name and Service Interface Namespace already exists in the IFTT's database. In that case, it will be automatically populated in the column Automation Object. In this case, you can save the test case - it's ready for execution.
As above, if an automation object doesn’t exist, we can change the Object ID to our own. In the example, we called it ‘SELF_CREATION_OBJECT’ and leave the proposed description. Now press the Save button to confirm both the test case and automation object. Result:
Automation object ‘SELF_CREATION_TEST’ was created and saved in the database. Now, assuming you make new test cases where Service Interface Name and Service Interface Namespace are the same as in the new object. Then, the system won’t create a new automation object - it will look in configuration and pick up an existing object ( in our case - ‘SELF_CREATION_TEST’).