SAP Library - Find your answers

we are finding the problem at the time of put entries in vendor account, customer account and gl account. prbolem show when we want to save the data in same vendor account (fb60), gl acount (fb50). folowing problem show at the time of saving "balancing field "segment" in line item 001 not filled"

Thanks & Regards
Anmol Bhat
SAP ABAP Consultant




________________________________
From: "wilhiten@aol.com via sap-abap" <sap-abap@Groups.ITtoolbox.com>
To: anmol_extra <anmol_extra@yahoo.com>
Sent: Monday, 6 April, 2009 6:34:04 PM
Subject: Re: [sap-abap] SE30 - ABAP runtime analysis
Toolbox sap-abap
Rupesh,
Different requirements bound your code to different areas. You could
have code that has very simple logic, and thus Low ABAP but very large
amount of data returned from the database, and thus a high % DB. You
may have a company that requires a lot of security functions and has
really poor hardware, so that you are constantly having to wait for
update processes and low memory is slowing down context changes. This
will raise your system side. These are the "Bounds" of your
efficiency. Once you get down to these bounds, you can't go any lower.
You have to consider what your code is up against. So, if your DB
processes are minimal and your hardware is moderately good and your
spending significant effort processing the data, 55 ABAP, 25 DB, 20 SYS
is totally reasonable, but 40 ABAP, 40 DB, 20 SYS means that you've
written your SQL poorly or you need to think about getting some new index's.
In the simplest sense, it is hard to know the relative amounts of work
that you are requesting from each component. What you can say though is
that if you are looking at 10 ABAP, 80 DB, 10 SYS then improving your
ABAP code is not going to significantly change the runtime/efficiency of
your program. On the other hand, there could be a huge amount of gain
from rethinking how you are accessing the DB.
The SYS component is hard to manipulate. You can cut down on context
switching. You can look for limited resources that you may be bumping
into and try to avoid them. One of the best thnigs you con do (after
cutting down on context switches) is to try running it during system
idle time (when there are no users or large job loads). If the system %
doesn't drop then you are on your bound for the hardware you are using...
HTH,
Neal
Rosie Brent via sap-abap wrote:
>
>
> Personally Rupesh I would think that scenario two would be better. But
> I'd
> be interested to see what other developers think.
>
> Best Regards
>
> Rosie Brent
>
> From: Rupesh via sap-abap [mailto:sap-abap@Groups.ITtoolbox.com]
> Sent: 04 April 2009 09:36
> To: Rosie Brent
> Subject: RE:[sap-abap] SE30 - ABAP runtime analysis
>
>
>
> Thanks Neal,
> But for better performance which of the two(ABAP or system) needs to be
> maximum used. Database should obviously be left out as this would make
> the
> execution of the program sleep.
> For e.g : A given program takes -
> Scenario 1 -
> 13 % of Abap
> 35 % of Database
> 52% of System
> Scenario 2 -
> 42% of Abap
> 35 % of Database
> 23% of System
> Out of two scenario, which is better?
> Thank You,
> Regards,
> Rupesh __.____._