Skip to main content

CPI

C4C/CPI: Automatically adjust mapping for DEV namespace

Submitted by Stefan Barsuhn on

As C4C development systems (that are in development) use a different namespace than non-dev systems, one challenge is to adjust the CPI mapping of extension fields when moving to test or production.

When you are finished with development and unit testing in your dev environment, naturally, all CPI iflow mappings that involve extension fields would be mapped to the DEV namespace. If you simply move this iflow/mapping to your test system, it won't work, as the DEV namespace is not known in the test/production environment.

Tags

SAP: Download IDOC WSDL in SAP ERP

Submitted by Stefan Barsuhn on

WSDLs for an IDOC can be downloaded in transaction WE62.

Simply enter the IDOC type and click Documentation --> Download XML Schema

image 41

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.

Tags

SAP: CPI Default Message Headers and Properties

Submitted by Stefan Barsuhn on

Anybody ever looking for a list of standard CPI message headers and properties:

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/headers-and-exchange-properties-provided-by-integration-framework

These properties can be used, for instance, in Groovy functions like this (where SAPMessageID is the property from above link):

Tags