Explore topic-wise InterviewSolutions in .

ALWAYS the table structure will be the structure of an ODS or InfoCube.

For EXAMPLE if it is an ODS then ACTIVE table structure will be the table.

Always the table structure will be the structure of an ODS or InfoCube.

For example if it is an ODS then active table structure will be the table.

Start routine can be used to ACCESS INFOPACKAGE while UPDATE routines are used while UPDATING the Data TARGETS.

Start routine can be used to access InfoPackage while update routines are used while updating the Data Targets.

START Routines: The start ROUTINE is run for each DataPackage after the data has been written to the PSA and before the TRANSFER rules have been executed. It allows complex computations for a key figure or a characteristic. It has no return value. Its PURPOSE is to execute preliminary calculations and to store them in global DataStructures. This structure or table can be accessed in the other routines. The entire DataPackage in the transfer structure format is used as a parameter for the routine.

Transfer / Update Routines: They are defined at the InfoObject level. It is like the Start Routine. It is independent of the DataSource. We can use this to define Global Data and Global Checks.

Start Routines: The start routine is run for each DataPackage after the data has been written to the PSA and before the transfer rules have been executed. It allows complex computations for a key figure or a characteristic. It has no return value. Its purpose is to execute preliminary calculations and to store them in global DataStructures. This structure or table can be accessed in the other routines. The entire DataPackage in the transfer structure format is used as a parameter for the routine.

Transfer / Update Routines: They are defined at the InfoObject level. It is like the Start Routine. It is independent of the DataSource. We can use this to define Global Data and Global Checks.

• It ENABLES queries that do not contain an authorization relevant object that have been checked into the INFOCUBE.
• It allows summary data to be displayed if the user does not have access to detailed data. For example, if you create 2 authorizations for one user: one with Sales Org * and CUSTOMERS : and second with sales org 1000 and customers *, the user sees all customers for sales org 1000 and only summarized REPORT for other sales org.

Non cumulatives are stored USING a "MARKER" for the current period. A marker is nothing but POINTER referring to a time period. For example an inventory cube marker may refer to the inventory LEVELS as of yesterday.

Non cumulatives are stored using a "Marker" for the current period. A marker is nothing but pointer referring to a time period. For example an inventory cube marker may refer to the inventory levels as of yesterday.

This option is used to distribute data according to TIME. For EXAMPLE, if the source contains calendar week and the target contains calendar DAY, time data is split for each calendar day. Here you can select EITHER the NORMAL calendar or the factory calendar.

This option is used to distribute data according to time. For example, if the source contains calendar week and the target contains calendar day, time data is split for each calendar day. Here you can select either the normal calendar or the factory calendar.

• RESULT This gets the result of the ABAP code.
• RETURN CODE You SET this to 0 if everything is OK; ELSE this RECORD is skipped.
•  ABORT Set this to a value not 0, to abort the centric package.

Amount /QUANTITY is ALWAYS combined with UNITS. For example, sales will be linked to currency and inventory will be linked to quantity in units. In your design if you don't NEED units then you should use NUMBER or integer to improve performance.

Amount /quantity is always combined with units. For example, sales will be linked to currency and inventory will be linked to quantity in units. In your design if you don't need units then you should use number or integer to improve performance.

This defines how the data is displayed in the QUERY definition screen or when the query is executed. Options are from the data displayed, from master data table (all data) and from dimension data. For EXAMPLE let US assume that you have 100 products in total in your material master, 10 products available in a cube and in BEx you display a query for 2 products; the FOLLOWING options for the PRODUCT will display different data:

• Selective data only will display 2 products
• Dimension data will display 10 products
• From master data will display all 100 products

This defines how the data is displayed in the query definition screen or when the query is executed. Options are from the data displayed, from master data table (all data) and from dimension data. For example let us assume that you have 100 products in total in your material master, 10 products available in a cube and in BEx you display a query for 2 products; the following options for the product will display different data:

• Aggregates
• OLAP cache
• Pre-calculated web templates
• Use small amount or result data as starting point of any queries and do the drill down.
• Avoid reporting on ODs and use INFOSET containing ODs for reporting.
• If you use exclusion in reporting (< >), the indices are not used. So avoid using the exclusion but use INCLUSION.
• Use the read mode "H" read when navigating and expanding hierarchies".
• Use compression on Infocubes since the E table is optimized for queries.
• Create additional indexes.
• Run DB statistics often.
• Use secondary indexes on ODS active table.
• Use RSRT TRANSACTION to look at the "Explain Plan" statement.
• If you are running a query on an info provider with non cumulative key figure then suppress summary line items (totals)

These are key figures that are not SUMMARIZED (unlike sales, etc.). Examples are head count and INVENTORY amount. They are ALWAYS SHOWN in relation to a POINT in time. For example, we will ask how many employees we had as of last quarter. We don't add up the head count.

These are key figures that are not summarized (unlike sales, etc.). Examples are head count and inventory amount. They are always shown in relation to a point in time. For example, we will ask how many employees we had as of last quarter. We don't add up the head count.

An InfoSet is an info provider giving DATA by joining data from different sources like ODs and master data. You can also do an OUTER join in an InfoSet. InfoSets can also be used to combine transactional data with master data. For example, if you have cli~anti tying the transaction data and you have price as an attribute of the material. Then you can have an InfoSet with transaction data and material where you will be able to do calculations BASED on material price in BEx.

ANOTHER usage is, if you have ODs you can disable BEx reporting (in the setting) and use the ODs in the InfoSet for reporting, which leads to improved PERFORMANCE

An InfoSet is an info provider giving data by joining data from different sources like ODs and master data. You can also do an outer join in an InfoSet. InfoSets can also be used to combine transactional data with master data. For example, if you have cli~anti tying the transaction data and you have price as an attribute of the material. Then you can have an InfoSet with transaction data and material where you will be able to do calculations based on material price in BEx.

Another usage is, if you have ODs you can disable BEx reporting (in the setting) and use the ODs in the InfoSet for reporting, which leads to improved performance

This is the process by which we delete the request IDS which leads to space savings. All the regular REQUESTS are stored in the F table. When you COMPRESS, the request ID is deleted and data is moved from the F table to the E table. This saves space and IMPROVES performance but the disadvantage is that you cannot delete the compressed requests INDIVIDUALLY. You can, however, still use SELECTIVE deletion.

If you are using noncumulative key figures in a cube, the cube should be compressed as often possible to improve performance.

This is the process by which we delete the request IDS which leads to space savings. All the regular requests are stored in the F table. When you compress, the request ID is deleted and data is moved from the F table to the E table. This saves space and improves performance but the disadvantage is that you cannot delete the compressed requests individually. You can, however, still use selective deletion.

If you are using noncumulative key figures in a cube, the cube should be compressed as often possible to improve performance.

• Assign an INFOOBJECT - direct transfer, no transformation
• Assign a constant eg. If you are loading data from a specified country from a flat file, you can make the country (17s) as a constant and assign the value explicitly
• ABAP routine eg. If you want to do some complex string manipulation, assume that you are GETTING a flat file from legacy data and the cost CENTER is in a field and you have to "massage" the data to get it in. In this case the use of an ABAP routine is most appropriate 
• Formula - for SIMPLE calculations usc formula eg. If you want to convert all lower casc cl~uractcrst o upper case, use the TOUPPER formula. You can use formilla builder to help put your formulas together.

• Identify a fact table.
• Identify the dimension TABLES.
• Define the attributes of the entities.
• Define the granularity of the fact table (how detailed do you want the DATA to be).
• Define pre-calculated key figures.
• Identify SLOWLY changing dimensions.
• Identify AGGREGATES.
• How long will the data be kept.
• How often is the data EXTRACTED.
• From which system is the data to be extracted.

COMPOUNDING defines the superior INFO OBJECT, which MUST be combined to define an object. For EXAMPLE, when you define a cost center, the controlling area is the compounding (superior) object.

Compounding defines the superior info object, which must be combined to define an object. For example, when you define a cost center, the controlling area is the compounding (superior) object.

Answer : NUMC Numeric CHAR (up to 60) IJp to 60 CHARACTERS DATS Date TIMS Time

If yo11 want to filter on key figures or do a ranked ANALYSIS then you USE a CONDITION. For example, you can use a condition to report on the top 10 customers, or customers with more than a million DOLLARS in annual sales.

If yo11 want to filter on key figures or do a ranked analysis then you use a condition. For example, you can use a condition to report on the top 10 customers, or customers with more than a million dollars in annual sales.

RSR00001

RSR00001

A calculated key figure is used to do complicated calculations on key FIGURES such as mathematical FUNCTIONS, PERCENTAGE functions and total functions. For example, you can have a calculated key figure to calculates ales tax based on your sale price.

A calculated key figure is used to do complicated calculations on key figures such as mathematical functions, percentage functions and total functions. For example, you can have a calculated key figure to calculates ales tax based on your sale price.

A BW system feeding data to itself is CALLED the myself data mart. It is created AUTOMATICALLY and ilscs ALE for data transfer.

A BW system feeding data to itself is called the myself data mart. It is created automatically and ilscs ALE for data transfer.

TRANSACTION RSA1

Transaction RSA1

There are a total of 16 DIMENSIONS in a culx. Of these 16, 3 are predefined by SAP and THCSC arc timc, unit and request. This leaves the customer URI TH 1 3 dimensions.

There are a total of 16 dimensions in a culx. Of these 16, 3 are predefined by SAP and thcsc arc timc, unit and request. This leaves the customer uri th 1 3 dimensions.

• USES generated numeric keys and aggregates in its own tables for faster access.
• Uses an external hierarchy.
• Supports multiple LANGUAGES.
• CONTAINS master data common to ;DL cubcs.
• Supports slowly changing dimensions.

To DISABLE MULTIPLE user logins within the same client implement this parameter in the instance profile:

To disable multiple user logins within the same client implement this parameter in the instance profile:

The following TABLES HOLD information about change REQUESTS.

E070 Change request headers

E071 Change request object LISTS

The following tables hold information about change requests.

E070 Change request headers

E071 Change request object lists

PLACE the ANSWERS in table USR40.

Place the answers in table USR40.

RSA7, LBWQ, IDOCS and SMQ1.

RSA7, LBWQ, Idocs and SMQ1.

This field from the EXTRACTION STRUCTURE of a DataSource meets one of the following criteria:

1. The field has the following type: Time stamp. New RECORDS to be LOADED into the BW using a delta upload have a higher entry in this field than the time stamp of the last extraction.
2. The field has the following type: Calendar day. The same criteria applies to new records as in the time stamp field.
3. The field has another type. This case is only supported for SAP Content DATASOURCES. In this case, the maximum value to be read must be displayed using a DataSource-specific exit when beginning data extraction.

This field from the extraction structure of a DataSource meets one of the following criteria:

FI Flow Basically there are 5 major topics/areas in FI,

1. GL Accounting -related tables are SKA1, SKB1 Master DATABASE and BSAS are the Transaction Data
2. ACCOUNT Receivables- related to Customer All the SD related data when transferred to FI these are created. Related Tables BSID and BSAD
3. Account Payable - related Vendor All the MM related documents data when transferred to FI these are created Related Tables BSIK and BSAK All the above six tables data is present in BKPF and BSEG tables You can link these tables with the help of BELNR and GJAHR and with Dates also.
4. Special Purpose Ledger. which is rarely used.
5. Asset Management In CO there are Profit center Accounting Cost center Accounting will be there.

FI Flow Basically there are 5 major topics/areas in FI,

From a QUERY name or description, you would not be able to judge whether the query is having any exception. There are TWO ways of finding exception against a query:1. Execute QUERIES one by one, the one which is having background color as exception reporting are with exceptions.2. Open queries in the BEX Query Designer. If you are finding exception tab at the right side of filter and rows/column tab, the query is having exception.

From a query name or description, you would not be able to judge whether the query is having any exception. There are two ways of finding exception against a query:1. Execute queries one by one, the one which is having background color as exception reporting are with exceptions.2. Open queries in the BEX Query Designer. If you are finding exception tab at the right side of filter and rows/column tab, the query is having exception.

BeX query Global STRUCTURE to local structure Steps; ***a local structure when you want to add structure elements that are unique to the specific query. Changing the global structure changes the structure for all the queries that use the global structure. That is reason you go for a local structure.Coming to the navigation part--In the Bex Analyzer, from the SAP Business EXPLORER toolbar, choose the open query icon (icon that looks like a FOLDER) On the SAP Bex Open dialog box:Choose Queries.Select the desired Info Cube Choose New.On the Define the query SCREEN:In the left frame, expand the Structure node.Drag and drop the desired structure into either the Rows or Columns frame.Select the global structure.Right-click and choose Remove reference.A local structure is created.Remember that you cannot revert back the changes made to global structure in this regard. You will have to delete the local structure and then drag and drop global structure into query definition.*When you try to save a global structure, a DIALOGUE box prompts you to confirm changes to all queries. that is how you identify a global structure*

BeX query Global structure to local structure Steps; ***a local structure when you want to add structure elements that are unique to the specific query. Changing the global structure changes the structure for all the queries that use the global structure. That is reason you go for a local structure.Coming to the navigation part--In the Bex Analyzer, from the SAP Business Explorer toolbar, choose the open query icon (icon that looks like a folder) On the SAP Bex Open dialog box:Choose Queries.Select the desired Info Cube Choose New.On the Define the query screen:In the left frame, expand the Structure node.Drag and drop the desired structure into either the Rows or Columns frame.Select the global structure.Right-click and choose Remove reference.A local structure is created.Remember that you cannot revert back the changes made to global structure in this regard. You will have to delete the local structure and then drag and drop global structure into query definition.*When you try to save a global structure, a dialogue box prompts you to confirm changes to all queries. that is how you identify a global structure*

Generally attribute CHANGE run is used when there is any change in the master data. it is used for realignment of the master data. Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the Sid’s so that u may not have any problem when loading the transaction data in to data targets. The detail explanation about Attribute change run. The HIERARCHY/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases:

1. Finding all AFFECTED aggregates
2. Set up all affected aggregates again and write the result in the new aggregate table.
3. Activating ATTRIBUTES and hierarchies
4. Rename the new aggregate table. When renaming, it is not possible to execute QUERIES.

In some databases, which cannot rename the indexes, the indexes are also created in this phase.

Generally attribute change run is used when there is any change in the master data. it is used for realignment of the master data. Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the Sid’s so that u may not have any problem when loading the transaction data in to data targets. The detail explanation about Attribute change run. The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases:

In some databases, which cannot rename the indexes, the indexes are also created in this phase.

How to do basic LO extraction for SAP-R3-BW

1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create INFOPACKAGE and under the update tab select the initialize DELTA process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and CHANGE the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.

How to do basic LO extraction for SAP-R3-BW

Functional Specs are requirements of the business user.Technical Specs translate these requirements in a technical fashion.Let's say Functional Spec says,

1. the user should be able to enter the KEY date, Fiscal Year, Fiscal Version.
2. The Company variable should be defaulted to USA but then if the user wants to change it, they can check the drop down list and choose other countries.
3. The calculations or formulas for the report will be displayed in precision of one decimal POINT.
4. The report should return values for 12 months of data DEPENDING on the fiscal year that the user enters Or it should display in quarterly values. Functional specs are also called as Software requirements.

Now from this Technical Spec follows, to resolve each of the line items listed above.

1. To give the option of key date, Fiscal year and Fiscal Version – certain Info Objects should be available in the system. If available, then should we create any VARIABLES for them - so that they are used as user entry variable. To create any variables, what is the approach, where do you do it, what is the technical of the objects you'll use, what'll be the technical name of the objects you'll Crete as a result of this report.
2. Same explanation goes for the rest. How do you set up the variable,
3. What changes in PROPERTIES will you do to get the precision.
4. How will you get the 12 months of data. What will be the technical and display name of the report, who'll be authorized to run this report, etc are clearly specified in the technical specs.

Functional Specs are requirements of the business user.Technical Specs translate these requirements in a technical fashion.Let's say Functional Spec says,

Now from this Technical Spec follows, to resolve each of the line items listed above.

Its depends on your project requirement. Customized cubes are not mandatory for all the projects. If your business requirement is differs from given scenario (BI content cubes) then only we will opt for customized cubes. Normally your BW customization or creation of new INFO providers all are depending on your source system. If your source system other that R3 then you should GO with customization of your all objects. If your source system is R3 and your users are USING only R3 standard business scenarios like SD, MM or FI... etc., then you don’t want to create any info providers or you don’t want to ENHANCE anything in the existing BW Business Content. But 99% this is not possible. Because surely they should have included their new business scenario or new enhancements. 

Its depends on your project requirement. Customized cubes are not mandatory for all the projects. If your business requirement is differs from given scenario (BI content cubes) then only we will opt for customized cubes. Normally your BW customization or creation of new info providers all are depending on your source system. If your source system other that R3 then you should go with customization of your all objects. If your source system is R3 and your users are using only R3 standard business scenarios like SD, MM or FI... etc., then you don’t want to create any info providers or you don’t want to enhance anything in the existing BW Business Content. But 99% this is not possible. Because surely they should have included their new business scenario or new enhancements. 

SAP has DEFINED a business BLUEPRINT phase to help extract PERTINENT INFORMATION about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that UNCOVERS how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements.

SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements.

BI7 is PSA used only for Data LOAD from SOURCE System into BW

BI7 is PSA used only for Data load from Source System into BW

Data Transfer Process:

Data transfer process (DTP) loads data WITHIN BI from one object to another object with respect to transformations and filters. In short, DTP determines how data is transferred between two persistent objects.

It is used to load the data from PSA to data TARGET (cube or ods or infoobject) thus, it replaced the data mart interface and the INFO Package.

Data Transfer Process:

Data transfer process (DTP) loads data within BI from one object to another object with respect to transformations and filters. In short, DTP determines how data is transferred between two persistent objects.

It is used to load the data from PSA to data target (cube or ods or infoobject) thus, it replaced the data mart interface and the Info Package.

You get information on where the web template details are stored from the following tables :

RSZWOBJ Storage of the Web OBJECTS

RSZWOBJTXT Texts for Templates/Items/ Views

RSZWOBJXREF Structure of the BW Objects in a Template

RSZWTEMPLATE Header Table for BW HTML Templates

You can check these tables and search for your web template entry . However, If I UNDERSTAND your question CORRECTLY, you will have to open the template in the WAD and then make the corrections in the same to correct it.

You get information on where the web template details are stored from the following tables :

RSZWOBJ Storage of the Web Objects

RSZWOBJTXT Texts for Templates/Items/ Views

RSZWOBJXREF Structure of the BW Objects in a Template

RSZWTEMPLATE Header Table for BW HTML Templates

You can check these tables and search for your web template entry . However, If I understand your question correctly, you will have to open the template in the WAD and then make the corrections in the same to correct it.

Marker update is just like check point.

ie it will give the snapshot of the stock on a particular date ie when was the marker updated.

Because we are using Non cumulative key FIGURE it will lot of time to calculate the current stock for example at report time. To OVERCOME this we use marker update

Marker updates do not summarize the data.. In inventory management SCENARIOS, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will ADD and SUBTRACT the values for each record.

In the absence of marker update, the data will be added up and will not provide the correct values.

Marker update is just like check point.

ie it will give the snapshot of the stock on a particular date ie when was the marker updated.

Because we are using Non cumulative key figure it will lot of time to calculate the current stock for example at report time. To overcome this we use marker update

Marker updates do not summarize the data.. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record.

In the absence of marker update, the data will be added up and will not provide the correct values.

TRY to CHECK the SYSTEM LOGS through SM21 for the same.

Try to check the system logs through SM21 for the same.

The R/3 database structure for accounting is much more easier than the Logistical structure.

Once you post in a ledger that is DONE. You can correct, but that give just another posting.

BI can get information direct out of this (relatively) simple database structure.

In LO, you can have an order with multiple deliveries to more than one delivery ADDRESSES. And the payer can ALSO be different.

When 1 item (order line) changes, this can have its reflection on order, supply, delivery, invoice, etc.

Therefore a special record structure is built for Logistical reports. and this structure now is used for BI.

In order to have this special structure filled with your starting position, you must run a set-up. From that moment on R/3 will keep filling this LO-database.

If you wouldn't run the setup. BI would start with DATA from the moment you start the filling of LO (with the logistical cockpit)

The R/3 database structure for accounting is much more easier than the Logistical structure.

Once you post in a ledger that is done. You can correct, but that give just another posting.

BI can get information direct out of this (relatively) simple database structure.

In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.

When 1 item (order line) changes, this can have its reflection on order, supply, delivery, invoice, etc.

Therefore a special record structure is built for Logistical reports. and this structure now is used for BI.

In order to have this special structure filled with your starting position, you must run a set-up. From that moment on R/3 will keep filling this LO-database.

If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistical cockpit)

FOLLOW these steps to filling the set up table.

1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents: ORDERS) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW SYSTEM and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button..
9. Now you can go to your data target and see the delta record.

Follow these steps to filling the set up table.

You can check that in RSRT tcode.

EXECUTE the QUERY in RSRT and after that follow the below steps

Go to SE16 and in the resulting screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT-DM for BI 7.0 and press enter you can VIEW all the details about the query like time TAKEN to execute the query and the TIMESTAMPS

You can check that in RSRT tcode.

execute the query in RSRT and after that follow the below steps

Go to SE16 and in the resulting screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT-DM for BI 7.0 and press enter you can view all the details about the query like time taken to execute the query and the timestamps

Synchronous UPDATING (V1 Update)

The statistics update is made synchronously with the document update.

While updating, if problems that result in the termination of the statistics update OCCUR, the original documents are NOT saved. The cause of the termination should be investigated and the problem solved.

Subsequently, the documents can be ENTERED again. Radio button: V2 updating

Synchronous Updating (V1 Update)

The statistics update is made synchronously with the document update.

While updating, if problems that result in the termination of the statistics update occur, the original documents are NOT saved. The cause of the termination should be investigated and the problem solved.

Subsequently, the documents can be entered again. Radio button: V2 updating

V1 Update: whenever we create a transaction in R/3(e.g.Sales Order) then the entries get into the R/3 Tables (VBAK, VBAP..) and this takes PLACE in V1 Update.

V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values get into STATISTICAL Tables, from where we do the extraction into BW.

V3 Update: Its PURELY for BW extraction.

V1 Update: whenever we create a transaction in R/3(e.g.Sales Order) then the entries get into the R/3 Tables (VBAK, VBAP..) and this takes place in V1 Update.

V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values get into Statistical Tables, from where we do the extraction into BW.

V3 Update: Its purely for BW extraction.

If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select MANUAL process.

You NEED to reprocess this IDOC which are RED. For this you can take help of Any of your Team (ALE IDOC Team or BASIS Team) Or Else

you can push it manually. Just search it in bd87 screen only to reprocess.

ALSO, try to find why this Idocs are stuck there.

If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select Manual process.

You need to reprocess this IDOC which are RED. For this you can take help of Any of your Team (ALE IDOC Team or Basis Team) Or Else

you can push it manually. Just search it in bd87 screen only to reprocess.

Also, try to find why this Idocs are stuck there.

In RSA1 -> Transport Connection you can collect the Queries and the Role and after this you can transport them (ENABLING the transport in SE10, import it in STMS

1. RSA1
2. Transport connection (button on the left bar MENU)
3. Sap transport -> OBJECT Types (button on the left bar menu)
4. Find Query Elements -> Query
5. Find your query
6. Group necessary object
7. Transport Object (car icon)
8. Release transport (SE10 T-code)
9. LOAD transport (STMS T-code)

In RSA1 -> Transport Connection you can collect the Queries and the Role and after this you can transport them (enabling the transport in SE10, import it in STMS