Object types
For sales and profit planning with workflow support, only the following
object type is relevant:Object type BUS1166 (COPAPlanningPackage)
You can use the object type BUS1166 to process planning packages in CO-PA Planning. The key fields for the object type are:
You define a planning level and the associated planning packages when
setting up planning content.The object type BUS1166 contains the following methods:
Tasks
The following tasks delivered by SAP are available as modules and can be used in a workflow scenario without having to be changed beforehand (for more information, see
Tasks and Task Groups).One task is used to enter planning data whereas the other task is used to display it.
Task COPA_PLAN_01
Definition
Task: 20000612
Short name: COPA_PLAN_01
Description: Entering CO-PA planning data
Structure
Object type: BUS1166 (COPAPlanningPackage)
Referenced object method: ChangePlanData
Attributes: Object method with dialog, confirm end of processing
Agent assignment: no restriction on possible agents
This is where you specify which agents can be selected as the responsible agent. The responsible agent for this task is determined by the role. Any agent can be the responsible agent. For this reason, it is necessary to classify the task in Customizing as a general task. For more information, see:
Set Up and Customizing.Task COPA_PLAN_02
Definition
Task: 20000664
Short name: COPA_PLAN_02
Description: Displaying CO-PA planning data
Structure
Object type: BUS1166 (COPAPlanningPackage)
Referenced object method: DisplayPlanData
Attributes: Object method with dialog, confirm end of processing
Agent assignment: no restriction on possible agents
This is where you specify which agents can be selected as the responsible agent. The responsible agent for this task is determined by the role. Any agent can be the responsible agent. For this reason, it is necessary to classify the task in Customizing as a general task. For more information, see:
Set Up and Customizing.Workflow
Each workflow can contain one or more tasks. The business flow for this task is implemented as the workflow definition within a workflow.
Workflow COPA_PLAN_M1
You can use this workflow to influence sales and profit planning when several planning packages are to be processed.
Definition
Workflow: 20000377
Short name: COPA_PLAN_M1
Description: Performing CO-PA Planning
Workflow Container
The import parameters of a workflow are placed in the workflow container.
The following two sources of information are essential for the workflow COPA_PLAN_M1 to be processed and therefore must b available:
You must enter both sets of information when starting the workflow.
Workflow Steps
The workflow COPA_PLAN_M1 consists of a single step, the task Enter CO-PA Planning Data. However, the distinguishing feature of this step is that its dynamic processing occurs in parallel (tab page Miscellaneous in the step definition): the system creates a work item with a planning package for every entry in the multiple-lined container element COPAPlanningPackage.
Agent for the Workflow Step Enter CO-PA Planning Data
You can enter in a workflow step the planning data for a planning package. There are many different ways of determining the responsible agent for this workflow step. Role COPA_PLAN_R1 is used to find the agent in the delivered workflow COPA_PLAN_M1 (see below).
Starting the Workflow
You do not use an event to start the workflow COPA_PLAN_M1. Instead, you start it directly by choosing Office ® Start Workflow in the menu.
When starting the workflow, you need to enter one or several planning packages and a parameter set.
Role COPA_PLAN_R1
Definition
This is a role used to determine the agent for a planning package. It is used in the delivered workflow template COPA_PLAN_M1.
Role: 20000069
Short name: COPA_PLAN_01
Description: Person responsible for the CO-PA planning package
Role Parameters
You can copy all key fields for the object type BUS1166 as role parameters: operating concern, type of profitability analysis, planning level and planning package. Your assignment of an agent is then dependent on these fields. For more information, see:
Set Up and Customizing.