All articles

As C4C development systems (that are in development) use a different namespace than non-dev systems, simply copying or transporting an iflow from DEV to TEST (or PROD) will lose all extension field mappings.

You can either adjust your iflows manually. This involves uploading the test system WSDL to the iflow and re-mapping all extension fields from the DEV namespace to the test/production namespace, which is not recommended as it is very error-prone.

However, you can also do this automatically with a one-line change as follows:

The C4C object identifier webservice (CommunicationServicesManagementQueryObjectIdentifierMappingIn/Query Object Identifier Mappings) only works if you supply the correct Remote and Local ID type code. Thankfully, the documentation (linked above) provides a list of type codes for commonly used objects, however, the employee business object is missing.

To make it short, the type codes for employee are:

I recently needed to modify the body of an HTTP response in a BSP page. Previously, the request was simply returning a status 403. This was done using request->set_status. So I assumed that I simply had to do request->set_cdata to set the HTML body corresponding to the status. But this was incorrect. 

The correct approach was to use me->write (me referring to the BSP page in the DO_REQUEST method). I know too little about BSP to explain why the request and the BSP page are two different objects.

I came across this interesting article by Paul Hardy yesterday and in one of his screenshots he's using a pretty cool header/signature for his methods.

Surveys in C4C are a bit complicated. Here's a quick overview of the data structure (based on Ticket/ServiceRequest).

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.