RELEASE STRATEGY IN BI CONTENT

Question

Hi !
Do we have Release Strategy or work flow in BI Content of BW  Release 3.5 ?
I have to display a history of purchasing requisitions and orders that was uploaded from SRM.
Thanks !!!
Zelda

Answer 1

There are couple of approaches that can be taken with this issue since there are delivered extracters exclusively for Purchasing Requisitions.
1) Piggy back on PO ITEM Extracter (2LIS_02_ITM) or PO Schedule Line Extracter (2LIS_02_SCL).
Purchasing Requisition/Items (Table EBAN, TCODE ME53) are uniquely linked to PO/Item (Tables EKPO, TCODE ME23N).
PO Item (EKPO-EBELN & EKPO-EBELP) are linked to (EBAN-BANFN & EBAN-BNFPO).
Based on this you can extract the required fields from EBAN in the User Exit for PO ITM or PO SCL extracter.
This is what I did but my case was not same as yours. We primarily need PO Item/SCL information with some pertinent attributes from the requisitions
Pros: No need to write a seperate extracter.
Cons: If there are any requisitions that are not converted to PO's they will not be included in extraction till such time they are actually converted to PO's
2) As Bala indicated , Create a Custom extracter based on Table EBAN.
Pros: All Requisitions are extracted regardless of whether they have been converted to PO's.
Cons:
1) I am not certain if Generic Delta will successfully trigger all Changes to the Requisitions (depending on how the P2P process is configured for your Project).
2) If Delta does'ent work in all scenarios then a FULL load might be very difficult to manage based on the Data Volume.
Hope this helps.
Thanks
Vasu