consolut - /ISDFPS/FOLLOW_ON_PURDOCS - Follow-On Documents for Purchase Requisition

/ISDFPS/FOLLOW_ON_PURDOCS - Follow-On Documents for Purchase Requisition

General Material Data SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.

Purpose

This report allows you to display the document flow, from the purchase requisition, through the order,to the delivery. You can restrict the selection results using the selection screen or dynamic selection.All the preceding and subsequent documents are included in the selection. The documents are displayed in chronological order.

Integration

The display comprises the following documents with their items:

Purchase requisition

Purchase requisition with loan indicator (loan requisition)

Purchase requisition with obligation for return delivery (return delivery requisition)

Forwarded purchase requisition

Service purchase requisition

Order

Delivery

Service entry sheet

Prerequisites

To use this report, you must be authorized to display purchase requisitions, orders, and deliveries.If, for example, you are authorized to display only purchase requisitions, all purchase requisitionsare displayed, but no information or details about the orders or deliveries is displayed. If, in addition to this, you are only authorized to display orders, the details about the delivery are not provided.

Features

Selection screen fields and dynamic selection fields are provided as selection criteria for the purchaserequisition. Here you can fill as many selection fields as required. In addition, you can call up thereport from the documents: purchase order, delivery, or service entry sheet. If one of these fieldsis filled, it has priority over the purchase requisition in the selection process. The selectioncriteria can include only one document type. You cannot combine the selection criteria of the purchase requisition with additional documents.

In addition to the selection criteria, you can restrict the hit list using the "Also Display CompletedDocs" and "Also Display Deleted Documents" options. This function can be used for both purchase requisitions and orders. These fields are already selected by default.

When you double-click a document in the hierarchy, a table containing the relevant detailed fields appearsin the bottom of the screen. The display can be compiled from the named tables as often as required (see standard variants). When you double-click a row in this table, you jump to the relevant standard transaction.

These functions are also possible using the "Display Details" and "Display Document" pushbuttons.

When exporting to an Excel list, note the following:

Under Spreadsheet -> , choose Select Spreadsheet -> All Available Formats: Excel (in previous XXL format).

If the list is very wide, you can change the view by choosing Change Layout-> and selecting "Microsoft Excel" as the preferred view on the View tab page with a selected template.

In the Excel program, the "Trust Access to Visual Basic Project" field must be selected by choosing: "Tools -> Macro -> Security -> Trusted Sources".

Selection

Tables EBAN and EBKN are used to procure data for the purchase requisition, tables EKKO, EKPO, EKET, EKBE, EKPV and EKKN for the order, and LIKP and LIPS for the delivery.

Standard Variants

The amount of details of the purchase requisition, order, and delivery is restricted due to the quantityof data. For this purpose, a defined number of fields from the named tables are selected for the fieldcatalog. You can control the addition/removal of fields for the detailed display in the document overview(ALV grid) using BAdI /ISDFPS/MM_FOLLOW_ON_PURDOCS in enhancement spot /ISDFPS/MM_FOLLOW_ON_DOCS. The details in the document overview cannot be enhanced.

Output

The tree structure is divided into: Plant->Purchase Requisition->PReq Item->Order->PO Item->Delivery.

For documents such as purchase requisition with loan indicator (loan requisition), purchase order withobligation for return delivery (return delivery requisition), and forwarded purchase requisition, thedisplay differs from this pattern since these documents contain follow-on documents, which in turn create follow-on documents (for example, return delivery requisitions).

The individual documents are each identified with different icons and a quick info text.

Activities

Example

If a purchase requisition with loan indicator 10...1 is created, when it is converted to order 45...1, a return delivery request 10...2 is automatically created. .

In the tree structure, the follow-on documents would be displayed as follows:

Loan Requisition 10...1

,,,,Item 10

|->Order 45...1

| Item 10

| |

| Delivery 80...1 / 10

|->Return Delivery Requisition for Loan 10...2

|,,

Item 10

|->Order 45...2

Item 10