Monitoring Logistical Data and Procurement Processes

ProMan is an application that is integrated with materials management, purchasing, production, and shipping. The following list outlines ProMan characteristics:

• Focus on components or activities, or on the respective account assignment objects

• Views for components, activities and elements, quantities, dates, orders and documents, stock and deliveries

• Hierarchical display of project structure for navigation

• ALV-based overviews

• Executable functions

  • Purchase requisitions, create purchase order

  • Create reservation

  • Goods issue

  • Stock transfer posting

  • Delivery from project

ProMan consists of a selection screen and a main screen. The main screen contains a hierarchical navigation area and different overviews (for example, for components, quantities, dates, activities, orders, and documents). The documents and orders that are displayed in this way in ProMan include: purchase requisition, purchase order item, reservation, and planned order.

For components or documents to be displayed in ProMan, they must be assigned or account assigned to an object in a project (for example, WBS element or network activity). Caution: Requirements that are independent of a project such as dependent requirements that refer to anonymous plant stock cannot be evaluated in ProMan.

In the navigation area, in addition to simply navigating, you can also assign components from one activity to the next.

The orders/documents view provides you with information about orders (for example, planned orders, production orders) and documents (for example, purchase requisitions, purchase orders, requests for quotation, material documents) that are assigned to the selected components (or external services). The individual documents and orders can be displayed directly from ProMan by simply double-clicking the individual document or order number.

You can also create new documents from all of the overviews. The object that you have selected and the view that you are currently using both determine which documents you can actually create.

The Quantities view supplies you with detailed information about the quantities and stock levels of components. In detail, you see the following information:

• Requirements quantity of the reservation

• Quantity in the planned order and in the production order

• Quantity of the purchase requisition and the purchase order

• Stock

• Quantity withdrawn

• Quantity in the material document

The date overview gives you detailed information about the dates of components (and external services). For example, you are provided with the following information:

• Requirements date

• Delivery date of the purchase requisition and purchase order

• Basic start and finish date of planned orders and production orders

• Final delivery date of production orders

The Progress Tracking view was introduced to ProMan with SAP ERP 6.0 Enhancement Package 3. It displays data that was planned in Progress Tracking for components. Currently, you cannot maintain this data. The Progress Tracking view does not display any Progress Tracking data for WBS elements or network activities.

The following list outlines the additional functions offered by ProMan:

• Integration

  • Order progress, order report

  • Requirements planning run, stock/requirements list

• Navigation for all displayed objects

  • Material master, planned order, production order

  • Network, purchase requisition, purchase order

  • Request for quotation, quotation, vendor master

• Highlighting exceptions

You can use the ProMan menu to select other functions. In ProMan, choose Edit→Functions to carry out the following functions:

• Order progress

• Order report

• Single-item, single-level (requirements planning run, MRP)

• Single-item, multilevel (requirements planning run, MRP)

• Project planning (requirements planning run, MRP)

• Stock/requirements List

You can use the BAdI BADI_CNMM_CUST_ENH_SCR to develop your own view (that is, a tab page) in which you can display customer-defined fields. The BAdI was delivered with SAP ERP 6.0 Enhancement Package 3.

Defining an exception profile is also optional. It is not assigned directly when ProMan is called up, instead it is selected via the ProMan profile. The exception profile specifies rules that are evaluated; the result of this evaluation determines whether the traffic lights are set to red or yellow. The traffic lights are displayed on the individual overviews. The rules for exceptions are therefore adjusted to fit the individual views, such as exceptions for documents, for example.