Tuesday, March 11, 2008

Tickets and Authorization in SAP Business Warehouse

What is tickets? and example?


The typical tickets in a production Support work could be:


1. Loading any of the missing master data attributes/texts.

2. Create ADHOC hierarchies.

3. Validating 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/texts - This would be done by scheduling the infopackages 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 or 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/remove fields in any of 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 client.


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 what ever. 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.

Tickets 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 respective 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) InfoCubes / ODS / datatargets

2) planning areas

3) planning levels

4) planning packages

5) planning functions

6) planning layouts

7) global planning sequences

8) profiles

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

No comments:

Tutorials on SAP-ABAP

Adobe Interactive Forms Tutorials

Business Server Pages (BSP)

Userexits/BADIs

Web Dynpro for ABAP (Step by step procedure for web dynpro,Tutorials on Web Dynpro,)

ALV Tutorials

Blog Archive

goodsites