‎2005 Feb 27 6:49 AM
Hi,
I use the batch input for transaction CKR1.
After the execution, I get a warning message, which stops the process until pressing the ENTER key.
The problem is that the enter is not recorded and when running the batch input SUBRC is not 0.
I tried adding the ENTER before the CALL TRANSACTION
(perform bdc_field using 'BDC_OKCODE' '=ENTR'.), but it does not change the result.
How can I overcome the problem?
Thanks,
Hagit.
‎2005 Feb 27 8:13 AM
Hi Hagit,
it's just a report. Give
submit SAPRCKR1 with P_BUKRS eq '0001' sign 'I' ...a chance.
(Or try out to 'enter' with '/00' instead of '=ENTR'.)
Regards,
Christian
‎2005 Mar 02 11:56 AM
Hi Christian,
Thank's for the reply.
I have tried both your suggestions but both off them did not overcome the problem.
I have also tried finding the message and change its type to another type then warning so it won't appear but I couldn't find it.
Do you have any more ideas for a solution?
Thank's,
Hagit.
‎2005 Mar 02 1:13 PM
Hi Hagit!
Which problems did you have using submit? Did you try to run your program in background?
If background execution brings just an entry in job-log, you might live with this.
If you want to spend some more time, have a look at BAPIs
BAPI_COSTESTIMATE_DELETE and BAPI_COSTESTIMATE_DELETE_MULTI.
Regards,
Christian
‎2005 Mar 02 1:20 PM
‎2005 Mar 03 1:07 PM
Hi Rich,
You are right, the BDC does not stop but it fails.
It gets subrc 1001.
Hagit.
‎2005 Mar 03 1:16 PM
‎2005 Mar 03 1:45 PM
‎2005 Mar 13 6:58 AM
Hi Rich,
Sorry for the delay.
I'm using mode 'N', but I have used mode 'A' in order to see what the problem is and when I've reached the warning message the process stopped until I have pressed the 'Enter', that is why I have figured out that this is the reason for the BDC's failure.
Hagit.
‎2005 Mar 13 5:08 PM
Could the warning be something like "dynpro not found?"
If yes - then it would work in forground but not in background. But then it would not explain why submit or the bapi would have the same problem - could you provide some info?
Christian
‎2005 Mar 15 12:02 PM
No, the warning is not "dynpro not found".
The warning is " Deleting current standard cost estimates can cause inconsistencies", Message no. CK 669.
I guess it's a matter of customization to hide it, I just couldn't find where.
Thanks,
Hagit.
‎2021 May 25 11:02 AM
I am also facing the same issue please please update if your problem is solved or not