0PM_OM_OPA_1 & 2

Hi

The datasource 0PM_OM_OPA_1 is NOT delta enabled. Only FULL upload can be done via this datasource because no TIMESTAMP field is present in the COPF table. Since the datasource is NOT delta enabled in order to improve the performance during FULL upload the field "VTYPE" was set to "Selectable" (Table - ROOSFIELD -> selection) in order to

restrict the number of records retrieved by 0PM_OM_OPA_1 extractor.

If you still want to proceed with delta extraction it may be possible to create a Generic datasource on the source table for

0PM_OM_OPA_1 from transaction RSO2 using Calender day or numeric pointer.

0PM_OM_OPA_2 Delta-Capable Extraction for Order Costs which is a diffrent datasource from maintain orders

Santosh

Hi

0PM_OM_OPA_1 - is for the planning costs. It provides the movement data for maintenance orders.

0PM_OM_OPA_2 - Delta extraction of the actual costs (table COEP) of the maintenance orders

Thanks

Hi

0PM_OM_OPA_1 it is for the planning costs (vtype=20), actual costs (vtype=10) , commitment lines (vtype=40), ecc.

It's based on FM BWSM_PM_GET_ORDCST and provides data from

1) COSP : CO Object: Cost Totals for External Postings

2) COSS: CO Object: Cost Totals for Internal Postings

0PM_OM_OPA_2 it provides delta extraction of the actual costs.

It's based on and provides data from

COVP (database view on COEP and COBK): CO Object: Line Items (by Period and Document Header)

We upload data from both datasource:

from 0PM_OM_OPA_1 for planning costs and commitment lines (and we delete datapacKage actual records in start routine)

from 0PM_OM_OPA-2 for actual costs.

It depends from you scenario and your purpose.

Hope this help you.