8/17/13
SAP BI: SAP BI Pr oducti on Suppor t Issues Share
0
More
Nex t Blog»
Creat e Blog
Sign In
SAP BI Dear Viewrs.. This Blogs are Abt the SAP BI .
Wednesday, April 8, 2009
SAP BI Production Support Issues Production Prod uction Support Errors : 1) Inv alid characters while loading: When you are loading data then then you yo u may may get get some special characters like @#$%...e.t.c.then BW will throw an error like In v In v alid alid characters then you need t o go thro ugh this RSKC transaction and enter all the Invalid chars and exec ute. It will store this data in RSALLOWED RSALLOWEDCHAR CHAR table. T hen reload the data. You won't get any error because now these are eligible chars done by RSKC. 2) IDOC Or Or T RFC Error: We can see the f ollowing error at “Status” Scre en:Sendin en:Sending g
About Me
packages from OLTP to BW lead to errorsDiagnosisNo IDocs could be sent to the SAP BW
Blog Archive ► 2012 (1)
using RFC.System responseThere are IDocs in the source system ALE outbox that did not ► 2010 (1)
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 sourc e 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 syste m.Action to be taken:If Source Sy stem connection is OK Reload the Data. 3)PROCESSING IS OVER DUE DUE FOR FOR PROCESSED IDOCsDiagnosis IDocs were IDocs were found fo und in the ALE inbox for Source Sy stem that is is not updated. updated. Processing is overdue. Error co rrectio n: Attempt to proce ss the IDocs manuall manually. y. Y ou can process the IDocs manually manually using using the Wizard or by selecting the IDocs with with incorrect status and processing them manuall manually. y. Analysis:Afte r looking at all 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 manually v ia RSMO -> Header Header T ab -> Click on Proce ss manually. manually.
Cool Guy hi .. i'm Sasi Reddy i'm SAP BI BPC Consulant im working past 15 yrs on SAP BI.I 'M Working Banking and Retail and Oil&Gas and Utilities Domai Domains. ns. View my complete profile
▼ 2009 (22) ► November (1) ► July July (3) (3) ▼ April (18)
SAP Business Warehous e Topics Comparing/L imitation of SAP R/3 Reporting Systems...
4) LOCK LOCK NOT SET FO FOR R LOADING LOADING MASTER DAT A ( T EXT / AT TRIBUE / HIER HIERARCHY ARCHY )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. num ber. Sy stem response For reasons of c onsistency, the system cannot allow the update to continue, and it has terminated terminated the proce ss. Proc edure 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:Afte r looking at all all the above error messages we find that the user is “Locked”. Action to be taken:Wait for sometime & try re loading the Master Data man manually ually from Infopackage at RSA1. 5) Flat File Loading ErrorDetail Error Me ssageDia ssageDiagnosis gnosis 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). maintenance). You c an find the error message for each re cord in the PSA by double-clicking on the record status.Analysis:After looking at all the above error messages
SAP BW Glossary Evolution of SAP BW Evolution of SAP BW I am giving System landscape means real time prosp... SAP System Landscape Directory
there are two methods:-i) We can rectify the data at the source sy stem & then load the
ASAP Methodolo gies
data.ii) We can correct the incorrec t recor d in the PSA & then upload the data into the data
ASAP
we find that the PSA contains incorrec incorrec t record.A ction to be taken:To reso lve this issue
i ndel asap.bl og spot.com/2009/04/sap- bi - pr oducti on- suppor t- issues.html
1/15
8/17/13
SAP BI: SAP BI Production Support Issues
target from here.
gies SAP What are the Business content Cubes, ODS and some ...
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 ALEREMOTEProce dureLook in the lock table to establish which user or transaction is using the requested lock (T ools -> Administration -> Monitor -> Lock entries).
About T he Informatio n Broadcasti ng in SAP NetWeave. ..
Analysis:Afte r looking at all the above error messages we find that the Object is “Locked. This must have happened since there might be some other bac k ground process runningAction to Be t aken : Delete the error request. Wait fo r some time and Repeat the chain. Idocs between R3 and BW while extraction
SAP Bw Interview Questions With IBM/HP
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 ( REQDAT E )
SAP BW LO Extraction
Request Time (REQTIME) Info-source (ISOURCE)
SAP BI Productio n Support Issues
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
FAQ SAP Business Informatio n Warehous e
to the information in the request. This request starts the extraction process in the source system (ty pically a batch job with a naming conve ntion that begins with BI_REQ). The request IDoc status now beco mes 53 (application document posted). This status means the system cannot process the IDoc further. 4)The source sy stem confirms the start of the ex traction job by the source system to BW
Features in BI 7.0 or Netweaver 2004s
by sending another info IDoc (RSINFO) with status = 1 5)T ransactional Remote Function Calls (tRFCs) extract and transfer the data to BW in data packages. Another info IDoc (RSI NFO) with status = 2 sends information to BW about the data package number and number of records tr ansferred
BW-BPS as iView in the Portal
6)At the conclusion of the data extraction process (i.e., when all the data records are extrac ted and transferred to BW), an info IDoc (RSINFO) with status = 9 is sent to BW, which confirms the extrac tion process.
Seeting SAP BW 3.5 Reports in to Portal 6.0
When is recon struction allowed? 1. When a request is deleted in a ODS/Cube, will it be av ailable 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
Followers Join this site w ith Google Friend Connect
Membe rs (289) More »
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 Already a member? Sign in
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. selec t 'simulate update' indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
2/15
8/17/13
SAP BI: SAP BI Production Support Issues
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 f ile datasource fo r uploading master data.Data loaded fine upto PSA.Once the DT P which runs the transformation is scheduled, its ends up in error as below:
SolutionAfter r efering 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" for mat option in the datasource ( in this case fo r Material ) and apply the conversion routine MATN1 as shown in the picture below :Once the abov e 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 ver sa 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/e9a20d3347b340946c32331c96a6 4e/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/07/6de91f463a9b47b1 fedb5be18699e7/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 conv ersion exit t o 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 y ou are loading via psa, you c an 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 sy stem 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 r epeat the same delta load from the source, then making the request re d sends the message that the load was not successful, so do not discard these delta records.Delta queue in r/3 will kee p until the next upload successfully performed in bw. The same records are then extracted into BW in the next requested delta load. Appearence o f Values f or charecterstic input hel p 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 t he input help for characteristics:Display: Determines the display of the characteristic values with the following options "Key", "Tex t", "Key and text" and "Text and key".Tex t 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 t he attributes.F4 re ad mode: Determines in which mode the input help obtains its characteristic v alues. This includes the modes "Values fro m the master data table (M)", "Values from the InfoPro vider (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 indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
3/15
8/17/13
SAP BI: SAP BI Production Support Issues
(for ex ample, 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 InfoProv ider-specific c haracteristic settings using transaction RSDCUBE in the context of the characteristic within an InfoProvider or in the BEx Query Designer in the context of the c haracteristic within a query. No te that not all the settings can be maintained in all the contexts. T he following table shows where certain settings can be made: Setting RSD1 RSDCUBE BExQueryDesigner Display X X X Tex t 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 exec uting the input help.
When do I use the settings from Inf oObject m aintenance (t ransaction RSD1) for the characteristic for the input help? The se ttings that are made in InfoObject maintenance are act ive in the c ontext o f 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 characte ristic settings are not explicitly ove rwritten in the higher levels and settings are made in the InfoProvider-specific settings, these are then active . Note that the set tings are thus overwritten in InfoObject maintenance.When do I use the settings in the BEx Query Designer for characte ristics for the input help?In the BEx Query Designer, you c an make the input help-relev ant 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 leve ls 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 : Yo u might be aware of a standard solution. In transaction RSRT, select y our query and click o n the "message" button. Now you can determine which messages for the chosen query are not to be shown to the user in the fr ont-end. Custom Solution: Only selected messages can be suppressed using the standard solution. Howeve r, 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 collec ted 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 y our own logic to chec k the input parameters like the message class and number and skip the remainder of the proce ssing logic if y ou don't want this message to show up in the front-end. FUNCTI ON rrms_message_handling. StartENHANCEMENT 1 Z_CHECK_BIA. * Filter BIA Message if i_class = 'RSD_TREX' and i_type = 'W' and i_number = '1 36'* just testing it.* indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
4/15
8/17/13
SAP BI: SAP BI Production Support Issues
exitend if. ENHANCEMENT End IMPORTING -----------------------EXCEPTIONS Dummy .. How can I display attributes for the characteristic in the input help? Attributes for the characte ristic can be displayed in the respectiv e 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 deter mine the initial visibility and the display sequence of the attributes in InfoObject maintenance on the tab page "Attributes" -> "Detail" -> column "Sequence F4". A ttributes marked with "0" are not displayed initially in the input help. Why do the sett ings for th e input h elp 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 differ ent queries or InfoProviders. For this reason, you can use only the settings on the variable screen that were made in InfoObject maintenance. Why do the read mode sett ings for th e characteristic and the providerspecific read mode settings not take effect during the execution of a query in the BEx Analyzer? The query read mode settings always take effect in the BEx Analyzer during the execution of a query . If no sett ing was made in the BEx Query Designer, then default read mode Q (query) is used. How can I change settings for the input help on the variable screen in the BEx Java Web? In the BEx Java We b, at present, y ou can make settings for the input help only using InfoObject maintenance. Y ou can no longer change these settings subsequently on the variable screen. Selective Deletion in Process Chain The standard procedure : Use Pro gram RSDRD_DELETE_FACT S 1. Create a variant which is stored in the table RSDRBATCHPARA for the selection to be deleted from a data target. 2. Execute the generated program. Observations: The generated pr ogram executes will delete the data from data target based on the given selections. The program also removes the variant created for this selective deletion in the RSDRBATCHPARA table. So this generated program wont delete on the second execution. If we want to use this program for scheduling in the process chain we can comment the step where the program remove the deletion of the generated variant. Eg:REPORT ZSEL_DELETE_QM_C10 . TY PE-POOLS: RSDRD, RSDQ, RSSG. DATA: L_UID TYPE RSSG_UNI_IDC25, L_T_MSG TYPE RS_T _MSG, indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
5/15
8/17/13
SAP BI: SAP BI Production Support Issues
L_THX_SEL TYPE RSDRD_THX_SEL L_UID = 'D2OP7 A6385IJRCKQCQP6W4CCW'. IMPORT I_THX_SEL TO L_THX_SEL FROM DAT ABASE RSDRBAT CHPARA(DE) ID L_UID. * DELETE FROM DAT ABASE RSDRBAT CHPARA(DE) ID L_UID.CALL FUNCTION 'RSDRD_SEL_DELETION' EXPORTING I_DATAT ARGET = '0QM_C10' I_T HX_SEL = L_THX_SELI_AUTHORITY_CHECK = 'X' I_THRESHOLD = '1.0000E-01' I_MODE = 'C' I_NO_LOGGING = '' I_PARA LLEL_DEGREE = 1 I_NO_COMMIT = '' I_WORK_ON_PARTITIONS = '' I_REBUILD_BIA = '' I_WRITE_APPLICATION_LOG = 'X' CHANGING C_T_MSG = L_T_MSG.export l_t_msg to memory id sy-repid. UPDATE RSDRBATCHREP SET DELETEABLE = 'X' WHERE REPID = 'ZSEL_DELETE_QM_C10'.
ABAP program to f ind prev request in cube and delete Ther e will be cases when we cannot use the SAP built-in settings to delete prev ious request..The logic to determine previous request may be so customised, a requirement.In such cases you can write a ABAP program which calculates previous request basing our own defined logic.Following are the tables used : RSICCONT ---(list of all requests in any particular cube)RSSELDONE ----- ( has got Reqnumb, source , target , selection infoobjec t , selections ..etc)Following is one example code. Logic is to select request based on selection conditions used in the infopackage:
TCURF, T CURR and T CURX TCURF is always used in reference to Exchange rate.( in case of currency translation ).For example, Say we want to co nvert f ig's from FROM curr to T O curr at Daily avg rate (M) and we have an exc hange rate as 2,642.34 . Factors for this currency c ombination for M in TCURF are say 1 00,000:1.Now the effective exchange rate becomes 0.02642. Question ( taken from sdn ):can't we have an exchange rate of 0.0264 2 and not at all use the factors from TCURF table?.I suppose we have to still maintain factors as 1:1 in TCUR F table if we are using exchange rate as 0.0264 2. am I right?. But why is this so?. Can't I get rid off TCURF.What is the use of TCURF co-existing with TCURR.Answer :Normally it's used to allow you a greater precision in calaculationsie 0.00011 with no factors gives a different result to0.00111 with factor of 10:1So basing on the above answer, TCURF allows greater precision in calculations.Its factor shud be considered before considering exchange rate .-------------------------------------------------------------------------------------TCURRT CURR table is generally used while we create c urrency conversion types.The currency conversion types will refer to the entries in TCURR defined against each currency ( with time reference) and get the exchange rate factor from source currency to target currency. ------------------------------------------------------------------------------------TCURXTCURX table is used to exactly define the correct number of decimal places for any currency. It shows effect in the BEx report output. ------------------------------------------------------------------------------------How to define F4 Order Help for infoobject for reporting indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
6/15
8/17/13
SAP BI: SAP BI Production Support Issues
Open attributes tab of infoobject definition.In that you will observe column for F4 order help against each attribute of that infoobject like below : This fie ld defines whether and where the attribute should appear in the value help.V alid values:• 00: The attribute does not appear in the value help.• 01: The attribute appears at the first position (to the left) in the value help.• 02: The attribute appears at the second position in the valuehelp.• 03: ......• Altogether, only 40 fields are permitted in the input help. In addition to the attributes, the characteristic itsel, its texts, and the compounded characteristics are also generated in the input help. The total number of these fields cannot exceed 40. So accordingly , the inofobjects are changed> Suppose if say for infobject 0vendor, if in case 0country ( which is an attribute of 0vendor) is not be shown in the F4 help of 0vendor , then mark 0 against the attribtue 0country in the infoobject definition of 0vendor. Dimension Size Vs Fact Size The c urrent size of all dimensions can be monitored in relation to fact table by t-code se38 running report SA P_INFOCUBE_DESIGNS.Also,we c an test the infocube design by RSRV tests.It gives out the dimension to fact ratio. The ratio of a dimension should be less than 10% of the fact table.In the report,Dimension table looks like /BI[C/O]/D[xxx] Fact table looks like /BI[C/0]/[E/F][xxx] Use T -CODE LISTSCHEMA to show the diff erent tables associated with a cube. When a dimension grows very large in relation to the fact table, db optimizer can't choose efficie nt path to the data because the guideline of each dimension having less than 10 percent of the fact table's records has been violated. The condition of hav ing large data growth in a dimension is called degenerative dimension.To fix, move the characteristics to different dimensions. But can only be done when no data in the InfoCube. Note : In case if you have requirement to include item level details in the cube, then may be the Dim to Fact size will obvio usly be more which y ou cant help it.But you c an make the item charecterst ic to be in a line item dimension in that case.Line item dimension is a dimension having only one charect erstic in it.In this case, Since there is only o ne charecterstic in the dimension, the fact table entry can directly link with the SID of the charecterst ic without using any DIMid (Dimid in dimension table usually co nnects the SID of the c harecterstic with the fact) .Since link happens by ignoring dimension table ( not in real sense ) , this will have faster query performance. BW Main tables Extractor related tables: ROOSOURCE - On source system R/3 server, filter by: OBJVERS = 'A' Data source / DS type / delta type/ extract method (table or function module) / etc RODELTAM - Delta type lookup table. ROIDOCPRMS - Control parameters for data transfer fr om the source sy stem, result of "SBIW - General setting - Maintain Control Parameters for Data Tr ansfer" on OLTP system. maxsize: Maximum size of a data packet in kilo by tes STATFRQU: Frequency with which status Idocs are sent MAXPROCS: Maximum number of parallel processes fo r data transfer MAXLINES: Maximum Number of Lines in a DataPacke tMAXDPAKS: Max imum Number of Data Packages in a Delta RequestSLOGSYS: Sourc e sy stem. Query related tables: RSZELTDIR: filter by : OBJVERS = 'A', DEFTP : REP - query, CKF - Calculated key figureReporting component elements, query, variable, structure, formula, etc RSZELTTXT: Similar to RSZELTDIR. Texts of reporting component elementsTo get a list of query elements built on that cube:RSZELTXREF: filter by : OBJVERS = 'A', I NFOCUBE= [cubename] To get all queries of a cube:RSRREPDIR: filter by: OBJVERS = 'A', INFOCUBE= [cubename]To get query change status (version, last changed by, owner) of a indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
7/15
8/17/13
SAP BI: SAP BI Production Support Issues
cube:RSZCOMPDIR: OBJVERS = 'A ' . Workbooks related tables: RSRWBINDEX List of binary large objects (Excel workbooks) RSRWBINDEXT T itles of binary objects (Excel workbooks) RSRWBSTORE Storage for binary large objects (Excel workbooks) RSRWBTEMPLATE Assignment of Excel workbooks as personal templatesRSRWORKBOOK 'Where-used list' for repo rts in workbook s. Web templates t ables: RSZWOBJ Storage of the Web Objects RSZWOBJTXT Tex ts for Templates/Items/Views RSZWOBJXREF Structure of the BW Objects in a TemplateRSZWTEMPLATE Header Table for BW HTML Templates. Data t arget loading/status tables: rsreqdone, " Request-Data rsseldone, " Selection for current Request rsiccont, " Request posted to which InfoCube rsdcube, " Directory of InfoCubes / InfoProvider rsdcubet, " T exts for the InfoCubes rsmonfact, " Fact table monitor rsdodso, " Directory of all ODS Objects rsdodsot, " Texts of ODS Objectssscrfields. " Fields on selection screens Tables holding charactoristics: RSDCHABAS: fields OBJVERS -> A = active; M=modified; D=deliver ed (business content characteristics that have only D ver sion and no A v ersion means not activated yet)TXTT ABFL -> = x -> has text AT TR IBFL -> = x -> has attribute RODCHABAS: with fields TXTSHFL,TXTMDFL,TXTLGFL,ATTRIBFL RSREQICODS. requests in ods RSMONICTAB: all requestsTransfer Structures live in PSAPODSD /BIC/B0000174 000 T rannsfer Structure Master Data lives in PSAPSTABD /BIC/HXXXXXXX Hierarchy :XXXXXXXX /BIC/IXXXXXXX SID Structure of hierarchies: /BIC/JXXXXXXX Hierarchy intervals /BIC/KXXXXXXX Conversion of hierarchy nodes - SID: /BIC/PXXXXXXX Master data (time-independent): /BIC/SXXXXXXX Master data IDs: /BIC/TXXXXXXX Texts: Char./BIC/XXXXXXXX Attribute SID table: Master Data views /BIC/MXXXXXXX master data tables: /BIC/RXXXXXXX View SIDs and values: /BIC/ZXXXXXXX View hierarchy SIDs and nodes:InfoCube Names in PSAPDIMD /BIC/Dcube_name1 Dimension 1....../BI C/Dcube_nameA Dimension 10 /BIC/Dcube_nameB Dimension 1 1 /BIC/Dcube_nameC Dimension 1 2 /BIC/Dcube_nameD Dimension 1 3 /BIC/Dcube_nameP Data Packet /BIC/Dcube_nameT Time/BIC/Dcube_nameU Unit PSAPFACTD /BIC/Ecube_name Fact Table (inactive)/BIC/Fcube_name Fact table (active) ODS Table names (PSAPODSD) BW3.5/BIC/AXXXXXXX00 ODS object XXXXXXX : Actve records /BIC/A XXXXXXX40 ODS object XXXXXXX : New records /BIC/A XXXXXXX50 ODS object XXXXXXX : Change log
indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
8/15
8/17/13
SAP BI: SAP BI Production Support Issues
Previously: /BIC/AXXXXXXX00 ODS object XXXXXXX : Actve records /BIC/A XXXXXXX10 ODS object XXXXXXX : New records T-code tables: tstc -- table of tr ansaction code, text and program name tstct - t-code text . 1What is tickets? And example? The typical tickets in a production Support work could be: 1. Loading any of the missing master data attributes/tex ts. 2. Create A DHOC hierarchies. 3. V alidating the data in Cubes/ODS. 4. If any of the loads runs into errors then resolve it. 5. Add/remove fields in any of the master data/ODS/Cube. 6. Data source Enhancement. 7. Create ADHOC reports. 1. Loading any of the missing master data attributes/tex ts - This would be done by scheduling the info packages for the attributes/texts mentioned by the client. 2. Create ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object. 3. Validating the data in Cubes/ODS. - By using the Validation reports o r by comparing BW data with R/3. 4. If any of the loads runs into errors then resolve it. - Analyze the error and take suitable action. 5. Add/r emove f ields in any o f the master data/ODS/Cube. - Depends upon the requirement 6. Data source Enhancement. 7. Create ADHOC reports. - Create some new reports based on the requirement of c lient. Tickets are the tracking tool by which the user will track the work which we do. It can be a change requests or data loads or whatever. They will of types critical or moderate. Critical can be (Need to solve in 1 day or half a day) depends on the client. After solving the ticket will be closed by informing the client that the issue is solved. T ickets are raised at the time of support project these may be any issues, problems.....etc. If the support person faces any issues then he will ask/request to operator to raise a ticket. Operator will raise a ticket and assign it to the re spectiv e person. Critical means it is most complicated issues ....depends how you measure this...hope it helps. The concept of Ticket varies from contract to contract in between companies. Generally Ticket raised by the client can be considered based on the priority . Like High Priority, Low priority and so on. If a ticket is of high priority it has to be resolved ASAP. If the ticket is of low priority it must be considered only after attending to high priority tickets. Checklists for a support project of BPS - To start the checklist: 1) Info Cubes / ODS / data targets 2) planning areas 3) planning levels 4 ) planning packages 5) planning functions 6) planning layouts 7 ) global planning sequences 8) pro files 9) list of reports 10) process chains 11) enhancements in update routines 12) any ABAP programs to be run and their logic 13) major bps dev issues 14) major bps production support issues and resolution . 2 What are the tools to download tickets from client? Are there any standard tools or it depends upon company or client...? Ye s there are some tools for that. We use Hpopenview. Depends on client what they use. Yo u are right. T here are so many tools available and as you said some clients will develop their own tools using JAVA, A SP and other software. Some c lients use just Lotus Notes. Generally 'Vantive' is used for tracking user requests and tickets. It has a vantive ticket ID, field for description of problem, severity for the business, priority for the user, group assigned etc. Different technical groups will have diffe rent group ID's. User talks to Level 1 helpdesk and they raise ticket. If they can solve issue for the issue, fine...else helpdesk assigns ticket to the Level 2 technical group. Ticket status keeps changing from open, working, resolved, on hold, back from hold, closed etc. The way we handle the tickets vary depending on the client. Some companies use SAP CS to handle the tick ets; we have bee n using Vantage to handle the tickets. T he indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
9/15
8/17/13
SAP BI: SAP BI Production Support Issues
ticket is handled with a change request, when you get the ticket you will have the priority level with which it is to be handled. It co mes with a ticket id and all. It's totally a client specific tool. The common features here can be - A ticket Id, - Priority, - Consultant ID/Name, - User ID/Name, - Date of Post, - Resolving Time etc. There ideally is also a knowledge repository to search for a similar problem and solutions given if it had occ urred earlier. Y ou can also have training manuals (with screen shots) for simple transactions like v iewing a query , saving a workbook etc so t hat such queried can be addressed by using them. When the problem is logged on to you as a consultant, you need to analyze the problem, check if you have a similar problem occurred earlier and use ready solutions, find out the exact server on which this has occurred etc. Yo u have to solve the problem (assuming you will have access to the dev sy stem) and post the solution and ask the user to test afte r the preliminary testing from y our side. Get it transported to production once tested and posts it as closed i.e. the ticket has to be closed. 3.What is User Authorizations in SAP BW? Authorizations are very important, for ex ample you don't want the important financial report to all the users. so, you can have authorization in Object level if you want to keep the authorization for specific in object for this you have to check the Object as an authorization relevant in RSD1 and RSSM tcodes. Similarly you set up the authorization for certain users by giving that users certain auth. in PFCG tcode. Similarly y ou create a role and include the tcodes; BEx repo rts etc into the role and assign this role to t he userid. Posted by Cool Guy at 12:13 PM
36 comments: Pintu December 17, 2009 at 10:51 PM Excellent work !!! would be useful to many folk s in SAP BI/BW Thanks a lot ... keep post ing :) PRATIK L PATEL Reply Replies QA January 9, 2013 at 1:00 PM Hi Pathik, If you are working in SAP BI, so can you please help me in to answer the interview questions. my I D
[email protected] Nilesh Patel Reply
ramesh December 19, 2009 at 3:21 AM excellent material....Many thanks to u Reply
naresh February 4, 2010 at 6:12 AM Excellent...this is very usefull Thanks a lot indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
10/15
8/17/13
SAP BI: SAP BI Production Support Issues
Reply
anki May 8, 2010 at 12:02 PM Anki reddy Excellent work !!! would be useful to many folk s in SAP BI/BW Thanks a lot ... keep post ing :) Reply
ram May 27, 2010 at 11 :26 PM excellent pls update latest issue Reply
poWer May 29, 2010 at 2:37 AM Why Andhra peo ple are more in SAP ? Is that SAP is defined as Super Andhra Pradesh (SAP) Reply
Boya June 16, 2010 at 1 :19 AM HI thq soomuch for this.tc. Reply
shilpa June 30, 2010 at 10:53 PM good job ver y useful Reply
chitti July 8, 2010 at 8:00 AM Sasi...this is venkat,can u confirm that reconstruction is not therein SAP BI from many forums Reply
Venki August 3, 2010 at 1:27 AM Hi Sasi, Good Afternoon! This is V enkat and this is regarding RFC problem while ex traction. When I am try ing connect SAP BI with R/3 and I got RFC problem. Could you please help me what can I do to solv e it. Reply
venu October 22, 2010 at 11 :12 PM could u plz give the scenario for reporting concepts...........ur's venu Reply indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
11/15
8/17/13
SAP BI: SAP BI Production Support Issues
venu October 22, 2010 at 11:14 PM i want business scenario for LO Extract ion with sd module in sap bw or bi............ .......................CHEERS VENU Reply
Kumar October 31, 2010 at 7:15 PM Very nice. i have got more information from this. Please keep posting. it will be helpful to more bi consultants...pavs Reply
prembujju November 17, 2010 at 4:09 AM really its worth Reply
pavan November 26, 2010 at 2:55 AM Thanks Boss, for your giving this material. From Pavan. Reply
santhoshi January 18, 2011 at 12:14 AM Thanks a lot. It is really useful for interview preparation. Reply
deva August 10, 201 1 at 9:51 PM this is very much use full who is entering to sap bw/bi filed. Thanks so Much Reply
lepraveen October 20, 2011 at 3:06 AM POST US MORE IN SUPPORT ISSUES P LZZZZZZZZZZZZZZZ Reply
Berlin Clock October 21, 2011 at 12:10 AM Hi BW GEM, Post us with more BW Support issues... T hanks for more information given us. Suresh Teegala Reply
deva October 21, 2011 at 4:36 AM This info is very much use full for beginners. Reply
indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
12/15
8/17/13
SAP BI: SAP BI Production Support Issues
Chandra February 28, 2012 at 1 1:09 PM The majority of AP Guys are responsible for setting a fake trend in the Industry. Yo u guys c an say thanks t o A meerpet, the hub of all Fake Institutes. Bett er learn SAP Courses the official way & GET CERTIFIED. Reply
Kittu April 18, 201 2 at 4:17 AM The majority of AP Guys are responsible for settling the SAP BI Industry. This BI World say thanks to Them, Ameerpet the Hub of world wide softwares. T hose who learnt SAP Courses on official way & those who GET CERTIFIED are simply sitting in the industry and getting money on the name SAP BI industry. I F Sap BI industry belive only certifie d c onsultants 90% of implimentations become fail and 90% of support projects become scrap.Rest 10% become live .. because all theese certified consultants also depends on fake consultants only. Reply
Srinivas April 18, 201 2 at 7:56 AM HI Experts can any one Explain is L1,L2,L3,L4 MONITORING What type of issue we will get in L1.... L2...L3..L4 Reply
Srinivas April 18, 201 2 at 8:00 AM can any one help me regarding testing phases and deployments how to deploy how many modules will be there in sap bw implementation project explanation clearly step by step i will be waiting for your reply Reply
Srinivas April 18, 201 2 at 8:07 A M DOES WE RUN DIFFERENT PR OCESS CHAINS FOR SD,MM,PP,FI,I C,HR,CRM--ECT...........HOW MANY MODULES ARE THERE WHAT ARE THE EXTRACTION STEPS FOR THESE MODULES WITH SOME SMALL SCENARIOS SOME REPORTS WITH CLEAR SMALL SCENARIOS FOR EXPLANATION IN INTERVIEW I WILL BE WAITING FOR UR RESPONCE Reply
Srinivas April 18, 201 2 at 8:23 AM can any one tell lifecycle of SD,MM,PP,FI,IC,HR,CRM With clear explanation of business Reply
Kiran Kumar June 25, 2012 at 6:00 AM Hey srinivas, got any details for the lifecycle of SD , MM FI CO Reply
chaitanya varma July 1 9, 2012 at 12:04 AM There are speculations that SAP BI is dead and no more projects in it as it overtaken by SA P HANA is that true. Reply
Cool Guy
August 1, 201 2 at 11:56 PM
No Varma, If need to run HANA it some back bone of BW nessary..! indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
13/15
8/17/13
SAP BI: SAP BI Production Support Issues
Reply
Joseph October 1, 2012 at 1:36 AM Hi Sasi, I am attending Classes on SAP BI and can I go ahead with this or some people are saying there is BO and HANA are coming so the opportunity in BI is less. Please give me your suggestion. - Joseph. Reply
Robert P. Calfee December 7, 201 2 at 5:09 AM I am robert.. Good work buddy... keep continuing... it shows yours commitment towards sapbwbi field... Reply
john williams April 9, 2013 at 9:41 PM Hi..i am kartik,, thanks fo r sharing a vailable information in sap bwbi&SAP HANA Reply
dil August 2, 2013 at 2:35 AM hi i raj ,, iam sap consulatnt its ver y nice blog .blo g has effectiv e information on sap bi Reply
magnifictraining August 3, 2013 at 4:59 A M Resources like the one you mentioned here will be very useful to me! I will post a link to this page on my blog. I am sure my v isitors will find that very useful. Hadoop online training Reply
magnifictraining August 13, 201 3 at 3:30 AM Valuable information and exce llent design you got here! I would like to thank you for sharing your thoughts and time into the stuff you post!! Hadoop training Reply Enter your comment...
Comm ent as: Google Account Publish
Preview
indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
14/15
8/17/13
Newer Post
SAP BI: SAP BI Production Support Issues
Home
Older Post
Subscribe to: Post Comments (Atom)
Watermark template. Powered by Blogger.
indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
15/15