Skip to Content
author's profile photo Former Member
Former Member

Mapping fields and identifying extractors

Our client requirement is below

1)One of our client purchased business from x client.

And x client is giving only end user web based portal and R/3 system copy for different application.

And there is no BW system there and there not giving there BW system access and design documents.

2)From Portal reports we are identified the keyfigures and charactristics.

And we are mapping these characteristics and keyfigures to exsiting source system fileds .And we are unable to find some source fileds.We dont know the datasources also.

If some fields are not mapped then what approach we have to take.And the users goal are they expecting same reports what they are seeing now.What approach i have to take.

These reports are coming to Portal via Bw only.

And we dont have access other client (X client) BW systems and they are not giving design document also.They are giving only R/3 sytem copy and we are able to see reports in web based portal.Based on Portal reports we identified Characteristics and Keyfigures.And some characteristics and keyfigures we are mapped with R/3 source fields and Source tables.And these are not standard reports and all are custom report.And there is no use of businee content.Based on these information we have to develop reports from scratch mean from starting i.e. identifying KFs and char's and mapping fields with R/3 here I have doubt we are unable to map some fields with R/3 what we have to do?what approach we have to take.How we identify datasource.what extractor method we have to follow.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 29, 2008 at 07:31 AM

    I think in your case you will need to use generic extractors if you are not able to map the required field to any standard datasource. You can create a view based on the tables that are providing the fields and data. This you would need to create in se11. Then in RSO2 you create the datasource on that view and then if you want to have it as a generic delta then you would need to create a function module specifying that this datasource will perform a delta extraction. There is PDF in generic extractors. Very useful. It will give you a good idea on how to handle your requirement. Good luck.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 25, 2008 at 05:18 AM

    Hi Sridhar,

    It would be diff to make a dession of fields just based on the Web reports,i mena by any output of a report.

    The report will not give you any idea of the Technical properties of the fields and based ont the discussion with the reponsible person only u can take some decession on anything.

    As u have mentioned some fields are not matching as well.

    I suggest u have to approach by application area wise.

    Say FI then u have to make sure that the data that you are looking in the Report is really from FI then only u can trust the Datasourcess from giving the data.

    But all togather this exercise is really diff to produce the same kind of reports.

    Al the best .........!!

    Best Regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.