Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-SLS (Application Component) Sales⤷
ERP_PRS_SD (Package) Professional Services; parts in SD Core
IMG Activity
| ID | BADI_SLS_LO_OIF_FOUP | BAdI: Define Follow-Up Activities for Configurable Sales UI |
| Transaction Code | S_EB5_05000426 | (empty) |
| Created on | 20091014 | |
| Customizing Attributes | BADI_SLS_LO_OIF_FOUP | Define Follow-Up Activities for Configurable Sales UI |
| Customizing Activity | BADI_SLS_LO_OIF_FOUP | Define Follow-Up Activities for Configurable Sales UI |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_SLS_LO_OIF_FOLLOW_UP |
Use
This Business Add-In (BAdI) is used in the Configurable Sales UI in the Sales and Distribution (SD) component.
You can use this BAdI to control follow-up processing in the Sales UI. The follow-up actions are defined in transaction Overview of Launchpads (transaction code LPD_CUST), launch pad role LO_OIF with launch pad instance FOLLOW_UP.
Requirements
- As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), you can use the Sales&Distribution Simplification 2 (LOG_SD_SIMP_02) business function (software component SAP_APPL). If you have activated this business function, you can work with the Lean Order OIF-based Configurable Sales UI.
- As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), you can use the Sales&Distribution 2 (LOG_SD_CI_02) business function (software component SAP_APPL). This business function provides the infrastructure of follow-up processing as well as three standard follow-up actions Print Preview, Billing and Delivery.
- To access the list of possible follow-up actions, complete processing a sales document by choosing the following pushbuttons:
- Create and Change mode: Save and Follow Up
- Display mode: Follow Up
Standard settings
This BAdI is shipped with two BAdI implementations:
- The first enhancement implementation covers the standard follow-up actions Print Preview, Billing, and Delivery.
- The second enhancement implementation covers the professional services-related follow-up actions Sales Document Staffing, Project Staffing, and Project Setup.
The relevant OBN (object-based navigation) business parameter(s) are determined in these implementations. For example, the current sales document number for which the follow-up action is being launched and which is needed in the subsequent process step is determined here.
Activities
The BAdI consists of the following methods:
- ADAPT_LIST
This method is called after the user finished the sales document processing by choosing Follow Up. You can use it to adapt the list of follow-up actions. We recommend that you only delete follow-up actions you no longer need. Use launchpad Customizing if you want to create new follow-up actions or change existing ones.
- ADAPT_PARAM
This method is called after the user has launched a follow-up action from the list. You can use it to enrich the business parameters of the chosen follow-up action with business data.
For more information, see the relevant method documentation for the IF_BADI_SLS_LO_OIF_FOLLOW_UP interface.
Example
The following implementations are available:
- The standard BAdI implementation for the standard follow-up actions Print Preview, Billing, and Delivery is implemented as follows:
- Enhancement Implementation ERP_BADI_SLS_LO_OIF_FOLLOW_UP
BAdI Implementation ERP_BADI_SLS_LO_OIF_FOLLOW_UP
Implementing Class CL_ERP_BADI_OIF_FOLLOW_UP
The enhancement implementation is part of the business function LOG_SD_CI_02. Therefore this implementation is only visible and can be called if this business function has been activated.
- The standard BAdI implementation for the Professional Services-related follow-up actions Sales Document Staffing, <LS Project Staffing, and Project Setup is implemented as follows:
- Enhancement Implementation PRS_BADI_SLS_LO_OIF_FOLLOW_UP
BAdI Implementation PRS_BADI_SLS_LO_OIF_FOLLOW_UP
Implementing Class CL_PRS_BADI_OIF_FOLLOW_UP
The enhancement implementation is part of the business function PRS_ERP_CPILS. Therefore this implementation is only visible and can be called if this business function has been activated.
Notes
SAP only delivers follow-up actions of the launchpad application category OBN Navigation.
- We recommend that you do not change the launchpad Customizing of the standard follow-up actions. If necessary, delete these follow-up actions using the BAdI implementation, method ADAPT_LIST, and create your own follow-up actions in launchpad Customizing.
- Always use unique application aliases in the (virtual) non-SAP name range for your launchpad applications. The application aliases of the standard follow-up actions begin with
SAP_. We ecommend that you do not use this prefix for your launchpad entries.The application alias is the only attribute that all the different launchpad application categories have in common and you should therefore use it to identify the different launchpad applications within your BAdI implementation.
- The above-mentioned standard BAdI implementations rely on this. It is therefore likely that a standard follow-up action will no longer work after its launchpad setup has been changed.
- We recommend that you use OBN Navigation for your customer-specific follow-up actions.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | 20091022 |
| SAP Release Created in | 605 |
