on 07-05-2015 4:46 PM
Hello,
While LSMW upload of customer master , errors in the data file was fixed after 4 LSMW upload attempts. My mistake. On the fourth attempt all data got uploaded. However there are 4 duplicate master data for all records (except the one record which data was fixed by 3 attempts) . Tried to delete duplicate through obr2/ov52 Program dumps and show the following message.
method get_cvic_cust_to_bp1_line
assert i_account_group is not initial
select single * from cvic_cust_to_bp1
into r_cvic_cust_to_bp1
where account_group=i_account_group
endmethod
Any idea how to get out of this trouble. Thanks.
Kavita
This could be a number range related issue.Please double check the assigned range.The customer no: range was selected from the available ranges provided by the system or it was self assigned. If it was self assigned, then that could be the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sam,
There are 5 account groups and 5 different no: objects are assigned to those account groups and 5 different no; ranges was assigned to those no objects. The available no ranges from the system was ignored and i have selected my own no; ranges to match the account group. for eg
Account group-2200
No;object-22
No range-220000-225000
The no: ranges which i selected was accepted by the system. So there shouldn't be any problem. correct.
is it possible to upload the complete dump file?
Regards
Yan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Yan,
Here is the complete dump
Runtime Errors ASSERTION_FAILED
Date and Time 06.07.2015 06:38:37
Short text The ASSERT condition was violated.
What happened?
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.
Error analysis
The following checkpoint group was used: "No checkpoint group specified
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
Trigger Location of Runtime Error
Program CVI_KA_BP_CUSTOMER============CP
Include CVI_KA_BP_CUSTOMER============CM009
Row 3
Module type (METHOD)
Module Name GET_CVIC_CUST_TO_BP1_LINE
Source Code Extract
Line SourceCde
1 method get_cvic_cust_to_bp1_line.
2
>>>>> assert i_account_group is not initial.
4
5 select single * from cvic_cust_to_bp1
6 into r_cvic_cust_to_bp1
7 where account_group = i_account_group.
probably customizing errors, check it with the report from OSS note 1623677 - BP_CVI: Check report for checking CVI Customizing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.