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
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_FIXEDASSET_CHANGE Change Documents

debbie_morrison
Explorer
0 Likes
1,337

I am uploading a spreadsheet and using BAPI_FIXEDASSET_CHANGE to update asset master records and everything is working well. However, if the same cost center is on the spreadsheet as in the master data, a change document is generated. If other data in the master record is the same, (description, etc.) nothing is changed and no change documents are generated. This only seems to happen with data in the timedependentdata structure.

If the data is the same and, in effect, no updates occurred, we do not want change documents to be created. Is there a way to turn this off??

1 ACCEPTED SOLUTION
Read only

mvoros
Active Contributor
0 Likes
893

Hi,

just guess but isn't the problem in dates. You use different from and to dates than are in the system so SAP takes it as change.

Cheers

I am uploading a spreadsheet and using BAPI_FIXEDASSET_CHANGE to update asset master records and everything is working well. However, if the same cost center is on the spreadsheet as in the master data, a change document is generated. If other data in the master record is the same, (description, etc.) nothing is changed and no change documents are generated. This only seems to happen with data in the timedependentdata structure.

If the data is the same and, in effect, no updates occurred, we do not want change documents to be created. Is there a way to turn this off??

3 REPLIES 3
Read only

mvoros
Active Contributor
0 Likes
894

Hi,

just guess but isn't the problem in dates. You use different from and to dates than are in the system so SAP takes it as change.

Cheers

Read only

0 Likes
893

Thanks, Martin. that is exactly what i suspect as well. Especially since this is the only structure of the BAPI that creates this behavior and it is the most date/time sensitive. I was hoping the BAPI was smart enough to realize that only date changes doesn't really constitute a change!

It looks like I may just have to read the data in before determining if it should be updated. Not that complex, just a pain!!! I was hoping someone out there knew something about this BAPI that I didn't!

Read only

0 Likes
893

I am suspecting this is happening bcoz of the "Change Document" setting for the data element's you are using...

for some which are recorded the changes have the Change document checkbox set at data element level, in further characteristics tab.