Announcement

Collapse
No announcement yet.

CDD Mandatory fields definition catalogue

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kim Mossong
    replied
    RSM Gaz 01/2021

    CDD Mandatory fields definition catalogue
    • Proposal from Electris will be implemented for the next release 4.60

    Leave a comment:


  • Richard Lütteke
    replied
    In demdc_ annex says Nom et Prénom is mandatory but CDD says only mandatory if "Si IDPC inconnu".

    Leave a comment:


  • Frank Himmes
    replied
    Please find attached BETA 3 version based on CDD 4.50:

    CDD_Annexe_Beta3.pdf

    Feedback is welcome

    Leave a comment:


  • Kim Mossong
    replied
    RSM Gas 10/20
    • Updated version has been published
    • Feedback is welcome
    • Part of the agenda for next SteerCo DSO Gas à The proposals will be analysed and included in the new version
    • Our goal is to create a final version by release 4.50

    Leave a comment:


  • Richard Lütteke
    replied
    Hello,
    thank you for providing the updated version.

    A couple of point after a brief first runthrough:
    According to https://luxmaco.vbulletin.net/forum/...=4752#post4752 the phone nuber was supposed to be optional in
    • DEMDC
    • DEMCF
    • DEMMESPC
    In the beta2 for all three messages the phone number is still marked as X = OBLIGATOIRE.


    Also, the example file temp_202002_1.csv contains to many days (20200301).
    IDFournisseur_reconc_aaaamm_#.csv example file is missing.
    In the example file for arefconsa the ID Fournisseur in the filename is different from the ID fournisseur in line2 #Message ID and #Destinataire message.
    The DEFINITION DE MESSAGE ET CHAMPS OBLIGATOIRES of cdt_IDPC_aaaammjj_IDProcessNr.csv (p.36&37) implies that all fields are X = OBLIGATOIRE in contrast to the table at the bottom of p.37, which marks each of them as obligatiore only for certain cases.
    Last edited by Richard Lütteke; 19.10.2020, 09:46 PM.

    Leave a comment:


  • Frank Himmes
    replied
    Please find attached BETA 2 version based on CDD 4.50:

    CDD_4.50_Annexe_Beta2.pdf

    Feedback is welcome
    Last edited by Frank Himmes; 19.10.2020, 04:54 PM.

    Leave a comment:


  • Frank Himmes
    replied
    RSM GAZ 09/2020:
    • Die Vorschläge werden analysiert und in die neue Version mit übernommen
    • Ein Abkürzungsverzeichnis wird angelegt
    • Die Nachrichten an den TSO werden implementiert
    • Die Tabelle der cdt_message wird implementiert
    • Offene Fragen werden bis zum nächsten RSM in diesem Topic beantwortet
    • Weiteres Feedback ist gewünscht

    Leave a comment:


  • Frank Himmes
    commented on 's reply
    Danke für das schnelle Feedback, wir werden die Verbesserungsvorschläge aufnehmen.

  • Richard Lütteke
    commented on 's reply
    In der message Beschreibung wir der Dateiname immer in Kleinbuchstaben angegeben, im Beispiel sind es dann immer Grossbuchstaben. Was ist richtig?

    Grade für die cdt_ message hatten wir doch eine ganze Tabelle welches Feld wann ein Pflichtfeld ist. Davon sehe ich im Dokument gar nichts.

    Was bedeutet FN / FA ? Das steht nirgends im Dokument. Ich vermute es bedarf einiger einleitender Worte zu Beginn des Dokuments.
    Die Bezeichnungen sind vielleicht etwas ungünstig gewählt. Der Spaltenheader "O" soll wahrschienlich obligatoire bedeuten. Ein X in der Spalte markiert dann ein "Ja, ist obligatiore". Ein "O" in der Spalte ist dann aber wieder optionell?!?

    In t_IDFournisseur_IDPC_aaaammjj_IDProcessNr.csv sollte für den FA doch Date de changement de Fournisseur / d’Acquéreur prévue/possible doch kein Pflichtfeld sein, denn lt. CDD gilt "Si Statut de la demande = 0,....aucune date n’étant indiquée pour un changement de Fournisseur."

    Ein Beispiel für temp_ scheint weiterhin zu fehlen. Ebenso _lc_ ; loadcurve_; loadcurveS30_ ...
    Last edited by Richard Lütteke; 15.09.2020, 12:05 AM.

  • Frank Himmes
    replied
    Please find attached an updated beta-version based on CDD 4.50 for the mandatory fields and message examples:

    CDD_4.50_Annexe_Beta1.pdf

    Changes:
    • New layout
    • Distinction between old and new supplier
    • Extended with optional fields in each message
    • Mandatory fields are marked separately
    • Message examples for every message type
    Feedback is welcome

    Leave a comment:


  • Sebastian Boos
    replied
    RSM Gaz 07/2020
    • message description and message examples will be moved from CDD into this catalogue
    • format of the catalogue needs to be clarified (Excel, PDF, ...?)
    • DSOs are working on this catalogue, publication in the forum probably during September
    • Phone number of customer will be optional field (please see post from Mr. Hauser)
      • Remark will be added: supplier should always send the phone number. In exceptional cases he might leave the field empty.

    Leave a comment:


  • Gabriel Hauser
    replied
    Suggestion:
    According to daily work circumstance within the perspective of suppliers, it would be good to exclude telephone no. from mandatory fields.

    Affected messages:
    • DEMDC
    • DEMCF
    • DEMMESPC

    Leave a comment:


  • Frank Himmes
    replied
    RSM 06/2020:

    Proposals for next version:
    • In case of messages for old and new supplier: distinction between old and new supplier in an own column?
    • Catalogue will be extended with optional fields in each message & mandatory fields will be marked separately
    • Feedback is welcome
    Last edited by Frank Himmes; 01.07.2020, 09:51 AM.

    Leave a comment:


  • Frank Himmes
    started a topic CDD Mandatory fields definition catalogue

    CDD Mandatory fields definition catalogue

    Please find attached a first version based on CDD 4.50 for the mandatory fields for GAZ CONTRL implementation:

    Champs obligatoires.pdf

    Open points to discuss:
    • How to handle messages sent to the old and new supplier with different mandatory fields ( e.g. ri_, rcdce_, rcdcv_)
    • Feedback is welcome!
    Attached Files
    Last edited by Frank Himmes; 30.06.2020, 03:09 PM.
Working...
X