cancel
Showing results for 
Search instead for 
Did you mean: 

last fields missing in the target file

Former Member
0 Kudos

Hi friends,

I have done IDOC to file scenario where in, the 8-10 fields are not visible in the target file, but ALL the fields are SEEN IN THE PAYLOAD.There are 22 fillers in the scenario which have varying lenght form 6 - 11chars and more over there are two fields of lenght 150 and 255,and the field of lenght 255 is not the mandatory field to be sent to the target file.my requirement is send the mandatory fields to output file.with this lenght specified in the File Content Conversion the last mandatory fields are not visible in the target file.

can you all please suggest any way where all the mandatory fields are displayed.

thanks in advance,

meghna.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

what is the error you are getting in communication channel monitoring for this receiver file adapter?

Thanx

Aamir

Former Member
0 Kudos

Hi Aamir,

here we are not using any field separator.so we need fixed length.for that we use d fieldNames.

when we are trying to reduce some of the field length we are able to see some more fields.based on that we got conclusion that the file has some fixed size to display a particular row.

Is it so that the file has a size character for each row in a text file?if so what is the maximum length and where we can able to change or increase the number of character size?

please give me your comments.

thanks,

meghna.

Former Member
0 Kudos

>>here we are not using any field separator.so we need fixed length.for that we use d fieldNames.

well that does not makes sense to me:),both the parameters serve two different purpose,one does not compliments other.

i use only .fieldFixedLengths on receiver side and all the fields are displayed correctly.

>>Is it so that the file has a size character for each row in a text file?

i don't think so,if the length is more than what can fit into one row then it will come in next row by itself.

Thanx

Aamir

Former Member
0 Kudos

>>8-10 fields are not visible in the target file, but ALL the fields are SEEN IN THE PAYLOAD

clearly means there is some issue with your FCC parameters.

can you please post your target message type(along with occurence) as well as your FCC parameters

Thanx

Aamir

Former Member
0 Kudos

Hi Aamir,

These are the FCC parameters and the same fields is defined as target message type with occurence as 1.

1.Recordset.endSeparator 'nl'

2.Recordset.fieldNames Action_Code,PO_Number,PO_date,filler1,Owner_code,filler2,Due_date,filler3,Vendor_number,Vendor_owner_code,filler4,Buyer_code,Consignee,Dest_code,Freight_mgmt,Cases,filler5,Weight,filler6,Pallets,filler7,Cube,filler8,Points,filler9,Cost,filler10,Bracket_price,filler11,Est_allow,filler12,HOT,Streamline,Pickup_date,filler13,Comments,Recv_cases,Recv_weight,Recv_pallets,filler14,Recv_cube,filler15,Recv_cost,filler16,Recv_BP,filler17,Recv_actual_allow,filler18,Buyer_allow,filler19,Arrive_date,Arrive_time,filler20,Sched_date,Sched_time,filler21,Actual_date,Actual_time,filler22,Super_Vendor,Pallet_type,Commodity_code,Trailer_type,Backhaul,Buyer_comments,Temp_type,Recv_date,Recv_time

3.Recordset.fieldFixedLengths 1,15,10,10,2,1,10,10,15,1,2,15,15,15,3,7,9,7,9,7,9,7,9,7,9,10,6,10,6,10,6,1,1,10,10,150,16,16,5,11,8,9,10,6,10,6,10,6,10,6,10,8,2,10,8,2,10,8,2,15,3,15,3,1,255,3,10,8

thanks,

meghna.

Former Member
0 Kudos

isn't your receiver FCC?

in that case i don't see a reason why you have given <i>Recordset.fieldNames</i>

.fieldNames are used in sender FCC,not on the receiver side

also which field you are not getting on the receiver flat file?what is the occurence of that field in your receiver structure?

Thanx

Aamir

Former Member
0 Kudos

Hi Aamir,

These are the fields which are not getting populated and the occurance is defined as 1 for all the fields.

filler17,Recv_actual_allow,filler18,Buyer_allow,filler19,Arrive_date,Arrive_time,filler20,Sched_date,Sched_time,filler21,Actual_date,Actual_time,filler22,Super_Vendor,Pallet_type,Commodity_code,Trailer_type,Backhaul,Buyer_comments,Temp_type,Recv_date,Recv_time

thanks,

meghna.