Skip to Content
0

SAP HCI with eclipse. Problem deploying iflow.

Oct 26, 2016 at 09:06 AM

469

avatar image
Former Member

Hi!

I'm trying to extend a standard iflow in HCI - C4C integration, with some new Z fields.

I have downloaded the new WSDL from C4C and also from ERP with the new fields included.

I have changed the source and target elements in my mapping, and when i try to deploy my iflow i get the following error trace.

Wed Oct 26 08:09:18 UTC 2016 | Build and deploy task started for task id: 8a65df26-dd02-42db-ae42-6325c4ece0b7 
Wed Oct 26 08:09:18 UTC 2016 | Validator Logs :
Wed Oct 26 08:09:18 UTC 2016 | INFO : Source/Target check finished successfully <sourceElement;targetElement> Wed Oct 26 08:09:18 UTC 2016 | INFO : Mapping Completion Check is successful <mappingCompletion> Wed Oct 26 08:09:18 UTC 2016 | INFO : Source/Target check finished successfully <sourceElement;targetElement> Wed Oct 26 08:09:18 UTC 2016 | INFO : Mapping Completion Check is successful <mappingCompletion> Wed Oct 26 08:09:18 UTC 2016 | ERROR : Target element contentis not found <sourceElement;targetElement> Wed Oct 26 08:09:18 UTC 2016 | Generation started for com.sap.scenarios.erp2cod.customermaster.replicate project
Wed Oct 26 08:09:18 UTC 2016 | Generation and build failed for com.sap.scenarios.erp2cod.customermaster.replicate as validation of resource is failed
Wed Oct 26 08:09:18 UTC 2016 | Deploy skipped; project list is empty

Any clue where it may be the problem?

10 |10000 characters needed characters left characters exceeded
Former Member

Hi Cesar,

I am facing exactly same error.

However I have a slight different Scenario, where I am creating Sender WSDL in Eclipse and Importing Receiver WSDL. Both of these WSDL have different names as well structure and I am trying to map this based on some conditions and deployment is failing.

I cant import source and target wsdl with same name in resources.wsdl.

Can you please suggest.

Thanks Much.

Rashmi

0
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
avatar image
Former Member Oct 26, 2016 at 11:06 AM
-1

I have found the solution by myself in this note:

The same principle applies for importing the on-premise wsdl as well. Ensure that the source and target wsdl’s have the same name before importing into the wsdl folder.

:)

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Thanks, it worked

0
Former Member

Can you please share the note? I'm having exactly the same problem.

Thanks.

0