Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD (Application Component) Sales and Distribution⤷
ERP_SD_ANALYTICS_CORE_TR (Package) Sales, Billing and Delivery Analytics - Translation Relevant
IMG Activity
| ID | SHP_ODP_MC12VC0HDR | Adjust ODP Data for Header Data (MC12VC0HDR) |
| Transaction Code | S_EBS_44000328 | (empty) |
| Created on | 20110104 | |
| Customizing Attributes | SHP_ODP_MC12VC0HDR | Adjust ODP Data for Header Data (MC12VC0HDR) |
| Customizing Activity | SHP_ODP_MC12VC0HDR | Adjust ODP Data for Header Data (MC12VC0HDR) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_SHP_ODP_MC12VC0HDR |
Use
This Business Add-In (BAdI) allows you to enhance the header data from the outbound delivery, by including customer-specific field content in the evaluation (operative reporting).
This BAdI is only called at query runtime when the data is determined by direct access to the database of your ERP system.
The query definition includes the following data and information:
- The query is based on DataSource 2LIS_12_VCHDR (Outbound Delivery: Header Data).
- The assigned extract structure MC12VC0HDR
(Outbound Delivery: Header Data) defines the number of fields that the extractor offers the search and analytics model 0OPS_12_VCHDR_T01.
The above-mentioned query is based on this search and analytics model with the defined operational data provider (ODP) 0OPS_12_HDR.
When the query is run, the system generates the TransientProvider 2O0OPS_12_HDR, into which the data is loaded, and which is used to evaluate the queries.
You can integrate your customer-specific fields into the query evaluation as follows:
- Using the append method, add your customer-specific fields to the extract structure (transaction LBWE).
- After you have enhanced your extract structure, you can add your customer-specific fields to the above-mentioned search and analytics model. To enhance the model, use the Modeler for Search and Analytics application.
For more information about this application, refer to SAP Help Portal, under Introducing SAP NetWeaver Enterprise Search -> Configuration and Administration Tools -> Modeler for Search and Analytics. - Using this BAdI, you can fill these customer-specific fields for the query evaluation.
To do this, implement the BAdI method ADAPT_DATA, to adjust the extracted results data. At query runtime, the content of the extract structures is enriched accordingly.In the data provision process at query runtime, this method is called once for each data request from the query.
If a query requests data via several DataSources (extract structures or ODP models), the system calls the relevant BAdI method once for each DataSource. - In the BEx Query Designer, change the query definition such that these customer-specific fields become visible in the results list.
Note:
This BAdI is not called if the data is determined at query runtime via SAP NetWeaver Business Warehouse Accelerator (BWA). In that situation, you can use the customer exits from the Logistics Information System (LIS) to fill your customer-specific fields before the application runtime.
For more information, refer to the documentation for the enhancements MCS10001 (Sales Order), MCS50001 (Delivery), and MCS60001 (Billing Document) in Transaction SMOD (SAP Enhancements), and to SAP note 576886.
Standard settings
The BAdI does not provide default coding or a fallback class implementation.
Activities
Implement the method ADAPT_DATA for the use case described above.
For more information, refer to the documentation on the method ADAPT_DATA.
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
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 | 20110104 |
| SAP Release Created in | 606 |
