Description
This program imports credit card transaction data into the SAP systemfor use in the Travel Expenses application.
A file format has been agreed upon by SAP and the credit card companiesthat contains all relevant data for credit card transactions.

• Import of data file and verification of data

This includes verification of the correctness of the data file, thecredit card number of the employee, the name of the employee, thetransaction currency, and the expense type.

• Assignment of credit card transactions to employees

The assignment is based on the personnel number and name of theemployee, and the credit card number.

• Import of transactions into the document buffer or the employees trips

The three radio buttons on the selection screen are of primaryimportance here (use F1 help for more information on them).
A transaction will be imported to the relevant trip as a receipt if theimport of the transaction to a trip is permissible based on theselection parameters, a trip already exists for the employee for thecredit card transaction date, the transaction is in accordance withsettings in the assignment table (see below), and no mandatory entriesmust be made for the relevant trip expense type in the Additionalreceipt info window. Otherwise it will be imported into the documentbuffer as a credit card receipt and can then be imported to the relevanttrip by the employee.

• Transfer unassignable credit card transactions to a correction table

Credit card transactions that cannot be assigned are moved to tablePTRV_CCC. You can then process these transactions using general tablemaintenance or view V_PTRV_CCC. The view only displays transactions thatneed to be corrected. Once all transactions have been corrected, you canuse report RPRCCC_CREATE_CORRECTION_FILE to create a few file, which canthen be imported back into the system.

• Start the report as a test run first, because this checks the
relevant settings and outputs a list of missing or incorrect settings inthe system.
CAUTION:
If fatal errors occur in the production system while a data file isbeing imported (such as if certain settings are missing in theassignment table of credit card clearing), the import will not becompleted properly. The list output of the report will then include theentry "The import was therefore only performed as a test run." No dataof that data file is transferred into the document buffer in such cases.

• If the report was not completed correctly due to an error in the system
or some other factor (see above), you must first reimport your lastimported data file. Only the data that was not imported to either thedocument buffer or to trips during the last report run will be imported.To check whether a credit card accounting run has been correctly andcompletely imported, you can view the table of imported credit cardaccounting runs. If a run was not completed successfully, this willnormally be indicated in the top entry.

• If individual transactions cannot be assigned (due to an incorrect
personnel number or name, for example), they are moved to tablePTRV_CCC. Transactions that are incorrect (due to the wrong currency orgeneral currency problems, for example) are moved to table PTRV_CCC aswell. You can correct these errors using general table maintenance orview V_PTRV_CCC. The corrected transactions can then be added to a newfile using report RPRCCC_CREATE_CORRECTION_FILE, and reimported usingreport RPRCCC00. The exported transactions (from table PRTV_CCC) areidentified as such and cannot be duplicated.

• If a personnel number is locked during the data import, the data for
that personnel number cannot be imported directly to trips. In that casethe data is imported to the document buffer instead. This cannot be seenin a test run.

Precondition
The credit card company's accounting currency should be the same as theemployee's local currency.
Furthermore, before importing a data file you should make certain that:


• Your employees' credit card numbers are stored in the system


• The table for the assignment of credit card company expense keys to the
trip expense types in travel expenses is maintained

• Credit card clearing is activated in feature TRVPA

An employee's credit card numbers must be stored in the informationtype Communication (0105), subtype 0011. The first two placesidentify the credit card company, and the remaining 19 places are thecredit card number.
The assignment table can be maintained in Customizing under DefineAssignment Table for Credit Card Clearing (view V_T702B).
In the step Set Up Feature TRVPA for Travel Expense Parameters,the value for parameter in feature TRVPA must be set to 1
for the relevant organizational unit.