SAP BI

Useful SAP Links

2018-10-11T02:25:00.000-07:00

SAP HANA

http://www.biportal.org/Resources/Documents/cool%20features%207.4.pdf
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7018dff1-187c-2f10-ef86-c6cde2cef5e4?QuickLink=index&overridelayout=true&54863912240010
http://scn.sap.com/docs/DOC-51568

SAP BW

Data modelling

ETL

Reporting

2014-10-15T07:20:00.000-07:00

SAP FICO overview from Peter Ezzat

2014-05-14T10:16:00.001-07:00

SAP BusinessObjects Business Intelligence 4.0 Maintenance Strategy from SAP Analytics

SAP BI SD Implementation

2014-05-11T22:07:00.001-07:00

SAP BI Implementation

How to Add an SAP BusinessObjects Xcelsius Dashboard to a Transport Request in SAP BW

2013-01-14T08:06:00.001-08:00

Database Joins

2012-11-29T19:53:00.000-08:00

"Creating Access Relationships creates a family of data information harmonising the use of queries and reports..."

Access Relationships enable data in one table to be joined to data in another table which generally serves as the basis for your reports (typically via a query).

Without relationships in place, you are restricted to how data is managed from the reporting point of view and each table sits as a 'stand-alone' file.

As part of the database normalisation process , setting Access relationships keeps to the rules and general good practice of RDBMS Relational Database Management System.

Joining tables together can be set in one of three ways:

Table level via the 'Relationship' Window
Query level via the 'Query' Window
Both Table and Query levels

In order to join two tables together, there are rules that must be observed which are:

1. Field Data Types - the fields which are to be joined across two tables must be the same data type. Therefore a 'Text' data type cannot join to a'Number' data type field.

The exception to the above is a 'Number' data type can join to a'AutoNumber' data type providing both are set to same size (i.e. Long Integer).

2. Field Sizes - applies to only the 'Text', 'Number' and 'AutoNumber' data types where the size or length of a field can be modified. For the numeric data types, the size must be the same and therefore a 'Number' data type field size in one table which is set to 'Double' cannot join to a field whose size is set for example to 'Integer'.

The 'Text' data type is a little more relaxed as the joining field must be at least the same length (or greater) of characters (bytes)

Note: It is possible to join different field sizes with 'Number' data types provided the field can be cast and fit into the larger size. This is not good practice and in any event shouldn't the data type be the same across tables for the same data value?

3. Field Names? - this is not essential as field names are not checked when joining tables together. But for user-friendliness, having the same field name makes life just a little bit easier!

As a reminder, you may want to review data types and sizes before setting any primary or foreign key indexes.

Setting the correct keys (primary and foreign) must be considered and applied before joining tables together.

The type of key applied will lead to the type of Access relationship you can have and in essence there are four:

One-to-one
One-to-many
Many-to-one
Many-to-many

The 'one' side is associated to a unique value for a field and is referred as the primary key. The 'many' side is an indexed field which allow for duplicate values in a field and is known as the foreign or secondary key.

To get a better understanding of these keys, please review primary and foreign keys.

One-to-One This type of Access relationship is seldom used but it allows you to join two tables together whereby each row (record) in table A has a related row (only one record) in table B.

Types of uses for this setup could be a way to overcome some management, performance or sensitive data issues. For example, if you had two tables dealing with employee information where one table Personnelstores general profile information including surname, ID and contact information and the other table Payroll containing salary and other sensitive data, then there would only be one record per individual in each table(joined by a common unique value - 'Employee ID').

Other times, this type of Access relationship may be used is when overcoming limitations and performance problems. For example, for a table to hold over 100 fields (maximum is 255) will require a lot more memory than a table with far less. If you had a client table which held a lot more profile information than the normal, consider splitting into two tables; table A to hold the main essential fields and table B holding the less frequently used data (especially when using 'Memo' and 'OLE Object' data types). The common field would be unique in both (i.e. Customer ID).

One-to-Many / Many-to-One This is the most common type of Access relationship where a single record in one table is joined to one or more records in another table with the same matching data value from the unique value of the first table.

There are many examples to highlight but imagine if you have a table calledCustomers which contains the client's details including name, address and contact and another table of transactions called Orders where a customer can place more than one order over a period of time. The common field between the two is the Customer ID and is unique from Customers but duplicated in the Orders table for each instance an order was placed for the same customer.

This type of Access relationship is sometimes referred as parent-child ormaster-detail. Terminology sometimes used when talking about a customerhaving never placed an order is referred as a widow record (a parent with no children). The other way around where an order does not have a knowncustomer is referred as an orphan record.

Many-to-Many This type of Access relationship cannot be created directly in Access and therefore will require three tables. It is where in table A, a record can refer to one or more records in table B and table B can be linked to one or more records in table A (a two-way 'one-to-many/many-to-one' link) but requires a third interim table C!

This relationship happens by default if you have created multiple tables using the database normalisation techniques and have joined tables together using the 'one-to-many' relationships.

For example, for each order stored in the Orders table which holds the header information including date, customer ID and shipping information has a second table which stores the item details that make up the order calledOrder Details where the Order ID field is common to both tables causing a'one-to-many' relationship. For each item in the Order Details table, a product is held identifying the item and its product information which in turn is held in a separate table called Products containing name, stock levels and price. The relationship between Order Details and Products is a 'many-to-one' where the common field is Product ID.

So we have three tables; Orders linked to Order Details linked to Productsand therefore we have an indirect relationship between Orders and Products (the Order Details table sitting between the two).

In the 'real world', this would be a typical relationship because you have one order with many products (items) and the product is sold across many orders. The middle table Order Details handles the two way relationship.

In addition to Access relationships, you also have three different join types to choose from:

Equi-Join (Inner Join)
Left-Join (Outer Join)
Right-Join (Outer Join)

Equi-Join By default, when you join two tables together, it sets it as anEqui-Join also referred to as the Inner Join.

It tells Access to show only records from the two tables where they both have the matching values. Any record in either table that does not have a corresponding record in the other table is simply suppressed from view.

For example, if we continue to use our Customers and Orders table relationship scenario of a 'one-to-many', it would only return records where the matching Customer ID field existed across the two tables. Therefore, it will display all customers that have placed at least one order and only display orders that have a known customer account.

Any orders that do not have a matching Customer ID will be suppressed and in the 'real world' this would be unusual due to the fact you first would choose and assign a customer before placing the order!

However, it is possible to have a customer as a new prospect that has yet to place their first order and therefore would also be suppressed with this type of join.

Note: Access relationships cause and effect - Before adding any criteria, you will find records have been filtered because of this type of join. If you had 99 out 100 records in table A each having 3 records from table B with the remaining 1 record not having any records from table B, then the result recordset would be 297 (99 X 3) suppressing the 1 record.

Left/Right-Joins which are also known as Outer Joins change the relationship link. Access will force records to be displayed whether there is a matching value or not.

In Access, you can only set one direction of outer join (left or right) at time and it tells the system from which direction to force the records to be all shown.

For example, using our Customers and Orders table scenario, creating aRight-Join (pointing from Customers to Orders) will show all customers whether they have orders related or not.

Where there are records from Customers which do not have any related orders are said to be Widow Records (parent with no children).

Using the Left-Join example for the above tables will force all orders to be displayed and only related customers.

This type of example may not be different from an Equi-Join if the relational database has been designed with care as in the 'real world' you wouldn't really have an order issue without first choosing a customer!

This type of join will be driven towards data that may have been imported from an external system where Access cannot deal with those orphanrecords (records without a parent).

There it is, Access relationships understood!

Don't get too wrapped with up different joins, keep it simple and as you develop the database you will learn to modify the rules.

The next step is to create the joins which is covered under how to apply the joins and create a relational database.

Activating BW objects

2012-08-20T20:34:00.001-07:00

Info Objects:
RSDG_IOBJ_ACTIVATE Activation of InfoObject (without automatic transport connection)

Info Cube:
RSDG_CUBE_ACTIVATE Activation of Info Cubes

Multiprovider:
RSDG_MPRO_ACTIVATE Activating Multiprovider

ODS:
RSDG_ODSO_ACTIVATE Activating/Repairing Data Store Objects (Without Automatic Transport Connection)

Transfer Structure:
RS_TRANSTRU_ACTIVATE_ALL Activate all active transfer structures for a source system

Data Source:
RSDS_DATASOURCE_ACTIVATE_ALL Activate All DataSources of a Log System

Communication Structure:
RS_COMSTRU_ACTIVATE_ALL Activate all inactive communication structures

Update Rule:
RSAU_UPDR_REACTIVATE_ALL Report RSAU_UPDR_REACTIVATE_ALL

Labels

2012-05-17T03:28:00.003-07:00

How to transfer the Data from SAP-System to Non-SAP system without additional Cost/License

How to transfer the Data from SAP-System to Non-SAP system without additional Cost/License

Can we Transfer the Reports/Data from SAP-System to Non-SAP system without additional Cost/License?.

Yes, we can transfer using with simple FTP/SFTP.

Is it required any additional License or additional Cost?

No.

Is there any complex Coding or Configuration required?.

No, it is very simple.

How Can I transfer the Report/Data?.

Here I'm considering SAP-BW system running in UNIX operating system and Windows XP as Non-SAP System.

Source : SAP-BW System running on UNIX.

Destination : SQL-Server running on Windows XP.

Scenario:

I have data in SAP-BW System, e.g. InfoCube 0SD_C03. And 0SD_C03 is having some reports and want to transfer the reports data to SQL-Server running on Windows XP.

Else

You may need to transfer ECC Data to SQL-Server running on Windows XP. For this also you can use the same logic.

Here are the steps...

Set the Variable values using fixed restrictions or Using SAP/Customer Exits variables in BW Report. (If you have any variables.)
Using RSCRM_BAPI TCode schedule the report based on your requirement i.e. daily, weekly...etc. And then dump the report result into one path (Directory) in Application Server. E.g.: Directory: /usr/sap/BP1/DVEBMGS00/work/
You can see this path in AL11 Tcode.
Open the port in BW Application server.
Create FTP/SFTP User ID in Application server level in BW System.
Using Windows Script you call the Report in /usr/sap/BP1/DVEBMGS00/work/ path in BW system to SQL-Server running on Windows XP. This script you can save as a batch file and schedule it based on your requirement in Windows Server.

Sample Windows script:

Note: For better understanding or Changing of the above code, please contact your Windows system Administrator. This is just sample code only.

Here I’m using RSCRM_BAPI Tcode to dump the report result into Application Server. You can use your own method also. Our intension is how to transfer the data from SAP to Non-SAP System.

Inflow/Outflow

2012-04-02T13:06:00.000-07:00

The Business Information Warehouse (SAP BW) key figures are either about cumulative values (for example sales, number of pieces sold) or non-cumulative values (for example number of employees, warehouse stock). Key figures that are defined as non-cumulative values form a key figure group with further key figures that contain the values for the non-cumulative value changes (inflows and outflows). In order to be able to plan non-cumulative values, all key figures that belong to such a key figure group must therefore be compared with each other, so that no inconsistencies occur.
The function to accumulate balances offers you an alternative approach for this comparison, by determining values for the respective missing key figure, for the updating of balances over time. You determine the key figures, from which the key figure group is made up, here within SEM-BPS (and not with the key figure definition in SAP BW). Either the closing balance or the non-cumulative value change (applied to the period) can be calculated. Here is the following general formula that it is based on:

Closing balance = opening balance + inflows – outflows
as well as
Opening balance (current period) = closing balance (current period – 1)
The time period for which the update of balances is executed, results from the value restriction of the time characteristic you selected in the planning package or level.
The general use of this function is that you receive direct access to all balance-relevant values for a given key figure for every desired period. This occurs without time-intensive translations having to be carried out beforehand, as would be necessary for the query of values direct from the data basis.
Only apply the function to accumulate balances for those key figures that are not defined as non-cumulative values in the Business Information Warehouse. The reason for this is that the additional key figures (for non-cumulative value changes or inflows and outflows) compounded to a non-cumulative value defined in SAP BW are not included in InfoCubes, which contain a non-cumulative value. As a result no access possibilities would exist for the additional key figures from SEM-BPS. You can determine the exact key figure definition with the help of the SAP BW Administrator Workbench.
Features : When creating a planning function to accumulate balances, only select the characteristic that contains the time dimension. The value restriction of this characteristic determines the time period in the planning package or level, for which the update of balances takes place.
In the parameter groups for the function to accumulate balances, you define which balances should be planned. For this you can choose four key figures at most for the opening balance, the closing balance as well as the inflows and outflows in the balance.
It is not absolutely necessary to enter a key figure name for all fields. By omitting a key figure you can use the function in various ways:
If no key figure name is entered for the outflows in the balance, then the function interprets the key figure for the inflows as the non-cumulative value change that can also have a negative value. Therefore the value of the key figure that you enter under inflows corresponds in this case to the balance of the outflows and inflows. A detailed conclusion about the real outflows and inflows is not possible with this type of data retention.
If no key figure name is entered for the opening balance, then no closing balance can be determined for the first period of the package. On the contrary it is assumed that the closing balance has already been determined in the first period of the planning package and can serve as the starting point for the update of balances in the following periods.
In addition in the parameter groups you can define whether the closing balance should be calculated according to the formula mentioned above, or whether inversely the non-cumulative value change is to be calculated on the basis of planned closing balances according to the following formula:
Balance change (current period) = closing balance (current period) – closing balance (current period – 1)
Example 1: Calculating the Closing Balance
Period Opening Balance Inflow Outflow Closing Balance
001.2000 100 80 20 160
002.2000 160 50 70 140
003.2000 140 120 30 230
Example 2: Calculating the Non-Cumulative Value Change on the Basis of the Closing Balance
Period Opening Balance Inflow Outflow Closing Balance
001.2000 100 60 160
002.2000 160 -20 140
003.2000 140 90 230

Date Amount Open_Bal Close_Bal
1/01/2012 100 0 100
3/01/2012 -20 100 80
4/01/2012 200 80 280
4/01/2012 10 280 290
5/01/2012 10 290 300

Variable Selection : From Date and To Date.
Create Customer Exit Variable on Calendar Day (0CALDAY)
Create ZC_FYFD variable on 0CALDAY, the properties are..
Type of Variable = Characteristic
Variable Name = ZC_FYFD
Processing by = Customer Exit
Characteristic = Calendar Day
Variable Represents = Interval
Variable Entry = Mandatory
Check ready for input

********************Begin of Data Type Declaration*********************************
DATA: L_S_RANGE TYPE RSR_S_RANGESID,
LOC_VAR_RANGE LIKE RRRANGEEXIT,
zbuper LIKE t009b-poper,
zbdatj LIKE t009b-bdatj,
ZDT1 TYPE SY-DATUM,
ZFDT TYPE SY-DATUM,
ZLDT TYPE SY-DATUM.
********************End of Data Type Declaration************************************
****************************************Begin***************************************
********To get the Financial Year From and To dates based on System/Current Date****

CASE i_vnam.
WHEN 'ZC_FYFD'.
IF i_step = 1.
ZDT1 = SY-DATUM.
CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
EXPORTING
I_DATE = ZDT1
* I_MONMIT = 00
I_PERIV = 'V3'
IMPORTING
E_BUPER = zbuper
E_GJAHR = zbdatj
EXCEPTIONS
INPUT_FALSE = 1
T009_NOTFOUND = 2
T009B_NOTFOUND = 3
OTHERS = 4
.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'FIRST_AND_LAST_DAY_IN_YEAR_GET'
EXPORTING
I_GJAHR = zbdatj
I_PERIV = 'V3'
IMPORTING
E_FIRST_DAY = ZFDT
E_LAST_DAY = ZLDT
EXCEPTIONS
INPUT_FALSE = 1
T009_NOTFOUND = 2
T009B_NOTFOUND = 3
OTHERS = 4
.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
l_s_range-low = ZFDT.
l_s_range-high = ZLDT.
l_s_range-sign = 'I'.
l_s_range-opt = 'BT'.
APPEND l_s_range TO e_t_range.
ENDIF.
ENDCASE.
*****************************************End*****************************************
****
Save and Activate the above code and project.

Code Example:
DATA: L_S_RANGE TYPE RSR_S_RANGESID.
* Current month to date variable ZCMTD example.
WHEN 'ZCMTD'.
* you variable name
data: ZCMTD_LOW like sy-datum.
*defining variable for using as a starting date of the interval
ZCMTD_LOW = sy-datum. *initializing it with the current date
ZCMTD_LOW+6(2) = '01'.
*replacing last two symbols (day) in the current date with '01'(see ref.1)
CLEAR L_S_RANGE.
L_S_RANGE-LOW = ZCMTD_LOW.
*initializing low interval limit
L_S_RANGE-HIGH = SY-DATUM.
*initializing high interval limit
L_S_RANGE-SIGN = 'I'.
*defining interval as inclusive
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
* Current month to date variable ZCMTD example end.
ENDCASE.

The result of this will be an interval from the first day of the current month till
the current system date.

SAP V1, V2 and V3 Updates

2012-04-01T23:35:00.000-07:00

SAP V1, V2 and V3 Updates
Document update is where the transaction (documents) are updated in the application tables. This update is normally a synchronous update, i.e. if the update does not go through for whaterever reason, the complete transaction is rolled back.

Statistical update is the update of statistics for the transaction – like LIS or extractors for BW.

V1 – synchronous update. If the update is set to V1, then all tables are update and if any one fails, all are rolled back. Done for all transaction plus critical statistics like credit management, etc.

V2 – asynchronous update – transactions are updated and statistical updates are done when the processesor has free resources. If the statistical update fails, the transaction would have still gone through and these failures have to be addressed separately.

V3 – batch update – statistics are updated using a batch (periodic) job like every hour or end of the day. Failure behaviour is same as V2 updates.
Statistical update is also used as to describe the initial setup of the statistical tables for LO/LIS. When old transactions are updated in LO/LIS as a one time exercise, then it is called a statistical update also. Once these tables are upto date will all transactions, then every transaction is updated in them using V1, V2 or V3.

Function Modules within BW

2011-07-28T21:54:00.000-07:00

Function Module	Description (Function Group RRMX)
RRMX_WORKBOOK_DELETE	Delete BW Workbooks permanently from Roles & Favourites
RRMX_WORKBOOK_LIST_GET	Get list of all Workbooks
RRMX_WORKBOOK_QUERIES_GET	Get list of queries in a workbook
RRMX_QUERY_WHERE_USED_GET	Lists where a query has been used
RRMX_JUMP_TARGET_GET	Get list of all Jump Targets
RRMX_JUMP_TARGET_DELETE	Delete Jump Targets
Function Module	Description
MONI_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	Used to read Infocube or ODS data through RFC
RSDRI_INFOPROV_READ_DEMO
RSDRI_INFOPROV_READ_RFC
DATE_COMPUTE_DAY	Returns a number what day of the week the date falls on.
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	Determine Last Day of the Month.
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->internal
CONVERSION_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/3
RSDMD_DEL_MASTER_DATA	Deletion of master data
RSPC_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 the transformation version from database, helpful if the transformation metadata are corrupted.
DELETE_RULE_FROM_DB	For deleting a given rule of transformation

Useful ABAP Programs in SAP BI

2011-07-28T21:50:00.000-07:00

Program name	Details
RSCDS_NULLELIM	Delete fact table rows where all Key Figure values are zero. See Note 619826.
RSDG_CUBE_ACTIVATE	Activation of InfoCubes
RSDG_CUBE_COPY	Make InfoCube Copies
RSDG_CUBE_DELETE	Delete InfoCubes
RSDG_DODS_REPAIR	Activation of all ODS Objects with Navigation Attributes
RSDG_ODSO_ACTIVATE	Activation of all ODS Objects
RSDG_IOBJ_ACTIVATE	Activation of all InfoObjects
RSDG_IOBJ_DELETE	Deletion of InfoObjects
RSDG_IOBJ_REORG	Repair InfoObjects
RSDG_IOBJ_REORG_TEXTS	Reorganization of Texts for InfoObjects
RSDG_MPRO_ACTIVATE	Activating Multiproviders
RSDG_MPRO_COPY	Make Multiprovider Copies
RSDG_MPRO_DELETE	Deleting Multiproviders
RS_COMSTRU_ACTIVATE_ALL	Activate all inactive Communication Structures
RS_TRANSTRU_ACTIVATE_ALL	Activate Transfer Structure
RSAU_UPDR_REACTIVATE_ALL	Activate Update Rules
RRHI_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 Objects
SAP_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,
CUBE_SAMPLE_CREATE	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.

To raise an event in source system which triggers a job in BW system.

2011-07-22T04:10:00.000-07:00

To raise an event in source system which triggers a job in BW system.

In source system after the job completion of an abap report, needs to raise an event which triggers a job in BW.

1. Craete Event in SM62 in BW , Event name = ECCTOBW.
2. Assign that Event in BW and give Parameter name = ECCTOBW_P. (Param is directly give in BW)

(In Case of dataloads, create Process chain and give thios Event and Parameter in Start-->Event) and Activate and Exexute the Processc Chain.

3. Then Run the below program in ECC then check your processc hain, it will trigger.

This is the way how to use the Events triggers in different system.

REPORT  ytestrd1tobd1.
 
CALL FUNCTION 'RSSM_EVENT_RAISE'
  DESTINATION 'BWCLNT' ------------> Here give your BW system ID
  EXPORTING
    i_eventid              = 'ECCTOBW'
    i_eventparm            = 'ECCTOBW_P1'
  EXCEPTIONS
    bad_eventid            = 1
    eventid_does_not_exist = 2
    eventid_missing        = 3
    raise_failed           = 4
    OTHERS                 = 5.
IF sy-subrc  0.
  MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
          WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

DB Growth

2011-02-13T21:32:00.000-08:00

1.SAP_DROP_TMPTABLES
2.RSB_ANALYZE_ERRORLOG anf then use RSBM_ERRORLOG_DELETE

1.Clean up PSA for every 15 days
2. Optimize the Aggregates ( Delete bad Aggregates, If u have )
3. Compress the Cubes to washout duplicate records.
4.If you have more historic data, currently not in reporting scope..ARCHIVE that data in different formats.
: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/342cba90-0201-0010-0d99-ab4bfb868eb6
SAP NetWeaver - Data Warehousing with Large Data Volumes
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d56bbf90-0201-0010-53aa-923512127968
5.By Using transaction ST14 you can find the detail information of space used by objects (infocube/ods/psa).you need to schedule the job in ST14 to get the first result for top 30 objects.
ST14 lets you run a job that collects info on the Top 30 largest InfoCubes - considers E and F fact tables separately ( 30 largest Es, and 30 largest Fs).
It will provide:
Top 30 PSA Elements
Top 30 ODS Elements
Top 30 E-Fact tables
Top 30 F-Fact tables
Top 30 Dimension Tables
Top 30 Aggregates
Top 30 Master Data Tables
Top 30 Object tables
Top 30 Other Tables
Top 30 Change Logs
Top 30 Cubes
6. Check the size of object through DB02...object name and then add the size of all the tables pertaining to that object.
--------------------------------------------------------------------------
RSBERRORLOG Table performance problem

RSBM_ERRORLOG_DELETE

If you are running on oracle please run a online reorg on rsberrorlog.

1144400-RSBM_ERRORLOG_DELETE no frequent commits.
1095924-Correction: Deletion/analyis report for error handlign logs.

If you are on SAP_BW 701 above notes are not applicable ... you can go ahead and run report (RSBM_ERRORLOG_DELETE).

Useful Sites

2011-02-12T19:39:00.000-08:00

SAP BEST PRACTICES

http://www.sap.com/services/more/servsuptech/servicedetail.epx?context=%5b%5bt%3db3782b8%5d%5d|

Useful Links
http://sap.emc-labs.com/
http://sapbwneelam.blogspot.com/
http://www.consolut.com/
http://sapbwqa.blogspot.com/

SAP WEBINARS
http://www.sdn.sap.com/irj/scn/business-analytics-webinars

Reconcile Sales Data

2011-02-12T16:23:00.001-08:00

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 1
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
Applies to:
SAP ECC 6.00 and SAP BW 7.0 releases. For more information, visit the Business Intelligence homepage.
Summary
This paper gives a detail understanding of the steps to follow custom ABAP Programs creation for Sales reconciliation. This document provides a step by step guide to create custom ABAP programs on ECC environment and also discusses how these programs can help in reconciling sales data on SAP BW environment.
Author: Vamsi Sirish Siddabattuni
Company: Deloitte Consulting LLP
Created on: 06 November 2009
Author Bio
Vamsi Sirish Siddabattuni is an SAP Certified Netweaver 2004s BI Solution Consultant and SAP Certified ABAP Workbench consultant. He has more than 6 yrs of experience working on SAP BW projects and has implemented SAP BW systems based on SAP BW 3.0b, 3.5 and 7.0 versions.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 2
Table of Contents
Introduction .................................................................................................................................................. 3
Scenario ................................................................................................................................................... 3
Step By Step Procedure ............................................................................................................................... 3
Sales Order Reconciliation :....................................................................................................................... 3
Delivery Item Reconciliation : ..................................................................................................................... 4
Billing Item Reconciliation : ........................................................................................................................ 4
Billing Conditions Reconciliation : .............................................................................................................. 4
The Code ..................................................................................................................................................... 5
Sales Analysis Program Code ................................................................................................................... 5
Delivery Analysis Program Code.............................................................................................................. 14
Billing Analysis Program Code ................................................................................................................. 25
Billing Conditions Analysis Program Code ............................................................................................... 36
Related Content ......................................................................................................................................... 50
Disclaimer and Liability Notice ..................................................................................................................... 51
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 3
Introduction
Often SAP BI Projects implementing Sales and Distribution module face the challenge of reconciling the data loaded into SAP BI from ECC as there are no standard reports in ECC which can help in easy reconciliation of Sales, Delivery and Billing data loaded.
This document is focused on creating custom ABAP Reports on ECC environment to validate data loaded onto SAP BW and perform reconciliation process easily.
Scenario
The scenario discusses about loading the Line Item Level data for Sales Header and Item, Delivery Header and Item, Billing Header and Item and Billing Conditions into SAP BI environment to DSOs and validating the data loaded into those DSOs with custom ABAP Reports built on ECC to see if the data loads are getting the data successfully.
It primarily concentrates on creation of ABAP programs within each sub-module of Sales and Distribution on ECC and steps on how generic BEx queries built on SAP BI environment on top of the Line Item Level DSOs for Sales Line Item , Delivery Line Item, Billing Line Item and Billing Conditions DSOs are used to reconcile the data. The scenario doesn’t discuss about the creation of Line Item Level DSOs and the design of those DSOs and BEx queries built on top of the DSOs.
Step By Step Procedure
Step by Step Procedure discusses in four sections about the Sales Order Item, Delivery Item, Billing Item and Billing Conditions reconciliation of data on SAP BI with ECC environment.
Sales Order Reconciliation :
1. Create an ABAP Program on ECC environment (Ex : ZBI_SALES_ANALYSIS ). Refer to appendix for Program Code. This program retrieves the data from Sales Order Header and Sales Order Item Tables and shows the data in an ALV output with the selections entered in the selection screen.
Selection screen for the ABAP Program ( ZBI_SALES_ANALYSIS ) is in the screenshot below.
Sample output of the program execution is show below.
2. You can also schedule a background job for this ABAP Program to execute at the same time when the nightly job run for BI Extraction happens. This way the spool output of the ABAP Program can be downloaded onto a flat file and can be compared with the BI Report we are going to discuss in the next point.
Execute the ABAP Program ‘ZBI_SALES_ANALYSIS’ for example in SE38. This prompts the following screen.
Enter the selections needed and schedule the background job which runs on a daily basis.
Enter the spool parameters in the below screen
Enter the frequency
Background job will be scheduled after entering the selections and pressing the check button.
Spool output of the request can be printed from SM37 on a daily basis to keep the documents for records.
3. On the SAP BW environment connected to the ECC environment create a BEx Query on top of DSO which stores Sales Order Header and Item Information on SAP BI Environment. Sample query definition is shown in the below screenshot.
Execute the query with the same selections you defined for ABAP Program on ECC to check the data for reconciliation. Sample output of the BEx query is shown below. Output of the BEx query can be used for reconciliation with the ABAP Spool output on a daily basis to check and see if the data loaded in to BW is correct or not.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 4
Delivery Item Reconciliation :
1. Create an ABAP Program on ECC environment (Ex : ZBI_DELIVERY_ANALYSIS ). Refer to appendix for Program Code. This program retrieves the data from Delivery Header and Delivery Item Tables and shows the data in an ALV output with the selections entered in the selection screen.
Selection screen for the ABAP Program ( ZBI_DELIVERY_ANALYSIS ) is in the screenshot below.
Sample output of the program execution is show below.
2. You can also schedule a background job for this ABAP Program by following the steps mentioned in Step by step procedure for Sales Analysis Reconciliation for background job scheduling.
3. On the SAP BW environment connected to the ECC environment create a BEx Query on top of DSO which stores Delivery Header and Item Information on SAP BI Environment. Sample query definition is shown in the below screenshot.
Execute the query with the same selections you defined for ABAP Program on ECC to check the data for reconciliation. Sample output of the BEx query is shown below. Output of the BEx query can be used for reconciliation with the ABAP Spool output on a daily basis to check and see if the data loaded in to BW is correct or not.
Billing Item Reconciliation :
1. Create an ABAP Program on ECC environment (Ex : ZBI_BILLING_ANALYSIS ). Refer to appendix for Program Code. This program retrieves the data from Billing Header and Billing Item Tables and shows the data in an ALV output with the selections entered in the selection screen.
Selection screen for the ABAP Program ( ZBI_BILLING_ANALYSIS ) is in the screenshot below.
Sample output of the program execution is show below.
2. You can also schedule a background job for this ABAP Program by following the steps mentioned in Step by step procedure for Sales Analysis Reconciliation for background job scheduling.
3. On the SAP BW environment connected to the ECC environment create a BEx Query on top of DSO which stores Billing Header and Item Information on SAP BI Environment. Sample query definition is shown in the below screenshot.
Execute the query with the same selections you defined for ABAP Program on ECC to check the data for reconciliation. Sample output of the BEx query is shown below. Output of the BEx query can be used for reconciliation with the ABAP Spool output on a daily basis to check and see if the data loaded in to BW is correct or not.
Billing Conditions Reconciliation :
1. Create an ABAP Program on ECC environment (Ex : ZBI_BILLING_COND_ANALYSIS ). Refer to appendix for Program Code. This program retrieves the data from underlying Billing Conditions Tables and shows the data in an ALV output with the selections entered in the selection screen.
Selection screen for the ABAP Program ( ZBI_BILLING_COND_ANALYSIS ) is in the screenshot below.
Sample output of the program execution is show below.
2. You can also schedule a background job for this ABAP Program by following the steps mentioned in Step by step procedure for Sales Analysis Reconciliation for background job scheduling.
3. On the SAP BW environment connected to the ECC environment create a BEx Query on top of DSO which stores Delivery Header and Item Information on SAP BI Environment. Sample query definition is shown in the below screenshot.
Execute the query with the same selections you defined for ABAP Program on ECC to check the data for reconciliation. Sample output of the BEx query is shown below. Output of the BEx query can be used for reconciliation with the ABAP Spool output on a daily basis to check and see if the data loaded in to BW is correct or not.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 5
The Code
Sales Analysis Program Code
*&---------------------------------------------------------------------*
*& Report ZBI_SALES_ANALYSIS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZBI_SALES_ANALYSIS.
TABLES : VBAK,VBAP,VBEP.
START-OF-SELECTION.
SELECT-OPTIONS SLS_DOC FOR VBAK-VBELN.
SELECT-OPTIONS CRTD_ON FOR SY-DATUM.
SELECT-OPTIONS REQD_DT FOR SY-DATUM.
SELECT-OPTIONS DOC_TYPE FOR VBAK-AUART.
SELECT-OPTIONS SAL_ORG FOR VBAK-VKORG.
SELECT-OPTIONS DIS_CHAN FOR VBAK-VTWEG.
SELECT-OPTIONS DIVISION FOR VBAK-SPART.
SELECT-OPTIONS MATERIAL FOR VBAP-MATNR.
SELECT-OPTIONS SOLD_TO FOR VBAK-KUNNR.
SELECT-OPTIONS PLANT FOR VBAP-WERKS.
END-OF-SELECTION.
TYPES : BEGIN OF STR_SALES,
VBELN TYPE VBAK-VBELN,
POSNR TYPE VBAP-POSNR,
ERDAT TYPE VBAK-ERDAT,
VBTYP TYPE VBAK-VBTYP,
AUART TYPE VBAK-AUART,
AUGRU TYPE VBAK-AUGRU,
VKORG TYPE VBAK-VKORG,
VTWEG TYPE VBAK-VTWEG,
SPART TYPE VBAK-SPART,
VDATU TYPE VBAK-VDATU,
VSBED TYPE VBAK-VSBED,
BSTNK TYPE VBAK-BSTNK,
KUNNR TYPE VBAK-KUNNR,
MATNR TYPE VBAP-MATNR,
ABGRU TYPE VBAP-ABGRU,
ZMENG TYPE VBAP-ZMENG,
ZIEME TYPE VBAP-ZIEME,
NETWR TYPE VBAP-NETWR,
KWMENG TYPE VBAP-KWMENG,
VRKME TYPE VBAP-VRKME,
VGBEL TYPE VBAP-VGBEL,
VGPOS TYPE VBAP-VGPOS,
NETPR TYPE VBAP-NETPR,
SHKZG TYPE VBAP-SHKZG,
WAVWR TYPE VBAP-WAVWR,
KZWI1 TYPE VBAP-KZWI1,
KZWI2 TYPE VBAP-KZWI2,
KZWI3 TYPE VBAP-KZWI3,
KZWI4 TYPE VBAP-KZWI4,
KZWI5 TYPE VBAP-KZWI5,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 6
KZWI6 TYPE VBAP-KZWI6,
WERKS TYPE VBAP-WERKS,
WADAT TYPE VBEP-WADAT,
END OF STR_SALES.
TYPES : BEGIN OF STR_VBAK,
VBELN TYPE VBAK-VBELN,
ERDAT TYPE VBAK-ERDAT,
VBTYP TYPE VBAK-VBTYP,
AUART TYPE VBAK-AUART,
AUGRU TYPE VBAK-AUGRU,
VKORG TYPE VBAK-VKORG,
VTWEG TYPE VBAK-VTWEG,
SPART TYPE VBAK-SPART,
VDATU TYPE VBAK-VDATU,
VSBED TYPE VBAK-VSBED,
BSTNK TYPE VBAK-BSTNK,
KUNNR TYPE VBAK-KUNNR,
END OF STR_VBAK.
TYPES : BEGIN OF STR_VBAP,
VBELN TYPE VBAP-VBELN,
POSNR TYPE VBAP-POSNR,
MATNR TYPE VBAP-MATNR,
ABGRU TYPE VBAP-ABGRU,
ZMENG TYPE VBAP-ZMENG,
ZIEME TYPE VBAP-ZIEME,
NETWR TYPE VBAP-NETWR,
KWMENG TYPE VBAP-KWMENG,
VRKME TYPE VBAP-VRKME,
VGBEL TYPE VBAP-VGBEL,
VGPOS TYPE VBAP-VGPOS,
NETPR TYPE VBAP-NETPR,
SHKZG TYPE VBAP-SHKZG,
WAVWR TYPE VBAP-WAVWR,
KZWI1 TYPE VBAP-KZWI1,
KZWI2 TYPE VBAP-KZWI2,
KZWI3 TYPE VBAP-KZWI3,
KZWI4 TYPE VBAP-KZWI4,
KZWI5 TYPE VBAP-KZWI5,
KZWI6 TYPE VBAP-KZWI6,
WERKS TYPE VBAP-WERKS,
END OF STR_VBAP.
TYPES : BEGIN OF STR_VBEP,
VBELN TYPE VBAP-VBELN,
POSNR TYPE VBAP-POSNR,
ETENR TYPE VBEP-ETENR,
WADAT TYPE VBEP-WADAT,
END OF STR_VBEP.
DATA : IT_VBAK TYPE TABLE OF STR_VBAK,
IT_VBAP TYPE TABLE OF STR_VBAP,
IT_VBEP TYPE TABLE OF STR_VBEP,
WA_VBAK TYPE STR_VBAK,
WA_VBAP TYPE STR_VBAP,
WA_VBEP TYPE STR_VBEP,
IT_OUTPUT TYPE TABLE OF STR_SALES,
WA_OUTPUT TYPE STR_SALES.
type-pools : slis .
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 7
* data: fieldcatalog type slis_t_fieldcat_alv with header line,
* gd_tab_group type slis_t_sp_group_alv,
* gd_layout type slis_layout_alv,
* gd_repid like sy-repid,
* gt_events type slis_t_event.
DATA: gr_table TYPE REF TO cl_salv_table,
gr_functions TYPE REF TO cl_salv_functions, "#EC *
gr_columns TYPE REF TO cl_salv_columns, "#EC *
gr_column TYPE REF TO cl_salv_column, "#EC *
gr_sorts TYPE REF TO cl_salv_sorts,
gr_agg TYPE REF TO cl_salv_aggregations.
SELECT * FROM VBAK INTO CORRESPONDING FIELDS OF TABLE
IT_VBAK WHERE VBELN IN SLS_DOC AND
ERDAT IN CRTD_ON AND VDATU IN REQD_DT AND
AUART IN DOC_TYPE AND VKORG IN SAL_ORG AND
VTWEG IN DIS_CHAN AND SPART IN DIVISION AND
KUNNR IN SOLD_TO.
SELECT * FROM VBAP INTO CORRESPONDING FIELDS OF TABLE IT_VBAP
FOR ALL ENTRIES IN IT_VBAK WHERE
VBELN = IT_VBAK-VBELN AND MATNR IN MATERIAL AND WERKS IN PLANT.
SELECT * FROM VBEP INTO CORRESPONDING FIELDS OF TABLE IT_VBEP
FOR ALL ENTRIES IN IT_VBAP WHERE
VBELN = IT_VBAP-VBELN AND POSNR = IT_VBAP-POSNR.
SORT IT_VBEP BY VBELN POSNR ETENR DESCENDING.
LOOP AT IT_VBAP INTO WA_VBAP.
WA_OUTPUT-VBELN = WA_VBAP-VBELN.
WA_OUTPUT-POSNR = WA_VBAP-POSNR.
WA_OUTPUT-MATNR = WA_VBAP-MATNR.
WA_OUTPUT-ABGRU = WA_VBAP-ABGRU.
WA_OUTPUT-ZMENG = WA_VBAP-ZMENG.
WA_OUTPUT-ZIEME = WA_VBAP-ZIEME.
WA_OUTPUT-NETWR = WA_VBAP-NETWR.
WA_OUTPUT-KWMENG = WA_VBAP-KWMENG.
WA_OUTPUT-VRKME = WA_VBAP-VRKME.
WA_OUTPUT-VGBEL = WA_VBAP-VGBEL.
WA_OUTPUT-VGPOS = WA_VBAP-VGPOS.
WA_OUTPUT-NETPR = WA_VBAP-NETPR.
WA_OUTPUT-SHKZG = WA_VBAP-SHKZG.
WA_OUTPUT-WAVWR = WA_VBAP-WAVWR.
WA_OUTPUT-KZWI1 = WA_VBAP-KZWI1.
WA_OUTPUT-KZWI2 = WA_VBAP-KZWI2.
WA_OUTPUT-KZWI3 = WA_VBAP-KZWI3.
WA_OUTPUT-KZWI4 = WA_VBAP-KZWI4.
WA_OUTPUT-KZWI5 = WA_VBAP-KZWI5.
WA_OUTPUT-KZWI6 = WA_VBAP-KZWI6.
WA_OUTPUT-WERKS = WA_VBAP-WERKS.
APPEND WA_OUTPUT TO IT_OUTPUT.
CLEAR : WA_OUTPUT, WA_VBAP.
ENDLOOP.
LOOP AT IT_OUTPUT INTO WA_OUTPUT.
READ TABLE IT_VBAK INTO WA_VBAK
WITH KEY VBELN = WA_OUTPUT-VBELN.
IF SY-SUBRC EQ 0.
WA_OUTPUT-ERDAT = WA_VBAK-ERDAT.
WA_OUTPUT-VBTYP = WA_VBAK-VBTYP.
WA_OUTPUT-AUART = WA_VBAK-AUART.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 8
WA_OUTPUT-AUGRU = WA_VBAK-AUGRU.
WA_OUTPUT-VKORG = WA_VBAK-VKORG.
WA_OUTPUT-VTWEG = WA_VBAK-VTWEG.
WA_OUTPUT-SPART = WA_VBAK-SPART.
WA_OUTPUT-VDATU = WA_VBAK-VDATU.
WA_OUTPUT-VSBED = WA_VBAK-VSBED.
WA_OUTPUT-BSTNK = WA_VBAK-BSTNK.
WA_OUTPUT-KUNNR = WA_VBAK-KUNNR.
ENDIF.
READ TABLE IT_VBEP INTO WA_VBEP
WITH KEY VBELN = WA_OUTPUT-VBELN POSNR = WA_OUTPUT-POSNR.
IF SY-SUBRC EQ 0.
WA_OUTPUT-WADAT = WA_VBEP-WADAT.
ENDIF.
MODIFY IT_OUTPUT FROM WA_OUTPUT.
CLEAR : WA_OUTPUT, WA_VBAK, WA_VBEP.
ENDLOOP.
DATA: ls_info TYPE slis_listheader,
lv_stext TYPE scrtext_s, " Short Text
lv_mtext TYPE scrtext_m, " Medium Text
lv_ltext TYPE scrtext_l, " Long Text
lv_colname TYPE lvc_fname, " Column Name
lv_position TYPE i VALUE 1, " Position
ls_line TYPE slis_listheader, "
lv_char(15) TYPE c.
* Class declarations
DATA: ls_rows TYPE REF TO cl_salv_form_layout_grid,
ls_row TYPE REF TO cl_salv_form_layout_flow.
* Create Object Reference
CREATE OBJECT ls_rows.
TRY.
cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING t_table = it_output ). "#EC
CATCH cx_salv_msg. "#EC
CATCH cx_salv_not_found. "#EC
ENDTRY.
gr_columns = gr_table->get_columns( ).
gr_columns->set_optimize( abap_true ).
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBELN'.
lv_position = 1.
lv_stext = 'Sales Order'(s28).
lv_mtext = 'Sales Order'(s28).
lv_ltext = 'Sales Order'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSNR'.
lv_position = lv_position + 1.
lv_stext = 'Sales Item'(s28).
lv_mtext = 'Sales Item'(s28).
lv_ltext = 'Sales Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ERDAT'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 9
lv_position = lv_position + 1.
lv_stext = 'Create Date'(s28).
lv_mtext = 'Create Date'(s28).
lv_ltext = 'Create Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBTYP'.
lv_position = lv_position + 1.
lv_stext = 'Doc Categ'(s28).
lv_mtext = 'Doc Categ'(s28).
lv_ltext = 'Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUART'.
lv_position = lv_position + 1.
lv_stext = 'Doc Type'(s28).
lv_mtext = 'Doc Type'(s28).
lv_ltext = 'Doc Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUGRU'.
lv_position = lv_position + 1.
lv_stext = 'Ord Reason'(s28).
lv_mtext = 'Ord Reason'(s28).
lv_ltext = 'Ord Reason'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VKORG'.
lv_position = lv_position + 1.
lv_stext = 'Sales Org'(s28).
lv_mtext = 'Sales Org'(s28).
lv_ltext = 'Sales Org'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VTWEG'.
lv_position = lv_position + 1.
lv_stext = 'Dist Chan'(s28).
lv_mtext = 'Dist Chan'(s28).
lv_ltext = 'Dist Chan'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SPART'.
lv_position = lv_position + 1.
lv_stext = 'Division'(s28).
lv_mtext = 'Division'(s28).
lv_ltext = 'Division'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VDATU'.
lv_position = lv_position + 1.
lv_stext = 'Req Del Date'(s28).
lv_mtext = 'Req Del Date'(s28).
lv_ltext = 'Req Del Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VSBED'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 10
lv_position = lv_position + 1.
lv_stext = 'Ship Cond'(s28).
lv_mtext = 'Ship Cond'(s28).
lv_ltext = 'Ship Cond'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BSTNK'.
lv_position = lv_position + 1.
lv_stext = 'Cust Pur No'(s28).
lv_mtext = 'Cust Pur No'(s28).
lv_ltext = 'Cust Pur No'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNNR'.
lv_position = lv_position + 1.
lv_stext = 'Sold To'(s28).
lv_mtext = 'Sold To'(s28).
lv_ltext = 'Sold To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATNR'.
lv_position = lv_position + 1.
lv_stext = 'Material'(s28).
lv_mtext = 'Material'(s28).
lv_ltext = 'Material'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ABGRU'.
lv_position = lv_position + 1.
lv_stext = 'Reason for Rej'(s28).
lv_mtext = 'Reason for Rej'(s28).
lv_ltext = 'Reason for Rej'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ZMENG'.
lv_position = lv_position + 1.
lv_stext = 'Target Qty'(s28).
lv_mtext = 'Target Qty'(s28).
lv_ltext = 'Target Qty'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ZIEME'.
lv_position = lv_position + 1.
lv_stext = 'Target Qty UOM'(s28).
lv_mtext = 'Target Qty UOM'(s28).
lv_ltext = 'Target Qty UOM'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NETWR'.
lv_position = lv_position + 1.
lv_stext = 'Net Value'(s28).
lv_mtext = 'Net Value'(s28).
lv_ltext = 'Net Value'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KWMENG'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 11
lv_position = lv_position + 1.
lv_stext = 'Sal Qty'(s28).
lv_mtext = 'Sal Qty'(s28).
lv_ltext = 'Sal Qty'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VRKME'.
lv_position = lv_position + 1.
lv_stext = 'Sal Qty UOM'(s28).
lv_mtext = 'Sal Qty UOM'(s28).
lv_ltext = 'Sal Qty UOM'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGBEL'.
lv_position = lv_position + 1.
lv_stext = 'Refer Doc'(s28).
lv_mtext = 'Refer Doc'(s28).
lv_ltext = 'Refer Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGPOS'.
lv_position = lv_position + 1.
lv_stext = 'Refer Item'(s28).
lv_mtext = 'Refer Item'(s28).
lv_ltext = 'Refer Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NETPR'.
lv_position = lv_position + 1.
lv_stext = 'Net Price'(s28).
lv_mtext = 'Net Price'(s28).
lv_ltext = 'Net Price'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SHKZG'.
lv_position = lv_position + 1.
lv_stext = 'Returns'(s28).
lv_mtext = 'Returns'(s28).
lv_ltext = 'Returns'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WAVWR'.
lv_position = lv_position + 1.
lv_stext = 'Cost'(s28).
lv_mtext = 'Cost'(s28).
lv_ltext = 'Cost'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WADAT'.
lv_position = lv_position + 1.
lv_stext = 'Goods Issue Dt'(s28).
lv_mtext = 'Goods Issue Dt'(s28).
lv_ltext = 'Goods Issue Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WERKS'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 12
lv_position = lv_position + 1.
lv_stext = 'Plant'(s28).
lv_mtext = 'Plant'(s28).
lv_ltext = 'Plant'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI1'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 1'(s28).
lv_mtext = 'Sub Total 1'(s28).
lv_ltext = 'Sub Total 1'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI2'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 2'(s28).
lv_mtext = 'Sub Total 2'(s28).
lv_ltext = 'Sub Total 2'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI3'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 3'(s28).
lv_mtext = 'Sub Total 3'(s28).
lv_ltext = 'Sub Total 3'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI4'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 4'(s28).
lv_mtext = 'Sub Total 4'(s28).
lv_ltext = 'Sub Total 4'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI5'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 5'(s28).
lv_mtext = 'Sub Total 5'(s28).
lv_ltext = 'Sub Total 5'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI6'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 6'(s28).
lv_mtext = 'Sub Total 6'(s28).
lv_ltext = 'Sub Total 6'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Display the Header information.
CALL METHOD gr_table->set_top_of_list
EXPORTING
value = ls_rows.
* Getting the All columns names
gr_columns = gr_table->get_columns( ).
gr_functions = gr_table->get_functions( ).
gr_functions->set_all( abap_true ).
* To addd the sort functionality
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 13
gr_sorts = gr_table->get_sorts( ).
* gr_sorts->add_sort( columnname = 'VBELN'(s27) subtotal = abap_true ).
* gr_sorts->add_sort( columnname = 'POSNR'(s30) subtotal = abap_true ).
gr_agg = gr_table->get_aggregations( ).
gr_agg->add_aggregation( 'ZMENG'(s66) ).
gr_agg->add_aggregation( 'NETWR'(s63) ).
gr_agg->add_aggregation( 'NETPR'(s46) ).
gr_agg->add_aggregation( 'WAVWR'(s55) ).
gr_agg->add_aggregation( 'KZWI1'(s57) ).
gr_agg->add_aggregation( 'KZWI2'(s57) ).
gr_agg->add_aggregation( 'KZWI3'(s57) ).
gr_agg->add_aggregation( 'KZWI4'(s57) ).
gr_agg->add_aggregation( 'KZWI5'(s57) ).
gr_agg->add_aggregation( 'KZWI6'(s57) ).
*Display output table.
gr_table->display( ).
*&---------------------------------------------------------------------*
*& Form F_SETCOLUMN_NAME
*&---------------------------------------------------------------------*
* Display the column according to the report output
*----------------------------------------------------------------------*
FORM f_setcolumn_name USING pu_colname TYPE lvc_fname " Field Name
pu_position TYPE i " Position
pu_lv_stext TYPE scrtext_s " Short Text
pu_lv_mtext TYPE scrtext_m " Medium Text
pu_lv_ltext TYPE scrtext_l. " Short Text
TRY.
* get the required column details to GR_COLUMN.
gr_column = gr_columns->get_column( pu_colname ).
* Short Text for column.
gr_column->set_short_text( pu_lv_stext ).
* Medium Text for column.
gr_column->set_medium_text( pu_lv_mtext ).
* Long Text for column.
gr_column->set_long_text( pu_lv_ltext ).
* Setting Column name and position.
gr_columns->set_column_position(
columnname = pu_colname
position = pu_position ).
CATCH cx_salv_not_found. "#EC
ENDTRY.
* clearing the variable used in the perform .
CLEAR: pu_colname,pu_lv_stext,pu_lv_mtext,pu_lv_ltext.
ENDFORM. " F_SETCOLUMN_NAME
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 14
Delivery Analysis Program Code
*&---------------------------------------------------------------------*
*& Report ZBI_DELIVERY_ANALYSIS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZBI_DELIVERY_ANALYSIS.
TABLES : LIKP,LIPS.
START-OF-SELECTION.
SELECT-OPTIONS DEL_DOC FOR LIKP-VBELN.
SELECT-OPTIONS CRTD_ON FOR SY-DATUM.
SELECT-OPTIONS PLNGDSDT FOR SY-DATUM.
SELECT-OPTIONS ACTGDSDT FOR SY-DATUM.
SELECT-OPTIONS DEL_TYPE FOR LIKP-LFART.
SELECT-OPTIONS ITEM_CAT FOR LIPS-PSTYV.
SELECT-OPTIONS SAL_ORG FOR LIKP-VKORG.
SELECT-OPTIONS PLANT FOR LIPS-WERKS.
SELECT-OPTIONS DIS_CHAN FOR LIPS-VTWEG.
SELECT-OPTIONS DIVISION FOR LIPS-SPART.
SELECT-OPTIONS MATERIAL FOR LIPS-MATNR.
SELECT-OPTIONS SOLD_TO FOR LIKP-KUNNR.
SELECT-OPTIONS SHIP_TO FOR LIKP-KUNAG.
END-OF-SELECTION.
TYPES : BEGIN OF STR_DEL,
VBELN TYPE LIKP-VBELN,
POSNR TYPE LIPS-POSNR,
ERDAT TYPE LIKP-ERDAT,
VKORG TYPE LIKP-VKORG,
LFART TYPE LIKP-LFART,
WADAT TYPE LIKP-WADAT,
LFDAT TYPE LIKP-LFDAT,
VBTYP TYPE LIKP-VBTYP,
VSBED TYPE LIKP-VSBED,
KUNNR TYPE LIKP-KUNNR,
KUNAG TYPE LIKP-KUNAG,
WADAT_IST TYPE LIKP-WADAT_IST,
PSTYV TYPE LIPS-PSTYV,
MATNR TYPE LIPS-MATNR,
WERKS TYPE LIPS-WERKS,
LGORT TYPE LIPS-LGORT,
KDMAT TYPE LIPS-KDMAT,
LFIMG TYPE LIPS-LFIMG,
VRKME TYPE LIPS-VRKME,
NTGEW TYPE LIPS-NTGEW,
BRGEW TYPE LIPS-BRGEW,
GEWEI TYPE LIPS-GEWEI,
LGMNG TYPE LIPS-LGMNG,
VBTYV TYPE LIPS-VBTYV,
VGBEL TYPE LIPS-VGBEL,
VGPOS TYPE LIPS-VGPOS,
POSAR TYPE LIPS-POSAR,
VTWEG TYPE LIPS-VTWEG,
SPART TYPE LIPS-SPART,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 15
SHKZG TYPE LIPS-SHKZG,
NETPR TYPE LIPS-NETPR,
NETWR TYPE LIPS-NETWR,
WAVWR TYPE LIPS-WAVWR,
KZWI1 TYPE LIPS-KZWI1,
KZWI2 TYPE LIPS-KZWI2,
KZWI3 TYPE LIPS-KZWI3,
KZWI4 TYPE LIPS-KZWI4,
KZWI5 TYPE LIPS-KZWI5,
KZWI6 TYPE LIPS-KZWI6,
END OF STR_DEL.
TYPES : BEGIN OF STR_LIKP,
VBELN TYPE LIKP-VBELN,
ERDAT TYPE LIKP-ERDAT,
VKORG TYPE LIKP-VKORG,
LFART TYPE LIKP-LFART,
WADAT TYPE LIKP-WADAT,
LFDAT TYPE LIKP-LFDAT,
VBTYP TYPE LIKP-VBTYP,
VSBED TYPE LIKP-VSBED,
KUNNR TYPE LIKP-KUNNR,
KUNAG TYPE LIKP-KUNAG,
WADAT_IST TYPE LIKP-WADAT_IST,
END OF STR_LIKP.
TYPES : BEGIN OF STR_LIPS,
VBELN TYPE LIPS-VBELN,
POSNR TYPE LIPS-POSNR,
PSTYV TYPE LIPS-PSTYV,
MATNR TYPE LIPS-MATNR,
WERKS TYPE LIPS-WERKS,
LGORT TYPE LIPS-LGORT,
KDMAT TYPE LIPS-KDMAT,
LFIMG TYPE LIPS-LFIMG,
VRKME TYPE LIPS-VRKME,
NTGEW TYPE LIPS-NTGEW,
BRGEW TYPE LIPS-BRGEW,
GEWEI TYPE LIPS-GEWEI,
LGMNG TYPE LIPS-LGMNG,
VBTYV TYPE LIPS-VBTYV,
VGBEL TYPE LIPS-VGBEL,
VGPOS TYPE LIPS-VGPOS,
POSAR TYPE LIPS-POSAR,
VTWEG TYPE LIPS-VTWEG,
SPART TYPE LIPS-SPART,
SHKZG TYPE LIPS-SHKZG,
NETPR TYPE LIPS-NETPR,
NETWR TYPE LIPS-NETWR,
WAVWR TYPE LIPS-WAVWR,
KZWI1 TYPE LIPS-KZWI1,
KZWI2 TYPE LIPS-KZWI2,
KZWI3 TYPE LIPS-KZWI3,
KZWI4 TYPE LIPS-KZWI4,
KZWI5 TYPE LIPS-KZWI5,
KZWI6 TYPE LIPS-KZWI6,
END OF STR_LIPS.
DATA : IT_LIKP TYPE TABLE OF STR_LIKP,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 16
IT_LIPS TYPE TABLE OF STR_LIPS,
WA_LIKP TYPE STR_LIKP,
WA_LIPS TYPE STR_LIPS,
IT_OUTPUT TYPE TABLE OF STR_DEL,
WA_OUTPUT TYPE STR_DEL.
type-pools : slis .
*data: fieldcatalog type slis_t_fieldcat_alv with header line,
* gd_tab_group type slis_t_sp_group_alv,
* gd_layout type slis_layout_alv,
* gd_repid like sy-repid.
DATA: gr_table TYPE REF TO cl_salv_table,
gr_functions TYPE REF TO cl_salv_functions, "#EC *
gr_columns TYPE REF TO cl_salv_columns, "#EC *
gr_column TYPE REF TO cl_salv_column, "#EC *
gr_sorts TYPE REF TO cl_salv_sorts,
gr_agg TYPE REF TO cl_salv_aggregations.
SELECT * FROM LIKP INTO CORRESPONDING FIELDS OF TABLE
IT_LIKP WHERE VBELN IN DEL_DOC AND
ERDAT IN CRTD_ON AND WADAT IN PLNGDSDT
AND WADAT_IST IN ACTGDSDT AND LFART IN DEL_TYPE AND
VKORG IN SAL_ORG AND WERKS IN PLANT AND
KUNNR IN SOLD_TO AND KUNAG IN SHIP_TO.
SELECT * FROM LIPS INTO CORRESPONDING FIELDS OF TABLE IT_LIPS
FOR ALL ENTRIES IN IT_LIKP WHERE
VBELN = IT_LIKP-VBELN AND MATNR IN MATERIAL AND WERKS IN PLANT AND
PSTYV IN ITEM_CAT AND VTWEG IN DIS_CHAN AND SPART IN DIVISION.
SORT IT_LIPS BY VBELN POSNR.
LOOP AT IT_LIPS INTO WA_LIPS.
WA_OUTPUT-VBELN = WA_LIPS-VBELN.
WA_OUTPUT-POSNR = WA_LIPS-POSNR.
WA_OUTPUT-PSTYV = WA_LIPS-PSTYV.
WA_OUTPUT-MATNR = WA_LIPS-MATNR.
WA_OUTPUT-WERKS = WA_LIPS-WERKS.
WA_OUTPUT-LGORT = WA_LIPS-LGORT.
WA_OUTPUT-KDMAT = WA_LIPS-KDMAT.
WA_OUTPUT-LFIMG = WA_LIPS-LFIMG.
WA_OUTPUT-VRKME = WA_LIPS-VRKME.
WA_OUTPUT-NTGEW = WA_LIPS-NTGEW.
WA_OUTPUT-BRGEW = WA_LIPS-BRGEW.
WA_OUTPUT-GEWEI = WA_LIPS-GEWEI.
WA_OUTPUT-LGMNG = WA_LIPS-LGMNG.
WA_OUTPUT-VBTYV = WA_LIPS-VBTYV.
WA_OUTPUT-VGBEL = WA_LIPS-VGBEL.
WA_OUTPUT-VGPOS = WA_LIPS-VGPOS.
WA_OUTPUT-POSAR = WA_LIPS-POSAR.
WA_OUTPUT-VTWEG = WA_LIPS-VTWEG.
WA_OUTPUT-SPART = WA_LIPS-SPART.
WA_OUTPUT-SHKZG = WA_LIPS-SHKZG.
WA_OUTPUT-NETPR = WA_LIPS-NETPR.
WA_OUTPUT-NETWR = WA_LIPS-NETWR.
WA_OUTPUT-WAVWR = WA_LIPS-WAVWR.
WA_OUTPUT-KZWI1 = WA_LIPS-KZWI1.
WA_OUTPUT-KZWI2 = WA_LIPS-KZWI2.
WA_OUTPUT-KZWI3 = WA_LIPS-KZWI3.
WA_OUTPUT-KZWI4 = WA_LIPS-KZWI4.
WA_OUTPUT-KZWI5 = WA_LIPS-KZWI5.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 17
WA_OUTPUT-KZWI6 = WA_LIPS-KZWI6.
APPEND WA_OUTPUT TO IT_OUTPUT.
CLEAR : WA_OUTPUT, WA_LIPS.
ENDLOOP.
LOOP AT IT_OUTPUT INTO WA_OUTPUT.
READ TABLE IT_LIKP INTO WA_LIKP
WITH KEY VBELN = WA_OUTPUT-VBELN.
IF SY-SUBRC EQ 0.
WA_OUTPUT-ERDAT = WA_LIKP-ERDAT.
WA_OUTPUT-VKORG = WA_LIKP-VKORG.
WA_OUTPUT-LFART = WA_LIKP-LFART.
WA_OUTPUT-WADAT = WA_LIKP-WADAT.
WA_OUTPUT-LFDAT = WA_LIKP-LFDAT.
WA_OUTPUT-VBTYP = WA_LIKP-VBTYP.
WA_OUTPUT-VSBED = WA_LIKP-VSBED.
WA_OUTPUT-KUNNR = WA_LIKP-KUNNR.
WA_OUTPUT-KUNAG = WA_LIKP-KUNAG.
WA_OUTPUT-WADAT_IST = WA_LIKP-WADAT_IST.
ENDIF.
MODIFY IT_OUTPUT FROM WA_OUTPUT.
CLEAR : WA_OUTPUT, WA_LIKP.
ENDLOOP.
DATA: ls_info TYPE slis_listheader,
lv_stext TYPE scrtext_s, " Short Text
lv_mtext TYPE scrtext_m, " Medium Text
lv_ltext TYPE scrtext_l, " Long Text
lv_colname TYPE lvc_fname, " Column Name
lv_position TYPE i VALUE 1, " Position
ls_line TYPE slis_listheader, "
lv_char(15) TYPE c.
* Class declarations
DATA: ls_rows TYPE REF TO cl_salv_form_layout_grid,
ls_row TYPE REF TO cl_salv_form_layout_flow.
* Create Object Reference
CREATE OBJECT ls_rows.
TRY.
cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING t_table = it_output ). "#EC
CATCH cx_salv_msg. "#EC
CATCH cx_salv_not_found. "#EC
ENDTRY.
gr_columns = gr_table->get_columns( ).
gr_columns->set_optimize( abap_true ).
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBELN'.
lv_position = lv_position.
lv_stext = 'Delivery No'(s28).
lv_mtext = 'Delivery No'(s28).
lv_ltext = 'Delivery No'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSNR'.
lv_position = lv_position + 1.
lv_stext = 'Delivery Item'(s28).
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 18
lv_mtext = 'Delivery Item'(s28).
lv_ltext = 'Delivery Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSNR'.
lv_position = lv_position + 1.
lv_stext = 'Delivery Item'(s28).
lv_mtext = 'Delivery Item'(s28).
lv_ltext = 'Delivery Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ERDAT'.
lv_position = lv_position + 1.
lv_stext = 'Create Date'(s28).
lv_mtext = 'Create Date'(s28).
lv_ltext = 'Create Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VKORG'.
lv_position = lv_position + 1.
lv_stext = 'Sales Org'(s28).
lv_mtext = 'Sales Org'(s28).
lv_ltext = 'Sales Org'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WERKS'.
lv_position = lv_position + 1.
lv_stext = 'Plant'(s28).
lv_mtext = 'Plant'(s28).
lv_ltext = 'Plant'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'LFART'.
lv_position = lv_position + 1.
lv_stext = 'Delivery Type'(s28).
lv_mtext = 'Delivery Type'(s28).
lv_ltext = 'Delivery Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WADAT'.
lv_position = lv_position + 1.
lv_stext = 'Planned Goods Issue Dt'(s28).
lv_mtext = 'Planned Goods Issue Dt'(s28).
lv_ltext = 'Planned Goods Issue Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'LFDAT'.
lv_position = lv_position + 1.
lv_stext = 'Delivery Date'(s28).
lv_mtext = 'Delivery Date'(s28).
lv_ltext = 'Delivery Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBTYP'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc Categ'(s28).
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 19
lv_mtext = 'Sales Doc Categ'(s28).
lv_ltext = 'Sales Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VSBED'.
lv_position = lv_position + 1.
lv_stext = 'Shipping Cond'(s28).
lv_mtext = 'Shipping Cond'(s28).
lv_ltext = 'Shipping Cond'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNNR'.
lv_position = lv_position + 1.
lv_stext = 'Sold To'(s28).
lv_mtext = 'Sold To'(s28).
lv_ltext = 'Sold To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNAG'.
lv_position = lv_position + 1.
lv_stext = 'Ship To'(s28).
lv_mtext = 'Ship To'(s28).
lv_ltext = 'Ship To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WADAT_IST'.
lv_position = lv_position + 1.
lv_stext = 'Act Goods Issue Dt'(s28).
lv_mtext = 'Act Goods Issue Dt'(s28).
lv_ltext = 'Act Goods Issue Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'PSTYV'.
lv_position = lv_position + 1.
lv_stext = 'Item Categ'(s28).
lv_mtext = 'Item Categ'(s28).
lv_ltext = 'Item Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATNR'.
lv_position = lv_position + 1.
lv_stext = 'Material'(s28).
lv_mtext = 'Material'(s28).
lv_ltext = 'Material'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'LGORT'.
lv_position = lv_position + 1.
lv_stext = 'Storage Loc'(s28).
lv_mtext = 'Storage Loc'(s28).
lv_ltext = 'Storage Loc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KDMAT'.
lv_position = lv_position + 1.
lv_stext = 'Customer Mat No'(s28).
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 20
lv_mtext = 'Customer Mat No'(s28).
lv_ltext = 'Customer Mat No'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'LFIMG'.
lv_position = lv_position + 1.
lv_stext = 'Act Del Qty in SU'(s28).
lv_mtext = 'Act Del Qty in SU'(s28).
lv_ltext = 'Act Del Qty in SU'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VRKME'.
lv_position = lv_position + 1.
lv_stext = 'Sales Unit'(s28).
lv_mtext = 'Sales Unit'(s28).
lv_ltext = 'Sales Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NTGEW'.
lv_position = lv_position + 1.
lv_stext = 'Net Weight'(s28).
lv_mtext = 'Net Weight'(s28).
lv_ltext = 'Net Weight'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BRGEW'.
lv_position = lv_position + 1.
lv_stext = 'Gross Weight'(s28).
lv_mtext = 'Gross Weight'(s28).
lv_ltext = 'Gross Weight'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'GEWEI'.
lv_position = lv_position + 1.
lv_stext = 'Weight Unit'(s28).
lv_mtext = 'Weight Unit'(s28).
lv_ltext = 'Weight Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'LGMNG'.
lv_position = lv_position + 1.
lv_stext = 'Act Del Qty in Stock Keeping'(s28).
lv_mtext = 'Act Del Qty in Stock Keeping'(s28).
lv_ltext = 'Act Del Qty in Stock Keeping'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBTYV'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc Categ'(s28).
lv_mtext = 'Sales Doc Categ'(s28).
lv_ltext = 'Sales Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI1'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 1'(s28).
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 21
* lv_mtext = 'Subtotal 1'(s28).
* lv_ltext = 'Subtotal 1'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI2'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 2'(s28).
* lv_mtext = 'Subtotal 2'(s28).
* lv_ltext = 'Subtotal 2'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI3'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 3'(s28).
* lv_mtext = 'Subtotal 3'(s28).
* lv_ltext = 'Subtotal 3'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI4'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 4'(s28).
* lv_mtext = 'Subtotal 4'(s28).
* lv_ltext = 'Subtotal 4'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI5'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 5'(s28).
* lv_mtext = 'Subtotal 5'(s28).
* lv_ltext = 'Subtotal 5'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'KZWI6'.
* lv_position = lv_position + 1.
* lv_stext = 'Subtotal 6'(s28).
* lv_mtext = 'Subtotal 6'(s28).
* lv_ltext = 'Subtotal 6'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGBEL'.
lv_position = lv_position + 1.
lv_stext = 'Refer Doc'(s28).
lv_mtext = 'Refer Doc'(s28).
lv_ltext = 'Refer Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGPOS'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 22
lv_stext = 'Refer Item'(s28).
lv_mtext = 'Refer Item'(s28).
lv_ltext = 'Refer Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSAR'.
lv_position = lv_position + 1.
lv_stext = 'Item Type'(s28).
lv_mtext = 'Item Type'(s28).
lv_ltext = 'Item Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VTWEG'.
lv_position = lv_position + 1.
lv_stext = 'Dist Chan'(s28).
lv_mtext = 'Dist Chan'(s28).
lv_ltext = 'Dist Chan'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SPART'.
lv_position = lv_position + 1.
lv_stext = 'Division'(s28).
lv_mtext = 'Division'(s28).
lv_ltext = 'Division'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SHKZG'.
lv_position = lv_position + 1.
lv_stext = 'Returns'(s28).
lv_mtext = 'Returns'(s28).
lv_ltext = 'Returns'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'NETPR'.
* lv_position = lv_position + 1.
* lv_stext = 'Net Price'(s28).
* lv_mtext = 'Net price'(s28).
* lv_ltext = 'Net Price'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'WAVWR'.
* lv_position = lv_position + 1.
* lv_stext = 'Cost'(s28).
* lv_mtext = 'Cost'(s28).
* lv_ltext = 'Cost'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
** Specify the Columnn name and position to be place in the ALV output.
* lv_colname = 'NETWR'.
* lv_position = lv_position + 1.
* lv_stext = 'Net Value'(s28).
* lv_mtext = 'Net Value'(s28).
* lv_ltext = 'Net Value'(s29).
* PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
*
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 23
*
*
* Display the Header information.
CALL METHOD gr_table->set_top_of_list
EXPORTING
value = ls_rows.
* Getting the All columns names
gr_columns = gr_table->get_columns( ).
gr_functions = gr_table->get_functions( ).
gr_functions->set_all( abap_true ).
* To addd the sort functionality
gr_sorts = gr_table->get_sorts( ).
* gr_sorts->add_sort( columnname = 'VBELN'(s27) subtotal = abap_true ).
* gr_sorts->add_sort( columnname = 'POSNR'(s30) subtotal = abap_true ).
gr_agg = gr_table->get_aggregations( ).
gr_agg->add_aggregation( 'LFIMG'(s66) ).
gr_agg->add_aggregation( 'NTGEW'(s63) ).
gr_agg->add_aggregation( 'BRGEW'(s46) ).
gr_agg->add_aggregation( 'LGMNG'(s46) ).
* gr_agg->add_aggregation( 'NETPR'(s46) ).
* gr_agg->add_aggregation( 'NETWR'(s46) ).
* gr_agg->add_aggregation( 'WAVWR'(s55) ).
* gr_agg->add_aggregation( 'KZWI1'(s57) ).
* gr_agg->add_aggregation( 'KZWI2'(s57) ).
* gr_agg->add_aggregation( 'KZWI3'(s57) ).
* gr_agg->add_aggregation( 'KZWI4'(s57) ).
* gr_agg->add_aggregation( 'KZWI5'(s57) ).
* gr_agg->add_aggregation( 'KZWI6'(s57) ).
*
*Display output table.
gr_table->display( ).
*&---------------------------------------------------------------------*
*& Form F_SETCOLUMN_NAME
*&---------------------------------------------------------------------*
* Display the column according to the report output
*----------------------------------------------------------------------*
FORM f_setcolumn_name USING pu_colname TYPE lvc_fname " Field Name
pu_position TYPE i " Position
pu_lv_stext TYPE scrtext_s " Short Text
pu_lv_mtext TYPE scrtext_m " Medium Text
pu_lv_ltext TYPE scrtext_l. " Short Text
TRY.
* get the required column details to GR_COLUMN.
gr_column = gr_columns->get_column( pu_colname ).
* Short Text for column.
gr_column->set_short_text( pu_lv_stext ).
* Medium Text for column.
gr_column->set_medium_text( pu_lv_mtext ).
* Long Text for column.
gr_column->set_long_text( pu_lv_ltext ).
* Setting Column name and position.
gr_columns->set_column_position(
columnname = pu_colname
position = pu_position ).
CATCH cx_salv_not_found. "#EC
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 24
ENDTRY.
* clearing the variable used in the perform .
CLEAR: pu_colname,pu_lv_stext,pu_lv_mtext,pu_lv_ltext.
ENDFORM. " F_SETCOLUMN_NAME
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 25
Billing Analysis Program Code
*&---------------------------------------------------------------------*
*& Report ZBI_BILLING_ANALYSIS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZBI_BILLING_ANALYSIS.
TABLES : VBRK,VBRP.
START-OF-SELECTION.
SELECT-OPTIONS BIL_DOC FOR VBRK-VBELN.
SELECT-OPTIONS CRTD_ON FOR SY-DATUM.
SELECT-OPTIONS BILL_DT FOR SY-DATUM.
SELECT-OPTIONS BIL_TYPE FOR VBRK-FKART.
SELECT-OPTIONS BIL_CATG FOR VBRK-FKTYP.
SELECT-OPTIONS COMP_CDE FOR VBRK-BUKRS.
SELECT-OPTIONS SAL_ORG FOR VBRK-VKORG.
SELECT-OPTIONS DIS_CHAN FOR VBRK-VTWEG.
SELECT-OPTIONS DIVISION FOR VBRK-SPART.
SELECT-OPTIONS MATERIAL FOR VBRP-MATNR.
SELECT-OPTIONS PAYER FOR VBRK-KUNRG.
SELECT-OPTIONS SOLD_TO FOR VBRK-KUNAG.
SELECT-OPTIONS PLANT FOR VBRP-WERKS.
SELECT-OPTIONS SERV_DT FOR VBRP-FBUDA.
END-OF-SELECTION.
TYPES : BEGIN OF STR_BILL,
VBELN TYPE VBRK-VBELN,
POSNR TYPE VBRP-POSNR,
FKART TYPE VBRK-FKART,
FKTYP TYPE VBRK-FKTYP,
VBTYP TYPE VBRK-VBTYP,
VKORG TYPE VBRK-VKORG,
VTWEG TYPE VBRK-VTWEG,
KNUMV TYPE VBRK-KNUMV,
VSBED TYPE VBRK-VSBED,
FKDAT TYPE VBRK-FKDAT,
BUKRS TYPE VBRK-BUKRS,
ERDAT TYPE VBRK-ERDAT,
KUNRG TYPE VBRK-KUNRG,
KUNAG TYPE VBRK-KUNAG,
BSTNK_VF TYPE VBRK-BSTNK_VF,
FKIMG TYPE VBRP-FKIMG,
VRKME TYPE VBRP-VRKME,
FKLMG TYPE VBRP-FKLMG,
NTGEW TYPE VBRP-NTGEW,
BRGEW TYPE VBRP-BRGEW,
GEWEI TYPE VBRP-GEWEI,
PRSDT TYPE VBRP-PRSDT,
FBUDA TYPE VBRP-FBUDA,
NETWR TYPE VBRP-NETWR,
VGBEL TYPE VBRP-VGBEL,
VGPOS TYPE VBRP-VGPOS,
VGTYP TYPE VBRP-VGTYP,
AUBEL TYPE VBRP-AUBEL,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 26
AUPOS TYPE VBRP-AUPOS,
MATNR TYPE VBRP-MATNR,
MATKL TYPE VBRP-MATKL,
PSTYV TYPE VBRP-PSTYV,
POSAR TYPE VBRP-POSAR,
SPART TYPE VBRP-SPART,
WERKS TYPE VBRP-WERKS,
SHKZG TYPE VBRP-SHKZG,
WAVWR TYPE VBRP-WAVWR,
KZWI1 TYPE VBRP-KZWI1,
KZWI2 TYPE VBRP-KZWI2,
KZWI3 TYPE VBRP-KZWI3,
KZWI4 TYPE VBRP-KZWI4,
KZWI5 TYPE VBRP-KZWI5,
KZWI6 TYPE VBRP-KZWI6,
END OF STR_BILL.
TYPES : BEGIN OF STR_VBRK,
VBELN TYPE VBRK-VBELN,
FKART TYPE VBRK-FKART,
FKTYP TYPE VBRK-FKTYP,
VBTYP TYPE VBRK-VBTYP,
VKORG TYPE VBRK-VKORG,
VTWEG TYPE VBRK-VTWEG,
KNUMV TYPE VBRK-KNUMV,
VSBED TYPE VBRK-VSBED,
FKDAT TYPE VBRK-FKDAT,
BUKRS TYPE VBRK-BUKRS,
ERDAT TYPE VBRK-ERDAT,
KUNRG TYPE VBRK-KUNRG,
KUNAG TYPE VBRK-KUNAG,
SPART TYPE VBRK-SPART,
BSTNK_VF TYPE VBRK-BSTNK_VF,
END OF STR_VBRK.
TYPES : BEGIN OF STR_VBRP,
VBELN TYPE VBRP-VBELN,
POSNR TYPE VBRP-POSNR,
FKIMG TYPE VBRP-FKIMG,
VRKME TYPE VBRP-VRKME,
FKLMG TYPE VBRP-FKLMG,
NTGEW TYPE VBRP-NTGEW,
BRGEW TYPE VBRP-BRGEW,
GEWEI TYPE VBRP-GEWEI,
PRSDT TYPE VBRP-PRSDT,
FBUDA TYPE VBRP-FBUDA,
NETWR TYPE VBRP-NETWR,
VGBEL TYPE VBRP-VGBEL,
VGPOS TYPE VBRP-VGPOS,
VGTYP TYPE VBRP-VGTYP,
AUBEL TYPE VBRP-AUBEL,
AUPOS TYPE VBRP-AUPOS,
MATNR TYPE VBRP-VGBEL,
MATKL TYPE VBRP-MATKL,
PSTYV TYPE VBRP-PSTYV,
POSAR TYPE VBRP-POSAR,
SPART TYPE VBRP-SPART,
WERKS TYPE VBRP-WERKS,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 27
SHKZG TYPE VBRP-SHKZG,
WAVWR TYPE VBRP-WAVWR,
KZWI1 TYPE VBRP-KZWI1,
KZWI2 TYPE VBRP-KZWI2,
KZWI3 TYPE VBRP-KZWI3,
KZWI4 TYPE VBRP-KZWI4,
KZWI5 TYPE VBRP-KZWI5,
KZWI6 TYPE VBRP-KZWI6,
END OF STR_VBRP.
DATA : IT_VBRK TYPE TABLE OF STR_VBRK,
IT_VBRP TYPE TABLE OF STR_VBRP,
WA_VBRK TYPE STR_VBRK,
WA_VBRP TYPE STR_VBRP,
IT_BILL TYPE TABLE OF STR_BILL,
WA_BILL TYPE STR_BILL,
IT_OUTPUT TYPE TABLE OF STR_BILL,
WA_OUTPUT TYPE STR_BILL.
type-pools : slis .
* data: fieldcatalog type slis_t_fieldcat_alv with header line,
* gd_tab_group type slis_t_sp_group_alv,
* gd_layout type slis_layout_alv,
* gd_repid like sy-repid,
* gt_events type slis_t_event.
DATA: gr_table TYPE REF TO cl_salv_table,
gr_functions TYPE REF TO cl_salv_functions, "#EC *
gr_columns TYPE REF TO cl_salv_columns, "#EC *
gr_column TYPE REF TO cl_salv_column, "#EC *
gr_sorts TYPE REF TO cl_salv_sorts,
gr_agg TYPE REF TO cl_salv_aggregations.
SELECT * FROM VBRK INTO CORRESPONDING FIELDS OF TABLE IT_VBRK WHERE
VBELN IN BIL_DOC AND ERDAT IN CRTD_ON AND FKDAT IN BILL_DT AND
FKART IN BIL_TYPE AND FKTYP IN BIL_CATG AND BUKRS IN COMP_CDE AND
VKORG IN SAL_ORG AND VTWEG IN DIS_CHAN AND SPART IN DIVISION AND
KUNRG IN PAYER AND KUNAG IN SOLD_TO.
SELECT * FROM VBRP INTO CORRESPONDING FIELDS OF TABLE IT_VBRP
FOR ALL ENTRIES IN IT_VBRK WHERE VBELN = IT_VBRK-VBELN AND
MATNR IN MATERIAL AND WERKS IN PLANT AND FBUDA IN SERV_DT.
LOOP AT IT_VBRP INTO WA_VBRP.
WA_BILL-VBELN = WA_VBRP-VBELN.
WA_BILL-POSNR = WA_VBRP-POSNR.
WA_BILL-FKIMG = WA_VBRP-FKIMG.
WA_BILL-VRKME = WA_VBRP-VRKME.
WA_BILL-FKLMG = WA_VBRP-FKLMG.
WA_BILL-NTGEW = WA_VBRP-NTGEW.
WA_BILL-BRGEW = WA_VBRP-BRGEW.
WA_BILL-GEWEI = WA_VBRP-GEWEI.
WA_BILL-PRSDT = WA_VBRP-PRSDT.
WA_BILL-FBUDA = WA_VBRP-FBUDA.
WA_BILL-NETWR = WA_VBRP-NETWR.
WA_BILL-VGBEL = WA_VBRP-VGBEL.
WA_BILL-VGPOS = WA_VBRP-VGPOS.
WA_BILL-VGTYP = WA_VBRP-VGTYP.
WA_BILL-AUBEL = WA_VBRP-AUBEL.
WA_BILL-AUPOS = WA_VBRP-AUPOS.
WA_BILL-MATNR = WA_VBRP-MATNR.
WA_BILL-MATKL = WA_VBRP-MATKL.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 28
WA_BILL-PSTYV = WA_VBRP-PSTYV.
WA_BILL-POSAR = WA_VBRP-POSAR.
WA_BILL-SPART = WA_VBRP-SPART.
WA_BILL-WERKS = WA_VBRP-WERKS.
WA_BILL-SHKZG = WA_VBRP-SHKZG.
WA_BILL-WAVWR = WA_VBRP-WAVWR.
WA_BILL-KZWI1 = WA_VBRP-KZWI1.
WA_BILL-KZWI2 = WA_VBRP-KZWI2.
WA_BILL-KZWI3 = WA_VBRP-KZWI3.
WA_BILL-KZWI4 = WA_VBRP-KZWI4.
WA_BILL-KZWI5 = WA_VBRP-KZWI5.
WA_BILL-KZWI6 = WA_VBRP-KZWI6.
APPEND WA_BILL TO IT_BILL.
CLEAR : WA_BILL, WA_VBRP.
ENDLOOP.
LOOP AT IT_BILL INTO WA_BILL.
READ TABLE IT_VBRK INTO WA_VBRK
WITH KEY VBELN = WA_BILL-VBELN.
IF SY-SUBRC EQ 0.
WA_BILL-FKART = WA_VBRK-FKART.
WA_BILL-FKTYP = WA_VBRK-FKTYP.
WA_BILL-VBTYP = WA_VBRK-VBTYP.
WA_BILL-VKORG = WA_VBRK-VKORG.
WA_BILL-VTWEG = WA_VBRK-VTWEG.
WA_BILL-VSBED = WA_VBRK-VSBED.
WA_BILL-FKDAT = WA_VBRK-FKDAT.
WA_BILL-BUKRS = WA_VBRK-BUKRS.
WA_BILL-ERDAT = WA_VBRK-ERDAT.
WA_BILL-KUNRG = WA_VBRK-KUNRG.
WA_BILL-KUNAG = WA_VBRK-KUNAG.
WA_BILL-SPART = WA_VBRK-SPART.
WA_BILL-BSTNK_VF = WA_VBRK-BSTNK_VF.
WA_BILL-KNUMV = WA_VBRK-KNUMV.
ENDIF.
MODIFY IT_BILL FROM WA_BILL.
CLEAR : WA_BILL, WA_VBRK, WA_VBRP.
ENDLOOP.
IT_OUTPUT[] = IT_BILL[].
DATA: ls_info TYPE slis_listheader,
lv_stext TYPE scrtext_s, " Short Text
lv_mtext TYPE scrtext_m, " Medium Text
lv_ltext TYPE scrtext_l, " Long Text
lv_colname TYPE lvc_fname, " Column Name
lv_position TYPE i VALUE 1, " Position
ls_line TYPE slis_listheader, "
lv_char(15) TYPE c.
* Class declarations
DATA: ls_rows TYPE REF TO cl_salv_form_layout_grid,
ls_row TYPE REF TO cl_salv_form_layout_flow.
* Create Object Reference
CREATE OBJECT ls_rows.
TRY.
cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING t_table = it_output ). "#EC
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 29
CATCH cx_salv_msg. "#EC
CATCH cx_salv_not_found. "#EC
ENDTRY.
gr_columns = gr_table->get_columns( ).
gr_columns->set_optimize( abap_true ).
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBELN'.
lv_position = 1.
lv_stext = 'Billing Doc'(s28).
lv_mtext = 'Billing Doc'(s28).
lv_ltext = 'Billing Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSNR'.
lv_position = lv_position + 1.
lv_stext = 'Billing Item'(s28).
lv_mtext = 'Billing Item'(s28).
lv_ltext = 'Billing Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKIMG'.
lv_position = lv_position + 1.
lv_stext = 'Act Inv Qty'(s28).
lv_mtext = 'Act Inv Qty'(s28).
lv_ltext = 'Act inv Qty'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VRKME'.
lv_position = lv_position + 1.
lv_stext = 'Sales Unit'(s28).
lv_mtext = 'Sales Unit'(s28).
lv_ltext = 'Sales Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKLMG'.
lv_position = lv_position + 1.
lv_stext = 'Bill Qty in Stock Keeping'(s28).
lv_mtext = 'Bill Qty in Stock Keeping'(s28).
lv_ltext = 'Bill Qty in Stock Keeping'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NTGEW'.
lv_position = lv_position + 1.
lv_stext = 'Net Wt'(s28).
lv_mtext = 'Net Wt'(s28).
lv_ltext = 'Net Wt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BRGEW'.
lv_position = lv_position + 1.
lv_stext = 'Gross Wt'(s28).
lv_mtext = 'Gross Wt'(s28).
lv_ltext = 'Gross Wt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'GEWEI'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 30
lv_position = lv_position + 1.
lv_stext = 'Wt Unit'(s28).
lv_mtext = 'wt unit'(s28).
lv_ltext = 'Wt Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'PRSDT'.
lv_position = lv_position + 1.
lv_stext = 'Pricing Dt'(s28).
lv_mtext = 'Pricing Dt'(s28).
lv_ltext = 'Pricing Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FBUDA'.
lv_position = lv_position + 1.
lv_stext = 'Service Rendered Dt'(s28).
lv_mtext = 'Service Rendered Dt'(s28).
lv_ltext = 'Service Rendered Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NETWR'.
lv_position = lv_position + 1.
lv_stext = 'Net Value'(s28).
lv_mtext = 'Net Value'(s28).
lv_ltext = 'Net Value'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGBEL'.
lv_position = lv_position + 1.
lv_stext = 'Refer Doc'(s28).
lv_mtext = 'Refer Doc'(s28).
lv_ltext = 'Refer Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGPOS'.
lv_position = lv_position + 1.
lv_stext = 'Refer Item'(s28).
lv_mtext = 'Refer Item'(s28).
lv_ltext = 'Refer Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGTYP'.
lv_position = lv_position + 1.
lv_stext = 'Preceeding Doc Categ'(s28).
lv_mtext = 'Preceeding Doc Categ'(s28).
lv_ltext = 'Preceeding Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUBEL'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc'(s28).
lv_mtext = 'Sales Doc'(s28).
lv_ltext = 'Sales Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUPOS'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 31
lv_position = lv_position + 1.
lv_stext = 'Sales Item'(s28).
lv_mtext = 'Sales Item'(s28).
lv_ltext = 'Sales Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATNR'.
lv_position = lv_position + 1.
lv_stext = 'Material'(s28).
lv_mtext = 'Material'(s28).
lv_ltext = 'Material'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATKL'.
lv_position = lv_position + 1.
lv_stext = 'Material Grp'(s28).
lv_mtext = 'Material Grp'(s28).
lv_ltext = 'Material Grp'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'PSTYV'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc Item Categ'(s28).
lv_mtext = 'Sales Doc Item Categ'(s28).
lv_ltext = 'Sales Doc Item Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSAR'.
lv_position = lv_position + 1.
lv_stext = 'Item Type'(s28).
lv_mtext = 'Item Type'(s28).
lv_ltext = 'Item Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SPART'.
lv_position = lv_position + 1.
lv_stext = 'Division'(s28).
lv_mtext = 'Division'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WERKS'.
lv_position = lv_position + 1.
lv_stext = 'Plant'(s28).
lv_mtext = 'Plant'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SHKZG'.
lv_position = lv_position + 1.
lv_stext = 'Returns Item'(s28).
lv_mtext = 'Returns Item'(s28).
lv_ltext = 'Returns Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WAVWR'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 32
lv_position = lv_position + 1.
lv_stext = 'Cost'(s28).
lv_mtext = 'Cost'(s28).
lv_ltext = 'Cost'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI1'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 1'(s28).
lv_mtext = 'Sub Total 1'(s28).
lv_ltext = 'Sub Total 1'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI2'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 2'(s28).
lv_mtext = 'Sub Total 2'(s28).
lv_ltext = 'Sub Total 2'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI3'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 3'(s28).
lv_mtext = 'Sub Total 3'(s28).
lv_ltext = 'Sub Total 3'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI4'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 4'(s28).
lv_mtext = 'Sub Total 4'(s28).
lv_ltext = 'Sub Total 4'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI5'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 5'(s28).
lv_mtext = 'Sub Total 5'(s28).
lv_ltext = 'Sub Total 5'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI6'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 6'(s28).
lv_mtext = 'Sub Total 6'(s28).
lv_ltext = 'Sub Total 6'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKART'.
lv_position = lv_position + 1.
lv_stext = 'Billing Type'(s28).
lv_mtext = 'Billing Type'(s28).
lv_ltext = 'Billing Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKTYP'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 33
lv_position = lv_position + 1.
lv_stext = 'Billing Categ'(s28).
lv_mtext = 'Billing Categ'(s28).
lv_ltext = 'Billing Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBTYP'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc categ'(s28).
lv_mtext = 'Sales Doc Categ'(s28).
lv_ltext = 'Sales Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VKORG'.
lv_position = lv_position + 1.
lv_stext = 'Sales Org'(s28).
lv_mtext = 'Sales Org'(s28).
lv_ltext = 'Sales Org'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VTWEG'.
lv_position = lv_position + 1.
lv_stext = 'Dist Chan'(s28).
lv_mtext = 'Dist Chan'(s28).
lv_ltext = 'Dist Chan'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VSBED'.
lv_position = lv_position + 1.
lv_stext = 'Ship Cond'(s28).
lv_mtext = 'Ship Cond'(s28).
lv_ltext = 'Ship Cond'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKDAT'.
lv_position = lv_position + 1.
lv_stext = 'Billing Date'(s28).
lv_mtext = 'Billing Date'(s28).
lv_ltext = 'Billing Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BUKRS'.
lv_position = lv_position + 1.
lv_stext = 'Comp Code'(s28).
lv_mtext = 'Comp Code'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ERDAT'.
lv_position = lv_position + 1.
lv_stext = 'Created On'(s28).
lv_mtext = 'Created On'(s28).
lv_ltext = 'Created On'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNRG'.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 34
lv_position = lv_position + 1.
lv_stext = 'Sold To'(s28).
lv_mtext = 'Sold To'(s28).
lv_ltext = 'Sold To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNAG'.
lv_position = lv_position + 1.
lv_stext = 'Ship To'(s28).
lv_mtext = 'Ship To'(s28).
lv_ltext = 'Ship To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BSTNK_VF'.
lv_position = lv_position + 1.
lv_stext = 'Cust PO No'(s28).
lv_mtext = 'Cust PO No'(s28).
lv_ltext = 'Cust PO No'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Display the Header information.
CALL METHOD gr_table->set_top_of_list
EXPORTING
value = ls_rows.
* Getting the All columns names
gr_columns = gr_table->get_columns( ).
gr_functions = gr_table->get_functions( ).
gr_functions->set_all( abap_true ).
* To addd the sort functionality
gr_sorts = gr_table->get_sorts( ).
* gr_sorts->add_sort( columnname = 'VBELN'(s27) subtotal = abap_true ).
* gr_sorts->add_sort( columnname = 'POSNR'(s30) subtotal = abap_true ).
gr_agg = gr_table->get_aggregations( ).
gr_agg->add_aggregation( 'NETWR'(s63) ).
gr_agg->add_aggregation( 'WAVWR'(s55) ).
gr_agg->add_aggregation( 'FKIMG'(s57) ).
gr_agg->add_aggregation( 'KZWI1'(s57) ).
gr_agg->add_aggregation( 'KZWI2'(s57) ).
gr_agg->add_aggregation( 'KZWI3'(s57) ).
gr_agg->add_aggregation( 'KZWI4'(s57) ).
gr_agg->add_aggregation( 'KZWI5'(s57) ).
gr_agg->add_aggregation( 'KZWI6'(s57) ).
*Display output table.
gr_table->display( ).
*&---------------------------------------------------------------------*
*& Form F_SETCOLUMN_NAME
*&---------------------------------------------------------------------*
* Display the column according to the report output
*----------------------------------------------------------------------*
FORM f_setcolumn_name USING pu_colname TYPE lvc_fname " Field Name
pu_position TYPE i " Position
pu_lv_stext TYPE scrtext_s " Short Text
pu_lv_mtext TYPE scrtext_m " Medium Text
pu_lv_ltext TYPE scrtext_l. " Short Text
TRY.
* get the required column details to GR_COLUMN.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 35
gr_column = gr_columns->get_column( pu_colname ).
* Short Text for column.
gr_column->set_short_text( pu_lv_stext ).
* Medium Text for column.
gr_column->set_medium_text( pu_lv_mtext ).
* Long Text for column.
gr_column->set_long_text( pu_lv_ltext ).
* Setting Column name and position.
gr_columns->set_column_position(
columnname = pu_colname
position = pu_position ).
CATCH cx_salv_not_found. "#EC
ENDTRY.
* clearing the variable used in the perform .
CLEAR: pu_colname,pu_lv_stext,pu_lv_mtext,pu_lv_ltext.
ENDFORM. " F_SETCOLUMN_NAME
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 36
Billing Conditions Analysis Program Code
*&---------------------------------------------------------------------*
*& Report ZBI_BILLING_COND_ANALYSIS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZBI_BILLING_COND_ANALYSIS.
TABLES : VBRK,VBRP,KONV.
START-OF-SELECTION.
SELECT-OPTIONS BIL_DOC FOR VBRK-VBELN.
SELECT-OPTIONS CRTD_ON FOR SY-DATUM.
SELECT-OPTIONS BILL_DT FOR SY-DATUM.
SELECT-OPTIONS BIL_TYPE FOR VBRK-FKART.
SELECT-OPTIONS BIL_CATG FOR VBRK-FKTYP.
SELECT-OPTIONS COMP_CDE FOR VBRK-BUKRS.
SELECT-OPTIONS SAL_ORG FOR VBRK-VKORG.
SELECT-OPTIONS DIS_CHAN FOR VBRK-VTWEG.
SELECT-OPTIONS DIVISION FOR VBRK-SPART.
SELECT-OPTIONS MATERIAL FOR VBRP-MATNR.
SELECT-OPTIONS PAYER FOR VBRK-KUNRG.
SELECT-OPTIONS SOLD_TO FOR VBRK-KUNAG.
SELECT-OPTIONS PLANT FOR VBRP-WERKS.
SELECT-OPTIONS SERV_DT FOR VBRP-FBUDA.
END-OF-SELECTION.
TYPES : BEGIN OF STR_BILL,
VBELN TYPE VBRK-VBELN,
POSNR TYPE VBRP-POSNR,
FKART TYPE VBRK-FKART,
FKTYP TYPE VBRK-FKTYP,
VBTYP TYPE VBRK-VBTYP,
VKORG TYPE VBRK-VKORG,
VTWEG TYPE VBRK-VTWEG,
KNUMV TYPE VBRK-KNUMV,
VSBED TYPE VBRK-VSBED,
FKDAT TYPE VBRK-FKDAT,
BUKRS TYPE VBRK-BUKRS,
ERDAT TYPE VBRK-ERDAT,
KUNRG TYPE VBRK-KUNRG,
KUNAG TYPE VBRK-KUNAG,
BSTNK_VF TYPE VBRK-BSTNK_VF,
FKIMG TYPE VBRP-FKIMG,
VRKME TYPE VBRP-VRKME,
FKLMG TYPE VBRP-FKLMG,
NTGEW TYPE VBRP-NTGEW,
BRGEW TYPE VBRP-BRGEW,
GEWEI TYPE VBRP-GEWEI,
PRSDT TYPE VBRP-PRSDT,
FBUDA TYPE VBRP-FBUDA,
NETWR TYPE VBRP-NETWR,
VGBEL TYPE VBRP-VGBEL,
VGPOS TYPE VBRP-VGPOS,
VGTYP TYPE VBRP-VGTYP,
AUBEL TYPE VBRP-AUBEL,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 37
AUPOS TYPE VBRP-AUPOS,
MATNR TYPE VBRP-MATNR,
MATKL TYPE VBRP-MATKL,
PSTYV TYPE VBRP-PSTYV,
POSAR TYPE VBRP-POSAR,
SPART TYPE VBRP-SPART,
WERKS TYPE VBRP-WERKS,
SHKZG TYPE VBRP-SHKZG,
WAVWR TYPE VBRP-WAVWR,
KZWI1 TYPE VBRP-KZWI1,
KZWI2 TYPE VBRP-KZWI2,
KZWI3 TYPE VBRP-KZWI3,
KZWI4 TYPE VBRP-KZWI4,
KZWI5 TYPE VBRP-KZWI5,
KZWI6 TYPE VBRP-KZWI6,
END OF STR_BILL.
TYPES : BEGIN OF STR_BILL_COND,
VBELN TYPE VBRK-VBELN,
POSNR TYPE VBRP-POSNR,
AUBEL TYPE VBRP-AUBEL,
AUPOS TYPE VBRP-AUPOS,
KSCHL TYPE KONV-KSCHL,
FKART TYPE VBRK-FKART,
FKTYP TYPE VBRK-FKTYP,
VBTYP TYPE VBRK-VBTYP,
VKORG TYPE VBRK-VKORG,
VTWEG TYPE VBRK-VTWEG,
VSBED TYPE VBRK-VSBED,
FKDAT TYPE VBRK-FKDAT,
BUKRS TYPE VBRK-BUKRS,
ERDAT TYPE VBRK-ERDAT,
KUNRG TYPE VBRK-KUNRG,
KUNAG TYPE VBRK-KUNAG,
BSTNK_VF TYPE VBRK-BSTNK_VF,
FKIMG TYPE VBRP-FKIMG,
VRKME TYPE VBRP-VRKME,
FKLMG TYPE VBRP-FKLMG,
NTGEW TYPE VBRP-NTGEW,
BRGEW TYPE VBRP-BRGEW,
GEWEI TYPE VBRP-GEWEI,
PRSDT TYPE VBRP-PRSDT,
FBUDA TYPE VBRP-FBUDA,
NETWR TYPE VBRP-NETWR,
VGBEL TYPE VBRP-VGBEL,
VGPOS TYPE VBRP-VGPOS,
VGTYP TYPE VBRP-VGTYP,
MATNR TYPE VBRP-MATNR,
MATKL TYPE VBRP-MATKL,
PSTYV TYPE VBRP-PSTYV,
POSAR TYPE VBRP-POSAR,
SPART TYPE VBRP-SPART,
WERKS TYPE VBRP-WERKS,
SHKZG TYPE VBRP-SHKZG,
WAVWR TYPE VBRP-WAVWR,
KZWI1 TYPE VBRP-KZWI1,
KZWI2 TYPE VBRP-KZWI2,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 38
KZWI3 TYPE VBRP-KZWI3,
KZWI4 TYPE VBRP-KZWI4,
KZWI5 TYPE VBRP-KZWI5,
KZWI6 TYPE VBRP-KZWI6,
KAWRT TYPE KONV-KAWRT,
KBETR TYPE KONV-KBETR,
WAERS TYPE KONV-WAERS,
KPEIN TYPE KONV-KPEIN,
KMEIN TYPE KONV-KMEIN,
END OF STR_BILL_COND.
TYPES : BEGIN OF STR_VBRK,
VBELN TYPE VBRK-VBELN,
FKART TYPE VBRK-FKART,
FKTYP TYPE VBRK-FKTYP,
VBTYP TYPE VBRK-VBTYP,
VKORG TYPE VBRK-VKORG,
VTWEG TYPE VBRK-VTWEG,
KNUMV TYPE VBRK-KNUMV,
VSBED TYPE VBRK-VSBED,
FKDAT TYPE VBRK-FKDAT,
BUKRS TYPE VBRK-BUKRS,
ERDAT TYPE VBRK-ERDAT,
KUNRG TYPE VBRK-KUNRG,
KUNAG TYPE VBRK-KUNAG,
SPART TYPE VBRK-SPART,
BSTNK_VF TYPE VBRK-BSTNK_VF,
END OF STR_VBRK.
TYPES : BEGIN OF STR_VBRP,
VBELN TYPE VBRP-VBELN,
POSNR TYPE VBRP-POSNR,
FKIMG TYPE VBRP-FKIMG,
VRKME TYPE VBRP-VRKME,
FKLMG TYPE VBRP-FKLMG,
NTGEW TYPE VBRP-NTGEW,
BRGEW TYPE VBRP-BRGEW,
GEWEI TYPE VBRP-GEWEI,
PRSDT TYPE VBRP-PRSDT,
FBUDA TYPE VBRP-FBUDA,
NETWR TYPE VBRP-NETWR,
VGBEL TYPE VBRP-VGBEL,
VGPOS TYPE VBRP-VGPOS,
VGTYP TYPE VBRP-VGTYP,
AUBEL TYPE VBRP-AUBEL,
AUPOS TYPE VBRP-AUPOS,
MATNR TYPE VBRP-VGBEL,
MATKL TYPE VBRP-MATKL,
PSTYV TYPE VBRP-PSTYV,
POSAR TYPE VBRP-POSAR,
SPART TYPE VBRP-SPART,
WERKS TYPE VBRP-WERKS,
SHKZG TYPE VBRP-SHKZG,
WAVWR TYPE VBRP-WAVWR,
KZWI1 TYPE VBRP-KZWI1,
KZWI2 TYPE VBRP-KZWI2,
KZWI3 TYPE VBRP-KZWI3,
KZWI4 TYPE VBRP-KZWI4,
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 39
KZWI5 TYPE VBRP-KZWI5,
KZWI6 TYPE VBRP-KZWI6,
END OF STR_VBRP.
TYPES : BEGIN OF STR_KONV,
KNUMV TYPE KONV-KNUMV,
KPOSN TYPE KONV-KPOSN,
STUNR TYPE KONV-STUNR,
ZAEHK TYPE KONV-ZAEHK,
KAPPL TYPE KONV-KAPPL,
KSCHL TYPE KONV-KSCHL,
KAWRT TYPE KONV-KAWRT,
KBETR TYPE KONV-KBETR,
WAERS TYPE KONV-WAERS,
KPEIN TYPE KONV-KPEIN,
KMEIN TYPE KONV-KMEIN,
KNUMH TYPE KONV-KNUMH,
KOPOS TYPE KONV-KOPOS,
KINAK TYPE KONV-KINAK,
END OF STR_KONV.
DATA : IT_VBRK TYPE TABLE OF STR_VBRK,
IT_VBRP TYPE TABLE OF STR_VBRP,
IT_KONV TYPE TABLE OF STR_KONV,
WA_VBRK TYPE STR_VBRK,
WA_VBRP TYPE STR_VBRP,
WA_KONV TYPE STR_KONV,
IT_BILL TYPE TABLE OF STR_BILL,
WA_BILL TYPE STR_BILL,
IT_OUTPUT TYPE TABLE OF STR_BILL_COND,
WA_OUTPUT TYPE STR_BILL_COND.
type-pools : slis .
* data: fieldcatalog type slis_t_fieldcat_alv with header line,
* gd_tab_group type slis_t_sp_group_alv,
* gd_layout type slis_layout_alv,
* gd_repid like sy-repid,
* gt_events type slis_t_event.
DATA: gr_table TYPE REF TO cl_salv_table,
gr_functions TYPE REF TO cl_salv_functions, "#EC *
gr_columns TYPE REF TO cl_salv_columns, "#EC *
gr_column TYPE REF TO cl_salv_column, "#EC *
gr_sorts TYPE REF TO cl_salv_sorts,
gr_agg TYPE REF TO cl_salv_aggregations.
SELECT * FROM VBRK INTO CORRESPONDING FIELDS OF TABLE IT_VBRK WHERE
VBELN IN BIL_DOC AND ERDAT IN CRTD_ON AND FKDAT IN BILL_DT AND
FKART IN BIL_TYPE AND FKTYP IN BIL_CATG AND BUKRS IN COMP_CDE AND
VKORG IN SAL_ORG AND VTWEG IN DIS_CHAN AND SPART IN DIVISION AND
KUNRG IN PAYER AND KUNAG IN SOLD_TO.
SELECT * FROM VBRP INTO CORRESPONDING FIELDS OF TABLE IT_VBRP
FOR ALL ENTRIES IN IT_VBRK WHERE VBELN = IT_VBRK-VBELN AND
MATNR IN MATERIAL AND WERKS IN PLANT AND FBUDA IN SERV_DT.
SELECT * FROM KONV INTO CORRESPONDING FIELDS OF TABLE
IT_KONV FOR ALL ENTRIES IN IT_VBRK WHERE
KNUMV = IT_VBRK-KNUMV AND KINAK NE 'X'.
LOOP AT IT_VBRP INTO WA_VBRP.
WA_BILL-VBELN = WA_VBRP-VBELN.
WA_BILL-POSNR = WA_VBRP-POSNR.
WA_BILL-FKIMG = WA_VBRP-FKIMG.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 40
WA_BILL-VRKME = WA_VBRP-VRKME.
WA_BILL-FKLMG = WA_VBRP-FKLMG.
WA_BILL-NTGEW = WA_VBRP-NTGEW.
WA_BILL-BRGEW = WA_VBRP-BRGEW.
WA_BILL-GEWEI = WA_VBRP-GEWEI.
WA_BILL-PRSDT = WA_VBRP-PRSDT.
WA_BILL-FBUDA = WA_VBRP-FBUDA.
WA_BILL-NETWR = WA_VBRP-NETWR.
WA_BILL-VGBEL = WA_VBRP-VGBEL.
WA_BILL-VGPOS = WA_VBRP-VGPOS.
WA_BILL-VGTYP = WA_VBRP-VGTYP.
WA_BILL-AUBEL = WA_VBRP-AUBEL.
WA_BILL-AUPOS = WA_VBRP-AUPOS.
WA_BILL-MATNR = WA_VBRP-MATNR.
WA_BILL-MATKL = WA_VBRP-MATKL.
WA_BILL-PSTYV = WA_VBRP-PSTYV.
WA_BILL-POSAR = WA_VBRP-POSAR.
WA_BILL-SPART = WA_VBRP-SPART.
WA_BILL-WERKS = WA_VBRP-WERKS.
WA_BILL-SHKZG = WA_VBRP-SHKZG.
WA_BILL-WAVWR = WA_VBRP-WAVWR.
WA_BILL-KZWI1 = WA_VBRP-KZWI1.
WA_BILL-KZWI2 = WA_VBRP-KZWI2.
WA_BILL-KZWI3 = WA_VBRP-KZWI3.
WA_BILL-KZWI4 = WA_VBRP-KZWI4.
WA_BILL-KZWI5 = WA_VBRP-KZWI5.
WA_BILL-KZWI6 = WA_VBRP-KZWI6.
APPEND WA_BILL TO IT_BILL.
CLEAR : WA_BILL, WA_VBRP.
ENDLOOP.
LOOP AT IT_BILL INTO WA_BILL.
READ TABLE IT_VBRK INTO WA_VBRK
WITH KEY VBELN = WA_BILL-VBELN.
IF SY-SUBRC EQ 0.
WA_BILL-FKART = WA_VBRK-FKART.
WA_BILL-FKTYP = WA_VBRK-FKTYP.
WA_BILL-VBTYP = WA_VBRK-VBTYP.
WA_BILL-VKORG = WA_VBRK-VKORG.
WA_BILL-VTWEG = WA_VBRK-VTWEG.
WA_BILL-VSBED = WA_VBRK-VSBED.
WA_BILL-FKDAT = WA_VBRK-FKDAT.
WA_BILL-BUKRS = WA_VBRK-BUKRS.
WA_BILL-ERDAT = WA_VBRK-ERDAT.
WA_BILL-KUNRG = WA_VBRK-KUNRG.
WA_BILL-KUNAG = WA_VBRK-KUNAG.
WA_BILL-SPART = WA_VBRK-SPART.
WA_BILL-BSTNK_VF = WA_VBRK-BSTNK_VF.
WA_BILL-KNUMV = WA_VBRK-KNUMV.
ENDIF.
MODIFY IT_BILL FROM WA_BILL.
CLEAR : WA_BILL, WA_VBRK, WA_VBRP.
ENDLOOP.
LOOP AT IT_KONV INTO WA_KONV.
READ TABLE IT_BILL INTO WA_BILL WITH KEY KNUMV = WA_KONV-KNUMV
POSNR = WA_KONV-KPOSN.
WA_OUTPUT-VBELN = WA_BILL-VBELN.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 41
WA_OUTPUT-POSNR = WA_BILL-POSNR.
WA_OUTPUT-KSCHL = WA_KONV-KSCHL.
WA_OUTPUT-KAWRT = WA_KONV-KAWRT.
WA_OUTPUT-KBETR = WA_KONV-KBETR.
WA_OUTPUT-WAERS = WA_KONV-WAERS.
WA_OUTPUT-KPEIN = WA_KONV-KPEIN.
WA_OUTPUT-KMEIN = WA_KONV-KMEIN.
WA_OUTPUT-FKIMG = WA_BILL-FKIMG.
WA_OUTPUT-VRKME = WA_BILL-VRKME.
WA_OUTPUT-FKLMG = WA_BILL-FKLMG.
WA_OUTPUT-NTGEW = WA_BILL-NTGEW.
WA_OUTPUT-BRGEW = WA_BILL-BRGEW.
WA_OUTPUT-GEWEI = WA_BILL-GEWEI.
WA_OUTPUT-PRSDT = WA_BILL-PRSDT.
WA_OUTPUT-FBUDA = WA_BILL-FBUDA.
WA_OUTPUT-NETWR = WA_BILL-NETWR.
WA_OUTPUT-VGBEL = WA_BILL-VGBEL.
WA_OUTPUT-VGPOS = WA_BILL-VGPOS.
WA_OUTPUT-VGTYP = WA_BILL-VGTYP.
WA_OUTPUT-AUBEL = WA_BILL-AUBEL.
WA_OUTPUT-AUPOS = WA_BILL-AUPOS.
WA_OUTPUT-MATNR = WA_BILL-MATNR.
WA_OUTPUT-MATKL = WA_BILL-MATKL.
WA_OUTPUT-PSTYV = WA_BILL-PSTYV.
WA_OUTPUT-POSAR = WA_BILL-POSAR.
WA_OUTPUT-SPART = WA_BILL-SPART.
WA_OUTPUT-WERKS = WA_BILL-WERKS.
WA_OUTPUT-SHKZG = WA_BILL-SHKZG.
WA_OUTPUT-WAVWR = WA_BILL-WAVWR.
WA_OUTPUT-KZWI1 = WA_BILL-KZWI1.
WA_OUTPUT-KZWI2 = WA_BILL-KZWI2.
WA_OUTPUT-KZWI3 = WA_BILL-KZWI3.
WA_OUTPUT-KZWI4 = WA_BILL-KZWI4.
WA_OUTPUT-KZWI5 = WA_BILL-KZWI5.
WA_OUTPUT-KZWI6 = WA_BILL-KZWI6.
WA_OUTPUT-FKART = WA_BILL-FKART.
WA_OUTPUT-FKTYP = WA_BILL-FKTYP.
WA_OUTPUT-VBTYP = WA_BILL-VBTYP.
WA_OUTPUT-VKORG = WA_BILL-VKORG.
WA_OUTPUT-VTWEG = WA_BILL-VTWEG.
WA_OUTPUT-VSBED = WA_BILL-VSBED.
WA_OUTPUT-FKDAT = WA_BILL-FKDAT.
WA_OUTPUT-BUKRS = WA_BILL-BUKRS.
WA_OUTPUT-ERDAT = WA_BILL-ERDAT.
WA_OUTPUT-KUNRG = WA_BILL-KUNRG.
WA_OUTPUT-KUNAG = WA_BILL-KUNAG.
WA_OUTPUT-SPART = WA_BILL-SPART.
WA_OUTPUT-BSTNK_VF = WA_BILL-BSTNK_VF.
APPEND WA_OUTPUT TO IT_OUTPUT.
CLEAR : WA_OUTPUT, WA_BILL, WA_KONV.
ENDLOOP.
DATA: ls_info TYPE slis_listheader,
lv_stext TYPE scrtext_s, " Short Text
lv_mtext TYPE scrtext_m, " Medium Text
lv_ltext TYPE scrtext_l, " Long Text
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 42
lv_colname TYPE lvc_fname, " Column Name
lv_position TYPE i VALUE 1, " Position
ls_line TYPE slis_listheader, "
lv_char(15) TYPE c.
* Class declarations
DATA: ls_rows TYPE REF TO cl_salv_form_layout_grid,
ls_row TYPE REF TO cl_salv_form_layout_flow.
* Create Object Reference
CREATE OBJECT ls_rows.
TRY.
cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING t_table = it_output ). "#EC
CATCH cx_salv_msg. "#EC
CATCH cx_salv_not_found. "#EC
ENDTRY.
gr_columns = gr_table->get_columns( ).
gr_columns->set_optimize( abap_true ).
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBELN'.
lv_position = 1.
lv_stext = 'Billing Doc'(s28).
lv_mtext = 'Billing Doc'(s28).
lv_ltext = 'Billing Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSNR'.
lv_position = lv_position + 1.
lv_stext = 'Billing Item'(s28).
lv_mtext = 'Billing Item'(s28).
lv_ltext = 'Billing Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KSCHL'.
lv_position = lv_position + 1.
lv_stext = 'Condition Type'(s28).
lv_mtext = 'Condition Type'(s28).
lv_ltext = 'Condition Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KAWRT'.
lv_position = lv_position + 1.
lv_stext = 'Cond Base Value'(s28).
lv_mtext = 'Cond Base Value'(s28).
lv_ltext = 'Cond Base Value'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KBETR'.
lv_position = lv_position + 1.
lv_stext = 'Rate'(s28).
lv_mtext = 'Rate'(s28).
lv_ltext = 'Rate'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WAERS'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 43
lv_stext = 'Currency'(s28).
lv_mtext = 'Currency'(s28).
lv_ltext = 'Currency'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KPEIN'.
lv_position = lv_position + 1.
lv_stext = 'Cond Pricing Unit'(s28).
lv_mtext = 'Cond Pricing Unit'(s28).
lv_ltext = 'Cond Pricing Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KMEIN'.
lv_position = lv_position + 1.
lv_stext = 'Condition Unit'(s28).
lv_mtext = 'Condition Unit'(s28).
lv_ltext = 'Condition Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKIMG'.
lv_position = lv_position + 1.
lv_stext = 'Act Inv Qty'(s28).
lv_mtext = 'Act Inv Qty'(s28).
lv_ltext = 'Act inv Qty'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VRKME'.
lv_position = lv_position + 1.
lv_stext = 'Sales Unit'(s28).
lv_mtext = 'Sales Unit'(s28).
lv_ltext = 'Sales Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKLMG'.
lv_position = lv_position + 1.
lv_stext = 'Bill Qty in Stock Keeping'(s28).
lv_mtext = 'Bill Qty in Stock Keeping'(s28).
lv_ltext = 'Bill Qty in Stock Keeping'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NTGEW'.
lv_position = lv_position + 1.
lv_stext = 'Net Wt'(s28).
lv_mtext = 'Net Wt'(s28).
lv_ltext = 'Net Wt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BRGEW'.
lv_position = lv_position + 1.
lv_stext = 'Gross Wt'(s28).
lv_mtext = 'Gross Wt'(s28).
lv_ltext = 'Gross Wt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'GEWEI'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 44
lv_stext = 'Wt Unit'(s28).
lv_mtext = 'wt unit'(s28).
lv_ltext = 'Wt Unit'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'PRSDT'.
lv_position = lv_position + 1.
lv_stext = 'Pricing Dt'(s28).
lv_mtext = 'Pricing Dt'(s28).
lv_ltext = 'Pricing Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FBUDA'.
lv_position = lv_position + 1.
lv_stext = 'Service Rendered Dt'(s28).
lv_mtext = 'Service Rendered Dt'(s28).
lv_ltext = 'Service Rendered Dt'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'NETWR'.
lv_position = lv_position + 1.
lv_stext = 'Net Value'(s28).
lv_mtext = 'Net Value'(s28).
lv_ltext = 'Net Value'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGBEL'.
lv_position = lv_position + 1.
lv_stext = 'Refer Doc'(s28).
lv_mtext = 'Refer Doc'(s28).
lv_ltext = 'Refer Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGPOS'.
lv_position = lv_position + 1.
lv_stext = 'Refer Item'(s28).
lv_mtext = 'Refer Item'(s28).
lv_ltext = 'Refer Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VGTYP'.
lv_position = lv_position + 1.
lv_stext = 'Preceeding Doc Categ'(s28).
lv_mtext = 'Preceeding Doc Categ'(s28).
lv_ltext = 'Preceeding Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUBEL'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc'(s28).
lv_mtext = 'Sales Doc'(s28).
lv_ltext = 'Sales Doc'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'AUPOS'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 45
lv_stext = 'Sales Item'(s28).
lv_mtext = 'Sales Item'(s28).
lv_ltext = 'Sales Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATNR'.
lv_position = lv_position + 1.
lv_stext = 'Material'(s28).
lv_mtext = 'Material'(s28).
lv_ltext = 'Material'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'MATKL'.
lv_position = lv_position + 1.
lv_stext = 'Material Grp'(s28).
lv_mtext = 'Material Grp'(s28).
lv_ltext = 'Material Grp'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'PSTYV'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc Item Categ'(s28).
lv_mtext = 'Sales Doc Item Categ'(s28).
lv_ltext = 'Sales Doc Item Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'POSAR'.
lv_position = lv_position + 1.
lv_stext = 'Item Type'(s28).
lv_mtext = 'Item Type'(s28).
lv_ltext = 'Item Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SPART'.
lv_position = lv_position + 1.
lv_stext = 'Division'(s28).
lv_mtext = 'Division'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WERKS'.
lv_position = lv_position + 1.
lv_stext = 'Plant'(s28).
lv_mtext = 'Plant'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'SHKZG'.
lv_position = lv_position + 1.
lv_stext = 'Returns Item'(s28).
lv_mtext = 'Returns Item'(s28).
lv_ltext = 'Returns Item'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'WAVWR'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 46
lv_stext = 'Cost'(s28).
lv_mtext = 'Cost'(s28).
lv_ltext = 'Cost'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI1'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 1'(s28).
lv_mtext = 'Sub Total 1'(s28).
lv_ltext = 'Sub Total 1'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI2'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 2'(s28).
lv_mtext = 'Sub Total 2'(s28).
lv_ltext = 'Sub Total 2'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI3'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 3'(s28).
lv_mtext = 'Sub Total 3'(s28).
lv_ltext = 'Sub Total 3'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI4'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 4'(s28).
lv_mtext = 'Sub Total 4'(s28).
lv_ltext = 'Sub Total 4'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI5'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 5'(s28).
lv_mtext = 'Sub Total 5'(s28).
lv_ltext = 'Sub Total 5'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KZWI6'.
lv_position = lv_position + 1.
lv_stext = 'Sub Total 6'(s28).
lv_mtext = 'Sub Total 6'(s28).
lv_ltext = 'Sub Total 6'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKART'.
lv_position = lv_position + 1.
lv_stext = 'Billing Type'(s28).
lv_mtext = 'Billing Type'(s28).
lv_ltext = 'Billing Type'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKTYP'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 47
lv_stext = 'Billing Categ'(s28).
lv_mtext = 'Billing Categ'(s28).
lv_ltext = 'Billing Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VBTYP'.
lv_position = lv_position + 1.
lv_stext = 'Sales Doc categ'(s28).
lv_mtext = 'Sales Doc Categ'(s28).
lv_ltext = 'Sales Doc Categ'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VKORG'.
lv_position = lv_position + 1.
lv_stext = 'Sales Org'(s28).
lv_mtext = 'Sales Org'(s28).
lv_ltext = 'Sales Org'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VTWEG'.
lv_position = lv_position + 1.
lv_stext = 'Dist Chan'(s28).
lv_mtext = 'Dist Chan'(s28).
lv_ltext = 'Dist Chan'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'VSBED'.
lv_position = lv_position + 1.
lv_stext = 'Ship Cond'(s28).
lv_mtext = 'Ship Cond'(s28).
lv_ltext = 'Ship Cond'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'FKDAT'.
lv_position = lv_position + 1.
lv_stext = 'Billing Date'(s28).
lv_mtext = 'Billing Date'(s28).
lv_ltext = 'Billing Date'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BUKRS'.
lv_position = lv_position + 1.
lv_stext = 'Comp Code'(s28).
lv_mtext = 'Comp Code'(s28).
lv_ltext = ''(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'ERDAT'.
lv_position = lv_position + 1.
lv_stext = 'Created On'(s28).
lv_mtext = 'Created On'(s28).
lv_ltext = 'Created On'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNRG'.
lv_position = lv_position + 1.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 48
lv_stext = 'Sold To'(s28).
lv_mtext = 'Sold To'(s28).
lv_ltext = 'Sold To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'KUNAG'.
lv_position = lv_position + 1.
lv_stext = 'Ship To'(s28).
lv_mtext = 'Ship To'(s28).
lv_ltext = 'Ship To'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Specify the Columnn name and position to be place in the ALV output.
lv_colname = 'BSTNK_VF'.
lv_position = lv_position + 1.
lv_stext = 'Cust PO No'(s28).
lv_mtext = 'Cust PO No'(s28).
lv_ltext = 'Cust PO No'(s29).
PERFORM f_setcolumn_name USING lv_colname lv_position lv_stext lv_mtext lv_ltext.
* Display the Header information.
CALL METHOD gr_table->set_top_of_list
EXPORTING
value = ls_rows.
* Getting the All columns names
gr_columns = gr_table->get_columns( ).
gr_functions = gr_table->get_functions( ).
gr_functions->set_all( abap_true ).
* To addd the sort functionality
gr_sorts = gr_table->get_sorts( ).
* gr_sorts->add_sort( columnname = 'VBELN'(s27) subtotal = abap_true ).
* gr_sorts->add_sort( columnname = 'POSNR'(s30) subtotal = abap_true ).
gr_agg = gr_table->get_aggregations( ).
gr_agg->add_aggregation( 'NETWR'(s63) ).
gr_agg->add_aggregation( 'WAVWR'(s55) ).
gr_agg->add_aggregation( 'FKIMG'(s57) ).
gr_agg->add_aggregation( 'KZWI1'(s57) ).
gr_agg->add_aggregation( 'KZWI2'(s57) ).
gr_agg->add_aggregation( 'KZWI3'(s57) ).
gr_agg->add_aggregation( 'KZWI4'(s57) ).
gr_agg->add_aggregation( 'KZWI5'(s57) ).
gr_agg->add_aggregation( 'KZWI6'(s57) ).
*Display output table.
gr_table->display( ).
*&---------------------------------------------------------------------*
*& Form F_SETCOLUMN_NAME
*&---------------------------------------------------------------------*
* Display the column according to the report output
*----------------------------------------------------------------------*
FORM f_setcolumn_name USING pu_colname TYPE lvc_fname " Field Name
pu_position TYPE i " Position
pu_lv_stext TYPE scrtext_s " Short Text
pu_lv_mtext TYPE scrtext_m " Medium Text
pu_lv_ltext TYPE scrtext_l. " Short Text
TRY.
* get the required column details to GR_COLUMN.
gr_column = gr_columns->get_column( pu_colname ).
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 49
* Short Text for column.
gr_column->set_short_text( pu_lv_stext ).
* Medium Text for column.
gr_column->set_medium_text( pu_lv_mtext ).
* Long Text for column.
gr_column->set_long_text( pu_lv_ltext ).
* Setting Column name and position.
gr_columns->set_column_position(
columnname = pu_colname
position = pu_position ).
CATCH cx_salv_not_found. "#EC
ENDTRY.
* clearing the variable used in the perform .
CLEAR: pu_colname,pu_lv_stext,pu_lv_mtext,pu_lv_ltext.
ENDFORM. " F_SETCOLUMN_NAME
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 50
Related Content
BW Data Modeling
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Query Design
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
For more information, visit the Business Intelligence homepage.
Step by Step Procedure for Reconciliation of Sales Data in SAP BW Environment with ECC Environment
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 51
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

------------------------------------------------------------------------------------

RSBERRORLOG Table performance problem
RSBM_ERRORLOG_DELETE. If you are running on oracle please run a online reorg on rsberrorlog.

1144400-RSBM_ERRORLOG_DELETE no frequent commits.
1095924-Correction: Deletion/analyis report for error handlign logs.

If you are on SAP_BW 701 above notes are not applicable ... you can go ahead and run report (RSBM_ERRORLOG_DELETE).

------------------------------------------------------------------------
ECC application tables which may potentially grow rapidly and then they may cause problems. I mentioned in there some tables from other SAP solutions like CRM, SCM, MDM, APO, PI, etc. In today’s post I would like to focus on BW big tables.
• BW statistics data: RSDDSTATAGGR, RSDDSTATAGGRDEF, RSDDSTATCOND, RSDDSTATDELE, RSDDSTATDM, RSDDSTATEVDATA, RSDDSTATHEADER, RSDDSTATINFO, RSDDSTATLOGGING
• PSA error logs: RSERRORHEAD, RSERRORLOG
• BW staging engine tables: RSMONMESS, RSSELDONE
• BW workbook tables: RSRWBSTORE
• Temporary BW tables: /BI0/0*
• RSBMNODES – “Hierarchical Log: Nodes”; If e.g. it takes a long time to set a DTP request to 'green' after it has been processed it is caused by large volume of data in this table. Since BI system in production a quite long time you got a lot of logs in it then you have a huge amount of entries in this table.
• RSBERRORLOG (Logs for Incorrect Records) – stores error handling logs due to following and other reasons:
• Warnings that are created during master data uploads for duplicate records
• Single record error messages in customer-specific transformation routines

Table is accumulated a numerous error messages records for a DTP requests. In most cases this is due to many errors while BW is processing data and InfoPackage (IP) or Data Transfer Package (DTP) is setup in way that every data duplicity needs to be recorded.

LO COCKPIT

2011-02-12T16:10:00.000-08:00

Gist of LO Cockpit Delta
Happy Tony
Business Card
Company: Tata Consultancy Services Ltd
Posted on Nov. 24, 2006 09:34 PM in Beginner, Enterprise Data Warehousing/Business Warehouse, SAP Business One, SAP NetWeaver Platform

Subscribe. Subscribe
Print. Print
Permalink Permalink
Share
Share
Objective: In this Blog I would like to bring your attention to an excellent piece of work by Glenn Cheung and Ramond Leenders of www.vnsg.nl which will give a crash understanding of the LO cockpit. I will be covering the delta mechanism explained in the presentation and there by direct you to this masterpiece.

Before starting the matter, I sincerely apologize for not working in the correct way with the material in my previous posting of this blog, that was not original. I admit that I have made the mistake of not giving credit to the author. I thank Vitaliy for pointing this and SDN community for giving me an opportunity to correct it.

1. Positioning of LO Cockpit extraction

image

2. How the data flow from OLTP to BW system

image

Transaction postings lead to:

1. Records in transaction tables
2. For an initial load a setup needs to be executed which reads the transaction data and stores the data in a setup table
3. These setup tables are read during an initial or full load
4. Further transactions are posted into the transaction tables and also caught into Update tables / Extraction Queue.
5. A periodically scheduled job transfers these postings into the BW delta queue
6. This BW Delta queue is read when a delta load is executed.

3. The Update Modes

a. < 2002.1: (Serialized) V3 Update
b. Direct Delta
c. Queued Delta
d. Un-serialized V3 Update

Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.

a. Update methods: (serialized) V3

• Transaction data is collected in the R/3 update tables
• Data in the update tables is transferred through a periodic update process to BW Delta queue
• Delta loads from BW retrieve the data from this BW Delta queue

image

Transaction postings lead to:

1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.

Issues:

• Even though it says serialized , Correct sequence of extraction data cannot be guaranteed
• V2 Update errors can lead to V3 updates never to be processed
• Details in SAP Note 505700

b. Update methods: direct delta

• Each document posting is directly transferred into the BW delta queue
• Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues

image

Transaction postings lead to:

1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.

Pros:

• Extraction is independent of V2 update
• Less monitoring overhead of update data or extraction queue

Cons:

• Not suitable for environments with high number of document changes
• Setup and delta initialization have to be executed successfully before document postings are resumed
• V1 is more heavily burdened

Note: Con 2: a delta queue has to present to collect the document postings. This queue is only available after a successful delta initialization.

c. Update methods: queued delta

• Extraction data is collected for the affected application in an extraction queue
• Collective run as usual for transferring data into the BW delta queue

image

Transaction postings lead to:

1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.

Pros:

• Extraction is independent of V2 update
• Suitable for environments with high number of document changes
• Writing to extraction queue is within V1-update: this ensures correct serialization
• Downtime is reduced to running the setup

Cons:

• V1 is more heavily burdened compared to V3
• Administrative overhead of extraction queue

d. Update methods: Un-serialized V3

• Extraction data for written as before into the update tables with a V3 update module
• V3 collective run transfers the data to BW Delta queue
• In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables

Note: i. Pro 2: In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.
ii. Pro 4: Even without a successful initial load and thus no BW delta queue yet available, document postings are already collected in the extraction queue.

image

Transaction postings lead to:

1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3.This BW Delta queue is read when a delta load is executed.

Issues:

• Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
• V2 update has to be successful

Note: Issue 1: Each Material Movement delivers a new Material Document, so no problem when updating into ODS/Cube.

Source:http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4972

SAP JOB MONITORING

2010-12-13T00:52:00.001-08:00

SAP ABAP Background jobs: Managing

SAP provides a Central Area (single screen), to manage all sorts of Background Job related issues, which are as follows:

·         Monitoring and managing jobs

·         Defining Jobs

·         Scheduling, rescheduling and copying existing jobs

·         Editing and Rescheduling of Jobs and job steps

·         Repeating a job

·         Debugging an active job

·         Reviewing information about a job

·         Cancelling a job’s release status

·         Cancelling and deleting jobs

·         Comparing the specification of different jobs

·         Checking the status of jobs

·         Reviewing job logs

·         Releasing a job to run

To handle above mentioned things, we need to follow certain procedures.

For specifying jobs:

1.     To specify job, we need to open “Job Overview Screen”. For that, either we need to choose CCMS Jobs Maintenance or to call SM37. SAP system first shows Select Background Jobs screen, where we have to select criteria for the jobs, we want to manage, and of which some criteria’s are mandatory or required fields. These criteria include:

o    Job name – Required ( here we can use a wildcard() to get a range of similar job names )*

o    Name of the user who scheduled the job – Required (here also we can use wildcard )

o    Job Status

o    Planned or actual start time

o    Job start condition or event linked to start condition

o    Job step

o    Periodicity of job

2.     We can also choose Extended Job Selection, where we pin point our criteria regarding selection of exact job. An administrator of Authorizing for Background Processing can display Jobs in all clients. Without authorization, only jobs in current client will be displayed.

3.     Now we choose. Execute.

Managing and Monitoring Jobs:

After selecting the job which we want to manage, we can choose various management tasks as described in following part

·         To copy a single existing job – choose Job Copy

·         To reschedule or edit job steps or attributes of a single job — choose Job Change.
A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows displaying ABAP programs and variants. We can scan a program for syntax errors. We can also display the authorizations for an authorized user of an ABAP job step.

·         To repeat a single job — choose Job Repeat scheduling.

·         To debug an active job — choose Job Capture: active job.
Here, only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), we can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
Note : we will be able to capture a background job only if we are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and marks the job, then choose Job – Job details.

·         To review information about a job — choose Job – Job details. Details displayed can include:

o    current

o    job status

o    periodicity, or the repetition interval other jobs linked to the current job, either as previous or subsequent jobs

o    defined

o    job steps spool requests generated by the current job

·         To cancel a job’s “Released” status, select the job or jobs from the Job Overview list and choose Job Release -> Scheduled.

·         To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job – Cancel active job.

·         To delete a job entirely, select the job or jobs from the Job Overview list and choose Job – Delete. Jobs with the status of Ready or Running cannot be deleted.

·         To compare the specifications of more than one job, select the jobs from the Job Overview list and then choose Job – Compare jobs.

·         To check the status of jobs, we select the job or jobs from the Overview Job list and then choose Job – Check status. This allows us to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.

·         To review job logs, we will select a job or jobs with the status Completed or Canceled from the Job Overview list and then choose Goto – Job log.

·         To release a job so it can run, first we select a job from the Job Overview list and choose Goto – Release

BI Boxnet RSS

2010-03-06T03:44:00.000-08:00

SAP BP

2009-12-23T04:45:00.000-08:00

BP

http://www.element61.be/e/compete.asp?ServiceId=41

http://examples.idashboards.com/idashboards/?guestuser=wpman1

http://www.sap.com/services/pdf/BWP_SAP_Best_Practices_for_Business_Intelligence.pdf

http://www.tli-usa.com/download/Track1_session8.pdf

Modelling

2009-12-23T04:11:00.000-08:00

Transformations

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/dc43c445-0d01-0010-23a1-ca348ff5f975?QuickLink=index&overridelayout=true

SAP BI Content

2009-12-23T04:00:00.000-08:00

BI 7 Business content latest link - for all areas:
http://help.sap.com/saphelp_nw70/helpdata/en/3d/5fb13cd0500255e10000000a114084/frameset.htm
BI 7 HR Business content:
http://help.sap.com/saphelp_nw2004s/helpdata/en/26/77eb3cad744026e10000000a11405a/frameset.htm
BI 7 Financials Business Content:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c9/fe943b2bcbd11ee10000000a114084/frameset.htm
BI 7 SCM Business Content:
http://help.sap.com/saphelp_nw70/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm

SAP BI Reporting

2009-12-16T23:57:00.000-08:00

GL Reporting

What is SAP Recommendation to use 0FI_GL_14 (Line Item) and 0FI_GL_10(Summary).

0FL_GI_14 is a delta-enabled DataSource that extracts the general ledger line items for only one ledger, the one that's defined as the 'leading ledger' in your source system. All other ledgers, if you require that data, would require separate DataSources be created for each ledger. These would be named 3FI_GL_XX_SI, where XX would be replaced with the ledger name.

0FI_GL_10 is a delta-enabled DataSource that extracts the general ledger balances for only the defined 'leading ledger' in your source system. All other ledgers, again if required, would require separate DataSources be created for each ledger. These would be named 3FI_GL_XX_TT, where XX would be replaced with the ledger name. This would be the most appropriate DataSource for your Balance Sheet and Income Statement (P&L) reporting requirements, if you only use one ledger. If you have more than one ledger, you can still use this and add the 3FI_GL_XX_TT DataSources. These would then be integrated into one InfoCube for reporting.

Are there any other difference between the 0FI_GL_14/10 and 0FI_GL_20/40/50?

Yes, there are differences between these DataSources:

0FI_GL_10 - Extracts general ledger balances for only the 'leading ledger'

0FI_GL_14 - Extracts general ledger line items for only the 'leading ledger'

0FI_GL_20 - Extracts account activity for all ledgers

0FI_GL_21 - Extracts account accumulated activity, for each Fiscal Year/Period, for all ledgers

0FI_GL_40 - Extracts general ledger line items for all ledgers. It differs also from 0FI_GL_14 in that it pulls from more tables.

0FI_GL_50 - Extracts general ledger planned line items for all ledgers.

- If you have SAP ECC 6.0 EhP 3 or higher, is it required to use the new datasources?

It is not a requirement to use the New GL Reporting DataSources, per se. If your FI functional consultant(s) haven't configured your environment to use this new functionality, there won't be any data to extract using the new DataSources and therefore the old DataSources would still be pertinent.

- What are the main differences between the new and the old flows?

The New GL Reporting functionality in ECC6 EHP3 and beyond provides for the posting of not only business financial transactions (as it always has) but also provides for settlement of internal document postings associated with managerial accounting concepts. It also provides the ability to manage multiple ledgers for different accounting principles, integrates financial and managerial accounting reporting (as eluded to previously), provides for segemented reporting to meet requirements for International Financial Reporting Standards (IFRS) and US Generally Accepted Accounting Principles (GAAP) and Cost of Goods Sold accounting.

As of Plug-In 2002.2, it is no longer necessary to have DataSources linked. This means that you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4, and 0FI_TX_4 in any order. You also have the option of using DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).

- Can you use them simultanously?

I'm not sure that there's any process that would preclude you from executing both the New GL Reporting DataSources and the older ones, but if your ECC environment is configured for the New GL Reporting, I'm not sure that you'd want to execute the old DataSources (not sure if you'd get duplication of data or something worse if you tried).

As of Plug-In 2002.2, it is no longer necessary to have DataSources linked. This means that you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4, and 0FI_TX_4 in any order. You also have the option of using DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).

Recommended as the DSO keys, :

if yu also have the option of using DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).

Recommended as the DSO keys, :

if you require a DSO in between 0FI_GL_20 and 0FIGL_C20:

InfoObject (DataSource Field)

0VERSION (RVERS)

0COMP_CODE (RBUKRS)

0FISCPER (FISCPER)

0CHRT_ACCTS (CHARTACCTS)

0GL_ACCOUNT (RACCT)

0FUNC_AREA (RFAREA

0COSTCENTER (RCNTR

0VTYPE (VALUETYPE

0PROFIT_CTR (PRCTR)

0SEGMENT (SEGMENT)

0FISCVARNT (FISCVAR)

0CURTYPE (CURTYPE)

0VALUATION (VALUTYPE)

0CURKEY_TC (RTCUR)

0UNIT (CURRUNIT)

OSS note 1002272.

Try creating a new doc and check if the table 0BWFIAEDAT gets updated

I had a situation where there was no delta coming into BWFI_AEDA2. I had to regenerate some GL Structures using program RGZZGLUX. I referred to notes:619454 last section and also 656431. I am not sure whether it is pertinent in your case but you might want to check these notes out.

FI GL/AP/AR help

For this 0FI_GL_4 Datsource CI_BSIS included is provided by SAP, also for enhancement purpose. You will see that no matter what fields you add into this include, as long as the field is in table BKPF or BSEG, you won't need any code to fill in data for that field.

However, if the field you want to add is not in BKPF or BSEG, you will need to add an append structure and then code accordingly as per normal.

For 0fi_gl_4 extractor we got 2 Includes and 1 append by sap

INCLUDE CI_BSIS CI_BSIS

Fields:

BKTXT

GLVOR

PERNR

INCLUDE DTFIGL_WF Extraction Structure: GL Work Fields

Fields:

AWTYP

AWKEY

BSTAT

DMBTR

Append Structure Predefined:

AGTR_FIGL_4 Grantor Management: additional fields for extraction

For this datasource, CI_BSIS included is provided by SAP, also for enhancement purpose. You will see that no matter what fields you add into this include, as long as the field is in table BKPF or BSEG, you won't need any code to fill in data for that field.

However, if the field you want to add is not in BKPF or BSEG, you will need to add an append structure and then code accordingly as per normal.

If you are on ECC 6.0 then confirm with the Fi Consultant if the New GL concept has been activated, If so you can make use of the DS 0FI_GL_10, 0FI_GL_14(If you are on EHP3). You can also use 0FI_GL_4 instead of 0FI_GL_14 if you are not on EhP3.

If you are still on the Old GL concept then activate 0FI_GL_4 and 0FI_GL_6.

Old GL: http://help.sap.com/saphelp_nw70/helpdata/en/30/44593167d447198995bed770d70ddf/frameset.htm

NewGL: http://help.sap.com/saphelp_nw2004s/helpdata/en/be/928f40f5767d17e10000000a1550b0/frameset.htm

Financial Accounting: Procedure for Line Item Extraction Locate the document in its SAP Library structure

General Comments on Extraction Procedure

The consistent data extraction in the delta procedure is possible for line items from General Ledger Accounting (FI-GL) and selected subledgers (Accounts Receivable (FI-AR) and Accounts Payable (FI-AP)) and tax reporting with effect from SAP BW 3.1 Content. The extraction procedure delivered with the business content for SAP BW 2.0B, which is based on the DataSources 0FI_AR_3 and 0FI_AP_3, can be replaced. This is described in note 410797.

The decisive advantage of choosing R/3 line item tables as the data source is that additional fields can be transferred to the BW. These are not available for the transaction figures. This provides more extensive and flexible analysis options in BW.

To enter a consistent delta dataset, you can use any of the following InfoSources (with the corresponding DataSources and extractors in SAP R/3):

Application

InfoSource

Name

FI-GL

0FI_GL_4

General ledger: Line Items

FI-AP

0FI_AP_4

Accounts payable: Line Items

FI-AR

0FI_AR_4

Accounts receivable: Line Items

FI-TX

0FI_TAX_4

General ledger: Data for taxes on sales and purchases

For the General Ledger, selection is made from the tables BKPF and BSEG, while selection for the subledgers is made from tables BSID/BSAD (Accounts Receivable) and BSIK/BSAK (Accounts Payable). InfoSource 0FI_GL_4 transfers only those fields that are relevant for General Ledger Accounting from the Financial Accounting document (tables BKPF and BSEG) to the BW system.

The consistent recording of data from General Ledger Accounting and Subledger Accounting is provided by means of coupled delta extraction in the time stamp procedure. General ledger accounting is the main process in delta mode and provides subsidiary ledger extraction with time stamp information (time intervals of previously selected general ledger line items). This time stamp information can also be used for a loading history: this shows which line items have previously been extracted from the SAP R/3 system.

Delta Method

Delta extraction enables you to load into BW only that data that has been added or has changed since the last extraction event. Data that has already been loaded and has not changed is not extracted and does not need to be deleted before a new load. This improves performance compared with periodic extraction of the entire dataset.

Financial Accounting line items are read by extractors directly from the tables in SAP R/3. A time stamp on the line items serves to identify the status of the delta data. Time stamp intervals that have already been read are stored in a time stamp table. The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).

The Financial Accounting line items are extracted from SAP R/3 in their most recent status (after-image delta method). This delta procedure is not suitable for filling InfoCubes in BW directly. Therefore, firstly, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes, ODS objects) can be provided with data from this ODS object.

If the ODS object permits BEx Reporting, queries can be defined directly there.

Time Stamp Method

With Financial Accounting line items that have been posted in SAP R/3 since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT).

When a delta dataset has been selected successfully, SAP R/3 logs two time stamps that delimit a selection interval for a DataSource in table BWOM2_TIMEST:

he foll are the settings in my settings table. FYI

BWFILOWLIM 19910101

ABAP - BW

2009-12-15T23:11:00.000-08:00

Start Routine:
The start routine is run for each data package at the start of the transformation. The start routine has a table in the format of the source structure as input and output parameters. It is used to perform preliminary calculations and store these in a global data structure or in a table. This structure or table can be accessed from other routines. You can modify or delete data in the data package.

Routine for Key Figures or Characteristics:
This routine is available as a rule type; you can define the routine as a transformation rule for a key figure or a characteristic. The input and output values depend on the selected field in the transformation rule. More information: the Routine section under

End Routine:
An end routine is a routine with a table in the target structure format as input and output parameters. You can use an end routine to postprocess data after transformation on a package-by-package basis. For example, you can delete records that are not to be updated, or perform data checks.

Expert Routine:
This type of routine is only intended for use in special cases. You can use the expert routine if there are not sufficient functions to perform a transformation. The expert routine should be used as an interim solution until the necessary functions are available in the standard routine.

ABAP-BW WIKI LINKS
https://wiki.sdn.sap.com/wiki/display/BI/ABAP+in+BW
https://wiki.sdn.sap.com/wiki/display/BI/ABAP+in+BW
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=35458
http://wiki.sdn.sap.com/wiki/display/BI/Useful+functions+for+Data+Transformation

Datasources Enhancement

LO Datasource
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0af763b-066e-2910-a784-dc6731660f46?QuickLink=index&overridelayout=true
******************************************************************************
*&---------------------------------------------------------------------*

*& Report ZBI_ACTIVATE_TRANSFORMATION

*&

*&---------------------------------------------------------------------*

*&

*&

*&---------------------------------------------------------------------*

REPORT zbi_activate_transformation.

TYPES: t_tran TYPE rstran,

i_tran TYPE STANDARD TABLE OF t_tran.

DATA: r_tran_maintain TYPE REF TO cl_rstran_maintain,

lv_subrc TYPE sy-subrc,

lv_output(255) TYPE c,

tab_tran TYPE i_tran,

i_s_source TYPE rstran_s_tlogo,

i_s_target TYPE rstran_s_tlogo.

SELECTION-SCREEN BEGIN OF BLOCK b1.

SELECTION-SCREEN SKIP 1.

PARAMETERS: p_id TYPE char35.

SELECTION-SCREEN END OF BLOCK b1.

START-OF-SELECTION.

FIELD-SYMBOLS: TYPE t_tran.

REFRESH tab_tran.

SELECT * FROM rstran INTO TABLE tab_tran WHERE tranid = p_id

AND objvers = 'A'

AND objstat = 'INA'.

SORT tab_tran.

IF tab_tran IS NOT INITIAL.

LOOP AT tab_tran ASSIGNING .

TRY.

CREATE OBJECT r_tran_maintain

EXPORTING

i_tranid = -tranid

i_s_source = i_s_source

i_s_target = i_s_target

i_expert = rs_c_false

i_mode = rsawc_c_tfc-display

i_with_message = rs_c_true.

CATCH cx_rstran_not_found .

CATCH cx_rstran_input_invalid .

CATCH cx_rstran_cancelled .

CATCH cx_rstran_not_authorized .

CATCH cx_rstran_display_only .

CATCH cx_rstran_already_exist .

CATCH cx_rstran_error_with_message.

ENDTRY.

CALL METHOD r_tran_maintain->check

EXPORTING

i_with_display = rs_c_true

IMPORTING

e_subrc = lv_subrc.

IF lv_subrc = 0.

CONCATENATE 'Activated Transformation : '

-tranid

' : '

-sourcename

'->' -targetname INTO lv_output.

ELSE.

CONCATENATE 'Transformation : '

-tranid

' : '

-sourcename

'->'

-targetname

'Could Not be Activated' INTO lv_output.

ENDIF.

IF lv_subrc = 0.

TRY.

CALL METHOD r_tran_maintain->execute

EXPORTING

i_wrkmode = cl_rstran_stat=>wrkmode_activate

IMPORTING

e_subrc = lv_subrc.

CATCH cx_rstran_cancelled .

CATCH cx_rstran_error_with_message .

CATCH cx_rstran_display_only .

ENDTRY.

ENDIF.

WRITE:/ lv_output.

ENDLOOP.

ELSE.

WRITE:/ 'Transformation is not Inactive'.

ENDIF.

*****************************************************************************

Five Ways to Enhance BI Functionality Using ABAP--Part V--ABAP in Process Chain

http://wiki.sdn.sap.com/wiki/display/BI/Five+Ways+to+Enhance+BI+Functionality+Using+ABAP--Part+V--ABAP+in+Process+Chain?bc=true

SAP BI IP

2009-12-15T22:48:00.000-08:00

A filter’s functionality depends on its particular use in either a planning function or a query.
In connection with planning functions, a filter in the characteristic restrictions describes the data that is
used for executing a planning function. Selections in the default values are

You can also use a key date for the filter to determine time-dependent selections.

The values defined in a query’s characteristic restrictions limit the volume of data that is available for
further filtering during a query’s runtime. It is then no longer possible to filter using a characteristic
value outside this value set. The default values determine the query’s initial filter state.
The settings & essentially refer to the use of filters with a
query:
determines whether the selection of values affected by the characteristic
restrictions can be changed when the query is executed. This setting is a prerequisite for the
definition of default values for a characteristic.
· If you select the option to
specify that only a single value can be used for filtering the query.
_ The two functionalities described above are described in more detail in the following units.

*********************************************************************************

Data: h_clean(3),
h_check,
h_off(2) type p.

h_clean = SOURCE_FIELDS-INCO1.
translate h_clean to upper case.

clear h_off.
do 3 times.
* (*****Loop number of times the length of the info object).
move h_clean+h_off(1) to h_check.
* if not h_check ca '1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÜ-'.
if not h_check ca '1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZÖÜ-'.

move space to h_clean+h_off(1).
endif.
add 1 to h_off.
enddo.

* result value of the routine
RESULT = h_clean.