Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

AS91: master table for cumulative values - Asset Value Fields

Former Member

‎2009 Jul 30 12:25 PM

0 Likes
2,318

hi guys,

Asset master upload : tcode: AS91

I am able to upload the data with BAPI_FIXEDASSET_OVRTAKE_CREATE function module.

But my requirement is: one of the column for aseet value fields(AR = 10) in NON EDITABLE mode for Cumulative fields.

remaining two columns are AR=01 and AR15...WHICH ARE EDITABLE CS.

take over: cumulative table fields of BAPI (we can find the using code also)

when i provide the data for all the three columns, for third column,SAP is calculating itself (based on functional configuration, as it make non editable column) all the values.

when functional people enable the column by configuration, I am able to upload all the data properly.

But requirement is: functional people DONOT WANT to enable the column.(AR=10)

1)How can I upload the data to those non editable column fields. we have tried with BDC, LSMW, BAPI.

2)if want to update the DB table directly, as we could not find any option, what are the tables need to be uploaded?

I have gone thru ANLC Asset Value Fields. I can update this table.

are there any other tables, we need to update for legacy data upload ?

PLS HELP ME TO FIND THE TABLES, IF THERE IS NO SOLUTION AVAILABLE

TO THE ABOVE PROBLEM.

Edited by: puneindian on Jul 30, 2009 1:34 PM

hi guys,

Asset master upload : tcode: AS91

I am able to upload the data with BAPI_FIXEDASSET_OVRTAKE_CREATE function module.

But my requirement is: one of the column for aseet value fields(AR = 10) in NON EDITABLE mode for Cumulative fields.

remaining two columns are AR=01 and AR15...WHICH ARE EDITABLE CS.

take over: cumulative table fields of BAPI (we can find the using code also)

when i provide the data for all the three columns, for third column,SAP is calculating itself (based on functional configuration, as it make non editable column) all the values.

when functional people enable the column by configuration, I am able to upload all the data properly.

But requirement is: functional people DONOT WANT to enable the column.(AR=10)

1)How can I upload the data to those non editable column fields. we have tried with BDC, LSMW, BAPI.

2)if want to update the DB table directly, as we could not find any option, what are the tables need to be uploaded?

I have gone thru ANLC Asset Value Fields. I can update this table.

are there any other tables, we need to update for legacy data upload ?

PLS HELP ME TO FIND THE TABLES, IF THERE IS NO SOLUTION AVAILABLE

TO THE ABOVE PROBLEM.

Edited by: puneindian on Jul 30, 2009 1:34 PM

Reply
4 REPLIES 4
Read only

RaymondGiuseppi
Active Contributor

‎2009 Jul 30 12:37 PM

0 Likes
1,282

So functional requires

- column must not be editable

- column must be edited

You are in trouble with this paradox, if you find a way to fulfil requirement, send an OSS message, you find a gap in system security.

For database tables, look via SE36 at ADA logical database,

But,

If you update tables via open SQL statements, what will happen at first Depreciation Run, at first Year-End Closing, you wont be able to use Asset accounting in two years (previous year must be closed to open next year) , also there is a 99% chance that SAP reports will not care to your records, ANLC does not have records for derived depreciation area (there is nowhere to store this data...)

So, go to functionnals and request two new depreciation areas, one for this legacy amount and another for the delta with the derived one, with a customizing if required to generate some postings in accounting....

Go to forum to ask for this.

Regards,

Raymond

Read only

Former Member
In response to RaymondGiuseppi

‎2009 Jul 30 1:21 PM

0 Likes
1,282

Raymond,

Thank you verymuch for useful information.

I have one question: Even though one column is non editable, we could able to upload the data succesfully to SAP, except the non editable column. non editable fields are updated by SAP based on other colums.

now data available in SAP.

We are only planning to CHANGE(update) those non editable fields through OPEN SQL. (fields only 3 in non editable). Means, we are overwriting the existing data with our data.

will it be a problem?

Read only

RaymondGiuseppi
Active Contributor
In response to RaymondGiuseppi

‎2009 Jul 30 1:56 PM

0 Likes
1,282

You must be very careful, as this can put the database in a state beyond repair

(at least without new debug or open sql update executions...)

First, do it in a sandbox with a handful of assets, execute at least two depreciation runs and some transfers, retirements and sales of assets with a "wild" change (before, between and after depreciation runs) - Check accounting documents generated, check depreciation area values.

Then if all has good performed, execute a year end closing run to insure that you wont get a blocking error.

Remember that if the field is locked (transaction and BDC as well as direct input or BAPI) SAP should better have a reason for that.

Also "calculated" fields are not-input ready, cause they sometimes don't even exist in database and are dynamically generated by SAP program just before display takes place. (Most reports wont even try to read them in database, some will be "disturbed" by finding them)

Expect long tests in qualification.

Regards,

Raymond

Read only

Former Member

‎2009 Sep 10 12:11 PM

0 Likes
1,282

it is not possible to develop this thru programatically. Functionals should uncheck them and then only we can meet the requirement.