Release

Use

You can apply a multiple-level release procedure to the main functions involved in processing master data and flow data. The release procedure is based on the multiple control principle, and can be set up differently for individual areas. For example, you can require one employee to release loan master data for a mortgage loan but two employees to release disbursements. A release status is used to determine the release levels.

The release procedure is not provided for loans from the product category Installment Loans (360).

Prerequisites

Base

You need to have set up the SAP Business Workflow in the Customizing settings for Basis .

Loans Management

You need to have completed the following IMG activities in the Customizing settings for Loans Management :

You must activate the relevant release objects under Transaction ManagementReleaseMaintain Active Indicators. You must also define how many employees will be required to release each object under Define Release Status Parameters. You need to make further settings under Maintain Workflow Settings .

In addition to your settings under Release , you can also make the following settings for loans that are based on the product category Consumer Loans (340), under Define Product Types :

You can determine that the release process should only be started when the conditions for the underlying product have been breached.

You can determine which product version the system should use to check the loan.

The current product version

The product version that was valid when the loan was created

SAP Banking

Make the settings for the release object SAP Business Partner in the Customizing settings for SAP Banking under SAP Business Partner for Financial ServicesSettings for Financial ServicesToolsRelease

Scope of Functions

If the release object has been set to active, you can use the release workflow to process and release the following:

Loan master data

SAP Business Partner

Real Estate Business Partner

Objects

Decision-making

New business tables

Condition table assignment

Condition table

Product

Disbursement

Unscheduled repayment

Charges

Single postings

Payoff

Notice

Waivers/write-offs

Borrower change

Capital transfer

Deferral

Capitalization of overdue items

Interest on arrears

Capital reposting

Reversal

Payment postprocessing

Dependencies

One feature of the release procedure is that all the master data for a loan has to be released before further activities can be carried out (such as postings, or generating planned records). The loan master data includes the data for the loan itself, for the collateral object and for all the partners assigned to the loan. Flow data always relates to accounting activities. These include disbursements, individual business operations, payment postprocessing, capital reposting and reversal.

Before you release the data, you can make changes. If you make changes to the data after it has been released, you have to release it again. The release status changes back to the initial status.

Moreover, you cannot enter a new flow record for a loan if an existing flow for the same posting application or a different posting application still has to be released. For example, the system will not let you activate a processing charge if a disbursement created previously has not yet been released.

Starting the release procedure

Each time you create a new release object or change an existing one, the system generates a new work item , thus starting the release procedure. The work item appears automatically in the business workplace inbox of the person who is authorized to process the object and release it.

For decision-making, the release procedure must be triggered manually. This is a special case. For more information, see Decision-Making .

Release using the Business Workplace

From the SAP Easy Access screen, choose OfficeWorkplaceInbox .The system displays the objects to be released in a table using the SAP List Viewer

Select a work item and choose Execute. The system displays the release history for the object, where you can see the changes to the release status. The release history is split into several parts:

You see the Date and Time at which the object was created or changed.

The person who created or changed the object is identified in the First name , Last name and User fields. You also see details for the Telephone (area code and number), the Extension , and the Department .

The release procedure assigns a release status to the objects to be released. The release status tells you the current status of the data record. The first digit represents the number of employees required in the release procedure. The second digit is the number of releases still to be made.

A data record is subject to the dual control principle involving two employees. In other words, two users have to release the record. When you create a record, the system assigns the initial status 22. After the first release, the release status is 21, and after the second release 20. The status 20 indicates that the record has been fully released.

The Release indicator tells you whether the object has been created for the first time ('I') or has already been changed ('U'). This field remains empty when you release the object.

The release principle applied (in other words, the number of employees required to release the object) is displayed in the Description field, which corresponds to the numeric Release status .

You can also display the Release history when you create or change a release object. From here, however, you cannot process or release the object.

To change data for an existing object, choose Change release object. Once you have saved your changes, the system returns automatically to your business workplace inbox. As a result of the change, the system replaces the existing work item with a new one. You can then process and release the object by choosing Execute.

To display the object data, choose Display release object. The system automatically opens a new session, which allows you to compare the displayed object data with the change documents. To view the change documents, choose Display change documents for object. The Display change documents for object function is only supported for loan master data, business partners and collateral objects.

If you do not want to accept this task you can now choose the new Replace button, displayed in addition to the existing Cancel button. This not only cancels the processing but also replaces the task so that it appears in the inbox of all the administrators with the appropriate authorization enabling them to process it

To release an object, choose Release. Once an object has been fully released, in other words, the second digit of the release status is 0, the effect varies according to the type of object:

Loan Master Data, Objects, Business Partner, New Business Table, Payoff, Waivers / Write Offs, Borrower Change, Capital Transfer

The data for these objects is released.

When processing payoffs, waivers/write offs, borrower changes and capital transfers you can carry out subsequent processing (for example, activate or post ) directly after releasing the records. You can control this in a separate screen for postprocessing.

Disbursement, Charges, Single Postings

Upon release of the records, the system generates planned records, which are written to the database. These flows can now be posted.

Capital Reposting, Payment Postprocessing, Reversals

When you execute the release, the system posts the data (actual records) immediately.

You can also reject a release object. If you choose Reject release the system returns the release object to the person who initiated the release workflow (it appears as a work item in the person's business workplace inbox). You should specify the rejection reason in an attachment.

If a release object that you entered or initiated is rejected a Release rejected item appears in your Business Workplace inbox. After you have executed this work item you can use the Control function to start the release process again. You need to enter an attachment - in the same way as for a rejection - so that a new work item can be created for release.

For more information, see BC- BasisSAP Business Workflow (BC-BMT-WFM).