Which scenerio we use at new and on change....

i which scenerio we use at new then on change....
basically what is the difference b/w them...

Hi,
if u use 'at-new' statement , basically it dont pick first record of the itab where as 'on chage of' can pick from first record.
all these control brake statements can work with header line except 'on change of' event.
At New.
Effect
Beginning or end of a group of lines with the same content in the component comp1 comp2 ... and in the components to the left of comp1 comp2 .... The components comp1 comp2 ... can be specified, as described in the section Specification of Components, with the limitation that access to object attributes is not possible here.
Example:
codeLOOP AT itab result ...
[AT NEW comp1.
ENDAT.
endloop.[/code]
On Change of:
Effect:
The statements ON CHANGE OF and ENDON, which are forbidden in classes, define a control structure that can contain a statement block statement_block. After ON CHANGE OF, any number of data objects dobj1, dobj2... of any data type can be added..
Example:
In a SELECT loop, a statement block should only be executed if the content of the column CARRID has changed.
codeDATA spfli_wa TYPE spfli.
SELECT *
FROM spfli
INTO spfli_wa
ORDER BY carrid.
ON CHANGE OF spfli_wa-carrid.
ENDON.
ENDSELECT.[/code]
difference btwn at new and on change of

Similar Messages

How to decide which adapter to use from IDOC and RFC?

Hi All,
When interating XI with an SAP system,
How to decide which adapter to use from IDOC and RFC?
Thanks.

Hi,
you can also consider to use ABAP Proxy if you are working with Systems based on SAP Web AS 6.40.
Here some useful links:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm">ABAP Proxy Runtime</a>
ABAP Proxies in XI(Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
ABAP Server Proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
How do you activate ABAP Proxies?
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
XI: Reliable Messaging EOIO in ABAP Proxies
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
More links for proxy:
proxies and performance...
Hope this help
Francesco

What is the perfect defference between AT NEW and ON CHANGE...

What is the perfect defference between AT NEW and ON CHANGE...?

hi vijay,
if u use 'at-new' statement , basically it dont pick first record of the itab where as 'on chage of' can pick from first record.
all these control brake statements can work with header line except 'on change of' event.
regards..
seshu.
Jogdand M B
Hi,
At New.
Effect
Beginning or end of a group of lines with the same content in the component comp1 comp2 ... and in the components to the left of comp1 comp2 .... The components comp1 comp2 ... can be specified, as described in the section Specification of Components, with the limitation that access to object attributes is not possible here.
Example:
LOOP AT itab result ...
    [AT NEW comp1.
     ENDAT.
endloop.
On Change of:
Effect:
The statements ON CHANGE OF and ENDON, which are forbidden in classes, define a control structure that can contain a statement block statement_block. After ON CHANGE OF, any number of data objects dobj1, dobj2... of any data type can be added..
Example:
In a SELECT loop, a statement block should only be executed if the content of the column CARRID has changed.
DATA spfli_wa TYPE spfli.
SELECT *
       FROM spfli
       INTO spfli_wa
       ORDER BY carrid.
ON CHANGE OF spfli_wa-carrid.
ENDON.
ENDSELECT.

Difference between At-new and on change of

Hi,
Can anyone send me the exact difference between At-new and On change of
Thank You
Santosh

Hi anjali,
I just entered your subject "difference between At-new and on change of" as search terms in the SEARCH FORUM input field.
Please check the results and come back after.
Difference between At new and On change of?
Posted on: 28.09.2006 19:01, by user: subhash soni -- Relevance: 100% -- Show all results within this thread
Hi What is the difference between At new and On change of? Thank You
difference between At-new and on change of
Posted on: 09.03.2007 20:16, by user: anjali nalluri -- Relevance: 89% -- Show all results within this thread
Hi, Can anyone send me the exact difference between At-new and On change of Thank You Santosh
Diff between AT new and on change of
Posted on: 30.11.2006 16:06, by user: Pavan Ravikanti -- Relevance: 53% -- Show all results within this thread
hi, can any one tell me what is the exact difference between AT new and on change of thanks pavan ...
Diff. between At New and On Change Of
Posted on: 05.10.2005 08:58, by user: surya mamtha -- Relevance: 48% -- Show all results within this thread
Hi, Could anybody exlain the difference between At New event and On Change Of event in detail? And how can we avoid the inner loops ...
Major Diff. Between On change of and At New
Posted on: 24.05.2006 12:48, by user: IFF -- Relevance: 46% -- Show all results within this thread
Hi Experts, Could you please let me know that what is the major difference between the control break statements On change of and At new. Which one is best to used ...
diff between at new and on change of
Posted on: 08.03.2007 16:27, by user: saroja ponnam -- Relevance: 44% -- Show all results within this thread
Hi all, what is the main diff between at new and on change of statements. Regards Saroja.
Differnce between AT NEW AND ON CHANGE OF
Posted on: 06.05.2006 10:55, by user: Raja Sekhar T -- Relevance: 44% -- Show all results within this thread
Hi, Differnce between AT NEW AND ON CHANGE OF Iam waiting foryour reply Thanks & Regards Raja Sekhar.T ...
Regards,
Clemens

Differnce between AT NEW AND ON CHANGE OF

Hi,
Differnce between AT NEW AND ON CHANGE OF
Iam waiting foryour reply
Thanks & Regards
Raja Sekhar.T

Hai Raja
check the following Documents
1. AT NEW f.
2. AT END OF f.
3. AT FIRST.
4. AT LAST.
5. AT fg.
Effect
In a LOOP which processes a dataset created with EXTRACT , you can use special control structures for control break processing. All these structures begin with AT and end with ENDAT . The sequence of statements which lies between them is then executed if a control break occurs.
You can use these key words for control break processing with extract datasets only if the active LOOP statement is proceesing an extract dataset.
The control level structure with extract datasets is dynamic. It corresponds exactly to the sort key of the extract dataset, i.e. to the order of fields in the field group HEADER by which the extract dataset was sorted .
At the end of a control group ( AT END OF , AT LAST ), there are two types of control level information between AT and ENDAT :
If the sort key of the extract dataset contains a non-numeric field h (particularly in the field group HEADER ), the field CNT(h) contains the number of control breaks in the (subordinate) control level h .
For extracted number fields g (see also ABAP/4 number types ), the fields SUM(g) contain the relevant control totals.
Notes
The fields CNT(h) and SUM(g) can only be addressed after they have been sorted. Otherwise, a runtime error may occur.
The fields CNT(h) and SUM(g) are filled with the relevant values for a control level at the end of each control group ( AT END OF , AT LAST ), not at the beginning ( AT FIRST , AT NEW ).
When calculating totals with SUM(g) , the system automatically chooses the maximum field sizes so that an overflow occurs only if the absolute value area limits are exceeded.
You can also use special control break control structures with LOOP s on internal tables.
Variant 1
AT NEW f.
Variant 2
AT END OF f.
Effect
f is a field from the field group HEADER . The enclosed sequence of statements is executed if
the field f occurs in the sort key of the extract dataset (and thus also in the field group HEADER ) and
the field f or a superior sort criterion has a different value in the current LOOP line than in the prceding ( AT NEW ) or subsequent ( AT END OF ) record of the extract dataset.
Example
DATA: NAME(30),
 SALES TYPE I.
FIELD-GROUPS: HEADER, INFOS.
INSERT: NAME INTO HEADER,
 SALES INTO INFOS.
LOOP.
AT NEW NAME.
 NEW-PAGE.
ENDAT.
AT END OF NAME.
 WRITE: / NAME, SUM(SALES).
ENDAT.
ENDLOOP.
Notes
If the extract dataset is not sorted before processing with LOOP , no control level structure is defined and the statements following AT NEW or AT END OF are not executed.
Fields which stand at hex zero are ignored by the control break check with AT NEW or AT END OF . This corresponds to the behavior of the SORT statement, which always places unoccupied fields (i.e. fields which stand at hex zero) before all occupied fields when sorting extract datasets, regardless of whether the sort sequence is in ascending or descending order.
Variant 3
AT FIRST.
Variant 4
AT LAST.
Effect
Executes the relevant series of statements just once - either on the first loop pass (with AT FIRST ) or on the last loop pass (with AT LAST ).
Variant 5
AT fg.
Addition
... WITH fg1
Effect
This statement makes single record processing dependent on the type of extracted record.
The sequence of statements following AT fg are executed whenever the current LOOP record is created with EXTRACT fg (in other words: when the current record is a fg record).
Addition
... WITH fg1
Effect
Executes the sequence of statements belonging to AT fg WITH fg1 only if the record of the field group fg in the dataset is immediately followed by a record of the field group fg1 .
Basic form
ON CHANGE OF f.
Addition
... OR f1
Effect
Executes the processing block enclosed by the " ON CHANGE OF f " and " ENDON " statements whenever the contents of the field f change (control break processing).
Normally, you use the statement to manipulate database fields during GET events or SELECT / ENDSELECT processing.
Note
There are special control structures for processing control breaks in LOOP s on internal tables or extract datasets AT ).
ON CHANGE OF is unsuitable for recognizing control levels in loops of this type because it always creates a global auxiliary field which is used to check for changes. This global auxiliary field can only be changed in the relevant ON CHANGE OF statement. It is not reset when the processing goes into loops or subroutines, so unwanted effects can occur if the loop or subroutine is executed again. Also, since it is set to its initial value when created (like any other field), any ON CHANGE OF processing will be executed after the first test, unless the contents of the field concerned happen to be identical to the initial value.
Example
TABLES T100.
SELECT * FROM T100 WHERE SPRSL = SY-LANGU AND
 MSGNR < '010'
 ORDER BY PRIMARY KEY.
ON CHANGE OF T100-ARBGB.
 ULINE.
 WRITE: / '**', T100-ARBGB, '**'.
ENDON.
WRITE: / T100-MSGNR, T100-TEXT.
ENDSELECT.
Displays all messages with their numbers in the logon language, provided the number is less than '010'.
Each time the message class changes, it is output.
Addition
... OR f1
Effect
Also executes the code whenever the contents of the field f1 changes.
You can use this addition several times.
Example
Logical database F1S
TABLES: SPFLI, SFLIGHT, SBOOK.
GET SBOOK.
ON CHANGE OF SPFLI-CARRID OR
 SPFLI-CONNID OR
 SFLIGHT-FLDATE.
 ULINE.
 WRITE: /5 SPFLI-CARRID, SPFLI-CONNID,
 5 SFLIGHT-FLDATE, SPFLI-FLTIME,
 5 SFLIGHT-SEATSMAX, SFLIGHT-SEATSOCC.
ENDON.
WRITE: / SBOOK-CUSTOMID.
The code between ON CHANGE OF and ENDON is executed only if at least one of the fields SPFLI-CARRID , SPFLI-CONNID or SFLIGHT-FLDATE has changed, i.e. there is a different flight connection (which also has bookings).
Notes
Thanks & regards
Sreenivasulu P

At new and on change of

Hi Friends,
can any one explain ,
1) what is main difference between at new and on change of
control break statements...
2) in which situation we are supposed use on change of control beark.
cheers,

Vijay ,
Control Break Event AT- NEW :
Event AT-NEW will be triggered whenever the control level changes or any field prior to the control level changes.
For Example:
DATA : BEGIN OF IT_TAB OCCURS 0,
A(5),
B(5),
C(5),
END OF ITAB.
Insert some Values to the internal table.
SORT IT_TAB.
LOOP AT IT_TAB,
AT NEW A.
<Only when value of A Changes.>
ENDAT
AT NEW B.
<When Combined vales of A & B Changes i.e either A or B Or both>.
ENDAT.
1) Sorting of the INTERNAL TABLE is necessary.
2) You cannot use multiple fields in AT-NEW statement.
3) Between AT-NEW and ENDAT the content of work area will not contain any value
4) If you change the value of a work area within AT-NEW and ENDAT your changes will be lost after the ENDAT statement.
5) When AT NEW occurs, the alpha-numeric fields have ******* in their value
6) Can be used in ABAP objects
ON-CHANGE-OF :
On Change of will be triggered whenever the control level changes.
It won't be triggered when the field prior to the control level change.
For Example:
DATA : BEGIN OF IT_TAB OCCURS 0,
A(5),
B(5),
C(5),
END OF ITAB.
Insert some Values to the Internal table.
LOOP AT IT_TAB,
On CHANGE OF B.
< Every time a value of B changes >
ENDON.
ENDLOOP.
1) Sorting of the INTERNAL TABLE is NOT necessary.
2) Mutilpe Fields are used in ON-CHANGE-OF
3) It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
4) In ON CHANGE,the alpha-numeric fields have their corresponding value, of that particular record, where the Event gets fired.
5) When used within a loop, a change in a field to the left of the control level does not trigger a control break.
6) You can use else between on change of and endon.
7) You can use it with loop at it where . . ..
8) cannot be used in ABAP objects
Regards,
Shiv.G.Sethu

In Reports what is the difference between the AT NEW and ON CHANGE Event

Hi,
Could you tell the differences of AT NEW and ON CHANGE events in Repors

Hi raghava,
The Major Difference is :
a) When AT NEW occurs,
the alpha-numeric fields have ******* in their value,
b) where as in case of ON CHANGE,
the alpha-numeric fields have their corresponding value,
of that particular record,
where the Event gets fired.
Other differences are :
ON CHANGE OF can be used any where in the program..
on change of differs from at new in the following respects:
1.It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
2.A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
3.When used within a loop, a change in a field to the left of the control level does not trigger a control break.
4.When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
5.You can use else between on change of and endon.
6.You can use it with loop at it where . . ..
7.You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
8.Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
while
AT NEW can be used only within a loop of an INTERNAL TABLE..
5. Sample program to get the taste of it
(just copy paste)
6.
REPORT ABC.
DATA : BEGIN OF ITAB OCCURS 0,
bukrs like t001-bukrs,
f1(10) type c,
end of itab.
itab-bukrs = '1000'.
itab-f1 = '1111111'.
append itab.
itab-bukrs = '1100'.
itab-f1 = '3333333'.
append itab.
itab-bukrs = '1200'.
itab-f1 = '555555'.
append itab.
AT NEW
loop at itab.
at new bukrs.
write :/ itab-bukrs , itab-f1.
endat.
endloop.
AT ONCHANGE
loop at itab.
ON CHANGE OF ITAB-BUKRS.
write :/ itab-bukrs , itab-f1.
ENDON.
endloop.

How to find out which users are using SharePoint Designer to make changes in SharePoint 2010 site?

Hi there,
How to find out which users are using SharePoint Designer to make changes in SharePoint 2010 site?
Thanks.

You need to enable auditing on SharePoint server and it will let you know, if someone makes any critical changes for the same.
Please walk through this informative KB to enable auditing on SharePoint :https://support.office.com/en-za/article/Configure-audit-settings-for-a-site-collection-f5a346d0-ee0f-4412-a5e6-d9b5abaa1012
Here is one more resource :
https://support.office.com/en-in/article/View-audit-log-reports-4293e8d5-4e7d-4201-b8ac-c8e63a100131
Moreover, if you wish to audit such critical changes automatically, you may consider on this comprehensive application (http://www.sharepointauditing.com/) that helps to track every changes on SharePoint into
real time and provides the captured data at granular level.

Difference btwn at new and on change of

Hi all,
can i know the difference between 'at new' and 'on change of'.

Hi,
at new - > means inside the loop, the new value.
eg :
1
1
2
3
4
5
5
loop at itab
at new matnr
write matnr.
end at.
end loop.
1
2
3
4
5
On change of -> chnage of particular value inside the loop.
The Major Difference is :
a) When AT NEW occurs,
the alpha-numeric fields have ******* in their value,
b) where as in case of ON CHANGE,
the alpha-numeric fields have their corresponding value,
of that particular record,
where the Event gets fired.
Other differences are :
ON CHANGE OF can be used any where in the program..
on change of differs from at new in the following respects:
1.It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
2.A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
3.When used within a loop, a change in a field to the left of the control level does not trigger a control break.
4.When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
5.You can use else between on change of and endon.
6.You can use it with loop at it where . . ..
7.You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
8.Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
while
AT NEW can be used only within a loop of an INTERNAL TABLE..
5. Sample program to get the taste of it
(just copy paste)
6.
REPORT ABC.
DATA : BEGIN OF ITAB OCCURS 0,
bukrs like t001-bukrs,
f1(10) type c,
end of itab.
itab-bukrs = '1000'.
itab-f1 = '1111111'.
append itab.
itab-bukrs = '1100'.
itab-f1 = '3333333'.
append itab.
itab-bukrs = '1200'.
itab-f1 = '555555'.
append itab.
AT NEW
loop at itab.
at new bukrs.
write :/ itab-bukrs , itab-f1.
endat.
endloop.
AT ONCHANGE
loop at itab.
ON CHANGE OF ITAB-BUKRS.
write :/ itab-bukrs , itab-f1.
ENDON.
Regards,
Ferry Lianto

Diff bt AT NEW and ON CHANGE OF

can any one explain me diff bt AT NEW and ON CHANGE OF
Thanks and regards,
venki..

Hi
Both will do the same function
ON CHANGE OF is not used much now-a-days.
see the sample for At new
All this AT NEW, AT FIRST, AT END OF and AT LAST are called control break statements of Internal tables and are used to calculate the TOTALS based on sertain key fields in that internal table
FIrst to use these statements the ITAB has to be sorted by the key fields on whcih you need the SUM of the fields.
Some time you will get * when mopving data from this int table to other table using these commands
so you have to use
READ TABLE ITAB INDEX SY-TABIX in AT..ENDAT..if you are using other fields between them
DATA: sflight_tab TYPE SORTED TABLE OF sflight
 WITH UNIQUE KEY carrid connid fldate,
 sflight_wa LIKE LINE OF sflight_tab.
SELECT *
 FROM sflight
 INTO TABLE sflight_tab.
LOOP AT sflight_tab INTO sflight_wa.
AT NEW connid.
 WRITE: / sflight_wa-carrid,
 sflight_wa-connid.
 ULINE.
ENDAT.
WRITE: / sflight_wa-fldate,
 sflight_wa-seatsocc.
AT END OF connid.
 SUM.
 ULINE.
 WRITE: / 'Sum',
 sflight_wa-seatsocc UNDER sflight_wa-seatsocc.
 SKIP.
ENDAT.
AT END OF carrid.
 SUM.
 ULINE.
 WRITE: / 'Carrier Sum',
 sflight_wa-seatsocc UNDER sflight_wa-seatsocc.
 NEW-PAGE.
ENDAT.
AT LAST.
 SUM.
 WRITE: / 'Overall Sum',
 sflight_wa-seatsocc UNDER sflight_wa-seatsocc.
ENDAT.
ENDLOOP.
Reward points for useful Answers
Regards
Anji

Difference between At new and on change statement?

What is the difference between at new and on change statement? Please explain with an example.

hi
on change of differs from at new in the following respects:
It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
When used within a loop, a change in a field to the left of the control level does not trigger a control break.
When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
You can use else between on change of and endon.
You can use it with loop at it where . . ..
You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
REGARDS
PRASANTH

AT NEW and AT CHANGE

Hi,
what is use of AT NEW and AT CHANGE.
When we will use it?
Akash

Hi Akash,,
Using the at new and at end of Statements
Use the at new and at end of statements to detect a change in a column from one loop pass to the next. These statements enable you to execute code at the beginning and end of a group of records.
sort by c.
loop at it.
at new c.
endat.
at end of c.
endat.
endloop.
where:
These statements can only be used within loop at; they cannot be used within select.
at new does not have to come before at end of. These statements can appear in any order.
These statements can appear multiple times within the same loop. For example, you could have two at new and three at end of statements within one loop and they can appear in any order.
These statements should not be nested inside of one another (that is, at end of should not be placed inside of at new / endat).
There are no additions to these statements.
Using at new
Each time the value of c changes, the lines of code between at new and endat are executed. This block is also executed during the first loop pass or if any fields to the left of c change. Between at and endat, the numeric fields to the right of c are set to zero. The non-numeric fields are filled with asterisks (*). If there are multiple occurrences of at new, they are all executed. at end of behaves in a similar fashion.
A control level is the component named on a control break statement; it regulates the control break. For example, in the following code snippet, f2 is a control level because it appears on the at new statement.
loop at it.
at new f2.
"(some code here)
endat.
endloop.
It is said that a control break is triggered if the control level changes. This means that when the contents of the control level change, the code between the at and endat is executed.
A control break is also triggered if any of the fields prior to the control level in the structure change. Therefore, you should define the internal table structure to begin with the fields that form your control levels. You must also sort by all fields prior to and including c.
Between at and endat, numeric fields to the right of the control level will be zero and non-numeric fields will be filled with asterisks.
The lines of code between at end of and endat are executed:
If the control level changes.
If any field prior to the control level changes.
If this is the last row of the table.
report Ztemp.
data: begin of it occurs 4,
            f1,
            f2,
            end of it.
it = '1A'. append it. "Fill it with data
it = '3A'. append it.
it = '1B'. append it.
it = '2B'. append it.
sort it by f1.
loop at it.
     at new f1.
         write: / it-f1, it-f2.
         endat.
     endloop.
skip.
sort it by f2.
loop at it.
     at new f2.
         write: / it-f1, it-f2.
         endat.
     endloop.
skip.
sort it by f1 f2.
loop at it.
     at new f1.
         write: / it-f1.
         endat.
     at new f2.
         write: /4 it-f2.
         endat.
     endloop.
free it.
If Found Help Full Do Reward.
Regards.
Eshwar.

Determining which PCA to use between new-GL and classic EC-PCA

I tried to use 1kek to transfer AR and AP from FI to PCA but failed with message saying "Document Splitting is Activated".
We are considering using PCA to make B/S and P/L of several business unit in a company. We are using SAP 6.0. After looking for the references, I understood that I can use new-GL or EC-PCA(classic PCA) for Profit Center Accounting. I wonder which way is the best and easiest one to achieve my company's object.
As I understood if I activate document splitting, it means I use new-GL for PCA, and I should use table FAGLFLEXA of FI instead of GLPCA of EC-PCA.
I'd like to use new-GL because it's "new" and convenient, hopefully. But I found several problems using new-GL to make financial reports.
The first problem was that I couldn't make allocation with accounts which cannot be manually input like AA accounts(Building, Machine, etc.), AR/AP or materials. When I operate transaction FAGLGA35, no effect occurs on those accounts.
And the second problem is that I couldn't find a way to make a report which has accounts list on its first column and profit center list on its first row. It's surely because I'm a newbie in SAP
I think everybody trying to use new_GL encounter this problem and it's wired because I couldn't find any thread about this.
And If I decide to use EC-PCA and make allocation on GLPCA, I think I should make some CBO to transfer AR/AP to EC-PCA. Is there any other possible solution?
I have a lot of things to ask but I'm not even sure what I know and don't.
Thanks for you guru's great help.

The following notes will help you in understanding the set up of PCA in New GL with Classic PCA (EC-PCA): OSS Norte no 826357
You want to know
For release SAP ERP, the Profit Center Accounting was integrated into the new G/L accounting. The solution is as follows:
SAP delivers the 'Profit Center' and the 'Partner Profit Center' as fixed characteristics that are posted on the original FI postings. The data is not updated in another ledger as in the classic Profit Center Accounting.
As a result of integration of the Profit Center Accounting into the new G/L accounting, new functions such as 'Document Splitting' are available. Using the function 'Document Splitting' (online document split), you can create balance sheets for company codes as well as for other entities such as the profit center. The balance is then set to 0 for each document for the profit center.
Integrating the G/L accounting and the Profit Center Accounting into the one application also removes the time and effort needed to reconcile G/L accounting and PCA.
When implementing the new G/L accounting in Release SAP ERP, we recommend that all new customers map the Profit Center within the new G/L accounting by activating the scenario FIN_PCA (profit center update). It is not advisable to activate the classic Profit Center Accounting in parallel and consequently update parallel data volumes.
Detailed information about setting Profit Center Accounting in the New General Ledger:
Define the update of the characteristics 'Profit Center' and 'Partner Profit Center' in the ledger by selecting the scenario 'Profit center update' (Customizing: Financial Accounting (New) -> Financial Accounting Basic Settings (New) -> Ledgers -> Ledger -> Assign Scenarios and Customer-Defined Fields to Ledgers).
If you want to use the document splitting, you can define the field 'Profit center' as a splitting characteristic in the document splitting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Business Transactions -> Document Splitting -> Define Document Splitting Characteristics for General Ledger Accounting). Set the 'Zero balance' indicator again for the added field 'Profit Center'. You can now create balance sheets on the profit center. You must also activate the Mandatory Field check to ensure that the profit center is set in all postings. If you want to display balance sheet items at profit center level (for example, receivables and payables) but you do not require complete balance sheets, we recommend that you do not set the indicator 'Zero balance' and 'Mandatory Field check'.
If you already used classic Profit Center Accounting as an SAP R/3 customer but you now want to use Profit Center Accounting in the new general ledger, you can continue to use classic Profit Center Accounting in parallel to the profit center update scenario in the new G/L accounting in the interim. However, we do not recommend you do this on a long-term basis due to the increased data volume and the increased time and effort required.
However, if the classic Profit Center Accounting continues to play a leading role for you, we recommend that you do not activate the document splitting in the new G/L accounting, and not for other entities such as the segment either. This is because the classic Profit Center Accounting uses certain functions of the classic general ledger that are no longer available with active document splitting (for example, transaction F.5D, Calculate Balance Sheet Adjustment).
See the following information for details about the differences between the function of PCA in new G/L accounting and in classic PCA and for details about the effects of new G/L accounting on the posting behavior in classic PCA. Even if mapped into new G/L accounting, PCA always occurs within a controlling area. SAP does not support cross-controlling area PCA. The derivation of profit center and partner profit center with the different business processes when you use the new G/L Accounting is identical to the classic Profit Center Accounting. Details about the differences are available in the following.
1. Set the proposal profit center for additional balance sheet and P&L accounts.
Release SAP ERP 2004:
 Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings.
 Profit center scenario in new G/L accounting and classic PCA is active: Transactions 3KEH and 3KEI are available in the classic Profit Center Accounting for maintaining a proposal profit center for balance sheet accounts and P&L accounts. Transactions 3KEH and 3KEI also exist in SAP ERP2004 and function in the same way as in R/3: In other words, you can use the settings in transaction 3KEH to control the update in classic Profit Center Accounting, and the transactions set a proposal profit center where necessary. Keep in mind that the profit center information is therefore affected in new G/L accounting by settings in classic Profit Center Accounting.
Release SAP ERP 2005:
 Transactions 3KEH and 3KEI (from classic Profit Center Accounting) for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
 Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings. In addition, the new transaction FAGL3KEH and the BAdI FAGL_3KEH_DEFPRCTR are available for maintaining proposal profit centers. You can use these new functions to determine a proposal profit center depending on the company code and the account. Note that this proposal profit center does not appear on the input screen; it is derived only when you post the document. The proposal profit center is used if the line item does not contain a CO account assignment and if the profit center was not already determined elsewhere.
 Profit center scenario in new G/L accounting and classic Profit Center Accounting are active: The entries of transaction 3KEH control ONLY the transfer of line items to classic Profit Center Accounting. Transaction 3KEI is no longer relevant. To set the profit center, use the options which are available in the new G/L accounting (make entries manually, use FI substitution, or implement the BADI AC_DOCUMENT).
2. Derivation of the partner profit center
Release SAP ERP 2004:
 Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT to set the partner profit center.
 Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL (reading purchase order/sales order for affiliated companies) are active. However, we recommend that you no longer use transaction 8KER or 8KES. Partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting.
Release SAP ERP 2005:
 Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT or the new BAdI FAGL_DEFPPRCTR (enhancement spot FAGL_LEDGER_CUST_DEFPRCTR) with the method SET_DEFAULT_PART_PRCTR to set the partner profit center.
 Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL are active. However, we recommend that you no longer use transaction 8KER or 8KES because partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting. Instead, if required, you should use the BAdI FAGL_DEFPPRCTR to set the partner profit center. A partner profit center determined in this way is always updated both in new G/L accounting and in classic Profit Center Accounting.
3. Displaying receivables and payables for each profit center
Document splitting is active
 The detailed information from the general ledger view about receivables and payables split online from the document splitting is NOT available for classic Profit Center Accounting. In this case, you CANNOT split receivables/payables nor follow-up costs subsequently (Transaction F.5D - report SAPF180A, Transaction F.50 - report SAPF181, Transaction F.05 - report SAPF100). This means that you CANNOT use transaction 1KEK to transfer receivables and payables to classic Profit Center Accounting. Follow-up costs split according to source can be transferred online to the classic Profit Center Accounting because these are already available in the data entry view.
 Read the documentation of the document splitting carefully. Analyze in which cases you have to set default account assignments because the document splitting is sometimes prevented by default account assignments.
Document splitting is not active
 In this case, you CANNOT display the receivables and payables according to source at profit center level within the new G/L accounting. However, you can use the old split of the receivables and payables within the classic Profit Center Accounting (transaction F.5D) as well as of the follow-up costs (transaction F.50), and you can use the periodic transfer of receivables and payables using transaction 1KEK. However, you can execute the new report for the foreign currency valuation of the open items (report FAGL_FC_VALUATION) with depreciation areas only, which means that the documents are no longer updated (valuation difference not updated in BSEG-BDIFF). As a result, transaction 1KEK copies only the original receivables/payables, independently of transaction 2KEM 'Account Valuation Differences'; in other words, the original data is not corrected by the valuation differences.
 You can use the standard report groups 8A98 and 8A99 to display the open receivables and payables in classic Profit Center Accounting.
4. Periodic transfers of asset portfolios to classic Profit Center Accounting
 As of Release 4. 7, it is possible to map a parallel reporting mapped in FI (for example, parallel accounts) for parallel depreciation areas in Asset Accounting by using particular settings (defining an accounting principle). You must stop the execution of transaction 1KEI because it would result in duplicated data in PCA because of postings to the same accounts. You must also stop transaction 1KEI with a 'different company code' or a 'different depreciation area in the different company code' because the data cannot be transferred correctly. Transaction 1KEI terminates with the error message KM 764. As of Release SAP ERP, if the new general ledger accounting is active, the system issues the message FAGL_LEDGER_CUST 076.
5. Dummy profit center on P&L accounts
 You use transactions 3KEH and 3KEI to firstly try to determine a proposal profit center in classic Profit Center Accounting for document line items with a P&L account (no cost element) and without a profit center account assignment. If the system does not find a proposal profit center, the dummy profit center is set for some activities (primarily from Logistics). If the new G/L accounting is active AND if at least one of the two characteristics 'Profit Center' and 'Segment' is used in the document splitting, the routine for setting the dummy profit center will no longer run (see Note 820121 and 832776). Otherwise the document splitting would not split a document, or not split it correctly. The system must then find the profit center that is valid for the process using the document splitting or another derivation. If this is not the case, the document line item will not be updated in the classic Profit Center (document line items with Profit Center initial are not allowed in the classic Profit Center Accounting).
6. PCA additional rows
 If you map Profit Center Accounting in new General Ledger Accounting in SAP ERP, you can use consulting note 937872 to update PCA additional lines recognized from classic Profit Center Accounting in new General Ledger Accounting.
 If you use the transfer price functions, you do not require Note 937872 because the structure of the PCA additional lines are technically "true" and are automatically posted in new General Ledger Accounting when maintained in transaction 0KEK.
7. Substitution of profit centers in sales orders
 Transactions 0KEL and 0KEM are available both in the classic Profit Center Accounting and in the new G/L accounting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Tools -> Validation/Substitution)
8. Reporting
Line item reporting within the new G/L accounting
 Release SAP ERP 2004: Even if document splitting is set with the characteristic Profit Center, only one restricted line item reporting to profit centers is available in this release at present. When you use the G/L account line item list of FI, you can limit profit centers for line item settlement G/L accounts that are not relevant for the document splitting. As of Support Package 10, line item reporting to profit centers and segments is available.
 Release SAP ERP 2005: Line item reporting according to profit centers and segments is available.
Ledger reporting within the new G/L accounting
 Release SAP ERP 2004: Even if the document splitting is set with the characteristic profit center or segment, no current account reporting to profit centers and segments is available up to Support Package 10. With Support Package 10, current account reporting according to profit centers and segments is available. Also see the detailed explanations for Release SAP ERP 2005.
 Release SAP ERP 2005: Current account reporting according to profit centers and segments is available. It replaces the standard report groups 8A98/8A99 in earlier releases. However, the difference is that the foreign currency valuation correction is no longer displayed for each item because no update of the valuation in items occurs through the foreign currency valuation in the new general ledger (no BDIFF/BDIFF2 update). It is a key date-related valuation (mostly for the period end).
9. Transfer prices
 The transfer price functions (multiple valuations) are available for new General Ledger Accounting as of SAP ERP 2005. For SAP ERP 2004, see the release restrictions in Note 741821. In SAP ERP 2004, you can use the transfer price functions or multiple valuation functions only if you have activated the classic General Ledger and classic Profit Center Accounting.
10. Creating the profit center standard hierarchy
Release SAP ERP 2004: You must create the highest node of the standard hierarchy in the Customizing of the classic Profit Center Accounting (transaction 0KE5), even if you are not using classic Profit Center Accounting.
Release SAP ERP 2005: To create the highest node of the standard hierarchy, use transaction SM30 with the maintenance view V_FAGL_PC_STHR.
11. Creating the dummy profit center
Classic Profit Center Accounting is active (regardless of whether classic G/L accounting or new G/L accounting is active):
 If the classic Profit Center Accounting is active, you must create a dummy profit center to avoid postings with an initial profit center in the database tables of the classic PCA.
 If the new G/L accounting is also active AND if you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting, you have to ensure in Release SAP ERP 2004 that Notes 820121 and 832776 are included. In Release SAP ERP 2005, the changed posting logic is included from the beginning. Note that the update of document line items in classic Profit Center Accounting is omitted because of this.
Classic Profit Center Accounting is not active, New G/L Accounting is active and you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting:
 You do not have to create and use a dummy profit center. Using the dummy profit center can cause situations you want to avoid: For example, the system splits receivables/payables to the dummy profit center because of the document splitting (you cannot transfer them manually), or a document line item with dummy profit center account assignment is not split by the document splitting. To ensure that a profit center is assigned in all rows, set the profit center as mandatory field in the Customizing of the document splitting. However, note that this can also lead to terminations while posting, if a profit center assignment is missing.
12. Compare G/L Accounts in FI with Profit Center Accounting (Transaction KE5T)
 In classic Profit Center Accounting, transaction KE5T is used to compare account balances. In this transaction, the ledgers to be compare are fixed. If you use Profit Center Accounting in new General Ledger Accounting, use the general transaction GCAC. You can enter any base ledger and any comparison ledger.

I have an Iphone 4s which I bought used, its unlocked and i put it on T-mobile. I see that the person who was using it before may have been Chinese, my computer is not recognizing it and itunes either. What can i do?

I want to Delete everything in it, but since it cannot be recognized by my computer and doesn't show on Itunes, I cannot do it. It has some a jailbreak which the last user put into it, might be Redsnow, and most of the app's and other stuff on the phone I cannot use it only says loading after I press it and then dissappears. The last user may have been Chinese, in which he put a chinese jailbreak and since i changed the language etc. of the iphone some things show up as little squares instead of normal english format. Please Help, Ive been looking all over google etc. and tried to fix it myself but nothing has worked.

I have the same problem with my 4S too, if the slider won't even let you slide, the it's most likely that the WiFi module inside the phone is broken
Take your phone to a Apple store and let them see if I'm correct
This is a common issue found only on 4S, Apple gave me a new 4S because of this

What is use of AT NEW and AT CHANGE

what is use of AT NEW and AT CHANGE

Using AT NEW
Use at new to detect a change in a column from one loop pass to the next. This statements enable you to execute code at the beginning of a group of records.
Syntax for the at new Statement
sort by c.
loop at it.
    at new c.
     endat.
    endloop.
where:
it is an internal table.
c is a component of it.
The following points apply:
This statements can only be used within loop at; it cannot be used within select.
at new does not have to come before at end of. It can appear in any order.
This statement can appear multiple times within the same loop. For example, you could have two at new and three at end of statements within one loop and they can appear in any order.
These statements should not be nested inside of one another (that is, at end of should not be placed inside of at new / endat).
There are no additions to these statements.
Each time the value of c changes, the lines of code between at new and endat are executed. This block is also executed during the first loop pass or if any fields to the left of c change. Between at and endat, the numeric fields to the right of c are set to zero. The non-numeric fields are filled with asterisks (*). If there are multiple occurrences of at new, they are all executed. at end of behaves in a similar fashion.
A control level is the component named on a control break statement; it regulates the control break. For example, in the following code snippet, f2 is a control level because it appears on the at new statement.
loop at it.
    at new f2.
        "(some code here)
        endat.
    endloop.
It is said that a control break is triggered if the control level changes. This means that when the contents of the control level change, the code between the at and endat is executed.
A control break is also triggered if any of the fields prior to the control level in the structure change. Therefore, you should define the internal table structure to begin with the fields that form your control levels. You must also sort by all fields prior to and including c.
Between at and endat, numeric fields to the right of the control level will be zero and non-numeric fields will be filled with asterisks.
Using ON CHANGE OF
Another statement you can use to perform control break processing is on change of. It behaves in a manner similar to at new.
Syntax for the on change of Statement
The following is the syntax for the on change of statement.
on change of v1 or v2 .
else.
endon.
where:
v1 and v2 are variable or field string names.
any number of or conditions might follow.
The following points apply:
If the value of any of the variables (v1, v2, and so on) changes from one test to the next, the statements following on change of are executed.
If no change is detected and else is specified, the statements following else are executed.
on change of differs from at new in the following respects:
It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
When used within a loop, a change in a field to the left of the control level does not trigger a control break.
When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
You can use else between on change of and endon.
You can use it with loop at it where . . ..
You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
When a loop begins execution, the system creates a global auxiliary field for each field named in an on change of statement contained by the loop. On creation, these fields are given default initial values (blanks or zeros). They are freed when the loop ends.
Each time on change of is executed, the contents of its fields are compared with the contents of the global auxiliary fields. If they are different, the on change of is triggered and the auxiliary fields are updated with the new values. If they are the same, the code within on change of is not executed
Because global auxiliary fields do not exist outside a loop, you cannot use on change of outside of a loop.
I hope it helps.
Best Regards,
Vibha
Please mark all the helpful answers

Which scenerio we use at new and on change....

Similar Messages

Maybe you are looking for