on 03-09-2010 3:56 PM
Hi All,
i am doing FCC conversion in FTP receiver adapter. i need to produce text file converting below structure in given format with field seperating by comma.
Messages
.......Message1
............MT_Employee
..................NODE1
........................Field1
........................Field2
........................Field3
........................Field4
..................NODE2
........................FieldA
........................FieldB
........................FieldC
........................FieldD
..................NODE3
........................FieldX
........................FieldY
........................FieldZ
........................FieldP
File flat structure required is.
Field1,Field2,Field3,Field4
FieldA,FieldB,FieldC,FieldD
FieldX,FieldY,FieldZ,FieldP
i am doing as below but get gets error in RWB in channel monitoring saying 'ns0Messages' unknown structure found in document.
NODE1.fieldseperator = ,
NODE2.fieldseperator = ,
NODE3.fieldseperator = ,
PLease suggest.
Regards
Swapnil
Hi Swapnil,
I think you are dong multimapping. Just make sure you have all the messages ie., there is no empty message. Did you give in your recordset structure as NODE1,NODE2,NODE3. Also you have given as NODE1.fieldseperator which is wrong. The s should be capital S. So change like this:
NODE1.fieldSeparator and do the same for rest of them also.
Regards,
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Satish,
Below is the paylod from sxmb_moni need to convert into file. since paylod is larger so i had given first two nodes of it.
PAYLOAD
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:MT_EMPLOYEE xmlns:ns1="http://xxxxx.co.uk/xxxx/xxxxxx/EmployeeMaster">
<EMPLOYEE_00>
<Employee_number>00100276</Employee_number>
<Transaction_date/>
<Transaction_time/>
</EMPLOYEE_00>
<PERDET_10>
<Employee_number>00100276</Employee_number>
<Transaction_date/>
Recordset structure: EMPLOYEE_00,PERDET_10
FCC parameters:
EMPLOYEE_00,fieldSeparator = ,
PERDET_10,fieldSeparator = ,
Swapnil
Edited by: Swapnil Bhalerao on Mar 9, 2010 5:35 PM
Hi Swapnil,
I see you have given as EMPLOYEE_00,fieldSeparator and PERDET_10,fieldSeparator. I see a comma between the fieldname and fieldSeparator instead it should be dot. Is it a typo? or correct it and test once again. Are you using any variable subsitutioon etc in your receiver communication channel?
Regards,
---Satish
Hi Satish,
Sorry i dont understand what you say by variable substitution. the above one was typo error and it is a dot.
while testing scenario mapping gets executed successfully but fails in communication channel during converision. below is the error messages i get.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Messages' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Messages' found in document', probably configuration error in file adapter (XML parser error)'
Regards
Swapnil.
Hi Swapnil,
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Messages' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Messages' found in document', probably configuration error in file adapter (XML parser error)'
This error occurs only when it is unable to generate the target structure properly
Test in message mapping, then test it in interface mapping.
Best Regards,
Lakshmi
Hi Satish,
Below is my target structure
Messages
.......Message1
............MT_Employee
..................EMPLOYEE_00
........................RECORD_TYPE
........................TRANSACTION_ID
........................EMP_NO
........................NEW_EMP
..................PERDET_10
........................EMP_NO
........................SURNAME
........................FORENAME
........................TITLE
..................PAYGROUP
........................PAYID
........................EFFECTIVE_DATE
........................PAY_ELEMENT
........................FIXED_TEMP
Payload after message mapping.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ZHRMD_A07>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>400</MANDT>
<DOCNUM>0000000000496217</DOCNUM>
<DOCREL>700</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ZHRMD_A07</IDOCTYP>
<MESTYP>ZHRMD_NGA_DELTA</MESTYP>
<STDMES>ZHRMD_</STDMES>
<SNDPOR>SAPERT</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>ERTCLNT400</SNDPRN>
<RCVPOR>XI3PORT</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>XITCLNT400</RCVPRN>
<CREDAT>20100309</CREDAT>
<CRETIM>102756</CRETIM>
<SERIAL>20100308110924</SERIAL>
</EDI_DC40>
<E1PLOGI SEGMENT="1">
<PLVAR>01</PLVAR>
<OTYPE>P</OTYPE>
<OBJID>00100276</OBJID>
<OPERA>U</OPERA>
<Z1EMPDATA SEGMENT="1">
<BUILD>RIVERSID</BUILD>
<STRAS>Riverside House</STRAS>
<STRS2>2A Southwark Bridge Road</STRS2>
<ORT01>London</ORT01>
<PSTLZ>SE1 9HA</PSTLZ>
<ORGTX>Human Resources</ORGTX>
<ATX>OPS</ATX>
<LTEXT>Professional Development</LTEXT>
<MGR_PERNR>00100015</MGR_PERNR>
<MGR_NACHN>Campbell</MGR_NACHN>
<MGR_RUFNM>Janet</MGR_RUFNM>
<PLSTX>Head of Professional Development</PLSTX>
<LMSROLE>M</LMSROLE>
<MGR_LOGON>JANET.CAMPBELL</MGR_LOGON>
<ZZFTE> 0.70000</ZZFTE>
<EMP_STATUS>CURRENT</EMP_STATUS>
<EHRO_ENABLED>Y</EHRO_ENABLED>
<COLLEAGUE_OR_NOT>Y</COLLEAGUE_OR_NOT>
<MASSN>Z4</MASSN>
<VORNA>Janet</VORNA>
<ANRED>2</ANRED>
<GBDAT>19621119</GBDAT>
<ABKRS>Z5</ABKRS>
<BEGDA>20080401</BEGDA>
<MASSG>10</MASSG>
<BEGDA_60>20080401</BEGDA_60>
<BEGDA_70>00000000</BEGDA_70>
<TEILK>X</TEILK>
</Z1EMPDATA>
<E1PITYP SEGMENT="1">
<PLVAR>01</PLVAR>
<OTYPE>P</OTYPE>
<OBJID>00100276</OBJID>
<INFTY>0000</INFTY>
<BEGDA>20080401</BEGDA>
<ENDDA>99991231</ENDDA>
<E1P0000 SEGMENT="1">
<PERNR>00100276</PERNR>
<INFTY>0000</INFTY>
<ENDDA>99991231</ENDDA>
<BEGDA>20080401</BEGDA>
<SEQNR>000</SEQNR>
<AEDTM>20100308</AEDTM>
<UNAME>SBHALERAO</UNAME>
<MASSN>Z4</MASSN>
<MASSG>10</MASSG>
<STAT2>3</STAT2>
</E1P0000>
</E1PITYP>
<E1PITYP SEGMENT="1">
<PLVAR>01</PLVAR>
<OTYPE>P</OTYPE>
<OBJID>00100276</OBJID>
<INFTY>0001</INFTY>
<BEGDA>20080401</BEGDA>
<ENDDA>99991231</ENDDA>
<E1P0001 SEGMENT="1">
<PERNR>00100276</PERNR>
<INFTY>0001</INFTY>
<ENDDA>99991231</ENDDA>
<BEGDA>20080401</BEGDA>
<SEQNR>000</SEQNR>
<AEDTM>20100308</AEDTM>
<UNAME>SBHALERAO</UNAME>
<BUKRS>1000</BUKRS>
<WERKS>OF01</WERKS>
<PERSG>1</PERSG>
<PERSK>01</PERSK>
<VDSK1>OF01</VDSK1>
<BTRTL>0002</BTRTL>
<ABKRS>Z5</ABKRS>
<ANSVH>Z9</ANSVH>
<KOSTL>0000003030</KOSTL>
<ORGEH>00000200</ORGEH>
<PLANS>00002151</PLANS>
<STELL>00000000</STELL>
<SNAME>ADDISON KEELEY</SNAME>
<ENAME>Keeley Addison</ENAME>
<OTYPE>S</OTYPE>
<SBMOD>OF01</SBMOD>
<KOKRS>OFCO</KOKRS>
</E1P0001>
</E1PITYP>
<E1PITYP SEGMENT="1">
<PLVAR>01</PLVAR>
<OTYPE>P</OTYPE>
<OBJID>00100276</OBJID>
<INFTY>0002</INFTY>
<BEGDA>19721024</BEGDA>
<ENDDA>99991231</ENDDA>
<LONG_INFTY>X</LONG_INFTY>
<E1P0002 SEGMENT="1">
<PERNR>00100276</PERNR>
<INFTY>0002</INFTY>
<ENDDA>99991231</ENDDA>
<BEGDA>19721024</BEGDA>
<SEQNR>000</SEQNR>
<AEDTM>20100308</AEDTM>
<UNAME>SBHALERAO</UNAME>
<NACHN>Addison</NACHN>
<NAME2>Lawlor</NAME2>
<VORNA>Keeley</VORNA>
<RUFNM>Keeley</RUFNM>
<KNZNM>00</KNZNM>
<ANRED>2</ANRED>
<GESCH>2</GESCH>
<GBDAT>19721024</GBDAT>
<SPRSL>E</SPRSL>
<FAMST>C</FAMST>
<FAMDT>00000000</FAMDT>
<ANZKD>0</ANZKD>
<PERMO>08</PERMO>
<PERID>NY830453B</PERID>
<GBPAS>00000000</GBPAS>
<GBJHR>1972</GBJHR>
<GBMON>10</GBMON>
<GBTAG>24</GBTAG>
<NCHMC>ADDISON</NCHMC>
<VNAMC>KEELEY</VNAMC>
<SPRSL_ISO>EN</SPRSL_ISO>
<NACHN_40>Addison</NACHN_40>
<NAME2_40>Lawlor</NAME2_40>
<VORNA_40>Keeley</VORNA_40>
<RUFNM_40>Keeley</RUFNM_40>
<E1Q0002 SEGMENT="1">
<PERNR>00100276</PERNR>
<INFTY>0002</INFTY>
<ENDDA>99991231</ENDDA>
<BEGDA>19721024</BEGDA>
<SEQNR>000</SEQNR>
</E1Q0002>
</E1P0002>
</E1PITYP>
</E1PLOGI>
</IDOC>
</ZHRMD_A07>
</ns0:Message1>
</ns0:Messages>
FCC parameters as requested.
Processing parameters:
File construct mode: Add time stamp
write mode: directly
empty message handling: write empty file.
max occurency: 1
file type: text
file encoding: is blank
FCC parameters
Recordset structure: EMPLOYEE_00,PERDET_10,PAYGROUP
EMPLOYEE_00.fieldSeparator:,
PERDET_10.fieldSeparator:,
PAYGROUP.fieldSeparator:,
varaible substitution: not used
adapter specifc message attributes: not used.
i have given error message in above reply.
please suggest
Swapnil
Hi Lakshmi,
Fortunately i tested my mesaage maping and its generating output as desired without any issues. Also it doesnt error out in message mapping but gets error during file conversion.
Can you please suggest how FCC patameters should be.? and dunno why its picking up ns0:Messages for conversion as this is occuring as a standard format after producing target structure.
Swapnil
Hi,
I donno how exactly u have configured....
Let me remind u.. in multimapping also, when u create the target structure,
The ns0:Messages and ns1:Message1 tags should not be present at all.
I donno how u r getting these tags also.
Yes in mapping u can see these tags, but when in it comes to adapter engine... these tags are automaticaly removed.
ONly u will have from the message type name.
My suggestion will be please cross check once ur design and configuration once more...
Let us know if still any prblm
Babu
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.