SAP ABAP IMG Activity ME_RELEASE_CREATE (BAdI: Release Creation for Scheduling Agreements with Release Documentation)
Hierarchy
BBPCRM (Software Component) BBPCRM
   SRM-EBP (Application Component) Enterprise Buyer
     BBP_APPLICATION (Package) Structure Package EBP
       ME (Package) Application development R/3 Purchasing
IMG Activity
ID ME_RELEASE_CREATE BAdI: Release Creation for Scheduling Agreements with Release Documentation  
Transaction Code S_P6D_40000001   (empty) 
Created on 20040524    
Customizing Attributes ME_RELEASE_CREATE   BAdI: Release Creation for Scheduling Agreements with Release Documentation 
Customizing Activity ME_RELEASE_CREATE   BAdI: Release Creation for Scheduling Agreements with Release Documentation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ME_RELEASE_CREATE    

BAdI: Release Creation for Scheduling Agreements with Release Documentation

Use

You can use this Business Add-In (BAdI) to influence release creation.

This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).

This BAdI includes the following methods:

  • Change Data Before Release Creation (BEFORE_CREATION)
  • Change Data After Release Creation (AFTER_CREATION)

This BAdI is called during manual and automatic release creation.

Requirements

Standard settings

The BAdI is not active in the standard system.

The BAdI is not filter-dependent and is not multiple-use.

This BAdI replaces, as of 4.70, the following customer exits in enhancement MEETA001:

  • EXIT_SAPLEINL_001: Customer Enhancement Forecast Delivery Schedules: Determine Schedule Line Type (such as Backlog)
  • EXIT_SAPLEINL_002: Customer Enhancement Forecast Delivery Schedules: Determine Schedule Line Type (such as Backlog) (Note, that the BAdI only replaces this EXIT in specific releases (as of SAP R/3 4.70).

If you want to implement the BAdI, then you can:

  • Call the existing customer exist in the BAdI method, or
  • Re-implement the BAdI method.

Activities

Example

To call the default coding, choose Goto -> Default Coding.

See also

Methods

Change data going into release creation (BEFORE_CREATION)

Change data created by release creation (AFTER_CREATION)

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
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 ME_RELEASE_CREATE 0 HLA0001538 Scheduling Agreement 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20040524 
SAP Release Created in