Hierarchy
⤷ MM-PUR-FIP (Application Component) Perishables Procurement
⤷ FIP_DDIC (Package) DDIC package for Fresh Item Procurement
IMG Activity
ID | W_FIP_036 | BAdI: Access Sales Orders |
Transaction Code | S_E4A_94000216 | (empty) |
Created on | 20080611 | |
Customizing Attributes | W_FIP_036 | BAdI: For Accessing Sales Order |
Customizing Activity | W_FIP_036 | BAdI: For Accessing Sales Order |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FIP_BADI_SALES_ORDER_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. It is used for handling sales orders.
This BAdI uses the following methods:
- CREATE_SALES_ORDER
Creates a new sales order. The default document type and net price condition are used from Customizing.
- CHANGE_SALES_ORDER
Changes the quantity or sets up blocking. The default blocking reason is used from Customizing.
- READ_SO_BY_IDS
Reads all relevant sales document data for the imported sales order IDs
- READ_SO_BY_ELEMENTS
Reads the sales document data according to import parameters.
- FINDOPENSALESORDERS
Determines all sales orders, which are not blocked and not fully delivered. The required import parameter is the supplying plant, and optional parameters are:
- Range of customers
- Range of material
- Range of changing dates or, a range of delivery dates
Requirements
Standard settings
As with all 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_ORDER_BAL
BAdI
DATA:
lo_bal_factory TYPE REF TO cl_fip_bal_factory,
lo_badi_sales_order TYPE REF TO fip_badi_sales_order_bal.
" Get instance of the BAL factory
cl_fip_bal_factory=>get_instance(
IMPORTING eo_factory = lo_bal_factory ).
" Instantiate the FIP_BADI_SALES_ORDER_BAL BAdI
lo_badi_sales_order ?= lo_bal_factory->get_badi(
cl_fip_const=>co_sales_order_bal ).
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 |