• No se han encontrado resultados

2) Fusion

7.4 Evaluation of Diagnosis Methods

PATH: (SPRO)

IMG  Sales and Distribution  Billing  Payment Cards  Maintain Card Types PROCEDURE:

Add missing card types.

[NEW ENTRIES] BUTTON PARAMETER SETTINGS:

Card Type Description

DIN Diners card

KK Customer card

EC Electronic cash

AMEX American Express VISA Visa Card

MC Master Card BACKGROUND:

This information about the card type can be specified in the IDoc and used as selection criteria for reports in the RIS.

REMARKS: BC SET:

/BPR3R/SD_KART

3.3.12.2 Assign Account Determination Procedures for Credit Cards to Billing Type

PRECONDITIONS:

Billing type FP has been maintained in the POS interface - inbound.

PATH: (SPRO)

IMG  Sales and Distribution  Billing  Payment Cards  Authorization and Settlement  Maintain Clearing House  Account Determination  Maintain Procedures  Assign Account Determination Procedures

PROCEDURE:

Assign an account determination procedure to the billing type for the POS interface (FP).

PARAMETER SETTINGS:

BillT ADPyCd

FP A00001

BACKGROUND:

The account determination procedure determines the reconciliation account (account in which the receivables are posted to the clearing house, such as 146500). The account determination procedure is a pricing procedure for account determination for payment cards. It contains

condition type A001, which refers to the access sequence of the same name. You can display the access sequence in transaction 0V84.

REMARKS: BC SET:

/BPR3R/SD_ZKART_SCHEMA

3.3.12.3 Assign Clearing Account

PRECONDITIONS:

Settings have been maintained for the company code, in particular the chart of accounts.

The account determination procedure has been assigned to the billing type.

PATH: (SPRO)

IMG  Sales and Distribution  Billing  Payment Cards  Authorization and Settlement  Maintain Clearing House  Account Determination  Assign G/L Accounts  Table 4 - General PROCEDURE:

Specify a reconciliation account (G/L account) for each sales organization.

PARAMETER SETTINGS:

Appl. CandTy Charts of Accounts SOrg. G/L Account

VD A001 INT V001 146500

BACKGROUND:

In this step, you assign the appropriate card types the accounts to which the open items to be settled to the clearing house are posted.

REMARKS:

In this case, only one account from chart of accounts INT is assigned to the various card types. If a settlement is carried out, the card type is specified as an additional selection criterion. Table 6, however, enables you to specify different G/L accounts for each card type, if a particular volume of receivables is reached. If you are working with different clearing houses, you have to specify an account for each clearing house, since a logical destination for the data transfer is assigned to each clearing house.

BC SET:

/BPR3R/SD_ZO_KTO_ZKART

3.3.12.4 Make Central Settings for Payment Cards

PRECONDITIONS:

The customer who is paying by card has been maintained in the system.

PATH: (SPRO)

IMG  Financial Accounting  Accounts Receivable and Accounts Payable  Business Transactions  Payments with Payment Cards  Make Central Settings for Payment Cards PROCEDURE:

Maintain settings to determine whether the customer line item is to be retained in the accounting document.

PARAMETER SETTINGS:

‘Settings for Forwarding Billing Documents to FI’ subscreen Retain cus. item: ‘X’ Set indicator

‘Settings for the Settlement Document’ subscreen

Document type: ‘AB’

‘Settlements for Resetting Clearing when Settlement Unsuccessful’ subscreen Document type: ‚AB’

BACKGROUND:

You specify whether the posting to customer account is to be retained for your customer who is paying by card. The open item in the document is cleared immediately and an open item is created in the clearing house’s G/L account instead (receivables from payment cards).

In addition you specify the document type for settling payment card data to the clearing house.

REMARKS:

Although more database space is needed if this indicator is set (due to more line items), you have the advantage of being able to display receivables on the debit side and being able to deal with any settlement problems more easily.

BC SET:

/BPR3R/FI_ZKART

3.3.12.5 Settlement Control Per Account

PRECONDITIONS:

The customer who is paying by card has been maintained in the system.

PATH: (SPRO)

IMG  Sales and Distribution  Billing  Payment Cards  Authorization and Settlement

Maintain Clearing House  Set Authorization / Settlement Control Per Account PROCEDURE:

PARAMETER SETTINGS:

ChAc Receivable Clearing INT 146500 113105 Choose [Details].

‘Authorization Control Functions’ subscreen Authorization: CCARD_AUTH_SIMULATION

‘Settlement Control Functions’ subscreen

Settlement: CCARD_SETTLEMENT_SIMULATION BACKGROUND:

REMARKS:

You do not need to maintain any further settings here, since the standard settings for chart of accounts INT are used.

3.3.13 Pricing Control

3.3.13.1 Maintain Condition Types

The sales price and the payment methods are set as condition types in the IDoc. These fields are filled by the converter, which also performs calculations if necessary. Condition types have to be maintained for this purpose. Condition types are one element of the standard pricing activities. They can be created for all types of pricing element, such as prices, markups and markdowns, tax, and so on. For the individual pricing elements and conditions, standard SAP condition types can be used or new ones defined to suit company requirements.

Conditions represent a set of circumstances that apply when a price is calculated. The variable factors, such as the customer, product, and so on, determine the final price. This information is stored in the system as condition records in condition tables. Several condition records usually exist for each condition type.

A pricing procedure defines the valid condition types and the sequence in which they are calculated. An access sequence can be assigned to each condition type. An access

sequence is a search strategy that the system uses to find valid records in a condition table.

The names of the access sequences often correspond to the condition types for which they were designed. The system repeats this process for each condition type in the pricing procedure and determines a final price.

Condition types can be determined using automatic pricing, or set manually. Condition records must already exist for all the condition types that the system is to use automatically.

These are maintained in the customer/material master record. In Customizing, you make precise settings for each condition type to define the extent to which manual changes can be made.

In this ‘sales’ process, the condition types are set manually (by the converter).

Important condition types for the process:

Payment method for cash payment (PTCS) Payment method for voucher (PTVO)

Payment method for customer card (PTBL) if postings are to be made directly to the customer (payment by invoice to customer).

Sales price (PN10)

Item discounts (RB10, RB19) Header discounts (HB00) Net value (PNET)

3.3.13.2 Maintain Condition Type for Cash Payment

PRECONDITIONS:

Condition type PTCS already exists. You just need to define the condition category for this type.

PATH: (V/06)

IMG  Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define Condition Types  Maintain Condition Types

PROCEDURE:

Change the settings for the existing condition type PTCS. Position your cursor on PTCS by choosing [Position]. Select the row, choose [Details], check the parameters, and add the condition category (lower case).

PARAMETER SETTINGS: Cond. Type

Cond. Class Calc. Type Cond. Category Group Cond. Manual Entries Plus/Minus Header Condit. Item Condition

PTCS

A B g X Blank X X Blank BACKGROUND:

Condition type PTCS is required in pricing procedure POSPCS for pricing and for determining the accounting account for the POS using an account key assigned to the condition type.

REMARKS: BC SET:

/BPR3R/SD_KOND_ART

Discounts can also be transferred and the VAT calculated for domestic sales.

To maintain the condition types, choose:

Customizing  Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define Condition Types  Maintain Condition Types

or enter transaction V/06.

The standard system already contains the required condition types and their settings. It is only for the means of payment that you have to define the condition category (lower case).

Access sequence No

Condition class A Discount or surcharge

Calculation type B Fixed amount

Condition category g Payment

Rounding rule Commercial

Header condition X

Item condition No

Group condition X

Plus/minus X Negative

Manual entries No limitations

Payment method, in which postings are made directly to the customer (PTBL).

If you want to make postings to a customer card on the debit side, you can either use payment method PTBL or not transfer a means of payment, which means that the system automatically posts the amounts that are not covered by the means of payment to the customer.

Access sequence No

Condition class A Discount or surcharge

Calculation type B Fixed amount

Condition category

Rounding rule Commercial

Header condition X

Item condition No

Group condition X

Plus/minus X Negative

Manual entries No limitations

Access sequence No

Condition class A Discount or surcharge

Calculation type B Fixed amount

Condition category H Basic price

Rounding rule Commercial

Header condition No

Item condition X

Group condition No

Plus/minus Positive and negative

Manual entries No limitations

Net Value (PNET)

Access sequence No

Condition class A Discount or surcharge

Calculation type G Formula

Condition category L Generally new when copying

Rounding rule Commercial

Header condition No

Item condition X

Group condition No

Plus/minus Positive and negative

Manual entries D Not possible to process manually

The system determines the VAT using tax codes. You cannot specify VAT amounts manually.

Access sequence MWST Value-added tax

Condition class D Taxes

Calculation type H Percentage included

Condition category D Tax

Rounding rule Commercial

Header condition No

Item condition X

Group condition X

Plus/minus Positive and negative

Manual entries D Not possible to process manually

Group cond. routine 0

RefConType MWST

RefApplicatio V Sales/Distribution

3.3.13.3 Maintain Pricing Procedures

The pricing procedure is used to determine which condition types are taken into account, and in what order. In addition, the pricing procedure determines what subtotals are formed and the pricing screen on which they are displayed, how far it is possible to edit pricing manually, on what basis percentage markups and markdowns are calculated, as well as the conditions that must be met to assure a certain condition type can be taken into account.

PRECONDITIONS:

The condition types and keys have already been maintained.

PATH: (V/08)

Customizing  Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures  Maintain Pricing Procedures

PROCEDURE:

Take a look at pricing procedure POSPCS and find the condition types described.

PARAMETER SETTINGS:

Refer to the screenshots below for the parameter settings.

BACKGROUND:

The POS inbound profiles in sales contain the name of the pricing procedure to be used. The existing standard SAP pricing procedure called POS000 already contains condition type PTBL for invoiced amounts (used for customer card) and PTCS for cash payments. Pricing procedure POSPCS, which is used in the BEST PRACTICES, has been extended to additionally take account of the requirements of the bonus buy process for example.

REMARKS:

INFO: If you want to make changes to the existing pricing procedure, you are advised against making direct changes to the standard pricing procedure. Instead, you should copy the standard pricing procedure and create your own pricing procedure, in which you then make the required changes.

IMPORTANT: Copy the pricing procedure with all the dependent settings.

BCSET:

/BPR3R/SD_KALKSCHEMA_ZO