Extensive Testing: API

•  Alle notwendigen Felder sind vorhanden und in richtigem Format (Linkfelder) 
• Contract Type: postpaid 
• Contract Type: adhoc 
• Contract Type: hubject cpo 
• Fabian Ringwald Use Case - 2 Entitäten User und Person
• Fetch Organization 
  • Adress, Contacts, Payment Terms available? 
  • Organization Supplier
  • Organization Customer 
  • Organization both 
  • Related Contracts? 
• Fetch Person 
  • Adress, Contacts, Payment Terms available? 
  • Organization Supplier 
  • Organization Customer 
  • Organization both 
  • Related Contracts? 
• Fetch Employee 
  • linked Company correct? 
• Supplier 177 
  • Contract Hubject 507
  • Contract Adhoc 117

Testing feedback: 

• Payment Methods missing
• In case of person/organization should we link respective contracts to supplier and customer to differentiate? Currently the contract is linked to Party only if p/o is supplier. Example: https://becharged.f.erpnext.com/app/gridware-party/GDW-P-000348 

Contracts: 

• Authorizaton Contracts: The supplier is always becharged, which is wrong: https://cloud.becharged.de/backoffice/contracts/275 vs. https://becharged.f.erpnext.com/app/gridware-contract/GWC-0000180 
• Contract Company Car:
  

--> 

• Contract DocType improvements: 

--> Linkfield will be postponed

• Error Code occuring: Can we change this to "Contract already existing"

Gridware Usage: 

• Time format 

• Re-calculation of wh to kwh -> Values are more like: decimal number (eleven point three five five not as eleven thousand three hundred fifty-five
• Use Case: Paying Customer vs. User
  
• 
• Sometimes there are a view usages missing per contract (always between 1-4) 

Party Master: 

• SEPA Mandates: 

•