SAP ABAP IMG Activity FAGL_ALE_SEND_CLR_FD (BAdI: Clear Fields Before Document Aggregation)
Hierarchy
SAP_FIN (Software Component) SAP_FIN
   FI-GL (Application Component) General Ledger Accounting
     FAGL_DISTR_SCEN_1_SFWC_RS (Package) Distribution Scenario: Transfer of Totals Docs + Single Docs
IMG Activity
ID FAGL_ALE_SEND_CLR_FD BAdI: Clear Fields Before Document Aggregation  
Transaction Code S_EB5_05000200   (empty) 
Created on 20090304    
Customizing Attributes FAGL_ALE_SEND_CLR_FD   BAdI: Clear Fields Before Document Aggregation 
Customizing Activity FAGL_ALE_SEND_CLR_FD   BAdI: Clear Fields Before Document Aggregation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAGL_ALE_SEND_CLEAR_FIELDS    

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.

You can use this BAdI to initialize fields. In this way, the system uses such fields for summarization.

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

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:

  1. 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.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. 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.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. 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:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

There are two documents with the following values:

Doc. No.    Account    Amount    Dr/Cr    Cost Center    Profit Center

1    400000    100    Dr    KST01    PC A

1    400010    100    Cr    KST02    PC A

2    400000    50    Dr    KST02    PC A

2    400010    50    Cr    KST03    PC A

Without the BAdI, the system creates one document from the two documents, and the aggregated document has the following data:

Doc. No.    Account    Amount    Dr/Cr    Cost Center    Profit Center

3    400000    100    Dr    KST01    PC A

3    400010    100    Cr    KST02    PC A

3    400000    50    Dr    KST02    PC A

3    400010    50    Cr    KST03    PC A

If you do not need a cost center for the totals document, you can delete the cost center in all line items for the purposes of the aggregation. The totals document then appears as follows:

Doc. No.    Account    Amount    Dr/Cr    Cost Center    Profit Center

3    400000    150    Dr        PC A

3    400010    150    Cr        PC A

Example Coding:

DELETE CT_FIELDS WHERE object = 'POPER'.

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  20101008 
SAP Release Created in 605