SAP ABAP IMG Activity SIMG_CFMENUORKSACTDA (BAdI: Implement Transfer of External CO Actual Data)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ CO (Application Component) Controlling
     ⤷ KIMB (Package) Cost Accounting: Manual Actual Postings
IMG Activity
ID SIMG_CFMENUORKSACTDA BAdI: Implement Transfer of External CO Actual Data  
Transaction Code S_AL0_96000819   (empty) 
Created on 20020205    
Customizing Attributes SIMG_CFMENUORKSACTDA   BAdI: Implement Transfer of External CO Actual Data 
Customizing Activity SIMG_CFMENUORKSACTDA   BAdI: Implement Transfer of External CO Actual Data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EXT_CO_ACTUAL_DATA    

Use

This Business Add-In transfers external actual posting data to Overhead Cost Controlling. This implements the uploading of the posting data into the SAP system.

Requirements

You can transfer actual posting data for the following business transactions:

  • Activity allocation
  • Primary cost reposting
  • Revenue reposting
  • Manual cost allocation
  • Non-allocable activities
  • Statistical key figures
  • Reversal

Depending on the transaction, the BAdI implementation transfers the uploaded posting data to the following output tables:

  • aa_headers and aa_items for activity allocations ( BAPIAAHDR or BAPIAAITM),
  • rc_headers and rc_items for primary cost repostings ( BAPIRCHDR or BAPIRCITM),
  • rr_headers and rr_items for revenue repostings (structure BAPIRRHDR or BAPIRRITM),
  • ma_headers and ma_items for manual cost allocations (BAPIMAHDR or BAPIMAITM),
  • ia_headers and ia_items for non-allocable activities (BAPIIAHDR or BAPIIAITM),
  • skf_headers and skf_items for statistical key figures ( BAPISKFHDR or BAPISKFITM) or
  • rev_headers for reversals (BAPIDOCHDRR)

In addition, if profitability segments are to be assigned:

  • send_crit (BAPISCRIT) and
  • recv_crit (BAPIRCRIT).

The output tables for the document headers (xx_headers) have the same structure as the corresponding interface paramter of the BAPIs for these transactions. This is specified above in parentheses.

The output tables for the document items (xx_items) have the following components:

  • CO_AREA - controlling area
  • DOC_NO - document number
  • ITEMS - document items.

The document number is initially used for assigning the document headers to document items. If you do not set the External Document Number Assignment for the data transfer, these document numbers are replaced by numbers from the internal number range related to the transaction. If you set this indicator, the documents are posted with the specified document numbers. You need to ensure that the specified document numbers are in teh correct external number ranges.

The document item component is a table with the same structure as the corresponding interface paramter of the BAPI for this transaction. This is specified above in parentheses.

Actual posting data for more than one transaction can be transferred at the same time. To enable this, the BAdI implementation must fill the corresponding output tables.

Standard settings

If there is no active BAdI implementation, the system does not transfer any actual posting data.

Activities

Create an implemenation for the EXT_CO_ACTUAL_DATA definition and implement the IMPORT method.

Example

An example for uploading posting data that was entered in Excel and saved as a tab-separated text file has been implemented in the CL_IM_EXT_CO_DATA_EXAMPLE class (implementation name EXT_CO_DATA_EXAMPLE).

The following data format is required for this example:

  • A data block is started off with a header and ended by an empty row.
  • The header is in the first cell of the row and the rest of the cells in this row are empty.
  • The header defines the structure of the following data rows and must also contain the name of one of the BAPI structures mentioned above (BAPIxxHDR, BAPIxxITM etc.).
  • The row that comes after the header contains the names of the fields used in the following data rows.
  • The following data rows contain the posting data, whereby the field name row described above is the "table header".

Example:

BAPIRCHDR
CO_AREA DOC_NO POSTGDATE TRANS_CURR
0001 0000000001 20011001 EUR
0000000002 20010921 EUR
0000000003 20010819 EUR

BAPIRCITM
CO_AREA DOC_NO SEND_CCTR REC_CCTR VALUE_TCUR COST_ELEM
0001 0000000001 R-KS1 R-KS2 100 0000417000
R-KS3 R-KS2 120 0000420000
R-KS1 R-KS4 50 0000417000
0000000002 R-KS5 R-KS2 200 0000420000
0000000003 R-KS1 R-KS3 40 0000420000
R-KS2 R-KS1 160 0000417000

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  20020207 
SAP Release Created in 470