Return code for transportation

hi i have done transportation in sap bi/bw it sucessfully completed for se10 after that i have to see return code where i see that return code i think that se03 tcode what is the useful for se03 tcode and what's the purpose of return code kindly explain me briefly about return code and transportation also.

Once your request is released to the next landscape, the log for that particular request appears in SE09.

Give the request name in the Display request option that you have and click the log for that particular request 

You will get the step upto "Method execution", there the return code value will be displayed.

Once the request is realeased you may see logs in SE09/SE10 or SE03.If the transprt request is transproted successfully you may see the step Method execution successful.

You may check the TR queue as well at STMS. In that for particular system queue you may see thataus as green/red for your TR.

Transportation is moving created objects with the landscape that is create the objects in Dev and collect it in the Request which can be move across the landsacpe.

Return codes are nothing but the status of the transport request which is moved to target. It can endup with warnings ( Return code = 4) or successful ( return code = 0) or errors ( return code = 8). It is to identify whether the changes has been moved to the target system successfully or not.

SE03 is the transport organizeris the tool to display request type and request status.

SAP 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.

Some Project issuesIn Shell Project point of view,

*how many process chains u have* -  1800 + chains

and how many loads per day  -  3 schedule per day ( G1, G2, G3 ),  G1 isfor Europe Region ( starts at 6:15 am IST ), G2 is for Asia region  ( Startsat 7:30 pm IST), G3 is for US region ( starts at 12:30 pm IST ).

*modules of projects* -

FSS  ( Financial Services )PGS ( Procurment of Good and Supply),GAME ( Global Asset  Management system )StBC ( Sell to Business Customers ),StRC ( Sell to Retail Customers )HM ( Hydro Corbon Managment ),LSC ( Lubricants supply chain management )

*data source whic u have used -*

2LIS_BAITEM -  Sales Item2LIS_BAIHDR  -  Sales header2LIS_12VCITEM  -  Delivery Item2LIS_VDHRD  -  Delivery Header2LIS_VCItem -  Billing itemThese are some of SAP standdard Data sources, serach in google with  "SAPstanddard Data sources", u can find many more.

***title of project   -*  Shell BAM ( GSAP )*Object of project*  -

*Shell* is a global group of energy and petrochemicals companies, operatingin over 145 countries and employing more than 119, 000 people best known tothe public for service station and for exploring and producing oil and gason land and at sea. GSAP will replace Shell’s fragmented Enterprise ResourcePlanning systems with a harmonized global platform, critical to the deliveryof OP-One benefits. Shell aims to reduce the number of Enterprise ResourcePlanning systems in oil products from 123 to less than 10.*flow of project*   - Not clear with the question, U just can't explain theflow of the projects but can explain flow of a particular Report.like from which source system data is coming to BW, where u are storing itin BW etc,

Eg : R/3 system --> 2LIS_BAITEM -->PSA-->ABAP Routine ( Update rules )-->ODS --> Cube --> Multi Provider --> Query  ( explain Logic in the query )--> Report name.

*roles and responsibilities -*

  - Monitoring Data load activities and recovered failures in Dev, Quality  system as part of Unit Testing** - Preparing the process documents for each and every enhancement.**  - Handled the tickets of different severities by following SOP (Standard  Operating Procedures) and never missed the SLA (Service level agreement).  ** - Involved in solving high-prioritized tickets regarding extractions,  performances issues and also Data load failures.**  - Extensively worked on process chains to automate the Deleting indexes  in Info cubes, Process of info packages, creating indexes, ODS activation,  further updating, PSA request deletion and Attribute change run so on.**  - Experience using the Open Hub Feature to export data from SAP BW to  external systems (Flat files / Database tables).**  - Involved in Unit testing, Integration testing, Regression testing and  User acceptance testing in different servers.**  - Deleted the Delta queues by running the programs for different  applications. And filled the set up tables in production during the  downtime. Before upgrading the BI7.0 system.  - Having experience in RMI&OPSM   interfaces technology.  - Enhancing the existing reports as per the new requirement.  - Monitoring the daily loads to various data targets in the system.  - Monitoring the process chains on the basis of daily, weekly & monthly.

  - Manual loading and rolling up the data into data targets.  - Maintaining the logs for each manual load.  - Created aggregates to improve the query response.  - Performance tuning of queries using aggregates, indexing of Info cubes.  - Responsible for the Rev track system in maintaining, creating RevTracks  for the PGS area

used in transports   -  Shell uses the toll RevTrac  to transfer the objectsfrom Dev to Production systems.Above details are different from project to Project. Understand and preparesome thing similar to ur project as well.

Frequently used ABAP Programs in SAP BI (NW 2004).

Listed below are some of the frequently used ABAP Programs in SAP BI (NW 2004).

Program name  

RSCDS_NULLELIM Delete fact table rows where all Key Figure values are zero. See Note 619826.

RSDG_CUBE_ACTIVATE Activation of InfoCubesRSDG_CUBE_COPY Make InfoCube CopiesRSDG_CUBE_DELETE Delete InfoCubes

RSDG_DODS_REPAIR Activation of all ODS Objects with Navigation Attributes

RSDG_ODSO_ACTIVATE Activation of all ODS ObjectsRSDG_IOBJ_ACTIVATE Activation of all InfoObjectsRSDG_IOBJ_DELETE Deletion of InfoObjectsRSDG_IOBJ_REORG Repair InfoObjectsRSDG_IOBJ_REORG_TEXTS Reorganization of Texts for InfoObjectsRSDG_MPRO_ACTIVATE Activating MultiprovidersRSDG_MPRO_COPY Make Multiprovider CopiesRSDG_MPRO_DELETE Deleting MultiprovidersRS_COMSTRU_ACTIVATE_ALL Activate all inactive Communication StructuresRS_TRANSTRU_ACTIVATE_ALL Activate Transfer StructureRSAU_UPDR_REACTIVATE_ALL Activate Update RulesRRHI_HIERARCHY_ACTIVATE Activate Hierarchies

SAP_AGGREGATES_ACTIVATE_FILL Activating and Filling the Aggregates of an InfoCube

SAP_AGGREGATES_DEACTIVATE Deactivating the Aggregates of an InfoCube

RS_PERS_ACTIVATE Activating Personalization in Bex(Inactive are highlighted)

RSSM_SET_REPAIR_FULL_FLAG Convert Full Requests to Repair Full Requests

SAP_INFOCUBE_DESIGNS Print a List of Cubes in The System and Their Layouts

SAP_ANALYZE_ALL_INFOCUBES Create DB Statstics for all InfoCubes

SAP_CREATE_E_FACTTABLES Create Missing E-Fact Tables for InfoCubes and Aggregates

SAP_DROP_EMPTY_FPARTITIONS Locate/Remove Unused or Empty partitions of F-Fact Table

SAP_DROP_TMPTABLES Remove Temperory Database ObjectsSAP_RSADMIN_MAINTAIN Add, change, delete RSADMIN table entries

CUBE_SAMPLE_CREATE

A fast way to put some "sample" records in a InfoCube. No need to use Flatfiles, just enter the value in a ALV-Grid or let fill the Cube with random value.

SAP_CONVERT_NORMAL_TRANS Convert BasisCube to Transactional Cube and the opposite way around.

Listed below are some of the frequently used Function Modules within BW.

Function Module Description (Function Group RRMX)

RRMX_WORKBOOK_DELETE Delete BW Workbooks permanently from Roles & Favourites

RRMX_WORKBOOK_LIST_GET Get list of all WorkbooksRRMX_WORKBOOK_QUERIES_GET Get list of queries in a workbookRRMX_QUERY_WHERE_USED_GET Lists where a query has been used RRMX_JUMP_TARGET_GET Get list of all Jump TargetsRRMX_JUMP_TARGET_DELETE Delete Jump Targets

Function Module DescriptionMONI_TIME_CONVERT Used for Time Conversions.

CONVERT_TO_LOCAL_CURRENCY Convert Foreign Currency to Local Currecny.

CONVERT_TO_FOREIGN_CURRENCY Convert Local Currency to Foreign Currency.

TERM_TRANSLATE_TO_UPPER_CASE Used to convert all texts to UPPERCASE

UNIT_CONVERSION_SIMPLE Used to convert any unit to another unit. (Ref. table : T006)

TZ_GLOBAL_TO_LOCAL Used to convert timestamp to local time

FISCPER_FROM_CALMONTH_CALC Convert 0CALMONTH or 0CALDAY to Financial Year or Period

RSAX_BIW_GET_DATA_SIMPLE Generic Extraction via Function Module

RSAU_READ_MASTER_DATA Used in Data Transformations to read master data InfoObjects

RSDRI_INFOPROV_READ RSDRI_INFOPROV_READ_DEMO  RSDRI_INFOPROV_READ_RFC

Used to read Infocube or ODS data through RFC

DATE_COMPUTE_DAY  DATE_TO_DAY

Returns a number what day of the week the date falls on.

DATE_GET_WEEK Will return a week that the day is in.

RP_CALC_DATE_IN_INTERVAL Add/Subtract Years/Months/Days from a Date.

RP_LAST_DAY_OF_THE_MONTHS  SLS_MISC_GET_LAST_DAY_OF_MONTH Determine Last Day of the Month.

RSARCH_DATE_CONVERT Used for Date Converstions. We can use in Info Package routines.

RSPC_PROCESS_FINISH     To trigger an event in process chain DATE_CONVERT_TO_FACTORYDATE Returns factory calendar date for a date

 CONVERSION_EXIT_PDATE_OUTPUT Conversion Exit for Domain GBDAT: YYYYMMDD  -> DD/MM/YYYY

CONVERSION_EXIT_ALPHA_INPUT Conversion exit ALPHA, external->internalCONVERSION_EXIT_ALPHA_OUTPUT Conversion exit ALPHA, internal->external RSPC_PROCESS_FINISH Finish a process (of a process chain)RSAOS_METADATA_UPLOAD Upload of meta data from R/3RSDMD_DEL_MASTER_DATA Deletion of master dataRSPC_CHAIN_ACTIVATE_REMOTE To activate a process chain after transport                         USEFUL ABAP-CLASS in NW 7 - BI to fix problems with Transformation

Class CL_RSTRAN_STAT Description

DELETE_VERSION_FROM_DB (Static Method) For deleting a transformations rule version