Content conversion file picked up no output
hi , i am trying a content conversion. the sender communication channel picked up the csv file after some eroors and correcting those errors. now i can't see the output xml file. i can't see any processed messages in sxmb_moni. when looked at all monitoring options, under cache monitoring the sender communication channel's direction is being showed as reciever. although in ID it shows as sender. thats the only odd thing i found in the scenario. how do u go on trouble shooting this problem. io know the file is picked up and in xi. can't monitor it from there. please advice me on how to trouble shoot content conversion.
thnak you
If u r done with communication channel monitoring and the status is success for ur CC...then do the Message Monitoring (Select Adapter Engine) and look for the Audit Log of ur message....You will see the entire message lifecycle in Adapter Engine...
Pravesh
Similar Messages
-
Problem in file content conversion, file 2 xml scenario
Hi,
Could some one help me in finding out the error in my file to xml scenario, please do consider the following things what I did for this scenario.
1.My sender file structure is flat file with , seperated 4 fields. On receiver end expecting xml file.
2.Did file content conversion at sender file adapter and given parameters as follows.
Document name : MT_FileInput
DocumentnameSpace : http://file/praveenworkshop
Recordset Name : DT_Record
Recordset Structure : DT_Row,*
KeyfieldType : String( default)
DT_Row.fieldnames : FirstName,LastName,City,PostCode
DT_Row.fieldSeparator : ,
DT_Row.processConfiguration: FromConfiguration
Dt_Row.endSeparator : 'nl'
3. I did check in Adapter Monitor that Both Sender and receiver adapter are showing green and It was showing 'Adapter is up and running: But no messages processed'
4. I did check the SXMB_MONI which was showing " Scheduled for Outbound processing"
5. In SXMB_MONI outbound processing payload was picking up the file and also inbound processing showing the same.
6. my source folder and destination folder are very simple c:/praveenfiles/input and c:/praveenfiles/output
files are source file praveen.txt and destination file praveenOP.xml
Please help me in finding out the error to see the output file in my output folder.Hi Praveen,
Hope these bloga are useful to you..
File content conversion sites
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Thanks,
Satya -
File content conversion (file to file)
Hi Guys,
Sender File
@! is the delimiter
LEVEL1@!227833338@!08710@!REPAIR@!20080101@!99990909@!0000212897@!0000000001000@!0000000500000@!R400@!A@!Assigned
LEVEL2@!227833338@!08710@!000099071608@!Blind@!20020115@!20020115@!R400@!1@!3@!20020430@!99990909@!SLC-@!VESSELLS@!A@!Assigned
LEVEL3@!227833338@!08710@!000099071608@!0010@!Blind@!20020115@!20020115@!20020430@!20020430@!10000414@!Assigned
LEVEL1@!4501065777@!00010@!SUPERHEAT@!20071206@!99990909@!0000219169@!00000001000@!0000002000000@!R020@!A@!Assigned
LEVEL2@!4501065777@!00010@!000009416742@!Alky@!20080107@!99990909@!R020@!E@!2@!20080101@!99990909@!LAT@!COKE@!A@!Assigned
LEVEL3@!4501065777@!00010@!000009416742@!0010@!v-895@!20080107@!99990909@!20080101@!99990909@!10001577@!Assigned
Sender Structure
<?xml version="1.0" encoding="UTF-8"?>
<ns0:CostObjects xmlns:ns0="http://*****************">
<LEVEL1>
<LevelID/>
<PONumber>35435454</PONumber>
<POLineNo>545</POLineNo>
<ShortText>AAAAAAA</ShortText>
<StDate>20080101</StDate>
<EndDate>20080101</EndDate>
<Vendor/>
<POValue/>
<ExpectedValue>4343</ExpectedValue>
<Plant/>
<Status>A</Status>
<OrderType>Assigned</OrderType>
</LEVEL1>
<LEVEL2>
<LevelID/>
<PONumber>35435454</PONumber>
<POLineNo>545</POLineNo>
<Level2ID>457899</Level2ID>
<Level2Desc>bbbbbbbbb</Level2Desc>
<L2StDate>20080101</L2StDate>
<L2EndDate>20080101</L2EndDate>
<L2Plant>y001</L2Plant>
<L2Priority>3</L2Priority>
<L2SAPStatus>a</L2SAPStatus>
<L2ActStDate>20080101</L2ActStDate>
<L2ActEndDate>20080101</L2ActEndDate>
<L2FuncLoc>LAR</L2FuncLoc>
<L2FuncDesc>LOS ANGLES</L2FuncDesc>
<L2Status>1</L2Status>
<L2OrderType>Assigned</L2OrderType>
</LEVEL2>
<LEVEL3>
<LevelID/>
<PONumber>35435454</PONumber>
<POLineNo>545</POLineNo>
<Level2ID>457899</Level2ID>
<Level3ID>10</Level3ID>
<Level3Desc>cccccccc</Level3Desc>
<L3StDate>20080101</L3StDate>
<L3EndDate>20080101</L3EndDate>
<L3ActStDate>20080101</L3ActStDate>
<L3ActEndDate>20080101</L3ActEndDate>
<L3WorkCenter>los</L3WorkCenter>
<L3OrderType>Assigned</L3OrderType>
</LEVEL3>
</ns0:CostObjects>
Receiver Structure
<?xml version="1.0" encoding="UTF-8"?>
<ns0:TCostObject xmlns:ns0="http://**************">
<LEVEL1>
<L1RecordIndicator><L1></L1RecordIndicator>
<L1ID>35435454545</L1ID>
<L1Desc>AAAAAAA</L1Desc>
<L1StartDate>20080101</L1StartDate>
<L1EndDate>20080101</L1EndDate>
<L1Hours>0</L1Hours>
<L1Costs>4343</L1Costs>
<L1Status>A</L1Status>
<L1OrderType>Assigned</L1OrderType>
</LEVEL1>
<LEVEL2>
<L2RecordIndicator><L2></L2RecordIndicator>
<L1ID>35435454545</L1ID>
<L2ID>457899</L2ID>
<L2Desc>bbbbbbbbb</L2Desc>
<L2StartDate>20080101</L2StartDate>
<L2EndDate>20080101</L2EndDate>
<L2Hours>0</L2Hours>
<L2Costs>0</L2Costs>
<L2OrderType>Assigned</L2OrderType>
<L2Plant>y001</L2Plant>
<L2Priority>3</L2Priority>
<L2SAPStatus>a</L2SAPStatus>
<L2CostObject/>
<L2CostObjectDesc/>
<L2ActStartDate>20080101</L2ActStartDate>
<L2ActEndDate>20080101</L2ActEndDate>
<L2AreaID>01</L2AreaID>
<L2FuncLoc>LAR</L2FuncLoc>
<L2FuncLocDesc>LOS ANGLES</L2FuncLocDesc>
<L2UnitName/>
<L2MaintCatCode/>
<L2MiscInfo1/>
<L2MiscInfo2/>
<L2SAPExempt/>
<L2ShortWorkOrderID/>
<L2Status_AorI>1</L2Status_AorI>
<L2LaborTaxFlag/>
<L2EquipTaxFlag/>
<L2MaintTaxFlag/>
</LEVEL2>
<LEVEL3>
<L3RecordIndicator><L3></L3RecordIndicator>
<L1ID>35435454545</L1ID>
<L2ID>457899</L2ID>
<L3ID>10</L3ID>
<L3Desc>cccccccc</L3Desc>
<L3PlanStartDate>20080101</L3PlanStartDate>
<L3PlanEndDate>20080101</L3PlanEndDate>
<L3ActStartDate>20080101</L3ActStartDate>
<L3ActEndDate>20080101</L3ActEndDate>
<L3OrderType>Assigned</L3OrderType>
<L3WorkCenter>los</L3WorkCenter>
<L3WorkAmtScheduled/>
<L3UnitofWork/>
<L3DurationScheduled/>
<L3UnitofDuration/>
<L3NoofEmp/>
</LEVEL3>
</ns0:TCostObject>
The receiver file look more or less the same as sender file but with delimiter @# and the fields are different
<L1>@#...........
<L2>@#..........
<L3>@#............
<L1>@#...........
<L2>@#..........
<L3>@#............
Sender file adapter content conversion:
LEVEL1.fieldNames LevelID,PONumber,POLineNo,ShortText,StDate,EndDate,Vendor,POValue,ExpectedValue,Plant,Status,OrderType
LEVEL1.fieldSeparator @!
LEVEL1.endSeparator 'nl'
LEVEL1.processFieldNames fromConfiguration
LEVEL1.keyFieldValue LEVEL1
LEVEL2.fieldNames LevelID,PONumber,POLineNo,Level2ID,Level2Desc,L2StDate,L2EndDate,L2Plant,L2Priority,L2SAPStatus,L2ActStDate,L2ActEndDate,L2FuncLoc,L2FuncDesc,L2Status,L2OrderType
LEVEL2.fieldSeparator @!
LEVEL2.endSeparator 'nl'
LEVEL2.processFieldNames fromConfiguration
LEVEL2.keyFieldValue LEVEL2
LEVEL3.fieldNames LevelID,PONumber,POLineNo,Level2ID,Level3ID,Level3Desc,L3StDate,L3EndDate,L3ActStDate,L3ActEndDate,L3WorkCenter,L3OrderType
LEVEL3.fieldSeparator @!
LEVEL3.endSeparator 'nl'
LEVEL3.processFieldNames fromConfiguration
LEVEL3.keyFieldValue LEVEL3
ignoreRecordsetName true
Receiver Adapter content conversion:
LEVEL1.fieldSeparator @#
LEVEL2.fieldSeparator @#
LEVEL3.fieldSeparator @#
LEVEL1.endSeparator 'nl'
LEVEL2.endSeparator 'nl'
LEVEL3.endSeparator 'nl'
The file is not being picked up.I am sure sender file adapter is correct as I have used this for (file to soap) and the scenario works file.I am not sure of receiver file adapter,do we have to use adavanced mode in receiver file adapter?Can you guys plz help me.Let me know if you have any questions
ThanksCan someone let me know what are the parameters to give in FCC receiver file adapter.
Thanks -
Content conversion File Query.
Hii,
I wanted a little help with the content conversion. I have mentioned the parameters bleow:
Document Name: MT_Vault_TRY
RecordStructure: DT_DLY_DEPOSIT1.*
Key Field Name: DT_DLY_DEPOSIT1.STRNBR
parameters:
DT_DLY_DEPOSIT1.fieldNames STRNBR,SLSDT,RECTYP,TNDRTYP,CURRTYPCD,AMT
DT_DLY_DEPOSIT1.fieldSeparator ','
DT_DLY_DEPOSIT1.endSeparator 'nl'
ignoreRecordSetName true
My Record structure looks like:
MT_VAULT_TRY
-DT_DLY_DEPOSIT1
--STRNBR
SLSDT
RECTYP
TNDRTYP
CURRTYPCD
AMT
The Problem faced here is that the flat file does not get picked from the ftp directory.When the same file is defined as an xml w.o the content conversion, it gets processed. Thus the commu.channel details are fine.
The transfer mode is 'text' and my file name is "dly.txt."
Could somebody please help me out on this one.
Thanks~HD,
If you have given your RecordStructure as DT_DLY_DEPOSIT1.* then it is wrong. You should give like this:
<b>DT_DLY_DEPOSIT1,*</b>
Also in Key field name you give as STRNBR
In the parameters you give like this:
ignoreRecordSetName true
DT_DLY_DEPOSIT1.fieldNames STRNBR,SLSDT,RECTYP,TNDRTYP,CURRTYPCD,AMT
DT_DLY_DEPOSIT1.fieldSeparator ,
DT_DLY_DEPOSIT1.endSeparator 'nl'
Also if you have only one strucutre DT_DLY_DEPOSIT1 then you dont need keyfield also.
So you have to change fieldseparator as <b>,</b> instead of <b>','</b> and <b>remove keyfield</b> and give a try.
---Satish -
Content Conversion - File Receiver
Hi All,
I am facing problems with File Content Conversion in the File Receiver adapter.
Input XML File
===============
<?xml version="1.0" encoding="utf-8"?>
<ns:mt_Hyp_FICO057 xmlns:ns="http://Astra-Honda.com/Prime/FICO/FICO057">
<userlist>
<user>
<Year>2005</Year>
<Month>Jan</Month>
<Version>0</Version>
<Value>64</Value>
<CostCenter>P13000</CostCenter>
</user>
<user>
<Year>2006</Year>
<Month>FEB</Month>
<Version>0</Version>
<Value>264</Value>
<CostCenter>P13000</CostCenter>
</user>
</userlist>
</ns:mt_Hyp_FICO057>
I have set the Content Conversion parameters in receiver File Adapter as
Recordset Structure = user
user.fieldSeparator = ;
but i am getting the output only as
Output
======
2005;2006
it is not considering other fields.
Can anyone help.
Thanks in Advance
Chemmanzhey
also specify the end separator
<b>user.endSeparator='nl'</b>
rgerads
jithesh -
File Content Conversion : File to File Scenario
hi all,
I have a Input file
It has the following structure:
<?xml version="1.0" encoding="utf-8"?>
<n0:rfc_proxy_message_type xmlns:n0="http://kpr.com/sample">
<Name>abhishek</Name>
<Age>10</Age>
</n0:rfc_proxy_message_type>
I use a File to File Scenario, with Sender and receiver FTP adapters.
I would like to convert this file at the recieveing end into a flat file as follows:
Name Age
abhishek 10
How can I do so?
Can anyone please help.
Thanks,
Best Regards
AbhishekHi,
Your Xml file should be like this.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee_MT xmlns:ns0="http://sap.com/demo">
<Recordset>
<item>
<Name>vinod</Name>
<Id>12</Id>
<Age>30</Age>
<***>male</***>
</item>
</Recordset>
</ns0:Employee_MT>
In the content conversion parameters mention the following
Document name: Student_MT
Document Namespace: enter your namespace
RecordsetName: Recordset
Recoedset Structure: item,*
item.endSeparator = 'nl'
item.fieldSeparator= ,
item.fieldnames= Name,Id,Age,***
Hope this helps you. -
Complex content conversion File sender
RecordSet
>Header 1..1
hfield1 1..1
hfield2 1..1
>/Header
>Detail 1..n
Dfield1 1..1
Dfield2 1..1
> SubDetail 1..1
SDfield3 1..n
> /SubDetail
>/Detail
/RecordSet
My CSV File would be like.
1hfield1,hfield2
2Dfield1,Dfield2
3SDfield3
3SDfield3
2Dfield1,Dfield2
3SDfield3
3SDfield3
2Dfield1,Dfield2
3SDfield3
3SDfield3
I have Used following Conversion Parameter. Please check.
Recordset Structure : Header,1,Detail,,SubDetail,
Keyfieldname : key
Keyfieldtype: string
Header.fieldSeparator ,
Header.endSeparator u2018nlu2019
Header.fieldNames hfield1,hfield2
Header.keyFieldValue 1
Header.keyFieldInStructure ignore
Detail.fieldSeparator ,
Detail.endSeparator u2018nlu2019
Detail.fieldNames Dfield1,Dfield2,SubDetail
Detail.keyFieldValue 2
Detail.keyFieldInStructure ignore
SubDetail.fieldSeparator ,
SubDetail.endSeparator u2018nlu2019
SubDetail.fieldNames SDfield3
SubDetail.keyFieldValue 3
SubDetail.keyFieldInStructure ignore
Suggest , where I am wrong. And what is missing ?????????????????
So . I am not able to convert this SubDetail by using content conversion.
Upto Level Header and Detail , it is coming in xml file . but not for SUBDETAIL and SDfield3.
Please check above config and suggest.
Is there any way to perform such content conversion without using KEVALUE 1, 2, 3 in CC parameters,Thanks Hareenkumar for reply ..
The Blog which you have Given , in that all the substructure is in same hierarchy , But in my case subDetail in Under Detail .
What Can i do for such structure ???.
And Thank You for pointing me on using key under fieldNames .But It was my mistake . I was forgot to write "key" under fieldNames , as i am already using Using it. -
Text Content Conversion - File Adapter - Creates empty file
I am running XI 7.0.
Mapping from abap proxy to file - text content conversion.
The process works, generates and sends file from mySAP, maps through XI, logs onto ftp site and creates file, but doesn't write any data into the file!
I am really confused as to what is happening!
This is taken from the communication channel!
Audit Log for Message: 5ccc2e46-c0f2-5349-e100-00000ddf240f
Time Stamp Status Description
2007-04-28 10:37:21 Success Message successfully received by messaging system. Profile: XI URL: http://host.fqdn:55000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-04-28 10:37:21 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-04-28 10:37:21 Success Message successfully put into the queue.
2007-04-28 10:37:21 Success The message was successfully retrieved from the receive queue.
2007-04-28 10:37:21 Success The message status set to DLNG.
2007-04-28 10:37:21 Success Delivering to channel: EPIW_FTP_Receiver_EmployeeRecords
2007-04-28 10:37:21 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2007-04-28 10:37:21 Success File adapter receiver channel EPIW_FTP_Receiver_EmployeeRecords: start processing: party " ", service "XE_DEV_3RD_EPIW_001"
2007-04-28 10:37:21 Success Connect to FTP server "ftp.ftp.ftp.ftp", directory "/ECS/Target"
2007-04-28 10:37:21 Success Write to FTP server "ftp.ftp.ftp.ftp", directory "/ECS/Target", file "epiw_output.dat"
2007-04-28 10:37:21 Success Transfer: "BIN" mode, size 125 bytes, character encoding -
2007-04-28 10:37:21 Success Start converting XML document content to plain text
2007-04-28 10:37:21 Success File processing complete
2007-04-28 10:37:21 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2007-04-28 10:37:21 Success The message status set to DLVD.
I can see the data before and after... Any ideas?hi,
this is starange:)
did you refresh FTP (F5) ?
maybe you're checking wrong ftp server? with the same folders ?
ups - I thought I doens't create any file...
as suggested check your mapping as per my blog:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
just use TCODe for abap mapping tests - SXI_MAPPING_TEST
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
Content Conversion File Reciever issue
Experts,
Please help me to identify FCC parameters for the following message structure
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_CreditResponse xmlns:ns1="http://predictivemetrics.com/xi/AccessLink_1.0">
<IDENTIFIER>0000003504</IDENTIFIER>
<ACCOUNT_NUM>0000003504</ACCOUNT_NUM>
<DATADATE>20000719013920</DATADATE>
<TOTBAL>2823.0000</TOTBAL>
<CURRENCY>USD</CURRENCY>
<RATING1>001</RATING1>
<CURRENT_CREDIT_LINE>1000000.0000</CURRENT_CREDIT_LINE>
</ns1:MT_CreditResponse>
Nikhilhi Nikhil,
There is an expectation about the document structure that needs to be content converted but your document fails to meet that structural requirement.
Please go through the link http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm which might give you an insight how things work with file content conversion.
Regards
joel -
Skip field in file content conversion (file adapter)
hy guys,
I have a log file and want to convert it into xml. that works fine.
the problem is: can I skip some fields that I do not need in the xml with file content conversion
the fields I want to skip are the same in every record of the log file.
thanks.Ralf,
You can only ignore lines in the begiining of the file using Document Offset option.
If you have the unwanted field in the end of the record and you are in SPS12 (PI 7.0), you can use the option additionalLasstFields in FCC parameters. have a look into the blog /people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
Easier, is to ignore those fields in mapping.
Also, you can try to remove those fields using a shell script which can be called from the File adapter.
Regards,
Jai Shankar -
File Content Conversion File-File scenario
Dear experts,
I have been tweaking with file to file scenario where a simple file goes in source as text delimited and comes out in target as xml.
I know ,i finally get my scenario get working with these settings :
ROOT.fieldSeparator ,
ROOT.fieldNames Store_Id,TRDT,SKU,SALE_RETURN,PRICE_OVERRIDE,PROMOTION_NUMBER,PROMO_DETAIL_ID,MIX_MATCH_NUMBER,DISCOUNT_ID,QUANTITY,EXTENDED_SELLING_PRICE,EXTENDED_ORIGINAL_PRICE,DIFFERENCE_PRICE
ROOT.fieldContentFormatting trim
ROOT.endSeparator 'nl'
ROOT.missingLastfields add
ROOT.processFieldNames fromConfiguration
ignoreRecordsetName true
Now my question is where i can find all properties that are probable in ROOT.Other thing is i kept on getting mapping related errors until i reached
at this stage of properties definition.But there was no tracking as of why i got that error.The error was :
Mapping "http://TPOCTEST_SFILE/OM_TPOCTEST" failed to execute: MappingException: Runtime Exception when executing application mapping program com/sap/xi/tf/_MM_TPOCTEST_; Details: com.sap.aii.mappingtool.tf7.IllegalInstanceException; Cannot create target element /ns0:MT_TPOCTEST_T/Record. 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
I resolved once i made settings on top but this was only a hit and trial.I dont know what actually was the reason behind this error.
I also used Test option of mapping and found things working.Hi Aditya,
That error indicates that when you were facing problems with your FCC the system did not generate XML that worked with the mapping that you have OM_TPOCTEST. The error is showing that you have a target node named Record which I'm guessing is set to 1...unbounded but your FCC did not generate XML that would map in such a manner that 1 or more nodes named Record would be created in your target message.
Regards,
Ryan Crosby -
Sender File Content Conversion with re-occuring record pairs
Hi,
Our FCC works fine with the following structure:
Header1: H1F1, H1F2, H1F3,... (1:1)
Header2: H2F1,H2F2,H2F3,..... (1:1)
Notes: NF1,NF2,NF3,.............(1:1)
Line1:L1F1,L1F2,L1F3,.............(1:N)
Line1:L1F1,L1F2,L1F3,
Line1:L1F1,L1F2,L1F3,
Line1:L1F1,L1F2,L1F3
Line2:L2F1,L2F2,L2F3,............(1:N)
Line2:L2F1,L2F2,L2F3,
Line2:L2F1,L2F2,L2F3,
Line2:L2F1,L2F2,L2F3,
But we have structure as below:
Header1: H1F1, H1F2, H1F3,... (1:1)
Header2: H2F1,H2F2,H2F3,..... (1:1)
Notes: NF1,NF2,NF3,.............(1:1)
Line1:L1F1,L1F2,L1F3,.............(1:N)
Line2:L2F1,L2F2,L2F3,.............(1:N)
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Lin1 and Line2 occur as multiple pairs making it as multiple line items. When we use content conversion parameters as below:
Header1.fieldNames H1F1,H1F2,H1F2,...
Header1.fieldFixedLengths 10,5,10,.....
Header1.keyFieldValue H1
Header1.keyFieldInStructure add
Header1.endSeparator 'nl'
Header1.lastFieldsOptional YES
and same for Header2, Notes, Line1, Line2
It picks up only first Header1, Header2, Notes, Line1 and Line2 in a recordset.
Does anyone have idea how could we do this content conversion? Any help would be appreciated.
Reagrds,
N@v!nHi Navin,
You can check the below links :-
Complex File Content Conversion - with random multiple occurrences
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
Complex content conversion File sender
These might be of some help.
Regards,
Rohit -
Can't get File content conversion to produce CSV file
Hi Guys
Have no problem at all getting XML file created via an RFC
Structure is something like this
From MONI message monitor inbound message payload
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <IP_CUSTOMER_HEADER>
<CUSTOMERID>100853</CUSTOMERID>
<COMPANY>Bram Van Tuyl Coldstore</COMPANY>
<SHORT_NAME>VAN TUYL</SHORT_NAME>
<STREET>Middelkampseweg 1</STREET>
etc
</IP_CUSTOMER_HEADER>
</rfc:Z_XI_005_RFC>
Receiver Grouping payload
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <IP_CUSTOMER_HEADER>
<CUSTOMERID>100853</CUSTOMERID>
<COMPANY>Bram Van Tuyl Coldstore</COMPANY>
<SHORT_NAME>VAN TUYL</SHORT_NAME>
etc.
With no conversion xml file is created on output directory
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_customer_header xmlns:ns1="http://avenue.com/xi/test"><customerid>100853</customerid><company>Bram Van Tuyl Coldstore</company>
etc
Now trying to use File content conversion with the simplest possible conversion -- just insert a colon after all the fields in the structure.
Following parameters
Adapter type FILE
receiver box checked
Message protocol File Content conversion
File access etc as before
Content conversion parameters
Recordset : IP_CUSTOMER_HEADER
(have also tried Z_XI 005_RFC)
Name
CUSTOMERID.fieldSeparator : (colon)
MONI shows message received by XI and processed correctly but NO outfile gets written to the target directory.
what am I doing wrong --it's probably something stupid.
The data into XI is a ONE RECORD structure -- not a table etc.
Cheers
jimboHi guys -- both solutions STILL not working
all I'm now getting is just a file with garbage in it
Payload is fine on XI system
Here's the payload
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <IP_CUSTOMER_HEADER>
- <item>
<CUSTOMERID>65013</CUSTOMERID>
<COMPANY>OY PANDA AB</COMPANY>
<SHORT_NAME>PANDA</SHORT_NAME>
<STREET>P.O.Box 3</STREET>
<STREET2 />
<STREET3 />
<STREET4 />
<POSTCODE>3331 GT</POSTCODE>
etc etc until end of customer mmaster details
</item>
</IP_CUSTOMER_HEADER>
</rfc:Z_XI_005_RFC>
Without conversion file is generated on target directory
Here's the XML output file sent to the directory
(for testing I only usec the ist 3 fields)
Not sure why <item> disappeared - maybe that has something to do with it ?
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:MT_customer_header xmlns:ns1="http://avenue.com/xi/test">
<CustomerId>65013</CustomerId>
<company>OY PANDA AB</company>
<shortname>PANDA</shortname>
</ns1:MT_customer_header>
RFC call from R3 system is fine (otherwise I wouldn't get the message into XI. Transaction SM58 as well on R3 shows no RFC errors
Converted file is just a blank with nl character at the end ??????
cheers
jimbo -
RCVR File Content Conversion - Remove empty Recordsets
Hello everyone,
Here's my scenario: IDOC > XI > TXT (File Content Conversion)
Here's how my output XML currently looks like:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:D001FILE_MT xmlns:ns0="http://www.pharmaindustries.com">
<Recordset/>
<Recordset>
<MATLCODE>00155581</MATLCODE>
<MATLNAME>ALCOHOL REFINED 96% V/V (BALAYAN)</MATLNAME>
</Recordset>
<Recordset>
<MATLCODE>00155581</MATLCODE>
<MATLNAME>ALCOHOL REFINED 96% V/V (BALAYAN)</MATLNAME>
</Recordset>
<Recordset/>
<Recordset>
<MATLCODE>20388853</MATLCODE>
<MATLNAME>POLYSORBATE 60 SD (TWEEN 60 SD)</MATLNAME>
</Recordset>
</ns0:D001FILE_MT>
Currently, the conversion settings in the receiver file adapter results into this:
BLANK
00155581 ALCOHOL REFINED 96% V/V (BALAYAN)
00155581 ALCOHOL REFINED 96% V/V (BALAYAN)
BLANK
20388853 POLYSORBATE 60 SD (TWEEN 60 SD)
I want to get remove the BLANK LINES from the text file so that it now resembles this:
00155581 ALCOHOL REFINED 96% V/V (BALAYAN)
00155581 ALCOHOL REFINED 96% V/V (BALAYAN)
20388853 POLYSORBATE 60 SD (TWEEN 60 SD)
Here are the conmmand parameters already existing in the "Content Conversion Parameters":
Recordset.fieldNames
Recordset.fieldFixedLengths
Recordset.endSeparator
Would anyone know which command I should add in this section so that empty "Recordsets" are removed from the text file?
Thanks in advance!
GlennHi,
as per my understanding, u have teo record sets
i.e Recordset(bold one which has no fileds)
Recordet(which has two fileds)
if you use Recordset.field Separator-- 'nl'
nothing but ignoring the first record set
for second record set(which is not bold)
provide FCC parameters which i have provided previously.
still u r facing problem, try with
ignore recordset name - true
Recordset.fieldContentFormatting - ignore
note: here you have two record set i.e<Recordset>(blod)
<Recordset>(not bold).
warm regards
mahesh. -
File Content conversion - IDOC to Fixed length File
Hi,
Scenario : SAP R/3(IDOC) -> XI -> Fixed Length file
IDOC is sending from SAP R/3, XI has to do the mapping and send a Fixed length File to /tmp in XI.
When I am using the message Protocol as "File" in the Receiver communication channel, XML file is writing to /tmp. When I am using "File Content Conversion" as a message protocol,Empty File is writing. Can anybody tell me why empty file is creating. Can we use File content Conversion in this scenario. Is there any additional parameter or settings required?
Receiver communication channel settings:
Message Protocol: File Content Conversion
File type : Binary
Recordstructure : MT_V_PER01
Name Value
MT_V_PER01.fieldFixedLengths 25,35
MT_V_PER01.fieldNames PERSNR,NAME
File Data Type : DT_V_PER01,
Message type : MT_V_PER01
IDOC type : WP_PER01.
Expecting your expert advice.
Thanks
vineeshHi Moorthy,
I am getting success messages in Audit log as below:
2006-09-29 12:08:53 Success Trying to put the message into the send queue.
2006-09-29 12:08:53 Success Message successfully put into the queue.
2006-09-29 12:08:53 Success The message was successfully retrieved from the send queue.
2006-09-29 12:08:53 Success The message status set to DLNG.
2006-09-29 12:08:53 Success The message was successfully transmitted to endpoint http://nslcxi08:8010/sap/xi/engine?type=entry using connection AFW.
2006-09-29 12:08:53 Success The message status set to DLVD.
2006-09-29 12:08:53 Success The message was successfully delivered.
I have checked the Payload maindocument,the IDOC structure contains data.
<?xml version="1.0" encoding="UTF-8" ?>
- <WP_PER01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<IDOCTYP>WP_PER01</IDOCTYP>
<MESTYP>WP_PER</MESTYP>
<STDMES>WP_PER</STDMES>
<SNDPOR>SAPLCD</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LCDCLNT210</SNDPRN>
<RCVPOR>LXDCLNT250</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>LXDCLNT250</RCVPRN>
</EDI_DC40>
- <E1WPP01 SEGMENT="1">
<PERSNR>0000100006</PERSNR>
- <E1WPP02 SEGMENT="1">
<NAME>Consumer</NAME>
</E1WPP02>
</E1WPP01>
</IDOC>
</WP_PER01>
Thanks
Vineesh
Maybe you are looking for
-
On Friday, October 28th I updated my iphoto 11 because I received notice from Apple that I should do so for better stability in the program. Today I opened I photo and found that although all my events show they are present and the number of photo
-
Desaturated colors in email compared to thumbnail enalrgements in iPhoto 6
The image that iPhoto creates when I use it to compose an email is desaturated compared to the image that iPhoto shows when enlarging the thumbnail. This wasn't the case with my earlier version of iPhoto (on my pismo), so it's not the photos. I use a
-
Having problems with family sharing invites
Hi, I send the invite to my son, which appears in his email, but when he views the invite it does not come up with the option to accept or decline and is therefore unable to join?
-
ITunes 7 only recognises the first CD I insert
I have just updated to the latest release of iTunes 7 and wish I hadn't. It is not clear that is is possible to revert to the prior version with which I never had problems. My issue is that when I insert the first CD in a session iTunes recognises it
-
hello, Using Labview 5.1 and Imaq boards PCI 1408 and PCI 1411 with driver version 2.2., I have the following problems: Under measurement and automatisation the devices are working fine with both boards (a colour camera on the 1411 and a spectrograph