Workflow for Pricing Condition Records

[joelramirez]

Hi all,

The requirement is to configure workflow for Pricing master data maintenance.

For example, user 1 enters condition records using VK11 and saves, upon saving then a workflow task for approval needs to be created. Price is not active until someone approves it.

Can this be achieved using Workflow?

If so, can you please send information.

Thanks,

[Former Member]

Hello Colleague;

Here some suggest for your process:

Thank you for your response. Please see below some further information

that should help you.

IMG

>SD

>Basic Function

>Pricing

>Define processing status

In this step you can define the processing status for condition records

and assign these a pre-assigned release status, using the release

procedure. The processing status can be assigned condition records in

condition maintenance. In pricing, only those conditions are used, that

have the release status 'released'.

1. Release Status (KOMG-KFRST)

The release status controls in which scenarios the condition records

found. If the status is set at 'B', for example, then the

corresponding records are taken into account during a pricing

simulation, but are not used in current documents.

The release status can only be maintained directly for agreements

sales deals). For condition records, this is done via the

processing status.

2. Processing status for conditions (KOMG-KBSTAT)

The processing status can be freely assigned for condition records

There is a maintenance view in Customizing, which contains the

prmitted processing status. Here a release status is assigned to

processing status. This determines under what conditions a condition

is retrieved(Callmode).

For specific business requirement, you need to use Business Transaction

Event (BTE).

Please check documentation:

Help.sap.com > SAP Library >Logistics->Sales & Distribution->Pricing

& Conditions->Pricing & Conditions->Condition Records->Condition

Maintenance->Release Procedures

(There are detailed documentation about it)

There is one sentence:"Business Transaction Event 00503303 Maintain

Conditions: Transfers" In transaction SE37, you can display

SAMPLE_INTERFACE_00503303. There is an additional information button

which will give you the following:

FU SAMPLE_INTERFACE_00503303

____________________________________________________

Short text

Event: Maintain Conditions: Transitions

Functionality

This function module is an interface description only and does not

contain any instructions. It is intended for developers of those

additional components that provide their own function module at Eve

00503303 (Maintain conditions: Transitions).

Function module SAMPLE_INTERFACE_00503303 must not be changed.

If you want to create your own function module that is to be access

the callup point mentioned above, proceed as follows:

1. Copy the function module to your own name range.

2. Do not change any transfer parameters !!

3. Write your own coding in the copied function module.

4. Save and activate your function module.

5. Carry out the necessary settings in Customizing. Business

Transaction Events

This function module (user-exit) allows you to decide which field

contents are permitted in condition maintenance when creating or

changing condition records.

The following import parameters are available:

o KOMG_OLD old status of KOMG structure

o KOMG_NEW new status of KOMG structure

o VAKE_OLD old status of VAKE structure

o VAKE_NEW new status of VAKE structure

You can set the export parameter TRANSITION_FORBIDDEN to either

SPACE or 'X':

o If you set it to SPACE, you can continue with condition maintena

o However, if it is set to 'X', then you will receive an error

message.

Example

To display your workflow, you can use the processing status for the

condition records, for example. This functionality is available from

Release 4.6A for newly created condition tables, as long as the sett

was made accordingly in the condition table.

If your workflow does not allow, for example, the transition from

processing status from 'A' to 'C' (as only 'A' to 'B' or 'B' to 'C'

permitted), you can compare the two fields

o KOMG_OLD-KBSTAT

o KOMG_NEW-KBSTAT

in this user exit.

Notes

SAP cannot ensure that all fields in the KOMG and VAKE structures ha

been completed with the appropriate values. To implement this user e

we urgently recommend that you check the current content of the fiel

that you are using.

Parameter

KOMG_OLD

KOMG_NEW

VAKE_OLD

VAKE_NEW

TRANSITION_FORBIDDEN

Exceptions

unction group

V13A

I hope that documentation can help you a lot.

Regards

Ruy Castro