0ASSET_AFAB_ATTR

0ASSET_AFAB_ATTRDepreciation Area Real or Derived

This datasource has Assets based on Depreciation Area

Base Tables

ANLB.

This datasource has both real and derived depreciation areas ( eg: 93 and 91 are derived, I guess. They are not in ANLC)

Calculating expired useful life

When a asset is created, the number of useful life years and months is also decided. There will also be start date for the depreciation. 

Useful Life is present in table ANLB-NDJAR/NDPER (Planned useful life in years/periods). Once the asset start depreciating , the useful years also decrease.

Expired useful life is saved in table NDABJ/NDABP (Expired useful life in years at start of the fiscal year/period)

This can also be calculated as follows.

Expired life in years = (Present Fisc Year - 1) - (Year from Start of Depreciation date)

Expired life in months = ( Period of the fiscal year from which Start of Depreciation is starting ) - ( Period of Start of Depreciation period)

Refer Notes :

https://www.linkedin.com/pulse/asset-accounting-data-extraction-important-steps-learning-patil

0ASSET_AFAB_TEXTDepreciation Area Real or Derived

Only FULL load is possible for this datasource.

Asset Management

TCode
AS01 / 02 / 03

Asset Explorer
AW01N

CRM T-Codes

CRMD_ORDER

2LIS_03_BF/BX

Inventory

Deleting Setup Tables : LBWG(03)

Filling Setup Tables    : OLI1BW
Setup Table Job           : RMCBNEUA

Tables
MKPF
MSEG

TCodes
MB01/02/03



SAP Notes
492828 - Determining the transaction key for 2LIS_03_BF + 2LIS_03_UM

2LIS_06_INV

Filling Setup Tables : OLI6BW
Delete Setup Tables : LBWG - Application 06
Setup Table : MC06M_0ITMSETUP

When running setup tables, the selection screen parameters are mandatory, even  the screen doesn’t say so.

With out the selections the job would give the error

Enter Doc number, Year and Comp Code and run the setup tables. It ran fine few times, but twice I had duplicate error. So I deleted the setup tables (LBWG) and ran them again with only Doc Number and Year.

My Notes:

This datasource is used to get the invoiced data. The requirement is to replicate 'MB5S' tcode from ECC. Users wanted the data from EKBE table which shows Invoiced Quantities BEWTP = Q and 'E' delivered quantities.

The entries from EKBE with BEWTP = 'Q' can be extracted using this datasource, given that we extract records where EBELN, MENGE,MATNR are not inital (my assumption and it worked fine).

The BEWTP = 'E' is extracted from 2LIS_03_BF.

Issues:

• Difference in amounts of MSEG-DMBTR and EKBE-DMBTR
• EKBE table has Purchase Order History data and MSEG has Document Segment: Material data in it. When using a Join of 2LIS_03_BF ( for Good Movement (E) from MSEG data ) and 2LIS_06_INV ( for Invoice (Q) from EKBE data ) ; In general the DBMTR is same in MSEG and EKBE, but there are few scenarios when they are different. Below is the explanation.
• http://scn.sap.com/thread/1895345
• For the below example the $0 value in MSEG is due to the fact that the std price for that material in table MBEW is $0 - this is the value that would post to inventory.  The value that appears in EKBE for where value = "E" is the amount the vendor is invoicing us.  So it appears that EKBE is using the invoiced amount as the value for DMBTR.

SAP Link

http://help.sap.com/saphelp_nw70/helpdata/en/57/dad06449114814919000e27dfb255e/content.htm