As a creator of structure Concession, I want to add fields to the NCR header with special logic (e.g. different dropdown values that depend on the selection on other fields).

1. + Label of field “Description” is changed to “Divergence description”. Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus)
2. + The field “Divergence description” (formerly “Description”) shall not be editable for the supplier. Only in case of Airbus NCR process(seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus)
3. x The field “Divergence description” (formerly “Description”) shall feature an input field that shows 4 lines instead of one (incl. scroll-bar at the right hand side, in case more input than the displayed 4 lines is provided). Same handling as for defect field “Defect Description” is expected. Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus).
4. - The field “Divergence description” is filled the following way (per defect), when defect data is saved:
   1. - “NonConformity [Nr. of the defect]:”
   2. - “NonConformity type:” & Fault Code Description
   3. - “Defect Description” of the defect
5. + New field on screen “NCR Details”, tab “Header” called “Concession type” (Not editable, Mandatory (user has to select it before creating the concession, so it will be there in any case), String 30). The field is filled with the “Concession type” that the NCR creator selected in the popup “Concession type selection”. Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
6. + The new header field “Concession type” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
7. + The new header field “Concession type” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
8. + The field “Concession Type” is a value / code combination, which means the user can select between values “Equipment” and “Material&Part” on the UI. However corresponding codes “CE” (in case of “Equipment”) & “CO” (in case of “Material&Part”) will be used for the M2M message.
9. + The new header field “Concession type” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
10. x New field on screen “NCR Details”, tab “Header” called “Factory Code” (Mandatory, String 4). Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
11. x The new header field “Factory Code” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
12. x The new header field “Factory Code” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
13. x The new header field “Factory Code” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
14. + New field on screen “NCR Details”, tab “Header” called “Normalized” (Mandatory, Dropdown selection: Yes / No). Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
15. + The new header field “Normalized” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
16. + The new header field “Normalized” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
17. + The new header field “Normalized” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
18. + New field on screen “NCR Details”, tab “Header” called “CA code” (Conditional, String 5). Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
19. + The new header field “CA code” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
20. + The new header field “CA code” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
21. + The new header field “CA code” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
22. + New field on screen “NCR Details”, tab “Header” called “CA serial number” (Conditional, String 15). Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
23. + The new header field “CA serial number” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
24. + The new header field “CA serial number” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
25. + The new header field “CA serial number” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
26. x The “CA serial number” must only be used once, in case the supplier uses the same CA serial number for the same networklink one more time, there shall be an error message (exact wording of the error message to be defined). Similar function to content of existing field “NCR Supplier Reference”, which can also only be used once.
27. x The “CA serial number” needs to start with the content of the field “Factory Code”. If this is not the case, on validation there shall be an error message displayed for the user (exact wording of the error-message to be defined).
28. + New field on screen “NCR Details”, tab “Header” called “Drawing number” (Conditional, String 15). Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
29. - The new field “Drawing Number” is initially set mandatory, however when the user selects value “Yes” for field “Normalized”, the field becomes optional.
30. + The new header field “Drawing number” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
31. + The new header field “Drawing number” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
32. + The new header field “Drawing number” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama)
33. + The new header field “Drawing Number” shows the following mouse-over information: “For Example: Drawing number is currently first 9 digits from Customer material number F3837003700800 = F38370037 or ASNA3133-5625 = ASNA3133”
34. ***** New field on screen “NCR Details”, tab “Header” called “Liability” (Mandatory, String 15, drop-down list selection: Supplier (set per default) / Airbus). Input to be handeled as value / code combiation (0001 = Supplier / 0002 = Airbus). Value used for UI, while code is used for M2M. Only in case of Airbus NCR process (seescmdb0.torganization_scd.cncrcustomerconfigtype = Airbus). See mockup in the “Refinement” area.
35. ***** The new header field “Liability” is included in the table display on screen “NCR Overview”, tab “NCR Overview” (hidden for the default table profile, can be added manually)
36. ***** The new header field “Liability” is considered for the advanced search on screen “NCR Overview”, tab “NCR Overview” (not to be considered for quick search)
37. ***** The new header field “Liability” is included in the outbound M2M message to the customer backend system (placement inside the message to be defined with help of Samy Scemama). Content in the Boost XML message will only be the code, not the value.
38. + The following dynamic logic applies that determines state mandatory/optional for the following fields:
    1. + If MSN is filled in all the following fields are mandatory:
       1. CA code
       2. CA Serial Number
       3. Aircraft Type
    2. x If CA code and CA Serial Number are filled in, all the following field are not mandatory:
       1. MSN
       2. Aircraft Type
    3. x If the part reference is a CA (rule to identify CA t.b.d.), all the following field are mandatory:
       1. CA code
       2. CA Serial Number

• Divergence description (only for AIRBUS)
  • Change label from “Description” to “Divergence description”
  • Field should be not editable for supplier
  • Input area with 4 visible lines (like “Defect description”)
  • The field “Divergence description” is filled the following way (per defect), when defect data is saved:
    • “NonConformity [Nr. of the defect]:”
    • “NonConformity type:” & Fault Code Description
    • “Defect Description” of the defect
• New field “Concession type”
  • + 30 chars
    • + extend SQL
  • - mandatory
  • Filled with “Concession type” selected on creation.
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • Only for AIRBUS
• New field “Normalized”
  • + boolean
    • + add to SQL
    • + add to model
  • Mandatory
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • Only for AIRBUS
• New field “CA code”
  • + 5 characters
    • + add to SQL
    • + add to model
  • Conditional
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • Only for AIRBUS
• New field “CA serial number”
  • + 15 characters
    • + add to SQL
    • + add to model
  • - Conditional
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • Only for AIRBUS
• New field “Drawing number”
  • + 15 characters
    • + add to SQL
    • + add to model
  • - The field is initially set mandatory, however when the user selects value “Yes” for field “Normalized”, the field becomes optional.
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • The new header field “Drawing Number” shows the following mouse-over information: “For Example: Drawing number is currently first 9 digits from Customer material number F3837003700800 = F38370037 or ASNA3133-5625 = ASNA3133”
  • Only for AIRBUS
• New field “Liability”
  • ***** 15 characters
    • ***** add to SQL
    • ***** add to model
  • Mandatory
  • drop-down list selection: Supplier (set per default) / Airbus). Input to be handeled as value / code combiation (0001 = Supplier / 0002 = Airbus). Value used for UI, while code is used for M2M.
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • Include in outbound M2M message (placement TBD by Marc Harazim)
  • Only for AIRBUS
• The following dynamic logic applies that determines state mandatory/optional for the following fields:
  • If MSN is filled in all the following field are mandatory:
    • CA code
    • CA Serial Number
    • Aircraft Type
  • If CA code and CA Serial Number are filled in, all the following field are not mandatory:
    • MSN
    • Aircraft Type

• New field “Concession type”
  • + 30 chars
    • + extend SQL
  • ***** mandatory (nothing to do, because it is filled with “Concession type” selected on creation)
  • - Write a “renderer” for this field
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • + Extend XSD
    • - Implement logics
    • - Test
  • Only for AIRBUS
• Divergence description (only for AIRBUS)
  • Change label from “Description” to “Divergence description”
  • Field should be not editable for supplier
  • Input area with 4 visible lines (like “Defect description”)
  • The field “Divergence description” is filled the following way (per defect), when defect data is saved:
    • “NonConformity [Nr. of the defect]:”
    • “NonConformity type:” & Fault Code Description
    • “Defect Description” of the defect
• New field “Normalized”
  • + boolean
    • + add to SQL
    • + add to model
  • Mandatory
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • - Extend XSD
    • - Implement logics
    • - Test
  • Only for AIRBUS
• New field “CA code”
  • + 5 characters
    • + add to SQL
    • + add to model
  • Conditional
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • - Extend XSD
    • - Implement logics
    • - Test
  • Only for AIRBUS
• New field “CA serial number”
  • + 15 characters
    • + add to SQL
    • + add to model
  • - Conditional
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • - Extend XSD
    • - Implement logics
    • - Test
  • Only for AIRBUS
• New field “Drawing number”
  • + 15 characters
    • + add to SQL
    • + add to model
  • - The field is initially set mandatory, however when the user selects value “Yes” for field “Normalized”, the field becomes optional.
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • - Extend XSD
    • - Implement logics
    • - Test
  • The new header field “Drawing Number” shows the following mouse-over information: “For Example: Drawing number is currently first 9 digits from Customer material number F3837003700800 = F38370037 or ASNA3133-5625 = ASNA3133”
  • Only for AIRBUS
• New field “Liability”
  • ***** 15 characters
    • ***** add to SQL
    • ***** add to model
  • Mandatory
  • drop-down list selection: Supplier (set per default) / Airbus). Input to be handeled as value / code combiation (0001 = Supplier / 0002 = Airbus). Value used for UI, while code is used for M2M.
  • Include column in overview (hidden for default profile)
  • Include column in advanced search of overview
  • - Include in outbound M2M message
    • - Extend XSD
    • - Implement logics
    • - Test
  • Only for AIRBUS
• The following dynamic logic applies that determines state mandatory/optional for the following fields:
  • If MSN is filled in all the following field are mandatory:
    • CA code
    • CA Serial Number
    • Aircraft Type
  • If CA code and CA Serial Number are filled in, all the following field are not mandatory:
    • MSN
    • Aircraft Type

• Wie soll der Inhalt des Tooltips von dem Feld “Drawing number” sein? In der Spec steht: “For example….”
  • Es soll exakt wie in Spec beschrieben implementiert werden.
• Wie wird das Feld “Divergence description” gerendert? Momentan “gelb”, weil mandatory, und man kann aber nichts eintippen, da es woanders gemacht wird.
  • Das Feld soll als “Label” gerendert werden.
• Wie wird das Feld “Divergence description” gefüllt? Existiert ein Extra-(Sub-)Task dafür?
  • Ja, AIRS-1070
• Die mandatory/optional Logik funktioniert nicht wg. Aircraft Type. Beispiel: MSN wird gefüllt ⇒ CA Code, CA Serial Number, Aircraft Type sind mandatory, jetzt werden CA Code & CA Serial number gefüllt ⇒ Aircraft Type geht auf NOT mandatory.
  • Marc klärt es mit Airbus. → das zweite Teil der Spec ist gestrichen, deshalb werden nur 3 Felder mandatory/optional abhängig von MSN
• In der Spec steht: If CA code and CA Serial Number are filled in, all the following field are not mandatory: MSN, Aircraft Type. Das Feld MSN war meines Wissens nie “Mandatory”. Was soll hier gemacht werden?
  • Marc klärt es mit Airbus. → dieses Teil der Spec ist gestrichen, deshalb ist das Feld einfach immer optional