2011 Mar 03 12:47 PM
Hi,
I have a few queries as below:
1. I need to migrate BILLDOCEBF object. I am maintaining the entries in the SPRO for the same, but am not sure what the structure for the Z (EBF) table should be? Can someone help me understanding the structure of the Z table required for migrating the BILLDOCEBF object.
2. At present, we are migrating historical contracts using the MOVE_IN_H object (with Billing order as suppressed), but are facing an issue that we cannot bill the installation for the active time slice. It throws out an error something like " Historical Contract XXXX not billed". Hence, we are looking at migrating the Billing Document EBF. Is this the right object for this task or should we be looking at the other object for migrating billing document (BILLDOC) as we already are migrating all the historical installation structure?
Please do let me know if all this needs further detailing at my end.
Thanks for all your help.
Karan
2011 Mar 03 5:57 PM
Hi,
To the point nr. 1 - EBF data pool structure:
You have to create local storage for the lines from the legacy billing documents.
The structure should be created::
1. EBFKEY - EBF Lines - Key Fields
2. EBFLIN - EBF Lines - Data Fields
3. CI_EBLIN - EBF Lines - Data Fields - Customer Include
Example fields:
.INCLUDE EBFKEY
MANDT
BELNR
BELZEILE
.INCLUDE EBFLIN
BELZART
BUCHREL
PRINTREL
AKLASSE
TVORG
GEGEN_TVORG
LINESORT
AB
BIS
TIMTYPZA
SNO
MASSBILL
TIMBASIS
TIMTYP
TARIFNR
KONDIGR
EIN01
MWSKZ
ERMWSKZ
NETTOBTR
TWAERS
PREISTUF
PREISTYP
PREIS
VONZONE
BISZONE
ZONENNR
PREISBTR
MNGBASIS
PRCTR
KOSTL
I_ZWSTAND
I_ZWSTNDAB
I_ABRMENGE
ZEITANT
.INCLUDE CI_EBFLIN
PROGRAMM
EIN02
AUS01
AUS02
STGRQNT
STGRAMT
MENGESTREL
BETRSTREL
I_ZWSTVOR
GERAET
UMWFAKT
STAFO
AUFNR