Kontakt

Ansicht
Dokumentation

RFKK_JP_CVS_CONVERT - Convenience Store File Converter (Japan)

RFKK_JP_CVS_CONVERT - Convenience Store File Converter (Japan)

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You, as a utility company, receive the payment data from convenience stores (or external payment collector) in an external standard payment data file format as defined by DSRI (Distribution Systems Research Institute). So that you can process the incoming payment data in your SAP system, you must convert the data into an internal file format.

You can use this report to convert the external payment data that you receive in payment files from convenience stores or from external payment collectors. As the external payment file that you have saved on an application server or on your local PC can contain real-time data, prompt data, confirmation data, and cancellation data as well, you have to execute the report separately: to convert real-time data and to convert prompt/confirmation/cancellation data.

Note:

The report can also handle payment files that contain more data blocks - each block is built up of the following parts: a header, one or more data statements, a trailer, and an end.

Integration

Prerequisites

Features

You can execute the report to either convert real-time data or prompt/confirmation/cancellation data at a time as follows:

Real-time payment data is transmitted to the utility retailer online after the actual payment transaction, for example, after 15 or 30 minutes. This immediate payment data transmission is used in special cases, for example, in case of final dunning to the customer to ensure that the utility company receives the payment data as soon as possible.

To convert real-time payment data, enter data as follows on the selection screen:

  • Choose the Real-Time Data radio button.
  • In the Source File group box, enter the navigation path to the payment file that you have already saved either to an application server or to your local PC.
  • Optionally, if you want to keep an open item from being dunned, in the Real-Time Data group box, choose the reason for blocking an open item from being dunned, using the search help. Note that if you leave this entry blank, no dunning block is set to the open item.

The report extracts the data from the payment file, converts the data and creates an entry in the Convenience Stores: Data for Convenience Store Document (DFKKCVS) database table.

To convert prompt data, enter data as follows on the selection screen:

  • Choose the Prompt/Confirmation/Cancellation Data radio button.
  • In the Source File group box, enter the navigation path to the payment file that you have already saved either to an application server or to your local PC.
  • In the Target File group box, in the Payment Lot Transfer File field enter the navigation path to the folder where you want the report to store the payment lot transfer file.
  • In the Prompt Data group box, enter the document type, posting date, and the document date.
For parallel processing, select the Post Parallelcheckbox, enter the application server and the maximum number of jobs you want the system to run simultaneously. Those parameters are used only when the Execute Payment Lot Transfer checkbox is also set. For information about the prefixes, see section Handling Prefixes below in this document.
Note:
If the file contains a combination of prompt, confirmation, and cancellation data, the posting of the payment lots (prompt data) can take time. In the Number of iterations field, you can specify how many times you want the system to recheck if the posting of the payment lots is successfully finished. The number of iterations is set to 60 by default, which means that the system repeats the check 60 times. This applies only when you select the Execute Payment Lot Transfer checkbox.
In the Prompt Data group box, you can select the Zero File checkbox if the incoming file does not contain any data for the prompt data processing.
Creation of Line Items
You can also choose to create line items in the relevant G/L accounts during the conversion by selecting the Create Line Items in G/L checkbox. When you select the checkbox, the system adds each line item separately to the generated file. If you do not select the checkbox, the system adds only one line into the file containing the aggregated amount.
Please note that this setting applies to both the prompt and confirmation data conversion. If you have selected to create the line items in G/L for the prompt data conversion, you cannot change this for the confirmation data conversion process. Once the line items have been added during the prompt process in an aggregated/non-aggregated way, the confirmation process cannot change this.
The same setting applies during the conversion of both the prompt data and the confirmation data.

Note

Also select the Execute Payment Lot Transfercheckbox if you want the report to automatically run the Payment Lot Transfer (transaction FPB3) after the conversion has been finished.

If you do not select the checkbox, you must run the FPB3 transaction manually after the payment data has been converted with this report.

To convert confirmation data, enter data as follows on the selection screen:

  • Choose the Prompt/Confirmation/Cancellation Data radio button.
  • In the Source File group box, enter the navigation path to the payment file that you have already saved either to an application server or to your local PC.
  • In the Target File group box, in the Transfer Payment Data File field enter the navigation path to the folder where you want the report to store the payment data file.
  • In the Confirmation Data group box, enter the document type, posting date, document date, and the value date. Field entries are valid only when you select the Execute Transfer Payment Data checkbox.
For information about the prefixes, see section Handling Prefixes below in this document.
In the Confirmation Data group box, you can select the Zero File checkbox if the incoming file does not contain any data for the confirmation data processing.

Note:

You can select the Execute Transfer Payment Data checkbox if you want the report to automatically run the External Payment Collectors: Transfer Payment Data (transaction FPCVS_CONF) transaction after the conversion has been finished.

If you do not select the checkbox, you must run the FPCVS_CONF transaction manually after the payment data has been converted with this report.

Note:

Please note that your line item creation in G/L setting applies to both the prompt and confirmation data conversion. You cannot change this setting for the confirmation data conversion separately. The same setting applies during the conversion of both the prompt data and the confirmation data.

To convert cancellation data, enter data as follows on the selection screen:

  • Choose the Prompt/Confirmation/Cancellation Data radio button.
  • In the Source File group box, enter the navigation path to the payment file that you have already saved either to an application server or to your local PC.
  • In the Target File group box, in the Return Lot Transfer File field enter the navigation path to the folder where you want the report to store the return lot transfer file.
  • In the Cancellation Data group box, enter the document type, posting date, document date, and the return reason.
For information about the prefixes, see section Handling Prefixes below in this document.
In the Cancellation Data group box, you can select the Zero File checkbox if the incoming file does not contain any data for the cancellation data processing.

Note:

You can select the Execute Return Lot Transfer checkbox if you want the report to automatically run the Return Lot Transfer (transaction FPB5) after the confirmation has been finished.

If you do not select the checkbox, you must run the FPB5 transaction manually after the payment data has been converted with this report.

After you have entered the document type in the Prompt Data, Confirmation Data, Cancellation Data group boxes, you can press Enter. In this case the system automatically generates and enters prefixes for the payment/return lot ID, the reconciliation key, and the lot itself into the relevant fields on the selection screen.

Note:
If you do not press Enter, after you have entered the document type and you execute the report, the system generates the prefixes in the background. The prefixes are optional for the execution of the report.

The automatically generated prefixes are built up in the format of XXYYMMDDNN where:

  • XX identifies the two-character document type
  • YYMMDD identifies the year, month, date on which the report is executed (system date (SY-DATUM))
  • NN is a two-digit constant. The two digits are 00.

If you want the system to use a different prefix, or you want to change parts of the generated prefix, change them manually and press Enter. The system will use your changed prefixes. Do not delete the generated prefixes or the ones you have changed because the report cannot be executed without them.

After you have executed the report, the system additionally assigns two digits to the end of the prefixes to uniquely identify them. The two digits range from 0 to 99. The following example explains this assignment:

Example:

You run the report twice to convert data of two files (one run per file), both containing one header with one statement with the following run ID, lot ID, and reconciliation key on July 27, 2017:

  • Prefix for Identification: 01170727
  • Prefix for Reconciliation Key: 01170727
  • Prefix for Payment/return Lot: 01170727

In this case, the system generates the following values for the run ID, lot, and reconciliation key: 0117072701 for the first file, and0117072702 for the second file.

Note the following: if you change one or two of the automatically generated prefix(es) and execute the report again for both files later but still on the same day, the system generates the values as follows:

  • Prefix for Identification: 01170727 (no change)
  • Prefix for Reconciliation Key: 02170727
  • Prefix for Payment/Return Lot: 01170727 (no change)

The generated values are the following for the reconciliation keys: 0217072703 for the first file, and0217072704 for the second file.

The report can also handle payment files that contain more than one data blocks (header to end). Each block is built up of the following parts: a header, one or more data statements, a trailer, and an end.

When the report reads the file from the local server, checks the file type, and if it is a prompt, confirmation, or a cancellation file, it first validates each data block and continues the conversion process only if all the blocks are error-free.

When you convert the file data, the system assigns a separate two-digit unique identifier to the identification and reconciliation key for each block. For example, if the file contains three blocks, the unique IDs at the end of the prefixes will be 01, 02, and 03.

This unique ID is the ID that we have already explained in section Handling Prefixesin this document.

Selection

Standard Variants

Output

The report checks settings in Customizing and the data you entered on the selection screen, and then converts the data of the chosen payment file. The report generates a text file for the conversion data and stores the real-time data in database tables.

If you have chosen the automatic execution of the FPB3/FPCVS_CONF/FPB5 transactions as well, after the conversion is finished and the required data is provided for the execution of these transactions, the report starts the execution of the relevant transaction(s).

Activities

To access the report, on the SAP Easy Accessscreen, choose Utilities Industry -> Contract Accounts Receivable and Payable -> Periodic Processing -> Copy Data -> Country-Specific Functions for Japan -> Convenience Store File Converter.

Example






General Material Data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 15670 Date: 20240520 Time: 115631     sap01-206 ( 238 ms )