Hierarchy

⤷

⤷

IMG Activity
ID | FAGL_ALE_SET_SINGL_T | BAdI: Identify Documents for Single Document Transfer |
Transaction Code | S_EB5_05000183 | (empty) |
Created on | 20090302 | |
Customizing Attributes | FAGL_ALE_SET_SINGL_T | BAdI: Identify Documents for Single Document Transfer |
Customizing Activity | FAGL_ALE_SET_SINGL_T | BAdI: Identify Documents for Single Document Transfer |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FAGL_ALE_SET_SINGLE_TRANSFER |
Use
This Business Add-In (BAdI) is used in General Ledger Accounting (FI-GL) (New) for the ALE distribution scenario FI-GL (New), Transfer of Totals and Single Documents in Distributed Systems.
This distribution scenario uses the message types FAGLDT01
for single document transfer and FAGLST01
for aggregated document transfer.
In this distribution scenario, the system uses the document to determine during posting whether the document is transferred individually or in aggregated form.
With the standard settings, the system individually transfers documents that contain an account for which the Account Managed in External System indicator is set in the account master record. In Customizing, you can set up the individual transfer to be applied generally or to be applied for all documents that contain a receivable or payable account (in ALE Customizing under Make Basic Settings for Distribution Scenario).
You can override these settings with this BAdI.
Requirements
You have activated the distribution scenario FI-GL (New), Totals Document and Single Document Transfer in Distributed Systems for the desired company codes in ALE Customizing under Activate Distribution Scenario for Each Company Code.
Standard settings
This BAdI is not active in the standard delivery.
The BAdI is not for multiple use, and it is not filter-dependent.
If the BAdI is activated without changes, the system behaves as if the BAdI were not activated. In this way, the system uses the document and Customizing settings to determine whether individual or aggregated documents are transferred. Changes are not made to this decision.
There is no default implementation.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
In the BAdI, the document is transferred to tables IT_BKPF
and IT_BSEG
.
To mark a document for single document transfer, you have to set the CV_SINGLE_TRANSFER
parameter to 'X
'. If the CV_SINGLE_TRANSFER
parameter field is left empty, the document is marked for transfer in aggregated form.
See also
Method: Flag Document for Single Transfer (SET_SINGLE_TRANSFER)
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20090302 |
SAP Release Created in | 605 |