Flat vs Qualified Flat

Hi,
What's the difference between Flat & Qualified Flat table?
Thanks

Hi Rokie,
What's the difference between Flat & Qualified Flat table?
    Genarally to avoid the redundancy of data, both Lookup[Flat] and Qualified Flat will be used.
    But What's the difference between Flat & Qualified Flat table?
    Lookup[Flat] contains some set of legal values which can be shared by main table .But in some cases
    we may have the data in some fields changes frequently based on other fields in that table.
    Suppose Price of a particular product changes based on region.Here what we need to understand is
    there are multiple values for each main table product.Obvisouly it increases redundancy of data.
    Qualifer table contains qualifier and non-qualifier fields.
    Data which is frequently changes based on other fields considered as Qualifier fields.
    Non-Qualifier fields contains the data which is responsible of changes in qualifier fields.
     I am giving differences between Lookup[Flat] and Qualified lookup.
     1) Lookup[Flat] contains predefined set of records (Ex: List of manufactures for particular product)
        whereas Qualified lookup contains conditional set of records (Ex: Pricing based on manufaturer and
         region)
   2) Lookup within lookup is possible whereas qualified lookup is possible only on main table
   3) Lookup table record need to be maintained before main table record whereas qualified record is
      maintained after main table gets created.
4) Lookup[Flat] contains relatively small no of records when compared to main table whereas qualified
     lookup contains large no of records when compared to main table.
    For better understanding, go through the above blogs given by others.
   Hope it helps,
   Reward points,if found useful.
   Thanks,
   Narendra.M

Similar Messages

Unique Field as Non-Qualifier in Qualified Flat Table

Hi experts,
I have the requirement to store the customer data regarding company code in the qualified flat:
customer have different data related on company code. It's important that this company code have to be unique in this qualified flat. (e. g. one customer have data with company code 3850, 3860 and 3870, its not allowed to store further data with the same company code 3850).
In the console I set the company code as unique and non-qualifierer field. But afterwards I was able to put two records with the same company code in this lookup qualified flat table.
What did I wrong? ( I use MDM 5.5 SP 6 Patch 3).
Best regards,
Nico

Hello,
the behaviour depend of the settings for qualified upadate.
(Set Qualified Update sub-menu when define mapping in import manager)
Settings can be:
- Append
- Replace
- Update
In your, case looks to be "Update". be sure the Set Matching Qualifier is righly set for the qualifier which indentify the relation to the flat data. (sometimes have to clean this point)
Check New links are : Create and Existing Links are : Update (All Mapped Qualifiers)
Hope helps you
best regards
Vincent

MDM ABAP API - Retrieval of Qualified Flat lookup fields

Hi,
I am having trouble retrieving the records using MDM ABAP API when the fields that are being retrieved includes a Qualified Flat lookup field. An exception is being thrown with the error message <b>Value with type id 0 is not supported</b>. I don't see any problem when I am trying to retrieve other fields of types String or Real. The type of the Qualified Flat lookup field is set to MDM_QUALIFIED_LINK_TABLE as per the How to guides given by SAP. Any ideas on why the exception is occuring?
Thanks
Suman

Hi Suman,
Please check if the How to guide (#13) in SMP -operations is of help https://websmp204.sap-ag.de/nw04operation
Regards,
Anita

Search by qualified parameter in a LookUP Qualified Flat Multi Valued Table

I am working on a MDM development but I am having some problems the development consists in searching in MDM a certain key but the thing is that this value is stored in a Look up qualified flat multi valued table, I have implemented a code that gives me the correct results but it takes a lot of time because it goes through all the main table the ideal would be to search directly for this value but as it is in a look up qualified multi valued table I dont know how to implement this kind of search, do you have an idea how to implement this.
Main Table : ING_ROLE_PLAYER
Lookup qualified flat multi valued table : ILYTICS_SEARCH_KEY, this table has two qualifiers KEY_TYPE and SEARCH_KEY
I receive a string that represents a SEARCH KEY as a parameter to look into MDM and get some data this is I want to search using a qualifier parameter as a search parameter.
If anybody could help me it would be vey helpful
Best Regards
Michele González

Hi Michele,
Try the following code :
String searchKey="/the value of the input searchkey/";
// create a catalog object
CatalogData catalog = new CatalogData();
// create a search object on the main table.
Search search = new Search("ING_ROLE_PLAYER");
// create a resultset definition on the main table
ResultSetDefinition rsd = new ResultSetDefinition("ING_ROLE_PLAYER");
A2iResultSet result=null;
// adding a free-form limiting for the specified table
     FreeFormTableParameter fftpRole = search.GetParameters().NewFreeFormTableParameter("ING_ROLE_PLAYER");
//add a new table 'ILYTICS_SEARCH_KEY'-the qualified lookup table to the search object.
     FreeFormTableParameter fftpKeys = search.GetParameters().NewFreeFormTableParameter("ILYTICS_SEARCH_KEY");
// get the field 'SEARCH_KEY' of the 'ILYTICS_SEARCH_KEY' table for free-form search.
     FreeFormParameterField fftpKey = fftpKeys.GetFields().New("SEARCH_KEY",FreeFormParameterField.SEARCH_OPERATOR_AND);
//add a free-form search parameter for 'SEARCH_KEY'
     fftpKey.GetFreeForm().NewString(searchKey,FreeFormParameter.EqualToSearchType);
// obtain the result set
     result = catalog.GetResultSet(search, rsd, "/any field name in main table and resultset definition/", true, 0);
Hope it helps.
Pls reward, if helpful.
Regards,
Karambir Singh.

Reading data from Lookup [qualified flat] (multi-valued) table

I have a main table u2019ABCu2019 which has a Lookup [qualified flat] (multi-valued) field u2018XYZu2019 along with some other text fields. I am able to read data from table ABC including lookup field data, but I do not see the relation
For Ex: If for a contract in table u2018ABCu2019, there are multiple line items in look up table. I have a contract with 2 line items in u2018ABCu2019, but 4 line items in look up table (2 records each for each line item with item number). Now, when I read the data from table u2018ABCu2019 for that contract, I get all the 4 lines in result table; but item no is blank even though there is item no field in table u2018XYZu2019.
Below is the sample code:
wa_query-parameter_code = Contract ID Field.
wa_query-operator = 'EQ'.
wa_query-dimension_type = 1. "mdmif_search_dim_field.
wa_query-constraint_type =8. " mdmif_search_constr_text.
wa_string = Contract Number.
GET REFERENCE OF wa_string INTO wa_query-value_low.
APPEND wa_query TO lt_query.
CLEAR wa_query.
CALL METHOD lcl_api->mo_core_service->query
        EXPORTING
          iv_object_type_code      = 'ABCu2019
        it_query                 = lt_query
        IMPORTING
          et_result_set            = lt_result_set_key.
LOOP AT lt_result_set_key INTO ls_result_set_key.
    lt_keys = ls_result_set_key-record_ids.
ENDLOOP.
Contract Price for lower bound
ls_result_set_definition-field_name = XYZ'.
APPEND ls_result_set_definition TO lt_result_set_definition.
CALL METHOD lcl_api->mo_core_service->retrieve
    EXPORTING
      iv_object_type_code      = 'ABCu2019
      it_result_set_definition = lt_result_set_definition
      it_keys                  = lt_keys
    IMPORTING
      et_result_set            = lt_result_set.
In table lt_result_set, I see 4 records, but I do not know which 2 records belong to item 1 of the contract and other 2 records for item2.
Can anyone help me in resolving this. Any kind of help is appreciated.
Thanks,
Shekar

i do not quite understand ur problem statement ..
but if u have items in the main table to which QLUT entries are linked ..
then when you read the main table record (u get LinkIds at the record level) that gives u the relation to the Qlookup values
i mean for ur case - u would get only 2 values in the QLUT values for the "selected" record in the main table
am not sure if you say correctly - that you get "unlinked" values in the QLUts
so u should 2 values in lt_result_set and not 4 .. see if u are using the LinkIds properly
hth
thanks
-Adrivit

Read Only Field in Qualified Flat Table

Hi Guys.
After upgrading MDM 5.5 SP4 to MDM 5.5 SP6, fields of the qualified flat table appear as read only in Standard IView Item Details.
Any ideas ?
Thanks in advance
Luciano

Hi Luciano,
Have you made sure to upgrade your portal content as well when you upgraded your MDM ?
As portal SCA files are MDM server version and patch dependent.
So if you have upgraded to SP06 from SP04 then accordingly you will have to deploy the SP06 version sca files on WAS.
This will also cause you to recreate your Iviews and pages again as once you undeploy your older version of Sca file from EP their Iview contents and configurations will also be lost.Unless you have used some way of reusing the created iViews.
So test for these two changes,they could be the possible cause of the qualified fields behaviour.
Also make sure you upload the rep with update indices and Update repository if you are using an archived version of it from the SP04 version to the SP06 version.
Hope It Helped
Thanks & Regards
Simona Pinto

Flat File to Flat File Scenario using File Adapter

Hi Experts,
In my scenario, requirement is Flat File to Flat file through File Adapter in PI. At sender end, we would need to use Sender File Adapter (NFS) and receiver end we would need to use Receiver File Adapter (FTP). File would be coming as a encrypted format, and the file needs to be sent in encrypted format.
Any idea how to proceed with this requirement would be helpful.
Thanks and Regards
Soumya

Hi Soumya,
You need to choose the FTP in the "transport protocol" option. Then in the FTP connection parameters choose the option Connection Security and assign the value "FTPS for control and Data Connection". Then the "Command Order" will show up below that option and you could leave the default value itself. If you are using Public private key certificates of X.509 then you could choose the option "Use x.509 certificate for client authentication" and assign the values to the "keystore" and "certificate & private key" fields.
Note: To use the FTP with SSL you need to add the CA certificate to the TrustedCAs keystore view.
Regards,
Vishnu.

File Content Conversion i.e Flat file 2 Flat file

Hi guys,
I am new 2 SAP XI
and i am trying 2 do "Flat File To Flat File".
Input File contains following data:
Name:varun
Surname:rajaraman
Address:B-2
Employee no:8204
i.e Each Data is in separate Row.
Output File Should contain the following data:
I am varun rajaraman staying at B-2 bearing employee no. 8204.
(name,surname) (address) (Employee No.)
i.e data should be in a single row.
So, i have a problem of reading the data from input file i.e data from each row and transfering it into output file along with which i need 2 insert "i am " ,"staying at", etc.
pls tell me the procedure in detail.
Thanks and regards
santhosh rajaraman

Hi,
Check this links for file content convertion.
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
Regards,
Phani
Reward Points if Helpful

Reg error in flat file to flat file scenario

Hi techies,
Iam just starting working with XI scenarios.
In base flat file to flat file scenario which is mentioned in wiki.sdn
http://wiki.sdn.sap.com/wiki/display/XI/FLATFILETOFLATFILE
I had completed entire scenario. After generating sender file. Iam getting this error in runtime work bench.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
Please suggest how to resolve this error.
Thanks in advance,
Regards,
Kiran

Hi,
From your error description,
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
it is clear that you have missed out either or both the 2 parameters in receiver file adapter content conversion, namely EMP.fieldFixedLengths and EMP.fieldSeparator.
From the example that you followed, use the following values for the 2 parameteres is the output file is a comma separated file:
EMP.fieldFixedLengths: 8,10,10
EMP.fieldSeparator: ,
I have assumed that the lengths of the fields NAME,ADD,MOBILE are 8,10 and 10 respectively. Change them according to your requirement.
Use any other value in place of comma(,) in EMP.fieldSeparator according to the requirement.
Hope it helps you buddy!!!
Thanks
Biswajit
Edited by: 007biswa on Feb 22, 2011 9:25 AM
Edited by: 007biswa on Feb 22, 2011 9:28 AM

Flat File to Flat File scenario

Hi all,
I have a flat file to flat file scenario. I pick up a file in a specific format and produce a flat file in tab delimited format after some mapping.
Everything is ok. All the functionality is working perfectly. However, there is one small error. In case the source file is empty, there is an error message in SXMB_MONI (which is correct as there is no XML content) but I still need to generate an empty output file.
Is this possible ? Can I change something at the 'File Content Conversion' level ?
Any advise will be highly appreciated.
Thanks,
Freddy.

Hi Freddy,
>>>Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed.
The charset of the XML cannot be determined. That is written clearly in the message.
Is your XML belongs to UTF-16 or UTF-32? Then it needs a BOM which is missing.
Have a look at below link.
http://en.wikipedia.org/wiki/Byte-order_mark
Check, if there is an XML header and which charset is mentioned.
Regards,
P.Rajesh

Flat File to Flat File

Hi,
I am doing an interface (Flat file to Flat file)
The input file fields are separated by delimiter @!.Which will have multiple records like LEVEL1,LEVEL2,LEVEL3
Input Flat file
Level1@!PoNo@!ShortText@!StDate@!EndDt@!Vendor@!Status
Level2@!PoNo@!L2id@!L2desc@!L2stdt@!L2ensdt@!L2plant@!order
Level3@!PoNo@!L2id@!L3id@!L3stdt@!L3enddt@!order
Level1@!PoNo@!ShortText@!StDate@!EndDt@!Vendor@!Status
Level2@!PoNo@!L2id@!L2desc@!L2stdt@!L2ensdt@!L2plant@!order
Level3@!PoNo@!L2id@!L3id@!L3stdt@!L3enddt@!order
Level1@!PoNo@!ShortText@!StDate@!EndDt@!Vendor@!Status
Level2@!PoNo@!L2id@!L2desc@!L2stdt@!L2ensdt@!L2plant@!order
Level3@!PoNo@!L2id@!L3id@!L3stdt@!L3enddt@!order
Output file
The outfile fields are separated by tab delimiter
<L1> L1Pono L1desc L1stdt L1enddt L1hr L1cost L1vendor L1misc L1status
<L2> L1Pono L2ID L2desc L2stdt L2enddt L2priority L2loc L2plant L2order
<L3> L1Pono L2ID L3ID L3desc L3stdt L3enddt L3work L3emp L3order
The outfile fields are separated by tab delimiter
<L1> L1Pono L1desc L1stdt L1enddt L1hr L1cost L1vendor L1misc L1status
<L2> L1Pono L2ID L2desc L2stdt L2enddt L2priority L2loc L2plant L2order
<L3> L1Pono L2ID L3ID L3desc L3stdt L3enddt L3work L3emp L3order
Do I need to use file content conversion?how do I replace the delimiter?
Can you please tell me how to do this,appreciate you help.Let me know if you need more info.
Points will bw rewarded
Thanks

Hi Guys,
Thanks for all the replies.I have done all necessary things for sender and reciver communication channels.I am pretty sure the sender CC is fine,but I am not sure of the receiver CC.The file is not being picked up at the sender side.In went and saw the adapter monitoring,it shows me the below error
Receiver Adapter v2405 for Party '', Service 'BS_XIX_010':
Configured at 2008-04-21 09:44:11 CDT
History:
- 2008-04-21 09:44:11 CDT: Error: Conversion initialization failed: Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In the receiver CC I am giving the following details,is there anything I am missing,do I need to check the Advanced mode in the CC and give info there?
LEVEL1.fieldSeparator     ,
LEVEL2.fieldSeparator     ,
LEVEL3.fieldSeparator     ,
LEVEL1.endSeparator     'nl'
LEVEL2.endSeparator     'nl'
LEVEL3.endSeparator     'nl'
Thanks

IDOC to Flat file and Flat file to IDOC

Hello Experts,
I have the following requirement in my current project:
Third Party Sender sends the data in the in the below XML format via HTTP:
<?xml version="1.0"?>
<fxEnvelope>
<header>
    <message>
      <exchangeID></exchangeID>
      <messageID></messageID>
      <subject></subject>
      <payloadType>IDOC</payloadType>
    </message>
    <from>
      <orgID></orgID>
      <locationID></locationID>
      <messageID></messageID>
    </from>
    <to>
      <orgID></orgID>
      <locationID></locationID>
    </to>
</header>
<body>
    <Opaque>
      <DataType></DataType>
      <DataStream></DataStream>
    </Opaque>
</body>
</fxEnvelope>
In the above XML, the Tag <DataStream> is a string which contains the IDOC flat file.
Now, the scenario is HTTP to IDOC, where the sender sends the above XML payload and PI needs to convert <DataStream> to IDOC XML and pass it on to the receiver R/3.
But the challange i am facing is converting this <DataStream> tag which contains the IDOC flat file to IDOC XML using a Mapping program.Since both adapters are running on ABAP stack i can not go for Adapter Modules available(We are using PI 7.10).
Looking for some guidance on the same.
Thanks in advance.
Cheers,
Manasa.

There are 2 options for you
In either case, you might need a java mapping to convert the DataStream into String. Use a file adpater to write this string to IDOC-File.
1) Option1: Write the content of DataStream into IDOC-Flatfile.(java mapping) Pick it from PI to convert IDOC-flat file inot IDOC-XML (using std features of PI) & send it to ECC.
2) Option2: Write the Content of DataStream to IDOC-Flatfile (accessible to ECC system). Configure WE21 to pick the file from a file port.
If the datastream was IDOC-XML, then it would have been simpler, it will be a direct communcation from PI to ECC (using java mapping & IDOC adapter).
Regards,
Siva Maranani

Mapping error - Flat file to Flat file Scenario

Hi All,
Iam designing Flatfile to Flatfile Scenario.
Source Structure
RSET
RSETSTRUCTURE 1-un
S1 1-1
S2 1-1
S3 1-1
target Structure
RSET
RSETSTRUCTURE 1-un
R1 1-1
R2 1-1
R3 1-1
Mapping
RSETSTRUCTURE - RSETSTRUCTURE
S1 - R1
S2 - R2
S3 - S3
Flatfile is getting picked
Iam getting Mapping exception.
Please help.
Regards,
Jeevan

Hi Raj,
Iam sending the Inbound payload
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_DB2_S_FF xmlns:ns="http://gsll.com/DB2">
- <RSETSTRUCT>
<S1>A</S1>
<S2>A</S2>
<S3>A</S3>
</RSETSTRUCT>
- <RSETSTRUCT>
<S1>B</S1>
<S2>B</S2>
<S3>B</S3>
</RSETSTRUCT>
</ns:MT_DB2_S_FF>
regads,
Jeevan

SCHEMA: Flat vs. hierarchical

All,
I'd like your feedback on another topic relating to the schema, this
one at a higher level. Basically, the question is whether you think we
should adopt a flat schema, or a hierarchical schema. To explain:
- With a flat schema, we assign some number of "buckets" to hold event
data, give a name to each bucket, and then for any event that comes in
we extract the relevant data and drop it into that bucket
- With a hierarchical schema, we would have a set of "objects" with
attributes that we could attach to events, and then for any given event
that we receive we extract the relevant data and set the various
attributes of the various objects.
You may have already noted that to some extent we already have a
hierarchical schema, in that we define four top-level containers - the
Initiator, Action, Target, and Observer - and then we have some
pseudo-objects under those like User, Host, etc. Right now we sort of
"fake" an object-based schema by using CamelCase, e.g. InitUserName,
InitUserDomain, etc. With a true hierarchical schema, we'd actually have
an object calling Initiator, which might have a child object called
User, which might have attributes Name, Domain, ID.
Please again ignore details about how this would actually be
implemented; you could always convert from one to the other for internal
storage if need be. Instead focus on whether it would be easier to
access the data you want to see by using a hierarchical model or a flat
model.
These are the pros and cons as I see it:
- The flat schema is a little easier to display in a table and easier
to read in a single-line format, but on the other hand the object schema
yields much more interesting, interactive displays (the SLM event
display, again, sort of "fakes" an object schema but putting the Init*
fields at left and the Target* fields at right.
- If we go to an object schema, we could actually reference almost any
type of object we wanted by re-using something like DMTF's Common
Information Model, which describes virtually any manageable IT resource.
Right now if we want to include, say, a MAC address and we hadn't
thought about that before, we have to completely revise our flat schema
and define a new field. The potential downside is that not every event
would then have even a standard set of fields if the values for those
fields were null.
- The other downside of course is how we migrate from one schema to
another if we fundamentally change how this works. I think this is
do-able, however, if we come up with some migration plans and perhaps
support both models in some way for a while (the flat schema, for
example, is just a representation of some subset of object attributes).
So let's give some examples. Let's say that we have a user opening a
file - simple enough. In a flat schema, this might look like:
{ "InitUserName": "user2", "InitUserID": "104", "InitHostName": "dc01",
"TargetDataName": "syslog-ng.conf", "TargetDataContainer":
"/etc/syslog", "TargetHostName": "dc01" }
Note that it's a little ambiguous that this particular username
represents an account on host 'dc01'
But in an object schema, this might look like:
{ Initiator: { Account: { Name: user2, UserID: 104, Host:
dc01}},
"Target": { "File": { "Name": "syslog-ng.conf", "Container":
"/etc/syslog", "Host": "dc01"}}}
OK, so what do you all think?
DCorlette
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=419793

Hi Rokie,
What's the difference between Flat & Qualified Flat table?
    Genarally to avoid the redundancy of data, both Lookup[Flat] and Qualified Flat will be used.
    But What's the difference between Flat & Qualified Flat table?
    Lookup[Flat] contains some set of legal values which can be shared by main table .But in some cases
    we may have the data in some fields changes frequently based on other fields in that table.
    Suppose Price of a particular product changes based on region.Here what we need to understand is
    there are multiple values for each main table product.Obvisouly it increases redundancy of data.
    Qualifer table contains qualifier and non-qualifier fields.
    Data which is frequently changes based on other fields considered as Qualifier fields.
    Non-Qualifier fields contains the data which is responsible of changes in qualifier fields.
     I am giving differences between Lookup[Flat] and Qualified lookup.
     1) Lookup[Flat] contains predefined set of records (Ex: List of manufactures for particular product)
        whereas Qualified lookup contains conditional set of records (Ex: Pricing based on manufaturer and
         region)
   2) Lookup within lookup is possible whereas qualified lookup is possible only on main table
   3) Lookup table record need to be maintained before main table record whereas qualified record is
      maintained after main table gets created.
4) Lookup[Flat] contains relatively small no of records when compared to main table whereas qualified
     lookup contains large no of records when compared to main table.
    For better understanding, go through the above blogs given by others.
   Hope it helps,
   Reward points,if found useful.
   Thanks,
   Narendra.M

Getting error while loading Flat File

Hello All,
I am getting error while loading flat file. Flat file is a CSV file.
Value ',,,,,,,,' of characteristic 0DATE is not a number with 000008 spaces
Data seprator |
Escape sign ;
It has 23708 entries , it s loading successfully till 23 665 entries
Besides when checked in PSA
for record having entries >23667 has calender day as ,,,,,, where as rest entries are having date
Besides when i checked in Flat file ,the total number of rows is 23,667 is there but i wonder why it has got 23,708 in
RSMO
Could you please let me know how to correct.
regards
path

Hi,
For date column you should maintain YYYYMMDD formate Eg: 20090601, kepp cursor on date column and right click and Formate >Custome>make it 00000000 then save teh file as .CSV . First type values on column and do like this formate and save it and without opening it load it. Once you open it you losw 00000000 formate you need to give again the same formate.
Settings in Infopackage:
Data Format = CSV
Data Separator = ,
Escape Sign = ;
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/01ed2fe3811a77e10000000a422035/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6567e07211d2acb80000e829fbfe/content.htm
Thanks
Reddy

Flat vs Qualified Flat

Similar Messages

Maybe you are looking for