Regarding LO cockpit extraction

hi all,
In LO cockpit data extraction.when we go for maintainence of extract structure of 2LIS_02_SCL data source we are able to see the field BANFN in selection criteria of
communication structure but when we transfer the field to data source this field is not being
reflected. The R/3 system we are using is 4.7 IDES version.
can somebody help us to rectify this problem.
Thanks in advance .
regards
rahul kharya

Hello Rahul,
Please check the Data source on left hand side of Communication structure properly once again for the field BANFN.
It should come automatically.
Regards ,
Amol.
(u r friend)

Similar Messages

LO cockpit extraction differnce between 2LIS_11_VAHDR     2LIS_11_VASTH

Hi All
I have a doubt reg LO cockpit extraction(LBWE)
1. The SD extractors like
   2LIS_11_VAHDR     Sales document header
   2LIS_11_VAITM     Sales document item
   2LIS_11_VASCL    Sales document schedule line
   2LIS_11_V_ITM Allocation of order item/delivery item
   2LIS_11_V_SCL Allocation of order schedule line/     delivery item and so on ...............
But when i check the latest business content I dont find these Data sources under the below linketc.
http://help.sap.com/saphelp_nw04/helpdata/en/3c/63073c52619459e10000000a114084/frameset.htm
2. Instead I find 4 data sources as below
      2LIS_11_VASTH (Extraction SD Order Header Status)
      2LIS_11_VASTI (Extraction SD Order Item Status )
      2LIS_11_V_SSL (Extraction SD Sales: order Delivery)
      2LIS_08TRTLP(Shipment Delivery-Item Data by Stage )
Can I assume that these data sources (in 2) are replaced by the datasources(1) If not could you please let me know where can I find the documentation for
datasources in (1)
Could u please let me know any info as soon as possible
Regards
Naveen

Hi,
   Here is the links :
2LIS_01_S260/2LIS_11_VAITM:
http://help.sap.com/saphelp_nw04/helpdata/en/8f/36f338472b420de10000000a114084/content.htm
2LIS_12_VASCL:
http://help.sap.com/saphelp_nw04/helpdata/en/42/06f3381fff3358e10000000a11402f/content.htm
2LIS_12_VCITM:
http://help.sap.com/saphelp_nw04/helpdata/en/32/26f438151bc321e10000000a11402f/content.htm
and 2LIS_01_S264
http://help.sap.com/saphelp_nw04/helpdata/en/59/efe8375ae64014e10000009b38f8cf/content.htm
NOTE: Quotations is not included in the LO Cockpit.
and go through this link, this will gave some idea to you
about the Sales Business content model.
http://help.sap.com/saphelp_nw04/helpdata/en/3c/63073c52619459e10000000a114084/frameset.htm
hope this helps you.
regards,
ravi
Message was edited by: Ravi

LO Cockpit extraction

Dear All,
Please explain me the LO COCKPIT extraction in detail. I am looking for detail explanation.
Like filling of setup tables etc.

Aloka,
Please search the forums before posting - there are excellend blogs by roberto negro on the same . Locking the post...
Arun

HI experts various steps involved in LO cockpit extractions

Hi experts ,
can some one tell me various steps invoved in LO COCKPIT extraction cheers thanks.

Hi,
This a wonderful document which explains you A-Z for LO data sources along with the screenshots and nothing more can be added to it.
Keep it with you for any reference.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d019f683-eac1-2b10-40a6-cfe48796a4ca
Thanks
Ajeet

LO Cockpit Extraction Process...

Hi Gurus,
I want help in undersatanding the following:
1. How can we Initialize Delta Process Selectively?
2. What is the difference between Queued Delta and Unserialized V3
Update?
3. In the entire LO Cockpit Extraction process where do we use the V1
and V2 updates?
4. What is the ENQUEUE concept?
Thanks
NewBW

Hi,
Try with these documents:
www.service.sap.com/bi --> Documentation --> Business Content Documentation:
- 2.0B Extracting MM (Purchasing) Transaction Data
- 2.0B Extraction of Logistics Transaction Data
- 2.0B Extraction of logistics transaction data for retail
- Extracting Sales and Distribution Transaction Data - vers. 2
You could also go through these weblogs on LO extraction
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Also if you can send me your email, I can send some LO extraction docs. Hope this helps.
Thanks
Sumit

Can I use full load for daily loads in LO Cockpit extraction.

I am using LO cockpit extraction for 2LIS_11_VAITM and i am using delta load for daily load and I have following doubt.
Can i use full load for daily loads instead of delta in LO Cockpit extraction.
Because, my understanding is that full load always takes data from setup tables in ECC and set up tables will not have delta data.
pls reply. Thanks.

You are right abt the understanding that full load (atleast for the extractor at hand) brings data from setup tables. You are also right that delta records are not loaded into setup tables.
So if you plan to do full loads every day, you have to load the setup tables everyday. It is at this juncture that I have to remind you that, filling of setup tables requires a downtime of the system to ensure that no changes / creates happen during the process.
Hence performing a full load is not a very good approach to go by...especially when SAP made the job easy by doing all the dirty work of identifying changes and writing them to extraction queue.
Hope this helps!

LO cockpit extraction - data flow question

This question is related with the LO cockpit extraction.
Are update tables are meant to be the same as set tables or
are they different?
can anybody provide a highlevel data flow for the logistics data
using LO cockpit from R3 to BW
please correct / enhance the below data flow for different methods of LO delta updates as i assume
and inculude the set up table where it fits.
(for direct update)
R3 db talbes -> delta queue -> extract structure -> transfer structure -> infosource -> data target
(for queued delta)
R3 db talbes -> extraction queue -> delta queue -> extract structure -> transfer structure -> infosource -> data target
(for unserialized V3 update)
R3 db talbes -> postings to update tables -> delta queue -> extract structure -> transfer structure -> infosource -> data target
I also want to know where does the delta queue reside - in R3 or in BW? Can the content of delta queue be viewed?
Thanks for ur help - i will give full points for your input.
ak

Check the diagram in links below. It clearly identifies the data flow and whether the component is in R3 or BW.
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur

Steps to be followed in lo cockpit extraction

hi,
i have read help links and so many blogs in sdn before doing lo extraction
right now i need to do init and delta for purchasing (02)
i want to follow these steps
correst me if i am wrong
step1:
i will fill set up tables for init extraction during that i will stop users for posting documents
step2
after fillling setup tables, in lbwe transaction i will select delta mode as 'queued delta' and run a v3 job for every hour
step3
documents which are new or modified or deleted are collected in lbwq transaction for one hour and transferred to rsa7 as 1 luw
step 4
when i do delta this luw will be extracted to bw
correct me if i am wrong?
if this is correct
if i modify my data source when my deltas are running
what should i do in bw and r/3 side?

Hi Venkat,
To extract data from LO Cockpit follow this steps
1. Log on to R/3
2. execute Transaction LBWE (to get in to LO Cockpit)
3. After u are in LO Cockpit. Expand the desired extract
structures(eg:SD,MM etc..)
4. Click on Maintainence to Maintain Extract Structures
5. Add and remove fields like (MCVBAK, MCVBAP)
6. Generate Data Source by clicking on the data source and then
Select/Hide/Invert fields.
7. Activate Extract Structure by clicking on inactive.( If its already
active you have to deactivate it by clicking on active before step 4)
8. Then execute transaction LBWG to delete the content of setup
tables(Select the application 01 for sales etc)
9. Now execute transaction OLI*BW to fill the set up tables ( where *=7
for sales and *=9 for billing etc)
10. check the data in setup table RSA3
11. Go to BW and Replicate the Data Source
12. Maintain the transfer rules, comm struct, schedule infopacks etc...
13. For delta go in r/3 then LBWE then you application(eg: Sales) and
click on delta and then select DIRECT, QUEUED, or NON SERIALISED V3
And before everything.. after you log on to R/3 transfer the Master
data for your application for Eg: for SD go to SD-IO and transfer it by
using transactions RSA5, RSA6 and RSA3 in that order.
You should fill the setup table in R/3 system & extract the data
to BW .... the setup tables is in SBIW....after that you can do
delta extraction by initialize the extractor.....Full loads are
always taken from the Setup table.
Setup table concept applize only to Lo-Extracion.
Steps for Lo-Extraction:
LO-EXTRACTION
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.
Assign Points if useful
Regards
Venkata Devaraj !!!

Some doubts regarding sorcing cockpit in EBP

Hi all,
This is sankar bhatta , working in IBM . I am new to the EBP module. I got few doubts regarding the sourcing cockpit.
When a shopping cart comes to the sourcing cockpit of the purchaser. I mean in what cases??
i am listing some of the cases where i have doubts.
1) A user creates a SC , but he doesn't assign any vendors. in that case it comes to the sourcing cockpit of the Purchase . is it right??
2)A user created a shopping cart ( with more than one item) without vendor and it has gone to SOCO of purchaser . he has assigned the vendor and orders it. the PO is created in the Backend. now because of some reason ( for example the vendor is not able to supply the item ) the purchase deletes one item from the PO in EB. In this case is the SC comes again to SOCO of the Purchaser???
3) the user created the SC without vendor.The SC goes to the SOCO of the purchaser. The SC is in approval process. Now the user deletes one item and orders it again. In this case whether the SC goes to the SOCO again???
4) User created a SC ( with more than one item) and approval is over. PO is created in the backend. Now, if the user or somebody who has the authorisation deletes the item in SC , does the SC goes to the SOCO of the purchaser??
5)According to SAp standard functionallity, PO can be deleted only by one in purcasing organisation. Is this person person csn be a purchaser (or) some other person in the Purchasing organisation??
Please answer these questions and if you know any other case where a SC comes to the SOCO of the Purcher please include that also.
Thanks and regards
Sankar Rao Bhatta.

Hi Sankara,
The Sourcing cockpit is much more simple than that. Your questions show you'rre very confused in this.
There is only one customizing point used : SAP Reference IMG -> SAP Implementation Guide -> Supplier Relationship Management -> SRM Server -> Sourcing -> Define Sourcing for Product Categories
If Sourcing for Product Categories is not configured, the system creates purchase orders in the local scenario for all requirements; these are incomplete if the source of supply is missing. If you require additional control options, for example, the facility to control processing at product level, you can use the following BAdI: Define Execution of Sourcing.
The diferent options you have in the customizing point are:
-Sourcing is never carried out: This is the default setting. Enterprise Buyer does not transfer any items to the purchaser's sourcing application ¨C independent of the status of the shopping cart.
-Sourcing is always carried out: Enterprise Buyer transfers each item to Sourcing ¨C independent of the status of the shopping cart.
-Sourcing is carried out for items without a source of supply: Enterprise Buyer transfers all requirements that have multiple sources of supply of which none is assigned, or if there is no source of supply for the requirement, to Sourcing.
-Automatic requirement grouping; sourcing for items without assigned source of supply:
If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO. If the requirement does not have a source of supply, it appears in the work list of the sourcing application for manual assignment. Once you have assigned a source of supply, you can submit the requirement to the report.
-Automatic grouping; sourcing is never carried out: If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO. If the requirement does not have a source of supply, an incomplete PO is created.
-Automatic bid invitation for items without a source of supply: Enterprise Buyer creates a bid invitation for all requirements that do not have any source of supply.
So for your questions:
1)depending on your customizing, this SC will lead to:
-Backend PR (classic scenario)
-Local incomplete PO (standalone or extended classic without soircing)
-Requirement in the Sourcing cockpit (if customized)
2)The modification of a PO will never change the initial document (SC and/or requirement), nothing 'comes back' into the sourcing cockpit
3)If you customized the sourcink cockpit, the SC line goes into it only after the approval process
4)This has nothing to do with the sourcing cockpit
5)The POs can be deleted by people who have correct authorizations (that is purchasers of the document purch. org. in standard). Be careful the POs cannot be deleted as soon as they have been edited (as of R/3).
Regards.
Vadim
PS: Please don't forget to reward points for helpful answers on your threads.

Regarding bw crm extraction

Hello Guys,
I need to know what are the steps for BW CRM extraction. I know this has been asked for a lot of times, and I have read some threads before I am posting this question.
I know that we have to activate the BW meta data for the CRM to for the extractors to work, but somehow the steps mentioned on the various thread do not seem to be adequate.
Can we have one thread where we talk all about BW CRM extraction ? Right from step 1. Can someone please post it please ? Also, if we can talk the implications (of what goes in side when we execute each step) it would be great. Its also good to get a technical understanding of the thing works.

HI Mukund,
Steps for Extracting data from CRM:
Configuration Steps
1.Click on ->Assign Dialog RFC destination
If your default RFC destination is not a dialog RFC destination, you need to create an additional dialog RFC destination in addition and then assign it to your default RFC destination
2.Execute Transaction SBIW in CRM
3.Open BC DataSources.
4.Click on Transfer Application Component Hierarchy
Application Component hierarchy is transferred.
5.SPRO in CRM .Go to CRM->CRM Analytics
6.Go to transaction SBIW-> Settings for Application specific Data Source ->Settings for BW adapter
7.Click on Activate BW Adapter Metadata
Select the relevant data sources for CRM sales
8.Click on Copy data sources
Say yes and proceed
9.Logon to BW system and execute transaction RSA1.
Create a source system to establish connectivity with CRM Server
A source system is created. (LSYSCRM200)(Prerequisites: Both BW and CRM should have defined Back ground, RFC users and logical systems)
10.Business content activation for CRM sales area is done
11.Click on source system and choose replicate datasources.
Which Datasource using....?
Hope this Help
Regards,
Raj

Regarding the FI extraction

can any one tell me /send me the procedure to extract FI data sources data to BI/BW.
HOW TO CREATE FI DATA SOURCES.
I WANT STEPS
WHAT R THE PROCEDURES to analyze business requirements, leverage pre-existing SAP BI content, and to design best practice solutions to extend the BI platform to meet OCs integration requirements.
what r the steps to be taken for publishing BI output to Enterprise Portal.

Hi there,
Which tables do you want to use for FI datasource?
We have standard datasources in FI like
0FI_AR_4 - Line Item Data for Account Receivables
0FI_AP_4 - Line Item Data for Account Payables
0FI_GL_4 - Line Item Data for General Ledger
check the fields and if required try to enhance as per the requirement.
Regards,
Rajdeep.

Regarding AP delat extraction time delay

Hi All,
I am facing an issue in AP delta extarction,
The problem is, AP extarctor is taking some time to get the delta records from r3 system to BW, I have cross checked, it is talking around 15+hours to get the delta records to BW from R3.
Because of it I am wasting a lot of time coming to AP testings.
Is there any predefined time delay for this or do I need to change any settings?If yes please suggest your views.
Thanks with regards,
vinay

The default safety time interval is 1 day, which means the records older than one day only will come while extracting data. You can change this setting. Refer OSS NOTE 991429 - Minute Based extraction enhancement for 0FI_*_4 extractors.
Pravender

LO cockpit Extraction Step by step guide and enhancement process

Hi All,
My name is Prathibha and I started of my career with SAP BW. It is my pleasure to get introduced to this SDN World and I am very much impressed with the extent of help that is available here.
Could some one mail me the step by step procedure and the enhancement process (Pls explain with some example,screen shots will be appreciated), the method of populating data into new fields. I went thru Roberto blogs and to some extent i am ok.Pls throw more light on this scenarios from ur experiences.
Mail ID: [email protected]
All good luck to everyone.
Thanks,
Prathibha.

Also check out...
How to make added custom field Delta mechanism work for LO Cookpit?
Regarding Enhancing LO Data Source.
PLUG-INs & Data source Enhancements
changing the datasource of LO cockpit inR/3..need a backup plan
Enhancement issue somebody clarify plz
assign points if useful ***
Thanks,
Raj

Regarding Oil & Gas extraction into sap bi

Hi friends
We are above to do extraction from Industry specific OIL & Gas , and civil projects \
can anyone has done this kind of project , or atleast guide me how to work on this ( as it is differenct compare to LO & COPA extraction) please help me . i tried to search the relevant objects in Business content i didnt find
thanks in advance
thanks

Hi,
please check this link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/405f09c8-ca95-2e10-bd81-8d79bd3afa04?QuickLink=index&overridelayout=true
hope it will give some idea.
and congrats for the good project...!

Regarding the Routing extraction

Hi All,
I am extracting the data from legacy system for routings CA01 transaction . Could any body help in giving the standard function modules to extract the data based on the plant . Because i need to extract the data based on the plant and task list type. Its urgent .
Full rewards if useful.
Thanks,
Satheesh

check FM CP_EX_PLAN_READ. before you call the FM flush the structures with FM CP_EX_DATA_REFRESH
Regds, Murugesh
code example:
*- Flush buffer
        CALL FUNCTION 'CP_EX_DATA_REFRESH'.
*- Read plan
        CALL FUNCTION 'CP_EX_PLAN_READ'
             EXPORTING
                  cmode_imp                      = 'R'
                  plnty_imp                      = l_t_plan-plnty_imp
                  plnnr_imp                      = l_t_plan-plnnr_imp
                  plnal_imp                      = l_t_plan-plnal_imp
                  sttag_imp                      = l_t_plan-sttag_imp
*         CHECK_IMP                      = 'X'
*         CUOBJ_IMP                      =
                  parnt_imp                      = l_t_plan-parnt_imp
*         FCAPO_IMP                      = ' '
*         TCA11_IMP                      = ' '
*         FLG_VAL_REC_IMP                = ' '
*         STLNR_IMP                      =
*         I_BUSINESS_OBJECT              =
*         PRODCOST                       = ' '
*         I_FLG_CHARACTERISTICS_PLANNING = ' '
                 i_plant                        = l_t_plan-i_plant
    IMPORTING
*         RES_APPR_CHK_EXP               =
*         ERROR_EXP                      =
                 e_mapl                         = l_s_mapl
             TABLES
                 mlst_exp                       = l_t_mlstd
                 plab_exp                       = l_t_plab
                 plas_exp                       = l_t_plas
                 plfh_exp                       = l_t_plfh
                 plfl_exp                       = l_t_plfl
                 plft_exp                       = l_t_plft
                 plfv_exp                       = l_t_plfv
                 plko_exp                       = l_t_plko
                 plmz_exp                       = l_t_plmz
                 plpo_exp                       = l_t_coplpo
                 pltx_exp                       = l_t_pltxd
                 aennr_exp                      = l_t_rc280
                 plmk_exp                       = l_t_plmkb
                 plmw_exp                       = l_t_plmw
            EXCEPTIONS
                 not_found                      = 1
                 plnal_initial                  = 2
                 OTHERS                         = 3

Regarding LO cockpit extraction

Similar Messages

Maybe you are looking for