VDA4927, transfer, and LE reporting
Purpose
This page extends the loading-unit documentation around two topics that often belong together in projects: potential VDA4927-related transfer of loading-unit data and report-oriented evaluation of posted movements per account keeper.
1. Classify VDA4927 support correctly
Automotive is prepared for loading-unit-related VDA messages. The legacy documentation especially names these record types:
- VDA4927 record type 721
- VDA4927 record type 722
- VDA4927 record type 723
- VDA4927 record type 724
- VDA4927 record type 725
- VDA4927 record type 729
The important point is that this preparation does not automatically mean that every variant is productive without project clarification. The concrete functionality must be defined, aligned, and tested within the project.
For users, this means:
- not every theoretically supported message is automatically active in your tenant,
- the interface logic for loading units should always be aligned with the real reconciliation process of the partner,
- report, account evaluation, and message must all reflect the same account-keeper logic.
2. Use LE reports as evidence
In addition to account and history pages, report-oriented evidence also matters. The Loading Equipment Account report shows movements for one account keeper within a defined period.
| Report view | What it is used for |
|---|---|
| Loading Equipment Account | periodic view of posted package or loading-unit movements for one account keeper |
| Movement filters | narrow down by period, partner, or item reference |
The report is mainly intended for monthly reconciliation with the respective account keeper. It complements page-based views because it condenses the movements for communication and evidence.
Recommended use in project practice
- First clarify whether your project actually uses VDA4927 productively.
- Then align which record types are business-relevant.
- For periodic evidence, build the LE reports per account keeper and period.
- Always compare report values against LE account, history, and, where relevant, empties documents.
Typical error patterns
| Situation | Possible cause | Check |
|---|---|---|
| Partner expects VDA4927, but the system sends nothing | project transfer functionality was never fully defined | inspect project scope and technical activation |
| Report totals do not fit the reconciliation | wrong period or wrong account-keeper filter | inspect report parameters and account-keeper relation |
| LE report and page evaluation differ | underlying filters or movement types are not the same | compare report, LE account, and history in parallel |
Result
- You can classify VDA4927-related loading-unit transfer realistically as a project building block.
- You know when report-based LE evaluations are useful for account-keeper reconciliations.
- You avoid misunderstandings between theoretical interface capability and the actually active project scope.
Links