Problem while uploading master data through two files

Hi all,
When i try to upload master data of CUSTOMER with two files , Attribute and Text.
Text gets uploaded perfectly.
for Attribute, the data upload is done and psa i can see the exact data. But when i check the CUSTOMER object, i am not able to find the actually Attributs data. Instead those colmns are filed with 'E'.
Can anybdy please explain me wheret the problem is.
Thanks..

Hi Sun,
First check the data in PSA whether the records are fine or any discrepancy in them. Also check the properties of the COSTUMER object into which you are loading. The properties "type" or the "size" of the object may not be matching with the same in the file.
Check them and try to load once again.
Hope this helps u...
Regards,
Koundinya Karanam.
Edited by: koundinya karanam on Jan 15, 2008 12:05 AM

Similar Messages

Error while uploading master data attributes thru flat file

while uploading master data attributes thru flat file i am facing the below errow. can nyone let me know plz.
Error 8 when compiling the upload program: row 227, message: Data type /BIC/CCDEIO_MAT5_ATTR was found in a new

This just means that you changed the transfer rules/transfer structure and have not refreshed the workbench yet. The infopackage data hasn't been updated ... this is similar to a datasource update, where you need to replicate to make sure BW knows the latest version.
The best way to correct this error is to reload RSA1. Every time I make a change to the tr/ts, I always run /nrsa1 to refresh the workbench.
Brian

Loading of master data through flat files

Hi
can anybody tell how to load master data through flat files.As for as my knowledge we load characteristic and attributes values first and then we load text and then hierarchy.
is it right or is there any procedure to load all values at a time.
sai

Hi ,
condition1:The sequence of columns in the transfer structure must correspond to the sequence of columns in your flat file
chk this help.sap link
http://help.sap.com/saphelp_nw04s/helpdata/en/c8/e92637c2cbf357e10000009b38f936/frameset.htm
Hope this helps you!!!!!!!
cheers,
Swapna.G

Issue while loading Master Data through Process Chain in Production

Hi All,
We are getting an error in Process chain while loading Master Data
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
I had checked the PSA also but I could not find any record and the strange thing is, Job itself is not getting scheduled. Can any one help me out in order to resolve this issue.
Regards
Bhanumathi

Hi
This problem is not related to Process chain..
u can try this..
In RSMO, select the particular load you want to monitor.
In the menu bar, Environment >>> Transact. RFC >>> Select whichever is required, BW or Source System.
In the next screen you can select the Execute button and the IDOCS will be displayed.
Check Note 561880 - Requests hang because IDocs are not processed.
OR
Transact RFC - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
(from JituK)
Hope it helps
Darshan

How to avoid the split problem when uploading the data from csv file

Dear Friends,
              I have to upload data from the .csv file to my custom table , i have found a problem when uploading the data .
i am using the code as below , please suggest me what i have to do in this regard
      SPLIT wa_raw_csv AT ',' INTO
                wa_empdata_csv-status
                 wa_empdata_csv-userid
                 wa_empdata_csv-username
                 wa_empdata_csv-Title
                 wa_empdata_csv-department.
APPEND wa_empdata_csv TO itab.
in the flat file i can see for one of the record for the field Title as
Director, Finance - NAR............there by through my code the wa_empdata_csv-Title is getting splited data as "Director, and Department field is getting Finance - NAR" , i can see that even though " Director, Finance - NAR" is one word it is getting split .
.......which is the problem iam facing.Please could any body let me know how in this case i should handle in my code that this word
"Director,Finance - NAR"   wil not be split into two words.
Thanks & Records
Madhuri

Hi Madhuri,
Best way to avoid such problem is to use TAB delimited file instead of comma separated data. Generally TAB does not appear in data.
If you are generating the file, use tab instead of comma.
If you cannot modify the format of file and data length in file is fixed character, you will need to define the structure and then move data in fixed length structure.
Regards,
Mohaiyuddin

Long text problem while uploading Inspection plan through BDC.

Hi,
I am facing some problem while uploading the inspection plan. There are few MICs for which we are having long text, while uploading the inspection plan through BDC - some other long text is getting copied into the MIC's long text. After checking I came to know that in function module, read_text - some text which is stored in ABAP memory is getting copied into the inspection plan.
I am working in SAP release 4.7. I have checked with SAP notes: 97419, but it is also not satisfying.
Waiting for quick solution.
Thanks in advance.
Fahié

Hi a®s,
Thanks a lot for your kind reply.
My requirement is I want to maintain long text for few MICs (which are not having long texts at MIC level) in inspection plan (QP01).
When I am trying to manually assign the MIC's to inspection plan (QP01), long text is copied whereas I am not clicking the long text icon in (QP01). Long text is not maintained in MIC level, still some long text is copied to this MIC. This was also happening while uploading the inspection plan thro' BDC.
I believe what you have mentioned about function module SAVE_TEXT cannot be used here since long text is already copied before we pass the long text. Also if we pass some long text, still apart from the long text what we have passed there is some other long text copied (extra long text).
Waiting for quick solution.
Thanks in advance.
Fahié

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
 MATNR LIKE MARA-MATNR,
 MBRSH LIKE MARA-MBRSH, "Industry Sector
 MTART LIKE MARA-MTART, "Matl Type
 WERKS LIKE MARD-WERKS, "Plant
 LGORT LIKE MARD-LGORT, "Storage location
 VKORG LIKE MVKE-VKORG,
 VTWEG LIKE MVKE-VTWEG,
 MAKTX LIKE MAKT-MAKTX, "Matl Desc.
 MEINS LIKE MARA-MEINS, "Base UOM
 MATKL LIKE MARA-MATKL, "Matl.Grp
* BISMT LIKE MARA-BISMT,
 SPART LIKE MARA-SPART, "Division
* BRGEW LIKE MARA-BRGEW, "Gross weight
 GROES LIKE MARA-GROES,
 FERTH LIKE MARA-FERTH,
 ZEINR LIKE MARA-ZEINR,
 TAXKM1 LIKE MLAN-TAXM1,
 TAXKM2 LIKE MLAN-TAXM2,
 TAXKM3 LIKE MLAN-TAXM3,
 TAXKM4 LIKE MLAN-TAXM4,
 KTGRM LIKE MVKE-KTGRM,
* GEWEI LIKE MARA-GEWEI, "Weight unit
* NTGEW LIKE MARA-NTGEW, "Net weight
* KLART LIKE RMCLF-KLART,
 MTVFP LIKE MARC-MTVFP, "Availibility Check
* XGCHP LIKE MARA-XGCHP,
 XCHPF LIKE MARA-XCHPF, "Batch Management
 TRAGR LIKE MARA-TRAGR,
 LADGR TYPE MARC-LADGR,
 VPRSV LIKE MBEW-VPRSV, "Price Control
 VERPR LIKE MBEW-VERPR,
* SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
* $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
* $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
 IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
* $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
 MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
* DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = 'P_FILE'
 IMPORTING
 FILE_NAME = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*& Form data_fetch_to_xls
* text
* --> p1 text
* <-- p2 text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = 1
 I_BEGIN_ROW = 2
 I_END_COL = 25
 I_END_ROW = 2
 TABLES
 INTERN = IT_EXCEL
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
 /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
 IF NOT IT_EXCEL[] IS INITIAL.
 CLEAR LEGACY_DATA.
 REFRESH LEGACY_DATA[].
 LOOP AT IT_EXCEL.
 IT_EXCEL_DUMMY = IT_EXCEL.
 AT NEW COL.
 CASE IT_EXCEL_DUMMY-COL.
 WHEN 1.
 LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 2.
 LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 3.
 LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 4.
 LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 5.
 LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 6.
 LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 7.
 LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 8.
 LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
 WHEN 9.
 LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
 WHEN 10.
 LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
 WHEN 11.
 LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 12.
 LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
 WHEN 13.
 LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 14.
 LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
 WHEN 15.
 LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 16.
 LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 17.
 LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 18.
 LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 19.
 LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 20.
 LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 21.
 LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 22.
 LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 23.
 LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 24.
 LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 25.
 LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
 APPEND LEGACY_DATA.
 CLEAR LEGACY_DATA.
 ENDCASE.
 ENDAT.
 AT END OF ROW.
 ENDAT.
 ENDLOOP.
 ENDIF.
ENDIF.
ENDFORM. " data_fetch_to_xls
*& Form insertion
* text
* --> p1 text
* <-- p2 text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM. " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

Problems with uploading master data in BI 2004S

Hi all,
I wanna upload master data in FI from R/3 System to BI System. I created its transformation. Then, I migrated it WITH EXPORT option. After that, I created Data Transfer Process (DTP), I didn't change any thing, just "Save and Active". Then I created InfoPackage for it => choose Schedule tab and press Start. Open DTP and choose Execute tab -> press Execute.
1. In the case of successful process (the log showed no errors), How can we check that data is transferred successfully?
2. Case 2: I did all above steps for a data source. But when I opened InfoPackage -> it said "This InfoPackage has been already in Process Chain"... I still continued to execute its DTP but I failed. The log said that the data was duplicated.
What does it mean? And what should I do in this case?
3. Case 3: I have a data souce Account Type with <0ACCT_TYPE_TEXT> (icon dialog). I migrated it but failed. Then, after I refreshed, this datasource moved to the group that had been migrated before (in the end of the tree) but <0ACC_TYPE_TEXT> disappeared.
So, I cannot create DTP or InfoPackage for it to transfer. In this case, Do I have to re-create a DataSource? What should I do?
Thanks in advance.

case 1:
Check there might be duplicate record. as it is a text datasource language may be maintained. U can check in monitor what record is showing error.
case 2:
If u migrate the data source then it is a BI7.0 version.
If u want to recover 3.x datasource then u need to use RSDS .
Then again u can create Data Transaformation and DTP and migrate once again.
then load the data.
Normally if u r working on BI7.0 do all the stuffs(DT, DTP) using 3.X version then do the migration of datasource else if u migrate first and do the transformation then u will have to manual mapping and u may missed and do a lot of mistakes.
Thanks,
Debasish

Standard Report to upload Master Data from Excel files

Hi,
I am testing some configuration items and I am in need of master data for various scenarios, which is not available in the system now. Is there any standard report that will read data from an excel sheet and upload the corresponding infotypes? This will be of great help.
Thanks
K

Hi,
As far as I know, there is no standard report in SAP for master data load using excel sheet. You have write a custom z-program with the help of BDC for basic actions or for individual infotypes upload you can use 'Fast Entry' for quickly uploading data for any perticular infoype using Tcode PA30.
Hope this helps.
Thanks,
Sarika.

Problem while attaching master data source to generic datasource

Hi All,
I have created a generic datasource using three tables in crm systems. the tables are CMSD_CB, CMAD_LO_PRICE AND CMSD_LO_QUANT.
i have loaded data to bw system and want to attach 0ORGUNIT master datasource to the generic datasource. so that i can get 0ORGUNIT hierarchy and sales grp/office details.
could some one help how to solve this problem.
Thanks in advance.
Thanks,
Mahantesh

You don't have to attach the master data datasource to your generic datasource.
Master data is loaded separately from transaction data, so you will see your hierarchy from the moment you loaded it with the 0ORGUNIT hierarchy datasource into your infoobject 0ORGUNIT.

Problem while loading master data - Help

Hi
I am using BI-7. I have Customer & Plant compounded in ZMat_Plant. I am trying to load zmat_Plant but getting following error.
I followed the solution as in link,but didnt worked: RSDMD 194: Error Loading 0Material 7.0 using 0SOURSYSTEM as compounding
Looking for your help... Thanks...
Diagnosis
    Data record 1 & with the key '00000000033000100000009 &' is invalid in value '00000000033000100000009 &' of the attribute/characteristic ZMAT_PLNT &.
System Response
    The system has recognized that the value mentioned above is invalid, and has processed this general error message. A subsequent message may give you more information on the error. This message refers to the same value, even though it does not state this explicitly.
Procedure
    If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

I used 'APLHA' conversion routine in infopackage, so the problem has been solved. Thanks...

Problem while loading Master data load

Hi,
i am loading master data for 0PROJECT. for attributes and text we do have delta.
for text after load added records will be 0 eventhough few records there and they are transferred records. i checked in RSA3 it has records.
can any body tell me the reason for this?
Thanks,
Vijaya

for full load only no of added records are 0 where transferred are 26.
i checked in master data table and all these records already present... may be becoz of that reason if i do full load and delta ...added is 0 only.
am i right in this? plz let me know.
Thanks,
Vijaya

REg Upload of data through Flat file ..... .XLS or .TXT or .CSV

Hi,
I am trying to upload flat file data using the FM GUI_UPLOAD for .TXT file and
FM TEXT_CONVERT_XLS_TO_SAP for .Xls and .csv files
My internal table is as follows
TYPES : BEGIN OF ty_f64,
 field(255) type c,
 END OF ty_f64.
data : it_f64 type table of ty_f64.
Example Flat file data is as follows
H 20112008 DR 0001 20112008 INR
L 01 61 1000
L 50 41000 1000
H 20112008 DR 0001 20112008 INR
L 01 61 1000
L 50 41000 500
L 50 41000 400
L 50 41000 100
My problem is that only the first field i.e H or L is getting updated into my internal table but I want whole record to be the content in one row
i.e in RUN TIME I see the internal table data as
H
L
L
H
L
L
L
regards
Prasanth

Check the below code
REPORT ZSRK_073 .
CLASS CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
TYPES : BEGIN OF TY_F64,
 FIELD(255) TYPE C,
 END OF TY_F64.
DATA : IT_F64 TYPE TABLE OF TY_F64,
 WA_F64 TYPE TY_F64.
TYPES : BEGIN OF TY_HEADER,
 RECNO TYPE I,
 INDICATOR,
 BLDAT TYPE BLDAT,
 BLART TYPE BLART,
 BUKRS TYPE BUKRS,
 BUDAT TYPE BUDAT,
 WAERS TYPE WAERS,
 END OF TY_HEADER.
TYPES : BEGIN OF TY_ITEM,
 RECNO TYPE I,
 INDICATOR,
 NEWBS TYPE NEWBS,
 NEWKO TYPE NEWKO,
 WRBTR(16), " TYPE WRBTR,
 END OF TY_ITEM.
TYPES : BEGIN OF TY_TAB,
 F1,
 F2(10),
 F3(17),
 F4(17),
 F5(10),
 F6(5),
 END OF TY_TAB.
DATA : IT_HEADER TYPE TABLE OF TY_HEADER ,
 IT_ITEM TYPE TABLE OF TY_ITEM,
 WA_HEADER TYPE TY_HEADER,
 WA_ITEM TYPE TY_ITEM,
 IT_TAB TYPE TABLE OF TY_TAB,
 WA_TAB TYPE TY_TAB.
DATA : L_REC TYPE I,
 FLAG.
CONSTANTS : C_HTAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
DATA : FNAME TYPE STRING VALUE 'C:\TTT1.xls',
 L_FILE LIKE RLGRAP-FILENAME.
IF FNAME CS '.TXT'.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = FNAME
 FILETYPE = 'ASC'
 TABLES
 DATA_TAB = IT_F64.
PERFORM SPLIT_TEXT_TABLE TABLES IT_F64.
ELSEIF FNAME CS '.XLS'.
L_FILE = FNAME.
PERFORM UPLOAD_XLSFILE TABLES IT_TAB
 USING L_FILE.
PERFORM SPLIT_XLS_TABLE TABLES IT_TAB.
ELSEIF FNAME CS '.CSV' .
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = FNAME
 FILETYPE = 'ASC'
 TABLES
 DATA_TAB = IT_F64.
PERFORM SPLIT_CSV_TABLE TABLES IT_F64.
ENDIF.
*& Form UPLOAD_XLSFILE
 text
--> p1 text
<-- p2 text
FORM UPLOAD_XLSFILE TABLES P_TABLE
 USING P_FILE.
DATA : L_INTERN TYPE KCDE_CELLS OCCURS 0 WITH HEADER LINE.
DATA : L_INDEX TYPE I.
DATA : L_START_COL TYPE I VALUE '1',
 L_START_ROW TYPE I VALUE '1',
 L_END_COL TYPE I VALUE '256',
 L_END_ROW TYPE I VALUE '65536'.
FIELD-SYMBOLS : <FS>.
CALL FUNCTION 'KCD_EXCEL_OLE_TO_INT_CONVERT'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = L_START_COL
 I_BEGIN_ROW = L_START_ROW
 I_END_COL = L_END_COL
 I_END_ROW = L_END_ROW
 TABLES
 INTERN = L_INTERN
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
 FORMAT COLOR COL_BACKGROUND INTENSIFIED.
 WRITE : / 'File Error'.
 EXIT.
ENDIF.
IF L_INTERN[] IS INITIAL.
 FORMAT COLOR COL_BACKGROUND INTENSIFIED.
 WRITE : / 'No Data Uploaded'.
 EXIT.
ELSE.
 SORT L_INTERN BY ROW COL.
 LOOP AT L_INTERN.
 MOVE L_INTERN-COL TO L_INDEX.
 ASSIGN COMPONENT L_INDEX OF STRUCTURE P_TABLE TO <FS>.
 MOVE L_INTERN-VALUE TO <FS>.
 AT END OF ROW.
 APPEND P_TABLE.
 CLEAR P_TABLE.
 ENDAT.
 ENDLOOP.
ENDIF.
ENDFORM. " UPLOAD_XLSFILE
*& Form SPLIT_TEXT_TABLE
 text
 -->P_IT_F64 text
FORM SPLIT_TEXT_TABLE TABLES IT_F64 .
LOOP AT IT_F64 INTO WA_F64.
 IF WA_F64+0(1) = 'H'.
 SPLIT WA_F64 AT C_HTAB INTO WA_HEADER-INDICATOR
 WA_HEADER-BLDAT
 WA_HEADER-BLART
 WA_HEADER-BUKRS
 WA_HEADER-BUDAT
 WA_HEADER-WAERS.
 CLEAR FLAG.
 IF FLAG EQ SPACE.
 L_REC = L_REC + 1.
 WA_HEADER-RECNO = L_REC.
 FLAG = 'X'.
 ENDIF.
 APPEND WA_HEADER TO IT_HEADER.
 CLEAR WA_HEADER.
 ELSEIF WA_F64+0(1) = 'L'.
 SPLIT WA_F64 AT C_HTAB INTO : WA_ITEM-INDICATOR
 WA_ITEM-NEWBS
 WA_ITEM-NEWKO
 WA_ITEM-WRBTR.
 IF FLAG EQ 'X'.
 WA_ITEM-RECNO = L_REC.
 ENDIF.
 APPEND WA_ITEM TO IT_ITEM.
 CLEAR WA_ITEM.
 ENDIF.
ENDLOOP.
ENDFORM. " SPLIT_TEXT_TABLE
*& Form SPLIT_xls_TABLE
 text
 -->P_IT_TAB text
FORM SPLIT_XLS_TABLE TABLES IT_TAB .
LOOP AT IT_TAB INTO WA_TAB.
 IF WA_TAB-F1 = 'H'.
 WA_HEADER-INDICATOR = WA_TAB-F1.
 WA_HEADER-BLDAT = WA_TAB-F2.
 WA_HEADER-BLART = WA_TAB-F3.
 WA_HEADER-BUKRS = WA_TAB-F4.
 WA_HEADER-BUDAT = WA_TAB-F5.
 WA_HEADER-WAERS = WA_TAB-F6.
 CLEAR FLAG.
 IF FLAG EQ SPACE.
 L_REC = L_REC + 1.
 WA_HEADER-RECNO = L_REC.
 FLAG = 'X'.
 ENDIF.
 APPEND WA_HEADER TO IT_HEADER.
 CLEAR WA_HEADER.
 ELSEIF WA_TAB-F1 = 'L'.
 WA_ITEM-INDICATOR = WA_TAB-F1.
 WA_ITEM-NEWBS = WA_TAB-F2.
 WA_ITEM-NEWKO = WA_TAB-F3.
 WA_ITEM-WRBTR = WA_TAB-F4.
 IF FLAG EQ 'X'.
 WA_ITEM-RECNO = L_REC.
 ENDIF.
 APPEND WA_ITEM TO IT_ITEM.
 CLEAR WA_ITEM.
 ENDIF.
 CLEAR WA_TAB.
ENDLOOP.
ENDFORM. " SPLIT_xls_TABLE
*& Form SPLIT_CSV_TABLE
 text
 -->P_IT_F64 text
FORM SPLIT_CSV_TABLE TABLES IT_F64 .
LOOP AT IT_F64 INTO WA_F64.
 IF WA_F64+0(1) = 'H'.
 SPLIT WA_F64 AT '|' INTO WA_HEADER-INDICATOR
 WA_HEADER-BLDAT
 WA_HEADER-BLART
 WA_HEADER-BUKRS
 WA_HEADER-BUDAT
 WA_HEADER-WAERS.
 CLEAR FLAG.
 IF FLAG EQ SPACE.
 L_REC = L_REC + 1.
 WA_HEADER-RECNO = L_REC.
 FLAG = 'X'.
 ENDIF.
 APPEND WA_HEADER TO IT_HEADER.
 CLEAR WA_HEADER.
 ELSEIF WA_F64+0(1) = 'L'.
 SPLIT WA_F64 AT '|' INTO : WA_ITEM-INDICATOR
 WA_ITEM-NEWBS
 WA_ITEM-NEWKO
 WA_ITEM-WRBTR.
 IF FLAG EQ 'X'.
 WA_ITEM-RECNO = L_REC.
 ENDIF.
 APPEND WA_ITEM TO IT_ITEM.
 CLEAR WA_ITEM.
 ENDIF.
ENDLOOP.
ENDFORM. " SPLIT_CSV_TABLE

Problem While loading Master data from R/3

Hi All,
When i am trying to load masters data from R/3 datasources to BW Info objects in Info provider menu data is coming to PSA but going to dta targets. the data is matching with the data in R/ 3 but
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
Info IDoc 1 : sent, not arrived ; IDoc ready for dispatch (ALE service)
and error message says ERROR 4 in the update.
Can you please help me in this regard . Its Urgent.

Hi,
Check for pending IDOCS in BD87 or SM58 and execute them.
In RSMO, select the particular load you want to monitor.
In the menu bar, Environment >>> Transact. RFC >>> Select whichever is required, BW or Source System.
In the next screen you can select the Execute button and the IDOCS will be displayed.
Refer this Tcodes for IDOC status.
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDoc in Database
WE10 Search for IDoc in Archive
WE23 Verification of IDoc processing
IDOC
www.erpgenie.com/sapgenie/docs/ale_whitepaper.doc
Check Note 561880 - Requests hang because IDocs are not processed.
OR
Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
Thanks,
JituK

Having problem while uploading the data.

Hi All,
i am facing some problem when trying to upload csv file in the database.
ERROR:
"SQL*Loader-704: Internal error: ulconnect: OCIServerAttach [0]
ORA-12560: TNS:protocol adapter error".
have anybody aware of this kind of problem or having knowledge regarding this problem.database is working fine.
-rajnish

Hi,
About this error, you need to enable tracing and get the exact error from the listener trace files:
12560, 00000, "TNS:protocol adapter error"
// *Cause: A generic protocol adapter error occurred.
// *Action: Check addresses used for proper protocol specification. Before
// reporting this error, look at the error stack and check for lower level
// transport errors.For further details, turn on tracing and reexecute the
// operation. Turn off tracing when the operation is complete.Regards,
Yoann.

Problem while uploading master data through two files

Similar Messages

Maybe you are looking for