07.02.2013 Views

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Planning profiles are used to only present those planning objects from the<br />

possibly very large quantity of planning objects, which are relevant <strong>for</strong> a specific<br />

user or <strong>for</strong> a certain planning task.<br />

planning sequence<br />

List of user-defined planning functions or parameter groups, which are<br />

processed sequentially in the order determined by the list.<br />

Planning sequences are used to execute recurrent complex planning tasks as<br />

efficiently as possible. These can be defined both locally within a planning area<br />

and globally across several planning areas.<br />

Port<br />

A defined point of interface into and out of a component.<br />

Portal Connection Framework<br />

Part of <strong>SAP</strong>'s Enterprise Portal, provides a set of APIs which extend the standard<br />

JCA interfaces and are used to build Portal-compliant connectors. The <strong>BI</strong> Java<br />

Connectors are compliant with the Portal Connection Framework.<br />

primary source system<br />

Source system from which recently created or changed objects need to be<br />

transported into another target source system.<br />

A primary source system is, within the framework of a system landscape<br />

consisting of OLTP and BW systems, an OLTP development system. The<br />

respective target source system is the OLTP system that is connected with the <strong>BI</strong><br />

target system.<br />

In order to be able to transport objects that are specific to the source system (<strong>for</strong><br />

example, transfer structures), the logical system names must be specified <strong>for</strong> the<br />

source systems be<strong>for</strong>e and after the transport in a mapping table in the <strong>BI</strong> target<br />

system.<br />

process<br />

Process with a definite beginning and end within or outside of an <strong>SAP</strong> system.<br />

process chain<br />

Sequence of processes that are scheduled in the background to wait <strong>for</strong> a<br />

particular event. Some of these processes trigger an additional event, which in<br />

turn can start other processes.<br />

process instance<br />

Value of the process:<br />

Appendix A. Glossary <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> 299

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!