EXPORT ��1�� TO MEMORY ID ��ZP10PSEX011TEST��.
IMPORT FLAG FROM MEMORY ID ��ZP10PSEX011TEST��.

����FLAG��û�б���Ϊ1���﷨��û�б�����˵�����Ӧ���dzɹ��ģ���Ϊʲôû�гɹ��أ�

ԭ���ǣ�MEMORY ID�����������д����Ӧ���Dz���ͬ���ģ�����1����FLAG��Ȼ��ͬ��������û�гɹ����յ�ֵ�������д��P1 = 1�IJ�����ʽ�򲻻������������ƣ����磺1����EXPORT FLAGTO MEMORY ID ��ZP10PSEX011TEST��.
IMPORT FLAG FROM MEMORY ID ��ZP10PSEX011TEST��.

2����EXPORT P1 = ��1�� TO MEMORY ID ��ZP10PSEX011TEST��.
IMPORT P1 = FLAG FROM MEMORY ID ��ZP10PSEX011TEST��.

SAP: ABAP will live on, but new skill focus required

1. Some developers have remarked that it seems SAP is moving away from classic ABAP development and going toward true object orientation. What does the future hold for ABAP versus OO?

Mario Herger: First off, the majority of SAP code around is still ABAP. However, what we��re seeing today is a need to expand beyond pure ABAP, which is why SAP opened up to Java a few years ago. The Java world is very different from what we used to have and offers many advantages. We have our own J2EE engine in place and we��re working with Eclipse to facilitate OO development in SAP. Meanwhile, ABAP is more than 10 years old and has the benefit of being a proven technology.

For those concerned about ABAP��s future, I want to make it very clear that ABAP will live on. The majority of current SAP development going on is still done in ABAP, and there are tremendous investments made in ABAP.

So rather than viewing an either/or proposition, think of it as merely opening up for other technologies. What we see today is something of an equalization process where ABAP and Java are used in a complementary way. You can use either approach for pretty much anything, and SAP provides the platform and the tools to make it come together seamlessly.

2. What new development tools are on the horizon?Herger: We��re going into an era of model-driven development. Increasingly, the question is: Are we still going to hand-code everything, or can we automatically generate most of the code? In other words, the focus is going away from directly coding every tedious call by hand and instead focusing on the pieces that are really interesting.

With that in mind, I see two big things in terms of development tools that should be of particular interest. First, there is a new, browser-based tool called Visual Composer. This product allows for building models in a graphical way by drag-and-drop, drawing lines and so forth. You can build from an analytical dashboard with a BW connection, creating complete transactions right there on screen.

I mentioned Eclipse earlier; it��s a development environment for Java that is very similar to the ABAP workbench. On top of that, we have the composite application framework, a modeling tool that supports building applications in that it generates most of the code while letting you focus on the last 10% of fine-tuning.

3. Speaking of Eclipse, will ABAP development be possible in Eclipse?Herger: At the moment, I don��t see that happening. The ABAP workbench is very strong and there isn��t much reason to move it to Eclipse. Bear in mind, the ABAP Workbench has the advantage of having had over a decade to evolve.

The only scenario where I see ABAP in Eclipse is as a result of an increasingly model-driven development world. ABAP code may be generated out of other tools, but I believe the ABAP Workbench will stay where it is for the foreseeable future.

4. Remote function calls (RFC)/BAPI support seems to be dwindling. Is SAP moving away from providing business objects with supporting BAPIs?Herger: SAP will, of course, continue to support existing BAPIs, though we actively try to cut bloated BAPIs to the right size whenever possible and make them ESA compliant. When you��re talking about developing new BAPIs and RFCs, the focus today is on making sure they are ESA compliant.

5. Will SAP Java Connector (JCo) become fully compliant with the J2EE Connector Architecture standards?Herger: Normally, SAP tends to offer a richer set of functionality than what is in the standard. But we are aware that JCo isn��t J2EE Connector Architecture standard compliant today. SAP is working on JCo to make it more compliant, but I can��t make any guarantees as to the extent, nor can I give you a timeline for when -- or if - it will become 100% JCA compliant.

6. What skills should ABAP developers focus on to stay competitive?Herger: Look beyond the home system and focus on the technologies that allow you to talk to other systems and applications. That means mastering SAP Exchange Infrastructure (XI,) getting practical experience with Web Services and staying on top of integration technologies like Web Dynpro.

The applications we��ll see in the future are primarily composite applications. Your system will talk to other systems; your data will come from somewhere else. To stay competitive, you need to learn how to seamlessly integrate with others. That doesn��t mean just being able to tap someone else��s data; it also means opening up your own system to the other party as well.

1. User create Quotation for a FG using MTO scenario, the dependent requirement for all component in the FG's BOM is also MTO using the quotation's number as account assignment. [standard function]

2. User create Sales Order with reference to the Quotation, which originally bring the Quotation's FG to the SO, which is still using the quotation's number as account assignment. [standard function]

3 (key point). Then user can change the copied sales order item to another FG (which share most of the same BOM as the FG in the quotation) or change the whole sales order to another customer

4 (key point). We expect the account assignment in Sales order item will retain as the "quotation's number".

5. If ok, the dependent requirement for all component in the Sales order's FG will be the same the Quotation's FG as they share the same account assignment.

��Ұ�æ��������������ڵ�3���͵�4��ʱ�ܷ�ʵ�ֲ�����

��Ͷ��˵Ľ�����Ϊ��Ҫ���ִ�����ѧ���о����������ڿո�ʱ������Ѫ��ˮƽΪ80-120���ˣ�100����Ѫ�����Ѫ��ˮƽ���ͣ����е�������ƣ������������ͷ�Σ�վ�����Ȼ��ļ¡�����Ѫ��ˮƽ��ά�֣���Ҫȡ����һ�쵱�е�һ�͵Ľ�ʳ�����������������ͣ��ͺ���ά������������Ѫ��ˮƽ���ͻ���ֵ�Ѫ�ǣ�ֱ��Ӱ�칤����ѧϰ�����塣ͬʱ������־��������С���Ӧ�������Ӧ�����½��������߿ɳ������ѡ���Ѫ�ǻ��Եȡ�
����

������Ͳ��ԣ�ǰһ���������ڶ���������͵�ʱ��̫�������м�θҺ�����صķ��ڽ�ʧȥƽ�⣬��������ƫʳ��ƫʳ�Խ�������������Ӱ�졣

������Щ��Ϊ�˼��ʶ����������Ҳ�Ǵ���ġ�ʵ���ϣ��ٳ�һ��Ҳ�����˷ʡ���Ϊ�˰��������޶ȵģ����Ŷ��ӽ���ͷ�����Եø��ࡣ

�������һ��Ҫ�ԣ���Ϊ�糿θҺ�ķ��ڲ�����ʢ��θ��Ҳû���κ�ʳ���ʱ��������ǿ�������Ƕ�ά���غͿ����ʵ�������һ������õ�ʱ�̡���Ϳ�������������ȡ�����ʣ�����Ǽ��ʵ�ԭ��Ҳ�ǽ���֮����

��������������͵��ˣ��ڳ�ʱ��ո���������̻��ʵس���ͣ������׷�����ʣ������ص�ʳ������֢���ո���ʱ�����������Һ�ķ��ھͻ���٣���ɹ����ϰ�����Ҳ������θ��������Ҫԭ��

�����ڹ��⣬�������һ��������Ҫ��һ�ٷ������ÿ�ճ�һ�ٷḻ����ͣ���ʹ�㳤�١����Ǽ��ݴ�ѧ�����һ�ε����з��ֵġ���7000������׷�ٵ������Ů�У�����ϰ�߲�����͵��˵������ʽ�֮������߸�40%�����⣬���ս�˹��ѧ��һ������80-90������Ϊ����ĵ����з��֣����dz��ٵ�Ψһ��ͬ����--ÿ���ֳ�һ�ٷḻ����͡�

�����о��������������ڲ������ʱ���ر��������겻����ͣ���ֱ��Ӱ������ˮƽ����ѧ������8-13�������ͯ��������������������Ĺ�ϵ�����о����֣��Ըߵ�������͵ĺ��������̵�ƽ���÷���ߣ����Ϊ�Ը��Ƿ���͵ĺ��ӣ���������͵ĺ������̵÷���͡��ɴ�˵�������ڴ������������׶ε������ͯ������Ҫ��ʱ����ͣ�ͬʱ��Ҫע����͵�������

������Ӫ��ѧ�Ĺ۵���������ͳ�����ţ�̻����⣬��Ӧ�й���ʳƷ�����ﵰ���ʡ����������⡢ˮ�����߲ˣ��Լ���������֬�����ǵ�ʳƷ��

The following processes including SD,MM,PP,FI,CO .

SD Relevant Steps:
1.Check if all delivery in due list have been processed VL06G (Could set background jobs to automatically generate the billing due list for posting)
2.Check if all picking in due list have been processed VL06P
3.Check if all goods issue in due list have been processed VL04
4.Check if all billed AR has been release to accounting VFX3

PP Relevant Steps:
1.Check if all back flash error has been solved (COGI Check every day this kind of problem and solved on time)
2.Check if all production orders that will not be followed have been finally confirmed or technically closed. Do final confirmation even small quantity variance exist but we consider this order has finished
3.Do technical close at month end for the orders will not be followed in the future
4.Confirmation. Do not confirm any assembly scrap when do production order conf.

MM Relevant Steps 1.Check if all goods movement has been booked in SAP
2.GR/IR clearing accounts maintenance if needed
3.Open the MM period for movement posting when new period starts MMPV

FI Relevant Steps
1.Book all accounting entries for:
- Accrued expense
- Do recurring entry (prepayment, accrued expense, amortization)
- Process G/L, vendor, customer balance & open items
- Cost allocations by FI
2.AM Fixed asset depreciation run and period posting AFAB
3.AM Periodic posting ASKB
4.G/L,AR,AP balance check & Open item clearing
5.Foreign currency revaluation for bank/cash & AR AP open items
Bank/cash revaluation: F.06
AR AP open items: F.05
6.GR/IR clearing account regrouping process F.19
7.Automatic clearing for G/L accounts, vendor and customer F.13

CO Relevant Steps 1.Release standard cost estimate
CK24 Only when there are costing run to be released.
2.Cost reallocation according to activity
Distribution: CKV5
Assessment: KSU5
3.Cost splitting among activity KSS2
4.Actual activity price calculation KSII
5.Production order revaluation with actual activity price CON2
6.WIP calculation for the production orders KKAO
7.Variance calculation for the production orders KKS1
8.Production / Costing orders settlement CO88/KO88
9.Material ledger closing > MMPV first
a.Create costing run CKRU00
b.Allow settlement CKMF_RUN
c.Allow closing entries CKMG_RUN
d.Material selection CKMB_RUN
e.Determine costing sequence CKMC_RUN
f.Settle single level CKMH_RUN
g.Settle multi level CKMM_RUN
h.Post closing CKMI

GR/IR���ݹ�������˼·�ļ򵥶Ա� /images/blogs/files/5251/GRIR��Ŀ����.doc
�ӽ����ɹ���->���->��ƱУ��ʵ���ϻ��и������,�����������GR/IR��Ŀ��ʹ��.
GR/IR��Ŀ,���Tcode:OBYP|F.19|F.13|MB5S|MR11|MR11 SHOW
ʲô�� GR/IR?
GR/IR Ӣ��ȫ����Goods Receipt/Invoice Receipt,���й������ʲɹ�|���ϲɹ���Ŀ����,�������ڶ����ƿ�Ŀ���������:ԭ��ҵ����ƶ����������ʲɹ�����ƿ�Ŀ������ҵ������ϡ���Ʒ�ȵIJɹ��ɱ���������ҵ����ʵ�ʳɱ����Dz��üƻ��ɱ����в��ϡ���Ʒ���ճ����㣬������ʹ�ñ���Ŀ��

1.���ڹ�ҵ��ҵ���Խ�����Ŀ��Ϊ�����ϲɹ�����Ŀ�����в��ϵ��ճ�����.��
2.������Ʒ��ͨ��ҵ��ɹ���Ʒ������ĩ��������;��Ʒ���Լ�����ʵ�ʳɱ�������ϡ���Ʒ����ҵ,���Խ�����Ŀ��Ϊ����;��������Ŀ����.��
3.��׼���ƺ�ȡ���������ʲɹ�����Ŀ��ʹ�ã�����ȷ�����������ϲɹ���������;������������Ŀ�ĺ������ݡ����У������ϲɹ�����Ŀ������ҵ���üƻ��ɱ����в����ճ������������ϵIJɹ��ɱ�������ĿӦ�����չ�Ӧ��λ������Ʒ�ֽ�����ϸ���㣻����;��������Ŀ������ҵ����ʵ�ʳɱ�������ۣ����в��ϣ�����Ʒ���ճ����㣬�����Ѹ���δ�������Ĺ�����ϻ���Ʒ�IJɹ��ɱ�������ĿӦ�����չ�Ӧ��λ������ϸ���㡣�����ʲɹ����������ϲɹ�������Ŀ��������ʵ��һ��,ֻ�ǿ�Ŀ������ͬ���ѡ�һ��GR/IR��Ŀ����
1������GR/IR��Ŀ(Tcode: OBYC->WRX)��OBYC->WRX�����øÿ�Ŀͨ����E�ľͽ���GR/IR�����������ƹ������������ϲɹ�����ֱ��ʹ����Ӧ���ʿ�-Ӧ���ݹ�����Ŀ��ֱ��ʹ����Ӧ���ʿ�-Ӧ���ݹ�����Ŀ����ҵͨ���Dz�����Ʊ����δ����ҵ������ȷ��Ӧ���ʿ��Ƿdz������ģ��Ͼ���Ǯ�������ͳ�ȥ�Ǽ����ܵ����飬����һ��Ҫ������3����3��ͨ��ָ��Ӧ�̵��ͻ�������ҵ���ջ����͹�Ӧ�̷�Ʊ������൥��ƥ�䣬�������¢���Ե�ǿ�ƹ�Ӧ�̻�δ�����ͷ�Ʊ�����Ŷ�û�С���ĩ������Ҫ��GR/IR��Ŀ(���ϲɹ�)��Ŀ����ĩ�ط��ൽ����;����������Ӧ���ʿ�-Ӧ���ݹ�����Ŀ�ֱ������ʲ���ծ�������ʲ��͸�ծ����,���õ�Tcode:F.19���з���,��F.19����ҵͨ��ͬʱ������Ʊ����δ������������Ʊδ������ҵ�������ҵ�ǻ�����������Ʊ����δ������ҵ��GR/IR��Ŀ������Ӧ���ʿ�-Ӧ���ݹ�����ʵ����F.19�ط���Ҳ��û�б�Ҫ����,�������GR/IRֱ�Ӿ͹Ҹ�ծ��ر��,�ڿ��������Ŀ��,�����漰�����ƿ�Ŀ��,����ʹ����ǿLMR1M002(Tcode:SMOD|CMOD)��ǿGR/IR��Ŀ��

Aggregate

An aggregate is a subset of an InfoCube. The objective when using aggregates is to reduce I/O volume. The BW OLAP processor selects an appropriate aggregate during a query run or a navigation step. If no appropriate aggregate exists, the BW OLAP processor retrieves data from the original InfoCube instead.

Aggregate rollup

Aggregate rollup is a procedure to update aggregates with new data loads.

Application component

Application components are used to organize InfoSources. They are similar to the InfoAreas used with InfoCubes. The maximum number of characters allowed for the technical name is 32.

Authorization

An authorization defines what a user can do, and to which SAP objects. For example, a user with an authorization can display and execute, but not change, a query. Authorizations are defined using authorization objects.

Authorization object

An authorization object is used to define user authorizations. It has fields with values to specify authorized activities, such as display and execution, on authorized business objects, such as queries. The maximum number of characters allowed for the technical name is 10.

Authorization profile

An authorization profile is made up of multiple authorizations. The maximum number of characters allowed for the technical name is 10.

Bitmap index

A bitmap index uses maps of bits to locate records in a table. Bitmap indices are very effective for Boolean operations of the WHERE clause of a SELECT statement. When the cardinality of a column is low, a bitmap index size will be small, thereby reducing I/O volume.

Business Content

Business Content is a complete set of BW objects developed by SAP to support the OLAP tasks. It contains roles, workbooks, queries, InfoCubes, key figures, characteristics, update rules, InfoSources, and extractors for SAP R/3, and other mySAP solutions.

BW

BW is a data warehousing solution from SAP.

BW Monitor

BW Monitor displays data loading status and provides assistance in troubleshooting if errors occur.

BW Scheduler

BW Scheduler specifies when to load data. It is based on the same techniques used for scheduling R/3 background jobs.

BW Statistics

BW Statistics is a tool for recording and reporting system activity and performance information.

Change run

Change run is a procedure used to activate characteristic data changes.

Characteristic

Characteristics are descriptions of key figures, such as Customer ID, Material Number, Sales Representative ID, Unit of Measure, and Transaction Date. The maximum number of characters allowed for the technical name is 9.

Client

A client is a subset of data in an SAP system. Data shared by all clients is called client-independent data, as compared with client-dependent data. When logging on to an SAP system, a user must specify which client to use. Once in the system, the user has access to both client-dependent data and client-independent data.

Communication structure

The communication structure is the structure underlying the InfoSource.

Compound attribute

A compound attribute differentiates a characteristic to make the characteristic uniquely identifiable. For example, if the same characteristic data from different source systems mean different things, then we can add the compound attribute 0SOURSYSTEM (source system ID) to the characteristic; 0SOURSYSTEM is provided with the Business Content.

Data packet size

For the same amount of data, the data packet size determines how work processes will be used in data loading. The smaller the data packet size, the more work processes needed.

Data Warehouse

Data Warehouse is a dedicated reporting and analysis environment based on the star schema database design technique and requiring special attention to the data ETTL process.

DataSource

A DataSource is not only a structure in which source system fields are logically grouped together, but also an object that contains ETTL-related information. Four types of DataSources exist:

• DataSources for transaction data

• DataSources for characteristic attributes

• DataSources for characteristic texts

• DataSources for characteristic hierarchies

If the source system is R/3, replicating DataSources from a source system will create identical DataSource structures in the BW system. The maximum number of characters allowed for a DataSource's technical name is 32.

Delta update

The Delta update option in the InfoPackage definition requests BW to load only the data that have been accumulated since the last update. Before a delta update occurs, the delta process must be initialized.

Development class

A development class is a group of objects that are logically related.

Display attribute

A display attribute provides supplemental information to a characteristic.

Drill-down

Drill-down is a user navigation step intended to get further detailed information.

ETTL

ETTL, one of the most challenging tasks in building a data warehouse, is the process of extracting, transforming, transferring, and loading data correctly and quickly.

Free characteristic

A free characteristic is a characteristic in a query used for drill-downs. It is not displayed in the initial result of a query run.

Full update

The Full update option in the InfoPackage definition requests BW to load all data that meet the selection criteria specified via the Select data tab.

Generic data extraction

Generic data extraction is a function in Business Content that allows us to create DataSources based on database views or InfoSet queries. InfoSet is similar to a view but allows outer joins between tables.

Granularity

Granularity describes the level of detail in a data warehouse. It is determined by business requirements and technology capabilities.

IDoc

IDoc (Intermediate Document) is used in SAP to transfer data between two systems. It is a specific instance of a data structure called the IDoc Type, whose processing logic is defined in the IDoc Interface.

Index

An index is a technique used to locate needed records in a database table quickly. BW uses two types of indices: B-tree indices for regular database tables and bitmap indices for fact tables and aggregate tables.

InfoArea

InfoAreas are used to organize InfoCubes and InfoObjects. Each InfoCube is assigned to an InfoArea. Through an InfoObject Catalog, each InfoObject is assigned to an InfoArea as well. The maximum number of characters allowed for the technical name is 30.

InfoCube

An InfoCube is a fact table and its associated dimension tables in the star schema. The maximum number of characters allowed for the technical name is 30.

InfoCube compression

InfoCube compression is a procedure used to aggregate multiple data loads at the request level.

InfoObject

In BW, key figures and characteristics are collectively called InfoObjects.

InfoObject Catalog

InfoObject Catalogs organize InfoObjects. Two types of InfoObject Catalogs exist: one for characteristics, and one for key figures. The maximum number of characters allowed for the technical name is 30.

InfoPackage

An InfoPackage specifies when and how to load data from a given source system. BW generates a 30-digit code starting with ZPAK as an InfoPackage's technical name.

InfoSource

An InfoSource is a structure in which InfoObjects are logically grouped together. InfoCubes and characteristics interact with InfoSources to get source system data. The maximum number of characters allowed for the technical name is 32.

Key figure

Key figures are numeric values or quantities, such as Per Unit Sales Price, Quantity Sold, and Sales Revenue. The maximum number of characters allowed for the technical name is 9.

Line item dimension

A line item dimension in a fact table connects directly with the SID table of its sole characteristic.

Logical system

A logical system is the name of a client in an SAP system.

Multi-cube

A multi-cube is a union of basic cubes. The multi-cube itself does not contain any data; rather, data reside in the basic cubes. To a user, the multi-cube is similar to a basic cube. When creating a query, the user can select characteristics and key figures from different basic cubes.

Navigational attribute

A navigational attribute indicates a characteristic-to-characteristic relationship between two characteristics. It provides supplemental information about a characteristic and enables navigation from characteristic to characteristic during a query.

Number range

A number range is a range of numbers that resides in application server memory for quick number assignments.

ODS

ODS is a BW architectural component located between PSA and InfoCubes that allows BEx reporting. It is not based on the star schema and is used primarily for detail reporting, rather than for dimensional analysis. ODS objects do not aggregate data as InfoCubes do. Instead, data are loaded into an ODS object by inserting new records, updating existing records, or deleting old records, as specified by the 0RECORDMODE value.

Parallel query

A parallel query uses multiple database processes, when available, to execute a query.

Partition

A partition is a piece of physical storage for database tables and indices. If the needed data reside in one or a few partitions, then only those partitions will be selected and examined by a SQL statement, thereby significantly reducing I/O volume.

Profile Generator

Profile Generator is a tool used to create authorization profiles.

PSA

PSA is a data staging area in BW. It allows us to check data in an intermediate location, before the data are sent to its destinations in BW.

Query

A BW query is a selection of characteristics and key figures for the analysis of the data in an InfoCube. A query refers to only one InfoCube, and its result is presented in a BEx Excel sheet. The maximum number of characters allowed for the technical name is 30.

Read mode

Read mode for a query determines the size and frequency of data retrievals from database: all data at once, as needed per navigation step, or as needed per hierarchy node.

Reconstruct

Reconstruct is a procedure used to restore load requests from PSA.

Request

A request is a data load request from BW Scheduler. Each time that BW Scheduler loads data into an InfoCube, a unique request ID is created in the data packet dimension table of the InfoCube.

RFC

RFC (Remote Function Call) is a call to a function module in a system different from the caller's�usually another SAP system on the local network.

Role

In Profile Generator, an authorization profile corresponds to a role. A user assigned to that role also has the corresponding authorization profile. A user can be assigned to multiple roles. The maximum number of characters allowed for the technical name is 30.

SID

SID (Surrogate-ID) translates a potentially long key for an InfoObject into a short four-byte integer, which saves I/O and memory during OLAP.

Source system

A source system is a protocol that BW uses to find and extract data. When the source system is a non-SAP system, such as a flat file or a third-party tool, the maximum number of characters allowed for the technical name is 10. When the source system is an SAP system, either R/3 or BW, the technical name matches the logical system name. The maximum number of characters allowed for the technical name is 32.

Star schema

A star schema is a technique used in the data warehouse database design to help data retrieval for online analytical processing.

Statistics

For a SQL statement, many execution plans are possible. The database optimizer generates the most efficient execution plan based on either the heuristic ranking of available execution plans or the cost calculation of available execution plans. Statistics is the information that the cost-based optimizer uses to calculate the cost of available execution plans and select the most appropriate one for execution. BW uses the cost-base optimizer for Oracle databases.

System Administration Assistant

System Administration Assistant is a collection of tools used to monitor and analyze general system operation conditions.

System landscape

The system landscape specifies the role of each system and the paths used in transporting objects among the various systems.

Time-dependent entire hierarchy

A time-dependent entire hierarchy is a time-dependent hierarchy whose nodes and leaves are not time-dependent.

Time-dependent hierarchy structure

A time-dependent hierarchy structure consists of nodes or leaves that are time-dependent, but the hierarchy itself is not time-dependent

Transfer rule

Transfer rules specify how DataSource fields are mapped to InfoSource InfoObjects.

Transfer structure

A transfer structure maps DataSource fields to InfoSource InfoObjects.

Update rule

An update rule specifies how data will be updated into their targets. The data target can be an InfoCube or an ODS object. If the update rule is applied to data from an InfoSource, the update rule's technical name will match the InfoSource's technical name. If the update rule is applied to data from an ODS object, the update rule's technical name will match the ODS object's technical name prefixed with number 8.

Variable

A variable is a query parameter. It gets its value from user input or takes a default value set by the variable creator.

Workbook

A BW workbook is an Excel file with a BEx query result saved in BDS. BW assigns a 25-digit ID to each workbook. Users need merely name a workbook's title.

1.����BAPI Structure (Structure������BAPI���ظ�ʹ�ã���Ϊһ��BAPI���ͷţ���Structure�����ᣩ��T-CODE��SE11��

2.����FUNCTION MODULE��T-CODE��SE37��

ÿ��BAPI�������Լ���Function Group��Function Group���Ա���ΪRFC

3.����Business Object(T-CODE��SWO1)

4.ʹ��BAPI WIZARD����API Method (T-CODE:SWO1:Utilities--API methods--methods)

����BAPI���Ա��ⲿ�������

5.Function Module����BOR Method

4.�ͷ�BAPI Function Module,

�ͷ�Business Object Type,�����ͷŶ����������ͷŶ��������µ������

�ͷ�BAPI��ΪBOR��һ��Method

Path��CODE��SWO1��Edit��change release status��Object type��To modeled��������

�� J2EE ���洴�� RFC Ŀ���ļ�

Use

In this activity you establish the RFC destination of the BW system for
the J2EE Engine.

Requirements

You have already established an RFC destination for the BW system in the
J2EE Engine.

Activities

1. Choose Edit -> Create.

2. Enter a name and a description for the destination.

3. Choose T as the connection type (start an external program using
TCP/IP).

4. On the Technical Settings tab page, choose Registered ServerProgram as the activation type and specify the registered server program
under program ID.
The program ID here has to correspond to the program ID that you
entered when maintaining the RFC destination in the J2EE Engine.

5. Specify the gateway host and the gateway service under Gateway
Options.

6. Save and test the connection.

������֪�� J2EE ����˿ں�������

Use

In order for the administrator of the Computing Center Management System
(CCMS) to be able to monitor the J2EE Engine, you must inform the system
of the host and port of the J2EE Engine.

Standard settings

Standard HTTP Port: 50000.

�ڿͣ��ҿ�������ĵ���
С�ף���ô���Ƶģ�
�ڿͣ���ľ��
С�ף��������������������û������
�ڿͣ���������������
С�ף���������������������������ģ�
�ڿͣ�������������ĵ������棡��
С�ף����ҵĵ��ԡ�����û�а�
�ڿͣ����ˣ�����ʲôҲû����

�ڿͣ����Ѿ���������ĵ���
С�ף�Ŷ
�ڿͣ������˰ɣ����ٺ�
С�ף��������ã�����ɱɱ���ɣ�����ҵĻ���ë���ܶ�Ү
�ڿͣ�������������

С�ף�����ô�������ҵ���������������
�ڿͣ������װ����ǽ
С�ף�װ����ǽ����Ͳ��ܽ�������
�ڿͣ���������ֻ�������ӵ�Ȥζ�ԣ�����������ĵ������Ҿ��úܰ׳�Ү

С�ף���˵������조����������
�ڿͣ���
С�ף�����Կ��Ʊ��˵ĵ��ԣ���
�ڿͣ�һ���ǵ�
С�ף�������Ժڵ���Щ��վ��
�ڿͣ���Ȼ��û�����˼ҽ��ҡ��ڿ͡���
С�ף���������Ŷ~~~`�һ���Ϊ������Ϊ�㳤�úܺڡ���������
����~~��

�ڿͣ��������ˣ���
С�ף�����������������úܷ���
�ڿͣ��Ǻܷ�����Ļ������Ҽ��������õ�һ̨��
С�ף����ǰɣ����������
�ڿͣ�����˵��Ļ��������������Ϸ��ֻ�в�����
С�ף�Ŷ~~���㿴���ҵġ������������𣬲��ǵ�װ���ģ����˺þ���Ү
�ڿͣ������������ټ�

�ڿͣ���~~~�����ˣ�
С�ף��ü��첻���㣬���ҵķ���ǽ��ס����
�ڿͣ�������Ц��������Ļ��ӱ����Լ��Ļ����ף����������˰�
С�ף������������һ��æ
�ڿͣ�ʲô�£�
С�ף����ܲ��ܽ������ϵͳ�޸�һ������
�ڿͣ���������������������
С�ף������㣬���Ұ��Ҽ�����µĵ�����˰ɡ�����������
�ڿͣ�ȥ������

�ڿͣ�������ȥ�ˣ�������
С�ף�����������ȥ���˼��찡�����Ҹ���
�ڿͣ���Ҫ�ҵ㶫��
С�ף����������ʲô������
�ڿͣ���������һ��ǰ������ϲ�����ֻ����Ļ����ϲ����������ȫ��

�ڿͣ������ˣ���
������������
�ڿͣ���ô��˵����
С�ף����鲻��
�ڿͣ�˭�۸����ˣ�
С�ף��ҵ�һ��Q�Ÿ㶪�ˣ��������ҵ����ϳ���
�ڿͣ�����򵥣��Ұ����û���
С�ף��ò�������
�ڿͣ������ܣ������ң����ٺţ�
С�ף���~~~~���Dz��ǵ���

С�ף�����ҳ�����������
�ڿͣ���ô������
С�ף����Dz������ҵ�IDȥ��̳���ˣ�����
�ڿͣ���������������˼�����˸������ˣ���������û�ɻ��£���Ϲ���˸����ӣ��ұ�֤�´���Ҳ������
С�ף��Dz��У�����
�ڿͣ��㻹Ҫ��ô����
С�ף��㷢�����ӵú�����Ү���ҵ�һ�εú������ÿ���Ŷ��������ٸ��ұ�һ��
�ڿͣ�����

�ڿͣ��ٺ٣��ղ�������һ������Ȥ����
С�ף�ʲô��
�ڿͣ��ҵ���̳��ȥ������
С�ף����ƽ����
�ڿͣ��Ҽ����Ͷ����������¥���������ý���
С�ף�������̫����ˣ��ҿɴ������ң��ᱻ��ɱ�ģ�
�ڿͣ�û�����Ѿ�����ɱ�ˡ�
С�ף��⻹��Ȥ����
�ڿͣ��ǰ�����Ϊ���õ������ID

С�ף����Ǹ�����
�ڿͣ�����˵�ǰɡ�
С�ף��ߵ�ʲô�̶ȣ�
�ڿͣ��ţ������ĵ�ʱ����Լ����Լ�
С�ף����������Ҳ�ᣡ
�ڿͣ�#��%����Ҳ���ԣ���
С�ף��ǰ���һ�ػ����ͺ��ˡ���������
�ڿͣ�����

�úڿ�Ŀǰ��ס�ں���ҽԺ����ȷ���ѳ��ֳ�����ǰ�ף�

*&---------------------------------------------------------------------*
*& Report ZMM71 *
*&---------------------------------------------------------------------*
* &Program : ZMM71 *
* &Author : Louis(ZhouCong) *
* &CreateDate : 10/04/2006 *
* &Change Author : Louis(ZhouCong) *
* &ChangeDate : 10/04/2006/-11/04/2006 *
* &Last ChangeDate : 11/05/2006 *
* &Code type : Report *
* &Description : ???????? *
* &--------------------------------------------------------------------*

REPORT zmm71
NO STANDARD PAGE HEADING LINE-SIZE 255 .

***********************************************************************
***>Include TYPE-POOLS
***********************************************************************
TYPE-POOLS: slis.
CLASS cl_mmim_auth DEFINITION LOAD.

***********************************************************************
***>Include Tables
***********************************************************************
TABLES: ekko, "Purchasing Document Header
ekpo, "Purchasing Document Item
ekbe, "History per Purchasing Document
ekkn, "Account Assignment in Purchasing Document
lfa1, "Vendor Master (General Section)
t023t, "Material Group Descriptions
t001. "Company Codes

***********************************************************************
***>Define Intervals tables
***********************************************************************
* working table for the entries of all Po tables
DATA: BEGIN OF wa_line,
ebeln LIKE ekko-ebeln, "?????'
lifnr LIKE ekko-lifnr, "?????'
waers LIKE ekko-waers, "????'
wkurs LIKE ekko-wkurs, "??'
* wkurc(15) TYPE c, "????'
ebelp LIKE ekpo-ebelp, "?????????'
matkl LIKE ekpo-matkl, "???'
txz01 LIKE ekpo-txz01, "???'
meins LIKE ekpo-meins, "????'
menge LIKE ekpo-menge, "????'
netwr LIKE ekpo-netwr, "PO??'
peinh LIKE ekpo-peinh, "????
netpr LIKE ekpo-netpr, "??'
netps(13) TYPE p DECIMALS 6, "????'
mwskz LIKE ekpo-mwskz, "??'

belnr LIKE ekbe-belnr, "??????'
bwart LIKE ekbe-bwart, "???? (????)'
budat LIKE ekbe-budat, "????????'
mengs LIKE ekbe-menge, "????'
dmbts LIKE ekbe-dmbtr, "????'
wrbtr LIKE ekbe-wrbtr, "????
mengi LIKE ekbe-menge, "??????'
dmbti LIKE ekbe-dmbtr, "??????'
shkzg LIKE ekbe-shkzg, "??/????'

sakto LIKE ekkn-sakto, "?????'
kostl LIKE ekkn-kostl, "????'
wgbez LIKE t023t-wgbez, "?????'
name1 LIKE lfa1-name1, "?????'

color TYPE slis_t_specialcol_alv,
END OF wa_line,
it_line LIKE TABLE OF wa_line WITH HEADER LINE,
itab LIKE TABLE OF wa_line WITH HEADER LINE.

DATA: BEGIN OF it_ekbe OCCURS 0,
ebeln LIKE ekbe-ebeln, "?????'
ebelp LIKE ekbe-ebelp, "?????????'
zekkn LIKE ekbe-zekkn, "????????'
vgabe LIKE ekbe-vgabe, "????/????'
belnr LIKE ekbe-belnr, "??????'
buzei LIKE ekbe-buzei, "????????'
bewtp LIKE ekbe-bewtp, "????????'
bwart LIKE ekbe-bwart, "???? (????)'
menge LIKE ekbe-menge, "??'
dmbtr LIKE ekbe-dmbtr, "????????'
shkzg LIKE ekbe-shkzg, "??/????'
END OF it_ekbe.

DATA: tab_lines TYPE i,
color TYPE slis_t_specialcol_alv WITH HEADER LINE.

DATA: g_menge LIKE ekbe-menge, "????'
g_dmbtr LIKE ekbe-dmbtr, "????'
g_mengt LIKE ekbe-menge, "????'
g_dmbtt LIKE ekbe-dmbtr. "????'

***>Uses For ALV
DATA: it_fieldcat TYPE slis_t_fieldcat_alv,
it_event TYPE slis_t_event,
wa_event TYPE slis_alv_event,
it_listhead TYPE slis_t_listheader,
sortcat TYPE slis_t_sortinfo_alv,
sortcat_ln LIKE LINE OF sortcat,
wa_listhead TYPE slis_listheader,
wa_layout TYPE slis_layout_alv,
wk_repid LIKE sy-repid,
g_command_form TYPE slis_formname VALUE 'USER_COMMAND',
gt_list_top_of_page TYPE slis_t_listheader,
g_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

*********************************************************
***>Parameters Selection-screen
*********************************************************
* Selection Conditions OBLIGATORY
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_ekorg FOR ekko-ekorg,
s_budat FOR ekbe-budat MEMORY ID but,
s_lifnr FOR ekko-lifnr MEMORY ID lif,
s_ebeln FOR ekko-ebeln MEMORY ID ebl,
s_matnr FOR ekpo-matnr MEMORY ID mat,
s_belnr FOR ekbe-belnr MEMORY ID mbl.
SELECTION-SCREEN END OF BLOCK b1.

*************************************************************
*INITIALIZATION
*************************************************************
INITIALIZATION.
wk_repid = sy-repid.

AT SELECTION-SCREEN.
CALL FUNCTION 'MMIM_ENTRYCHECK_MAIN'
TABLES
it_lifnr = s_lifnr
it_ekorg = s_ekorg.

**************************************************************
*START-OF-SELECTION
**************************************************************
START-OF-SELECTION.
IF ( s_ekorg IS INITIAL ) AND ( s_budat IS INITIAL ) AND
( s_lifnr IS INITIAL ) AND ( s_ebeln IS INITIAL ) AND
( s_matnr IS INITIAL ) AND ( s_belnr IS INITIAL ).
MESSAGE text-inf TYPE 'S' DISPLAY LIKE 'E'.
EXIT.
ENDIF.

PERFORM account_list_01.

CLEAR tab_lines.
DESCRIBE TABLE itab LINES tab_lines.
IF tab_lines EQ 0 OR tab_lines LT 0 .
MESSAGE text-msg TYPE 'S'.
EXIT.
ENDIF.

SORT itab BY lifnr ebeln ebelp belnr bwart.
PERFORM comment_build USING gt_list_top_of_page[].
PERFORM alv_field_cat_01.
PERFORM alv_show_01.

END-OF-SELECTION.

*&--------------------------------------------------------------------*
*& Form account_list_01
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
FORM account_list_01 .

REFRESH : it_line, itab, it_ekbe.
SELECT ekko~ebeln ekko~lifnr ekko~waers ekko~wkurs ekpo~ebelp
ekpo~matkl ekpo~txz01 ekpo~meins ekpo~menge ekpo~netwr
ekpo~peinh ekpo~netpr ekpo~mwskz ekbe~belnr ekbe~bwart
ekbe~budat ekbe~menge AS mengs ekbe~dmbtr AS dmbts ekbe~wrbtr
ekbe~shkzg
INTO CORRESPONDING FIELDS OF TABLE it_line
FROM ekko
INNER JOIN ekpo ON ekko~ebeln = ekpo~ebeln
INNER JOIN ekbe ON ekpo~ebeln = ekbe~ebeln AND ekpo~ebelp =
ekbe~ebelp
WHERE ekko~ebeln IN s_ebeln AND ekko~bstyp = 'F' AND
* ekko~bsart = 'ZSPO' AND ekko~loekz = space AND
ekko~lifnr IN s_lifnr AND ekko~ekorg IN s_ekorg AND
ekpo~matnr IN s_matnr AND ekpo~loekz = space AND
* ekbe~zekkn = '00' AND ekbe~vgabe = '1' AND
* ekbe~belnr IN s_belnr AND ekbe~bewtp = 'E' AND
ekbe~budat IN s_budat.
IF sy-subrc NE 0.
MESSAGE text-msg TYPE 'S'.
EXIT.
ENDIF.

SORT it_line BY ebeln ebelp belnr bwart.
REFRESH itab.
LOOP AT it_line INTO wa_line.
IF wa_line-bwart = '101'.
MOVE-CORRESPONDING wa_line TO itab.
APPEND itab.
ELSEIF wa_line-bwart = '102'.
LOOP AT itab WHERE ebeln = wa_line-ebeln AND ebelp = wa_line-ebelp
.
itab-mengs = itab-mengs - wa_line-mengs.
itab-dmbts = itab-dmbts - wa_line-dmbts.
itab-wrbtr = itab-wrbtr - wa_line-wrbtr.
MODIFY itab.
ENDLOOP.
ENDIF.
IF wa_line-bwart = '122'.
MOVE-CORRESPONDING wa_line TO itab.
APPEND itab.
ELSEIF wa_line-bwart = '123'.
LOOP AT itab WHERE ebeln = wa_line-ebeln AND ebelp = wa_line-ebelp
.
itab-mengs = itab-mengs - wa_line-mengs.
itab-dmbts = itab-dmbts - wa_line-dmbts.
itab-wrbtr = itab-wrbtr - wa_line-wrbtr.
MODIFY itab.
ENDLOOP.
ENDIF.
ENDLOOP.

SELECT ekbe~ebeln ekbe~ebelp ekbe~zekkn ekbe~vgabe ekbe~belnr
ekbe~buzei ekbe~bewtp ekbe~bwart ekbe~menge ekbe~dmbtr
ekbe~shkzg
INTO CORRESPONDING FIELDS OF TABLE it_ekbe
FROM ekbe
FOR ALL ENTRIES IN itab
WHERE ekbe~ebeln = itab-ebeln AND ekbe~ebelp = itab-ebelp AND
ekbe~zekkn = '01' AND ekbe~vgabe = '2' AND ekbe~bewtp = 'Q'.
SORT it_ekbe BY ebeln ebelp.

LOOP AT itab.
* ?????'
SELECT SINGLE wgbez INTO itab-wgbez
FROM t023t WHERE spras = sy-langu AND matkl = itab-matkl.
* ?????'
SELECT SINGLE name1 INTO itab-name1
FROM lfa1 WHERE lifnr = itab-lifnr.
* ?????/????'
SELECT SINGLE sakto kostl INTO (itab-sakto,itab-kostl)
FROM ekkn
WHERE ebeln = itab-ebeln AND ebelp = itab-ebelp AND zekkn = '01'.
* ??'
itab-netps = itab-netpr / itab-peinh.

CLEAR: itab-mengi, itab-dmbti.
LOOP AT it_ekbe WHERE ebeln = itab-ebeln AND ebelp = itab-ebelp.
* ??????/??????'
IF it_ekbe-zekkn = '01'.
IF it_ekbe-shkzg = 'S'.
itab-mengi = itab-mengi + it_ekbe-menge.
itab-dmbti = itab-dmbti + it_ekbe-dmbtr.
ENDIF.
IF it_ekbe-shkzg = 'H'.
itab-mengi = itab-mengi - it_ekbe-menge.
itab-dmbti = itab-dmbti - it_ekbe-dmbtr.
ENDIF.
ENDIF.
ENDLOOP.
REFRESH color.
IF itab-shkzg = 'H'.
itab-mengs = - itab-mengs.
itab-dmbts = - itab-dmbts.
itab-wrbtr = - itab-wrbtr.
* CLEAR:itab-mengi, itab-dmbti.
color-color-col = '6'.
ELSE.
color-color-col = '5'.
ENDIF.
color-fieldname = 'MENGE'. APPEND color.
color-fieldname = 'MEINS'. APPEND color.
color-fieldname = 'NETPS'. APPEND color.
color-fieldname = 'NETWR'. APPEND color.
color-fieldname = 'WAERS'. APPEND color.
color-fieldname = 'WKURS'. APPEND color.
color-fieldname = 'MWSKZ'. APPEND color.
color-fieldname = 'BELNR'. APPEND color.
color-fieldname = 'MENGS'. APPEND color.
color-fieldname = 'DMBTS'. APPEND color.
color-fieldname = 'WRBTR'. APPEND color.
color-fieldname = 'BUDAT'. APPEND color.
color-fieldname = 'MENGI'. APPEND color.
color-fieldname = 'DMBTI'. APPEND color.
itab-color[] = color[].
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
EXPORTING
input = itab-lifnr
IMPORTING
output = itab-lifnr.
MODIFY itab.
ENDLOOP.
ENDFORM. " account_list_01

*&--------------------------------------------------------------------*
*& Form comment_build
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->LT_TOP_OF_Ptext
*---------------------------------------------------------------------*
FORM comment_build USING lt_top_of_page TYPE
slis_t_listheader.
DATA:g_budat(25) TYPE c,
g_lifnr(25) TYPE c,
ls_line TYPE slis_listheader.

CLEAR ls_line.
ls_line-typ = 'H'.
ls_line-info = text-h01.
APPEND ls_line TO lt_top_of_page.
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = text-h02.
IF s_budat IS INITIAL.
g_budat = sy-datum.
CONCATENATE sy-datum+6(2) '.' sy-datum+4(2) '.' sy-datum+0(4)
INTO g_budat.
ELSE.
CONCATENATE s_budat-low+6(2) '.' s_budat-low+4(2) '.'
s_budat-low+0(4) ' To ' INTO g_budat.
CONCATENATE g_budat s_budat-high+6(2) '.' s_budat-high+4(2)
'.' s_budat-high+0(4) INTO g_budat.
ENDIF.
WRITE g_budat TO ls_line-info.
APPEND ls_line TO lt_top_of_page.
ls_line-key = text-h03.
ls_line-info = sy-uname.
APPEND ls_line TO lt_top_of_page.
ENDFORM. " COMMENT_BUILD

*&---------------------------------------------------------------------*
*& Form alv_field_cat_01
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM alv_field_cat_01 .
DATA:wa_fieldcat TYPE slis_fieldcat_alv.

REFRESH it_fieldcat.
PERFORM field_cat USING 'LIFNR' 'Verdor' '08' '' '' ''.
PERFORM field_cat USING 'NAME1' 'Vendor N' '08' '' '' ''.
PERFORM field_cat USING 'EBELN' 'Po.' '08' '' '' ''.
PERFORM field_cat USING 'EBELP' 'Po.Item' '06' '' '' ''.
PERFORM field_cat USING 'MATKL' 'M.Group' '10' '' '' ''.
PERFORM field_cat USING 'WGBEZ' 'M.Group.D' '20' '' '' ''.
PERFORM field_cat USING 'TXZ01' 'Text' '20' '' '' ''.
PERFORM field_cat USING 'MENGE' 'Qty' '10' 'MEINS' '' ''.
PERFORM field_cat USING 'MEINS' 'Unit' '08' '' '' ''.
PERFORM field_cat USING 'NETPS' 'Price' '08' '' '' ''.
PERFORM field_cat USING 'NETWR' 'PO.Am' '08' 'MEINS' '' ''.
PERFORM field_cat USING 'WAERS' 'Curr' '04' '' '' ''.
PERFORM field_cat USING 'WKURS' 'Rate' '04' '' '' ''.
PERFORM field_cat USING 'MWSKZ' 'Tax' '04' '' '' ''.
PERFORM field_cat USING 'BELNR' 'Gr.No' '08' '' '' ''.
PERFORM field_cat USING 'MENGS' 'Gr.Qty' '10' 'MEINS' 'X' ''.
PERFORM field_cat USING 'DMBTS' 'Gr.Am(L)' '14' 'MEINS' 'X' ''.
PERFORM field_cat USING 'WRBTR' 'Gr.Am(F)' '14' 'MEINS' 'X' ''.
PERFORM field_cat USING 'MENGI' 'Ir.Qty' '10' 'MEINS' '' ''.
PERFORM field_cat USING 'DMBTI' 'Ir.Am' '10' 'MEINS' '' ''.
PERFORM field_cat USING 'SAKTO' 'G/L Ac' '10' '' '' ''.
PERFORM field_cat USING 'KOSTL' 'Cost.C' '08' '' '' ''.
ENDFORM. " alv_field_cat_01

*&--------------------------------------------------------------------*
*& Form alv_show_01
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
FORM alv_show_01 .

* wa_layout-zebra = 'X'.
CLEAR : sortcat, sortcat_ln.
sortcat_ln-spos = '1'.
sortcat_ln-fieldname = 'LIFNR'.
sortcat_ln-fieldname = 'EBELN'.
sortcat_ln-up = 'X'.
sortcat_ln-down = space.
sortcat_ln-subtot = 'X'.
APPEND sortcat_ln TO sortcat.

wa_layout-coltab_fieldname = 'COLOR'.
* wa_layout-totals_text = 'Test'.
* wa_layout-subtotals_text = 'Test'.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = wk_repid
it_fieldcat = it_fieldcat
is_layout = wa_layout
i_callback_top_of_page = g_top_of_page
i_callback_user_command = g_command_form
i_default = 'X'
i_save = 'X'
it_events = it_event
it_sort = sortcat
TABLES
t_outtab = itab[]
EXCEPTIONS
program_error = 1
OTHERS = 2.

ENDFORM. " alv_show_01

*&--------------------------------------------------------------------*
*& Form field_cat
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->P_FIELD text
* -->P_TEXT text
* -->P_LEN text
* -->P_MEINS text
* -->P_SUM text
* -->P_FIX text
*---------------------------------------------------------------------*
FORM field_cat USING p_field
p_text
p_len
p_meins
p_sum
p_fix.

DATA:wa_fieldcat TYPE slis_fieldcat_alv.

wa_layout-colwidth_optimize = 'X'.

CLEAR wa_fieldcat.
wa_fieldcat-fieldname = p_field.
wa_fieldcat-tabname = 'ITAB'.
wa_fieldcat-seltext_l = p_text.
wa_fieldcat-outputlen = p_len.
wa_fieldcat-qfieldname = p_meins.
wa_fieldcat-do_sum = p_sum.
wa_fieldcat-fix_column = p_fix.
APPEND wa_fieldcat TO it_fieldcat.

ENDFORM. "field_cat

*&--------------------------------------------------------------------*
*& Form top_of_page
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = gt_list_top_of_page.
ENDFORM. " TOP_OF_PAGE

*&--------------------------------------------------------------------*
*& Form user_command
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->R_UCOMM text
* -->RS_SELFIELDtext
*---------------------------------------------------------------------*
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
CASE r_ucomm.
WHEN '&IC1'. "doubleclick
READ TABLE itab INDEX rs_selfield-tabindex.
IF sy-subrc = 0.
CASE rs_selfield-fieldname.
WHEN 'BELNR'.
IF itab-belnr IS INITIAL.
EXIT.
ENDIF.
SET PARAMETER ID 'MBN' FIELD itab-belnr.
SET PARAMETER ID 'MJA' FIELD ''.
CALL TRANSACTION 'MB03' AND SKIP FIRST SCREEN.
WHEN 'EBELN'.
IF itab-ebeln IS INITIAL.
EXIT.
ENDIF.
SET PARAMETER ID 'BES' FIELD itab-ebeln.
CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
ENDCASE.
ENDIF.
ENDCASE.
CLEAR r_ucomm.
ENDFORM. "user_command

*&---------------------------------------------------------------------*
*& Report Z_TEST_2
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT Z_TEST_2.
*---------------------------OLE----------------------------------*
include ole2incl.

data: excel type ole2_object, " Excel object
workbook type ole2_object, " Workbook object
sheet type ole2_object, " Worksheet object
range type ole2_object, " Range object
cell type ole2_object. " Cell object

data: sheet_name(20) value 'BS'. "Excel�ļ����sheet name
data local_file like rcgfiletr-ftfront."�����ļ�����
local_file = 'c:DO_TEST_OLE.xls'.

START-OF-SELECTION.

data: c1 type i,
c2 type i,
c3 type i,
c4 type i.

create object excel 'EXCEL.APPLICATION'. " CREATE EXCEL OBJECT
if sy-subrc ne 0.
write: / 'Excel init failed, return code is ', sy-subrc.
exit.
endif.
set property of excel 'Visible' = 1.
call method of excel 'Workbooks' = workbook.
data h type i.

call method of workbook 'Open' exporting #1 = local_file.
call method of excel 'Sheets' = sheet exporting #1 = sheet_name.
call method of sheet 'SELECT' .

*���̧ͷ
perform fill_range using 1 1 'F_TEST1'.
perform fill_range using 1 2 'F_TEST2'.

free object excel.
free object workbook.
free object sheet.
free object range.
free object cell.

*---------------------------------------------------------------------*
* FORM fill_range *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
* --> VALUE(F_ROW) *
* --> VALUE(F_COL) *
* --> VALUE(F_VALUE) *
*---------------------------------------------------------------------*
form fill_range using value(f_row)
value(f_col)
value(f_value).

call method of excel 'CELLS' = cell
exporting
#1 = f_row
#2 = f_col.
set property of cell 'VALUE' = f_value.
endform. "FILL_RANGE