All business object processing originates from the Java component of the connector. This is for all objects and all possible verbs. To unit test, the adapter includes an ABAP program that simulates the connector's action of sending in a business object request.
Specifically, the program simulates the doVerbFor() processing in the Java component of the connector by calling the ABAP function module Y_XR_RFC_DO_VERB_NEXTGEN. Like doVerbFor(), the test program requires a business object as an input to pass to the ABAP function module n. The ABAP test program uses a text file as its input.
All input test files have the same ASCII text format. From this file format, the test program restructures the data to resemble the business object passed to Y_XR_RFC_DO_VERB_NEXTGEN. The following rules apply to business object input files:
Table 15. Attribute Properties and Values
Attribute Property | Description or Possible Values |
---|---|
Name | name of the attribute |
Value | value of the attribute or CxIgnore = 'CxIgnore' or CxBlank = ' ' |
IsKey | value that specifies whether the attribute is a key:0 = no 1 = yes |
Peers | NumberOfPeers value expressed an integer that represents the total number of child business objects at the same level For example, if an Item business object contains two line items, each line item would have the value '2'. |
AppInfo | application-specific information that is specific to each business object |
The test program provides a Quick Retrieve function to help generate a test input file. For more information, see "Testing an ABAP handler".