In my line of work, the high-level requirements for most developments are fairly straight-forward.
“I need a report that shows my on-hand stock quantity.”
“I need to see all returns for a given batch at a specific plant.”
The known requirements are easy enough as they allow a developer to locate the source table and fields and extrapolate the required development needed to build custom data models and reports.
Unclear or unidentified requirements are another beast altogether. Fuzzy requirements and undefined expectations will double (if not triple) your timeline.
“Properly defining business requirements is among the most important contributors to successful IT programs and projects“, Michael Krigsman of IT Project Failures
Read MoreHere is an example where I wanted to specify how the records are read and formed when data is loaded in BW. That is, I wanted to ensure certain groups of data are logically packaged in one data package (DTP) and not sprinkled across two different data packages.
Read MoreYou will run into this rare, but frustrating bug in SAP’s Netweaver BW modeling interface when editing infocubes: unable to uncheck or unselect the Line Item Dimension.
Given my luck, I run into this issue every other time an infocube needs to be created, remodeled, or rebalanced.
Read MoreLoading in BW 7.x is greatly simplified with the introduction of the Data Transfer Package (DTP). Initializations and deltas between two (or more) data targets are handled automatically by the system.
Where you will run into trouble with the 7.x DTP objects is during initial or reloads of a data target.
Read MoreCaution: Please use common sense. I do not advocate going into areas of SAP that are sensitive in nature. The purpose of this article is to allow the studious worker to complete his/her task in environments where security is a mess.
Task: I need to document a process that correct listens to an event. (Event triggering should be an all-too-familiar topic for those who have worked with BW 3.0B.)
Problem: To raise an event, I had access to transaction SM64 in the Development environment, but not in the Quality Assurance environment.
Read More
Here is a familiar phrase for anyone who has worked in SAP BW or BI production support environment:
‘Short dump in the Warehouse’
Checking transaction ST22, you should see another familiar screen telling you about a deadlock issue.
Personally, I find it hilarious that the system message tells you to try again and hope the outcome will be different.