2008 May 02 2:09 PM
Hi All,
I am updating the Partner Functions for the Customers using FM 'SD_CUSTOMER_MAINTAIN_ALL' and passing the partner functions and numbers to the XKNVP structure.
while running the program in am getting the short dump as ASSERTION_FAILED.
Detailed Description:
In the running application program, the ASSERT statement recognized a situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort" for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
The Dump is occuring in the method 'get_cvic_cust_to_bp1_line'.
We have searched for a relevant SAP note but could not find any.
can any one please help to solve this issue?
Helpful answer will surely be rewarded.
Thanks in Advance,
Asif Ali Khan
Hi All,
I am updating the Partner Functions for the Customers using FM 'SD_CUSTOMER_MAINTAIN_ALL' and passing the partner functions and numbers to the XKNVP structure.
while running the program in am getting the short dump as ASSERTION_FAILED.
Detailed Description:
In the running application program, the ASSERT statement recognized a situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort" for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
The Dump is occuring in the method 'get_cvic_cust_to_bp1_line'.
We have searched for a relevant SAP note but could not find any.
can any one please help to solve this issue?
Helpful answer will surely be rewarded.
Thanks in Advance,
Asif Ali Khan
2008 May 02 2:53 PM
When you are (absolutely) sure you are using this function module in the correct way, only then opening a message for SAP is liable. However, most of the times this happens because not all (or all) parameters are not provided for the FM to work properly, or what ever reason that may be.
It might be helpful to determine the checkpoint group and have a look at the log in transaction SAAB. This might give you a clue as to where the problems lies.
2008 May 02 3:13 PM
Hi,
I do not know how to give Check point group.. can u please help me regarding that?
Thanks
Asif Ali Khan
2008 May 02 3:25 PM
I'm afraid I can't help you with that. Try and find it via F4 search help in transaction SAAB, or have a look at the dump message. Maybe it refers to checkpoint group....???
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |