Ansicht
Dokumentation
RFKKCORR_EXP_UNIT_TEST - Complex Unit Tests of Correspondence
TXBHW - Original Tax Base Amount in Local Currency rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
Purpose
ABAP UNIT Test for Testing the Correspondence Tool
The components of the correspondence tool to be tested here cannot run on their own. Therefore, service methods are called for the test cases. These service methods initialize the functions. This means that an implemented application is necessary to realize the functions that are to be tested later. Internal auxiliary methos should also be used to ensure a clear overview of the "real" test methods.
For more information, see the design.
Integration
Prerequisites
Features
The ABAP Unit Test processes the following test cases:
1. Test case: Simple creation of a correspondence request
A correspondence request is to be created that is sent to an original recipient (without copy recipient) and created using correspondence type 9991.
2. Test case: Creation of correspondence with copy recipient
Creation of a correspondence request with send to original recipient and copy recipient. This correspondence should also be created with correspondence type 9991.
3. Test case: Creation of correspondence without recipient
This variant should create a correspondence request with no original or copy recipient.
4. Test case: Creation of correspondence with additional cluster data
This test case should check whether the following components have been created correctly. The task is the creation of a correspondence request with additional data in a cluster, using correspondence type 9991.
5. Test case: Creation of correspondence using a BAdI
As in the first test case, a correspondence request is created (with the same parameters). However, in this case, correspondence type 9992is used.
6. Test case: Creation of correspondence with test indicator set
In this test case, the parameters of the Test indicator should vary. In this case it should be set. That is, correspondence requests should be created in the test with the indicator set.
7. Test case: Creation of correspondence with buffer model
From the first test case, a correspondence request is to be created using the buffer model. This is confirmed. The test case tests whether a correspondence request is written to the database correctly.
8. Test case: Creation of two correspondences with buffer model and rejection of one correspondence
The buffer model results in further test possiblities. It is possible to create two correspondence requests. The first is to be rejected and the second confirmed. The result must be that a correspondence request created is written to the database.
9. Test case: Creation of correspondence with local buffer
The buffer option enable you to confirm or reject only those correspondence requests created in an LUW. This means that here you can create a correspondence request with buffer (remaining parameters as in test case 1) and to confirm it.
10. Test case: Creation of correspondence and actual printout
A correspondence request is to be created and then output. This is set up with the real printout option (in the print parameters).
11. Test case: Creation of correspondence and test print
A correspondence request is to be created and then output. This is set up with the test printout option (in the print parameters).
12. Test case: Creation of correspondence and repeat printout
A correspondence request is to be created and then output. This is set up with the repeat printout option (in the print parameters).
13. Test case: Creation of correspondence and subsequent deletion
This scenario is to test whether a correspondence request created receives the status #deleted# when it is deleted. Therefore, two correspondence requests are to be deleted, since two were created.
14. Test case: Creation of two correspondences with data in the cluster added to the first correspondence
This test case tests whether the results of the creation of a correspondence request with subsequent creation of a new correspondence request and the addition of data (Additional Information field) to the first correspondence are correct.
15. Test case: Creation of correspondence with married original and copy recipient and the Customizing setting for marriage partner linkage activated
The test case determines whether the results of the creation of a correspondence request for married original and copy recipient are correct when the setting Marriage Partner Linkage is selected in Customizing. Only one correspondence request should be created.
16. Test case: Creation of correspondence with married original and copy recipient and the Customizing setting for marriage partner linkage deactivated
The test case determines whether the results of the creation of a correspondence request for married original and copy recipient are correct when the setting Marriage Partner Linkage is not selected in Customizing. Two correspondence requests should be created.
17. Test case: Creation of correspondence with married original and copy recipient and the Customizing setting for marriage partner linkage does not exist.
The test case determines whether the results of the creation of a correspondence request for married original and copy recipient are correct when the setting Marriage Partner Linkage does not exist in Customizing. Two correspondence requests should be created.
18. Test case: Creation of correspondence with married original and copy recipient, the Customizing setting for marriage partner linkage, and different addresses for the marriage partners
The test case determines whether the results of the creation of a correspondence request for married original and copy recipient are correct when the setting Marriage Partner Linkage is selected in Customizing. The marriage partners also have different addresses. Two correspondence requests should be created.
19. Test case: Creation of correspondence with a group as recipient and the Customizing setting Group Breakdown
The test case determines whether the results of the creation of a correspondence request with a group as original recipient are correct when the group breakdown setting is selected in Customizing. Three correspondence requests should be created.
20. Test case: Creation of correspondence with a group as recipient and without the Customizing setting Group Breakdown
The test case determines whether the results of the creation of a correspondence request with a group as original recipient are correct when the group breakdown setting is not selected in Customizing. One correspondence request should be created.
21. Test case: Creation of correspondence with a group as recipient and no Customizing setting Group Breakdown
The test case determines whether the results of the creation of a correspondence request with a group as original recipient are correct when the group breakdown setting does not exist in Customizing. Three correspondence requests should be created, or as many as there are members in the group.
22. Test case: Creation of correspondence with a group as recipient and the Customizing setting Group Breakdown activated and the same address for the group and group members
The test case determines whether the results of the creation of a correspondence request with a group as original recipient are correct when the group breakdown setting is selected in Customizing. The members of the group also have the same address as the group. One correspondence request should be created.
23. Test case: Creation of correspondence with one recpient and a change in the status Printed
The test case checks whether the results of the creation of a correspondence request are correct where there is a subsequent change to the technical status to Output.
24. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = On, TDIMMED = On, and TDFINAL = Off
The test case checks whether the output of correspondence requests is correct. There must be two output spool requests.
25. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = On, TDIMMED = Off, and TDFINAL = On
The test case checks whether the output of correspondence requests is correct. There must be two completed spool requests.
26. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = On, TDIMMED = Off, and TDFINAL = Off
The test case checks whether the output of correspondence requests is correct. There must be two extendible spool requests.
27. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = Off, TDIMMED = On, and TDFINAL = Off
The test case checks whether the output of correspondence requests is correct. There must be one output spool request.
28. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = Off, TDIMMED = Off, and TDFINAL = On
The test case checks whether the output of correspondence requests is correct. There must be one output spool request.
29. Test case: Creation of two correspondences with one recipient and output in a job where the module parameters are set as follows: FONSP = Off, TDIMMED = Off, and TDFINAL = Off
The test case checks whether the output of correspondence requests is correct. There must be one extendible spool request.
Selection
Standard Variants
Output
Where the test is successful, a status message appears that all test methods were successfully executed.
However, if there is an error, the place where the error accord and the relevant assert method are detailed.
Activities
Example
TXBHW - Original Tax Base Amount in Local Currency BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 11670 Date: 20240601 Time: 053355 sap01-206 ( 145 ms )
