Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI (Application Component) Financial Accounting⤷
FIN_FSSC_SR_INT (Package) FSSC - Integration of CRM Service Request
IMG Activity
| ID | FSSC_SAPF110O_RETRIE | BAdI: Application Context for Automatic Payments |
| Transaction Code | S_EB5_05000150 | (empty) |
| Created on | 20090223 | |
| Customizing Attributes | FSSC_SAPF110O_RETRIE | BAdI: Assign Values in Application Context - 3 |
| Customizing Activity | FSSC_SAPF110O_RETRIE | BAdI: Assign Values in Application Context - 3 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FSSC_SAPF110O_RETRIEVE |
Use
This Business Add-In (BAdI) is used in the Financial Accounting (FI) component. You can use this BAdI to assign or change values in the application context for Automatic Payment Transactions (transaction F110) before determining target field values and transferring them to the CRM Service Request UI.
When you launch the Service Request UI from an ERP backend transaction, some of the fields in the UI can have settings based on the application context information in that ERP backend. In certain circumstances, you may need to change this context information by setting values expected in the CRM UI.
You may also want to add your own source fields when determining CRM target field values in view cluster SSC Group Settings. In this case, you can also implement the BAdl to set the runtime value of your enhanced source field list.
This BAdl gives you a way to impact the determination of field values in the CRM Service Request UI when this UI is launched from the ERP backend.
You can use BAdI method RETRIEVE_APPLICATION_CONTEXT to assign or change values in the application context for automatic payments (transaction F110).
The current content of the line item display is imported to the BAdI with the following parameters:
- IV_TCODE: Current Transaction Code
- IS_REGUH: Settlement data from payment program
- IS_REGUP: Processed item from payment program
The application context is used to fill the service request. Based on the current content of the transaction, the system prefills the application context before the BAdI is called. In your BAdI implementation, you can enhance the application context (changing parameter CS_APPLICATION_CONTEXT) based on the import parameters, as follows:
- You can assign additional business partners.
- You can change the assigned company code.
- You can change the description of the service request. Alternatively, you can assign the service request description in the Determination of Service Request Attributes from Application Context.
- You can add notes or assign additional linked objects, which enhance the service request directly.
- You can add additional information, in the form of field values, that can be used as one of the following:
- Additional source fields in Determination of Service Request Attributes from Application Context
- For information on input fields for an implementation to enhance the service request, see the documentation for BAdI: Set Service Request Values
Requirements
If you want to determine additional source fields, you must also do the following:
- Define them in BAdI: Enhance Source Fields
- Use them in Determine Service Request Attributes from Application Context
Standard settings
In the standard system, there is no active BAdI implementation.
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 | 257 | Create User Exits |
| 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 | 20090326 |
| SAP Release Created in | 605 |
