What is the diff b/n sy-tabix,sy-subrc,sy-dbcnt

hi
experts can u help me for this

Hi
- SY-TABIX is the index (record number) of a record of an internal table: while looping or reading an internal table it means the current record:
LOOP AT ITAB.
WRITE: SY-TABIX.
ENDLOOP.
READ TABLE ITAB WITH KEY FIELD = <...>
WRITE SY-TABIX.
- SY-SUBRC is the rEsult of a certain command: if it's done succeffully its value is 0:
SELECT SINGLE * FROM T001 WHERE BUKRS = <....>
IF SY-SUBRC = 0.
WRITE: 'Table T001 is read succeffully".
ENDIF.
- SY-DBCNT is the number of records got out by a SELECT:
SELECT * FROM BKPF INTO TABLE T_BKPF WHERE BUKRS = <...>
AND GJAHR = '2007'.
WRITE: 'Extracted', SY-DBCNT, 'records'.
Max

Similar Messages

What is the diff b\w open form and start form in scripts.

Hi,
can any one tell me what is the diff andb\w open form and start form in scripts.when we should use open form and when start form.

Hi Friend.
I have understood some usefull information and would like to share with you.
Within one transaction, you can open and close several layout sets using OPEN_FORM and
CLOSE_FORM, however not simultaneously. You can use parameters in the OPEN_FORM to control
whether the output is stored in the same print request. But also the SAP spool decides,
depending on several plausibility checks, whether new output is appended to an existing
print request or whether to create a new print request anyway.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
You cannot combine ABAP/4 list output and SAPscript output in one print request.
START A LAYOUT SET AGAIN
Usually a print program does not print only one urging letter or one account statement, but
several layout sets for different customers. To have the output for each customer begin with
the start page of the layout set, you must start the current layout set again and again.
To start a layout set again, you must first end the current layout set and then open the
layout set again. Within one print request, first call the function module END_FORM. It
executes the final processing for the current layout set. Then start the layout set again
using START_FORM. Output then begins again on the start page of the desired layout set.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION CLOSE_FORM
Hope your obstacle is cleared.
If not do ask me again?

What is the diff b/w flat file and legacy system?

Hi everyone,
when v say v r working on scenario FILE to FILE? which format of file r v usually working on? and what is the diff b/w flat file and legacy system?
thanx

Hi,
when v say v r working on scenario FILE to FILE? which format of file r v usually working on?
>>>Many a times it will be a Flat file with CSV format,Tab delimited format, fixedlength fields.
what is the diff b/w flat file and legacy system?
>>>We can not differeniate like this..
Flat file may come from any systems, it may be live system or legacy system.
Legacy system- is something like old, or past one. If you talk about SAP , then older versions of SAP can be called as a legacy system.
So it may be a file system, or any system which is old version but it doesnot mean it is not in use,
Regards,
Moorthy

What is the diff b/w transactional cube and std cube

What is the diff b/w transactional cube and std cube

Hi Main differences,
1) Trasactional infocube are optimized for writing data that is multiple user can simultaneously write data into it without much effect on the performance where as the std infocube are optimized to read the data ie.e through queries.
2) transactional inofcubes can be loaded through SEM process as well normal laoding process.Std can be loaded only thorugh normal loading process.
3) the way data is stored is same but the indexing and partionong aspects are different since one is optimized for writing and another one for reading.
Thanks
Message was edited by:
Ajeet Singh

What is the diff b/w Conventional Path and Direct Path?

What is the diff b/w Conventional Path and Direct Path?
While doing exp/imp
which one is best in peroformance Conventional Or Direct
consider my Oracle is 9i (9.2.0) and Os is Solaris 9
Could you please clarify.....
Thanks

http://download.oracle.com/docs/cd/B10501_01/server.920/a96652/ch01.htm#1005685

Hi this pandu can i know what is the diff between pnp &pnpce ldb

hi,
this pandu can i know what is the diff between pnp &pnpce logical database.
thanks and regards,
pandu.

pretty much the same.. except that PNPCE has additional functionality to deal with Concurrent Employment.. PL go through <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm">SAP Help</a> for more info.
~Suresh

What is the diff between general gl a/c, control a/c, reconciliation a/c,

Dear All
what is the diff between general gl a/c, control a/c, reconciliation a/c & offsetting a/c.

Hi,
Normal GL Account is the account where the accounting entries are posted. GL Accounts will be broadly of two categories like Balance Sheet Accounts (Assets & Liabilities) and Profit & Loss Accounts (Income and Expenses).
Reconciliation Accounts are used where a subsidiary ledger is maintained. For example for Customers and Vendors details are maintained in separate ledgers but the control totals are posted in the Reconciliation Account which is part of GL Accounts. Similarly reconciliation accounts are maintained for Assets and Materials also. Further, in case of Customer and Vendor accounts the number of line items will be very high, hence only the totals are updated in GL and line items will be individual ledgers. Basically reconciliation account and control account are similar.
Offsetting Account: In Financial Accounting for every debit there should be a corresponding credit. So when ever any entry posted it will normally hit two GL Accounts. When we look at one line item, we will be interested where the other side of the entry is posted. This entry is the offsetting entry.
If you find this usel, please assign points.
Thanks
Murali.

What is the Diff Between tcodes WE19 in XI and WE19 in r/3 sys

Hi all,
Can anyone tell me
What is the Diff Between tcodes WE19 in XI and WE19 in r/3 sys?
one more question I have a File>XI->IDOC scenario
the file is picked up from the sender sys
but not posted the IDOC to the receiver sys
I need to post that particular record to r/3 sys can any tell me how to post the record.
Thanks
Sai.

SAP PI alo have ABAP stack part of PI server, so we will have all trasaction codes in PI too(ECC trasaction codes),the use of WE 19 in ECC to reprocess IDoc to external partner system.
WE 19 tx in PI also same purpose if you are using PI ABAP stack for creating and processing IDoc's,but we never use it.
You hav to build mapping logic to suppress unwated data and create IDoc in ECC.
Regards,
Raj

What is the diff bet XI and Business connector, backend contracts & Goa?

hi friends
what is the diff bet XI and Business connector ,diff bet backend contracts and goa
i know that XI(for new customers) and business connector for existing customers
do u think xi and Business Connector perform the same task
Regards
Vinny

Hi Vinny,
As Khan told, business connector is old technolgy and it has almost same functionlities like in XI.
both are mainly used for converts idoc's into xml format....
GOA: Global outline agreemnts mainly used when srm is having multiple backend systems. with reference to GOA , we can create local contracts in backend systems ...
Thanks
Ravi

What is the Diff bet partner functions and business partner?

Hi friends
what is the Diff bet partner functions and business partner
Regards
Abirath

Hi,
In SRM there are different Partner functions like REQUESTER, GOODS RECIPIENT, VENDOR ,LOCATION.
All the org units or users in SRM will have a unique identification number called Business Partner Number maintained in table BUT000.
The users can have differnt partner functions in differnt documents and accordingly mainatained in table CRMD_PARTNER.
Hope this will give you some infomation.
Regards,
Sheetal.

What r the diff types of schedule line categoriesr there ? purposes of its?

what r the diff types of schedule line categoriesr there ? purposes of its?

Deva, you are asking A LOT of basic SD questions which you can find answers to in standard SAP documentation available on line.
Please read that stuff first, and keep your questions here to more specific configuration / transaction details
Thanks in advance

What r the diff. error that can be solved using RSRV tcode?

Hi ,
what r the diff. error that can be solved using RSRV tcode?
I want to know all the errors that can be solved using RSRV t code
if any body is having good document regarding RSRV please send it to me at
[email protected]
Thanx in advance,
ravi.

Hi,
Refer the below links for more details about RSRV TCODE.
/community [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
Transaction RSRV: BW Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.
The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.
Starting the Transaction
You can reach the test and repair environment
By entering the transaction code RSRV
From InfoObject maintenance (Transaction RSD1)
By clicking on the "Analyze" button in the intial screen.
After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.
The Initial Screen
When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.
After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:
1. On the left-hand side, you can see a tree structure with the pool of available tests.
2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.
Combined and Elementary Tests
An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.
In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.
Combining a Test Package and Executing it.
Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.
Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.
A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.
After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.
Test Results
The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.
In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.
Repairs
Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.
After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.
Test Packages
The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:
Load packages
Load for processing - the package is then locked against changes by others.
Delete and
Schedule execution at a later date or at regular intervals in background processing
Settings
In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.
Jobs Menu Option
You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.
Application Log Menu Option
You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.
New Selection Button
The currently selected test package is deleted when you press this button.
Filter Button
After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.
Executing Test Packages in Process Chains
You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.
The RSRV process log in the process chain is built as follows:
First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.
A log view of the RSRV test package at the specified detail level follows.
Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.
A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.
Hope This Helps,
This is already there in SDN.
Regards,
rik

Hi guru's what is the diff between for all entries & joins

hi guru's what is the diff between for all entries & joins

Hi Vasu,
Joins are used to fetch data fast from Database tables:
Tables are joined with the proper key fields to fetch the data properly.
If there are no proper key fields between tables don't use Joins;
Important thing is that don't USE JOINS FOR CLUSTER tableslike BSEG and KONV.
Only use for Transparenmt tables.
You can also use joins for the database VIews to fetch the data.
JOINS
... FROM tabref1 [INNER] JOIN tabref2 ON cond
Effect
The data is to be selected from transparent database tables and/or views determined by tabref1 and tabref2. tabref1 and tabref2 each have the same form as in variant 1 or are themselves Join expressions. The keyword INNER does not have to be specified. The database tables or views determined by tabref1 and tabref2 must be recognized by the ABAP Dictionary.
In a relational data structure, it is quite normal for data that belongs together to be split up across several tables to help the process of standardization (see relational databases). To regroup this information into a database query, you can link tables using the join command. This formulates conditions for the columns in the tables involved. The inner join contains all combinations of lines from the database table determined by tabref1 with lines from the table determined by tabref2, whose values together meet the logical condition (join condition) specified using ON>cond.
Inner join between table 1 and table 2, where column D in both tables in the join condition is set the same:
Table 1 Table 2
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
3
e2
f2
g2
h2
a3
b3
c3
2
4
e3
f3
g3
h3
a4
b4
c4
3
|--|||--|
Inner Join
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
1
e1
f1
g1
h1
a4
b4
c4
3
3
e2
f2
g2
h2
|--||||||||--|
Example
Output a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or a table alias.
Note
In order to determine the result of a SELECT command where the FROM clause contains a join, the database system first creates a temporary table containing the lines that meet the ON condition. The WHERE condition is then applied to the temporary table. It does not matter in an inner join whether the condition is in the ON or WHEREclause. The following example returns the same solution as the previous one.
Example
Output of a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID
WHERE FCONNID = PCONNID
AND P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
Note
Since not all of the database systems supported by SAP use the standard syntax for ON conditions, the syntax has been restricted. It only allows those joins that produce the same results on all of the supported database systems:
Only a table or view may appear to the right of the JOIN operator, not another join expression.
Only AND is possible in the ON condition as a logical operator.
Each comparison in the ON condition must contain a field from the right-hand table.
If an outer join occurs in the FROM clause, all the ON conditions must contain at least one "real" JOIN condition (a condition that contains a field from tabref1 amd a field from tabref2.
Note
In some cases, '*' may be specified in the SELECT clause, and an internal table or work area is entered into the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the FROM clause, according to the structure of each table work area. There can then be gaps between table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, not simply by counting the total number of fields. For an example, see below:
Variant 3
... FROM tabref1 LEFT [OUTER] JOIN tabref2 ON cond
Effect
Selects the data from the transparent database tables and/or views specified in tabref1 and tabref2. tabref1 und tabref2 both have either the same form as in variant 1 or are themselves join expressions. The keyword OUTER can be omitted. The database tables or views specified in tabref1 and tabref2 must be recognized by the ABAP-Dictionary.
In order to determine the result of a SELECT command where the FROM clause contains a left outer join, the database system creates a temporary table containing the lines that meet the ON condition. The remaining fields from the left-hand table (tabref1) are then added to this table, and their corresponding fields from the right-hand table are filled with ZERO values. The system then applies the WHERE condition to the table.
Left outer join between table 1 and table 2 where column D in both tables set the join condition:
Table 1 Table 2
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
3
e2
f2
g2
h2
a3
b3
c3
2
4
e3
f3
g3
h3
a4
b4
c4
3
|--|||--|
Left Outer Join
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
1
e1
f1
g1
h1
a3
b3
c3
2
NULL
NULL
NULL
NULL
NULL
a4
b4
c4
3
3
e2
f2
g2
h2
|--||||||||--|
Example
Output a list of all custimers with their bookings for October 15th, 2001:
DATA: CUSTOMER TYPE SCUSTOM,
BOOKING TYPE SBOOK.
SELECT SCUSTOMNAME SCUSTOMPOSTCODE SCUSTOM~CITY
SBOOKFLDATE SBOOKCARRID SBOOKCONNID SBOOKBOOKID
INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID)
FROM SCUSTOM LEFT OUTER JOIN SBOOK
ON SCUSTOMID = SBOOKCUSTOMID AND
SBOOK~FLDATE = '20011015'
ORDER BY SCUSTOMNAME SBOOKFLDATE.
WRITE: / CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or using an alias.
Note
For the resulting set of a SELECT command with a left outer join in the FROM clause, it is generally of crucial importance whether a logical condition is in the ON or WHERE condition. Since not all of the database systems supported by SAP themselves support the standard syntax and semantics of the left outer join, the syntax has been restricted to those cases that return the same solution in all database systems:
Only a table or view may come after the JOIN operator, not another join statement.
The only logical operator allowed in the ON condition is AND.
Each comparison in the ON condition must contain a field from the right-hand table.
Comparisons in the WHERE condition must not contain a field from the right-hand table.
The ON condition must contain at least one "real" JOIN condition (a condition in which a field from tabref1 as well as from tabref2 occurs).
Note
In some cases, '*' may be specivied as the field list in the SELECT clause, and an internal table or work area is entered in the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the llen in der FROM clause, according to the structure of each table work area. There can be gaps between the table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, as in the following example (not simply by counting the total number of fields).
Example
Example of a JOIN with more than two tables: Select all flights from Frankfurt to New York between September 10th and 20th, 2001 where there are available places, and display the name of the airline.
DATA: BEGIN OF WA,
FLIGHT TYPE SFLIGHT,
PFLI TYPE SPFLI,
CARR TYPE SCARR,
END OF WA.
SELECT * INTO WA
FROM ( SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID )
INNER JOIN SCARR AS C
ON FCARRID = CCARRID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / WA-CARR-CARRNAME, WA-FLIGHT-FLDATE, WA-FLIGHT-CARRID,
WA-FLIGHT-CONNID.
ENDSELECT.
And for all entries,
this will help u.
use of FOR ALL ENTRIES:
1. INNER JOIN
DBTAB1 <----
> DBTAB2
It is used to JOIN two DATABASE tables
having some COMMON fields.
2. Whereas
For All Entries,
DBTAB1 <----
> ITAB1
is not at all related to two DATABASE tables.
It is related to INTERNAL table.
3. If we want to fetch data
from some DBTABLE1
but we want to fetch
for only some records
which are contained in some internal table,
then we use for alll entries.
1. simple example of for all entries.
2. NOTE THAT
In for all entries,
it is NOT necessary to use TWO DBTABLES.
(as against JOIN)
3. use this program (just copy paste)
it will fetch data
from T001
FOR ONLY TWO COMPANIES (as mentioned in itab)
4
REPORT abc.
DATA : BEGIN OF itab OCCURS 0,
bukrs LIKE t001-bukrs,
END OF itab.
DATA : t001 LIKE TABLE OF t001 WITH HEADER LINE.
itab-bukrs = '1000'.
APPEND itab.
itab-bukrs = '1100'.
APPEND itab.
SELECT * FROM t001
INTO TABLE t001
FOR ALL ENTRIES IN itab
WHERE bukrs = itab-bukrs.
LOOP AT t001.
WRITE :/ t001-bukrs.
ENDLOOP.
cheers,
Hema.

What is the diff bet CCM catalog and MDM catalog?

Hi Friends
What is the diff bet CCM catalog and MDM catalog?
Thanks & Regards
Kanni

Hello,
CCM & SRM-MDM are SAP Catalog Content Management solutions.
In basic terms, MDM is latest solution & will be replacing CCM. All new features like service hierarchies are included in MDM 3.0.
CCM: upload, manage, and search in procurement catalogs.
http://help.sap.com/saphelp_ccm20/helpdata/en/index.htm
MDM: Search, compare, and procure products from suppliers.
It provides:
Catalog content management functions, such as the import of catalog structures or data, the transfer of catalog items to a procurement application, and search functions
Procurement catalogs
Supplier catalogs in a Web-based environment
The SRM-MDM Catalog is based on functions provided by SAP NetWeaver Master Data Management (SAP NetWeaver MDM) and bundles together in one specific application those SAP NetWeaver MDM functions required for catalog content management.
http://help.sap.com/saphelp_srm70/helpdata/en/45/ddd04f8c6e2e97e10000000a155369/frameset.htm
Hope this helps.
Thanks
Ashutosh

Hi gurus what is the diff between free & refresh

hi gurus what is the diff between free & refresh

Hii!
FREE f.
Effect
FREE f has the same effect as CLEAR f , namely that a Data object f is reset to the initial value corresponding to its type.
Unlike CLEAR, FREE also releases any resources taken up by the data object f. FREE can also release more resources than CLEAR for table work areas declared using the TABLES statement.
After FREE f, the data object f can be re-addressed at any time. The only condition is that you may need to re-allocate resources to the object.
Note
If f is an internal table with header line (where the name f in a sense has two meanings) the statement FREE f refers to the body of the table, and the statement CLEAR f refers to the header line.
REFRESH itab.
Effect
The internal table itab is reset to its initial state, i.e. all table entries are deleted.
Der Return Code SY-SUBRC is undefined.
Notes
The header entry of a table with a header line remains unchanged. It can be reset to its initial value using CLEAR.
FREE itab can be used to free up the memory allocated to the table.
Note
Performance:
The runtime required to reset an internal table depends on the amount of memory previously occupied by that table.
Resetting a small internal table takes around 15 msn (standard microseconds). Resetting a 200 KB table takes around 400 msn, and a 1 MB table, around 3000 msn.
If the internal table has an index or a hash table (because it was edited using INSERT, DELETE, SORT or COLLECT), the runtime increases slightly, since the index or hash table has to be released as well as the table itself.
Regards
Abhijeet

What is the diff b/n sy-tabix,sy-subrc,sy-dbcnt

Similar Messages

Maybe you are looking for