Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

This wiki page describes the possibility to determine a different driver function module that is called up instead of the module defined in the standard.

Overview

This badi will be called within the Function Module META_BAPI_DISPATCH after the standard logic based on the Table BBP_FUNCTION_MAP.

Methods

The badi has only one method DETERMINE_DRIVER.

DETERMINE_DRIVER

Parameters

Type

Associated Type

Description

LOGICAL_SYSTEM

Importing

BBP_BACKEND_DEST-LOG_SYS

Logical System

DESTINATION

Importing

BBP_BACKEND_DEST-DEST

Logical Destination (Specified in Function Call)

SYSTEM_TYPE

Importing

BBP_BACKEND_DEST-SYS_TYPE

System type

RFC_POSSIBLE

Importing

BBP_BACKEND_DEST-RFC_POSS

Indicator: If the System Is RFC-Compatible

LOCAL_SYSTEM

Importing

BBP_BACKEND_DEST-LOC_SYS

Create Materials Management Document in Local System

OBJECT

Importing

SWO_OBJTYP

Object Type

METHOD

Importing

BBP_METHOD

Method

FUNCTIONNAME

Changing

TFDIR-FUNCNAME

Name of the Function Module

The badi get the details of the target system as import parameter based on the customizing in SPRO/Define System Landscape (BBP_BACKEND_DEST), and also the same OBJECT and METHOD parameter how the META_BAPI_DISPATCH has been called.
The parameter returned in FUNCTIONNAME will be used for the function call and the value from the standard design will be already assigned to it before the badi call.

Related Content

Related Documents

Using RFC transfer with ECC system 6.04 and higher