cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC to PROXY

mf_haq
Active Participant
0 Kudos

Hi Experts,

we are using PI 7.1, the secnarion is from JDBC to PROXY.

I am getting all the values which are in DB to XI (MONI) as well as in Communication channel .

The data flow from DB to XI is fine, but i am getting below error (Mapping exception, value misssing)

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

<SAP:P1>com/sap/xi/tf/_MM_SOTaggingDeTagging_TO_SOTagging~</SAP:P1>

<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>

<SAP:P3>on: Cannot create target element /ns1:MT_SO_TagDet</SAP:P3>

<SAP:P4>ag. Values missing in queue context. Target XSD r~</SAP:P4>

<SAP:AdditionalText />

<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_SOTaggingDeTagging_TO_SOTagging; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:MT_SO_TagDetag. Values missing in queue context. Target XSD r</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

Thanks & Regards,

MFH

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member185881
Active Participant
0 Kudos

Hi MF

This is a Mapping Issue only as told by others.

  • check ur source structure occurences and target structure occurences.

  • Do testing through your test tab first.

  • check from your DB all the fields and fields values are coming correct.

  • Do check in your target structure also for there data length and type of data they can accept ---- for example- might be from the source side char value is coming but your target structue field type is of integer

--- check the length also wheather the data is coming of same length which is acceptable by target field.

  • Have you tested your proxy is it working fine???

  • have you declared all the fields correctly in your proxy?

I just given my assumptions of error, you please check at your end.

Regards

Dheeraj Kumar

Former Member
0 Kudos

Hi Haq,

So it means that for ur mapping the input XML payload is not sufficing.

U copy the payload from the moni and check in the Message Mapping-->Test.

SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>

<SAP:P3>on: Cannot create target element /ns1:MT_SO_TagDet</SAP:P3>

<SAP:P4>ag. Values missing in queue context. Target XSD r~</SAP:P4>

It means... the mapping to the message type u have did in mapping is not correct.

Please check once this..

If still prblm arises.. do post the prblm...

Babu

mf_haq
Active Participant
0 Kudos

Hi Babu,

source target

resultset resultset

-


row -


sotag

-


column1 -


column1

the above structure i am using in mapping, does it require to change anything in defined mapping structure.

while testing in Message Mapping I am getting below error.(XML taken from MONI View source)

Cannot create target element /ns1:MT_SO_TagDetag. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD.

In this case what i need to do to slove this please suggest me.

With Regards,

MFH

Former Member
0 Kudos

Hi,

Please check ur source payload once.

When u r testing in message mapping-->Test.

The source structure tree view should be green.

1. First check this(Green on tree view of source).

2.If green, then the problem is with the mapping.

Now check with the default payload u get in testing(not from moni)..

Let us know the result..

Babu

MichalKrawczyk
Active Contributor
0 Kudos

hi,

this is a just a mapping error - you need to correct your mapping

check out my blog on how to test correctly :

/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

Regards,

Michal Krawczyk

mf_haq
Active Participant
0 Kudos

Hi,

Michal/Babu thanks FYR.

Its not Mapping a Error, its related to sender CC, when testing with MONI's payload the XML structure should be like below shown.

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

<ns0:MT_SOTagDetag xmlns:ns0="urn://jspl.it/xi/LEGACY/MES/IF0002_SOTaggingDetagging/100">

<row>

<MATERIAL_CODE>PL_ST02_16_040X1490_3500</MATERIAL_CODE>

<MATERIAL_NO>1111112DC0</MATERIAL_NO>

<ACTUAL_TONNAGE>27</ACTUAL_TONNAGE>

<TRANSACTION_TYPE>413</TRANSACTION_TYPE>

<SAP_LOC>DEBA</SAP_LOC>

<CURRENT_ORDER_NO>80002610</CURRENT_ORDER_NO>

<CURRENT_ORDER_ITEM_NO>10</CURRENT_ORDER_ITEM_NO>

<ORDER_NO>80002611</ORDER_NO>

<ORDER_ITEM_NO>10</ORDER_ITEM_NO>

</row>

</ns0:MT_SOTagDetag>

Regards,

MFH

Former Member
0 Kudos

Hi Haq,

For sure the error is a mapping error because the payload what you are receiving is not mapping correctly to your target.

Now the payload what you are expected is not coming because you also have given recordset (as per your reply). Now there is a problem in source payload. So check the source payload structure and the communication cahnnel parameters first.

Regards,

---Satish

Former Member
0 Kudos

Hi,

Its not Mapping a Error, its related to sender CC, when testing with MONI's payload the XML structure should be like below shown.

Ok fine.. if the payload should be like the one u have given..... what exactly u r getting from adapter to the PI(Monitor)...

Post the FCC u r using and the source file structure...

So that others here can give u a solution.

Babu

Former Member
0 Kudos

hi Haq ,

Issue deems to be with Mapping part only. Your receiver structure is not forming up properly .

Reasons could be :

1. Check the Occurrences at the sender data type .

2. Check the mapping once again..copy the payload from Moni and test it in IR message mapping tool .

Regards ,