Ansicht
Dokumentation
BAPI_EDR_TCOLL_CREATEMULTIPLE - Create EDR for Toll Billing
CPI1466 during Backup General Data in Customer MasterThis documentation is copyright by SAP AG.
Functionality
This BAPI transfers Event Data Records (EDR) for toll billing from an external system and saves them in the SAP system. The EDRs created in the SAP system are assigned to the EDR category TOLLCOLL (toll billing). In a successful transfer, the system saves the EDRs in the database table DFKKBIEDRTC.
In the transfer, the system uses the External Reference of Billing Document field (BILLACCREF) to determine the related billing account for each EDR. If the system does not find the billing account, it saves the EDR as a temporarily rejected EDR in the database table DFKKBIEDRRJTC.
For each EDR, the Transfer Time field must contain the time stamp of the current system time. The system requires the transfer time to decide whether the EDR has already been billed or not. Therefore, the BAPI must ensure that the transfer time of new EDRs is definitely not in a billed period. The procedure is dependent on whether an express billing is possible for the billing account:
- The system locks billing accounts where the Express Billing field is selected for the duration of the processing. If the system cannot run the lock - because billing is taking place at the same time - it saves the EDR as a temporarily rejected EDR in the database table DFKKBIEDRRJTC. If the lock is successful, the system sets the transfer time to a time that is before the time stamp. Billed To of the billing account.
- Billing accounts with no express billing must not be billed until the present. Consider also the field Billing Delay when defining the billing process. This ensures that the transfer time is not in a billed period.
When you define the billing process, you must specify a sufficiently large billing delay. Otherwise, there is the danger that EDRs are transferred to a billed period and never billed. Via organizational or technical means, make sure that the system time is synchronized on all application servers.
The system checks all EDR data transferred. It logs errors in the export table RETURN. If the system finds errors, the BAPI does not make a database change: No EDRs are created.
The BAPI does not run a COMMIT WORK command.
Example
Notes
To ensure best performance, you should create several EDRs with this BAPI for each call.
You can enhance this BAPi with no need for modification by implementing event 8014. Use the event to check customer-specific fields and to fill customer-specific fields in table DFKKBIEDRTC.
The BAPI can automatically process customer-specific fields that are of character type:
- To do this, add the required character type fields to table DFKKBIEDRTC and structure BAPI_TE_FKKBIEDR_TC.
- Transfer the values for these character type fields to the BAPI in the import table EXTENSIONIN. Fill the field STRUCTURE with the value BAPI_TE_FKKBIEDR_TC.
- Enter the same value that you use in the import table EDRS in the field EDRREF.
Further information
For more information, see Customer Enhancement and Modification of BAPIs (CA-BFA) in the documentation for SAP NetWeaver in SAP Help Portal(help.sap.com).
Parameters
BILLTASKKEYSEDRKEYS
EDRRJKEYS
EDRS
EXTENSIONIN
EXTENSIONOUT
RETURN
TESTRUN
Exceptions
Function Group
FKKBI_EDR_BAPIBAL Application Log Documentation SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4533 Date: 20240523 Time: 111532 sap01-206 ( 83 ms )
