cancel
Showing results for 
Search instead for 
Did you mean: 

BPM mapping fault

Former Member
0 Kudos

Hi experts! I've faced with a problem with building my process. The error ocuries when I try to map different complex types. I created test process to simplify a type of problem. Compile error was like this:

[BpemTask] Compiling process 'main_pool' ...

  [BpemTask]  "BPM.bp.00006" BC-BMT-BPM-SRV com.sap.tc.glx.BpemTask  execute() - Exception during process compilation, compilerType: BPMN2CSVCOMPILERcaused by com.sap.glx.paradigmInterface.bpmn.compiler.BPMNCompilerException: Mapping compilation failed!

  [BpemTask] [ERROR] Incompatible expression type.

  [BpemTask] Expected:ParentType

  [BpemTask] Found:ProcessInstanceAttributes

  [BpemTask]     at com.sap.glx.paradigmInterface.bpmn.compiler.helpers.MappingHelper.compileMapping(MappingHelper.java:74)

  [BpemTask]     at com.sap.glx.paradigmInterface.bpmn.compiler.helpers.MappingHelper.compile(MappingHelper.java:51)

  [BpemTask]     at com.sap.glx.paradigmInterface.bpmn.compiler.rules.MappingActivityRule.compile(MappingActivityRule.java:36)

  [BpemTask]     at com.sap.glx.paradigmInterface.bpmn.compiler.rules.MappingActivityRule.compile(MappingActivityRule.java:23)

  [BpemTask]     at com.sap.glx.paradigmInterface.bpmn.compiler.stage.CompileArtifactsStage.compile(CompileArtifactsStage.java:110)

Mapping screen:0

During design there are no any erros icon.

Moreover, If I copy this broken Development Component to a new Software Component of other local Development Configuration  with standart SCA's

it will be compiled well!

So what the matter? My project was loaded from NWDI, The all dependens components there - are of version 7.31.

I use NWDS 7.31 SP05 PAT0001

Possibly there is an incompartible componet, but I don't know how to check it

Thanks in advance

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi all!

The issue was fixed. The problem was not in NWDI configuration.

I found NWDS: SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP04 PAT0003. I imported there my project and problem was gone! Real mystery issue

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Viktor, In that case search the NWDI space - there have been discussions about similar issues when NWDI and BPM (and other CAF applications) are used together there so you may find something there that helps.

Rgds,

Jocelyn

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Viktor,

Actually I can see the mapping itself is showing an error icon in your screenshot - that's why there's a red cross on the line between source and target.

Generally the easiest way to work out what's wrong is to double-click on the target to open up the expression editor. Then rest your cursor on the error icon in the top left hand corner of the expression pane and see what it says.  Proabably just a datatyping error.

I wonder if you meant to use an n of m mapping instead of a deep copy?

Or perhaps the data type definition is different in your different compilations? That can happen if the XSD defining the data types has changed.

Try this blog for some more help...

Regards,

Jocelyn

Former Member
0 Kudos

Jocelyn, thank you for reply. I'm really sorry about duplicated posts, it was my fault.

I've read you article before and its a realy excelent guide

But in my case there is no error in screenshot, it was just an active line

This is just a test example of the error, the real project has other xsd-s where nodes have occurence of [0..infinity] and simple or deep copy does not fit there, different types

Of course, checked xsd schemes, reimported them. But problem remains

And as I've posted beyond:

If I copy this broken Development Component to a new Software Component of other local Development Configuration  with standart SCA's

it will be built well

So, I did many things, and discover that with local standart software components it works, I tried to replace some components from NWDI but it works.

Unfortunately, it does not work in the development infrastructure imported from NWDI with whole required SCA's and my own component, which was built successful and loaded before few months ago