Entering content frameImporting Credit Card Transactions Locate the document in its SAP Library structure

The data file import should not access travel expense accounting, where possible, as this locks the personnel numbers for further processing (for example, for other credit card transactions). The program RPRCCC00 (import credit card files), used to copy and process credit card transactions, reads all of the data of a data file. During the process, the system checks to see if the data records in the data file are correct. If the data records were imported successfully, they are indicated on the data file and blocked to prevent double importing.

You start the program RPRCCC00 manually from Travel Management. You can start the program as a test or update run. You can automatically run the report using Job Processing, and is recommended as long as a successful pilot has been completed.

Test run

The aim of a test run is to check the data files and the R/3 System settings. The program creates a list of missing or incorrect system settings. This error list allows you to correct the master data and/or to change or add the required system settings in Customizing.

Update Run with Table for Data Records with Errors

The aim of an update run is to transfer credit card transactions to trips or to the receipt buffer. If the test run does not show missing or incorrect system settings, you can start importing the data file in an update run.

Now, every credit card transaction that does not pass the data checks is imported into a database. The transactions that do not have errors are imported to the receipt buffer (or assigned to trips) and can be processed immediately.

The new function for processing transactions with errors (Transaction PRCCE) allows you to correct any data records with errors. After you have done this, you can generate a new credit card file using transaction PRCCF and import it using report RPRCCC00.

Errors and Error Handling

The main cause for data files being imported incorrectly is missing or incorrect system settings or conflicting master data (personnel and credit card number). You should have already discovered such sources of repeated errors by means of a test run.

It is also possible that cluster TC is locked for the personnel number required at the time of import of a data record because the buffer is already being accessed by trip data entry. The data record can not be imported. Since this is only a temporary cause of errors, it is not shown in the error list of the test run.

If you want to check to see if a credit card accounting run has been correctly and completely imported, you can view the table of imported credit card accounting runs.

 

 

 

 

Leaving content frame