Date format in flat file recon

Hi,
I am trying to do Flat file reconciliation but i am getting some error related to date format. I have tried format like 20 march 2009, 02-02-2010,20 Mar 2009,2010-01-01,2010/01/01
can any one please suggest me which format i need to use.
Thanks

Hi sunny,
I get the same error during GTC Flat file recon. "java.text.ParseException: Unparseable date: "2009/01/25"
my xl.defaultDateformat=yyyy/MM/dd hh:mm:ss z and source Date Format is given as yyyy/MM/dd(2009/01/25) and the date format in my flatfile is given as yyyy/MM/dd. But i still get this error.
I also tried with the following dates in flatfile
2009/Mar/25
2009/01/25
2009/March/25
Did I miss anything here!
Thanks

Similar Messages

Date format in flat file is MM/DD/YYYY

I want to to change date format in flat file from MM/DD/YYYY to in info cube YYYYMMDD.
What is the step by step procedure to do this.

Hi,
The date format should be YYYYMMDD in flat file.
IF the date format is not the above mentioned way, then you can change setting.
Going to System in Menu
System->User Profile->Own data.
Under Owndata you can change the date format to your requirement.
Check the below link also for detain info of coding:
Mandatory for Date field
regards
shoba

Date format in Flat File

Hi Experts,
I need to load date from flatfile. In flatfile the date format is hh:mm:ss.
I have an infoobject with type TIMS which can store only 6 CHAR length.
How is it possible to read 8 characters length in file with this info object ??
Two solutions i have is to ask for a file in hhmmss format or
the second one is to read the date with a new infoobject and write a routine to convert date to the required format in the transforamtion.
Is there any better way to handle this situation with out asking for a change in file ??

Hello Narasimha,
You can perform a conversion from 8 characters to 6 characters in the transfer rules of your flat file datasource.
In the transfer rule of the infoobject (with type TIMS), do the following:
1) Create an ABAP rule code
2) Select the 8 char field in the list of source fields
3) write the following ABAP code. This converts the data from the 8 char field to 6 chars:
concatenate trans_structure-<your 8 char field here>(2) trans_structure-<your 8 char field here>+3(2) trans_structure-<your 8 char field here>+6(2) into RESULT.
Hope this helps.

Date format in flat file of bdc

Hi Folks,
In BDC I have a flat file which has to be uploaded from a flat file and 4 users are using each of one has their date format.
so inorder to get their required date format what i need to do .

Hi,
       use the below logic in your code.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-031.
PARAMETERS: date1 RADIOBUTTON GROUP rad1 DEFAULT 'X',                                     "SAP date format YYYYDDMM
            date2 RADIOBUTTON GROUP rad1,                                                 "Date format like aprial31, 2006
            date3 RADIOBUTTON GROUP rad1,                                                 "Date format like 31 apr,2006
            date4 RADIOBUTTON GROUP rad1,                                                 "Date format like DD/MM/YYYY
            date5 RADIOBUTTON GROUP rad1.                                                 "Date format like DD.MM.YYYY
SELECTION-SCREEN END OF BLOCK b2
FORM getmonth .
SELECT mnr
         ktx
         ltx
   INTO TABLE T_month
   FROM t247
   WHERE spras = 'EN'.
IF sy-subrc NE '0'.
      MESSAGE I                                                          "Message - Not able to get month values from the table T247
ENDIF.
ENDFORM.
DATA : temp_date(16) TYPE c,
         temp1_date(60) TYPE c,
         year(4)        TYPE c,
         daymonth(11)   TYPE c,
         daymonth1(11) TYPE c,
         month(9)       TYPE c,
         day(2)         TYPE c,
         mon            LIKE t247-ktx,
         len            TYPE i   .
MOVE date TO temp1_date .
CONDENSE temp1_date NO-GAPS.
MOVE temp1_date TO temp_date .
IF date2 EQ 'X'.                                                                     "The date format is like Aprial 31, 2007
    CONDENSE temp_date NO-GAPS.
    SPLIT date AT ',' INTO daymonth year.
    IF STRLEN( year ) NE '4'.
      error = 'X'.
      WRITE : 'Invalid date format.'.
    ELSE.
      daymonth1 = daymonth.
      CONDENSE daymonth1 NO-GAPS.
      _len      = STRLEN( _daymonth1 ).
      l_len      = 13 - len.
      SHIFT daymonth1 RIGHT BY len PLACES.
      CONDENSE daymonth1 NO-GAPS.
      month    = daymonth1.
      CONDENSE month NO-GAPS.
      SORT t_month BY monthltx.
      READ TABLE t_month WITH KEY monthltx = month.
      IF sy-subrc <> 0.
        error = 'X'.
        WRITE : 'Invalid date format.' .
      ELSE.
        len = STRLEN( month ).
        CONDENSE daymonth NO-GAPS.
        SHIFT daymonth LEFT BY len PLACES.
        day = daymonth.
        CONDENSE day NO-GAPS.
        CONCATENATE year t_month-monthnumber day INTO o_date.
      ENDIF.
    ENDIF.
ELSEIF p_date3 EQ 'X'.                                                                "The date format is like 31 apr, 2007
    CONDENSE temp_date NO-GAPS.
    SPLIT i_date AT ',' INTO daymonth year.
    IF STRLEN( year ) NE '4'.
      error = 'X'.
      WRITE : 'Invalid date format.'.
    ELSE.
      daymonth1 = daymonth.
      CONDENSE daymonth1 NO-GAPS.
      SHIFT daymonth1 LEFT BY 2 PLACES.
      CONDENSE daymonth1 NO-GAPS.
      month = daymonth1.
      CONDENSE month NO-GAPS.
      TRANSLATE month TO UPPER CASE.
      SORT t_month BY monthstx.
      MOVE month to mon.
      READ TABLE t_month WITH KEY monthstx = mon.
      IF sy-subrc <> 0.
        error = 'X'.
        WRITE : 'Invalid date format.' .
      ELSE.
        CONDENSE daymonth NO-GAPS.
        day = daymonth+0(2).
        CONDENSE day NO-GAPS.
        CONCATENATE year t_month-monthnumber day INTO o_date.
     ENDIF.
   ENDIF.
ELSEIF p_date4 EQ 'X' OR p_date5 EQ 'X'.                                             "Date format is like DD.MM.YYYY or DD/MM/YYYY
    CONDENSE temp_date NO-GAPS.
    IF STRLEN( temp_date ) EQ 10.
      o_date0(4) = temp_date6(4).
      o_date4(2) = temp_date3(2).
      o_date6(2) = temp_date0(2).
    ELSE.
      error = 'X'.
      WRITE : 'Invalid date format.' .
    ENDIF.
ENDIF.
IF STRLEN( o_date ) NE '8'.
     error = 'X'.
     WRITE : 'Invalid date format.'.
ENDIf.
ENDFORM.
regards

Issue in trusted flat file recon for usr field having double data type

Hi
I have a field in usr schema which is of double data type. Now when i am doing gtc trusted flat file recon the user is getting created and all fields are getting populated but field having double data type doesn't get populated.
I have tried in other way also. After creating the user, I am trying to update that field (which is of double data type) via gtc trusted flat file update but in that case no recon event is getting generated.
Enviroment : OIM 11.1.1.5.0
I am stuck. Please help.

Somebody PLEASE some idea!!!
Any thought on the same would be really appreciated.
Thanks in advance.

What is the best way to load and convert data from a flat file?

Hi,
I want to load data from a flat file, convert dates, numbers and some fields with custom logic (e.g. 0,1 into N,Y) to the correct format.
The rows where all to_number, to_date and custom conversions succeed should go into table STG_OK. If some conversion fails (due to an illegal format in the flat file), those rows (where the conversion raises some exception) should go into table STG_ERR.
What is the best and easiest way to archive this?
Thanks,
Carsten.

Hi,
thanks for your answers so far!
I gave them a thought and came up with two different alternatives:
Alternative 1
I load the data from the flat file into a staging table using sqlldr. I convert the data to the target format using sqlldr expressions.
The columns of the staging table have the target format (date, number).
The rows that cannot be loaded go into a bad file. I manually load the data from the bad file (without any conversion) into the error table.
Alternative 2
The columns of the staging table are all of type varchar2 regardless of the target format.
I define data rules for all columns that require a later conversion.
I load the data from the flat file into the staging table using external table or sqlldr without any data conversion.
The rows that cannot be loaded go automatically into the error table.
When I read the data from the staging table, I can safely convert it since it is already checked by the rules.
What I dislike in alternative 1 is that I manually have to create a second file and a second mapping (ok, I can automate this using OMB*Plus).
Further, I would prefer using expressions in the mapping for converting the data.
What I dislike in alternative 2 is that I have to create a data rule and a conversion expression and then keep the data rule and the conversion expression in sync (in case of changes of the file format).
I also would prefer to have the data in the staging table in the target format. Well, I might load it into a second staging table with columns having the target format. But that's another mapping and a lot of i/o.
As far as I know I need the data quality option for using data rules, is that true?
Is there another alternative without any of these drawbacks?
Otherwise I think I will go for alternative 1.
Thanks,
Carsten.

Export HRMS data to a flat file

Hi All!
Are there any ways of exporting employee related data to a flat file without using a client app (PeopleCode or Integration Broker), that is simply generate a CSV feed from UI?

You can Schedule a query and specify the output format as text. Note that when you select View Log/Trace in process monitor, you will see a file with a .csv extension. However, it will open by default in Excel, and even if you select Save instead of Open it will try to change the extension to .xls. You will have to change it back to .csv.

Extract PSA Data to a Flat File

Hello,
I would like to download PSA data into a flat file, so I can load it into SQL Server and run SQL statements on it for analysis purposes. I have tried creating a PSA export datasource; however, I can find way to cleanly get the data into a flat structure for analysis and/or download.
Can anyone suggest options for doing this?
Thanks in advance for your help.
Sincerely,
Sonya

Hi Sonya,
In teh PSA screen try pressing Shift and F8. If this does not bring up the file types then you can try the following: Settings > Chnage Display Variants > View tab > Microsoft Excel > Click SAP_OM.xls and then the green check amrk. The data will be displayed in excel format which you can save to your PC.
Hope this helps...

Loading Master Data from a Flat File

Hi Guru, I have flat files of different SAP tables (Transactional data tables and Master Data ), I want to upload this flat files to a DSO, my question is in the case of Master Data Files example SAP table USR03 ( User Address Data) in a Flat file format which is better to create a Master data text and attributes Datasource or create it as a transactional data Datasource to upload it to a DSO.

Hi
Master data datasource should be used to load master data like customer details. customer data is the master data which does not change frequently. customer infoobject may have some attributes like customer name, customer contact number, customer address, etc. we have to maintain these attributes and text data.
Transaction data is something which keeps changing very frequently like price of the material, sales, etc. for loading such data we go for transaction datasources.
As mentioned above too,the changes in the address are very rare, therefore youshould not use transactional datasource.
Regards, Rahul
Edited by: Rahul Pant on Feb 7, 2011 12:24 PM

Uploading Data from a Flat File

Hi
I am trying to Upload data from a Flat File to the MDS. I have a few questions on the Process.
a) XI would be the Interface, and one end would be a file adapter with the Flat File format. On the other end, which Interface should I use - ABA Business Partner In or MDM Business Partner In. I do not understand the differences between them and where should which one be used?
B) At the moment,I want to map the data to standard Object type, Business Partner BUS1006. This also has a staging area already defined in the System. Can I view the data which is imported into the Staging area ? How so ?
C) The struture (or data) that I wish to upload has few fields, and does not map to the BP structure easily. In such a scenario does it make sense to
Create a new Object type
(ii) Create a new Business Partner type with the appropriate fields only ..
What I need to know is if either of these options is feasible and what are the pros & cons of doing this, in terms of effort, skillset & interaction with SAP Development ?
Kindly do reply if you have any answers to these questions.
Regards,
Gaurav

Hi Markus,
Thanks for your inputs.
I have tried uploading some dats from a Flat file to the Business Partner Onject type, BUS1006. I initially got some ABAP Parsing errors on the MDM side, but after correcting that, I find my message triggers a short dump - with the Method SET_OBJECTKEYS, not finding any keys in the BP structure that has been created.
Q1 - How do I get around this problem ? Is it necessary for me to specify Keys in the PartyID node of the Interface ABABusinessPartnerIn. or is it something else ?
Q2 - How is this general process supposed to work? I would assume that for staging, I would get incomplete Master data or data from flat files, which need not neccesarily contain keys. The aim is to use the matching strategies in the CI to identify duplicates and consolidate them.
Thanks in advance for your reply.
Regards,
Gaurav

Hierachy format in Flat file

Dear All,
We are in the process of creating the flat file interfaces for hierarchies to load into BW. We have few hierarchies for customer, product and few hierarchies for custom time dimensions. I would like to know the format in which we can request the master data management team to give hierarchy data in that format. Can any body guide in creating the format for flat file hierarchy to load. Meanwhile can any body tell me whether any restrictions are there in BI7 for hierarchy load from flat file. I heard as part of BI7 hierarchy load from flat file is not yet introduced, is it true.
Regards
Vijay

Hi Chandra,
Did you check this blog? Its a step by step example
/people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
hope this can be useful too.
http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/frameset.htm
Regards,
R.Ravi

Hierarchy format in Flat file

Hi gurus,
      please tellme the Hierarchy format in Flat file.
           ThanQ.
   Regards,
   Ramesh.

Hi
1.Defining the source system from which you want to load data:
Create For a flat file, choose: File System, Manual Metadata; Data via File Interface.
2.Defining the InfoSource for which you want to load data:
Create Application Component.
Create InfoSource , Direct Update
Choose an InfoObject from the proposal list, and specify a name and a description.
3.Assigning the source system to the InfoSource
Assign Source System. You are taken automatically to the transfer structure maintenance.
The system automatically generates DataSources for the three different data types to which you can load data.
Attributes, Texts,Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4.      Maintaining the transfer structure / transfer rules
Choose the DataSource to be able to upload hierarchies.
Idoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject, for which hierarchies are loaded. With this transfer method, during loading, the structure is converted to the structure of the PSA, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5.      Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6.      Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated from the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading via a PSA.
Further Steps:
Maintaining InfoPackages
Result
You have uploaded the hierarchy data for the corresponding characteristic.

Cube creation & Data loading from Flat file

Hi All,
I am new to BI 7. Trying to create a cube and load data from a flat file.
Successfully created the infosource and Cube (used infosource as a template for cube)
But got stucked at that point.
I need help on how to create transfer rules/update rules and then load data into it.
Thanks,
Praveen.

Hi
right click on infosource->additional functions->create transfer rules.
now in the window insert the fields you want to load from flat file->activate it.
now right click on the cube->additional functions->create update rules->activate it.
click on the small arrow on the left and when you reach the last node(DS)
right click on it->create info package->extenal data tab->give your FLAT file path and select csv format->schedule tab->click on start.
hope it helps..
cheers.

Date field in flat file

I ve date filed in flat file, like this
5/5/2007 12:00:00 AM
1/1/2007 12:00:00 AM
HOW could i take above date characteristic in my time dimension.
I m new to bw.
thanks
KS

Hi,
The date format should be YYYYMMDD in flat file.
IF the date format is not the above mentioned way, then you can change setting.
Going to System in Menu
System->User Profile->Own data.
Under Owndata you can change the date format to your requirement.
Check the below link also for detain info of coding:
Mandatory for Date field
Reg
Pra

Data misplaced during Flat file data load

Hi all,
i have to load the data from the flat file(txt format) but i found some record are not populating in PSA.
the voluem of the data is very huge. how to resolve this and data load seems to be green in info package monitoring.

Hi,
How did you conclude that the records are missing the PSA? Is it because the count is less?
There are the chances that the records are duplicated in the flat file.
Perhaps, you can increase the number of records per datapackage in the settings and can check the count.
If you feel, a particular record is not getting loaded, the load that record selectively through filter.
Split the load according to your convenience and load so that it will be easy to keep track of the records.
Thanks.

Date format in flat file recon

Similar Messages

Maybe you are looking for