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_VALID_DC | Information on Validating Document Splitting |
| Transaction Code | S_AC0_52000891 | (empty) |
| Created on | 20050407 | |
| Customizing Attributes | FAGL_VALID_DC | Information on Validating Document Splitting |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FAGL_VALID_DC |
Use
You use validation during migration to check the documents in the production system before activating New General Ledger Accounting. By conducting this check, you ensure that error-free documents are available for document splitting when you activate New General Ledger Accounting.
The aim of validation is to test as early as possible and in a live system the business processes modeled in document splitting. Validation enables you to perform the following quality assurance measures:
- Extend iteratively the quality and scope of modeling
- Identify early on any problem areas in the operational posting transactions and undertake any necessary measures
- Ensure that the posting rules specified in document splitting are adhered to
- Prevent the accumulation of documents containing errors and for subsequent posting from the current production system
During the migration, you can log error statuses in the production system and postprocess them in the test system (preparation system). In this way, you prepare the postprocessing of these documents in the test system (if they need to be posted subsequently) or you identify and remedy any gaps in the modeling of document splitting and in the business processes.
If the document to be posted does not fulfill the requirements of document splitting, you can set up the production system so that messages are issued and grant the user appropriate ways of intervening. In the case of third-party processes (such as MM or SD) and automatic processes in FI (such as payment runs or recurring entries), you can only have entries generated in the log, for example.
You can set up dependencies for the error messages on other constraints (such as account assignment determination or master data processing) that need to be fulfilled coupled with the attainment of a certain project status. You can activate using time dependency and in stages.
Requirements
The validation of document splitting occurs in the production system. The upgrade to the ERP system needs to have occurred. To be able to perform validation in a useful manner and thereby avoid redundant error logs, the following prerequisites need to be fulfilled:
- You have assigned the document splitting method.
- You have made or checked all other required settings in Customizing for document splitting.
- You activate the validations when processing the migration plans. For this reason, you need to have transported the migration plans to the production system and determined the leading ledger.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 252 | Prepare Data Transfer Fields |
| 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 | FAGL_VALID_DC | 0 | HLA0006520 | Basic Functions |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20050407 |
| SAP Release Created in | 600 |
