SAP ABAP IMG Activity BP_CLEANSE_RELEASE (Assign Release Procedure to Release Object)
Hierarchy
☛ SAP_BS_FND (Software Component) SAP Business Suite Foundation
   ⤷ FS-BP (Application Component) Business Partner
     ⤷ FS_BP_FSP_CLEANSING_DOCU (Package) FS Business Partner Data Cleansing - Documentation Objects
IMG Activity
ID BP_CLEANSE_RELEASE Assign Release Procedure to Release Object  
Transaction Code S_FPD_79000161   (empty) 
Created on 20100913    
Customizing Attributes BP_CLEANSE_RELEASE   Assign Release Procedure to Release Object 
Customizing Activity BP_CLEANSE_RELEASE   Assign Release Procedure to Release Object 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BP_CLEANSE_RELEASE    

Use

In this Customizing activity, you make the settings for releasing the release object FSBP_CC. Since the release of release objects is regulated by the SAP Business Workflow, in the Run Release Workflow group box you need to define if and when the system places a release object in the release process.

Requirements

You have made the standard settings for the SAP Business Workflow under Maintain Standard Settings.

Standard settings

The release process is not configured in the standard system for the release object FSBP_CC because the default implementation of the business add-in BAdI: Rules for Release-Relevance never identifies release-relevance.

Special Features of Release Object FSBP_CC (Data Cleansing Case - SAP Business Partner for Financial Services)

The data cleansing function of SAP Business Partner for Financial Services is based on the assumption that you have decided on the release-relevance of a data cleansing case in the BAdI Rules for Release-Relevance and have forwarded the information to the release tool being used. The structure FSBP_CC_RELEASE contains the attribute IS_RELEASE_RELEVANT for this information. This is the only attribute that can be used to determine the release-relevance of the release object FSBP_CC.

Therefore, you must always select Conditional in the Run Release Workflow group box and check that the release attribute Indicates That Data Cleansing Case Must Be Approved (technical name: IS_RELEASE_RELEVANT) is the sole release reason.

Activities

  1. Select Conditional in the Run Release Workflow group box.

    Note

    If you switch from Always, Conditional or Statistical to a different type, the system deletes all the settings specific to this type.

  2. Select the required release steps in the Release Basic Data group box.
  3. Make sure that the decision from the business add-in BAdI: Rules for Release-Relevance has been configured as the sole release reason for the release process. This is transferred in the release attribute Indicates That Data Cleansing Case Must Be Approved (technical name: IS_RELEASE_RELEVANT). The Settings for Release Process table must contain the following rows:

Release Attribute        Indicates That Data Cleansing Case Must Be Approved

Lower limit        X

Upper limit       

Relational operator        EQ

To check or change the release reason for a release process, make the following settings:

  1. If you choose Display All, you can check whether release reasons have already been defined for the release object.
  2. Go back.
  3. Choose a release procedure for which you want to define release reasons.
  4. Choose Execute in change mode.
    5. If release reasons have not already been defined for the release object, the Customizing: Release Procedures screen appears.
    If release reasons have already been defined for the release object, the Settings for Release Procedure screen appears. If you choose New Entry or select a row in a release reason, the Customizing: Release Procedures screen appears.
  5. Define or change a release reason for the selected release object and release procedure by selecting release attributes from the overview tree and assigning a lower limit (and an upper limit for ranges) and a relational operator to each release attribute in the Free Selections group box.

When defining release reasons, make sure there is an 'And' connector between the conditions that you define with the value entries for the release attributes.
Also note the connection between release reason and the exact rule definition in the corresponding Customizing activity Assign Rule to Release Steps for the corresponding release object. You must make sure that the system finds a user group for each release object via the rule; meaning that the rules are defined in such a way that they cover all release reasons.
  1. Assign the relational operator by double-clicking the entry fields of the release attributes.

The system assigns the number for the release reasons.
If you want to delete individual release reasons, you must delete all the release attributes of this release reason individually. Note that the system deletes all the release reasons if you choose Delete Entries for Release Object.
  1. Choose Execute.
  2. Go back to the initial screen for the Customizing activity.

  1. Save your entries.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BP_CLEANSE_RELEASE 0 KFM0000891 Business Partner 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
BCA_RELPROC_INDX T - Individual transaction object BP_CLEANSE_RELEASE  
History
Last changed by/on SAP  20121210 
SAP Release Created in 400