Ansicht
Dokumentation

Payment cards in accounting ( RELNPS_30F6_PURCHASECARD )

Payment cards in accounting ( RELNPS_30F6_PURCHASECARD )

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Payment cards in accounting

Description

From Release 30F/PS/6 purchases made using payment cards (e.g. VISA, AMEX, MasterCard) can be processed in SAP Financial Accounting (Accounts payable). In this way settlement and source-related updating of the individual accounting transactions are executed in accounting.

There is no integration between the component Purchasing and the payment processing in accounting.

The use of the component Purchasing is not presupposed. If you implement this component, the data generated there will not be considered.

Outflow

  1. A payment card (Purchase card) is placed at the disposal of employees of a company (XYZ) by its own company. With this card employees buy or order articles. The credit card company (VISA, AMEX,....) debits the employees' company.
  2. The credit card company transmits a file with the data of the individual business transactions to the company (XYZ). No account assignments, e.g. CO account assignments, cost center, order or FM account assignments (commitment item, funds center, fund, funds reservation) or a purchase order reference are included with the data. However, information which is not operatively evaluated can be included in the text fields provided on the input file.
  3. The total of the individual business transactions is posted as an invoice and paid by the company (XYZ).
  4. Every accounting transaction is posted as a single, accounting document which can optionally be a parked document with or without Workflow.
    The accounting documents' account assignment can be taken from:
    1. the card master record or
    2. a card voucher.
      Entering a card voucher is not necessary for the outflow described above and can be created anytime before of after the actual purchase transaction takes place. (Note: If the card voucher is to be effective for a specific processing period, then it naturally must be entered before the relevent transaction file from the credit card institute is processed.) A card voucher is comparable with a funds reservation in Controlling or in Funds management. It contains the following important data:
      - Card number
      - Transaction amount
      - Transaction date
      - account assignment which differs from the card master file
      The card voucher has the additional function of reserving funds from a budget specifically for purchasing.
    3. The account assignment taken from card master record or the card voucher can be adjusted manually in the parked document.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

You execute the required Customizing settings in the financial accounting application menu. For this choose Accounting -> Financial accounting -> Accounts payable-> Environment ->Payment cards.

If Workflow is used with the parked documents you have to carry out the following Customizing settings for the Workflow:

  • Maintaining the linkage table (Transaction SWE2):
    Object type FIPP
    Event CREATECARD
    Receiver type WS50000021
    Receiver Fm SWW_WI_CREATE_VIA_EVENT
    Check Funktion
    Receiver type Fm
    Destination
    global X
    enabled X

    For this choose Tools -> Business Engeneering -> Business Workflow -> Development -> Utilities -> Other tools -> Event linkage.
  • Assign the standard task in the organizational plan:
    TS 50000048 FIPP_CHAPOST

    For this choose Human Resources -> Planning -> Organization ->
    Change OrgPlan

Effect on batch input

Changes to the Interface

Changes in procedure

The use of payment cards processing requires the following procedure:

  1. Maintaining authorizations.
    In the standard the model profile F_PCARD_ALL is delivered.
  2. Setting up the number range for card documents. (Customizing)
    For this choose Accounting -> Financial accounting -> Accounts payable -> Environment -> Payment cards -> No.range crdt vchr
  3. Setting up the card types. (Customizing)
    For this choose Accounting -> Financial accounting-> Accounts payable -> Environment -> Payment cards -> Card types -> Maintain
  4. Setting up card master records and the default account assignment.
    For this choose Accounting -> Financial accounting -> Accounts payable -> Master records -> Payment cards -> Create
  5. Periodic importing and storing of the card transactions in the R/3-System.
    For this choose Accounting -> Financial accounting -> Accounts payable -> Periodic processing -> Payment card data -> Read original file.
  6. If a Workflow is used with the parked documents you must carry out the corresponding Customizing settings for the Workflow.
    This Customizing is completely independent of the Customizing for the parked accounting documents. You carry out the essential settings in
    each card master record.
  7. Generating the (parked) accounting documents which perhaps can only be changed and posted via a Workflow processing.
    For this choose Accounting -> Financial accounting -> Accounts payable -> Periodic processing -> Payment card data-> Process data.
    For processing mass data SAP recommends the generation of accounting documents with the Batch Input in the background. For this you must create a corresponding variant and a job for the Report RFFCRD10.
  8. Processing the Error log file (Errors detected when attempting to post).
    For this choose Accounting -> Financial accounting-> Accounts payable -> Periodic processing -> Payment card file -> Process data.
  9. Possible changing/posting of parked documents in Workflow by the agents specified in the card master file.

Procedure for removing dataset errors

Dependent functions

Planning

Further notes






rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 7009 Date: 20240523 Time: 062252     sap01-206 ( 104 ms )