Hierarchy
BBPCRM (Software Component) BBPCRM⤷
AP-PRC-PR (Application Component) Pricing⤷
VF (Package) Application development R/3 invoice
Basic Data
| Data Element | FKISM |
| Short Description | Transaction-specific pricing procedure |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Spec.proc. |
| Medium | 15 | Specific proc. |
| Long | 20 | Specific procedure |
| Heading | 4 | TSPP |
Documentation
Definition
Pricing procedure transaction-specific indicator
Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.
This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.
Example:
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
