Wednesday, September 24, 2014

Using a customized IDOC in SAP Cloud for Customer HCI



Last week my colleague Nick van de Hulsbeek wrote a blog about the integration of SAP Cloud for Customer with SAP ECC. This week's blog will continue on Hana Cloud Integration (HCI), focusing on customising the default integration package.

A lot of customers have extra fields in there ECC environment, these fields are not available by default to SAP Cloud for Customer. To make these fields available you have to create an extension to the outgoing IDOC and make them available in HCI to map the fields to Cloud for Customer.

HCI provides a standard packages for integration with SAP ECC. SAP provides a lot of information about customising the C4C side, but doesn’t provide good documentation about customising the ECC side. In this blog I will explain how easy it is to implement this.

Wednesday, September 17, 2014

Keep your original SAP ECC Account_ID for existing ECC Accounts in SAP Cloud for Customer.

The default integration setup between SAP Cloud for Customer and SAP ECC will result in that all existing ECC Customers receive a new (internal) Account_ID in Cloud for Customer. Also the result of following this SAP Best Practise integration guide: C4C PI Integration Guide

Is this really the standard SAP approach? Yes, unfortunately this is the case.

But, with this small enhancement you are able to keep the original ECC Account_ID in SAP Cloud for Customer.

Business Benefit: This will really help your Sales Reps in accepting your new Cloud For Customer system if they were using SAP ECC before. And knowing some accounts by ID :-)
 

Wednesday, September 10, 2014

Documenting your Custom Code

There is always some discussion on how far you want to go in documenting your custom abap code.
For me it makes no sense to spend much time in actually copying code to MS Word documents. Documentation should explain the overall working of an enhancement. The code itself should contain enough explanation for fellow programmers to understand the process. But it still can be very usefull to have your code easily downloaded and back-upped for multiple reasons.
I found the following program online from a friend of mine and found it very useful, so i did not want to keep it from all our followers.



Wednesday, September 3, 2014

Customer dunning level not up to date...?

Today's blog is about a little piece of information on the customer master, the dunning information.


In standard SAP, whenever a customer is dunned for an open item, the dunning level is not only maintained on the open item, but also on the customer.

A typical scenario would be that when the customer does not pay his bills within say 30 days, the customer receives a dunning letter, raising the open item to level 1. Then after another say 20 days, the customer receives a reminder, raising to level 2 etc.

As said, the indicator for level 1 and level 2 are both maintained on the open item and on the customer.
But... when the customer pays, standard SAP will clear the open item, but the indicator on customer level will not be deleted, nor will it be redetermined.