The indicator you enter in this field controls the
1. Whether you can enter contract
data for a sales document of this type
2. How changes made in the contract
header affect the contract item data
Leave this field blank if you do not want contract data to be
maintained for a sales document of this type.
If you want to be able to maintain contract data for a sales
document of this type, enter either X or
Contract header data applies to all
the contract items until you enter data at item level which differs
from the header data. Once item data differs from the header, it is
the indicator you set in this field which determines how changes to
the contract header affect the contract item data:
Contract data allowed = X
If the indicator X has been set in
the Contract data allwd field, any
changes you make to the contract header data will not be copied
into the items. This applies even if the contract item data was
identical to the contract header data before you made the changes
to the header data.
Contract data allowed = Y
If the indicator Y has been set in
the Contract data allwd field, any
changes you make to the contract header data are automatically
copied into the items if the contract item data was identical to
the contract header data before you made the changes. When you make
changes to data in the header of a contract, the system determines
whether the data should be copied into the items. On completing
this process, the system issues a log which informs you of the
actions it has taken. It also informs you of any problems or
inconsistencies which require your attention.
Each entry in the log specifies the
Action taken by the system or to be taken by you
From the action log you can perform
functions such as the following:
Branch to more detailed information on each entry in the
Send a mail to the appropriate employee informing him or her of
the action which needs to be taken
The entries in the log are
color-coded according to their significance for further processing
(for example, red for errors, white for information).
Some of the checks performed by the
system during the copying process are listed below:
If the system determines the item has already been cancelled,
the system does not include it in the copying process.
If the contract is cancelled at header level, the system
automatically determines the next possible cancellation date for
The contract item data valid at the
time the contract was cancelled at header level is used to
determine this date.
If the system determines that the contract end date at header
level lies before the item becomes valid, it records this in the
You need to reject or delete the item
The contract is cancelled at header level and, as a result, the
contract date is extended. If a contract end date has already been
entered at item level, the system determines whether this date
should be extended to match the new contract end date in the
header. The contract item date is only extended if it was identical
to the contract header end date before the contract was cancelled
at header level.
If the validity period for the item ends after the validity
period for the header, this is recorded in the action log.
You need to change the item validity
The system does not copy rules for determining contract start
and end dates.
After the contract header data has
been copied into the items during contract creation, the rules for
indirect date determination are deleted as the indirect date
determination function is not performed item level.
You can define your own checks to be
performed by the system during the copying process. The user exit
SAPLV45W_001 is provided for this purpose. For further information
on this user exit, see the documentation for the IMG activity 'User
Exits in Contract Processing'