Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-GL (Application Component) General Ledger Accounting⤷
FAGL_MIG_CONVERSION (Package) Future Standard Reports for Building Data
IMG Activity
| ID | FAGL_V_FAGL_MIG_PROC | Define Alternative Business Transaction Assignment |
| Transaction Code | S_AC0_52000621 | (empty) |
| Created on | 20050301 | |
| Customizing Attributes | FAGL_V_FAGL_MIG_PROC | Define Alternative Business Transaction Assignment |
| Customizing Activity | FAGL_V_FAGL_MIG_PROC | Define Alternative Business Transaction Assignment |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FAGL_V_FAGL_MIG_PROC |
Use
In this IMG activity, you can assign an alternative business transaction variant to selected documents. In the migration, this assignment overrides the standard derivation of the business transaction variant, such as derivation from the document type.
Requirements
Either you have assigned a document splitting method in Customizing for document splitting, or you have entered an alternative document splitting method in the migration settings.
Note:
Here, you only assign existing business transaction variants and may also need to have assigned a corresponding rule to the document splitting method.
Standard settings
Activities
In the case of documents that cannot be migrated using the business transaction variant derived in the standard, assign an alternative business transaction variant.
In the case of cross-company-code documents, single documents from other company codes are automatically assigned to the same business transaction variant. For this reason, the internal key of the entire document is displayed in the fields Reference Key and Reference Transaction. You cannot assign different business transaction variants to documents with the same reference fields. Check your assignments and how they are derived by saving your settings.
For the migration of the documents contained in the table, the business transaction variant assigned explicitly is used instead of the business transaction variant derived from the document type or transaction to interpret the document. This is logged in the status management of the migration objects in the Adjustment field. You can display the status management in the IMG activity Analyze Migration Status and in the log for migration-specific document adjustment.
Example
You have entered a customer invoice with document type DZ. However, in Customizing for document splitting, the business transaction Payment is assigned to document type DZ in a variant that requires a bank account line in the document.
Migration of the invoice is rejected with the error message that the document does not contain the required bank account line.
Assign business transaction Customer Invoice with an appropriate business transaction variant to the document in this IMG activity. You can then repeat the migration for this document.
Document splitting now interprets the document as a customer invoice and no longer applies the business transaction Payment to this document.
Business Attributes
| ASAP Roadmap ID | 152 | Design data acquisition |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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 | FAGL_V_FAGL_MIG_PROC | 0 | HLA0006520 | Basic Functions |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_FAGL_MIG_PROC | V - View | SM30 |
History
| Last changed by/on | SAP | 20050308 |
| SAP Release Created in | 600 |
