on 09-30-2015 7:54 AM
Hi All,
our scenario is Sender->SFTP to Receiver->SFTP(file).
How to use the functionality of File Content Conversion in sftp adapter?
But is a option called file content conversion in sftp ,PO 7.4
When i use FCC,in communication Channel it showing Message sent to Module Processor
but i used Standard MessageTransformBean for CC ,
i am getting the problem Sender Side while Seeing Payload Structure is Different form Sender Structure
Sender Structure
<FileHeader>
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
</FileHeader>
Payload Structure
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
Here is my Module configuration Parameters
any Clues on this Issue
Thanks in Advance
Umesh
Hi all,
Thanks For your Quick Reply's,
Now My Sender SFTP FCC working Without Module Configuration.
In PO 7.4 Single Stack For FCC in SFTP Adapter ,it has Default FCC option in Message Protocol and it is working after up gradation of SP-3 to SP -4
Best Regards
Umesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All
any Clues on this Issue ?
Regards
Umesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Umesh,
If I had to take a guess based on your module configuration I would remove either the use of recordsetName & recordsetStructure or the structureTitle. I would bet that the inclusion of both of those is what is resulting in the duplication of the "FileHeader" tags.
Regards,
Ryan Crosby
Hi Umesh,
Upon re-reading your initial post I misunderstood thinking you were looking for:
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
Now I realize you are looking for this structure:
<FileHeader>
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
</FileHeader>
I'm not sure how you would achieved that with FCC in the standard file adapter as the recordset name is layered two times in the payload. There really is no value addition in data meaning to have it layered twice like that so if it were possible I would be looking to remove that extra layer from the definition of the sender structure. I don't know what restraints you have with achieving your requirement so you may be stuck doing some sort of XSL transform or Java Mapping to get the second FileHeader layer into the payload.
Regards,
Ryan Crosby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tinu
In My interface Content Conversion Type is SimplePlain2XML
Thanks
Hi Umesh,
For your Record Structure, you have to use the ConversionType - "StructPlain2XML".
SimplePlain2XML is used for the simple record set structure.
Find the below link for the FCC parameters,
Also incase you are using the ConversionType "StructPlain2XML", KeyField is mandatory.
can you provide some sample data?
Regards,
Tinu
Hi Umesh,
For your input data, you can give the contentType -"SimplePlain2XML", but you have change the Record Structure as below,
<?xml version="1.0" encoding="utf-8" ?>
- <ns:<MessageType> xmlns:ns="<Namespace>">
<FileHeader>
<S_No></S_No>
<CODE></CODE>
<STATUS></STATUS>
</FileHeader>
</ns:<MessageType> >
But if you don't want to change the structure, you have to give the ContentType- "StructPlain2XML", and for this contentType- KeyField is mandatory.
Regards,
Tinu
Hi Tinu
your are not getting my point this is my input Strucute
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_WAVE_AP1 xmlns:ns0="http://C3_IDD1147_AP_INVOICE_AP(WAVE).com">
<FileHeader>
<FileHeader>
<S_No/>
<EXCISE_INVOICE_NUMBER/>
<LINE_ID/>
<EXCISE_INVOICE_DATE/>
<GL_DATE/>
<EXCHANGE_DATE/>
<SHIPMENT_NUM/>
<SEGMENT1/>
<PO_NUM/>
<RECEIPT_NUM/>
<VENDOR_CODE/>
<CREATION_DATE/>
<DESCRIPTION/>
<REQUISITION_NUM/>
<INVOICE_CURRENCY_CODE/>
<INVOICE_AMOUNT/>
<SEGMENT3/>
<SEGMENT2/>
<WBS_CODE/>
<QUANTITY_INVOICED/>
<UOM_CODE/>
<TAX_TYPE/>
<TAX_RATE/>
<INVOICE_AMOUNT2/>
<EXCHANGE_RATE/>
<PAY_CURR_INVOICE_AMOUNT/>
<ORG_ID/>
<ITEM_DESCRIPTION/>
<ITEM_CODE/>
</FileHeader>
</FileHeader>
</ns0:MT_WAVE_AP1>
and after module configuration input payload structure like this
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_WAVE_AP1 xmlns:ns0="http://C3_IDD1147_AP_INVOICE_AP(WAVE).com">
<FileHeader>
<FileHeader>
<S_No/>
<EXCISE_INVOICE_NUMBER/>
<LINE_ID/>
<EXCISE_INVOICE_DATE/>
<GL_DATE/>
<EXCHANGE_DATE/>
<SHIPMENT_NUM/>
<SEGMENT1/>
<PO_NUM/>
<RECEIPT_NUM/>
<VENDOR_CODE/>
<CREATION_DATE/>
<DESCRIPTION/>
<REQUISITION_NUM/>
<INVOICE_CURRENCY_CODE/>
<INVOICE_AMOUNT/>
<SEGMENT3/>
<SEGMENT2/>
<WBS_CODE/>
<QUANTITY_INVOICED/>
<UOM_CODE/>
<TAX_TYPE/>
<TAX_RATE/>
<INVOICE_AMOUNT2/>
<EXCHANGE_RATE/>
<PAY_CURR_INVOICE_AMOUNT/>
<ORG_ID/>
<ITEM_DESCRIPTION/>
<ITEM_CODE/>
</FileHeader>
</FileHeader>
</ns0:MT_WAVE_AP1>
Hi,
Please make sure OSS note 2144272 is applied.
Kind regards,
Dimitri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.