{"audience":"Customer complaint teams, quality assurance, customer service and integration teams.","authorization_objects":[{"note":"Authorization to create quality notifications by notification type","object":"Q_QMEL"},{"note":"QM transaction authorization (QM01)","object":"Q_TCODE"}],"components":[],"countries":[],"effort_days_max":6,"effort_days_min":4,"effort_size":"M","faq":[{"a":"The program checks the external reference (QMEL-REFNUM). If a notification with this reference exists, the row is skipped as a \"duplicate\" and the existing notification number is shown in the message.","q":"What happens if the same complaint is sent twice?"},{"a":"Yes. The same check and creation logic can be published as an OData service or an RFC, so the portal writes the complaint to SAP immediately and gets the notification number back. The effort range grows with the service design.","q":"Can a direct portal connection be used instead of a file?"},{"a":"Yes. BAPI_QUALNOT_CREATE, BAPI_QUALNOT_SAVE, QMEL and QMFE are also used in S/4HANA; the file template stays the same.","q":"Does the program work on S/4HANA?"}],"features":[{"code":"background","label":"Runs as a background job","note":"An hourly job processes portal or CRM exports as they arrive in the application server folder."},{"code":"test_run","label":"Test mode (check without posting)","note":""},{"code":"log","label":"Line-by-line result and error log","note":""},{"code":"error_file","label":"Download failed lines as a separate file","note":""},{"code":"alv","label":"ALV list (sort, filter, subtotals)","note":""}],"functions":[{"name":"BAPI_QUALNOT_CREATE","role":"Creates the customer complaint notification for each row"},{"name":"BAPI_QUALNOT_SAVE","role":"Saves the notification created"},{"name":"BAPI_TRANSACTION_COMMIT","role":"Makes the save permanent"}],"gap":"QM01 creates notifications one by one and manually; if complaints are collected in another system, each one is typed again and delivery and batch data are often missing. The standard offers no ready file interface for customer complaints. The custom interface validates the complaints in the file, completes missing material and batch from the delivery item and opens the notifications through the standard BAPI.","id":"qm-customer-complaint-notification-interface","industries":[],"input_columns":[{"derived":false,"label":"External reference","required":true,"rule":"","target_field":"REFNUM","target_table":"QMEL"},{"derived":false,"label":"Customer","required":true,"rule":"","target_field":"KUNUM","target_table":"QMEL"},{"derived":false,"label":"Delivery","required":false,"rule":"","target_field":"LS_VBELN","target_table":"QMEL"},{"derived":false,"label":"Delivery item","required":false,"rule":"","target_field":"LS_POSNR","target_table":"QMEL"},{"derived":false,"label":"Material (blank = from delivery)","required":false,"rule":"","target_field":"MATNR","target_table":"QMEL"},{"derived":false,"label":"Batch (blank = from delivery)","required":false,"rule":"","target_field":"CHARG","target_table":"QMEL"},{"derived":false,"label":"Complaint quantity","required":true,"rule":"","target_field":"RKMNG","target_table":"QMEL"},{"derived":false,"label":"Unit","required":false,"rule":"","target_field":"MGEIN","target_table":"QMEL"},{"derived":false,"label":"Short text","required":true,"rule":"","target_field":"QMTXT","target_table":"QMEL"},{"derived":false,"label":"Defect code group","required":false,"rule":"","target_field":"FEGRP","target_table":"QMFE"},{"derived":false,"label":"Defect code","required":false,"rule":"","target_field":"FECOD","target_table":"QMFE"},{"derived":false,"label":"Priority","required":false,"rule":"","target_field":"PRIOK","target_table":"QMEL"}],"kind":"program","language":"en","lastmod":"2026-11-17","logic":"1. The file (CSV or XLSX) is read from the user's PC or, in a background job, from a folder on the application server. If a notification with the same external reference (QMEL-REFNUM) already exists, the row is skipped.\n2. Checks: the customer exists in KNA1; if a delivery is given, it belongs to the customer in LIKP; if a delivery item is given, material and batch are completed from LIPS and the complaint quantity may not exceed the delivered quantity (LIPS-LFIMG); the defect code group and code must exist in the catalog.\n3. BAPI_QUALNOT_CREATE is called with the selected notification type: customer, material, batch, complaint quantity and unit, delivery reference, priority and short text in the header; defect code group and code in the item; a description, if any, goes to the long text.\n4. The notification is saved with BAPI_QUALNOT_SAVE and BAPI_TRANSACTION_COMMIT. In test mode only the checks run and no notification is created.\n5. Result and message are listed per row; failed rows are written to a separate file and the processed file is moved to an archive folder.","module":"QM","object_type":"interface","output_columns":[{"calculated":true,"formula":"Row number in the file","label":"Row","source_field":null,"source_table":null},{"calculated":false,"formula":"","label":"External reference","source_field":"REFNUM","source_table":"QMEL"},{"calculated":false,"formula":"","label":"Notification","source_field":"QMNUM","source_table":"QMEL"},{"calculated":true,"formula":"Created, duplicate (skipped), test OK or error","label":"Status","source_field":null,"source_table":null},{"calculated":true,"formula":"Check message or the first message from the BAPI return table","label":"Message","source_field":null,"source_table":null}],"parameters":[{"example":"/interface/sikayet/gelen/","kind":"parameter","label":"File or application server folder","name":"P_FILE","ref_field":"","required":true},{"example":"Q1","kind":"parameter","label":"Notification type","name":"P_QMART","ref_field":"QMEL-QMART","required":true},{"example":"X","kind":"checkbox","label":"Move processed file to the archive folder","name":"P_MOVE","ref_field":"","required":false},{"example":"","kind":"checkbox","label":"Test mode (check without creating notifications)","name":"P_TEST","ref_field":"","required":false}],"part_of":["qm-complaint-root-cause-pack"],"performance":"Because complaint files are small, the program can run as an hourly background job. Check the external references for all rows in the file with a single SELECT.","process":"O2C","quote_url":"https://nekuhub.com/en/request-a-quote/?report=qm-customer-complaint-notification-interface","related":["qm-customer-complaint-batch-trace","qm-notification-defect-cause-pareto","qm-overdue-quality-notifications"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Creates quality notifications manually one at a time; does not read file or portal data.","tcode":"QM01"},{"note":"Changes an existing notification; does not create notifications in bulk.","tcode":"QM02"}],"summary":"A custom interface program that reads customer complaints exported by a web portal, CRM or call centre from a file and creates a customer complaint quality notification for each row, with delivery, material, batch and defect code. It prevents the same complaint from being created twice through the external reference and lists the result per row.","tables":[{"access":"read_write","join_on":"","role":"Notification headers created; duplicate check by external reference","table":"QMEL","variant":"both"},{"access":"write","join_on":"","role":"Notification defect item and defect code","table":"QMFE","variant":"both"},{"access":"read","join_on":"KNA1-KUNNR = QMEL-KUNUM","role":"Customer check","table":"KNA1","variant":"both"},{"access":"read","join_on":"LIKP-VBELN = QMEL-LS_VBELN","role":"Check that the delivery belongs to the customer","table":"LIKP","variant":"both"},{"access":"read","join_on":"LIPS-VBELN = QMEL-LS_VBELN AND LIPS-POSNR = QMEL-LS_POSNR","role":"Material, batch and delivered quantity from the delivery item","table":"LIPS","variant":"both"}],"title":"Customer Complaint Quality Notification Creation Interface from File or Portal","url":"https://nekuhub.com/en/programs/customer-complaint-quality-notification-creation-interface/","vendor_id":"nekudos"}