Preparations

Before you create a customer-specific action, you should check whether a standard action is contained in the delivered Customizing settings that fulfills your requirements.

Identify the business process in which the action should be used.

The business process is represented in Customizing by the warranty claim type .An action control is assigned to each warranty claim type there.The action control contains an action matrix in which is defined which actions are allowed at which processing status of the claim and how the processing status is changed by the action.

Define the framework for the action.

Which processing status does the warranty claim have before the desired action?Which processing status does it have afterwards?

For copying actions: which categories of the versions are involved?(versions form claimant, versions to reimburser etc.)

Define in which mode the action is to be executed (display, change, create, automatic processing).

Define the functionality of the action (copy, check, pricing etc.).

If you require more than one functionality within the action, you can create an interlinking action (see below).

Check whether you can use one of the existing standard actions.

To do this, choose the action in Customizing by using the description or search for the action in the action matrix of the action control by using the start and target processing status and then compare the description.

Does the action module deliver the desired functionality?

Are the general Customizing settings for the action correct?

Is the action matrix of the action control in which the action is contained correct?

Execution

If you do not want to use a standard action either because Customizing has not been defined as you require it or because the action module does not have the desired functionality, proceed as follows:

Create a new warranty claim type (Customizing for Warranty Claim Processing under Define Warranty Claim Types ).Copy an existing warranty claim type to the customer namespace.

Make further settings in Customizing if you require them for programming your own action modules.

Only for copy actions: Customizing for Copying Control (Customizing for Warranty Claim Processing under Control Data → Copying Control )

Is a copy procedure required?

Has the copy procedure been defined?

Has the copy procedure been assigned to the claim type, source category and target category?

If you do not enter a copy procedure, all the field contents are copied. with the exception of technical fields such as the GUID.

Only for check actions: Customizing for VSR Checks (Customizing for Warranty Claim Processing under Control Data → VSR Checks )

Only for pricing actions: Customizing for Pricing (Customizing for Warranty Claim Processing under Pricing )

If required, create your own action function module.To do this, copy action module WTY04_EXAMPLE_FOR_ACTION to the customer namespace.

You can find out more bout the export parameters in the long text for the appropriate parameters.

Program the desired functionality in this action module.

In Customizing, create a new action with action code in the customer namespace with descriptive text (Customizing for Warranty Claim Processing under Control Data   → Process Control   → Define Actions ).

Choose action type F or T (elementary action) or A or V (interlinking action).

Can you display the action?

Should the action be logged in the action log?

Only for interlinking actions: define which actions should be contained in the interlinking action and in which sequence they are to be processed.

Both elementary and interlinking actions can be used in an interlinking action.

Leave space between the items when you enter the sequence so that you can add further actions later, e.g.: enter 5, 10, 15 and not 3, 4, 5.

Only for elementary actions: assign an action module to the action.

Use the action module of a suitable standard action or your own action module (see above).

Assign a unique function code to the action code (Customizing for Warranty Claim Processing under Control Data   → Process Control   → Assign Function Codes to Action Codes ).

Each action that you start via the action box, triggers a function code.The action code and the function code are the same for these actions.Nevertheless, you have to enter the appropriate assignment.

For function codes that are triggered via pushbuttons and menu path commands, the function code is defined in the Screen Painter or the Menu Painter for existing screens.For new screens, you have to enter a function code there.You must assign this function code to the action code.

Define the start and target processing status for the action (Customizing for Warranty Claim Processing under Control Data   → Process Control   → Define Processing Statuses ).

Which processing status do the warranty claims to be processed have?

Which processing status should the processed warranty claims have?

Use the existing processing statuses or create new ones in the customer namespace.

For interlinking actions, ensure that the processing statuses of the actions contained build on each other.Example: interlinking action V1 contains actions A1, A2 and A3 in this sequence.For A1, the processing status changes from B1 (start processing status) to B2, for A2 from B2 to B3, for A3 from B3 to B4.B1 must therefore be entered as start processing status for V1 and B4 as target processing status.

When executing an interlinking action, the target processing status of the last successfully performed action is always set as target processing status.If, in our example, action A3 is not successful when V1 is executed, the target processing status is set to B3 and not B4.

Create a new action control an (Customizing for Warranty Claim Processing under Control Data → Process Control → Define Action Controls ).Copy an existing action control to the customer namespace.

Copy this action with start and target processing status to the action matrix of this action control.

Should automatic processing be possible for the chosen start processing status?

If you want to allow a grouped area of connected actions for a specific start processing status, you can work with placeholders.

Assign user authorizations for the action (authorization object Action ).

All users should have at least the authorization for the delivered actions with action code T*, since these are mostly technical actions that are required for the display and processing of warranty claims.

Assign your action control to the warranty claim type (Customizing for Warranty Claim Processing under Define Warranty Claim Types ).