Hierarchy
⤷ MM-PUR-FIP (Application Component) Perishables Procurement
⤷ FIP_DDIC (Package) DDIC package for Fresh Item Procurement
IMG Activity
ID | W_FIP_037 | BAdI: Access Sales Price |
Transaction Code | S_E4A_94000217 | (empty) |
Created on | 20080611 | |
Customizing Attributes | W_FIP_037 | BAdI: For Accessing Sales Price |
Customizing Activity | W_FIP_037 | BAdI: For Accessing Sales Price |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FIP_BADI_SALES_PR_INFO_BAL |
Use
This technical Business Add-In (BAdI) is part of a business abstraction layer used internally by SAP. It is not intended for reuse by customers. This technology enables individual functionality or complete applications to be called either by back-end functions or enterprise services.
This BAdI contains the following method:
- READ_RECIPIENT_PRICE
The method
READ_SALES_AREA
returns a table containing the sales price for material / selling plant or for material / selling plant / customer . Therefore, the following input parameters have to be filled in: IV_WERKS_D
- Relevant supplying plant
IV_ADATU
- Date on which validity begins
IV_BDATU
- Date validity ends
IV_RETAIL_SWITCH
- A flag which must be set when the retail switch is on in the system
IT_SALES_PRICE
- Input table for material-recipient list
Requirements
Standard settings
As with BAdIs in the ES_FIP_BAL
enhancement spot, a developer should never use the GET_BADI
call to create an instance of this BAdI. Rather, the developer should first get an instance of the CL_FIP_BAL_FACTORY
class and then use its GET_BADI
method to instantiate the required BAdI.
Example - Instantiation of the FIP_BADI_SALES_PR_INFO_BAL
BAdI
DATA:
lo_bal_factory TYPE REF TO cl_fip_bal_factory,
lo_bal_sales_pr_info TYPE REF TO fip_badi_sales_pr_info_bal.
" Get instance of the BAL factory
cl_fip_bal_factory=>get_instance(
IMPORTING eo_factory = lo_bal_factory ).
" Instantiate the FIP_BADI_SALES_PR_INFO_BAL BAdI
lo_bal_sales_pr_info ?= lo_bal_factory->get_badi(
cl_fip_const=>gc_badi_def-sales_pr_inf ).
This BAdI was designed to run only one BAdI implementation. It uses a filter named ACCESS_TYPE
to determine which implementation is to be executed. Each implementation must have a different filter. In the GET_BADI
call to the BAL factory, the value of ACCESS_TYPE
is automatically determined and set.
All possible values of ACCESS_TYPE
:
- 0BA
Implementation using BAPIs and/or direct database access
- 0ES
Implementation using enterprise services, which allows access to different backends in case used functionalities are available in different systems.
- Cnn (where nn is a one-digit or two-digit number)
Customer implementation
The BAL factory class determines the value of the ACCESS_TYPE
filter by going through the following process:
- Get the value from the
FIP_C_BAL_BADI
client-specific customizing table. - If a value was not yet obtained, get the value from the
FIP_C_BAL_CONF
client-specific customizing table. - If a value was not yet obtained, the default value as determined by the BAL factory will be used. In ERP 6.0 EHP4, this value is 0BA.
As of ERP 6.0 EHP4, 0BA and 0ES implementations exist for each BAdI that belongs to the ES_FIP_BAL
enhancement spot.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20080703 |
SAP Release Created in | 604 |