Notes on the Data Format (Rental Agreement)
Line: BGR00 structure (folder header)
The following lines contain the rental agreements to be transferred in concurrent order
A rental agreement is introduced with the BVIMV00 structure (rental agreement master data). The BVIMVxx substructures that belong to this rental agreement follow in a random order. As soon as there is a new rental agreement master data, the current rental agreement is finished.
A record consists of a string, the format of which is based on the BVIMVxx structure (structure fields are next to each other without a separator when field lengths are exactly the same). Individual fields must be filled out (in relation to alignment, leading zero etc.) as would be the case in online processing.
The STYPE field (the first field in all structures) identifies the record type:
STYPE |
Structure |
Corresponding Tables |
Contents |
0 - |
BGR00 |
Folder headers |
|
1 |
BVIMV00 |
vimimv |
Master data |
2 |
BVIMV01 |
vimi32 |
Addition rental collateral |
3 |
BVIMV02 |
vimi56 |
Adjustment blocks |
4 |
BVIMV03 |
vzzusp |
Extras |
5 |
BVIMV04 |
vimi54 |
Adjustment types |
6 |
BVIMV07 |
vikoko |
Condition headers |
7 |
BVIMV08 |
vzzkopo |
Condition items |
8 |
BVIMV10 |
vzgpo |
Partner allocations |
9 |
BVIMV05 |
vimiuh |
Sales headers |
A |
BVIMV06 |
vimiui |
Sales items |
B |
BVIMV09 |
vimi55 |
Index adjustment data |
C |
BVIMV11 |
vimi38 |
Cost center assignments |
Caution
During rental agreement direct input, the nodat character is not used for the application.
If the fields are empty, you do not fill them.
If there are required fields, you will see an information message that there is an initial value for a required field.