We are facing the following issue when trying to re-distribute a central contract to ECC and we need some help or any information regarding this issue.
Please find below details on the issue:
We’ve created a new tab in the contract header tab. This tab is transmitted to ECC when the contract is distributed, so, when the contracted is updated by the user, the contract should be redistributed.
However, we are not able to re-distribute the contract, after the approval process, when the modification that triggered the new approval is done only on the new custom tab.
Analyzing the system behavior, we’ve found that the standard checks modifications only on selected standard fields, and does not check any other modification on the contract, which includes the custom tab information.
Below is the extract of the includes that performs the validation for standard fields.
INCLUDE LBBP_PDHGPF14 (line 356)
INCLUDE LBBP_PDHGPF14 (line 378)
We believe an enhancement point is needed to achieve our scenario where changes in custom information re-distributes the contract.
Has anyone faced the same scenario? If so, can you provide us details of the approach used?
Your CTR`s custom fields are created properly like metadata enhancing the standard structures right?
In BRF you control when and how the workflow is triggered to update the Contract. BADI name is Manage Process Restarts interface /SAPSRM/IF_EX_WF_PROC_RESTART and method VALIDATE_RESTART. At Filter Type use your BRF's Process Level Configuration name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.