BDC problem

[Former Member]

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.

[Former Member]

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

[christian_wohlfahrt]

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

[Former Member]

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.

[christian_wohlfahrt]

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

[RichHeilman]

In BDC, warning and information messages are ignored. I don't believe that the BDC is stopping because of a warning message. There has to be something else which is not correct.

Regards,

Rich Heilman

[Former Member]

Hi Rich,

You are right, the BDC does not stop but it fails.

It gets subrc 1001.

Hagit.

[RichHeilman]

Yea....I think that you are getting the 1001 for other reasons. Warning and info messages are not suppose to stop/fail a BDC.

Regards,

Rich Heilman

[RichHeilman]

What mode are you running the transaction in....

CALL TRANSACTION 'CKR1' mode <What is the value here>.

Regards,

Rich Heilman

[Former Member]

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.

[ChristianFi]

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

[Former Member]

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.

[former_member701505]

I am also facing the same issue please please update if your problem is solved or not