0PLANT_TEXT

Hi
I am trying to extract text data for 0PLANT object. so i have 0PLANT_TEXT datasource is the source system and when i loaded that to BW i am getting the data like this
Key     description
E              US01
E              US02
E               US50
actually it should be like this
Plant           TXTMD                  
US01                  atlanta               
0001                  chain
9999                   Dummy                  
BE01                  Belgium, Essen    
BE03                  Belgium, Turnhout 
when i check the datasource in R/3 it is giving the same.
but when i checked this in RS02 TEXT i can see that it is extracted from T001W_BIW view/Table. So i checked in that table in R/3 i can see the correct results.
like
MANDT    SPRAS    WERKS     TXTMD                        
100           E            US01                               
100           E            0001            atlanta
100           E            9999            chaina               
100           E             BE01           Belgium, Essen          
100           E             BE03           Belgium, Turnhout       
what is the reason ..why i am not seeing the correct results in R/3 in RSA3 or in BW?.
Thanks.
Naga,

Hi,
Where u checked the data, check once the data in 0plant.
Hope this helps u.....
Assigning points is the way of saying Thanks in SDN.
Regards,
Ramakrishna Kamurthy

Similar Messages

  • Transfer Structure Error

    Hi Guys,
    I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.
    Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130
    Message no. R3104
    Diagnosis
    An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .
    System response
    The action was terminated. No data was changed.
    Procedure
    Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.
    I am using PSA as the transfer method. Any help is appreciated.
    Thanks.

    Hi Govind,
    To implement what is said in the note IS VERY EASY!
    I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.
    So, here is a way to implement the program.
    - In the text tabstrip of the note click on 'Correction Instructions' tabstrip.
    - Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).
    - Click on a report name 'z_rs_scrsystem_r3_check'.
    - In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.
    - Enter program description, choose 'executable' option.
    - Into the screen of ABAP Editor copy-paste the code from the note correction instructions.
    - Click on 'Check', then 'Activate' icons.
    - If everything is OK, press F8 (execute).
    Then follow the note:
    "These programs have the following input parameters:
    SLOGSYS Specify the logical system name of your source system here
    RLOGSYS Specify the logical system name of the BW system here
    If you enter nothing here, all existing BW source system connections are processed.
    Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.
    2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.
    3. If the error continues to occur:
    Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.
    After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.
    We recommend that you use the PSA transfer method."
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov

  • Key mapping from vt100 to vt220

    my existing system is in forms3.0 and report writer3.0 with
    oracle 7.1 on aix 3.x with vt100 terminal
    now I have upgraded to forms and report developer 6i , oracle 8i
    on aix 4.3. as forms6i and report6i only supports vt220 , I have
    to map my vt100 key functionality to vt220 terminal.
    is there any utility for doing this ??
    can i do it using oraterm or any other utility is ther??

    dear Joseph,
    you can use datasource 0plant_text, 0plant_attr and 0material_text and 0material_attr to extract r/3 material and plant to bw. they are using view to access mara and lfa1.
    logon to r/3 and tcode rsa5, choose application component LO-IO, and transfer these datasources,
    then from bw, rsa1->source system->r/3 source system->right click 'datasource overview' and go to the same application component node, and 'replicate datasource'.
    then rsa1->infosource and locate 0material and 'assign datasource', choose r/3 source system and datasource 0material_text and 0material_attr. do the same for 0plant.
    the other way is through business content activation, using infoobject 0material and 'in dataflow before'.
    hope this helps.

  • Error installing business content update rules

    Hi,
    I'm trying to install the below updates rules from the business content
    0PLANT$T 0PLANT_TEXT      53AFFWD74OI3CT3RDE3RI9THU
    0PLANT 0PLANT_ATTR         5UZVD7UWYN4T81H24YBKGH6KY
    I get the error
    IC=0PLANT$T IS=0PLANT_TEXT syntax error:  rows 0
    Long Text:
    IC=0PLANT$T IS=0PLANT_TEXT syntax error:  rows 0
    Message no. RSAU466
    Diagnosis
    When generating the update program for InfoProvider 0PLANT$T, InfoSource 0PLANT_TEXT, a syntax error in line 0.
    System Response
    The update rules cannot be activated.
    Procedure
    If error message :
    is cut off, proceed as follows to get the complete complete error message:
    Go into update rule maintenance, choose Extras -> Display Activated Program and perform a syntax check. This allows you to find out what the error is.
    If I select the Display Activated Program it says does not exist.
    Can anyone help me figure out this issue?
    Thanks

    We are currently on SAP EHP 1 for SAP NetWeaver 7.0
    SAP_BW Release 701 Support Package SAPKW70107
    BI_CONT Release 705 Support Package SAPK-70501INBICONT

  • Regarding Master Data loading In BI 7.0 for  SD Module

    Hi Guys ,
    Iam new to BI 7.0 Impln.Can anybody  help me how to load the Master data for cubes like 0sd_c01,0sd_c03.I have activated the MD ds like 0Plant_Attr,0Plant_Text,0Master_attr,0master_text and replicated into BI 7.0.After that i need help from u guys.what are the steps required to activate the Masterdata.
    thanks,
    Chinnu

    Hi Chinnu,
    1)By replication I think you mean to say that you now have the datasources 0Plant_Attr,0Plant_Text,0Master_attr,0master_text in BW now.
    2)You then have to complete the mapping to the corresponding Infosources
    3) activate the infoobjects 0PLANT, 0Master.
    4)Load your master data
    regards,
    Vinay

  • R/3 Plug-In for NW04s

    Hi,
    Currently, we are on PI_BASIS Level 8 (SAPKIPYI58)in our R/3 system and our R/3 was just recently unicoded as well.  What level should we be at for NW04s? 
    Also, we are getting a short dump in R/3 when doing a simple plant text extraction (0PLANT_TEXT).  This is failing in R/3 as the language field is not getting populated.  When the language is made a selection field, the extract (Txn RSA3) is actually short dumping R/3.  Does anyone have any insight into this?
    My feeling is that the unicoding created this additional language field in the extract structure and also not being on the correct Plug-in might be creating some issues.  Any help is appreciated.
    Thanks
    Senthil

    It is certainly due to an inconsistency between the structures on R/3 and BW.
    Please check if your 0plant_text datasource (in RSO2) has LANGU or SPRAS field, it should not be there (same with table T001w_biw).
    You will also need to remove such field if it is there, on BW in the infosource. And, make sure 0PLANT infoobject , text tab, the language-dependent flag is unchecked. You will have to activate, replicate and do extraction again.
    I am not sure, it could be that an upgrade might not have changed the structure the way it was supposed to (earlier versions had language field in the extraction, which is no more there in newer versions).
    It may have nothing to do with unicode, I think.

  • I want to learn abt datasources.. pl tel some datasources in sd, mm, pp

    Pl tel some datasources for sd, mm, pp ...
    and tel me where to find the datasource...
    with example...

    HI
    SD     
    2LIS_HT_DR0DRM                    DRM Business Matrix     
    2LIS_HT_MS0DRM                    DRM: MS Business Matrix     
    2LIS_13_VDKON                     Billing Document Condition     
    2LIS_13_VDITM                     Billing Document Item Data     
    2LIS_13_VDHDR                     Billing Doc. Header Data     
    2LIS_01_S001                      Customer     
    2LIS_01_S005                      Shipping point     
    2LIS_01_S264                      SD- Offer     
    2LIS_08TRFKP                      Shipment Costs at Item Level     
    2LIS_08TRFKZ                      Shipment Costs at Delivery Item Level     
    2LIS_08TRTK                       Shipment: Header Data     
    2LIS_08TRTLP                      Shipment: Delivery Item Data by Section     
    2LIS_08TRTS                       Shipment: Section Data     
    2LIS_11_VAHDR                     Sales Document Header Data     
    2LIS_11_VAITM                     Sales Document Item Data     
    2LIS_11_VAKON                     Sales Document Condition     
    2LIS_11_VASCL                     Sales Document Schedule Line     
    2LIS_11_VASTH                     Sales Document Header Status     
    2LIS_11_VASTI                     Sales Document Item Status     
    2LIS_11_V_ITM                     Sales-Shipping Allocation Item Data     
    2LIS_11_V_SCL                     Sales-Shipping Allocation Schedule Line     
    2LIS_11_V_SSL                     Sales Document Order Delivery     
    2LIS_12_VCHDR                     Delivery Header Data     
    2LIS_12_VCITM                     Delivery Item Data     
    2LIS_12_VCSCL                     Sales-Shipping Schedule Line Delivery     
    QM     
    2LIS_05_QVUDN                     Inspection Lot/Usage Decision     
    2LIS_05_QE2                       Inspection Result: Quantitative Data     
    2LIS_05_QE1                       Inspection Result: General Data     
    2LIS_05_Q0TASK                    Quality Notifications - Tasks     
    2LIS_05_Q0NOTIF                   Quality Notifications     
    2LIS_05_Q0ITEM                    Quality Notifications - Items
    2LIS_05_Q0CAUSE                   Quality Notifications - Causes
    2LIS_05_Q0ACTY                    Quality Notifications - Activities
    PM
    0PM_OM_OPA_1                      Maintenance Orders: Costs and Allocations
    0PM_OM_OPA_2                      Maintenance Orders: Actual Costs by Means of Delta Extract.
    0PM_OM_OPA_3                      Maintenance Orders: Commitmt Line Items
    0PM_PRM_PLCS_1                    Planned Costs Maintenance
    2LIS_17_I3HDR                     Plant maintenance orders
    2LIS_17_I0TASK                    Maintenance Notifications - Tasks
    2LIS_17_I0NOTIF                   Maintenance Notifications
    2LIS_17_I0ITEM                    Maintenance Notifications - Items
    2LIS_17_I0CAUSE                   Maintenance Notifications - Causes
    2LIS_17_I3OPER                    Plant Maintenance Order Process
    2LIS_17_I0ACTY                    Maintenance Notifications - Activities
    0PM_MEASUREMENT                   Measuring Points and Measurement Documents
    0PM_DSMNTL                        Plant Maintenance - Equipment Dismantling
    MM
    2LIS_03_S195                      Material movements: storage location
    2LIS_02_S011                      Purchasing groups
    2LIS_02_S012                      Purchasing
    2LIS_02_S013                      Vendor Evaluation
    2LIS_02_S015                      Subsequent Settlement: Evaluation
    2LIS_02_S174                      Services
    2LIS_02_SCL                       Purchasing Data (Schedule Line Level)
    2LIS_02_SCN                       Produced Activity: Confirmation of Schedule Lines
    2LIS_02_SGR                       Produced Activity: Delivery of Schedule Lines
    2LIS_06_INV
    0MM_PUR_VE_02                     Vendor Evaluation Semiauto
    2LIS_03_BF                        Goods Movements From Inventory Management
    2LIS_03_BX                        Stock Initialization for Inventory Management
    2LIS_03_S091                      WM: Quantity flows
    2LIS_03_S194                      MRP: Business Info Warehouse
    0MM_PUR_VE_01                     Vendor evaluation
    2LIS_02_ITM                       Purchasing Data (Item Level)
    0CO_PC_ACT_07                     Material Valuation: Prices - Project Stocks
    0CO_PC_ACT_06                     Material Valuation: Prices - Sales Order Stocks
    0CO_PC_ACT_05                     Material Valuation: Prices
    0CO_PC_ACT_04                     Material Valuation: Per. Ending Inventory Project Stocks
    0CO_PC_ACT_03                     Material Valuation: Per. Ending Inventory Sales Order Stocks
    0CO_PC_ACT_02                     Material Valuation: Per. Ending Inventory
    2LIS_03_UM                        Revaluations
    2LIS_03_S198                      Periodic plant stock
    2LIS_02_HDR                       Purchasing Data (Header Level)
    2LIS_02_CGR                       Produced Activity: Delivery of Confirmations
    0SR_VE_INT_IV                     Vendor Evaluation in Invoice Verification (ECC)
    2LIS_03_S196                      Goods movement: Plant
    2LIS_03_S197                      Periodic storage location stock
    2LIS_02_ACC                       Purchasing Data (Account Level)
    LO
    0CUST_SALES_ATTR                  Customer number
    0CUST_SALES_LKDH_HIER             Customer number
    0CUST_SALES_TEXT                  Customer Number
    0CUST_SALES_TID_LKDH_HIER         Customer number (Time-Independent)
    0ART_ST_LOC_ATTR                  Article Number Compounded with Plant and Storage Location
    0ARTICLE_ATTR                     Article Number
    0ART_SALES_ATTR                   Article Number Compounded with Sales
    0ARTICLE_TEXT                     Article Number
    0ART_PLANT_ATTR                   Article Number Compounded with Sales
    0CUST_COMPC_TEXT                  Customer Number Compounded with Company Code
    0MATERIAL_TEXT                    Material Number
    0MAT_KONDM_TEXT                   Text DataSource for Field KONDM (Material Group)
    0MAT_PLANT_ATTR                   Material Number with Plant
    0MAT_PLANT_TEXT                   Material number with plant
    0MAT_SALES_ATTR                   Material number with sales
    0MAT_SALES_LPRH_HIER              Material Number Compounded to Sales
    0MAT_SALES_TEXT                   Material number with sales
    0MAT_ST_LOC_ATTR                  Material Number Compounded to Plant and Storage Location
    0MAT_ST_LOC_TEXT                  Material Number Compounded to Plant and Storage Location
    0MAT_UNIT_ATTR                     Material: Unit Conversion
    0PROD_HIER_LPRH_HIER              Material number
    0PLANT_ATTR                       Plant
    0PLANT_LKLS_HIER                  Plant
    0PLANT_TEXT                       Plant
    0CUST_COMPC_ATTR                  Customer Number Compounded with Company Code
    0CUSTOMER_TEXT                    Customer number
    0CUSTOMER_LKLS_HIER               Customer number
    0CUSTOMER_ATTR                    Customer Number
    0USAGE_IND_TEXT                   Usage Indicator Material
    0VEN_ACCNT_GRP_TEXT               Vendor account group
    0VEN_COMPC_ATTR                   Vendor Number Compounded to Company Code
    0VEN_COMPC_TEXT                   Vendor Number Compounded to Company Code
    0VEN_PURORG_ATTR                  Vendor Number
    0MATERIAL_ATTR                    Material Number
    0VEN_PURORG_TEXT                  Vendor Number
    0MATERIAL_LGEN_HIER               Material number
    0MATERIAL_LKLS_HIER               Material number
    0MATERIAL_LPRH_HIER               Material number
    PP
      2LIS_04_PEMATNR                   Repetitive Manufacturing Material View
      2LIS_04_PECOMP                    Repetitive Manufacturing Component View
      2LIS_04_PEARBPL                   Reporting Points for Repetitive Manufacturing
      2LIS_04_P_ARBPL                   Work Center View from PP/PP-PI
      2LIS_04_P_COMP                    Component View from PP/PP-PI
      2LIS_04_P_MATNR                   Material View from PP/PP-PI
      0PP_WCCP                          PP(PI)Work Center Capacity
      0PP_DOWNTIME                      Resource Downtimes
    PS
    0PS_CLM_CST                       Claim Costs
    0PS_ORD_EVA                       Progress in Orders
    0PS_KAP_NAE                       Extraction of Capacity Requirements for Activity Element
    0PS_NWA_EVA                       Progress in Network Activities
    0PS_NTW_EVA                       Progress in Networks
    0PS_NAE_EVA                       Progress in Network Activity Elements
    0PS_CSH_NTW                       Network Plan Payments
    0PS_CSH_NWA                       Payments on Network Plan Process
    0PS_CSH_ORD                       Payments on Orders
    0PS_DAT_WBS                       WBS Element Dates
    0PS_DAT_PRJ                       Date Project
    0PS_WBS_EVA                       Progress in WBS Elements
    0PS_KAP_NWA                       Extraction of Capacity Requirements for Network Activity
    COPA_Master
    0DESTINATION_TEXT                 Trip Destination
    0AIRCRAFT_TYPE_TEXT               Aircraft Type
    0ROTATION_TEXT                    Rotation
    0BRAND_TEXT                       Brand
    0BUSFIELD_TEXT                    Business field
    0STRBUSUNIT_TEXT                  Strategic Business Unit
    0ZONE_TEXT                        Zone
    0ORIGIN_TEXT                      Departure Location
    0DAY_OF_OPERATION_TEXT            Day of Operation
    0TRANSPORT_TEXT                   Shipment Type
    0IATA_SEASON_TEXT                 IATA Season
    0REC_TYPE_TEXT                    Activity type
    0FLIGHT_NO_TEXT                   Flight Number
    0LEG_TEXT                         Route Segment
    0MAINMATGRP_TEXT                  Main Material Group

  • Master Data Mappings

    Hi All,
    I am trying to map the Datasource to master data InfoObject
    The way I did it for 0PLANT_TEXT is:
    Right click on the 0PLANT transfer rule and "create transformation"
    This pops up the message to either copy Infosource or use the current.
    I created a ZPLANT_TEXT infosource and activated that (some routine was a problem while activation and I deactivated the routine)
    I then migrated the datasource successfully >created infopackage>created DTP
    Is that the right approach?
    In BW3.5 this was pretty quick, if I am activating 50 master data objects that would take a lot of time?
    I can now see two update rules one is Z update rule for 0PLANT and the other one is the business content. Is it ok to delete to business content one.Why do we need to copy the Infosource??
    Thanks,
    Gaurav

    Is that the right approach? - yeah sure it is
    I can now see two update rules one is Z update rule for 0PLANT and the other one is the business content.
    Yeah actually there are not two update rules, infact one is update rule and the other is transformation. You can now delete the old update rule(3.x)
    Is it ok to delete to business content one.
    Yeah it is ok. If you dont want to, you can keep the update rule and never use, but whats the use, go ahead and delete it.
    Why do we need to copy the Infosource??
    The old is a 3.x infosource and that IS is being used by the object in the update rules. So you would need to create a new infosource. Even when you create a new infosource you have 2 options, 3.x or a 7.0 one.

  • Cannot transport transfer rules!

    Hi,
    We have a problem transporting the transfer rules from BWD to BWQ.
    Here are the steps I did :
    New object ZZRANK was added to user exit on R/3 dev. and transported
    New infor object ZZRANK was created in BWD
    ZZRANK was added as attribute to 0PLANT (mater data)
    Transfers were created and comm struc updated.,  
    testing was successful in Dev,  r3 changes were transported to Q and BWD transports to BWQ.  ALL info objects transported successfull but the transfer rules failed.  Cannot determine why.,
       Start of the after-import method for object type R3TR ISMP (Activation Mode)
       Mapping between data source 0PLANT_ATTR and source system PR2200LS is inconsistent
       Field ZZRANK will not be delivered from DataSource 0PLANT_ATTR in source system PR2200LS
       Mapping between data source 0PLANT_TEXT and source system PR2200LS is inconsistent
       Field KEY1 will not be delivered from DataSource 0PLANT_TEXT in source system PR2200LS
       Errors occurred during post-handling RS_AFTER_IMPORT for ISMP L
       The errors affect the following components:
          BW-WHM (Warehouse Management)
    Any help is appreciated.

    You may have to replicate your data source on BWQ.
    First replicate and then send your transport again from BWD to BWQ.
    Regards.
    Sanjay
    Message was edited by:
            Sanjay Sinha

  • Unable to activate transformation, error generating program

    Hi,
    We are currently on SAP EHP 1 for SAP NetWeaver 7.0
    SAP_BW Release 701 Support Package SAPKW70107
    BI_CONT Release 705 Support Package SAPK-70501INBICONT
    When I try to activate my transformation between 0PLANT and infosource ZPLANT_TEXT(Generated from 3.x infosource 0PLANT_TEXT), I get the below error message
    Syntax error in GP_MET_RSTRAN_MASTER_TMPL, row 0 (-> long text)
    Error during generation(Message no. RSTRAN511)
    Error when resetting Transformation 06L8E7JA476EMLRHOX35W9KX6TMS8XSX to the active version(Message no. RSO410)
    Long Text:
    Syntax error in GP_MET_RSTRAN_MASTER_TMPL, row 0 (-> long text)
    Message no. RG102
    Diagnosis
    SQL error 1654 occurred when accessing program GP_MET_RSTRAN_MASTER_TMPL part LREF.
    When  I check for the program GP_MET_RSTRAN_MASTER_TMPL in SE38 is does not exist.
    Can anyone help me figure out this problem?
    Thanks

    I ran the program RS_TRANSTRU_ACTIVATE_ALL with below parameters
    Source System = <logical system name of our src system>
    InfoSource (* gen) = 0PLANT_TEXT
    Got the error message as
    Error generating program
    Error generating program
    Transfer structure 0PLANT_TEXT_DC NOT activated successfully Activate manually
    Long Text:
    Message no. RSAR245
    Diagnosis
    An error occurred during program generation:
    Template:   RSTMPL80
    Error code: 6
    Row:        0
    Message:
    Procedure
    Correct the template to remove the problem.
    Incase I give the InfoSource (* gen) = ZPLANT_TEXT
    I get the message
    No Transfer Structure Selected

Maybe you are looking for