on 04-29-2009 12:06 PM
Hi there
I have a scenario that produces different output structures. All of the comes from the same MM and goes to the same output file which is a fixed length flat file. Lets say I have 3 types of output:
Type1:
Name
Surname
Type2
Name
Surname
Address
Type3
Name
Surname
Address
Phone
How can I design my content conversion that it would handle these 3 types? each type has got a different number of fields. Like I mentioned this must be fixed length.
Thanks,
Jan
Hi,
I think you can have look at below and try to implement in your scenario.
Use the following parameters if you want to influence the behavior of the conversion routine for inbound structures that deviate from the configuration.
● NameA.missingLastfields
If the inbound structure has less fields than specified in the configuration then the XML outbound structure is created as follows:
○ ignore
Outbound structure only contains the fields in the inbound structure
Warm Regards,
Chandra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
@Chandra
Hi,
I think you can have look at below and try to implement in your scenario.
Use the following parameters if you want to influence the behavior of the conversion routine for inbound structures that deviate from the configuration.
u25CF NameA.missingLastfields
If the inbound structure has less fields than specified in the configuration then the XML outbound structure is created as follows:
u25CB ignore
Outbound structure only contains the fields in the inbound structure
Warm Regards,
Chandra.
NameA.missingLastfields is not supported at receiver CC, i have tried with this, but failed. Could you check this again.
I have tried the following it works ok.
In FCC, use the follwing parameters:
RecordSetStructure: Type (Incase type is your parent node)
Type. fieldSeparator = , (it may by any thing #, etc)
Type.endSeparator = 'nl'.
Inorder to produce the same output strucutr in flat file like below
Name,Surname,,
Name,Surname,Address,
Name,Surname,Address,Phone
Check this link where i have explained how to solve this issue.
Regards,
Prasanna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You have to use diiferenent CC for diiferent nodes.
use fieldFixedLength and use keepIncompleteFields. You will get it.
For More Help Refer This Link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
NameA.fieldFixedLengths
Specify a character string containing a list of fixed column widths that are separated by commas and determine the number and the length of columns generated in the text file.
Kindly check this link for detail[http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Just add the NameA.missingLastfields :ignore .
Maintain the FCC parameter for Type3 structure.
Regards,
Prakasu.M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
dynamic content conversion is not possible
you will have to use different CC per different message you need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.