Logistics Extraction Structures Customizing Cockpit, (URGENT)

Can someone give me a step by step way of how to use and apply Logistics Extraction Structures Customizing Cockpit. Eric Thanks.

Pls have a look at the engagement rules of this forum:
/thread/117232 [original link is broken]

Similar Messages

  • Lis extract structures

    Dear consultants,
    i have problem with lis structures (like 2LIS_17_IOCAUSE)
    before transfering into my bi system i need to fill these structures with transaction
    Managing Transfer Information Structures - Initialization -Filling in the Setup Table-Application-Specific Setup of Statistical Data.
    is there any way to fill these table automatically? or i should fill these tables everytime i load data to my bi system?
    thanks

    Dear Ramesh,
    my lis structure is 2LIS_17_IONOTIF. therefore it has delta capability. However, i do not know wehere to set it and what else have to do.
    Do i need to;
    1) Activate 2LIS_17_IONOTIF in Logistics Extraction Structures Customizing Cockpit.
    2) Set Plant Maintenance: BW  in Logistics Extraction Structures Customizing Cockpit as;
    Update:Job control and Update Mode:Queued Delta?
    3) What else have to be done?
    Thanks in advance..

  • LIS Extract structure MC17I00ACT changed while implementing oss note 865254

    Hi,
    While i am trying to implement the oss notes 865254 , the sap defined data source 2LIS_17_I0ACTY , having the extracture MC17I00ACT , extract structure is modified and many  fields and includes are deleted .can any one please give soluation how to restore the original extract structure.its very urgent. please help me.
    thanks,
    sri.c

    Hi,
    it might be possible to get it back from the version management. I didn't do that, but you can try. Goto se11->Tools->Versions
    regards
    Siggi
    PS: Be careful and check the versions before.
    Message was edited by: Siegfried Szameitat

  • SAP help for Logistics Customizing Cockpit

    Hi Friends
    Greetings...
    I want to read complete scenario for BW extraction, I want to know LIS, and LO concept, Central Delta Managemen, Set up tables, why we need MCstructures if we have LIS structures etc.,
    I'm trying to search in "help.sap.com" but couldn't find i got only "customizing extractors" in BW help, but couldn't find complete scenario of LO and LIS. I have 350 extraction material, but still i want to read from help.sap.com also. kindly help me to get this site
    bye
    lasya

    Hi,
    Step by Step for LIS Extraction
    LIS EXTRACTION
    T.code - :MC18 – create field catalog
    1. Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc.
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog
    Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 – create infostructure
    Infostructure : S789
    Application – 01
    Choose characteristic select the catalog, select the fields, copy + close
    Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code – MC24 – create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter
    Select the key figures click on rules for key figures give suggest rules, copy save and generate
    Click on updating (activate updating)
    Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period
    Updating –1)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code – LBW0 - Connection of LIS Information structures to SAPBW
    Information structure : S786
    Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute
    Select the radio button -Activate / deactivate and Execute.
    T.code – SBIW – Display IMG (implementation guide)
    Setting for applications specific data source – logistics – Managing transfer information structure – setup of statistical data – applications specific setup of statistical data –perform statistical setup – sales.
    Choose activity
    Setup – Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code – RSA3 – Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records
    Go to BW side replicate data source – Assign infosource – Create infocube – Create update rules – create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code – MC25, set update (V1) or (V2) or (V3)
    T.code – LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side - create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    3.Modules:
    SD,MM, PP,QM..
    4. Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables ‘SnnnBIW1’, ‘SnnnBIW2’ and the structure ‘SnnnBIWS’ and the InfoStructure itself ‚Snnn‘
    The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure ‘SnnnnBIWC’ is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table ‘TMCBIW’. Within transaction ‘SE16’ you’ll see, that for your particular InfoStructure the field ‘BIW active’ has the value ‘X’ and the field ‘BIW status’ is filled with value ‘1’ (refers to table SnnnBIW1).
    The orgininal LIS update program ‚RMCX#### will be enhanced within the form routines ‚form Snnnbiw1_update_....‘ and ‚form Snnnbiw2_update
    With the transaction ‘SE38’ you’ll see at the end of the program [starting at line 870 / 1006], that the program is enhanced within a ‘BIW delta update’ coding
    Within the flag ‚Activate/Deactivate‘ the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table ‚TMCBIW‘ is defined, which table is active for delta update.
    check LO also
    LO
    rgds,
    raj
    Message was edited by:
            gangaraju mullapudi

  • Unable to create Custom Datasource on AFRU -Invalid extract structure error

    Hello folks,
    All SDN experts I need urgent help with an issue here.I am trying to create a custom datasource on a view on AFRU table.But i am getting this error 'Invalid extract structure template ZAFRU_V ' , i know it could be cuz of the field SMENG which is refrenced to AFVV tables MEINH field.My boss needs to have this field.I would like to know what can i do to get it, do i need to write a user exit, will that help or not. Please tell me what to do.
    Thanks,

    i tried what you asked me to do, this was my joing condition
    AFRU     MANDT     =     AFVV     MANDT
    AFRU     AUFPL     =     AFVV     AUFPL
    AFRU     APLZL     =     AFVV     APLZL
    But then what i ran into was if the counter (APLZL) was 0 or blank it wouldnt get that data for me.That means i will loose hundreds or thousands of records if they have confirmation and routing number  of ops in order but no counter.Please assist.
    And to answer is open so please any one who sees this and knows the answer please reply.
    Thanks.

  • Custom Datasource using View COVJ - R8359 Invalid extract structure

    I'm trying to build a custom datasource so I can get at plan line item data with partner object (I've tried using 0CO_OM_CCA_1 but I dont get the partner object for plan data - no idea why). So I thought if I create a datasource using COVJ I can get it out. However when I try and save the custom datasource (created using RSO2) I get the error R8359 Invalid extract structure: You tried to generate an extract structure with the template structure COVJ. This operation failed, because the template structure quantity fields or currency fields, for example, field WOG001 refer to a different table.
    I saw posts saying when people get this error thye should reference the table these fields come from in the view. So I've talked to our ABAP'er and I asked him to reference the table these fields come from but he said this cant be done because these come from a structure not a table.
    Any ideas?
    Thanks
    Joel

    The WOG* columns in table COEJ, one of the tables contributing to the COVJ view, use CCCUR-CURKY as the reference table-column for those quantities. The ABAPer you spoke to is correct that CCCUR is a structure. View value fields inherit their reference table-column from the source, in this case COEJ, and since this source table is an SAP delivered table it cannot be modified change this reference.
    This means that you're only option for extracting the data out of the COVJ view would be to create a Function Module and use that Function Module as the basis for your DataSource.

  • Changes in Logistics DataSource Extract Structure

    Hi All,
    We intend to transport our enhanced extract structure of our Logistics DataSource. We know that extraction queue and delta queue must be emptied first before the transport starts.
    However, we are wondering whether a re-INIT of delta also must be done or not. At this moment, we have delta up and running already.
    Please advice. Thanks.

    Hi Reddy,
    Thanks for your fast reply.
    No, we don't need that historical data. Perhaps, to be more specific, we are wondering whether a Re-INIT without data transfer should be done again or not ?
    We have two cubes. One is old one with up and running delta. The other is new one which we are going to transport soon.
    So, we plan to use same delta infopackage later for these two cubes.
    The concern is now about the delta.
    Please advice again. Thanks.

  • Extract Structure not Being transported with custom Datasource

    I'm having trouble transporting a custom datasource from BW 3.5 dev to QAS.  The datasource is coming through and showing up in RSA6 but when I click on it I get the following error:
    "The extract structure ZOXDBW0123 of the DataSource ZRSPCTRIGTEXT is invalid
    Message no. R8444
    Diagnosis
    An invalid extract structure has been assigned to the DataSource. An extract structure has to be active in the DDIC. It cannot be a view, since the customer is not able to add append fields for filling in the customer exits to a view."
    Any ideas?
    Thanks,
    Luke

    Thanks for your input.  We managed to get through one of the errors on about the 8th try to transport everything together.  It might of had something to do with the way things were being grouped in the packages.
    So now were just getting an RJ044 Error: "ZRSPCTRIGTEXT: Only tables and views are permitted for extraction". 
    I think it may be some kind of program error after all, cause our basis consultant took a look and couldn't figure it out at all either.  The transport says that everything is going through, but the view were extracting from is still not showing up in QAS.  He suggested we blow everything away and try building the datasource again from scratch.  So if we can't figure it out today we may try that route tomorrow. 
    Anyway, thanks again for all the help.

  • Urgent Please : Change back in Extract structure

    Hi All,
    I am working on enhancing an extract structure of Time and labour of 0hr_pt_2 . I had successfully added 2 fields now but afterwords when I try to delete those fields or change that structure it does not allow me to add new fields or delete old those fields which I created.
    I am wondering why it is happening ? Has anyone came across such situation if yes , please feel free to share your experience.
    How can i delete them ? Any helpful reply will be appritiated and rewarded with points.
    Thanks in advance.
    Warm regards,
    John

    One way - Delete the data source via RSA6 and activate back via RSA5; this way you will back to the standard structure.
    Thanks.

  • Transporting extended MC02M_0ITM extract structure in LO Cockpit

    I have extended the extract structure via the maintenance screen for 2LIS_02_ITM to include BUKRS and KTWRT. However, when I transport this into PRD environment, the two fields were not appended into the extract structure. As a consequence, the user exit failed as reference to these 2 fields cannot be made. Any idea what's the problem in the transport ??
    .APPEND
    BUKRS
    KTWRT
    .INCLUDE

    Hi Siew,
    Welcome to SDN!!
    In your transport make sure you had these:
    1. datasource- Active
    2. Extract structure
    3. User exit program
    4. Appended extract structure
    Bye
    Dinesh

  • Error "No extraction structure for event I3" running set up 2LIS_17_I3HDR

    Hi, Experts:
    I am trying to activate and run set up datasource for PM 2LIS_17_I3HDR, so that data can be extracted from R/3 into BW 3.5 system.
    In R/3 environment, we have 2 clients. client 200 for configurations but has no data, and client 230 has data but can not change configurations.
    I have done the following in client 200:
    - Activated datasources for for PM 2LIS_17_I3HDR in RSA5.  
    - Made selection in RSA6.
    - Activated extract structures and datasource for application 17 in LBWE and also ran job control. Now I can see the extract structures for application 17 are active in client 200 only, but inactive in client 230. I tried to turn then active in client 230 but got error "Client 230 has status not modifiable".
    - I assume I should run set up tables in client 230 because it is the client with data in tables? But when run set up in OLIIBW, I got the error "
       No extraction structure for event I3: Messages active
       Message no. MCEX106
       Diagnosis
       You called the setup for the extractor structures of application '17' (Plant Maintenance). However no extractor structure is active for event I3 (messgaes).
       System Response
       Data for event I3 is not transferred to the BW interface.
       Procedure
       First activate the desired extractor structures for application '17' using the Customizing Cockpit and then start the setup again."
    - I can not manually activate extract structures in client 230 because it is not modifiable. I tried moving transports, the path is not set up. I see extract structures for other applications like 11, 13 are active. So I guess there may be other ways to activate the extract structures in client 230.
    - I also tried to run set up in client 200, which has extract structures for 17 in active status. But got the same error as client 230.
    Would anyone please help me with what to do to fix this?
    Thanks,
    Jenny
    Edited by: Jenny Chen on Oct 29, 2009 6:38 AM

    Hi, thanks for the reply!
    Just update for what we did to solve this. Both clients are for development. Client 200 is only for configuration but no data. Client 230 has data but not modifiable. Usually, when we create a structure, table, program, or active anything in 200. We will see it in 230 right away without transports. But this is not the case for activating extract structure for datasource from Business Content. We end up having Basis guy manually activate the structure for us directly in client 230 with transaction LBWE. That worked.
    Thanks,
    Jenny

  • Change to Extract Structure Doubt

    Hi,
    Our Basis Folks are trying to install Patch 6 ST-PI 2005_1_700 in ECC. I refered to OSS Note 328181.
    For this Patch do we need to delete the Set up Table and Fill it again? And How about Init Delta in BW?
    Please suggest me. Any answers will be appreciated with Points.
    Kind Regards
    Mahesh.N

    Hello,
    Yes you have to delete the Setup table data before that as per the OSS Note you have to clear the delta queue data which cannot be recovered after changing the extract structure. So execute the BW Delta Infopackages and make sure there is no delta records in RSA7 or LBWQ.
    Then you can delete the setup table using LBWG and implement the patch.
    1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
    2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
    3. Load all data of the respective DataSource into the BW System.
    Now you can make the change.
    After a change you can no longer use the statistical data already recreated. If such data still exists, you should delete it (Transaction LBWG).
    We recommend in particular to upload the data immediately after a restructuring and (after checking in BW) delete them from the restructuring tables.
    Moreover, the update log (Transaction LBWF) can no longer be read. Post a document in this case so that the last log entry is overwritten. This log entry then has the correct new format of the extract structure.
    As of PI 2000.2 the program RMCEXDELETELOG is available. It can be used to delete log entries.
    But if there is any change in lenght of any field of the extract structure, then you have  to reload the entire data again in BW otherwise a Init without data transfer will do.
    But what is the patch all about? Please follow the instruction given in the OSS Note 328181 - Changes to extract structures in Customizing Cockpit.
    Thanks
    Chandran

  • 2LIS_05_Q0ITEM Enhancement / Extract structure

    Hi experts,
    I am trying to enhance a data source and am having an issue adding a field to the extract structure.
    The 2LIS_05_Q0ITEM includes a field called MATNR for the Material Number of the claimed notification (Table MCQMEL) which I don't need (as it is in the Notification Data source).
    What I need is the material number of the replacement part (MATNR / Table MCQMFE). I can't add it in the Extraction Customizing cockpit. (2 fields with the same is not possible and it isn't possible either to remove the MCQMEL/MATNR field).
    I tried to find a workaround using a user exit to enhance the extract structure but couldn't find anything allowing me to retrieve the MATNR from MCQMEL.
    Any clues on how to add this field to the datasources other than doing a select fron the Table in the extract structure?
    Thanks,

    Hi,
    The LO steps are described in:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:How_to_do_LO_Extraction
    Go through these weblogs for detailed understanding of LO extraction mechanism. If you have any further queries, post them.
    /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
    /people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
    Bye
    Dinesh

  • Inventory Extract structure

    hi all,
    I cant able to find the 2lis_03_bx(Material stock) extract structure under the inventory application in the LO customizing
    cockpit screen .
    The other extract structures 2lis_03_bf and 2lis_03_um are available.
    can anbody help how to get the 2lis_03_bx extractor under Inventory application.
    Thanks
    satish.

    Hi Sathish
    BX datasource is only used to transfer initial stock. Is a full update datasource that is used once, after the stock init process. Thats why you can't find it in the cockpit (it doesnt manages delta and flexible structure, it's only to transfer actual stock). You have to activate that datasource in RSA5. You also have to activate UM and BF datasources in RSA5 before using them. The Cockpit activation is only customizing, it doesn't activates the "program" that makes datasource work.
    you can check this thread for more information: IM Scenario using 2lis_03_bx
    check this link for inventory
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31

  • Unable to change Extract structure MC03BF0 for DataSource 2LIS_03_BF

    Hi all
    In LBWE in R/3, I need the change the extract structure MC03BF0 for DataSource 2LIS_03_BF, by including some fields from MCMSEG pool. On including these fields from MCMSEG pool on the right side table to the left side table, and on confirming these entries, I get the following error message,
    ' Struct. from appl. 03 due to open V3 proc. not changed '.
    The long text for this message is :
    'Diagnosis
    Changing the extract structure MC03BF0 of application 03 is not allowed as there are no V3 update entries for the update module MCEX_UPDATE_03.
    If an extract structure is changed for which there are still open V3 updates, these can no longer be updated and the V3 collective update is terminated.
    Procedure
    Start the V3 update using the "Job Control" function in the customizing cockpit (transaction yDS:TRAN.LBWE>LBWE) or delete those update entries that are already incorrect. You will find these in the update overview.'
    Please guide me with what is to be done so that I can maintain the extract structure.
    Thanks
    Urmi

    Jelina,
    I think still some records available at SM13 clear it aswell.
    Clear records at LBWQ, SM13, RSA7, Setuptables in all CLIENTS of R/3 and check.
    Still a problem, then instead of enhancing datasource from RSA6, take extract structure name and enhance from SE11.
    P.S: Its better to create a new post by referencing same thread, so you can close call by assigning poings.
    Srini

Maybe you are looking for