Setup of Lis. extractor

Hi !
Can I get a material of the process of setup and automatic uploading of Lis. extractor ( 2LIS_13_VDITM, 2LIS_03_BX - compress process etc. ) .
Thanks
Moshe

Hi,
Please take a look at the inventory management doc.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Regards,
®

Similar Messages

  • How to make LIS Extractor nightly full load

    Hello All,
    We need an LIS Extractor to be a full load.  It appears Full Load only reads setup tables.  How can we do a full load for a LIS Extractor?
    Thanks!

    Hi All,
    Here is our scenerio:
    I am referring to the LO Cockpit. 
    We have deltas coming over to a DSO that has a key of order number, material and batch.  Now, when the order is created, for example, it will have batch NULL because we have not determined what batch to use yet.  It could remain like this for days.  In the meantime this record comes over to BW...just fine and updates.  Now, we have decided for this order that exists in BW with a batch of NULL that we allocate a batch to it now.  Now this record comes over to BW and it creates a new record.  So we have 2 records in BW, one with batch NULL and one with batch updated.  We really only want to see the record with batch updated.
    We also thought about, what happens if we assign a batch (after the record came over to BW as batch NULL), then this creates 2 records as mentioned above and then now we change this batch to yet another batch.  Now when this record comes over to BW this order will have 3 records by batch, yet only the latest is valid.
    So we thought a full load would work, which it would.  How do you handle such a scenerio for deltas?  We load to DSO as mentioned and then push to a Cube.
    Thanks

  • Delta load - LIS extractor to several target - test load to single target

    Hi
    I want have a daily delta load from a LIS extractor to 3 targets (ODS's). I would like to make a test delta load to one of the 3 targets (because it has been reconstructed).
    Will it cause any problems if I make a delta load from the LIS extractor to one of the targets and not all of the targets? Will the records that I loaded in my test load arrive in the two other targets when the daily delta runs later on?
    Kind regards,
    Torben

    Hi Torben,
    you can do this if you first load the data to PSA, because when you load the data with delta infopack the delta queue will be reset in source system. But the data will remain in PSA, so you can upload again (to same infoprovider or different one if update rules exists) from PSA.
    Sarhan.

  • LIS extractors with 2 BW systems

    Hi
    Is it possible to have a single source system with LIS extractors going to 2 different BW systems? This is part of a migration from an existing BW system to another (various reasons.)
    Do you have to do another initialisation on the new system?
    Thanks

    Hi,
    Definately we can go with Multiple BW sytems with one Source system. For more information on this refer the note : 775568
    Regards,
    Anil Kumar Sharma .P

  • Extension of LIS extractor - possible to delta enable field from Z-table?

    Hi Experts
    We have to get data from a date field in a custom Z-table (delivery related) in R/3 to BW.
    We would like to get the date by extending a delivery LIS extractor with a new field and make some ABAP to lookup the correct value in the custom Z-table.
    A requirement is though that if the date in Z-table is changed then we need to get the update value to BW. Therefore, we need to delta enable the new field in the append structure - but that ain't possible is it?
    Alternatively will we have to make a new DataSource based on the custom Z-table and somekind of full load (with a fake delta).
    Thanks.
    Kind regards,
    Torben

    Torben,
    If your custom Z-table does not contain too much data and doesn't change too often it might be an option to turn on DB logging (Technical settings ->  Log data changes). Do not do this for large tables containing transactional data as the logs will consume a lot of diskspace!
    Each insert/mod/deletion will be logged and in in a user-exit you can use FM DBLOG_READ_WITH_STATISTIC to check if something has changed and then append the corresponding data to your data package.
    Grtx!
    Marco

  • Selective Deletion and Data Load from Setup Tables for LIS Extractor

    Hi All,
    We came across a situation where one of the delta in PSA was missed to load in DSO. This DSO updates another cube in the flow. Since it has been many days since this miss come in our knowledge we need to selectively delete data for those documents from DSO & Cube and then take a full load for the Documents filling the setup table.
    Now what will be the right approach to load this data from setup table > DSO > cube. There is change log present for those documents and a few KPI's in DSO are in summation mode.
    Regards
    Jitendra

    thanks Ajeet!!!!
    This is Sales Order extractor, the data got loaded to ODS just fine, but since the data is coming to ODS from different extractor. Everything is fine in ODS, but not in the cube. Will Full repair request and Full load would it make difference when the data is going to cube? I thought that it would matter only if I am loading to ODS.
    what do you mean "Even if you do a full load without any selections you should do a full repair ".
    thanks.
    W

  • LIS Extractor

    Hi people
    I have activated the business content and i have some problem in the SD Scenarios. In the phase of ectraction do not work properly. I talk with an expert that say's to me there's a problem about LIS extracotor. I say that this extractor must be inzialized and configured. It's true? How i can do it? The expert say to me that's an hard work and givo to me no other  information. Help Me!
    P.s
    Sorry for the English

    No one can tell me the solution?

  • Which Setup Table for extractor 2LIS_08TRTLP

    Hi,
    Can anyone guide me which setup table i should execute if my extractor is 2LIS_08TRTLP?
    Thanks for your help!!
    Onn

    Hi Swetha:
      Use Transaction code SE11 or SE16 on R/3 to make sure the underlying tables used by the 2LIS_08TRTLP Extractor contain data. The main tables are:
    VTTK - Shipment Header
    VTTS - Stage of Shipment
    VTTP - Shipment Item
    LIKP - SD Document: Delivery Header Data
    LIPS - SD document: Delivery: Item data
    For the relations among the Tables take a look at the paper by Christopher Solomon "SAP Tables Relations", just google it to download a copy of the PDF file.
    Regards,
    Francisco Milán.
    P.S. One more thing: go to Transaction Code LBWE and make sure the DataSource 2LIS_08TRTLP is active, if not, activate it and fiill the Setup Table again.
    Edited by: Francisco Milan on Sep 2, 2010 11:22 PM

  • How to find where the code for append structures for LIS extractors?

    Hi,
    I found 4 append structures for extractor 2LIS_03_BF,
    Out of 4 append structures, I found code for one, using where-used option. But in vain for other 3. Is it possible they didn't transport the code for remaining structures? how to find that?
    Cheers,
    Kannan N

    Kannan,
    When ever you apply a logic to populate tdata for the appended filed then you will be writing some code in CMOD transaction code where you will find a ZXRSAU01
    program, just double click on that then it will take you to the complete exit. Ther you can find with your data source name.
    Hope it helps...
    ****Assign Points if it helps******
    Gattu

  • LIS Extractor (LE Shippments)  Direct Delta, no queue visible

    Hi gurus,
    I am new in data extraction and I have the following problem:
    I am trying to set up the datasouces for deliveries (application 12) through the cockpit.
    I have set the update mode to Direct Delta, I have deleted the setup tables, then performed initiaization. Everything seems to be ok BUT when I check RSA7 and SMQ1 for these queues, nothing is displayed. Ofcourse, I check after making some changes to one delivery.
    Previously, when the update mode was Queued Delta, I could see these changes in SMQ1 but not in RSA7 (there was no queue at all).
    Because I was not allowed to change the update mode as long as there were records in the outbound queue, I deleted this queue in SMQ1 and now, after changing it, it's no queue at all in the outbound queue monitor.
    I hope I described the problem clearly and I hope you can help me. Points will be rewarded.
    Thanks!
    null

    Hi Andreea,
    Please see the following pdf for an explanation of the various update modes:
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7312ec94-0501-0010-0da3-a49815566423#426,15,New Update Methods (II)">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7312ec94-0501-0010-0da3-a49815566423#426,15,New Update Methods (II)</a>
    For deliveries I would recommend staying with queued delta.

  • How to get two fields with same tech name in LIS Extractors?

    Hi Experts,
    I need "ERDAT" field from two structures (QMSM & QMFE) in 2LIS_18_IOTASK extractor.
    In LBWE first I moved ERDAT from QMSM. When I moved ERDAT from QMFE it gives an error:
    "Field with same technical name is already available in the Extract Structure".
    I don't want to create Append Structure as we need to write User exit.
    Can any one tell me how to get this field added in the extractor from QMSM and QMFE?
    Thanks for your help.
    Regards,
    Sree

    this is not possible as the all those fields are put in one structure. per definition you can't put the same field name twice in a structure, table in the data dictionary...
    hence, you really need to use an append and fill via user exit
    M.

  • Enhancement fields from ekko - LIS extractor

    Hi,
    I append in structure MCEKKO two fields (RLWRT and FRGRL from the EKKO table) but in order to come up these fields include in others releases and conflicts can be generated, I put them a "zz" at the beginning but preserving the data type.
    Then in LBWE transaction I added these fields using arrow buttons provided and I understand there is no need to write user exit code to populate these new fields.
    Then the data source is activated with the changes.
    When I simulate 2LIS_02_HDR with the RSA3 transaction, these fields do not fill.
    The ZZ at the beginning would be the problem? What could be?
    I appreciate your help,
    Regards,
    Victoria

    Hi Subray,
    When I remove the ZZ a warning is showed.
    "Field RLWRT does not lie within customer namespace."
    But the activation is permitted.
    This is the procedure:
    "If they are new fields or fields which are only used in structures, you are recommended to change the field names and the reports which access them."
    "The field name for fields of database tables cannot be changed without the corresponding data being lost. It is only necessary to change the field name if the same name is used by SAP."
    But the field is the same by SAP, because is the same. :S
    Message was edited by: Victoria León

  • LIS Extractor Missing Data

    I am using 2LIS_18_I0TASK to extract data into BW.
    If the record(notification) in SAP is created directly in SAP via tcode then I get all the bespoke fields as well as the SAP standard ones.
    If the record(notification) in SAP is created via an interface into SAP then I dont get any of the bespoke fields but do get the SAP standard ones.
    I can see the data in the underlying tables in both cases and all the fields are in the extract structure MC18I00TSK.
    Any suggestions on how to fix this?
    Thanks

    hi yosuf,
    Pl go to OVL2 ( Maintain shipping point determination ).for the combination of
    shipping conditions ( from customer master, shipping tab) +
    loading group ( from material master) +
    plant ( delivering plant )
    > shipping point
    Maintain this.  Your issue will be fixed.
    Pl reward if useful.
    Thanks,
    Sadhu Kishore

  • Purchasing Extractors - Overall Limit

    Hello,
    I have a requirement for our Purchasing cube where I need to bring over Overall Limit.....I have tried to bring it over by creating a new field and populated in the user exit but I'm having issues....I think that partially because the LIS extractor uses processkeys for the amount  values and also with the Deltas the signs are not set up right.  For the purchasing experts out there, have you ever had to bring over Overall Limit?  Would you please share your thoughts and experiences?
    Thanks for your help!
    Helena

    Hi Dave,
    While running the Setup Jobs in transaction OLI3BW did you specify any selection criteria?
    Did you give sufficient Termination Date/Time ?
    Did you run the job in foreground or background?
    If background was the job successful?
    Regards,
    Praveen.

  • BW-LIS Extraktor - OLLIBW / LBWE

    Hi togehter,
    we are working with this really complex LIS-extractors to bring data into BW.
    In TA LBWE we activated under application 17 the datasources 2lis_17_i3hdr und i0notif. To get data we started the LBWE as a new run.
    Problem now is that in RSA7 I saw that the destination which was served last time was our testsystem. This time we want to serve the developementsystem. Where is the possibility to configurate which system will be served by LBWE run?
    Hope anyone can help me.
    Mirjam

    hmmm....
    you can't change the update method just like this without loosing data!
    the procedure should be the following:
    - ensure that no postings are done in source system for your datasource
    - run the update job
    - empty your delta queue(s) for your application (17 I think) for ALL clients (you need to load twice the data from your BW(s) clients: one for the delta + one to empty the "repeat" of the delta"
    - verify that no LUW are pending for your application in SMQ1
    - delete the init from all BW systems
    - change the update method
    - reinit your deltas
    - only after that you can release the source system to the users for posting transactions....
    Now if your need history data you'll have to fill your SETUP table for your datasources and reload the data...
    If you just init your delta now, you'll have to wait that some orders are created/changed. With the direct delta, the changes should be passed directly to your delta queue (without running the update job)...
    for more details check OSS note
    <b>LBWE: New update methods as of PI 2002.1
    SAP Note Number: 505700</b>
    hope this helps...
    Olivier.
    Message was edited by:
            Olivier Cora

Maybe you are looking for