直接在BAPI中手动输入测试数据显然又费时间又不现实.使用程序FBGENDAT可以实现测试目的.
Troubleshooting for BAPI problems is difficult if the parameters transferred to the interface are not completely available as a test data record. This is particularly problematic if the BAPI is called by RFC,and then debugging is very complicated or cannot be performed at all. For example, this is the case when the BAPI is called from SAP applications such as SRM and APO, but in particular, when the BAPI is called from external systems that are programmed with Java, MicrosoftVisual Basic or C++ and that use SAP integration technology such as BAPI ActiveX Control, C++ class libraries, or Java Connector.In these cases, it would be useful to have a complete test data recording the Function Builder, which could be used to reproduce the error in the target system.
1. For the user, under whose name the call is to be executed, enter parameter FBGENDAT = X. Use Transaction SU01
to do this. If the call comes from an external system, the caller can be an RFC user.
2. Execute report FBGENDAT to activate the generation of test data records for certain function modules. Enter the corresponding function module in the first line. Choosethe mode in which you want to generate the report and execute it.The displayed list shows all function modules for which the testdata generator is active and in which mode.
3. Start the BAPI call and check whether a test data record was generated in the Function Builder.
4. Deactivate the generation of test data records by deleting the entries in report FBGENDAT and resetting the user parameter.
Note 539978: Automatic generation of BAPI test data directory