Purchasing Delta Issue

Hello,
We were loading purchasing delta from the extractor 2LIS_02_SCL.
2 Days back there were support pack applied in R/3 and after that we are having failure of a job RMBWV302 and delta extraction to BW have stopped.
RMBWV302 is no longer running on the R/3 side that populates an extraction queue and it gives the error message
"Queue processing started (MCEX02, 100, , 0)
Extraction queue processing started MCEX02 with 27,184 LUWs
ABAP/4 processor: MESSAGE_TYPE_X"
Does anyone know how to fix, or can point me to a resource to get me back on my feet?
Thank you,

Hi,
You should follow the proper process to stop the LIS jobs and empty the delta queue and take the help of Basis in that.
Seems one of the queue was not maintained properly before patch application.
Now you can activate the extract structure for this data source again by activating it in the development system and doing the transports or if in production you have the authorization to do so.
Once done
Do a new initialization again to the target from R/3.
Do a full repair to the target for the days of the delta missed if possible by filling the set up tables before that.
Hope it helps
Thanks
Ajeet

Similar Messages

GI quantity Delta issue with 2LIS_02_SCL

Hi Friends !
We are facing delta issue in the BI Prod. Hence to look into the issue, performed few steps in Test environment to check whether delta is performing or not. Mentioned below are the steps which are carried :
1. BW Setup
a. Deletion of queues for Purchasing data in ECC
b. Data collection of purchasing documents for March 1 u2013 March 31 in ECC
c. Deletion of source system initialization in BW
d. Loaded collected data into SAP as delta initialization
Result - OK
2. ECC data entry
a. Created PO #5052422, intracompany STO from DDP1 to USC1
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
3. First delta run
a. BW brings over 2 schedule lines for PO #5052422
Result - OK
4. ECC data entry
a. Created PO #5052423, intercompany from DDP1 (USC1) to IRP3 (BV11)
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
5. Second delta run
a. BW brings over 2 schedule lines for PO #5052423
Result - OK
6. ECC data entry
a. Posted partial delivery for schedule line 1 of PO #5052422 with a quantity of 1
7. Third delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
8. ECC data entry
a. Posted partial delivery for remainder of schedule line 1 of PO #5052422 with and a partial delivery for schedule line 2 with a quantity of 1
9. Fourth delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
10. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052422
11. Fifth delta run
a. Both schedule lines of PO #5052422 brought over with updated delivery dates and goods issue quantities
Result - OK
12. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052423
13. Fifth delta run
a. Both schedule lines of PO #5052423 brought over with updated delivery dates
Result - OK
Ques :
1) When modified, GI quantity is not triggering delta. Please advise.
2) 2LIS_02_SCL extractor is build on which delta field.
3) How delta works & behaves with 2LIS_02_SCL extractor?
With Regards
Rekha

Good afternoon Rehka,
I believe that it is correct that the GL change you mention will not trigger a delta on the BW side. This functionality appears to be missing.
If you check in LBWE you will see that the EVENTS for 02: Purchasing -> MC02M_0SCL include the following:
MA: Purchase order
MB: Goods receipt
MC: Invoice receipt
MD: Scheduling agreement
The event associated with a Goods Issue is ML and not included in the list of events for this structure. This is the standard behavior.
I checked and I was unable to find a datastructure that does handle event ML. From what I see the only way to do this is through a custom datasource.
Kind Regards,
Des

Delta issue on a Generic Datasource

Hi
   I had a Generic Datasource on a Z table.
   The Z table had a Date field on which Delta is based.The Postings are performed manually.
How to solve the delta issue in the below scenario.
Ex; A user made a manual posting with a date 09AUG2010 today and delta is extracted to BW.
    But tommorow a used made another posting with a date 14JULY2010....
Currently that record is not being extracted....how can i resolve this
Thanks

Hi,
Once the data source is created you will extract the data till that date and as the delta is set it will fetch the newly updated records .But i dont think one can post with the back dates in R/3 side.
If i'm not wrong if you are asking regarding record got missed out them wht need to be done?
Then do the repair full request and pull the missed delta records and it wont effect the delta settings.
Regards
KP

Purchase Order - Issue storage location set mandatory entry

Hello All,
When create subcontracting PO, want to set the field of Issue storage location as mandatory.
I tried to find configuration "Materials Management>Purchasing>Purchase Order-->Define Screen Layout at Document Level", but there is not entry "Issue storage location" to set the screen layout field.
I searched previous threads, but only find some to mention issue storage location for STO. Now, I just use subcontracting PO that is same as NB document type.
Please your kind suggestion or any method to set Issue storage location as mandatory in PO.
Thanks very much!
Mag

Hi ,
Please, could you re-check it again, I have found storage location and issue storage location fields under define fields for fields selection group.
Under Field selection group NBF Purchase order
Selection group                    supplying plant
Issue storage location required entry chose
Under Field selection group NBF Purchase order
Selection group                    Basic data item
Storage location   required entry chose
After this setting, I can be find this storage location fields as Mandatory.
Regards,
Thiru

Delta issues between two DSO's

This issue has been a recurrent one over past years, so maybe someone can explain me what is happening here:
The case is always the same, i.e. I try to load a delta from one DSO into another one. Let's call them DSO1, and DSO2. More in detail, the case is as follows:
1. I get an error when loading DSO1 to DSO2, due to some characteritic value's checks that I have implemented in a start routine.
2. I delete the red request from DSO2, and manually delete the wrong entryfrom DSO1.
3. I reload (full) the deleted records into DSO1, with the corrected values. At the end I check that my data into DSO1 is correct, and that the wrong record has gone.
4. I then reload a delta from DSO1 into DSO2, but I still get the same wrong record transferred, even if the record does not exist anymore in DSO1 !!
My guess is therefore that the data for deltas is fully saved in separate tables, instead of being compared at runtime. Does anyone know if my assumption is correct...If yes, how can I find this table? Is there anything I can do to solve this issue?

The error is not very important...I have implemented a check so that a field is never transferred empty. The field is not empty anymore in the source DSO, but it still exists in the change log table...Can I do something about it?
With other words: Can I force the change log to be recreated as the difference between my two DSO's, instead as a package of changed records...?
Edited by: TTBBRR on Mar 22, 2010 1:43 PM

Delta Issue in Generic data source

HI all ,
    I have a HR generic data source .which extracts only two records ffrom the source for so many days during delta.
   I checked in RSA3 .It shows 16000 records nearly. I did init without data transfer and then delta,still it picks onlys same 2 records .
   Delta setting in RSO2 is Numeric pointer with new status for changed records with field name as"cheque number"
   In BWdatasourceExtraction tab--Deltaprocess is AIE After Image by extractor.Iam not able to choose any other delta process type as it is built from R/3 .I think because of this process type.
anybody faced the same problem .. I tried many ways.. please guide me how to solve. this issue.

HI Prashanth,
                    I checked RSA7 now and I found the problem .In RSA7 the pointer for cheque number is 991749. The delta record created has cheque number 005409 which is lesser than the pointer ,thats why the record is not picking i guess.
       now ,If this is the case ,How can I give delta field.The generic datasource is built on only one table PAYR ,and having cheque number and other fields as keys in the table PAYR.Date is not a key in the table. Please help how to proceed
Thanks
Rgds
Pradeep

GL Transaction delta issue!

Hi
I am using OFI_GL_6 for GL trans data. I have done a succesful initialization. Now when I do the delta, it brings 0 records. I have used this datsource in a couple of other places but I haven't had any issues with the delta. I have a couple of questions:
1.Is there any specific setting that needs to be done for this in R/3
2.Is the extraction method the same as in FI Line item?
We are on: 3.5 SP13 and Content 3.53 SP 5.Has anything changed with this new content and server versions?
Rgds
Anand

Thanks. No. I didn't load immediately after the init.I have been trying the delta for the past two days everyday.Also when I had a look at the BWFI_AEDAT table, not all of the docs are in.Does the table get updated as soon as the doc is created/changed or there is some time delay there as well? I am perplexed. Any suggestions pls.?
Cheers
Anand
Message was edited by: Anand Nataraj

2LIS_04_P_COMP and 2LIS_04_P_MATNR delta issue

Hi experts,
I am having problems with 2LIS_04_P_COMP and 2LIS_04_P_MATNR delta extraction.
I run the init, it is ok. I create an order and then I run DELTA expecting to get more record(s).
DELTA will bring no records. But if I delete set up tables LBWE, initialize them again, and then run the init again, the new records will be available.
Has someone had the same issue? I can't find the reason why the delta extraction does not bring the new records, if I don't re-setup the tables in LBWE.
Thanks in advance for your help,
Best Regards,
André Oliveira

Thanks for your help.
In job control window I do not have the green check button, only the cancel (red cross). When I try to schedule the job it gives me an error "error creating a job", so only I can do is save a start date and periodicity in job parameters. Is this ok?!
I also wrote sap a message because I am trying to enhance it with two fields (they are in LBEW), but same happens... I just see a cancel button, never a green check to validate and accept. I have done all the recomendations. I put the message I wrote below hoping you can give me some insight on this issue:
am trying to do an enhancement to extractor 2LIS_04_P_COMP.
+I go to LBWE and select these 2 fields:
MCAFKO GAMNG Qtd.teór.
MCAFKO GMEIN UM básica
The problem is that in the selection window to select these fields from
pool (scroll down box) to selection criteria (scroll down box) the
button to accept these changes does not appear (I mean the button with
the green check). So it is impossible to add this fields to the
structure. Is there any reason for this not to appear?
I think I have done everything that was needed:
LBWG: delete setup tables for 04 (production application)
RSA7: delete 04 queues
LBWQ: delete 04 queues
LBWF: check for active maintenance logs (does not exist any)+
Some points already assigned.
Best regards,
André Oliveira
Edited by: Andre Oliveira on Feb 23, 2010 12:01 PM

Purchasing group issue

Hi,
I am trying to assign an output type for PO printing to a P.Grp using T.Code MN04.I already assigned it but the output is not getting determined in PO.Where as, if I do the same thing for any other P.Grp. its easily getting determined.
The issue is only with one P.Grp.
Can you please suggest what can be the problem?
Ashish

Hi
Check, if you have created the Output determination using the Txn MN04, If you try to create the same combination again in MN04 it should not allow you. Check the condition Recodr details in MN05 in the second screen enter the Doc. tyep /Purchase orgn/vendor which you have already created and execute you should be able to view the detailsinside if not then the condition is not there.
mean whil how did you create an output type condition record based upon Purchasing Group ? The existing Key combination does not contain any Pur grp. reference but Only Purchase Organisation only
for two of the selections.
Regards

2lis_11_vascl and 2lis_11_vaitm delta issues

Hi ALL,
I am pulling data from Sales order datasources like 2lis_11_vahdr, 2lis_11_vaitm, 2lis_11_vascl, 2lis_11_vasti and 2lis_11_vasth.
I have some problem with standard extractor of 2lis_11_vascl and 2lis_11_vaitm of not capturing the delta properly. I am currently analysing the issue.
Could any one please clear my below doubts.
1. When ever there is a change to schedule line 2lis_11_vascl to a sales order - does the header and item level also come as a delta?.
2. Secondly i find the delta is correctly captured in Item status datasource 2lis_11_vasti whereas i am missing many documents in item level details datasource 2lis_11_vaitm. Have any one faced this issue. Really finding it difficult to debug the standard extractor.
I could sense that i am missing documents in item level only for a particular item category(Third part order).
It would be great if anyone could explain the above two questions to clear my doubt.
Thanks,
Aravind

Hi Fazal,
Please find the details below
2LIS_11_VASCL : This DataSource provides the BW with data from the Sales area and supplies the InfoSource
                                2AF_SD_SLS_1 with data. Extraction records are generated for the sales order event.
2LIS_11_V_SCL : This DataSource provides the BW with data from the Sales area and supplies the key figure Open Order
                              Quantity in the InfoSource 2AF_SD_SLS_2 with data. Extraction records are generated for the sales order
                               and delivery events.
For More details check the below link :
http://help.sap.com/saphelp_nw70/helpdata/en/ba/0b853c01c89d7ce10000000a11405a/frameset.htm.
Note : To understand more about the open order quatity and sales order details contact SD Cconsultat.Then you will understand about the details.
Regards
Ram.

ODP Data Source Delta issue 2lis_11_VAHDR 2lis_11_VAKON

Hi Expert,
I am pulling the data from SAP using ODP data sources. 2LIS_11_VAHDR 2LIS_11_VAITM 2LIS_11_VAKON.
For all the data sources I am doing the initloads. For 2LIS_11_VAITM data source after init load its enabling the delta.
For remaining data sources even if you try to pull the delta it's loading full load.
Steps I am following
LBWG do the deletion of setup tables.
OLI7BW fill the setup tables.
Run the data services job which pull the initial load. It loads all the data.
Change the ODP data source settings to Init load to No (Capture only delta)
In SMQ1 all the delta records will be captured
Run the Jobs which pull the delta records to ODQMON from there if you run Job in data services it has to pull the Delta records.
This is happening for 2LIS_11_VAITM but not for other data sources 2LIS_11_VAHDR and 2LIS_11_VAKON.
Event if you try to pull the delta records its loading all the records.
Can some one throw some light on this
Regards,
Murali.

In RSMO, go to the details tab and check in which stage the load has failed. If the issue is with extraction then go to Environment > Job Overview in the source system. Check if this job is complete.
I hope you must have cleared the Delta Queue, so now go and check if any entry is being displayed for 2lis_11_vahdr

0COSTELMNT_ATTR delta issue

Dear Group,
We have a delta load step for 0costelmnt_attr in one of our Process chains.This step failed with an error message-
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
On getting into monitor , the Status tab says" Error occurred in Data Selection".
I tried performing an Init with data transfer and it was successful. However the delta load followed by init failed again . Henceforth, On trying to repeat this step in process chain or when tried to manually schedule the infopackage,it said Last delta Incorrect.A repeat must be requested.But this is not possible.Please suggest what needs to be done to address this issue
We also created a new infopackage for 0costelmnt_attr with full update and schedule it manuallyand
Run the delta infopackage manually with init without data transfer. (this would fetch 0 records)
and we scheduled delta it gaving same error.
Please suggest.

Hi,
Did you tried the 'Repair Full load' and then do a delta load.
Regards,
Vishnu

INDIVIDUAL PURCHASE ORDER ISSUE

Hello Every body,
I have an issue in Individual purchase order. Created sales order with an item category TAB.
Just i tried delivery note VL01n: picking tab it is allowing picking quantity.
I am wondering, how system will accept.
i am not created any special stock: and again am verified delivery item category controls.
Could you please guide me, is't i have to verify any other controls
waitaing for your replies
Prasad.
Edited by: pilla.varaprasad on Aug 19, 2010 10:29 AM

For individual Purcahse order i have prepared document which might usefull for u.
http://www.scribd.com
search ---
15806527-Individual-purchase-order-Configuration-document-ERP-SAP-ECC
15806698-Individual-Purchase-Order-End-user-Document-ERP-SAP-ECC
possibilities: Check in OPJJ avaialble check and checking rule

Generic Delta issue..

hi experts,
i have created Datasource based on view which is based on EKPO and EKBE tables.
i have date fields BUDAT, CPUDT and CPUTM.
I have selected CPUDT as Delta Field.
select Calendar Day and Safety Interval Upper Limit as 1.
I have initialized yesterday, though the records are created and i can see the new records with today's date, in RSA7 i cannot see any records.
what is the issue in it, do i need to change delta field as CPUTM as it is time.
if yes then how can i set the Delta to capture the Delta Records?
regards
venuscm

Hi,
All three fields are from EKBE table, so kindly check whether there is any change in source system table EKBE, for these fileds for the new records created.
New record created will be updated in table EKPO and EKKO only.
Also make sure that delta field should be one of the extracted field in your generic extractor.
wish u all the best
Regards,
Vinod

Delta issue

Hi Gurus,
I added a new field MCODE in 0vendor_attr and this field is populated by user exit(SMOD). But when user change MCODE in source sytem why that record is not coming as a delta record. Any advice.
Thanks
Pramod

I think this is due to the delta mechanism in the SAP R/3, actually the delta will pick the changes to vendor master only, if the user modifies the MCODE field alone (since it has no impact on vendor master),the delta won't pick the change, because the vendor delta will look for vendor master change..
to overcome this issue, u can make the full upload once a week, so that the routine will pick the field value and update the vendor master...
Hope I asnwered ur query...

Purchasing Delta Issue

Similar Messages

Maybe you are looking for