Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Customer or SAP issues

Former Member

‎2007 May 22 5:20 PM

0 Likes
1,137

How would I differentiate among the issues about customer enhancements, SAP modifications, standard features - features that are applied to a specific industry sectors, and something that SAP should provide a solution? What analysis should be performed to determine if an issue should be resolved by me or SAP?

How would I differentiate among the issues about customer enhancements, SAP modifications, standard features - features that are applied to a specific industry sectors, and something that SAP should provide a solution? What analysis should be performed to determine if an issue should be resolved by me or SAP?

Reply
7 REPLIES 7
Read only

Former Member

‎2007 May 22 5:28 PM

0 Likes
1,116

Hi,

While you are doing the analysis of the coding, you can also send Note(s) to SAP for suggestion and solution (perhaps).

Also try to search OSS Note(s) which related to the issue you are facing. Perhaps there are some patches available for you to download and solve the issue.

Regards,

Ferry Lianto

Read only

Former Member

‎2007 May 22 5:33 PM

0 Likes
1,116

If the issue is coming out due to some logic in standard code, then SAP is responsible for fixing it. But if you are using a SAP delivered function module in your Z program and it is not working as you expected but working in standard SAP code, then it is your issue.

If certain functionality or features are missing in your current version, that is not an issue as such. It may be something that SAP may add in the next versions. That kind of things you cannot take it to SAP for fixing unless you are the lab animal on whom they are testing their product first and want to take your feedback to improve the product.

So the analysis you will do is to ask yourself these questions.

1. Is it something happening in SAP standard code?

2. Is it happening only to me?

3. Is it happening only in one environment not in others?

4. What version am I on and what is the latest version available?

5. What patch level I am on and what is the latest patch level available?

6. Is there an OSS note that fits my issue?

7. Can I replicate the issue again and again?

Bottom line is, if you cannot show that it is happening in standard code and consistantly, then it is your issue.

Read only

Former Member
In response to Former Member

‎2007 May 22 6:04 PM

0 Likes
1,116

<i>That kind of things you cannot take it to SAP for fixing unless you are the lab animal on whom they are testing their product first and want to take your feedback to improve the product.</i>

Interesting analogy... This will take me awhile to see what you're referring to.

My issue has to do with the industry sector that I am working on that requires certain way of doing the reporting side. The object is a standard SAP provided object, but the way it is being used for reporting is not the norm for this specific industry sector.

The repsonse is that it is a customer problem and not something SAP should provide.

I am trying to dig into this to see how shallow this issue is...

Thanks anyway

Read only

Former Member
In response to Former Member

‎2007 May 22 7:25 PM

0 Likes
1,116

The point I wanted to convey by that analogy was that sometimes, particularly with industry solutions, there will always be some pilot or early adaptors chosen by SAP to try out a new product. While these pilot customers try out the product, their feedback is taken and the product is fine tuned before it is made available to public (what SAP refers to as GA or Generally Available). So I was saying unless you are one of those pilot customer, your requirement may not be treated as something that needs to be addressed ASAP.

Also, reporting (apart from mandatory and regulatory types) is a low priority compared to business functionality. But again, if 10 big customers in that industry say that it is required and missing, then they may include it in a different release. It will not be addressed through a message sent to SAP in service net.

Read only

Former Member
In response to Former Member

‎2007 May 22 7:36 PM

0 Likes
1,116

Sounds fair...But I am working with Business Intelligent reporting and it is the most crucial part of this requirement. The end users only see the frontend of the reporting side and expecting the format layout of the report to be a specific way.

I wanted to get perspectives from the technical forum. Should I entertain you with this link...

Thanks

Read only

Former Member
In response to Former Member

‎2007 May 22 7:51 PM

0 Likes
1,116

Interesting argument but sorry it is consulting issue (sounds like SAP response to your OSS message).

That is why when numbers are stored in character fields, SAP stores them with leading zeros so that you will not encounter this issue with sorting. See if that may be the issue. Some reports provide you with sorting related configuration settings but may be not for this one.

Read only

Former Member
In response to Former Member

‎2007 May 22 8:49 PM

0 Likes
1,116

Hi,

I think that, if you don't belong to the previous mentioned big 10, best/only? way to get SAP to include it in the standard is to have your local SAP user group, like ASUG, DSAG (don't know if there is an italian) request for it. If it's a problem for the other members within your specific industry you may be successful. But it's still a long and winding road...

To be pragmatic, as you wrote in the other thread, you know how to fix it - do both! Fix it and talk to your SAP user group, may be you'll see it within several SP's from now

Peter

--

Points always appreciated