Message Mapping

[Former Member]

HI,

I am doing a file to RFC scenario

Sender is File and receiver is a BAPI BAPI_FP_CHANGE

after i ocnfigure it is not raising any message. below is the data type and communication channel i defined . if anything wrong pls correct it. advices are highly appreciable.

BAPI Structure _ Target

-

---

BAPI_FP_CHANGE 1…1

PRODUCTCATEGORY 1…1

SECURITYNUMBER 1…1

CONDITIONS 0…1

Item 0… unbounded

Valid_from 0..1

Amount 0..1

Currency 0..1

Due_Date 0..1

File Source Structure

-

---

FWZZ_MasterRecExt 1..1

Header

Product Category 1..1

Security Number 1..1

Row 0..unbounded

EffFrom 1..1

Amount 1..1

Currency 1..1

DueDate 1..1

Freq 1..1

Communication Channel

-

---

Document Name : Message Interface

Document namespace: urn

Recordset Name:

Recordset Structure : Header,1,Row,*

Keyfield: KF

Row.fieldNames - KF,EffFrom,Amount,Curr,DueDate,Freq

Row.fieldSeparator – ,

Row.endSeparator – ‘nl’

Row.processConfiguration – FromConfiguration

Row.keyFieldValue – 10

Header.fieldNames - KF,SecurityID,ProdCat

Header.fieldSeparator – ,

Header.endSeparator – ‘nl’

Header.processConfiguration – FromConfiguration

Header.keyFieldValue – 20

[bhavesh_kantilal]

1. Check the inbound paylaod. Is it a valid payload ,ie. is the source payload after content conversion as expected?

2. Check the mapping with this payload . refer this blog to see how to test the mapping.

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

Does the mapping exectue fine? If yes, then check what the error in MONI is and let us know. If no, then check once again if the source is in acccordance with step 1 and if yes, then there is some issue in your mapping which needs to be looked into.

Regards

Bhavesh

[Former Member · Accepted solution]

HI Bhavesh,

when i use SXMB_MONI there are no messages displayed.

when i monitor communication channel following error appears

Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Header.fieldNames': no value found

in source i used header but in target ther eis no header node.

but i m mapping fields under source header (ProductCategory, SecurityNumber) to target structure.

is there any influence of it.

Regards,

jeff

[bhavesh_kantilal · Accepted solution]

Can you give us a smple source file?

Regards

Bhavesh

[Former Member]

HI,

This is due to content conversion parameters prob.

Try

Document Name : message Type name

Document namespace: urn

Recordset Name:

Recordset Structure : Header,1,Row,*

Row.fieldNames - EffFrom,Amount,Curr,DueDate,Freq

Row.fieldSeparator – ,

Row.endSeparator – ‘nl’

Row.processConfiguration – FromConfiguration

Header.fieldNames - SecurityID,ProdCat

Header.fieldSeparator – ,

Header.endSeparator – ‘nl’

Header.processConfiguration – FromConfiguration

Also see the below links to get an idea about FCC

/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC

/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC

/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC

/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario - FCC /people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp - FCC

/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC

/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter - EOIO

Regards

Chilla

[Former Member]

10,BLACKROCBR024,20

20,01.01.2007,10000000,USD, 31.01.2007

20,02.01.2007,10000000,USD, 31.01.2007

20,03.01.2007,10000000,USD, 31.01.2007

20,04.01.2007,10000000,USD, 31.01.2007

20,05.01.2007,10000000,USD, 31.01.2007

20,06.01.2007,10000000,USD, 31.01.2007

20,07.01.2007,10000000,USD, 31.01.2007

20,08.01.2007,10000000,USD, 31.01.2007

20,09.01.2007,10000000,USD, 31.01.2007

20,10.01.2007,10000000,USD, 31.01.2007

HI this is sample file structure...

i kept processinf mode as delete.. file is not deleting

and error is same

Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Header.fieldNames': no value found

[Former Member]

Hi,

The header contains three fields but you mentioned two field ??

10,BLACKROCBR024,20

Plz check the no of fields available??

10 is the KF , i mean key field?

if yes then add the KF to the Header filedNames and lengthe is 2 char not 20 or 10

add to row also .

Regards

Chilla

[Former Member]

Hi Bahvesh,

I did but still same error.

when i remove Content conversion file is getting deleted from directory.

if i use Content conversion this error occurs

[Former Member]

Hi,

I understand , but , in you config, plz check the Order offieldNames those are not matching to the fieldNames ? and lengths try to check and change and test again.

Even if yu are not sure see above example links

Regards

Chilla

[Former Member]

HI,

I removed Header,1 from Recordset Name.

file is pciking up and in payload i cant see header data.

I think somehting to do with Header node.

is source it is like

Header

ProdID

Sec Num

but in target we dont have any mapping to header node.

we ar emapping ProdiD and SecNum

Regards,

Jeff

[Former Member]

Hi,

Nop

Keep the Header first and Row next in parameters and

Did you checked the Order of fields,and the fieldlengths..

see above reply

Regards

Chilla

[Former Member]

HI,

Now in payload header aswell as details are appearing

but when i test the payload in message mapping following error appears.

any advice pls

01:55:48 Start of test

Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -

---

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)

01:55:48 End of test

[Former Member]

HI,

Get the source XML from SXMB_MONI and come back to message mapping , and goto test tab, test with that xml, sure you will get the exact mapping error.

Regards

Chilla

[Former Member]

jeff,

you have not copied propely from SXMB_MONI in to ur test tab. in frist row of ur XML Message in Mapping test tool column 8 you have some problem check if you have any speical chars or etc.

[Former Member]

I got this error is message mapping.

there are two fields in header productcategory and securitynumber

first it was showing this error for prod category then i remove the prodi cat field it is showing same error yto security number

any clue pls....

Cannot produce target element /ns1:BAPI_FP_CHANGE/SECURITYNUMBER. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

[prabhu_s2]

jeff

can u test ur mapping without the payload....enter the data mannually and see if the target nodes are framed.

[Former Member]

HI,

I tested it in Message mapping and interface mapping without payload.

it is a success.

i can see manually entered value in source to appear in target

Jeff

[Former Member]

can u enter all the test dat you have in file in mapping say for 5 records and excute and see itgives any error

[prabhu_s2]

if this is fine then there is a problem with ur payload...check for the payload strucutre with the the DT defined

[Former Member]

HI,

I tried multiple time i am getting same error

Cannot produce target element /ns1:BAPI_FP_CHANGE/PRODUCTCATEGORY. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

when i try manually it is working fine

[Former Member]

Jeff,

you paste our SXMB_MONI XML and ur Mapping XML in test tab which u used to test it.

[Former Member]

payload in SXMB_MONI

-

---

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

<ns:FWZZ_MasterRecExt xmlns:ns="urn:
mellon">

<Recordset>

<FileHeader>

<KF>10</KF>

<ProductCategory>20</ProductCategory>

<SecurityNumber>BLACKROCBR024</SecurityNumber>

</FileHeader>

<Row>

<KF>20</KF>

<EffFrom>01.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>02.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>03.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>04.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>05.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>06.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>07.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>08.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>09.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

<Row>

<KF>20</KF>

<EffFrom>10.01.2007</EffFrom>

<Amount>10000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

</Row>

</Recordset>

</ns:FWZZ_MasterRecExt>

Payload in message Mapping

-

---

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

<ns0:FWZZ_MasterRecExt xmlns:ns0="urn:
mellon">

<FileHeader>

<KF/>

<ProductCategory>20</ProductCategory>

<SecurityNumber>BLACKROCBR024</SecurityNumber>

</FileHeader>

<Row>

<KF/>

<EffFrom>01.01.2007</EffFrom>

<Amount>1000000</Amount>

<Curr>USD</Curr>

<DueDate>31.01.2007</DueDate>

<Freq/>

</Row>

</ns0:FWZZ_MasterRecExt>

[Former Member]

Hi,

Hey this is related to mapping problem , so kindly check the mapping .

Because can you please tell mapping source and target and mapping ..

And source and target messages occurrences

So product category occurrences problem.

Check carefully or give you mapping what you have done.

Regards

Chilla

[Former Member]

HI,

I cheked the occurence, it is same for source and destiantion

source is a file and target is a BAPI BAPI_FP_CHANGE

[Former Member]

Hi Jeff,

see your payloads are different......in SXMB_MONI, you have :

<ns:FWZZ_MasterRecExt xmlns:ns="urn:
mellon">

<Recordset>

<FileHeader>

But in msg mapping you have:

<ns0:FWZZ_MasterRecExt xmlns:ns0="urn:
mellon">

<FileHeader>

So in your Data type - recordset is missing.....edit your data type to have recordset in it and make your data type like the structure you are seeing in SXMB_MONI payload......then save and activate it....now in msg mapping again take source msg type.....then your latest source msg type will come in msg mapping.....then map the recordset node to target node......then save and acitvate your msg mapping.....then your this msg mapping problem may be solved....

Thanks,

Rajeev Gupta

[Former Member]

cool got here the solution to ur problem

add an enter in ur sender file adapter Content conversion

ignoreRecordsetName :true

then run the interface from frist . dont forgot to activate after you nake changes in file adapter

Sreeram Reddy

[Former Member]

Hi,

it would be more helpful if u can mention the full syntax as i havent used it before

is it FileHeader.ignoreRecordsetName

Jeff

[prabhu_s2]

if ur are not able to get the maaping executed from ur payload then u need to check this first. the fileds are different when checked ur payload and the source structure...just make them in sync and again test it. it shud work

Message was edited by:

Prabhu S

[Former Member]

it is <b>"ignoreRecordsetName"</b> nothing else is need this correct syntax

Sreeram Reddy

[Former Member]

Hi Jeff,

in ID in file sender comm channel, remove Recordset from Recordset Name.. ie in content conversion parameters, give Recordset Name : blank value

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

Hi sreeram

now there is no error

but i cna see a black arrow

saying recorded for outbound processing

wat does that mean

Jeff

[Former Member]

cool we sloved that problem . did you activate ur queues SXMB_ADm->ManageQueues->Selct the atcivate queue and acitvate it

[Former Member]

Hi Jeff,

saying recorded for outbound processing - it means your queue is deactivated.....

just go to queue......click it........you will see an entry in queue....click on Execute LUW button.....then your queue will be empty.....then refresh your msg in SXMB_MONI.....then you will see your msg being processed successfully in SXMB_MONI......

now from SXMB_ADM.....select your queue and activate it...

again run your scenario....now your complete scenario will run automatically......

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

HI,

Queue problem see the below link

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972...

Regards

Chilla

[Former Member]

Hi Sreeram,

I am testing it again.

Hope it works

Jeff

[Former Member]

yha we are here to help u out

[Former Member]

Hi Friends,

The message was successful from SXMB_MONI

i can see the succes flag followed by a green flag (recorded).

but in R3 it is not posted. any suggestions

jeff

[Former Member]

goto Smq1 and check the RFC adapter