Show TOC

Function documentationStatus Management in Grants Management for Grantor

 

The current status of a program (or the combination of all statuses) determines whether the program can be edited and which business transactions can be executed for this program. The status of a program is defined under Status. Statuses can be set by the system or by a user.

Features

A program is not a static object. It has its own life cycle that begins with its creation and ends with its closure or cancellation. During this time, the program is changed by different business transactions.

Each program can have the following system statuses, one of which is always set.

  • Created

    This status is set automatically when a program is created.

  • Released

    This status can either be set manually or can be set by an action. You can only release a subordinate program if the higher-level program has already been released.

  • Closed

    This status can either be set manually or can be set by an action. It can only be set if all subordinate programs already have the status Closed. You cannot make changes to a program with status Closed. If you want to make changes, the program needs to be reset to Released. This can only be done if the higher-level program does not have the status Closed so you reset starting at this level.

  • Locked

    This status can be set or reset manually or by an action and can be set independently from the status of the higher-level program or the subordinate programs. Once a program has the status Locked, it cannot be changed unless the status is reset. No follow-up processes are permitted if a program has this status.

  • Object Moving Locked

    This status is set by the system once the transfer to PSM (funded program) has been triggered. A program with this status cannot be moved within the hierarchy. To move the program, you need to reset the status manually. In this event, a warning message is issued to let you know that this may lead to problems in PSM with budgeting. When the status is reset, the program can be moved. After saving, the system sets the status again.

  • Integration Status

    This status shows the status of program replication to ERP (in process, successful or failed).

Activities

You can define user statuses if you want to control when particular business transactions are to be allowed. User statuses are enhancements to the existing system statuses.

The following table of Business Transactions for Grantor is an interaction matrix between system status and business transaction.

(P: Permitted, B: Banned, -: No Influence)

System Statuses

I1001

I1004

I1008

I1121

I1320

Business Transactions

CRTE Created

REL Released

FSHD Finished

LCK Locked

SCLC Moving Locked

CCLS

Close

-

P

-

B

-

CCLU

Undo “Closed Status”

-

-

P

B

-

CEDL

Delete

P

P

B

B

-

CGCH

Change Attributes

P

P

B

B

-

CLKS

Block

P

P

B

-

-

CLKU

Unblock

-

-

-

P

-

COMV

Move objects

P

P

-

-

B

CREL

Release

P

P

B

B

-

CSTC

Change structure

P

P

B

B

-

CSTE

Expand structure

P

P

B

B

-

CSTU

Unlock structural change

-

-

-

B

P

CTR3

Transfer to ERP

-

P

B

-

-

GPM1

Create application

-

P

B

B

-

GPM2

Create agreement

-

P

B

B

-

GPM4

Create claim

-

P

B

B

-

GPM5

Create change request

-

P

B

B

-

To define user statuses, in Customizing for Customer Relationship Management choose Start of the navigation path Industry-Specific Solutions Next navigation step Public Sector Next navigation step Grantor Management Next navigation step Grantor Program Management Next navigation step General Settings Next navigation step Define Status Profile for User Status End of the navigation path.