Ansicht
Dokumentation

Treasury Business partner: Release 2F ( RELNTRTM02F_GP_FREIGABE )

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Short text

Treasury Business partner: Release 2F

Description

In the release procedure for business partners, a partner has to be released after being changed (or after being newly created), before business can be transacted with this partner.

The business partner can either have the status 'released' or 'still to be released'. If the release procedure is not used, a partner always has the 'released' status.

The release relates to all roles of a business partner, but by using customizing you can determine the role categories and role types in which the business partner has to be noted as 'still to be released' after changes (see release parameters).

You have to activate the release procedure specifically in customizing. Otherwise, no note is made to the effect that a partner still has to be
released.

Release status

A business partner who still has to be released is assigned a release status via the release parameter controls. The release status tells you the current status of the release of a particular partner. The two digits of the release status have the following significance:

The first digit represents the number of users involved in the release of the partner.

The second digit indicates the number of releases still to be given.

Example: dual control principle:

A partner is to be released using the dual control principle, i.e. two release levels and two different users are necessary to release the partner, while one user may be identical with the user who entered or changed the business partner.

The initial status which is to be allocated to the partner when first created in customizing should be '22'. In other words, two releases are to take place and two releases still have to be given.

After the first release, the business partner is given the release status '21' since one release is still necessary. After the second release has been given, the status is set to '20'. This means that the partner has been released and no further release is necessary.

Using the release history of a business partner, you are able to retracewho gave the release and when.

You can change the description of the release status in customizing.

Release parameters

In customizing, you can use the release parameters role category and role type to specify the role categories and, where applicable, the role types for which the release procedure is necessary (here you have to activate the release procedure and the parameter settings). With the same paramters, you can also specify the initial status when a business partner is created or changed.

The initial status defines the release procedure, e.g. the dual control principle.

If the business partner is always to be released, regardless of role category, then the parameter, role category, should be set to the initial value. This applies analogously to the role type.

Release function

To release a business partner who still requires to be released, you use the central function 'business partner release'.

This function displays all business partners to be released who fulfil the selection criteria. You can branch from the overview list display to call up one single business partner. You can also change a business partner (use the post-process function).

When you release the business partner, the release status is modified. When the last release level has been reached, the business partner is market as being released.

If the release is rejected, the release status contains the value '99'. The partner continues to exist on the release list until post- processing takes place (when the partner is given a new release status as a result of the change) and until the partner has been through all release levels.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

Recommendation:

Since the status 'to be released' affects all roles in which the partner is created, a system user who gives releases should have authorization to display all role categories. Otherwise, when a partner is displayed, the user only sees the roles and the role data for which he/she has authorization.

Customizing settings for release parameters should not be changed and the release should not be activated/deactivated until after all partners have been released. Otherwise, when a partner is changed, there is a danger that different initial statuses or no statuses can be set. For example, a partner to be released would be saved as already released after a change if the activation had been removed in the meantime.

TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5442 Date: 20240523 Time: 061735     sap01-206 ( 106 ms )