Reg: Table creation for generic source

Hai,
I tried to create generic data source using a table that I created. But when I tried to enter entries into the table using se16 transaction, one field is not at all coming.
I didnt understand why this field is not coming. I checked the enhancement category, but that is allowing too.. I changed the position of that field in the table and tried. But still its not coming in se16 create entries..
What can be the problem. When we check the table in se12, that field we able to see.. When we check through se16 also its available. Only when we want to make entries its not coming..
Can someone help me to resolve this issue..

Hi,
Yes I am able to see the filed in the data source also.
I want to do flat file loading. So I am using LSMW recording for the same. So in se16 i need to create dummy entries. But as this filed is not coming, I cant populate.
When i tried outside lsmw also in SE16 that filed is not there.

Similar Messages

FUNCTION MODULE CREATION FOR GENERIC DATA SOURCE

Hi BI gurus,
I am creating function module for generic datasource. For that I followed below mentioned steps
Steps
1.     Created s structure with the fields that needed.
2. Created FM by copying the standard Function module
" RSAX_BIW_GET_DATA_SIMPLE " and Give a New name starting With
Y or Z .
3. IN SE37 ->Your Function module name -> Change, In table tab given structure
name by deleting the associated type given in E_T_DATA .
And inserted the required code given below
      PROGRAM 'ZHU_BALANCE'.
*& Report ZHU_BALANCE
TABLES: VEKP, VEPO.
DATA: BEGIN OF T_DISPLAY,
      DATE   LIKE SY-DATUM,
      EXIDV LIKE VEKP-EXIDV,
      LGORT LIKE VEPO-LGORT,
      WERKS LIKE VEKP-WERKS,
      END OF T_DISPLAY.
DATA: ITAB_DISPLAY LIKE TABLE OF T_DISPLAY.
DATA: WA_ITAB_DISPLAY LIKE LINE OF ITAB_DISPLAY.
SELECT VEKPEXIDV VEPOLGORT VEPO~WERKS
       INTO CORRESPONDING FIELDS OF TABLE ITAB_DISPLAY
       FROM VEKP AS VEKP INNER JOIN VEPO AS VEPO
         ON VEKPVENUM = VEPOVENUM
         AND VEKPWERKS = VEPOWERKS
       WHERE VEKP~VSTEL = SPACE
         AND VEKP~VEGR1 = '401'
         AND VEKP~VPOBJ = '12'
         AND VEKP~STATUS = '0020'
         AND VEPO~VEPOS = '000001'.
LOOP AT ITAB_DISPLAY INTO WA_ITAB_DISPLAY.
WA_ITAB_DISPLAY-DATE = SY-DATUM.
MODIFY ITAB_DISPLAY FROM WA_ITAB_DISPLAY TRANSPORTING DATE.
ENDLOOP.
WRITE:/ 'DATE', 20 'EXIDV', 40 'LGORT', 60 'WERKS'.
ULINE.
LOOP AT ITAB_DISPLAY INTO WA_ITAB_DISPLAY.
WRITE:/ WA_ITAB_DISPLAY-DATE, 20 WA_ITAB_DISPLAY-EXIDV , 40 WA_ITAB_DISPLAY-LGORT, 60 WA_ITAB_DISPLAY-WERKS.
ENDLOOP.
While checking the function module its populating the syntax error as
THE TYPE SRSC_S_IF_SIMPLE IS UNKOWN. (Though this is commented in program)
So pls suggest
Regards,
praful

hi indira,
thanx for ur reply we have created the funcion module successfuly it is also showing the output correct. But when we put that function module in the generic data source and try to extract data in RSA3 it shows the correct output of function module but with the msg ' 0 entries found in customer enhancement' and therfore zero records in the display list.
is there any correction or steps to be followed in data extraction
pls suggest
regards,
praful

Reg View creation in Generic

Hi SDN,
Im trying to create Generic Data source of View Method. I wanted to create View on BSID ( Closed Customer Invoices) and BSAD ( Open Customer invoices) Tables, But while creating its giving error as "THERE IS NO RELATION BETWEEN THE TABLES" I want to know how to create Relation Between the tables. Both BSID & BSAD are standard tables, so we cant make any changes.
Please let me know the procedure to bulid Rlation between the tables.
Regards
Sujan

Hi Siva,
You have to give relation between these two tables in tab "Table/Join Conditions".
Creating Views:
http://help.sap.com/saphelp_webas620/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
View creation fr generic extraction
Hope it Helps

Merchandise Category creation for Generic Article in SAP IS-Retail

Hi,
Can anyone help me out to with clear and complete process and settings i have to maintain for merchandise category for generic article for shoes of our client. I created merchandise category with the below transaction codes
ct04,clwe,clwe,clw1 and wg21 but when i used to create generic article i have to find characteristics in variants tab in basic data view in mm41 but i didn't find it.
HELP ME with SCREENSHOTS which will HELP ME in FUTURE of our CLIENT
Thanks & Regards
Gopi Krishna
Mobile:+91 9741042296

Hi Manish,
Thank you for your reply which is the procedure for relevance of variants in creation of generic article.My concern is to know complete merchandise category creation with screenshots which i can create by own merchandise category.
Thanks & Regards
Gopi Krishna Potteti

REG:USER EXIT FOR DATA SOURCE 0HR_LSO_1

Hi ,
I have to write the enhancement ABAP code for data source 0HR_LSO_1 which is related to module " training and event management "(also known as LMS or LSO) in ECC 6.0 .
So how can I find out appropriate user exit for the same .I have to concentrate on the field "kostl (cost centre)" in that data source .
Please provide some suggestions .
Thanking You ,
Tarun Brijwani .

Hi Tarun...
I this might help you.
In the HR System:
1) T-CODE: CMOD
2) Choose an existing project (vg: Z12345)
3) Modify
4) Press Components button
5) Look for the enhance: RSAP0001 (the BW extracting enhancement)
6) The you have one of the following option:
a- If the Data Source is "transaction data": The exit is "EXIT_SAPLRSAP_001"
b- If the Data Source is "master data": The exit is "EXIT_SAPLRSAP_002"
7) double-click in the appropriate one
8) You'll see an INCLUDE sentence. Could be this ZXRSAU01 or this ZXRSAU02 (depending on the previous step). Double-click and you'll be redirected to the SE38
9) some code:
CASE i_datasource
WHEN '0HR_LSO_1'.
    LOOP i_t_data INTO my_struct
       my_struct-KOSTL           "Here you'll must have your Cost Center
       ...etc...etc...etc
    ENDLOOP.
WHEN OTHERS.
ENDCASE
Hope it helps.
gdmon

Datasource Creation for Informatica Source system in NW2004s

Hi,
We are upgrading BW 3.5 to SAP NW2004s. In NW2004s Create datasource
is new feature provided in BW 7.0.
I tried to create this datasource for Flat file and worked fine. We
are also using Informatica as source system (External System).
Whenever I tried to create datasource for External system such as
Informatica, it gives message
"Datasource ZTEST(INFPCPD):Object Type RSDS not supported in BAPI
Source System"
Is it a bug? or Creation of datasource is not supported incase of
Informatica or external system?
Thanks
Rupesh

Hi Rupesh,
The latest BI release in SAP NetWeaver 7.0 (2004s) includes a new type of DataSource for which staging BAPI has not yet been aligned.
Third party ETL tool vendors can therefore only implement their load processes using the original type of DataSource from BW 3.x. This DataSource is still provided in the new release without any changes. Upgrading to NetWeaver 7.0 (2004s) BI (BI 7.0) does not therefore endanger existing implementations based on BW 3.x and NetWeaver 2004 (BW 3.5).
It is also possible to migrate third party ETL implementations based on BW 3.x into the new data-flow concept of a NetWeaver 7.0 (2004s) BI environment using new DataSources, transformations (also new), and data transfer processes (DTP) (also new). This is possible because the system provides an emulated view for BW 3.x DataSources, which makes it possible to combine them with NetWeaver 7.0 (2004s) transformations and DTPs for regular batch load processing (this does not include direct access and real-time data acquisition (RDA)).
This allows the benefits of the new data loading concept to be made available in such third party ETL-based loading scenarios.
Regards,
Anil

WF_DEFERRED_QUEUE_M table creation for 11g

We are trying to create WF_DEFERRED_QUEUE_M after upgrade to 11g from 10g
For table WF_DEFERRED_QUEUE_M with
compatible parameter 8.0 works to create the table but refuses to create the queue.
compatilble parameters 8.1 and 10.0 give “object already exists”
all of the compatible parameters work if we specify MULTIPLE_CONSUMERS = FALSE
Please help how do we create WF_DEFERRED_QUEUE_M table with option of MULTIPLE_CONSUMERS=TRUE for 11g
(workflow background process program is failing with error of ORA-24039: Queue WF_DEFERRED_QUEUE_M not created in queue table for multiple consumers)

What is the application release?
We are trying to create WF_DEFERRED_QUEUE_M after upgrade to 11g from 10gHow? Are you using the script in (Workflow Queues Creation Scripts [ID 398412.1])?
For table WF_DEFERRED_QUEUE_M with
compatible parameter 8.0 works to create the table but refuses to create the queue.
compatilble parameters 8.1 and 10.0 give “object already exists”WF_DEFERRED_QUEUE_M is a queue -- http://etrm.oracle.com/pls/trm11510/etrm_pnav.show_object?c_name=WF_DEFERRED_QUEUE_M&c_owner=APPLSYS&c_type=QUEUE
all of the compatible parameters work if we specify MULTIPLE_CONSUMERS = FALSE
Please help how do we create WF_DEFERRED_QUEUE_M table with option of MULTIPLE_CONSUMERS=TRUE for 11g
(workflow background process program is failing with error of ORA-24039: Queue WF_DEFERRED_QUEUE_M not created in queue table for multiple consumers)Have you reviewed these docs (assuming you use the right script to create this queue)?
USING SINGLE-CONSUMER QUEUE CAUSES ORA-24039 [ID 1301605.1]
How to Resolve ORA-24039 on DBMS_AQADM.ADD_SUBSCRIBER [ID 98007.1]
Thanks,
Hussein

Best Practice Table Creation for Multiple Customers, Weekly/Monthly Sales Data in Multiple Fields

We have an homegrown Access database originally designed in 2000 that now has an SQL back-end. The database has not yet been converted to a higher format such as Access 2007 since at least 2 users are still on Access 2003. It is fine if suggestions
will only work with Access 2007 or higher.
I'm trying to determine if our database is the best place to do this or if we should look at another solution. We have thousands of products each with a single identifier. There are customers who provide us regular sales reporting for what was
sold in a given time period -- weekly, monthly, quarterly, yearly time periods being most important. This reporting may or may not include all of our product identifiers. The reporting is typically based on calendar-defined timing although we have
some customers who have their own calendars which may not align to a calendar month or calendar year so recording the time period can be helpful.
Each customer's sales report can contain anything from 1,000-20,000 rows of products for each report. Each customer report is different and they typically have between 4-30 columns of data for each product; headers are consistently named. The
product identifiers included may vary by customer and even within each report for a customer; the data in the product identifier row changes each week. Headers include a wide variety of data such as overall on hand, overall on order, unsellable on hand,
returns, on hand information for each location or customer grouping, sell-through units information for each location or customer grouping for that given time period, sell-through dollars information for each location or customer grouping for that given time
period, sell-through units information for each location or customer grouping for a cumulative time period (same thing for dollars), warehouse on hands, warehouse on orders, the customer's unique categorization of our product in their system, the customer's
current status code for that product, and so on.
Currently all of this data is stored in a multitude of Excel spreadsheets (by customer, division and time period). Due to overall volume of information and number of Excel sheets, cross-referencing can take considerable time. Is it possible to
set-up tables for our largest customers so I can create queries and pivot tables to more quickly look at sales-related information by category, by specific product(s), by partner, by specific products or categories across partners, by specific products or
categories across specific weeks/months/years, etc. We do have a separate product table so only the product identifier or a junction table may be needed to pull in additional information from the product table with queries. We do need to maintain
the sales reporting information indefinitely.
I welcome any suggestions, best practice or resources (books, web, etc).
Many thanks!

Currently all of this data is stored in a multitude of Excel spreadsheets (by customer, division and time period). Due to overall volume of information and number of Excel sheets, cross-referencing can take considerable time. Is it possible to
set-up tables .....
I assume you want to migrate to SQL Server.
Your best course of action is to hire a professional database designer for a short period like a month.
Once you have the database, you need to hire a professional DBA to move your current data from Access & Excel into the new SQL Server database.
Finally you have to hire an SSRS professional to design reports for your company.
It is also beneficial if the above professionals train your staff while building the new RDBMS.
Certain senior SQL Server professionals may be able to do all 3 functions in one person: db design, database administration/ETL & business intelligence development (reports).
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Reg Table name for Menu / Form Details

What is the Table name having the Menu name and Menu ID details for all modules?

Hi,
AFAIK this information is not stored in the database, appart from a fiew that are in the OADM table (PorName, RpdName, PdnName...). I think that this info is stored in a C++ library (don´t remember the name now).
Perhaps if you ask what the objetive is we could help you with a workaround.
Regards,
Ibai Peñ

Reg:challan creation for 701 movement type

Dear All,
Is there any possibility to create challan referring to the 701 movement type I've included the movement type for sub transaction type in SPRO but even then it is not allowing is there any possibility ?
Reg
VVK

Hi
U can create challan for 701 mvt.
Make sure the mvt 701 is included in subcontracting issues group type with spl stock indicator O.
make sure all other settings for subcontracting are correct like number ranges for series group of subcontracting, excise a/c for 57fc with subtrabsaction 01.
Check and revert with the problem u face bcoz i tried in my system and it worked.
Reg
Raja

Condition Table creation for Taxes (TAXINN)

I want to create a condition table for Taxing procedure with application <b>TX</b> with the following fields : <b>Plant , Control Code</b>
Kindly tell me the SPRO path where i can create a condition table for Taxes.
Regards
Jyotsna

Dear Jyotsna,
We can create taxes in two ways.one is FICO side and another one is SD side
in FICO side you can do in FTXP
in SD you can do OVK1
hope this helps you
Prem.

Reg : object creation for controller and view ?

hi friends....
i am new to WDA and objects...
please explain me..
when i create the web dynpro component one interface is automatically created as IF_COMPONENTCONTROLLER for component
IF_MAINVIEW for view
IF_WINDOW for window
correct me if i am wrong
suppose if i want to reuse class, i want to create object... like wise
if i want to reuse interfaces, i want to create object.
but in this case..for eg (IF_COMPONENTCONTROLLER, IF_MAINVIEW ) where we are creating object...?
no need to create object ?
regards
deva

>but in this case..for eg (IF_COMPONENTCONTROLLER, IF_MAINVIEW ) where we are creating object...?
no need to create object ?
No you don't have instantiate any of the objects. Think of Web Dynpro as a modeling layer implemented in ABAP Objects, but sitting on top of the Object Oriented constructs. You still have some of the benfiits of OO - like event registration, inheritance, methods, etc - but a lot of the OO setup is done and maintained by the framework for you. So although each section of Web Dynpro - the component, the controllers, contexts, views, etc - are all technically ABAP Object instances, you don't have to manage the objects directly.

File creation for Generic Withholding Tax Reporting : amounts are zero

Hi,
I try to use the program RFIDYYWT to create the file for witholding tax reporting for France
The format tree DMEE IDWTFILE_FR_DAS2.
I have succeeded to create a file, with the correct format/layout (so a 10, 20, 210, 30, and 31 structure), but the amounts are all equal to zero in the fle generated compared to the result on the screen after execution of the program.
Does anybody knows the solution for this problem ?
Thanks a lot.

Hi Wayne,
We opened a note with SAP and were told that a US 1042s copy could not be used within the standard system. Looking into it further we found that the form name was coded into a selection program. We had an ABAP developer add code that allows us to use a "Z_" copy form.
Regards,
Gregg

External Table Creation for .dat file

Hi,
I have created an External Table, below is the code
CREATE TABLE "NFO_DATA_LOAD_STAGING_TEST1"
   (     "DATA_DISCRAPANCY" VARCHAR2(100),
     "APPLICATION_NUMBER" VARCHAR2(30),
     "BATCH_NUMBER" VARCHAR2(30),
     "AMC_ID" VARCHAR2(30),
     "TA_BRANCH" VARCHAR2(30),
     "SERVER_DATE_1" DATE,
     "SERVER_TIME_1" DATE,
     "ARN_NUMBER" VARCHAR2(30),
     "BROKER_CODE" VARCHAR2(30),
     "SUB_BROKER_CODE_1" VARCHAR2(30),
     "SUB_BROKER_CODE_2" VARCHAR2(30),
     "SUB_BROKER_CODE_3" VARCHAR2(30),
     "BROKER_ADDRESS" VARCHAR2(100),
     "FOLIO_NO" NUMBER,
     "MODE_OF_HOLDING" VARCHAR2(30),
     "STATUS" VARCHAR2(30),
     "SALUATION" VARCHAR2(30),
     "CONTACT_PERSON_NAME" VARCHAR2(30),
     "INVESTOR_NAME" VARCHAR2(30),
     "GUARDIAN_NAME" VARCHAR2(30),
     "PAN_NO" VARCHAR2(30),
     "POA_HOLDER_NAME" VARCHAR2(30),
     "KYC" VARCHAR2(30),
     "GUARDIAN_PAN_NO" VARCHAR2(30),
     "DOB_DOC" DATE,
     "GUARDIAN_RELATIONSHIP" VARCHAR2(30),
     "SALUATION_2" VARCHAR2(30),
     "DATE_OF_BIRTH" DATE,
     "SECOND_HOLDER_NAME" VARCHAR2(30),
     "GUARDIAN_NAME_2" VARCHAR2(30),
     "PAN_NO_2" VARCHAR2(30),
     "GUARDIAN_PAN_NO_2" VARCHAR2(30),
     "KYC_2" VARCHAR2(30),
     "GUARDIAN_RELATIONSHIP_2" VARCHAR2(30),
     "SALUATION_3" VARCHAR2(30),
     "DATE_OF_BIRTH_3" DATE,
     "THIRD_HOLDER_NAME" VARCHAR2(30),
     "GUARDIAN_NAME_3" VARCHAR2(30),
     "PAN_NO_3" VARCHAR2(30),
     "GUARDIAN_PAN_NO_3" VARCHAR2(30),
     "KYC_3" VARCHAR2(30),
     "GUARDIAN_RELATIONSHIP_3" VARCHAR2(30),
     "ADDRESS_LINE_1" VARCHAR2(100),
     "PINCODE" NUMBER,
     "ADDRESS_LINE_2" VARCHAR2(100),
     "CONTACT_NUMBER_O" VARCHAR2(15),
     "CITY" VARCHAR2(30),
     "CONTACT_NUMBER_R" VARCHAR2(15),
     "STATE" VARCHAR2(30),
     "MOBILE_NUMBER" VARCHAR2(15),
     "COUNTRY" VARCHAR2(30),
     "EMAIL_ID" VARCHAR2(30),
     "ALT_EMAIL_ID" VARCHAR2(30),
     "ADDRESS_LINE_1_A" VARCHAR2(100),
     "PINCODE_A" NUMBER,
     "ADDRESS_LINE_2_A" VARCHAR2(100),
     "CONTACT_NUMBER_O_A" VARCHAR2(15),
     "CITY_A" VARCHAR2(30),
     "CONTACT_NUMBER_R_A" VARCHAR2(15),
     "STATE_A" VARCHAR2(30),
     "MOBILE_NUMBER_A" VARCHAR2(15),
     "COUNTRY_A" VARCHAR2(30),
     "EMAIL_ID_A" VARCHAR2(30),
     "ALT_EMAIL_ID_A" VARCHAR2(30),
     "DESPATCH_ACCOUNT" VARCHAR2(30),
     "REDEMPTION_PAYOUT" VARCHAR2(30),
     "I_PIN_ASSIGN" VARCHAR2(30),
     "DIVIDEND_PAYOUT" VARCHAR2(30),
     "T_PIN_ASSIGN" VARCHAR2(30),
     "TO_FUND_NAME" VARCHAR2(30),
     "TO_FUND_ID" VARCHAR2(30),
     "OPTION_F_S" VARCHAR2(30),
     "MCR_NO" NUMBER,
     "BANK_NAME" VARCHAR2(30),
     "ACCOUNT_NUMBER" NUMBER,
     "BANK_BRANCH" VARCHAR2(30),
     "ACCOUNT_TYPE" VARCHAR2(30),
     "MCR_NO_P" NUMBER,
     "CHEQUE_DD_NO" NUMBER,
     "BANK_NAME_P" VARCHAR2(30),
     "PAYMENT_DATE" DATE,
     "BANK_BRANCH_P" VARCHAR2(30),
     "ADVICE_NO" NUMBER,
     "PAYMENT_TYPE_P" VARCHAR2(30),
     "AMOUNT_P" NUMBER,
     "MINIMUM_AMOUNT" NUMBER,
     "AMOUNT_WORDS" VARCHAR2(1000),
     "NOMINEE_NAME" VARCHAR2(30),
     "SALUATION_STG" VARCHAR2(30),
     "NOMINEE_DOB_STG" DATE,
     "GUARDIAN_NAME_STG" VARCHAR2(30),
     "RELATIONSHIP_STG" VARCHAR2(30),
     "ADDRESS_LINE_1_STG" VARCHAR2(100),
     "COUNTRY_STG" VARCHAR2(30),
     "ADDRESS_LINE_2_STG" VARCHAR2(100),
     "PINCODE_STG" NUMBER,
     "CITY_STG" VARCHAR2(30),
     "CONTACT_NUMBER_STG" VARCHAR2(15),
     "STATE_STG" VARCHAR2(30),
     "MOBILE_NUMBER_STG" VARCHAR2(15),
     "REMARKS_STG" VARCHAR2(100),
     "EXCEPTION_CHK_STG" CHAR(1),
     "HOLD_CHK_STG" CHAR(1),
     "PAN_STG" CHAR(1),
     "BOARD_RESOLUTION_STG" CHAR(1),
     "KYC_STG" CHAR(1),
     "MOA_STG" CHAR(1),
     "CHEQUE_STG" CHAR(1),
     "ASL_STG" CHAR(1),
     "TRUST_DEED_STG" CHAR(1),
     "PARTNERSHIP_DEED_STG" CHAR(1),
     "BYE_LAWS_STG" CHAR(1),
     "AUTO_DEBIT_STG" CHAR(1),
     "ENROLLMENT_FORM_STG" CHAR(1),
     "APPROVED" VARCHAR2(10),
     "CREATED_BY" NUMBER,
     "CREATION_DATE" DATE,
     "LAST_UPDATE_DATE" DATE,
     "LAST_UPDATED_BY" NUMBER,
     "FUND_TYPE" VARCHAR2(30)
   ORGANIZATION EXTERNAL
    ( TYPE ORACLE_LOADER
      DEFAULT DIRECTORY DUMP_DIR
      ACCESS PARAMETERS
      ( RECORDS DELIMITED BY NEWLINE
           BADFILE 'emp.bad'
                      LOGFILE 't.log_xt'
                      FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' LDTRIM
                      REJECT ROWS WITH ALL NULL FIELDS
               "DATA_DISCRAPANCY"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "APPLICATION_NUMBER"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BATCH_NUMBER"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "AMC_ID"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "TA_BRANCH"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SERVER_DATE_1"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SERVER_TIME_1"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ARN_NUMBER"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BROKER_CODE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SUB_BROKER_CODE_1"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SUB_BROKER_CODE_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SUB_BROKER_CODE_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BROKER_ADDRESS"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "FOLIO_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MODE_OF_HOLDING"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "STATUS"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SALUATION"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_PERSON_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "INVESTOR_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAN_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "POA_HOLDER_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "KYC"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_PAN_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "DOB_DOC"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_RELATIONSHIP"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SALUATION_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "DATE_OF_BIRTH"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SECOND_HOLDER_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_NAME_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAN_NO_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_PAN_NO_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "KYC_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_RELATIONSHIP_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SALUATION_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "DATE_OF_BIRTH_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "THIRD_HOLDER_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_NAME_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAN_NO_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_PAN_NO_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "KYC_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_RELATIONSHIP_3"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_1"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PINCODE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_2"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_NUMBER_O"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CITY"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_NUMBER_R"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "STATE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MOBILE_NUMBER"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "COUNTRY"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "EMAIL_ID"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ALT_EMAIL_ID"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_1_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PINCODE_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_2_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_NUMBER_O_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CITY_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_NUMBER_R_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "STATE_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MOBILE_NUMBER_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "COUNTRY_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "EMAIL_ID_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ALT_EMAIL_ID_A"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "DESPATCH_ACCOUNT"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "REDEMPTION_PAYOUT"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "I_PIN_ASSIGN"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "DIVIDEND_PAYOUT"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "T_PIN_ASSIGN"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "TO_FUND_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "TO_FUND_ID"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "OPTION_F_S"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MCR_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BANK_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ACCOUNT_NUMBER"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BANK_BRANCH"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ACCOUNT_TYPE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MCR_NO_P"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CHEQUE_DD_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BANK_NAME_P"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAYMENT_DATE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BANK_BRANCH_P"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADVICE_NO"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAYMENT_TYPE_P"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "AMOUNT_P"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MINIMUM_AMOUNT"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "AMOUNT_WORDS"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "NOMINEE_NAME"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "SALUATION_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "NOMINEE_DOB_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "GUARDIAN_NAME_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "RELATIONSHIP_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_1_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "COUNTRY_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ADDRESS_LINE_2_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PINCODE_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CITY_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CONTACT_NUMBER_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "STATE_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MOBILE_NUMBER_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "REMARKS_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "EXCEPTION_CHK_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "HOLD_CHK_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PAN_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BOARD_RESOLUTION_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "KYC_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "MOA_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CHEQUE_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ASL_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "TRUST_DEED_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "PARTNERSHIP_DEED_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "BYE_LAWS_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "AUTO_DEBIT_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "ENROLLMENT_FORM_STG"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "APPROVED"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CREATED_BY"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "CREATION_DATE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "LAST_UPDATE_DATE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "LAST_UPDATED_BY"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " ' ,
               "FUND_TYPE"
                                                         TERMINATED BY "," OPTIONALLY ENCLOSED BY ' " '
      LOCATION
       ( 'Key_File_Report.dat'
{code}
while trying to select the data from external table, am facing the below error.
{code}
ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-29400: data cartridge error KUP-00554: error encountered while parsing access parameters KUP-01005: syntax error: found "identifier": expecting one of: "and, column, exit, (, ltrim, lrtrim, ldrtrim, missing, notrim, rtrim, reject" KUP-01008: the bad identifier was: LDTRIM KUP-01007: at line 4 column 77
{code}
can anyone suggest me how to resolve this.
Regards,
Sakthi.

I think i found the problem:
KUP-01008: the bad identifier was: LDTRIM KUP-01007: at line 4 column 77There is no LDTRIM. It is LDRTRIM or LRTRIM.
this should work
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LDRTRIM{code}
Edited by: Sven W. on Aug 27, 2010 2:59 PM -- removed the blanks in the optionally enclosed spec

Reg:variable creation for date

how to create a variable with last refresh date
after that use that object ( <Date> is less than New
Date). This will give you the entire data till last refresh date.

Hi Vinay,
You can get last refresh date using below function
Var1=LastExecutionDate()
Then you can apply filter [Date Object]>Var1

Reg: Table creation for generic source

Similar Messages

Maybe you are looking for