Purchase Requisition data

[Former Member]

Hi folks,

I want to extract the Purchasing Documents (Purchase Reqs and Purchase Orders) into BW. I see that there are data sources (2LIS_02_HDR and 2LIS_02_ITM) for purchase orders. But there are no datasources for purchase requisitions.

Does this mean I have to create a generic extractor for extracting the purchase requisition data?

The PO data comes from EKKO/EKPO and PR data comes from EBAN/EBKN. Is anybody aware of SAP supplied extractors for extracting PR data?

Thank you.

Abdul

[Former Member]

Hi,

Purchase requisitions data from EBAN and EBKN is not supported for extraction by SAPs standard plug-in. Primarily because, requistions are considered as loose documents which can get deleted from the database tables directly (without having a trace) by factors such as MRP runs.

What SAP provides via 2lis_02_hdr, itm, scl is limited requistions data for those which have follow on documents created in the system. More often this information is not sufficient to requisition based reporting.

Options available : 1. Use generic data source based on EBAN and EBKN --> If the volume of data is not a constraint.

2. Create a function module based data source with a custom delta mechanism.

Just keep in mind requistions affected by MRP runs would have to be loaded as full loaded dropping data in BW.

Hope this helps.

[Former Member]

Thank you guys. Before jumping into creating the generic extractor, I figured I will check with you all on this board. I will assign you all points for helpful answers.

Pradeep, I agree with you - the generic extraction will not be as efficient as the SAP generated extractor. If you do find the content extractor for PRs, please let me know.

Thanks.

Abdul

[Former Member]

Depending on the data you need from purchasing request, you can enhance the existing datasources for purchasing data.

[Former Member]

Hi Pradeep/Govind,

Thank you guys for looking into this. Appreciate it!!

Pradeep,

I was also of the view that the purchasing document header and the item includes both POs and PRs. Because SAP is calling the datasources as "Purchasing Doc Hdr" and "Item" not "Purchase Order Hdr" and "Item". Because purchasing documents can be of many types, I was assuming that all are included in this one hdr and item datasource. But the 2LIS_02_HDR and ITM only contains the POs because they are sourced from EKKO/EKPO.

Govind,

2LIS_02_SCL contains the scheduling details/arrangement from EKET table and it only has a reference to PR document and the item number. If you look at the comm structures they are being sourced from EKET/EKKO/EKPO only and not EBAN/EBKN.

Correct me if I am wrong with my findings so far.

Abdul

[Former Member]

Abdul, i have been looking through your situation. I totally agree with you as i have been trying to look and see if any where i can get hold of this Pur Reqn data.

We definitely have an option wherein we can generate a Generic Datasource depending on the Table-View and get data from EBAN/EBKN. But this impacts performance at some stage. I dont suggest this unless it a do or die situation. I will keep working on this and keep me posted if you find something.

Pete

[Former Member]

Hi Abdul kaleem,

Yes you are right . There is no standard extractor to push the data regarding Purchase requisition .So here you have to dependent on Generic extractor.

With rgds,

Anil Kumar Sharma .P

[Former Member]

Pradeep,

Thanks for your reply.

What I am seeing in LO Cockpit is that there are extractors for PO data, but there are no extractors for PR data. The 2LIS_02_HDR & ITM that I mentioned above, extract only the PO data. Are you aware of any extractors for extracting the PR (Purchase Requisitions) data from EBAN/EBKN tables?

Thanks.

Abdul

[Former Member]

Abdul,

I was about the view that all the Procurement Data which here Reqs data (EBAN/EBKN) is also extracted with the same. Lemme see and get back to you accordingly.

Thanx for pointing this out.

Pete

[Former Member]

Hi Abdul,

The data source you are looking for is 2LIS_02_SCL. i.e. Purchasing Data (Schedule Line Level). If that data Source does not appear in LBWE, you should transfer that from RSA5 and activate it in RSA6. You wil then see that in LBWE.

Thanks

[Former Member]

Abdul, I am not clear what exactly you want. What i understood from your questions is How to extract Purchasing Data...If i am wrong let me know???

But Purchasing data is done through Logistics Cockpit or also called Lo-Cockpit. And all you need to do is use the standard extractors or enhance if all your fields are not being populated with data. If you need the step up procedure i can send you some documentation and these are also available in SAP Service Marketplace.

Pete