Post Processing Framework in EWM

Author: Sharmila Parmar

Copyright © 2012 Tata Consultancy Services Limited

1
 Post Processing Framework (PPF) in EWM

• The Post Processing Framework (PPF) provides SAP applications with a

uniform interface for the condition-dependent generation of actions (for
example, printing delivery notes, faxing, creating subsequent documents,
triggering workflow processes, etc.)

• The Post Processing Framework is part of the SAP Web Application Server
and can be used by different applications. It is the successor to Message
Control

• The Post Processing Framework (PPF) is a Basis technology used in EWM

delivery processing for scheduling and processing actions with reference to
delivery documents. Output/message control for EWM delivery processing
uses the PPF.

2
 Determination & Triggering of PPF Actions

Scenario Considered : Use PPF action to create Inbound Delivery

document from Inbound Delivery Notification

Step1: Create Inbound Delivery in ECC

Tcode: VL33N
Eg: 0180006407

Step2: Inbound Delivery Notification will be created in EWM automatically.

Tcode: /SCWM/IDN
Eg: 0180006407

Step3: On creation of Inbound Delivery Notification, PPF is triggered, which in

turn creates Inbound Delivery through Action /SCDL/IDR_TRANSFER
Tcode: /SCWM/PRDI
Eg: 1700000405

3
 Determination & Triggering of PPF Actions

Action /SCDL/IDR_TRANSFER is determined

4
 Determination & Triggering of PPF Actions

Check the processing log. Inbound Delivery created through method call of Action

5
 How PPF action got determine
• When Inbound Delivery Notification is created, in background, PPF is
triggered and Action Profile is read, based upon Document type and
Document category of the document.

• The action profile contains action definitions and the settings for all the action
definitions in the profile.

• Each Action is analyzed one by one and if condition is met, action is consider
and added in the PPF tab.

• Depending upon the processing type of actions, further processing takes

place.
• In our example, processing type is method call, which creates the Inbound
Delivery.

6
 PPF Configuration Steps
In Customizing for Delivery Processing, you execute the following activities:

• Create an action profile

• Under the action profile, define actions, for example sending of messages,
printing delivery note or posting goods receipt.

• For every action, you define processing type, action determination and
processing time-spots.

• Assign the action profile to the document type and item type.

7
 Action Profile
An action profile contains action definitions and the settings for all the action
definitions in the profile.

8
 Action Profile

Eg: /SCDL/IDR

9
 Actions linked to Action Profile

Eg: Action /SCDL/IDR_TRANSFER

10
 Processing Type for Action

Actions always occur using the execution of a processing.

Eg: Processing Type for Action /SCDL/IDR_TRANSFER

Select Action and Click Processing Type

11
 Processing Type for Action (Contd)

Eg: Processing Type for Action /SCDL/IDR_TRANSFER is Method Call

12
 Linkage of Action Profile
Linkage of Action Profile to Document Type and Document Category in
Customizing. In example: Action Profile is linked to /SCDL/IDR

13
 Connection of PPF to the Application 

If you want your application to use the PPF, you must perform a number of
programming steps. The connection is object-oriented using the classes.

Necessary Classes

A persistent class (in the sense of Object Services) that represents the application
object (Eg: /SCDL/CL_DLV_PPF)

A context class that encapsulates all information for the PPF

(/SCDL/CL_DLV_CONTEXT_PPF)

A processing class provided Smart Forms are used

(/SCWM/CL_PROCESSING_SMARTFORM)

A BADI implementation provided the processing method call is used

Workflow template provided a workflow is to be triggered

14
 Application Class & Context Class

The PPF expects a persistent class so it can handle different types of application
objects.

The application object implements the interface IF_LOCK_PPF and thus both
methods for locking and unlocking the application object.
These two methods are important so that an action does not operate on documents
that are already locked. If the interface is not implemented, this can result in actions
being executed twice under certain circumstances. Generally, the interface must be
implemented.
Eg: /SCDL/CL_DLV_PPF

The context class encapsulates all the application data necessary for the PPF.
The context class redefines the method GET_VALUE_OF_ATTRIBUTE of class
CL_CONTEXT_PPF
Eg: (/SCDL/CL_DLV_CONTEXT_PPF)

15
Application & Context Class linked to Action
Profile

16
 Smartform processing class linked to
Processing Type
In the Smart Forms processing options, enter the name of the Smart Form used
and a processing class with a processing method,

17
 Interaction Between Application & PPF at Runtime

Necessary Steps for starting the PPF

Data declarations 
Reference to application/proxy object
appl_object TYPE REF TO /SCDL/CL_DLV_PPF

Reference to context object

context TYPE REF TO /SCDL/CL_DLV_CONTEXT_PPF.

Reference to PPF manager (interface to PPF services)

manager TYPE REF TO cl_manager_ppf.

18
 Interaction Between Application & PPF at Runtime

Get an instance of class CL_MANAGER_PPF.

This class displays the interface for PPF. All service methods are called by it.
manager = cl_manager_ppf=>get_instance( ).

Generate the application object and set the key fields so that the application object can
be found
appl_object ?= /SCDL/CL_DLV_PPF=>agent->if_os_factory~create_persistent_by_key( i_key
= id ).

Generate an object of the action profile Context class

CREATE OBJECT context.
The action profile object that encapsulates all information for the PPF. The name of the
application and the action profile that were defined in Customizing are transferred. The
reference to the application is transferred

Set context attribute

context->applctn = ‘Name of Application’ Eg: /SCDL/DELIVERY
Context->name = ‘Name of Action Profile’ Eg: /SCDL/IDR

19
 Interaction Between Application & PPF at Runtime

Start PPF

CALL METHOD manager->determine

EXPORTING io_context = context
IMPORTING ep_protocol = determination_protocol.

COMMIT WORK

20
Thank You