Changing Data at Header Level
The following logic applies to the item level data if you change data at header level:
When you change a field at header level, if the contents of the fields at header and item level agreed before any changes were made, these changes are copied to the item.
This applies to business and contract data.
The following graphic provides an example:
Caution
Caution
Note the following rules:
If items have already been billed, changes to the pricing date and exchange rate at header level are not copied to the items. The system displays a warning message.
If the pricing date is changed at header level and the items have not yet been billed, the exchange rate is also copied to the item.
If the currency is changed at header level, the exchange rate is always copied to the item. This also applies to items that have already been billed. The system displays a warning message.
Special Features for Contract Data
If you change contract header data that affects item data (such as the contract start date), the system collects messages and activities while it copies the data. It then displays an activity log in a dialog box containing details about the item, field and message. You can use user exit EXIT_SAPLV45W_001 to extend the activity log, for example, by running checks that meet your individual requirements.
The following rules apply when changing contract data at header level:
If an item has already been canceled, the changes at header level will not affect it.
If you cancel at header level, the item is canceled for the next possible cancellation date according to its data.
If the contract end data at header level is before the contract start date at item level (for example, header contract end date: 1 January 1998, item contract start: 1 June 1998), the system sends a note to the activity log. You can then reject or delete the item manually.
If you extend the contract end date at header level and the contract end date for the item has already been exceeded, the item contract end date can only be extended if it originally agreed with the header date.
If the validity of the item does not correspond to the validity at header level, the system creates a note in the activity log.
The system never copies the rules for contract end and contract start dates. Once the data has been copied, the rules are always deleted so that nothing can be determined at item level.