Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
| Data Element | JH_ZWG_BASE |
| Short Description | IS-M/AM: Components for Export to Pricing |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD03L |
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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 30 | Export to pricing via |
Documentation
Definition
A condition basis must be transferred to pricing during contract settlement for twinned billing datasets. This condition basis is produced from the price schema of the standard billing dataset. Once the standard billing dataset has been settled, this condition basis is temporarily saved in the structure RJHVAABP and transferred to pricing with the communication structure KOMP during the next settlement of the twinned billing dataset.
The condition basis is set in the components whose names are entered here for both structures.
Example
In the case of twinned billing datasets of the "separate agency commision" type, the agency commission basis is taken from the field RJHVAABP-JAEPRBASIS and transferred to the field KOMP-JAEPRBASIS. You should therefore enter JAEPRBASIS.
In the case of twinned billing datasets that you have defined yourself, you should add additional fields (in append structures) to these structures.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
