SAP ABAP IMG Activity SIMG_CFMENUOLMEKONDT (Set Up Condition Technique for Subsequent Settlement)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ ME0C (Package) Customizing R/3 Purchasing
IMG Activity
ID SIMG_CFMENUOLMEKONDT Set Up Condition Technique for Subsequent Settlement  
Transaction Code S_ALR_87002101   IMG Activity: SIMG_CFMENUOLMEKONDT 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLMEKONDT   Set Up Condition Technique for Subsequent Settlement 
Customizing Activity SIMG_CFMENUOLMEKONDT   Set Up Condition Technique for Subsequent Settlement 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLMEKONDT    



The "subsequent settlement" (end-of-period rebate settlement) facility in the standard SAP System works in the same way as a price determination (pricing) mechanism with its own account determination process. Therefore, the same components of the condition technique must be maintained as in the case of price determination.

Notes

If you use a jurisdiction code for tax processing in the company code, the tax information in the purchase order or invoice verification is not used to update the statistics. Instead, you use the tax code and the jurisdiction code of the booking code for non-taxable transactions. This means that the statistics update and settlements are treated as non-taxable transactions.

Standard settings for "subsequent settlement"

  • Revenue Account Determination

    The standard SAP System contains the access sequences 0004, 0005, 0007, 0008, 0009 and 0010 for subsequent (end-of-period rebate) settlement.

  • Configure Automatic Postings

    Condition types A001, A002, A0003 and A0004 are provided for subsequent settlement purposes.

    The following condition types have been included for the debit-side settlement type:

    'MWST' for tax determination

    'VS00' as a tax trigger for the tax code

    'MWVS' to provide tax data from VS00

    'SBCB' to provide the header data in the case of the billing document

    'S000' to provide the settled income data in the case of the billing document

    Notes

    • The names of the last two condition types can not be changed because they are mandatory for debit-side settlement accounting.

  • Condition Table

    The rebate arrangement number has been included in the key for the condition table for subsequent settlement. This permits several rebate arrangements to be managed under the same condition type and variable key.

  • Calculation Schema

    No separate calculation schema (may also be termed "pricing procedure") has been included for the purposes of subsequent settlement.

  • Settlement Schema

    The settlement schema RM5000 is provided for subsequent settlement.
    There is a separate schema determination facility for schema RM5000.

    Separate tax code determination is carried out for condition type MWST in schema RM5000 for debit-side settlement.

    Account key VST must be maintained for condition type MWST.

    Tax determination is not carried out for schema RM5001. The tax code is copied from the business volume statistics and entered in the item of the billing document. The amount is determined directly.

Standard settings in account determination

  • Additional account keys

The following account keys have been added:

  • B01 Provisions for subsequent settlement
  • B02 Income from subsequent settlements
  • B03 Differences involving provisions
  • VST Tax determination for debit-side settlement

In the calculation schema for revenue account determination, the condition types for subsequent settlement (A001, A002) have the account key 1 (AccKy1) BO2 and the account key 2 (AccKy2) BO1 respectively.

  • Account determination for debit-side settlement is the same as account determination in SD. You must ensure that the account keys of the debit-side settlement schema (BO1, BO2, VST) exist in SD Customizing (See Revenue Account Determination).

  • If you want to carry out debit-side settlement, you must maintain the vendor as a customer with partner role 'Payer'.

SAP recommendation

You are advised to use the elements provided in the standard system for subsequent settlement and account determination. In this case, you need take no further action.

Activities

First check whether you can adopt the elements for subsequent settlement and account determination provided in the standard system supplied. If you wish to extend or adjust these elements, you must attend to the following points:

  1. Maintain tax rates for the debit-side settlement type
  2. Maintain the field catalog
  3. Set up an access sequence
  4. Create a condition table
  5. Define appropriate condition types
  6. Define an amount interval per condition type

    Here you can set upper and lower limits for the permitted amounts for each condition type.

  7. Calculation schema

    Condition types that are to be taken into account in price determination must be included in the relevant calculation schemas for price determination. If you wish to set up provisions, you should ensure that the key B01 is assigned to the condition types for subsequent settlement in the field "Account key 2" (AccKy2).

  8. At the time of goods receipt, provisions can be created, which are updated during the invoice verification process to form cumulative business volumes. The standard system is set up (via requirement 26 in the calculation schema) in such a way that the condition types for subsequent settlement appear in the PO as statistical condition types at the end of the price screen.
  9. Settlement schema

    Condition types that are to be taken into account during price determination must also be included in the settlement schema.

  10. Schema determination

    This facility is used to determine which settlement schema is used for subsequent settlement accounting.

  11. Define overviews for condition records

    An overview defines a particular view for several condition records, including those with different condition types. For example, you can define an overview which allows you to display and change only the administrative data for certain condition records. An overview can consist of any number of views, but the initial view and the sequence of subsequent views must be defined.

    The fact that you can define variable views for condition records makes condition record control easier and reduces the amount of data you need to enter.

    An overview consists of two parts:

    • The static part contains the condition type and the fields which comprise the condition table key.
    • The dynamic part contains the data, which is different for each view selected. You define this part in Customizing for the overview.
      If necessary, you can create user-specific views.
  12. The checking of the calculation schemas allows straightforward control of the schemas that are available in Purchasing.
    You can obtain further information:
    • On the selection screen under the menu option "Help - Help on application".
    • On the output list by double-clicking on the line that is highlighted in color. If desired, you can also initiate the necessary Customizing activities via this dialog box.

Account determination

For information on account determination, refer to the step Configure Automatic Postings in the IMG under Materials management -> Valuation and account assignment -> Account Determination -> Account Determination without Wizard -> Create Automatic Postings.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUOLMEKONDT 0 HLA0009512 Purchasing 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VV_T681F_EM V - View SM30 0000000009 Maintain Field Catalog for Subsequent Settlement 
VVC_T682_MA C - View cluster SM34 0000000016 Define Access Sequences for Subsequent Settlement 
VV_T685A_MA V - View SM30 0000000001 Create Condition Types for Subsequent Settlement 
IMGDUMMY D - Dummy object OMHA 0000000001 Define Condition Table for Subsequent Settlement 
VV_T685Z_M1 V - View SM30 9999999999 Define Upper/Lower Limits for Conditions for Subsequent Settlement 
VVC_T683_MA C - View cluster SM34 9999999999 Maintain Settlement Schema for Subsequent Settlement 
V_TMKS_BO V - View SM30 0000000001 Schema Determination for Subsequent (End-of-Period Rebate) Settlement 
OBYC T - Individual transaction object OBYC 0000000020 Account Determination for Subsequent Settlement 
IMGDUMMY D - Dummy object MEBC 0000000001 Check Calculation Schemas for Subsequent Settlement 
History
Last changed by/on SAP  19990223 
SAP Release Created in