Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI (Application Component) Financial Accounting⤷
FIN_FSSC_ICR_INT (Package) FSSC - Integration for Intercompany Reconciliation
IMG Activity
| ID | FSSC_ICR_RETRIEVE | BAdI: Application Context for Intercompany Reconciliation |
| Transaction Code | S_EE5_50000341 | (empty) |
| Created on | 20091124 | |
| Customizing Attributes | FSSC_ICR_RETRIEVE | BAdI: Application Context for Intercompany Reconciliation |
| Customizing Activity | FSSC_ICR_RETRIEVE | BAdI: Application Context for Intercompany Reconciliation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FSSC_ICR_RETRIEVE |
Use
This Business Add-In (BAdI) is used in the Financial Accounting (FI) component. You can use BAdI method RETRIEVE_APPLICATION_CONTEXT to assign or change values in the application context for intercompany reconciliation processes (transactions FBICR1, FBICR2, FBICR3, FBICR3L).
The current content of the transaction call is imported to the BAdI with the following parameters:
- IV_TCODE: Current Transaction Code
- IT_ORGUNIT: Org Unit Data
- IT_PARTNER: Partner Data
- IT_ASSIGNED: Assigned Data
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FSSC_ICR_RETRIEVE | 0 | HLA0001205 | Closing Operations |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20091124 |
| SAP Release Created in | 605 |
