Java J2EE Mega Walkin On 1st Feb 14@ Tech Mahindra - Pune/Noida

Dear Candidate

Tech Mahindra is hiring for Java J2EE skills in Pune / Noida Location.

You are requested to appear for the Test process on 1^st Feb 2014

Interview Process:

·         Aptitude + English Test (80 minutes) Java Technical Test (60 minutes) Result Declaration.

·         Candidates who would qualify in the above test, would be called for a Technical round + HR round of Interview on 2^nd Feb 2014@ 10:00 AM.

Skills	:- Java, J2EE
Job Location	:- Pune/Noida
Experience range	:- 2-3 Years only
Reporting Time	:- 9:00 AM – 12:00 AM

Job Description

• Experience in java related technologies.
• Excellent java, JSP, Java programming skills.
• Knowledge of Ajax , jquery, webservices will be additional advantage.
• Unix basic commands and sql
• Strong programming skills of system flows and processes; structured thinking.
• Coordinate with design team and able to understand the design. Validate the design.
• Should be able to implement (coding) the design.
• Knowledge of tools and technologies related to java advancements.

Interview Locations 

Venue - Pune
Tech Mahindra Ltd.
3rd floor, Sharda Annex,
Off Karve Road, Pune 411004
Contact Person: Mrinal Mazumdar

Venue - Noida
Tech Mahindra Ltd.
A 7, Sector 64, Noida
Contact Person: Prachi Tiwari

Documents to be carried for Interview:

·          Updated resume.

·          Latest salary slips (2 months)

·          Offer / Appointment letter of current employer.

·          Latest Appraisal/ Increment letter of current company.

·          Experience letter of all the last employers (Should contain both DOJ and date of relieving).

·          Degree certificate of highest Qualification.

·          Final year/semester Marksheet ( consolidated Marksheet in case of JNTU)

·          Xerox copy of your passport. (First & Last Page).


Note: Please do not carry laptop / mass storage device along with you.

Check below link for more details

Java J2EE Mega Walkin On 1st Feb 14@ Tech Mahindra - Pune/Noida 

Check below link for interview Questions and Answers on JAVA

JAVA Interview questions and answers 

Walk-in For Technical Specialist - Informatica On 1 Feb' 14( Saturday)

Job Description

Date: 1 Feb 2014

Venue: Mumbai

IKP  iGATE Computer Systems Ltd IT 1 / IT 2,

TTC Industrial Area ,

Thane Belapur Road Airoli,

Navi Mumbai 400708.

Venue: Pune

iGATE Information Services Pvt. Ltd.

Level 2, Wing ‘B’, Tower III

Cyber City, Magarpatta City

Hadapsar, Pune 411013

Maharashtra

India.

Job Location: Mumbai

-Should have minimum 4 years experience development using Informatica Power Center 7.1, 8.1 tools. Good knowledge of Dimensonal modelling

-Identify key/critical design elements and interfaces, provide ETL design approaches

-Must have experience in Developed ETL mappings, transformations using informatica power mart, implementing source and target definitions in Informatica power mart.

-Must have experience in Installation, Configuration and Administration of Informatica Power Center.

5. Must have hands on experience in SQL scripting.

Skills Required:

Informatica, Unix, DWH, Dataware house, SQL

Desired Candidate Profile:

-The candidate must have Total Experience of 4-6 Years and relevant experience of minimum 4 Years in Informatica.

-Strong technical skills

-Organisational skills

-Communication skills

-Analytical skills

-Team-working skills

** Must have a Bachelor’s degree

Must have a stable career background

For detail Check the below link

Walk-in For Technical Specialist - Informatica On 1 Feb' 14( Saturday) 

For Informatica Interview questions and answers check the below link

Informatica Interview Questions and answers 

Walkin For Technical Specialist - SAP ABAP On 25th Jan14 @ Mumbai / Pune / Blore / Hyd / Chennai

Job Description

-Work independently for development with various functional consultants on various ABAP developments like Enhancements, Conversions, Reports, Scripts and Interface.

-Should have worked on BAPIs, Badis, Enhancement spots.

-Good understanding of business requirements.

-Should be able to communicate well.

-Should be able to read the functional specifications  and convert it into technical specifications.

- Should be able to estimate the efforts correctly and ensure that the deliveries are on time

Desired Candidate Profile:

SAP ABAP

** Must have a Bachelor’s degree

Must have a stable career background

Job Location: Mumbai, Pune, Hyderabad, Bangalore, chennai

Walkin interview on 25th Jan14 at Mumbai / Pune / Bangalore / Hyderabad / Chennai

Time: 9.00am to 2.00pm

For details check below link

Walkin For Technical Specialist - SAP ABAP On 25th Jan14 @ Mumbai / Pune / Blore / Hyd / Chennai 

Cognizant Coimbatore DWBI Walk-in Interviews on 25-Jan-14,Sat @ Bangalore

Job Description

DWH Skills:

• Informatica - 3 to 8 yrs
• OBIEE - 5 to 7 yrs
Candidate Checklist to bring
• Hard copy of your resume
• One Passport size photograph
• ID & Address Proof (Xerox Copies): Passport copy / Any Govt. Authorized ID Proof.
• Present company’s offer letter, relieving letter, last three month’s pay slips, and last revision letter.
• Previous Organizations offer letter, relieving letter and three month’s pay slips

Walk-in Details

Venue Address
Cognizant Technology Solutions,Golf View Campus, Wind Tunnel Road,Murugesh Palaya, Bangalore â€Â" 560017

City: Bengaluru / Bangalore

Date: 25/01/2014 and 25/01/2014

Timings: 10:00 AM to 12:00 PM

 For details Check this link

Cognizant Coimbatore DWBI Walk-in Interviews on 25-Jan-14,Sat @ Bangalore

L&T Infotech -excellent Opportunity for SAP Bi/bw Professionals

To Meet our growing needs we are looking for SAP BI/BW professionals for our various locations.

Walkin drive Scheduled on Saturday -25th Jan 2014 at Pune Location  
Exp required in the following area:
Data Modelling
Reporting
Extraction
Complete End -End Implementation Exp is must.
Willing to travel domestic and International. 


for details check the below link


L&T Infotech -excellent Opportunity for SAP Bi/bw Professionals

TCS arrange Walk-in Informatica Senior Developer/Designer Kolkata on 25-Jan- 2014 (Saturday)

Hi,

We are pleased to inform that we are having requirements for "Informatica Senior Developer/Designer"
Details of the opening are as follows :

Skill: Informatica Senior Developer/Designer

Exp : 4 -8 yrs

Job Location : Kolkata

Job Description :

Required Technical Skill Set:

Good understanding of Data Integration concepts and Data Integration solution landscape. Proficiency & varied experience of Informatica products, especially, PowerCenter, Metadata Manager, IDE and IDQ.

Date	25-Jan- 2014 (Saturday)
Venue	TCS,Delta Park Lords, Plot B-1, Block EP & GP, Sector 5, Salt Lake Electronics Complex, Kolkata 700 091
Registration Time	9:30 AM to 12:30 PM
Joining	Kolkata

If you are interested and find yourself eligible as per the JD, we request you to share your updated resume with us.
Eligibility criteria:

BE/B.Tech/MCA/M.Sc/MS with minimum 3 years of relevant experience post Qualification IT- Experience.

Bsc Graduates with minimum 4+ years of relevant experience post qualification IT Experience.

Only Full Time courses would be considered.

Consistent academic records Class X onwards (Minimum 50%)

Candidate who have attended TCS interview in the last 6 months need not apply.

Steps to create EP number:

1. Go to http://www.careers.tcs.com/
2. Go to Experienced professionals tab and select India as the geography
3. Go to create new profile and fill the details and submit it.
4. You will get the EP number & Password in your e-mail id

In case of any issue related to creation./validation of EP Number, pls take help from our Talent Acquisition Group
Help Line No.: 1800-209-3111 (Toll Free).

 Guidelines on Calculation of Aggregate Marks:

All subjects mentioned on the mark sheets should be taken into consideration for calculating the aggregate marks. All optional /additional subjects to be included (Irrespective of any University/Education Board Norms). Do not use any concept of Best of 5/6 or Additional Marks etc.

In case of Graduation and Post Graduation, aggregate marks will mean taking into consideration Honors as well as Pass subjects also.

*** You may like to take help from TCS Talent Aquisition group Helpline in case of any issues related to profile creation/Application form completion by calling at Toll Free number (1800-209-3111)

Note : If you already have a profile in TCS career portal and have an EP number, please ensure that the online Application form is properly filled and CV uploaded before appearing for Interview.

Request you to please fill in the required details in the Application Form only after referring your relevant documents because the details which you enter in the form will be used for your Background Check Process post offer from TCS.

We look forward to seeing you at the venue
Thanks & regards
TATA CONSULTANCY SERVICES

SAP BI/BW Consultant Walkin @ NTT Data Hyderabad on 25th January 2014

This is with reference to your resume in FirstNaukri portal and to seek your interest for the below opportunity with NTT DATA (formerly known as “Keane India Limited”).

NTT Data currently seeks SAP BI/BW Consultants with 3-7Years experience

Job Description:

Minimum 3- 7 years of technical experience with SAP BW/BI including the experience in both 3.5 and 7.0 versions

Hands on experience in 3 - 4 SAP development projects
Has experience in working in 1 - 2 Support / Maintenance Projects.
Deep knowledge in configuration of SAP BW data objects InfoObjects, DataSources, InfoSources, DTPs, Transformations, ODS, InfoCubes, MultiProviders, InfoSets and Process Chains.
Perform analysis and design; write technical specifications; configuration and programming in the SAP BW environment, including testing and implementation.
A proven track record for leading and executing complex SAP BW data warehouse architecture
Deep knowledge of SAP BI Content extractors from the ECC system and working knowledge of SAP structures, object dependencies and tables in version ECC 6.0 environment.
Extensive experience in reconciling ECC data with BW data
Extensively worked on extractors like SD, FI/CO, PM, PP, MM, Project Systems, CRM
ABAP knowledge to handle SAP BW enhancements
Experience in designing and building SAP BW - BEx queries for SAP BusinessObjects - BI Reporting/dashboards.
Experience in building SAP BusinessObjects - BI Reports/dashboards based on SAP BW-BEx Queries and its integration with SAP BW
Nice to have the knowledge on SAP BW 7.3 objects SPO, Hybrid Providers, Composite Providers...etc. and other capabilities of SAP BW 7.3 (LSA and LSA ++)
SAP BW 7.3 upgrade project experience would be an added advantage Excellent problem-solving skills and knowledge of business process
Good communication and interpersonal skills, should be a team player
Work Location: Bangalore, Chennai, Hyderabad

Qualification: BE / BTech / ME / MTech / MCA(Full time) / MBA(Full time)/ MSc

Note: Contractors are not eligible for the above requirement.
We have a planned for a walk-in drive on 25^th Jan (Saturday) at Hyderabad location. Please make yourself available for the interview process at the following venue;

Date: 25-Jan-14 Day: Saturday Time: 10.00 AM to 1.30 PM Contact Person: RaviSiddineni /Srinivas Mungara Contac t Number : 040 66010000

Venue: NTT DATA (Formerly - Intelligroup Asia Private Limited) 5th Floor (Blocks A & B), ILabs Centre, Plot No.18,Software Units Layout, Madhapur, Hyderabad, Landmark: Opposite to In-Orbit Shopping Mall

Kindly carry with you the below documents: ·         Updated profile ·         Last two Months Payslips ·         Current company offer letter ·         Passport size Photograph ·         ID proof document

Candidates who have already taken up the interview with us in the last 3 months are not eligible.

Interviews Informatica at Chennai & Bangalore @ L&T Infotech on 25th Jan Saturday

Job Description

Informatica

Experience: 3 years- 9 years

Job Location : Mumbai

Informatica Developer / Lead :

-Will be involved in the entire lifecycle of a project that involves analysis, coding, testing, User acceptance, deployment and support.

-Development of Informatica mappings/Sessions/Workflows.

-Development of Unix scripts

-Debugging of Informatica mappings

-Will be responsible for the task or module assigned to him or her and ensure quality delivery within acceptable timelines.

-Liaise with end-users business and other application groups to meet the set deliverables

L&T Infotech is having interviews at following location on 25th January between  9 AM – 1 PM.

Please walk in with following documents (mandatory) :

-Resume

-Last 3 months Pay slips

-Current company Appointment Letter + Last Increment Letter (If Any)

-1 Color Photograph

-Original Photo ID for verification

Bangalore Venue :

Larsen & Toubro Infotech Limited

Plot #25-30, EPIP I Phase, KIADB Industrial Area

Whitefield, Bangalore - 560 066.

Contact Person: Nutan Chillal

Chennai Venue:

Larsen & Toubro Infotech Limited.

Block 4, IInd Floor, DLF IT Park, SEZ Campus,

1/124, Shivaji Gardens,

Mount Poonamallee Road,

Manapakkam,

Chennai – 600 089.

Contact Person: Sathya Ram Sudan R

For Details Check the Below Link

Interviews Informatica at Chennai & Bangalore @ L&T Infotech on 25th Jan Saturday 

SAP Production Support-Ticket Resolving

What is SAP Production Support - Ticket Resolving
1. How the tickets in production support are resolved?
2. Give some examples with solutions?
What are the types of ticket and its importance?
This depends on the SLA. It can be like:
  1. Critical.
  2. Urgent.
  3. High.
  4. Medium
  5. Low.
The response times and resolution times again are defined in the SLA based on the clients requirement and the charges.
This is probably from the viewpoint of Criticality of the problem faced by the client as defined by SAP.
  1)      First Level Ticketing:
Not severe problem. Routine errors. Mostly handled by Service desk arrangement of the company (if have one).
Eg: a) Say Credit limit block in working on certain documents?
      b) Pricing Condition Record not found even though conditions are maintained?
      c) Unable to print a delivery document or Packing list?
PS: In the 4th phase of ASAP Implementation Methodology( i.e Final Preparations for GO-LIVE) SAP has clearly specified that a Service desk needs to be arranged for any sort of Implementation for better handling of Production errors.
Service desk lies with in the client.
2)      Second Level Ticketing:
Some sort of serious problems. Those Could not be solved by Service Desk. Should be referred to the Service Company (or may be company as prescribed in SLA).
Eg: a) Credit Exposure (especially open values) doesn't update perfectly to KNKK Table.
      b) Inter company Billing is taking a wrong value of the Bill.
      c) Need a new order type to handle reservation process
      d) New product has been added to our selling range. Need to include this into SAP. (Material Masters, Division attachements, Stock Handling etc.)
3)      Third Level Ticketing:
Problems could not be solved by both of the above, are referred to Online Service Support (OSS) of SAP Itself. SAP tries to solve the Problem, sometimes by providing the perfect OSS Notes, fits to the error and rarely SAP logs into our Servers (via remote log-on)for post mortem the problem. (The Medical check-up client, connections, Login id and Passwords stuff are to be provided to SAP whenever they need or at the time of opening OSS Message.)
There are lots of OSS Notes on each issue, SAP Top Notes and Notes explaining about the process of raising a OSS Message.
Sometimes SAP Charges to the client / Service company depending on the Agreement made at the time of buying License from SAP.
Eg: 1) Business Transation for the Currency 'EUR' is not possible. Check OSS Note  - This comes at the time of making Billing.
      2) Transaction MMPI- Periods cannot be opened – See OSS Note.
      There are many other examples on the issue.
4)      Fourth Level Ticketing:
Where rarely, problems reach this level.
Those problem needs may be re-engineering of the business process due to change in the Business strategy. Upgradation to new Version.  More or less this leads to extinction of the SAP Implementation.

SAP BW Production Support Issues

SAP BW Production Support Issues

Production Support Errors :1) Invalid characters while loading: When you are loading data then you may get some special characters like @#$%...e.t.c.then BW will throw an error like Invalid characters then you need to go through this RSKC transaction and enter all the Invalid chars and execute. It will store this data in RSALLOWEDCHAR table. Then reload the data. You won't get any error because now these are eligible chars done by RSKC.

2) IDOC Or TRFC Error: We can see the following error at “Status” Screen:Sending packages from OLTP to BW lead to errorsDiagnosisNo IDocs could be sent to the SAP BW using RFC.System responseThere are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.Further analysis:Check the TRFC log.You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".Removing errors:If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.Action to be taken:If Source System connection is OK Reload the Data.

3)PROCESSING IS OVERDUE FOR PROCESSED IDOCsDiagnosis IDocs were found in the ALE inbox for Source System that is 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. Analysis:After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.Action to be taken:We can process the IDocs manually via RSMO -> Header Tab -> Click on Process manually.

4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )Diagnosis User ALEREMOTE is preventing you from loading texts to characteristic 0COSTCENTER . The lock was set by a master data loading process with therequest number. System response For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process. Procedure Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks. If a process terminates, the locks that have been set by this process are reset automatically. Analysis:After looking at all the above error messages we find that the user is “Locked”. Action to be taken:Wait for sometime & try reloading the Master Data manually from Info-package at RSA1.

5) Flat File Loading ErrorDetail Error MessageDiagnosis Data records were marked as incorrect in the PSA. System response The data package was not updated.Procedure Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.Analysis:After looking at all the above error messages we find that the PSA contains incorrect record.Action to be taken:To resolve this issue there are two methods:-i) We can rectify the data at the source system & then load the data.ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.

6) Object requested is currently locked by user ALEREMOTEDetail Error Message.DiagnosisAn error occurred in BI while processing the data. The error is documented in an error message.Object requested is currently locked by user ALEREMOTEProcedureLook in the lock table to establish which user or transaction is using the requested lock (Tools -> Administration -> Monitor -> Lock entries). Analysis:After looking at all the above error messages we find that the Object is “Locked. This must have happened since there might be some other back ground process runningAction to Be taken : Delete the error request. Wait for some time and Repeat the chain.

Idocs between R3 and BW while extraction
1)When BW executes an infopackage for data extraction the BW system sends a Request IDoc ( RSRQST ) to the ALE inbox of the source system.Information bundled in Request IDoc (RSRQST) is :
Request Id ( REQUEST )
Request Date ( REQDATE )
Request Time (REQTIME)
Info-source (ISOURCE)
Update mode (UPDMODE )
2)The source system acknowledges the receipt of this IDoc by sending an Info IDoc (RSINFO) back to BW system.The status is 0 if it is ok or 5 for a failure.
3)Once the source system receives the request IDoc successfully, it processes it according to the information in the request. This request starts the extraction process in the source system (typically a batch job with a naming convention that begins with BI_REQ). The request IDoc status now becomes 53 (application document posted). This status means the system cannot process the IDoc further.
4)The source system confirms the start of the extraction job by the source system to BW by sending another info IDoc (RSINFO) with status = 1
5)Transactional Remote Function Calls (tRFCs) extract and transfer the data to BW in data packages. Another info IDoc (RSINFO) with status = 2 sends information to BW about the data package number and number of records transferred
6)At the conclusion of the data extraction process (i.e., when all the data records are extracted and transferred to BW), an info IDoc (RSINFO) with status = 9 is sent to BW, which confirms the extraction process.

When is reconstruction allowed?

1. When a request is deleted in a ODS/Cube, will it be available under reconstruction.
Ans :Yes it will be available under reconstruction tab, only if the processing is through PSA Note: This function is particularly useful if you are loading deltas, that is, data that you cannot request again from the source system
2. Should the request be turned red before it is deleted from the target so as to enable reconstruction
Ans :To enable reconstruction you may not need to make the request red, but to enable repeat of last delta you have to make the request red before you delete it.
3. If the request is deleted with its status green, does the request get deleted from reconstruction tab too
Ans :No, it wont get deleted from reconstruction tab
4. Does the behaviour of reconstruction and deletion differ when the target is differnet. ODS and Cube
Ans :Yes


How to Debugg Update and transfer Rules
1.Go to the Monitor.
2. Select 'Details' tab.
3. Click the 'Processing'
4. Right click any Data Package.
5. select 'simulate update'
6. Tick the check boxes ' Activate debugging in transfer rules' and 'Activate debugging in update rules'.
7. Click 'Perform simulation'.


Error loading master data - Data record 1 ('AB031005823') : Version 'AB031005823' is not valid
ProblemCreated a flat file datasource for uploading master data.Data loaded fine upto PSA.Once the DTP which runs the transformation is scheduled, its ends up in error as below:


SolutionAfter refering to many links on sdn, i found that since the data is from an external file,the data will not be matching the SAP internal format. So it shud be followed that we mark "External" format option in the datasource ( in this case for Material ) and apply the conversion routine MATN1 as shown in the picture below

:Once the above changes are done, the load was successful.Knowledge from SDN forumsConversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.

Check the info :http://help.sap.com/saphelp_nw04/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/07/6de91f463a9b47b1fedb5be18699e7/content.htmThis fm ( MATN1) will add leading ZEROS to the material number because when u query on MAKT with MATNR as just 123 you wll not be getting any values, so u should use this conversion exit to add leading zeros.’

Function module to make yellow request to RED
Use SE37, to execute the function module RSBM_GUI_CHANGE_USTATE.From the next screen, for I_REQUID enter that request ID and execute.From the next screen, select 'Status Erroneous' radiobutton and continue.This Function Module, change the status of request from Green / Yellow to RED.

What will happend if a request in Green is deleted?
Deleting green request is no harm. if you are loading via psa, you can go to tab 'reconstruction' and select the request and 'insert/reconstruct' to have them back.But,For example you will need to repeat this delta load from the source system. If you delete the green request then you will not get these delta records from the source system.Explanation :when the request is green, the source system gets the message that the data sent was loaded successfully, so the next time the load (delta) is triggered, new records are sent.If for some reason you need to repeat the same delta load from the source, then making the request red sends the message that the load was not successful, so do not discard these delta records.Delta queue in r/3 will keep until the next upload successfully performed in bw. The same records are then extracted into BW in the next requested delta load.

Appearence of Values for charecterstic input help screen
Which settings can I make for the input help and where can I maintain these settings?In general, the following settings are relevant and can be made for the input help for characteristics:Display: Determines the display of the characteristic values with the following options "Key", "Text", "Key and text" and "Text and key".Text type: If there are different text types (short, medium and long text), this determines which text type is to be used to display the text.Attributes: You can determine for the input help which attributes of the characteristic are displayed initially. When you have a large number of attributes for the characteristic, it makes sense to display only a selected number of attributes. You can also determine the display sequence of the attributes.F4 read mode: Determines in which mode the input help obtains its characteristic values. This includes the modes "Values from the master data table (M)", "Values from the InfoProvider (D)" and "Values from the Query Navigation (Q)".

Note that you can set a read mode, on the one hand, for the input help for query execution (for example, in the BEx Analyzer or in the BEX Web) and, on the other hand, for the input help for the query definition (in the BEx Query Designer). You can make these settings in InfoObject maintenance using transaction RSD1 in the context of the characteristic itself, in the InfoProvider-specific characteristic settings using transaction RSDCUBE in the context of the characteristic within an InfoProvider or in the BEx Query Designer in the context of the characteristic within a query. Note that not all the settings can be maintained in all the contexts. The following table shows where certain 
settings can be made:

Setting RSD1 RSDCUBE BExQueryDesigner
Display X X X
Text type X X X
Attributes X - -
Read mode -
Query execution X X X -
Query definition X - -
Note that the respective input helps in the BEx Web as well as in the BEx Tools enable you to make these settings again after executing the input help.


When do I use the settings from InfoObject maintenance (transaction RSD1) for the characteristic for the input help?

The settings that are made in InfoObject maintenance are active in the context of the characteristic and may be overwritten at higher levels if required. At present, the InfoProvider-specific settings and the BEx Query Designer belong to the higher levels. If the characteristic settings are not explicitly overwritten in the higher levels, the characteristic settings from InfoObject maintenance are active.When do I use the settings from the InfoProvider-specific characteristic settings (transaction RSDCUBE) for the input help?You can make InfoProvider-specific characteristic settings in transaction RSDCUBE -> context menu for a characteristic -> InfoProvider-specific properties.These settings for the characteristic are active in the context of the characteristic within an InfoProvider and may be overwritten in higher levels if required. At present, only the BEx Query Designer belongs to the higher levels. If the characteristic settings are not explicitly overwritten in the higher levels and settings are made in the InfoProvider-specific settings, these are then active. Note that the settings are thus overwritten in InfoObject maintenance.When do I use the settings in the BEx Query Designer for characteristics for the input help?In the BEx Query Designer, you can make the input help-relevant settings when you go to the tab pages "Display" and "Advanced" in the "Properties" area for the characteristic if this is selected.These settings for the characteristic are active in the context of the characteristic within a query and cannot be overwritten in higher levels at present. If the settings are not made explicitly, the settings that are made in the lower levels take effect.

How to supress messages generated by BW Queries
Standard Solution :
You might be aware of a standard solution. In transaction RSRT, select your query and click on the "message" button. Now you can determine which messages for the chosen query are not to be shown to the user in the front-end.

Custom Solution:
Only selected messages can be suppressed using the standard solution. However, there's a clever way you can implement your own solution... and you don't need to modify the system for it!All messages are collected using function RRMS_MESSAGE_HANDLING. So all you have to do is implement an enhancement at the start of this function module. Now it's easy. Code your own logic to check the input parameters like the message class and number and skip the remainder of the processing logic if you don't want this message to show up in the front-end.

FUNCTION rrms_message_handling.
StartENHANCEMENT 1 Z_CHECK_BIA.
* Filter BIA Message
if i_class = 'RSD_TREX' and i_type = 'W' and i_number = '136'*
just testing it.*
exitend if.
ENHANCEMENT
End
IMPORTING
------------
----------
----
EXCEPTIONS
Dummy ..

How can I display attributes for the characteristic in the input help?
Attributes for the characteristic can be displayed in the respective filter dialogs in the BEx Java Web or in the BEx Tools using the settings dialogs for the characteristic. Refer to the related application documentation for more details.In addition, you can determine the initial visibility and the display sequence of the attributes in InfoObject maintenance on the tab page "Attributes" -> "Detail" -> column "Sequence F4". Attributes marked with "0" are not displayed initially in the input help.


Finance  economy  finance & insurance money derivatives wall street young money  got money cash money  get money 
 
Why do the settings for the input help from the BEx Query Designer and from the InfoProvider-specific characteristic settings not take effect on the variable screen?
On the variable screen, you use input helps for selecting characteristic values for variables that are based on characteristics. Since variables from different queries and from potentially different InfoProviders can be merged on the variable screen, you cannot clearly determine which settings should be used from the different queries or InfoProviders. For this reason, you can use only the settings on the variable screen that were made in InfoObject maintenance.