The technical means for exchanging utilities business data are transfer documents (TDOC), which each carry a business message. You can view the transferred data structures and their content in the Details section of the Monitor TDOC app. A business message comprises one or more business objects, with each object corresponding to one of the data structures.
For the exchanged data structures, there are corresponding DDIC structures in the business system that have a table on the top level. All these data retrieval tables are contained in table /US4G/S_UBD_DATA.
For most of these DDIC structures, there is a dedicated ABAP class that handles the data retrieval to fill the structure. In the class documentation in the business system, you find more information about how the retrieval works.
In messages that request data from another system, the REQUEST and REQ_FILTER components are used. When sending messages with actual content, the DATA components are filled. These DATA components can include several levels of detailed information.
Down on field level, you see details like data type and field length. There are fields for free values like text or meter readings, and there are fields with a fixed set of allowed values. For the fixed values, the MaCo cloud uses human-readable values in camel case notation instead of the codes from the BDEW documents. For example, for the meter reading complaint reason, ComplaintValuesTooHigh and TooLow, instead of the BDEW codes Z04 and Z05. When converted into EDIFACT messages later, of course, the prescripted codes are used.
