cancel
Showing results for 
Search instead for 
Did you mean: 

Some DOC_NO not extracted / missing in rsa3 datasource checker

Former Member
0 Kudos

Hi all,

Does anyone could give me a reason why some how we could not get / missing doc_no  purchasing doc no in extractor checker (rsa3)

Let examples

Some doc no not exits / not extracted in rsa3 , BUT exits in me23n.

1) Datasource

2LIS_02_SCL

2LIS_02_ITM

2LIS_02_HDR

FROM ECC : tcode : me23n.

any reason why? so something i could do ? filling setup table again, I did try but no success.

Thank you

Accepted Solutions (1)

Accepted Solutions (1)

former_member182346
Active Contributor
0 Kudos

Hi Edi,

If you are talking about the MM i.e. Purchasing docs.

I would like to say, the std. extractors of purchasing won't fetch the incomplete POs.

You will always get those many PO-Line item less in BW as compare to ECC (EKKO-EKPO) table.

Earlier, I spent lots of time in finding why ECC & BW not reconciling in number of records, and found above behavior.

Confirmed with functional team, and as they said, many users try to create test POs and wont mark them as complete, so that they are not considered as real PO.

SAP BW extractor too wont consider such POs as real PO and filter out.

Please let me know if you need any more details on this.

Thank-You.

Regards,

VB

Former Member
0 Kudos

Hi VB,

Quite good info, I will do check with functional on this, and let you know if any help I needed,

point awarded ..

Rgds

Edi.

Former Member
0 Kudos

Hi VB / team,

How if I'm going to extract also this doc event the PO no is dummy? because I face issues reconcile the data between ECC & BI due to this doc_no not been extracted

Rgds

Edi.

former_member202718
Active Contributor
0 Kudos

Hi Edi,

You can talk to MM Functional Consultant and do a detailed Validation.

He will give the Proper reasons for the data not matching and then take him to the Users who will convince the Users.

rgds

SVU

former_member182346
Active Contributor
0 Kudos

Hi Edi,

I guess that is how the std extractor works. And generally it should work like that only, because if you go on adding such dummy POs then the report will give the false info.

But although if you want to add such POs as well then I will say go with enhancement code.

Like in E_T_DATA, put ABAP logic to fill such records which are having status incomplete.

Take help of ABAPer if required.

Also Delta will be an issue since it is going to check the status of the POs which are not bought by std extractor, so staging DSO will be good idea.

Thank-You.

Regards,

VB

Former Member
0 Kudos

Hi VB,

How we going to changed the standard datasource logic? Is that possible to do that.. I know how to append the struc.. But never know we could change the std datasource logic.. Some clue and advise are appreciate.. You help me a lots ..

Thanks again..

former_member182346
Active Contributor
0 Kudos

Hi Edi,

I am not suggesting to Chang the logic of std extractor, but we can add records using enhancement code.

Say your std extractor bought 10k records and there are 5 such incomplete POs (which are not bought by std extractor).

So E_T_DATA will have those 10k records but you can write the code to get those incomplete records and then using append statement add those to E_T_DATA.

In this way you are fetching all 10K + 5 records.

But again suggesting, talk to your functional team first as you are challenging std functionality by adding such logic - which give rise to false info.

Thank-You.

Regards,

VB

Answers (2)

Answers (2)

former_member182470
Active Contributor
0 Kudos

Please increase Data Extraction /Calls while running in RSA3 in F mode.

To check the data in D mode, you have to intiialize the DS in BW .

RamanKorrapati
Active Contributor
0 Kudos

Hi Edi,

Data source      Base tables

2LIS_02_ITM -  EKKO,EKPO

2LIS_02_HDR - EKKO

2LIS_02_SCL -  EKO EKPO

Actually data sources pulls data from set up tables(for full loads). While filling setup-tables data was pulled from base tables of data source.

so pleas check the doc_no is available at base tables or not. if its availble then that doc no status or some thing data will be different compare to normal doc.

Doc status - canceled/not delivered or some kind abnormal status.

From RSA3 find the one doc no which was coming at RSA3.

Take that doc no and take another doc no which was not coming at RSA3.

Compare the whole record information. there might some differentiate will be there.

That may cause. please take SD team help.

Thanks

Former Member
0 Kudos

Hi Raman,

thanks for your prompt reply, do you think after we filling setup table it will extract all the DOC_NO from the base table ? does it have any condition which will exlcude certain doc_no? I don;t think it will extract all doc_no base on base table.. I still need to find why the reason , base on your comment it give me some clue , but it still not meet my issues. 

I take some another sample here..

Datasource                    Base Table

2LIS_11_V_SSL             VBAP        ( EBELN)

DOC_NO ,

60000008   (Coming from rsa3)

30000001   (Not coming),

I check  both DOC_NO in VBAP table, and both exits,

https://www.dropbox.com/s/50pzbbteqz3ts64/DOC_NO-Not%20in%20rsa3.XLS

But the 30000001  exits in 2LIS_11_VAITM.  The only difference was this doc_no was schedule agreement. Does 2LIS_11_V_SSL will not extracted the schedule agreement doc_no? I did check all the doc_no which under schedule agreement not extracted under 2LIS_11_V_SSL

is that any of SDN note regarding this matter?


RamanKorrapati
Active Contributor
0 Kudos

Hi Edi,

if possible try copy the same data into Dev environment.

Try debug the extactor  at RSA3, select debug check box. its may give some clue. why its not pulling doc no.

Some times there might be chance of extraction logic may exclude as per the logic. for that we need to debug the extractor.

"Does 2LIS_11_V_SSL will not extracted the schedule agreement doc_no? I did check all the doc_no which under schedule agreement not extracted under 2LIS_11_V_SSL"

Might be, its not pulling them. just debug the extrcator  you will find the reason.

Thanks

former_member202718
Active Contributor
0 Kudos

Hi Edi,

I Guess , we are talking two different things here.

1 ) MM Module - 2LIS_02_SCL/ITM/HDR

2) SD Module - 2LIS_11_VAITM

The document number related to SD will come in MM.

DOC_NO ,

60000008   (Coming from rsa3)

30000001   (Not coming) - Is This a Purchase Order,if YES then it shud come in MM Flow.

Can you check what is this 30000001 refer to.

Rgds

SVU123

Former Member
0 Kudos

Hi Ramanjaneyulu Korrapati,

I did tried to debug, but to debug the standard datasource, it not really easy to trace the source and how the flow of the data.

Hi svu123,

30000001 is NOT purchase order , this is schedule agreement no which I could view under va33, futher more I'm not using 1 ) MM Module - 2LIS_02_SCL/ITM/HDR   , but I'm using 2LIS_11_V_SSL.

Rgds

Edi.

former_member202718
Active Contributor
0 Kudos

Hi Edi,

2LIS_11* is related to SD Flow and the document numbers will be avaliable in tables  VBAK,VBAP.

2LIS_02* are MM Related Flow.

I could not understand as to why are you searching SD data in MM Module.

Can you explain the business Scenario so that we can understand that and then suggest.

rgds

SVU

Former Member
0 Kudos

Hi svu123 svu123,..

Thanks for your reply,  I'm NOT using MM datasource 2LIS_02*  fo SD doc flow.. Might be I get you guys confuse.. sorry yah .. here the real situation :- both I explained above was 2 separate difference issues which mean both datasource have same issues representative it's own module.

I've same issues on both datasource

1st issues

1) 2LIS_02_ITM -  EKKO,EKPO

( For this same thing why some of doc exits in EKKO but when I do test in rsa3 it's exits for this DS)

2nd issues

2)2LIS_11_V_SSL             VBAP        ( EBELN)

(Same thing can see the doc extis in VBAP but some of them not exits in rsa3) ..

Rgds

Edi.


RamanKorrapati
Active Contributor
0 Kudos

Hi Edi,

Take the doc no 30000001, with help of SD/MM find the 3 series doc numbers. as my guess extrcator may not pulling the 3 number series, if yes then extractor logic will be correct.

at ECC side which view/part your reconciling with bw data.

As said by mate, Talk to SD/MM functional and team, get the requried info and inform the same to users.

Even if they are not convinced then raise to SAP and check it .

Thanks

former_member213275
Contributor
0 Kudos

Hi,

As per SAP Note : Note 1347563 - FAQ: DataSource
2LIS_11_V_SSL "Order Delivery"
question no. 5 says taht the DataSource 2LIS_11_V_SSL CANNOT be used for scheduling agreements with delivery schedules. This usage is excluded. Also see Note 782366.

Srikanth.

Former Member
0 Kudos

Hi raman,

Thanks for the info, you are right, ive already test and none of them are extracted.  And as what been mentioned by VB, its right , thats its because their using the dummy PO's. now need to think how im going to write a code to include this dummy's POs doc_no? Im going to ask my abaper.. But not sure wherei need to enhance.. I know how to append struc And using badi, but is that possible we chnage current logic std datasource to include this dummy POs?

Thanks guys..  alot you really help me

RamanKorrapati
Active Contributor
0 Kudos

hi edi,

you can add required field to Extract structure directly at SE11, give ext str name and click on append, give some name ZZext str, add fields.save, back,

appende fields will be added to yout ext str as last row.

go to RSA6, choose your data source, added fields was hidden, un hide it. save and back.

Go to CMOD, choose existing project, RSAP00001, Exit - EXIT_SAPLRSAP_001, INLUDE ZXRSAU01, double click on it, its take you to SE38   or Directly go to SE38 - INCLUDE ZXRSAU01, edit mode and maintain logic with help iof abap.save, syntax check and activate.

All changes capure in Transport request.

Do the test case at RSA3. if you field and data. then replicate data source into bw side and activate. do the rest of steps.

All changes move to prod once you got design as you needs.

Thanks

Former Member
0 Kudos

Hi Raman,

your step explain how to add additional field in existing structure.  I know how to do that, now the issues how we going to change the standard logic datasurce which currently not include dummy PO as the doc_no in the extraction.

Hope you get my point here.

Regards

Edi.

RamanKorrapati
Active Contributor
0 Kudos

Hi Edi,

Not possible and never do the changes to SAP Standard extractor.

Original extractor not pulling your dummy PO's. As my mate suggested to do enhancement. so in that you can add field which can hold dummy po's. To populate dummy po's you need to maintain logic.

Already you have existing field along with standard extractor. so you can hide that field. use this enhanced one.

Hope you may got it my point

Thanks