SAP ABAP Data Element GRURP_2 (Data Transfer 2nd Item)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
AP-PRC-PR (Application Component) Pricing
⤷
VF (Package) Application development R/3 invoice
BBPCRM (Software Component) BBPCRM⤷
AP-PRC-PR (Application Component) Pricing⤷
VF (Package) Application development R/3 invoice
Basic Data
| Data Element | GRURP_2 |
| Short Description | Data Transfer 2nd Item |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM3 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | 2nd Item |
| Medium | 15 | Data 2nd Item |
| Long | 20 | Data Trans. 2nd Item |
| Heading | 7 | 2ndItem |
Documentation
Definition
Data transfer routine that is run for the second item in an item pair.
Use
In the case of differential or final billing documents that are created during differential billing, an item pair consists of the current new item and the preceding billing document item that is copied with a negative value. This routine can be used to manipulate the data when creating the item that is copied with a negative value.
Dependencies
You can only make an entry in this field for billing types with the billing categories N and O that are enabled for differential billing.
Example
By manipulating the header data VBRK, you can force a split that distributes the new items and negative items between separate billing documents.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 606 |
