LSMW for Asset Data (Tcode-AS01)

Hello All,
I am working on LSMW for Asset master data creation for transaction AS01. When i go to tcode AS01 there is a field with description called "NUMBER OF SIMILAR ASSETS". The LSMW program for the asset data uses two structures BALTD and BALTB. But the field description field is not available in these stuctures. So i am not able to create asset data through t code AS01.
Can anybody help me out. I will reward you with points.
Thanks,

Hi,
The number of similar assets
enables you to create multiple similar assets in one master transaction. These assets initially differ from each other only by their main and/or sub-number. When you save, you can also enter a description and inventory number for each individual master record.
This function does not allow you to create multiple assets that automatically have the same long text.
In order to work with lsmw you are creating asset in reference to old asset number/subnumber. i think the default number of assets are 1. in case you require more assets to be created of same type you may have to pass different long texts.
Reward if find useful.

Similar Messages

When we have LSMW for migrating data then why we will go for Session/Call ?

Hi Guru's,
Could you please tell me ...
When we have LSMW for migrating data , why will go for Sessions/call Transaction for migrating? when we do with LSMW we can complete the object with less time then why we have will do with session/call transaction?
when we have to use LSMW ? and when we have to use SESSION/ CALL TRANSACTION ..
thanks in advance..
vardhan

LSMW can't upload large amount of data into the database.
Whereas BDC SESSION CALL /TRANSACTION method can upload large amount of data into the database.
The error capture method is superior in BDC.
BDC programs can be scheduled to run on periodic basis as per the customer requirements.

Bapi for asset deletion (Tcode AS06)

Hi Guys,
Do we have any BAPIs for asset deletion (Tcode: AS06) ? Pls. let me know .
Thanks and Regards,
Sumit

There is no BAPI for it: just for creation, change, get list and detail.
I had the same doubt and then I tried FM AM_ASSET_DELETE_FROM_AI but it asks for a "AI_ID" which I don't have during execution time.
If possible, do a Batch Input to AS06 as it is very simple.

LSMW for Asset Creation not creating Transaction

Hi,
I am using standard LSMW for creating Asset into the SAP system and passing transaction code as AS91.
Object: 0160
Method: 0001
Program Name: RAALTD01
Program Type: B
The asset is getting created, but even after passing the Transaction Data (Structure BALTB), with T-Code AS91, it is not creating the transaction record into Asset.
Any solution / work around for this?
Thanks & Regards,
Sandip kamdar

try with recording method, i had done this for same tcode and sucessfully completed the job.

LSMW for master data & transaction data

Hello Experts,
We have master data :
1)Material
2)Vendor
and
Transaction data
3)Open PR
4)Open PO
5)Stock Posting
Can we use LSMW for all these?
Or which one is recommended for each one of them...
Whether BDC or LSMW recommended ?
Kindly suggest...
Regards
Mahesh

alternativ you can use standard reports:
RFBIKR00 fpr vendors
RMDATIND for material
RM06BBI0 FOR PR
RM06EEI0
RM06EEI1
RSTXLITF
for PO
and RM07MMBL for material (transaction data)
hope that helps
Andreas

LSMW for master data

Is LSMW used mainly for master data transfer? if yes, what can b the reason for this?
About BDC, is it used both for master data, transaction data,right?

Hi,
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP
systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be
imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data
migration object" in an entry or change transaction.
In LSMW have source and target field mapping. so that data should not be lost.
Regards,
Boobalan Suburaj

MATERIAL DOCUMENTS FOR POSTING DATE TCODE ?

HI ALL,
CAN SOMEBODY GIVE ME THE MATERIAL
DOCUMENTS FOR POSTING DATE TRANSACTION CODE.
THANKS,
KSR

Hi all,
For dispaly of Material Document we have Transaction Code : MB03,
this with the Document No & Year,
like wise for dispaly of Material Document for a date range i want to know the Tranasction Code.
Thanks

LSMW for uploading data in MM01

Hi,
       I have never used LSMW.I have to upload data for material master for MM01 Fields are MATNR MTART LGORT MEINS etc from MARA MARC and MAKT table.I have the records in text file for uploading.
                  Could you please tell me which step will be good?
Direct i/p I do not want to use.
Batch i/p recording-Please explain me step while recording in MM01.
IDOC which msg type to be used and also port no details.
BAPI Which BAPI should be used?
Rgds,
Rag

use LSMW BAPI method
Business Object      BUS1001006   Standard material
Method               SAVEDATA                    Create and change materia
Message Type         MATMAS_BAPI                 Create and change materia
Basic Type           MATMAS_BAPI02               Create and Change Materia

Error in asset data migration thru LSMW

Hi u all,
i have an issue while running an lsmw for asset data loads here, when i did it in foreground it saves the asset but when i run it in background its erring out
i am doin it thru as91 whichis legacy transfers the error is
Field RALT_DYNP_STRUC-ANBTR02(7) is not an input field AS91 1 SAPLALTD 1100 14 S 00 347
Field RALT_DYNP_STRUC-ANBTR03(7) is not an input field AS91 1 SAPLALTD 1100 14 S 00 347
this ANBTR02(7) n ANBTR03(7) are the *** spl dep fields for TAX and AMT in the takeover values tab,where we were giving the values of spl dep (Bonus value which is taken off in the acquisition yr)
all is goin good in foreground but its giving the error whichi pasted above saying ..is not an input field, when i did it in background not able to figure out...
Any help would be really grateful and appreciated......Thanka a lot in advance.

Hi Nathan,
as i mentioned earlier, it goes smooth when it is done manually or lsmw foreground, and answering to ur ques'n yes the fields are open. i am getting the error when i do it in batch input....
Thanks ya
Jay

Asset Tables for legacy data takeover

Dear Friends
We've to take assets data from one client to another and hence would be using Legacy assets.
Could you please let me know from which tables / reports i should extract the data related to master & transaction data from the legacy system which is also on SAP.
ANLA - master data and to take those assets which are not deactivated
ANLB
ANLC - asset accumulated APC & dep. And current yr dep
ANLZ - dep terms data
ANEP - asset transaction data for current year acquisitions
I dont have the system in from of me and i hope the above tables are correct.
1. Please let me know if other tables are required?
2. Should the dep area data be posted with remaining useful life & expired life in legacy asset?
Regards
Kapil

Hello Kapil,
I invite you to carefully review the attached SAP notes which should
provide you with the necessart answer:
68802   Legacy data trnsfr: diff.fields n.ready f.input
550176 FAQ note legacy data transfer asset master records
373894 Collective note: introdctn to prblm solutn in FI-AA
Further I also attach the following 6 notes that provide further
informative details regarding legacy transfer, and also some specific
only for legacy transfer during the year:
729164 AS91/AS92: Incorrect ready for input status for prop. values
29706   AS91/92/94: Dep. area fields not ready for input
4206    Net book value input at old data transfer
50607   Depreciation during old assets data takeover
26240   Reconciliation of posted depreciat. after takeover
For further information, please review the information for asset data
transfer in the R/3 Library:
FI-AA - Assets -> Legacy Data Transfer -> Special Considerations for
Asset Data Transfer -> Time of Transfer...
thanks and regards
Ray

LSMW While importing data

Hello, I'm using LSMW for transfering data, But I got an error on step 9. Import Data.
I can't read error message text because it's not readable (shows in a wrong encoding,)
The error doesn't occur everytime. I use the same file but run it in a different period of time. I don't know the reason of that error.
I know it's may be not enough info to solve my problem. But if someone was confronted with that pls notify me,
Thanks.
Edited by: kernel.panic on Sep 28, 2009 12:07 PM
link to the error: http://s53.radikal.ru/i140/0909/e5/5a937bff1451.jpg

no matter which codepage I am using.
for example: when I specify input file to disk H: although my file is on disk C; I got the same error.
I've launched debugger and found the line with error:
FORM write_header_record.
    CLEAR gs_lsheader.
    gs_lsheader-lsmw = 'LSMW'.
    gs_lsheader-project = g_project.
    gs_lsheader-subproj = g_subproj.
    gs_lsheader-object = g_object.
    gs_lsheader-systemid = sy-sysid.
    gs_lsheader-client = sy-mandt.
    gs_lsheader-datum = sy-datum.
    gs_lsheader-uzeit = sy-uzeit.
    gs_lsheader-uname = sy-uname.
* Begin: binary write
    g_record_length = STRLEN( gs_lsheader ).
    g_hex_record_length = g_record_length.
    TRANSFER g_hex_record_length TO g_filename. // AT THIS LINE ERROR OCCURS
    ASSIGN g_max_buffer(g_record_length) TO <g_buffer>.
    <g_buffer> = gs_lsheader.
    TRANSFER <g_buffer> TO g_filename.
* End: binary write

LSMW for AS01

Dear experts,
We are trying to upload asset master (T-Code AS01)thru LSMW.We tried to upload data thru BDC which is working fine. But in LSMW we are getting error at the time of conversion of data. LSMW is working fine for all others like material master upload, vendor master upload etc.
We can not use T Code AS91, because actual legacy date has been frozen in the system.
I want to know whether AS01 creation is possible thru LSMW or not? If yes, what could be the reason that its working for other master data and not for asset? Could it be because for Asset creation, internal number is generated and for other master data, external numbering is there?
I will be extremely grateful to receive any input from you.
expecting a quick reply,
Vijaya

Dear all,
Thanks a lot for reply. In my case I am getting the error that transaction code is not set. In step 5, maintain field mapping and conversion rule, I select the field TCODE, then I click on rule, then click on constant.There when i drill down , the transaction AS01 is not appearing but other transactions AS91, AS92 etc. is appearing.
Even then when I am typing tcode AS01, then the above mentioned error is coming at the time of conversion.
For material master and all, this drill down option is not coming. so whichever tcode I am giving , system is taking that.
Can u let me know, where should I maintain Tcode AS01.
Thanx,
Vijaya

LSMW for PA40 Tcode

Hi all,
I have created a LSMW for the Tcode PA40 to upload the employees data for the initial infotypes 0000,0001,0002.   The record uploaded successfully. But the employees no. is generated by skipping one dummy no.
For example, if 2 records I am uploading means,
Employee no.
1006455    -   Uploaded succes
1006456    -   skipped
1006457   -    Uploaded.
How to stop the employee no. skip as dummy.
Regards,
Raj

Yes Mr. Raj,
In the case of uploading, or when doing the cut-over activity the numbers ranges must be kept in External Range.
Once the system goes live you can keep it as internal.
Regards
Venu

Lsmw for fixed asset

Hi All,
I am uploading data for fixed assets using LSMW with bapi -
business object - BUS1022
Method - FIXEDASSET_CREATEINCLVALUES
Message Type - FIXEDASSET_CREATEINCLVALUES02
According to project settings group asset and group asset subnumber are mandatory fields for depreciation area 15. When i am running the lsmw i am getting the error
"DEPRECIATIONAREAS-GRP_ASSET ("Group asset") is a required entry field in depreciation area 15. The field was not supplied with data when the BAPI was called."
Please help me how to solve the problem...
I am copying the lsmw for which group asset and group asset sub number were not included and i am adding those two fields in my lsmw and i am not able to upload the data because of the error. Previously these two fields were not mandatory and LSMW was working fine.
Thanks,
Govinda

Hi Govinda,
                  Please try with the following code , if it is useful then please allocate points to me
*& Report ZASSET_CREATE
REPORT zasset_create.
DATA:
   input parameters to the bapi
    input_key       LIKE bapi1022_key,
    gen_data        LIKE bapi1022_feglg001,
    gen_datax       LIKE bapi1022_feglg001x,
    posting_info    LIKE bapi1022_feglg002,
    posting_infox   LIKE bapi1022_feglg002x,
    posting_data    LIKE bapifapo_gen_info,
    acquis_data     LIKE bapifapo_acq,
    time_dep_data   LIKE bapi1022_feglg003,
    time_dep_datax LIKE bapi1022_feglg003x,
    real_estate     LIKE bapi1022_feglg007,
    real_estatex    LIKE bapi1022_feglg007x,
    allocations     LIKE bapi1022_feglg004,
    allocationsx    LIKE bapi1022_feglg004x,
    extensionin     TYPE TABLE OF bapiparex,
    origindata      LIKE bapi1022_feglg009,
    origindatax     LIKE bapi1022_feglg009x,
it_depreciationareas TYPE TABLE OF bapi1022_dep_areas,
wa_depreciationareas TYPE bapi1022_dep_areas,
                 occurs 0 with header line,
it_depreciationareasx TYPE TABLE OF bapi1022_dep_areasx,
wa_depreciationareasx TYPE bapi1022_dep_areasx,
                 occurs 0 with header line,
it_investment_support TYPE TABLE OF bapi1022_inv_support,
                 occurs 0 with header line,
output parameters from the bapi
    asset_number    LIKE bapi1022_1-assetmaino,
    sub_number      LIKE bapi1022_1-assetsubno,
    out_return      LIKE bapiret2,
    out_return2     LIKE bapiret2.
input_key-companycode = 'CAT1'.
gen_data-assetclass   = '00003000'.
gen_datax-assetclass = 'X'.
gen_data-descript = 'Testing BAPI'.
gen_datax-descript   = 'X'.
gen_data-serial_no    = '1111'.
gen_datax-serial_no = 'X'.
gen_data-base_uom     = 'KG'.
gen_datax-base_uom   = 'X'.
*Append the Depreciation keY VALUE EQUAL TO LINA to the internal table.
wa_depreciationareas-area = '01'.
wa_depreciationareas-descript = 'Book deprec.'.
wa_depreciationareas-dep_key = 'LINA'.
wa_depreciationareas-ulife_yrs = '2'.
wa_depreciationareas-ulife_prds = '3'.
wa_depreciationareas-exp_ulife_yrs = '5'.
wa_depreciationareas-exp_ulife_prds = '3'.
*wa_depreciationareas-EXP_ULIFE_SDEP_YRS
*wa_depreciationareas-EXP_ULIFE_SDEP_PRDS
*wa_depreciationareas-ORIG_ULIFE_YRS
*wa_depreciationareas-ORIG_ULIFE_PRDS
wa_depreciationareas-change_yr = '3'.
*wa_depreciationareas-dep_units = '3'.
*wa_depreciationareas-odep_start_date = '01012005'.
*wa_depreciationareas-sdep_start_date = '01012005'.
*wa_depreciationareas-INTEREST_START_DATE
*wa_depreciationareas-READINESS
*wa_depreciationareas-INDEX
wa_depreciationareas-AGE_INDEX
wa_depreciationareas-var_dep_portion = '200'.
wa_depreciationareas-scrapvalue = '20'.
*wa_depreciationareas-currency = 'USD'.
*wa_depreciationareas-currency_iso = 'USD'.
*wa_depreciationareas-NEG_VALUES
*wa_depreciationareas-GRP_ASSET
*wa_depreciationareas-GRP_ASSET_SUBNO
*wa_depreciationareas-ACQ_YR
*wa_depreciationareas-ACQ_PRD
*wa_depreciationareas-SCRAPVALUE_PRCTG
APPEND wa_depreciationareas TO it_depreciationareas.
CLEAR: wa_depreciationareas.
wa_depreciationareasx-area = '01'.
*wa_depreciationareasX-DESCRIPT = 'X'.
*wa_depreciationareasX-DEACTIVATE = 'X'.
wa_depreciationareasx-dep_key = 'X'.
wa_depreciationareasx-ulife_yrs = 'X'.
wa_depreciationareasx-ulife_prds = 'X'.
*wa_depreciationareasX-EXP_ULIFE_YRS = 'X'.
*wa_depreciationareasX-EXP_ULIFE_PRDS = 'X'.
*wa_depreciationareasX-EXP_ULIFE_SDEP_YRS = 'X'.
*wa_depreciationareasX-EXP_ULIFE_SDEP_PRDS = 'X'.
*wa_depreciationareasX-ORIG_ULIFE_YRS = 'X'.
*wa_depreciationareasX-ORIG_ULIFE_PRDS = 'X'.
wa_depreciationareasx-change_yr = 'X'.
*wa_depreciationareasx-dep_units = 'X'.
wa_depreciationareasx-odep_start_date = 'X'.
wa_depreciationareasx-sdep_start_date = 'X'.
*wa_depreciationareasX-INTEREST_START_DATE = 'X'.
*wa_depreciationareasX-READINESS = 'X'.
*wa_depreciationareasX-INDEX = 'X'.
*wa_depreciationareasX-AGE_INDEX = 'X'.
wa_depreciationareasx-var_dep_portion = 'X'.
wa_depreciationareasx-scrapvalue = 'X'.
*wa_depreciationareasx-currency = 'X'.
*wa_depreciationareasx-currency_iso = 'X'.
*wa_depreciationareasX-NEG_VALUES = 'X'.
*wa_depreciationareasX-GRP_ASSET = 'X'.
*wa_depreciationareasX-GRP_ASSET_SUBNO = 'X'.
*wa_depreciationareasX-ACQ_YR = 'X'.
*wa_depreciationareasX-ACQ_PRD = 'X'.
*wa_depreciationareasX-SCRAPVALUE_PRCTG = 'X'.
APPEND wa_depreciationareasx TO it_depreciationareasx.
CLEAR wa_depreciationareasx.
*Append the Depreciation keY VALUE EQUAL TO LINb to the internal table.
break mukherar.
CALL FUNCTION 'BAPI_FIXEDASSET_CREATE1'
EXPORTING
    key                        = input_key
REFERENCE                  =
CREATESUBNUMBER            =
POSTCAP                    =
CREATEGROUPASSET           =
TESTRUN                    =
   generaldata                = gen_data
   generaldatax               = gen_datax
INVENTORY                  =
INVENTORYX                 =
POSTINGINFORMATION         =
POSTINGINFORMATIONX        =
TIMEDEPENDENTDATA          =
TIMEDEPENDENTDATAX         =
ALLOCATIONS                =
ALLOCATIONSX               =
ORIGIN                     =
ORIGINX                    =
INVESTACCTASSIGNMNT        =
INVESTACCTASSIGNMNTX       =
NETWORTHVALUATION          =
NETWORTHVALUATIONX         =
REALESTATE                 =
REALESTATEX                =
INSURANCE                  =
INSURANCEX                 =
LEASING                    =
LEASINGX                   =
IMPORTING
COMPANYCODE                = company_code
   asset                      = asset_number
   subnumber                  = sub_number
ASSETCREATED               =
   return                     = out_return
TABLES
   depreciationareas          = it_depreciationareas
   depreciationareasx         = it_depreciationareasx.
INVESTMENT_SUPPORT         =
EXTENSIONIN                =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT          =
          IMPORTING
            RETURN        =
WRITE: / 'Asset Number:',asset_number.

Document date is earlier than acquisition date for asset

Client has an asset which they want to post an acquistion for as of 1/1/2011. They are in December of 2011. They first put an acquisition in with 12/31/2011 and then cancelled it, realizing they needed a docdate of 1/1/2011. When they try to redo the acquisition with a docdate of 1/1/2011 they get the error "Document date is earlier than acquisition date for asset xxxxx"
The capitalization date on the asset is 1/1/2011. I looked at the acquisition date (thorugh SQL) and it is "1899-12-30 00:00:00.000"
Does anyone know why it is preventing from posting?
(Posting dates allowed are 1/1/11-12/31/11 for period 12 of 2011 and the period is unlocked)
Alan

Hi
I do believe that the problem is in the capitalization date 12/31/2011
Even if you have cancellled the first acqusition , and the acquisition date has taken the dummy date that assets have when there are no acqusitions 1899-12-30 00:00:00.000
Still the capitalization date remains 12/31/2011
and this will deter any transactions earlier than 12/31/2011
My question is,
can you still edit the field capitalization date?
Jose Antonio Castillo

LSMW for Asset Data (Tcode-AS01)

Similar Messages

Maybe you are looking for