Skip to Content
author's profile photo Former Member
0
Former Member

Date field selection criteria changed after upgrade to BW EHP1

Posted on May 05, 2011 at 10:41 AM 11 Views

Hi,

We are using BW 7.0 and recently upgraded to 7.01 EHP1. After this, we have an issue in the Bex report.

We have a field End date in the Bex report. Before the upgrade the date field was in the form of a parameter. But after the upgrade, the date field changed to select options. We are populating the date from customer exit for variables via the exit EXIT_SAPLRRS0_001. This is happening only in the Dev and test systems, becasuse both these systems are upgraded. Production system is not yet upgraded.

For eg. before upgrade the date field had the input in the form of a parameter.

i.e. End date = <system date>

After upgrade it changed to select options

i.e. End date [] <system date> To <12/31/9999>

Any help on this would be appreciated.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 05, 2011 at 11:09 AM
    1

    Hi Priyadharshini,

    Check with the properties of Variable, Details tab> Variable Represent is single value or not.

    Hope this helps you.

    Regards,

    Rajeswari.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 05, 2011 at 11:09 AM
    0

    Hi Priyadharshini,

    Check with the properties of Variable, Details tab> Variable Represent is single value or not.

    Hope this helps you.

    Regards,

    Rajeswari.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      May 06, 2011 at 04:28 AM

      Hi,

      If the data is ok in production leave it as it is..

      else you make changes in dev with the selection option as ' = ' and while importing to production you need to check mark the option overwrite.

      Some one might have changed in dev after moving to production that Request might not transported again.

      Regards,

      Rajeswari.

    Comment on This Answer

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.