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".
In the legacy Cloud Application Studio, the system connections are stored in the Windows Registry, path
\HKEY_CURRENT_USER\SOFTWARE\SAP\SAPCloudApplicationsStudio\<release>\DialogPage\SAP.Copernicus.CopernicusOptionPage
Key: SystemConnections.
Upgrading the legacy Studio was tedious enough, having to manually copy that entry to the registry path of the new version.
In the new (pilot) release, they are stored in a different path and format.
I guess it was the first time that I've translated an SAP report after releasing the code changes to the Q system. But much to my surprise, I wasn't prompted for a transport request when I maintained the translations.
There's a very good article that explains how to transport the translations using transaction SLXT, however what I was really after was how to add those texts to the transport request manually.
Quick note to self - SAP provides the following reports to manage segmentation and target groups:
Wow, this is one for the history books ...
So we had this weird issue during replication from ERP that C4C would throw an error
The BO 'CUSTOMER_QUOTE' supplied with the message does not match the BO of the current service call; within a service call, it is not allowed to raise messages for other BOs; application component 'LOD-LE-CQP
Nothing was showing in the Dump logs and the Incident Context was inconclusive.