RE-FX Legacy data migration using BUS1505_CREATE

[stephen_long]

Hello Community,

Does anybody have experience of using the BAPI BUS1505_CREATE via LSMW to create RE-FX lease contracts?

I'm receiving an error relating to this part of the structure E1BP_RE_TERM_CE_DAT - the error message 'BAPI Error occured during processing of table/field TERM_EVALUATION

I've tested the underlying BAPI BAPI_RE_CN_CREATE and this successfully creates a contract although I had to create asset master and provide the asset id in the field just as 'assetid' - the field handling appears different using the BUS1505_CREATE I'm not sure if asset needs to be nnnn/assetid/0 (this is how it is populated using BAPI_RE_CN_GET_DETAIL)

nnnn = company code

assetid = asset master

0 = sub asset

Anyone with experience of using this BAPI please get in touch - thank you

Steve

[stephen_long]

Ok I resolved this - for lease contracts BUS1505_CREATE04 use the following segments:

E1BUS1505_CREATE - Header

E1BP_RE_CONTRACT_DAT - core contract data

E1BP_RE_TERM_OA_DAT - Org assignment

E1BP_RE_TERM_PY_DAT - Posting terms (assign tax type/tax group, payment data if using RE-FX to trigger lease creditor payments)

E1BP_RE_TERM_RH_DAT - Frequency Term - so you can specify a term for Qtrly a term for Monthly etc)

E1BP_RE_PARTNER_DAT - to assign the business partner (lessor)

E1BP_RE_OBJECT_REL_DAT - create contract objects, assgin object type, account assignment

E1BP_RE_CONDITION_DAT - contract conditions

E1BP_RE_TERM_CE_DAT - valuation rule

I had mistakenly included some empty segments based on the output from BAPI_RE_CN_GET_DETAIL, once I removed those segments from the structure relationships the BAPI worked - there are many constants I have included, also important to include constants within E1BP_RE_TERM_CE_DAT for STATUS_VALUATION_RULE = C and STATUS_VALUATION = C

then once the contracts are loaded one can use RECEEP to post the valuations on mass

[stephen_long]

Hi Hitesh,

Thanks for the advice - at this stage I'm just trying to get the bapi to work.

With regard to automatic asset creation I have had to add message AIST-001 into OBA5 else asset creation was failing even in RECN transactoin due to useful life field for non-leading depn area not being changable (which it should not, it should be inherited from leading Depn area)

I've removed asset_Object_id from the source and field mappings now - annotation-2020-07-17-102941.png Should I also remove Asset_object_type = AN?

Bapi is complaining that Object ID was not entered

Do you have any documentation or know of resources which I can reference for this BAPI?

Thanks

[former_member441136]

HI Steve,

You will have to give values in 2 fields.

ASSET_OBJECT_TYPE >>> AN

ASSET_OBJECT_ID >>>> Co.code Asset No. Sub no. >>> 0010 500015 0

Why you are giving the Asset no. manually, system would create automatically.

Regards,

Hitesh