Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VA0C (Package) Customizing R/3 sales
Basic Data
| Data Element | PUSH_GRP |
| Short Description | Update lower level contract - on/off |
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 | Update |
| Medium | 15 | Update l.l.cont |
| Long | 20 | Update low.lev.cont. |
| Heading | 6 | Update |
Documentation
Procedure
Activate this field if you want all lower level contracts to be updated when you change a master contract of this sales document type.
When you change the master contract, a workflow scenario is initiated which updates the lower level contracts immediately. The system accesses each lower level contract and determines on the basis of the referencing procedure whether the changes in the master contract should be copied.
If you do not activate the update function, changes to the master contract reach a lower level contract, when you specifically call the lower level contract for processing.
Dependencies
Fields to which rule C has been assigned are only updated if the workflow scenario runs without any errors.
When errors occur, the user who changed the master contract receives a work item which enables him to make the changes in the lower level contract manually. Two sessions are created. One session lists all changed data and a description of the errors. The second session starts the transaction for processing the lower level contract.
History
| Last changed by/on | SAP | 19970902 |
| SAP Release Created in |
