Ansicht
Dokumentation
RFUBCCEUPL - Transfer Cost Event Files
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up General Material DataThis documentation is copyright by SAP AG.
Purpose
This program is used for the manual or periodic transfer of cost event files. These files are generated by the components of SAP Biller Consolidator. The files can be saved on the application server or presentation server. The program reads the files, carries out formal checks and saves the cost event data in the system. Incorrect files are not processed. If errors occur, you should contact SAP.
Note that batch processing is only possible for file uploads from the application server. If you use batch processing to upload files from the presentation server, the program will be terminated.
The data is subsequently processed with program RFUBCCCRE (transfer to the billing application, for instance Service Billing).
Integration
This program can be used in the Schedule Manager.
Prerequisites
The cost event files must be saved on an accessible server (SAP application server or presentation server)
The file names must have the form "name.extension", whereby the "name" must not exceed 32 characters and the "extension" 3 characters. The cost event files generated by SAP Biller Consolidator comply with this convention.
Features
Selection
You can specify whether the files are imported from the application server or presentation server.
- Application Server
- Enter the path (e.g../COST_EVENT_DATA) and the file name or a filter (e.g. *.ced).
- Presentation Server
- Enter the path (e.g. C:\COST_EVENT_DATA) and the file name or a filter (e.g.*.ced).
If you set the indicator, you specify that the files will be deleted after successful processing. Incorrect files will not be deleted.
You can activate a duplicate processing check by setting the indicator. The system then checks whether a file of the same name has already been imported. If this is the case, the file is not processed.
If you set the simulation indicator, the data transfer is tested. In this case, no data is actually transferred to the system and no files deleted.
Standard Variants
No standard variants are delivered to the customer.
Output
The system logs the result of the data transfer, listing all messages along with the respective file.
Activities
Example
General Material Data BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 2757 Date: 20240601 Time: 053533 sap01-206 ( 48 ms )