Fonction SAP BAPI_EDR_TCOLL_CREATEMULTIPLE - Create EDR for Toll Billing

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
TESTRUN BAPI_FKKBI_AUX-TESTRUN C 1 Switch to Simulation Mode for Write BAPIs

Paramètre Reférence Long. Facultatif Description
BILLTASKKEYS BAPI_FKKBI_BILLTASKKEY 54 X BAPI Structure: Billing Order Key
EDRKEYS BAPI_FKKBI_EDRKEY 72 X BAPI Structure: External Reference and Internal EDR Key
EDRRJKEYS BAPI_FKKBI_EDRRJKEY 80 X BAPI Structure: External Reference and Internal Key of Rejected EDR
EDRS BAPI_FKKBI_IN_EDR_TC 156 BAPI Structure for EDR for Toll Billing
EXTENSIONIN BAPIPAREX 990 X Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
EXTENSIONOUT BAPIPAREX 990 X Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
RETURN BAPIRET2 548 X Return Parameter(s)

Functionality
This BAPI transfers Event DataRecords (EDR) for toll billing from an external system and saves themin the SAP system. The EDRs created in the SAP system are assigned tothe EDR category TOLLCOLL (toll billing). In asuccessful transfer, the system saves the EDRs in the database tableDFKKBIEDRTC.
In the transfer, the system uses the External Reference of BillingDocument field (BILLACCREF) to determine therelated billing account for each EDR. If the system does not find thebilling account, it saves the EDR as a temporarily rejected EDRin the database table DFKKBIEDRRJTC.
For each EDR, the Transfer Time field must containthe time stamp of the current system time. The system requires thetransfer time to decide whether the EDR has already been billed or not.Therefore, the BAPI must ensure that the transfer time of new EDRs isdefinitely not in a billed period. The procedure is dependent onwhether 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 thesystem cannot run the lock - because billing is taking place at the sametime - it saves the EDR as a temporarily rejected EDR in the databasetable DFKKBIEDRRJTC. If the lock is successful, the system sets thetransfer 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. Thisensures that the transfer time is not in a billed period.
      When you define the billing process, youmust specify a sufficiently large billing delay. Otherwise, thereis the danger that EDRs are transferred to a billed period and neverbilled. Via organizational or technical means, make sure that thesystem time is synchronized on all application servers.
      The system checks all EDR data transferred. It logs errors in the exporttable RETURN. If the system finds errors, the BAPI does not make adatabase change: No EDRs are created.
      The BAPI does not run a COMMIT WORK command.

      Notes
      To ensure best performance, you should create several EDRs with thisBAPI for each call.
      You can enhance this BAPi with no need for modification by implementingevent 8014. Use the event to checkcustomer-specific fields and to fill customer-specific fields in tableDFKKBIEDRTC.
      The BAPI can automatically process customer-specific fields that are ofcharacter 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 fieldEDRREF.

          Further information
          For more information, see Customer Enhancement and Modification ofBAPIs (CA-BFA) in the documentation for SAP NetWeaverin SAP Help Portal (help.sap.com).