In case you're operating multiple tenants and find it tedious to monitor incidents created in each tenant separately, please check out SAP note 2611988, which explains the two available options Central Helpdesk Scenario - CHD and Customer Competence Center Scenario - CCC.
One of the things that's a bit annoying in C4C coding is that you can't check if a business document is locked. Or so I thought. I just googled this issue again and came across this blog post.
Interesting enough, there is no proper guide out there that explains how to set up PHP debugging in Eclipse when you are working with a remote server. There are tons of guides, but they all assume that you're running PHP on your local machine. (Update: Actually, one of the first pages that come up on Google regarding PDT remote debugging is this manual page. However, this assumes you're running Zend and not XDebug.
So I had heard about the book "Clean ABAP" before but I didn't know that there's an online version.
I do read a lot about coding practices and so it was interesting to read "Clean ABAP" as well - and I do agree with most of what they say.
WSDLs for an IDOC can be downloaded in transaction WE62.
Simply enter the IDOC type and click Documentation --> Download XML Schema
If you get the error "Segment X is unknown in release Y" (EA 257), it generally means that the segment in question has not been released. If it's a custom IDOC you've built or generated yourself, you can do the release in BDFG or WE30.
Anybody ever looking for a list of standard CPI message headers and properties:
These properties can be used, for instance, in Groovy functions like this (where SAPMessageID is the property from above link):
Not sure if you're familiar with the saying "You don't need to know everything, you just need to know where to find it". I have a strong can-do attitude, so I regularly work in areas I haven't worked in before. This means starting at square one and having to google all the beginner questions about transactions and tables or even debugging.
In case you have to deal with text in ERP, the text function modules do not usually allow you to pass a string value. Rather, you have to pass a table that contains your string, split up into multiple lines. The data element of those texts is usually TDLINE and you have to provide some additional information in the table, like object type and format.
Doing this split was actually not very straight-forward because you need to take into account that your (flat) source string may contain line breaks.
In case you're faced with a technical error screen in C4C and are looking for the root cause:
Sometimes there's the need to add a help text to a custom or standard screen so the users know (or don't forget) how to use it.
There are two ways for doing this. For custom screens, the preferred way is to do this in the UI Designer.
Look for the property section "Text Information" - it is usually available for Views or Pane Containers - and set "Always show Explanation Area Text" to true. Then maintain the text under "Explanation Area Text".