Does Batch Input have problems after migration to new SAP release ?

[former_member207873]

Hello Experts,

We had a BI program which ran successfully through years. But after the change of SAP release this particular batch input is not working in backgroud. Does SAP release have an impact on batch inputs since change of screen and fields may also differ from the earlier release ?

B.R.

[former_member207873]

Hello Experts,

We had a BI program which ran successfully through years. But after the change of SAP release this particular batch input is not working in backgroud. Does SAP release have an impact on batch inputs since change of screen and fields may also differ from the earlier release ?

B.R.

[TammyPowlas]

I have experienced authorization errors with the BW batch user when updating releases; I recommend checking that

[former_member207873]

tammy.powlas3 . Thanks for your answer. I have an issue with same user locking the screen. Account ****** is currently blocked by user *****. But it worked perfectly before in the background. But now it is not working in the background . Any thoughts ?

[TammyPowlas]

Maybe perform an STAUTHTRACE on the background user to see if it experiences any authorization issues.

[former_member207873]

tammy.powlas3 All authorization checks are successfulll in STAUTHTRACE .

[TammyPowlas]

Okay, you can rule out authorizations. I will try to think on this some more, hopefully community members will have better suggestions than I do

[former_member207873]

May be is it because the screens , screen Sequences of input field changes in the new releas?. But will it have an impact on background running Batch inputs also ?

[Sandra_Rossi]

Yes. Any new release may have an impact on custom batch inputs. They all need to be verified.

[Sandra_Rossi]

What message number is it? (F2042, F5287, COPC013?)

[former_member207873]

sandra.rossi F2042