SAP ABAP Data Element MC_DELKRRG (Key Figure: Payment based on Remuneration List Conditions)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   LO-AB (Application Component) Agency Business (Global Trade)
     MCWZ (Package) R/3 Application Development: LIS settlement
Basic Data
Data Element MC_DELKRRG
Short Description Key Figure: Payment based on Remuneration List Conditions  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type WERTV9    
Data Type CURR   Currency field, stored as DEC 
Length 17    
Decimal Places 2    
Output Length 23    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Basis d.cr 
Medium 15 Basis del cred. 
Long 20 Basis del credere 
Heading 21 Basis del credere 
Documentation

Definition

Basis value from which the del credere is calculated.

The value is derived from the subtotal 2 of the vendor-side document conditions.

Use

In this key figure the condition subtotal 2 is cumulated from those single payment request items in which the subtotal is used.

This is the case if vendor-side pricing is intended (see Customizing payment type) and the calculation schema uses the subtotal. Various calculation schemata can be used, depending on the payment type, billing document type, vendor, customer and purchasing organization.

In standard SAP R/3 this key figure is updated in the information structures S170 and S171 when the document is released to accounting. The update group in 000030 (agency business) for event WZ (single payment request).

Dependencies

Single payment requests can have various document currencies. The update is made in the local currency of the company code.

In general, it only makes sense to update this key figure if the company code is a characteristic of the information structure. Otherwise problems arise if company codes with different local currencies are used.

Unlike a sales organization, a purchasing organization does not have a statistics currency for grouping the update over several company codes when the local currencies differ. Furthermore, single payment requests do not always have a purchasing organization (Customizing payment type).

On the other hand, a sales organization has a statistics currency for grouping the update over several company codes when the local currencies differ. However, single payment requests do not always have a sales organization (Customizing payment type).

An update in the standard currency of the client (table T000) could be considered for company codes with different local currencies, but this would have to be implemented individually in the customer project.

The key figure is determined at document item level. An update in the information structures with header and item characteristics is possible.

History
Last changed by/on SAP  19991129 
SAP Release Created in