Shipment No. in BW Datasource

Daer All
Is there any datasource in BW having Shipment No.
Thanks
Dinesh sharma

Dinesh,
Chk these link from help.sap.com
http://help.sap.com/saphelp_nw70/helpdata/en/a1/fa1aa01efbda488958bf3eb3a968fc/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/5e/16b41e56e8874186642683253f1583/content.htm
They say that you have shipment number i.e. the field TKNUM in the datasources 2LIS_08TRTK and 2LIS_08TRTLP
The field TKNUM might be hidden in the above datasources... Go to LBWE transaction and drag this field in it...
Edited by: mansi dandavate on Jul 2, 2009 6:54 AM

Similar Messages

What is the Shipments Datasource?

Hi,
I have a requirement where I need to report total shipments in an order and how many days are there between order date and shipment date. My question is what datasource I can use to achieve this functionality. I appreciate your help with reward.
Thanks,
Rao.

Monica,
I think we can't get the Goods Issue Document Number from the 2LIS_03_BF. If you are able to fidn out the Material Document number from the abouve mentioned Data Source, we can go with Monica View.
Shipment processed date depends on the Goods Issue date.
We have a Shipment header Data Source, there you will all the materials. Go through the Documentation, for Shipment Header DS.you will get better idea. That DS will give you when the shipment Started and When shipment ended.
Monica please update the thread with your View.
Thanks and Regards,
Nagesh.

Delivery document no in shipment cube ?

How to identify delivery document no from shipment extract stru ?
I need a report with shipment details for specific del document no . Do v have any field in shipment extract structure where v can link it with delivery doc no .
Let me know field name and extractor name
Regards

The field VBELN on the 2LIS_08TRTLP DataSource is the Delivery Number.

ShipMent and Delivery Extractor

Can somebody explain the differences between shipment extractors and Delivery Extractors (SD). when exactly we use shipment and when 2lis_12_vchdr or itm. If anybody has document on shipment please mail it
[email protected]
Regards
Kunal

Hi Kunal,
all these extraxt structures/ datasources are event driven Delivery extractor are purely based on even VC i.e. creating, changing or deleting deliveries.
while shipment ones are also influenced by VA & few others, mailing you a document on SD extarction, see if that helps.
regards
Vikash

Transport Status in Shipment

Dear All,
I used the cube 0OI_TDC01- TD: Shipment Items for new requirement. 0OI_TD_OIGSII this datasource has Transport Status object. In R/3 This transport status avaliable up to 6(copmletly deliverd). Once load the data i get it only transport status 6. bellow 6 not able to get.
Please give ur valuable solutions.
Amulu

solved. Stadnard extraction program modified as status level 6 as per OSS replay.

Naming of Datasources

Hello,
Need some guidance here. I hope to find out why FI-SL DataSource is sometimes named as 3FI_SL_L1 and sometimes 3FI_SL_L1_TT? Or is it due to different naming convention for different releases?
thanks!
adette

Level names can be reused across dimensions. This is common. For example, detail level data is very often shared across levels. When is comes to summary levels, you need decide whether this makes sense. Consider two hierarchies:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Item
Product Type hierarchy, with levels:
Total Product
Brand
Group
Item
In the above case, Total Product in each hierarchy should yield the same values because it is the aggregation of all items. So, you might decide that is ok. A different case might not be ok. Consider:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product
Brand
Group
Items sold
Since Items Shipped and Items Sold are likely to have different values, the aggregation of each level will yield a different value. In this case, Total Product as the top of each hierarchy doesn't make sense.
A different twist would be (note the display names):
Shipping Hierarchy, with levels:
Total Shipments with 'Total Product' as display name
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product Types with 'Total Product' as display name
Brand
Group
Items sold
In this case there will be different levels with different values, but the user will see each as 'Total Product'. Only your user community can tell you if this is want they want.

Shipment Batch level details report

Hi All,
Our client has come up with a new report requirement. They want the below columns in their report.
Sales Order , Sales Order Item, Delivery, Delivery Item, Batch , Shipment , Individual delivery quantity
Please suggest what will be the best approach to build the report. Should we go for a generic datasource or should we enhance any existing LIS Datasource?
Regards and Thanks,
Vivek Das Gupta

Hi,
There are standard datasources for Sales Orders/Shipments:
2LIS_11_VAITM (Sales Orders Items)
2LIS_12_VCITM (Delivery Items)
These datasources are used in the most BI solutions.
Regards,
Tiago.

Exposure of BI Content/Generic DataSources in Data Services XI 3.x

We were told by SAP Business Objects personnel back in May 2009 that SAP DataSources (standard content and generic) would be exposed in SAP Business Objects Data Services XI 3.2. We have recently upgraded Data Services, in a sandbox environment, to XI 3.2 and found that this isn't there.
After pinging some others that we know at SAP, we're now hearing that this won't be available until SP4. Is this correct? Right now, the unrestricted shipment version is SP0 and we're wondering if it truly is SP4 or SP0 FP4 when then is scheduled to be in unrestricted shipment and when these are scheduled to be released for general customer consumption. Can anyone from SAP monitoring this forum comment?

Hi Dennis:
BW uses the business content extractors. In 4.0 Data Services will also use the Business Content extractors.
This does not mean BW customers have to start using Data Services; SAP is not replacing the connectivity between ECC and BW. Data Services is added as an option to the landscape and adds the option of accessing other 3rd party sources u2013 one single tool to extract data.
With Data Services, you have the possibility to consolidate extraction rules into one platform. You can also make sure you can load correct and clean data into target application with the data quality components of Data Services.
You just need to know the name of the extractor and connect. No ABAP programs are generated, making it easier to deploy and maintain.
Since you originally posted your question almost two years ago you might be aware of this but I think people visiting this forum in the future may find very useful information on the blog by Tammy Powlas.
SAP BusinessObjects Data Services - What is new in 4.0?
/people/tammy.powlas3/blog/2011/04/18/sap-businessobjects-data-services--what-is-new-in-40
Regards,
Francisco Milán.
Edited by: Francisco Milan on May 24, 2011 4:12 PM

I want to learn abt datasources.. pl tel some datasources in sd, mm, pp

Pl tel some datasources for sd, mm, pp ...
and tel me where to find the datasource...
with example...

HI
SD
2LIS_HT_DR0DRM                    DRM Business Matrix
2LIS_HT_MS0DRM                    DRM: MS Business Matrix
2LIS_13_VDKON                     Billing Document Condition
2LIS_13_VDITM                     Billing Document Item Data
2LIS_13_VDHDR                     Billing Doc. Header Data
2LIS_01_S001                      Customer
2LIS_01_S005                      Shipping point
2LIS_01_S264                      SD- Offer
2LIS_08TRFKP                      Shipment Costs at Item Level
2LIS_08TRFKZ                      Shipment Costs at Delivery Item Level
2LIS_08TRTK                       Shipment: Header Data
2LIS_08TRTLP                      Shipment: Delivery Item Data by Section
2LIS_08TRTS                       Shipment: Section Data
2LIS_11_VAHDR                     Sales Document Header Data
2LIS_11_VAITM                     Sales Document Item Data
2LIS_11_VAKON                     Sales Document Condition
2LIS_11_VASCL                     Sales Document Schedule Line
2LIS_11_VASTH                     Sales Document Header Status
2LIS_11_VASTI                     Sales Document Item Status
2LIS_11_V_ITM                     Sales-Shipping Allocation Item Data
2LIS_11_V_SCL                     Sales-Shipping Allocation Schedule Line
2LIS_11_V_SSL                     Sales Document Order Delivery
2LIS_12_VCHDR                     Delivery Header Data
2LIS_12_VCITM                     Delivery Item Data
2LIS_12_VCSCL                     Sales-Shipping Schedule Line Delivery
QM
2LIS_05_QVUDN                     Inspection Lot/Usage Decision
2LIS_05_QE2                       Inspection Result: Quantitative Data
2LIS_05_QE1                       Inspection Result: General Data
2LIS_05_Q0TASK                    Quality Notifications - Tasks
2LIS_05_Q0NOTIF                   Quality Notifications
2LIS_05_Q0ITEM                    Quality Notifications - Items
2LIS_05_Q0CAUSE                   Quality Notifications - Causes
2LIS_05_Q0ACTY                    Quality Notifications - Activities
PM
0PM_OM_OPA_1                      Maintenance Orders: Costs and Allocations
0PM_OM_OPA_2                      Maintenance Orders: Actual Costs by Means of Delta Extract.
0PM_OM_OPA_3                      Maintenance Orders: Commitmt Line Items
0PM_PRM_PLCS_1                    Planned Costs Maintenance
2LIS_17_I3HDR                     Plant maintenance orders
2LIS_17_I0TASK                    Maintenance Notifications - Tasks
2LIS_17_I0NOTIF                   Maintenance Notifications
2LIS_17_I0ITEM                    Maintenance Notifications - Items
2LIS_17_I0CAUSE                   Maintenance Notifications - Causes
2LIS_17_I3OPER                    Plant Maintenance Order Process
2LIS_17_I0ACTY                    Maintenance Notifications - Activities
0PM_MEASUREMENT                   Measuring Points and Measurement Documents
0PM_DSMNTL                        Plant Maintenance - Equipment Dismantling
MM
2LIS_03_S195                      Material movements: storage location
2LIS_02_S011                      Purchasing groups
2LIS_02_S012                      Purchasing
2LIS_02_S013                      Vendor Evaluation
2LIS_02_S015                      Subsequent Settlement: Evaluation
2LIS_02_S174                      Services
2LIS_02_SCL                       Purchasing Data (Schedule Line Level)
2LIS_02_SCN                       Produced Activity: Confirmation of Schedule Lines
2LIS_02_SGR                       Produced Activity: Delivery of Schedule Lines
2LIS_06_INV
0MM_PUR_VE_02                     Vendor Evaluation Semiauto
2LIS_03_BF                        Goods Movements From Inventory Management
2LIS_03_BX                        Stock Initialization for Inventory Management
2LIS_03_S091                      WM: Quantity flows
2LIS_03_S194                      MRP: Business Info Warehouse
0MM_PUR_VE_01                     Vendor evaluation
2LIS_02_ITM                       Purchasing Data (Item Level)
0CO_PC_ACT_07                     Material Valuation: Prices - Project Stocks
0CO_PC_ACT_06                     Material Valuation: Prices - Sales Order Stocks
0CO_PC_ACT_05                     Material Valuation: Prices
0CO_PC_ACT_04                     Material Valuation: Per. Ending Inventory Project Stocks
0CO_PC_ACT_03                     Material Valuation: Per. Ending Inventory Sales Order Stocks
0CO_PC_ACT_02                     Material Valuation: Per. Ending Inventory
2LIS_03_UM                        Revaluations
2LIS_03_S198                      Periodic plant stock
2LIS_02_HDR                       Purchasing Data (Header Level)
2LIS_02_CGR                       Produced Activity: Delivery of Confirmations
0SR_VE_INT_IV                     Vendor Evaluation in Invoice Verification (ECC)
2LIS_03_S196                      Goods movement: Plant
2LIS_03_S197                      Periodic storage location stock
2LIS_02_ACC                       Purchasing Data (Account Level)
LO
0CUST_SALES_ATTR                  Customer number
0CUST_SALES_LKDH_HIER             Customer number
0CUST_SALES_TEXT                  Customer Number
0CUST_SALES_TID_LKDH_HIER         Customer number (Time-Independent)
0ART_ST_LOC_ATTR                  Article Number Compounded with Plant and Storage Location
0ARTICLE_ATTR                     Article Number
0ART_SALES_ATTR                   Article Number Compounded with Sales
0ARTICLE_TEXT                     Article Number
0ART_PLANT_ATTR                   Article Number Compounded with Sales
0CUST_COMPC_TEXT                  Customer Number Compounded with Company Code
0MATERIAL_TEXT                    Material Number
0MAT_KONDM_TEXT                   Text DataSource for Field KONDM (Material Group)
0MAT_PLANT_ATTR                   Material Number with Plant
0MAT_PLANT_TEXT                   Material number with plant
0MAT_SALES_ATTR                   Material number with sales
0MAT_SALES_LPRH_HIER              Material Number Compounded to Sales
0MAT_SALES_TEXT                   Material number with sales
0MAT_ST_LOC_ATTR                  Material Number Compounded to Plant and Storage Location
0MAT_ST_LOC_TEXT                  Material Number Compounded to Plant and Storage Location
0MAT_UNIT_ATTR                     Material: Unit Conversion
0PROD_HIER_LPRH_HIER              Material number
0PLANT_ATTR                       Plant
0PLANT_LKLS_HIER                  Plant
0PLANT_TEXT                       Plant
0CUST_COMPC_ATTR                  Customer Number Compounded with Company Code
0CUSTOMER_TEXT                    Customer number
0CUSTOMER_LKLS_HIER               Customer number
0CUSTOMER_ATTR                    Customer Number
0USAGE_IND_TEXT                   Usage Indicator Material
0VEN_ACCNT_GRP_TEXT               Vendor account group
0VEN_COMPC_ATTR                   Vendor Number Compounded to Company Code
0VEN_COMPC_TEXT                   Vendor Number Compounded to Company Code
0VEN_PURORG_ATTR                  Vendor Number
0MATERIAL_ATTR                    Material Number
0VEN_PURORG_TEXT                  Vendor Number
0MATERIAL_LGEN_HIER               Material number
0MATERIAL_LKLS_HIER               Material number
0MATERIAL_LPRH_HIER               Material number
PP
2LIS_04_PEMATNR                   Repetitive Manufacturing Material View
2LIS_04_PECOMP                    Repetitive Manufacturing Component View
2LIS_04_PEARBPL                   Reporting Points for Repetitive Manufacturing
2LIS_04_P_ARBPL                   Work Center View from PP/PP-PI
2LIS_04_P_COMP                    Component View from PP/PP-PI
2LIS_04_P_MATNR                   Material View from PP/PP-PI
0PP_WCCP                          PP(PI)Work Center Capacity
0PP_DOWNTIME                      Resource Downtimes
PS
0PS_CLM_CST                       Claim Costs
0PS_ORD_EVA                       Progress in Orders
0PS_KAP_NAE                       Extraction of Capacity Requirements for Activity Element
0PS_NWA_EVA                       Progress in Network Activities
0PS_NTW_EVA                       Progress in Networks
0PS_NAE_EVA                       Progress in Network Activity Elements
0PS_CSH_NTW                       Network Plan Payments
0PS_CSH_NWA                       Payments on Network Plan Process
0PS_CSH_ORD                       Payments on Orders
0PS_DAT_WBS                       WBS Element Dates
0PS_DAT_PRJ                       Date Project
0PS_WBS_EVA                       Progress in WBS Elements
0PS_KAP_NWA                       Extraction of Capacity Requirements for Network Activity
COPA_Master
0DESTINATION_TEXT                 Trip Destination
0AIRCRAFT_TYPE_TEXT               Aircraft Type
0ROTATION_TEXT                    Rotation
0BRAND_TEXT                       Brand
0BUSFIELD_TEXT                    Business field
0STRBUSUNIT_TEXT                  Strategic Business Unit
0ZONE_TEXT                        Zone
0ORIGIN_TEXT                      Departure Location
0DAY_OF_OPERATION_TEXT            Day of Operation
0TRANSPORT_TEXT                   Shipment Type
0IATA_SEASON_TEXT                 IATA Season
0REC_TYPE_TEXT                    Activity type
0FLIGHT_NO_TEXT                   Flight Number
0LEG_TEXT                         Route Segment
0MAINMATGRP_TEXT                  Main Material Group

Options on Transtru/DataSource tap page in Infosource maintenance!!

Hello BW Experts,
Are the options in the Transtru/DataSource tap page (in the infosource manitenance screen) i.e., Full Upload, New Status(ODS Only) and Additive data (ODS and InfoCube).. ALSO AVAILABLE when we do the Business Content Extraction eg: LO Extraction.
Are these options only applicable for Flat File Loading??
plz Clarify,
Regards,
Sapster.

Hi Sapster,
Those options are available for only Flat file loading..
And as for the extractions you can do as below..
T-Code: LBWE
First we need to check which data source suits the client's
requirements in LBWE.
Check whether it is in Active version/Modified version. If it is
in M version go to RSA5 and select our data source and press on
Transfer. Then go to RSA6 and see whether the datsource is been
transferred.
If the datasource is already in active version then we need to
check whether the datsource is already extracting data in to BW.
If the datasource is extracting the data then we need to check the
data existence in Setup tables (use SE11 to check the setup tables
data. For every extract structure one and only one setup table is
generated whose technical name is Extract structure name+ setup, for
eg. If extract structure name is MC11VAOHDR then set up tables name
is MC11VAOHDRSETUP) and Extraction Queue (LBWQ) and Update tables
(SM13) and Delta Queue (RSA7). If data exists in any of these T-
codes we need to decide whether we need the data in BW or not. If we
need the extract it as we do in LO-Extraction below. I f we don't
need delete the data.
The dataflow from R/3 into BW:
We nee to generate the extract structure by selecting the fields
from the communication structure in LBWE.
Generate the datasource and select the selection fields,
cancellation fields, hide fields that we want.
Replicate it into BW. Then we need to attach Info source(Transfer
rules/communication structure) to the datasource. We got 3 methods
to attach the infosource..
1) Business content:: Business content automatically proposes the
transfer rules and communication structure, we don't have to do
anything manually.
2) Application proposal: Here too proposal is done but some objects
will be missing which we need to assign in the transfer rules.
3) Others: here we need to create the transfer structure, rules,
comm. Strct from the scratch.
Modeling like infocube, Infosurce attachment,.
Then activate the extract structure.
We need to fill the setup tables for the first time loading. In
filling the setup tables we can select between Full load and delta
initialization loads.
Filling Set up table:
T Code : SBIW
Settings for Application-Specific DataSources (PI)->Logistics--
>Managing Extract Structures>Initialization>Filling in the Setup
Table -->Application-Specific Setup of Statistical Data --> in that
Youcan perform the Setup (Example : SD-Sales Orders - Perform Setup)
and execute .. or else direct T Code : OLIBW ( means based on your
application like sales order/billing/ purchase etc) For setup
tables T-Code is OLI*BW where * equals to application number like 02
fro purchasing,08 for shipment..
First we need to decide whether we want delta loads to be
performed in the future. If we want to do delta loads, then we need
to go for Delta Initialization process or else do full load.
When we perform setup tables extraction, since setup tables are
cluster tables, we can't see the data in the setup tables. So we go
for Extractor checker (RSA3) just to see the setup tables data
(full/delta initialization).
Then create infopackage and select Full or Delta initialization in
Update tab and schedule it.
Delete the setup tables data by using LBWG.
Now we need to do delta loads.
Delta load data flow differs with various delta update methods. We
got 3 delta update methods as u know.
If we select "Queued Delta"update method then the data moves to
Extraction queue(LBWQ). Then run Collective update to move the data
from LBWQ into Delta Queue (RSA7). Then schedule the data using the
infopackage by selecting Delta Load in the update tab.
If we select "Direct delta" then the delta data moves into RSA7
directly.
If we select "Unserialized V3" method then the data goes
into "Update tables(SM13)", then run Collective update to move the
data from SM13 into RSA7. Schedule the data using infopackage.
If we click on Maintenance, we can generate the extract structure.
If we click on 2LIS_02_CGR button, then we we can generate data
source
Inactive under Update column: we can make a extract structure as
active or inactive.
If we click on Job control button the we can maintain the
collective update parameters like, start time, and is it hourly once
or dialy once
If we click on Queued delta button under Update mode then we can
select among 3 delta update methods.
Only Full/Delta initialization data loads only moves into setup
tables. Delta load data doesn't move into setup tables.
**RSA3 contains only setup table's data
Only Delta update data moves into RSA7/LBWQ/SM13 no full/delta
initialization loads data.
Generic extrction..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Hope it helps,
Assign points if useful.
Regards,
Archna

Extraction shipment cost 2lis_08trfkz

Hi,
I have a problem with shipment cost. A shipment cost is assigned to a transport.
Datas are updated to BI system. When I delete a shipment cost in order to create an other one and assign it to the same transport, BI system detects changes, but it create 2 register with the same transport number but different shipment cost. I need a DSO to store data, but the KEY FIELD must be transport numer, shipment cost and shipment cost item. Then tha data are update into a cube.
Is there into SAP R/3 a field when I can store deleted shipment costs? The used table is VFKP, but there is no place where I can store deleted shipment cost. Do you know how I can solve this problem?
Thank you very much

Hi pcamp :
The solution for you is to add to your DSO the Reversal Indicator (InfoObject 0STORNO), this way you can identify the deleted Shipments/Shipment Cost documents when the 0STORNO = 'R'. If the 0STORNO = '' then the document exists in the ERP.
You could either make 0STORNO part of the Data Fields or Key Fields of you DSO, depending on your particular needs (overwrite or preserve existing records).
Hi Ramesh:
As you mentioned before, the SAP Note 440166 explains that there is ODS Capability for Shipment and Shipment Costs DataSources.
Depending on the Support Package of your SAP System you may need to apply the corrections, according to the follwoing SAP Note: 440416 - BW OLTP: Correction report for change of delta process.
Regards.

Delivery Item in 2LIS_08TRFKZ datasource

Hi,
    I want to use the 2LIS_08TRFKZ extractor to load the shipment costs and Qty by Delivery number to BI. I see that I can enhance the extractor to bring the Delivery Number from the VTTP table. But I am wondering how I can get the Delivery Item information and split the Costs and Qty at the Item level.
Please provide some input.
Thanks.

Hi,
   I had the same design idea. This is what I have in my mind, let me know if it works...
   We have a Deliveries DSO DEL_DSO (loading from VCITM) with the Delivery Number and delivery Item as the key, the shipment number and delivery Qty are in the data fields. I thought of creating a FKZ_DSO with Shipment number, the Delivery number, and delivery item as the key and the costs in the data part and load it with the 2LIS_08TRFKZ datasource.
    Then load the costs from the FKZ_DSO to an intermediate DSO while looking up the Qty from the DEL_DSO. So the Costs and the Qty would line up at the Shipment, delivery and item level.
But this would only work if I can get the Delivery number and Item from the FKZ data source. I am in a fix now cos the REBEL and the REPOS does not give me that information. I would have to enhane the extractor and write code to get the delivery number and the item from the VFSI table and also will have to split the shipment cost accross the all the deliveries. It seems a lot of redundency to me, so trying to avoid it.
Can you please double check tho REBEL and the REPOS fields?
Thanks.

Delta problem with datasource 2LIS_08TRTLP

Hello everybody,
I'm having a problem with the delta to datasource 2LIS_08TRTLP.
I follow this tasks:
1 - I did a deletion of setup table data in transaction LBWG for application 08 and checked Shipment document and Shipment Costs.
2 - Transaction VTBW -> Execute this transaction with the fields "Shipment Number" and "Created on" empty.
3 - Execute a infopackage with update - "Initialize Delta process - Initialization with Data Transfer".
I don't have problem with this 03 tasks, the data come from ECC without problem.
But when I execute a infopackage with "Delta Update" the Monitor - Administrator Workbench show me 0 from 0 records "No data available, data selection ended ".
What is wrong in my tasks? Why the delta don't work?
Thanks.
Paulo Sampaio

Hi,
Your Process is correct for initialization load. But when you are running the delta there should be a V3 run for this datasource in ECC system, then it captures the deltas.
Till you have pulled all the full load data to BI, but there is no data available in the delta tables for this datasource, since you have not run any V3 run for this. That is why it is showing zero from zero recrods.
There must be some positings in ECC to the database tables related to this datasource after your initialization run, then only after running the V3 to capture the new/changed records it updates to Delta Queue (RSA7), then we will get the records to the BI.
Otherwise check the data source data in RSA7 tcode.
Hope this helps.
Veerendra.

Regarding Delta update for Standers Datasource

Hi Guys,
I am working in BI 7.0 environment with 3.x dasources. I have a datasource 0RPM_FI_DATA, I loaded full load first and now i am trying to do init beofre going to delta. But i am not INIT or Delta option in Infopackage screen. then i had look in the rsa6, Delta update option is not enabled for that datasouce.
So, Can anybody explain to me how can i make this Datasource as Delta enabled.
How can i do delta loads. For every clue, points will be awardable.
Thanks,
Suri.

seemingly this datasource is delta capable following the version of your xRMP version
RPM FI Data Extractor
Technical Name: 0RPM_FI_DATA
Use
This extractor is used to extract xRPM Financial integration attributes to the equivalent BW InfoSource Cost and Time Analysis (0RPM_COA_01). The extractor is a function based extractor of the source table rpm_fidata.
Technical Data
Application Components:
APCO_XAPPS_RPM
Available as from Release:
SAP xRPM 4.0
Shipment:
Content Version:
7.03
RemoteCube-Capable:
No
Delta-Capable:
Yes
Extraction from Archives:
No
Verifiable:
No
http://help.sap.com/saphelp_nw70/helpdata/en/16/039d1642004d479033f0f2a92fa86e/content.htm

Set up of historical data for 2lis_08 datasources

Hello All,
Would like to know how to setup the setup tables for 2lis_08 datasources which are shipments.
thanks
amit

Hi Amit,
transaction VTBW for transport and VIFBW for shipment costs !
Hope it helps!
Bye,
Roberto

Shipment No. in BW Datasource

Similar Messages

Maybe you are looking for