FULL is not FULL ? - extractor 2LIS_02_SCL

Hi Experts,
I have a problem with the loading from R/3 to BW regarding extractor 2LIS_02_SCL
Earlier we loaded the infoprovider in BW with DELTA but now we want to use FULL instead.
Theproblem is that our FULL load do not seems to get everything without filling a new SETUP
I have an exemple:
The FULL Load before filling a new SETUP shows a old Delivery Date, the user have change the date I ME38 in R/3 but
after filling a new SETUP the new date appears.
We have tested to set the InfoPackage to Repair Full Request but no difference.
Please help me to describe this and why FULL is not FULL.
Regards
Kerstin

Hi,
The information I had was that you only use SETUP table when to make an INIT-load and that FULL loads is independent of the SETUP but as I understand from you guys is that LIS extractors have to have a new SETUP table when to make a new FULL also. Correct?
I don't want a daily full load of 2LIS_02_SCL, that was only an exemple
Regards
Kerstin

Similar Messages

Full extractor does not load all the g/l accounts

Hello experts,
I have a empy DataStore Object (ZFI_O02) and I want to load the information (g/l accounts) with a full infopackage. The load have the status of "Green" but when I check the information I have accounts without some documents. I do not know why my full extractor does not load correctly all the information.
I test the DataSources (3FI_SL_K2_SI) with the Tcode RSA3 and the test shows the all the accounts with all the documents.
Others tests -> I used the same infopackage (full mode) and restrict with the 0FISCPER (2010) and 0GL_ACCOUNT (Account Number) checked the PSA and I have the acoount with all the documents.
-> I used the same infopackage (full mode) and restrict only with the 0FISCPER (2010) checked the PSA and I have the account with one document missed.
Please help me.
Regards
Jeanette

Hi Jeanette,
Looks like the data is getting overwritten in the DSO. This usually happens when there are records with same Key Fields and also has certain characteristics that are unique but not key fields.
I suggest, you take a subset of a GL for which the data does not match, then compare the entries in the DSO and the PSA.
For Eg: If Business Area is not the key, then the data for all the same business areas will be overwritten. Thus making the BA key would eliminate the problem.
Hope this helps.
Regards,
Gaurav

Extractor 2LIS_02_SCL -- behaviour when ELIKZ is set

Dear BI-colleagues,
we are actually facing an issue with the standard extractor 2LIS_02_SCL - schedule line Level of purchase orders.
Our system setup:
The data of this extractor needs to be used to measure a supplier service sevel based upon single schedule lines. My predecessor actually changed the standard definition of this extractor in the System (which might be a reason for our issue?!).
In the BW-System, one standard staging DSO has been created with the folling key:
- PO document number
- PO document position
- PO document schedule line
- field BWVORG --> process key to distinguish between purchasing, goods receipt and invoice receipt data
Coming to the issue....
We are using the following fields to measure the (on time) Service Level:
SLFDT statistical delivery date           = "to be" date
BUDAT booing date of GR / IR           = "as is" date
--> whenever the BUDAT is higher than SLFDT, the delivery was not in time
In case a purchase order position has more than one schedule line, we get into trouble using this logic. When the final delivery indicator (field ELIKZ) is set on position level, there are update records passed to the BW for all schedule lines of this position showing as BUDAT the date when ELIKZ was set. Example:
Record      Record date     Sched. line     SLFDT               BUDAT               Comment
1               01.04.2014          1                    01.04.2014     01.04.2014          on time
2               10.04.2014          2                    10.04.2014     10.04.2014          on time
3               15.04.2014          3                    15.04.2014     15.04.2014          with this partial delivery the ELIKZ was set
4               15.04.2014          1                    01.04.2014     15.04.2014          not in time
5               15.04.2014          2                    10.04.2014     15.04.2014          due to record 3, a new BUDAT arrives for line 2 --> not in time
Unfortunately it's not as easy as e.g. just deleting incoming records having the same BUDAT as the last schedule line, as there are some intended processes which can lead to a later BUDAT (e.g. cancellations, corrections...)
Does anyone know if this is the Standard behaviour of this Extractor? How can I solve my issue?
Thank you in advance,
Andre

Dear Gajesh,
thank you for your remark.
Yes indeed the schedule line is in the key of the staging DSO. But as already said, the issue is that there are update records coming for ALL schedule lines whenever the ELIKZ is set on Position Level. From my Point of view the correct behaviour would be to deliver only update records for the last schedule line (the latest line). In my example the records 4 & 5 should never arrive in the BW system.
On BW side there are no modifications done for this Extractor.. the above mentioned examples are taken out of the PSA table, not from the DSO.
My requirement is either to stop transferring records 4 & 5 and/or to filter them somehow out in the BW-System, which is - from my point of view - almost impossible. I've already done a deep analysis of the incoming records in the PSA table and I couldn't find any way to separate these records from other, correct ones.
You said my example is not the standard behaviour... What would it be in this case (and how to restore standard)?
Thanks and best regards,
Andre

Extractor 2LIS_02_SCL and AFS-Contracts

Hi together,
we use in our AFS-system contracts with schedule-lines and
we need the contract-information in BW.
The extractor 2LIS_02_SCL don't extract this infomations.
Someone can help me.
Thank you in advance

Hi Roberto,
i have found my problem:
Report: LMCRSF01
Form: ANREICHERN_EKET
Tranfer Mengen/Werte zuweisen
      CASE zeitp.
        WHEN con_zeitp_bestellung.     "Bestellung
          xmceket-bwmng = xmceket-menge.
          xmceket-bwgeoo = xmceket-menge * x_effw.
          xmceket-bwgvo = xmceket-menge * x_vpom.
          xmceket-bwgvp = xmceket-menge * x_vpmm.
        WHEN con_zeitp_we_zu_best.     " WE zur Bestellg
          xmceket-bwmng = xmceket-wemng.
*... Only for valuated GR
          IF xmcekpo-weunb IS INITIAL.                      "558508
            xmceket-bwgvo = xmceket-wemng * x_vpom.
            xmceket-bwgvp = xmceket-wemng * x_vpmm.
          ENDIF.
          xmceket-bwgeo = xmceket-wewrt.
        WHEN con_zeitp_rechnung.       "Rechnung
          xmceket-bwmng = xmceket-remng.
          xmceket-bwgeo = xmceket-rewrt.
        WHEN con_zeitp_lieferplan.     "Lieferplan
          xmceket-bwmng = xmceket-menge.
          xmceket-bwgeoo = xmceket-menge * x_epom.
          xmceket-bwgvo = xmceket-menge * x_vpom. "Operat.: keine VP-
          xmceket-bwgvp = xmceket-menge * x_vpmm. "Operat.: keine VP-E
        WHEN OTHERS.
>> my comment : ignore      inquiry and contract
Nicht verarbeitete Vorgänge: z.b. Anfrage, Kontrakt <
          xmceket-bwmng = xmceket-menge.             <
          xmceket-bwgeoo = xmceket-menge * x_epom.    <
          xmceket-bwgvo = xmceket-menge * x_vpom.    <
          xmceket-bwgvp = xmceket-menge * x_vpmm.    <
      ENDCASE.
and i must solve this problem myself with
generic extractor EKET (Function module)
on the BW site consolidate item and schedule line in a new ODS
Thank's for trying to help me.
I hope the solution of this problem is helpful for someone
regards
thorsten

Extractor "2LIS_02_SCL".

hi
Anybody know how BUDAT fonctionne in extractor "2LIS_02_SCL".
best regard
francoise

hi,
check this out.
http://help.sap.com/saphelp_nw04/helpdata/en/8d/bc383fe58d5900e10000000a114084/content.htm
BUDAT u2013 Posting Date
If the information in this field relates to an event in the purchase order, the field is filled with the posting date of the purchase order. If the information relates to a goods receipt or an invoice, the field is filled with the posting date of the corresponding document.
regards,
mahesh

LBWQ entries are not loaded to 2LIS_02_SCL queue after run RMBWV302

Hi Guys,
I have some strange problem in R/3.
We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. The problem is when the user changes a PO (like G/L account change EKKN-SAKTO or changing sales person EKKO-VERKF) then delta entry will be created in MCEX02 queue (LBWQ) and the job to empty the entries to RSA7 queue was successful, the problem is here the SCL datasource shows 0 records in it where as ITM DS shows one entry in it. Even if I load data SCL brings 0 records and ITM brings 1 (changed) record......
What needs to be done to capture it in SCL extractor, any settings needs to be done???

Hi,
I have faced the same kind of issues; some we solved by implementing an IObj reflecting the PO#/Item# (compounded), having Nav Attr on it. The master data for this IObj is updated while loading the deltas of ITM and HDR.
Otherwise I also investigated a sophisticated scenario, which works but quite complex:
- the HDR and ITM deltas are also passed to the SCL content
- the start routine get all the corrresponding SCL loaded in the target, generates a reversal record for each of them as well as the same records again enhanced with the required objects...
This way would accurately store updated data howver it is a bit expensive.
hope this helps...
Olivier.

PO : Invoice value in ME23N is not matching with 2LIS_02_SCL field BWGEO

Hi Expert,
              1) Invoice value in ME23N tcode is not matching with datasource 2LIS_02_SCL field BWGEO in item level
for few item BWGEO field contain the data with tax but for few item the value is not coming correctly.
2) The value is not matching for that particular item which has same material document in other Item level.
eg. PO(eg 60000XXXXX) if item 1 has invoice value with tax is 1300+52 and its material doc is XXXX1234. if same material doc XXXX1234 is present in
item 2 for another invoice of same material invoice value with tax is 1200+48. In that case the value which is coming in
BWGEO field is 1300 only.
I am working in 7.0 system for AFS specific. My whole transaction is in INR.
Thanks and Regards
Lalit Kumar

Please review the information below from one of our deverlopers
- it may explain the behaviour you are seeing on your system:
When posting a GOODS RECEIPT for a DELTA UPLOAD process you only will
have the information regarding the GOODS RECEIPT values (XMCEKET-WEMNG
and XMCEKET-WEWRT) and not the invoice values (XMCEKET-REMNG and
XMCEKET-REWRT).
When posting an INVOICE for a DELTA UPLOAD process you only will
have the information regarding the INVOICE values (XMCEKET-REMNG
and XMCEKET-REWRT) and not the GOODS RECEIPT values (XMCEKET-WEMNG and
XMCEKET-WEWRT).
The DELTA INIT process is different, because for this process, all
information about posted documents against a purchasing order need to
processed again and this means that all documents related to an order
(invoices, goods receipt, deliver costs, goods issue, etc)
are read from database and rebuild one by one in the same process, and
of course this information in available.
When posting an invoice, the goods receipt information is not
available because of the following reasons:
1 - System standard fields.
In datasource 2LIS_02_SCL, there is only
fields BWMNG - that represents quantity, BWGEO and BWGEO that
represent values. The information under these fields are dependent
from the information of field BWVORG (BW transaction key). This field
determines whether these values are from a purchasing order, goods
receipt or an invoice. You never have a missing information, but when
you want to get goods receipt values, you need to check where the
BWVORG correspond to goods receipt process and not invoice.
2 - Performance
There are documents as purchasing orders and schedule agreements that
are opened for years in some customer system (it may not be your case),
where goods receipt and invoices have been posted during all this time.
Every time that a new document is posted in order to built the
cancellation sentence (ROCANCEL = X) and in order to add the new
value in the old, system need to process all previous posted documents,
and this means processing time. For this reason when posting invoices
only previous documents that are invoices are taken into account and
not goods receipt.
The delta fields, DBWMNG and DBWGEO, are the difference between the
purchasing order quantity and values and the goods receipt quantity
and values, then is natural that this information is only available
when processing a goods receipt and not when processing an invoice.
I'm sorry if this is not the system behavior that you are expecting,
but this is the normal standard behavior and this is really necessary
because of the system performance when dealing with documents that
have a long order history.
Hope this information is useful for you
Best Regards
Barry

REMNG (Invoice qunty) field not getting values 2LIS_02_SCL Datasource ?

Hi,
I have added the standard field REMNG field to the ds 2lis_02_scl and I am not seeing any values either in rsa3 or psa. Can anyone suggest if anyone have seen this problem before.
BTW in RSA6 ...field only is selected, so do we need to uncheck it ? As I dont see any code written in CMOD for it. Please suggest some clues.
Thanks,

HI,
After activating the datasource did you fill the setup tables again for that application.If not then give a try to it and see if it works or not.
In the mean time i will search on the same issue.
Hope it helps.
Regards,
AL

Purcahsign data tables for the extractors 2lis_02_scl and 2lis_02_itm

Hi,
Can any one tell in which tables the purchasing data is stored in R/3
Thanks in Advance
Dru

Hi........
EKKO >> Purchase document
EKPO >> Purchase document (item level)
EKPV >> Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item
EINA >>Purchase info record (main data)
EINE >> Purchase info record (organizational data)
EBAN >> Purchase requisition
EBKN >> Purchase Requisition Account Assignment
T024 >> Purchasing Groups
EKET >> Scheduled lines
EKES >> Vendor confirmed lines
Regards,
Debjani......

LPA changes are not reflected fully in 2LIS_02_SCL

The changes done to scheduling agreement, schedule lines are not reflecting in 2LIS_02_SCL, and there by resulting errors in delta update in BI system.
For example
     LPA     RM     SCL     Quantity                                    (2LIS_02_SCL)
ODS(A)      3001             15          800
ODS(C)     3001     X     15          300
     3001          15          800
PSA      3001     X     15          400
        3001             15          900
As we are using the Update type Addition,
From PSA, it is clear that the change is 500; this change got reflected in ODS properly.
But when I compare ODS data with EKET data,
LPA     SCL     ODS(Active)          EKET
3001     15     800               900
As you can see wrong validation results between BI & R3
I am missing the below changes happened to SCL in the extractor
     3001     X     15          300
     3001          15          400
The missing above entry is resulting errors.
Does anybody know how the EKET line changes can be tracked?
How to check the V3 Update, we checked the program: RMBWV302
Does anybody have idea where to track this error.
Note: the above case is happening to only a for few documents
Regards,
NK.A
Message was edited by:
        nandakumar a

Hi Renjith,
Thanks for the reply. Can you please let me know few more answers to the below points.
As the datasource 2LIS_02_SCL does not takes this event into account (only MA, MB, MC and MD), this field is not passed to BW (you can see the events per datasource in transaction LBWE)
You are referring to posting of the Material Ledger posting right ? Can you please give some more information about MA MB MC MD as I have verified in LBWE and could not find anything about it except that its picking that GLMNG value from MCEKET table.
Renjith, Please update your views on the below query. I am not able to get any answers from anyone on this query. I appreciate your reply.
In my opinion you would be able to fill it in the customer-exit of LIS (EXIT_SAPLEINS_001) or BW (EXIT_SAPLRSAP_001)
If I add a zfield to the SCL DS and then populate that field with the code in the include ZXRSAU01 , EXIT_SAPLRSAP_001 in that going to help.
Do I have to verify the events MA MB MC and MD while populating this zfield or I can just do a direct lookup on EKET
select single * from EKET
where EBELN = l_MC02M_0SCL-EBELN
and EBELP = l_MC02M_0SCL-EBELP
and ETENR = l_MC02M_0SCL-ETENR will do ?
So when ever the ds fields are getting populated in the org DS ...it will find this zfield in the same structure and will fill this field. Is that going to fix it ? I have also found couple of SAP Notes on the same issue and do you think implementing those notes will fix the problem without the zfield or code.
Could you please check out these notes 100690 and 431145. Please suggest.
Thanks,
Daniel

Starling lines with the 2LIS_02_SCL extractor.

Hi expert.
I have got a problem with the schedule line purchasing extractor, 2LIS_02_SCL.
I noted that the extractor extract many more lines that those present in a purchasing order. In particular, it extracts also deleted items and the corresponding starling items. When I speak of deleted items, I am not referring to those items whose fields LOEKZ is evaluated (these items appears in the order), but I am speaking of lines which does not appear in the order.
Now, I need to filter out these items. I saw that the deleted lines can be recognised through the field ROCANCEL.
The problem is: How can I distinguish the starling lines?
Can someone help me?
Thanks in advance
Andrea

Thanks Jain, but what you are suggesting does not resolve my issue. I try to explain me better.
The estractor estract one line, which is deleted (ROCANCEL = X). THis line has NETW = X and another fields, let us say AA not evaluated. Then I Have a starling line, which will have NETW = -X and AA not evaluated. Then I Have the right item, with NETW = Y and AA opportunely evaluated. Now, only the right line is the one that I have to carry in my DSO. In the PSA I have all the three lines, but unfortunately the last one (the one which goes in the DSO) is not the rigth one (but, almost ever, is the starling line for which the field AA, which is the field I am interested in, is not evaluated).
Very strange, isn't it?
Some ideas?

2LIS_02_SCL extractor is delivering wrong document currency amount

Dear all,
We are currently trying to get the invoiced amount of a purchase order in the document currency (of the invoice). While extracting the Purchasing Orders via the 2LIS_02_SCL we discover that the invoiced amount in document currency (BWGEOO) is wrong (if document currency is not matching local currency). However the invoiced amount in local currency (BWGEO) is correct.
It seems that the BWGEOO is calculated from the local currency field by using the PO header exchange rate (EKKO-WKURS). If we take the exchange rate (RBKP-KURSF) from the invoice header and apply it on the extracted invoiced amount in local currency, we get the correct value.
- Does anyone have some information how the extractor is working (which source table is taken into account)?
- Why is the local currency matching and the document currency not?
- Do you have experienced the same issue? Do you have any solution for this problem?
Thank you.
Regards,
    Michael

Hi,
There are several Notes around this issue, but none of them is solving our problem:
     856004 Invoice value and GR value in extractor 2LIS_02_SCL
     838670 Net value for BWGEO and BWGEOO
     833209 BWGEO and BWGEOO values
The field BWGEOO is delivering a cost based value in document currency out of the PO. This means it is calculating it (quantity * net price). But we needed the actual invoiced amount out of FI.
We found a work-around for this System Design issue. We are going to extract the exchange rate out of the invoice header and apply it to the invoiced amount (REWERT) out of the 2LIS_02_SCL extractor.
Logic to extract it is:
Join the Document Header: Invoice Receipt (RBKP) with the Document Item: Incoming Invoice (RSEG) on Invoice document number (BELNR) and Fiscal Year (GJAHR) key fields. Out of the Item table the purchase order document number (EBELN) and the PO item number (EBELP) can be derived. The exchange rates need to be loaded out of the header (KURSF).
Does anyone of you have additional documentation/information on how the LO extractors (e.g. 2LIS_02_SCL) are working and especially the details of the values (and the definition) out of the extractor?
Thank you.
Regards,
    Michael

Filling the 2LIS_02_SCL extractor.

Hi experts,
I am an abap programmer but i am now starting working on a BW project to become a junior BW consultant.
I am now trying to fill the extractor 2LIS_02_SCL. Qhen i go to the RSA3 transaction on the R3 sistem, i see that it is now empty. How can i fill it on the r3 system? it is the first time i'm doing this, excuse me if the quation is too basic.I'll later charge this data to the BW system.
Thank you very much!

Hi
Please have a look at the below url..it gives an idea how to go with LO extraction
LO step by step procedure
Hope it helps
Thanks,
Teja

Purchasing Data Not Tying Up between BW and R/3.

Hi,
As a part of our project, we reloaded the all the data related to Purchasing through the extractors
2LIS_02_SCL
2LIS_02_ITM
2LIS_02_HDR
As these were corrupted due to patch application.
We took all the possible care during reloading of all the data from R/3 like locking the user from making any transactions, Deleting the setup tables etc in a step by step process etc.
But however, after the extraction the data is not tying up between R/3 and BW Purchasing ODS.
Is there some thing wrong did we do or How can we get that missing records into BW again.
Appreciate your help.
Thanks.

Hi......
Did u fill the set up table with any selection...........?.....Previously no of records picked was larger than this time........right?..........Hav u checked RSA3 in the source system..........is it showing correct no of records........? if yes............then check the selection tab of the IP..whether u hav maintained any selection there.........
If no..........then......first check the selection in the set up table..............then the function module....which is extracting the data..........u will get the function module in RSA2.........there just double click on the Extractor.........u will get the function module name........
Anyways.........did u know which records r missed.........then just fill the set up table for those values only.........then do full load......
Anyways,............I think u know the steps in LO Extraction...........still for ur reference..........
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header...
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani...

Records not showing in Report

Hi All,
I'am facing peculair issue, We have an issue where inventory is showing in -ve.
From 2LIS_03_BF we are loading the data to DSO, from DSO again to Cube.
I can see Reocrds in Cube for a certian Plant , Storage Location and Material combinations....when I gave same selection criteria in Report the records are not shown in Report. I have checked Query designer too if there are any condition applies but there are no conditions as such expet Special Process Indicator K is excluded.
so i checked Special process indicator for that material but its not K.......its Blank.
Inorder to recover the issue, I have selectivdely deleted the material, Plant and Storage location combination and reloaded the data to cube and compreessed the request without checking No marker Update.
Please need inputs here.
SujanR

Hi,
Use 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to 0IC_C03 Cube and design the report.
Use :See the steps how to load the data to 0IC_C03.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
See some importent SAP Notes in Invventory Lods.
Note 747037 - Update of before images in ODS objects
Note 752492 - Non cumulative keyfigures are incorrectly allowed in ODS
Note 581778 - ODS capability of extractors from inventory management
Note 684465 - BWVORG for purchasing data sources
Note 417703 - Missing duplicate record during extraction with 2LIS_03_BF
Note 929378 - 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM and BI 2004s
Note 745788 - Non-cumulative mgmnt in BW Verifying and correcting data
Note 352762 - Collective note purchasing extractors and setup
Note 353042 - Howto Activate transaction key (PROCESSKEY)
Note 352344 - Process key + reversals in Inventory Management
Note 586163 - Composite Note on SAP R3 Inventory Management in SAP BW
Thanks
Surendra Kumar Reddy Koduru

FULL is not FULL ? - extractor 2LIS_02_SCL

Similar Messages

Maybe you are looking for