cancel
Showing results for 
Search instead for 
Did you mean: 

Message Split without BPM - Error

Former Member
0 Kudos

Hi,

I am creating a message split scenario without BPM as per weblog <a href="/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible Split without BPM</a>

I am able to receive message in XI but after that it shows error in Integration engine.

Error Category : MAPPING

Error Code : GENERIC

I am able to see the message in SXMB_MONI with error

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">GENERIC</SAP:Code>

<SAP:P1>No messages created from split mapping</SAP:P1>

Please advice.

Thanks,

Sri.

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

I too faced the sme problem and i resolved it like this.

My source message was

<?xml version="1.0" encoding="UTF-8"?>

<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">

<ns0:Message1>

<CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<Record>

<UNIQUE_ID>158487</UNIQUE_ID>

<PARTNER_NUMBER>123</PARTNER_NUMBER>

<FULL_NAME>Geetha J</FULL_NAME>

<LAST_NAME>J</LAST_NAME>

<FIRST_NAME>Geetha</FIRST_NAME>

<MDM_PARTNER_ID>456</MDM_PARTNER_ID>

<CREATE_DATE>25/08/2008</CREATE_DATE>

<CREATE_BY>Geetha</CREATE_BY>

<UPDATE_BY>Admin</UPDATE_BY>

<UPDATE_DATE>26/08/2008</UPDATE_DATE>

<SOURCE_SYS>SAP</SOURCE_SYS>

<DATA_STEWARD_EMAIL_ID></DATA_STEWARD_EMAIL_ID>

</Record>

</CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<Record>

<UNIQUE_ID>158487</UNIQUE_ID>

<PARTNER_NUMBER>123</PARTNER_NUMBER>

<FULL_NAME>Geetha J</FULL_NAME>

<LAST_NAME>J</LAST_NAME>

<FIRST_NAME>Geetha</FIRST_NAME>

<MDM_PARTNER_ID>456</MDM_PARTNER_ID>

<CREATE_DATE>25/08/2008</CREATE_DATE>

<CREATE_BY>Geetha</CREATE_BY>

<UPDATE_BY>Admin</UPDATE_BY>

<UPDATE_DATE>26/08/2008</UPDATE_DATE>

<SOURCE_SYS>SAP</SOURCE_SYS>

<DATA_STEWARD_EMAIL_ID></DATA_STEWARD_EMAIL_ID>

</Record>

</CM_EE_ACROSS_SYSTEM_NOTIFICATION>

</ns0:Message1>

</ns0:Messages>

AND U NEED TO CORRECT IT LIKE THIS AND THEN POST IT

<?xml version="1.0" encoding="UTF-8"?>

<CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<Record>

<UNIQUE_ID>158487</UNIQUE_ID>

<PARTNER_NUMBER>123</PARTNER_NUMBER>

<FULL_NAME>Geetha J</FULL_NAME>

<LAST_NAME>J</LAST_NAME>

<FIRST_NAME>Geetha</FIRST_NAME>

<MDM_PARTNER_ID>456</MDM_PARTNER_ID>

<CREATE_DATE>25/08/2008</CREATE_DATE>

<CREATE_BY>Geetha</CREATE_BY>

<UPDATE_BY>Admin</UPDATE_BY>

<UPDATE_DATE>26/08/2008</UPDATE_DATE>

<SOURCE_SYS>SAP</SOURCE_SYS>

<DATA_STEWARD_EMAIL_ID></DATA_STEWARD_EMAIL_ID>

</Record>

</CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<CM_EE_ACROSS_SYSTEM_NOTIFICATION>

<Record>

<UNIQUE_ID>158487</UNIQUE_ID>

<PARTNER_NUMBER>123</PARTNER_NUMBER>

<FULL_NAME>Geetha J</FULL_NAME>

<LAST_NAME>J</LAST_NAME>

<FIRST_NAME>Geetha</FIRST_NAME>

<MDM_PARTNER_ID>456</MDM_PARTNER_ID>

<CREATE_DATE>25/08/2008</CREATE_DATE>

<CREATE_BY>Geetha</CREATE_BY>

<UPDATE_BY>Admin</UPDATE_BY>

<UPDATE_DATE>26/08/2008</UPDATE_DATE>

<SOURCE_SYS>SAP</SOURCE_SYS>

<DATA_STEWARD_EMAIL_ID></DATA_STEWARD_EMAIL_ID>

</Record>

</CM_EE_ACROSS_SYSTEM_NOTIFICATION>

THAT IS REMOVE LAST THREE LINES..

Former Member
0 Kudos

Hi Sri,

Look the trace in sxmb_moni.

Let us know what exception has ocurred. That might be more helpful to solve your problem.

If you are doing message split, Then is sub-groupIds created in sxmb_moni?

Then take care of the occurences of the messages in the target side.

regards,

P.Venkat

Former Member
0 Kudos

Hi Venkat,

I am not able to see sub-groupid in sxmb_moni.

Please see below the contents from sxmb_moni trace.

============================

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = QN7</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 67F58830CE9E11DA91CD00111120E6DB</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0002</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0002</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = QN7</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO6___0000</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T" />

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = QN7</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="T">Mapping-Object-Id:29EB87F0231C357A8336DDEBD574EEAB</Trace>

<Trace level="1" type="T">Mapping-SWCV:0CF1E1E0C5FC11DABCB9E4A50A07012B</Trace>

<Trace level="1" type="T">Mapping-Step:1</Trace>

<Trace level="1" type="T">Mapping-Type:JAVA</Trace>

<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_filesplit_without_bpm_</Trace>

<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

</SAP:Trace>

Thanks,

Sri.

Former Member
0 Kudos

Hi Sri,

I don't know whether you still have the problem, but I also stepped across it and found the solution here:

You have to take out the <Messages> tags...

Hope this helps!

Cheers,

Dennis

Former Member
0 Kudos

Hi,

This scenario you are trying can be done using <b>CONDITIONAL RECEIVER DETERMINATION and RB SPLIT</b>

To do this without using a BPM.

1. In your message mapping, make sure that the source message has an occurence of 1 and destination message occurence is made to unbounded (n).

2. in interface mapping, make sure source interface has an aoccurence of 1 and destination interface has an occurence of N or unbounded.

Now, there are a few essential steps in your configuration,

1. In the receiver determination, specify the 2 receiver systems, one for your IDOC and the other for your MAIL.

2. Now, you will have a condition window. Just type the condition on the basis of which the receiver has to be determined for the mail and the idoc business system. Just remember that the condition can be specified only for the source message.

3. In the Interface Determination, you have an option called RB CLASSIC and RB SPLIT. To do a 1:N split, you will have to do a RB_SPLIT.

You can even use xslt mapping to split source message type into multiple target messages types.for more information on the same check this link:

http://help.sap.com/saphelp_erp2005/helpdata/en/83/2200cb50d345c793336d9a1683163e/frameset.htm

Thus, your solution can be devised without a BPM also.

Regards,

Abhy

Former Member
0 Kudos

Hi Sri,

1. Please can you check if the Message mapping is working fine in IR in the test phase.

2. Hope have not done message split for IDoc destination.

Can you describe you error more from the trace. This error is only shows that there is some problem with mapping.

Regards

Vijaya

Former Member
0 Kudos

Hi,

1. Message mapping is working fine in IR(Test).

2. This is a file to file scenario.

3. Both the message specified in target side and are visible in interface.

4. Checked the radio button in Interface Mapping, But in my case it shows two radio button with label 'Standard' and 'Extended'. I have selected 'Extended'. I am in SP15.

Thanks,

Sri.

Shabarish_Nair
Active Contributor
Shabarish_Nair
Active Contributor
0 Kudos

Can you confirm if you have specified both the messages at your target side in mapping and also in your Inter. mapping check if both the mess. interfaces are visible at target.

Also you need to specify RB_SPLIT in your Inter. determination.